> 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-network-mobile-kits/one-box-solution-gxc-5g-mobile-kit/one-box-quick-start-guide/equipment.md).

# Equipment

<p align="center"><strong>One-Box Solution</strong></p>

<figure><img src="https://4084968256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgSxa0NIdBp5aDw7Lf2N9%2Fuploads%2FaSnaFL2nOQN8NIyWhKAV%2Fimage.png?alt=media&amp;token=2230fec6-8a61-49ae-889c-0e9ee66275ac" alt=""><figcaption></figcaption></figure>

## Equipment in Kit

* Customized, weather-resistant, TSA-compliant travel case containing:
  * 1 pc. pre-wired GXC-SER-002 Onyx Edge preloaded with Onyx Connect software
  * 1 pc. pre-wired high-power 24 to 56 VDC 802.3bt-compliant PoE Injector
  * Various panel-mounted connectors and switches for user interface
* 1 pc. Askey SCE2120 indoor integrated base station (gNB)
* 1 pc. 5G dongle with pre-programmed 5G UE SIM card
* 4 pcs. pre-programmed 5G UE SIM cards (USIMs)
* 5 pcs. provisioned and ready-to-activate eSIM profiles
* 1 pc. 160 Watt, 24 VDC output AC/DC industrial power adapter for powering the mobile kit
* 1 pc. North America Standard 6 ft. NEMA 5-15P power cord for the power adapter
* 1 pc. 7 ft. Shielded Cat5E (STP) patch cable (for connection between One-Box and SCE2120)

## Equipment Provided by the Customer

* Ethernet/Cat6 cable for Internet backhaul
* Band n48, n77, or n78 compatible end-user device(s)

\* 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-network-mobile-kits/one-box-solution-gxc-5g-mobile-kit/one-box-quick-start-guide/equipment.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.