YateUCN is a powerful equipment in the Core Network, it handles both VOICE and DATA for the Telecom network, regardless of the used radio technology.
Unified EPC/IMS core network
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 (e.g. Dell PowerEdge R430).
YateUCN integrates the EPC layers – MME, PGW, SGW, and PCEF and 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
YateUCN also implements the functions and protocols of GSM/GPRS core networks. In GSM/GPRS, 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).
Many areas in the world are not covered by a cellular network due to the cost of existing circuit-switched network technology.
YateUCN brings a new solution for deploying GSM/LTE networks at a lower cost.
Supported Codecs
YateUCN only supports the following codecs of the ITU-T standard, G.711 [also titled as Pulse code modulation (PCM) of voice frequencies]:
- A-law (PCMA, G.711A)
- μ-law (PCMU, G.711U)
YateUCN
Unified LTE/GSM+GPRS core network, including SGSN, GGSN, GMSC, MME, SGW, PGW
See the product here ››
YateUCN, the Unified LTE/GSM/GPRS Core Network
This section contains information about the unified YateUCN.
-
General information about YateUCN, as an LTE/GSM/GPRS core network server.
-
Configuration parameters necessary for each mobile network node type.
-
General information about the JSON API and how you can use it for node configuration, set up or management.
-
This is used for clients with more than one EnodeB equipment connected to a CORE Network
-
Instructions on how to use the JSON API to configure YateUCN.
-
Instructions on how to use the JSON API to retrieve information about node statistics, data sessions and more.
-
Learn how to configure YateUCN using YateMMI.
-
Learn how to change network name through YateUCN.
-
Generic information about the YateMMI management interface.
-
Generic information about licensing system.
-
Learn how to configure zabbix module to send performance data to Zabbix server.
-
Generic information about the CDRs in all Yate packages.
YateUCN as an MME/SGW
This section contains information about configuring YateUCN’s MME and SGW functions.
-
Information about how to connect your own eNodeB equipment to our equipment.
YateUCN as an GGSN/PGW
This section contains information and configuration examples used for charging functions.
-
Information about how to configure YateUCN charging interfaces.
-
General information and examples of iptables on YateUCN for the GGSN/PGW.
YateUCN as MSC/VLR
This section contains information about the usage of YateUCN as MSC/VLR.
-
General information about MSC/VLR.
-
Information about our solution for obtaining redundant MSC/VLR.
YateUCN as an IMS
This section contains information about configuring YateUCN for IMS
-
General information about the YateUCN IMS CSCF.
-
Configuring the YateUCN IMS CSCF.
-
Information about setting up a SIP listener for outbound calls.
Latest Changes
| Revision number | Time since commit | Commit message |
|---|---|---|
| 4067 | 13h 48m | Added function to report unsupported MAP operations only if allowed by its class. |
| 4062 | 8d 19h | Fixed confusing trace messages. |
| 4060 | 13d 20h | Allow set_ifcs to be set from extra params. |
| 4059 | 13d 20h | Fixed ifcs property array type check. |
| 4054 | 15d 22h | Changed default handler priorities so local NPDB is used before MNP server. Added regexroute sections for porting and roaming checks. |
