[{"name":"C4-233066","title":"LS on GSMA 5GMRR Working Solution Assumption L-PRINS and Data Session Control","source":"GSMA 5GMRR","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"The GSMA 5GMRR group has reached the conclusion that these services cannot be realized within the current 3GPP 5G SA security framework without adaptations.\nGSMA 5GMRR kindly asks 3GPP to review the following proposals and service flows considered as working solution assumptions within 5GMRR and as enablers for the roaming service implementation.\n... ...\nL-PRINS is a hop-by-hop solution which offers a digital signature protection for all N32-f messages between any two immediate hops over the N32 interface. GSMA 5GMRR considers L-PRINS to be a potential milestone towards a solution with end-to-end security between the VPLMN and the HPLMN.\nThe solution as described in the attached document (5GMRR Doc 41_11) can be used to provide a possible E2E attribution via cryptographical means using offline processing that can be used for convincing a third party.\nGSMA 5GMRR anticipate the update to 3GPP specifications as follows:\n1.\t3GPP SA3 and CT4 to evaluate whether the existing PRINS modificationsBlock can be reused by SEPP for providing a digital signature protection (asymmetric) to the whole N32-f message or a new or similar procedure is required.\n2.\t3GPP SA3 and CT4 to define a new security capability of L-PRINS in addition to the two existing ones, i.e., in addition to TLS and PRINS. GSMA 5GMRR believes that this approach is best to avoid any backward compatibility issue and to provide a path forward to using PRINS for end-to-end security in the future.\nAction to 3GPP CT4: \n1.\tGSMA 5GMRR kindly requests 3GPP CT4 to evaluate whether the existing PRINS modificationsBlock can be reused by SEPP for providing an asymmetric digital signature protection to the whole N32-f message or a new or similar procedure is required. Additionally, to look into defining a new security capability that meets L-PRINS working solution assumption.\n2.\tIf CT4 receives a positive confirmation on the security aspects of the working solution assumption presented in this LS, GSMA 5GMRR kindly request 3GPP CT4 update its respective specification as needed.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30660,"status":"noted","reservation_date":"2023-08-01 05:20:49","uploaded":"2023-08-01 07:45:18","revisionof":"C4-232010","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA2, SA3, CT4","Cc":"3GPP SA, SA1","lsoriginalls":"5GMRR Doc 41_41r3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233066.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233067","title":"LS Reply on PRINS middle boxes","source":"SA3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"3GPP SA3 would like to point out that this kind of session management as well as the concept of intermediaries originating signalling messages are not covered by the current 5G architecture. More generally, if there is a requirement for intermediaries to generate arbitrary messages within the context of other use cases that are currently not described, there may be further security issues, e.g. with subscriber privacy, if intermediaries are allowed to ask for subscriber location.\nSA3 would like to request SA2 to verify whether this kind of message injection would be aligned with 5G system architecture and procedures. \nIndependently, SA3 would like to inform 5GMRR that SA3 believes that the potential for state mismatch between cNF and pNF may also have security impacts. 3GPP SA3 would like to inform GSMA 5GMRR that SA3 is willing to work with 5GMRR to enable an end to end secure solution. However, a stable and comprehensive set of requirements is necessary.\nSA3 has included a potential solution (see attached S3-231419) that is under discussion (i.e. not agreed yet) to understand, whether this would provide the required features as required by GSMA 5GMRR. Further analysis of the solution will take place in SA3 to fully understand the security and privacy impact.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30670,"status":"noted","reservation_date":"2023-08-01 05:21:10","uploaded":"2023-08-01 07:45:18","revisionof":"C4-232011","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"LS 5GMRR#40 Doc 05","lsto":"GSMA 5GMRR, 3GPP CT4, 3GPP SA2","Cc":"GSMA DESS","lsoriginalls":"S3-231389","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233067.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233069","title":"LS on the Applicability of the Unavailability Period for Dual Registered UEs","source":"CT1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"CT1 is currently working on stage 3 aspects of SUECR. CT1 would like to ask about the Applicability of the Unavailability Period for Dual Registered UEs. For example, is there an assumption that dual registered UEs will not use the Unavailability Period, is there an assumption that a dual registered UE will deregister from the EPC before applying the Unavailability Period to its 5GC registration, or is there an assumption that the MME will be made aware of the unavailability period?","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30690,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"SUECR"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT4","lsoriginalls":"C1-233275","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233069.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233070","title":"Reply LS on issues related to SNPN selection for localized services","source":"CT1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"CT1 would like to thank SA2 for the LS S2-2305772 \"Reply LS on issues related to SNPN selection for localized services\".\n\nCT1 would like to inform SA2 that CT1 decided to continue using:\n- \"credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN\"; and\n- \"credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN\".","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30700,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA1, CT4","lsoriginalls":"C1-234302","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233070.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233071","title":"Reply LS on having OpenAPI changes only in GitLab","source":"CT1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"CT1 thanks CT3 and CT4 from their jointly provided LS on having OpenAPI changes only in GitLab.\n\nCT1 has discussed the information provided by CT3 and CT4 and CT1 would also like to continue using the existing method of handling source code in 3GPP documentation for specifications under its remit.\n\nFinally, CT1 wants also to continue applying the same methodology and process as per CT3 and CT4.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30710,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP CT, 3GPP SA, 3GPP CT WG3, 3GPP CT WG4,","Cc":"3GPP SA WG5","lsoriginalls":"C1-234390","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233071.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233072","title":"Reply LS on removal of unspecified QoS monitoring control option","source":"CT3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"CT3 thanks SA2 for their LS on removal of unspecified QoS monitoring control option, and would like to inform SA2 that CT3 agrees to remove the option to report \u201cwhen the PDU Session is released\u201d from Rel-16 onwards.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30720,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT4","lsoriginalls":"C3-232192","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233072.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233073","title":"Reply LS on MBS service area update clarification","source":"CT3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"CT3 thanks SA6 for their LS on clarifying MBS service area update procedures.\nRegarding the below question to CT3:\n\"Q2. SA6 would like to ask CT3 and CT4 to clarify the scenario(s) when the error \"UNKNOWN_MBS_SERVICE_AREA 404 Not Found The requested MBS service area (e.g. identified by the Area Session ID) cannot be found.\" in 3GPP TS 29.522 can occur? Is the MBS service area not found in MB-SMF, NRF or NEF? Can it occur during MBS session update?\"\nCT3 would like to provide the below answer:\n-\tThis HTTP \"404 Not found\" error status code response and the corresponding \"UNKNOWN_MBS_SERVICE_AREA\" application error are simply relayed by the NEF to the AF when received from the MB-SMF as specified in the last paragraph of clause 4.4.29.3.5 of TS 29.522.\n-\tThis error case is not related to the procedure of MBS Session update request with an updated MBS Service Area. It is rather related to the case where the received Area Session ID in an MBS Session Status Subscription request is not found. CT3 has agreed the attached CR to further clarify this.\nCT3 will wait for the feedbacks from SA2 and CT4 to provide further feedback and update its specifications accordingly, if necessary. CT3 would also like to point out that this issue should also be studied for the case where the MBSF is used.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30730,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18"},{"winame":" 5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6 and SA3","Cc":"","lsoriginalls":"C3-232410","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233073.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233074","title":"Reply LS on GNSS integrity parameters","source":"RAN2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"RAN2 would like to thank CT4 for the LS on GNSS integrity requirement parameters definition, and would like to ask CT4 to take the following RAN2 feedback into consideration:\nQuestion: CT4 would like to kindly ask RAN2 to define the data structure of TTA, TIR and AL, and provide the related reference to CT4 in order to implement this feature.\nAnswer: The requested parameters TIR, AL and TTA are represented as follows\n-\tTarget Integrity Risk (TIR): The range can be adopted from TS 37.355 defined within TargetIntegrityRisk-r17 of IE CommonIEsRequestLocationInformation. The recommended range is calculated by P=10-0.1n [hour-1] where n is from 10 to 90 and the range of the TIR is 10-1 to 10-9 per hour.\n-\tAlert Limit (AL): The parameter is separated into a horizontal and vertical alert limit. The range can be adopted from horizontal and vertical protection level defined in TR 37.355 within IntegrityInfo-r17 of the IE CommonIEsProvideLocationInformation. The recommended range for both horizontal and vertical alert limit are 0 to 500 meters, with 0.01 meters granularity. \n-\tTime to Alert (TTA): The range can be adopted from the use cases for integrity listed in TR 38.857, Table 9.2.4, where the TTAs listed in different use cases have the range from 100ms to 30s. The recommended value range is from 0.1 to 30s, with 0.1s granularity.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30740,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_pos_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"SA2","lsoriginalls":"R2-2306681","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233074.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233075","title":"Reply LS on INACTIVE eDRX above 10.24sec and SDT","source":"RAN3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"RAN3 thanks RAN2 for their LS (R2-2302082 \/ S2-2303947) on \u201cINACTIVE eDRX above 10.24sec and SDT\u201d and thanks SA2 for their reply LS (R3-232506 \/ S2-2305619) on that matter.\n\nRAN3 would like to inform SA2, RAN2 and CT4 that RAN3 discussed the changes to the NGAP signalling based on the updated call flows from SA2 in TS 23.502:\n1.\tRAN3 has agreed to include the RAN configured Paging Time Window (PTW) in the MT COMMUNICATION HANDLING REQUEST message, when the NG-RAN sends this message to request CN applying HLCOM.\n2.\tFollowing SA2 and CT4 updates, RAN3 has agreed to include the QFI, PPI, ARP and PDU session ID of the QoS Flow in the DL DATA NOTIFICATION message from AMF to NG-RAN requesting connection resume. Concerning signalling 5QI, RAN3 is still discussing it and would like to check with SA2, if the signalled 5QI can be different than the one associated with the stored QFI in the RAN UE context. \n3.\tFurthermore, RAN3 has discussed the need to signal the DL data size in the DL DATA NOTIFICATION message to help NG-RAN making decision if MT-SDT paging can be performed based on the QFI associated with the configured SDT radio bearer. RAN3 would like to ask SA2 and CT4 whether it is feasible that DL data size can be signalled to the NG-RAN (e.g. for QoS flows that have buffered data in the CN) along with the paging differentiation parameters to assist NG-RAN for MT-SDT paging decision.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30750,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_REDCAP_Ph2"},{"winame":" NR_redcap_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, CT4","Cc":"RAN2","lsoriginalls":"R3-233347","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233075.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233076","title":"LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"SA1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA1 has discussed the LSs from GSMA 5GMRR, S1-231055, 056, 057 and 058 as well as the LS from SA3 S1-231034, and concluded that a SA1 study would be needed to describe and discuss the use cases and derive potential service requirements. \nSA1 suggest SA to inform GSMA 5GMRR that SA1 welcomes all interested parties to contribute in SA1 with their use cases and requirements.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30760,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA, SA3","Cc":"SA2, CT4","lsoriginalls":"S1-231776","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233076.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233077","title":"Reply LS on 3GPP work on Energy Efficiency","source":"SA1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30770,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"EE5GPLUS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"SA, RAN, CT, SA1, SA2, SA3, SA4, SA6, RAN1, RAN2, RAN3, RAN4, CT3, CT4","lsoriginalls":"S1-231805","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233077.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233078","title":"LS reply to RAN3 progress on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 thanks RAN3 for the progress to address the Editor's notes in TS 23.502 related to NGAP messages and has agreed the attached CR for TS 23.502 taking the progress into account.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30780,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_redcap_enh"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN3","Cc":"RAN2, CT4","lsoriginalls":"S2-2307730","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233078.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233079","title":"LS on DCCF subscriptions to UPF","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 thanks CT3 for their LS. SA2 have discussed it and would like to answer that when the NWDAF uses DCCF services to get information from an UPF, the DCCF is a consumer of the UPF event exposure service i.e. according to the conditions described in 23.501 clause 5.8.2.17 the DCCF determines to perform a subscription to the UPF directly or a subscription to the UPF via the SMF.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30790,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"UPEAS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"CT4","lsoriginalls":"S2-2307736","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233079.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233080","title":"LS on UE memory available for SMS","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"When looking at the architecture for notification Event Type \"UE memory available for SMS\", SA2 has noticed that this feature was incomplete in SA2 5GC specifications. The Event Type \"UE memory available for SMS\" was included in the Event Type list in Rel-17 and Rel-18 versions of TS 23.502 but the UDM procedures to detect this notification event were not specified. This was not even possible, as neither the AMF nor the UDM has got the information that is required to generate this monitoring event report. \n\nTo correct this, SA2 has agreed the attached CRs from Rel-17 onwards to allow the SMSF to provide the UE memory available for SMS information to the UDM to trigger it to send monitoring event report. SA2 uses the Alert procedure specified in TS 23.540 by referencing to it from TS 23.502.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30800,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SMS_SBI"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, CT4","Cc":"","lsoriginalls":"S2-2307793","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233080.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233081","title":"LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 has discussed the LSs from GSMA 5GMRR, S2-2306270, 6271, 6272, 6273, and LS in S2-2306304 from SA3 and concluded that use cases and service requirements need to be clarified by SA1 before work can be started in SA2 and SA2 will then analyze whether and which agreed requirements and use cases can be supported by the current specifications or require extensions. Any such work is expected to follow the usual 3GPP process.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30810,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA, SA3","Cc":"SA1, CT4","lsoriginalls":"S2-2307983","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233081.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233083","title":"Non-homogeneous deployment of PDU Set based handling","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30830,"status":"noted","reservation_date":"2023-08-01 05:37:49","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN3, CT4","Cc":"RAN2","lsoriginalls":"S2-2308252","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233083.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233084","title":"Reply LS on Security architecture for 5G multicast\/broadcast services","source":"SA3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA3 thanks SA2 for the Reply LS on security architecture for 5G multicast\u2013broadcast services. For the deployment issue of MBSSF, SA3 agrees that the MBSSF needs to be (not only \"can be\") located in MBSF or MBSTF in Rel-17. The clause W4.1 in TS 33.501 is also updated accordingly. Please find the detailed information in the attachment.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30840,"status":"noted","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA4, CT4","lsoriginalls":"S3-233139","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233084.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233085","title":"LS on Further input to address GSMA LS on requirements for intermediaries in the roaming ecosystem (S3-232344)","source":"SA3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30850,"status":"noted","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA1, SA2, CT4","lsoriginalls":"S3-233308","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233085.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233086","title":"LS on Clarification on Removal of the Indicator of UUAA result from AMF","source":"SA3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"To address the LS C4-230790\/S3-232322 from CT4, SA3 is currently discussing on the need to consider the UUAA successful results during the UUAA invocation and the related need of the indicator sent from the AMF to the SMF that successful UUAA-MM has already been performed. Based on the change in CR S2-2210930 made in TSG-SA2 Meeting #154, it implies that the UUAA during PDU session establishment is mandatory even if a successful UUAA is already performed during registration, another UUAA process is still initiated during the PDU session establishment, so sending of the indicator that \u2018successful UUAA-MM has already been performed\u2019 from the AMF to the SMF may not be needed if UUAA initiation is always mandatory at SMF. Currently according to TS 23.256 Clause 4.3.2 UAS NF, it states that \u2018To support re-authentication\/re-authorization and revocation request by USS, the UAS NF stores information as to whether the re-authentication\/re-authorization and revocation is towards an AMF or SMF\/SMF+PGW-C and the address of the serving AMF or SMF\/SMF+PGW-C. UAS NF stores the result of UUAA-MM procedures and the result of UUAA-SM procedures\u2019.. However, we also observe the following statements in steps of Clause 5.2.2.1 in TS 23.256 V18.0.0 (2023-03) which still states the AMF stores a successful UUAA result.\n?\tIn step 4 of subclause 5.2.2.1, \u201cThe AMF stores in the UE context that a UUAA is pending.\u201d\n?\tIn step 6 of subclause 5.2.2.1, \u201cOnce the UUAA-MM procedure is successfully completed for the UAV, the AMF stores a successful UUAA result and updates the UE context indicating that UUAA is no longer pending.\u201d\n?\tIn step 3 of subclause 5.2.2.1, \u201c3. AMF shall determine whether UUAA-MM is required for the UAV. The AMF decides that UUAA is required if:\na)\tthe UE has a valid Aerial UE subscription information;\nb)\tUUAA is to be performed during Registration according to local operator policy;\nc)\tthere is no successful UUAA result from a previous UUAA-MM procedure;\nd)\tthe UE has provided a CAA-Level UAV ID.\u201c.\n?\tTS 23.256 Clause 5.2.1 UUAA Model states that, \u2018If UUAA-MM is not performed, the UAV shall be authenticated by UUAA-SM during the PDU session establishment procedure for UAS service\u2019.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30860,"status":"noted","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"UAS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT4","lsoriginalls":"S3-233322","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233086.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233087","title":"Reply LS on security architecture for 5G multicast\u2013broadcast services","source":"SA3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA3 thanks SA4 for the Reply LS on security architecture for 5G multicast\u2013broadcast services. SA3 agrees to update the Control Plane procedure in TS 33.501 clause W.4.1 to keep an architectural consistency between the Control Plane procedure and the User Plane procedure. Please find the detailed information in the attachment.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30870,"status":"noted","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA4","Cc":"SA2, CT4","lsoriginalls":"S3-233439","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233087.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233088","title":"LS on 3GPP work on Energy Efficiency","source":"SA4","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30880,"status":"noted","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"EE5GPLUS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA5, 3GPP TSGs SA, RAN, CT","Cc":"3GPP WGs SA1, SA2, SA3, SA6, RAN1, RAN2, RAN3, RAN4, CT1, CT3, CT4","lsoriginalls":"S4-231111","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233088.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233089","title":"Reply LS on object acquisition","source":"SA4","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30890,"status":"noted","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" 5MBUSA"},{"winame":" 5MBP3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP CT4","Cc":"3GPP CT3, 3GPP SA3","lsoriginalls":"S4-231116","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233089.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233090","title":"LS on Enhancement on Charging Identifier Uniqueness Mechanism","source":"SA5","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"SA5 thanks CT4 for the incoming LS on Enhancement on Charging Identifier Uniqueness Mechanism.\nThe (TS 29.571 CR 0389 rev1 is inline with the recommendations proposed by SA5, i.e., that it should be unique.\nThere are three CRs for TS 32.255 on the Charging Identifier handling for the following scenarios:\n-\tInter-PLMN mobility for HPLMN to VPLMM, i.e., V-SMF insertion\n-\tInter-PLMN mobility between R17 VPLMN and pre-R17 VPLMM for a HR PDU Session\n-\t5GS to EPS Mobility for a HR PDU Session with String based Charging ID assigned by R17 V-SMF\n-\tEPS to 5GS mobility for a HR PDU Session with R17 H-SMF and R17 V-SMF","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30900,"status":"postponed","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"C4-234354","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP CT4","Cc":"3GPP CT3","lsoriginalls":"S5-234452","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233090.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233091","title":"Reply LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"TSG SA","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"3GPP TSG SA has concluded that the roaming requirements in the LSs from GSMA 5GMRR need a SA1 study to describe and discuss the use cases and derive potential service requirements. SA invites interested parties to contribute their use cases and requirements in 3GPP SA1 as per normal 3GPP working procedures. This would then be followed by any architectural and protocol work as needed.\n3GPP TSG SA would like to inform GSMA that earliest possibility to undertake this work would be Rel-19 (refer to 3GPP workplan in SP 230738).","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30910,"status":"noted","reservation_date":"2023-08-01 05:37:50","uploaded":"2023-08-01 07:40:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GMRR","Cc":"3GPP SA1, 3GPP SA2, 3GPP SA3, 3GPP SA5, 3GPP CT4","lsoriginalls":"SP-230763","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233091.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233092","title":"LS to 3GPP on the introduction of the domain \u201cipxnetwork.org\u201d in addition to \u201c3gppnetwork.org\u201d","source":"GSMA 5GMRR","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Action","abstract":"To differentiate between SEPP instances deployed by either a PLMN or managed by a service provider on behalf a PLMN (Outsourced SEPP) versus SEPP instances of a service provider (Hosted SEPP and Hub based use cases), the new distinct domain name \u201cipxnetwork.org\u201d has been introduced in support of the latter instances.\nThe domain name \"3gppnetwork.org\" has been referenced in TS 23.003 and TS 33.310, and there may be more instances in other 3GPP specifications. It is suggested to add a reference to the domain \"ipxnetwork.org\" in those cases as well.\nPlease note that the domain \"ipxnetwork.org\" is an existing dormant GSMA domain name and was originally introduced in anticipation for the support of e.g. specific roaming use cases with SS7 and Diameter.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":30920,"status":"noted","reservation_date":"2023-08-01 08:11:12","uploaded":"2023-08-01 08:12:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA2, SA3 and CT4","Cc":"5GMRR, NRG, DESS","lsoriginalls":"5GMRR Doc 42a_04r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233092.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233501","title":"Reply LS on INACTIVE eDRX above 10.24sec and SDT","source":"Ericsson","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":35100,"status":"revised","reservation_date":"2023-08-16 23:15:57","uploaded":"2023-08-16 23:15:57","revisionof":"","revisedto":"C4-233691","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, RAN3","Cc":"RAN2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233501.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233535","title":"N32 Race conditions and recovery","source":"5GMRR","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":35350,"status":"postponed","reservation_date":"2023-08-21 17:01:31","uploaded":"2023-08-21 17:09:31","revisionof":"","revisedto":"C4-234355","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233535.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233536","title":"LS-Reply on Introduction of the domain \"ipxnetwork.org\"","source":"SA3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":35360,"status":"noted","reservation_date":"2023-08-21 17:03:45","uploaded":"2023-08-21 17:09:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233536.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233537","title":"Reply LS on Security Context Transfer between MBSF and MBSTF","source":"SA3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":35350,"status":"postponed","reservation_date":"2023-08-21 17:05:39","uploaded":"2023-08-21 17:09:31","revisionof":"","revisedto":"C4-234356","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233537.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-233691","title":"Reply LS on INACTIVE eDRX above 10.24sec and SDT","source":"Ericsson","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":35101,"status":"approved","reservation_date":"2023-08-19 23:15:57","uploaded":"2023-08-19 23:15:57","revisionof":"C4-233501","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, RAN3","Cc":"RAN2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_117_Goteborg\/Docs\/C4-233691.zip","group":"C4","meeting":"C4-117","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]