[{"name":"S2-2303921","title":"LS from SA WG3: LS on enforcement of AF specific identifier","source":"SA WG3","contact":"Ivy Guo","contact-id":94398,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to suggest SA WG2 to remove the following NOTE 2 in TS 23.501 clause 5.20: NOTE 2: How to enforce that the AF specific UE Identifier is different for different AFs is defined in TS 33.501 [29]. The justification is, SA WG3 did not specify the identifier. There are already some clarifications from TS 23.003 and TS 23.682 excerpted below, with those clarifications, the AF specific UE identifier can be ensured to be different for different AF(s), thus this NOTE 2 is not needed anymore. - For External Identifier , TS 23.003 defined that External Identifier shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. The username part format of the External Identifier shall contain a Local Identifier as specified in 3GPP TS 23.682 [98]. The realm part format of the External Identifier shall contain a Domain Identifier as specified in 3GPP TS 23.682 [98]. - For Local Indentifier , TS 23.682 defined that: Domain Identifier: identifies a domain that is under the control of a Mobile Network Operator (MNO) Local Identifier shall be unique within the applicable domain. It is managed by the Mobile Network Operator. SA WG3 kindly requests SA WG2 to consider the above information and make the corresponding change in TS 23.501. Action: SA WG3 kindly asks SA WG2 to take the above information into account and make the corresponding change in TS 23.501.","secretary_remarks":"Revision of postponed S2-2302201 from S2#155. Response drafted in S2-2304403. Postponed","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12420,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-03 14:38:30","revisionof":"S2-2302201","revisedto":"S2-2306268","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-230462","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303921.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303953","title":"LS from RAN WG2: LS on the use of PEI during an emergency PDU session","source":"RAN WG2","contact":"Martin Van Der Zee","contact-id":58600,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed the use of PEI during an emergency PDU session, and RAN WG2 observed that disabling UE-ID based PEI for CM-IDLE paging (Paging on NG) and CM-CONNECTED paging (RAN paging on Xn\/F1) during an emergency PDU session is not supported: The UE-ID based PEI capability (pei-SubgroupingSupportBandList-r17) is signalled in the PAGING message (UERadioPagingInformation) either from AMF or from the last serving gNB. Based on the UE capability and gNB s configuration (PEI-Config-r17) UE-ID based PEI is used even when the UE has an emergency PDU session. The latency introduced by UE-ID based PEI (similar as for CN-assigned PEI) depends on the configured time offset between PEI and the following Paging Occasion (PO) e.g. 50 ms. The RAN WG2 specifications do not have any special treatment for PEI during emergency call considering the latency difference is small compared to the paging cycle length. This means that when the UE has an emergency PDU session the CN-assigned PEI (PEIPS Assistance Information) is not used, but UE-ID based PEI is used. Action: RAN WG2 kindly asks SA WG2 and RAN WG3 to take this information into account.","secretary_remarks":"Responses drafted in S2-2304192, S2-2304278, S2-2304340, S2-2305229. Postponed","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12340,"status":"postponed","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306277","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"R2-2302302","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303953.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304190","title":"Paging Early Indication with emergency","source":"Ericsson, T-Mobile USA, AT&T, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Specify the handling of PEI function when UE has emergency PDU session","secretary_remarks":"Postponed","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12390,"status":"postponed","reservation_date":"2023-05-04 19:15:09","uploaded":"2023-04-07 15:57:34","revisionof":"","revisedto":"S2-2306663","release":"Rel-17","crspec":23.501,"crspecversion":"17.8.0","workitem":[{"winame":"NR_UE_pow_sav_enh-Core"},{"winame":" TEI17"}],"crnumber":4232.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304190.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.4.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304191","title":"Paging Early Indication with emergency","source":"Ericsson, T-Mobile USA, AT&T, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Specify the handling of PEI function when UE has emergency PDU session","secretary_remarks":"Postponed","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12400,"status":"postponed","reservation_date":"2023-05-04 19:15:10","uploaded":"2023-04-07 15:57:34","revisionof":"","revisedto":"S2-2306664","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"NR_UE_pow_sav_enh-Core"},{"winame":" TEI17"}],"crnumber":4233.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304191.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.4.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304192","title":"[DRAFT] Reply LS on the use of PEI during an emergency PDU session","source":"Ericsson Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Provides SA WG2 view on the Paging Early Indication support for a UE with emergency PDU session","secretary_remarks":"Response to S2-2303953. Postponed","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12350,"status":"postponed","reservation_date":"2023-05-04 19:26:02","uploaded":"2023-04-07 15:57:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_UE_pow_sav_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304192.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304214","title":"On uniqueness and policing of AF specific UE ID usage","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper elaborates on the necessary steps to be taken in order to guarantee the proper usage of the AF specific UE ID","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12440,"status":"noted","reservation_date":"2023-05-04 22:19:58","uploaded":"2023-04-07 21:13:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304214.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304215","title":"Authorization of usage of AF specific UE ID - Option 1","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.20 is updated to: Remove the note as proposed by SA WG3 and replace it with a reference to TS 23.003; Clarify how a PCF\/NEF can verify that a certain AF is using only the AF specific UE IDs it is authorized to use by referring to a new clause introduced in clause TS 23.502.","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12460,"status":"noted","reservation_date":"2023-05-04 22:19:58","uploaded":"2023-04-07 21:13:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.8.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":4241.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304215.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304216","title":"Authorization of usage of AF specific UE ID - Option 1","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Clause 5.20 is updated to: Remove the note as proposed by SA WG3 and replace it with a reference to TS 23.003; Clarify how a PCF\/NEF can verify that a certain AF is using only the AF specific UE IDs it is authorized to use by referring to a new clause introduced in clause TS 23.502.","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12470,"status":"noted","reservation_date":"2023-05-04 22:20:00","uploaded":"2023-04-07 21:13:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":4242.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304216.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304217","title":"Authorization of usage of AF specific UE ID - Option 1","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The changes introduced can be summarized as follows: Introduced new clause 4.15.10A to describe how the new Nudm_AFSpecificUEID Verify service operation is used by the PCF and NEF to verify that a certain AF is using only AF specific UE identifiers it is authorized to use; The table in caluse 5.2.3.1 is extended to include the newly defined AFSpecificUEID Verify service operation; The new clause 5.2.3.X (and related subclauses) describe the new Nudm_AFSpecificUEID service and the associated Verify service operation.","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12480,"status":"noted","reservation_date":"2023-05-04 22:20:01","uploaded":"2023-04-07 21:13:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.8.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3977.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304217.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304218","title":"Authorization of usage of AF specific UE ID - Option 1","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: The changes introduced can be summarized as follows: Introduced new clause 4.15.10A to describe how the new Nudm_AFSpecificUEID Verify service operation is used by the PCF and NEF to verify that a certain AF is using only AF specific UE identifiers it is authorized to use; The table in caluse 5.2.3.1 is extended to include the newly defined AFSpecificUEID Verify service operation; The new clause 5.2.3.X (and related subclauses) describe the new Nudm_AFSpecificUEID service and the associated Verify service operation.","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12490,"status":"noted","reservation_date":"2023-05-04 22:20:02","uploaded":"2023-04-07 21:13:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3978.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304218.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304219","title":"Authorization of usage of AF specific UE ID - Option 2","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.20 is updated to: Remove the note as proposed by SA WG3 and replace it with a reference to TS 23.003; Clarify how a PCF\/NEF can verify that a certain AF is using only the AF specific UE IDs it is authorized to use.","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12500,"status":"noted","reservation_date":"2023-05-04 22:20:03","uploaded":"2023-04-07 21:13:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.8.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":4243.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304219.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304220","title":"Authorization of usage of AF specific UE ID - Option 2","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Clause 5.20 is updated to: Remove the note as proposed by SA WG3 and replace it with a reference to TS 23.003; Clarify how a PCF\/NEF can verify that a certain AF is using only the AF specific UE IDs it is authorized to use.","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12510,"status":"noted","reservation_date":"2023-05-04 22:20:03","uploaded":"2023-04-07 21:13:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":4244.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304220.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304278","title":"[DRAFT] Reply LS on the use of PEI during an emergency PDU session","source":"OPPO","contact":"Peng Tan","contact-id":101478,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC:","secretary_remarks":"Response to S2-2303953. Merged into S2-2304192 (Postponed)","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12360,"status":"postponed","reservation_date":"2023-06-04 08:29:52","uploaded":"2023-04-07 21:27:16","revisionof":"","revisedto":"S2-2307337","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_UE_pow_sav_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304278.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304282","title":"The use of PEIPS during emergency PDU session","source":"OPPO","contact":"Peng Tan","contact-id":99889,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: A note is added at the end of Clause 5.4.12.2 of TS 23.501","secretary_remarks":"CR Cover sheet error! Merged into S2-2304190 (Postponed)","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12410,"status":"postponed","reservation_date":"2023-06-04 08:36:41","uploaded":"2023-04-07 21:21:38","revisionof":"","revisedto":"S2-2307333","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":4260.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304282.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304340","title":"[DRAFT] LS reply on the use of PEI during an emergency PDU session","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Proposed reply to RAN WG2 and RAN WG3 (cc: CT WG1) clarifying that SA WG2 expects RAN specifications to be aligned with the Stage 2 requirements","secretary_remarks":"Response to S2-2303953. Merged into S2-2304192 (Postponed)","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12370,"status":"postponed","reservation_date":"2023-06-04 10:15:01","uploaded":"2023-04-07 07:05:37","revisionof":"","revisedto":"S2-2307141","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_UE_pow_sav_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304340.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304403","title":"[DRAFT] Reply LS on enforcement of AF specific identifier","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on enforcement of AF specific identifier","secretary_remarks":"Revision of S2-2303271 from S2#155. Response to S2-2303921. Postponed","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12430,"status":"postponed","reservation_date":"2023-06-04 12:20:32","uploaded":"2023-04-07 17:08:26","revisionof":"S2-2303271","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304403.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304542","title":"Rewording of NOTE on AF Specific UE identifier","source":"Apple","contact":"Sudeep M Vamanan","contact-id":87305,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: NOTE 2 in clause 5.20 is reworded to remove reference to 33.501 and add text to clarify how the uniqueness of AF Specific UE identifier and restrictions on the usage is enforced.","secretary_remarks":"Revision of S2-2303270 from S2#155. Merged into S2-2304219 (noted)","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12520,"status":"noted","reservation_date":"2023-06-04 17:23:36","uploaded":"2023-04-07 18:01:03","revisionof":"S2-2303270","revisedto":"S2-2307045","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4155.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304542.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304544","title":"Enforcing restrictions on AF specific UE Identifier","source":"Apple","contact":"Sudeep M Vamanan","contact-id":87305,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper analyses the impact on 3GPP TS 23.501 from the SA WG3 conclusion on managing uniqueness of AF specific UE ID across different AFs. Related to incoming LS in S2-2303921.","secretary_remarks":"Noted","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12450,"status":"noted","reservation_date":"2023-06-04 17:27:41","uploaded":"2023-04-07 18:01:03","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_156E_Electronic_2023-04\/Docs\/S2-2304544.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305225","title":"Clarify the NOTE2 in 5.20","source":"China moible","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the NOTE2 in 5.20","secretary_remarks":"Revision of S2-2303013 from S2#155. Merged into S2-2304219 (noted)","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12530,"status":"noted","reservation_date":"2023-07-04 17:05:50","uploaded":"2023-04-07 17:08:26","revisionof":"S2-2303013","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":4171.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305225.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305229","title":"[DRAFT] Reply LS on the use of PEI during an emergency PDU session","source":"Qualcomm Austria RFFE GmbH","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Responds to RAN WG2 that text already exists for PEIPS and emergency services, and no further clarifications are needed","secretary_remarks":"Response to S2-2303953. Merged into S2-2304192 (Postponed)","agenda_item_sort_order":71,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":12380,"status":"postponed","reservation_date":"2023-07-04 17:14:20","uploaded":"2023-04-07 17:20:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_UE_pow_sav_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305229.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]