BAP configuration associated with a topology identifier

Patent metadata

Field	Value
Publication number	US-12507149-B2
Application number	US-202117451797-A
Country	US
Kind code	B2
Filing date	Oct 21, 2021
Priority date	Oct 22, 2020
Publication date	Dec 23, 2025
Grant date	Dec 23, 2025

Abstract

A second network node determines a backhaul adaptation protocol (BAP) configuration associated with a backhaul traffic transport and including a topology identifier corresponding to a topology of a plurality of topologies for which traffic associated with the topology is transported based on the BAP configuration. The second network node sends, to a first network node, the BAP configuration associated with the backhaul traffic transport. The first network node receives a first BAP configuration associated with a first topology identifier (ID) corresponding to a first topology, and a second BAP configuration associated with a second topology ID corresponding to a second topology that overlaps at least in part with the first topology. The first network node determines with which traffic is associated routes traffic associated with the first topology ID based on the first BAP configuration, and traffic associated with the second topology ID based on the second BAP configuration.

First claim

What is claimed is:

1 . An apparatus for wireless communication at a first network node, comprising:
memory; and at least one processor coupled to the memory and configured to:
receive a first backhaul adaptation protocol (BAP) configuration associated with a first topology, and a second BAP configuration associated with a second topology that overlaps at least in part with the first topology, wherein the first BAP configuration is associated with a first topology identifier (ID) for the first topology and includes a first BAP address configured for the first network node, and the second BAP configuration is associated with a second topology ID for the second topology and includes a second BAP address configured for the first network node; and
route traffic associated with the first topology based on the first BAP configuration, and traffic associated with the second topology based on the second BAP configuration.

2 . The apparatus of claim 1 , wherein the at least one processor is further configured to:
determine whether the traffic is associated with the first topology ID or the second topology ID in order to route the traffic.

3 . The apparatus of claim 1 , wherein each of the first BAP configuration and the second BAP configuration comprises, for the first topology and the second topology, respectively, at least one of:
a setup of a backhaul radio link control (RLC) channel at the first network node; an uplink mapping configuration between at least one of a traffic type or Internet protocol (IP) header field and a BAP routing identifier (ID), an egress link at the first network node, or egress backhaul RLC channel at the first network node; a routing configuration along a BAP route between a BAP routing ID and the egress link at the first network node; or a backhaul RLC channel mapping configuration between an ingress backhaul RLC channel and the egress backhaul RLC channel at the first network node.

4 . The apparatus of claim 1 , wherein first traffic associated with the first topology is associated with a second network node and second traffic associated with the second topology is associated with a third network node.

5 . The apparatus of claim 1 , wherein the at least one processor is further configured to:
receive information indicating that at least one of the first topology or the second topology is associated with a particular traffic type, wherein the traffic is routed based on the information, a traffic type being at least one of F1 control plane (F1-C) signaling, F1 user plane (F1-U) tunnel, or non-F1 traffic.

6 . The apparatus of claim 1 , where the traffic is associated with the first topology or the second topology based on a default for a traffic type of the traffic, the traffic type being at least one of F1 control plane (F1-C) signaling, F1 user plane (F1-U) tunnel, or non-F1 traffic.

7 . The apparatus of claim 6 , wherein the traffic is associated with the first topology by default if the traffic is communicated with a second network node, and is associated with the second topology by default if the traffic is communicated with a third network node.

8 . The apparatus of claim 1 , wherein to route the traffic, the at least one processor is further configured to:
receive a downstream packet associated with the first topology; and pass the downstream packet to upper layer processing when the downstream packet carries a destination BAP address that matches a BAP address allocated to the first network node via a BAP address configuration in the first BAP configuration with the first topology.

9 . The apparatus of claim 1 , wherein to route the traffic, the at least one processor is further configured to:
receive a downstream packet associated with the first topology; and forward the downstream packet to an egress link based on a BAP routing ID carried by the downstream packet and a routing configuration received in the first BAP configuration with the first topology when a destination BAP address carried by the downstream packet mismatches a BAP address allocated to the first network node via a BAP address configuration in a third BAP configuration with the first topology.

10 . The apparatus of claim 9 , wherein to route the traffic, the at least one processor is further configured to:
map the downstream packet associated with the first topology to an egress backhaul radio link control (RLC) channel on the egress link based on an ingress backhaul RLC channel on which the downstream packet is received by the first network node and based on a backhaul RLC channel mapping received in a fourth BAP configuration with the first topology.

11 . The apparatus of claim 1 , wherein to route the traffic, the at least one processor is further configured to:
receive an upstream packet associated with the first topology; and forward the upstream packet to an egress link based on a BAP routing identifier (ID) carried by the upstream packet and a routing configuration received in the first BAP configuration associated with the first topology.

12 . The apparatus of claim 11 , wherein to route the traffic, the at least one processor is further configured to:
map the upstream packet associated with the first topology to an egress backhaul radio link control (RLC) channel on the egress link based on an ingress backhaul RLC channel on which the upstream packet is received by the first network node and based on a backhaul RLC channel mapping received in a third BAP configuration with the first topology.

13 . The apparatus of claim 1 , wherein at least one of the first BAP configuration or the second BAP configuration is comprised in at least one of radio resource control (RRC) signal or F1 control plane (F1-C) signaling.

14 . The apparatus of claim 1 , wherein to route the traffic, the at least one processor is further configured to:
receive a BAP service data unit (SDU) associated with the first topology; and send a corresponding packet that carries a BAP routing ID based on a traffic type of the BAP SDU or an Internet protocol (IP) header field and based on an uplink mapping configuration received in the first BAP configuration with the first topology, wherein the corresponding packet for transmission on an egress link based on the BAP routing ID and a routing configuration in a third BAP configuration with the first topology, and wherein the corresponding packet maps to an egress backhaul radio link control (RLC) channel on the egress link based on the traffic type or the IP header field and based on the uplink mapping configuration received in a fourth BAP configuration with the first topology.

15 . The apparatus of claim 1 , wherein to route the traffic, the at least one processor is further configured to:
receive a BAP service data unit (SDU) associated with the first topology; and send a corresponding packet that carries a BAP routing ID based on Internet protocol (IP) header fields and a downlink mapping configuration received in the first BAP configuration with the first topology, wherein the corresponding packet is for transmission on an egress link based on the BAP routing ID and a routing configuration in a third BAP configuration with the first topology, and wherein the corresponding packet maps to an egress backhaul radio link control (RLC) channel on the egress link based on the IP header fields and based on the downlink mapping configuration in a fourth BAP configuration with the first topology.

16 . The apparatus of claim 1 , wherein to route the traffic, the at least one processor is further configured to:
receive an upstream

Assignees

• Qualcomm Inc

Inventors

• Akl Naeem
• Hampel Karl Georg
• Abedini Navid
• Luo Jianghong
• Blessent Luca
• Li Junyi
• Luo Tao

Classifications

• H04L45/52

  Multiprotocol routers · CPC title

• H04W28/0273

  adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP] (wireless network protocols or protocol adaptations to wireless operation, e.g. wireless application protocol H04W80/00) · CPC title

• H04L45/02

  Topology update or discovery · CPC title

• H04W40/248

  Connectivity information update · CPC title

• H04W40/34

  Modification of an existing route · CPC title