Patent Grant
9462057
This application claims the benefit under 35 U.S.C. §119(a) of Korean Patent Application No. 10-2013-0012476, filed on Feb. 4, 2013, the entire disclosure of which is incorporated herein by reference.
The following description relates to a content-centric networking method, and more particularly, to a location-based content-centric networking method.
Communication characteristics of the Internet users are content-centric rather than location-centric, focusing more on what content is to obtain than on where to obtain. To share content with another user in typical Internet protocol (IP)-based communication systems, a user needs to know an IP address (where) of another user to share content with. Also, it is required to build a connection link (or a path) between the IP of the user's device and the IP of the peer device. In an environment where such requirements are satisfied, the user further needs to use a third server for sharing content. Hence, the IP-based connection which is based on end-to-end communications may have difficulties in supporting content-centric data sharing services.
In contrast, content-centric networking is a new paradigm for the future Internet to overcome the limitations of current IP-based networking. The content-centric networking allows intermediate nodes on the Internet to store in a cache area the content that they transmit to another node and to thereby perform a role of a content server by transmitting the stored content to an Internet user on request. The content-centric networking is capable of providing a user with desired content from a closer location to the user, and thus can reduce the overall network communication load and a delay time in acquiring the content requested by the user.
In implementing the content-centric network, there is a need to develop data transmission algorithms which are suitable for Internet content characteristics. Currently, there is no clear distinction between the content creators and the content consumers, such that users can be both content creators and consumers at the same time, and content created by such users have local dependence. The users tend to acquire content located close to them among the location-based content, and are more likely to search for content based on landmarks.
Therefore, there is a need for an effective data transmission technology for location-based content in a content-centric network.
Related Patent Document: KR 10-2012-0058782 A
The following description relates to a method for effectively providing location-based content services in the field of content-centric networking-based communications.
In one general aspect, there is provided a location-based content-centric networking method for location-based content, including: naming location-based content in such a manner that the name given to the location-based content includes a hierarchical prefix corresponding to information contained in the location-based content; and forwarding the location-based content based on prefix information of the location-based content.
The naming of the location-based content may include defining a first prefix at a very beginning of the given name in order to distinguish the location-based content from other content by means of a longest prefix matching (LPM) scheme.
The naming of the collected location-based content may include defining a second prefix to clarify a user's intention. The user's intention may be to search or to advertise content.
The naming of the collected location-based content may include defining a third prefix to classify a type of the location-based content. The naming of the collected location-based content may include defining a fourth prefix including location information of the location-based content.
The naming of the collected location-based content may include defining a fifth prefix including a context name as a target of the location-based content. The location-based content-centric networking method may further include receiving a user's interest for requesting the location-based content. The user's interest may include an identifier of the location-based content requested by a user.
The forwarding of the location-based content may include transmitting the location-based content to neighboring nodes so as to advertise the content, or transmitting the user's interest to the neighboring nodes so as to acquire the location-based content requested by the user.
The forwarding of the location-based content may utilize location information about where the location-based content is created and location information of a node that receives the user's interest or the location-based content. The forwarding of the location-based content to the neighboring nodes comprises advertising created or updated location-based content to nodes within a predetermined range of area according to predefined rules.
A prefix which indicates advertisement of the location-based content may be previously registered in a pending interest table (PIT). A geographical range within which the location-based content is advertised may be determined by utilizing information about a distance between the location at which the location-based content is created and the location of the node.
The forwarding of the location-based content may include forwarding the user's interest for the location-based content using location information contained in the location-based content. The location-based content-centric networking method may further include registering in forwarding information base (FIB) prefix information which confirms that the location-based content is location-based content, so as to invoke a function to perform location-based forwarding with respect to the prefix information.
The location-based content-centric networking method may further include caching the location-based content. The caching of the location-based content may include determining, at a node that receives the location-based content, whether to cache the advertised location-based content, based on a distance between the node and the location at which the location-based content is created.
Also, the caching of the location-based content may include caching data in response to the user's interest, wherein a probability of cache replication being executed is set to be reduced with an increase in a distance between a node that receives the data and a target location of location-based content included in the data. In addition, the caching of the location-based content may include caching data in response to the user's interest, wherein a probability of cache replacement being executed is set to be increased with an increase in a distance between a node that receives the data and a location of the location-based content stored in the cache.
Other features and aspects will be apparent from the following detailed description, the drawings, and the claims.
Throughout the drawings and the detailed description, unless otherwise described, the same drawing reference numerals will be understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity, illustration, and convenience.
The invention is described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. It will be understood that for the purposes of this disclosure, “at least one of X, Y, and Z” can be construed as X only, Y only, Z only, or any combination of two or more items X, Y, and Z (e.g., XYZ, XZ, XYY, YZ, ZZ). Throughout the drawings and the detailed description, unless otherwise described, the same drawing reference numerals are understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Furthermore, the use of the terms a, an, etc. does not denote a limitation of quantity, but rather denotes the presence of at least one of the referenced item. The use of the terms “first,” “second,” and the like does not imply any particular order, but they are included to identify individual elements. Moreover, the use of the terms first, second, etc. does not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. It will be further understood that the terms “comprises” and/or “comprising”, or “includes” and/or “including” when used in this specification, specify the presence of stated features, regions, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, regions, integers, steps, operations, elements, components, and/or groups thereof. Although some features may be described with respect to individual exemplary embodiments, aspects need not be limited thereto such that features from one or more exemplary embodiments may be combinable with other features from one or more exemplary embodiments.
In addition, embodiments described in the specification are wholly hardware, and may be partially software or wholly software. In the specification, “unit”, “module”, “device”, “system”, or the like represents a computer related entity such as hardware, combination of hardware and software, or software. For example, in the specification, the unit, the module, the device, the system, or the like may be an executed process, a processor, an object, an executable file, a thread of execution, a program, and/or a computer, but are not limited thereto. For example, both of an application which is being executed in the computer and a computer may correspond to the unit, the module, the device, the system, or the like in the specification.
Content-centric networking operation mechanism for a location-based content-centric networking method in accordance with an exemplary embodiment is described herein.
The content-centric networking is based on two types of messages: interest and data.
The content-centric networking may use a method of “content request->content transmission” in which, in response to a user's interest in certain content, that is, a user's request or query about the content, being sent based on a name of the desired content, an intermediate node or a terminal node, which has corresponding content, transmits the content (i.e., data) to the user. Here, the nodes may refer to devices that provide cache or content-centric networking, or that provide similar functions.
More specifically, in S210, a user's interest is received. Although “interest” is a superordinate concept to “request” and “query,” it will be, hereinafter, referred to as “request.” The user's request may be received from an initial terminal that issues a request for data or an intermediate node that receives the request for data.
In S220, the intermediate node determines whether the requested data exists in a cache area. If a determination is made that the requested data exists in the cache area, corresponding data is transmitted through a path reverse to a path through which the user's request is transferred in S290.
If it is determined that the requested data is not present in the cache area, information of a pending interface table (PIT) is looked up in S230 to determine whether the user's request is a duplicate request in S240.
In response to a determination being made that the user's request is a duplicate request, the user's request is dropped in S250, and otherwise, it is determined, in S270, whether forwarding information base (FIB) exists. In response to a determination being made that the FIB exists, the user's request is transmitted to a neighboring node in S280.
There may be three critical factors in implementation of the above content-centric networking. The first is “content naming” to name content for identification, the second is “routing” or “forwarding” to assign the content name as an identifier, and the final is “cache management” performed in the process of “content request”->“content transmission.” The exemplary embodiments described herein are related to the provision of the three core factors.
A method for acquiring location information and a practical method of implementing content-centric networking are not within the scope of the present invention. In addition, in the following description, a detailed description of known functions and configurations incorporated herein will be omitted when it may obscure the subject matter with unnecessary detail. Further, terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The terms used herein are defined in consideration of functions according to exemplary embodiments, and can be varied according to a purpose of a user or manager, or precedent and so on. Therefore, definitions of the terms should be made on the basis of the overall context.
<Location-Based Content Naming>
Content naming for identification of content, as the most fundamental factor for the content-centric networking, is generally performed by first allocating a hierarchical prefix to a location (a physical location or a logical location) at which the content is present and then associating the prefix and a name of the content (e.g., file name, context name, etc.).
Such content naming is based on longest prefix matching (LPM) used in an IP-based network, and has, thus, an advantage in facilitating data routing based on the content name. For example, according to the above content naming, a document created by Ubiquitous Networked System (UbiNes) lab of Ajou University in Korea may be named as “/Korea/Ajou_Univ/UbiNeS/Report_CCN.”
In one example, a special prefix is assigned to identify location-based content in the content-centric networking. For example, a prefix, such as “/LBC,” may be placed at the very beginning of a content name, thereby facilitating the process branching based on an LPM algorithm.
In addition, a predefined prefix may be used to clarify the user's intention and purpose of the location-based content. For example, a prefix, such as “/FIND,” may be assigned if the user's intention is to search for location-based content. As another example, a prefix, such as “/ADV,” may be used if the user's intention is to advertise newly created location-based content. To classify location-based content as, for example, food, a context name, such as “/FOOD,” may be used.
In addition, a location at which location-based content is created is included in the name of the content. The creation location may be specified based on a geographical location (e.g., GPS coordinates and latitude/longitude coordinates), a logical location (e.g., predefined grid coordinates), landmarks (e.g., Incheon Airport, Seoul station, etc.) or based on a combination thereof.
Examples of naming of location-based content are provided below, which are illustrated in
Referring to
<Location-Based Content-Centric Routing>
The routing or forwarding of the location-based content in accordance with the exemplary embodiment of the present invention may have primarily two purposes. The first is to advertise or send the notification of created or updated location-based content to neighbors, and the second is to acquire user's desired location-based content. These two purposes are distinguished by the content names. For example, the content may start with a predefined prefix, such as “/LBC/ADV,” for the first purpose, or with a predefined prefix, such as “LB C/FIND,” for the second purpose.
To notify the neighbors of created or updated location-based content, an owner of the relevant content propagates data (content) to the neighbors. In this case, to conform to an operating method of the content-centric networking, i.e., “content request->content transmission,” information for the location-based content is defined in advance in the PIT, so that the data propagation is enabled by broadcasting the data to the neighbors under the restriction that the content is previously requested. As a prefix registered in the PIT, “LBC/ADV” may be used (refer to
Moreover, to acquire location-based content, a user request (interest) containing an identifier (name) of the user's desired location-based content is transmitted. As an example of the content identifier, the content name, such as “/LBC/FIND/LAT37.2843/LONG127.0444/R1Km/CAFÉ” provided above, may be used. Further, to process the user's request for the location-based content, a specific processing function for the prefix, for example, “LBC/FIND,” may be invoked (refer to
<Location-Based Content Cache Management>
In the exemplary embodiments of the present invention, two cache areas are defined. A first cache area caches location-based content which is created in the proximity of where a node exists, and a second cache area caches location-based content which is created at a distant location from where the node is present.
In the content-centric networking which does not deploy a third server for sharing content, the first cache area performs a role of a local server for the location-based content created in the proximity of where the node exists. In the course of advertising the location-based content, a node that has received the location-based content determines whether to cache the advertised location-based content, based on a distance from a location of creating the content. With respect to cache replacement, the first cache area does not remove but retains the location-based content for a predetermined period of time by means of an exclusive hold timer, thereby acting as a local server.
The second cache area is provided for caching in the process of reverse-path forwarding of data which is generated in response to a request created by the Internet user. There may be generally two types of cache management schemes for the content-centric networking: cache replication and cache replacement. Cache replication is to determine whether to cache data, and cache replacement is to choose victim content in the event of lack of sufficient cache space.
In the aforementioned caching procedures according to the exemplary embodiments, location information included in the data, regarding the location at which the location-based content is created, and location information of a node that receives the data are utilized. As a distance between the locations indicated by each of the location information becomes greater, a probability of the location-based content being a target of cache replication may be decreased, while a probability of being a target of cache replacement may be increased. Accordingly, a probability of content being cached may be set to be decreased with an increase of a distance between the location contained in the data and the location at which the content is created. This is because generally Internet users request location-based content that is located in user's proximity.
In one exemplary embodiment, a content search method for searching for location-based content cached by the two schemes in response to a user's request is provided. In response to receiving the user's request (interest), a node searches for the requested content from among pieces of location-based content cached by the second cache area. Like the content search performed in general content-centric networking, the searching may be carried out by immediate matching of the pieces of content, based on the content name included in the request.
If the node that receives the request fails to find the desired location-based content via the immediate match, the node searches for the content from among pieces of location-based content cached by the first cache area. The node that receives the request finds the desired location-based content based on content name specified in the request, and aggregates all the found location-based content into a single piece of data. Then, through a reverse path of the request, the node transmits the data to the user who creates the request.
Here, a determination whether the node has the requested location-based content may be made by comparing an area of the location-based content and the creation location at which the location-based content cached by the first cache area of the node which receives the request is created. If the remotest location-based content, among pieces of location-based content stored in the cache of the node that receives the request, is located farther than the location of creating the requested location-based content, a determination may be made that the node has the requested location-based content.
A primary purpose of a meta-algorithm for cache management according to the exemplary embodiment of the present invention is to allow a node to retain closely located content for as long as possible. By use of this meta-algorithm, the node can perform a role of a local content server. Referring back to
The meta-algorithm for cache management with a content store structure to cache content newly received in the data packet forwarding process may generally consist of two stages.
In the first stage, cache replication is performed to determine whether to cache received content by taking into consideration variables, such as a distance to a location at which the content is created, content creator information (“Signed Info” field of data packet), etc. At this time, a zone in which the content is to be cached is also determined. Generally, it is more frequent to request information about the nearby content than information about the remote location, and hence a cache probability may be designed to be decreased with an increase in the distance. Further, the reliability of the content creator may be taken into account in the cache probability. For example, since an administrator of online community website has more reliability than others, content, for example, menus in the website, which is made by the administrator, may be given a higher probability of being cached.
In the second stage, in the event of there being lack of storage space to cache new content in the content store, cache replacement is performed to determine which content to be replaced with the new content. In the case of cold zone, as performed in the first stage, variables are taken into account to select content to be first deleted from the cache area, wherein the selected content may be located far from the node and created by a creator with a lower reliability. If content having old information with the same context as the context of the new content is present in the cache area, this content is replaced with the new content.
In the case of hot zone, various existing content replacement algorithm can be applied to the content which is located far from the node, variables, such as a distance or a creator, may be assigned as weights.
The content cached in the cold zone may be a subset of requested information included in the content name. Therefore, pieces of content having the same name in the cold zone may be processed by an aggregation operation. Further, although the content cached in hot zone includes all the requested information that are indicated by the content name, periodic update of content is performed in consideration of the lifetime of content created by a user.
As apparently described above, the location-based content-centric networking method provides content naming, which enables the user to identify the location-based content and the user's intention of use, allows neighboring terminals to recognize the created location-based content, and offers a method of requesting and acquiring the location-based content and the cache management schemes, and thereby it is possible to effectively transmit the location-based content.
A number of examples have been described above. Nevertheless, it will be understood that various modifications may be made. For example, suitable results may be achieved if the described techniques are performed in a different order and/or if components in a described system, architecture, device, or circuit are combined in a different manner and/or replaced or supplemented by other components or their equivalents. Accordingly, other implementations are within the scope of the following claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2013-0012476 | Feb 2013 | KR | national |
| Number | Name | Date | Kind |
|---|---|---|---|
| 8638271 | Wang | Jan 2014 | B2 |
| 20010056416 | Garcia-Luna-Aceves | Dec 2001 | A1 |
| 20020143984 | Hudson Michel | Oct 2002 | A1 |
| 20070156842 | Vermeulen | Jul 2007 | A1 |
| 20090285209 | Stewart | Nov 2009 | A1 |
| 20100195654 | Jacobson | Aug 2010 | A1 |
| 20100195655 | Jacobson | Aug 2010 | A1 |
| 20100229205 | Hakusui | Sep 2010 | A1 |
| 20100265951 | Fujita | Oct 2010 | A1 |
| 20100299702 | Lo | Nov 2010 | A1 |
| 20110082982 | Harvell | Apr 2011 | A1 |
| 20110107379 | Lajoie | May 2011 | A1 |
| 20110161355 | Lee | Jun 2011 | A1 |
| 20110265174 | Thornton | Oct 2011 | A1 |
| 20120155348 | Jacobson | Jun 2012 | A1 |
| 20120159176 | Ravindran et al. | Jun 2012 | A1 |
| 20120166806 | Zhang | Jun 2012 | A1 |
| 20120204224 | Wang | Aug 2012 | A1 |
| 20120230199 | Chiabaut | Sep 2012 | A1 |
| 20120290696 | Wu | Nov 2012 | A1 |
| 20120297088 | Wang | Nov 2012 | A1 |
| 20120317307 | Ravindran | Dec 2012 | A1 |
| 20130007186 | Liu | Jan 2013 | A1 |
| 20130060962 | Wang et al. | Mar 2013 | A1 |
| 20130188513 | Vasseur et al. | Jul 2013 | A1 |
| 20130219081 | Qian | Aug 2013 | A1 |
| 20130227048 | Xie et al. | Aug 2013 | A1 |
| 20130242996 | Varvello | Sep 2013 | A1 |
| 20130258878 | Wakikawa | Oct 2013 | A1 |
| 20130282860 | Zhang | Oct 2013 | A1 |
| 20130282920 | Zhang | Oct 2013 | A1 |
| 20130290697 | Wang | Oct 2013 | A1 |
| 20130332955 | Hong | Dec 2013 | A1 |
| 20140032714 | Liu | Jan 2014 | A1 |
| 20140122737 | Silberstein | May 2014 | A1 |
| 20140143446 | Jacobson et al. | May 2014 | A1 |
| 20140146819 | Bae et al. | May 2014 | A1 |
| 20140173034 | Liu | Jun 2014 | A1 |
| 20140189060 | Westphal | Jul 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 10-2012-0014104 | Feb 2012 | KR |
| 1020120058782 | Jun 2012 | KR |
| 10-2012-0128042 | Nov 2012 | KR |
| 1020120136544 | Dec 2012 | KR |
| Entry |
|---|
| Korean Office Action dated Feb. 24, 2014 for KR 10-2013-0012476; no English Translation available at this time. |
| Korean Notice of Allowance issued on Nov. 25, 2014; no English Translation available at this time. |
| Number | Date | Country | |
|---|---|---|---|
| 20140222891 A1 | Aug 2014 | US |
