3GPP TSG-RAN WG2 Meeting #130	R2-2503368
St Julian’s, Malta, 19-23 May 2025	

Agenda item:	8.7.6
Source:	Qualcomm Incorporated, MediaTek Inc.
Title:	Discussion on XR rate control
WID/SID:	NR_XR_Ph3-Core
Document for:	Discussion and decision

Conclusion
Based on the above analysis, we respectively request RAN2 to discuss and agree to the following proposals:
Proposal 1.	The maximum number of QoS flows subject to rate control is a UE capability, whose range is 1~64. 
Proposal 2. 	[MAC-05] The Rate Control MAC CE (both rate indication and rate query) can include bit rates for multiple QoS flows. 
Proposal 3.	[MAC-04] Use an identifier configured by RRC, which is shorter than QFI, to identify QoS flows in the Rate Control MAC CE. 
Proposal 4.	[MAC-06] The Rate Control MAC CE includes a length field. 
Proposal 5.	[RRC-01] Rate query prohibit timer is configured per QoS flow.
Proposal 6. 	[MAC-08] Multiple rate queries (for different QoS flows) can be pending at the same time. 
Proposal 7.	[MAC-08] A pending rate query is canceled after a corresponding rate query is sent in a Rate Control MAC CE.
Proposal 8. 	[MAC-08] To keep the design simple, a Rate Control MAC CE is sent only if it can accommodate all pending rate queries. No truncation is supported. 
Proposal 9. 	[MAC-09] UE considers the indicated bit rate in a Rate Control MAC CE received in any cell group as the total bit rate available to the application. 

3GPP TSG-RAN WG2 Meeting #130                                                        R2-2503429
St.Julians, Malta, May 19th – 23rd, 2025

Source:	CATT
Title:	Discussion on XR Rate Control
Agenda Item:	8.7.6
Document for:	Discussion and Decision

Conclusion
According to the analysis in section 2, it is proposed:
Proposal 1: (MAC-04) RAN2 uses the PDU session ID and QoS Flow ID to indicate per QoS flow level recommended bit rate in Rel-19 as baseline.
Proposal 2: (MAC-04) RAN2 further discusses whether any optimize for the overhead is needed.
Proposal 3: (MAC-05) RAN2 follows the legacy design not to introduce the flexibility MAC CE format in Rel-19 XR.
Proposal 4: (MAC-07) RAN2 adapts 3 bytes format for the new Recommended bit rate MAC CE for Rel-19 XR, including 14 bits QoS flow indication, 1 bit direction, 8 bits rate index and 1 reservation.
Proposal 5: (MAC-09) RAN2 confirms no additional specification impact to support the UE behaviour on handling multiple XR rate control MAC CEs in CA/DC scenario from RAN2 perspective.

3GPP TSG-RAN WG2 Meeting #130	R2-2503440
St Julian’s, Malta, 19 – 23 May 2025

Agenda item:		8.7.6
Source:	Xiaomi
Title:	XR rate control
Document for:		Discussion and Decision

Conclusion
In this contribution, we discuss open issues of XR rate control, and propose the following:
Proposal 1: (MAC-11) RAN2 confirm that same design for UL rate control design is applicable to DL data transmission, and inform SA2/SA4/RAN3 about the agreement.	
Proposal 2: (MAC-09) In DC configuration, UL rate control MAC CE is only applicable to QoS flows served in the MAC entity. For split bearer, the MAC entity indicates the aggregated bit rate provided by MN and SN to upper layers.
Proposal 3: (MAC-04) QoS flow is indicated with LCID + QFI.
Proposal 4: (MAC-05) Rate Control MAC CE includes bit rate for single QoS flow.
Proposal 5: (MAC-06) Rate Control MAC CE includes the following fields: LCID, QFI, UL/DL, Bit Rate.
Proposal 6: (RRC-1) The granularity of bit rate query prohibit timer is QoS flow.
Proposal 7: (MAC-08, MAC-10) Legacy Recommended bit rate query procedure (i.e. triggering, multiplexing, cancellation, prohibit timer) is used as baseline for bit rate query, with the change of logical channel to QoS flow.

3GPP TSG-RAN WG2 Meeting #130											R2-2503512
St. Julians, Malta, May 19th – 23rd, 2025
Agenda Item:	8.7.6
Source: 	Sharp
Title:  	Open Issues on Rate Control
Document for: 	Discussion

Conclusions
Based on the discussion above, RAN2 is requested to agree the following proposals:
QFI without DRB ID is included in Rel-19 Rate Control MAC CE.
Rel-19 Rate Control MAC CE can be used for DL as well as UL.
Bit rate query is based on QoS flow level and configured in LogicalChannelConfig.
Index 0 is used for indicating that no new recommendation on bit rate is given, same as Rel-15.
The Rate Control MAC CE includes multiple QoS flows.

3GPP TSG RAN WG2 Meeting #130                                                            R2-2503523
St Julian's, Malta, May 19th - 23rd, 2025
Agenda item:	8.7.6
Source:	Ofinno
Title:	XR Rate Control
Document for:	Discussion and decision

Conclusion
Based on the analysis above, we have made the following proposals:
Proposal 1	[MAC-12] RAN2 to discuss and down-select one of the following options to indicate that the bit rate query is for an available bit rate with no desired bit rate:
Option 1: Use a specific index (e.g., index 0 or a reserved index) in the bit rate table:
The specific index (e.g., index 0 or reserved index) in the bit rate table specifically to indicate a query for an available bit rate with no desired bit rate.
Option 2: Introduce a single-bit field/flag in the Rate Control MAC CE:
The single-bit field/flag can indicate whether the UE queries an available bit rate with no desired bit rate or queries an available bit rate by indicating a desired bit rate
Option 3: Introduce an additional Rate Control MAC CE format which does not include bit rate field.
Proposal 2	[MAC-08] For the triggered bit rate query, when MAC entity has allocated UL resources for a new transmission:
(1) If the allocated UL resources can accommodate the Rate Control MAC CE (plus its subheader as a result of LCP), the MAC entity generates the Rate Control MAC CE;
(2) If the allocated UL resources cannot accommodate the Rate Control MAC CE (plus its subheader as a result of LCP), the MAC entity triggers a Scheduling Request (SR) for the Rate Control MAC CE.
Proposal 3	[MAC-08] A triggered bit rate query is cancelled when:
(1) MAC entity has UL resources allocated for new transmission and the allocated UL resources can accommodate the Rate Control MAC CE (plus its subheader as a result of LCP); 
(2) MAC Reset.
Proposal 4	[MAC-05] A single Rate Control MAC CE can indicate one or multiple QoS flows.
Proposal 5	[MAC-07] If the Proposal 4 is agreed, define a bitmap to identify QoS flows(s) within the Rate Control MAC CE. FFS on the size of the bitmap.

3GPP TSG-RAN WG2 Meeting #130	R2-2503558
St.Julians, Malta, May 19th – 23th, 2025

Agenda item:	8.7.6
Source: 	Fujitsu
Title: 	Discussions on XR rate control
Document for:	Discussion and decision

Conclusion
In this contribution, we have discussed the details of the rate control MAC CE from gNB to UE, the potential format of the rate control MAC CE and whether to support the rate query MAC CE. We have the following proposals: 
Proposal 1: The bit rate table has 256 code points with exponential distribution of around 2.4% granularity. 
Proposal 2: Multiplier is not needed. 
Proposal 3: The rate control MAC CE indicates the rate control information of multiple DRBs/QoS flows. 
Proposal 4: In the rate control MAC CE, the index (indices) of the QoS flows is included, e.g., via a bitmap. 
Proposal 5: The index in the rate control MAC CE can be configured by network based on the QoS flow ID and the PDU session ID, or the mapping between the index in the rate control MAC CE and the QoS flow ID and the PDU session ID can be pre-defined. 
Proposal 6: After the generation or transmission of the rate query MAC CE, the triggered rate query is cancelled. 
Proposal 7: The upper layer can cancel the pending rate query. 

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130	R2-2503702
St. Julians, Malta, 19 – 23 May 2025	


Agenda item:	8.7.6
Source:	Apple
Title:	Views on Remaining Issues of XR Uplink Rate Control
WID/SID:	NR_XR_Ph3-Core
Document for:	Discussion / Decision

Conclusions
This paper provides some of our views about UL rate control for Rel-19 XR. We have the following proposals:
Proposal 1: The rate control MAC CE for Rel-19 XR can include the following fields:
A LCID corresponding to the DRB where this MAC CE is applicable
A bitmap indicating the concerned QoS flows mapped to the applicable DRB
A list of bit rates respectively applicable to the concerned QoS flows.

Proposal 2: RAN2 can confirm that rate query prohibit timer can be configured per QoS flow.

Proposal 3: RAN2 can confirm the following UE behaviours related to rate query prohibit timer:
The UE starts the prohibit timer for a QoS flow when a rate query MAC CE includes the query of this QoS flow.
The UE does not transmit another rate query MAC CE that includes the query of this QoS flow until the associated prohibit timer expires.

3GPP TSG-RAN WG2 Meeting #130							R2-2503796
Malta, MT, 19th – 23th May, 2025
Agenda Item:	8.7.6
Source:	China Telecom
Title:	Discussion on Remaining Issues of XR Rate Control
Document for:	Discussion
1	

Conclusion
Based on the above analysis, we have the following proposals:
Proposal 1: RAN2 to agree the per flow indication in MAC CE.
Proposal 2: To reduce overhead in the MAC CE, the QoS Flow ID can be mapped to a shorter ID configured by the RRC.
4	

3GPP TSG-RAN WG2 Meeting #130			     R2-2503831
St. Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	8.7.6 (NR_XR_Ph3-Core)
Source: 	LG Electronics Inc.
Title:         	Remaining open issues on rate control signaling for XR
Document for: 	Discussion and Decision

Conclusion
Based on the above discussions, we present the following observations and proposals:
Proposal 1. DRB ID + QoS flow ID is used to indicate a QoS flow in the rate control MAC CE.
Proposal 2. The Rate Control MAC CE can include information for multiple QoS flows.
Proposal 3. The prohibit timer is configured per QoS flow. 
Proposal 4. When a UL rate query for a QoS flow is triggered and not cancelled, 
if the prohibit timer for the QoS flow is configured and it is not running and the allocated UL resources can accommodate a rate control MAC CE plus its subheader as a result of LCP as defined in clause 5.4.3.1, the MAC entity shall
instruct the Multiplexing and Assembly procedure to generate the rate control MAC CE for the QoS flow
start the prohibit timer for the QoS flow included in the rate control MAC CE
cancel UL rate queries for the QoS flows included in the rate control MAC CE
Proposal 5. The rate control MAC CE for bit rate query has same priority as MAC CE for Recommended bit rate query for the LCP procedure. 
Proposal 6. The index 0 in the new bit rate table does not have a special meaning, i.e., indicate 0 bit rate or make it reserved bit.
Proposal 7. The available bit rate query is not supported and the bit rate query from the UE always includes a desired bit rate.
Proposal 8. No special handling for UL split bearer is needed for rate control MAC CE.

3GPP TSG-RAN WG2 Meeting #130	R2-2503836
Malta, 19 – 23 May, 2025	


Agenda item:	8.7.6
Source:	InterDigital
Title:	Discussion on UL congestion signaling
WID/SID:	NR_XR_Ph3-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
This document has made the following observations and proposals:
Proposal 1: Use the LCID + QFI (6 + 6 bits) combination to identify a specific QoS flow for UL rate control.
Proposal 2: The new UL Rate Control MAC CE can provide UL rate control information for multiple QoS flows.
Proposal 3: For a DRB, only one LCID indication within the UL rate control MAC CE is required which can follow number of QFIs for QoS flows for which the rate control information is provided for the given DRB.

3GPP TSG-RAN WG2 #130 meeting	R2-2503889
St Julian's, Malta, 19th May – 23rd May, 2025

Source:		NEC
Agenda item:		8.7.6	XR rate control
Title:		Uplink rate control for XR
Document for:		Discussion and decision
1. 

Summary
This contribution provides our analysis on the uplink rate control for XR, and has the following proposals:
Proposal 1: RAN2 confirms that the gNB receives from CN the information regarding which QoS flows are subject to uplink rate control.
Proposal 2: RAN node configures UE with information regarding which QoS flows support bit rate adaptation.
Proposal 3: [MAC-04] RAN2 agrees to indicate “QFI + DRB ID” in the new recommended bit rate MAC CE.
Proposal 4: For a QoS flow, UE informs the network of its preference for bit rate recommendation granularity, either on a per-LCH basis or on a per-QoS flow basis.
Proposal 5: [MAC-09] RAN2 considers the following solutions to apply the indicated recommended bit rate for a QoS flow in DC:
For PDCP duplication, the UE may not be expected to go beyond the recommended bit rate of min (recommended bit rate 1, recommended bit rate 2) for the QoS flow. 
For split transmission, the recommended bit rate for a QoS flow may be applied to the cells or cell groups where the MAC CE is received.

3GPP TSG-RAN WG2 Meeting #130		R2-2503975
St.Julians, Malta, May 19 – 23, 2025

Title: 	XR Rate control details
Source: 	ZTE Corporation, Sanechips
Agenda item:	8.7.6
Document for:	Discussion and decision

Conclusion
The following proposal is made in this contribution: 

Proposal 1 (MAC-05, 06, 07, 11, 12): The MAC CE for XR rate control includes just the QFI indicator as shown in the figure below (with the assumption that only one PDU session has QoS flows subject to rate control): 

Proposal 2 (MAC-05, 06, 07, 09, 11, 12): RRC signalling indicates which PDU session contains the QoS flows subject to rate control (if there is more than one PDU session)

3GPP TSG-RAN WG2 Meeting #130	R2-2504000
St. Julians, Malta, May 19th – 23rd, 2025

Agenda Item:	8.7.6
Source:	OPPO
Title:	Discussion on XR Rate Control
Document for:	Discussion, Decision

Conclusion
We have the following proposals:
Proposal 1	[MAC-04] In the UL Rate Control MAC CE, use DRB ID + QFI to identify a specific QoS flow.
Proposal 2	[MAC-05] The UL Rate Control MAC CE can include bit rate indications for multiple QoS flows.
Proposal 3	[RRC-Issue1] RAN2 introduces a per-QoS flow prohibit timer for the rate query MAC CE.
Proposal 4	[MAC-08] The MAC entity can generate the rate query MAC CE to include the information associated with the triggered bit rate query(s), when the MAC entity has UL resources allocated for new transmission and the allocated UL resources can accommodate the rate query MAC CE plus its subheader. Otherwise, the MAC entity does not generate and transmit the rate query MAC CE.
Proposal 5	[MAC-08] The MAC entity cancels a triggered rate query when the rate query MAC CE, including the information associated with this rate query, is generated.
Proposal 6	[MAC-09] No special UE handling is introduced for the Rate Control MAC CE in the DC scenario.
Proposal 7	[MAC-10] If the bitRateQueryProhibitTimer for a QoS flow associated with a triggered bit rate query is running, the MAC entity does not generate the rate query MAC CE for that query.
Proposal 8	[MAC-10] Upon generating the rate query MAC CE for a triggered bit rate query, the MAC entity starts the bitRateQueryProhibitTimer for the associated QoS flow.

3GPP TSG-RAN WG2 Meeting #130	R2-2504119
St.Julian's, Malta, 19-23 May, 2025

Agenda item:	8.7.6
Source: 	Huawei, HiSilicon
Title: 	Discussion on XR rate control
Document for:	Discussion and Decision
1. 

Conclusion
In this contribution, we analyzed the potential enhancements for XR rate control. The following observations and proposals were made:
Reply LS S2-2504252:
Proposal 1: RAN2 to confirm to SA2 that UL Rate Control applies to both GBR and non-GBR.
Format of Uplink Rate Control MAC CE:
Proposal 2: (MAC-04) PDU session ID should be used together with QFI to identify a QoS flow.
Proposal 3: (MAC-05) The uplink rate recommendation MAC CE should support bit rate recommendation for multiple QoS flows within a single MAC CE.
Proposal 4: (MAC-07) The NW configures QoS flows for uplink rate control via RRC and use a bitmap with each bit corresponding to the QoS flows with uplink rate control in ascending order of the PDU session ID and QFI. Adopt the TP below.
Rate Query MAC CE:
Proposal 5: (RRC-01) The NW configure the prohibit timer in QoS flow level to enable the Rate Query MAC CE. 
Proposal 6: (MAC-08) The multiplexing, transmission and cancellation of the Rate Query MAC CE follow the same way as legacy.
Proposal 7: The Rate Query MAC CE has the same format as the Rate Control MAC CE.
Rate Control in DC:
Proposal 8: (MAC-09) RAN2 to capture a NOTE that each Rate Control MAC CE indicates the recommended bit rate for the service corresponding to the QoS flow.
Proposal 9: (MAC-09) RAN2 to leave the issue of Rate Control in DC to NW implementation or RAN3 discussion.
4. 

3GPP TSG- Meeting #130	R2-2504343
St. Julians, Malta, 19th – 23rd May 2025

Agenda Item:	8.7.6
Source:	Ericsson
Title:	More Views on XR Rate Control
Document for:	Discussion, Decision
1	

Conclusion
Based on the discussion in the previous sections, we have the following observations:
Observation 1	Only the gNB-CU can perform per-QoS flow monitoring under the assumption of using the information in the SDAP header.
Observation 2	The gNB-CU cannot perform per-QoS flow monitoring if the SDAP header is not present.
Observation 3	Putting additional requirements (i.e., per-QoS flow bit rate monitoring) on the CU has the risk that not all implementations can or will support it.
Observation 4	DRB-level bit rate monitoring is feasible with all possible configurations and is architecture and deployment independent.
Observation 5	There is much more F1 signaling load for the QoS flow in MAC CE solution when comparing the RRC-based solution.
Observation 6	If the QoS flow data rate indication from the CU to the DU is to be provided on a one-shot basis, then this is no different from the RRC-based solution with DRB-level MAC CE.
Observation 7	Due to the F1 delays, the QoS flow data rate information (including the QoS flows that need to be adapted) provided to the DU can be stale, rendering the solution less flexible. If the DU needs to inform the CU of its congestion level to receive the QoS flow data rate information, this further exacerbates the F1 delays.
Observation 8	The speed advantage of a MAC CE is diminished in the QoS flow in MAC CE solution considering cross-layer interactions or F1 delays for higher layers to provide additional information, such as the QFI.
Observation 9	By utilizing the QoS flow to DRB mapping and the associated QoS information, the RAN can accurately estimate the per-QoS flow data rate and deliver a reliable configuration to the UE that remains valid throughout the entire duration of a PDU session.
Observation 10	CN is unaware of the contents of the UE radio access capabilities and whether it can support the XR rate control radio access capability, so will always perform the determination of QoS flow rate adaptability.

Based on the discussion in the previous sections, we propose the following:
Proposal 1	The gNB is allowed to configure one or more QoS flows (mapped to a DRB) to be rate adapted.
Proposal 2	For rate adaptation of more than one QoS flow within a DRB, consider three options:
	a.	 Up to UE implementation how to perform rate adaption between the configured QoS flows.
	b.	 gNB indicates the ratio of rate adaption between the QoS flows as part of the configuration providing rate adaptability of one or more QoS flows.
	c. 	gNB indicates the ratio of rate adaption between the QoS flows in the MAC CE itself.
Proposal 3	XR rate control MAC CE shall at least consist of the LCID.
Proposal 4	Discuss the issue on the CN being unaware of UE’s XR rate control capability when determining the rate adaptability of the QoS flow.
Proposal 5	Introduce a new NAS UE capability to inform the CN about UE’s support for XR rate control. Send an LS to SA2.
Proposal 6	Define a new (optional) per-UE capability with signaling for the XR rate query MAC CE. A UE supporting this capability shall also indicate support for the UL (XR) rate control MAC CE.
4 	

3GPP TSG-RAN2 Meeting #130			R2-2504375
St. Julian, Malta, 19th-23rd May

Agenda item:	8.7.6
Title:	Further consideration on Rate control
Source:	CMCC
Document for:	Discussion

Conclusion
Based on the abovementioned analysis and observations, the following is proposed.
Overall:
Observation 1: With 8 codepoints and bit rate ranges from 0.1 to 40 Mbps, the expected QE is about 4.8%, which is acceptable for XR applications as accuracy in rate control is not a critical concern.
Proposal 1: The rate control table ranges from 0.1 to 40Mbps.
Proposal 2: RAN2 will not specify DL rate control and DL rate control query.
Proposal 3: SRB is not affected by rate control.
UL Rate Control MAC CE;
Observation 2a: Capture DRB identity in Rate Control MAC CE is beneficial for LCP and fast rate control at UE side, as LCP is on LCH granularity.
Observation 2b: Capture DRB identity in Rate Control MAC CE can also avoid potential ambiguity in case two PDU sessions have QoS flows with the same QFI.
Proposal 4: The QoS flow in the Rate control MAC CE is indicated via the combination of DRB ID and QFI.
Proposal 5: Support rate control over multiple QoS flows by assembling the DRB-QFI pairs in an ascending or descending order with regarding to QoS flow priority in the Rate Control MAC CE, FFS which one.
Proposal 6: The Rate Control MAC CE should consist of one or multiple set(s) of 5-bit LCH ID, 6-bit QFI, and 8-bit (physical) bit rate.
Handling of UL Rate Queries:
Proposal 7a: The UL Rate Query MAC CE is triggered by upper layer, e.g., UE application layer. FFS there will be SA4/CT1 impact on indication of QoS flow or it’s up to UE implementation.
Proposal 7b: The triggered UL Rate Query will not trigger the SR.
Proposal 7c: The triggered UL Rate Query is cancelled when:
A MAC PDU is transmitted and this PDU includes a UL Rate Query MAC CE.
The MAC entity receives an UL Rate Control MAC CE inducing all the LCH(s) and QoS flow(s) reported in the UL Rate Query MAC CE.
FFS any other case.
Proposal 8: The priority of Rate Query MAC CE should be the same as the MAC CE for Recommended bit rate query.
Proposal 9: Introduce a per LCH prohibit timer for UL rate query to avoid signaling overhead.
UL Rate Query MAC CE:
Proposal 10: The Rate Query MAC CE should support both DRB and QoS flow granularity.
Proposal 11: The Rate Query MAC CE should consist of one or multiple pair(s) of 5-bit LCH ID and 6-bit QFI.
Impact on other WGs:
Proposal 12: Send an LS to RAN3/SA4/CT1 to synchronize RAN2’s agreements on rate control and query.

3GPP TSG-RAN WG2 Meeting #130	R2-2504434
St Julian’s, Malta, 19 – 23 May, 2025	
Agenda item:	8.7.6
Source:	Samsung
Title:	Discussion on UL rate control for Rel-19 XR
Document for:	Discussion & Decision

Conclusion
Based on the discussion above, we have the following proposals:
Proposal 1: RAN2 to use [LCID + QoS Flow ID] to signal/identify a targeted QoS flow in the new MAC CE for UL rate control.
Proposal 2: The new MAC CE is designed to support the signalling for multiple QoS flows.

3GPP TSG-RAN WG2 Meeting #130	R2-2504457
Saint Julian’s, Malta, 19 – 23 May 2025		

Agenda item:	8.7.6
Source:	Nokia, Nokia Shanghai Bell
Title:	Closing the Loop on XR rate control
WID/SID:	NR_XR_Ph3-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
This document has made the following proposals:
Proposal 1: Support Multiple entry Rate Control MAC CE using LCID and QFI for a QoS flow identification.
Proposal 2: In Multiple entry Rate Control MAC CE, the LCID field is 6 bits and is omitted for the rest of QoS flows belonging to the same LCID. 
Proposal 3: In Multiple entry Rate Control MAC CE, a 2-bit bitmap is used to indicate a QoS flow to which the rate control is applied, in ascending order of the QoS flow ID of the QoS flows which are subject to rate control within the associated logical channel. 
Proposal 4: In Multiple entry Rate Control MAC CE, an 8-bit bit rate filed is included unless DL rate control is supported. If DL rate control is supported, a 7-bit bit rate field and 1-bit Direction field are included for byte alignment.
Proposal 5: For XR rate control, multiplexing, transmission, and cancellation are specified by taking the RBR query as a baseline.
Proposal 6: For XR rate control, the prohibit timer for query function is defined/configured at the DRB level (as legacy).  
Proposal 7: For XR rate control, RAN2 discusses whether the prohibit timer starts or restarts when the UE receives the uplink rate control MAC CE from the gNB. 
Proposal 8: In the table of bit rate values, there is no need to assign the index 0 to indicate either no desired bit rate or invalidity of the previous value.
Proposal 9: For XR rate control in DC scenario, the MCG and SCG sends the available bit rate independently without any coordination. It is up to UE how to utilize such information. 

3GPP RAN WG2 Meeting #130	R2-2504476
St. Julians, Malta, May 19th – 23rd, 2025

Agenda Item:	8.7.6
Source:	HONOR
Title:	Discussion on XR rate control
Document for:	Discussion and Decision
1. 

Conclusions
This contribution provides the following proposals. 
Proposal 1: (MAC-04) Use DRB ID + QFI to identify a QoS flow that need to be throttled.
Proposal 2: (MAC-05) XR rate control MAC CE can comprise multiple QoS flows.
Proposal 3: (MAC-07) For the MAC CE design, use bitmap to indicate which QoS flows need to be throttled.
Proposal 4: (MAC-07) Define two MAC CEs with different octet of the bitmap field (e.g. one octet, eight octets) for XR rate control.
Proposal 5: (MAC-10) Support to configure prohibit timer in DRB granularity.
4. 

3GPP TSG-RAN2#130	R2-2504599
St. Julian, Malta, May 19 – May 23, 2025

Agenda item:		8.7.6
Source:		Lenovo
Title:		 XR Rate Control
Document for:		Discussion and Decision

Conclusion
Proposal 1: (MAC-04) The UL rate recommendation on a per QoS flow is indicated using the DRB ID and QFI ID. 
Proposal 2: (MAC-05) The Rate Control MAC CE can include multiple QoS flows. 
Proposal 3: (MAC-06) The Rate Control MAC CE consists of the following fields: DRB ID, QoS Flow ID (QFI), Bit Rate Recommendation. 
-	The number of bits for DRB ID shall be at least 5 bits. 
-	The number of bits for QFI shall be at least 6 bits. 
-	The number of bits for Bit Rate Recommendation shall be 8 bits.
Proposal 4: (MAC-07) The Rate Control MAC CE does not include a bit rate multiplier field.  
Proposal 5: (MAC-08) The Rate Control Query MAC CE is specified with the same principles as legacy RBR Query MAC CE, i.e., within section 5.18.10.  
Proposal 6: (MAC-08) The Rate Control MAC CE can be multiplexed with the same priority as the legacy RBR Query MAC CE. 
Proposal 7:  (MAC-09) UE applies the latest received UL bitrate recommendation for a QoS flow if UE can receive Rate Control MAC CE from both MCG and SCG for split DRB.