> 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/lte/4g-mesh-nodes/gm02/gm02-mesh-node-installation-guide/introduction-and-features.md).

# Introduction and Features

GXC's GM02 Mesh Node provides wireless backhaul between a GXC Gateway (donor) Node and a GXC Access Point (AP). This is accomplished through self-interference mitigation techniques that allow for access and backhaul carriers to co-exist in CBRS Band 48. A GXC Mesh Node in conjunction with a Mesh AP provides CBRS coverage for UE utilizing wireless backhaul to the Gateway Node.

Combined with the GXC Onyx Platform for orchestration, management, and SAS registration, the Mesh Node offers coverage extension and rapid deployment where wired infrastructure is unavailable.

<p align="center"><strong>GM02 Mesh Node</strong></p>

<figure><img src="https://4084968256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgSxa0NIdBp5aDw7Lf2N9%2Fuploads%2F7sUUgCWDOKV7bipRP2WJ%2Fimage.png?alt=media&amp;token=7d33beb2-528c-40a3-b5ba-95055c6beec3" alt="" width="563"><figcaption></figcaption></figure>

## Onyx Platform Features

The Mesh Node is a part of the GXC Onyx Platform that ties together multiple hardware and software elements to bring a full solution to enterprise.

The Onyx Platform provides an enterprise network based on a Cellular Mesh architecture. This private network platform provides high levels of resiliency, flexible deployments, strong coverage in hard-to-reach areas, and a powerful distributed application platform. Mesh nodes are connected via integrated wireless backhaul without the need for fiber or Ethernet cables.

The Onyx Platform features:

* Mesh-based RAN
* Indoor and Outdoor APs
* On-premises core network (available as a hardware appliance, machine image, or edge machine image)
* A robust network management platform tied together with a single pane of glass controller presented as a web-portal

<p align="center"><strong>GXC Onyx Platform Architecture</strong></p>

<figure><img src="https://4084968256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgSxa0NIdBp5aDw7Lf2N9%2Fuploads%2FM6sVoLzjhszVKrI2XhWH%2Fimage.png?alt=media&amp;token=724aee1a-c5b2-4a89-b2f9-c01ef30a5c9a" alt=""><figcaption></figcaption></figure>

## GM02 Mesh Node Features

The GM02 Mesh Node, which operates in the Citizens Broadband Radio Service (CBRS) Band 48, is suitable for private and public deployment and indoor or outdoor applications with an IP66 rated enclosure. It can be wall or pole mounted.

The GM02 Mesh Node’s core differentiating technology is its ability to connect APs wirelessly to provide ultra-dense, reliable networks without the need to build upon existing wired infrastructure. It utilizes the same spectrum for backhaul (node-to-node) connectivity, and access (node-to-device) which simplifies radio planning and allows for design portability anywhere in the U.S.

The GM02 Mesh Node has multiple external antenna options for both access and backhaul allowing for customized deployments – providing coverage where it is most needed. Its low power consumption is suitable for off-grid solar power applications.

The GM02 Mesh Node features GUI-based remote Web management, with local Wi-Fi diagnostic access to simplify installation.

{% hint style="info" %}

### Watchdog Service

The Watchdog service monitors the Mesh Node’s system health. Should critical service failures occur, the Mesh Node undergoes a power cycle, subsequently triggering the Onyx Portal “Watchdog Powercycle” alert, which includes a description of the failure. The Watchdog service ensures the Mesh Node system's reliability and availability.
{% endhint %}


---

# 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/lte/4g-mesh-nodes/gm02/gm02-mesh-node-installation-guide/introduction-and-features.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.