CN107196985B - Data management method and device and network equipment - Google Patents
Data management method and device and network equipment Download PDFInfo
- Publication number
- CN107196985B CN107196985B CN201610146813.0A CN201610146813A CN107196985B CN 107196985 B CN107196985 B CN 107196985B CN 201610146813 A CN201610146813 A CN 201610146813A CN 107196985 B CN107196985 B CN 107196985B
- Authority
- CN
- China
- Prior art keywords
- data
- request packet
- data request
- identifier
- packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a data management method, a data management device and network equipment, and belongs to the technical field of networks. The method comprises the following steps: receiving a data request packet sent by data request equipment, wherein the data request packet at least comprises a first source identifier, a first destination identifier and a request data identifier; searching the requested data in the CCM according to the first target identifier and the request data identifier; if the requested data is not found in the CCM, judging whether the data request packet allows caching; if the data request packet is allowed to be cached, the data content encapsulated in the data request packet is cached in the CCM with the first source identification and an identification of the data content encapsulated in the data request packet. The network equipment of the invention can not only forward the data request packet, but also decide whether to process the data request packet under the condition of not storing the request data, and can cache the data content packaged in the data request packet when processing the data request packet, thereby realizing the way cache of the data.
Description
Technical Field
The present invention relates to the field of network technologies, and in particular, to a data management method, an apparatus, and a network device.
Background
With the advancement of science and technology and the popularization of informatization, the main body of network application has been converted into data such as characters, images and videos, so the demand for sharing hardware resources in the internet field has been gradually reduced, and instead, data sharing becomes a main target. The user is no longer concerned about where the data is stored, but rather the data itself. Therefore, the conventional IP (Internet Protocol) network has a trend of gradually shifting to a network architecture centering on data content. For data content-centric network architectures, data is stored in the network, but different network architectures differ in the specific management of data, such as data discovery, data request and matching, data forwarding, and so on.
As shown in fig. 1, DONA (Data organized Network Architecture) employs an additional RH (name parser) to parse Data names, find Data and locate actual storage locations of the Data, and then transmit the Data through a conventional IP Network. See figure 1 for a detailed workflow of DONA: step 1-3 is a registration process of data on RH, a data publisher registers the data in RH so that a data requester can search and acquire the data in RH according to the name of the data; 4-7, a data requester searches data through RH, and after the data requester sends a data acquisition request to one RH, the RH sends the data acquisition request to a data publisher through the connection among the RH; steps 8-11 send data to the data requestor for the data publisher.
As shown in fig. 2, 4WARD (The Architecture and design for The future Internet, european union future network Architecture) registers and resolves data names through a hierarchical NRS (Name Resolution System). Referring to the specific workflow of 4WARD shown in FIG. 2, step 1-2, the data publisher registers the name of the data in the NRS; 3-6, the data requester obtains the actual storage position of the requested data through NRS; 7-9 and a-c, sending a data acquisition request to a data publisher by a data requestor through a routing device; steps 10-12 and steps d-f send data to the data requestor for the data publisher.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
for the two network architectures, after receiving a data acquisition request sent by a data requester, if a data publisher that does not request data itself receives any RH or routing device in the network architecture, the RH or routing device directly forwards the data acquisition request without performing any operation processing, and the processing manner of the data acquisition request is single and limited, which causes that the data requester can only acquire the requested data from one location of the data publisher, and the data acquisition request may need to be forwarded to the data publisher through forwarding of multiple devices, which increases the operations of each network device undoubtedly, is complicated, and reduces the data propagation efficiency and network performance.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention provide a data management method, an apparatus, and a network device. The technical scheme is as follows:
in a first aspect, a data management method is provided, the method including:
receiving a data request packet sent by a data request device, wherein the data request packet at least comprises a first source identifier, a first destination identifier and a request data identifier, the first source identifier is used for indicating the data request device, and the first destination identifier is used for indicating a storage device of requested data;
searching the requested data in a CCM (Cached Content Manager) according to the first destination identifier and the request data identifier;
if the requested data is not found in the CCM, judging whether the data request packet allows caching;
if the data request packet allows caching, caching the data content encapsulated in the data request packet in the CCM with the first source identification and an identification of the data content encapsulated in the data request packet.
In a first possible implementation manner of the first aspect, after the searching for the requested data in the CCM, the method further includes:
if the requested data is found in the CCM, discarding the data request packet, and encapsulating the requested data in a new data packet, wherein a second source identifier in the new data packet is the first destination identifier, and a second destination identifier in the new data packet is the first source identifier;
and determining a next hop address of the new data packet in a FIB (Forwarding Information Base, data Forwarding table) according to the second destination identifier, and Forwarding the new data packet according to the next hop address of the new data packet.
With reference to the first aspect, in a second possible implementation manner of the first aspect, after the determining whether the data request packet is allowed to be cached, the method further includes:
and if the data request packet does not allow caching, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
With reference to the first aspect, in a third possible implementation manner of the first aspect, the method further includes:
judging whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier and the request data identifier;
discarding the data request packet if the data request packet is already present in the loop detection record;
if the data request packet does not appear in the loop detection record, recording the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes:
acquiring path forwarding information included in the data request packet, wherein the path forwarding information records each network device through which the data request packet passes;
judging whether the own equipment identification appears in the path forwarding information;
if the data request packet appears in the path forwarding information, discarding the data request packet;
and if the data request packet does not appear in the path forwarding information, adding the equipment identifier in the path forwarding information, determining a next hop address of the data request packet in the FIB, and forwarding the data request packet according to the next hop address of the data request packet.
In a second aspect, there is provided a data management apparatus, the apparatus comprising:
a receiving module, configured to receive a data request packet sent by a data request device, where the data request packet at least includes a first source identifier, a first destination identifier, and a request data identifier, the first source identifier is used to indicate the data request device, and the first destination identifier is used to indicate a storage device of requested data;
the searching module is used for searching the requested data in the CCM according to the first target identifier and the request data identifier;
a first judging module, configured to judge whether the data request packet allows caching if the requested data is not found in the CCM;
and the cache module is used for caching the data content packaged in the data request packet in the CCM according to the first source identifier and the identifier of the data content packaged in the data request packet if the data request packet allows caching.
In a first possible implementation manner of the second aspect, the apparatus further includes:
a first processing module, configured to discard the data request packet and encapsulate the requested data in a new data packet if the requested data is found in the CCM, where a second source identifier in the new data packet is the first destination identifier, and a second destination identifier in the new data packet is the first source identifier; and determining the next hop address of the new data packet in the FIB according to the second destination identifier, and forwarding the new data packet according to the next hop address of the new data packet.
With reference to the second aspect, in a second possible implementation manner of the second aspect, the apparatus further includes:
and a second processing module, configured to determine, according to the first destination identifier, a next hop address of the data request packet in the FIB if the data request packet is not allowed to be cached, and forward the data request packet according to the next hop address of the data request packet.
With reference to the second aspect, in a third possible implementation manner of the second aspect, the apparatus further includes:
a second judging module, configured to judge whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier, and the request data identifier;
a third processing module, configured to discard the data request packet if the data request packet is already present in the loop detection record; if the data request packet does not appear in the loop detection record, recording the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
With reference to the second aspect, in a fourth possible implementation manner of the second aspect, the apparatus further includes:
an obtaining module, configured to obtain path forwarding information included in the data request packet, where the path forwarding information records each network device through which the data request packet passes;
a third judging module, configured to judge whether a device identifier of the third judging module is present in the path forwarding information;
a fourth processing module, configured to discard the data request packet if the data request packet is present in the path forwarding information; and if the data request packet does not appear in the path forwarding information, adding the equipment identifier in the path forwarding information, determining a next hop address of the data request packet in the FIB, and forwarding the data request packet according to the next hop address of the data request packet.
In a third aspect, a network device is provided, including: a transmitter, a receiver, a memory and a processor, wherein the memory, the transmitter and the receiver are respectively connected with the processor, the memory stores program codes, and the processor is used for calling the program codes and executing the following operations:
receiving, by the receiver, a data request packet sent by a data request device, where the data request packet at least includes a first source identifier, a first destination identifier, and a request data identifier, the first source identifier is used to indicate the data request device, and the first destination identifier is used to indicate a storage device of requested data;
searching the requested data in the CCM according to the first target identifier and the request data identifier;
if the requested data is not found in the CCM, judging whether the data request packet allows caching;
if the data request packet allows caching, caching the data content encapsulated in the data request packet in the CCM with the first source identification and an identification of the data content encapsulated in the data request packet.
In a first possible implementation manner of the third aspect, the processor is configured to invoke the program code and perform the following operations:
if the requested data is found in the CCM, discarding the data request packet, and encapsulating the requested data in a new data packet, wherein a second source identifier in the new data packet is the first destination identifier, and a second destination identifier in the new data packet is the first source identifier;
and determining the next hop address of the new data packet in the FIB according to the second destination identifier, and forwarding the new data packet according to the next hop address of the new data packet through the transmitter.
With reference to the third aspect, in a second possible implementation manner of the third aspect, the processor is configured to invoke the program code and perform the following operations:
and if the data request packet does not allow the cache, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet through the transmitter.
With reference to the third aspect, in a third possible implementation manner of the third aspect, the processor is configured to invoke the program code and perform the following operations:
judging whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier and the request data identifier;
discarding the data request packet if the data request packet is already present in the loop detection record;
if the data request packet does not appear in the loop detection record, recording the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet through the transmitter.
With reference to the third aspect, in a fourth possible implementation manner of the third aspect, the processor is configured to invoke the program code and perform the following operations:
acquiring path forwarding information included in the data request packet, wherein the path forwarding information records each network device through which the data request packet passes;
judging whether the own equipment identification appears in the path forwarding information;
if the data request packet appears in the path forwarding information, discarding the data request packet;
if the data request packet does not appear in the path forwarding information, adding the device identifier in the path forwarding information, determining a next hop address of the data request packet in the FIB, and forwarding the data request packet according to the next hop address of the data request packet through the transmitter.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
the network device not only forwards the data request packet sent by the data request device, but also determines whether to process the data request packet under the condition that the request data is not stored, and caches the data content encapsulated in the data request packet when the data request packet is processed, so that the data is cached along the path.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of data forwarding in a DONA network architecture provided in the background of the present invention;
fig. 2 is a schematic diagram of data forwarding in a 4WARD network architecture provided in the background of the present invention;
fig. 3A is a schematic diagram illustrating a specific deployment of a network architecture according to an embodiment of the present invention;
fig. 3B is a schematic structural diagram of a network device according to an embodiment of the present invention;
FIG. 4 is a flow chart of a data management method according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a data packet format according to an embodiment of the present invention;
FIG. 6 is a flow chart of a data management method according to an embodiment of the present invention;
FIG. 7 is a flow chart of a data management method according to an embodiment of the present invention;
FIG. 8 is a flow chart of a data management method according to an embodiment of the present invention;
FIG. 9 is a flow chart of a data management method according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a data management apparatus according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Fig. 3A is a schematic diagram of a specific deployment of a network architecture according to an embodiment of the present invention. Referring to fig. 3A, a network architecture provided in an embodiment of the present invention includes: user equipment, an ICN (Information center Network) router, a backbone Network, an IP router, and a data center. The user equipment is a data requester, namely equipment for requesting data; the data center is a data publisher, i.e., a device that stores data. Through data transmission of the ICN router, the backbone network and the IP router, the user equipment can acquire data from the data center.
The embodiment of the invention only carries out incremental deployment at the ICN router, and does not modify other network equipment in the traditional network, such as an IP router. Wherein each ICN router is provided with a CCM and a FIB. An ICN router is provided with a CCM at the present stage, the CCM is used for managing cache data, and the FIB is used for storing a route forwarding strategy. In the embodiment of the invention, the ICN router does not need to record the state of the data link and also has the function of caching along the path. That is, the ICN router may also cache the data content encapsulated in the data packet while forwarding the data packet initially initiated by the user equipment, so as to improve the information propagation efficiency. In addition, each data packet in the embodiment of the present invention may be forwarded using a unified forwarding mechanism, allowing one data packet to be forwarded through multiple paths, and preventing a loop through an intrinsic mechanism or path information carried by the data packet itself. See the examples which follow for details.
Fig. 3B is a schematic structural diagram of a network device according to an embodiment of the present invention, and referring to fig. 4, the network device includes: the system comprises a transmitter 301, a receiver 302, a memory 303 and a processor 304, wherein the memory 303, the transmitter 301 and the receiver 302 are respectively connected with the processor 304, the memory 303 stores program codes, and the processor 304 is used for calling the program codes and executing the following operations:
receiving, by a receiver 302, a data request packet sent by a data request device, where the data request packet at least includes a first source identifier, a first destination identifier, and a request data identifier, the first source identifier is used to indicate the data request device, and the first destination identifier is used to indicate a storage device of requested data;
searching the requested data in the CCM according to the first target identifier and the request data identifier; if the requested data is not found in the CCM, judging whether the data request packet allows caching; if the data request packet is allowed to be cached, the data content encapsulated in the data request packet is cached in the CCM with the first source identification and an identification of the data content encapsulated in the data request packet.
In another embodiment, the processor 304 is configured to invoke program code to perform the following operations:
if the requested data is found in the CCM, discarding the data request packet, and encapsulating the requested data in a new data packet, wherein a second source identifier in the new data packet is a first destination identifier, and a second destination identifier in the new data packet is a first source identifier;
and determining the next hop address of the new data packet in the data forwarding table FIB according to the second destination identifier, and forwarding the new data packet according to the next hop address of the new data packet through the transmitter 301.
In another embodiment, the processor 304 is configured to invoke program code to perform the following operations:
if the data request packet does not allow the cache, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet through the transmitter 301.
In another embodiment, the processor 304 is configured to invoke program code to perform the following operations:
judging whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier and the request data identifier;
if the data request packet appears in the loop detection record, discarding the data request packet;
if the data request packet does not appear in the loop detection record, the data request packet is recorded in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, the next hop address of the data request packet is determined in the FIB according to the first destination identifier, and the data request packet is forwarded according to the next hop address of the data request packet through the transmitter 301.
In another embodiment, the processor 304 is configured to invoke program code to perform the following operations:
acquiring path forwarding information included in the data request packet, wherein the path forwarding information records each network device through which the data request packet passes;
judging whether the own equipment identification appears in the path forwarding information;
if the data request packet appears in the path forwarding information, discarding the data request packet;
if the data request packet does not appear in the path forwarding information, adding the device identifier in the path forwarding information, determining a next hop address of the data request packet in the FIB, and forwarding the data request packet according to the next hop address of the data request packet through the transmitter 301.
The network device provided by the embodiment of the invention determines whether to process the data request packet according to the storage characteristics and requirements of the data packet except for forwarding the data request packet sent by the data request device under the condition that the request data is not stored, and caches the data content encapsulated in the data request packet when the data request packet is processed, so that the data is cached along the path.
Fig. 4 is a flowchart of a data management method according to an embodiment of the present invention. The interaction subject is a network device A and a network device B, wherein the network device A is a data request device, and the network device B is a storage device of requested data. Referring to fig. 4, a method flow provided by the embodiment of the present invention includes:
401. network device a sends a data request packet into the network in a specific data packet format.
In the embodiment of the present invention, when the network device a sends the data request packet, the data request packet adopts the data packet format as shown in fig. 5. Wherein, the specific meanings of each field are as follows:
destination Name (Destination Name): the name of the requesting data storage device. Any naming may be used. For example, a fixed-length address of 32 bits in IPv4(Internet Protocol Version 4 ); a hierarchical and indefinite-length address in a CCN (Content-Centric Networking ), which is not specifically limited in this embodiment of the present invention. In the embodiment of the present invention, the first destination identifier corresponds to a destination name for indicating a storage device of the requested data, i.e., the network device B.
Source Name (Source Name): the name of the data requestor; in the embodiment of the present invention, the first source identifier corresponds to a source name, which is used to indicate a data requesting device, i.e., network device a.
Content Name (Content Name): either as a complete name or as the remainder of the name relative to the source. In embodiments of the present invention, the request data identifies a corresponding content name.
TT L (Time To L ive) survival Time of data packet;
session Sequence (Sequence): a sequence number of the session;
content cached Specification (Cacheable Specification): specific specifications or constraints to be complied with when data content is cached by network equipment; for example, the data content is allowed to be cached for 1 minute, etc.
Publisher Information & Signature (Sender Information & Signature): information and signature of a data packet sender, which are used for detecting the validity of the data packet and the like;
other remarks (annotation): information requiring additional specification;
data Content (Content): the content itself. In the embodiment of the present invention, the data content item may be any data stored in the network device a.
402. After receiving the data request packet sent by the network device a, the network device B obtains the first destination identifier and the request data identifier carried in the data request packet, and searches for the requested data in the CCM according to the first destination identifier and the request data identifier. If the requested data is found in the CCM, then the following step 403 is performed; if the requested data is not found in the CCM, the following step 405 is performed.
The first destination identifier network device a may be obtained through a route such as google, which is not specifically limited in this embodiment of the present invention. The network framework provided by the embodiment of the invention adopts CCM to manage the cached data content. Currently, a network device is equipped with a CCM in which the data content is cached in a hash table storage structure. After receiving the data request packet, the network device B searches whether the data requested by the network device a is cached in the CCM corresponding to the network device B by using the first destination identifier and the request data identifier as keys.
403. If the requested data is found in the CCM, the network device B discards the data request packet and encapsulates the requested data in a new data packet, wherein the second source identifier in the new data packet is the first destination identifier of the data request packet, and the second destination identifier in the new data packet is the first source identifier of the data request packet.
In the embodiment of the present invention, if the network device B finds the requested data in the corresponding CCM, the network device a acquires the requested data stored in the CCM, and encapsulates the requested data in a new data packet and returns the new data packet to the network device a. The method comprises the following specific processes: the network device B discards the data request packet sent by the network device a and encapsulates the requested data in a new data packet. Wherein, the second source identifier in the new data packet is the first destination identifier of the data request packet, that is, the source name in the new data packet is the destination name in the data request packet sent by the network device a; the second destination identifier in the new data packet is the first source identifier of the data request packet, that is, the destination name in the new data packet is the source name in the data request packet sent by the network device a.
404. And the network equipment B determines the next hop address of the new data packet in the FIB according to the second destination identifier, and forwards the new data packet according to the next hop address of the new data packet.
After the data requested by the network device a is encapsulated in the new data packet, the network device B determines the next hop address of the new data packet in the FIB table according to the second destination identifier, and forwards the new data packet according to the next hop address, so as to return the new data packet to the network device a.
405. If the network device B does not find the requested data in the CCM, judging whether the data request packet allows caching; if the data request packet does not allow caching, then the following step 406 is performed; if the data request packet allows buffering, the following step 407 is performed.
In the embodiment of the present invention, when the network device forwards the data packet, whether to cache the data packet may be determined according to a specific context environment, that is, along-path caching is implemented. Since network device B does not find the requested data in the CCM, network device B processes the data request packet according to the storage characteristics and requirements of the data request packet. I.e. whether the data request packet is allowed to be buffered has been explicitly indicated in the data request packet. The storage characteristics and requirements may include packet validity time, requirements on a device allowing buffering, and the like, which is not particularly limited in this embodiment of the present invention. If the data request packet is not allowed to be cached, the data request packet sent by the network device a is forwarded in the manner shown in the following step 406 without any processing. If the data request packet is allowed to be cached, the data content encapsulated in the data request packet is cached in its corresponding CCM in the manner shown in step 407.
406. If the data request packet does not allow the cache, the network device B determines the next hop address of the data request packet in the FIB according to the first destination identifier, and forwards the data request packet according to the next hop address of the data request packet.
If the network device B judges that the data request packet is not allowed to be cached according to the storage characteristics and the requirements of the data request packet, the network device A does not process the request data packet sent by the network device A, directly determines the next hop address of the data request packet in the FIB, and forwards the data request packet according to the next hop address.
407. If the data request packet allows caching, the network device B caches the data content encapsulated in the data request packet in the CCM corresponding to the network device B according to the first source identifier and the identifier of the data content encapsulated in the data request packet.
In the embodiment of the present invention, in order to improve the information propagation efficiency, after determining that the data request packet is allowed to be cached, the network device B further caches the data content encapsulated in the data request packet in the CCM corresponding to the network device B according to the specific format. Since the data content is the data originally stored on the network device a, the data content is cached in the CCM corresponding to the network device B by using the first source identifier for indicating the network device a and the identifier of the data content, thereby realizing the way caching of the data in the network. In this way, when other network devices except the network device a in the network architecture in the subsequent process request the data content, the data content can be acquired from the network device a and also can be acquired from the network device B, so that the network propagation efficiency of the information is improved.
In the method provided by the embodiment of the invention, the network device not only forwards the data request packet sent by the data request device, but also determines whether to process the data request packet according to the storage characteristics and requirements of the data packet under the condition that the request data is not stored, and the data content encapsulated in the data request packet is cached when the data request packet is processed, so that the data is cached along the path.
Fig. 6 is a flowchart of a data management method according to an embodiment of the present invention. The interaction subject is a network device A and a network device B, wherein the network device A is a data request device, and the network device B is a storage device of requested data. Taking the method provided by the embodiment of the present invention implemented in an IP network as an example, referring to fig. 6, the method provided by the embodiment of the present invention includes:
601. network device a sends a data request packet into the network in a specific data packet format.
The network framework provided by the embodiment of the invention can realize incremental deployment in the existing IP network. In an IP network, the IP destination address corresponds to the "destination name" and the IP source address corresponds to the "source name", and other parts shown in fig. 5 may be encapsulated in an IP packet. Because the IP protocol supports no loop, the path is determined, so the system does not detect the loop; because the incremental deployment is possible, all network devices are not required to support, only part of the network devices are required to support the network framework provided by the embodiment of the invention, and other network devices can keep the original forwarding mode for forwarding, namely, the forwarding mode of the existing network device is used for forwarding.
602. After receiving the data request packet sent by the network device a, the network device B obtains the first IP destination address and the request data identifier carried in the data request packet, and searches for the requested data in the CCM according to the first IP destination address and the request data identifier. If the requested data is found in the CCM, then the following step 603 is performed; if the requested data is not found in the CCM, the following step 605 is performed.
603. If the requested data is found in the CCM, the network device B discards the data request packet and encapsulates the requested data in a new data packet, wherein the second IP source address in the new data packet is the first IP destination address of the data request packet, and the second IP destination address in the new data packet is the first IP source address of the data request packet.
604. And the network equipment B determines the next hop address of the new data packet in the FIB according to the second IP destination address, and forwards the new data packet according to the next hop address of the new data packet.
After the data requested by the network device a is encapsulated in the new data packet, the network device B determines the next hop address of the new data packet in the FIB table according to the second IP destination address, and forwards the new data packet according to the next hop address, so as to return the new data packet to the network device a.
605. If the network device B does not find the requested data in the CCM, judging whether the data request packet allows caching; if the data request packet does not allow caching, then go to step 606; if the data request packet allows buffering, the following step 607 is performed.
606. If the data request packet does not allow the cache, the network device B determines the next hop address of the data request packet in the FIB according to the first IP destination address, and forwards the data request packet according to the next hop address of the data request packet.
607. If the data request packet allows caching, the network device B caches the data content encapsulated in the data request packet in the CCM corresponding to the network device B according to the first IP source address and the identification of the data content encapsulated in the data request packet.
In the method provided by the embodiment of the invention, the network device not only forwards the data request packet sent by the data request device, but also determines whether to process the data request packet according to the storage characteristics and requirements of the data packet under the condition that the request data is not stored, and the data content encapsulated in the data request packet is cached when the data request packet is processed, so that the data is cached along the path.
It should be noted that the network framework provided by the embodiment of the present invention can also be applied to a new network architecture as an independent network layer protocol. And the network equipment forwards and caches the data packet according to the data packet forwarding process. Meanwhile, the network framework provided by the embodiment of the invention also supports multi-path forwarding. Compared with the data packet processing flow, the loop detection mechanism is added, and the loop problem caused by multipath forwarding is prevented. In the embodiment of the present invention, two different ways are adopted to perform loop detection prevention, the first is a detection mechanism for preventing a loop by using a local record, which is detailed in the embodiment shown in fig. 7; the second is a detection mechanism for preventing loop by using the path information of the packet itself, which is described in detail in the embodiment shown in fig. 8.
Fig. 7 is a flowchart of a data management method according to an embodiment of the present invention. The interaction subject is a network device A and a network device B, wherein the network device A is a data request device, and the network device B is a storage device of requested data. Referring to fig. 7, a method flow provided by the embodiment of the present invention includes:
701. network device a sends a data request packet into the network in a specific data packet format.
702. After receiving the data request packet sent by the network device a, the network device B obtains the first destination identifier and the request data identifier carried in the data request packet, and searches for the requested data in the CCM according to the first destination identifier and the request data identifier. If the requested data is found in the CCM, the following step 703 is performed; if the requested data is not found in the CCM, the following step 705 is performed.
703. If the requested data is found in the CCM, the network device B discards the data request packet and encapsulates the requested data in a new data packet, wherein the second source identifier in the new data packet is the first destination identifier of the data request packet, and the second destination identifier in the new data packet is the first source identifier of the data request packet.
704. And the network equipment B determines the next hop address of the new data packet in the FIB according to the second destination identifier, and forwards the new data packet according to the next hop address of the new data packet.
705. If the network device B does not find the requested data in the CCM, judging whether the data request packet allows caching; if the data request packet does not allow caching, the following steps 706 to 708 are performed directly; if the data request packet allows buffering, the following steps 706 to 708 are continued after the following step 709 is performed.
706. The network equipment B judges whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier and the request data identifier; if the data request packet is already present in the loop check record, then the following step 707 is performed; if the data request packet is not present in the loop check record, then step 708 is performed as follows.
In the embodiment of the present invention, the "destination name + source name + content name" is used as a key, and the forwarding trace of the data request packet is recorded in the local loop detection record. If the data request packet is already present in the loop detection record of the network device B, that is, if the network device B has forwarded the data request packet, the following step 707 is executed to discard the data request packet; if the data request packet does not appear in the loop detection record of the network device B, that is, if the network device B has not forwarded the data request packet, the following step 708 is executed to record the trace of the data packet, and then the following step 709 is executed to forward the data request packet through the FIB. The loop detection record may be implemented by a data structure such as a Bloom Filter (Bloom Filter) and a hash table, which is not specifically limited in this embodiment of the present invention.
707. If the data request packet is already present in the loop detection record, the network device B discards the data request packet sent by the network device a.
708. If the data request packet does not appear in the loop detection record, the network device B records the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determines a next hop address of the data request packet in the FIB according to the first destination identifier, and forwards the data request packet according to the next hop address of the data request packet.
709. If the data request packet allows caching, the network device B caches the data content encapsulated in the data request packet in the CCM corresponding to the network device B according to the first source identifier and the identifier of the data content encapsulated in the data request packet.
The method provided by the embodiment of the invention determines whether to process the data request packet according to the storage characteristics and requirements of the data packet except for forwarding the data request packet sent by the data request device under the condition that the request data is not stored, and caches the data content encapsulated in the data request packet when the data request packet is processed, so that the data is cached along the path.
Fig. 8 is a flowchart of a data management method according to an embodiment of the present invention. The interaction subject is a network device A and a network device B, wherein the network device A is a data request device, and the network device B is a storage device of requested data. Referring to fig. 8, a method flow provided by the embodiment of the present invention includes:
801. network device a sends a data request packet into the network in a specific data packet format.
802. After receiving the data request packet sent by the network device a, the network device B obtains the first destination identifier and the request data identifier carried in the data request packet, and searches for the requested data in the CCM according to the first destination identifier and the request data identifier. If the requested data is found in the CCM, the following step 803 is performed; if the requested data is not found in the CCM, the following step 805 is performed.
803. If the requested data is found in the CCM, the network device B discards the data request packet and encapsulates the requested data in a new data packet, wherein the second source identifier in the new data packet is the first destination identifier of the data request packet, and the second destination identifier in the new data packet is the first source identifier of the data request packet.
804. And the network equipment B determines the next hop address of the new data packet in the FIB according to the second destination identifier, and forwards the new data packet according to the next hop address of the new data packet.
805. If the network device B does not find the requested data in the CCM, judging whether the data request packet allows caching; if the data request packet does not allow caching, performing the following steps 806 to 808; if the data request packet is allowed to be cached, the following steps 806 to 808 are continued after the following step 809 is performed.
806. The network equipment B acquires path forwarding information included in the data request packet; judging whether the own equipment identification appears in the path forwarding information; if the data request packet is present in the path forwarding information, the following step 807 is executed; if the data request packet is not present in the path forwarding information, the following step 808 is performed.
In the embodiment of the present invention, each data request packet may further include path forwarding information. The path forwarding information records each network device through which the data request packet passes. Using the path information carried in the data request packet itself can be used to prevent loop. That is, after a data request packet passes through a network device, the name of the network device is recorded in its own path information. Therefore, if the received data request packet includes path forwarding information, network device B may check for a loop by looking up whether its name already exists in the path information of the data request packet.
807. If the data request packet appears in the path forwarding information, the network device B discards the data request packet sent by the network device a.
808. If the data request packet does not appear in the path forwarding information, the network device B adds a device identifier in the path forwarding information, determines a next hop address of the data request packet in the FIB, and forwards the data request packet according to the next hop address of the data request packet.
The device identifier added to the path forwarding information by the network device B is a name of the network device B, which is not specifically limited in this embodiment of the present invention.
809. If the data request packet allows caching, the network device B caches the data content encapsulated in the data request packet in the CCM corresponding to the network device B according to the first source identifier and the identifier of the data content encapsulated in the data request packet.
In the method provided by the embodiment of the invention, the network device not only forwards the data request packet sent by the data request device, but also determines whether to process the data request packet according to the storage characteristics and requirements of the data packet under the condition that the request data is not stored, and the data content encapsulated in the data request packet is cached when the data request packet is processed, so that the data is cached along the path.
Fig. 9 is a flowchart of a data management method according to an embodiment of the present invention. Referring to fig. 9, a method flow provided by the embodiment of the present invention includes:
901. receiving a data request packet sent by a data request device, wherein the data request packet at least comprises a first source identifier, a first destination identifier and a request data identifier, the first source identifier is used for indicating the data request device, and the first destination identifier is used for indicating a storage device of requested data.
902. And searching the requested data in the content cache manager CCM according to the first destination identifier and the request data identifier.
903. If the requested data is not found in the CCM, it is determined whether the data request packet is allowed to be cached.
904. If the data request packet is allowed to be cached, the data content encapsulated in the data request packet is cached in the CCM with the first source identification and an identification of the data content encapsulated in the data request packet.
In the method provided by the embodiment of the invention, the network device not only forwards the data request packet sent by the data request device, but also determines whether to process the data request packet according to the storage characteristics and requirements of the data packet under the condition that the request data is not stored, and the data content encapsulated in the data request packet is cached when the data request packet is processed, so that the data is cached along the path.
Optionally, after searching for the requested data in the CCM, the method further comprises:
if the requested data is found in the CCM, discarding the data request packet, and encapsulating the requested data in a new data packet, wherein a second source identifier in the new data packet is a first destination identifier, and a second destination identifier in the new data packet is a first source identifier;
and determining the next hop address of the new data packet in the FIB according to the second destination identifier, and forwarding the new data packet according to the next hop address of the new data packet.
Optionally, after determining whether the data request packet is allowed to be cached, the method further includes:
and if the data request packet does not allow the cache, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
Optionally, the method further comprises:
judging whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier and the request data identifier;
if the data request packet appears in the loop detection record, discarding the data request packet;
if the data request packet does not appear in the loop detection record, recording the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
Optionally, the method further comprises:
acquiring path forwarding information included in the data request packet, wherein the path forwarding information records each network device through which the data request packet passes;
judging whether the own equipment identification appears in the path forwarding information;
if the data request packet appears in the path forwarding information, discarding the data request packet;
and if the data request packet does not appear in the path forwarding information, adding an equipment identifier in the path forwarding information, determining a next hop address of the data request packet in the FIB, and forwarding the data request packet according to the next hop address of the data request packet.
All the above-mentioned optional technical solutions can be combined arbitrarily to form the optional embodiments of the present invention, and are not described herein again.
Fig. 10 is a schematic structural diagram of a data management apparatus according to an embodiment of the present invention. Referring to fig. 10, the apparatus includes: the device comprises a receiving module 1001, a searching module 1002, a first judging module 1003 and a caching module 1004.
A receiving module 1001, configured to receive a data request packet sent by a data request device, where the data request packet at least includes a first source identifier, a first destination identifier, and a request data identifier, the first source identifier is used to indicate the data request device, and the first destination identifier is used to indicate a storage device of requested data;
the searching module 1002 is configured to search for the requested data in the CCM according to the first destination identifier and the requested data identifier;
a first determining module 1003, configured to determine whether the data request packet allows caching if the requested data is not found in the CCM;
the caching module 1004 is configured to cache the data content encapsulated in the data request packet in CCM with the first source identifier and the identifier of the data content encapsulated in the data request packet if the data request packet allows caching.
Optionally, the apparatus further comprises:
a first processing module 1005, configured to discard the data request packet and encapsulate the requested data in a new data packet if the requested data is found in the CCM, where a second source identifier in the new data packet is a first destination identifier, and a second destination identifier in the new data packet is a first source identifier; and determining the next hop address of the new data packet in the FIB according to the second destination identifier, and forwarding the new data packet according to the next hop address of the new data packet.
Optionally, the apparatus further comprises:
a second processing module 1006, configured to determine, according to the first destination identifier, a next hop address of the data request packet in the FIB of the data forwarding table if the data request packet is not allowed to be cached, and forward the data request packet according to the next hop address of the data request packet.
Optionally, the apparatus further comprises:
a second determining module 1007, configured to determine whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier, and the request data identifier;
a third processing module 1008, configured to discard the data request packet if the data request packet is already present in the loop detection record; if the data request packet does not appear in the loop detection record, recording the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determining a next hop address of the data request packet in the FIB according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
Optionally, the apparatus further comprises:
an obtaining module 1009, configured to obtain path forwarding information included in the data request packet, where the path forwarding information records each network device through which the data request packet passes;
a third determining module 1010, configured to determine whether a device identifier of the third determining module is present in the path forwarding information;
a fourth processing module 1011, configured to discard the data request packet if the data request packet is present in the path forwarding information; and if the data request packet does not appear in the path forwarding information, adding an equipment identifier in the path forwarding information, determining a next hop address of the data request packet in the FIB, and forwarding the data request packet according to the next hop address of the data request packet.
The device provided by the embodiment of the invention determines whether to process the data request packet according to the storage characteristics and requirements of the data packet except for forwarding the data request packet sent by the data request device under the condition that the request data is not stored, and caches the data content encapsulated in the data request packet when the data request packet is processed, so that the data is cached along the path.
It should be noted that: in the data management device provided in the above embodiment, when performing data management, only the division of the above functional modules is exemplified, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the above described functions. In addition, the data management apparatus and the data management method provided in the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments and are not described herein again.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (11)
1. A method for managing data, the method comprising:
receiving a data request packet sent by a data request device, wherein the data request packet at least comprises data content stored in the data request device, a first source identifier, a first destination identifier and a request data identifier, the first source identifier is used for indicating the data request device, and the first destination identifier is used for indicating a storage device of requested data;
searching the requested data in the content cache manager CCM according to the first target identifier and the request data identifier;
if the requested data is not found in the CCM, judging whether the data request packet allows caching;
if the data request packet allows caching, caching the data content encapsulated in the data request packet in the CCM with the first source identification and an identification of the data content encapsulated in the data request packet.
2. The method of claim 1, wherein after said searching for the requested data in the Content Cache Manager (CCM), the method further comprises:
if the requested data is found in the CCM, discarding the data request packet, and encapsulating the requested data in a new data packet, wherein a second source identifier in the new data packet is the first destination identifier, and a second destination identifier in the new data packet is the first source identifier;
and determining a next hop address of the new data packet in a data forwarding table (FIB) according to the second destination identifier, and forwarding the new data packet according to the next hop address of the new data packet.
3. The method of claim 1, wherein after determining whether the data request packet is allowed to be buffered, the method further comprises:
and if the data request packet is not allowed to be cached, determining a next hop address of the data request packet in a data forwarding table (FIB) according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
4. The method of claim 1, further comprising:
judging whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier and the request data identifier;
discarding the data request packet if the data request packet is already present in the loop detection record;
if the data request packet does not appear in the loop detection record, recording the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determining a next hop address of the data request packet in a data forwarding table (FIB) according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
5. The method of claim 1, further comprising:
acquiring path forwarding information included in the data request packet, wherein the path forwarding information records each network device through which the data request packet passes;
judging whether the own equipment identification appears in the path forwarding information;
if the data request packet appears in the path forwarding information, discarding the data request packet;
if the data request packet does not appear in the path forwarding information, adding the device identifier in the path forwarding information, determining a next hop address of the data request packet in a data forwarding table (FIB), and forwarding the data request packet according to the next hop address of the data request packet.
6. A data management apparatus, characterized in that the apparatus comprises:
a receiving module, configured to receive a data request packet sent by a data request device, where the data request packet at least includes data content stored in the data request device, a first source identifier, a first destination identifier, and a request data identifier, the first source identifier is used to indicate the data request device, and the first destination identifier is used to indicate a storage device of requested data;
the searching module is used for searching the requested data in the content cache manager CCM according to the first target identifier and the request data identifier;
a first judging module, configured to judge whether the data request packet allows caching if the requested data is not found in the CCM;
and the cache module is used for caching the data content packaged in the data request packet in the CCM according to the first source identifier and the identifier of the data content packaged in the data request packet if the data request packet allows caching.
7. The apparatus of claim 6, further comprising:
a first processing module, configured to discard the data request packet and encapsulate the requested data in a new data packet if the requested data is found in the CCM, where a second source identifier in the new data packet is the first destination identifier, and a second destination identifier in the new data packet is the first source identifier; and determining a next hop address of the new data packet in a data forwarding table (FIB) according to the second destination identifier, and forwarding the new data packet according to the next hop address of the new data packet.
8. The apparatus of claim 6, further comprising:
and a second processing module, configured to determine, according to the first destination identifier, a next hop address of the data request packet in a FIB of a data forwarding table if the data request packet is not allowed to be cached, and forward the data request packet according to the next hop address of the data request packet.
9. The apparatus of claim 6, further comprising:
a second judging module, configured to judge whether the data request packet appears in a loop detection record stored locally based on the first source identifier, the first destination identifier, and the request data identifier;
a third processing module, configured to discard the data request packet if the data request packet is already present in the loop detection record; if the data request packet does not appear in the loop detection record, recording the data request packet in the loop detection record based on the first source identifier, the first destination identifier and the request data identifier, determining a next hop address of the data request packet in a data forwarding table (FIB) according to the first destination identifier, and forwarding the data request packet according to the next hop address of the data request packet.
10. The apparatus of claim 6, further comprising:
an obtaining module, configured to obtain path forwarding information included in the data request packet, where the path forwarding information records each network device through which the data request packet passes;
a third judging module, configured to judge whether a device identifier of the third judging module is present in the path forwarding information;
a fourth processing module, configured to discard the data request packet if the data request packet is present in the path forwarding information; if the data request packet does not appear in the path forwarding information, adding the device identifier in the path forwarding information, determining a next hop address of the data request packet in a data forwarding table (FIB), and forwarding the data request packet according to the next hop address of the data request packet.
11. A network device, comprising: a transmitter, a receiver, a memory and a processor, wherein the memory, the transmitter and the receiver are respectively connected with the processor, the memory stores program codes, and the processor is used for calling the program codes and executing the following operations:
receiving, by the receiver, a data request packet sent by a data request device, where the data request packet at least includes data content stored in the data request device, a first source identifier, a first destination identifier, and a request data identifier, the first source identifier is used to indicate the data request device, and the first destination identifier is used to indicate a storage device of requested data;
searching the requested data in the content cache manager CCM according to the first target identifier and the request data identifier; if the requested data is not found in the CCM, judging whether the data request packet allows caching; if the data request packet allows caching, caching the data content encapsulated in the data request packet in the CCM with the first source identification and an identification of the data content encapsulated in the data request packet.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610146813.0A CN107196985B (en) | 2016-03-15 | 2016-03-15 | Data management method and device and network equipment |
| PCT/CN2017/073671 WO2017157126A1 (en) | 2016-03-15 | 2017-02-15 | Data management method and apparatus, and network device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610146813.0A CN107196985B (en) | 2016-03-15 | 2016-03-15 | Data management method and device and network equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107196985A CN107196985A (en) | 2017-09-22 |
| CN107196985B true CN107196985B (en) | 2020-08-07 |
Family
ID=59850731
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610146813.0A Active CN107196985B (en) | 2016-03-15 | 2016-03-15 | Data management method and device and network equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107196985B (en) |
| WO (1) | WO2017157126A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113038535B (en) * | 2019-12-09 | 2022-06-17 | 广东外语外贸大学 | Multi-source transmission load balancing method based on bandwidth in wireless multi-hop network |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103200640A (en) * | 2013-03-05 | 2013-07-10 | 北京交通大学 | Packet structure and interest packet transfer and source switching and source agency selection method |
| CN104753797A (en) * | 2015-04-09 | 2015-07-01 | 清华大学深圳研究生院 | Content center network dynamic routing method based on selective caching |
| CN104836737A (en) * | 2015-03-27 | 2015-08-12 | 北京邮电大学 | Internet of things communication method taking named data as center |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8103768B2 (en) * | 2009-04-14 | 2012-01-24 | At&T Intellectual Property I, Lp | Network aware forward caching |
| KR20130085558A (en) * | 2011-12-21 | 2013-07-30 | 삼성전자주식회사 | A processing method of an interest message and a data message according to priority in a content centric network |
| CN103491003B (en) * | 2012-06-14 | 2016-12-21 | 华为技术有限公司 | A kind of content router and the method processing message thereof |
| CN105049254B (en) * | 2015-07-30 | 2018-08-21 | 重庆邮电大学 | Data buffer storage replacement method based on content rating and popularity in a kind of NDN/CCN |
-
2016
- 2016-03-15 CN CN201610146813.0A patent/CN107196985B/en active Active
-
2017
- 2017-02-15 WO PCT/CN2017/073671 patent/WO2017157126A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103200640A (en) * | 2013-03-05 | 2013-07-10 | 北京交通大学 | Packet structure and interest packet transfer and source switching and source agency selection method |
| CN104836737A (en) * | 2015-03-27 | 2015-08-12 | 北京邮电大学 | Internet of things communication method taking named data as center |
| CN104753797A (en) * | 2015-04-09 | 2015-07-01 | 清华大学深圳研究生院 | Content center network dynamic routing method based on selective caching |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017157126A1 (en) | 2017-09-21 |
| CN107196985A (en) | 2017-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102033999B1 (en) | Method and apparatus for communication in content centric network | |
| CN101656765B (en) | Address mapping system and data transmission method of identifier/locator separation network | |
| US8694675B2 (en) | Generalized dual-mode data forwarding plane for information-centric network | |
| US10757213B2 (en) | Method and apparatus for pushing data in a content-centric networking (CCN) network | |
| US10666759B2 (en) | Communication method of node overhearing content in content centric network and node | |
| KR20150104187A (en) | Contextualized information bus | |
| WO2012151430A1 (en) | Content identification, retrieval and routing in the internet | |
| JP4755683B2 (en) | Method, apparatus, and program for efficiently extending a peer-to-peer (P2P) network | |
| US20040063449A1 (en) | Multimedia messaging method and system for transferring multimedia content | |
| CN104717186B (en) | A kind of method, apparatus and data transmission system for transmitting data in network system | |
| CN108293023B (en) | System and method for supporting context-aware content requests in information-centric networks | |
| US20180287940A1 (en) | Data universal forwarding plane for information exchange | |
| US9268813B2 (en) | Terminal device based on content name, and method for routing based on content name | |
| CN103546375A (en) | Content routing method and device | |
| CN107196985B (en) | Data management method and device and network equipment | |
| US11063863B2 (en) | Systems and methods for transmitting and receiving interest messages | |
| US9338230B2 (en) | Method, network entity and network system for forwarding resources | |
| US20150019755A1 (en) | Data-centric communications system, node, and data forwarding method | |
| CN106657181B (en) | Data pushing method based on content-centric network | |
| CN116566897A (en) | Addressing routing method, device, equipment and medium | |
| CN112688880B (en) | Method for reducing redundant data packet transmission in named data network | |
| CN106470156B (en) | Method and device for forwarding message | |
| Serhane et al. | A label-based producer mobility support in 5G-enabled ICN networks | |
| JP5784234B2 (en) | Generalized dual-mode data transfer plane for information-centric networks | |
| CN114363240B (en) | Network forwarding device and data forwarding method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |