Products
  •  
  • Yate
  • YateUCN
  • YateHSS/HLR
  • YateBTS
  •  
| Open Source
  •  
  • Yate
  • YateClient
  • YateBTS
  • Freesentral
  •  
| Documentation
  •  
  • Getting Started
  • How To's
  • Documentation
  • Compatibility
  •  
| Community
  •  
  • SVN
  • Discord
  • IRC
  • Mailing List & Archives
  • Forum
  • Partners
  • Report a bug
  •  
| Contact | Blog | Shop Old website
Products
Open Source
Documentation
Community
Contact
Blog
Shop
 Yate YateUCN YateHSS/HLR YateBTS   
Products
Yate
YateUCN
YateHSS/HLR
YateBTS
YateUCN

    Unified EPC/IMS core network

    The YateUCN is a unified core network solution intended for new LTE networks, for upgrading GSM/GPRS networks to LTE or for extending existing LTE networks.

    The YateUCN software-defined core implements all the functions and protocols of the LTE core network in software, and uses commodity hardware. It integrates the EPC layers - MME, PGW, SGW, PCRF, and PCEF. The YateUCN also includes the IMS layers for VoLTE - PCSCF, ISCSCF, IWF, and BGW.

    It communicates with the YateENB (LTE eNodeB module) over S1AP and GTP protocols and uses a JSON API for configuration and management.

    Unified GSM/GPRS core network

    The YateUCN also implements the functions and protocols of GSM/GPRS core networks. In a GSM/GPRS network, the YateUCN acts as a MSC/VLR/SGSN/GGSN/GMSC in a single server.

    It connects to the YateBTS (GSM module) over GTP and SIP, replacing the 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.

    The unified core network solution is based on replacing the eNodeB with the YateENB (LTE) and the base station subsystem with the YateBTS (GSM).

Features and Benefits

Runs on commodity hardware, allowing for a simplified network architecture and lower deployment costs.
Enables carriers to deploy 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.
The SIP protocol establishes connection between the YateUCN and the YateBTS, allowing the SatSite base station to communicate with any YateUCN in the network. A Base Station Controller (BSC) is not needed between the YateBTS-powered SatSite and the YateUCN.
Has low idle traffic, which allows transport technologies like satellite.

Dell PowerEdge R4303.5" Chassis with up to 4 Cabled Hard Drives
ProcessorIntel Xeon E5-2630 v3 2.4GHz,20M
Memory8GB RDIMM, 2133MT/s, Dual Rank, x8 Data
Hard Drives1TB 7.2K RPM SATA 6Gbps 3.5in Cabled Hard
Hard Drive Configuration RAID 1 for H330/H730/H730P (2 HDDs) with Cabled Chassis
Internal controllerDVD ROM SATA Internal for 4HD Chassis ReadyRails Sliding Rails With Cable
Power Supply550W
Network AdapterIntel Ethernet I350 DP 1Gb Server Adapter, Low Profile
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
- E.164
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 sessions)
   - 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
Support
Forum
IRC Channel
Documentation
Mailing list
Products
YateUCN
YateHSS/HLR
YateBTS
Information for
Developers
Journalists
Yate
Current stable release
Why Yate?
Feature list