> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/hw/5g/5g-cpe/gxc-cpe-001-n48-n78-specification-sheet.md).

# GXC-CPE-001 (n48/n78) Specification Sheet

Last Updated: 2026-02-23

<h4 align="center">5G High Gain Outdoor CPE</h4>

<figure><img src="https://4084968256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgSxa0NIdBp5aDw7Lf2N9%2Fuploads%2FfaVVinQ8oTEgobssKhbw%2FCPE_only_wht.jpg?alt=media&amp;token=1f9eeccf-1123-4a3f-be80-cf30cf577c0c" alt="" width="401"><figcaption></figcaption></figure>

The GXC CPE is a High-Gain Outdoor CPE 5G applications, with:

* IP67-rated customer premises equipment
* Powered by the Qualcomm SDX62 SoC
* Sub-6GHz support for 5G NR SA networks
* Compatible with n48 and n78 frequency bands
* PoE input power with a Gigabit Ethernet backhaul port

### Technology

<table><thead><tr><th width="250">Parameter</th><th>Specification</th></tr></thead><tbody><tr><td>Standard</td><td>5G NR (3GPP R16 compliant)</td></tr><tr><td>Duplex Mode</td><td>TDD</td></tr><tr><td>Frequency Band</td><td><p>n48 (3550 MHz to 3700 MHz) 2T4R</p><p>n78 (3300 MHz to 3800 MHz) 2T4R</p></td></tr><tr><td>EIRP</td><td>Up to 38 dBm @78 (PC1.5)</td></tr><tr><td>Peak Antenna Gain</td><td>≥ 9dBi</td></tr></tbody></table>

### Interfaces

<table><thead><tr><th width="250">Parameter</th><th>Specification</th></tr></thead><tbody><tr><td>Ports</td><td>1 x Gbps RJ45 (Access/PoE+)</td></tr><tr><td>SIM</td><td>Nano (4FF)</td></tr><tr><td>LED Indicators</td><td>5G, System (Green/Red)</td></tr><tr><td>Button</td><td>Reset </td></tr></tbody></table>

### Physical

<table><thead><tr><th width="250">Parameter</th><th>Specification</th></tr></thead><tbody><tr><td>Power</td><td>1 x PoE+ (802.3at compliant) - customer supplied</td></tr><tr><td>Power Consumption</td><td>&#x3C;35W</td></tr><tr><td>Ingress Protection Rating</td><td>IP67</td></tr><tr><td>Operating Temperature</td><td>-30°C to 55°C</td></tr><tr><td>Weight</td><td>2.4 lbs. (1.1 kg)</td></tr><tr><td>Dimensions (H x W x D)</td><td>9.8 x 6.4 x 2.2 in (249 x 162 x 56 mm)</td></tr><tr><td>Installation</td><td>wall or pole mount</td></tr></tbody></table>

### Global Part Numbers

<table><thead><tr><th width="250">Item</th><th>Description</th></tr></thead><tbody><tr><td>GXC-CPE-001</td><td>5G High-Gain Outdoor CPE – CBRS (n48/n78) with mounting bracket</td></tr></tbody></table>

* Specifications and ID are subject to change without notice.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gxc.io/hw/5g/5g-cpe/gxc-cpe-001-n48-n78-specification-sheet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.