Grzegorz Sikora, Business Development at OVOO The TELCO world thinks that the only way to run real-time services is to deploy it on a platform consisting of middeware like an application server. We believe that this is an old way approach and isn’t tailored to the cost-cutting, customers, management demands. Service Providers are trying to introduce agile service development but they cannot move forward because of heavy legacy solutions. On the other hand, we are about to launch a new service which should be light, low latency and works on the edge of the network. We want to show the journey from platform-centric to the cloud native approach.

1. Cloud native apps
Grzegorz Sikora

2. Who am I?
2

3. About us

4. OVOO team
OVOO company confidential 4
OVOO is a leading Polish TELCO software company.
Started in 2012 - growing organically
OVOOcado is our product line
Our numbers:
• 60+ Highly skilled specialists
• 175+ Successfully delivered projects
• 0 failed projects
OVOO: Why our offer is so unique?
• We are TELECOM experts
• We are DISRUPTIVE
• We are PROFESSIONAL
• We have a FUN

5. T-Mobile Poland
T-Mobile Austria
Magyar Telecom
T-Mobile Czech
DT Group
Hrvatski Telekom
T-Mobile Hubraum
Orange Poland - FIX part
Orange Group
Orange Poland - Mobile part
Our customers

6. 6
OVOOocad
Our product brad
OVOOcado is our brand fully focused at the product development
and offering to MNOs, MVNx, CPaaS providers.
More details at
https://ovoocado.com
OCS Service Broker PrePaid CC TAS Convergent
Messaging
GW

7. Market drivers 2020+

8. Market drivers 2020+
OVOO company confidential 8
Source EDN Network “The 5 best 5G use cases”

9. Market drivers 2020+
OVOO company confidential 9

10. 10
Real Market drivers!?

11. Technology drivers
OVOO company confidential 11

12. What is the issue with current deployments

13. Issues with current deployments
1. Lack of services separation – common middleware
2. Monolithic big application
3. Heavy regression testing because of inter-service dependency
4. Complicated deployment procedure which differs depend on test, pre-
prod, prod environment
5. Heavy acceptance tests – version rollout
6. No or limited automatic scalability – peak support
OVOO company confidential 13

14. SDP
NTS
14
MNO Network
S-CSCF/MSS
VoLTE/3G/SIP
Common
customers
Service Broker
VPN PrePaidMSIMMNP NTS
Common 1 Common 2 Common 3 Common 4 Common 5
SDP deployment challenges
Service overload
Emergency

15. 15
MNO Network
S-CSCF/MSS
VoLTE/3G/SIP
Common
customers
SDP
VPN PrePaid
MNP
1.0
Service Broker
MSIM NTS
Common 1 Common 2 Common 3 Common 4 Common 5
SDP deployment challenges
New version of service or library
MNP
2.0
Common 2
1.1

16. SDP deployment challenges
Customer specific service
16
MNO Network
S-CSCF/MSS
VoLTE/3G/SIP
Customer nicheCommon
customers
SDP
Service Broker
VPN PrePaidMSIMMNP NTS
Common 1 Common 2 Common 3 Common 4 Common 5
PoC

17. Low latency services demands
17
SDP
VPN
PrePaid
MNO
Network
Visited network Home network Backend
Internet
MNO
Network
VR V2X
VR
V2X
VR V2X
Edge cloud

18. Evolution not revolution

19. What is our proposal?
We believe in evolution instead revolution
• Step by step approach.
1. 2018-2019 – utilize existing
JainSLEE/SIPServlets platforms
and optimize the cost structure
for new services
2. 2019 – 2021 – hybrid deployment
mixing legacy and cloud native
services
3. 2021+ - Unified cloud native
deployment
OVOO company confidential 19
• HOW TO?
– Application Server based
service should be migrated to
cloud native apps
– Decoupling based on micro
services
– Containers for automated
deployment and DevOps
– Container orchestration for
scalability and management

20. Service Broker – Orchestration
20
• Horizontal
orchestration
– Business level
orchestration
– SIP and Call Control REST
– Stateful balancing
– Profile based
• Legacy and new services
orchestration
– Based on the profile the
SB can orchestrate
between new cloud based
apps and legacy JainSLEE
services
– The IMS and CS core can
trigger directly legacy SDP
platform or use SB
App 1
SB
S-CSCF/MSS
SI
P
SIP/CAP
App
2
App
3
RES
T
RES
T
SIP/CAPProfile
DB
OVOO company confidential
SDP
NTS
Service Broker
VPN PrePaidMSIMMNP
Common 1 Common 2 Common 3 Common 4 Common 5

21. SBSB
Service Broker – Scalability
21
• Different routing
algorithms
• SB pool can
orchestrate scale
up/down application
pool
• It can be either static
or fully automated
mechanism
App
1
SB
S-CSCF
SI
P
SIP/CAP
App
2
RES
T
Profile
DB
OVOO company confidential
App
3 App
4
SI
P
SI
P

22. OVOOcado Service Broker
Turn key orchestration for MNO
22
• Flexible Multi Network: 3G and 4G
• IMS and CS core integration
• Integration with 3rd party
components
• Legacy IN and SIP AS orchestration
• Pre-integrated with OVOOcado TAS
and OCS for real time rating and
fraud detection
• Low latency (reduced signaling
overhead)
• High flexibility (re-configuration on
the fly)
• TCO and TTM lower up to 80%
CS Core IMS Core
API GW
Service Broker
Service
Profile
MMTel SCC-AS
HLR HSS
Legacy
IN
Legacy
SIP AS
Other
services
OVOOcado
OCS
CAP
Ro
API
SIP
$$$
External
services

23. SIP/Diameter/SS7 application (POD)
23
Akka Library
Akka Library
JVM
JVM
Application
• Full control on signalization –
detailed access
• Effective programing
• Library not middleware
• Full control on software quality
• OVOO OCS product is based on this
technology
• Light technology
OVOO company confidential

24. REST application (POD)
24
SpringBoot
SpringBoot
JVM
JVM
Call Logic
• Common repeatable services
• IT based development
• SpringBoot based light technology
• Full control on software quality
• OVOO VPABX and MSGGW product is
based on this technology
• Currently the most popular
technology for REST services
OVOO company confidential

25. Results

26. 26
OCS and MSGGW deployment
• Project was successfully
accomplished in
September/2018.
• Since that time, the OCS is
working without any down time
• Last time we added MSG GW to
the solution (replaced legacy
one)
• The system is handling in
average 1000 TPS with pick up
to 2000 TPS
• The Average latency is 20
milliseconds

27. 27
OCS latency

28. OVOOcado OCS
Internal architecture
• Modular internal architecture
• Flexible and customizable solution.
• Integration via open standard
interfaces.
• Compliant with Telco 3GPP
standards
• Carrier grade architecture with
built-in Fault Tolerance, High
Availability and Load Balancing
features
• Flexible data model
• Provisioning, Alarm, CDR subsystem
for BSS and OSS integration
28OVOO company confidential

29. 29OVOO company confidential
MSGGW 1.0.0 GA

30. Convergent Messaging GW
Key features and benefits
● No single point of failure with capacity on
demand
● Small footprint
● A2P Messaging
● End2End security
● 100% compliant with Kannel and Jasmin
● Distributed message bus
● Flexible, plugable routing algorithm based
on multiple criteria
● Advanced business rules including content
filtering
● Cloud and on-prem deployment,
● Virtualized and docker-ized
● Mobile Number Portability
● OCS integration for PrePaid and PostPaid
online rating
30

31. IaaS
Cloud native apps - architecture blueprint
31
Service
Layer
POD (SS7)
Service1
Service4
(SpringBut)
POD (SIP)
Service1
POD API
Gateway
POD (SIP)
Service2
OVOO company confidential
OAM
PaaS
DataLayer
Cache
RA
Subscri
bers
Srv conf
Object
storage
(Swift)
Sessions
Block
storage
(Ceph)
Access
Layer
HTTP Load
Balancer
Service Broker
SS7 SIPDIAMETER
SMPP Proxy

32. Lessons learned
• Yes - you can do it.
• Yes – it works for real time services
• Is “platform” still needed?
– You don’t need platform you need the way to control the
environment
• Be aware – automatization is very cool but the first
deployment require a lot of work.
• You have to be ready for a quick deployment and
scalability

33. Thank you