evolution of telecom software
DESCRIPTION
Evolution of Telecom Software. Perspectives from a Software Engineer Dr. Jey Veerasamy. Background: Education. BE Electronics and Communication Engineering, Anna University, India 1986-90 MS Computer Science @ UTD, 1991-94 PhD Computer Science @ UTD, 1994-99 - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/1.jpg)
Evolution of Telecom Software
Perspectives from a Software Engineer
Dr. Jey Veerasamy
![Page 2: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/2.jpg)
Background: Education
• BE Electronics and Communication Engineering, Anna University, India 1986-90
• MS Computer Science @ UTD, 1991-94• PhD Computer Science @ UTD, 1994-99– Dissertation: Graph algorithms - improved
approximation algorithms for tour problems
![Page 3: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/3.jpg)
Background: Software Engineer
• Mobile Switching Center (MTX) software, BNR/Nortel, 1994-97– Developed features on MTX platform
• Base Station & Base Station Controller software, Samsung Telecom America (STA), 1997-2010– Limited development, worked more on requirements
& post-deployment support– Performance trending, troubleshooting &
optimization
![Page 4: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/4.jpg)
Wireless network : Block Diagram
Source: Wiki
![Page 5: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/5.jpg)
Snapshot : 1991
• Cost for one minute US India phone call?• $2.20• Cost for one minute Dallas SFO phone call?• Anywhere from $0.25 to $0.60• Long distance carrier business was great!
![Page 6: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/6.jpg)
Snapshot: 1994
• Telecom companies were doing very well. • Focus on Features, capacity & reliability • New employees: 6 month honeymoon period • All UTD CS/EE graduates: – First stop: Nortel– 2nd stop: Ericsson– 3rd: time to think
![Page 7: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/7.jpg)
1994: Software development Environment
• Waterfall model – Documentation heavy– Reviews can be brutal or boring– Weekly load-build was a big deal
• Proprietary real-time Operating Systems, HW & programming languages, even homegrown source code config. control software!
• Why? Limited processing power, exercise full control, concerns over reliability & source code leaks …
• Reluctance to try new tools/environments
![Page 8: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/8.jpg)
1994: Telecom Software Engineer
• Concerned about marketability of skills, but not worried about job security
• Typical work week:– <50% spent on design work, – ~30% spent on learning standards,– ~20% spent on testing
• Expensive & complex lab equipment: – 4 hours in setup & 2 hours in testing
• Who knew the acronyms?
![Page 9: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/9.jpg)
Concepts: BHCA capacity
• Busy Hour Call Attempts• 1 Million BHCA central processor should
spend < 2.5 milli-second per call (assuming 70% load)
• Managing BHCA is a “system engineering” activity, done in every software release.
• Per-call measurements & optimization
![Page 10: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/10.jpg)
Capacity issues
• 2 types of nodes: – control nodes – transaction processing – CPU load
can vary a lot (>60% load is a concern). Use watch-dog timers that automatically reset the node if 100% sustained CPU load is seen.
– traffic nodes – actual traffic processing – can safely operate at 90% CPU load
• Power of Trending
![Page 11: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/11.jpg)
Handling Overload
• Overload can occur during mega-events or new years day
• Similar to “Denial of Service” attack• Need to shed call requests with minimal
effort. • Goal is to handle as many requests as possible
in reliable manner.
![Page 12: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/12.jpg)
Magic of CDMA
Single Frequency Channel operation
Soft Handoff
Coverage vs. Capacity
![Page 13: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/13.jpg)
Concept: Real-time OS
• Traffic processing: every 20 msec once, for each call– load distributed by frame offsets (1.25 msec)
• Control processing• Diagnostic processing
![Page 14: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/14.jpg)
Concept: Hard vs. Soft real-time
![Page 15: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/15.jpg)
Magic of “always connected”
• IP was not designed for mobility.• All IP traffic towards the mobiles is terminated
at specific node in wireless network. That node takes care of delivering it to mobile using tunneling protocols – also known as “Mobile IP”.
![Page 16: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/16.jpg)
Redundancy
• Is it for hardware or software?• Control nodes: Active/Standby redundancy • Traffic nodes: N+1 redundancy• Load sharing algorithm?• Round-robin or load-balancing• Leaky bucket?
…
![Page 17: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/17.jpg)
Interesting SW bugs
• Look at the following code:if (sector_id = 1)
… Send call setup message to ALPHA
• Lab tested the code in alpha sector. • What happens when this code is applied to
field?
![Page 18: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/18.jpg)
Blocking printf()
• Debug port used for logs• printf() was used to output messages – cannot
use break points due to timers• CDMA works based on GPS time• Timing drift is not good for soft handoffs
handoff failures• More time spent in printf() less time in
actual call processing less capacity
![Page 19: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/19.jpg)
Working with limited pipe
• There are two types of messages over the air:– Acknowledgement required– No ack required
• I changed neighbor information message type to improve soft handoff success.
• Resulted in more handoff failures, since actual handoff processing related messages could not get through.
![Page 20: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/20.jpg)
BSC crashes
• Unexpectedly long message or spurious content from mobiles causes buffer overrun
• Fixed size stack was used in OS – more local variables added over time.
![Page 21: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/21.jpg)
Software efficiency: Do we really care?
• Goal is to make software work & meet deadline for most industry projects.
• Game console: Algorithm takes longer to run requires higher-end CPU to keep realism higher price product fails amid competition
• Web-server: Algorithm takes longer to run (consider 5 seconds vs. 20 seconds) tests web-users’ patience & requires more web server capacity.
• Daily data crunching: What if it takes >1 day?
![Page 22: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/22.jpg)
Snapshot: 2011
• All long distance-only carriers disappeared several years ago.
• Too efficient for our own good • All-you-can-eat or bucket plans – Data usage
picking up – carriers struggling to keep up• “Cost reduction” or efficiency is the goal!• New interns – help out with testing in the lab on
day #1 • Continuous fight between Quality & deadlines.
![Page 23: Evolution of Telecom Software](https://reader035.vdocuments.us/reader035/viewer/2022070500/56816885550346895ddf02e9/html5/thumbnails/23.jpg)
2011• Smart phones generate lot of data traffic even when
the user is sleeping! “Femtocells” appealing to carriers.
• IP has become acceptable protocol.• Real-time Linux is popular OS used in lots of
telecom nodes.• Management nodes use Sun WS with Java
applications & web browser.• Real-time nodes tend to use C/C++.• Focus has shifted to applications for smart-phones.