Request response method, ICN network element, apparatus, device, medium and program product

Abstract

The present application relates to a request response method, an ICN network element, an apparatus, a device, a medium and a program product. The method is applied to an ICN central node within an information-centric networking (ICN) network element deployed in a metropolitan area network, the ICN network element comprising the ICN central node and a plurality of ICN edge nodes, and each ICN edge node being communicatively connected to the ICN central node. The method comprises: an ICN central node receives a target ICN service request sent by a first ICN edge node for requesting target data content; on the basis of the target ICN service request, determining whether a second ICN edge node that stores the target data content is present within an ICN network element; and if the second ICN edge node is present, forwarding to the first ICN edge node the target data content stored within the second ICN edge node. The present method can be used for improving the edge node hit ratio, thus preventing the generation of back-to-origin traffic.

Description

Request response method, ICN network element, device, equipment, medium and program product

[0001] Related applications

[0002] This application claims priority to Chinese patent application number 202410009861.X, filed on January 2, 2024, entitled “Request and Response Method, ICN Network Element, Device, Equipment, Medium and Program Product,” the entire text of which is hereby incorporated by reference. Technical Field

[0003] The present application relates to the field of network technology, and in particular to a request response method, ICN network element, device, equipment, medium and program product. Background Art

[0004] With the introduction of the spine-leaf architecture in new metropolitan area networks (MANs) that integrate cloud and network, the east-west traffic bandwidth of MANs has increased significantly, while costs have been significantly reduced. Therefore, edge cloud nodes can be deployed at the edge of the network on a leaf-scale basis to provide users with local services.

[0005] However, the current architecture with edge cloud node deployment is a CDN node networking solution based on the traditional north-south cascade method of the Content Delivery Network (CDN). The hit rate of edge CDN nodes in this architecture is low, which may cause a large amount of back-to-source traffic.

[0006] Summary of the Invention

[0007] In view of this, it is necessary to provide a request response method, ICN network element, device, equipment, medium and program product that can improve the hit rate of edge nodes in response to the above technical problems.

[0008] In a first aspect, the present application provides a request response method, which is applied to an ICN central node deployed in an information center network (ICN) network element in a metropolitan area network, the ICN network element including an ICN central node and multiple ICN edge nodes, each ICN edge node being communicatively connected to the ICN central node, the method comprising:

[0009] Receive a target ICN service request sent by the first ICN edge node, where the target ICN service request is used to request target data content; determine whether a second ICN edge node exists in the ICN network element based on the target ICN service request, where the second ICN edge node stores the target data content; if the second ICN edge node exists, forward the target data content stored in the second ICN edge node to the first ICN edge node.

[0010] In one embodiment, the method further comprises:

[0011] If the second ICN edge node does not exist, a request is sent to the upper-level content delivery network CDN node of the ICN central node.

[0012] In one embodiment, sending a request to a CDN node above the ICN central node includes:

[0013] Send a back-to-origin request to the upper-level CDN node of the ICN central node. The back-to-origin request is used to instruct the upper-level CDN node to return the target data content;

[0014] The target data content returned by the upper-level CDN node is forwarded to the first ICN edge node.

[0015] In one embodiment, sending a back-to-origin request to a CDN node above the ICN central node includes:

[0016] Convert the target ICN service request into a back-to-origin request, which is an IP-based media service request.

[0017] In one embodiment, determining whether a second ICN edge node exists in an ICN network element according to a target ICN service request includes:

[0018] The forwarding table FIB is queried according to the target ICN service request to determine whether a second ICN edge node exists in the ICN network element.

[0019] In one embodiment, the FIB stores the ICN service request and the connection interface information of the ICN edge node in the ICN network element that can respond to the ICN service request, and querying the forwarding table FIB according to the target ICN service request to determine whether the second ICN edge node exists in the ICN network element includes:

[0020] The FIB is queried according to the target ICN service request, and it is determined whether a second ICN edge node exists in the ICN network element according to the query result.

[0021] In one embodiment, the method further comprises:

[0022] The pending request table PIT is updated according to the target ICN service request. The PIT stores the ICN service request and the connection interface information of the ICN edge node from which the ICN service request originates.

[0023] In one embodiment, forwarding target data content stored in the second ICN edge node to the first ICN edge node includes:

[0024] Query the FIB according to the target ICN service request; forward the target ICN service request to the second ICN edge node based on the connection interface information queried from the FIB; receive the target data content returned by the second ICN edge node in response to the target ICN service request, and forward the target data content to the first ICN edge node according to the PIT.

[0025] In a second aspect, the present application also provides a request response method, which is applied to a first ICN edge node deployed in an ICN network element in a metropolitan area network, the ICN network element including an ICN central node and multiple ICN edge nodes, each ICN edge node is communicated with the ICN central node, the method comprising:

[0026] Receive the CDN service request sent by the gateway, where the CDN service request is used to request the target data content; determine whether the first ICN edge node has the target data content stored locally; if the target data content is stored, respond to the CDN service request based on the locally stored target data content; if the target data content is not stored, convert the CDN service request into a target ICN service request, and forward the target ICN service request to the ICN central node.

[0027] In one embodiment, the method further comprises:

[0028] Receive the target data content returned by the ICN central node based on the target ICN service request.

[0029] In a third aspect, the present application also provides a request response device, which is applied to an ICN central node deployed in an information center network ICN network element of a metropolitan area network, the ICN network element including an ICN central node and multiple ICN edge nodes, each ICN edge node being communicatively connected to the ICN central node, the device comprising:

[0030] An ICN service request receiving module, configured to receive a target ICN service request sent by the first ICN edge node, where the target ICN service request is used to request target data content;

[0031] An ICN edge node determination module is configured to determine whether a second ICN edge node exists in the ICN network element according to the target ICN service request, and the second ICN edge node stores target data content;

[0032] The content forwarding module is configured to forward the target data content stored in the second ICN edge node to the first ICN edge node if the second ICN edge node exists.

[0033] In one embodiment, the device also includes a send-back-to-source request module, which is used to send a return-to-source request to the upper-level content distribution network CDN node of the ICN central node if there is no second ICN edge node. The return-to-source request is used to instruct the upper-level CDN node to return the target data content; and forward the target data content returned by the upper-level CDN node to the first ICN edge node.

[0034] In one embodiment, the sending back-to-source request module is used to convert the target ICN service request into a back-to-source request, where the back-to-source request is an IP-based media service request.

[0035] In one of the embodiments, the ICN edge node determination module is used to query the forward forwarding table FIB according to the target ICN service request, where the FIB stores the ICN service request and the connection interface information of the ICN edge node in the ICN network element that can respond to the ICN service request; and determine whether there is a second ICN edge node in the ICN network element based on the query result.

[0036] In one embodiment, the apparatus further includes an updating module configured to update a pending request table PIT according to a target ICN service request, wherein the PIT stores the ICN service request and connection interface information of an ICN edge node from which the ICN service request originates.

[0037] In one of the embodiments, the content forwarding module is used to query the FIB according to the target ICN service request; forward the target ICN service request to the second ICN edge node according to the connection interface information queried from the FIB; receive the target data content returned by the second ICN edge node in response to the target ICN service request, and forward the target data content to the first ICN edge node according to the PIT.

[0038] In a fourth aspect, the present application further provides a request response device, which is applied to a first ICN edge node deployed in an ICN network element of a metropolitan area network, the ICN network element including an ICN central node and multiple ICN edge nodes, each ICN edge node being communicatively connected to the ICN central node, the device comprising:

[0039] A CDN service request receiving module is used to receive a CDN service request sent by a gateway, where the CDN service request is used to request target data content;

[0040] a content determination module, configured to determine whether the first ICN edge node locally stores target data content;

[0041] A response module, configured to respond to the CDN service request based on the locally stored target data content if the target data content is stored;

[0042] The request forwarding module is used to convert the CDN service request into a target ICN service request if the target data content is not stored, and forward the target ICN service request to the ICN central node.

[0043] In one embodiment, the apparatus further includes a target data content receiving module, wherein the target data content receiving module is configured to receive the target data content returned by the ICN central node based on the target ICN service request.

[0044] In the fifth aspect, the present application also provides an ICN network element, which includes an ICN central node and multiple ICN edge nodes; the ICN central node is used to execute the request response method described in the above-mentioned first aspect embodiments; the ICN edge node is used to execute the request response method described in the above-mentioned second aspect embodiments.

[0045] In a sixth aspect, the present application also provides a content distribution network, which includes multiple ICN network elements; each ICN network element includes an ICN central node and multiple ICN edge nodes; the ICN central node in each ICN network element is communicatively connected to the upper-level CDN node.

[0046] In the seventh aspect, the present application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, it implements the request response method described in any one of the first aspect and / or second aspect above.

[0047] In an eighth aspect, the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the request response method described in any one of the first and / or second aspects above is implemented.

[0048] In a ninth aspect, the present application also provides a computer program product, comprising a computer program, which, when executed by a processor, implements the request response method described in any one of the first and / or second aspects above.

[0049] The above-mentioned request response method, ICN network element, device, equipment, medium and program product are applied to an ICN central node deployed in an information center network (ICN) network element of a metropolitan area network. The ICN network element includes an ICN central node and multiple ICN edge nodes, and each ICN edge node is in communication with the ICN central node. First, the ICN central node receives a target ICN service request sent by a first ICN edge node for requesting target data content. Then, based on the target ICN service request, it determines whether there is a second ICN edge node in the ICN network element that stores the target data content. If there is a second ICN edge node, the target data content stored in the second ICN edge node is forwarded to the first ICN edge node. In this way, when the target ICN service request is received, the multiple ICN edge nodes in the ICN network element are first searched to see whether there is a second ICN edge node that stores the target data content. If so, the target ICN service request can be responded to without sending a back-to-source request to the upper-level network, thereby improving the hit rate of the edge node and avoiding the generation of back-to-source traffic. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technology descriptions. Obviously, the drawings described below are only some embodiments of this application. For those of ordinary skill in the art, other drawings can be derived from these drawings without inventive effort.

[0051] FIG1 is a diagram showing an application environment of a request response method in an embodiment of the present application.

[0052] Figure 2 is a schematic diagram of traffic between nodes in the existing edge CDN network architecture.

[0053] FIG3 is a flow chart of a request response method in an embodiment of the present application.

[0054] FIG4 is a schematic diagram of traffic between nodes of the networking architecture of the present application in one embodiment of the present application.

[0055] FIG5 is a flow chart of a request response method in another embodiment of the present application.

[0056] FIG6 is a flow chart of a request response method in another embodiment of the present application.

[0057] FIG7 is a flow chart of a request response method in another embodiment of the present application.

[0058] FIG8 is a flow chart of a request response method in another embodiment of the present application.

[0059] FIG9 is a flow chart of a request response method in another embodiment of the present application.

[0060] FIG10 is a functional module diagram of an ICN edge node in an embodiment of the present application.

[0061] FIG11 is a functional module diagram of an ICN central node in an embodiment of the present application.

[0062] FIG12 is a structural block diagram of a request response device in an embodiment of the present application.

[0063] FIG13 is a structural block diagram of a request response device in another embodiment of the present application.

[0064] FIG14 is a diagram showing the internal structure of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0065] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0066] An embodiment of the present application provides a request response method, which can be applied in the application environment shown in Figure 1. Among them, the metropolitan area network includes an information center network (ICN) network element. The ICN network element may include an ICN central node 10 and multiple ICN edge nodes 20, wherein each ICN edge node 20 is communicatively connected to the ICN central node 10, and the ICN central node 10 is communicatively connected to the upper-level CDN node 30 in the backbone network. Users can access the ICN edge node nearby through the optical line terminal (OLT) and the cloud gateway. Among them, the ICN central node 10 can be but is not limited to various routers or switch devices. The upper-level CDN node 30 can be a server, specifically an independent server or a server cluster composed of multiple servers.

[0067] The current architecture for deploying edge cloud nodes relies on a traditional CDN node networking scheme based on a north-south cascade. This architecture results in a low hit rate for edge CDN nodes, potentially generating a large amount of back-to-origin traffic. As shown in Figure 2, the existing edge CDN networking architecture consists of a core layer, a convergence layer, and an edge layer. The core layer consists of core routers, while both the edge and convergence layers utilize a spine-leaf architecture. Users access edge nodes through optical line terminals (OLTs) or switches (SWs). Edge CDN nodes at the same level in the edge layer lack a mutual assistance mechanism and instead maintain independent cascade relationships with the convergence CDN nodes in the upper convergence layer. This connection method results in a high north-south traffic flow between edge CDN nodes, but no east-west traffic. This means that edge CDN nodes are independent of each other and independently cache hot content, resulting in a low hit rate for edge CDN nodes. When a hit fails at an edge CDN node, back-to-origin traffic is initiated to the upper convergence CDN node, potentially placing excessive traffic pressure on the upper convergence CDN node.

[0068] Based on the above-mentioned traditional technology, an embodiment of the present application provides a request response method, which is applied to an ICN central node in an information center network (ICN) network element deployed in a metropolitan area network. The ICN network element includes an ICN central node and multiple ICN edge nodes, and each ICN edge node is in communication with the ICN central node. First, the ICN central node receives a target ICN service request sent by a first ICN edge node for requesting target data content. Then, based on the target ICN service request, it determines whether there is a second ICN edge node storing the target data content in the ICN network element. If the second ICN edge node exists, the target data content stored in the second ICN edge node is forwarded to the first ICN edge node. In this way, when the target ICN service request is received, the multiple ICN edge nodes in the ICN network element are first searched to see whether there is a second ICN edge node storing the target data content. If so, the target ICN service request can be responded to without sending a back-source request to the upper-level network, thereby improving the hit rate of the edge node and avoiding the generation of back-source traffic.

[0069] It should be noted that the beneficial effects or technical problems solved by the embodiments of the present application are not limited to this one, but may also include other implicit or related problems. For details, please refer to the description of the following embodiments.

[0070] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0071] In an exemplary embodiment, as shown in FIG3 , a request response method is provided, which is described by taking the application of the method to the ICN central node in FIG1 as an example, and includes the following steps S301 to S303 .

[0072] Step S301: Receive a target ICN service request sent by a first ICN edge node.

[0073] The first ICN edge node is any one of the multiple ICN edge nodes, and the target ICN service request is used to request target data content. Optionally, the target ICN service request can be a media service request, and the user obtains media service by sending the media service request. The first ICN edge node is used to receive user requests and convert the received user requests into target ICN service requests. The ICN central node is used to receive the target ICN service request sent by the first ICN edge node and determine whether the corresponding target data content exists in the ICN network element based on the target ICN service request.

[0074] Step S302: Determine whether a second ICN edge node exists in the ICN network element according to the target ICN service request.

[0075] The second ICN edge node stores the target data content. Optionally, the ICN central node stores a correspondence table between each edge node and the ICN service requests to which each edge node can respond. By querying this correspondence table, it can be determined whether the edge node can respond to the target ICN service request, that is, whether it stores the target data content. If so, the edge node that can respond to the target ICN service request is determined to be the second ICN edge node.

[0076] Step S303: If the second ICN edge node exists, the target data content stored in the second ICN edge node is forwarded to the first ICN edge node.

[0077] Specifically, if there is a second ICN edge node, that is, the target data content corresponding to the target ICN service request exists in the ICN network element, the second ICN edge node reads the target data content and then forwards it to the ICN central node. The ICN central node forwards the target data content to the first ICN edge node that sends the target ICN server request.

[0078] Optionally, as shown in Figure 4, the ICN network element is applied to the network architecture shown in Figure 2 to realize the CDN and ICN hybrid networking of the edge cloud network. Among them, the convergence layer and the core layer remain unchanged, and the ICN network element shown in Figure 1 is established at the edge layer, including an ICN central node and multiple ICN edge nodes. When the ICN edge node receives a user request, it first searches in the ICN network element to which it belongs to determine whether there is a second ICN edge node in the ICN network element. At this time, the north-south traffic is converted into east-west traffic within the ICN network element. At the same time, the upper-level convergence CDN node regards each ICN network element as a lower-level CDN node, which will not change the service process of the existing CDN.

[0079] In the above embodiment, an ICN central node is applied to an information center network (ICN) network element deployed in a metropolitan area network. The ICN network element includes an ICN central node and multiple ICN edge nodes, and each ICN edge node is in communication with the ICN central node. First, the ICN central node receives a target ICN service request sent by a first ICN edge node for requesting target data content. Then, based on the target ICN service request, it determines whether a second ICN edge node storing the target data content exists in the ICN network element. If a second ICN edge node exists, the target data content stored in the second ICN edge node is forwarded to the first ICN edge node. In this way, when a target ICN service request is received, a search is first performed among multiple ICN edge nodes in the ICN network element to determine whether a second ICN edge node storing the target data content exists. If so, the target ICN service request can be responded to without sending a back-to-source request to the upper-level network. This improves the hit rate of the edge node and avoids generating back-to-source traffic.

[0080] In one embodiment, after step S302, if the second ICN edge node does not exist, a request is sent to a CDN node above the ICN central node. Specifically, as shown in FIG5 , the step of sending a request to a CDN node above the ICN central node further includes:

[0081] Step S501: a back-to-source request is sent to the upper-level content delivery network CDN node of the ICN central node.

[0082] The back-to-origin request instructs the upper-level CDN node to return the target data content. If the second ICN edge node does not exist—that is, if the target data content corresponding to the target ICN request does not exist within the ICN network element—the ICN central node forwards the target ICN service request to the upper-level CDN node connected to the ICN central node. Optionally, before forwarding, the target ICN service request is converted into a back-to-origin request, which is an IP-based media service request.

[0083] For the upper-level CDN node, the ICN network element is regarded as a CDN node. When the ICN central node sends the target ICN service request, it is necessary to convert the target ICN service request first, converting the ICN-based service request into an IP-based media service request, that is, converting it into a standard back-to-origin request, and then sending it to the upper-level CDN node.

[0084] Step S502: Forward the target data content returned by the upper-level CDN node to the first ICN edge node.

[0085] The ICN central node receives the target data content returned by the upper-level CDN node and then forwards it to the first ICN edge node that sent the target ICN service request. Optionally, the ICN central node determines the connection interface information of the first ICN edge node by querying the routing data table.

[0086] Optionally, the pending request table PIT is updated according to the target ICN service request, where the PIT stores the ICN service request and the connection interface information of the ICN edge node from which the ICN service request originates.

[0087] The ICN network uses content-based routing, and each ICN node maintains three data tables: the Pending Interest Table (PIT), the Forwarding Information Base (FIB), and the Content Store (CS). Based on the target ICN service request, the ICN central node updates the local PIT. This determines the connection interface information of the ICN edge node (i.e., the first edge node) that sent the target ICN service request, allowing the ICN central node to forward the target data content to the first edge node.

[0088] In one embodiment, the step of determining whether a second ICN edge node exists in the ICN network element based on the target ICN service request in step S302 includes querying a forwarding table (FIB) based on the target ICN service request to determine whether the second ICN edge node exists in the ICN network element. Specifically, as shown in FIG6 , step S302 may further include the following steps S601 to S602.

[0089] Step S601: query the forwarding table FIB according to the target ICN service request.

[0090] The FIB stores the ICN service request and the connection interface information of the ICN edge nodes in the ICN network element that can respond to the ICN service request. The ICN central node queries the local FIB table according to the target ICN service request and obtains the query result.

[0091] Step S602: Determine whether a second ICN edge node exists in the ICN network element according to the query result.

[0092] The ICN central node queries the FIB table. If the target ICN service request exists in the FIB table, the ICN edge node corresponding to the target ICN service request in the FIB table is designated as the second ICN edge node. The target ICN service request is forwarded to the second edge node based on the connection interface information of the second edge node in the FIB table. If the query result indicates that the target ICN service request does not exist in the FIB table, the ICN central node determines that the second ICN edge node with the target data content does not exist in the ICN network element.

[0093] In one embodiment, as shown in FIG7 , after determining that the second edge node exists in the ICN network element, the step of forwarding the target data content stored in the second ICN edge node to the first ICN edge node may further include steps S701 to S703 .

[0094] Step S701: query the FIB according to the target ICN service request.

[0095] Specifically, a match is performed in the FIB table according to the target ICN service request, and if the match is successful, the connection interface information of the second edge node is determined, and the interface information of the second edge node can be determined based on the connection interface information.

[0096] Step S702: forwarding the target ICN service request to the second ICN edge node according to the connection interface information retrieved from the FIB.

[0097] Specifically, according to the query result of the target ICN service request in the FIB, the ICN central node determines the interface information of the second edge node, and forwards the target ICN service request to the second edge node through the interface information.

[0098] Step S703: Receive the target data content returned by the second ICN edge node in response to the target ICN service request, and forward the target data content to the first ICN edge node according to the PIT.

[0099] Specifically, the second edge node receives the target ICN service request, determines the target data content corresponding to the target ICN service request, and then returns the target data content to the ICN central node. The ICN central node determines the first ICN edge node, the source of the target ICN service request, based on the previously updated PIT table. Then, based on the interface information, the target data content is forwarded to the first ICN edge node. At this point, the user can obtain the target data content corresponding to the target ICN service request.

[0100] Optionally, the first ICN edge node receives the target data content obtained through the back-to-source request, and can save the target data content locally and update the FIB table at the same time. In this way, when other ICN edge nodes in the ICN network element receive the target ICN service request, the target data content can be obtained in the ICN network element without sending back-to-source traffic.

[0101] In one embodiment, the present application also provides a request response method, which is applied to the first ICN edge node in the ICN network element in Figure 1 above. The first ICN edge node is any one of multiple ICN edge nodes. As shown in Figure 8, the method includes the following steps S801 to S804.

[0102] Step S801: Receive a CDN service request sent by a gateway.

[0103] The CDN service request is used to request target data content. The gateway can be a cloud gateway. Users access the nearest ICN edge node through the cloud gateway and send a media service request to the ICN edge node. The media service request is a CDN service request. The ICN edge node then provides media services based on the user's CDN service request. Optionally, the cloud gateway identifies the contracted CDN service request based on the message and forwards it to the ICN edge node.

[0104] Step S802: Determine whether the first ICN edge node has the target data content stored locally.

[0105] After the first ICN edge node receives the user's CDN service request, it first searches the local cache area of ​​the first ICN edge node according to the uniform resource locator URL requested by the CDN server to determine whether the target data content of the CDN service request is stored. If it is found, it is determined that the first ICN edge node stores the target data content.

[0106] Step S803: If the target data content is stored, respond to the CDN service request based on the locally stored target data content.

[0107] If the first ICN edge node stores the target data content, that is, a local hit, media services are provided to the user based on the target data content.

[0108] Step S804: If the target data content is not stored, the CDN service request is converted into a target ICN service request, and the target ICN service request is forwarded to the ICN central node.

[0109] Specifically, if the first ICN edge node does not store the target data content locally, it is necessary to search in the ICN network element to which the first ICN edge node belongs. At this time, the CDN service request needs to be converted into an ICN-based target ICN service request, and then the target ICN server request is forwarded to the ICN center node connected to the first ICN edge node.

[0110] After forwarding the target ICN service request to the ICN central node, the method further includes:

[0111] Receive target data content returned by the ICN central node based on the target ICN service request;

[0112] After the target ICN service request is forwarded, the first ICN edge node receives the target data content returned by the ICN central node, and then responds to the user's service request according to the target data content.

[0113] In an embodiment of the present application, please refer to FIG9 , which shows a flow chart of a request response method. The request response method includes the following steps S901 to S910 .

[0114] Step S901: The first ICN edge node receives a CDN service request sent by a gateway.

[0115] Step S902: The first ICN edge node determines whether the first ICN edge node has target data content stored locally.

[0116] Step S903: If the first ICN edge node stores the target data content, it responds to the CDN service request based on the locally stored target data content.

[0117] Step S904: If the first ICN edge node does not store the target data content, the CDN service request is converted into a target ICN service request, and the target ICN service request is forwarded to the ICN central node.

[0118] Step S905: The ICN central node receives the target ICN service request sent by the first ICN edge node.

[0119] Step S906: The ICN central node determines whether there is a second ICN edge node in the ICN network element according to the target ICN service request.

[0120] Step S907: If the second ICN edge node exists, the ICN central node forwards the target data content stored in the second ICN edge node to the first ICN edge node.

[0121] Step S908: If the second ICN edge node does not exist, the ICN central node sends a back-to-origin request to the upper-level content delivery network CDN node of the ICN central node.

[0122] Step S909: The ICN central node forwards the target data content returned by the upper-level CDN node to the first ICN edge node.

[0123] Step S910: The first ICN edge node receives target data content returned by the ICN central node based on the target ICN service request.

[0124] In the above embodiment, a hybrid ICN and CDN network is implemented, where ICN network elements convert north-south traffic at ICN edge nodes into east-west traffic. This improves the hit rate at the edge layer and reduces back-to-origin traffic, thereby alleviating pressure on upstream CDN servers. Furthermore, the reduced north-south traffic also reduces the complexity of upstream CDN management of downstream nodes.

[0125] In one embodiment, the functional modules of the ICN edge node may be as shown in FIG10 .

[0126] The media service module is responsible for receiving media service requests from the cloud gateway and converting IP-based media service requests into ICN-based media service requests, essentially converting CDN service requests into ICN-based service requests. It uses cache management and content storage to determine whether the target data content corresponding to the media service request is locally stored. If not, it forwards the media service request to the ICN central node via ICN routing. The ICN router is also responsible for updating the PIT and FIB tables based on the content distribution within the ICN network elements.

[0127] Optionally, the functional modules of the ICN central node may be as shown in FIG11 .

[0128] The difference between an ICN central node and an ICN edge node is that an ICN central node lacks caching or content storage capabilities and only forwards media service requests. An ICN router receives and responds to media service requests. If the target data content corresponding to the media service request does not exist in the ICN network element, the request is forwarded to the media service module. The media service module converts the media service request into an IP-based media service request and forwards it to the upper-level CDN node, which then retrieves the target data content.

[0129] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0130] Based on the same inventive concept, embodiments of the present application also provide a request response device for implementing the aforementioned request response method. The implementation solution provided by this device is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations in one or more request response device embodiments provided below can be found in the above-mentioned limitations on the request response method and will not be repeated here.

[0131] In an exemplary embodiment, as shown in FIG12 , a request response device is provided, which is applied to an ICN central node deployed in an information center network (ICN) element in a metropolitan area network. The ICN element includes the ICN central node and multiple ICN edge nodes, each of which is in communication with the ICN central node. The device includes an ICN service request receiving module, an ICN edge node determining module, and a content forwarding module, wherein:

[0132] An ICN service request receiving module, configured to receive a target ICN service request sent by the first ICN edge node, where the target ICN service request is used to request target data content;

[0133] An ICN edge node determination module is configured to determine whether a second ICN edge node exists in the ICN network element according to the target ICN service request, and the second ICN edge node stores target data content;

[0134] The content forwarding module is configured to forward the target data content stored in the second ICN edge node to the first ICN edge node if the second ICN edge node exists.

[0135] In one embodiment, the apparatus further includes a send-back-to-source request module, configured to send a request to a superior content delivery network (CDN) node of the ICN central node if the second ICN edge node does not exist.

[0136] In one embodiment, the send back-to-source request module is specifically used to send a back-to-source request to the upper-level content distribution network CDN node of the ICN central node. The back-to-source request is used to instruct the upper-level CDN node to return the target data content and forward the target data content returned by the upper-level CDN node to the first ICN edge node.

[0137] In one embodiment, the sending back-to-source request module is specifically configured to convert the target ICN service request into a back-to-source request, where the back-to-source request is an IP-based media service request.

[0138] In one embodiment, the ICN edge node determination module is specifically configured to query a forwarding table (FIB) according to a target ICN service request to determine whether a second ICN edge node exists in the ICN network element.

[0139] In one embodiment, the FIB stores the ICN service request and connection interface information of an ICN edge node in the ICN network element that can respond to the ICN service request. The ICN edge node determination module is specifically configured to query the FIB based on the target ICN service request and determine whether a second ICN edge node exists in the ICN network element based on the query result.

[0140] In one embodiment, the apparatus further includes an updating module configured to update a pending request table PIT according to the target ICN service request, wherein the PIT stores the ICN service request and connection interface information of the ICN edge node from which the ICN service request originates.

[0141] In one embodiment, the content forwarding module is specifically used to query the FIB according to the target ICN service request; forward the target ICN service request to the second ICN edge node based on the connection interface information queried from the FIB; receive the target data content returned by the second ICN edge node in response to the target ICN service request, and forward the target data content to the first ICN edge node according to the PIT.

[0142] Each module in the request response device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a memory in a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0143] In one embodiment, as shown in FIG13 , the present application further provides a request response device, which is applied to a first ICN edge node deployed in an ICN network element of a metropolitan area network. The ICN network element includes an ICN central node and multiple ICN edge nodes. Each ICN edge node is communicatively connected to the ICN central node. The device includes a CDN service request receiving module, a content determination module, a response module, and a request forwarding module, wherein:

[0144] The CDN service request receiving module is used to receive the CDN service request sent by the gateway, and the CDN service request is used to request the target data content;

[0145] The content determination module is used to determine whether the first ICN edge node locally stores the target data content;

[0146] The response module is used to respond to the CDN service request based on the locally stored target data content if the target data content is stored;

[0147] The request forwarding module is used to convert the CDN service request into a target ICN service request if the target data content is not stored, and forward the target ICN service request to the ICN central node.

[0148] In one embodiment, the device further includes a target data content receiving module, wherein the target data content receiving module is configured to receive the target data content returned by the ICN central node based on the target ICN service request.

[0149] Each module in the request response device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a memory in a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0150] Based on the same inventive concept, the present application also provides an ICN network element for implementing the above request-response method. The implementation solution provided by the ICN network element is similar to the implementation solution described in the above method embodiment. As shown in Figure 1, the ICN network element includes an ICN central node 10 and multiple ICN edge nodes 20.

[0151] Specifically, the ICN central node receives a target ICN service request sent by a first ICN edge node, where the first ICN edge node is any one of multiple ICN edge nodes, and the target ICN service request is used to request target data content; based on the target ICN service request, it is determined whether there is a second ICN edge node in the ICN network element, and the second ICN edge node stores the target data content; if there is a second ICN edge node, the target data content stored in the second ICN edge node is forwarded to the first ICN edge node.

[0152] Optionally, if the second ICN edge node does not exist, the ICN central node sends a request to an upper-level content delivery network CDN node of the ICN central node.

[0153] Optionally, a back-to-origin request is sent to the upper-level content delivery network CDN node of the ICN central node, where the back-to-origin request is used to instruct the upper-level CDN node to return the target data content; and the target data content returned by the upper-level CDN node is forwarded to the first ICN edge node.

[0154] Optionally, the ICN central node converts the target ICN service request into a back-to-origin request, where the back-to-origin request is an IP-based media service request.

[0155] Optionally, the ICN central node queries the forwarding table FIB according to the target ICN service request to determine whether the second ICN edge node exists in the ICN network element.

[0156] Optionally, the FIB stores the ICN service request and connection interface information of an ICN edge node in the ICN network element that can respond to the ICN service request. The FIB is queried according to the target ICN service request, and whether there is a second ICN edge node in the ICN network element is determined according to the query result.

[0157] Optionally, the ICN central node updates a pending request table PIT according to the target ICN service request, where the PIT stores the ICN service request and connection interface information of the ICN edge node from which the ICN service request originates.

[0158] Optionally, the ICN central node queries the FIB according to the target ICN service request; forwards the target ICN service request to the second ICN edge node based on the connection interface information queried from the FIB; receives the target data content returned by the second ICN edge node in response to the target ICN service request, and forwards the target data content to the first ICN edge node according to the PIT.

[0159] The ICN edge node receives a CDN service request sent by the gateway, where the CDN service request is used to request target data content; determines whether the target data content is stored locally on the first ICN edge node; if the target data content is stored, responds to the CDN service request based on the locally stored target data content; if the target data content is not stored, converts the CDN service request into a target ICN service request and forwards the target ICN service request to the ICN central node.

[0160] Optionally, the ICN edge node receives target data content returned by the ICN central node based on the target ICN service request.

[0161] In one embodiment, a content delivery network (CDN) is provided, as shown in FIG4 . The CDN includes multiple ICN network elements; each ICN network element includes an ICN central node and multiple ICN edge nodes; the ICN central node in each ICN network element is in communication with a higher-level CDN node. The ICN central node and ICN edge nodes provide the same solution to the problem as described in the above method.

[0162] In an exemplary embodiment, a computer device is provided, which may be a routing device, and its internal structure diagram may be shown in Figure 14. The computer device includes a processor, a memory, an input / output interface (I / O), and a communication interface. The processor, memory, and I / O interface are connected via a system bus, and the communication interface is connected to the system bus via the I / O interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store request and response content data. The I / O interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, it implements a request and response method.

[0163] Those skilled in the art will understand that the structure shown in FIG14 is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0164] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented: receiving a target ICN service request sent by a first ICN edge node, the target ICN service request being used to request target data content; determining whether a second ICN edge node exists in an ICN network element based on the target ICN service request, the second ICN edge node storing the target data content; and if the second ICN edge node exists, forwarding the target data content stored in the second ICN edge node to the first ICN edge node.

[0165] In one embodiment, when the processor executes the computer program, the processor further implements the following steps: if the second ICN edge node does not exist, sending a request to a content delivery network (CDN) node that is a higher level than the ICN central node.

[0166] In one embodiment, when the processor executes the computer program, it also implements the following steps: sending a back-to-source request to the upper-level content delivery network CDN node of the ICN central node, the back-to-source request is used to instruct the upper-level CDN node to return the target data content; forwarding the target data content returned by the upper-level CDN node to the first ICN edge node.

[0167] In one embodiment, when the processor executes the computer program, the processor further implements the following steps: converting the target ICN service request into a back-to-origin request, where the back-to-origin request is an IP-based media service request.

[0168] In one embodiment, when the processor executes the computer program, the processor further implements the following steps: querying the forwarding table FIB according to the target ICN service request to determine whether there is a second ICN edge node in the ICN network element.

[0169] In one embodiment, the FIB stores the ICN service request and the connection interface information of the ICN edge node in the ICN network element that can respond to the ICN service request. When the processor executes the computer program, the following steps are further implemented: querying the FIB according to the target ICN service request, and determining whether there is a second ICN edge node in the ICN network element based on the query result.

[0170] In one embodiment, when the processor executes the computer program, the processor further implements the following steps: updating a pending request table PIT according to the target ICN service request, wherein the PIT stores the ICN service request and the connection interface information of the ICN edge node from which the ICN service request originates.

[0171] In one embodiment, when the processor executes the computer program, it further implements the following steps: querying the FIB according to the target ICN service request; forwarding the target ICN service request to the second ICN edge node according to the connection interface information queried from the FIB; receiving the target data content returned by the second ICN edge node in response to the target ICN service request, and forwarding the target data content to the first ICN edge node according to the PIT.

[0172] In one embodiment, when the processor executes the computer program, it further implements the following steps: receiving a CDN service request sent by the gateway, the CDN service request being used to request target data content; determining whether the first ICN edge node has the target data content stored locally; if the target data content is stored, responding to the CDN service request based on the locally stored target data content; if the target data content is not stored, converting the CDN service request into a target ICN service request, and forwarding the target ICN service request to the ICN central node.

[0173] In one embodiment, when the processor executes the computer program, the processor further implements the following steps: receiving target data content returned by the ICN central node based on the target ICN service request.

[0174] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: receiving a target ICN service request sent by a first ICN edge node, the target ICN service request being used to request target data content; determining whether a second ICN edge node exists in the ICN network element based on the target ICN service request, the second ICN edge node storing the target data content; and if the second ICN edge node exists, forwarding the target data content stored in the second ICN edge node to the first ICN edge node.

[0175] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: if the second ICN edge node does not exist, sending a request to a content delivery network (CDN) node that is a higher level than the ICN central node.

[0176] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: sending a back-to-source request to the upper-level content delivery network CDN node of the ICN central node, the back-to-source request is used to instruct the upper-level CDN node to return the target data content; forwarding the target data content returned by the upper-level CDN node to the first ICN edge node.

[0177] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: converting the target ICN service request into a back-to-origin request, where the back-to-origin request is an IP-based media service request.

[0178] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: querying the forwarding table FIB according to the target ICN service request to determine whether there is a second ICN edge node in the ICN network element.

[0179] In one embodiment, the FIB stores the ICN service request and the connection interface information of the ICN edge node in the ICN network element that can respond to the ICN service request. When the computer program is executed by the processor, the following steps are also implemented: querying the FIB according to the target ICN service request, and determining whether there is a second ICN edge node in the ICN network element based on the query result.

[0180] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: updating a pending request table PIT according to the target ICN service request, wherein the PIT stores the ICN service request and the connection interface information of the ICN edge node from which the ICN service request originates.

[0181] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: querying the FIB according to the target ICN service request; forwarding the target ICN service request to the second ICN edge node according to the connection interface information queried from the FIB; receiving the target data content returned by the second ICN edge node in response to the target ICN service request, and forwarding the target data content to the first ICN edge node according to the PIT.

[0182] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving a CDN service request sent by the gateway, the CDN service request being used to request target data content; determining whether the first ICN edge node has the target data content stored locally; if the target data content is stored, responding to the CDN service request based on the locally stored target data content; if the target data content is not stored, converting the CDN service request into a target ICN service request, and forwarding the target ICN service request to the ICN central node.

[0183] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving target data content returned by the ICN central node based on the target ICN service request.

[0184] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the following steps: receiving a target ICN service request sent by a first ICN edge node, the target ICN service request being used to request target data content; determining, based on the target ICN service request, whether a second ICN edge node exists in an ICN network element, the second ICN edge node storing the target data content; and if the second ICN edge node exists, forwarding the target data content stored in the second ICN edge node to the first ICN edge node.

[0185] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: if the second ICN edge node does not exist, sending a request to a content delivery network (CDN) node that is a higher level than the ICN central node.

[0186] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: sending a back-to-source request to the upper-level content delivery network CDN node of the ICN central node, the back-to-source request is used to instruct the upper-level CDN node to return the target data content; forwarding the target data content returned by the upper-level CDN node to the first ICN edge node.

[0187] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: converting the target ICN service request into a back-to-origin request, where the back-to-origin request is an IP-based media service request.

[0188] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: querying the forwarding table FIB according to the target ICN service request to determine whether there is a second ICN edge node in the ICN network element.

[0189] In one embodiment, the FIB stores the ICN service request and the connection interface information of the ICN edge node in the ICN network element that can respond to the ICN service request. When the computer program is executed by the processor, the following steps are also implemented: querying the FIB according to the target ICN service request, and determining whether there is a second ICN edge node in the ICN network element based on the query result.

[0190] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: updating a pending request table PIT according to the target ICN service request, wherein the PIT stores the ICN service request and the connection interface information of the ICN edge node from which the ICN service request originates.

[0191] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: querying the FIB according to the target ICN service request; forwarding the target ICN service request to the second ICN edge node according to the connection interface information queried from the FIB; receiving the target data content returned by the second ICN edge node in response to the target ICN service request, and forwarding the target data content to the first ICN edge node according to the PIT.

[0192] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving a CDN service request sent by the gateway, the CDN service request being used to request target data content; determining whether the first ICN edge node has the target data content stored locally; if the target data content is stored, responding to the CDN service request based on the locally stored target data content; if the target data content is not stored, converting the CDN service request into a target ICN service request, and forwarding the target ICN service request to the ICN central node.

[0193] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving target data content returned by the ICN central node based on the target ICN service request.

[0194] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0195] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0196] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0197] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A request-response method, which is applied to an ICN central node in an Information-Centric Network (ICN) network element deployed in a metropolitan area network. The ICN network element includes the ICN central node and multiple ICN edge nodes, and each of the ICN edge nodes is communicatively connected to the ICN central node. The method includes: Receiving a target ICN service request sent by a first ICN edge node, where the target ICN service request is used to request target data content; Determining whether there is a second ICN edge node in the ICN network element according to the target ICN service request, where the second ICN edge node stores the target data content; If there is the second ICN edge node, forwarding the target data content stored in the second ICN edge node to the first ICN edge node.

2. The method according to claim 1, further comprising: If there is no second ICN edge node, sending a request to an upper-level Content Delivery Network (CDN) node of the ICN central node.

3. The method according to claim 2, wherein sending a request to an upper-level CDN node of the ICN central node includes: Sending a backhaul request to an upper-level CDN node of the ICN central node, where the backhaul request is used to instruct the upper-level CDN node to return the target data content; Forwarding the target data content returned by the upper-level CDN node to the first ICN edge node.

4. The method according to claim 3, wherein sending a backhaul request to an upper-level CDN node of the ICN central node includes: Converting the target ICN service request into the backhaul request, where the backhaul request is an IP-based media service request.

5. The method according to claim 1, wherein determining whether there is a second ICN edge node in the ICN network element according to the target ICN service request includes: Querying a Forwarding Information Base (FIB) according to the target ICN service request to determine whether there is the second ICN edge node in the ICN network element.

6. The method according to claim 5, wherein the FIB stores ICN service requests and connection interface information of ICN edge nodes in the ICN network element that can respond to the ICN service requests. Querying the Forwarding Information Base (FIB) according to the target ICN service request to determine whether there is the second ICN edge node in the ICN network element includes: Querying the FIB according to the target ICN service request and determining whether there is the second ICN edge node in the ICN network element according to the query result.

7. The method according to claim 6, further comprising: Updating a Pending Interest Table (PIT) according to the target ICN service request, where the PIT stores ICN service requests and connection interface information of ICN edge nodes from which the ICN service requests originate.

8. The method according to claim 7, wherein forwarding the target data content stored in the second ICN edge node to the first ICN edge node includes: Querying the FIB according to the target ICN service request; Forwarding the target ICN service request to the second ICN edge node according to the connection interface information queried from the FIB; Receiving the target data content returned by the second ICN edge node in response to the target ICN service request, and forwarding the target data content to the first ICN edge node according to the PIT.

9. A request response method applied to a first ICN edge node deployed in an ICN network element in a metropolitan area network, the ICN network element including an ICN central node and a plurality of ICN edge nodes, each of the ICN edge nodes being communicatively connected to the ICN central node, the method including: Receiving a CDN service request sent by a gateway, the CDN service request being used to request target data content; Determining whether the first ICN edge node locally stores the target data content; If the target data content is stored, responding to the CDN service request based on the target data content stored locally; If the target data content is not stored, converting the CDN service request into a target ICN service request, and forwarding the target ICN service request to the ICN central node.

10. The method according to claim 9, the method further including: Receiving the target data content returned by the ICN central node based on the target ICN service request.

11. A request response apparatus applied to an ICN central node deployed in an information centric network (ICN) network element in a metropolitan area network, the ICN network element including the ICN central node and a plurality of ICN edge nodes, each of the ICN edge nodes being communicatively connected to the ICN central node, the apparatus including: An ICN service request receiving module, configured to receive a target ICN service request sent by a first ICN edge node, the target ICN service request being used to request target data content; An ICN edge node determining module, configured to determine whether there is a second ICN edge node in the ICN network element that stores the target data content according to the target ICN service request; A content forwarding module, configured to, if there is a second ICN edge node, forward the target data content stored in the second ICN edge node to the first ICN edge node.

12. A request response apparatus applied to a first ICN edge node deployed in an ICN network element in a metropolitan area network, the ICN network element including an ICN central node and a plurality of ICN edge nodes, each of the ICN edge nodes being communicatively connected to the ICN central node, the apparatus including: A CDN service request receiving module, configured to receive a CDN service request sent by a gateway, the CDN service request being used to request target data content; A content determination module, configured to determine whether the target data content is locally stored in the first ICN edge node; A response module, configured to, if the target data content is stored, respond to the CDN service request based on the target data content locally stored; A request forwarding module, configured to, if the target data content is not stored, convert the CDN service request into a target ICN service request and forward the target ICN service request to the ICN central node.

13. An ICN network element, the ICN network element includes an ICN central node and a plurality of ICN edge nodes; The ICN central node is configured to execute the request response method according to any one of claims 1 to 8; The ICN edge node is configured to execute the request response method according to any one of claims 9 to 10.

14. A content delivery network, the content delivery network includes a plurality of ICN network elements; each ICN network element includes an ICN central node and a plurality of ICN edge nodes; The ICN central node in each of the ICN network elements is communicatively connected to an upper-level CDN node.

15. A computer device, including a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 or 9 to 10 are implemented.

16. A computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 or 9 to 10 are implemented.

17. A computer program product, including a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 or 9 to 10 are implemented.

Images