RP-191602

3GPP TSG RAN #84

Newport Beach, USA, 3rd – 6th, June, 2019 Agenda 9.9

Handling of TEI & Contribution

Submission in RAN WGs
for NR & LTE
3GPP RAN TSG and WG1/2/3/4 Chairmen

©
© 3GPP
3GPP2009
2019 Mobile World Congress, Barcelona, 19 February 2009
th
1
Background
TEI is a useful tool to introduce small technical enhancements, and has been actively used
for many years especially for LTE
For NR,
 For RAN1, a need to start handling TEI for NR in Rel-16 is emerging
 For RAN2, TEI16 is scheduled to be discussed from August meeting
 For RAN3, at least one TEI16 CR has already been agreed
 For RAN4, TEIx will be only used after Rel-x frozen
RAN needs further guidance to ensure efficient and useful use/handling of TEI
 Note: 21.900 provides overall description of TEI
 Note: there was also a previous guidance on TEI guidance in RAN (being used by RAN2)
The guidance in the subsequent slides is addressing Cat. B/C TEIs
 Existing procedures on handling Cat. F TEIs to address corrections related to experience obtained
from the field remain unchanged, and will take highest precedence

©
© 3GPP
3GPP2009
2019 Mobile World Congress, Barcelona, 19 February 2009
th
2
2
Proposal on Cat. B/C TEI handling
TEI, by definition, have to be small technical enhancements
 Very limited online time is available in WGs
 Each TEI shall be fully completed within the same quarter in all affected WGs
Work on TEI should predominantly be within a single WG
 Cross-WG TEI is strongly discouraged
 RAN1/2 TEI proposal with RAN4 impact to core requirements is strongly
discouraged
 Cross-TSG TEI including RAN is very strongly discouraged
TEI handling in a WG is up to the WG Chairman’s discretion
 Based on technical merit, commercial interest & level of support of the proposals
 The number of TEIs agreed per quarter and per release in a WG is expected to
be very limited
 Especially for RAN1/RAN2 TEIs with RAN4 impact on performance requirements

©
© 3GPP
3GPP2009
2019 Mobile World Congress, Barcelona, 19 February 2009
th
3
3
Proposal on Cat. B/C TEI handling – Cont’d
For cross WG TEI:
 A single WG makes the yes/no decision on a TEI
 It should be obvious which WG makes the decision - if it is not obvious then the cross WG interaction is too much for
a TEI
 RAN2 impact of RAN1/4-led TEI shall be limited to RRC signalling of configuration parameters and UE
capabilities (no MAC impact, no RRC procedural impact, etc)
 RAN4 impact of RAN1/2-led TEI to performance requirements, i.e., test case(s), can be evaluated/discussed
in performance phase of certain release, e.g., after March 2020 for Rel-16 as a package
For traceability:
 If a TEI enhancement affects more than one spec then the "other specs affected" shall be used to link the
CRs (this is a reminder - no change from current procedures)
 If a TEI enhancement requires correction after it is introduced then the (Cat F) correction CR shall refer to
the original CR in the "other comments"
 RAN will not utilize the procedure described in 21.900 to create a 'mini' WID for each TEI
 This implies that a 21.900 CR is to be provided by RAN leadership to SA#85

©
© 3GPP
3GPP2009
2019 Mobile World Congress, Barcelona, 19 February 2009
th
4
4
Proposal on Cat. B/C TEI handling – Cont’d

Additional TEI rules (primarily for RAN1 - at WG chair's

discretion whether to apply in other groups)
 Each TEI proposal is expected to have support ideally from at least one
operator, one infra vendor and one UE vendor
 Each company/organization/university can lead/initiate up to one TEI
item per quarter
 Necessary to not have excessive # of TEIs
The agreed TEI(s) in each WG in each quarter is to be reported
to RAN in the chair's report
 This allows RAN to monitor the usage of TEIs
 WG agreed CRs are submitted to RAN for approval following normal
procedures

©
© 3GPP
3GPP2009
2019 Mobile World Congress, Barcelona, 19 February 2009
th
5
5
Considerations on contributions submitted
under ”Others” agenda item in RAN1
Background:
 In RAN1, there is typically a limitation of maximum 1 contribution per
company/organization/university for each agenda item
 However, typically there is no limitation on the number of contributions
submitted under “Others” agenda item
 “Others” agenda item may be useful e.g., handling topics led by other WGs
 It becomes evident that the number of contributions submitted under “Others”
agenda item is excessively high in RAN1
 Which is distracting particularly for companies to review contributions
Proposals:
 RAN1 to further enforce a limitation of maximum 1 contribution per
company/organization/university for “Others” agenda item

©
© 3GPP
3GPP2009
2019 Mobile World Congress, Barcelona, 19 February 2009
th
6
6