[{"name":"S2-2201946","title":"LS from RAN WG2: LS on Tx Profile","source":"RAN WG2","contact":"Weiqiang Du","contact-id":89595,"tdoctype":"LS in","for":"Action","abstract":"In RAN WG2#117-e meeting, RAN WG2 discussed the information to be indicated in NR Tx Profile and made the following agreement: 1. The Tx profile should include at least the information of DRX support or not. 2. Check with SA WG2 whether a same L2 ID may associate with multiple Tx profiles, and thus may associate with both DRX-based Tx profile and non-DRX based Tx profile in Rel-16. Then also check with SA WG2 if feasible for Rel-17 SL DRX operation, L2 id is only associated with either DRX-based TX profile(s) or non-DRX based TX profile(s). DCR issue raised by ZTE can be discussed as part of LS preparation. If the question is valid to companies, we're also adding that question otherwise we're not adding it. Working assumption: no additional RAN WG2 work if SA WG2 confirms it's feasible for Rel-17 SL DRX operation, L2 id is only associated with either DRX-based TX profile(s) or non-DRX based TX profile(s). 3. For GC, we will check with SA WG2 whether the mapping from L2 id to TX profile is feasible in the gNB (like what we did in LTE). Working assumption: no additional RAN WG2 work if SA WG2 confirms it's feasible. 4. The default SL DRX configuration for BC\/GC [(including at least DRX cycle, start offset and on-duration timer)] can be used for both BC-based and UC-based DCR message. . In addition, RAN WG2 would like to ask SA WG2 for some clarifications on following questions: ? Question 1: May an L2 ID associate with multiple Tx profiles, and thus associate with both DRX-based Tx profile and non-DRX based Tx profile with the current SA WG2 spec? Based on the working assumption above, RAN WG2 assumes no additional RAN WG2 work if SA WG2 confirms it is feasible that an L2 id is only associated with either DRX-based TX profile(s) or non-DRX based TX profile(s). ? Question 2: For Groupcast, whether the mapping from L2 id to TX profile is feasible in the gNB (like what we did in LTE for broadcast, i.e. the mapping from Destination L2 ID to Tx Profile is configured in the gNB)? Based on the working assumption above, RAN WG2 assumes no additional RAN WG2 work if SA WG2 confirms it is feasible. Action: To SA WG2: RAN WG2 respectfully requests SA WG2 to take the above agreements into account in the further work and to provide feedback for the above questions on NR Tx Profile.","secretary_remarks":"Responses drafted in S2-2202283, S2-2202287, S2-2202681. Final response in S2-2203595","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13620,"status":"replied to","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 10:15:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2203693","lsreply":"S2-2203595, S2-2203595","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201946.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202283","title":"[DRAFT] Reply LS on Tx Profile","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Tx Profile","secretary_remarks":"Response to S2-2201946. r08 agreed. Revised to S2-2203595, merging S2-2202681 and S2-2202287.","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13630,"status":"revised","reservation_date":"2022-03-29 04:05:30","uploaded":"2022-03-29 16:29:45","revisionof":"","revisedto":"S2-2203595","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2-Core"},{"winame":" 5G_ProSe"},{"winame":" eV2XARC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202283.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202284","title":"Clarifications on PC5 DRX operations","source":"LG Electronics, CATT","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: \u00a73.1: - Related to RAN WG2 agreement#1, add '(e.g. PC5 DRX support or not)' to NR Tx Profile. \u00a75.9: - Related to RAN WG2 agreement#3, - add description about that for BC\/GC, the NG-RAN may deduce the NR Tx Profile from the DST Layer-2 ID. - add description about that for BC, the mapping from DST Layer-2 ID to NR Tx Profile is configured in the NG-RAN (as specified in TS\u00a023.285 related to Tx Profile for broadcast over LTE PC5) - Related to RAN WG2 agreement#4, add the related description. \u00a75.9, 6.3.1 and 6.3.2: - Clarify that the V2X layer does not provide NR Tx Profile to the AS layer when there is no NR Tx Profile mapped for the V2X service.","secretary_remarks":"r05 agreed. Revised to S2-2203247, merging S2-2202290","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13680,"status":"revised","reservation_date":"2022-03-29 04:06:49","uploaded":"2022-03-29 16:29:45","revisionof":"","revisedto":"S2-2203247","release":"Rel-17","crspec":"23.287","crspecversion":"17.2.0","workitem":[{"winame":"eV2XARC_Ph2"}],"crnumber":177.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202284.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202285","title":"Clarifications on PC5 DRX operations","source":"LG Electronics, CATT","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: \u00a73.1: - Refer TS\u00a023.287 for NR Tx Profile to avoid redundant definition. \u00a75.13.3: - Related to RAN WG2 agreement#3, - add description about that for BC\/GC, the NG-RAN may deduce the NR Tx Profile from the DST Layer-2 ID. - add description about that for BC, the mapping from DST Layer-2 ID to NR Tx Profile is configured in the NG-RAN (as specified in TS\u00a023.285 related to Tx Profile for V2X communication over LTE PC5) - Related to RAN WG2 agreement#4, add the related description. \u00a75.13.3, 6.4.1 and 6.4.2: - Clarify that the ProSe layer does not provide NR Tx Profile to the AS layer when there is no NR Tx Profile mapped for the ProSe service.","secretary_remarks":"r04 agreed. Revised to S2-2203248, merging S2-2202289","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13700,"status":"revised","reservation_date":"2022-03-29 04:08:26","uploaded":"2022-03-29 16:29:45","revisionof":"","revisedto":"S2-2203248","release":"Rel-17","crspec":"23.304","crspecversion":"17.2.1","workitem":[{"winame":"5G_ProSe"}],"crnumber":91.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202285.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202287","title":"[DRAFT] Reply LS on Tx Profile","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Tx Profile (R2-2203693)","secretary_remarks":"Response to S2-2201946. Merged into S2-2203595","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13660,"status":"merged","reservation_date":"2022-03-29 04:51:11","uploaded":"2022-03-29 12:37:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh-Core"},{"winame":" 5G_ProSe"},{"winame":" eV2XARC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"R2-2203693","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202287.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202288","title":"Tx profile.","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"discussion","for":"Discussion","abstract":"This DP analyses the statement of TS 23.304 and TS 23.287 regarding Tx profiles. This DP will also analyse the L2 ID for BC\/GC to see whether it is feasible to configure the mapping between L2 ID and Tx profile.","secretary_remarks":"Noted","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13710,"status":"noted","reservation_date":"2022-03-29 04:53:34","uploaded":"2022-03-29 12:37:18","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"},{"winame":" eV2XARC_Ph2"},{"winame":" NR_SL_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202288.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202289","title":"DRX operations","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that L2 IDs associated with DRX and non-DRX are not overlapped. It is clarified that for broadcast and groupcast communication, the NG-RAN may deduce the NR Tx Profile from the destination Layer-2 ID if the network scheduled operation mode is used. It is clarified that the DCR message is transmitted and received using default DRX.","secretary_remarks":"Merged into S2-2203248","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13730,"status":"merged","reservation_date":"2022-03-29 04:53:34","uploaded":"2022-03-29 12:37:18","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.2.1","workitem":[{"winame":"5G_ProSe"},{"winame":" NR_SL_enh-Core"}],"crnumber":92.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202289.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202290","title":"DRX operations","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that L2 IDs associated with DRX and non-DRX are not overlapped. It is clarified that for broadcast and groupcast communication, the NG-RAN may deduce the NR Tx Profile from the destination Layer-2 ID if the network scheduled operation mode is used. It is clarified that the DCR message is transmitted and received using default DRX.","secretary_remarks":"Merged into S2-2203247","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13740,"status":"merged","reservation_date":"2022-03-29 04:53:35","uploaded":"2022-03-29 12:37:18","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.287","crspecversion":"17.2.0","workitem":[{"winame":"eV2XARC_Ph2"},{"winame":" NR_SL_enh-Core"}],"crnumber":178.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202290.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202680","title":"SL DRX update considering new QoS parameters","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When new V2X services comes from the application layer and the V2X layer derives new PC5 QoS parameters for a destination Layer-2 ID, the AS layer may obtain a new PC5 DRX considering the new PC5 QoS parameters.","secretary_remarks":"r02 agreed. Revised to S2-2203249","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13750,"status":"revised","reservation_date":"2022-03-29 12:28:45","uploaded":"2022-03-29 13:01:41","revisionof":"","revisedto":"S2-2203249","release":"Rel-17","crspec":"23.287","crspecversion":"17.2.0","workitem":[{"winame":"eV2XARC_Ph2"}],"crnumber":179.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202680.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202681","title":"[DRAFT] Response LS on Tx Profile","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response to LS from RAN WG2 on NR Tx Profile.","secretary_remarks":"Response to S2-2201946. Merged into S2-2203595","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13650,"status":"merged","reservation_date":"2022-03-29 12:28:47","uploaded":"2022-03-29 13:01:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eV2XARC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202681.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202704","title":"Clarification on parameter for NR Tx Profile selection","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: \u00a74.4.1.1.2: - Add description about the policy\/parameter for NR Tx Profile selection under '4) Policy\/parameters for NR PC5'.","secretary_remarks":"Approved","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13770,"status":"agreed","reservation_date":"2022-03-29 13:38:30","uploaded":"2022-03-29 15:12:07","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.285","crspecversion":"17.0.0","workitem":[{"winame":"eV2XARC_Ph2"}],"crnumber":64.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220402","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202704.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203247","title":"Clarifications on PC5 DRX operations","source":"LG Electronics, CATT, Ericsson, Samsung, OPPO","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: \u00a73.1: - Related to RAN WG2 agreement#1, add '(e.g. PC5 DRX support or not)' to NR Tx Profile. \u00a75.9: - Related to RAN WG2 agreement#3, - add description about that for BC, the mapping from DST Layer-2 ID to NR Tx Profile is configured in","secretary_remarks":"Revision of S2-2202284r05, merging S2-2202290. Approved","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13690,"status":"agreed","reservation_date":"2022-04-13 09:53:13","uploaded":"2022-04-14 09:01:22","revisionof":"S2-2202284","revisedto":"","release":"Rel-17","crspec":"23.287","crspecversion":"17.2.0","workitem":[{"winame":"eV2XARC_Ph2"}],"crnumber":177.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220402","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203247.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203248","title":"Clarifications on PC5 DRX operations","source":"LG Electronics, CATT, Ericsson, Samsung, OPPO","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: \u00a73.1: - Refer TS\u00a023.287 for NR Tx Profile to avoid redundant definition. \u00a75.13.3: - Related to RAN WG2 agreement#3, - add description about that for BC, the mapping from DST Layer-2 ID to NR Tx Profile is configured in the NG-RAN (as sp","secretary_remarks":"Revision of S2-2202285r04, merging S2-2202289. Approved","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13710,"status":"agreed","reservation_date":"2022-04-13 09:53:15","uploaded":"2022-04-14 09:01:22","revisionof":"S2-2202285","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.2.1","workitem":[{"winame":"5G_ProSe"}],"crnumber":91.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220393","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203248.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203249","title":"SL DRX update considering new QoS parameters","source":"Huawei, HiSilicon, Tencent","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When new V2X services comes from the application layer and the V2X layer derives new PC5 QoS parameters for a destination Layer-2 ID, the AS layer may obtain a new PC5 DRX considering the new PC5 QoS parameters.","secretary_remarks":"Revision of S2-2202680r02. Approved","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13760,"status":"agreed","reservation_date":"2022-04-13 09:53:16","uploaded":"2022-04-14 09:01:22","revisionof":"S2-2202680","revisedto":"","release":"Rel-17","crspec":"23.287","crspecversion":"17.2.0","workitem":[{"winame":"eV2XARC_Ph2"}],"crnumber":179.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220402","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203249.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203595","title":"[DRAFT] Reply LS on Tx Profile","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Tx Profile","secretary_remarks":"Revision of S2-2202283r08, merging S2-2202681 and S2-2202287. Approved","agenda_item_sort_order":20,"ainumber":"8.12","ainame":"Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2)","tdoc_agenda_sort_order":13640,"status":"approved","reservation_date":"2022-04-13 09:55:41","uploaded":"2022-04-13 15:41:16","revisionof":"S2-2202283","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"},{"winame":" eV2XARC_Ph2"},{"winame":" NR_SL_enh2-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2201946","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"R2-2205101, R2-2205335, R2-2206079","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203595.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]