Systems and methods for implementing various metrics for in integrated IAB networks are disclosed. A child IAB node may determine metrics regarding one or more of its data flows and report these metrics to an upstream IAB node (that is a parent node and/or an IAB donor). The upstream node may determine a data flow prioritization configuration using these metrics that it either uses itself or sends back to the child IAB node or another IAB node of the IAB network for use there. Metrics discussed include a number of hops metric, an aggregate throughput per BH RLC channel ID (or per routing ID) metric, a fairness index per BH RLC channel ID (or per routing ID) metric, a packet drop metric, and a per-hop latency for aggregated traffic per BH RLC channel ID (or per routing ID) per IAB node metric.
Legal claims defining the scope of protection, as filed with the USPTO.
2. The method of claim 1, wherein the data flow prioritization configuration is sent to the child IAB node in a BH adaptation header (BAP) protocol data unit (PDU).
3. The method of claim 1, wherein the data flow prioritization configuration is sent to the child IAB node on an F1 application protocol (F1AP) interface.
5. The method of claim 4, wherein the information regarding the one or more data flows received at the descendent IAB node is received from the descendent IAB node on an F1 application protocol (F1AP) interface.
6. The method of claim 4, wherein the information regarding the one or more data flows received at the descendent IAB node is received from a child node that is not the descendent TAB node in a BH adaptation header (BAP) protocol data unit (PDU).
9. The method of claim 8, wherein the one or more per-hop latency metrics corresponding to the one or more data flows is indicated per a BH radio link control (RLC) channel of each of the one or more data flows.
10. The method of claim 8, further comprising configuring the descendent IAB node to timestamp packets of the one or more data flows; wherein the received information regarding one or more data flows comprises timestamps of the packets of the one or more data flows.
12. The method of claim 11, wherein the one of the plurality of metrics is sent to the parent IAB node in a BH adaptation header (BAP) protocol data unit (PDU).
13. The method of claim 11, wherein the one of the plurality of metrics is sent to the parent IAB node using an F1 application protocol (F1AP) interface.
14. The method of claim 11, wherein the one or more number of hops metrics are each calculated by incrementing a counter received at the child IAB node that corresponds to a data flow received at the child IAB node.
15. The method of claim 11, wherein the one or more aggregate throughput per BH RLC channel ID metrics or the one or more aggregate throughput per routing ID metrics for the one or more data flows are each calculated by dividing a number of RLC service data units (SDUs) by a number of corresponding acknowledgements received for the RLC SDUs.
16. The method of claim 11, wherein the one or more per-hop latency per BH RLC channel ID metrics are each calculated by referring to one of system frame numbers (SFNs) and subframe numbers received in each of the one or more data flows.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
January 14, 2021
May 21, 2024
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.