2 level routing in CCN
AssigneeTelefonaktiebolaget L M Ericsson (publ)
InventorCarlos Valencia Lopez
Life of this patent
Estimating the term…
Loading patent…
AssigneeTelefonaktiebolaget L M Ericsson (publ)
InventorCarlos Valencia Lopez
Estimating the term…
Exemplary methods at a content centric networking (CCN) gateway located at an autonomous system (AS), wherein the CCN gateway is communicatively coupled to a CCN domain name system (DNS) server, include receiving, on a first face, a first interest message comprising of a first content name identifying a first content being requested by the first interest message. The methods include in response to determining the first content is not located at the AS, determining a first remote AS name that identifies a first remote AS where the first content is located, generating a first 2-level (2L) content name comprising of the first remote AS name and the first content name, forwarding the first interest message comprising of the first 2L content name, and in response to receiving a first content object (CO) message comprising of the first 2L content name and the first content, forwarding the first content.
A method in a content centric networking (CCN) gateway located in an autonomous system (AS), wherein the CCN gateway is communicatively coupled to a CCN domain name system (DNS) server, the method comprising:
A content centric networking (CCN) gateway located at an autonomous system (AS), wherein the CCN gateway is communicatively coupled to a CCN domain name system (DNS) server, the CCN gateway comprising:
A non-transitory machine-readable storage medium having computer code stored therein, which when executed by a set of one or more processors of a content centric networking (CCN) gateway located at an autonomous system (AS), wherein the CCN gateway is communicatively coupled to a CCN domain name system (DNS) server, causes the CCN gateway to perform operations comprising:
A method in a content centric networking (CCN) domain name system (DNS) server that is communicatively coupled to a CCN gateway located at a first autonomous system (AS), the method comprising:
A content centric networking (CCN) domain name system (DNS) server that is communicatively coupled to a CCN gateway located at a first autonomous system (AS), the CCN DNS server comprising:
A non-transitory machine-readable storage medium having computer code stored therein, which when executed by a set of one or more processors of a content centric networking (CCN) domain name system (DNS) server that is communicatively coupled to a CCN gateway located at a first autonomous system (AS), causes the CCN DNS server to perform operations comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
No references of this kind are recorded.
Using standardised directories; using standardised directory access protocols: using domain name system [DNS]
Topology update or discovery: ensuring consistency of routing table updates, e.g. by using epoch numbers
Routing or path finding of packets in data switching networks: router architectures
Network directories; Name-to-address mapping: containing identifiers of data entities on a computer, e.g. file names
About 9 years of term left · ends 3 Nov 2035 (estimated)
Embodiments of the invention relate to the field of packet networks, and more specifically, to the 2 level routing of packets in content centric networks (CCNs).
An information centric network (ICN) is a conceptualization of a networking protocol stack, in particular layers 3 and above of a network protocol stack. CCN network as well as similar networks, such as, for example, named data networking (NDN) networks are particular architectures and implementations of an ICN network. ICN, CCN, and NDN networks are based on the premise of naming resources in these networks. In particular, the naming relates to the use of a globally shared namespace for objects that allows entities in these networks to retrieve any content of interest. NDN networks and CCN networks have similar architectures, and for sake of clarity, examples related to CCN networks are discussed herein below.
Within a CCN network, a name is utilized to identify a content object instead of an Internet Protocol (IP) address of the host of the content. In an IP network, routing is based on host names (e.g., source and destination addresses). In a CCN network by contrast, routing is based on a uniform resource identifier (URI) or similar identifier for a content object. CCN routing is performed hop-by-hop, using longest prefix matching on the CCN name. All communications seeking to access data are framed as a request and response transaction. A CCN client (e.g., executed by user equipment) sends a message referred to as a CCN interest packet/message to the nodes in the CCN network. An interest packet/message may herein be referred to simply as an “interest”. The nodes of the CCN network respond with a CCN object identified by a CCN name in the CCN interest. These CCN objects are returned via a CCN response referred to as a CCN content object (CO) packet/message. A CO message/packet may herein be referred to simply as a “CO”.
The invention may best be understood by referring to the following description and accompanying drawings that are used to illustrate embodiments of the invention. In the drawings:
FIG. 1 is a block diagram illustrating an architecture of a content centric networking (CCN) network according to one embodiment.
FIG. 2 is a block diagram illustrating an Internet architecture comprising of CCN networks according to one embodiment.
The following description describes methods and apparatus for performing 2 level routing in content centric networks (CCNs). In the following description, numerous specific details such as logic implementations, opcodes, means to specify operands, resource partitioning/sharing/duplication implementations, types and interrelationships of system components, and logic partitioning/integration choices are set forth in order to provide a more thorough understanding of the present invention. It will be appreciated, however, by one skilled in the art that the invention may be practiced without such specific details. In other instances, control structures, gate level circuits and full software instruction sequences have not been shown in detail in order not to obscure the invention. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.
References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
Bracketed text and blocks with dashed borders (e.g., large dashes, small dashes, dot-dash, and dots) may be used herein to illustrate optional operations that add additional features to embodiments of the invention. However, such notation should not be taken to mean that these are the only options or optional operations, and/or that blocks with solid borders are not optional in certain embodiments of the invention.