[{"name":"S2-2306269","title":"LS from GSMA ENSWI: LS reply on a new SST value for Extended Reality and Media Services","source":"GSMA ENSWI","contact":"Dan Wang","contact-id":90463,"tdoctype":"LS in","for":"Action","abstract":"GSMA ENSWI thanks SA WG2 for the LS on a new standardized SST value for Extended Reality and Media Services. GSMA ENSWI would provide the following feedback. Extended Reality and Media Services are promising services, and a new standardized SST will bring consistent user experience for Extended Reality and Media Services and will enhance the user experience, especially in the roaming case. Also, GSMA ENSWI is working on defining a new NEST (NEtwork Slice Template) for Extended Reality and Media Services. Action: GSMA ENSWI kindly asks SA WG2 to take the above information into account.","secretary_remarks":"Revision of Postponed S2-2303922 from S2#156E. Noted","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18090,"status":"noted","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303922","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"ENSWI21_Doc007","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306269.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306280","title":"LS on the Design of RTP Header Extension for PDU set handling","source":"SA WG4","contact":"Shuai Zhao","contact-id":95636,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 acknowledges SA WG2 s progress regarding the PDU set study (FS_XRM) and normative work in TS 23.501. In SA WG4#121, SA WG4 has agreed to work on defining the RTP header extension under WI 5G_RTP for PDU set handling, including PDU set sequence number, PDU sequence number, the indication of end PDU of a PDU set, PDU set importance, and optionally PDU set size. SA WG4 experts carefully consider codecs and application aspects of designing an efficient and meaningful RTP header extension to fulfil SA WG2 s requirement and agree on a single solution. In SA WG4#122, numerous proposals are currently under discussion. Therefore, we request that SA WG2 experts wait for SA WG4 work to finish before further investigation on identification of PDU set. SA WG4 believes that a format for the PDU set information header extension may be finalized by SA WG4#123-e. Guidelines on how to set the PDU set information fields within the new header extension will be finalized during SA WG4 Release-18 timeframe. Questions: - SA WG4 would like to ask if it is possible for a single QoS flow to include both PDUs marked with PDU set header extension and unmarked PDUs? - Does SA WG2 expect the application server to decide which PDUs belong to a data burst and signal related information in the RTP header extension? Action: SA WG4 respectfully asks SA WG2 to consider the above information and provide an answer to the raised questions.","secretary_remarks":"Revision of Postponed S2-2303974 from S2#156E. Responses drafted in S2-2306390, S2-2307035, S2-2307125, S2-2307215. Final response in S2-2308248","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18190,"status":"replied to","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303974","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2","lsoriginalls":"S4-230419","lsreply":"S2-2308248","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306280.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306309","title":"LS from SA WG4: LS out on the N6 PDU Set Identification","source":"SA WG4","contact":"Shuai Zhao","contact-id":95636,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for confirming the progress of the normative work timeline. As indicated in S4-230419, the new RTP header extension under SA WG4 5G_RTP will signal the PDU set information, including PDU set sequence number, PDU set boundary indication, PDU sequence number within a PDU set, PDU set size, and PDU set importance. During SA WG4#123-e, it was agreed to add a 3-bit End of Data Burst indication in the new header extension. SA WG4 has committed to progressing the semantics of the fields and developing normative guidelines for the Application Server on how to populate the fields of the RTP header extension for the supported media codecs. Upon completing such an effort, SA WG4 will continue to provide guidelines on how the UPF may extract some of the supported PDU set information from existing RTP\/SRTP headers, header extensions, and payloads in case the newly defined RTP header extension is absent. In addition to marking the last PDU of the data burst, SA WG4 sees the benefit of using additional bits to indicate inter-burst time, which may change dynamically due to various reasons, including application-layer rate control. SA WG4 believes that this can enable the RAN to switch to the most appropriate power state. SA WG4 kindly requests feedback from SA WG2 and RAN WG2 on the value and feasibility of such solution and if that can be supported within Rel. 18 timeframe. SA WG4 is also defining the SDP signaling of the usage of the RTP header extension based on RFC8285. This allows the AF to receive certain PDU set information and pass it along to the PCF\/NEF using the N5\/N33 interface procedures. The header extension configuration should be shared with the UPF, and SA WG4 will provide the relevant configuration information to SA WG2\/CT WG3 for this purpose. Action: 1. SA WG4 would like to ask SA WG2 to consider the above and provide any feedback on the attached document. 2. SA WG2 is kindly requested to provide feedback on the feasibility and value of introducing additional signaling bits related to the End of Burst within the Rel-18 timeframe.","secretary_remarks":"Responses drafted in S2-2306390, S2-2306466, S2-2306613, S2-2307037, S2-2307155, S2-2307295, S2-2307356. Final response in S2-2308199","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18270,"status":"replied to","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-04-27 06:26:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"RAN WG1","lsoriginalls":"S4-230739","lsreply":"S2-2308199","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306309.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306312","title":"LS from RAN WG3: Reply LS on RAN information exposure for XRM","source":"RAN WG3","contact":"Angelo Centonza","contact-id":45800,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for their LS on new functionalities exposing NG-RAN information in the specifications under SA WG2 control. RAN WG3 has analysed the functionalities described by SA WG2 and would like to provide the following feedback. RAN WG3 discussed the UP based QoS Notification Control and reached no consensus on the benefits of this feature. This feature may be feasible, but RAN WG3 has not analysed the details. During RAN WG3 s discussions the following possible technical issues were raised by some companies that may need to be further clarified by SA WG2: - UP based QNC may not be able to support reporting alternative QoS parameters. - Even in UP based QNC, QNC reporting delay is also possible, e.g. due to the hysteresis before determining the QNC result, and the delay depends on RAN s implementation. - UP based QNC is on top of GTP-U\/UDP which may cause out of sequence delivery. Concerning the data rate information, and assuming that data rate information is the measured value of the current bit rate, RAN WG3 thinks that: - The per QoS flow data rate measured by RAN cannot reflect the real bandwidth that can be provided by the network, since it is effected by many factors such as the traffic rate, the air-interface condition and the scheduling strategies - It is not feasible to assume that data rates measured per DRB by the RAN can be converted in data rates per QoS Flow, to be signalled to the CN. - The per QoS flow data rate measured by RAN before PDCP is exactly the same as the data rate that the UPF could measure, hence there is no need for RAN to report it. RAN WG3 therefore cannot reach consensus on the benefits of a solution based on data rate information on a per QoS Flow basis measured and exposed by NG-RAN via NGAP to SMF or via GTP-U to UPF. Action: RAN WG3 kindly ask SA WG2 to take the above into account and to provide feedback to RAN WG3 and clarify the benefits of UP based QoS Notification Control to RAN WG3, if needed.","secretary_remarks":"Responses drafted in S2-2306993, S2-2306391, S2-2306493. Final response in S2-2308200.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18380,"status":"replied to","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-04-28 05:15:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-232169","lsreply":"S2-2308200","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306312.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306323","title":"LS from RAN WG2: LS on TSCAI for XR","source":"RAN WG2","contact":"Benoist SEBIRE","contact-id":68461,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed the provision of assistance information from CN to RAN for XR services and is wondering whether TSCAI can be provided for both GBR and non-GBR QoS flows in case of XR. Action: RAN WG2 respectfully asks SA WG2 to clarify whether TSCAI can be provided for both GBR and non-GBR QoS flows in case of XR.","secretary_remarks":"Responses drafted in S2-2306389, S2-2306465, S2-2306899, S2-2307036, S2-2307355. Final response in S2-2308197","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18100,"status":"replied to","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-05-03 10:36:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"R2-2304569","lsreply":"S2-2308197","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306323.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306389","title":"[DRAFT] LS Reply on TSCAI for XR","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on TSCAI for XR","secretary_remarks":"Response to S2-2306323. Revised to S2-2307901.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18110,"status":"revised","reservation_date":"2023-10-05 06:40:32","uploaded":"2023-05-12 16:20:11","revisionof":"","revisedto":"S2-2307901","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306389.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306390","title":"[DRAFT] LS reply on the N6 PDU Set Identification","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply on the N6 PDU Set Identification","secretary_remarks":"Response to S2-2306309. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18360,"status":"not treated","reservation_date":"2023-10-05 06:40:32","uploaded":"2023-05-12 16:20:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306390.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306391","title":"[DRAFT] LS reply on RAN information exposure for XRM","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"LS reply on RAN information exposure for XRM","secretary_remarks":"Response to S2-2306312. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18470,"status":"not treated","reservation_date":"2023-10-05 06:40:32","uploaded":"2023-05-12 16:20:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306391.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306418","title":"Resolution of EN for L4S","source":"[Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Meta USA] China Mobile","contact":"Tianji Jiang","contact-id":90312,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides explanation for UE mobility and non-homogeneous L4S support scenario","secretary_remarks":"Revision of (Agreed) S2-2306189 from S2#156-e. Merged into S2-2307910","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18570,"status":"merged","reservation_date":"2023-10-05 22:07:26","uploaded":"2023-05-12 16:23:18","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4219.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306418.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.3.1, 5.37.3.2, 5.37.3.3,6.3.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306463","title":"Introduction of a new standard SST for Extended Reality and Media Services","source":"China Mobile, ZTE, Huawei, KDDI, Verizon, NTT Docomo, China Unicom, China Telecom","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing a new standardized SST for low latency communications and Advanced interactive communication","secretary_remarks":"Revision of S2-2305132. Revised to S2-2307909, merging S2-2307315.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18490,"status":"revised","reservation_date":"2023-11-05 06:43:48","uploaded":"2023-05-12 11:36:42","revisionof":"S2-2305132","revisedto":"S2-2307909","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4493.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306463.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.15.2.2, 5.37.5.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306465","title":"[DRAFT] Reply LS on TSCAI for XR","source":"OPPO","contact":"Boren Guo","contact-id":100775,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on TSCAI for XR","secretary_remarks":"Response to S2-2306323. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18140,"status":"not treated","reservation_date":"2023-11-05 07:14:31","uploaded":"2023-05-12 07:22:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306465.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306466","title":"[DRAFT] Reply LS on the N6 PDU Set Identification","source":"OPPO","contact":"Boren Guo","contact-id":100775,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on the N6 PDU Set Identification","secretary_remarks":"Response to S2-2306309. Revised to S2-2307904.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18280,"status":"revised","reservation_date":"2023-11-05 07:14:31","uploaded":"2023-05-12 07:22:36","revisionof":"","revisedto":"S2-2307904","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG1, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306466.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306467","title":"Clarification on the usage of TSCAI for XRM services","source":"OPPO","contact":"Boren Guo","contact-id":100775,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that TSCAI can be provided for both GBR and non-GBR QoS flows in case of XRM.","secretary_remarks":"Revised to S2-2307902.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19590,"status":"revised","reservation_date":"2023-11-05 07:14:31","uploaded":"2023-05-12 07:22:36","revisionof":"","revisedto":"S2-2307902","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4587.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306467.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.37.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306468","title":"PDU Set based QoS Handling requested by UE","source":"OPPO","contact":"Boren Guo","contact-id":100775,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description of PDU Set based QoS Handling requested by UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19220,"status":"not treated","reservation_date":"2023-11-05 07:14:32","uploaded":"2023-05-12 07:22:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4588.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306468.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.7.7.1, 5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306469","title":"PDU Set based QoS Handling requested by UE","source":"OPPO","contact":"Boren Guo","contact-id":100775,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description of PDU Set based QoS Handling requested by UE.","secretary_remarks":"Check Affected Clauses! Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19230,"status":"not treated","reservation_date":"2023-11-05 07:14:33","uploaded":"2023-05-12 07:22:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4170.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306469.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306470","title":"Resolve ENs for support of PDU Set handling","source":"[Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ]OPPO,[ MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson]","contact":"Boren Guo","contact-id":100775,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling.","secretary_remarks":"Revision of S2-2306194. Check Affected Clauses! Merged into S2-2308192","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18950,"status":"merged","reservation_date":"2023-11-05 07:18:24","uploaded":"2023-05-12 07:22:36","revisionof":"S2-2306194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306470.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306471","title":"Traffic Parameters Measurement generation issue","source":"Lenovo, [Huawei, HiSilicon, vivo]","contact":"Lizhuo Zheng","contact-id":98359,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that PCF generates PCC rules with Traffic Parameter Measurement based on its local configuration if no periodicity information from AF","secretary_remarks":"Revision of S2-2306202. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19540,"status":"not treated","reservation_date":"2023-11-05 07:30:18","uploaded":"2023-05-11 09:36:48","revisionof":"S2-2306202","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":995.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306471.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306472","title":"ECN marking for L4S status events exposure from SMF to AF via NEF","source":"Lenovo","contact":"Lizhuo Zheng","contact-id":98359,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the ECN marking for L4S is not used any more as one of the monitoring events that will be reported from SMF to AF via NEF","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18850,"status":"not treated","reservation_date":"2023-11-05 07:39:10","uploaded":"2023-05-11 09:36:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4171.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306472.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 4.15.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306473","title":"Resolve ENs for support of PDU Set handling","source":"Lenovo, [Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson]","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the sentence When the receiving NG-RAN does not support PDU set based QoS handling, it ignores PDU set QoS parameters Remove the following EN, Editor's note: [XRM] The applicability and details of PDU Set handling in uplink direction is pending RAN WG's progress.","secretary_remarks":"Revision of S2-2306194. Merged into S2-2308192","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18960,"status":"merged","reservation_date":"2023-11-05 07:58:18","uploaded":"2023-05-12 13:55:00","revisionof":"S2-2306194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306473.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.7.7.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306479","title":"Analysis of UP based QoS Notification Control","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"discussion","for":"Agreement","abstract":"Analysis of UP based QoS Notification Control","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18430,"status":"not treated","reservation_date":"2023-11-05 09:20:55","uploaded":"2023-05-12 14:07:29","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_157_Berlin_2023-05\/Docs\/S2-2306479.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306493","title":"[DRAFT] Reply LS on RAN information exposure for XRM","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on RAN information exposure for XRM","secretary_remarks":"Response to S2-2306312. Revised to S2-2307908.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18440,"status":"revised","reservation_date":"2023-11-05 10:13:30","uploaded":"2023-05-12 14:06:38","revisionof":"","revisedto":"S2-2307908","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306493.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306521","title":"Update for network exposure for XR services","source":"Tencent, Tencent Cloud, vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.37.4, it clarifies the congestion information, data rate informaiton and round trip delay for multiple QoS flows. Regards to the EN, it is proposed to remove it in clause 5.37.4, since it will be solved in TS 23.503. Remove the measured data rate from RAN.","secretary_remarks":"Revision of S2-2306191. Revised to S2-2307907 (withdrawn). Noted in parallel session","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18710,"status":"revised","reservation_date":"2023-11-05 13:28:42","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2306191","revisedto":"S2-2307907","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4503.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306521.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Clause 5.37.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306522","title":"QoS Monitoring and 5GS information exposure update","source":"vivo, [CATT, Huawei], China Mobile, Tencent, Tencent Cloud","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify QoS monitoring general description Clarify Reported congestion information Remove the measured data rate from RAN Clear the related ENs","secretary_remarks":"Revision of S2-2304392. Revised to S2-2307958.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18640,"status":"revised","reservation_date":"2023-11-05 13:28:43","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2304392","revisedto":"S2-2307958","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4294.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306522.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.7.2.7.1, 5.37.3.3, 5.45.1, 5.45.2, 5.45.3, 5.45.4, 5.45.3, 5.37.3.3.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306523","title":"QoS monitoring and use plane reporting","source":"Vivo, Lenovo, Tencent, Tencent Cloud","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce user plane reporting. Fix the description for QoS monitoring.","secretary_remarks":"Revision of S2-2304393. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18860,"status":"not treated","reservation_date":"2023-11-05 13:28:43","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2304393","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4001.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306523.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306524","title":"QoS monitoring enhancement","source":"vivo, [Lenovo, Tencent, Tencent Cloud, China Mobile]","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the incomplete examples. Fix the description for QoS monitoring. Round-trip delay measurements for multiple QoS flows, specifically for one service data flow with two QoS flows used for UL and DL respectively, as described in clause 5.37.4 of TS 23.501 [2].","secretary_remarks":"Revision of S2-2306193. Merged in S2-2308191.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18700,"status":"merged","reservation_date":"2023-11-05 13:28:44","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2306193","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":967.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306524.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.1.3.21, 6.1.3.5, 6.1.3.18, 6.2.3, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306525","title":"Fix the UE mobility EN for L4S and congestion exposure","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Fix the mobility EN in clause 5.37.3.3.","secretary_remarks":"Confirm CR Number - CR states 4297! Merged into S2-2308187.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18580,"status":"merged","reservation_date":"2023-11-05 13:28:45","uploaded":"2023-05-12 16:20:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4597.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306525.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306526","title":"Resolve ENs for support of PDU Set handling","source":"[Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated], vivo, [Ericsson]","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling. Clarify: UL PDU Set handling cannot applied to the UE which is incapable of the PDU Set handling. The definition of uplink PDU Set handling at SA WG2 will be prompted based on RAN WG's notification for their functionality definition on uplink PDU Set handling.","secretary_remarks":"Revision of S2-2306194. Merged into S2-2307960","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18970,"status":"merged","reservation_date":"2023-11-05 13:28:45","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2306194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306526.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.7.1.2, 5.7.7, 5.8.2.4.2, 5.8.5.3, 5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306527","title":"KI#5: Support for PDU Set QoS Framework","source":"[Qualcomm Incorporated, Apple], vivo, [CATT, Samsung, Meta USA, Nokia, Nokia Shanghai Bell, Ericsson]","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added clause 6.1.3.27.X as an introductory clause to the PDU Set based QoS handling. updated clause 6.2.2.4 to describe how the SMF sets the PDU Set related QoS Characteristics (PSDB, PSER, PSIHI) Extended table 6.3.1 (PCC rule info) to include the PDU Set Information.","secretary_remarks":"Revision of S2-2306196. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19330,"status":"not treated","reservation_date":"2023-11-05 13:28:46","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2306196","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":891.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306527.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306528","title":"PCF provides the Periodicity to SMF via PCC rules for resolving the EN for KI#8","source":"China mobile, vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PCF should send the Periodicity information received from the AF to SMF via PCC rules. Remove Editor s note in 5.37.8. Align 501 and 503.","secretary_remarks":"Revision of S2-2306203. Revised to S2-2308026.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19500,"status":"revised","reservation_date":"2023-11-05 13:28:47","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2306203","revisedto":"S2-2308026","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4529.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306528.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.37.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306529","title":"Procedure to acquire jitter information","source":"[MediaTek, KDDI, Futurewei, China Mobile, Tencent, Huawei], vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the N4 Session Level Reporting procedure with Traffic Parameter measurement reporting event triggered during N4 Session Establishment\/Modification procedure. Add periodicity information into Npcf_PolicyAuthorization service.","secretary_remarks":"Revision of S2-2306244. Merged into S2-2308025.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19460,"status":"merged","reservation_date":"2023-11-05 13:28:48","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2306244","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":3989.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306529.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306530","title":"Periodicity measurement and reporting for power saving","source":"[Huawei, HiSilicon], vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce policy for support of measurement of DL periodicity associated jitter information and\/or periodicity for power saving. Delete the EN about whether TSCAC can be reused or not.","secretary_remarks":"Revision of S2-2306202. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19550,"status":"not treated","reservation_date":"2023-11-05 13:28:48","uploaded":"2023-05-12 16:20:11","revisionof":"S2-2306202","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":995.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306530.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.1.3.2.4, 6.1.3.22, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306604","title":"Resolution of EN for L4S","source":"Ericsson, [Nokia], [Nokia Shanghai Bell], [Samsung], [Meta USA]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides explanation for UE mobility and non-homogeneous L4S support scenario. Rev3 (SA WG2#157): If ECN marking for L4S is not supported e.g. due to inter-NG-RAN handover or PSA UPF relocation, if enabled by the QoS Monitoring policy information from PCF, SMF may activate QoS Monitoring of congestion information (see clause 5.45). AF can request QoS Monitoring (Congestion information) and ECN marking for L4S and if so, SMF activates QoS Monitoring if ECN marking for L4S is not available (that is, either ECN marking for L4S or Congestion information monitoring is active at a time on a QoS Flow).","secretary_remarks":"Revision of S2-2306189. Revised to S2-2307910, merging S2-2306991, S2-2307397, S2-2306418.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18530,"status":"revised","reservation_date":"2023-11-05 17:35:27","uploaded":"2023-05-12 19:30:34","revisionof":"S2-2306189","revisedto":"S2-2307910","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4219.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306604.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.3.1, 5.37.3.2, 5.37.3.3, 5.45.3, 6.3.3.3 ","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306605","title":"Signaling procedures to support ECN marking for L4S.","source":"[OPPO, Samsung], Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the PDU session establishment\/modification to support ECN marking for L4S.","secretary_remarks":"Revision of S2-2306190. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18790,"status":"not treated","reservation_date":"2023-11-05 17:35:27","uploaded":"2023-05-12 19:30:34","revisionof":"S2-2306190","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4041.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306605.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":" 4.3.2.2, 4.3.3.2, 4.9.1.2.2, 4.9.1.3, 5.2.5.3.2, 5.2.6.9.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306606","title":"Notification of ECN marking for L4S support flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When AF provides indication of L4S support, it is notified by PCF about support for ECN marking for L4S. PCF gets information from SMF. SMF notities according to new trigger.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18800,"status":"not treated","reservation_date":"2023-11-05 17:35:28","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"S2-2308417","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1048.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306606.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.3.5, 6.1.3.18","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306607","title":"QNC Direct Exposure by UPF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR Solves the ENs in 5.7.2.4.1, 5.37.4, and 5.45 by removing UPF PSA exposure of QNC information provided by RAN over GTP-U. This CR is based on the LS reply by RAN WG3: As in LS Reply: UP based QNC may not be able to support reporting alternative QoS parameters . Consequently, UPF PSA exposure of QNC information can provide only a subset of the QNC information notification functionality (only the indication is exposed) and therefore it can t serve same use cases as existing mechanism via SMF\/PCF. As in LS Reply: RAN WG3 discussed the UP based QoS Notification Control and reached no consensus on the benefits of this feature . In SA WG2, the UC brought up in discussions has been application data rate adaptation. The benefits mentioned for this use case have been: Improved notification efficiency Improved notification speed But, whether UPF exposure in fact delivers these benefits and whether they provide significant value is unclear: Higher efficiency & speed may not be achieved in all deployments. As in LS reply even in UP based QNC, QNC reporting delay is also possible, e.g. due to the hysteresis before determining the QNC result, and the delay depends on RAN s implementation . Consequently, the actual relevance of any time savings is uncertain. And whether an application can effectively adapt its rate based only on this indication and without further guidance (e.g. QoS that may be available based on alternative QoS) is unclear. As in LS Reply: UP based QNC is on top of GTP-U\/UDP which may cause out of sequence delivery . Probably this can be avoided with guard times and correction logic in UPF. But that is foreseen to delay the notification and complicates the implementation. Based on the above, there are not clear benefits that justify enhancing 5GS Rel-18 with UPF PSA exposure of QNC information provided by RAN over GTP-U. Therefore, this option is not specfied and this CR removes this option and the related ENs from the specifications.","secretary_remarks":"Revised to S2-2307906.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18610,"status":"revised","reservation_date":"2023-11-05 17:35:29","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"S2-2307906","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4604.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306607.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.4, 5.45, 5.7.2.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306608","title":"Exposure of RAN measured data rates","source":"Ericsson, Deutsche Telekom, China Mobile, ZTE, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR Solves the ENs by removing data rate measurements in RAN. It is based the following answers in LS reply by RAN WG3: The per QoS flow data rate measured by RAN cannot reflect the real bandwidth that can be provided by the network, since it is effected by many factors such as the traffic rate, the air-interface condition and the scheduling strategies. It is not feasible to assume that data rates measured per DRB by the RAN can be converted in data rates per QoS Flow, to be signalled to the CN. The per QoS flow data rate measured by RAN before PDCP is exactly the same as the data rate that the UPF could measure . And finally: RAN WG3 therefore cannot reach consensus on the benefits of a solution based on data rate information on a per QoS Flow basis measured and exposed by NG-RAN via NGAP to SMF or via GTP-U to UPF . Above statements are said to be under assumption that what RAN is expected to provide as data rate information is the measured value of the current bit rate . According to 5.45 and 5.37.4 in TS 23.501 RAN assumption is correct. The above statements reflects then RAN WG3 feedback to the data rate measurements in RAN discussed in SA WG2. Based on RAN WG3 reponse, there are many complexities in specifying RAN measured data rates, and the benefits they bring on top of UPF measured data rates are unclear. The proposal is not to specify RAN data rate measurements. This CR removes that fucntionality and the related ENs from the specifications.","secretary_remarks":"Revised to S2-2307905.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18390,"status":"revised","reservation_date":"2023-11-05 17:35:30","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"S2-2307905","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4605.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306608.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.4, 5.45.4 ","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306609","title":"Network exposure support for XR services of RTT measurements","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying the new XRM RTT is measured on two QoS Flows, each carrying a direction of the service data flow. Measurement of this QoS parameter can be requested by an AF that provides different QoS requirements for each direction (DL and UL) of the XRM service data flow.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18730,"status":"not treated","reservation_date":"2023-11-05 17:35:30","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4606.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306609.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.37.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306610","title":"QoS monitoring enhancement","source":"[vivo], [Lenovo], [Tencent], [Tencent Cloud], [China Mobile], Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the incomplete examples. Fix the description for QoS monitoring. Rev.3 (SA WG2#157) Add RTT over Two QoS flows: An AF which provides different QoS requirements on each direction (UL and DL) of the XRM service data flow can subscribe to new Round-trip delay over two QoS flows specified in 5.37.4 in TS 23.501. A new PCF event is specified with that purpose. PCF determines the QoS Monitoring Policy for the PCC Rule for each service data flow direction based on the AF request, it calculates the RTT measurements based on reports received from SMF, and it reports the measurement to AF","secretary_remarks":"Revision of S2-2306193. Revised to S2-2307959.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18670,"status":"revised","reservation_date":"2023-11-05 17:35:31","uploaded":"2023-05-12 19:30:34","revisionof":"S2-2306193","revisedto":"S2-2307959","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":967.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306610.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.1.3.21, 6.1.3.5, 6.1.3.18, 6.2.3, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306611","title":"Signaling procedures to support policy control enhancements for multi-modal services","source":"Ericsson, China Telecom, Tencent, Samsung, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.15.6.6, 4.15.6.6a, the procedures of interaction between AF and 5GC are updated to include new requirements and parameters to support policy control enhancements for multi-modal services. Accordingly, the Nnef_AFsessionWithQoS service in clause 5.2.6.9 and the Npcf_PolicyAuthorization service in clause 5.2.5.3 are updated. Use the terminology single-modal data flow in alignment with TS 23.501 4.15.6.6a, step 4, as per offline agreement during SA WG2#156E, the following text has been removed: If the QoS monitoring requirements are updated, the PCF updates the PCC rules considering the updated QoS information provided by the AF.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19720,"status":"not treated","reservation_date":"2023-11-05 17:35:31","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"S2-2310735","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4181.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306611.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.6.6, 4.15.6.6a, 5.2.6.9.2, 5.2.6.9.5, 5.2.5.3.2, 5.2.5.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306612","title":"Support for delivery of multi-modal services","source":"Ericsson, China Telecom, Tencent, Samsung, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the definition of Multi-modal Service Requirements , and include the list of new attributes the AF may provide for the delivery of multi-modal services, according to 23.501 specification Add Multi-modal Service ID, as input for PCC decisions in clause 6.2.1.2 Definition of the term Multi-modal Data from TR 22.847 Introduce the terminology single-modal data flow in alignment with TS 23.501","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19730,"status":"not treated","reservation_date":"2023-11-05 17:35:32","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"S2-2310736","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1049.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306612.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"3.1, 6.1.3.27.3, 6.2.1.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306613","title":"[DRAFT] LS response on the N6 PDU Set Identification","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Provide a response to SA4","secretary_remarks":"Response to S2-2306309. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18340,"status":"not treated","reservation_date":"2023-11-05 17:35:33","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG1, RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306613.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306614","title":"Resolve ENs for support of PDU Set handling","source":"[Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo] Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling. Rev 5: Move indication to add PDU Set Information from the FAR to the QER. A new indication for PDU Set Handling is sent from the SMF to the NG-RAN. When that is acknowledged by the NG-RAN, the SMF activates PDU Set Identification in the UPF.","secretary_remarks":"Revision of S2-2306194. Merged into S2-2308192.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18980,"status":"merged","reservation_date":"2023-11-05 17:35:33","uploaded":"2023-05-12 19:30:34","revisionof":"S2-2306194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306614.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.7.1.2, 5.7.7, 5.8.2.4.2, 5.8.5.3, 5.8.5.4, 5.8.5.6, 5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306615","title":"Correction to UL\/DL policy control based on RT latency requirement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the text in clause 6.1.3.27.2 about the use case where the UL and DL traffic of the service have different QoS requirements. This use case is misplaced, as it is already covered in TS 23.501 clause 5.37.4 (Network Exposure of 5GS information). In particular the text about Round trip delay for multiple QoS Flows of the XR service (e.g. the UL and DL are separated into two flows) , covers reporting RT delay for two QoS flows. UL\/DL policy control is the functionality where PCF splits the QoS flow into two separate flows (one for UL and one for DL) in order to meet the required RT delay. The functionality is not applicable to separate QoS flows provided by the AF Make the following functionalities mutually exclusive: UL\/DL policy control based on round-trip latency requirement, and Subscription to real-time measurements of QoS parameters for a service data flow","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19780,"status":"not treated","reservation_date":"2023-11-05 17:35:34","uploaded":"2023-05-12 19:30:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1050.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306615.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.1.3.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306616","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"Ericsson [Tencent, Tencent Cloud, Huawei, HiSilicon]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN Rev 2: Handling of individual parameters within Traffic Parameter Measurements Generation of Traffic Parameter Measurement indication at the PCF Sending of DL Periodicity to the UPF when available in the PCC Rule Remove the EN on how to provide Periodicity to the SMF Rename Traffic Parameter Measurements as N6 Traffic Parameter Measurements Add End of Data Burst indication to the QER and remove it from the FAR","secretary_remarks":"Revision of S2-2306201. Merged into S2-2308024.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19390,"status":"merged","reservation_date":"2023-11-05 17:35:34","uploaded":"2023-05-12 19:30:34","revisionof":"S2-2306201","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306616.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.8.5.4, 5.8.5.11, 5.8.5.12, 5.37.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306617","title":"Procedure to acquire jitter information","source":"[MediaTek, KDDI, Futurewei, China Mobile, Tencent, Huawei], Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the N4 Session Level Reporting procedure with Traffic Parameter measurement reporting event triggered during N4 Session Establishment\/Modification procedure. Add periodicity information into Npcf_PolicyAuthorization service. Rev 3: Traffic Parameter Measurements can be extended to new parameters that can be reported in the future. Therefore, the parameters to be requested and reported need to be indicated. Renamed as N6 Traffic Parameter Measurements to set the right scope. PCF builds PCC rules with N6 Traffic Parameter Measurements request at reception of UL or DL Periodicity from AF and\/or local policies PCF requests UL and\/or DL Periodicity measurements when not received from the AF. SMF composes TSCAI from UL and\/or DL Periodicity both before and after UPF reporting. SMF requests N6 Traffic measurement reports from UPF according to the N6 Traffic measurements in the PCC rule. The procedure to mark End of Data Burst has been added.","secretary_remarks":"Revision of S2-2306244. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19470,"status":"not treated","reservation_date":"2023-11-05 17:35:35","uploaded":"2023-05-12 19:30:34","revisionof":"S2-2306244","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":3989.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306617.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 4.3.3.2, 4.4.2.2, 5.2.5.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306618","title":"Periodicity measurement and reporting for power saving","source":"[Huawei, HiSilicon, vivo], Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce policy for support of measurement of DL periodicity associated jitter information and\/or periodicity for power saving. Delete the EN about whether TSCAC can be reused or not. Rev 4: Traffic Parameter Measurement is renamed as N6 Traffic Parameter Measurement , to set the right scope for it. All N6 traffic parameters to be measured are considered optional, to allow for future development UL and DL Periodicity are optional within Traffic Parameter Information","secretary_remarks":"Revision of S2-2306202. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19560,"status":"not treated","reservation_date":"2023-11-05 17:35:36","uploaded":"2023-05-12 19:30:34","revisionof":"S2-2306202","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":995.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306618.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.1.3.2.4, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306629","title":"Resolve ENs for support of PDU Set handling","source":"[Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO,] MediaTek [,Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson]","contact":"Mehrdad Shariat","contact-id":97826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling.","secretary_remarks":"Revision of S2-2306194. Merged into S2-2307960.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18990,"status":"merged","reservation_date":"2023-11-05 18:38:57","uploaded":"2023-05-12 16:56:36","revisionof":"S2-2306194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306629.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.7.1.2, 5.7.7, 5.8.2.4.2, 5.8.5.3, 5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306683","title":"Addressing default PDU-set importance","source":"Lenovo,","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that when the PCF determines that an application session requires PDU set QoS handling the PCF, in addition to, PSDB, PSER and PSIHI determines also a default PDU set importance. The PCF provides the default PDU set importance within a PCC rule to the SMF. The SMF in turn includes a default PDU Set importance parameter in the N4 rule to the UPF. The UPF includes the default PDU Set importance in GTP-U for a PDU Set if the UPF determines that the PDU does not belong to a PDU Set already and marks it with PDU Set information. In addition, it is also proposed the AF to include a default PDU Set importance value to the PCF in case the AF is aware that the application session contains PDUs that do not match the protocol description of a service data flow. The information by the AF may be used by the PCF to determine appropriate PCC rules that includes the default PDU Set importance value provided by the AF.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19240,"status":"not treated","reservation_date":"2023-11-05 21:57:21","uploaded":"2023-05-12 19:06:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4609.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306683.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306687","title":"PDU Set QoS handling: non-homogenous support (Alternative 1)","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added description on non-homogenous support of PDU set based QoS handling in NG-RAN Clarified that PDU Set QoS handling is enabled by sending at least one of the PDU Set QoS Parameters to the NG-RAN.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19150,"status":"not treated","reservation_date":"2023-11-05 22:34:17","uploaded":"2023-05-12 20:03:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4610.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306687.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":" 5.7.7.1, 5.37.5.x (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306688","title":"PDU Set QoS handling: non-homogenous support (Alternative 2)","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added description on non-homogenous support of PDU set based QoS handling in NG-RAN Clarified that PDU Set QoS handling is enabled by sending at least one of the PDU Set QoS Parameters to the NG-RAN.","secretary_remarks":"Revised to S2-2307962, merging S2-2307203.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19100,"status":"revised","reservation_date":"2023-11-05 22:34:18","uploaded":"2023-05-12 20:03:34","revisionof":"","revisedto":"S2-2307962","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4611.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306688.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306689","title":"[DRAFT] Non-homogeneous deployment of PDU Set based QoS handling","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG4. CC: RAN WG2. Attachments: S2-2306687 (CR 04610 vs. TS 23.501)","secretary_remarks":"Revised to S2-2307963, merging S2-2307204.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19170,"status":"revised","reservation_date":"2023-11-05 22:34:18","uploaded":"2023-05-12 20:03:34","revisionof":"","revisedto":"S2-2307963","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306689.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306709","title":"Clarification on service operations for XRM service","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Multi-modal Service ID in Nnef_AFsessionWithQoS_Create service operation and Npcf_PolicyAuthorization_Create service operation. Adding new input, QoS monitoring requirements per media flow with the reference clause of TS 23.503. In addition, adding the NOTE clearly describing that it can be used for multi-modal service. Adding the reference clause for existing input, QoS parameter(s) to be measured","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19740,"status":"not treated","reservation_date":"2023-12-05 01:41:29","uploaded":"2023-05-12 01:43:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4187.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306709.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.9.2, 5.2.6.9.5, 5.2.5.3.2, 5.2.5.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306748","title":"Clarification on the TSCAI and QoS flow for the XR service","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying the GBR and non-GBR can be used for XR service. Adding the TSCAI determination for the XR service.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19620,"status":"not treated","reservation_date":"2023-12-05 03:03:08","uploaded":"2023-05-12 17:37:56","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4616.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306748.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.27.2.1, 5.37.1, 5.37.8.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306749","title":"Clarification on the NEF service operation and procedure","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the UL and\/or DL Periodicity to AF session with required Qos and Nnef_AFsessionWithQoS service related operation.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19630,"status":"not treated","reservation_date":"2023-12-05 03:03:08","uploaded":"2023-05-12 17:37:56","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4190.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306749.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.6.6, 4.15.6.6a, 5.2.6.9.2, 5.2.6.9.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306750","title":"Clarification on the AF Qos request","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the UL and\/or DL Periodicity to AF session with required Qos clause. Clarifying that the AF provides the Periodicity to PCF.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19640,"status":"not treated","reservation_date":"2023-12-05 03:03:09","uploaded":"2023-05-12 17:37:56","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1057.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306750.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.3.22, 6.2.1.2, 6.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306856","title":"Clarification on Protocol Description for PDU Set information","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: How to use PDU Set QoS parameters and which information is delivered by Protocol Description and how to use are clarified.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19250,"status":"not treated","reservation_date":"2023-12-05 07:08:21","uploaded":"2023-05-12 07:31:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4627.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306856.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.37.5.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306858","title":"PDU Set handling considering handover","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During handover, PSDB value for the forwarded PDU Sets should be compensated.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19260,"status":"not treated","reservation_date":"2023-12-05 07:11:25","uploaded":"2023-05-12 07:31:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4628.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306858.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.5.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306860","title":"Procedures for 5GS congestion exposure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AF Session with required QoS and Notification of User Plane Management Events procedures are updated to set congestion exposure and its notification of congestion method change.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18870,"status":"not treated","reservation_date":"2023-12-05 07:14:38","uploaded":"2023-05-12 07:31:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4199.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306860.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.6.3, 4.15.6.6, 4.15.6.6a","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306864","title":"Procedures for UPF relocation considering congestion exposure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UPF relocation procedures is modified to consider UPF s capability on ECN marking for L4S. and UPF s capability on ECN marking for L4S is added to UPF provisioning information in NRF.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18880,"status":"not treated","reservation_date":"2023-12-05 07:18:29","uploaded":"2023-05-12 07:31:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4200.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306864.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.5.1, 4.3.5.2, 4.3.5.3, 4.17.6.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306870","title":"Update on Data Rate Monitoring","source":"[CATT,] Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the data rate into measured traffic UL and\/or DL data rate.","secretary_remarks":"Revision of S2-2306188. Merged into S2-2308188","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18420,"status":"merged","reservation_date":"2023-12-05 07:29:38","uploaded":"2023-05-12 16:21:35","revisionof":"S2-2306188","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4364.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306870.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.45.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306871","title":"Support of extra traffic characteristics for alternative QoS profile","source":"[Nokia, Nokia Shanghai Bell,] Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 5.7.1.2a is updated to allow the SMF to provide MDBV for each alternative QoS profile 5.7.2.4 is updated to allow the RAN to check these extra traffic characteristics parameters.","secretary_remarks":"Revision of S2-2306187. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18740,"status":"not treated","reservation_date":"2023-12-05 07:29:39","uploaded":"2023-05-12 16:21:35","revisionof":"S2-2306187","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4183.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306871.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.7.1.2a, 5.7.2.4.2, 5.7.2.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306899","title":"[DRAFT] Reply LS on TSCAI for XR","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on TSCAI for XR","secretary_remarks":"Response to S2-2306323. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18150,"status":"not treated","reservation_date":"2023-12-05 08:06:00","uploaded":"2023-05-12 08:54:27","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306899.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306991","title":"Update for network exposure during handover","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution adds the configuration that the target NG-RAN reports congestion information immediately once the handover occurres, which can be used both for API based exposure and UPF-L4S.","secretary_remarks":"Merged into S2-2307910","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18560,"status":"merged","reservation_date":"2023-12-05 09:13:44","uploaded":"2023-05-12 16:59:45","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4639.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306991.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.3.1, 5.37.4 ","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306992","title":"Procedure to acquire jitter information","source":"[MediaTek, KDDI, Futurewei, China Mobile, Tencent], Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the N4 Session Level Reporting procedure with Traffic Parameter measurement reporting event triggered during N4 Session Establishment\/Modification procedure. Add periodicity information into Npcf_PolicyAuthorization service.","secretary_remarks":"Revision of S2-2306244. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19480,"status":"not treated","reservation_date":"2023-12-05 09:13:45","uploaded":"2023-05-12 16:59:45","revisionof":"S2-2306244","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":3989.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306992.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 4.3.3.2, 4.4.2.2, 5.2.5.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306993","title":"[DRAFT] Reply LS on RAN information exposure for XRM","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on RAN information exposure for XRM","secretary_remarks":"Response to S2-2306312. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18480,"status":"not treated","reservation_date":"2023-12-05 09:13:46","uploaded":"2023-05-12 16:59:45","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306993.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307013","title":"Policy Control for L4S","source":"[CATT, Samsung], Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: L4S ECN is used for QoS Flow binding; AF Session with required QoS includes the AF requested L4S ECN Request Indication, the L4S ECN Request Indication from the AF is used to do the PCC decision; SMF performs the L4S ECN PCC rule enforcement; Here is the summary changes of r11 for CC#4 based on r11 and comments provided: Delete' Indication of ECN marking for L4S (if available in the PCC rule);' in 6.1.3.2.4 Change PCF to SMF in 'The PCF should not bind the PCC rule(s) to the same QoS Flow' in 6.1.3.2.4 new paragraph Adding in 6.1.3.2.4 new EN: 'Editor's note: Whether PCC Rules for the supporting and non L4S supporting data flows can be bound to same QoS Flow is FFS.' Split out ' Indication of ECN marking for L4S' from flow description information in 6.2.1.2","secretary_remarks":"Revision of S2-2306241. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18810,"status":"not treated","reservation_date":"2023-12-05 09:29:41","uploaded":"2023-05-12 14:00:58","revisionof":"S2-2306241","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":897.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307013.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.1.3.2.4, 6.1.3.22, 6.2.1.2, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307014","title":"Resolve ENs for support of PDU Set handling","source":"Huawei, HiSilicon[, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson]","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling.","secretary_remarks":"Revision of S2-2306194. Revised to S2-2307960, merging S2-2306629, S2-2307283, S2-2306526.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18920,"status":"revised","reservation_date":"2023-12-05 09:29:42","uploaded":"2023-05-12 14:00:58","revisionof":"S2-2306194","revisedto":"S2-2307960","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307014.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.7.1.2, 5.7.7, 5.8.2.4.2, 5.8.5.3, 5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307015","title":"KI#6 text alignment text","source":"[Nokia, Nokia Shanghai Bell, ]Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Text alignment as per agreed clause heading. Removal of duplicate statement.","secretary_remarks":"Revision of S2-2306197. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19790,"status":"not treated","reservation_date":"2023-12-05 09:29:43","uploaded":"2023-05-12 14:00:58","revisionof":"S2-2306197","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4278.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307015.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 5.37.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307016","title":"Corrections on UL\/DL policy control based on RT requirement","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Corrections on UL\/DL policy control based on RT requirement","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19800,"status":"not treated","reservation_date":"2023-12-05 09:29:43","uploaded":"2023-05-12 14:00:58","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1060.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307016.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.3.22, 6.1.3.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307017","title":"[DRAFT] LS reply on design of RTP header","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS reply to SA4 on design of RTP header","secretary_remarks":"Revision of S2-2304717. Response to S2-2306280. Revised to S2-2307903.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18200,"status":"revised","reservation_date":"2023-12-05 09:29:44","uploaded":"2023-05-12 14:00:58","revisionof":"S2-2304717","revisedto":"S2-2307903","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307017.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307018","title":"[DRAFT] LS reply on TSCAI for XR","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS reply to SA4 on TSCAI for XR","secretary_remarks":"Response to S2-2306323. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18180,"status":"not treated","reservation_date":"2023-12-05 09:29:44","uploaded":"2023-05-12 14:00:58","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307018.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307019","title":"Periodicity measurement and reporting for power saving","source":"Huawei, HiSilicon[, vivo]","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce policy for support of measurement of DL periodicity associated jitter information and\/or periodicity for power saving. Delete the EN about whether TSCAC can be reused or not.","secretary_remarks":"Revision of S2-2306202. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19570,"status":"not treated","reservation_date":"2023-12-05 09:29:44","uploaded":"2023-05-12 14:00:58","revisionof":"S2-2306202","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":995.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307019.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.1.3.2.4, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307021","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"[Tencent, Tencent Cloud,] Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN","secretary_remarks":"Revision of S2-2306201. Merged into S2-2308024.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19400,"status":"merged","reservation_date":"2023-12-05 09:29:45","uploaded":"2023-05-12 14:00:58","revisionof":"S2-2306201","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307021.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 5.8.5.11, 5.8.5.12, 5.37.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307031","title":"Update on Data Rate Monitoring","source":"CATT","contact":"Chunshan Xiong","contact-id":94840,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the data rate measure is performed by the UPF","secretary_remarks":"Revision of S2-2306188. Merged into S2-2308188.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18600,"status":"merged","reservation_date":"2023-12-05 09:59:44","uploaded":"2023-05-12 12:58:34","revisionof":"S2-2306188","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4364.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307031.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.45.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307032","title":"Packet filter for the L4S traffic","source":"CATT","contact":"Chunshan Xiong","contact-id":94840,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the 'may' to 'can' in the NOTE. Add NOTE 4 TOS\/Traffic class includes the DSCP and ECN to identify that the DSCP and ECN are included in TOS\/Traffic class part. Remove the ECT(1) as the packet filter in the clause 5.37.3.1","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18750,"status":"not treated","reservation_date":"2023-12-05 09:59:45","uploaded":"2023-05-12 12:58:34","revisionof":"","revisedto":"S2-2308913","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4643.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307032.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.7.6.2, 5.7.6.3, 5.37.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307033","title":"RT latency requirements for different data flows","source":"CATT","contact":"Chunshan Xiong","contact-id":94840,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The RT latency requirement can also be supported with two different data flows, i.e., the UL delay of a data flow and DL delay of another data flow needs to meet the RT latency requirement. In such case, the AF needs to provide delay requirement between the UE and the PSA UPF expressed as the QoS Reference parameter or individual QoS parameters (as defined in clause 6.1.3.22 of TS 23.503 [45]) for each data flow, and the total latency of the two data flows meets the RT latency requirement. PCF determines the PDB and assigns the 5QI of each PCC rule for the two data flows.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19810,"status":"not treated","reservation_date":"2023-12-05 09:59:46","uploaded":"2023-05-12 12:58:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4644.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307033.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 5.37.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307034","title":"RT latency requirements for different data flows","source":"CATT","contact":"Chunshan Xiong","contact-id":94840,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As described in clause 5.37.6 of TS23.501 [2], the policy control of round-trip (RT) latency requirement can also be used on two different data flows. For the two different data flows, AF needs to provide delay requirement between the UE and the PSA UPF expressed as the QoS Reference parameter or individual QoS parameters (as defined in clause 6.1.3.22) for each data flow, and the two data flows can have different QoS requirements (e.g. different delay), . The PCF then identifies the PDB and assigns the 5QI of each PCC rule for the two data flows. In this case, the RT latency requirement of the two data flows is fulfilled by the sum of the PDB requirements.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19820,"status":"not treated","reservation_date":"2023-12-05 09:59:46","uploaded":"2023-05-12 12:58:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1061.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307034.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.3.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307035","title":"[DRAFT] LS on the Design of RTP Header Extension for PDU set handling","source":"CATT","contact":"Chunshan Xiong","contact-id":94840,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: RAN WG2","secretary_remarks":"Revision of S2-2304632. Response to S2-2306280. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18240,"status":"not treated","reservation_date":"2023-12-05 09:59:47","uploaded":"2023-05-12 12:58:34","revisionof":"S2-2304632","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307035.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307036","title":"[DRAFT] LS on TSCAI for XR","source":"CATT","contact":"Chunshan Xiong","contact-id":94840,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: RAN WG3","secretary_remarks":"Response to S2-2306323. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18160,"status":"not treated","reservation_date":"2023-12-05 09:59:47","uploaded":"2023-05-12 12:58:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307036.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307037","title":"[DRAFT] LS on the N6 PDU Set Identification","source":"CATT","contact":"Chunshan Xiong","contact-id":94840,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4, RAN WG2. CC: RAN WG1","secretary_remarks":"Response to S2-2306309. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18330,"status":"not treated","reservation_date":"2023-12-05 09:59:47","uploaded":"2023-05-12 12:58:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, RAN WG2","Cc":"RAN WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307037.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307049","title":"Clarification of End of data burst handling","source":"Apple","contact":"Sudeep M Vamanan","contact-id":103491,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarfied that UPF may detect end of data burst and mark the last PDU of the PDU Set to all the associated QoS Flows","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19660,"status":"not treated","reservation_date":"2023-12-05 10:39:25","uploaded":"2023-05-12 20:59:53","revisionof":"","revisedto":"S2-2309225","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4646.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307049.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.8.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307052","title":"PCF provides the Periodicity to SMF via PCC rules for resolving the EN for KI#8","source":"[China mobile,] NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PCF should send the Periodicity information received from the AF to SMF via PCC rules. Rev-02: Clarify that the Periodicity may be indicated as part of the Protocol Description, besides or instead a separate Periodicity parameter. Remove Editor s note in 5.37.8","secretary_remarks":"Revision of S2-2306203. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19520,"status":"not treated","reservation_date":"2023-12-05 11:00:08","uploaded":"2023-05-12 11:26:45","revisionof":"S2-2306203","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4529.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307052.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307053","title":"Indication of End of Data Burst as part of the PDU Set information","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to include the Indication of End of Data Burst as part of the PDU Set Information in clause 5.37.5.2.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19670,"status":"not treated","reservation_date":"2023-12-05 11:05:19","uploaded":"2023-05-12 11:26:45","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4648.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307053.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307082","title":"Discussion for QoS Flow Binding.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution propose to discuss how to improve the current QoS Flow Binding Mechanism when adding new features.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19650,"status":"not treated","reservation_date":"2023-12-05 11:37:06","uploaded":"2023-05-12 16:21:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307082.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307125","title":"[DRAFT] Reply LS on the Design of RTP Header Extension for PDU set handling","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: RAN WG2","secretary_remarks":"Response to S2-2306280. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18250,"status":"not treated","reservation_date":"2023-12-05 12:41:46","uploaded":"2023-05-12 17:14:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_RTP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307125.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307155","title":"[DRAFT] Reply LS on the N6 PDU Set Identification","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on the N6 PDU Set Identification","secretary_remarks":"Response to S2-2306309. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18350,"status":"not treated","reservation_date":"2023-12-05 13:31:38","uploaded":"2023-05-12 14:06:02","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307155.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307172","title":"Resolve EN on PDU set importance for PDU(s) that does not belong to a PDU set","source":"Lenovo, [Nokia, Nokia Shanghai Bell]","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the EN and add some descriptions on how PDU set importance is applied to the PDU(s) that does not belong to a PDU Set based on Protocol Description.","secretary_remarks":"Revision of S2-2306239. Merged into S2-2308193.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19050,"status":"merged","reservation_date":"2023-12-05 13:37:01","uploaded":"2023-05-12 13:55:00","revisionof":"S2-2306239","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4527.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307172.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307173","title":"Default PDU Set importance provisioning","source":"Lenovo, [KDDI, Futurewei, China Mobile, Tencent, Huawei, Samsung, Nokia, Nokia Shanghai Bell]","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The CR proposes to Add the default PDU Set importance and reference information to Npcf_PolicyAuthorization service. Add the default PDU Set importance and reference information to Nnef_AFsessionWithQoS service.","secretary_remarks":"Revision of S2-2306195. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19270,"status":"not treated","reservation_date":"2023-12-05 13:37:02","uploaded":"2023-05-12 13:55:00","revisionof":"S2-2306195","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":3999.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307173.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.6.6, 4.15.6.6a, 5.2.5.3, 5.2.6.9","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307174","title":"Default PDU set importance for PDU(s) that does not belong to a PDU set","source":"Lenovo, [Qualcomm Incorporated, Apple, vivo, CATT, Samsung, Meta USA, Nokia, Nokia Shanghai Bell, Ericsson]","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added Default PDU Set Importance into PDU Set Control Information.","secretary_remarks":"Revision of S2-2306196. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19340,"status":"not treated","reservation_date":"2023-12-05 13:37:03","uploaded":"2023-05-12 13:55:00","revisionof":"S2-2306196","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":891.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307174.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307175","title":"Remaining issues to support ECN marking for L4S","source":"Lenovo, [OPPO, Samsung]","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change reference 5.37.3 to 5.37.3.3 Add reference for ECN marking for L4S in RAN Modify the second trigger for QoS monitoring configuration for congestion information into QoS monitoring for congestion information subscribed by AF as described in clause 6.1.3.27.1 of TS 23.503[20].","secretary_remarks":"Revision of S2-2306190. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18840,"status":"not treated","reservation_date":"2023-12-05 13:37:04","uploaded":"2023-05-12 13:55:00","revisionof":"S2-2306190","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4041.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307175.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 4.3.2.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307176","title":"PDU set handling support indicator (Option1)","source":"Lenovo","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The modifications are as follows, For PDU session establishment, modification and inter NG-RAN handover procedure, NG-RAN provides the indicator of supporting PDU set based QoS handling upon receiving PDU set QoS parameters (Option1) For Xn based handover procedure, NG-RAN provides the indicator of supporting PDU set based QoS handling as long as it supports","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19280,"status":"not treated","reservation_date":"2023-12-05 13:37:05","uploaded":"2023-05-12 13:55:00","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4224.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307176.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"4.3.2.1, 4.3.3.2, 4.9.1.2.2, 4.9.1.2.3, 4.9.1.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307177","title":"PDU set handling support indicator(Option2)","source":"Lenovo, Xiaomi","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The modifications are as follows, For PDU session establishment, modification and inter NG-RAN handover procedure, NG-RAN provides the indicator of supporting PDU set based QoS handling upon receiving PDU set QoS parameters (Option2) For Xn based handover procedure, SMF triggers PDU session modification procedure to provide PDU set QoS parameters (if exist) if no indicator of supporting PDU set based QoS handling is received","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19290,"status":"not treated","reservation_date":"2023-12-05 13:37:06","uploaded":"2023-05-12 13:55:00","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4225.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307177.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"4.3.2.1, 4.3.3.2, 4.9.1.2.2, 4.9.1.2.3, 4.9.1.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307178","title":"Non-homogenous support of PDU set based QoS handling in NG-RAN","source":"Lenovo, Meta USA, CATT, Xiaomi,Tencent","contact":"luo haiyan","contact-id":93696,"tdoctype":"CR","for":"Approval","abstract":"Add description on Non-homogenous support of PDU set based QoS handling in NG-RAN","secretary_remarks":"Merged into S2-2308146","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19090,"status":"merged","reservation_date":"2023-12-05 13:37:06","uploaded":"2023-05-12 13:55:00","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4663.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307178.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":" 5.37.5.x(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307203","title":"Non-homogenous support of PDU set based QoS handling in NG-RAN","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on Non-homogenous support of PDU set based QoS handling in NG-RAN Add PDU Set Marking Handling Information (PSMHI) in the PDU Set QoS Parameters","secretary_remarks":"Merged in S2-2307962.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19140,"status":"merged","reservation_date":"2023-12-05 14:25:18","uploaded":"2023-05-12 14:44:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4664.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307203.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":" 5.7.7.1, 5.7.x(new), 5.37.5.x(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307204","title":"[DRAFT] LS on Non-homogenous support for PDU set based QoS handling","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"SA2 kindly asks RAN2 and RAN3 to take the above information into account and feedback if needed","secretary_remarks":"Merged in S2-2307963.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19160,"status":"merged","reservation_date":"2023-12-05 14:25:18","uploaded":"2023-05-12 14:44:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307204.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307215","title":"[DRAFT] LS reply on the Design of RTP Header Extension for PDU set handling","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on the Design of RTP Header Extension for PDU set handling","secretary_remarks":"Response to S2-2306280. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18260,"status":"not treated","reservation_date":"2023-12-05 14:28:16","uploaded":"2023-05-12 16:20:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307215.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307241","title":"Clarification on Protocol Description for multiplexing of multiple media","source":"Samsung","contact":"Jaehyeon Bae","contact-id":72740,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When PDUs composed of multiple media types within a single service data flow are received by UPF, related information is delivered using RTP bundle group information in the Protocol Description.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19300,"status":"not treated","reservation_date":"2023-12-05 15:13:09","uploaded":"2023-05-12 15:16:01","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4665.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307241.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307246","title":"Resolve the EN on End of Data Burst Indication","source":"Samsung","contact":"Jaehyeon Bae","contact-id":72740,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the EN on End of Data Burst Indication.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19680,"status":"not treated","reservation_date":"2023-12-05 15:21:22","uploaded":"2023-05-12 15:24:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4667.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307246.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.8.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307256","title":"Updates to 5GS Packet Delay Variation monitoring and reporting","source":"Samsung","contact":"Jaehyeon Bae","contact-id":72740,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a note that large delay values temporarily occurring due to events such as handover may be excluded when calculating packet delay variation","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19850,"status":"not treated","reservation_date":"2023-12-05 15:48:33","uploaded":"2023-05-12 15:56:38","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4668.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307256.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.37.7.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307261","title":"Procedure to acquire jitter information and provide Protocol Description","source":"[MediaTek], [KDDI], [Futurewei], [China Mobile], [Tencent], [Huawei], Nokia, Nokia Shanghai Bell","contact":"Georgios Gkellas","contact-id":68310,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the N4 Session Level Reporting procedure with Traffic Parameter measurement reporting event triggered during N4 Session Establishment\/Modification procedure. Add periodicity information into Npcf_PolicyAuthorization service. Add end of Data burst detection instruction.","secretary_remarks":"Revision of S2-2306244. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19490,"status":"not treated","reservation_date":"2023-12-05 16:09:34","uploaded":"2023-05-12 16:23:31","revisionof":"S2-2306244","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":3989.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307261.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 4.3.3.2, 4.4.2.2, 5.2.5.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307262","title":"Periodicity measurement and reporting for power saving","source":"[Huawei], [HiSilicon], [vivo], Nokia Nokia Shanghai Bell","contact":"Georgios Gkellas","contact-id":68310,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce policy for support of measurement of DL periodicity associated jitter information and\/or periodicity for power saving. Delete the EN about whether TSCAC can be reused or not. Add Protocol Description in the PCC rule information in 5GC.","secretary_remarks":"Revision of S2-2306202. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19580,"status":"not treated","reservation_date":"2023-12-05 16:09:35","uploaded":"2023-05-12 16:23:31","revisionof":"S2-2306202","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":995.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307262.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.1.3.2.4, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307263","title":"Introducing Protocol Description in input for PCC decisions","source":"Nokia, Nokia Shanghai Bell","contact":"Georgios Gkellas","contact-id":68310,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Protocol Description in input for PCC decisions.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19690,"status":"not treated","reservation_date":"2023-12-05 16:09:36","uploaded":"2023-05-12 16:23:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1074.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307263.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.3.22, 6.2.1.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307264","title":"Media Information to 5G System for trade-off of QoE and power saving requirements","source":"Nokia, Nokia Shanghai Bell","contact":"Georgios Gkellas","contact-id":68310,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify the media information provided by the AF for trade-off of QoE and power saving requirements.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19860,"status":"not treated","reservation_date":"2023-12-05 16:09:37","uploaded":"2023-05-12 16:23:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1075.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307264.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.2.1.2, 6.1.3.27.3.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307268","title":"Periodicity measurement and reporting for power saving","source":"Huawei, HiSilicon[, vivo]","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce policy for support of measurement of DL periodicity associated jitter information and\/or periodicity for power saving. Delete the EN about whether TSCAC can be reused or not.","secretary_remarks":"Revision of S2-2306202. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19530,"status":"not treated","reservation_date":"2023-12-05 16:14:17","uploaded":"2023-05-12 17:09:29","revisionof":"S2-2306202","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":995.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307268.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.1.3.2.4, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307278","title":"Discussion on UE indicating it s L4S capability .","source":"Charter Communications","contact":"Paul Russell","contact-id":95633,"tdoctype":"discussion","for":"Agreement","abstract":"Discusses the benefit of UE explicitly indicating its ability to support L4S feedback transport protocols.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18900,"status":"not treated","reservation_date":"2023-12-05 16:30:23","uploaded":"2023-05-12 19:30:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307278.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307283","title":"Resolve ENs for support of PDU Set handling","source":"[Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson],China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling.","secretary_remarks":"Revision of S2-2306194. Merged into S2-2307960.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19000,"status":"merged","reservation_date":"2023-12-05 16:41:25","uploaded":"2023-05-12 16:43:10","revisionof":"S2-2306194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307283.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.7.1.2, 5.7.7, 5.8.2.4.2, 5.8.5.3, 5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307286","title":"Introduction of UE explicit indication of L4S Feedback Capabilities","source":"Charter Comunications","contact":"Paul Russell","contact-id":95633,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR enables support for explicit indication from UE of its support for L4S feedback during SM signilaling by providing 'L4S Feedback Capabilities' indication as part of the 5GSM Capabilities.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18760,"status":"not treated","reservation_date":"2023-12-05 16:47:40","uploaded":"2023-05-12 19:30:31","revisionof":"","revisedto":"S2-2308752","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4671.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307286.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 5.4.4b, 5.37.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307287","title":"Additional clarification on explicit L4S requested from AF","source":"Meta USA","contact":"Curt Wong","contact-id":96274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides normative texts that for AF requested L4S handling, ECT (1) is not a determining factor.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18770,"status":"not treated","reservation_date":"2023-12-05 16:48:59","uploaded":"2023-05-12 17:28:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4672.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307287.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.37.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307288","title":"Update for network exposure for XR services","source":"[Tencent, Tencent Cloud], Xiaomi,","contact":"Jinhua WU","contact-id":90523,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.37.4, it clarifies the congestion information, data rate informaiton and round trip delay for multiple QoS flows. Regards to the EN, it is proposed to remove it in clause 5.37.4, since it will be solved in TS 23.503. Add the reference for the description about the data rate measurement and exposure.","secretary_remarks":"Revision of S2-2306191. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18780,"status":"not treated","reservation_date":"2023-12-05 16:49:49","uploaded":"2023-05-12 17:32:39","revisionof":"S2-2306191","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4503.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307288.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Clause 5.37.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307289","title":"QoS monitoring enhancement","source":"[vivo, Lenovo, Tencent, Tencent Cloud, China Mobile], Xiaomi","contact":"Jinhua WU","contact-id":90523,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the incomplete examples. Fix the description for QoS monitoring. Correct the QoS monitoring measurement description.","secretary_remarks":"Revision of S2-2306193. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18830,"status":"not treated","reservation_date":"2023-12-05 16:49:50","uploaded":"2023-05-12 17:32:39","revisionof":"S2-2306193","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":967.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307289.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.1.3.21, 6.1.3.5, 6.1.3.18, 6.2.3, 6.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307290","title":"Resolve ENs for support of PDU Set handling","source":"[Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson], Xiaomi","contact":"Jinhua WU","contact-id":90523,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling. Add the description to calrify that in this release of the specification, whether the eligibal discard has enough influence for charging issue is not address.","secretary_remarks":"Revision of S2-2306194. Noted in parallel session","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19010,"status":"noted","reservation_date":"2023-12-05 16:49:50","uploaded":"2023-05-12 17:32:39","revisionof":"S2-2306194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307290.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 5.7.1.2, 5.7.7, 5.8.2.4.2, 5.8.5.3, 5.37.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307291","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"[Tencent, Tencent Cloud, Huawei, HiSilicon], Xiaomi","contact":"Jinhua WU","contact-id":90523,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN Revise the description about the End of Data Burst Indication","secretary_remarks":"Revision of S2-2306201. Postponed","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19410,"status":"postponed","reservation_date":"2023-12-05 16:49:51","uploaded":"2023-05-12 17:32:39","revisionof":"S2-2306201","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307291.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 5.8.5.11, 5.8.5.12, 5.37.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307292","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"[Tencent, Tencent Cloud, Huawei, HiSilicon], Xiaomi","contact":"Jinhua WU","contact-id":90523,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN Add the Time to Next Burst into the 5.37.8 to send to the RAN for the power saving management.","secretary_remarks":"Revision of S2-2306201. Noted in parallel session","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19420,"status":"noted","reservation_date":"2023-12-05 16:49:52","uploaded":"2023-05-12 17:32:39","revisionof":"S2-2306201","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307292.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 5.8.5.11, 5.8.5.12, 5.37.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307293","title":"Update TS23.501 for PDU Set and PDU Handling","source":"[Nokia, Nokia Shanghai Bell], Xiaomi,","contact":"Jinhua WU","contact-id":90523,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates are made as proposed above so one QoS flow is used to support QoS for XR. The QoS flow only performs PDU Set based QoS handling using {PSER, PSDB and PSIHI} and all PDUs must belong to a PDU Set. Update the proposal to clarify the mapping for the PDU(s) unmarked the HE.","secretary_remarks":"Revision of S2-2306239. Merged into S2-2308193","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19060,"status":"merged","reservation_date":"2023-12-05 16:49:52","uploaded":"2023-05-12 17:32:39","revisionof":"S2-2306239","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4527.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307293.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307294","title":"PDU Set Importance spanning across QoS Flows","source":"[Intel], Xiaomi","contact":"Jinhua WU","contact-id":90523,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on the discussion in S2-2305101 it is proposed to add the following NOTE in clause 5.37.5.2 and delete the related Editor s note: In addition to considering the PDU Set Importance within a QoS Flow, NG-RAN could also consider the relative PDU Set Importance across QoS Flows of the same Priority Level when determining which PDU Set needs to be discarded, which is up to implementation and configuration of operator. Clarify how to select and apply them separately, when both parameters applied","secretary_remarks":"Revision of S2-2306243. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19310,"status":"not treated","reservation_date":"2023-12-05 16:49:53","uploaded":"2023-05-12 17:32:39","revisionof":"S2-2306243","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4486.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307294.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307295","title":"[DRAFT] LS Reply on the N6 PDU Set Identification","source":"Xiaomi","contact":"Jinhua WU","contact-id":90523,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 agree that there is benefit of using additional bits to indicate inter-burst time for power saving management. The attached CR has been agreed by SA WG2 to specify the indication of inter burst time.","secretary_remarks":"Response to S2-2306309 Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18370,"status":"not treated","reservation_date":"2023-12-05 16:49:54","uploaded":"2023-05-12 17:32:39","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4,","Cc":"RAN WG2,","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307295.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307296","title":"Introduction of UE explicit indication of L4S Feedback Capabilities","source":"Charter Communications","contact":"Paul Russell","contact-id":95633,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR adds L4S Feedback Capabilities to Npcf_SMPolicyControl_Create service operation.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18890,"status":"not treated","reservation_date":"2023-12-05 16:51:27","uploaded":"2023-05-12 19:30:31","revisionof":"","revisedto":"S2-2308753","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4233.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307296.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.5.4.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307304","title":"KI#4,5 General: PDU set with lonely PDU handling .","source":"Meta USA","contact":"Curt Wong","contact-id":96274,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution suggests the importance factor of lonely PDU in a PDU set is set based on local policy of the UPF to avoid any new impacts to 5GS.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19210,"status":"not treated","reservation_date":"2023-12-05 17:00:55","uploaded":"2023-05-12 17:28:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307304.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307314","title":"Update TS23.501 for PDU Set and PDU Handling","source":"[Nokia, Nokia Shanghai Bell], Meta USA","contact":"Curt Wong","contact-id":96274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates are made as proposed above so one QoS flow is used to support QoS for XR. The QoS flow only performs PDU Set based QoS handling using {PSER, PSDB and PSIHI} and all PDUs must belong to a PDU Set.","secretary_remarks":"Revision of S2-2306239. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19070,"status":"not treated","reservation_date":"2023-12-05 17:11:56","uploaded":"2023-05-12 17:28:23","revisionof":"S2-2306239","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4527.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307314.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307315","title":"Remove EN related to xRM SST","source":"Meta USA, Google","contact":"Curt Wong","contact-id":96274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove EN related to standardize or non-standardized SST for xRM.","secretary_remarks":"Merged into S2-2307909.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18520,"status":"merged","reservation_date":"2023-12-05 17:21:02","uploaded":"2023-05-12 17:28:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4673.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307315.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.5.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307350","title":"Support of ECN Marking Indication for L4S","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AF Session with required QoS includes the AF indication for enabling L4S.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18910,"status":"not treated","reservation_date":"2023-12-05 19:16:50","uploaded":"2023-05-12 21:55:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4240.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307350.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307352","title":"Support of extra traffic characteristics for alternative QoS profile","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow the AF to provide traffic characteristics such as maximum burst size for each alternative service requirement.","secretary_remarks":"Check Affected Clauses! Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18820,"status":"not treated","reservation_date":"2023-12-05 19:16:51","uploaded":"2023-05-12 21:55:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1079.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307352.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307353","title":"Service operation enhancement for PDU Sets","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PDU Set Protocol description parameters to Npcf_PolicyAuthorization_Create service operation and Npcf_PolicyAuthorization_Update service operation","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19320,"status":"not treated","reservation_date":"2023-12-05 19:16:52","uploaded":"2023-05-12 21:55:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"XRM"}],"crnumber":4241.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307353.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307355","title":"[DRAFT] Reply LS on TSCAI for XR","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on TSCAI for XR","secretary_remarks":"Response to S2-2306323. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18170,"status":"not treated","reservation_date":"2023-12-05 19:16:53","uploaded":"2023-05-12 21:55:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307355.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307356","title":"[DRAFT] Reply LS on the N6 PDU Set Identification","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on the N6 PDU Set Identification","secretary_remarks":"Response to S2-2306309. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18320,"status":"not treated","reservation_date":"2023-12-05 19:16:53","uploaded":"2023-05-12 21:55:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307356.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307357","title":"Update TS23.501 EoDB Time to Next Burst","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of EoDB is updated","secretary_remarks":"Postponed","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18310,"status":"postponed","reservation_date":"2023-12-05 19:16:53","uploaded":"2023-05-12 21:55:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4681.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307357.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307370","title":"Update TS23.501 for PDU Set and PDU Handling","source":"[Nokia, Nokia Shanghai Bell], InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates are made as proposed above so one QoS flow is used to support QoS for XR. The QoS flow only performs PDU Set based QoS handling using {PSER, PSDB and PSIHI} and all PDUs must belong to a PDU Set. Rev x: Added that when the SMF determines a QoS Profile for the QoS Flow it can also determine a default PDU Set Importance value. The SMF may then send the default PDU Set Importance value to the UPF and that the default PDU Set Importance value can be assigned to PDUs that do not belong to a PDU Set based on the Protocol Description. If no default PDU Set Importance value is sent to the UPF, then the UPF can determine a value based on implementation.","secretary_remarks":"Revision of S2-2306239. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19080,"status":"not treated","reservation_date":"2023-12-05 19:45:53","uploaded":"2023-05-12 20:08:38","revisionof":"S2-2306239","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4527.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307370.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307371","title":"Adding a Maximum UL PDB and a Maximum DL PDB to the RT latency requirement","source":"InterDigital Inc., Xiaomi","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added that the RT latency requirement may optionally be associated with a Maximum UL Delay Percentage and a Maximum DL Delay Percentage. The PCF can use this information to ensure that it does not assign too much delay to one direction (i.e., UL or DL) of the traffic.","secretary_remarks":"Revision of S2-2305319. Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19830,"status":"not treated","reservation_date":"2023-12-05 19:45:54","uploaded":"2023-05-12 20:08:38","revisionof":"S2-2305319","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4550.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307371.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 5.37.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307372","title":"Adding a Maximum UL PDB and a Maximum DL PDB to the RT latency requirement","source":"InterDigital Inc., Xiaomi","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added that the RT latency requirement may optionally be associated with a Maximum UL Delay Percentage and a Maximum DL Delay Percentage. The PCF can use this information to ensure that it does not assign too much delay to one direction (i.e., UL or DL) of the traffic.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19840,"status":"not treated","reservation_date":"2023-12-05 19:45:55","uploaded":"2023-05-12 20:08:38","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4242.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307372.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.6.6 ","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307373","title":"Update so that the URSP Enforcement Report can include an FQDN","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added text to say that the Traffic Descriptor can be reported by the UE and considered by the SMF during UPF selection.","secretary_remarks":"Check Affected Clauses! Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19750,"status":"not treated","reservation_date":"2023-12-05 19:45:56","uploaded":"2023-05-12 20:00:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4683.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307373.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307374","title":"Update so that the URSP Enforcement Report can include an FQDN","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the URSP Enforcement Reporting feature so that the UE can report the traffic descriptor if it is an FQDN. The reported FQDN can then be considered by the SMF during UPF selection.","secretary_remarks":"Check Affected Clauses! Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19760,"status":"not treated","reservation_date":"2023-12-05 19:45:56","uploaded":"2023-05-12 20:00:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":1080.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307374.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307375","title":"Update so that the URSP Enforcement Report can include an FQDN","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the URSP Enforcement Reporting feature so that the UE can report the traffic descriptor if it is an FQDN. The reported FQDN can then be considered by the SMF during UPF selection.","secretary_remarks":"Check Affected Clauses! Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19770,"status":"not treated","reservation_date":"2023-12-05 19:45:57","uploaded":"2023-05-12 20:00:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4243.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307375.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307376","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"Tencent, Tencent Cloud, [Huawei, HiSilicon] InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN In rev 6, changed N6 jitter measurements to Traffic Parameter measurements. Updated the text in 5.38.8.2 to say procedures for setting up or updating an AF session . Removed the update to the references section since 26.522 was already added to the references section in agreed CR S2-2306194.","secretary_remarks":"Revision of S2-2306201. Revised to S2-2308024, merging S2-2307021, S2-2306616.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19350,"status":"revised","reservation_date":"2023-12-05 19:45:58","uploaded":"2023-05-12 20:19:30","revisionof":"S2-2306201","revisedto":"S2-2308024","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307376.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.8.5.11, 5.8.5.12, 5.37.8.1, 5.37.8.2, 5.37.8.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307377","title":"Procedure to acquire jitter information","source":"MediaTek, [KDDI,] Futurewei, [China Mobile, Tencent, Huawei] InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the N4 Session Level Reporting procedure with Traffic Parameter measurement reporting event triggered during N4 Session Establishment\/Modification procedure. Add periodicity information into Npcf_PolicyAuthorization service. Reason for changes in Rev 7: Updated 4.3.3.2 to replace N6 Jitter Measurements with Traffic Parameter Measurements. Updated 4.3.3.2 to point out that providing the DL periodicity to the UPF is conditional on the SMF having received the information from the PCF. Updated the text in 4.3.3.2 that says that the UPF immediately sends traffic parameters to the SMF in step 2b. Added a clarification that the measurements are only sent if available and that N4 Session Level reporting is initiated. In section 4.4.2.2 added a mention that UPF conditionally reports the UL\/DL periodicity.","secretary_remarks":"Revision of S2-2306244. Revised to S2-2308025, merging S2-2306529.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19430,"status":"revised","reservation_date":"2023-12-05 19:45:59","uploaded":"2023-05-12 20:19:30","revisionof":"S2-2306244","revisedto":"S2-2308025","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":3989.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307377.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 4.3.3.2, 4.4.2.2, 5.2.5.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307378","title":"Jitter for QoS flow with multiple SDFs.","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses how jitter measurements are taken at the UPF and reported to RAN. We propose to report the jitter per XR traffic flow and report the relative time difference (Delta) between the XR traffic flows.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19700,"status":"not treated","reservation_date":"2023-12-05 19:46:00","uploaded":"2023-05-12 20:19:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307378.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307379","title":"Jitter Reports for QoS flow with multiple SDFs","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modify the Session Reporting Rule and Session reporting, for jitter measurements, to be per service data flow, in cases where a QoS flow has multiple service data flows. Configure the UPF to measure and report the Relative Time Difference between service data flows, in cases where a QoS flow has multiple service data flows. Modify the TSC Assistance Information (TSCAI) to include the jitter information per service data flow and to include the Relative Time Difference between service data flows, in cases where a QoS flow has multiple service data flows.","secretary_remarks":"Not Handled","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19710,"status":"not treated","reservation_date":"2023-12-05 19:46:00","uploaded":"2023-05-12 20:20:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4684.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307379.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.8.5.11, 5.8.5.12, 5.37.8.1, 5.37.8.2, 5.27.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307397","title":"Resolution of EN for L4S","source":"[Ericsson], Nokia, Nokia Shanghai Bell, [Samsung, Meta USA]","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides explanation for UE mobility and non-homogeneous L4S support scenario Revision Removal of EN and added normative text to explain mobility impacts (5.37.3.1, 5.37.3.2, 5.37.3.3)","secretary_remarks":"Revision of S2-2306189. Merged into S2-2307910","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18590,"status":"merged","reservation_date":"2023-12-05 21:04:59","uploaded":"2023-05-12 21:55:22","revisionof":"S2-2306189","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4219.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307397.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.37.3.1, 5.37.3.2, 5.37.3.3,6.3.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307399","title":"Update TS23.501 for PDU Set and PDU Handling","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates are made as proposed above so one QoS flow is used to support QoS for XR. The QoS flow only performs PDU Set based QoS handling using {PSER, PSDB and PSIHI} and all PDUs must belong to a PDU Set. Revision: EN is resolved and PDU Set Parmeter determination is clarified","secretary_remarks":"Revision of S2-2306239. Revised to S2-2307961, merging S2-2307172.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19020,"status":"revised","reservation_date":"2023-12-05 21:17:35","uploaded":"2023-05-12 21:55:22","revisionof":"S2-2306239","revisedto":"S2-2307961","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4527.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307399.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307901","title":"[DRAFT] LS Reply on TSCAI for XR","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on TSCAI for XR","secretary_remarks":"Revision of S2-2306389. Revised to S2-2308197.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18120,"status":"revised","reservation_date":"2023-05-30 10:09:10","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306389","revisedto":"S2-2308197","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307901.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307902","title":"Clarification on the usage of TSCAI for XRM services","source":"OPPO, Nokia, Nokia Shanghai Bell","contact":"Boren Guo","contact-id":100775,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that TSCAI can be provided for both GBR and non-GBR QoS flows in case of XRM.","secretary_remarks":"Revision of S2-2306467. Revised to S2-2308185.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19600,"status":"revised","reservation_date":"2023-05-30 10:09:10","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306467","revisedto":"S2-2308185","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4587.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307902.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307903","title":"[DRAFT] LS reply on design of RTP header","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS reply to SA4 on design of RTP header","secretary_remarks":"Revision of S2-2307017. Revised to S2-2308198.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18210,"status":"revised","reservation_date":"2023-05-30 10:09:11","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307017","revisedto":"S2-2308198","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307903.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307904","title":"[DRAFT] Reply LS on the N6 PDU Set Identification","source":"OPPO","contact":"Boren Guo","contact-id":100775,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on the N6 PDU Set Identification","secretary_remarks":"Revision of S2-2306466. Revised to S2-2308199.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18290,"status":"revised","reservation_date":"2023-05-30 10:09:11","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306466","revisedto":"S2-2308199","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG1, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307904.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307905","title":"Exposure of RAN measured data rates","source":"Ericsson, Deutsche Telekom, China Mobile, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR Solves the ENs by removing data rate measurements in RAN. It is based the following answers in LS reply by RAN WG3: The per QoS flow data rate measured by RAN cannot reflect the real bandwidth that can be provided by the network, since it is effected by many factors such as the traffic rate, the air-interface condition and the scheduling strategies. It is not feasible to assume that data rates measured per DRB by the RAN can be converted in data rates per QoS Flow, to be signalled to the CN. The per QoS flow data rate measured by RAN before PDCP is exactly the same as the data rate that the UPF could measure . And finally: RAN WG3 therefore cannot reach consensus on the benefits of a solution based on data rate information on a per QoS Flow basis measured and exposed by NG-RAN via NGAP to SMF or via GTP-U to UPF . Above statements are said to be under assumption that what RAN is expected to provide as data rate information is the measured value of the current bit rate . According to 5.45 and 5.37.4 in TS 23.501 RAN assumption is correct. The above statements reflects then RAN WG3 feedback to the data rate measurements in RAN discussed in SA WG2. Based on RAN WG3 reponse, there are many complexities in specifying RAN measured data rates, and the benefits they bring on top of UPF measured data rates are unclear. The proposal is not to specify RAN data rate measurements. This CR removes that fucntionality and the related ENs from the specifications.","secretary_remarks":"Revision of S2-2306608. Revised to S2-2308188, merging S2-2306870, S2-2307031.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18400,"status":"revised","reservation_date":"2023-05-30 10:09:11","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306608","revisedto":"S2-2308188","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4605.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307905.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307906","title":"QNC Direct Exposure by UPF","source":"Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR Solves the ENs in 5.7.2.4.1, 5.37.4, and 5.45 by removing UPF PSA exposure of QNC information provided by RAN over GTP-U. This CR is based on the LS reply by RAN WG3: As in LS Reply: UP based QNC may not be able to support reporting alternative QoS parameters . Consequently, UPF PSA exposure of QNC information can provide only a subset of the QNC information notification functionality (only the indication is exposed) and therefore it can t serve same use cases as existing mechanism via SMF\/PCF. As in LS Reply: RAN WG3 discussed the UP based QoS Notification Control and reached no consensus on the benefits of this feature . In SA WG2, the UC brought up in discussions has been application data rate adaptation. The benefits mentioned for this use case have been: Improved notification efficiency Improved notification speed But, whether UPF exposure in fact delivers these benefits and whether they provide significant value is unclear: Higher efficiency & speed may not be achieved in all deployments. As in LS reply even in UP based QNC, QNC reporting delay is also possible, e.g. due to the hysteresis before determining the QNC result, and the delay depends on RAN s implementation . Consequently, the actual relevance of any time savings is uncertain. And whether an application can effectively adapt its rate based only on this indication and without further guidance (e.g. QoS that may be available based on alternative QoS) is unclear. As in LS Reply: UP based QNC is on top of GTP-U\/UDP which may cause out of sequence delivery . Probably this can be avoided with guard times and correction logic in UPF. But that is foreseen to delay the notification and complicates the implementation. Based on the above, there are not clear benefits that justify enhancing 5GS Rel-18 with UPF PSA exposure of QNC information provided by RAN over GTP-U. Therefore, this option is not specfied and this CR removes this option and the related ENs from the specifications.","secretary_remarks":"Revision of S2-2306607. Revised to S2-2308189.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18620,"status":"revised","reservation_date":"2023-05-30 10:09:12","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306607","revisedto":"S2-2308189","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4604.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307906.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307907","title":"Update for network exposure for XR services","source":"Tencent, Tencent Cloud, vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.37.4, it clarifies the congestion information, data rate informaiton and round trip delay for multiple QoS flows. Regards to the EN, it is proposed to remove it in clause 5.37.4, since it will be solved in TS 23.503. Remove the measured data rate from RAN.","secretary_remarks":"Revision of S2-2306521. WITHDRAWN","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18720,"status":"withdrawn","reservation_date":"2023-05-30 10:09:13","uploaded":null,"revisionof":"S2-2306521","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4503.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307908","title":"[DRAFT] Reply LS on RAN information exposure for XRM","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on RAN information exposure for XRM","secretary_remarks":"Revision of S2-2306493. Revised to S2-2308200.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18450,"status":"revised","reservation_date":"2023-05-30 10:09:14","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306493","revisedto":"S2-2308200","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307908.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307909","title":"Introduction of a new standard SST for Extended Reality and Media Services","source":"China Mobile, ZTE, Huawei, KDDI, Verizon, NTT Docomo, China Unicom, China Telecom","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing a new standardized SST for high data rate and low latency communication, and removing the EN about this.","secretary_remarks":"Revision of S2-2306463, merging S2-2307315. Revised to S2-2308186.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18500,"status":"revised","reservation_date":"2023-05-30 10:09:14","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306463","revisedto":"S2-2308186","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4493.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307909.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307910","title":"Resolution of EN for L4S","source":"Ericsson, [Nokia], [Nokia Shanghai Bell], [Samsung], [Meta USA]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides explanation for UE mobility and non-homogeneous L4S support scenario. Rev3 (SA WG2#157): If ECN marking for L4S is not supported e.g. due to inter-NG-RAN handover or PSA UPF relocation, if enabled by the QoS Monitoring policy information from PCF, SMF may activate QoS Monitoring of congestion information (see clause 5.45). AF can request QoS Monitoring (Congestion information) and ECN marking for L4S and if so, SMF activates QoS Monitoring if ECN marking for L4S is not available (that is, either ECN marking for L4S or Congestion information monitoring is active at a time on a QoS Flow).","secretary_remarks":"Revision of S2-2306604, merging S2-2306991, S2-2307397, S2-2306418,. Revised to S2-2308187, merging S2-2306525.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18540,"status":"revised","reservation_date":"2023-05-30 10:09:15","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306604","revisedto":"S2-2308187","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4219.0,"crrevision":5.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307910.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307958","title":"QoS Monitoring and 5GS information exposure update","source":"Vivo, CATT, Huawei, China Mobile, Tencent, Tencent Cloud","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify QoS monitoring general description Clarify Reported congestion information","secretary_remarks":"Revision of S2-2306522. Revised to S2-2308190.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18650,"status":"revised","reservation_date":"2023-05-30 10:09:52","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2306522","revisedto":"S2-2308190","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4294.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307958.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307959","title":"QoS monitoring enhancement","source":"[vivo], [Lenovo], [Tencent], [Tencent Cloud], [China Mobile], Ericsson, Xiaomi","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the incomplete examples. Fix the description for QoS monitoring. Rev.3 (SA WG2#157) Add RTT over Two QoS service data flows: An AF which provides different QoS requirements on each direction (UL and DL) of the XRM service data flow can subscribe to new Round-trip delay over two QoS flows specified in 5.37.4 in TS 23.501.. A new PCF event is specified with that purpose. PCF determines the QoS Monitoring Policy for the PCC Rule for each service data flow direction based on the AF request, it calculates the RTT measurements based on reports received from SMF, and it reports the measurement to AF","secretary_remarks":"Revision of S2-2306610. Revised to S2-2308191, merging S2-2306524.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18680,"status":"revised","reservation_date":"2023-05-30 10:09:52","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2306610","revisedto":"S2-2308191","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":967.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307959.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307960","title":"Resolve ENs for support of PDU Set handling","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson, CATT, China Mobile","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling.","secretary_remarks":"Revision of S2-2307014, merging S2-2306629, S2-2307283, S2-2306526. Revised to S2-2308192, merging S2-2306470, S2-2306473, S2-2306614.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18930,"status":"revised","reservation_date":"2023-05-30 10:09:53","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2307014","revisedto":"S2-2308192","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307960.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307961","title":"Update TS23.501 for PDU Set and PDU Handling","source":"Nokia, Nokia Shanghai Bell, Meta, Mediatek, Interdigital, AT&T, China Mobile, Ericsson, Huawei, HiSilicon, Xiaomi, Apple","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates are made as proposed above so one QoS flow is used to support QoS for XR. The QoS flow only performs PDU Set based QoS handling using {PSER, PSDB and PSIHI} and all PDUs must belong to a PDU Set. Revision: EN is resolved and PDU Set Parmeter determination is clarified May 24, 2023 Show of hands outcome: No support for PDU Set with more than one unmarked PDUs. Importance value is configured in the UPF for such PDUs.","secretary_remarks":"Revision of S2-2307399. Revised to S2-2308193, merging S2-2307293, S2-2307172.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19030,"status":"revised","reservation_date":"2023-05-30 10:09:54","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2307399","revisedto":"S2-2308193","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4527.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307961.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307962","title":"PDU Set QoS handling: non-homogenous support (Alternative 2)","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added description on non-homogenous support of PDU set based QoS handling in NG-RAN Clarified that PDU Set QoS handling is enabled by sending at least one of the PDU Set QoS Parameters to the NG-RAN.","secretary_remarks":"Revision of S2-2306688, merging S2-2307203. Revised to S2-2308194.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19110,"status":"revised","reservation_date":"2023-05-30 10:09:55","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2306688","revisedto":"S2-2308194","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4611.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307962.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307963","title":"[DRAFT] Non-homogeneous deployment of PDU Set based QoS handling","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG4. CC: RAN WG2. Attachments: S2-2306687 (CR 04610 vs. TS 23.501)","secretary_remarks":"Revision of S2-2306689, merging S2-2307204. Revised to S2-2308249.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19180,"status":"revised","reservation_date":"2023-05-30 10:09:56","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2306689","revisedto":"S2-2308249","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307963.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308024","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"Tencent, Tencent Cloud, Huawei, HiSilicon, InterDigital Inc., Ericsson","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN In Rev 6, changed N6 jitter measurements to Traffic Parameter measurements. Updated the text in 5.38.8.2 to say procedures for setting up or updating an AF session . Removed the update to the references section since 26.522 was already added to the references section in agreed CR S2-2306194. Simplified NOTE 1 and 2 to clarify how the UPF derives the N6 jitter and periodicity when not provided by AF is implementation dependent. Made clarifications on what N6 jitter measures. Add End of Data Burst indication to the QER and remove it from the FAR. The request to perform End of Data Burst marking is included in the QER, since that s what contains instructions related to the QoS enforcement of the traffic, instead of forwarding actions in the FAR and the End of Data Bursts are to be detected at QoS Flow level. See C4-231525 for reference.","secretary_remarks":"Revision of S2-2307376, merging S2-2307021, s2-2306616. Revised to S2-2308195.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19360,"status":"revised","reservation_date":"2023-05-30 10:10:15","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2307376","revisedto":"S2-2308195","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308024.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308025","title":"Procedure to acquire jitter information","source":"MediaTek, [KDDI,] Futurewei, [China Mobile, Tencent, Huawei] InterDigital Inc., vivo, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the N4 Session Level Reporting procedure with Traffic Parameter measurement reporting event triggered during N4 Session Establishment\/Modification procedure. Add periodicity information into Npcf_PolicyAuthorization service. Reason for changes in Rev 7: Updated 4.3.3.2 to replace N6 Jitter Measurements with Traffic Parameter Measurements. Updated 4.3.3.2 to point out that providing the DL periodicity to the UPF is conditional on the SMF having received the information from the PCF. Updated the text in 4.3.3.2 that says that the UPF immediately sends traffic parameters to the SMF in step 2b. Added a clarification that the measurements are only sent if available and that N4 Session Level reporting is initiated. In section 4.4.2.2 added a mention that UPF conditionally reports the UL\/DL periodicity. Added that the SMF instructs the UPF to perform end of data burst detection and that the UPF performs end of data burst detection.","secretary_remarks":"Revision of S2-2307377, merging S2-2306529. Revised to S2-2308196.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19440,"status":"revised","reservation_date":"2023-05-30 10:10:16","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2307377","revisedto":"S2-2308196","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":3989.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308025.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308026","title":"PCF provides the Periodicity to SMF via PCC rules for resolving the EN for KI#8","source":"China Mobile, vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PCF should send the Periodicity information received from the AF to SMF via PCC rules. Clarify the TSCAI parameters from CN to NG-RAN.","secretary_remarks":"Revision of S2-2306528. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19510,"status":"agreed","reservation_date":"2023-05-30 10:10:17","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2306528","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4529.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308026.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308185","title":"Clarification on the usage of TSCAI for XRM services","source":"OPPO, Nokia, Nokia Shanghai Bell","contact":"Boren Guo","contact-id":100775,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that TSCAI can be provided for both GBR and non-GBR QoS flows in case of XRM.","secretary_remarks":"Revision of S2-2307902. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19610,"status":"agreed","reservation_date":"2023-05-30 10:12:16","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307902","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4587.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308185.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308186","title":"Introduction of a new standard SST for Extended Reality and Media Services","source":"China Mobile, ZTE, Huawei, KDDI, Verizon, NTT DOCOMO, China Unicom, China Telecom","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing a new standardized SST for high data rate and low latency communication, and removing the EN about this.","secretary_remarks":"Revision of S2-2307909. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18510,"status":"agreed","reservation_date":"2023-05-30 10:12:17","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307909","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4493.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308186.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308187","title":"Resolution of EN for L4S","source":"Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Meta USA","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides explanation for UE mobility and non-homogeneous L4S support scenario. Rev3 (SA WG2#157): If ECN marking for L4S is not supported e.g. due to inter-NG-RAN handover or PSA UPF relocation, if enabled by the QoS Monitoring policy information from PCF, SMF may activate QoS Monitoring of congestion information (see clause 5.45). AF can request QoS Monitoring (Congestion information) and ECN marking for L4S and if so, SMF activates QoS Monitoring if ECN marking for L4S is not available (that is, either ECN marking for L4S or Congestion information monitoring is active at a time on a QoS Flow).","secretary_remarks":"Revision of S2-2307910, merging S2-2306525. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18550,"status":"agreed","reservation_date":"2023-05-30 10:12:17","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307910","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4219.0,"crrevision":6.0,"crcategory":"C","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308187.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308188","title":"Exposure of RAN measured data rates","source":"Ericsson, Deutsche Telekom, China Mobile, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, CATT","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR Solves the ENs by removing data rate measurements in RAN. It is based the following answers in LS reply by RAN WG3: The per QoS flow data rate measured by RAN cannot reflect the real bandwidth that can be provided by the network, since it is effected by many factors such as the traffic rate, the air-interface condition and the scheduling strategies. It is not feasible to assume that data rates measured per DRB by the RAN can be converted in data rates per QoS Flow, to be signalled to the CN. The per QoS flow data rate measured by RAN before PDCP is exactly the same as the data rate that the UPF could measure . And finally: RAN WG3 therefore cannot reach consensus on the benefits of a solution based on data rate information on a per QoS Flow basis measured and exposed by NG-RAN via NGAP to SMF or via GTP-U to UPF . Above statements are said to be under assumption that what RAN is expected to provide as data rate information is the measured value of the current bit rate . According to 5.45 and 5.37.4 in TS 23.501 RAN assumption is correct. The above statements reflects then RAN WG3 feedback to the data rate measurements in RAN discussed in SA WG2. Based on RAN WG3 reponse, there are many complexities in specifying RAN measured data rates, and the benefits they bring on top of UPF measured data rates are unclear. The proposal is not to specify RAN data rate measurements. This CR removes that fucntionality and the related ENs from the specifications.","secretary_remarks":"Revision of S2-2307905, merging S2-2306870, S2-2307031. Agreed in parallel session This replaces S2-2306188 agreed at S2#156-e. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18410,"status":"agreed","reservation_date":"2023-05-30 10:12:18","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307905","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4605.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-230498","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308188.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308189","title":"QNC Direct Exposure by UPF","source":"Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR Solves the ENs in 5.7.2.4.1, 5.37.4, and 5.45 by removing UPF PSA exposure of QNC information provided by RAN over GTP-U. This CR is based on the LS reply by RAN WG3: As in LS Reply: UP based QNC may not be able to support reporting alternative QoS parameters . Consequently, UPF PSA exposure of QNC information can provide only a subset of the QNC information notification functionality (only the indication is exposed) and therefore it can t serve same use cases as existing mechanism via SMF\/PCF. As in LS Reply: RAN WG3 discussed the UP based QoS Notification Control and reached no consensus on the benefits of this feature . In SA WG2, the UC brought up in discussions has been application data rate adaptation. The benefits mentioned for this use case have been: Improved notification efficiency Improved notification speed But, whether UPF exposure in fact delivers these benefits and whether they provide significant value is unclear: Higher efficiency & speed may not be achieved in all deployments. As in LS reply even in UP based QNC, QNC reporting delay is also possible, e.g. due to the hysteresis before determining the QNC result, and the delay depends on RAN s implementation . Consequently, the actual relevance of any time savings is uncertain. And whether an application can effectively adapt its rate based only on this indication and without further guidance (e.g. QoS that may be available based on alternative QoS) is unclear. As in LS Reply: UP based QNC is on top of GTP-U\/UDP which may cause out of sequence delivery . Probably this can be avoided with guard times and correction logic in UPF. But that is foreseen to delay the notification and complicates the implementation. Based on the above, there are not clear benefits that justify enhancing 5GS Rel-18 with UPF PSA exposure of QNC information provided by RAN over GTP-U. Therefore, this option is not specfied and this CR removes this option and the related ENs from the specifications.","secretary_remarks":"Revision of S2-2307906. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18630,"status":"agreed","reservation_date":"2023-05-30 10:12:19","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307906","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4604.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308189.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308190","title":"QoS Monitoring and 5GS information exposure update","source":"Vivo, CATT, Huawei, China Mobile, Tencent, Tencent Cloud","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify QoS monitoring description","secretary_remarks":"Revision of S2-2307958. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18660,"status":"agreed","reservation_date":"2023-05-30 10:12:20","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307958","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4294.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308190.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308191","title":"QoS monitoring enhancement","source":"Vivo, Lenovo, Tencent, Tencent Cloud, China Mobile, Ericsson, Xiaomi","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the incomplete examples. Fix the description for QoS monitoring. Rev.3 (SA WG2#157) Add RTT over Two service data flows. A new PCF event is specified with that purpose. PCF determines the QoS Monitoring Policy for the PCC Rule for each service data flow direction based on the AF request, it calculates the RTT measurements based on reports received from SMF, and it reports the measurement to AF","secretary_remarks":"Revision of S2-2307959, merging S2-2306524. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18690,"status":"agreed","reservation_date":"2023-05-30 10:12:21","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307959","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":967.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"SP-230498","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308191.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308192","title":"Resolve ENs for support of PDU Set handling","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, MediaTek, Tencent, Tencent Cloud, Qualcomm Incorporated, vivo, Ericsson, CATT, China Mobile, Meta USA.","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve the existing ENs for support of PDU Set handling.","secretary_remarks":"Revision of S2-2307960, merging S2-2306470, S2-2306473, S2-2306614. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18940,"status":"agreed","reservation_date":"2023-05-30 10:12:21","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307960","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4383.0,"crrevision":11.0,"crcategory":"B","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308192.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308193","title":"Update TS23.501 for PDU Set and PDU Handling","source":"Nokia, Nokia Shanghai Bell, Meta, Mediatek, Interdigital, AT&T, China Mobile, Ericsson, Huawei, HiSilicon, Xiaomi, Apple, Lenovo, ZTE","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates are made as proposed above so one QoS flow is used to support QoS for XR. The QoS flow only performs PDU Set based QoS handling using {PSER, PSDB and PSIHI} and all PDUs must belong to a PDU Set. Revision: EN is resolved and PDU Set Parmeter determination is clarified May 24, 2023 Show of hands outcome: No support for PDU Set with more than one unmarked PDUs. Importance value is configured in the UPF for such PDUs.","secretary_remarks":"Revision of S2-2307961, merging S2-2307293, S2-2307172. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19040,"status":"agreed","reservation_date":"2023-05-30 10:12:22","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307961","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4527.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308193.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308194","title":"PDU Set QoS handling: non-homogenous support (Alternative 2)","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added description on non-homogenous support of PDU set based QoS handling in NG-RAN Clarified that PDU Set QoS handling is enabled by sending at least one of the PDU Set QoS Parameters to the NG-RAN.","secretary_remarks":"Revision of S2-2307962. Revised to S2-2308246.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19120,"status":"revised","reservation_date":"2023-05-30 10:12:23","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307962","revisedto":"S2-2308246","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4611.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308194.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308195","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"Tencent, Tencent Cloud, Huawei, HiSilicon, InterDigital Inc., Ericsson","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN In Rev 8, changed N6 jitter measurements to Traffic Parameter measurements. Updated the text in 5.38.8.2 to say procedures for setting up or updating an AF session . Removed the update to the references section since 26.522 was already added to the references section in agreed CR S2-2306194. Simplified NOTE 1 and 2 to clarify how the UPF derives the N6 jitter and periodicity when not provided by AF is implementation dependent. Made clarifications on what N6 jitter measures. Add End of Data Burst indication to the QER and remove it from the FAR. The request to perform End of Data Burst marking is included in the QER, since that s what contains instructions related to the QoS enforcement of the traffic, instead of forwarding actions in the FAR and the End of Data Bursts are to be detected at QoS Flow level. See C4-231525 for reference.","secretary_remarks":"Revision of S2-2308024. Revised to S2-2308247.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19370,"status":"revised","reservation_date":"2023-05-30 10:12:24","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2308024","revisedto":"S2-2308247","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308195.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308196","title":"Procedure to acquire jitter information","source":"MediaTek, KDDI, Futurewei, China Mobile, Tencent, Huawei InterDigital Inc., vivo, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the N4 Session Level Reporting procedure with Traffic Parameter measurement reporting event triggered during N4 Session Establishment\/Modification procedure. Add periodicity information into Npcf_PolicyAuthorization service. Reason for changes in Rev 9: Updated 4.3.3.2 to replace N6 Jitter Measurements with Traffic Parameter Measurements. Updated 4.3.3.2 to point out that providing the DL periodicity to the UPF is conditional on the SMF having received the information from the PCF. Updated the text in 4.3.3.2 that says that the UPF immediately sends traffic parameters to the SMF in step 2b. Added a clarification that the measurements are only sent if available and that N4 Session Level reporting is initiated. In section 4.4.2.2 added a mention that UPF conditionally reports the UL\/DL periodicity. Added that the SMF instructs the UPF to perform end of data burst detection and that the UPF performs end of data burst detection.","secretary_remarks":"Revision of S2-2308025. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19450,"status":"agreed","reservation_date":"2023-05-30 10:12:25","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2308025","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":3989.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"SP-230498","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308196.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308197","title":"LS reply on TSCAI for XR","source":"SA WG2","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3","secretary_remarks":"Revision of S2-2307901. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18130,"status":"approved","reservation_date":"2023-05-30 10:12:27","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307901","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306323","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308197.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308198","title":"[DRAFT] LS Reply on Design of RTP Header Extension for PDU Set handling","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS reply to SA4 on design of RTP header","secretary_remarks":"Revision of S2-2307903. Revised to S2-2308248.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18220,"status":"revised","reservation_date":"2023-05-30 10:12:27","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307903","revisedto":"S2-2308248","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308198.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308199","title":"Reply LS on the N6 PDU Set Identification","source":"SA WG2","contact":"Boren Guo","contact-id":100775,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: RAN WG1, RAN WG2, RAN WG3","secretary_remarks":"Revision of S2-2307904. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18300,"status":"approved","reservation_date":"2023-05-30 10:12:27","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307904","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306309","lsto":"SA WG4","Cc":"RAN WG1, RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308199.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308200","title":"Reply LS on RAN information exposure for XRM","source":"SA WG2","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Revision of S2-2307908. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18460,"status":"approved","reservation_date":"2023-05-30 10:12:28","uploaded":"2023-05-30 16:41:17","revisionof":"S2-2307908","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306312","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308200.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308246","title":"PDU Set QoS handling: non-homogenous support (Alternative 2)","source":"Qualcomm Incorporated, Google, ZTE, Lenovo, Meta","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added description on non-homogenous support of PDU set based QoS handling in NG-RAN Clarified that PDU Set QoS handling is enabled by sending at least one of the PDU Set QoS Parameters to the NG-RAN.","secretary_remarks":"Revision of S2-2308194. This CR was agreed","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19130,"status":"agreed","reservation_date":"2023-05-30 10:13:10","uploaded":"2023-05-30 16:41:18","revisionof":"S2-2308194","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4611.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-230498","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308246.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308247","title":"EN resolving for KI#8 Except TSCAC and clarifications on AF inputs","source":"Tencent, Tencent Cloud, Huawei, HiSilicon, InterDigital Inc., Ericsson","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing an EN about UPF reporting proceudre to SMF and make corresponding changes in 5.8.5 and 5.37.8 Resolve the EN and add reference Some editorial changes to N6 jitter\/jitter, NG RAN In Rev 8, changed N6 jitter measurements to Traffic Parameter measurements. Updated the text in 5.38.8.2 to say procedures for setting up or updating an AF session . Removed the update to the references section since 26.522 was already added to the references section in agreed CR S2-2306194. Simplified NOTE 1 and 2 to clarify how the UPF derives the N6 jitter and periodicity when not provided by AF is implementation dependent. Made clarifications on what N6 jitter measures. Add End of Data Burst indication to the QER and remove it from the FAR. The request to perform End of Data Burst marking is included in the QER, since that s what contains instructions related to the QoS enforcement of the traffic, instead of forwarding actions in the FAR and the End of Data Bursts are to be detected at QoS Flow level. See C4-231525 for reference.","secretary_remarks":"Revision of S2-2308195. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19380,"status":"agreed","reservation_date":"2023-05-30 10:13:11","uploaded":"2023-05-30 16:41:18","revisionof":"S2-2308195","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"XRM"}],"crnumber":4322.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"SP-230497","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308247.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308248","title":"LS Reply on Design of RTP Header Extension for PDU Set handling","source":"SA WG2","contact":"Hui Ni","contact-id":79738,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4, RAN WG3. CC: RAN WG2. Attachments: S2-2308193","secretary_remarks":"Revision of S2-2308198. Agreed in parallel session. Block approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":18230,"status":"approved","reservation_date":"2023-05-30 10:13:13","uploaded":"2023-05-30 16:41:18","revisionof":"S2-2308198","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306280","lsto":"SA WG4, RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308248.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308249","title":"[DRAFT] Non-homogeneous deployment of PDU Set based QoS handling","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG4. CC: RAN WG2. Attachments: S2-2306687 (CR 04610 vs. TS 23.501)","secretary_remarks":"Revision of S2-2307963. Revised to S2-2308252.","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19190,"status":"revised","reservation_date":"2023-05-30 10:13:14","uploaded":"2023-05-30 16:41:18","revisionof":"S2-2307963","revisedto":"S2-2308252","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308249.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2308252","title":"Non-homogeneous deployment of PDU Set based handling","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG4. CC: RAN WG2. Attachments: S2-2308246 (CR 04611 vs. TS 23.501)","secretary_remarks":"Revision of S2-2308249. This LS OUT was approved","agenda_item_sort_order":96,"ainumber":"9.12.2","ainame":"XR (Extended Reality) and media services (XRM)","tdoc_agenda_sort_order":19200,"status":"approved","reservation_date":"2023-05-30 10:13:15","uploaded":"2023-05-30 16:41:18","revisionof":"S2-2308249","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG4","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2308252.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]