Abstract
A base station includes a plurality of system-on-a-chip (SOC) boards, which each include a plurality of SOC devices to support wireless communication on a plurality of carriers. One of the SOC devices is a transport SOC (TSOC) device that terminates a backhaul interface for receiving downlink radio bearer packets. Each of the SOC devices configures the TSOC device to route downlink radio bearer packets to a packet data convergence protocol (PDCP) module in the SOC device.
Technologies
Backhaul Radio Link
Product
Use Cases
Wireless communication
Services
Claim
1. An apparatus comprising:
a plurality of system-on-a-chip (SOC) boards, each SOC board comprising a plurality of SOC devices to support wireless communication on a plurality of carriers, wherein one of the SOC devices is a transport SOC (TSOC) device that terminates a backhaul interface for receiving downlink radio bearer packets, and wherein each of the SOC devices configures the TSOC device to route downlink radio bearer packets to a packet data convergence protocol (PDCP) module in the SOC device, wherein each of the plurality of SOC devices comprises:
a hardware acceleration engine; and
a plurality of processor cores, wherein non-real-time processes are bound to a first portion of the processor cores, real-time backhaul support and the PDCP module are bound to a second portion of the processor cores, real-time scheduling is bound to a third portion of the processor cores, and physical layer processing is bound to a fourth portion of the processor cores.
2. The apparatus of claim 1, wherein the SOC devices implement transport abstraction layer (TALs) to configure the hardware acceleration engine in the TSOC device to route the downlink radio bearer packets to the corresponding PDCP modules on downlink radio bearer paths that bypass the plurality of processor cores.
3. The apparatus of claim 2, wherein the TALs in the SOC devices program the hardware acceleration engine in the TSOC to define rules for parsing, classification, and dispatching (PCD) of downlink radio bearer packets to the SOC devices on the downlink radio bearer paths.
4. The apparatus of claim 3, wherein the PCD rules for an SOC device are removed from the hardware acceleration engine in response to the SOC device being uninstalled or prior to rebooting the SOC device.
5. The apparatus of claim 2, wherein the hardware acceleration engine in the TSOC device is to route the downlink radio bearer packets to the PDCP modules based on identifiers included in the downlink radio bearer packets.
6. The apparatus of claim 5, wherein the identifiers include at least one of an identifier number that indicates the SOC device, information indicating one of the plurality of SOC boards that hosts the SOC device, or a shelf number that identifies a shelf in a base station that hosts the SOC board.
7. The apparatus of claim 6, wherein the identifiers include information indicating an instance of the PDCP module on the SOC device and an incarnation bit that is flipped in response to termination of a previous instance of the PDCP module.
8. The apparatus of claim 6, wherein the identifiers include information indicating a quality-of-service (QoS) field to hold a value that indicates a QoS class identifier (QCI) associated with the downlink packet.
9. The apparatus of claim 6, wherein the identifiers are generated in response to booting the corresponding SOC device, and wherein the generated identifiers are transmitted to a mobility management entity (MME) that is configured to attach the identifiers to downlink radio bearer packets destined for the corresponding SOC device.
10. A method comprising:
receiving, via a backhaul interface at a transport system-on-a-chip (TSOC) device that is one of a plurality of SOC devices implemented on a plurality of SOC boards, a downlink packet addressed to an indicated SOC device of the plurality of SOC devices, wherein the downlink packet is to be transmitted using one of a plurality of carriers supported by the indicated SOC device;
routing, at the TSOC, the downlink packet to a packet data convergence protocol (PDCP) module implemented by the indicated SOC device; and
configuring a hardware acceleration engine in the TSOC device to route the downlink packet to the corresponding PDCP modules on downlink radio bearer paths that bypass a plurality of processor cores in the TSOC device.
11. The method of claim 10, wherein routing the downlink packet to the PDCP module comprises routing the downlink packet on the downlink radio bearer path that bypasses the plurality of processor cores in the TSOC device.
12. The method of claim 10, wherein configuring the hardware acceleration engine comprises programming the hardware acceleration engine in the TSOC to define rules for parsing, classification, and dispatching (PCD) of downlink radio bearer packets to the SOC devices on the downlink radio bearer paths.
13. The method of claim 12, wherein configuring the hardware acceleration engine comprises removing the PCD rules from the hardware acceleration engine in response to the SOC device being uninstalled or prior to rebooting the SOC device.
14. The method of claim 10, wherein routing the downlink radio bearer packets to the PDCP modules comprises routing the downlink radio bearer packets to the PDCP modules based on identifiers included in the downlink radio bearer packets.
15. The method of claim 14, wherein the identifiers include at least one of an identifier number that indicates the SOC device, information indicating one of the plurality of SOC boards that hosts the SOC device, a shelf number that identifies a shelf in a base station that hosts the SOC board, information indicating an instance of the PDCP module on the SOC device, an incarnation bit that is flipped in response to termination of a previous instance of the PDCP module, and information indicating a quality-of-service (QoS) field to hold a value that indicates a QoS class identifier (QCI) associated with the downlink packet.
16. The method of claim 14, further comprising:
generating the identifiers in response to booting the corresponding SOC device; and
transmitting the identifiers to a mobility management entity (MME) that is configured to attach the identifiers to downlink radio bearer packets destined for the corresponding SOC device.
17. A system-on-a-chip (SOC) board comprising:
a plurality of SOC devices that includes a transport SOC (TSOC) to terminate a backhaul interface for receiving downlink radio bearer packets, wherein each of the plurality of SOC devices supports wireless communication on at least one carrier, and wherein each of the plurality of SOC devices configures the TSOC to route downlink radio bearer packets received on the backhaul interface to a packet data convergence protocol (PDCP) module for transmission via the at least one carrier, wherein the plurality of SOC devices implement transport abstraction layer (TALs) to configure a hardware acceleration engine in the TSOC device to route the downlink radio bearer packets to the corresponding PDCP modules on downlink radio bearer paths that bypass a plurality of processor cores implemented in the plurality of SOC devices.
Associated Portfolios
Licensor Claim Chart
 Claim Chart |
 Technology |
 Creation Date |
 Download |
|---|---|---|---|
|
Claim charts will soon be available!
|
|||
Note:
The information in blue was extracted from the third parties (Standard Setting Organisation, Espacenet)
The information in grey was provided by the patent holder
The information in purple was extracted from the FrandAvenue
Explicitly disclosed patent
Implicitly disclosed patent
Basis patent
Family member