CN112153172B

CN112153172B - Back source address configuration method and device, computer equipment and readable medium

Info

Publication number: CN112153172B
Application number: CN202011032922.2A
Authority: CN
Inventors: 陶国军; 缪川扬; 童浩
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-09-27
Filing date: 2020-09-27
Publication date: 2021-08-17
Anticipated expiration: 2040-09-27
Also published as: CN112153172A

Abstract

The present disclosure provides a back-to-source address configuration method, which receives a back-to-source address configuration message sent by an MEC-CDN content source node, and obtains a back-to-source address configuration policy carried in the back-to-source address configuration message, where the back-to-source address configuration policy at least includes a back-to-source address to be configured, and the back-to-source address to be configured is a private network address of the MEC-CDN content source node; if the starting source return address configuration is determined, performing Round Trip Time (RTT) test on the MEC-CDN content source node to obtain a first RTT, and performing RTT test on a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT; if the configuration of the source return address is determined to be changed at least according to the first RTT and the second RTT, configuring the first source return address as the source return address to be configured; users outside the venue can obtain real-time high-interactivity live broadcast media content inside the venue, bandwidth consumption required by public network transmission is saved, and transmission delay is reduced. The disclosure also provides a source return address configuration device, a computer device and a readable medium.

Description

Back source address configuration method and device, computer equipment and readable medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for configuring a source return address, a computer device, and a readable medium.

Background

A Content Delivery Network (CDN) is widely used in the fields of internet audio and video transmission, IPTV (interactive Network television) Network media transmission, and the like. The CDN can push the content onto the service node closest to the user so that the user accesses the content nearby. The CDN is used for media transmission, so that the response speed of a user for acquiring the media content can be greatly improved, and the bandwidth pressure of the media content transmitted on a backbone network is also greatly reduced. Due to the development of cloud computing and edge computing technologies, the CDN edge node may further sink to a location closer to the user in a virtualization manner, and may provide a greater computing capability than the conventional CDN node, so that a more excellent consumption experience may be further provided than the conventional audio/video service, for example, less bandwidth requirements may be consumed while consuming an ultra-high definition video (4K/8K), a shorter latency experience, and a greater interaction capability may be consumed.

A CDN scheme based on a Multi-access/Mobile Edge Computing (MEC) technology is gradually beginning to be used commercially in live broadcast services of some current event venues, and may be applied to provide various live video/on-demand applications inside venues, such as standard definition/high definition/ultra-high definition live broadcast (2D), VR (Virtual Reality) live broadcast, (3DoF, grid of free, Degree of Freedom), 360-Degree free view angle, and the like. As shown in fig. 1, the existing CDN networking architecture includes a CDN node including an MEC-CDN node supporting an MEC and a CDN edge node of a conventional CDN network (the edge node is generally deployed at an edge of a metropolitan area network and cannot be further sunk). According to different multimedia service requirements, the MEC-CDN nodes are designed differently according to functions thereof and comprise MEC-CDN content source nodes and MEC-CDN service nodes. The MEC-CDN content source node generates media content and provides continuous multicast stream or unicast stream services with different formats according to the service types. The MEC-CDN service node is responsible for providing media stream service for the user terminal, a default back-to-source node address is configured in the MEC-CDN service node as a public network address of a CDN upstream node (usually an edge node of a traditional CDN) to which the MEC-CDN service node belongs, and multiple back-to-source node switching is supported. When the MEC-CDN service node does not hit the content, returning the content to an upper-level node (namely a CDN edge node) according to the configuration of the back-source address. And when the CDN edge node does not hit the content, returning the content to an upper-level node (namely the CDN content center node) according to the configuration of the return source address. When the CDN content center does not have content, the content needs to be directly acquired from the content source station according to the preset back-to-source interface.

Since the MEC-CDN node may be deployed at an access base station inside the venue, the service may be provided with some local processing requirements, such as transcoding of video, local storage, local service request response, etc. For a User outside a venue, the service provided by the User takes the requirement of network transmission bandwidth into consideration, so the service category is greatly limited, for example, when a venue live broadcast provider synthesizes a multi-angle video into a code stream, the code stream is uploaded to an internet Content center node in a UGC (User Generated Content) manner, and then pushed to a CDN edge node in a conventional CDN Content distribution manner. The method includes the steps that a user obtains content from a CDN edge node in a traditional mode, when no related content exists in the CDN edge node, the content is pulled down in a mode that the CDN edge node returns to a CDN content center node, and all data need to be transmitted to a network edge to guarantee that the user can obtain the best viewing experience.

In a traditional source return address configuration scheme, a source return address is configured as a public network address of a superior node, and only a single resource can be applied to the superior node, and under the condition that the superior node does not have content, the content can be applied only by returning the source to the superior node, so that the problems of bandwidth consumption and overlarge time delay are caused due to the overlong source return path. In a live broadcast scene of a venue, local services can be provided for users in the venue only, media services in the venue cannot be provided for users outside the venue, and the users outside the venue can only use public network services in a unified way. In actual deployment, the content uploaded by the MEC-CDN content source node through the UGC is not necessarily the content of all formats in the source station, and the service provided by the MEC-CDN content source node is not all able to directly implement distribution of content streams in the public network, which requires the MEC-CDN content source node to generate corresponding content in real time, and users outside the venue cannot obtain the content generated in real time, resulting in poor content acquisition real-time performance.

Disclosure of Invention

The disclosure provides a method and a device for configuring a source-back address, a computer device and a readable medium.

In a first aspect, an embodiment of the present disclosure provides a method for configuring a source address, including:

receiving a source returning address configuration message sent by a MEC-CDN content source node of a multi-access/mobile edge computing content delivery network, and acquiring a source returning address configuration strategy carried in the message, wherein the source returning address configuration strategy at least comprises a source returning address to be configured, and the source returning address to be configured is a private network address of the MEC-CDN content source node;

if the starting source return address configuration is determined, performing Round Trip Time (RTT) test on the MEC-CDN content source node to obtain a first RTT, and performing RTT test on a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT;

and if the configuration of the source returning address is determined to be changed at least according to the first RTT and the second RTT, configuring the first source returning address as the source returning address to be configured.

In some embodiments, after configuring the first fallback address as the fallback address to be configured, the method further comprises:

and configuring a second source returning address as a public network address of a CDN edge node to which the MEC-CDN service node belongs, wherein the use priority of the first source returning address is higher than that of the second source returning address.

In some embodiments, the determining to change the source address configuration according to at least the first RTT and the second RTT includes: and if the first RTT is less than the second RTT, determining to change the configuration of the source address.

In some embodiments, the back source address configuration policy further includes a limiting parameter, and after performing round trip time RTT test with the MEC-CDN content source node and performing RTT test with a CDN edge node to which the MEC-CDN service node belongs, before configuring the first back source address as the back source address to be configured, the method further includes: adjusting the processing performance parameters of the MEC-CDN service node according to the limiting parameters;

the determining to change the configuration of the source address according to at least the first RTT and the second RTT comprises:

and if the first RTT is smaller than the second RTT and the processing performance parameter adjusted by the MEC-CDN service node reaches the limiting parameter, determining to change the configuration of the source address.

In some embodiments, the method for configuring an address of a source, further comprises:

and if the configuration of the source address is determined not to be changed according to the first RTT, the second RTT and the limiting parameter, or the configuration of the source address is determined not to be changed according to the first RTT and the second RTT, configuring a second source address as the source address to be configured, wherein the use priority of the first source address is higher than that of the second source address.

In some embodiments, the determining not to change the source address configuration according to the first RTT, the second RTT, and the restriction parameter includes: if the first RTT is greater than or equal to the second RTT, and/or the processing performance parameter adjusted by the MEC-CDN service node does not reach the limiting parameter, determining not to change the configuration of the source address; alternatively, the first and second electrodes may be,

determining not to change the configuration of the source address according to the first RTT and the second RTT, including: and if the first RTT is greater than or equal to the second RTT, determining not to change the configuration of the source address.

In some embodiments, the source address configuration policy further includes mode information used for indicating a source address configuration start opportunity, where the mode information is first mode information or second mode information; the determining to initiate a source address configuration includes: determining to start the configuration of the source address according to the mode information;

the determining, when the mode information is the first mode information, to start the source address configuration according to the mode information includes: if a source returning address configuration message sent by an MEC-CDN content source node is received, determining to start source returning address configuration;

when the mode information is second mode information, the determining to start back to source address configuration according to the mode information includes: and if the preset time length is passed after a source return address configuration message sent by the MEC-CDN content source node is received, or the failure frequency of acquiring the requested content from the corresponding CDN node according to the locally configured first source return address reaches the preset frequency, determining to start source return address configuration.

In some embodiments, the performing round trip time RTT tests with the MEC-CDN content origin node comprises: performing Round Trip Time (RTT) test with the MEC-CDN content source node according to a preset period;

performing RTT test on the CDN edge node to which the MEC-CDN service node belongs, wherein the RTT test comprises the following steps: and performing Round Trip Time (RTT) test with a CDN edge node to which the MEC-CDN service node belongs according to the period.

In another aspect, an embodiment of the present disclosure further provides a method for configuring a source address, including:

when the preset condition is met, sending a node discovery request message carrying the screening condition to the management equipment;

receiving a screening result returned by the management equipment, wherein the screening result comprises information of a multi-access/mobile edge computing content delivery network MEC-CDN service node, and is obtained by screening from the managed MEC-CDN node by the management equipment according to the screening condition;

and sending a back-source address configuration message carrying a back-source address configuration strategy to an MEC-CDN service node corresponding to the screening result, wherein the back-source address configuration strategy at least comprises a back-source address to be configured, and the back-source address to be configured is a private network address of the MEC-CDN content source node.

In some embodiments, the screening conditions include one or any combination of: the IP addresses belong to the same network segment, have the same MEC identity, belong to the same geographical area or service area, have the same service capabilities, belong to the same content provider, belong to the same service provider.

In some embodiments, the management device is a CDN management server or an MEC management server.

In another aspect, an embodiment of the present disclosure further provides an apparatus for configuring a source address, including: the system comprises a receiving module, an obtaining module, a testing module and a configuration module, wherein the receiving module is used for receiving a back source address configuration message sent by a content source node of a multi-access/mobile edge computing content delivery network MEC-CDN;

the obtaining module is configured to obtain a source return address configuration policy carried in the MEC-CDN, where the source return address configuration policy at least includes a source return address to be configured, and the source return address to be configured is a private network address of the MEC-CDN content source node;

the testing module is used for performing Round Trip Time (RTT) test on the MEC-CDN content source node to obtain a first RTT and performing RTT test on a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT when starting source return address configuration is determined;

the configuration module is used for configuring the first return source address as the return source address to be configured when determining to change the return source address configuration according to at least the first RTT and the second RTT.

In another aspect, an embodiment of the present disclosure further provides a source address configuration apparatus, including a sending module and a receiving module, where the sending module is configured to send a node discovery request message carrying a screening condition to a management device when a preset condition is met;

the receiving module is configured to receive a screening result returned by the management device, where the screening result includes information of a multi-access/mobile edge computing content delivery network MEC-CDN service node, and is obtained by screening, by the management device, the MEC-CDN node governed according to the screening condition;

the sending module is further configured to send a source return address configuration message carrying a source return address configuration policy to the MEC-CDN service node corresponding to the screening result, where the source return address configuration policy at least includes a source return address to be configured, and the source return address to be configured is a private network address of the MEC-CDN content source node.

In another aspect, an embodiment of the present disclosure further provides a computer device, including:

one or more processors;

a storage device having one or more programs stored thereon;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the return-to-source address configuration method as previously described.

In yet another aspect, the disclosed embodiments also provide a computer readable medium, on which a computer program is stored, where the program is executed to implement the source address configuration method as described above.

The method and the device for configuring the back source address provided by the embodiment of the disclosure receive a back source address configuration message sent by an MEC-CDN content source node, and acquire a back source address configuration policy carried in the back source address configuration message, wherein the back source address configuration policy at least comprises a back source address to be configured, and the back source address to be configured is a private network address of the MEC-CDN content source node; if the starting source return address configuration is determined, performing Round Trip Time (RTT) test on the MEC-CDN content source node to obtain a first RTT, and performing RTT test on a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT; if the configuration of the source return address is determined to be changed at least according to the first RTT and the second RTT, configuring the first source return address as the source return address to be configured; in the embodiment of the disclosure, the candidate MEC-CDN service node performs the preferable judgment of the back source path in a mode of actively pushing the back source address configuration strategy, and the configured back source address can directly point to the MEC-CDN content source node, so that the back source path is shortened, and the back source accuracy is improved; in a live broadcast scene of a venue, when a service is performed for a user outside the venue, the return source address is configured to be a private network address of the MEC-CDN content source node, so that the user outside the venue can obtain live broadcast media content with high interactivity in the venue in real time, bandwidth consumption required by public network transmission is saved, and transmission delay is reduced.

Drawings

Fig. 1 is a schematic diagram of a conventional CDN networking architecture;

fig. 2 is a schematic diagram of a CDN networking architecture provided in an embodiment of the present disclosure;

fig. 3 is a schematic diagram of a logical functional architecture of an MEC-CDN node according to an embodiment of the present disclosure;

fig. 4 is a first schematic view illustrating a back-source address configuration process applied to an MEC-CDN service node according to an embodiment of the present disclosure;

fig. 5 is a schematic view illustrating a configuration flow of a source return address applied to the MEC-CDN service node according to the embodiment of the present disclosure;

fig. 6 is a third schematic view of a back-source address configuration process applied to the MEC-CDN service node according to the embodiment of the present disclosure;

fig. 7 is a schematic view of a back-source address configuration process applied to an MEC-CDN content source node according to an embodiment of the present disclosure;

fig. 8a is a signaling diagram illustrating a source address configuration procedure according to an embodiment of the present disclosure;

FIG. 8b is a diagram illustrating a source address configuration policy in the embodiment of FIG. 8 a;

fig. 9 is a signaling diagram of a source address configuration flow according to another embodiment of the present disclosure;

FIG. 10 is a first block diagram illustrating a source address configuration apparatus according to an embodiment of the present disclosure;

fig. 11 is a second schematic structural diagram illustrating a source address configuration apparatus according to an embodiment of the present disclosure;

fig. 12 is a schematic structural diagram of another source address configuration apparatus according to an embodiment of the present disclosure.

Detailed Description

Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but which may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Embodiments described herein may be described with reference to plan and/or cross-sectional views in light of idealized schematic illustrations of the disclosure. Accordingly, the example illustrations can be modified in accordance with manufacturing techniques and/or tolerances. Accordingly, the embodiments are not limited to the embodiments shown in the drawings, but include modifications of configurations formed based on a manufacturing process. Thus, the regions illustrated in the figures have schematic properties, and the shapes of the regions shown in the figures illustrate specific shapes of regions of elements, but are not intended to be limiting.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

The embodiment of the present disclosure provides a back-to-source address configuration method, which is applied to a CDN network system shown in fig. 2, where the system includes: a CDN management Server/SLB (Server Load Balancer), an MEC management Server, MEC-CDN nodes, CDN edge nodes, and a CDN content center node (not shown), where the MEC-CDN nodes include an MEC-CDN content source node and an MEC-CDN service node. One CDN edge node may govern one MEC-CDN content origin node and at least one MEC-CDN service node, and one CDN content center node may govern at least one CDN edge node. The upper nodes of the MEC-CDN content source node and the MEC-CDN service node are CDN edge nodes to which the MEC-CDN content source node and the MEC-CDN service node belong, and the upper nodes of the CDN edge nodes are CDN content center nodes to which the CDN edge nodes belong. The MEC-CDN nodes may be deployed on the same or different edge computing platforms (MEPs) or MEC hosts (MEC hosts) for providing CDN service capabilities, where the MEPs provide an inter-MEC system communication, and the MEC-CDN nodes may discover each other through a MEC management server. The MEC management server records the MEP information, so the MEC-CDN node information running on these MEPs can be queried through the MEC management server. The CDN management server/SLB records information of all nodes in the CDN network, including CDN edge nodes and MEC-CDN nodes (including CDN content center nodes and MEC-CDN service nodes), so that the MEC-CDN nodes can also be found by a management server through the CDN.

As shown in fig. 3, the MEP, as an APP running on the MEC-CDN content source node, includes functions such as content delivery, content storage, and content processing, where the content storage function and the content processing function may be implemented according to the existing CDN technology. For an MEC-CDN content source node, the content delivery function of the CDN mainly makes a policy, and for an MEC-CDN service node, the content delivery function of the CDN mainly determines whether to update the configuration of the source address through RTT (Round-Trip Time) test, and configures the source address locally according to the source address configuration policy. As a bearing platform of the MEC-CDN APP, the MEP realizes the MEC interconnection communication function and mainly realizes information interaction with the MEP of other MEC-CDN nodes and the APP on the MEP.

As shown in fig. 4, the method for configuring a source address provided in the embodiment of the present disclosure includes the following steps:

and step 11, receiving a source address configuration message sent by the MEC-CDN content source node.

In this step, when the MEC-CDN content source node meets the preset condition, start back source address configuration, and send a source address configuration message back to the MEC-CDN service node. The condition that the preset condition is met means that when the content of the MEC-CDN content source node is processed and meets an external service requirement (for example, the content audit is passed), for example, in a live broadcast scene of a venue, the MEC-CDN content source node may start back to source address configuration if media content to be live is present.

And step 12, obtaining a source return address configuration strategy carried in the source return address configuration message.

The back source address configuration policy at least comprises a back source address to be configured, and the back source address to be configured is a private network address of the MEC-CDN content source node.

Step 13, if it is determined to start the source address configuration, performing round trip time RTT test with the MEC-CDN content source node to obtain a first RTT, and performing RTT test with a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT.

In this step, when it is determined that the source return address configuration is started, it is determined whether the current source return address configuration needs to be changed or not through an RTT test. And the MEC-CDN service node performs a first RTT test with the MEC-CDN content source node to obtain a first RTT, and performs a second RTT test with a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT. The RTT test is to send and receive test data packets through the MEC-CDN service node, and calculate the round trip time according to the timestamp in the test data packets, so as to obtain the source return time delay of the two MEC-CDN nodes. RTT is the reception time of the test packet — the echo time of the Timestamp (Timestamp) option in the packet, which is the transmission time of the test packet.

And 14, if the configuration of the source return address is determined to be changed according to at least the first RTT and the second RTT, configuring the first source return address as the source return address to be configured.

In this step, if it is determined through RTT test that the current configuration of the back source address needs to be changed, the first configuration of the back source address is updated to the back source address to be configured (i.e., the private network address of the MEC-CDN content source node) locally at the MEC-CDN service node.

The method for configuring the back-to-source address provided by the embodiment of the present disclosure receives a back-to-source address configuration message sent by an MEC-CDN content source node, and obtains a back-to-source address configuration policy carried in the back-to-source address configuration message, where the back-to-source address configuration policy at least includes a back-to-source address to be configured, and the back-to-source address to be configured is a private network address of the MEC-CDN content source node; if the starting source return address configuration is determined, performing Round Trip Time (RTT) test on the MEC-CDN content source node to obtain a first RTT, and performing RTT test on a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT; if the configuration of the source return address is determined to be changed at least according to the first RTT and the second RTT, configuring the first source return address as the source return address to be configured; in the embodiment of the disclosure, the candidate MEC-CDN service node performs the preferable judgment of the back source path in a mode of actively pushing the back source address configuration strategy, and the configured back source address can directly point to the MEC-CDN content source node, so that the back source path is shortened, and the back source accuracy is improved; in a live broadcast scene of a venue, when a service is performed for a user outside the venue, the return source address is configured to be a private network address of the MEC-CDN content source node, so that the user outside the venue can obtain live broadcast media content with high interactivity in the venue in real time, bandwidth consumption required by public network transmission is saved, and transmission delay is reduced.

In order to further improve the reliability of the source returning, the public network address of the CDN edge node to which the MEC-CDN service node belongs is still reserved when the source returning address configuration is performed, and is used as the second source returning address, so that when the source returning fails according to the first source returning address, the second source returning address can be used for the source returning.

Therefore, in some embodiments, further as shown in fig. 5, after configuring the first source-back address as the source-back address to be configured (i.e., step 14), the source-back address configuration method may further include the following steps:

and step 15, configuring the second back-source address as a public network address of a CDN edge node to which the MEC-CDN service node belongs.

And the second source returning address is used as a supplement of the first source returning address and is used when the first source returning address cannot normally return the source, and in order to ensure that the first source returning address is preferentially used, the use priority of the first source returning address is set to be higher than that of the second source returning address.

In some embodiments, the determining a modified return source address configuration based on at least the first RTT and the second RTT (i.e., step 14) includes: and if the first RTT is less than the second RTT, determining to change the configuration of the source address. That is to say, when the source return delay between the MEC-CDN service node and the MEC-CDN content source node is smaller than the source return delay between the MEC-CDN service node and the CDN edge node, the current source return address configuration is changed, that is, the private network address of the MEC-CDN content source node is used as the first source return address.

In some embodiments, the source-back address configuration policy may further include a restriction parameter, and the restriction parameter may serve as auxiliary configuration information for the source-back address configuration. Limiting parameters include, but are not limited to, one or more of the following: minimum time delay, required software and hardware resources (such as the number or resource occupation ratio of the required GPUs, and the size of the storage space), available Service information, required network resource information (such as minimum bandwidth and network jitter range), Qos index (Quality of Service), required Service information (including Service type, Service identifier, Service coverage, Service Quality requirement), content information (content identifier), and load status.

Correspondingly, as shown in fig. 6, after performing round trip time RTT test with the MEC-CDN content source node and RTT test with the CDN edge node to which the MEC-CDN service node belongs (i.e., step 13), before configuring the first loopback address as the loopback source address to be configured (i.e., step 14), the method further includes the following steps:

and step 13', adjusting the processing performance parameters of the MEC-CDN service node according to the limiting parameters.

In this step, the processing performance parameter corresponding to the limiting parameter of the MEC-CDN service node is adjusted to the condition defined by the limiting parameter. For example, if the limiting parameter includes the required network resource information and the required service information, the MEC-CDN service node adjusts the network resource parameter according to the minimum bandwidth and the network jitter range defined by the limiting parameter, and adjusts the service type, the service identifier, the service range, and the service quality of the node to the conditions defined by the limiting parameter. It should be noted that the MEC-CDN service node may apply for network resources, computing resources, and storage resources from the MEC management server according to the service quality requirement and the network resource information in the limited parameter, so as to meet the requirement specified by the configuration policy.

Currently, changing the configuration of the back-source address is often to select a new back-source address by the CDN edge node part, or to select a new back-source path for the user terminal, but limited by the capability of the service CDN, the back-source address still provides the traditional video stream and limited bandwidth. According to the embodiment of the disclosure, the limitation parameter is added in the back-source address configuration strategy, and the processing performance of the MEC-CDN service node is adjusted according to the limitation parameter, so that the MEC-CDN service node can be matched with the content of the media stream.

In case the source return address configuration policy includes a restriction parameter, said determining to change the source return address configuration according to at least the first RTT and the second RTT (i.e. step 14), comprising the steps of: and if the first RTT is less than the second RTT and the processing performance parameter adjusted by the MEC-CDN service node reaches the condition limited by the limiting parameter, determining to change the configuration of the source address. That is to say, under the condition that the source return address configuration policy includes the limiting parameter, after adjusting the processing performance of the MEC-CDN service node according to the limiting parameter, the MEC-CDN service node performs comprehensive judgment according to whether the performance requirement defined by the limiting parameter is met, and further performs comprehensive judgment in combination with the TTL test result and the judgment result of whether the processing performance parameter meets the standard, so as to determine whether the current source return address configuration needs to be modified. It should be noted that the value of the limitation parameter field in the source-back address configuration message may be set to "NULL", that is, the source-back address configuration policy must include the source-back address to be configured, and optionally the limitation parameter. In the case that the source-back address configuration policy does not include the restriction parameter, the determination result of whether to modify the source-back address configuration depends on the RTT test result.

In some embodiments, in the case that the source-back address configuration policy includes a restriction parameter, the source-back address configuration method further includes the steps of: and if the configuration of the source address is determined not to be changed according to the first RTT, the second RTT and the limiting parameter, or the configuration of the source address is determined not to be changed according to the first RTT and the second RTT, configuring the second source address as the source address to be configured, wherein the use priority of the first source address is higher than that of the second source address.

In some embodiments, in a case that the source address configuration policy includes a restriction parameter, the determining not to change the source address configuration according to the first RTT, the second RTT, and the restriction parameter includes: and if the first RTT is greater than or equal to the second RTT and/or the processing performance parameter adjusted by the MEC-CDN service node does not reach the limiting parameter, determining not to change the configuration of the source address. That is to say, the source return delay between the MEC-CDN service node and the MEC-CDN content source node is smaller than the source return delay between the MEC-CDN service node and the CDN edge node, and/or when the processing performance parameter of the MEC-CDN service node is adjusted and still does not meet the requirement, the current source return address configuration is not changed, and the public network address of the CDN edge node is still used as the first source return address.

In some embodiments, in a case that the source address configuration policy does not include a restriction parameter, the determining not to change the source address configuration according to the first RTT and the second RTT includes: and if the first RTT is larger than or equal to the second RTT, determining not to change the configuration of the source address. That is to say, when the source return delay between the MEC-CDN service node and the MEC-CDN content source node is greater than or equal to the source return delay between the MEC-CDN service node and the CDN edge node, the current source return address configuration is not changed, and the public network address of the CDN edge node is still used as the first source return address.

It should be noted that, under the condition that the back-source address configuration policy includes the limitation parameter, the test data packet generated by the MEC-CDN service node may include one or a combination of several of the requested service identifier, the service type, and the content identifier, so that it may be determined, through the RTT test, whether the corresponding MEC-CDN node supports the service defined by the limitation parameter and can provide the specified bandwidth and delay. If a returned test data packet cannot be received from the MEC-CDN content source node or the MEC-CDN service node (for example, an error response is received), or if the response time for receiving the test data packet is overtime, it indicates that the corresponding MEC-CDN content source node or the MEC-CDN service node cannot provide a specified service or the service capability reaches a limit, that is, the corresponding back-to-source service cannot be provided, it is determined that the back-to-source address configuration is not changed, that is, the default first back-to-source address (that is, the public network address of the CDN edge node) is maintained.

It should be noted that, under the condition that the source-return address configuration policy includes the limitation parameter and the limitation parameter includes the minimum delay, if the first RTT is less than the second RTT and the second RTT is less than the minimum delay, it is determined to change the source-return address configuration. And if any one of the first RTT and the second RTT is larger than the minimum time delay, determining that the configuration of the source return address is not changed, and keeping the current default source return address in the configuration of the first source return address.

In some embodiments, the source-back address policy may further include mode information indicating a source-back address configuration start opportunity, and the determining to start the source-back address configuration (i.e., step 13) includes: and determining to start the configuration of the source address according to the mode information. The mode information may be first mode information or second mode information, and when the mode information is the first mode information, the determining to start the configuration of the source address according to the mode information includes: and if receiving a back-to-source address configuration message sent by the MEC-CDN content source node, determining to start back-to-source address configuration. That is, in the first mode, the back-to-source address configuration starting time is when a back-to-source address configuration message sent by the MEC-CDN content source node is received, and at this time, the back-to-source address configuration is started immediately.

When the mode information is the second mode information, the determining to start the configuration of the source address according to the mode information includes: and if the preset time length is passed after a source return address configuration message sent by the MEC-CDN content source node is received, or the failure frequency of acquiring the requested content from the corresponding CDN node according to the locally configured first source return address reaches the preset frequency, determining to start source return address configuration. That is, in the second mode, the back-to-source address configuration is not started immediately, but is started after the back-to-source address configuration policy is issued for a period of time, or, after the back-to-source address configuration policy, the MEC-CDN service node is started when the back-to-source address (i.e., the public network address of the CDN edge node) according to the default configuration fails a large number of times.

It should be noted that the mode information may be carried by the MEC-CDN content source node in the source return address configuration policy and delivered to each MEC-CDN service node, or may be set by each MEC-CDN service node during initialization, for example, the MEC-CDN service node sets the mode type, and sets the specific condition for starting the source return address configuration in the second mode. In the embodiment of the present disclosure, the description is given by taking an example in which the mode information is notified to the corresponding MEC-CDN service node in a manner of sending back the source address configuration policy.

In order to ensure that the source return path is always the optimal path and whether the accuracy of the source return address configuration judgment is modified or not, after the source return address configuration strategy is received, whether the source return address configuration is changed or not can be periodically judged, namely, the RTT test is periodically carried out. Accordingly, in some embodiments, the performing round trip time RTT testing with the MEC-CDN content source node includes: and performing Round Trip Time (RTT) test with the MEC-CDN content source node according to a preset period. Performing RTT test on the CDN edge node to which the MEC-CDN service node belongs, wherein the RTT test comprises the following steps: and performing RTT test with the CDN edge node to which the MEC-CDN service node belongs according to the period. By periodically performing RTT test, the configuration of the source returning address can be performed based on the real-time information of the MEC-CDN node, and the source returning success rate is improved.

When the MEC-CDN service node receives a content request message sent by a user terminal, judging whether the characteristics (such as terminal type) of the user terminal and the requested service characteristics (such as service APP type) are matched with the service provided by the MEC-CDN node corresponding to the first return source address, if so, returning to the source according to the first return source address, and acquiring the requested content (media stream data) from the corresponding MEC-CDN node.

An embodiment of the present disclosure further provides a source address configuration method, as shown in fig. 7, the method includes the following steps:

and step 21, when the preset condition is met, sending a node discovery request message carrying the screening condition to the management equipment.

The private network address of the MEC-CDN content origin node serving a given area is set as the content acquisition address of the MEC-CDN in advance. In this step, when discovering that the locally-existing content which is processed and can be served externally (for example, the content auditing default is passed), the MEC-CDN content source node sends a node discovery request message carrying a screening condition to the management device to start a node discovery process. For example, in a live broadcast scene in a venue, the MEC-CDN content source node may initiate node discovery and source address configuration if there is media content to be live.

And step 22, receiving a screening result returned by the management equipment, wherein the screening result comprises MEC-CDN service node information and is obtained by screening the MEC-CDN service node information from the managed MEC-CDN node by the management equipment according to the screening condition.

The screening result may be a list of MEC-CDN service nodes that satisfy the screening condition.

And step 23, sending a back-source address configuration message carrying a back-source address configuration policy to the MEC-CDN service node corresponding to the screening result, where the back-source address configuration policy at least includes a back-source address to be configured, and the back-source address to be configured is a private network address of the MEC-CDN content source node.

In this step, the source address configuration message may be sent in a broadcast manner, or in a point-to-point manner. In the case of peer-to-peer transmission, if the MEC-CDN content source node has established a communication connection with the MEC-CDN service node, a source address configuration message may be directly sent back to the MEC-CDN service node. If the MEC-CD content source node does not establish communication connection with the MEC-CDN service node, the CDN management server/SLB or the MEC management server can forward the source address configuration message back to the MEC-CDN service node by sending the source address configuration message back to the CDN management server/SLB or the MEC management server.

According to the configuration method of the source address provided by the embodiment of the disclosure, when a preset condition is met, a node discovery request message carrying a screening condition is sent to a management device; receiving a screening result returned by the management equipment, wherein the screening result comprises MEC-CDN service node information and is obtained by screening from the managed MEC-CDN node by the management equipment according to a screening condition; sending a back-source address configuration message carrying a back-source address configuration strategy to an MEC-CDN service node corresponding to the screening result, wherein the back-source address configuration strategy at least comprises a back-source address to be configured, and the back-source address to be configured is a private network address of the MEC-CDN content source node; by setting screening conditions, MEC-CDN service nodes meeting requirements can be screened out, and a back-source address configuration strategy is issued to the MEC-CDN service nodes meeting the requirements, so that the back-source address configuration strategy is accurately issued, and bandwidth resources are saved; the screening conditions can be set according to requirements, the application range is wide, and the flexibility is strong; the node of the MEC-CDN content source in the embodiment of the disclosure can accurately find a proper MEC-CDN service node, and a private network address of the MEC-CDN content source node is issued to the proper MEC-CDN service node in a mode of actively pushing a source returning address configuration strategy, so that the MEC-CDN service nodes can configure the private network address of the MEC-CDN content source node as a first source returning address, a source returning path can be shortened, and the source returning accuracy is improved; in a live broadcast scene of a venue, when a service is carried out for users outside the venue, the source return address is configured to be a private network address of an MEC-CDN content source node, so that the users outside the venue can obtain live broadcast media content with high interactivity in the venue in real time, bandwidth consumption required by public network transmission is saved, and time delay can be reduced by distributing media data streams generated in real time through the private network.

In some embodiments, the screening conditions may include, but are not limited to, one or any combination of the following: the IP addresses belong to the same network segment, have the same MEC identity, belong to the same geographical area or service area, have the same service capabilities, belong to the same content provider, belong to the same service provider.

In some embodiments, the management device may be a CDN management server or a MEC management server.

As shown in fig. 2, the MEC-CDN node discovery process according to the embodiment of the present disclosure has 2 implementation manners, one implementation manner is implemented based on a CDN management server, and the other implementation manner is implemented based on an MEC management server. That is, the MEC-CDN node discovery process may be implemented by using an MEC system interconnection function (supported by an MEC management system), for example, the MEPM system provides home MEP information, the MEP needs to provide discovery capabilities of other MEPs, and communication capabilities between the MEPs and between the MEC-CDN APPs. The MEC-CDN node discovery process may also be implemented by a CDN management server/SLB, for example, relying on content routing system support or CDN operation and maintenance management system support. When an MEC-CDN content source node may select one of a CDN management server and an MEC management server as needed to perform peripheral node discovery, in the embodiment of the present disclosure, an MEC management server is preferentially selected to implement node discovery.

The process of discovering the MEC-CDN service node based on the MEC management server is as follows: the MEC-CDN content source node requests other MEP resource discovery (discover) from an MEC platform (MEP) where an APP is located through an MEC-CDN Application (APP), and provides a filter condition (filter). E.g. whether belonging to the same MEC-CDN APP identity, whether belonging to the same content provider Identity (ID), whether belonging to the same coverage (e.g. same physical geographical identity, same cell identity, same designated area identity (TAI)). The MEP interacts with the MEC management server to acquire the MEP identification and address which accord with the filter condition so as to carry out node interconnection subsequently.

The process of realizing MEC-CDN node discovery based on the CDN management server is as follows: and the MEC-CDN content source node acquires the IP address lists of all MEC-CDN nodes governed by the CDN management server/SLB through interacting with the DN management server/SLB. It should be noted that after the MEC-CDN node comes online, the MEC-CDN node is registered in the CDN management server/SLB, so that the CDN management server/SLB can discover and screen the MEC-CDN node.

In order to clearly illustrate the technical solutions of the embodiments of the present disclosure, the following description is made by using two specific examples with reference to fig. 8 and 9, respectively.

Fig. 8a shows an example of the source address configuration in the first mode, in which the source address configuration method includes the following steps:

step 1, starting an MEC-CDN node discovery process.

In this step, when the MEC-CDN content source node has available content, an MEC-CDN node discovery procedure is started. The MEC-CDN service node information can be inquired through an MEC system interconnection function in the MEP or through a CDN management server. The MEC-CDN node discovery process may be accompanied by a screening condition (e.g., IP addresses belong to the same network segment, have the same MEC identifier, belong to the same geographic area or service area, have the same service capability, belong to the same content provider, belong to the same service provider), and may finally screen out information (i.e., screening results) of one or more MEC-CDN service nodes.

And 2, the MEC-CDN content source node sends a source address configuration message back to the screened MEC-CDN-1 node and MEC-CDN-2 node and issues a source address configuration strategy.

As shown in fig. 8b, the source-back address configuration policy includes a source-back address to be configured and a restriction parameter. The back source address to be configured is the private network IP address of the MEC-CDN content source node (10.42.140.120). The limiting parameters may include: minimum time delay, minimum bandwidth, CPU occupancy rate, network jitter range and packet loss rate.

In scenario 1 of an MEC-CDN-1 service node, the method includes the following steps:

and 3a, carrying out RTT test by the MEC-CDN-1 service node.

In this step, the MEC-CDN-1 service node receives the back-source address configuration message, records the back-source address to be configured in the back-source address configuration policy, and starts the RTT test if the MEC-CDN-1 service node determines to immediately start back-source address configuration (i.e., the first mode). And the content distribution application of the MEC-CDN-1 service node creates a test data packet, wherein the test data packet comprises a content identifier, a service identifier and a service type of the simulation user request. And the MEC-CDN-1 service node respectively sends the test data packet to an MEC-CDN content source node and a superior CDN edge node to which the MEC-CDN content source node belongs, respectively receives the returned test data packet, and respectively records a first RTT and a second RTT.

And 4a, the MEC-CDN-1 service node adjusts the processing performance parameters of the MEC-CDN-1 service node according to the limiting parameters.

And 5a, the MEC-CDN-1 service node comprehensively judges according to the RTT test result and the adjustment result of the processing performance parameter, and modifies the configuration of the first return source address.

In this step, the MEC-CDN-1 service node determines that the first RTT is less than the second RTT and that the adjusted processing performance parameter reaches the limiting parameter, which indicates that the current source return address configuration needs to be modified, that is, the first source return address configuration is 10.42.140.120.

And 6a, the MEC-CDN-1 service node receives a content request message sent by the user terminal, and acquires media stream data from the MEC-CDN content source node according to the first return source address.

In scenario 2 of an MEC-CDN-2 service node, the following steps are included:

and 3b, carrying out RTT test by the MEC-CDN-2 service node.

And 4b, the MEC-CDN-2 service node adjusts the processing performance parameters of the MEC-CDN-2 service node according to the limiting parameters.

And 5b, the MEC-CDN-2 service node comprehensively judges according to the RTT test result and the adjustment result of the processing performance parameter without modifying the configuration of the first return source address.

In this step, the MEC-CDN-1 service node determines that the first RTT is greater than the second RTT, which indicates that the current source return address configuration does not need to be modified, that is, the first source return address configuration is still reserved as the public network address of the CDN edge node.

And 6b, the MEC-CDN-2 service node receives a content request message sent by the user terminal, and acquires media stream data from the CDN edge node according to the first return source address.

The MEC-CDN-1 service node and the MEC-CDN-2 service node can perform RTT test periodically in the follow-up process to prevent the RTT test result from being influenced by the changes of indexes such as bandwidth and network speed caused by the change of the network state, and correspondingly, the configuration of the first return source address can be dynamically modified in the follow-up process based on the re-performed RTT test result.

Fig. 9 shows an example of the back-source address configuration in the second mode, and the example shown in fig. 9 differs from the example shown in fig. 8 in that: after step 2 is executed, the MEC-CDN-1 service node and the MEC-CDN-2 service node may first respectively execute step 6a and step 6b, after a preset source address configuration start condition is satisfied, in scene 1, the MEC-CDN-1 service node executes step 3a-5a, and in scene 2, the MEC-CDN-2 service node executes step 3b-5 b.

In a scene 1 of an MEC-CDN-1 service node and a scene 2 of an MEC-CDN-2 service node, the MEC-CDN-1 service node and the MEC-CDN-2 service node respectively record the times of failure of obtaining requested content from corresponding nodes according to a first source return address, and when the identified times reach a preset value (the upper limit of the times of source return failure allowed by service), the judgment of whether the source return address configuration is modified is started, namely, the steps 3a to 5a and the steps 3b to 5b are respectively executed.

In the embodiment of the present disclosure, besides having the traditional CDN application function (content processing, media storage), the MEC-CDN node may further implement the following function in the content delivery management function in the MEC-CDN application function: (1) discovering other MEC-CDN nodes; (2) configuring a configuration strategy of a source address; (3) interact with other MEC-CDN nodes to exchange node information.

In the embodiment of the disclosure, when the content is available, the MEC-CDN content source node starts an MEC-CDN node discovery request with a screening condition, and pushes a source address configuration policy back to the MEC-CDN service node that meets the screening condition. The back-source address configuration strategy comprises a private network address of the MEC-CDN content source node and a limiting parameter. After receiving the source return address configuration strategy, the MEC-CDN service node initiates an RTT test to the MEC-CDN content source node and the higher-level CDN edge node respectively for source return delay comparison when the time for starting the source return address configuration arrives, and adjusts its node resource (i.e., processing performance parameter) according to the limiting parameter. And the MEC-CDN service node comprehensively judges whether the configuration of the return source address needs to be modified or not according to the return source delay comparison result and the resource adjustment result, and if so, the private network address of the MEC-CDN content source node is used as the return source address which is preferentially used.

Based on the same technical concept, an embodiment of the present disclosure further provides a source return address configuration apparatus, as shown in fig. 10, the source return address configuration apparatus includes: the device comprises a receiving module 101, an obtaining module 102, a testing module 103 and a configuration module 104, wherein the receiving module 101 is configured to receive a source address configuration message sent by a MEC-CDN content source node of a multi-access/mobile edge computing content delivery network.

The obtaining module 102 is configured to obtain a source return address configuration policy carried in the MEC-CDN, where the source return address configuration policy at least includes a source return address to be configured, and the source return address to be configured is a private network address of the MEC-CDN content source node.

The test module 103 is configured to, when it is determined to start the source address configuration, perform round trip time RTT test with the MEC-CDN content source node to obtain a first RTT, and perform RTT test with a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT.

The configuration module 104 is configured to configure the first return source address as the return source address to be configured when determining to change the return source address configuration according to at least the first RTT and the second RTT.

In some embodiments, the configuration module 104 is further configured to, after configuring the first back source address as the back source address to be configured, configure a second back source address as a public network address of a CDN edge node to which the MEC-CDN service node belongs, where a priority of use of the first back source address is higher than a priority of use of the second back source address.

In some embodiments, the configuration module 104 is configured to determine to change the source address configuration if the first RTT is less than the second RTT.

In some embodiments, the source return address configuration policy further includes a limiting parameter, as shown in fig. 11, the source return address configuration apparatus further includes a parameter adjusting module 105, and the parameter adjusting module 105 is configured to, before the configuration module 104 configures the first source return address as the source return address to be configured, adjust a processing performance parameter of the MEC-CDN service node according to the limiting parameter.

The configuration module 104 is configured to determine to change the source address configuration when the first RTT is less than the second RTT and the adjusted processing performance parameter of the MEC-CDN service node reaches the limiting parameter.

In some embodiments, the configuration module 104 is further configured to configure a second source return address as the source return address to be configured when it is determined that the source return address configuration is not changed according to the first RTT, the second RTT and the limiting parameter, or it is determined that the source return address configuration is not changed according to the first RTT and the second RTT, where a priority level of use of the first source return address is higher than a priority level of use of the second source return address.

In some embodiments, the configuration module 104 is configured to determine not to change the source address configuration when the first RTT is greater than or equal to the second RTT, and/or the adjusted processing performance parameter of the MEC-CDN service node does not reach the limiting parameter; or when the first RTT is greater than or equal to the second RTT, determining not to change the configuration of the source address.

In some embodiments, the source address configuration policy further includes mode information used for indicating a source address configuration start opportunity, where the mode information is first mode information or second mode information. The test module 103 is configured to, when the mode information is first mode information, determine to start a source address configuration if a source address configuration message sent by an MEC-CDN content source node is received; when the mode information is second mode information, if a preset time length passes after a source return address configuration message sent by the MEC-CDN content source node is received, or the number of times of failure of obtaining the requested content from the corresponding CDN node according to a locally configured first source return address reaches a preset number of times, determining to start source return address configuration.

In some embodiments, the test module 103 is configured to perform round trip time RTT test with the MEC-CDN content source node according to a preset period; and performing Round Trip Time (RTT) test with a CDN edge node to which the MEC-CDN service node belongs according to the period.

Based on the same technical concept, an embodiment of the present disclosure further provides a source address configuration apparatus, as shown in fig. 12, the source address configuration apparatus includes a sending module 201 and a receiving module 202, where the sending module 201 is configured to send a node discovery request message carrying a screening condition to a management device when a preset condition is met.

The receiving module 202 is configured to receive a filtering result returned by the management device, where the filtering result includes information of a MEC-CDN service node of a multi-access/mobile edge computing content delivery network, and is obtained by the management device through filtering from the managed MEC-CDN node according to the filtering condition.

The sending module 201 is further configured to send a source return address configuration message carrying a source return address configuration policy to the MEC-CDN service node corresponding to the screening result, where the source return address configuration policy at least includes a source return address to be configured, and the source return address to be configured is a private network address of the MEC-CDN content source node.

An embodiment of the present disclosure further provides a computer device, including: one or more processors and storage; the storage device stores one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the source address configuration method provided in the foregoing embodiments.

The embodiments of the present disclosure also provide a computer readable medium, on which a computer program is stored, where the computer program, when executed, implements the source address configuration method provided in the foregoing embodiments.

It will be understood by those of ordinary skill in the art that all or some of the steps of the methods disclosed above, functional modules/units in the apparatus, may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.

Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purposes of limitation. In some instances, features, characteristics and/or elements described in connection with a particular embodiment may be used alone or in combination with features, characteristics and/or elements described in connection with other embodiments, unless expressly stated otherwise, as would be apparent to one skilled in the art. It will, therefore, be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.

Claims

1. A method for configuring a source-back address, the method comprising:

a multi-access/mobile edge computing content delivery network MEC-CDN service node receives a back source address configuration message sent by a multi-access/mobile edge computing content delivery network MEC-CDN content source node, and obtains a back source address configuration strategy carried in the back source address configuration message, wherein the back source address configuration strategy at least comprises a back source address to be configured, and the back source address to be configured is a private network address of the MEC-CDN content source node;

if the MEC-CDN service node determines to start the configuration of the source address, performing Round Trip Time (RTT) test on the MEC-CDN content source node to obtain a first RTT, and performing RTT test on a CDN edge node to which the MEC-CDN service node belongs to obtain a second RTT;

and if the MEC-CDN service node determines to change the configuration of the source return address at least according to the first RTT and the second RTT, configuring the first source return address as the source return address to be configured.

2. The method of claim 1, wherein after configuring the first fallback address as the fallback address to be configured, the method further comprises:

3. The method of claim 1, wherein said determining to change a source address configuration based on at least the first RTT and the second RTT comprises: and if the first RTT is less than the second RTT, determining to change the configuration of the source address.

4. The method of claim 3, wherein the back-source address configuration policy further includes a restriction parameter, and further includes, after performing round trip time RTT test with the MEC-CDN content source node and RTT test with a CDN edge node to which the MEC-CDN service node belongs, before configuring a first back-source address as the back-source address to be configured: adjusting the processing performance parameters of the MEC-CDN service node according to the limiting parameters;

5. The method of claim 4, further comprising:

6. The method of claim 5, wherein the determining not to change a source address configuration based on the first RTT, the second RTT, and the restriction parameter comprises: if the first RTT is greater than or equal to the second RTT, and/or the processing performance parameter adjusted by the MEC-CDN service node does not reach the limiting parameter, determining not to change the configuration of the source address; alternatively, the first and second electrodes may be,

7. The method of claim 1, wherein the source address policy further includes mode information for indicating a source address configuration start opportunity, and the mode information is first mode information or second mode information; the determining to initiate a source address configuration includes: determining to start the configuration of the source address according to the mode information;

when the mode information is first mode information, the determining to start back to source address configuration according to the mode information includes: if a source returning address configuration message sent by an MEC-CDN content source node is received, determining to start source returning address configuration;

8. The method of any one of claims 1-7, wherein the performing Round Trip Time (RTT) tests with the MEC-CDN content origin node comprises: performing Round Trip Time (RTT) test with the MEC-CDN content source node according to a preset period;

9. A method for configuring a source-back address, the method comprising:

when the preset conditions are met, the MEC-CDN content source node of the multi-access/mobile edge computing content delivery network sends a node discovery request message carrying the screening conditions to the management equipment;

the MEC-CDN content source node receives a screening result returned by the management equipment, wherein the screening result comprises information of a MEC-CDN service node of a multi-access/mobile edge computing content delivery network and is obtained by screening the MEC-CDN service node governed by the management equipment according to the screening condition;

and the MEC-CDN content source node sends a source returning address configuration message carrying a source returning address configuration strategy to an MEC-CDN service node corresponding to the screening result, wherein the source returning address configuration strategy at least comprises a source returning address to be configured, and the source returning address to be configured is a private network address of the MEC-CDN content source node.

10. The method of claim 9, wherein the screening conditions comprise one or any combination of: the IP addresses belong to the same network segment, have the same MEC identity, belong to the same geographical area or service area, have the same service capabilities, belong to the same content provider, belong to the same service provider.

11. The method of claim 9 or 10, wherein the management device is a CDN management server or an MEC management server.

12. A back-source address configuration device, wherein the back-source address configuration device is a multi-access/mobile edge computing content delivery network MEC-CDN service node, and includes: the system comprises a receiving module, an obtaining module, a testing module and a configuration module, wherein the receiving module is used for receiving a back source address configuration message sent by a content source node of a multi-access/mobile edge computing content delivery network MEC-CDN;

13. A back-source address configuration device is characterized in that the back-source address configuration device is a multi-access/mobile edge computing content delivery network (MEC-CDN) content source node and comprises a sending module and a receiving module, wherein the sending module is used for sending a node discovery request message carrying a screening condition to a management device when a preset condition is met;

14. A computer device, comprising:

one or more processors;

a storage device having one or more programs stored thereon;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of source address configuration as recited in any of claims 1-11.

15. A computer-readable medium, on which a computer program is stored, wherein said program, when executed, implements the source-back address configuration method according to any of claims 1-11.