# Summary of 3GPP CR S4-260085

## Change Request Details
- **Specification**: TS 26.114 v18.12.0
- **CR Number**: 0605
- **Category**: F (Correction)
- **Release**: Rel-18
- **Work Item**: IVAS_Codec

## Main Technical Contribution

### Problem Statement
The document identifies an inconsistency in the bandwidth computation procedure for the IVAS codec specified in clause Z.2 compared to the general session setup procedures defined in clause 6.2.7.2 of TS 26.114. Specifically, the IVAS-specific procedure includes RTCP bandwidth in the b=AS (Application-Specific maximum bandwidth) calculation, while other codecs and general procedures do not.

### Technical Solution

The CR proposes a correction to clause Z.2 "Procedure for computing the bandwidth" to align the IVAS codec bandwidth calculation with existing procedures for other codecs.

#### Modified Bandwidth Calculation Procedure

The updated procedure for computing b=AS when no extra bandwidth is allocated for redundancy:

1. Use the highest negotiated bitrate for the IVAS codec included in the SDP (using ibr or ibr-recv parameters if specified)
2. Calculate bitrate for the RTP payload header
3. Add bandwidth needed for PI (Primary Importance) data (using pi-br or pi-br-recv parameters if specified)
4. Add bandwidth needed for IP, UDP and RTP headers assuming 50 frames per second:
   - 16 kbps for IPv4
   - 24 kbps for IPv6
5. ~~Add bandwidth needed for RTCP~~ **(REMOVED)**
6. The b=AS bandwidth is the sum of the above listed bitrates after rounding up to nearest integer kbps

**Key Change**: Step 5 (adding RTCP bandwidth) has been removed from the calculation procedure, and the subsequent step has been renumbered from 6 to 5.

### Impact

The CR ensures consistency across TS 26.114 by removing the RTCP bandwidth component from the IVAS-specific b=AS calculation, aligning it with the treatment of other codecs in the specification. This eliminates ambiguity in bandwidth modifier handling for IVAS codec implementations.