1. Discussion and Way Forward NB IoT UE Differentiation

2. Discussion on RRM Policy Container
RAN2 requested the RRM policy a container and the Subscription IE, RAN3 endorsed the stage 2 for both at RAN3 100
RRM Policy container allows to learn and store some RRM information e.g. power, scheduler, … details were discuss in RAN2, no intention to go in details…
No common understanding  need further discussion
Issue between RAN nodes of different vendors
Allow interoperability between RAN and CN of different vendors
IoT issue manageable by criticality
Container not restricted to NB IoT and not specified per vendor (generic), need further discussion included storage ….
How to allow time for container discussion?
1 quarter 2nd extension, enough?  no
Handle in TEI16?
More time  Move the issue into SID on RAN-centric data collection and utilization for LTE and NR

3. UE subscription
At least 15 companies believes this CRs can be approved independently:
RP /RP Introduction of Subscription based UE differentiation (Huawei, HiSilicon, China Telecom, CMCC, China Unicom, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Inter Digital, Broadcom, TIM, Panasonic, Deutsche Telekom, Institute for Information Industry (III), Verizon)

4. Summary and Way Forward
WF1
Explicitly capture the RRM Policy container as objective of the SID on RAN-centric data collection and utilization for LTE and NR
Approved the CRs related to Subscription based UE:
RP Introduction of Subscription based UE differentiation
RP Introduction of Subscription based UE differentiation
Completed the NB IoT WI
WF2
No agreed nothing
Implies removal from SA2
WF3
Agreed both (Subscription and container)
WF4 Move the UE differentiation in rel-16 both (NB IoT)
WF5 Move the UE differentiation with container only in rel-16 (NB IoT)
WF6 New SID dedicated to container