YateUCN is a unified core network solution intended for new GSM/LTE networks, upgrading GSM networks to LTE or for extending existing networks.
YateUCN software-defined core implements all the functions and protocols of GSM and LTE core networks in software, and uses commodity hardware. YateUCN integrates the MSC/VLR/SGSN/GGSN and GMSC nodes from the GSM/GPRS core network and the SAE/VoLTE layers from the 4G LTE network in a single server.
The unified core network solution is based on replacing the base station subsystem with YateBTS (GSM) and the eNodeB with YateENB (LTE). YateUCN communicates with YateBTS/YateENB using the SIP/S1AP/GTP protocols, instead of the more costly SS7 MAP-A interface (BSSAP protocol). This leads to a higher return on investment without affecting the reliability of the network or the provided services.
YateUCN uses a JSON API for configuration and management.
Features and benefits
YateUCN runs on commodity servers, allowing for a simplified network architecture and lower deployment costs.
Enables carriers to deploy 4G LTE networks with reduced initial investment.
Allows for scaling as you go. You can add more servers or separate the functionality as more users adopt your service.
Increases network resiliency. In case of equipment failure you can easily configure another server to take up the functions of the fault node.
SIP protocol establishes connection between YateUCN and YateBTS, allowing SatSite base station to communicate with any YateUCN in the network. No BSC is needed between YateBTS-powered SatSite and YateUCN.
Has low idle traffic, which allows using transport technologies like satellite.
|SS7 Connectivity||- SIGTRAN, SCTP with CRC checksum |
- M2UA, M2PA, M3UA
- ITU MTP, SCCP, TCAP
- ANSI MTP, SCCP
- ITU MAP v3
- CAMEL phase 2
|Voice interconnect||- SIP and RTP|
- ISUP using external MGCP gateway
|SCCP GTT||- E.212 (ANSI)|
- E.214 (ITU) translation table
|MSC/VLR||- ETSI MAP v3 |
- Supported operations:
- MSC <-> AuC messages (authentication)
- MSC <-> EIR messages (equipment identification, optional)
- VLR <-> HLR messages (location management, roaming)
- MSC <-> SMSC messages (SMS)
|SGSN/MME||- ETSI MAP v3|
- S1AP r11
- GTP v1
- Supported operations:
- SGSN <-> AuC messages (authentication)
- SGSN <-> EIR messages (equipment identification, optional)
- SGSN <-> HLR messages (data mobility management, roaming)
- SGSN <-> GGSN messages (data session)
- YateENB <-> SGSN messages (LTE control and user data)
- YateBTS <-> SGSN messages (GPRS control and user data)
|SIP||- Supported standards (RFC3261)|
- Registrar function
- B2BUA for calls
- RTP (RFC3550) with sideband DTMF (RFC2833)
- SMS and USSD over IP
|SMS||- Format: SMS PDU (MO and MT)|
- MAP/SS7 transport (T-PDU format)
- SIP MESSAGE transport (SMS over IP, R-PDU format)
|CDR||- File format|
- Rotation interval
- File transfer: FTP
|Dell PowerEdge R510||PE R510 Chassis for Up to Four 3.5" Cabled Hard Drives, LED|
|Processor||Intel Xeon E5606 2.13GHz, 8M Cache, 4.8 GT/s QPI, 4C|
|Memory||8GB Memory (2x4GB), 1333MHz Dual Rank LV RDIMMs for 1 Processor, Advanced ECC|
|Hard Drives||2 x 500GB 7.2K RPM SATA 3.5in Cabled Hard Drive|
|Hard Drive Configuration|| RAID 1 for PERC/SAS 6ir, PERC H200/H700 Controllers, x4 Chassis|
|Internal controller||SAS 6/iR Integrated with PERC,SAS 6/iR Cable, 4HD|
|Power Supply||480 Watt Non-Redundant|
|Network Adapter||2x Intel PRO 1000PT 1GbE Single Port NIC, PCIe1|