[{"name":"C4-234354","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":43540,"status":"noted","reservation_date":"2023-09-29 10:09:13","uploaded":"2023-09-29 11:03:10","revisionof":"C4-233090","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"},{"winame":" TEI17"}],"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_118_Xiamen\/Docs\/C4-234354.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234355","title":"N32 Race conditions and recovery","source":"5GMRR","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"Request to 3GPP\nGSMA NRG 5GMRR kindly requests 3GPP to clarify how N32 race conditions and recovery states should be handled by the SEPP.\nActions\n3GPP is kindly asked to take the following actions:\nSA3 to take the above into account and to provide feedback.\nCT4 to describe the behaviour of the SEPP in case N32-c handshake requests are received for existing N32 contexts and how potential race conditions should be resolved.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43550,"status":"noted","reservation_date":"2023-09-29 10:09:31","uploaded":"2023-09-29 11:03:10","revisionof":"C4-233535","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_118_Xiamen\/Docs\/C4-234355.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234356","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":"SA3 thanks CT4 for the LS on Security Context Transfer between MBSF and MBSTF. SA3 updated 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 as SA3 replied from the SA3 May meeting (S3-232689).\n\nCT4 asked following question regarding the Control-Plane procedure:\n\nQuestion 1: Since Rel-17 is frozen, CT4 intends to discuss deletion of above Editor's note in Q3 without changing CT4 specifications. Kindly provide feedback if any.\n\nSA3 answer for question 1:\n\nSA3 is fine to remove the editor\u2019s note without additional change.\n\n\n\nCT4 asked following question regarding the User-Plane procedure:\n\nQuestion 2: If MBSSF is co-located with MBSF, does CT4 need to update Nmb2 APIs to support transferring both MSK and MTK from NF-Service-Consumers of Nmbstf_MBSDistributionSession Service (e.g. MBSSF) to MBSTF over Nmb2? \n\nSA3 answer for question 2: No. MBSSF is logical function. When MBSSF is located in MBSF, the interface between MBSF and MBSTF for MSK\/MTK transfer is up to the implementation of the deployment options in Rel-17 and Rel-18. The same applies when the MBSSF is located in the MBSTF.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43560,"status":"noted","reservation_date":"2023-09-29 10:09:53","uploaded":"2023-09-29 11:03:10","revisionof":"C4-233537","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_118_Xiamen\/Docs\/C4-234356.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234357","title":"LS on the scope of LCS-SS messages transferred via the LCS user plane","source":"CT1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"CT1 has been discussing the LCS user plane protocol to transfer LCS supplementary service (LCS-SS) messages in stage 3 specifications.\n\nCurrently, different messages (e.g., MO-LR, event reporting, location privacy setting) can be encapsulated in the LCS-SS message. As per the statement in clause 5.10 of TS 23.273, the LCS-SS messages and LPP messages can be transferred via the user plane. However, only the event reporting message is stated in clause 6.18 of TS 23.273.\n\nCT1 would like to ask SA2 to confirm the scope of LCS-SS messages transferred via the user plane.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43570,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT4","lsoriginalls":"C1-236453","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234357.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234358","title":"LS on defining PIN ID format","source":"CT1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"CT1 has worked on the protocol aspects of PIN work item for Rel-18. One of the points that are not finalized yet is the format of PIN ID. CT1 assumes that the format should be defined in the stage 2, so that CT1 refers and designs protocol accordingly. So CT1 would like to ask SA2 to define or provide the format of PIN ID.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43580,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT3, CT4","lsoriginalls":"C1-236503","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234358.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234359","title":"LS on LPP message and supplementary service event report over a user plane connection between UE and LMF","source":"CT1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 Question:\n\u201cSA2 kindly asks CT1 and CT4 to comment on suitable types of user plane address for the LMF supporting user plane positioning (e.g. such as an IP address and\/or FQDN) and whether, which or what the transport protocols and application level messages to transfer LPP messages and supplementary service event report could be identified or defined by CT1 or CT4.\u201d\nCT1 Answer:\nFor specification of transport of LPP messages and supplementary service event reports over a user plane connection between UE and LMF, CT1 has decided to specify a new protocol, LCS-UPP, in 3GPP TS 24.572. The LCS-UPP protocol provides connectivity on a secure user plane connection and supports both LPP and supplementary services.\nCT1 further noted that user plane positioning using SUPL is described in 3GPP TS 38.305 and 3GPP TS 23.271 since Rel15, and it is the view of CT1 that this option remains unchanged even after introducing the user plane positioning based on LCS-UPP. CT1 intends to specify requirements for co-existence between the SUPL option and the LCS-UPP option as part of 3GPP TS 24.572.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43590,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2301857","lsto":"SA2","Cc":"SA3, RAN2, CT4","lsoriginalls":"C1-236562","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234359.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234360","title":"Reply LS on DTLS for SCTP next steps and request for input","source":"RAN3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"RAN3 thanks IETF TSVWG for the update on this issue. RAN3 would like to provide answers to the following questions.\n\nQ1. Confirm whether implementation possibilities in both userland and kernel implementations of SCTP are required for the solution, and whether any additional concerns with implementing either of the solutions are perceived.\n\nA1. SCTP implementation details are typically not discussed in RAN3.\n\nQ2. Confirm that the interpretation of the requirements is correct, i.e., which SCTP message size would be required to be supported. \u201cIn other words, are the theoretical maximum message size mentioned above relevant to be supported, or would it be sufficient that a smaller message size is supported?\u201d[IETF TSVWG text]\n\nA2. RAN3 would like to confirm our previous LS: we do not expect to limit the maximum message size of application protocols. For this reason, any solution with a limit on message size will not meet RAN3 requirements.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43600,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R3-233836","lsto":"IETF TSVWG","Cc":"SA3, SA2, CT1, CT4","lsoriginalls":"R3-234497","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234360.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234361","title":"Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502","source":"RAN3","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"RAN3 would like to further inform SA2 that RAN3 agreed to rename the NGAP \u201cDL data notification\u201d message to \u201cRAN paging request\u201d message. RAN3 also agreed to include the \u2018DL signalling indication\u2019 in the \u201cRAN paging request\u201d message to differentiate DL signalling and DL data. \n\nIn addition, RAN3 would like to inquire whether there is need to include the \u2018eRedCap indication\u2019 in the NGAP INITIAL UE MESSAGE message, \tto enable possible charging and policy control and differentiation of eRedCap devices, as was done in the past releases for Rel-17 RedCap UEs.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43610,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_redcap_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2307730","lsto":"SA2","Cc":"RAN2, CT4","lsoriginalls":"R3-234725","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234361.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234362","title":"Reply LS on Clarification on Removal of the Indicator of UUAA result from AMF","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 Answer: SA3 understanding is correct that when SMF is configured to trigger UUAA-SM based on a DNN configured with aerial services subscription information, UUAA-SM will be executed in the system even if the UUAA-MM has been already performed by AMF during registration since SA2 agreed to remove the indication of successful UUAA-MM which was sent from AMF to SMF . But it does not have any co-relation with the highlighted text by SA3 as part of Clause 5.2.2.1 of TS 23.256. The AMF shall store  the UUAA-MM result irrespective of whether it\u2019s \u201cPending\u201d or \u201cSuccess \u201c because based on this stored result AMF takes certain actions. In case of stored result is \u201cPending\u201d, if AMF receives any PDU session request for Aerial service then AMF will reject such request. Similarly, at each MRU, to prevent repeating UUAA-MM procedure the storing of \u201cSuccess\u201d result in AMF helps. Hence SA2 does not see the need for any modification to this clause based on the above explanation.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43620,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"UAS_Ph2"},{"winame":" ID_UAS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2308335","lsto":"SA3","Cc":"CT4","lsoriginalls":"S2-2309697","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234362.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234363","title":"LS on moving PMIC and UMIC into Annex","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"1. Overall Description:\nSA2 has agreed the attached CRs to move the tables describing PMIC and UMIC (i.e. Table 5.28.3.1-1 and Table 5.28.3.1-2 in TS 23.501) into Annex K. Please take this into account. \n\n2. Actions:\nTo CT1, CT3 and CT4 group.\nACTION: \tSA2 asks CT1, CT3 and CT4 group to update their specifications if needed taking the above 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":43630,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"IIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, CT3, CT4","Cc":"","lsoriginalls":"S2-2309702","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234363.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234364","title":"Reply LS on MBS service area update clarification","source":"SA2","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":43640,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2308285","lsto":"3GPP TSG SA WG6","Cc":"","lsoriginalls":"S2-2309746","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234364.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234365","title":"Reply LS on INACTIVE eDRX above 10.24sec and SDT","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 thanks RAN3 for the LS (R3-233347) on \u201cINACTIVE eDRX above 10.24sec and SDT\u201d with the following bullets.\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.\n\n\nFor the information in bullet 1 of in the overall description related to NG-RAN provides of PTW parameter for RRC_INACTIVE eDRX to CN. SA2 has agreed the attached CRs (TS 23.501 CR 4770 and TS 23.502 CR 4322).\n\nFor the two questions in bullet 2 and 3, SA2 discussed the issues and provided the following responses:\n\nAnswer 2: When NGAP DL DATA NOTIFICATION is triggered by downlink data on user plane, the signalled 5QI is the same as the one stored in RAN UE context. For the case of NGAP DL DATA NOTIFICATION is triggered by MT signalling, SA2 will continue the discussion and provide further response. \n\nAnswer 3: SA2 discussed the issue and considers it\u2019s technically feasible for UPF\/SMF to provide the DL data size of the first downlink packet to NG-RAN via AMF. SA2 also discussed if more accurate data size is needed besides the first packet, but no consensus could be reached. \n\nSA2 asks RAN3 to provide view regarding if indicating the first downlink packet data size by 5GC is sufficient for NG-RAN to decide the use of MT-SDT.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43650,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_REDCAP_Ph2"},{"winame":" NR_redcap_enh-Core"},{"winame":" NR_MT_SDT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2308320","lsto":"RAN3, CT4","Cc":"RAN2","lsoriginalls":"S2-2309757","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234365.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234366","title":"Reply LS on clarification on IMS media services and media capabilities","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 thanks CT4 for their liaison S2-2308308 (C4-232628) in which CT4 asks SA2 two questions; in response to the first question:\nQ1: Are there any difference between the media service list and the media capability list? CT4 considered that they are same and defined as one media capability list. Then different NFs, (e.g., MRF, MRFP, DCMF) shall contains the corresponding various IMS media capabilities\/services. Is the understanding correct?\nA: SA2 confirms CT4\u2019s understanding that there is no difference between the media service list and the media capability list.\nIn response to the second question:\nQ2: Given the potential drawbacks of defining the media service\/capability as a free string, CT4 would like to define each media service\/capability to be an enumeration type which is also a string but with exact meaning. CT4 would like to ask SA2 whether it is acceptable?\nA: SA2 has discussed this and concluded that there is no architectural reason that enumeration type is not acceptable (it is SA2\u2019s understanding that enumeration type which is also a string allows operators to define proprietary extensions). SA2 chose not to define any values for media service\/capability as it was agreed these would be implementation specific.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43660,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2308308","lsto":"CT4","Cc":"","lsoriginalls":"S2-2309941","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234366.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234367","title":"LS on Update of subscribed NSSAI when UE is not registered in network","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 would like to bring up an issue to CT4 and ask for guidance.\n\nSA2 has agreed to update TS 23.502 to clarify a case in which a UE with unacknowledged slice subscription changes registers to the network. This situation results in the new Configured NSSAI being sent during UE registration via a Registration Accept message that contains a Network Slice Subscription Change Indication (NSSCI). As outlined in the attached: TS 23502 CR 4249, SA2 agreed that in such a case \"the AMF indicates the NSSF that the AMF needs a Configured NSSAI\". \n\nHowever, to have the NSSF return the configured NSSAI, SA2 could not agree on whether:\n\u2022\ta new indication (e.g. a new parameter in the Nnssf_NSSelection_Get service operation)  is required to have the NSSF return Configured NSSAI,\n\u2022\tor an existing indication can be reused (e.g. the Default S-NSSAI indication in the Nnssf_NSSelection_Get service operation) \n\nSA2 kindly asks CT4 to: \n\u2022\tProvide guidance to SA2 on how to best provide the NSSF an indication resulting in the Configured NSSAI being returned to the AMF\n\u2022\tDecide whether the change can be applied to releases prior to Release 17\n\u2022\tIf needed, update TS 29.531 accordingly.\n\nAccording to CT4's response, SA2 will perform, if needed, an alignment reflecting CT4's decision.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43670,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"CT1","lsoriginalls":"S2-2309953","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234367.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234368","title":"Reply LS Network Triggered Service Request for a UE in Suspend State","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA2 thanks CT4 for information and agreement related to alternatives on the usage of service operations in SMF.\n\nFor Rel-17, based on the agreement in the LS and the agreed C4-232396 from CT4#116 meeting, SA2 considers no extra improvement in SA2 spec is needed.\n\nFor Rel-18, based on the agreement in the LS, SA2 agreed the attached CR to improve the SA2 spec.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43680,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"},{"winame":" TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2308303","lsto":"CT4","Cc":"RAN3","lsoriginalls":"S2-2309984","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234368.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234369","title":"LS on SNPN Identifier based N3IWF FQDN","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"1. Overall Description:\nThere is one editor\u2019s note in 23.501, copied below:\nEditor's note:\tFor example, the Operator Identifier based emergency SNPN N3IWF FQDN may take the form:\n\t\"sos.n3iwf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org\".\n\tOnce this FQDN has been decided and added to TS 23.003 [19], this Editor's note will be removed.\nSA2 understood that the above FQDN in the editor\u2019s note corresponds to \u201cSNPN Identifier based N3IWF FQDN\u201d mentioned in 23.003 clause 28.3.2.2.6.4 (see below), while the definition of \u201cSNPN Identifier based N3IWF FQDN\u201d is missing in the referred clause 28.3.2.2.6.1.\nThe replacement field shall take the form of an SNPN Identifier based N3IWF FQDN as specified in clause 28.3.2.2.6.1 with the addition of the label \"sos\" before the labels \"n3iwf.5gc\".\n\nSA2 are trying to resolve the Editor\u2019s notes in 23.501 related to SNPN N3IWF selection and the attached (postponed) CR is a draft proposal how to align the 23.501 with 23.003. SA2 will align TS 23.501 based on the CT4 feedback.\n\n2. Actions:\nTo CT4:\nACTION:\t\nSA2 would like CT4 to confirm whether \u201cSNPN Identifier based N3IWF FQDN\u201d mentioned in 23.003 is for the \u201cOperator Identifier based emergency SNPN N3IWF FQDN\u201d described in 23.501. \nIf yes, SA2 would like CT4 to specify the format for \u201cSNPN Identifier based N3IWF FQDN\u201d.\nIf no, SA2 would like CT4 to specify the \u201cOperator Identifier based emergency SNPN N3IWF FQDN\u201d as described in 23.501.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43690,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"-","lsoriginalls":"S2-2309993","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234369.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234370","title":"Reply LS on Clarification on NSAC procedure for counting of UEs with at least one PDU session or PDN connection","source":"SA2","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":43700,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNSAC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C4-232530","lsto":"CT4","Cc":"-","lsoriginalls":"S2-2310036","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234370.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234371","title":"LS on Metaverse Standards Forum (MSF)","source":"SA4","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA4 recommends SA, RAN and CT to identify and inform the relevant 3GPP WGs and ask them to designate at least one representative for the MSF Register. The representative would then be responsible to collect the respective WG related Metaverse specifications and projects and submit the information to the Metaverse Standards Register.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43710,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA1, SA, 3GPP RAN, 3GPP CT","Cc":"-","lsoriginalls":"S4-231082","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234371.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234372","title":"Reply LS on Security Context Transfer between MBSF and MBSTF","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":43720,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S4-231138","lsto":"CT4, SA3","Cc":"SA2, CT3","lsoriginalls":"S4-231485","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234372.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234374","title":"LS on documenting code in Forge-GitLab","source":"SA5","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":43740,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"CT CT1 CT3 CT4 SA4","lsoriginalls":"S5-235769","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234374.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234375","title":"Reply LS on Approval of eQoE CRs for NR","source":"SA5","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":43760,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eQoE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R2-2304401","lsto":"RAN2","Cc":"RAN3, SA4, CT1, CT4","lsoriginalls":"S5-235772","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234375.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234376","title":"LS on Enhancement on the attribute for 5GLAN management","source":"SA5","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"To support the 5G LAN-type services, as defined in TS 23.501 [2], the 5G VN group configuration is either provided by OAM or provided by an AF to the NEF. SA5 is specifying the enhanced NRM to support the management of 5G LAN-type services, including configuration management of AMF\/SMF\/NRF\/UDM. The following question was raised in SA5 and hope CT4 could provide feedback:\nFirstly, please clarify which identifiers is used to support 5G LAN-type services, as stated in TS 29.510, the attribute of internalGroupId has already defined and supported by the trusted AF in Table 6.1.6.2.96-1: Definition of type TrustAfInfo. However, 5g-vn-groups is used in TS 29.503.\nSecondly, SA5 would kindly ask CT4 to make the necessary updates to their specifications to enable 5G LAN-type services (e.g., enhancement for the AmfInfo\/SmfInfo\/NrfInfo).","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43770,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GLAN_Mgt"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP CT4","Cc":"3GPP SA2","lsoriginalls":"S5-235780","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234376.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234377","title":"Discussion paper on Using Forge-Git as the primary storage for Code","source":"SA5","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":43790,"status":"withdrawn","reservation_date":"2023-09-28 02:48:09","uploaded":"2023-09-28 02:48:09","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S5-235145","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234377.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234378","title":"LS to CT4 on documenting code in Forge-GitLab","source":"SA5","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA5 intends to facilitate the specification of the optional new methodology of storing code normatively in Forge, based on attachment 1.\n\nFor some of its documents SA5 intends to start storing code normatively in Forge. SA5 sees major advantages in storing code normatively in Forge. This should not impact other groups.\n\nThe intent is to get the attached draftCR for 29.501 converted to a real CR and get it approved.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":43750,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"CT1, CT3, CT, SA4 and SA","lsoriginalls":"S5-235855","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234378.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234379","title":"LS on 3GPP related Metaverse specifications and activities","source":"TSG SA","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":43800,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Metaverse Standards Forum (MSF)","Cc":"3GPP SA1, 3GPP SA4, 3GPP RAN, 3GPP CT","lsoriginalls":"SP-230741","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234379.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234380","title":"Reply LS on Roaming Hubs","source":"TSG SA","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":44140,"status":"noted","reservation_date":"2023-09-29 10:20:02","uploaded":"2023-09-29 10:59:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"Roaming5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-230807","lsto":"GSMA NG 5GMRR","Cc":"","lsoriginalls":"SP-231203","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234380.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234414","title":"LS on Enhancement on the attribute for 5GLAN management","source":"China Mobile","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":0,"status":"approved","reservation_date":"2023-09-28 02:48:09","uploaded":"2023-09-28 02:48:09","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GLAN_Mgt"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA5","Cc":"SA2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234414.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-234495","title":"LS on INACTIVE eDRX above 10.24sec and SDT (C4-233691\/R3-235005)","source":"RAN3","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":0,"status":"postponed","reservation_date":"2023-11-10 03:03:29","uploaded":"2023-10-12 06:01:06","revisionof":"","revisedto":"C4-235011","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, CT4","Cc":"RAN2","lsoriginalls":"R3-235765","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_118_Xiamen\/Docs\/C4-234495.zip","group":"C4","meeting":"C4-118","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]