CN116800836A

CN116800836A - Flow distribution method, file downloading method, controller and storage medium

Info

Publication number: CN116800836A
Application number: CN202210878125.9A
Authority: CN
Inventors: 赵�怡
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Suzhou Software Technology Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Suzhou Software Technology Co Ltd
Priority date: 2022-07-25
Filing date: 2022-07-25
Publication date: 2023-09-22

Abstract

The embodiment of the application discloses a flow distribution method, a file downloading method, a controller, electronic equipment, a chip and a computer readable storage medium, wherein the flow distribution method is applied to the controller and comprises the following steps: acquiring a first downloading request sent by a first edge station to a central cloud; extracting first downloading information aiming at a first target file in the first downloading request; acquiring a first flow table and a first group of tables issued by a central cloud; and forwarding the first downloading request to a first target edge site through the first flow table and a first group of tables to acquire the first target file, and sending the first target file to the first edge site. The scheme of the application extracts the downloading information in the request through the controller, distributes the request through the flow table rule and the group table, realizes the P2P flow through the central cloud detouring, can control the flow, supports the segmented downloading and has safe compliance.

Description

Flow distribution method, file downloading method, controller and storage medium

Technical Field

The present application relates to the field of edge cloud technologies, and in particular, to a traffic distribution method, a file downloading method, a controller, and a storage medium.

Background

When the edge cloud provides a service, a service image file is needed to generate a virtual machine or a container, but the following situations exist in image distribution and downloading: the edge node needs to be able to flexibly deploy the service due to less resources, and cannot pre-deploy the service in advance. The related service images are not pre-deployed, but are issued on demand; the mirror images are generally large, from a few GB to tens of GB, and a single service may rely on multiple mirror images; the mirror image is larger, and the central network is slower when the central network is issued uniformly as required under the condition of more edge nodes, so that the central network is congested; the same service is generally issued to a plurality of edge clouds at the same time, the plurality of edge clouds can use the same mirror image, and a large amount of redundant network traffic and redundant mirror images can be generated; because of the security requirements of the edge cloud, the management plane is generally not able to connect directly to the internet or to the content delivery network (Content Delivery Network, CDN), but only to other edge clouds or central clouds as needed.

At present, direct downloading, traditional CDN downloading or traditional P2P downloading modes are generally adopted for image files, but the requirements of edge cloud and the aim of saving cost cannot be completely met. The main problems are: the direct downloading is too slow, and the central cloud server and the network pressure are too high; the construction and use cost of the inter-cloud network is high, and the mirror image downloading occupies a large amount of bandwidth and resources; CDN construction is complex, and a large amount of resources are consumed; the common P2P downloading method may be abused and unsafe, and P2P interconnection is not opened in the SDN network, special configuration and network access are required, the downloading method cannot be managed by the SDN network, and the downloading method is required to meet the requirements of security compliance in the cloud, and is complex to reform.

Disclosure of Invention

The embodiment of the application provides a flow distribution method, a file downloading method, a controller, electronic equipment, a chip and a computer readable storage medium.

The technical scheme of the embodiment of the application is realized as follows:

in a first aspect, an embodiment of the present application provides a flow distribution method, applied to a controller, where the method includes:

acquiring a first downloading request sent by a first edge station to a central cloud;

extracting first downloading information aiming at a first target file in the first downloading request;

acquiring a first flow table and a first group of tables issued by a central cloud;

forwarding the first downloading request to a first target edge site through the first flow table and a first group of tables to acquire the first target file, and sending the first target file to the first edge site; the first download information is obtained by the first edge site based on a file index table of a central cloud.

In a second aspect, an embodiment of the present application provides a file downloading method, applied to an edge site, including:

acquiring an index of a third target file from the center cloud;

transmitting a third downloading request for the third target file to the central cloud based on the index of the third target file;

Receiving the third target file sent by the central cloud; the third target file is obtained by a controller located in the central cloud forwarding the third download request to a third target edge site through a first flow table and a first group of tables based on third download information aiming at the third target file in the third download request.

In a third aspect, an embodiment of the present application provides a controller, including:

an acquisition unit: the method comprises the steps of acquiring a first downloading request sent to a central cloud by a first edge station; the method is also used for acquiring a first flow table and a first group of tables issued by the central cloud;

extraction unit: extracting first downloading information aiming at a first target file in the first downloading request; the first downloading information is obtained by the first edge site based on a file index table of a central cloud;

a transmitting unit: and the first downloading request is forwarded to a first target edge site through the first flow table and a first group of tables to acquire the first target file, and the first target file is sent to the first edge site.

In a fourth aspect, the present application provides an electronic device comprising: the system comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute any one of the flow distribution method or the file downloading method provided by the embodiment of the application.

In a fifth aspect, the present application provides a chip comprising: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes any one of the flow distribution method or the file downloading method provided by the embodiment of the application.

In a sixth aspect, the present application provides a computer-readable storage medium storing a computer program that causes a computer to execute any one of the traffic distribution methods or the file downloading methods provided by the embodiments of the present application.

The flow distribution method provided by the embodiment of the application is applied to a controller and is used for acquiring a first downloading request sent by a first edge station to a central cloud; extracting first downloading information aiming at a first target file in the first downloading request; acquiring a first flow table and a first group of tables issued by a central cloud; forwarding the first downloading request to a first target edge site through the first flow table and a first group of tables to acquire the first target file, and sending the first target file to the first edge site; the first download information is obtained by the first edge site based on a file index table of a central cloud. In this way, aiming at the file downloading request of the edge cloud, the scheme of the application extracts the downloading information in the request through the controller, and distributes the request through the flow table rule and the group table, so that the P2P flow is realized through the center cloud bypass, the flow can be controlled, and the segmented downloading and the safety compliance are supported.

Drawings

Fig. 1 is a schematic implementation flow chart of a flow distribution method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a flow distribution method according to a second embodiment of the present application;

fig. 3 is a schematic diagram of a network physical connection architecture of a central cloud, an edge cloud and an SDN controller according to an embodiment of the present application;

fig. 4 is a schematic diagram of P2P logical network connection between a central cloud, an edge cloud, and an SDN controller provided by an embodiment of the present application;

fig. 5 is a schematic structural diagram of a controller according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a chip provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

It should be noted that, in the embodiment of the present application, the term "and/or" is merely an association relationship describing the association object, which means that three relationships may exist, for example, a and/or B may be represented: a exists alone, A and B exist together, and B exists alone. In addition, in the embodiment of the present application, the character "/", generally indicates that the front and rear association objects are in an or relationship.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, etc.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.

Cloud Computing (Cloud Computing), an internet-based Computing approach, by which shared hardware and software resources and information can be provided to computers and other devices on demand.

Edge Computing (Edge Computing) refers to providing near-end services on the side near the object or data source, using an open platform with integrated network, computing, storage, and application core capabilities. Edge cloud, namely, a small cloud computing environment deployed in the close vicinity of a customer; unlike public cloud, which is generally deployed in a centralized data center, the edge cloud is characterized in that the single machine room is very small in scale and very many in machine room, but is extremely dispersed in geographic distribution, so that nearby cloud computing services can be provided for users.

OpenFlow belongs to a protocol in the concept of a software defined network (Software Defined Network, SDN) that functions to separate message forwarding and forwarding policies on a switch. A special controller is generally used to manage the network forwarding policy, so that the message forwarding function (implemented by a hardware chip) and the message forwarding policy (various software protocols) which are originally on the same switch device are separated to different hardware devices, wherein the message forwarding function is also completed on the switch, and the message forwarding policy is transferred to the controller for implementation.

point-To-point (P2P), also known as Peer-To-Peer, is a new technology of networks that relies on the computing power and bandwidth of the participants in the network rather than aggregating the dependencies on fewer servers. P2P technology is used for a variety of purposes and is also used in data communication of real-time media services. The point quantity P2P distribution accelerates the product, can realize the effects of accelerating the downloading and saving the bandwidth, and is very suitable for the resource distribution fields such as network tour, large files and the like.

So that the manner in which the features and objects of the present application can be understood in more detail, a more particular description of the application, briefly summarized above, may be had by reference to the appended drawings, which are not necessarily limited to the embodiments described.

Fig. 1 is a schematic implementation flow chart of a flow distribution method provided by an embodiment of the present application, as shown in fig. 1, an embodiment of the present application provides a flow distribution method, which is applied to a controller, and the method includes the following steps:

step 101: and acquiring a first downloading request sent by the first edge station to the central cloud.

Here, when the client in the first edge site needs to use the first target file, and the first edge site does not store the first target file at this time, the first edge site is required to send a first download request for the first target file to the central cloud. The controller obtains a first downloading request sent by a first edge station to the central cloud.

Step 102: extracting first downloading information aiming at a first target file in the first downloading request; the first download information is obtained by the first edge site based on a file index table of a central cloud.

In practical application, the file index table includes: file address, file hash value, list of edge sites allowed to download using P2P, download priority of each edge site, and maximum traffic limit value of each edge site. Here, the file hash value may be a hash value based on an MD5 Message-Digest Algorithm (MD 5 Message-Digest Algorithm), the number of bits of the hash value may be 128 bits, the list of edge sites allowed to be downloaded by P2P refers to all edge sites allowed to be downloaded by P2P for a specific file, the IP address of the edge site may be used as a site identifier, the downloading priority of the edge site is preconfigured, as a preferred embodiment, the priority of the edge site may be represented by a 4-bit number, and the greater the number, the more P2P downloading services may be borne by the number from 0 to 15, further, in practical application, the priority value of the edge site may be updated periodically according to the free resource degree thereof, and each edge site maximum traffic limit value refers to the maximum traffic limit value of the download network channel provided by the edge site.

The first download request includes first download information for the first target file, the first download information including at least one of: the method provided by the embodiment of the application supports segmented downloading, and the first parameter represents the range of the first target file downloaded by the first request. It can be understood that, when the first target file needs to be downloaded in segments, the first edge site sends a plurality of first downloading requests for the first target file to the central cloud, and the first parameter in the first downloading information in each first downloading request represents the range of the first target file downloaded by the first downloading request, and the plurality of small files downloaded by the first downloading request for the first target file are integrated at the first edge site to obtain the first target file. Illustratively, when a file of 6000 bytes total needs to be downloaded in sections, if it is divided into two parts, 1-3000 bytes and 3100-6000 bytes, two download requests for the file need to be sent to the central cloud, a first parameter in one of the two download requests is used to indicate that the 1-3000 bytes of the file are downloaded, and a first parameter in the other download request is used to indicate that the 3001-6000 bytes of the file are downloaded. As a preferred embodiment of the present application, the first download request is a request based on the hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) protocol, and the first parameter in the corresponding first download request is a range parameter.

Based on this, in the flow distribution method provided by an embodiment of the present application, the file index table includes: file address, file hash value, list of edge sites allowed to use P2P for downloading, downloading priority of each edge site, maximum flow rate limit value of each edge site;

the first download information includes at least one of: the address of the first target file, the hash value of the first target file and a first parameter; the first parameter is used for marking the range of the first request for downloading the first target file when the first parameter is used for downloading the fragments.

Step 103: and acquiring a first flow table and a first group of tables issued by the center cloud.

The flow distribution method provided by the embodiment of the application, the first flow table comprises the following steps: a first entry, a second entry, a third entry, and a fourth entry; wherein,

the first table entry includes: a first table field, configured to indicate a flow table value of the first table entry in the first flow table; a first Priority field, configured to indicate a matching Priority of the first entry; a first Match Fields field for indicating a first Match condition for the first entry; and a first Instructions field for indicating a first action of the first entry; wherein the first matching condition includes at least one of: the request is an HTTP message, a hash value exists in the request, and a range parameter exists in the request; the first action includes: modifying the metadata field based on the hash value in the request and sending the entered request to the third entry;

The second entry includes: a second table field, configured to indicate a flow table value of the second table entry in the first flow table; a second Priority field, configured to indicate a matching Priority of the first entry; a second Match Fields field for indicating a second Match condition for said second entry; and a second Instructions field for indicating a second action of the second entry; wherein the second matching condition includes at least one of: the request is an HTTP message, and a hash value exists in the request; the second action includes: modifying metadata fields based on hash values in the requests and sending the input requests to a central cloud file distribution center;

the third entry includes: a third table field, configured to indicate a flow table value of the first table entry in the first flow table; a third Match Fields field for indicating a third Match condition for said third entry; and a third Instructions field for indicating a third action of the third entry; wherein the third matching condition includes: matching the hash value part in the metadata field; the third action includes: presetting a flow threshold, discarding requests exceeding the flow threshold, and sending requests not exceeding the flow threshold to the first group of tables;

Wherein the first set of tables is configured to send a request sent by the third table entry to the first target edge site;

the fourth table entry comprises a third table field, and is used for indicating a flow table value of the fourth table entry in the first flow table; a fourth Match Fields field for indicating a fourth Match condition for said fourth entry; and a fourth Instructions field for indicating a fourth action of the fourth entry; wherein the fourth matching condition includes: the request is an HTTP message; the fourth action includes: discarding the request;

the values of the first table field, the second table field, the third table field and the fourth table field have the following size relations: first table field = second table field < third table field < fourth table field; the magnitude relation between the values of the first Priority field and the second Priority field is as follows: first Priority field > second Priority field.

Here, the central cloud may issue an Openflow flow table rule to the controller, where the first table entry is mainly used to process a file downloading request that needs to be downloaded in a segmented manner, where the metadata field is a custom matching field in the Openflow protocol, and may transfer between flow tables, and support mask fuzzy matching, and in practical application, the flexibility of the metadata field may be utilized, and in the flow table, as an identifier of file transfer, a portion of the metadata field may be modified to a hash value of the target file, as an identifier of the file, and of course, other parameters may be added to the metadata field on the basis of the hash value, such as increasing priority of an edge site, and so on. The second table entry mainly processes a file downloading request which does not need to be downloaded in a segmented mode, and after the metadata field is modified, the request is sent to a file distribution center of the central cloud to download the file, and distribution through a group table is not needed. In the third table entry, the speed limit table can limit the speed of the request traffic, so that large-traffic malicious attacks and viruses are avoided, and the security of the center cloud is ensured. The files aimed by the download requests reaching the fourth table entry belong to the files in the central cloud index table, and all the requests are discarded.

Further, a first set of tables is used for sending the request sent by the third table entry to the first target edge site. The first target edge site is allocated according to a preset allocation rule through a first set of tables, and the higher the priority of the configured edge site is, the more downloading traffic will be born. In practical application, the type of the first group of tables can be group; the action sockets comprise a plurality of sockets, each socket corresponds to a forwarding outlet, and all edge sites allowing P2P downloading of the target downloading file can be corresponding to each forwarding outlet; meanwhile, the DSCP value of the IP message is rewritten to be changed into a downloading priority value corresponding to each edge site; and each socket weight is provided with a weight value used for determining the weight proportion during downloading in load balancing, and the weight value is set to be equal to the corresponding downloading priority value of the edge site, so that the edge site with high downloading priority can bear more downloading traffic tasks.

In actual application, the first table entry, the second table entry, the third table entry and the fourth table entry may be set as the following formats:

a first table entry: "table=0, match priority 65535, match: HTTP message, and there are query parameters in HTTP: __ hash=h1 and there is a range parameter in the HTTP header; the action of modifying metadata=h2 (h2=the first 60 bits of truncated file hash value+4 bits of edge site priority value), forwarding to table=1).

The second table entry: "table=0, match priority 65534, match: HTTP message, and there are query parameters in HTTP: __ hash=h1; the actions of modifying metadata=h2 (h2=the top 60 bits+4 bits of the truncated file hash value edge site priority value); forwarding to a central cloud file distribution center.

Third table entry: "table=1, match metadata=h2/0 xfffffffffffffffff 0", action: meter_id=speed limit table, forward to first set of table ", where 0 xfffffffffffffffffff 0 is a mask, indicating that only the first 60 bits of H2 are matched, i.e. the file hash value part, excluding the download priority part, can be ignored for saving entries, since the download priority part is always updated.

Fourth entry: "table=2, match HTTP message, action: discard".

Step 104: and forwarding the first downloading request to a first target edge site through the first flow table and a first group of tables to acquire the first target file, and sending the first target file to the first edge site.

In practical application, the controller may be an SDN controller, and the controller sends the downloaded file to the first edge site, so that the P2P traffic is realized through central cloud detouring, and network congestion is not generated.

In the flow distribution method provided by the further embodiment of the present application, for a plurality of newly-built edge sites, the method further includes:

receiving a second downloading request sent by a newly-built second edge station;

caching the second downloading request, and storing second downloading information aiming at a second target file in the second downloading request into a hash dictionary; wherein the second download information includes: the file name and the file segment of the second target file and the port of the second edge site; the key value pairs in the hash dictionary include: a key name for indicating a file name and a file segment; the value list is used for indicating the edge site port of the request message;

presetting request cache time, and adding all edge site ports corresponding to all new download requests with the same file names and file segments in the at least one new download request and the file names and file segments in the second download request to a value list corresponding to the second request in the hash dictionary for at least one new download request sent by other newly built edge sites in the second download request cache time;

when the message caching time is reached, changing a first field of the cached second downloading request into a first preset value, and then sending a modified second downloading request to the first group of tables, wherein the modified second downloading request is sent to a second target edge site through the first group of tables to obtain a second target file; when the second target file returns to the controller, the second field is configured by the second target edge site to be a second preset value; the first preset value is used for indicating the second target edge site to configure a second field as the second preset value when returning to the second target file, and the second preset value is used for indicating the file name and the file segment of the second target file;

And acquiring a third flow table and a second group of tables issued by the central cloud, and distributing the second target file to all edge site ports in a value list corresponding to the second downloading request in a hash dictionary through the third flow table and the second group of tables based on the second preset value.

In practical application, the message buffering time can be set according to the needs, such as 5 seconds, 6 seconds, 8 seconds, etc., which is not limited by the present application. Here, the first preset value is used to instruct the second target edge station to configure the second field as the second preset value when the second target edge station returns the second target file, when the second target edge station recognizes that the first field in the download request is the first preset value, the second field is configured as the second preset value when the download request replies to the file, as a preferred embodiment of the present application, the download request is a request based on the HTTP protocol, the first field is a reference field, the first preset value is SDN, the second field is a Cache-Control field, and the second preset value is set as a file name+a file segment.

The third flow table includes: a fifth table entry, including a fifth table value, a flow table value for indicating the fifth table entry in the third flow table; a fifth Match Fields field for indicating a fifth Match condition for said fifth entry; and a fifth Instructions field for indicating a fifth action of the fifth entry; wherein the fifth matching condition includes at least one of: HTTP message, the second field in the message is the second preset value; the fifth action includes: to a second set of tables.

In practical application, the fifth table entry may be set to "table=1, match HTTP packet, and Cache-Control field is: filename + file segment, action: send to the second set of tables.

The second set of tables is defined as: and sending the list to the request source edge site list. Here, the second group of tables find all the edge site ports in the corresponding value list of the target file in the hash dictionary according to the second preset value, and distribute the target file to each edge site port.

Further, the second edge site may send a second download request to the controller based on a second flow table issued by the central cloud. Specifically, the second flow table includes: the sixth table entry comprises a sixth table value and a flow table value used for indicating the sixth table entry in the second flow table; a sixth Match Fields field for indicating a sixth Match condition for said sixth entry; and a sixth Instructions field for indicating a sixth action of the sixth entry; wherein the sixth matching condition includes at least one of: the HTTP message and a third field in the message are a third preset value; the sixth action includes: and sending the data to a controller.

When the second edge cloud sends a second download request, a third field in the configuration request is a third preset value, so that the second download request is sent to the controller through a second group of tables.

In practical application, the third field may be the same as the first field, set to a reference field, the third preset value may be set to canmage, and correspondingly, the sixth table entry may be set to "table=1, and match with an HTTP packet, where the reference field is: canmage, action, send to controller.

The flow distribution method provided by the further embodiment of the application comprises the following steps:

recording the mapping relation among the third stream table, the second group table and the second target file size;

and polling to detect the message statistical information of the third flow table, and deleting the third flow table and the second group table corresponding to the third flow table if the message size exceeds the second target file size corresponding to the third flow table.

Specifically, the second target file, the third stream table and the second group table have a one-to-one correspondence relationship, the controller records the correspondence relationship between the second target file, the third stream table and the second group table, and polls and detects the message statistical information of the third stream table, and if the message size exceeds the size of the second target file corresponding to the third stream table, the third stream table and the second group table corresponding to the third stream table are deleted.

The embodiment of the application also provides a file downloading method which is applied to the edge site and comprises the following steps:

Acquiring an index of a third target file from the center cloud;

Here, the first download information, the first flow table, and the first set of tables are the same as those of the foregoing embodiments, and the related description may refer to the foregoing embodiments, which are not repeated herein.

The file downloading method provided by the further embodiment of the present application further includes, after receiving the third target file forwarded by the controller:

detecting whether the third target file is complete, if so, storing a specific catalog from the third target file to the third edge site, and sending third information to the central cloud; the third information is used for notifying the central cloud to update a file index table so as to provide the downloaded third target file for other edge sites to download; wherein,

When the third target file needs to be downloaded in a segmented manner, before the detecting detects whether the third target file is complete, the method further comprises: all file blocks downloaded in a segmented manner are spliced into a large file.

Here, whether the file is complete may be determined by comparing the size of the file and the hash value of the file, or may be determined in other manners, which is not limited by the present application.

Referring to fig. 2, fig. 2 is a second flowchart illustrating an implementation of a flow distribution method according to another embodiment of the present application, as shown in fig. 2, the flow distribution method according to the embodiment includes the following steps: step 201: the central cloud establishes an image file distribution management platform and prepares an image file index table; step 202: the center cloud issues an Openflow flow table to the global SDN controller; step 203: when the edge cloud downloads the target file, acquiring an index of the target file from the central cloud; step 204: the edge cloud newly adds a parameter_hash in the request to request the downloading of the P2P mirror image file; step 205: after the file downloading is completed, the edge cloud compares the file integrity; step 2051: returning to step 204 to resend the download request for the target file when the file is incomplete; step 2052: when the file is complete, storing the target file to a specific directory; step 206: sending third information to the central cloud, and informing the central cloud to update the mirror image file index table; step 207: and (5) ending.

Here, some central clouds may not have P2P capability, and at this time, a mirror image distribution management platform needs to be established, so that the central clouds can support the P2P function, and after updating the index table by the central clouds, the group table can be updated according to the update content, so as to ensure the accuracy of file downloading information. It can be understood that the downloading of the image file can be realized by the flow distribution method and the file downloading method provided by the embodiment of the application, and any large file and the file needing to be downloaded in a large-scale concurrency way can be realized by the flow distribution method and the file downloading method provided by the embodiment of the application.

Referring to fig. 3, fig. 3 is a schematic diagram of a network physical connection architecture of a center cloud, an edge cloud, and an SDN controller according to an embodiment of the present application. Referring to fig. 4, fig. 4 is a schematic diagram of a P2P logical network connection between a center cloud, an edge cloud, and an SDN controller according to another embodiment of the present application.

According to the flow distribution method and the file downloading method provided by the embodiment of the application, the controller is used for extracting the edge cloud to send the downloading request to the central cloud, extracting the parameters in the downloading request, carrying out P2P distribution, load balancing and other treatments of special flow table rules, and not needing to install special P2P client and server software on all the clouds and servers, so that the complexity of the system is greatly reduced, after the controller participates in parameter sensing and forwarding, one file flow can be distributed through a group table, and the full transmission in the network for many times from the beginning of the client transmission is not needed, and the consumption of network bandwidth is saved; after the file is downloaded by the edge cloud, the center cloud is informed to update the file index table, then the group table is dynamically refreshed, the on-demand connection of the file downloading between the center cloud and the edge cloud is formed, the bandwidth loss is reduced, the speed limit can be supported through the control of the Openflow flow table and the speed limit table, the large-scale downloading is prevented, the server and the network are impacted, and the safety controllability of P2P distribution is increased; the first 60 bits of H2 are matched through the mask, so that the number of flow table rules can be greatly reduced, the resource utilization rate of table entries is improved, and the management of flow tables is facilitated; the embodiment of the application redefines and marks whether to merge the buffer of the request message by utilizing the reference field and the Cache-Control field, thereby reducing the resource use, fully utilizing the existing HTTP protocol to solve the problem, reducing the workload of the whole system modification, simultaneously, the initiation time of a plurality of edge cloud download requests is close, fully utilizing the controller to buffer and merge a plurality of HTTP requests, storing the associated key information, compressing a plurality of requests and reducing the network load; when the file block returns, a plurality of ports are copied and distributed simultaneously through the Cache-Control field and associated key information stored in the request, so that the bandwidth cost is reduced; the method can judge whether the requested file block is distributed or not and timely release the flow table resources through the file block size value stored in the request and the message statistical mode in the SDN controller polling detection flow table rule; doing so may explicitly inform the SDN that the transfer has been completed without modifying the server-side HTTP reply header.

In addition, for the P2P service, the method provided by the embodiment of the application can be realized by using a pure HTTP protocol and ports, and is simple and convenient without using a special P2P protocol and a plurality of special ports; for the request of segmented downloading, the request is divided into a plurality of parts, the request message is sent to a plurality of edge clouds in a group table load balancing mode, then the edge clouds with different load priorities return to different file blocks, the purpose of load balancing is achieved reversely, and in this way, the problem that the OpenFlow group table cannot achieve broadcasting and load balancing of a single file at the same time can be avoided well.

The embodiment of the application also provides a controller 500; fig. 5 is a schematic structural diagram of a controller 500 according to an embodiment of the present application, and as shown in fig. 5, the controller 500 according to an embodiment of the present application includes:

the acquisition unit 501: the method comprises the steps of acquiring a first downloading request sent to a central cloud by a first edge station; the method is also used for acquiring a first flow table and a first group of tables issued by the central cloud;

extraction unit 502: extracting first downloading information aiming at a first target file in the first downloading request; the first downloading information is obtained by the first edge site based on a file index table of a central cloud;

Transmitting section 503: and the first downloading request is forwarded to a first target edge site through the first flow table and a first group of tables to acquire the first target file, and the first target file is sent to the first edge site.

In other embodiments of the present application, the file index table includes: file address, file hash value, list of edge sites allowed to use P2P for downloading, downloading priority of each edge site, maximum flow rate limit value of each edge site; the first download information includes at least one of: the address of the first target file, the hash value of the first target file and a first parameter; the first parameter is used for marking the range of the first request for downloading the first target file when the first parameter is used for downloading the fragments.

In other embodiments of the present application, the first flow table includes: a first entry, a second entry, a third entry, and a fourth entry; wherein,

the first table entry includes: a first table field, configured to indicate a flow table value of the first table entry in the first flow table; a first Priority field, configured to indicate a matching Priority of the first entry; a first Match Fields field for indicating a first Match condition for the first entry; and a first Instructions field for indicating a first action of the first entry; wherein the first matching condition includes at least one of: the request is an HTTP message, a hash value exists in the request, and a first parameter exists in the request; the first action includes: modifying the metadata field based on the hash value in the request and sending the entered request to the third entry;

the fourth table entry comprises a third table field, and is used for indicating a flow table value of the fourth table entry in the first flow table; a fourth Match Fields field for indicating a fourth Match condition for said fourth entry; and a fourth Instructions field for indicating a fourth action of the fourth entry; wherein the fourth matching condition includes: the request is an HTTP message; the fourth action includes: the request is discarded.

In other embodiments of the present application, the controller further comprises a receiving unit 504: the second downloading request is used for receiving a newly-built second edge station; caching unit 505: the second downloading request is used for caching the second downloading request, and second downloading information aiming at a second target file in the second downloading request is stored in the hash dictionary; wherein the second download information includes: the file name and the file segment of the second target file and the port of the second edge site; the key value pairs in the hash dictionary include: a key name for indicating a file name and a file segment; the value list is used for indicating the edge site port of the request message; setting unit 506: for presetting request cache time, for at least one new download request sent by other newly built edge sites in the second download request cache time, adding all edge site ports corresponding to all new download requests with the same file names and file segments in the at least one new download request and the same file names and file segments in the second download request to a value list corresponding to the second request in the hash dictionary; the transmitting unit 503: when the message buffering time is reached, changing the first field of the buffered second downloading request into a first preset value, and then sending a modified second downloading request to the first group of tables, wherein the modified second downloading request is sent to a second target edge site through the first group of tables to obtain a second target file; when the second target file returns to the controller, the second field is configured by the second target edge site to be a second preset value; the first preset value is used for indicating the second target edge site to configure a second field as the second preset value when returning to the second target file, and the second preset value is used for indicating the file name and the file segment of the second target file; the acquisition unit 501: and the third flow table and the second group table which are issued by the central cloud are also used for acquiring, based on the second preset value, the second target file to all the edge site ports in the value list corresponding to the second downloading request in the hash dictionary through the third flow table and the second group table.

In other embodiments of the present application, the controller further comprises: detection unit 507: the mapping relation among the third stream table, the second group table and the second target file size is recorded;

Those skilled in the art will appreciate that the implementation functions of the units in the controller shown in fig. 5 can be understood with reference to the relevant description of the foregoing method. The functions of the units in the controller shown in fig. 5 may be implemented by a program running on a processor or by a specific logic circuit.

Fig. 6 is a schematic structural diagram of an electronic device 600 according to an embodiment of the present application. The electronic device 600 shown in fig. 6 comprises a processor 610, from which the processor 610 may call and run a computer program to implement the method in an embodiment of the application.

Optionally, as shown in fig. 6, the electronic device 600 may also include a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, as shown in fig. 6, the electronic device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

The electronic device 600 may be a controller in the embodiment of the present application, and the electronic device 600 may implement corresponding processes implemented by the controller in the methods in the embodiments of the present application, which are not described herein for brevity.

Fig. 7 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 7 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 7, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the method in an embodiment of the application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

The chip can be applied to the controller in the embodiment of the present application, and the chip can implement the corresponding flow implemented by the controller in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program. The computer readable storage medium may be applied to the controller in the embodiment of the present application, and the computer program makes the computer execute the corresponding flow implemented by the controller in each method in the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions. The computer program product may be applied to the controller in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the controller in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program. The computer program may be applied to the controller in the embodiment of the present application, and when the computer program runs on the computer, the computer is caused to execute the corresponding flow implemented by the controller in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A flow distribution method, applied to a controller, comprising:

extracting first downloading information aiming at a first target file in the first downloading request; the first downloading information is obtained by the first edge site based on a file index table of the center cloud;

and forwarding the first downloading request to a first target edge site through the first flow table and a first group of tables to acquire the first target file, and sending the first target file to the first edge site.

2. The traffic distribution method according to claim 1, wherein the file index table comprises: file address, file hash value, list of edge sites allowed to download using P2P, downloading priority of each edge site and maximum flow rate limit value of each edge site;

3. The flow distribution method according to claim 1, wherein the first flow table includes: a first entry, a second entry, a third entry, and a fourth entry; wherein,

The values of the first table field, the second table field, the third table field and the fourth table field have the following magnitude relation: first table field = second table field < third table field < fourth table field; the magnitude relation between the values of the first Priority field and the second Priority field is as follows: first Priority field > second Priority field.

4. A traffic distribution method according to any of claims 1-3, characterized in that for a newly created plurality of edge sites, the method further comprises:

5. The flow distribution method according to claim 4, comprising:

6. A method for downloading a file, applied to an edge site, comprising:

acquiring an index of a third target file from the center cloud;

7. The file downloading method as claimed in claim 6, further comprising, after receiving the third target file forwarded by the controller:

When the third target file needs to be downloaded in a segmented manner, before the detecting detects whether the third target file is complete, the method further comprises:

all file blocks downloaded in a segmented manner are spliced into a large file.

8. A controller, comprising:

9. An electronic device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the flow distribution method according to any of claims 1-5, the file download method according to any of claims 6-7.

10. A computer-readable storage medium storing a computer program for causing a computer to execute the flow distribution method according to any one of claims 1 to 5, the file download method according to any one of claims 6 to 7.