Publishing Our First Research Paper in Telecommunication

During my final year studying Telecommunication Engineering, my friends and I did something I once thought was reserved for PhD students: we published a research paper. Here’s how it happened and what I learned.

The Beginning

It started with a course project. Dr. Abdullahi, our Wireless Communications professor, assigned us to analyze a specific aspect of 5G network optimization. My group—four of us who always sat in the back row—decided to take it seriously.

We were:

• Me: Interested in the theoretical modeling
• Ibrahim: The coder who could implement anything
• Fatima: The detail-oriented one who caught every error
• Aminu: The writer who made complex ideas readable

The Research Process

Finding the Gap

We spent weeks reading papers. Not skimming—actually reading, highlighting, arguing about methodology. We noticed that most existing work on network slicing optimization used centralized approaches. Very few explored distributed algorithms for resource allocation in ultra-dense networks.

That became our angle.

The Grind

For three months, we:

• Ran simulations at 2 AM because that’s when the lab computers were free
• Debugged MATLAB code that refused to converge
• Rewrote our literature review four times
• Discovered that our “brilliant” idea had been done in 2019 (and pivoted)

The Breakthrough

The moment everything clicked was mundane. Ibrahim was tweaking a parameter in the simulation while I was complaining about the theoretical model not matching results. Fatima pointed out that our channel model was wrong for the scenario we were simulating.

We fixed the channel model. The results made sense. The paper wrote itself after that.

The Submission

We aimed for a national conference—ambitious for undergraduates, but our supervisor believed in us.

The process:

1. Draft: Aminu wrote the first version in a week
2. Review: Our supervisor tore it apart (constructively)
3. Revise: Three rounds of major revisions
4. Submit: Clicked “submit” at 11:58 PM on the deadline day
5. Wait: Six weeks of anxiety

Getting Accepted

The acceptance email came on a Tuesday. I was in the middle of a lecture and had to step out. I called Ibrahim first, then we made a group call. We screamed like we’d won the lottery.

We hadn’t. But for four undergraduates from Nigeria, getting a paper accepted felt like validation that we could contribute to global knowledge.

What I Learned

1. Research is Messy

The final paper looks clean and logical. The process was chaotic, full of dead ends, arguments, and moments of despair. Science is human work.

2. Team Matters More Than Individual Brilliance

None of us was the smartest person in our department. But together, we covered each other’s weaknesses. Ibrahim’s coding plus Fatima’s rigor plus Aminu’s writing plus my modeling—this combination worked.

3. Persistence Beats Talent

The difference between published and unpublished research often isn’t brilliance—it’s willingness to do the boring revisions, run the extra simulations, and submit one more time after rejection.

4. Academic Writing is a Skill

Our first draft was terrible. By the fourth revision, we’d learned how to structure arguments, cite properly, and write for a specific audience. Writing is learnable.

The Paper

Title: “A Distributed Resource Allocation Algorithm for Network Slicing in Ultra-Dense 5G Networks”

Conference: Nigerian Society of Engineers Annual Conference 2025

Abstract: We proposed a game-theoretic approach to resource allocation that improved spectrum efficiency by 18% compared to baseline methods.

Reflections

Publishing this paper while building a startup and maintaining good grades taught me that capacity expands to fill meaningful work. I thought I was too busy. I wasn’t—I was just prioritizing less important things.

The skills I learned:

• How to read academic literature quickly
• How to structure complex arguments
• How to work in a team under pressure
• How to handle rejection and revise

These transfer directly to entrepreneurship. Reading papers is market research. Structuring arguments is pitching. Working in teams is cofounder dynamics. Handling rejection is startup life.

For Students Reading This

If you’re an undergraduate who thinks research is for graduate students, you’re wrong. Find a professor who will guide you. Find friends who will grind with you. Pick a problem that genuinely interests you. And submit the paper—even if you think it’s not ready. You’ll learn more from the review process than from another semester of coursework.

The barriers are lower than you think. The work is harder than you expect. And the satisfaction is greater than you can imagine.