[{"name":"R5-225916","title":"Reply LS on video call upgrade when preconditions are not used","source":"TSG WG CT1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"CT1 thanks RAN5 for the LS on video call upgrade when preconditions are not used. CT1 would like to provide the following answer to the question asked by RAN5:\n\u201cRAN5 is unclear on how the UE should behave when it receives re-INVITE, containing a call upgrade request from voice to video call and preconditions not being used. Two different interpretations are being discussed:\nA.\tThe UE optionally sends 100 Trying provisional response followed by 183 session progress with SDP answer.\n\nB.\tThe UE optionally sends 100 Trying provisional response followed by 200 OK containing SDP answer when user accepts the call modification (upgrade) request.\u201d\nCT1 answer: It is not specified in TS 24.229 that 183 (Session Progress) response is mandatory for the above mid-call without precondition scenario. Thus, both interpretations A and B are allowed by TS 24.229.\n2. Actions: To RAN5 group: ACTION: CT1 asks RAN5 to take the above feedback into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":746,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59160,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-06 15:01:20","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-223332","lsto":"TSG RAN WG5","Cc":"","lsoriginalls":"C1-225089","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225916.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-225917","title":"Reply LS on null security algorithm","source":"TSG WG RAN2","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN2 would like to thank RAN5 for their LS on V2X PC5 link for unicast communication with null security algorithms.Regarding the questions from RAN5, RAN2 would like to provide the following answers.\nACTION: RAN5 asks RAN2 to confirm whether or not PC5-RRC signalling could be sent based on\n\"null ciphering\/integrity algorithm\".\nRAN2 Answer:\nRAN2 has discussed this issue and reviewed the corresponding specification, and PC5-RRC signalling can be sent based on \u201cnull ciphering\/integrity algorithm\u201d. And to remove potential ambiguity, following Note is added into RRC specification:\nNOTE 5: The selection of NULL algorithms means that the PC5 messages are considered protected for the purposes of being allowed to be sent or received.\n2. Actions:\nTo 3GPP RAN WG5 group.\nACTION: \tRAN2 kindly asks RAN5 to take the above information into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":746,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59170,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-06 15:01:20","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_V2X_NRSL-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-222035","lsto":"TSG RAN WG5","Cc":"TSG WG CT1, TSG WG SA3","lsoriginalls":"R2-2208832","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225917.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-225922","title":"LS to RAN5 on Confirmation of resource reservation","source":"GSMA NG UPG","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG UPG has agreed to use SIP UPDATE request for precondition status update only. See CR1217 to  GSMA PRD IR.92 and CR1032 to GSMA PRD NG.114. \n3GPP TS 24.229 h70 section 5.1.3.1 states the following (It was introduced to 3GPP TS 24.229 from Rel-6 by CR1072):\nIf the precondition mechanism is used, the UE shall, upon successful reservation of local resources, confirm the successful resource reservation (see subclause 6.1.2) within the next SIP request.\nNOTE 3:\tThe next SIP request will be either a PRACK request or an UPDATE request.\nIt means both PRACK request and UPDATE request can be used for precondition status update. However, if GSMA NG UPG introduces PRACK request for precondition status update so late, there may be backward compatibility issues. As described below, if UE-A sends the second SDP Offer in the PRACK request, then (an old) UE-B may not support it.\nINVITE (SDP Offer 1) --->\n?<--- 183 Progress (SDP Answer 1)\nPRACK (SDP Offer 2) --->\n?<--- 200 OK (PRACK) (SDP Answer 2)\n2. Actions: To 3GPP RAN5 group: GSMA NG UPG kindly requests 3GPP RAN5 to take the information above into account.","secretary_remarks":"","agenda_item_sort_order":746,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59220,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-24 14:31:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG WG RAN5, TSG WG CT1","Cc":"","lsoriginalls":"UPG#04 Doc 111r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225922.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]