| |
Bands |
Power |
s-plane |
u-plane |
m-plane |
Field test |
Pilot |
Deployment |
comment |
| ORS |
27 |
2x1W |
✅ |
✅ |
✅ |
✅ |
|
✅ |
Datasheet |
| ORS Duo |
36 |
4x1W |
✅ |
✅ |
✅ |
|
|
|
Datasheet |
| ORS Max |
8 |
2x10W |
✅ |
✅ |
✅ |
|
|
|
Datasheet |
| ORS Brute |
9 |
2x20W |
✅ |
✅ |
✅ |
|
|
(✅) |
Datasheet Deployed in China with different main board |
| Prose |
14 |
4x40W |
✅ |
✅ |
✅ |
✅ |
✅ |
|
1, 3, 7, 8, 12, 13, 14, 28, 38, 40, 41, 77, 78, 79 |
| Prose |
9 |
2x40W |
✅ |
✅ |
✅ |
✅ |
✅ |
|
1, 3, 7, 20, 12, 13, 14, 28, 40, |
| Prose |
4 |
2x80W |
|
|
|
|
|
|
5, 8, 18, 26 |
| Comba |
15+ |
4x40W |
✅ |
|
|
|
|
|
1, 3, 5, 7, 8, 20, 28, 38, 39, 40, 41, 71, 77, 78, 79, other bands available on customization |
| NTS |
15+ |
4x40W |
✅ |
✅ |
✅ |
|
|
|
1, 3, 7, 8, 20, 28, 31, 34, 38, 39, 40, 41, 77, 78, 79, other bands available on customization |
| Comleap |
11 |
4T4R / 8T8R (320W Max) |
✅ |
✅ |
|
|
|
|
1, 3, 5, 7, 8, 20, 28, 38, 40, 41, 78 |
| Abside |
3 |
72x0.5W |
✅ |
✅ |
|
|
|
|
|
| Total |
151+ |
|
|
|
|
|
|
|
|
How to join this list?
First you should read the following document: Towards interchangeable Radio Units.
In order to start integration, we will require:
- root access to the RU
- commitment to provide access to RU's m-plane source code (we do not require open source)
- if possible, no dependency on any proprietary code running on BBU/DU/CU except Amarisoft OR access to the source code of any dependency running on the BBU/DU/CU
We enforce those requirements for two reasons: (1) cyber security (2) quality assurance of m-plane integration.
if you agree with this, then the next step will be to test your RU. We will come on site with our CPRI (Split 8) BBU/DU/CU for a test session. We also support eCPRI (Split 8). We will the ensure that s-plane and u-plane can be configured. It should usually take between 15 minutes and 4 hours. About 66% RU vendors fail this test due to inability to adapt IQ mapping or other reason. Please read the following document for preparing the test procedure: RU Integration Test Procedure (requirements,preparation, sync plane, user plan, test procedure, supported CPRI specs).
Then we will send a questionnaire, usually under NDA (but we are OK to share it publicly if you prefer transparency). This questionnaire will assess your product and corporate strategy in terms of digital resilience and market match.
Then we will start m-plane integration. We will verify our core requirements:
if our requirements are not met, we will need to analyse the suitability of the RU m-plane through extensive documentation provided to us.
Then we will integrate your RU completely.
The complete process takes between 3 months and 12 months. It will require effort on both sides, mainly on Rapid.Space side.