ORS其他问题请查看： https://handbook.rapid.space/ors
1、提供一下组网的网络拓扑图
Please explain the network architecture of the ORS and whether it is necessary to deploy additional wireless network management and gateways.
https://handbook.rapid.space/ors/rapidspace-Faq.Network.Architecture.Of.ORS
2、各个网元的性能参数和技术指标
3、组网要求以及其他
Please elaborate on the technical solutions for multi-cloud deployment of the product and the requirements for the bearer network?
The technology we use for multi-edge / multi-cloud is called SlapOS:
We recommend taking a look at the following presentations:
This technology has already been deployed on the following clouds:
- Aliyun
- Tencent
- UCloud
- Qingcloud
- AWS
- Azure
- OVHCloud
- Scaleway
- Hetzner
- Rackspace
- VMWare
- Contabo
- etc.
The table below explains how it compares to OpenStack and Kubernetes.
| |
SlapOS |
OpenStack |
Kubernetes |
| SDN |
✅ |
❌ |
❌ |
| NOS |
✅ |
❌ |
❌ |
| vRAN |
✅ |
❌ |
❌ |
| Global CDN |
✅ |
❌ |
❌ |
| OSS/BSS |
✅ |
❌ |
❌ |
| Self-converging |
✅ |
❌ |
❌ |
| Self-monitoring |
✅ |
❌ |
❌ |
| Self-accounting |
✅ |
❌ |
❌ |
| DR automation |
✅ |
❌ |
❌ |
| Portability (Linux to Linux) |
✅ |
✅ |
❌ |
| Portability (POSIX to POSIX) |
✅ |
❌ |
❌ |
| Hard real-time |
✅ |
❌ |
❌ |
| Shared services |
✅ |
❌ |
❌ |
| Delegated services |
✅ |
? |
? |
| Free of export restrictions |
✅ |
❌ |
❌ |
In summary, SlapOS does everything needed to deploy a complete edge or cloud across multiple infrastructure providers. The closest equivalent to SlapOS is Google Kubernetes + Anthos or some of the products provided by Virtuozzo (Swiss). However, only SlapOS is fully open source.
Regarding the backhaul network (translated in the question as bearer network), we can support virtually any backhaul. All we need is TCP/IP, preferrably IPv6 but IPv4 is also OK.
For our own deployment, we use a technology called re6st:
We recommend reading the following presentation:
re6st provides a flat IPv6 addressing of all nodes in our edge cloud, including ORS base stations and nodes present in other infrastructure (ex. Aliyun, AWS). It acts as a layer-3 overlay which can circumvent congestion and minimize latency between all nodes.
It is an essential tool for multi-cloud, multi-edge deployment. Without re6st, multi-cloud or multi-edge does not work due to all sorts of network incidents that exist in inter-cloud networks. The more nodes in different cloud providers, the more network incidents.
Latest versions of re6st are support deterministic real-time (TSN) for Industry 4.0 field bus (OPC-UA) or best effort real-time for safety networks (industrial automation) or signaling (transponder network in drones).
4、承载业务种类和延展性
5、实际运营商的应用情况，和第三方厂家设备的兼容性如何（包括后台支撑系统，传输，无线覆盖区域切换等）？
6、实际做过的区域的覆盖效果图，在网络上运营的业务数据(话务量，数据量，等）
https://handbook.rapid.space/ors/rapidspace-Faq.What.Is.The.Field.Test.Report.of.ORS
7、有没有第三方，或者运营商的检测报告，如果有提供一下。
8、另外，一个基站同时使用的手机数量能做到多少？
We will define three types of UEs:
- registered: the UE SIM ID is present in the HSS database;
- connected: the UE is connected to the 4G/5G network but idle;
- active: the UE is connected to the 4G/5G network and downloading or uploading.
The limits of ORS are:
| |
Design limit |
Typical practical limit |
Limiting factor |
| Registered UEs |
No limit |
1,000,000,000 |
Size of HSS database |
| Connected UEs |
No limit |
1,000 (4G) 500 (5G) |
RAM/CPU |
| Active UEs |
No limit |
100 |
Network congestion (3GPP standard) |
See test report with UEs: