Xiaomi asks when Topology 2 needs a session release indication

Both Xiaomi contributions address Ambient Internet of Things (A-IoT) Topology 2 and the reader's session release. At RAN2 #135, Xiaomi wrote "No need to introduce a separate session release indication". Xiaomi said deconfiguring or releasing A-IoT resources implies termination of A-IoT operation by the user equipment (UE) reader. It said the reader can then terminate an ongoing session through UE implementation, without a specification change.

Source: R2-2604854, Xiaomi, 3GPP TSG RAN WG2 #135. © Xiaomi.

At RAN2 #135-bis, Xiaomi's contribution asks whether resource release implies session release. If it does not, the later contribution says "explicit session release indication is supported". Our reading: This condition modifies the earlier objection, rather than recording a working group agreement. Neither contribution records a RAN2 decision about whether releasing resources ends a session.

Source: R2-2607424, Xiaomi, 3GPP TSG RAN WG2 #135-bis. © Xiaomi.

Xiaomi's later contribution also asks about a new signaling radio bearer (SRB) carrying inventory requests. Our reading: Inventory requests ask A-IoT devices to identify themselves. The contribution asks whether session release and downlink non-access stratum (NAS) data transfer should use the same or different messages. Our reading: That message question is conditional on a new bearer carrying inventory requests, not a decision to use one.