1. RESUME
Personal details
Name: Sandeep K N
Email: sandeepkn12@gmail.com
Contact Number: +91 9008777200
Address:
Sandeep K N,
s/o Natesh K M,
Kelluru (Post), Piriyapattana,
Mysore (Dist)
Karnataka, India, pin – 571108
Technology
Specialized in
Internet of things ( IoT ) ,
Machine to Machine Communication ( IoT platform) ,
REST Architecture,
3G , UMTS , Telecom, SQL
Languages
Specialized in C, C++ ( platforms: Linux, Windows), object oriented concepts
Experience
Total: 8 years
Experience in IoT / M2M : 4 years
Education
Name of the Degree Discipline/Major
Bachelor of Engineering
UBDT collage of Engineering, Karnataka,
India
Electronics and communication
Master of science
Birla Institute of Technology and science,
Rajasthan, India
Software Systems
Current position
Senior Software Engineer,
IoT / M2M Team,
Radisys Ltd, Bangalore, India
Projects
Project Name Protocol used Feature designed and implemented
Internet of
things / M2M
HTTP, COAP ( constrained
application protocol ), TCP, UDP
Payload formats: XML , JSON
REST Architecture,
Standards: oneM2M and ETSI
Standards
Service Discovery,
Resource Discovery,
Subscription and Notification,
Scheduling of communication for devices,
Communication Management and Delivery
Handling,
Device management
Open
Message Bus
RabbitMQ AMQP, MQTT (OMB)Open Message Bus Client for cloud
environment,

2. for M2M For
Cloud
DNS Based discovery,
OMB – Service directory
3G - Femto
Media
Gateway (
FMG )
RANAP, SCCP, SCTP, M3UA Legal Requisition ,
Macro to Femto Cell Call Hand over
Traffic
management
Diameter Usage Management Module
CAPABILITIES
 I am good at co-ordination with people across multiple teams. I like talking to the people
about any technical and new innovation related matters.
 Capable of designing, prototyping, implementing and contributing to specifications.
 I am passionate about coming up with new ideas, concepts and realizing them in to
implementations.
 I will be a critical reviewer for any new idea technical proposal, can support anyone
else idea also to take it to implementation level.
ACCOMPLISHMENTS
 I have designed and implemented these features in Iot / M2M project (Features of Iot /
M2M: subscription Notification, resource discovery, service discovery, device
management, scheduling, communication management and deliveryhandling).
 Involved in architecture and design discussions with customer and implementation of the
multiple features listed in above table.
 Involved in performance optimization of the solution.
 Shown highest dedication, focus while designing and implementing complex features
such as scheduling, which is very critical to IoT / M2M environment.
 I was able to utilize innovative features of C++ language features such as smart pointers,
namespaces, in implementation of project, the usage of smart pointers for managing the
memory has reduced the memory leaks to a greater extent.
 Contribution to oneM2M specifications.

3. Below is the brief technical description of my involvement in various projects.
PROJECT: Internet of things / M2M
DESCRIPTION:
A Common Services Entity(CSE) developed for internet of things project represents an
instantiation of a set of "common service functions" of the M2M environments. Such service
functions are exposed to other entities through the reference points ( Ex: Mca and Mcc
reference points).
Any real time entities can register to the CSE and they are called as resources , the real time
entities can be temperature sensors, light sensors, watches, Medical equipment’s , any
industrial sensors, the data collected from these real time entities can be analyzed and acted
upon in real time.
I have designed and implemented the following features as part of this project
Feature:Communication Management and DeliveryHandling
The Communication Management and Delivery Handling (CMDH) service provides
communications with other CSEs, AEs and NSEs.
The CMDH service decides at what time to use which communication connection for
delivering communications (e.g. CSE-to-CSE communications) and, when needed and allowed,
to buffer communication requests so that they can be forwarded at a later time. This processing
in the CMDH service is carried out per the provisioned CMDH policies and delivery handling
parameters that can be specific to each request for communication.
Feature:Resource Discovery
The resource discovery procedures allow discovering of resources residing on a CSE(Common
service Entity). The use of the filterCriteria parameter allows limiting the scope of the results.
Resource discovery shall be accomplished using the RETRIEVE method by an
Originator which shall also include the root of where the discovery begins: e.g. <CSEBase>.
The unfiltered result of the resource discovery procedure includes all the child resources under
the root of where the discovery begins, which the Originator has a Discover access right on.
Feature: Subscription and notification
The Subscription and Notification CSF(common services function) provides notifications
pertaining to a subscription that tracks event changes on a resource (e.g. deletion of a
resource). A subscription to a resource is initiated by an AE(Application Entity) or a
CSE(common services entity), and is granted by the Hosting CSE subject to access control

4. policies. During an active resource subscription, the Hosting CSE sends a notification regarding
a notification event to the address(es) where the resource subscriber wants to receive it.
Feature: Scheduling
The devices in the IoT environment are low powered battery devices, so they will be in
sleep mode usually, but periodically they may be in awaken mode to receive messages, the
period during which these devices are available for communication is called as availability
period. Therefore the devices which will register on CSE can also specify a schedule window
during which they will be available for communication, in case if the schedule window for a
device is not available then the CSE may buffer the message.
PROJECT :Open Message Bus for cloud based environment
DESCRIPTION:
The OMB supports scalable communication between services for cloud environment. The
OMB Backbone structures support discovery, management and accessibility to data stored and
other services connected to the OMB.
Feature:OMB Clinet – AMQP (advanced message queuing protocol) Based
implementation
The OMB Client allows services to connect to the OMB Backbone structures, OMB Client
Module is the transport specific module. This will have all elements that are specific to a given
transport, for e.g., AMQP, MQTT, etc.
AMQP based implantation of OMB Client will provide support for trnapostation of messages
using AMQP protocol.
Feature:Open Message Bus – Service Directory( Service discovery)
Open Message Bus Service Directory is one of the key components of the OMB backbone in
the Open Message Bus architecture. It facilitates OMB Clients on the Open Message Bus to

5. dynamically discover other OMB Clients. It provides value added services such as subscription
and notification for OMB Clients.
PROJECT: Femto Media gateway development (FMG) – 3G UMTS
DESCRIPTION:
The Femto media gateway (FMG) acts as Gateway for the telecommunication signals
exchanged between the Core Network (CN) and the user equipment (UE) through Base station
router. 3GPP standard RANAP signals were used between FMG and CN, similar signals were
used between FMG and BSR( base station router ) called as RANAP’.
The FMG system uses SS7 protocols and STRMGR (a proprietary protocol) to manage
the SCTP streams between FMG and BSR, each BSR will be identified with its association Id at
FMG, each association has 512 streams allocated for it.M3UA is used to transmit the traditional
SCCP signals over SCTP to core network. A stack manager is developed to mange the
SIGTRAN stack.
Feature: Legal Requisition feature for Femto Media Gateway project
DESCRIPTION:
FMG (Femto media gateway) will determine the location of UE on the event of Calls and
SMS for legal requisition and log the call and SMS event upon LR presence in the signaling
message of call establishment. The Call Event may be a new Call Origination or Termination or
as a result of Mobile initiated or a network initiated SMS.
The BSG logs the Legal Requisition information like Public IP Address and Port Number
of the DSL Router that interfaces the BSR with the Public IP Network along with the associated
Timestamp, the BSR Factory Serial Number and the Call Event against the UE context whenever
the UE is involved in a call while located on a Femto Cell and transfers the Log files at periodic
intervals to a secure file server known as Legal requisition Log Server.
Feature : Macro to Femto Cell Call Hand over for FMG project
DESCRIPTION:

6. This feature enables user equipments (UE) to move from a macro Cell to Femto cell during a
call.
During registration of Femto cells at FMG (Femto cell  FMG), relevant details required for
carrying relocation procedures will be stored in its (FMG) registration tables. On receipt of
relocation request from CN these registered parameters are used for comparison with different
parameters of relocation request.
During a call, Whenever UE moves from Macro cell to Femto Cell, the UE initiates a relocation
request from CN (CN  FMG), FMG will detect the Relocation request sent from C N. Based on
the RNC ID, Target Cell id , plmn id , FMG will generate a list of Target Femto Cells to which the
Relocation request has to be forwarded. The Femto cells present in the Target list will be
prioritized so as to attain the maximum probability of reaching the UE by forwarding less number
of Relocation requests to various Femto cells.
On receipt of Relocation request a if Femto cell finds corresponding UE in its coverage area,
Femto cell would send a relocation acknowledge , and then relocation complete message to FMG.
PROJECT: Traffic management
DESCRIPTION:
The traffic management solution is provided with policies to shape the data rate of the subscribers
based on the priority set by the operators. The program reports the data usage per subscriber
periodically to a management server over Gx interface. Once the data usage limit is reached the
subscriber will be notified of the data limitation.
OBJECTIVE:
______________________________________________________________________
Objective:To utilize my knowledge and experience to achieve organizational goals, and to
grow professionally to greater heights.

7. OTHER DETAILS:
Permanent Address : Sandeep KN
s/o Natesh KM
Kelluru (post),
Piriyapattana (Taluk),
Mysore (dist),
Karnataka,
India,
Pin – 571108.
Thanking you