Ran1 Agreements Sample Contracts
RAN1 Meeting #116Ran1 Agreements • October 26th, 2024
Alt1b: One PL offset value is configured in a joint or UL TCI state by RRC, where different PL offset values can be configured to different joint or UL TCI states. A MAC CE can update the PL offset value(s) for joint or UL TCI state(s).
RAN1 agreements (post-RAN1#112) on SRS with potential RAN2/RAN4 impactRan1 Agreements • March 3rd, 2023
Agreement (RAN2 RRC) For SRS interference randomization, support: Opt. 3: Both cyclic shift hopping and comb offset hopping. At least the two features can be separately configured FFS: Combined cyclic shift hopping and comb offset hopping for a UE FFS: Separate or combined with SRS sequence group hopping / sequence hopping FFS: Associated UE capability “RAN2 impact: RRC, SRS configuration / UE capability for comb offset hopping / cyclic shift hopping” “RAN4 impact: none” Agreement (RAN2 RRC) For SRS comb offset hopping and/or cyclic shift hopping, for each SRS port, the hopping pattern is determined based on the pseudo-random sequence c(i), initialized with one of the following IDs. Option 1: Reuse the SRS sequence identity . Option 2: Introduce new ID(s). FFS: the value range, one new ID or two separate new IDs, default ID(s) “RAN2 impact: RRC, SRS configuration of sequence ID for comb offset hopping / cyclic shift hopping” “RAN4 impact: none” Agreement (RAN2 RRC) For an 8-port SR
RAN1 Meeting #116Ran1 Agreements • September 24th, 2024
Alt1b: One PL offset value is configured in a joint or UL TCI state by RRC, where different PL offset values can be configured to different joint or UL TCI states. A MAC CE can update the PL offset value(s) for joint or UL TCI state(s).