Page 12 - 3GPP_Highlights_I4

TECHNICAL HIGHLIGHTS

TSG RAN#95-E PROGRESS

TO REPORT

By Wanshi Chen, 3GPP TSG RAN Chair

TSG RAN#95-e was a hectic and Administrative Aspects in RP-220882. RAN plans to work with the
critical meeting, held electronically guidelines, taking into account several
from March 17th to March 23rd, with aspects summarized in Section 5 of RP-
220882.
5 working days spread across two RAN#95-e addressed the following
weeks and a 48-hour quiet period administrative aspects: UTRAN Specs in Rel-17: One involved
imposed during the weekend. discussion in RAN#95-e was whether and
Inclusive language: In 3GPP, using how to automatically upgrade UTRAN specs
Besides the usual Plenary business inclusive language for specifications is (25 and some 34 specification series) from
of RAN WG issues, ITU related taken seriously. A large amount of effort Rel-16 to Rel-17. After lengthy discussion,
was spent in previous RAN plenary
RAN#95-e concluded the following (see
issues, meeting planning, etc., meetings. Such effort continued in more details in RP-220906):
RAN#95-e notched up some major RAN#95-e, resulting in the approval of
achievements: a set of Rel-17 CRs, including RP-220313 • 25 series : Do not upgrade any 25-series
on the removal of the “black List” term specifications to Rel-17.
• The successful functional freeze for and those derived from that term (CR to
RAN Rel-17, TS 44.318), RP-220314 to change “white • 34 series : Do not upgrade RAN4 specs
TS 34.124 & 34.926, and RAN2 spec TS
list” to ‘allowed list’ (CR to TS 45.008),
• Approval of RAN4-led Rel-18 RP-220238 to take out “master, slave” 34.109.
package,
(CRs for NR from RAN3), RP-220239 to However, since such an issue requires
• Note: RAN1/2/3-led Rel-18 package change “black cells” to “excluded cells” coordination across TSGs, a Liaison
was approved in December during (CR for E-UTRAN from RAN3), and RP- Statement (LS) was sent to TSG SA and TSG
RAN#94-e. 220506 for a variety of those terms (CRs CT (see RP-221015). The LS was carefully
for E-UTRAN and NR from RAN2). The discussed in a subsequent joint TSG session,
• Successful completion of the 5Gi detailed email discussion summary can which resulted in the following conclusion:
merger (from RAN perspective), be found in RP-220878.
and • All 25 and 34 series specs should be
WID names and acronyms: In response upgraded to Rel-17 and that until the
• Endorsed RAN meeting planning to ETSI MCC contribution RP-220065 end of Rel-18 there should be a cross-TSG
for 2022 titled “Guidelines on WIDs names and effort to find out if and how the related
acronyms”, RAN#95-e discussed and functionality could not be upgraded to
What follows is a detailed RAN#95-e endorsed feedback as summarized
summary of the key areas covered by Rel-18. This discussion should also be on
the meeting. whether to update the 2G specifications.
Proposed RAN meeting plan (2022) RP-220857
Proposed RAN meeting plan (2022)
E-meeting F2F Planned F2F (TBC) Planned E-meeting (TBC) Planned F2F (TBC)

April May June July August Sept. Oct. Nov. Dec.
2022 2022 2022 2022 2022 2022 2022 2022 2022
04-08 11-15 18-22 25-29 02-06 09-13 16-20 23-27 30-3 6-10 13-17 20-24 27-1 4-8 11-15 18-2225-29 1-5 8-12 15-1922-26 29-2 5-9 12-16 19-23 26-30 3-7 10-14 17-21 24-28 31-4 7-11 14-18 21-25 28-2 5-9 12-16 19-2326-30
F2F WG WG TSG WG TSG WG WG TSG
meeting
schedules
RAN1 -E RAN1-E I RAN1-E I RAN1-E
I
I I © 3GPP 2012 T N (5+3) N (2+5) I T
N N N S A A N A S
A Ad- A RAN2-E A RAN2-E G C RAN2-E C RAN2-E C G
C Hoc C C T (5+3) T (2+5) T
T T T # I I #
I I I 9 V V I 9
V V RAN3-E V RAN3-E 7 E RAN3-E E RAN3-E V 8
E E (5+4) E (5+4) E (5+2) (2+5) E E
E-meeting P P P
schedules P E P E RAN4-E P E RAN4-E E RAN4-E E RAN4-E E
R R R R I (5+3) R I (2+5) R
I I I O O I
O O RAN5-E O RAN5-E D D RAN5-E O
D D D D
Friday to Monday,
inclusive Back-up Plan
| * For RAN2 Ad-hoc in April, please refer to RP-213608 for more details Endorsed RAN meeting planning for the remaining 2022 (see RP-220857)
12 3GP P Highlights ne w slet t er