[{"name":"S2-2208106","title":"LS from RAN WG2: LS on Cast Type for Discovery message","source":"RAN WG2","contact":"Qianxi Lu","contact-id":71851,"tdoctype":"LS in","for":"Action","abstract":"During RAN WG2#118, RAN WG2 discussed how to deliver the discovery messages. AS-layer specification requires Tx-UE to carry cast-type-indicator in SCI, based on which the delivered packet is to be filtered by MAC layer by Rx-UE. But RAN WG2 noticed that there is no cast type indicator provided to lower layer for discovery message transmission based on the current TS 23.304, so AS-layer cannot know the cast type (unicast\/groupcast\/broadcast) of the destination L2 ID, and thus the AS layer cannot set the cast type of the discovery message based on the destination L2 ID. Thus, RAN WG2 has the following question: Q1: Can upper layer provide unicast \/ groupcast \/ broadcast cast-type-indicator to AS layer for the delivery of each discovery message? In case SA WG2 answers No to Q1, RAN WG2 discussed another option, i.e., AS-layer delivers all discovery messages using broadcast as the cast cast-type type-indicator in SCI, regardless of whether unicast, groupcast or broadcast L2 ID is used as the destination L2 ID. Considering this is different from sidelink communication in legacy, RAN WG2 would like to check with SA WG2. Q2: If No to Q1, whether SA WG2 is fine if all discovery message sent to unicast \/ groupcast \/ broadcast destination L2 ID always uses broadcast-type cast-type-indicator in SCI by Tx-UE, and are thus filtered in MAC layer at Rx-UE based on the destination L2 ID of the discovery message and broadcast-type cast-type indicator?. Action: RAN WG2 respectfully ask SA WG2 to provide answer for Q1 and Q2 above.","secretary_remarks":"Revision of Postponed S2-2205424 from S2#152-e. Responses drafted in S2-2208515, S2-2209064. Final response in S2-2209277","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11760,"status":"replied to","reservation_date":"2022-09-21 05:20:40","uploaded":"2022-09-21 08:06:27","revisionof":"S2-2205424","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2206391","lsreply":"S2-2209277, S2-2209277","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208106.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208122","title":"LS from CT WG1: LS on 5G DDNMF discovery","source":"CT WG1","contact":"Xingyue Zhou","contact-id":42680,"tdoctype":"LS in","for":"Action","abstract":"In their work on NR satellite access and the topic of multiple broadcast TAIs, CT WG1 has noted the stage 2 requirements for service area restrictions in TS 23.501, clause 5.4.11.8: The AMF receives the broadcast TAI (if a single TAI is broadcast) or all broadcast TAIs (if multiple TAIs are broadcast) from the NG-RAN as described clause 5.4.11.7. The AMF provides the UE with Service Area Restrictions which consist of either Allowed Areas or Non-Allowed Areas, as described in clause 5.3.4.1.2. The UE and AMF consider the UE to be in a Non-Allowed Area if none of the broadcast TAIs is Allowed. The UE and AMF consider the UE to be in an Allowed Area if at least one broadcast TAI is allowed. The corresponding stage 3 requirements to select a current TAI from multiple broadcast TAIs are specified in TS 24.501, clause 4.23.5, where the UE selects the TAI from the TACs supported by the selected PLMN. Note, however, that for the case when the satellite cell is a shared network cell, then there is an additional requirement on PLMN selection applicable which is specified in TS 23.122, clause 4.4.3: when a selected cell is a suitable cell for multiple PLMN identities, then the UE is mandated to select the registered PLMN if is available among these PLMN identities. Since logically PLMN selection is taking place before determination of the current TAI, the requirement from TS 23.122 takes precedence. As a result, it is possible that when all of the following is fulfilled: - the network is allocating TAI lists including TAIs from different, equivalent PLMNs, - the network is broadcasting multiple TAIs in its satellite NG-RAN cells, o whereby these TAIs belong to different, equivalent PLMNs, and o TAIs of one PLMN belong to the allowed area whereas TAIs of the equivalent PLMN belong to the non-allowed area, then - there can be cases where the UE selects a TAI that is part of the non-allowed area (because it belongs to the registered PLMN) although there would be an allowed TAI of an equivalent PLMN available. Note that this can occur both when the UE is actually located in an allowed TAI and when it is located in a non-allowed TAI. One example for such a case is as follows: The UE is assigned a registration area that contains at least one equivalent PLMN in addition to the registered PLMN; The UE is assigned an allowed area; The TACs of the registered PLMN which are part of the broadcast TAI list are not in the allowed area; The UE receives broadcast information in a satellite cell where at least one TAC of an equivalent PLMN part of the broadcast TAI list is included in the allowed area. CT WG1 has not made a systematic study of possible other corner cases, including the scenario above when the UE could select a TAI that is part of the allowed area, and has decided to not make any changes to specification under CT WG1 remit because of the above-described scenario, but would like to inform SA WG2 of these observations. Action: CT WG1 requests SA WG2 take the information provided into account.","secretary_remarks":"Response drafted in S2-2208600. Final response in S2-2209261","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11820,"status":"replied to","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-225229","lsreply":"S2-2209261, S2-2209261","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208122.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208128","title":"LS from CT WG1: LS on V2X policy or ProSe policy request during registration procedure","source":"CT WG1","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed the possible solutions to support that the UE requests for V2X policy and\/or 5G ProSe policy during registration procedure, but cannot reach the consensus. Due to the time frame for Rel-17, CT WG1 will not pursue this V2X\/ProSe policy request during registration procedure in Rel-17. Action: CT WG1 kindly asks SA WG2 to take into account the above information and provide feedback if any.","secretary_remarks":"Responses drafted in S2-2208355, S2-2208700. Postponed","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11860,"status":"postponed","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"S2-2210168","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG CT, TSG SA, CT WG3, CT WG4","lsoriginalls":"C1-225451","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208128.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208129","title":"LS from CT WG1: LS on setting RRC establishment cause value when relay UE has its own service","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 has discussed how to set RRC establishment cause value for the case when the access attempt is simultaneously triggered by both the own service of the 5G ProSe layer-2 UE-to-network relay UE in 5GMM-IDLE mode and the 5G ProSe layer-2 remote UE, and achieved the following consensus (see attachment): the RRC establishment cause is selected according to table 4.5.6.1 and table 4.5.6.2 of clause 4.5.6, 3GPP TS 24.501 in the above case, however, it is possible for the lower layer to decide an applicable RRC establishment cause according to the request from the 5G ProSe layer-2 remote UE.","secretary_remarks":"Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11930,"status":"noted","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2","lsoriginalls":"C1-225453","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208129.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208153","title":"LS from SA WG3: LS Reply on Reply LS on 5G ProSe security open items","source":"SA WG3","contact":"Samir Ferdi","contact-id":72165,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA for their LS on 5G ProSe security open items. SA WG3 has discussed it and would like to indicate the following reached agreements. SA decision: - SA asks SA WG3 and CT WGs to remove PDU Session Secondary Authentication from Rel-17 specifications. SA WG3 agreement: SA WG3 has agreed to the attached CR S3-222400 to remove the support for PDU Session Secondary Authentication from TS 33.503 Rel-17 specification. SA decision: - SA has agreed that SA WG2 and SA WG3 should work on PDU Session Secondary Authentication in Rel-18 as per normal 3GPP working procedures. SA WG3 agreement: SA WG3 has agreed to the attached draftCR S3-222262 and WID S3-222366 to work on PDU Session Secondary Authentication in Rel-18. Action: SA WG3 kindly asks SA, SA WG2 to take the above information into account.","secretary_remarks":"Response drafted in S2-2208359. Postponed","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11940,"status":"postponed","reservation_date":"2022-09-21 05:20:42","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"S2-2210176","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG CT, CT WG1, CT WG3, CT WG4","lsoriginalls":"S3-222434","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208153.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208355","title":"[DRAFT] Reply LS on V2X policy or ProSe policy request during registration procedure","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on V2X policy or ProSe policy request during registration procedure","secretary_remarks":"Response to S2-2208128. Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11870,"status":"noted","reservation_date":"2022-09-29 10:07:57","uploaded":"2022-09-30 10:34:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"},{"winame":" eV2XARC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"TSG CT, TSG SA, CT WG3, CT WG4, CT WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208355.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208356","title":"Removal of ProSe policy request during registration procedure","source":"Ericsson, LG Electronics, CATT, Huawei, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of support for the UE to provide ProSe Policy Provisioning Request indication in the Registration Request message. Add description that after registration, the UE may perform UE triggered 5G ProSe Policy Provisioning Request procedure.","secretary_remarks":"Postponed","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11890,"status":"postponed","reservation_date":"2022-09-29 11:46:07","uploaded":"2022-09-30 13:49:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.6.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":743.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208356.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208357","title":"Removal of ProSe policy request during registration procedure","source":"Ericsson, LG Electronics, CATT, Huawei, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of support for the UE to provide ProSe Policy Provisioning Request indication in the Registration Request message. Add text that the AMF reports the authorized 5G ProSe Capability to the selected PCF, which may determine the 5G ProSe Policy\/Parameter based on the authorized 5G ProSe Capability.","secretary_remarks":"Postponed","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11900,"status":"postponed","reservation_date":"2022-09-29 11:46:10","uploaded":"2022-09-30 13:49:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":115.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208357.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208358","title":"Discussion of 5G ProSe security open item for L3 Remote UE's secondary AA.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This paper discusses and proposes a way forward for secondary authentication & authorization for Layer-3 UE-to-Network relaying proposed by SA WG3.","secretary_remarks":"Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11960,"status":"noted","reservation_date":"2022-09-29 11:46:12","uploaded":"2022-09-30 13:49:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208358.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208359","title":"[DRAFT] Reply to 5G ProSe security open items","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper replies to SA WG3 that secondary authentication and authorization for L3 Remote UE is not needed","secretary_remarks":"Response to S2-2208153. Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11950,"status":"noted","reservation_date":"2022-09-29 11:46:12","uploaded":"2022-09-30 13:49:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG CT, CT WG1, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208359.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208482","title":"Removal of ProSe policy request during registration procedure","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 6.2.2 Remove the descriptions on ProSe policy request during registration procedure.","secretary_remarks":"Merged into (Covered by) S2-2208357","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11910,"status":"merged","reservation_date":"2022-09-30 01:35:02","uploaded":"2022-09-30 01:57:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":116.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208482.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208483","title":"Removal of V2X\/ProSe policy request during registration procedure","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 6.1.2.2.2 Remove the descriptions on V2X\/ProSe policy request during registration procedure.","secretary_remarks":"Merged into (Covered by) S2-2208356","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11920,"status":"merged","reservation_date":"2022-09-30 01:35:03","uploaded":"2022-09-30 01:57:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.6.0","workitem":[{"winame":"5G_ProSe"},{"winame":" eV2XARC_Ph2"}],"crnumber":747.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208483.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208513","title":"Cast type for direct discovery.","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"discussion","for":"Discussion","abstract":"This DP analyses the cast type for the direct discovery.","secretary_remarks":"Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11800,"status":"noted","reservation_date":"2022-09-30 03:47:15","uploaded":"2022-09-30 05:32:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"},{"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_153E_Electronic_2022-10\/Docs\/S2-2208513.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208514","title":"Cast Type for Discovery message","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The ProSe layer provides the discovery type to the lower layer when performing discovery.","secretary_remarks":"Revision of (Noted) S2-2205993 from S2#152E. Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11810,"status":"noted","reservation_date":"2022-09-30 03:47:15","uploaded":"2022-09-30 05:32:05","revisionof":"S2-2205993","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":108.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208514.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208515","title":"[DRAFT] Reply LS on Cast Type for Discovery message","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"This is a reply LS on Cast Type for Discovery message (S2-2208106\/R2-2206391)","secretary_remarks":"Revision of (Noted) S2-2205994 from S2#152E. Response to S2-2208106. Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11770,"status":"noted","reservation_date":"2022-09-30 03:47:16","uploaded":"2022-09-30 05:32:05","revisionof":"S2-2205994","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"},{"winame":" NR_SL_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208515.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208516","title":"Clarification on DCR message for DRX","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 'Default SL DRX configuration' also requires the NR Tx Profile. This is applied to transmitting and receiving DCR messages.","secretary_remarks":"Merged into S2-2209279","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11970,"status":"merged","reservation_date":"2022-09-30 03:47:16","uploaded":"2022-09-30 05:32:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":117.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208516.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208581","title":"Clarifications on PC5 DRX operations","source":"Vivo, LG Electronics","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: clarify that the initial signalling to establish unicast connection (DCR message) also needs to be applied to the default SL DRX configuration in the Policy\/Parameter provisioning for 5G ProSe Direct Communication remove the sentence that applies the potentical case of no TX profile configured to ProSe services. Capature the updated PC5 DRX operations in TS23.287 to ProSe service for groupcast and broadcast related to the case that multiple services use same DST L2 ID.","secretary_remarks":"r01 agreed. Revised to S2-2209279, merging S2-2208516","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11980,"status":"revised","reservation_date":"2022-09-30 07:50:34","uploaded":"2022-09-30 09:40:22","revisionof":"","revisedto":"S2-2209279","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":118.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208581.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208599","title":"Add 5G DDNMF Address in Parameter Provisioning for 5G ProSe Direct Discovery","source":"ZTE, Ericsson","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the FQDN or IP address of the 5G DDNMF in the Home PLMN in parameter provisioning for 5G ProSe Direct Discovery in clause 5.1.2.1. The description for 5G DDNMF discovery in clause 4.3.2.2 is updated accordingly.","secretary_remarks":"Approved","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11850,"status":"agreed","reservation_date":"2022-09-30 08:09:21","uploaded":"2022-09-30 09:12:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":119.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-221065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208599.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208600","title":"[DRAFT] Reply LS on 5G DDNMF Discovery","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on 5G DDNMF Discovery","secretary_remarks":"Response to S2-2208122. r00 agreed. Revised to S2-2209261.","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11830,"status":"revised","reservation_date":"2022-09-30 08:09:22","uploaded":"2022-09-30 09:12:27","revisionof":"","revisedto":"S2-2209261","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208600.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208700","title":"[DRAFT] Reply LS on V2X policy or ProSe policy request during registration procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 on V2X policy or ProSe policy request during registration procedure","secretary_remarks":"Response to S2-2208128. Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11880,"status":"noted","reservation_date":"2022-09-30 09:01:14","uploaded":"2022-09-30 15:29:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"},{"winame":" eV2XARC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"TSG CT, TSG SA, CT WG3, CT WG4, CT WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208700.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208908","title":"Correction on PC5 link release indication","source":"Huawei, HiSilicon, vivo","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To align the conclusion with RAN WG2, the indication from AS layer is changed from that PC5-RRC connection has been released to that indicates to trigger PC5 unicast link release , and to change the reference to TS 38.300 to TS 38.331.","secretary_remarks":"r01 agreed. Revised to S2-2209280.","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":12000,"status":"revised","reservation_date":"2022-09-30 12:04:53","uploaded":"2022-09-30 14:17:05","revisionof":"","revisedto":"S2-2209280","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":120.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208908.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209064","title":"[DRAFT] Reply LS on Cast Type for Discovery message","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Rely LS to RAN WG2 incoming LS S2-2205424.","secretary_remarks":"Response to S2-2208106. r03 agreed. Revised to S2-2209277.","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11780,"status":"revised","reservation_date":"2022-09-30 15:15:56","uploaded":"2022-09-30 19:17:25","revisionof":"S2-2206836","revisedto":"S2-2209277","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"}],"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_153E_Electronic_2022-10\/Docs\/S2-2209064.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209138","title":"Updates to Control Plane based security procedures for 5G ProSe UE-to-Network Relay","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description related to 5G ProSe UE to-Network Relay discovery to Control Plane based security procedures for 5G ProSe UE-to-Network Relay .","secretary_remarks":"CR Number missing! Noted","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":12020,"status":"noted","reservation_date":"2022-09-30 17:35:07","uploaded":"2022-09-30 17:51:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":121.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209138.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209261","title":"Reply LS on 5G DDNMF Discovery","source":"SA WG2","contact":"Hao Dong","contact-id":75723,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4. Attachments: TS23.304 CR#0119","secretary_remarks":"Revision of S2-2208600r00. Approved","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11840,"status":"approved","reservation_date":"2022-10-18 14:16:33","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208600","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208122","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209261.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209277","title":"Reply LS on Cast Type for Discovery message","source":"SA WG2","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1","secretary_remarks":"Revision of S2-2209064r03. Approved","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11790,"status":"approved","reservation_date":"2022-10-18 14:16:49","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2209064","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208106","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209277.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209279","title":"Clarifications on PC5 DRX operations","source":"Vivo, LG Electronics","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: clarify that the initial signalling to establish unicast connection (DCR message) also needs to be applied to the default SL DRX configuration in the Policy\/Parameter provisioning for 5G ProSe Direct Communication remove the sentence that applies the potentical case of no TX profile configured to ProSe services. Capature the updated PC5 DRX operations in TS23.287 to ProSe service for groupcast and broadcast related to the case that multiple services use same DST L2 ID.","secretary_remarks":"Revision of S2-2208581r01, merging S2-2208516. Approved","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":11990,"status":"agreed","reservation_date":"2022-10-18 14:16:50","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208581","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":118.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-221065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209279.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209280","title":"Correction on PC5 link release indication","source":"Huawei, HiSilicon, vivo","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To align the conclusion with RAN WG2, the indication from AS layer is changed from that PC5-RRC connection has been released to that indicates to trigger PC5 unicast link release , and to change the reference to TS 38.300 to TS 38.331.","secretary_remarks":"Revision of S2-2208908r01. Approved","agenda_item_sort_order":51,"ainumber":"8.8","ainame":"System enhancement for Proximity based Services in 5GS (5G_ProSe)","tdoc_agenda_sort_order":12010,"status":"agreed","reservation_date":"2022-10-18 14:16:51","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208908","revisedto":"","release":"Rel-17","crspec":"23.304","crspecversion":"17.4.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":120.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-221065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209280.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]