Core capabilities
Technical specifications, verification scope, and limits for a 1sc Core lab evaluation.
Scope
This page covers the proprietary Rust 1sc Core in a hosted 5G Standalone lab. It does not describe free5GC or Open5GS. Record the selected implementation and exact runtime version with every result.
A feature selection is not a test result. Mark a capability verified only when a completed test identifies the deployment, runtime version, configuration, equipment, and supporting evidence. Otherwise mark it unverified.
Technical specification
| Item | Scope |
|---|---|
| Deployment | One dedicated EC2-hosted core per deployment. The deployment form shows the managed region. |
| Network functions | AMF, SMF, UPF, AUSF, UDM, UDR, NRF, NSSF, and PCF in the default core. |
| Radio mode | 5G Standalone. Use a gNB and UE configured for SA. |
| N2 | gNB to AMF: NGAP over SCTP, port 38412. |
| N3 | gNB to UPF: GTP-U over UDP, port 2152. |
| Network identity | Use the deployment radio package for PLMN (MCC/MNC), TAC, S-NSSAI (SST/SD), and DNN. Do not copy values from another deployment. |
| Subscriber authentication | Use matching SIM and core subscriber authentication data. Keep the key and OPc in the agreed secure transfer system. |
| Data network | The deployment form offers Lab ICMP responder and External IPv4 network with NAT. Select the mode before the test. |
| Radio transport | The deployment form offers Direct N2 and N3 and Certificate-authenticated IPsec. Agree on routing and certificate preparation before using IPsec. |
Capability and evidence
| Capability | Available scope | Verification required |
|---|---|---|
| Registration and authentication | Hosted UERANSIM attach procedure. | Registration and authentication results for the selected deployment; repeat with the named physical UE and SIM. |
| PDU session and UE address | Hosted UERANSIM session procedure. | Session established, assigned IPv4 address, DNN, and slice recorded. |
| Lab packet path | Built-in ICMP responder. | Record the actual target, sent/received count, loss, and RTT. This does not prove external traffic. |
| External IPv4 traffic | External IPv4 network with NAT is selectable. | UE-originated ICMP, TCP, and UDP to a separate server, with return traffic. A server process on the core VM alone is insufficient. |
| Physical gNB and UE | Compatibility is unverified until a named equipment profile passes. | Record vendor, model, software, SIM profile, and repeatable registration, session, and traffic results. |
| Recovery and invalid credentials | Separate tests in the evaluation plan. | Record disconnect/reconnect, restart recovery, and rejection results. Do not infer these from a successful attach. |
| Capacity and performance | No capacity or throughput guarantee on this page. | State UE count, offered load, duration, core resources, network path, and measured results. |
| Handover | Not supported by the current general mobility procedure. | Exclude from first-phase acceptance. Agree on a separate implementation and test scope if required. |
Limits
No broad hardware compatibility, full 3GPP conformance, or O-RAN certification is claimed here. An end-to-end test applies only to the tested system and configuration. A hosted status of Verified is not a certificate.
IPv6, voice/IMS, roaming, charging, third-party UPF/PFCP integration, and guaranteed QoS are outside this evaluation scope. Obtain a separate support statement before making them acceptance requirements.