A Scalable Named Information Network Architecture (NINA)

Transcription

1 A Scalable Named Information Network Architecture (NINA) Ruidong Li, Hiroaki Harai Network Architecture Laboratory, National Institute of Information and Communications Technology (NICT) Contact 1

2 Outline ICN Arguments, Observations, Societal Needs Goal, Design Requirements, Motivations Named Information Network Architecture (NINA) NINA Entities Reference Architecture & Functional Components NINA Instantiation Naming, Packet Formats Functions of Information Router (IR), Information GW (IGW) Scalable Information Registration/Retrieval (SIRR) NINA Use Cases IoT Information Consumed Locally Information Remove Scalability Analysis 2

3 Information-Centric Network (ICN) Information-Centric Network (ICN): The network designed for trustworthy information dissemination and retrieval over networking devices with cache memories/storages Information-Centric Network Information Information Information user Information Providers publisher ICN is one prospective approach for designing future network 3

4 Arguments on ICN Design Approach Naming Information Location (In-)dependent Host (Un-)identifiable Built-in Management 4

5 Argument 1: Naming Information? Information naming requirements Global uniqueness Efficiency Augment 1: Decentralized method is needed for naming the information Hierarchical name has efficiency 5

6 Argument 2: Location (In-) dependent? Resolution/Routing system requirements Anycast capable routing Scalable Location dependent? Or Independent? Not necessary keep it in mind. Finding/retrieving the closest copy is the ultimate goal! Argument 2: Location with large granularity can be utilized to help fast discovery 6

7 Argument 3: Host unidentifiable? Retrieve data based on information name Has no relation with Hosts/Servers/Routers identifier? Current Situation Besides data retrieval, end-to-end, machine-tomachine communication, mobility-centric communication are necessary Authentication, accountability Argument 3: Hosts/Servers/Routers need to be identifiable 7

8 Argument 4: Built-in Management? Information life cycle management Synchronization Update Remove Act on all the copies simultaneously Argument 4 Management of copies also need to be built into the network for ease of actions 8

9 Observations on Design Trends Expected environments Huge number of data Temporary network connections in dynamic environments Expected explosive M2M communications and M2M small data Most local information are consumed locally Expected Technologies High speed optical network (fast long distance data distribution) Cloud technology (Collaborate to provide fast, efficient, and energy saving data service) Network virtualization (Utilizable over it) 9

10 Societal Needs Fast Information Retrieval Low Traffic Overhead Trustworthy Information Information Locality & Global Reachability Explosive M2M communications and data Temporary connections 10

11 Goal & Design Requirements Goal: To design a network architecture that can naturally and globally support efficient, effective, and trustworthy information dissemination and retrieval with low communication overhead. Design Requirements: Scalability Trust Mobility Information Centric Life-Cycle Manag. Multi-Paradigm 11

12 Design Motivations Information-centric design Decentralized naming information uniquely Anycast capable routing Scalability Hierarchical naming of Local Information Name (LIN) Flooding restriction Aggregation with global reachability Information life-cycle management Location information at high granularity is distributedly managed Trust Information published with signature Proactive security architecture for validating information source and protecting information flow Mobility Host identifiable Multiple communication paradigms support One-to-one communication 12

13 Foundations of NINA Design Key Idea: Divide & Conquer to design scalable ICN Divide the network into many suitable size InfOrmation Island (IOI) for information caching and fast retrieval while utilizing aggregate plane (AP) for global reachability and management IOI: for caching and storage of information AP: for information management and locating the closest copy of requested information in other domain. Proposed NINA Design Naming information with local information name (LIN) and global information name (GIN) Anycast capable routing: Scalable information registration/retrieveal (SIRR) Aggregate/Manage information at IOI granularity Built-in security architecture to assure information source Host identifiable for mobility and one-to-one communication 13

14 NINA Entities NINA Entities: AMN: Aggregate Management Node (Gateway, NAT, Openflow controller, ) FCN: Forwarding Cacheable Node (Router, BS, AP, ) Functions: FF: Forwarding Function CF: Cache Function GDM: Global Discovery and Management PSF: Proactive Security Function FF CF FF GDM PSF PSF FCN AMN 14

15 Reference Architecture Aggregate Plane (AP) AMN AMN IOI m AMN(s) AMN AMN(s) FCN FCN AP global retrieval IOI n FCN FCN FCN AP global action Proactive Security Architecture FCN FCN IOI local retrieval IOI local action 15

16 Functional Components Information Management Resolution/ Routing System Caching Policy Multiple Communication Paradigms Trustworthy Information Flow Information Publisher Information Consumer 16

17 NINA Instantiation A concrete NINA at network layer compatible with Internet IOI:Domain Aggregate Plane: Global Transit Network AMN: Information Gateway (IGW) FCN:Information Router (IR), Information Access Point (IAP), 17

18 Naming Naming (Routing Efficiency, Aggregatability, Accountability, Locality): LIN (Local Information Name) in One Domain: Hierarchical Naming GIN (Global Information Name) out of one domain: Hierarchical Naming # Origin Domain name Hosts/routers also have identifiers, which can be IP or other newly designed ID. IGWs also have identifiers for overlay construction among them in aggregate plane. 18

19 Users Behaviors Packet Types: Data Registration Packet: for information announcement, registration Data Request Packet: for information request, interest indication Data Retrieval Packet: for replying information request with data Data Remove Packet: for remove data and its copies from network 19

20 Packet Formats 20

21 Functional Components of IR (Information Router) Functions: Caching and Storage of information Create entries for information retrieval Routing data request packet to the closest IRs/Servers and routing data retrieval packet to device Fault: Transit to global network through IGW. If information cannot be retrieved locally, it should be transit to IGW for global query. (If no record matches) Caching Memory/ Storage Name Routing Table LIN/ID NextHop LIN 1 Locator 1 ID 1 Locator 2 LIN 2 Locatork Fault LIN 5 IGW Information Index 21

22 Functional Components of IGW (Information Gateway) Functions: Inter-domain registration: Create entries to show the domains holding copies, and then enable information to be globally retrievable. Routing data request packet to the closest domain and then cloesest IRs and routing data retrieval packet back to domain and then device [ a, b ) [ b, c ) 22

23 Scalable Information Registration/Retrieval (SIRR) Procedures in SIRR Information registration: After information is stored/cached, its existence will be announced in the local domain by flooding. Meanwhile, it will also be registered globally to some specific IGWs. Intra-domain information retrieval: Forward the users request to the closest IR/Server holding the copy of the information in the local domain, and then this closest IR/Server replies with the information to the requesting users based on their IDs or addresses. Inter-domain information retrieval: Forward data request packet to the closest IR/server in the closest domain. This closest IR/Server will reply with the information to the requesting users based on their IDs or addresses. 23

24 SIRR Overview 24

25 Information Registration 25

26 Intra-domain Information Retrieval 26

27 Inter-domain Information Retrieval 27

28 Use Case - IoT Data Aggregatable at Domain Unit No cache, but closest copy retrievable Local Data Balance between locality & reachability 28

29 Use Case - Data Remove 29

30 Scalability Analysis Registration/management overhead will be greatly restricted, because of flooding limitation in global area and information management at IOI level by aggregate plane Data is aggregatable at IOI unit, which well balances locality and global reachability. Local information can be consumed locally and meanwhile provide clue for global retrieval. Caches become globally organizable based on diverse interests of different regions Total number of unduplicated data can be reachable by NINA NINA ~ 1.5*10 22 bytes Comparable with estimated annual global IP traffic (10 21 bytes) at

31 Conclusions Provide arguments, observations, societal needs on ICN Design Approaches Identify goal and design requirements Introduce design motivations and NINA reference architecture and functions Present a concrete NINA at network layer compatible with Internet, where a scalable information registration/retrieval has been proposed. Two use cases for the designed concrete NINA 31

32 Thank you! 32