Martin-1

CSE5810

CSE 5810 Individual Research Project:CSE 5810 Individual Research Project:

Integration of Named Data Networking for Integration of Named Data Networking for Improved Healthcare Data HandlingImproved Healthcare Data Handling

Robert MartinComputer Science & Engineering Department

The University of Connecticut371 Fairfield Road, Box U-255

Storrs, CT 06269-2155

Robert.martin@engr.uconn.edu

Martin-2

CSE5810

MotivationMotivation

Technology limitationsTechnology limitations Larger data files Multiple databases Ever expanding healthcare network

Fast pace hospital environmentFast pace hospital environment Providers constantly moving Intolerant to delayed data access

Lack of communication between departmentsLack of communication between departments Clinical, technical, business management,

financial, etc.

Martin-3

CSE5810

Large ScopeLarge Scope

Keep up with changeKeep up with change Larger data files Mobile devices Real-time data availability

Conform to busy hospital environmentConform to busy hospital environment Revamp current network Transparent infrastructure

Martin-4

CSE5810

Overall GoalOverall Goal

Apply Named Data Networking within a hospital Apply Named Data Networking within a hospital environmentenvironment Data connectivity Improved transmission speeds (compared with

regular IP networking) Improved mobile device handling Interoperability between diverse departments

Martin-5

CSE5810

Named Data Networking (NDN)Named Data Networking (NDN)

Image adapted from:Image adapted from:Tsudik, Gene. NSF FIA PI meeting: “NDN team presentation.” Berkeley, CA, May 25, 2011.Tsudik, Gene. NSF FIA PI meeting: “NDN team presentation.” Berkeley, CA, May 25, 2011.

Martin-6

CSE5810

Hospital Setting NDN Hospital Setting NDN

Martin-7

CSE5810

NDN vs. IP NetworkingNDN vs. IP Networking Named Data NetworkingNamed Data Networking

Data centric approach IP NetworkingIP Networking

Looks at where data is located

Image adapted from:Jacobson et al. (full reference in notes)

Martin-8

CSE5810

Interest and Data PacketsInterest and Data Packets

Interest PacketInterest Packet Data name in query Nonce is unique identifier Selectors help better match interest to data Scope and interest lifetime help guide

packet to intended data

Data PacketData Packet Content is of arbitrary data size Signature is used to verify the

packet’s producer and its integrity throughout transmission

Martin-9

CSE5810

Pending Interest Table (PIT)Pending Interest Table (PIT)

Monitors all unsatisfied interest packetsMonitors all unsatisfied interest packets Entry classified as unsatisfied until either a data packet Entry classified as unsatisfied until either a data packet

is received (to match its interest) or the interest is received (to match its interest) or the interest lifetime value is reachedlifetime value is reached

“A Case for Stateful Forwarding Plane” by C. Yi et al. depicts a great image for how node’s use PITs(see full reference in notes)

Martin-10

CSE5810

Forwarding Information Base (FIB)Forwarding Information Base (FIB)

Monitors downstream data location through next hop Monitors downstream data location through next hop neighborneighbor

“A Case for Stateful Forwarding Plane” by C. Yi et al. depicts a great image for how node’s use FIBs(see full reference in notes)

Martin-11

CSE5810

Content StorageContent Storage

Cache data locallyCache data locally Pushes data closer to consumer(s)Pushes data closer to consumer(s) Allows network to become “data focused”Allows network to become “data focused”

Quicker fetching of data for consumer Data architecture can varyData architecture can vary

FIFO, LRU, etc.

Martin-12

CSE5810

Data NamingData Naming

Application specificApplication specific Flexible standardsFlexible standards

Classifications and standards can be adjusted

Martin-13

CSE5810

SecuritySecurity Nurse fetching data which is unrelated to her role in Nurse fetching data which is unrelated to her role in

the hospital (e.g. Patent’s social security number)the hospital (e.g. Patent’s social security number)

Security integrated into data packetSecurity integrated into data packet Authentication process

Martin-14

CSE5810

Fetching DataFetching Data Filtering naming systemFiltering naming system

Adjust documentation standards for each department E.g. Financial employee and patient see “heart attack”

vs. global view classification as “Myocardial Infarction”

Paths are dynamic while being transparent to end userPaths are dynamic while being transparent to end user Nodes can be added or removed without having an

effect on the user Robust among dense networks

We must make network aware of newly added data in an We must make network aware of newly added data in an efficient mannerefficient manner

Martin-15

CSE5810

Discovery ServiceDiscovery Service

Maps out data on network (similar to DNS)Maps out data on network (similar to DNS)

Martin-16

CSE5810

Mobility with IP NetworkingMobility with IP Networking

Illustration through Illustration through example:example: Pre-loading

patient’s data Large data files Based on IP

network

Martin-17

CSE5810

Mobility with IP NetworkingMobility with IP Networking

Provider must request file again

Additional stress to hospital network

Martin-18

CSE5810

Mobility with Named Data NetworkingMobility with Named Data Networking

Illustration through Illustration through example:example: NDN based network

Martin-19

CSE5810

Mobility with Named Data NetworkingMobility with Named Data Networking

Data content cached

Martin-20

CSE5810

Mobility with Named Data NetworkingMobility with Named Data Networking

Data requested again Reduced redundant data

packets

Martin-21

CSE5810

Simulation SettingsSimulation Settings

Ns3 and ndnSIM extension usedNs3 and ndnSIM extension used Regular IP based network vs. NDN integrated networkRegular IP based network vs. NDN integrated network Focus:Focus:

Transmission times Network stress

Martin-22

CSE5810

Preliminary Simulation DataPreliminary Simulation Data

Network StressNetwork Stress Overall Transmission TimeOverall Transmission Time

Martin-23

CSE5810

ConclusionConclusion Apply NDN concepts in hospital infrastructureApply NDN concepts in hospital infrastructure

“What” data instead of “Where” Reduce stress on keynote features Less bandwidth usage Friendlier to mobile devices

Additional featuresAdditional features Adaptability with discovery service Integrated security through data

ChallengesChallenges Acceptability by healthcare Ensuring security of data

Martin-24

CSE5810

THANK YOUTHANK YOU