دانلود رایگان ترجمه مقاله شبکه داده های نام گذاری شده – ACM 2014
دانلود رایگان مقاله انگلیسی + خرید ترجمه فارسی | |
عنوان فارسی مقاله: |
شبکه داده های نام گذاری شده |
عنوان انگلیسی مقاله: |
Named Data Networking |
|
مشخصات مقاله انگلیسی (PDF) | |
سال انتشار | 2014 |
تعداد صفحات مقاله انگلیسی | 8 صفحه با فرمت pdf |
رشته های مرتبط با این مقاله | مهندسی فناوری اطلاعات و کامپیوتر |
گرایش های مرتبط با این مقاله | معماری سیستم های کامپیوتری، شبکه های کامپیوتری و اینترنت و شبکه های گسترده |
چاپ شده در مجله (ژورنال) | بررسی ارتباطات کامپیوتر SIGCOMM |
ارائه شده از دانشگاه | دانشگاه ممفیس |
رفرنس | دارد ✓ |
کد محصول | F970 |
نشریه | ACM |
مشخصات و وضعیت ترجمه فارسی این مقاله (Word) | |
وضعیت ترجمه | انجام شده و آماده دانلود |
تعداد صفحات ترجمه تایپ شده با فرمت ورد با قابلیت ویرایش | 22 صفحه با فونت 14 B Nazanin |
ترجمه عناوین تصاویر و جداول | ترجمه شده است ✓ |
ترجمه متون داخل تصاویر | ترجمه شده است ✓ |
درج تصاویر در فایل ترجمه | درج شده است ✓ |
کیفیت ترجمه | کیفیت ترجمه این مقاله متوسط میباشد |
فهرست مطالب |
چکیده
1-چشم انداز: یک مدل “میانه باریک ” جدید
2-معماری NDN
2-1 نام ها
2-2 امنیت داده محور
2-3 مسیر یابی و ارسال
2-4 ذخیره درون شبکه
2-5 دستور انتقال
3-توسعه معماری NDN
3-1 تحقیقات برنامه
3-2 مسیر یابی و ارسال NDN
3-3 مدیریت اعتماد
4- جامعه و استقرار NDN
5-سوالات باز
6- چشم انداز آینده
|
بخشی از ترجمه |
1-چشم انداز: یک مدل “میانه باریک ” جدید |
بخشی از مقاله انگلیسی |
1. VISION: A NEW NARROW WAIST Today’s Internet’s hourglass architecture centers on a universal network layer (i.e., IP) which implements the minimal functionality necessary for global interconnectivity. This thin waist enabled the Internet’s explosive growth by allowing both lower and upper layer technologies to innovate independently. However, IP was designed to create a communication network, where packets named only communication endpoints. Sustained growth in e-commerce, digital media, social networking, and smartphone applications has led to dominant use of the Internet as a distribution network. Distribution networks are more general than communication networks, and solving distribution problems via a point-topoint communication protocol is complex and error-prone. The Named Data Networking (NDN) project proposed an evolution of the IP architecture that generalizes the role of this thin waist, such that packets can name objects other than communication endpoints (Figure 1). More specifically, NDN changes the semantics of network service from delivering the packet to a given destination address to fetching data identified by a given name. The name in an NDN packet can name anything – an endpoint, a data chunk in a movie or a book, a command to turn on some lights, etc. This conceptually simple change allows NDN networks to use almost all of the Internet’s well-tested engineering properties to solve a much broader range of problems including not only end-to-end communications but also content distribution and control problems. Based on three decades of experience with the strengths and limitations of the current Internet architecture, the design also builds in security primitives (via signatures on all named data) and self-regulation of network traffic (via flow balance between Interest and Data packets). The architecture includes functionality designed to be conducive to user choice and competition as the network evolves, such as multipath forwarding and innetwork storage. NDN is one instance of a more general network research direction called information-centric networking (ICN), under which different architecture designs have emerged [29]. The Internet Research Task Force (IRTF) established an ICN research working group in 20122 . In this paper we provide a brief (and necessarily incomplete) snapshot of the current state of the NDN architecture research project, which includes sixteen NSF-funded principal investigators at twelve campuses, and growing interest from the academic and industrial research communities. A more complete description of recent activities is in the third annual project report [20] and on the NDN web site (named-data.net). 2. NDN ARCHITECTURE Communication in NDN is driven by receivers i.e., data consumers, through the exchange of two types of packets: Interest and Data. Both types of packets carry a name that identifies a piece of data that can be transmitted in one Data packet. A consumer puts the name of a desired piece of data into an Interest packet and sends it to the network. Routers use this name to forward the Interest toward the data producer(s). Once the Interest reaches a node that has the requested data, the node will return a Data packet that contains both the name and the content, together with a signature by the producer’s key which binds the two (Figure 2). This Data packet follows in reverse the path taken by the Interest to get back to the requesting consumer. To carry out the Interest and Data packet forwarding functions, each NDN router maintains three data structures: a Pending Interest Table (PIT), a Forwarding Information Base (FIB), and a Content Store (CS) (Figure 3), as well as a Forwarding Strategy module (not shown in the figure) that determines whether, when and where to forward each Interest packet. The PIT stores all the Interests that a router has forwarded but not satisfied yet. Each PIT entry records the data name carried in the Internet, together with its incoming and outgoing interface(s). When an Interest packet arrives, an NDN router first checks the Content Store for matching data; if it exists the router returns the Data packet on the interface from which the Interest came. Otherwise the router looks up the name in its PIT, and if a matching entry exists, it simply records the incoming interface of this Interest in the PIT entry. In the absence of a matching PIT entry, the router will forward the Interest toward the data producer(s) based on information in the FIB as well as the router’s adaptive Forwarding Strategy. When a router receives Interests for the same name from multiple downstream nodes, it forwards only the first one upstream toward the data producer(s). The FIB itself is populated by a name-prefix based routing protocol, and can have multiple output interfaces for each prefix. The Forwarding Strategy may decide to drop an Interest in certain situations, e.g., if all upstream links are congested or the Interest is suspected to be part of a DoS attack. For each Interest, the Forwarding Strategy retrieves the longestprefix matched entry from the FIB, and decides when and where to forward the Interest.3 The Content Store is a temporary cache of Data packets the router has received. Because an NDN Data packet is meaningful independent of where it comes from or where it is forwarded, it can be cached to satisfy future Interests. When a Data packet arrives, an NDN router finds the matching PIT entry and forwards the data to all downstream interfaces listed in that PIT entry. It then removes that PIT entry, and caches the Data in the Content Store. Data packets always take the reverse path of Interests, and, in the absence of packet losses, one Interest packet results in one Data packet on each link, providing flow balance. To fetch large content objects that comprise multiple packets, Interests provide a similar role in controlling traffic flow as TCP ACKs in today’s Internet: a fine-grained feedback loop controlled by the consumer of the data (see Section 2.1). Neither Interest nor Data packets carry any host or interface addresses; routers forward Interest packets toward data producers based on the names carried in the packets, and forward Data packets to consumers based on the PIT state information set up by the Interests at each hop. This Interest/Data packet exchange symmetry induces a hop-by-hop control loop (not to be confused with symmetric routing, or with routing at all!), and eliminates the need for any notion of source or destination nodes in data delivery, unlike in IP’s end-to-end packet delivery model. |