Shravan Kumar B

Email Id:friendsofshravan@gmail.com
Phone: +91-8897018481

Career Objective:
To be a part of a reputed organization, contributing to it professionally and personally,
where my innovative skills are utilized to its optimal use and to be able to extract ideas in
order to transform them into realities
Professional Summary:

A technocrat with 8 months of experience in NOC (Network operation center),

Client Servicing and Troubleshooting/Technical Support.
Adept in analysing information Network needs, and troubleshooting.
An effective communicator with significant experience working with steering
committees and others.
Associated with TULIP Telecom Ltd. from Reliable HR Private Limited has Service
Engineer in NOC (Network operation Centre) from September-2011 to March-2012.

Expertise:

Bachelor of Electronics & Communications with knowledge in 3G/UMTS (L1,L2,L3)

Protocol Stack Development domain

Experience in all phases of product life cycle including Software Requirement Analysis
(SRA), High Level Designing (HLD), Low Level Designing (LLD)

Excellent understanding of Radio interface (Access stratum) Protocol Stack.

Better understanding of Physical Layer (L1), Medium Access Control (L2), Radio Link
Control (L2), Packet Data Convergence Protocol (L2), Broadcast & Multicast Control
(L2), Radio Resource Control (L3) protocols & working architecture

Well versed with 3GPP Specifications TS 25.331

Basic Knowledge of Non Access Stratum (NAS) Protocol

3GPP Technical Specifications study and requirements analysis

Protocol Stack Testing Development

Good communication and presentation skills

Skills:
Operating Systems
Languages
Packages
Technical

: Windows XP, Windows 7

:C
: MS office
: Computer Hardware Maintenance
Description:

Project 1:

Project Name
RELEASE

: RRC CONNECTION

Actually RRC connection establishment is

always initiated by UE but RRC Release is
always initiated from the network side. There
are two versions of this procedure depending
on whether a DPCH exists or not, the
network sends an RRC Connection release
message and the UE responds with an RRC
Connection release complete.
If a dedicated physical connection
exists, then it is used for the transport of
these messages. Both messages are sent using
unacknowledged mode in the lower layers.
The UE may send its response message
several times and after the last transmission,
it releases all its radio connections .Similarly
the UTRAN releases all UE dedicated
resources after receiving the complete
message. This is done once a corresponding
timer expires, even if it doesnt receive the
connection release complete message.
If there is not a dedicated connection,
then the downlink RRC connection release
message must be sent via FACH, and the
uplink RRC connection release complete
message via RACH. Only one occurrence of
both messages is sent, and the acknowledge
mode is used. This means that a data
acknowledgment message is sent as an
acknowledgment in the RLC protocol level to
the RRC connection release complete
message via the downlink FACH.

Responsibilities:

Study of 3GPP Specs TS 25.331, TS 34.123 and writing the test requirements.
Familiar with trace analysis tools. Execution of the test specification in the ASN1C
Compiler.

Identification and review of Test Cases and Test execution

Logging defects into defect tracking tool and Analysing/tracking them to closure.
Documenting test reports, defect reports, and bug reports.
Supporting activities on external team issues and good debugging skills
Good knowledge and practice of Verification process , test methodologies and
Quality
initiatives

Project 2:

Description:

Project Name
: RRC CONNECTION
ESTABLISHMENT

The RRC Connection establishment is initiated

by UE RRC and that will terminated by UTRAN
RRC. The NAS (core network) of UE get
triggered by core network of core network
through paging message. The network RRC
respond with RRC connection setup message,
the network can also reject the connection setup
and respond with RRC connection reject. The
RRC connection setup message contains the
information to be used in the L1/L2
configuration.
This includes transport format set, TTI,
physical channel information. Once the UE RRC
receives either RRC connection message or
failure message UE-RRC will send RRC setup
complete message.
It is possible that several UE have sent
the RRC connection request message via RACH
at the same time. RRC must store the value of
initial identity of UE encapsulated in RRC
connection request message and again same
value will be return by in RRC connection setup
message. If this value gets matched, the RRC
connection setup gets established otherwise UE
has to send the connection request once again.

Responsibilities:

Study of 3GPP Specs TS 25.331, TS 34.123 and writing the test requirements.
Familiar with trace analysis tools. Execution of the test specification in the ASN1C
Compiler.
Identification and review of Test Cases and Test execution
Logging defects into defect tracking tool and Analysing/tracking them to closure.
Documenting test reports, defect reports, and bug reports.
Documentation for High Level Design and Low Level Design.

Interact with product development team to provide best possible solution to customer
requirements
Supporting activities on external team issues and good debugging skills
Developing codes in C and UNIX
Good knowledge and practice of Verification process , test methodologies and Quality
initiatives

Education:
University / Board
Jawaharlal Nehru
Technological
University, A.P
Board of
Intermediate
Education,A.P
Board of Secondary
Education, A.P

Qualification
B.Tech(ECE)

Percentage
62.23

Year
2011

MPC

70.4

2006

SSC

69

2004

Extra-Curricular Activities:

NCC cadet in 2007-2009.

Student Coordinator for TECHZEAL a National level event organized at SCIENT
Institute of Technology in 2010.
Participated in the event Yantra-RoboWar National level event AAKRUTHI at
Osmania University in 2010.

Personal Details:
Name
:
Fathers Name :
Address
:
Date of Birth :

Shravan Kumar.B
Nagesh.B
H.No:3-1-523, SBH Colony, 3rd Venture,
LB Nagar, Hyderabad, Andhra Pradesh, India-500074.
27-08-1989

Shravan Kumar B