Patent Grant
10038633
The subject matter of this application is related to the subject matter in the following applications:
Field
This disclosure is generally related to distribution of digital content. More specifically, this disclosure is related to a system for querying historical network information in a content centric network, which facilitates users of the system to increase network efficiency.
Related Art
The proliferation of the Internet and e-commerce continues to create a vast amount of digital content. Content centric network (CCN) architectures have been designed to facilitate accessing and processing such digital content. A CCN includes entities, or nodes, such as network clients, forwarders (e.g., routers), and content producers, which communicate with each other by sending interest packets for various content items and receiving content object packets in return. CCN interests and content objects are identified by their unique names, which are typically hierarchically structured variable length identifiers (HSVLI). An HSVLI can include contiguous name components ordered from a most general level to a most specific level. A CCN name prefix, or namespace, may include one or more contiguous name components beginning from the most general level.
Some transport protocols implement flow and congestion control by maintaining a window of messages (e.g., packets) sent from a client (e.g, a consumer) to a server (e.g., a content producer). Upon sending a packet, the consumer adds a packet to the window, and upon receiving a responsive packet, the consumer removes a packet from the window. For a window with a size of “w,” only w messages can be outstanding at any given time. Some transport protocols (such as TCP) use a sliding window such that w is a variable that changes dynamically based on network conditions. For example, if the protocol determines congestion, e.g., due to heavy traffic of neighboring nodes, the consumer can decrease w so that fewer messages are sent to the network. Similarly, if the protocol determines that the network is not congested, the consumer can increase w so that more messages can be sent for better throughput and latency performance.
While a CCN brings many desired features to a network, some issues remain unsolved with enabling a CCN transport protocol to increase network efficiency by allowing system users to query the network for historical network information.
One embodiment provides a system that facilitates querying of historical network information. During operation, the system generates a query for historical information associated with interest and corresponding content object packets, wherein a name for an interest packet is a hierarchically structured variable length identifier (“HSVLI”) that includes contiguous name components ordered from a most general level to a most specific level, wherein the query is based on a name prefix that includes one or more contiguous name components. The system transmits the query to a responding entity. In response to receiving the historical information from the responding entity, the system performs an operation that increases network efficiency based on the historical information, thereby facilitating a protocol for querying the historical information to increase network efficiency.
In some embodiments, the query is an interest packet that indicates one or more of: a routable prefix which includes one or more contiguous name components beginning from the most general level; a user identifier of the requesting entity; authentication information of the requesting entity; a type for the query; a string for the query; one or more parameters for the query; a function for the query; and a random nonce.
In some embodiments, the query is an interest packet with a name that is an HSVLI that includes contiguous name components ordered from a most general level to a most specific level, wherein the name includes one or more of: a routable prefix which includes one or more contiguous name components beginning from the most general level; a user identifier of the requesting entity; authentication information of the requesting entity; a type for the query; a string for the query; one or more parameters for the query; a function for the query; and a random nonce.
In some embodiments, the method is performed by a requesting entity which is a component of a stack of communication modules, the responding entity is a local forwarder that services the stack, and the query is a control message that indicates one or more of: an identifier for the local forwarder; a component which is responsible for collecting and storing the historical information, wherein the component resides in the local forwarder; a type for the query; a string for the query; one or more parameters for the query; and a function for the query.
In some embodiments, the operation is one or more of: setting or changing a window size; setting or changing a rate of transmission for re-transmitted interests; setting or changing a rate of transmission for original interests, wherein an original interest is not a re-transmitted interest; and an operation related to increasing the efficiency of the network.
In some embodiments, the query includes a command to perform a function on the historical information, and the function includes one or more of: computing an estimate of an average round trip time for an interest and a corresponding content object based on the name prefix, wherein a round trip time begins when an interest is transmitted and ends when a corresponding content object is received, or begins when an interest is received and ends when a corresponding content object is transmitted, wherein the estimate is based on a plurality of average round trip times for a corresponding plurality of related namespaces that share at least one name prefix; computing an estimate of a size of a transmission window based on a number of outstanding interests for the name prefix for a predetermined period of time; and performing a function based on one or more interests as input, wherein an output for the function is a variable which can be stored by the system, wherein the function is defined by the system or a user of the system.
In some embodiments, the method is performed by a requesting entity which is one or more of: an application associated with a first stack, wherein the responding entity resides in or is associated with the first stack; an application associated with a second stack that is different from the first stack; a stack component of the first stack, wherein the stack component is different from the responding entity; a stack component of the second stack; and any other element or node in the network.
In some embodiments, the responding entity resides in one or more of: an application; a single stack; a shared stack; a single forwarder; a shared forwarder; and any node in a network.
In some embodiments, the historical information associated with the packets is one or more of: a round trip time that begins when an outgoing interest is transmitted and ends when a corresponding incoming content object is received; a number of outgoing interests for which a corresponding incoming content object has not been received; a number of outgoing interests for which a corresponding incoming content object is received based on a predetermined amount of time or the round trip time; a number of bytes correctly retrieved based on the predetermined amount of time or the round trip time; a number of outgoing interests that time out based on the predetermined amount of time or the round trip time; a number of outgoing interests which are retransmitted based on the predetermined amount of time or the round trip time; a number of re-transmitted outgoing interests that time out based on the predetermined amount of time or the round trip time; a number of interest return messages received based on the predetermined amount of time or the round trip time, wherein an interest return message is received in response to an outgoing interest and is identified based on a code indicated in the message; a number of outgoing interests aggregated based on the predetermined amount of time or the round trip time; a number of active upstream paths identified for a given time; a strategy for forwarding packets; a first number of transmitted original interests, wherein an original interest is not a re-transmitted interest, and wherein the first number of original interests include names that share one or more name prefixes; a second number of transmitted original interests, wherein the second number of original interests include names that do not share any name prefixes; a first number of active entries in a forwarding information base, wherein the first number of entries include names that share one or more name prefixes; and a second number of active entries in a forwarding information base, wherein the second number of entries include names that do not share any name prefixes.
In some embodiments, the historical information associated with the packets is one or more of: a round trip time that begins when an incoming interest is received and ends when a corresponding incoming content object is transmitted; a number of incoming interests for which a corresponding outgoing content object has not been transmitted; a number of incoming interests for which a corresponding outgoing content object is transmitted based on a predetermined amount of time or the round trip time; a number of bytes correctly retrieved based on the predetermined amount of time or the round trip time; a number of incoming interests that time out based on the predetermined amount of time or the round trip time; a number of re-transmitted incoming interests based on the predetermined amount of time or the round trip time; a number of re-transmitted incoming interests that time out based on the predetermined amount of time or the round trip time; a number of interest return messages transmitted based on the predetermined amount of time or the round trip time, wherein an interest return message is transmitted in response to an incoming interest and is identified based on a code indicated in the message; and a number of incoming interests aggregated based on a predetermined amount of time or a round trip time.
Another embodiment provides a system that facilitates querying of historical network information. During operation, the system receives a query from a requesting entity for historical information associated with interest and corresponding content object packets. In response to authenticating the requesting entity, the system transmits the queried historical information, which causes the requesting entity to perform an operation to increase network efficiency based on the historical information, thereby facilitating a protocol for querying the historical information to increase network efficiency.
In some embodiments, the requesting entity is one or more of: an application associated with a first stack, wherein the responding entity resides in the first stack; an application associated with a second stack that is different from the first stack; a stack component of the first stack, wherein the stack component is different from the responding entity; a stack component of the second stack; and any other element or node in the network.
In some embodiments, the method is performed by a responding entity which resides in one or more of: an application; a single stack; a shared stack; a single forwarder; a shared forwarder; and any node in a network.
In the figures, like reference numerals refer to the same figure elements.
The following description is presented to enable any person skilled in the art to make and use the embodiments, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
Overview
Embodiments of the present invention provide a system for querying historical network information in a CCN which facilitates a system user to perform a function that increases overall network efficiency. One aspect of network efficiency is flow and congestion control. Some transport protocols implement this control by maintaining a sliding window of a size “w” that changes based on network conditions. The window size w is dynamically changed based on the perceived and measured performance of the network. For example, if the protocol determines congestion, e.g., due to heavy traffic of neighboring nodes, a consumer can decrease w so that fewer messages are sent to the network. Similarly, if the protocol determines that the network is not congested, the consumer can increase w so that more messages can be sent for better throughput and latency performance.
In a CCN transport protocol (e.g., ICP, CCTCP and other variants), a similar TCP-like mechanism is used to control flow and congestion by maintaining a window of outstanding interests. Recall that traffic in a CCN is symmetric, where a single interest returns a corresponding content object (or an interest return, as described in U.S. patent application Ser. No. 14/334,530). Thus, historical information regarding a given CCN namespace (e.g., a name prefix) may be collected by a network entity through which CCN packets (e.g., interests and content objects) flow. Embodiments of the present invention provide a system and protocol for a system user to query the network for historical network information collected by a generic “collector component.” The historical information relates to outgoing interests and incoming content objects, and to incoming interests and outgoing content objects. The collector component, as the responding network entity, can reside in an application, a single or shared stack, a single or shared forwarder, or any node in the network. The system user, as the requesting entity, can be an application associated with a first stack, where the collector component resides in or is associated with the first stack, or an application associated with a second stack. The requesting entity can also be a stack component of the first stack, a stack component of the second stack, or any other element or node in the network.
The query can be in the form of an interest message or a control message. For example, if the requesting entity is an application or a stack component associated with a stack which the collector component neither resides in nor is associated with, the query can take the form of an interest message (as described below in relation to
The system can collect historical information for each namespace identified in a set of messages. A namespace is a CCN prefix (i.e., one or more contiguous name components beginning from the most general level) and a CCN name may have multiple namespaces or prefixes. For example, the name “/a/b/c” has three namespaces: “/a”; “/a/b”; and “/a/b/c.”
In CCN, each piece of content is individually named, and each piece of data is bound to a unique name that distinguishes the data from any other piece of data, such as other versions of the same data or data from other sources. This unique name allows a network device to request the data by disseminating a request or an interest that indicates the unique name, and can obtain the data independent from the data's storage location, network location, application, and means of transportation. The following terms are used to describe the CCN architecture:
Content Object (or “Content Object”):
A single piece of named data, which is bound to a unique name. Content Objects are “persistent,” which means that a Content Object can move around within a computing device, or across different computing devices, but does not change. If any component of the Content Object changes, the entity that made the change creates a new Content Object that includes the updated content, and binds the new Content Object to a new unique name.
Unique Names:
A name in a CCN is typically location independent and uniquely identifies a Content Object. A data-forwarding device can use the name or name prefix to forward a packet toward a network node that generates or stores the Content Object, regardless of a network address or physical location for the Content Object. In some embodiments, the name may be a hierarchically structured variable-length identifier (HSVLI). The HSVLI can be divided into several hierarchical components, which can be structured in various ways. For example, the individual name components parc, home, ccn, and test.txt can be structured in a left-oriented prefix-major fashion to form the name “/parc/home/ccn/test.txt.” Thus, the name “/parc/home/ccn” can be a “parent” or “prefix” of “/parc/home/ccn/test.txt.” Additional components can be used to distinguish between different versions of the content item, such as a collaborative document. The HSVLI can also include contiguous name components ordered from a most general level to a most specific level.
In some embodiments, the name can include an identifier, such as a hash value that is derived from the Content Object's data (e.g., a checksum value) and/or from elements of the Content Object's name. A description of a hash-based name is described in U.S. patent application Ser. No. 13/847,814, which is herein incorporated by reference. A name can also be a flat label. Hereinafter, “name” is used to refer to any name for a piece of data in a name-data network, such as a hierarchical name or name prefix, a flat name, a fixed-length name, an arbitrary-length name, or a label (e.g., a Multiprotocol Label Switching (MPLS) label).
Interest (or “Interest”):
A packet that indicates a request for a piece of data, and includes a name (or a name prefix) for the piece of data. A data consumer can disseminate a request or Interest across an information-centric network, which CCN/NDN routers can propagate toward a storage device (e.g., a cache server) or a data producer that can provide the requested data to satisfy the request or Interest.
The methods disclosed herein are not limited to CCN networks and are applicable to other architectures as well. A description of a CCN architecture is described in U.S. patent application Ser. No. 12/338,175, which is herein incorporated by reference.
Exemplary Network and Communication
In a traditional IP architecture, a forwarder is an IP-based forwarder that looks at the header of a packet to determine the source and the destination for the packet, and forwards the packet to the destination. The stack performs TCP/UDP, and an application interacts with the stack via a socket. In contrast, device 104 of the present invention does not use a conventional “stack.” Rather, device 104 via an application 110 can request a portal API instance corresponding to a portal 120 which corresponds to transport framework 130. Similarly, device 108 via an application 150 can request a portal API instance corresponding to a portal 160 which corresponds to transport framework 170.
Device 104 can include any computing device coupled to network 102, such as a smartphone 104.1, a tablet computer 104.2, and/or a server or personal computer 104.m. Specifically, device 104 can include application 110 which communicates via portal 120 with transport framework 130. Transport framework 130 can include stack components 134.1-134.n. Device 104 can also include forwarder 140 (e.g., a network interface card, or a router in a local area network) which can transfer packets between a stack (and individual stack components) of transport framework 130 and network 102. Similarly, device 108 can include any computing device coupled to network 102, such as a server or an end host device. Device 108 can include application 150 which communicates via portal 160 with transport framework 170. Transport framework 170 can include stack components 174.1-174.p. Device 108 can also include a forwarder 180 which can transfer packets between a stack (and individual stack components) of transport framework 170 and network 102. Forwarders 140 and 180 can also facilitate the transfer of packets directly between individual stack components 134.1-134.n and 174.1-174.p, respectively.
Exemplary Transport Frameworks
In embodiments of the present invention, the collector component can be implemented in a CCN transport framework, and can reside in a forwarder (as in
Similarly, application 250 can use APIs 252, 254, and 256 to communicate over network 202, and APIs 252-256 can interact via a portal 260 with a transport framework 270. Transport framework 270 can include one or more transport stacks which each include multiple stack components or communication modules. In
During operation, collector 242 residing in forwarder 240 can monitor a plurality of packets which are outgoing interests and incoming content objects. For example, application 210 can generate and send an interest 290 with a name of “/a/b/c,” via portal instance 220 through stack 231. As interest 290 leaves stack 231, it passes through forwarder 240 and collector 242. Collector 242 can monitor the time at which interest 290 is transmitted. Interest 290 can then travel over network 202, and through, e.g., forwarder 280 to be satisfied by application 250 associated with stack 271. Application 250 can generate a responsive content object 292 with a name of “/a/b/c” and a payload of “Data.” Content object 293 can travel via forwarder 280 to forwarder 240 over network 202. Collector 242 can note the time that it receives responsive incoming content object 292, and record in a storage device 242.1 the round trip time associated with the multiple namespaces included in the name “/a/b/c” (i.e., “/a,” “/a/b,” and “/a/b/c”). Collector 242 can also store in storage device 242.1 other historical information associated with a given namespace, as described below in the section entitled “Exemplary Historical Information.” Storage device 242.1 can be accessed solely by collector 242 or shared with other components or elements.
Collector 242 can also monitor an incoming interest 294 (with a name of “/d/e/f” sent by application 250 via forwarder 280) by monitoring the time at which interest 294 is received. Collector 242 can subsequently monitor and record the time that an outgoing responsive content object 296 is transmitted, where content object 296 has a name of “/d/e/f” and is sent by application 210 via forwarder 240. Collector 242 can also monitor and record the round trip time associated with the multiple namespaces included in the name “/d/e/f” (i.e., “/d,” “/d/e,” and “/d/e/f”) as well as other historical information.
Thus, collector 242 can obtain and store various historical information related to a given namespace. Any requesting entity (e.g., a user of the system) can subsequently query the component for the historical information. A requesting entity can be: an application associated with a first stack, where the collector component resides in the first stack (e.g., application 210); an application associated with a second stack that is different from the first stack (e.g., application 250); a stack component of the first stack, wherein the stack component is different from the collector component (e.g., flow controller 234); a stack component of the second stack (e.g., flow controller 274); and any other element or node in the network (not shown).
Local Message Stream Co-Processor Example
Because forwarder 240, and thus MSCP 244, processes all messages for all applications on a given system (e.g., a CCN end-host), maintaining the privacy of the messages is a key feature. The operating system can define and limit the functionality of MSCP 244, including the disclosure of collected historical information to authorized entities only. For example, requesting entity application 210 can transmit a query 286 to MSCP 244, and requesting entity flow controller 234 can also transmit a query 282 to MSCP 244. Queries 282 and 286 may include a request for historical information collected by MSCP 244. Since the requesting entities (e.g., application 210 and flow controller 234) are associated with the end host serviced by MSCP 244, MSCP 244 can identify the requesting entities as authorized entities and transmit the requested historical information back in response to queries 282 and 286. Similarly, application 250 and flow controller 274 may, respectively, submit queries 288 and 284 to MSCP 244, and in response receive the requested historical information from MSCP 244.
Thus, MSCP 244 can perform like a black box that consumes CCN messages for processing. The limits of this processing are unbounded. MSCP 244 can provide whatever is needed for its given end-host and associated applications. For example, MSCP 244 may be configured to count the number of processed messages, to log the names of all outgoing interest messages to a system log, or to collect any of the types of historical information described herein.
Exemplary Historical Information
Consider the following sequence of n interest messages issued by different applications on the same end-host, i.e., Ij for j=1, . . . , n:
In a window that includes each of interests Ij, the “/a” namespace has n interests, the “/a/b1” namespace has i interests, and the “/a/b2” namespace has (n−i+1) interests. Each of interests Ij has a corresponding content object response, Cj.
For each of interests Ij, the collector component can collect various types of historical information based on each particular namespace, including the items in the following non-exhaustive list:
In addition, the collector component can perform a function or compute information based on the historical information. Examples include computation of the average RTT for a given namespace, an estimate of the transmission window size, and a user-defined function. In estimating the average RTT for a given namespace, consider the n interest messages issued by different applications on the same end-host, i.e., Ij for j=1, . . . , n. Recall that each of interests Ij has a corresponding content object response, Cj. Let rj be the RTT of the issuance of the interest Ij and the retrieval of the corresponding content object Cj, and assume that historical information is maintained for windows of size d<i and d<(n−i+1). Then, for each of the three namespaces (i.e., “/a,” “/a/b1,” and “/a/b2”), the collector component can compute a smoothed RTT average r[/a], r[/a/b1], and r[/a/b2]. These RTT averages can be computed based on any appropriate algorithm, e.g., as a weighted moving average or exponential moving average. Additionally, while an RTT computation may be based on time, it may also be based on other information such as hop counts for retrieved content objects.
In estimating the transmission window size, recall that the transmission window size is coupled to time in that the window size changes over time, depending on the behavior of the transport protocol. The goal of this historical information is not to anticipate the behavior of the transport protocol, but rather to passively measure the effects of the transport protocol. Consider a small (and configurable) time epoch “E.” Given a frame of n interests I1, . . . , In, the collector component computes the number of outstanding interests for each namespace in the frame. The resultant number is treated as a sample in the given timeslot of size E. When the time slot advances, the new samples are computed. For example, in timeslot t1, there may be x outstanding interests for namespace “N.” Then, in timeslot t2, there may be y outstanding interests for namespace N. Thus, the average window size may be approximately computed as (x+y)/2. The accuracy of this approximation depends on both the granularity of the timeslot (e.g., E) and the width of the frame. E may also be dynamically modified based on RTT estimations. For example, if the RTT estimation for a given namespace is small, then E may correspondingly be decreased. The value of E is typically less than the time it takes for the collector component to process all interests in a given frame.
In computing a user-defined function, the collector component can accept closures for processing streams of interests. The representation of a closure conforms to the interface for the stream processing. That is, the closure is a function which accepts a sequence of interests, produces an output, and may invoke other closures in the process. This can be compared to the “map-reduce” paradigm, where a user provides custom “map” and “reduce” functions and the framework invokes them accordingly. The processing functions for an interest stream may be designed to model the functional paradigm. One example of such a user-defined function is one which estimates the frequency at which interests are used for a given namespace. Another example is a function which estimates the frequency of message failures (e.g., interest returns) for a given namespace.
Exemplary Communication Via a Query that is an Interest Message
Application 250 can generate an interest message 302 with a name 302.1 of the following format: “/r_prefix/type=outstanding-window-size/id=<id>/auth=<sig+cert>/<nonce>.” The variables in name 302.1 can be defined as follows: “/r_prefix” is a routable name prefix which includes one or more contiguous name components ordered beginning from the most general level (e.g., “/a/b2/fileN” or “/parc/ccn/file1”); “type” indicates the type of command or query (e.g., an outstanding window size which corresponds to a number of outstanding interests for the routable prefix or namespace, a number of interests answered correctly in a specific period of time, and other examples as described above in the section entitled “Exemplary Historical Information”); “id” indicates a user identifier of the requesting entity (e.g., “<id>”); “auth” indicates authentication information of the requesting entity, which can include the signature and/or digital certificate of the requesting entity (e.g., “<sig+cert>”); and “<nonce>” is a randomly generated nonce to ensure both uniqueness and freshness.
In some embodiments, name 302.1 can include one or more specific namespaces of the routable prefix for which the historical information is requested. Furthermore, the variables defined above and depicted as included in the name for the interest can be included in other fields of the interest. In other words, the variables and information included in name 302.1 can alternatively be indicated in interest 302 in other fields (not shown).
In addition, name 302.1 can include a string for the query (e.g., “outstanding-window-size”), one or more parameters for the query, and a function for the query. For example, the function for the query can indicate a request for the responding entity (e.g., the collector component) to perform a function or compute information based on the historical information, such as an average RTT for a given namespace, an estimate of the transmission window size for a given namespace, or a user-defined function (as described above in the section entitled “Exemplary Historical Information”). Interest 312 can also include a payload 312.2 with a value of “<data>” (e.g., if the requesting entity needs to provide additional data for the collector component to retrieve specific historical information or to perform a function or other computation).
Collector 242, as the responding entity, can receive interest 302, perform a lookup in storage 242.1 for the queried historical information, and subsequently return a response which can be a content object (not shown) that includes the queried historical information. The responsive content object can travel on a reverse path as interest 302 back to application 250. If the query includes a command to perform a function, the responsive content object can include the result of the function. The function may be performed by collector 242, or by another responding entity.
Exemplary Communication Via a Query that is a Control Message
Collector 242, as the responding entity, can receive control message 332, perform a lookup in storage 242.1 for the queried historical information, and subsequently return a response that includes the queried historical information (and, if the command includes a function, the result of the function). The response, which can be a content object, can travel back on a reverse path as control message 332 back to application 210.
Requesting Entity Queries for Historical Information
The requesting entity transmits the query to a responding entity (operation 404). The requesting entity determines whether it receives the queried historical information (decision 406). If it does not, the operation returns. If the requesting entity does receive the queried historical information, the requesting entity performs an operation that increases network efficiency (operation 408). For example, if the historical information indicates that the outstanding window size is small (implying that the flow is not congested), the requesting entity may increase its rate of transmission of interests for that namespace. Similarly, if the historical information indicates that the outstanding window size is large (implying congestion), the requesting entity may decrease its rate of interest transmission for that namespace. The requesting entity can perform other operations, such as setting or changing: a window size; a rate of transmission for original (e.g., first or initially transmitted) interests; and a rate of transmission for re-transmitted interests.
Responding Entity Responds to Query for Historical Information
If the requesting entity is not successfully authenticated, the operation returns. If the requesting entity is successfully authenticated, the collector component determines the queried historical information (operation 506). The collector component can obtain the queried historical information from a local storage cache or another accessible storage medium. The collector component determines whether a function is included in the query (decision 508). If a function is not included in the query, the collector component transmits the queried historical information to the requesting entity, which causes the requesting entity to perform an operation that increases network efficiency (operation 512).
If a function is included in the query, the collector component performs the function included in the query based on the historical information (operation 510). For example, the function can be for an average RTT or an estimate of the transmission window size for a given namespace. The function can also be a user-defined function. These examples are described above in the section entitled “Exemplary Historical Information.” Upon performing the function, the collector component transmits the result of the function performed on the queried historical information to the requesting entity, which causes the requesting entity to perform an operation to increase network efficiency (operation 512). Depending on the identity and authority of the requesting entity, the collector may also sanitize the requested historical information before transmitting it back to the requesting entity.
Exemplary Computer System
Content-processing system 618 can include instructions, which when executed by computer system 602, can cause computer system 602 to perform methods and/or processes described in this disclosure. Specifically, content-processing system 618 may include instructions for sending and/or receiving data packets to/from other network nodes across a computer network, such as a content centric network (communication module 620). A data packet can include an interest packet or a content object packet with a name that is an HSVLI. Further, content-processing system 618 can include instructions for generating a query for historical information associated with interest and corresponding content object packets (query-generating module 622). Content-processing system 618 can include instructions for transmitting the query to a responding entity (communication module 620), and, in response to receiving the historical information from the responding entity (communication module 620), performing an operation that increases network efficiency based on the historical information (operation-performing module 624). Content-processing system 618 can further include instructions for setting or changing a window size, setting or changing a rate of transmission for re-transmitted interests, setting or changing a rate of transmission for original interests, wherein an original interest is not a re-transmitted interest, and performing an operation related to increasing the efficiency of the network (operation-performing module 624).
Content-processing system 618 can additionally include instructions for receiving a query from a requesting entity for historical information associated with interest and corresponding content object packets (communication module 620). Content-processing system 618 can include instructions for, in response to authenticating the requesting entity (entity-authenticating module 628), transmitting the queried historical information (communication module 620). Content-processing system 618 can include instructions for performing a function on the historical information, including computing an estimate of an average round trip time for an interest and a corresponding content object packet based on the name prefix, computing an estimate of a size of a transmission window for the name prefix, and performing a function defined by the system of a user of the system (function-performing module 626).
Data 630 can include any data that is required as input or that is generated as output by the methods and/or processes described in this disclosure. Specifically, data 630 can store at least: a name; a name that is an HSVLI; one or more name components; a name prefix; a namespace; a packet that corresponds to an interest or a content object; a transport framework; a protocol or transport stack; one or more components of a transport or protocol stack; a collector component; a portal instance associated with a transport or protocol stack; historical information (as described above in the section entitled “Exemplary Historical Information”); a round trip time; a predetermined amount of time; a request or query for historical information; a control message; a routable name prefix; a user identifier; authentication information; a type for a query; a string for a query; one or more query parameters; a function for a query; a result of the function for the query; a randomly generated nonce; an identifier for a local forwarder; a window size; a rate of transmission for re-transmitted interests; and a rate of transmission for original interests.
The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. The computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.
The methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above. When a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.
Furthermore, the methods and processes described above can be included in hardware modules. For example, the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed. When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.
The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 817441 | Niesz | Apr 1906 | A |
| 4309569 | Merkle | Jan 1982 | A |
| 4921898 | Lenney | May 1990 | A |
| 5070134 | Oyamada | Dec 1991 | A |
| 5110856 | Oyamada | May 1992 | A |
| 5214702 | Fischer | May 1993 | A |
| 5377354 | Scannell | Dec 1994 | A |
| 5506844 | Rao | Apr 1996 | A |
| 5629370 | Freidzon | May 1997 | A |
| 5845207 | Amin | Dec 1998 | A |
| 5870605 | Bracho | Feb 1999 | A |
| 6052683 | Irwin | Apr 2000 | A |
| 6085320 | Kaliski, Jr. | Jul 2000 | A |
| 6091724 | Chandra | Jul 2000 | A |
| 6173364 | Zenchelsky | Jan 2001 | B1 |
| 6226618 | Downs | May 2001 | B1 |
| 6233617 | Rothwein | May 2001 | B1 |
| 6233646 | Hahm | May 2001 | B1 |
| 6332158 | Risley | Dec 2001 | B1 |
| 6366988 | Skiba | Apr 2002 | B1 |
| 6574377 | Cahill | Jun 2003 | B1 |
| 6654792 | Verma | Nov 2003 | B1 |
| 6667957 | Corson | Dec 2003 | B1 |
| 6681220 | Kaplan | Jan 2004 | B1 |
| 6681326 | Son | Jan 2004 | B2 |
| 6732273 | Byers | May 2004 | B1 |
| 6769066 | Botros | Jul 2004 | B1 |
| 6772333 | Brendel | Aug 2004 | B1 |
| 6862280 | Bertagna | Mar 2005 | B1 |
| 6901452 | Bertagna | May 2005 | B1 |
| 6917985 | Madruga | Jul 2005 | B2 |
| 6968393 | Chen | Nov 2005 | B1 |
| 6981029 | Menditto | Dec 2005 | B1 |
| 7013389 | Srivastava | Mar 2006 | B1 |
| 7031308 | Garcia-Luna-Aceves | Apr 2006 | B2 |
| 7061877 | Gummalla | Jun 2006 | B1 |
| 7152094 | Jannu | Dec 2006 | B1 |
| 7177646 | ONeill | Feb 2007 | B2 |
| 7206860 | Murakami | Apr 2007 | B2 |
| 7206861 | Callon | Apr 2007 | B1 |
| 7210326 | Kawamoto | May 2007 | B2 |
| 7246159 | Aggarwal | Jul 2007 | B2 |
| 7257837 | Xu | Aug 2007 | B2 |
| 7287275 | Moskowitz | Oct 2007 | B2 |
| 7315541 | Housel | Jan 2008 | B1 |
| 7339929 | Zelig | Mar 2008 | B2 |
| 7350229 | Lander | Mar 2008 | B1 |
| 7362727 | ONeill | Apr 2008 | B1 |
| 7382787 | Barnes | Jun 2008 | B1 |
| 7395507 | Robarts | Jul 2008 | B2 |
| 7430755 | Hughes | Sep 2008 | B1 |
| 7444251 | Nikovski | Oct 2008 | B2 |
| 7466703 | Arunachalam | Dec 2008 | B1 |
| 7472422 | Agbabian | Dec 2008 | B1 |
| 7496668 | Hawkinson | Feb 2009 | B2 |
| 7509425 | Rosenberg | Mar 2009 | B1 |
| 7523016 | Surdulescu | Apr 2009 | B1 |
| 7542471 | Samuels | Jun 2009 | B2 |
| 7543064 | Juncker | Jun 2009 | B2 |
| 7552233 | Raju | Jun 2009 | B2 |
| 7555482 | Korkus | Jun 2009 | B2 |
| 7555563 | Ott | Jun 2009 | B2 |
| 7564812 | Elliott | Jul 2009 | B1 |
| 7567547 | Mosko | Jul 2009 | B2 |
| 7567946 | Andreoli | Jul 2009 | B2 |
| 7580971 | Gollapudi | Aug 2009 | B1 |
| 7623535 | Guichard | Nov 2009 | B2 |
| 7647507 | Feng | Jan 2010 | B1 |
| 7660324 | Oguchi | Feb 2010 | B2 |
| 7685290 | Satapati | Mar 2010 | B2 |
| 7698463 | Ogier | Apr 2010 | B2 |
| 7698559 | Chaudhury | Apr 2010 | B1 |
| 7769887 | Bhattacharyya | Aug 2010 | B1 |
| 7779467 | Choi | Aug 2010 | B2 |
| 7801177 | Luss | Sep 2010 | B2 |
| 7816441 | Elizalde | Oct 2010 | B2 |
| 7831733 | Sultan | Nov 2010 | B2 |
| 7908337 | Garcia-Luna-Aceves | Mar 2011 | B2 |
| 7924837 | Shabtay | Apr 2011 | B1 |
| 7953014 | Toda | May 2011 | B2 |
| 7953885 | Devireddy | May 2011 | B1 |
| 8000267 | Solis | Aug 2011 | B2 |
| 8010691 | Kollmansberger | Aug 2011 | B2 |
| 8074289 | Carpentier | Dec 2011 | B1 |
| 8117441 | Kurien | Feb 2012 | B2 |
| 8160069 | Jacobson | Apr 2012 | B2 |
| 8204060 | Jacobson | Jun 2012 | B2 |
| 8214364 | Bigus | Jul 2012 | B2 |
| 8224985 | Takeda | Jul 2012 | B2 |
| 8225057 | Zheng | Jul 2012 | B1 |
| 8271578 | Sheffi | Sep 2012 | B2 |
| 8312064 | Gauvin | Nov 2012 | B1 |
| 8386622 | Jacobson | Feb 2013 | B2 |
| 8447851 | Anderson | May 2013 | B1 |
| 8462781 | McGhee | Jun 2013 | B2 |
| 8467297 | Liu | Jun 2013 | B2 |
| 8473633 | Eardley | Jun 2013 | B2 |
| 8553562 | Allan | Oct 2013 | B2 |
| 8572214 | Garcia-Luna-Aceves | Oct 2013 | B2 |
| 8654649 | Vasseur | Feb 2014 | B2 |
| 8665757 | Kling | Mar 2014 | B2 |
| 8667172 | Ravindran | Mar 2014 | B2 |
| 8677451 | Bhimaraju | Mar 2014 | B1 |
| 8688619 | Ezick | Apr 2014 | B1 |
| 8699350 | Kumar | Apr 2014 | B1 |
| 8718055 | Vasseur | May 2014 | B2 |
| 8750820 | Allan | Jun 2014 | B2 |
| 8761022 | Chiabaut | Jun 2014 | B2 |
| 8762477 | Xie | Jun 2014 | B2 |
| 8762570 | Qian | Jun 2014 | B2 |
| 8762707 | Killian | Jun 2014 | B2 |
| 8767627 | Ezure | Jul 2014 | B2 |
| 8817594 | Gero | Aug 2014 | B2 |
| 8826381 | Kim | Sep 2014 | B2 |
| 8832302 | Bradford | Sep 2014 | B1 |
| 8836536 | Marwah | Sep 2014 | B2 |
| 8862774 | Vasseur | Oct 2014 | B2 |
| 8868779 | ONeill | Oct 2014 | B2 |
| 8874842 | Kimmel | Oct 2014 | B1 |
| 8880682 | Bishop | Nov 2014 | B2 |
| 8903756 | Zhao | Dec 2014 | B2 |
| 8923293 | Jacobson | Dec 2014 | B2 |
| 8934496 | Vasseur | Jan 2015 | B2 |
| 8937865 | Kumar | Jan 2015 | B1 |
| 8972969 | Gaither | Mar 2015 | B2 |
| 8977596 | Montulli | Mar 2015 | B2 |
| 9071498 | Beser | Jun 2015 | B2 |
| 9112895 | Lin | Aug 2015 | B1 |
| 20020010795 | Brown | Jan 2002 | A1 |
| 20020038296 | Margolus | Mar 2002 | A1 |
| 20020048269 | Hong | Apr 2002 | A1 |
| 20020054593 | Morohashi | May 2002 | A1 |
| 20020077988 | Sasaki | Jun 2002 | A1 |
| 20020078066 | Robinson | Jun 2002 | A1 |
| 20020138551 | Erickson | Sep 2002 | A1 |
| 20020152305 | Jackson | Oct 2002 | A1 |
| 20020176404 | Girard | Nov 2002 | A1 |
| 20020188605 | Adya | Dec 2002 | A1 |
| 20020199014 | Yang | Dec 2002 | A1 |
| 20030004621 | Bousquet | Jan 2003 | A1 |
| 20030033394 | Stine | Feb 2003 | A1 |
| 20030046396 | Richter | Mar 2003 | A1 |
| 20030046437 | Eytchison | Mar 2003 | A1 |
| 20030048793 | Pochon | Mar 2003 | A1 |
| 20030051100 | Patel | Mar 2003 | A1 |
| 20030061384 | Nakatani | Mar 2003 | A1 |
| 20030074472 | Lucco | Apr 2003 | A1 |
| 20030088696 | McCanne | May 2003 | A1 |
| 20030097447 | Johnston | May 2003 | A1 |
| 20030099237 | Mitra | May 2003 | A1 |
| 20030140257 | Peterka | Jul 2003 | A1 |
| 20030229892 | Sardera | Dec 2003 | A1 |
| 20040024879 | Dingman | Feb 2004 | A1 |
| 20040030602 | Rosenquist | Feb 2004 | A1 |
| 20040064737 | Milliken | Apr 2004 | A1 |
| 20040071140 | Jason | Apr 2004 | A1 |
| 20040073617 | Milliken | Apr 2004 | A1 |
| 20040073715 | Folkes | Apr 2004 | A1 |
| 20040139230 | Kim | Jul 2004 | A1 |
| 20040221047 | Grover | Nov 2004 | A1 |
| 20040225627 | Botros | Nov 2004 | A1 |
| 20040252683 | Kennedy | Dec 2004 | A1 |
| 20050003832 | Osafune | Jan 2005 | A1 |
| 20050028156 | Hammond | Feb 2005 | A1 |
| 20050043060 | Brandenberg | Feb 2005 | A1 |
| 20050050211 | Kaul | Mar 2005 | A1 |
| 20050074001 | Mattes | Apr 2005 | A1 |
| 20050149508 | Deshpande | Jul 2005 | A1 |
| 20050159823 | Hayes | Jul 2005 | A1 |
| 20050198351 | Nog | Sep 2005 | A1 |
| 20050249196 | Ansari | Nov 2005 | A1 |
| 20050259637 | Chu | Nov 2005 | A1 |
| 20050262217 | Nonaka | Nov 2005 | A1 |
| 20050281288 | Banerjee | Dec 2005 | A1 |
| 20050286535 | Shrum | Dec 2005 | A1 |
| 20050289222 | Sahim | Dec 2005 | A1 |
| 20060010249 | Sabesan | Jan 2006 | A1 |
| 20060029102 | Abe | Feb 2006 | A1 |
| 20060039379 | Abe | Feb 2006 | A1 |
| 20060051055 | Ohkawa | Mar 2006 | A1 |
| 20060072523 | Richardson | Apr 2006 | A1 |
| 20060099973 | Nair | May 2006 | A1 |
| 20060129514 | Watanabe | Jun 2006 | A1 |
| 20060133343 | Huang | Jun 2006 | A1 |
| 20060146686 | Kim | Jul 2006 | A1 |
| 20060173831 | Basso | Aug 2006 | A1 |
| 20060193295 | White | Aug 2006 | A1 |
| 20060203804 | Whitmore | Sep 2006 | A1 |
| 20060206445 | Andreoli | Sep 2006 | A1 |
| 20060215684 | Capone | Sep 2006 | A1 |
| 20060223504 | Ishak | Oct 2006 | A1 |
| 20060256767 | Suzuki | Nov 2006 | A1 |
| 20060268792 | Belcea | Nov 2006 | A1 |
| 20070019619 | Foster | Jan 2007 | A1 |
| 20070073888 | Madhok | Mar 2007 | A1 |
| 20070078868 | Faulkner | Apr 2007 | A1 |
| 20070094265 | Korkus | Apr 2007 | A1 |
| 20070112880 | Yang | May 2007 | A1 |
| 20070124412 | Narayanaswami | May 2007 | A1 |
| 20070127457 | Mirtorabi | Jun 2007 | A1 |
| 20070160062 | Morishita | Jul 2007 | A1 |
| 20070162394 | Zager | Jul 2007 | A1 |
| 20070171828 | Dalal | Jul 2007 | A1 |
| 20070189284 | Kecskemeti | Aug 2007 | A1 |
| 20070195765 | Heissenbuttel | Aug 2007 | A1 |
| 20070204011 | Shaver | Aug 2007 | A1 |
| 20070209067 | Fogel | Sep 2007 | A1 |
| 20070239892 | Ott | Oct 2007 | A1 |
| 20070240207 | Belakhdar | Oct 2007 | A1 |
| 20070245034 | Retana | Oct 2007 | A1 |
| 20070253418 | Shiri | Nov 2007 | A1 |
| 20070255677 | Alexander | Nov 2007 | A1 |
| 20070255699 | Sreenivas | Nov 2007 | A1 |
| 20070255781 | Li | Nov 2007 | A1 |
| 20070274504 | Maes | Nov 2007 | A1 |
| 20070275701 | Jonker | Nov 2007 | A1 |
| 20070276907 | Maes | Nov 2007 | A1 |
| 20070283158 | Danseglio | Dec 2007 | A1 |
| 20070294187 | Scherrer | Dec 2007 | A1 |
| 20080005056 | Stelzig | Jan 2008 | A1 |
| 20080010366 | Duggan | Jan 2008 | A1 |
| 20080037420 | Tang | Feb 2008 | A1 |
| 20080043989 | Furutono | Feb 2008 | A1 |
| 20080046340 | Brown | Feb 2008 | A1 |
| 20080059631 | Bergstrom | Mar 2008 | A1 |
| 20080080440 | Yarvis | Apr 2008 | A1 |
| 20080101357 | Iovanna | May 2008 | A1 |
| 20080107034 | Jetcheva | May 2008 | A1 |
| 20080107259 | Satou | May 2008 | A1 |
| 20080123862 | Rowley | May 2008 | A1 |
| 20080133583 | Artan | Jun 2008 | A1 |
| 20080133755 | Pollack | Jun 2008 | A1 |
| 20080151755 | Nishioka | Jun 2008 | A1 |
| 20080159271 | Kutt | Jul 2008 | A1 |
| 20080165775 | Das | Jul 2008 | A1 |
| 20080186901 | Itagaki | Aug 2008 | A1 |
| 20080200153 | Fitzpatrick | Aug 2008 | A1 |
| 20080215669 | Gaddy | Sep 2008 | A1 |
| 20080216086 | Tanaka | Sep 2008 | A1 |
| 20080243992 | Jardetzky | Oct 2008 | A1 |
| 20080250006 | Dettinger | Oct 2008 | A1 |
| 20080256138 | Sim-Tang | Oct 2008 | A1 |
| 20080256359 | Kahn | Oct 2008 | A1 |
| 20080270618 | Rosenberg | Oct 2008 | A1 |
| 20080271143 | Stephens | Oct 2008 | A1 |
| 20080287142 | Keighran | Nov 2008 | A1 |
| 20080288580 | Wang | Nov 2008 | A1 |
| 20080298376 | Takeda | Dec 2008 | A1 |
| 20080320148 | Capuozzo | Dec 2008 | A1 |
| 20090006659 | Collins | Jan 2009 | A1 |
| 20090013324 | Gobara | Jan 2009 | A1 |
| 20090022154 | Kiribe | Jan 2009 | A1 |
| 20090024641 | Quigley | Jan 2009 | A1 |
| 20090030978 | Johnson | Jan 2009 | A1 |
| 20090037763 | Adhya | Feb 2009 | A1 |
| 20090052660 | Chen | Feb 2009 | A1 |
| 20090067429 | Nagai | Mar 2009 | A1 |
| 20090077184 | Brewer | Mar 2009 | A1 |
| 20090092043 | Lapuh | Apr 2009 | A1 |
| 20090097631 | Gisby | Apr 2009 | A1 |
| 20090103515 | Pointer | Apr 2009 | A1 |
| 20090113068 | Fujihira | Apr 2009 | A1 |
| 20090116393 | Hughes | May 2009 | A1 |
| 20090117922 | Bell | May 2009 | A1 |
| 20090132662 | Sheridan | May 2009 | A1 |
| 20090144300 | Chatley | Jun 2009 | A1 |
| 20090157887 | Froment | Jun 2009 | A1 |
| 20090185745 | Momosaki | Jul 2009 | A1 |
| 20090193101 | Munetsugu | Jul 2009 | A1 |
| 20090222344 | Greene | Sep 2009 | A1 |
| 20090228593 | Takeda | Sep 2009 | A1 |
| 20090254572 | Redlich | Oct 2009 | A1 |
| 20090268905 | Matsushima | Oct 2009 | A1 |
| 20090285209 | Stewart | Nov 2009 | A1 |
| 20090287835 | Jacobson | Nov 2009 | A1 |
| 20090288143 | Stebila | Nov 2009 | A1 |
| 20090288163 | Jacobson | Nov 2009 | A1 |
| 20090292743 | Bigus | Nov 2009 | A1 |
| 20090293121 | Bigus | Nov 2009 | A1 |
| 20090300079 | Shitomi | Dec 2009 | A1 |
| 20090300407 | Kamath | Dec 2009 | A1 |
| 20090300512 | Ahn | Dec 2009 | A1 |
| 20090307333 | Welingkar | Dec 2009 | A1 |
| 20090323632 | Nix | Dec 2009 | A1 |
| 20100005061 | Basco | Jan 2010 | A1 |
| 20100027539 | Beverly | Feb 2010 | A1 |
| 20100046546 | Ram | Feb 2010 | A1 |
| 20100057929 | Merat | Mar 2010 | A1 |
| 20100058346 | Narang | Mar 2010 | A1 |
| 20100088370 | Wu | Apr 2010 | A1 |
| 20100094767 | Miltonberger | Apr 2010 | A1 |
| 20100094876 | Huang | Apr 2010 | A1 |
| 20100098093 | Ejzak | Apr 2010 | A1 |
| 20100100465 | Cooke | Apr 2010 | A1 |
| 20100103870 | Garcia-Luna-Aceves | Apr 2010 | A1 |
| 20100124191 | Vos | May 2010 | A1 |
| 20100125911 | Bhaskaran | May 2010 | A1 |
| 20100131660 | Dec | May 2010 | A1 |
| 20100150155 | Napierala | Jun 2010 | A1 |
| 20100165976 | Khan | Jul 2010 | A1 |
| 20100169478 | Saha | Jul 2010 | A1 |
| 20100169503 | Kollmansberger | Jul 2010 | A1 |
| 20100180332 | Ben-Yochanan | Jul 2010 | A1 |
| 20100182995 | Hwang | Jul 2010 | A1 |
| 20100185753 | Liu | Jul 2010 | A1 |
| 20100195653 | Jacobson | Aug 2010 | A1 |
| 20100195654 | Jacobson | Aug 2010 | A1 |
| 20100195655 | Jacobson | Aug 2010 | A1 |
| 20100217874 | Anantharaman | Aug 2010 | A1 |
| 20100232402 | Przybysz | Sep 2010 | A1 |
| 20100232439 | Dham | Sep 2010 | A1 |
| 20100235516 | Nakamura | Sep 2010 | A1 |
| 20100246549 | Zhang | Sep 2010 | A1 |
| 20100250497 | Redlich | Sep 2010 | A1 |
| 20100250939 | Adams | Sep 2010 | A1 |
| 20100268782 | Zombek | Oct 2010 | A1 |
| 20100272107 | Papp | Oct 2010 | A1 |
| 20100281263 | Ugawa | Nov 2010 | A1 |
| 20100284309 | Allan | Nov 2010 | A1 |
| 20100284404 | Gopinath | Nov 2010 | A1 |
| 20100293293 | Beser | Nov 2010 | A1 |
| 20100322249 | Thathapudi | Dec 2010 | A1 |
| 20110013637 | Xue | Jan 2011 | A1 |
| 20110019674 | Iovanna | Jan 2011 | A1 |
| 20110022812 | vanderLinden | Jan 2011 | A1 |
| 20110029952 | Harrington | Feb 2011 | A1 |
| 20110055392 | Shen | Mar 2011 | A1 |
| 20110055921 | Narayanaswamy | Mar 2011 | A1 |
| 20110060716 | Forman | Mar 2011 | A1 |
| 20110060717 | Forman | Mar 2011 | A1 |
| 20110090908 | Jacobson | Apr 2011 | A1 |
| 20110106755 | Hao | May 2011 | A1 |
| 20110145597 | Yamaguchi | Jun 2011 | A1 |
| 20110145858 | Philpott | Jun 2011 | A1 |
| 20110149858 | Hwang | Jun 2011 | A1 |
| 20110153840 | Narayana | Jun 2011 | A1 |
| 20110158122 | Murphy | Jun 2011 | A1 |
| 20110161408 | Kim | Jun 2011 | A1 |
| 20110202609 | Chaturvedi | Aug 2011 | A1 |
| 20110219427 | Hito | Sep 2011 | A1 |
| 20110231578 | Nagappan | Sep 2011 | A1 |
| 20110239256 | Gholmieh | Sep 2011 | A1 |
| 20110258049 | Ramer | Oct 2011 | A1 |
| 20110264824 | Venkata Subramanian | Oct 2011 | A1 |
| 20110265159 | Ronda | Oct 2011 | A1 |
| 20110265174 | Thornton | Oct 2011 | A1 |
| 20110271007 | Wang | Nov 2011 | A1 |
| 20110286457 | Ee | Nov 2011 | A1 |
| 20110286459 | Rembarz | Nov 2011 | A1 |
| 20110295783 | Zhao | Dec 2011 | A1 |
| 20110299454 | Krishnaswamy | Dec 2011 | A1 |
| 20120011170 | Elad | Jan 2012 | A1 |
| 20120011551 | Levy | Jan 2012 | A1 |
| 20120023113 | Ferren | Jan 2012 | A1 |
| 20120036180 | Thornton | Feb 2012 | A1 |
| 20120047361 | Erdmann | Feb 2012 | A1 |
| 20120066727 | Nozoe | Mar 2012 | A1 |
| 20120106339 | Mishra | May 2012 | A1 |
| 20120114313 | Phillips | May 2012 | A1 |
| 20120120803 | Farkas | May 2012 | A1 |
| 20120127994 | Ko | May 2012 | A1 |
| 20120136676 | Goodall | May 2012 | A1 |
| 20120136936 | Quintuna | May 2012 | A1 |
| 20120136945 | Lee | May 2012 | A1 |
| 20120137367 | Dupont | May 2012 | A1 |
| 20120141093 | Yamaguchi | Jun 2012 | A1 |
| 20120155464 | Kim | Jun 2012 | A1 |
| 20120158973 | Jacobson | Jun 2012 | A1 |
| 20120163373 | Lo | Jun 2012 | A1 |
| 20120170913 | Isozaki | Jul 2012 | A1 |
| 20120179653 | Araki | Jul 2012 | A1 |
| 20120197690 | Agulnek | Aug 2012 | A1 |
| 20120198048 | Ioffe | Aug 2012 | A1 |
| 20120221150 | Arensmeier | Aug 2012 | A1 |
| 20120224487 | Hui | Sep 2012 | A1 |
| 20120226902 | Kim | Sep 2012 | A1 |
| 20120257500 | Lynch | Oct 2012 | A1 |
| 20120284791 | Miller | Nov 2012 | A1 |
| 20120290669 | Parks | Nov 2012 | A1 |
| 20120290919 | Melnyk | Nov 2012 | A1 |
| 20120291102 | Cohen | Nov 2012 | A1 |
| 20120314580 | Hong | Dec 2012 | A1 |
| 20120317307 | Ravindran | Dec 2012 | A1 |
| 20120322422 | Frecks | Dec 2012 | A1 |
| 20120323933 | He | Dec 2012 | A1 |
| 20120331112 | Chatani | Dec 2012 | A1 |
| 20130024560 | Vasseur | Jan 2013 | A1 |
| 20130041982 | Shi | Feb 2013 | A1 |
| 20130051392 | Filsfils | Feb 2013 | A1 |
| 20130054971 | Yamaguchi | Feb 2013 | A1 |
| 20130060962 | Wang | Mar 2013 | A1 |
| 20130066823 | Sweeney | Mar 2013 | A1 |
| 20130073552 | Rangwala | Mar 2013 | A1 |
| 20130074155 | Huh | Mar 2013 | A1 |
| 20130091539 | Khurana | Apr 2013 | A1 |
| 20130110987 | Kim | May 2013 | A1 |
| 20130111063 | Lee | May 2013 | A1 |
| 20130132719 | Kobayashi | May 2013 | A1 |
| 20130151584 | Westphal | Jun 2013 | A1 |
| 20130151646 | Chidambaram | Jun 2013 | A1 |
| 20130152070 | Bhullar | Jun 2013 | A1 |
| 20130163426 | Beliveau | Jun 2013 | A1 |
| 20130166668 | Byun | Jun 2013 | A1 |
| 20130173822 | Hong | Jul 2013 | A1 |
| 20130182568 | Lee | Jul 2013 | A1 |
| 20130182931 | Fan | Jul 2013 | A1 |
| 20130185406 | Choi | Jul 2013 | A1 |
| 20130191412 | Kitamura | Jul 2013 | A1 |
| 20130197698 | Shah | Aug 2013 | A1 |
| 20130198119 | Eberhardt, III | Aug 2013 | A1 |
| 20130212185 | Pasquero | Aug 2013 | A1 |
| 20130219038 | Lee | Aug 2013 | A1 |
| 20130219081 | Qian | Aug 2013 | A1 |
| 20130219478 | Mahamuni | Aug 2013 | A1 |
| 20130223237 | Hui | Aug 2013 | A1 |
| 20130227114 | Vasseur | Aug 2013 | A1 |
| 20130227166 | Ravindran | Aug 2013 | A1 |
| 20130242996 | Varvello | Sep 2013 | A1 |
| 20130250809 | Hui | Sep 2013 | A1 |
| 20130262365 | Dolbear | Oct 2013 | A1 |
| 20130282854 | Jang | Oct 2013 | A1 |
| 20130282860 | Zhang | Oct 2013 | A1 |
| 20130282920 | Zhang | Oct 2013 | A1 |
| 20130304758 | Gruber | Nov 2013 | A1 |
| 20130304937 | Lee | Nov 2013 | A1 |
| 20130325888 | Oneppo | Dec 2013 | A1 |
| 20130329696 | Xu | Dec 2013 | A1 |
| 20130336103 | Vasseur | Dec 2013 | A1 |
| 20130336323 | Srinivasan | Dec 2013 | A1 |
| 20130339481 | Hong | Dec 2013 | A1 |
| 20130343408 | Cook | Dec 2013 | A1 |
| 20140003232 | Guichard | Jan 2014 | A1 |
| 20140006354 | Parkison | Jan 2014 | A1 |
| 20140006565 | Muscariello | Jan 2014 | A1 |
| 20140029445 | Hui | Jan 2014 | A1 |
| 20140032714 | Liu | Jan 2014 | A1 |
| 20140040505 | Barton | Feb 2014 | A1 |
| 20140040628 | Fort | Feb 2014 | A1 |
| 20140047513 | vantNoordende | Feb 2014 | A1 |
| 20140074730 | Arensmeier | Mar 2014 | A1 |
| 20140075567 | Raleigh | Mar 2014 | A1 |
| 20140082135 | Jung | Mar 2014 | A1 |
| 20140089454 | Jeon | Mar 2014 | A1 |
| 20140096249 | Dupont | Apr 2014 | A1 |
| 20140108313 | Heidasch | Apr 2014 | A1 |
| 20140108474 | David | Apr 2014 | A1 |
| 20140112325 | Calcev | Apr 2014 | A1 |
| 20140115037 | Liu | Apr 2014 | A1 |
| 20140129736 | Yu | May 2014 | A1 |
| 20140136814 | Stark | May 2014 | A1 |
| 20140140348 | Perlman | May 2014 | A1 |
| 20140143370 | Vilenski | May 2014 | A1 |
| 20140146819 | Bae | May 2014 | A1 |
| 20140149733 | Kim | May 2014 | A1 |
| 20140156396 | deKozan | Jun 2014 | A1 |
| 20140165207 | Engel | Jun 2014 | A1 |
| 20140172783 | Suzuki | Jun 2014 | A1 |
| 20140172981 | Kim | Jun 2014 | A1 |
| 20140173034 | Liu | Jun 2014 | A1 |
| 20140173076 | Ravindran | Jun 2014 | A1 |
| 20140192717 | Liu | Jul 2014 | A1 |
| 20140195328 | Ferens | Jul 2014 | A1 |
| 20140195641 | Wang | Jul 2014 | A1 |
| 20140195666 | Dumitriu | Jul 2014 | A1 |
| 20140214942 | Ozonat | Jul 2014 | A1 |
| 20140233575 | Xie | Aug 2014 | A1 |
| 20140237085 | Park | Aug 2014 | A1 |
| 20140245359 | DeFoy | Aug 2014 | A1 |
| 20140254595 | Luo | Sep 2014 | A1 |
| 20140280823 | Varvello | Sep 2014 | A1 |
| 20140281489 | Peterka | Sep 2014 | A1 |
| 20140281505 | Zhang | Sep 2014 | A1 |
| 20140282816 | Xie | Sep 2014 | A1 |
| 20140289325 | Solis | Sep 2014 | A1 |
| 20140289790 | Wilson | Sep 2014 | A1 |
| 20140314093 | You | Oct 2014 | A1 |
| 20140337276 | Iordanov | Nov 2014 | A1 |
| 20140365550 | Jang | Dec 2014 | A1 |
| 20150006896 | Franck | Jan 2015 | A1 |
| 20150018770 | Baran | Jan 2015 | A1 |
| 20150032892 | Narayanan | Jan 2015 | A1 |
| 20150039890 | Khosravi | Feb 2015 | A1 |
| 20150063802 | Bahadur | Mar 2015 | A1 |
| 20150089081 | Thubert | Mar 2015 | A1 |
| 20150095481 | Ohnishi | Apr 2015 | A1 |
| 20150095514 | Yu | Apr 2015 | A1 |
| 20150188770 | Naiksatam | Jul 2015 | A1 |
| 20150195149 | Vasseur | Jul 2015 | A1 |
| 20150207633 | Ravindran | Jul 2015 | A1 |
| 20150207864 | Wilson | Jul 2015 | A1 |
| 20150248455 | Sevilla | Sep 2015 | A1 |
| 20160183168 | Horn | Jun 2016 | A1 |
| 20170257444 | Wood | Sep 2017 | A1 |
| 20170366526 | Wood | Dec 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2120402 | Nov 2009 | EP |
| 2120419 | Nov 2009 | EP |
| 2124415 | Nov 2009 | EP |
| 2214357 | Aug 2010 | EP |
| 2978174 | Jan 2016 | EP |
| 03049369 | Jun 2003 | WO |
| 2007144388 | Dec 2007 | WO |
| 2013123410 | Aug 2013 | WO |
| Entry |
|---|
| Jacobson, Van et al., “Content-Centric Networking, Whitepaper Describing Future Assurable Global Networks”, Palo Alto Research Center, Inc., Jan. 30, 2007, pp. 1-9. |
| Koponen, Teemu et al., “A Data-Oriented (and Beyond) Network Architecture”, SIGCOMM '07, Aug. 27-31, 2007, Kyoto, Japan, XP-002579021, p. 181-192. |
| Mahadevan, Priya, et al. “Orbis: rescaling degree correlations to generate annotated internet topologies.” ACM SIGCOMM Computer Communication Review. vol. 37. No. 4. ACM, 2007. |
| Mahadevan, Priya, et al. “Systematic topology analysis and generation using degree correlations.” ACM SIGCOMM Computer Communication Review. vol. 36. No. 4. ACM, 2006. |
| Beben et al., “Content Aware Network based on Virtual Infrastructure”, 2012 13th ACIS International Conference on Software Engineering. |
| Biradar et al., “Review of multicast routing mechanisms in mobile ad hoc networks”, Aug. 16, Journal of Network and Computer Applications 35 (2012) 221-229. |
| Detti et al., “Supporting the Web with an information centric network that routes by name”, Aug. 2012, Computer Networks 56, pp. 3705-3702. |
| Garcia-Luna-Aceves et al., “Automatic Routing Using Multiple Prefix Labels”, 2012, IEEE, Ad Hoc and Sensor Networking Symposium. |
| Ishiyama, “On the Effectiveness of Diffusive Content Caching in Content-Centric Networking”, Nov. 5, 2012, IEEE, Information and Telecommunication Technologies (APSITT), 2012 9th Asia-Pacific Symposium. |
| L. Wang et al., ‘OSPFN: An OSPF Based Routing Protocol for Named Data Networking,’ Technical Report NDN-0003, 2012. |
| Merindol et al., “An efficient algorithm to enable path diversity in link state routing networks”, Jan. 10, Computer Networks 55 (2011), pp. 1132-1140. |
| Soh et al., “Efficient Prefix Updates for IP Router Using Lexicographic Ordering and Updateable Address Set”, Jan. 2008, IEEE Transactions on Computers, vol. 57, No. 1. |
| V. Jacobson et al., ‘Networking Named Content,’ Proc. IEEE CoNEXT '09, Dec. 2009. |
| Ao-Jan Su, David R. Choffnes, Aleksandar Kuzmanovic, and Fabian E. Bustamante. Drafting Behind Akamai: Inferring Network Conditions Based on CDN Redirections. IEEE/ACM Transactions on Networking {Feb. 2009). |
| “PBC Library-Pairing-Based Cryptography-About,” http://crypto.stanford.edu/pbc. downloaded Apr. 27, 2015. |
| C. Gentry and A. Silverberg. Hierarchical ID-Based Cryptography. Advances in Cryptology—ASIACRYPT 2002. Springer Berlin Heidelberg (2002). |
| Boneh et al., “Collusion Resistant Broadcast Encryption With Short Ciphertexts and Private Keys”, 2005. |
| Hoque et al., “NLSR: Named-data Link State Routing Protocol”, Aug. 12, 2013, ICN'13. |
| D. Boneh and M. Franklin. Identity-Based Encryption from the Weil Pairing. Advances in Cryptology—CRYPTO 2001, vol. 2139, Springer Berlin Heidelberg (2001). |
| Xiong et al., “CloudSeal: End-to-End Content Protection in Cloud-based Storage and Delivery Services”, 2012. |
| J. Bethencourt, A, Sahai, and B. Waters, ‘Ciphertext-policy attribute-based encryption,’ in Proc. IEEE Security & Privacy 2007, Berkeley, CA, USA, May 2007, pp. 321-334. |
| J. Lotspiech, S. Nusser, and F. Pestoni. Anonymous Trust: Digit. |
| J. Shao and Z. Cao. CCA-Secure Proxy Re-Encryption without Pairings. Public Key Cryptography. Springer Lecture Notes in Computer ScienceVolume 5443 (2009). |
| Gopal et al. “Integrating content-based Mechanisms with hierarchical File systems”, Feb. 1999, University of Arizona, 15 pages. |
| R. H. Deng, J. Weng, S. Liu, and K. Chen. Chosen-Ciphertext Secure Proxy Re-Encryption without Pairings. CANS. Spring Lecture Notes in Computer Science vol. 5339 (2008). |
| RTMP (2009). Available online at http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/rtmp/ pdf/rtmp specification 1.0.pdf. |
| S. Chow, J. Weng, Y. Yang, and R. Deng. Efficient Unidirectional Proxy Re-Encryption. Progress in Cryptology—AFRICACRYPT 2010. Springer Berlin Heidelberg (2010). |
| S. Kamara and K. Lauter. Cryptographic Cloud Storage. Financial Cryptography and Data Security. Springer Berlin Heidelberg (2010). |
| Sandvine, Global Internet Phenomena Report—Spring 2012. Located online at http://www.sandvine.com/downloads/ documents/Phenomenal H 2012/Sandvine Global Internet Phenomena Report 1H 2012.pdf. |
| The Despotify Project (2012). Available online at http://despotify.sourceforge.net/. |
| V. K. Adhikari, S. Jain, Y. Chen, and Z.-L. Zhang. Vivisecting Youtube:An Active Measurement Study. In INFOCOM12 Mini-conference (2012). |
| Vijay Kumar Adhikari, Yang Guo, Fang Hao, Matteo Varvello, Volker Hilt, Moritz Steiner, and Zhi-Li Zhang. Unreeling Netflix: Understanding and Improving Multi-CDN Movie Delivery. In the Proceedings of IEEE INFOCOM 2012 (2012). |
| Jacobson, Van et al. ‘VoCCN: Voice Over Content-Centric Networks.’ Dec. 1, 2009. ACM ReArch'09. |
| Rosenberg, J. “Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols”, Apr. 2010, pp. 1-117. |
| Shih, Eugene et al., ‘Wake on Wireless: An Event Driven Energy Saving Strategy for Battery Operated Devices’, Sep. 23, 2002, pp. 160-171. |
| Fall, K. et al., “DTN: an architectural retrospective”, Selected areas in communications, IEEE Journal on, vol. 28, No. 5, Jun. 1, 2008, pp. 828-835. |
| Gritter, M. et al., ‘An Architecture for content routing support in the Internet’, Proceedings of 3rd Usenix Symposium on Internet Technologies and Systems, 2001, pp. 37-48. |
| “CCNx,” http://ccnx.org/. downloaded Mar. 11, 2015. |
| “Content Delivery Network”, Wikipedia, Dec. 10, 2011, http://en.wikipedia.org/w/index.php?title=Content_delivery_network&oldid=465077460. |
| “Digital Signature” archived on Aug. 31, 2009 at http://web.archive.org/web/20090831170721/http://en.wikipedia.org/wiki/Digital_signature. |
| “Introducing JSON,” http://www.json.org/. downloaded Mar. 11, 2015. |
| “Microsoft PlayReady,” http://www.microsoft.com/playready/.downloaded Mar. 11, 2015. |
| “Pursuing a pub/sub internet (PURSUIT),” http://www.fp7-pursuit.ew/PursuitWeb/. downloaded Mar. 11, 2015. |
| “The FP7 4WARD project,” http://www.4ward-project.eu/. downloaded Mar. 11, 2015. |
| A. Broder and A. Karlin, “Multilevel Adaptive Hashing”, Jan. 1990, pp. 43-53. |
| Detti, Andrea, et al. “CONET: a content centric inter-networking architecture.” Proceedings of the ACM SIGCOMM workshop on Information-centric networking. ACM, 2011. |
| A. Wolman, M. Voelker, N. Sharma N. Cardwell, A. Karlin, and H.M. Levy, “On the scale and performance of cooperative web proxy caching,” ACM SIGHOPS Operating Systems Review, vol. 33, No. 5, pp. 16-31, Dec. 1999. |
| Afanasyev, Alexander, et al. “Interest flooding attack and countermeasures in Named Data Networking.” IFIP Networking Conference, 2013. IEEE, 2013. |
| B. Ahlgren et al., ‘A Survey of Information-centric Networking’ IEEE Commun. Magazine, Jul. 2012, pp. 26-36. |
| Bari, MdFaizul, et al. ‘A survey of naming and routing in information-centric networks.’ Communications Magazine, IEEE 50.12 (2012): 44-53. |
| Baugher, Mark et al., “Self-Verifying Names for Read-Only Named Data”, 2012 IEEE Conference on Computer Communications Workshops (INFOCOM WKSHPS), Mar. 2012, pp. 274-279. |
| Brambley, Michael, A novel, low-cost, reduced-sensor approach for providing smart remote monitoring and diagnostics for packaged air conditioners and heat pumps. Pacific Northwest National Laboratory, 2009. |
| C.A. Wood and E. Uzun, “Flexible end-to-end content security in CCN,” in Proc. IEEE CCNC 2014, Las Vegas, CA, USA, Jan. 2014. |
| Carzaniga, Antonio, Matthew J. Rutherford, and Alexander L. Wolf. ‘A routing scheme for content-based networking.’ INFOCOM 2004. Twenty-third Annual Joint Conference of the IEEE Computer and Communications Societies. vol. 2. IEEE, 2004. |
| Cho, Jin-Hee, Ananthram Swami, and Ray Chen. “A survey on trust management for mobile ad hoc networks.” Communications Surveys & Tutorials, IEEE 13.4 (2011): 562-583. |
| Compagno, Alberto, et al. “Poseidon: Mitigating interest flooding DDoS attacks in named data networking.” Local Computer Networks (LCN), 2013 IEEE 38th Conference on. IEEE, 2013. |
| Conner, William, et al. “A trust management framework for service-oriented environments.” Proceedings of the 18th international conference on World wide web. ACM, 2009. |
| Content Centric Networking Project (CCN) [online], http://ccnx.org/releases/latest/doc/technical/, Downloaded Mar. 9, 2015. |
| Content Mediator Architecture for Content-aware Networks (COMET) Project [online], http://www.comet-project.org/, Downloaded Mar. 9, 2015. |
| D.K. Smetters, P. Golle, and J.D. Thornton, “CCNx access control specifications,” PARC, Tech. Rep., Jul. 2010. |
| Dabirmoghaddam, Ali, Maziar Mirzazad Barijough, and J. J. Garcia-Luna-Aceves. ‘Understanding optimal caching and opportunistic caching at the edge of information-centric networks.’ Proceedings of the 1st international conference on Information-centric networking. ACM, 2014. |
| Dijkstra, Edsger W., and Carel S. Scholten. ‘Termination detection for diffusing computations.’ Information Processing Letters 11.1 (1980): 1-4. |
| Dijkstra, Edsger W., Wim HJ Feijen, and A_J M. Van Gasteren. “Derivation of a termination detection algorithm for distributed computations.” Control Flow and Data Flow: concepts of distributed programming. Springer Berlin Heidelberg, 1986. 507-512. |
| E. Rescorla and N. Modadugu, “Datagram transport layer security,” IETF RFC 4347, Apr. 2006. |
| E.W. Dijkstra, W. Feijen, and A.J.M. Van Gasteren, “Derivation of a Termination Detection Algorithm for Distributed Computations,” Information Processing Letter, vol. 16, No. 5, 1983. |
| Fayazbakhsh, S. K., Lin, Y., Tootoonchian, A., Ghodsi, A., Koponen, T., Maggs, B., & Shenker, S. {Aug. 2013). Less pain, most of the gain: Incrementally deployable ICN. In ACM SIGCOMM Computer Communication Review (vol. 43, No. 4, pp. 147-158). ACM. |
| G. Tyson, S. Kaune, S. Miles, Y. El-Khatib, A. Mauthe, and A. Taweel, “A trace-driven analysis of caching in content-centric networks,” in Proc. IEEE ICCCN 2012, Munich, Germany, Jul.-Aug. 2012, pp. 1-7. |
| G. Wang, Q. Liu, and J. Wu, “Hierarchical attribute-based encryption for fine-grained access control in cloud storage services,” in Proc. ACM CCS 2010, Chicago, IL, USA, Oct. 2010, pp. 735-737. |
| G. Xylomenos et al., “A Survey of Information-centric Networking Research,” IEEE Communication Surveys and Tutorials, Jul. 2013. |
| Garcia, Humberto E., Wen-Chiao Lin, and Semyon M. Meerkov. “A resilient condition assessment monitoring system.” Resilient Control Systems (ISRCS), 2012 5th International Symposium on. IEEE, 2012. |
| Garcia-Luna-Aceves, Jose J. ‘A unified approach to loop-free routing using distance vectors or link states.’ ACM SIGCOMM Computer Communication Review. vol. 19. No. 4. ACM, 1989. |
| Garcia-Luna-Aceves, Jose J. ‘Name-Based Content Routing in Information Centric Networks Using Distance Information’ Proc ACM ICN 2014, Sep. 2014. |
| Ghali, Cesar, GeneTsudik, and Ersin Uzun. “Needle in a Haystack: Mitigating Content Poisoning in Named-Data Networking.” Proceedings of NDSS Workshop on Security of Emerging Networking Technologies (SENT). 2014. |
| Ghodsi, Ali, et al. “Information-centric networking: seeing the forest for the trees.” Proceedings of the 10th ACM Workshop on Hot Topics in Networks. ACM, 2011. |
| Ghodsi, Ali, et al. “Naming in content-oriented architectures.” Proceedings of the ACM SIGCOMM workshop on Information-centric networking. ACM, 2011. |
| Gupta, Anjali, Barbara Liskov, and Rodrigo Rodrigues. “Efficient Routing for Peer-to-Peer Overlays.” NSDI. vol. 4. 2004. |
| Heckerman, David, John S. Breese, and Koos Rommelse. “Decision-Theoretic Troubleshooting.” Communications of the ACM. 1995. |
| Heinemeier, Kristin, et al. “Uncertainties in Achieving Energy Savings from HVAC Maintenance Measures in the Field.” ASHRAE Transactions 118.Part 2 {2012). |
| Herlich, Matthias et al., “Optimizing Energy Efficiency for Bulk Transfer Networks”, Apr. 13, 2010, pp. 1-3, retrieved for the Internet: URL:http://www.cs.uni-paderborn.de/fileadmin/informationik/ag-karl/publications/miscellaneous/optimizing.pdf (retrieved on Mar. 9, 2012). |
| https://code.google.com/p/ccnx-trace/. |
| I. Psaras, R.G. Clegg, R. Landa, W.K. Chai, and G. Pavlou, “Modelling and evaluation of CCN-caching trees,” in Proc. IFIP Networking 2011, Valencia, Spain, May 2011, pp. 78-91. |
| Intanagonwiwat, Chalermek, Ramesh Govindan, and Deborah Estrin. ‘Directed diffusion: a scalable and robust communication paradigm for sensor networks.’ Proceedings of the 6th annual international conference on Mobile computing and networking. ACM, 2000. |
| J. Aumasson and D. Bernstein, “SipHash: a fast short-input PRF”, Sep. 18, 2012. |
| J. Hur, “Improving security and efficiency in attribute-based data sharing,” IEEE Trans. Knowledge Data Eng., vol. 25, No. 10, pp. 2271-2282, Oct. 2013. |
| Jacobson et al., “Custodian-Based Information Sharing,” Jul. 2012, IEEE Communications Magazine: vol. 50 Issue 7 (p. 3843). |
| Ji, Kun, et al. “Prognostics enabled resilient control for model-based building automation systems.” Proceedings of the 12th Conference of International Building Performance Simulation Association. 2011. |
| K. Liang, L. Fang, W. Susilo, and D.S. Wong, “A Ciphertext-policy attribute-based proxy re-encryption with chosen-ciphertext security,” in Proc. INCoS 2013, Xian, China, Sep. 2013, pp. 552-559. |
| Katipamula, Srinivas, and Michael R. Brambley. “Review article: methods for fault detection, diagnostics, and prognostics for building systemsa review, Part I.” HVAC&R Research 11.1 (2005): 3-25. |
| Katipamula, Srinivas, and Michael R. Brambley. “Review article: methods for fault detection, diagnostics, and prognostics for building systemsa review, Part II.” HVAC&R Research 11.2 (2005): 169-187. |
| L. Zhou, V. Varadharajan, and M. Hitchens, “Achieving secure role-based access control on encrypted data in cloud storage,” IEEE Trans. Inf. Forensics Security, vol. 8, No. 12, pp. 1947-1960, Dec. 2013. |
| Li, Wenjia, Anupam Joshi, and Tim Finin. “Coping with node misbehaviors in ad hoc networks: A multi-dimensional trust management approach.” Mobile Data Management (MDM), 2010 Eleventh International Conference on. IEEE, 2010. |
| Lopez, Javier, et al. “Trust management systems for wireless sensor networks: Best practices.” Computer Communications 33.9 (2010): 1086-1093. |
| M. Green and G. Ateniese, “Identity-based proxy re-encryption,” in Proc. ACNS 2007, Zhuhai, China, Jun. 2007, pp. 288-306. |
| M. Ion, J. Zhang, and E.M. Schooler, “Toward content-centric privacy in ICN: Attribute-based encryption and routing,” in Proc. ACM SIGCOMM ICN 2013, Hong Kong, China, Aug. 2013, pp. 39-40. |
| M. Naor and B. Pinkas “Efficient trace and revoke schemes,” in Proc. FC 2000, Anguilla, British West Indies, Feb. 2000, pp. 1-20. |
| M. Nystrom, S. Parkinson, A. Rusch, and M. Scott, “PKCS#12: Personal information exchange syntax v. 1.1,” IETF RFC 7292, K. Moriarty, Ed., Jul. 2014. |
| M. Parsa and J.J. Garcia-Luna-Aceves, “A Protocol for Scalable Loop-free Multicast Routing.” IEEE JSAC, Apr. 1997. |
| M. Walfish, H. Balakrishnan, and S. Shenker, “Untangling the web from DNS,” in Proc. USENIX NSDI 2004, Oct. 2010, pp. 735-737. |
| Matocha, Jeff, and Tracy Camp. ‘A taxonomy of distributed termination detection algorithms.’ Journal of Systems and Software 43.3 (1998): 207-221. |
| Matteo Varvello et al., “Caesar: A Content Router for High Speed Forwarding”, ICN 2012, Second Edition on Information-Centric Networking, New York, Aug. 2012. |
| Mobility First Project [online], http://mobilityfirst.winlab.rutgers.edu/, Downloaded Mar. 9, 2015. |
| Narasimhan, Sriram, and Lee Brownston. “HyDE—A General Framework for Stochastic and Hybrid Modelbased Diagnosis.” Proc. DX 7 (2007): 162-169. |
| NDN Project [online], http://www.named-data.net/, Downloaded Mar. 9, 2015. |
| Omar, Mawloud, Yacine Challal, and Abdelmadjid Bouabdallah. “Certification-based trust models in mobile ad hoc networks: A survey and taxonomy.” Journal of Network and Computer Applications 35.1 (2012): 268-286. |
| P. Mahadevan, E.Uzun, S. Sevilla, and J. Garcia-Luna-Aceves, “CCN-krs: A key resolution service for ccn,” in Proceedings of the 1st International Conference on Information-centric Networking, Ser. INC 14 New York, NY, USA: ACM, 2014, pp. 97-106. [Online]. Available: http://doi.acm.org/10.1145/2660129.2660154. |
| S. Deering, “Multicast Routing in Internetworks and Extended LANs,” Proc. ACM SIGCOMM '88, Aug. 1988. |
| S. Deering et al., “The PIM architecture for wide-area multicast routing,” IEEE/ACM Trans, on Networking, vol. 4, No. 2, Apr. 1996. |
| S. Jahid, P. Mittal, and N. Borisov, “EASiER: Encryption-based access control in social network with efficient revocation,” in Proc. ACM ASIACCS 2011, Hong Kong, China, Mar. 2011, pp. 411-415. |
| S. Kamara and K. Lauter, “Cryptographic cloud storage,” in Proc. FC 2010, Tenerife, Canary Islands, Spain, Jan. 2010, pp. 136-149. |
| S. Kumar et al. “Peacock Hashing: Deterministic and Updatable Hashing for High Performance Networking,” 2008, pp. 556-564. |
| S. Misra, R. Tourani, and N.E. Majd, “Secure content delivery in information-centric networks: Design, implementation, and analyses,” in Proc. ACM SIGCOMM ICN 2013, Hong Kong, China, Aug. 2013, pp. 73-78. |
| S. Yu, C. Wang, K. Ren, and W. Lou, “Achieving secure, scalable, and fine-grained data access control in cloud computing,” in Proc. IEEE INFOCOM 2010, San Diego, CA, USA, Mar. 2010, pp. 1-9. |
| S.J. Lee, M. Gerla, and C. Chiang, “On-demand Multicast Routing Protocol in Multihop Wireless Mobile Networks,” Mobile Networks and Applications, vol. 7, No. 6, 2002. |
| Scalable and Adaptive Internet Solutions (SAIL) Project [online], http://sail-project.eu/ Downloaded Mar. 9, 2015. |
| Schein, Jeffrey, and Steven T. Bushby. A Simulation Study of a Hierarchical, Rule-Based Method for System-Level Fault Detection and Diagnostics in HVAC Systems. US Department of Commerce,[Technology Administration], National Institute of Standards and Technology, 2005. |
| Shani, Guy, Joelle Pineau, and Robert Kaplow. “A survey of point-based POMDP solvers.” Autonomous Agents and Multi-Agent Systems 27.1 (2013): 1-51. |
| Sheppard, John W., and Stephyn GW Butcher. “A formal analysis of fault diagnosis with d-matrices.” Journal of Electronic Testing 23.4 (2007): 309-322. |
| Shneyderman, Alex et al., ‘Mobile VPN: Delivering Advanced Services in Next Generation Wireless Systems’, Jan. 1, 2003, pp. 3-29. |
| Solis, Ignacio, and J. J. Garcia-Luna-Aceves. ‘Robust content dissemination in disrupted environments.’ proceedings of the third ACM workshop on Challenged networks. ACM, 2008. |
| Sun, Ying, and Daniel S. Weld. “A framework for model-based repair.” AAAI. 1993. |
| T. Ballardie, P. Francis, and J. Crowcroft, “Core Based Trees (CBT),” Proc. ACM SIGCOMM '88, Aug. 1988. |
| T. Dierts, “The transport layer security (TLS) protocol version 1.2,” IETF RFC 5246, 2008. |
| T. Koponen, M. Chawla, B.-G. Chun, A. Ermolinskiy, K.H. Kim, S. Shenker, and I. Stoica, ‘A data-oriented (and beyond) network architecture,’ ACM SIGCOMM Computer Communication Review, vol. 37, No. 4, pp. 181-192, Oct. 2007. |
| V. Goyal, 0. Pandey, A. Sahai, and B. Waters, “Attribute-based encryption for fine-grained access control of encrypted data,” in Proc. ACM CCS 2006, Alexandria, VA, USA, Oct.-Nov. 2006, pp. 89-98. |
| V. Jacobson, D.K. Smetters, J.D. Thornton, M.F. Plass, N.H. Briggs, and R.L. Braynard, ‘Networking named content,’ in Proc. ACM CoNEXT 2009, Rome, Italy, Dec. 2009, pp. 1-12. |
| Verma, Vandi, Joquin Fernandez, and Reid Simmons. “Probabilistic models for monitoring and fault diagnosis.” The Second IARP and IEEE/RAS Joint Workshop on Technical Challenges for Dependable Robots in Human Environments. Ed. Raja Chatila. Oct. 2002. |
| Vutukury, Srinivas, and J. J. Garcia-Luna-Aceves. A simple approximation to minimum-delay routing. vol. 29. No. 4. ACM, 1999. |
| W.-G. Tzeng and Z.-J. Tzeng, “A public-key traitor tracing scheme with revocation using dynamic shares,” in Proc. PKC 2001, Cheju Island, Korea, Feb. 2001, pp. 207-224. |
| Waldvogel, Marcel “Fast Longest Prefix Matching: Algorithms, Analysis, and Applications”, A dissertation submitted to the Swiss Federal Institute of Technology Zurich, 2002. |
| Wang, Jiangzhe et al.,“DMND: Collecting Data from Mobiles Using Named Data”, Vehicular Networking Conference, 2010 IEEE, pp. 49-56. |
| Xylomenos, George, et al. “A survey of information-centric networking research.” Communications Surveys & Tutorials, IEEE 16.2 (2014): 1024-1049. |
| Yi, Cheng, et al. ‘A case for stateful forwarding plane.’ Computer Communications 36.7 (2013): 779-791. |
| Yi, Cheng, et al. ‘Adaptive forwarding in named data networking.’ ACM SIGCOMM computer communication review 42.3 (2012): 62-67. |
| Zahariadis, Theodore, et al. “Trust management in wireless sensor networks.” European Transactions on Telecommunications 21.4 (2010): 386-395. |
| Zhang, et al., “Named Data Networking (NDN) Project”, http://www.parc.com/publication/2709/named-data-networking-ndn-project.html, Oct. 2010, NDN-0001, PARC Tech Report. |
| Zhang, Lixia, et al. ‘Named data networking.’ ACM SIGCOMM Computer Communication Review 44.3 {2014): 66-73. |
| D. Trossen and G. Parisis, “Designing and realizing and information-centric internet,” IEEE Communications Magazing, vol. 50, No. 7, pp. 60-67, Jul. 2012. |
| Gasti, Paolo et al., ‘DoS & DDoS in Named Data Networking’, 2013 22nd International Conference on Computer Communications and Networks (ICCCN), Aug. 2013, pp. 1-7. |
| J. Hur and D.K. Noh, “Attribute-based access control with efficient revocation in data outsourcing systers,” IEEE Trans. Parallel Distrib. Syst, vol. 22, No. 7, pp. 1214-1221, Jul. 2011. |
| Kaya et al., “A Low Power Lookup Technique for Multi-Hashing Network Applications”, 2006 IEEE Computer Society Annual Symposium on Emerging VLSI Technologies and Architectures, Mar. 2006. |
| Hoque et al., ‘NLSR: Named-data Link State Routing Protocol’, Aug. 12, 2013, ICN 2013, pp. 15-20. |
| Nadeem Javaid, “Analysis and design of quality link metrics for routing protocols in Wireless Networks”, PhD Thesis Defense, Dec. 15, 2010, Universete Paris-Est. |
| Wetherall, David, “Active Network vision and reality: Lessons form a capsule-based system”, ACM Symposium on Operating Systems Principles, Dec. 1, 1999. pp. 64-79. |
| Kulkarni A.B. et al., “Implementation of a prototype active network”, IEEE, Open Architectures and Network Programming, Apr. 3, 1998, pp. 130-142. |
| Xie et al. “Collaborative Forwarding and Caching in Content Centric Networks”, Networking 2012. |
| Amadeo et al. “Design and Analysis of a Transport-Level Solution for Content-Centric VANETs”, University “Mediterranea” of Reggio Calabria, Jun. 15, 2013. |
| Lui et al. (A TLV-Structured Data Naming Scheme for Content-Oriented Networking, pp. 5822-5827, International Workshop on the Network of the Future, Communications (ICC), 2012 IEEE International Conference on Jun. 10-15, 2012). |
| Peter Dely et al. “OpenFlow for Wireless Mesh Networks” Computer Communications and Networks, 2011 Proceedings of 20th International Conference on, IEEE, Jul. 31, 2011 (Jul. 31, 2011), pp. 1-6. |
| Garnepudi Parimala et al “Proactive, reactive and hybrid multicast routing protocols for Wireless Mesh Networks”, 2013 IEEE International Conference on Computational Intelligence and Computing Research, IEEE, Dec. 26, 2013, pp. 1-7. |
| Tiancheng Zhuang et al. “Managing Ad Hoc Networks of Smartphones”, International Journal of Information and Education Technology, Oct. 1, 2013. |
| International Search Report and Written Opinion in counterpart International Application No. PCT/US2017/020798, dated Jun. 13, 2017, 10 pages. |
| Carofiglio, et al., “Optimal multipath congestion control and request forwarding in Information-Centric Networks,” 2013 21st IEEE International Conference on Network Protocols (ICNP), Oct. 2013, 10 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170257314 A1 | Sep 2017 | US |
