Huawei links R2D segmentation to CT1 application data length

Huawei with HiSilicon addressed RAN2, the radio protocols working group, in Observation 18 at RAN2 #135. In that observation, it wrote "The R2D segmentation should be supported to improve the R2D transmission performance". Its examples included cell-edge transmissions, large messages and collision avoidance involving periodic broadcast information. R2D segmentation here concerns splitting the named transmissions into parts.

Source: R2-2605187, Huawei (with HiSilicon), 3GPP TSG RAN WG2 #135. © Huawei, HiSilicon.

At RAN2 #135-bis, Huawei with HiSilicon submitted Proposal 5 on the same question. It described flexibility for the access stratum (AS, the radio protocol layers) and the application interface. It gave "efficient radio resource utilization and flexible (larger) application data length" as examples of that flexibility.

Source: R2-2606774, Huawei (with HiSilicon), 3GPP TSG RAN WG2 #135-bis. © Huawei, HiSilicon.

Whether RAN2 supports R2D segmentation will affect CT1 decisions on maximum application data length, the proposal says. CT1 is the core network and terminals working group handling protocols between devices and the core network. Our reading: The later proposal broadens the earlier performance case and retains a radio resource efficiency argument.

The register lists R2-2605187 as available, with no decision recorded. The register marks R2-2606774 as noted, which does not record agreement to support segmentation. Noted describes the contribution's status, not agreement to its content.