The TRPs 308 may be or may include a base station DU. The TRPs may be connected to one ANC (ANC 302) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific ANC deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
The local architecture of RAN 300 may be used to illustrate fronthaul communication. The architecture may be defined to support fronthauling solutions across different deployment types. For example, the architecture may be based at least in part on transmit network capabilities (e.g., bandwidth, latency, and/or jitter).
The architecture may share features and/or components with LTE. According to aspects, the NG-AN 310 may support dual connectivity with NR. The NG-AN 310 may share a common fronthaul for LTE and NR.
The architecture may enable cooperation between and among TRPs 308. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 302. According to aspects, no inter-TRP interface may be needed/present.
According to aspects, a dynamic configuration of split logical functions may be present within the architecture of RAN 300. The packet data convergence protocol (PDCP), radio link control (RLC), or medium access control (MAC) protocol may be adaptably placed at the ANC or TRP.
According to various aspects, a base station may include a CU (e.g., ANC 302) and/or one or more DUs (e.g., one or more TRPs 308).