3GPP Scout / Updates / Company proposal change

Company proposal changeRAN2 #135-bis

ZTE and Sanechips claim up to 4% overhead cut from a single user-plane sequence number

Published 2026-11-11Updated 2026-11-113GPP TSG RAN WG2 #135-bis

At a glance

ZTE and Sanechips proposed that RAN2 note a single user-plane sequence number (SN) cuts overhead by up to 4% for small Internet Protocol (IP) packets.

What changed in the proposal

RAN2 is the radio access network layer 2 working group. ZTE and Sanechips submitted R2-2605411 for RAN2 #135 and R2-2607131 for RAN2 #135-bis. The user-plane (UP) protocol stack carries user traffic. Observation 2 in R2-2605411 states "Supporting single SN in UP protocol stack is compatible with HLS but there may be impacts to RAN3 protocol". HLS means higher layer split of a base station between central and distributed units. RAN3 is the radio access network architecture and interfaces working group.

Source: R2-2605411, ZTE (with Sanechips), 3GPP TSG RAN WG2 #135. © ZTE, Sanechips.

In R2-2607131, Proposal 1 asks RAN2 to note "Overhead reduction (up to 4% for small IP packets which are predominant in IP networks)". Our reading: The later item quantifies an overhead claim, while the earlier observation identifies possible RAN3 protocol impacts.

Source: R2-2607131, ZTE (with Sanechips), 3GPP TSG RAN WG2 #135-bis. © ZTE, Sanechips.

R2-2605411 is listed as available at RAN2 #135, with no decision recorded in its register entry. R2-2607131 is listed as noted at RAN2 #135-bis. Our reading: Noted is the contribution's handling status, not acceptance of the proposed 4% gain.

Sources

  1. R2-2607131, ZTE (with Sanechips), 3GPP TSG RAN WG2 #135-bis. © ZTE, Sanechips.
  2. R2-2605411, ZTE (with Sanechips), 3GPP TSG RAN WG2 #135. © ZTE, Sanechips.

How this page was made

Written with AI assistance from TDocs indexed by 3GPP Scout. An AI model (GPT-6 Sol) drafted each sentence and named the source it rests on. Code checked every quote word for word against the stored source text, and the live check fetched each TDoc again before publishing. A second AI model from another company (Claude Opus 5.5) reviewed the page against the same sources. The 3GPP documents themselves govern.