CN116962395A - Cloud node determining method, device, equipment and computer readable storage medium - Google Patents
Cloud node determining method, device, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN116962395A CN116962395A CN202210412623.4A CN202210412623A CN116962395A CN 116962395 A CN116962395 A CN 116962395A CN 202210412623 A CN202210412623 A CN 202210412623A CN 116962395 A CN116962395 A CN 116962395A
- Authority
- CN
- China
- Prior art keywords
- cloud
- edge cloud
- request
- accessed
- delay
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 84
- 230000004044 response Effects 0.000 claims abstract description 20
- 230000002159 abnormal effect Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000008901 benefit Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 3
- 238000012512 characterization method Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 238000012937 correction Methods 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000003631 expected effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses a cloud node determining method, a cloud node determining device, cloud node determining equipment and a computer readable storage medium, wherein the cloud node determining method comprises the following steps: acquiring a resource request sent by a cloud computing application to an edge cloud to be accessed; determining a first request time delay based on the request time corresponding to the resource request and the response time corresponding to the resource request; acquiring a second request time delay corresponding to the candidate edge cloud outside the edge cloud to be accessed; and determining a target edge cloud finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and a time delay threshold. The target edge cloud with normal time delay can be determined through the first request time delay of the edge cloud to be accessed and the second request time delay of the candidate edge cloud, corresponding resources are provided through the target edge cloud with normal time delay, and normal operation of cloud computing application is guaranteed.
Description
Technical Field
The application relates to the technical field of cloud computing and big data, and relates to a cloud node determining method, device and equipment and a computer readable storage medium.
Background
With the advent of the fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) and the age of the internet of things and the gradual increase of cloud computing applications, the conventional cloud computing technology cannot meet the requirements of 'large connection, low time delay and large bandwidth' of a terminal side. With the advent of edge computing technology, cloud computing will necessarily develop to the next technical stage, expand the ability of cloud computing to the edge side nearest to the terminal, and realize the subsidence of cloud computing service through unified management and control of cloud edge end, for end-to-end cloud service, thereby generating the concept of edge cloud computing.
The edge cloud introduces more nodes while bringing lower time delay, so that the operation is faced with the fault problem brought by the edge cloud and more complex operation and maintenance work, when the edge cloud has local faults, service interruption or use time delay increase can be caused, the expected effect of the edge cloud can not be achieved, and the following problems can be caused: when the delay increases due to the failure, the core network and user plane functions (User Plane Function, UPF) cannot sense the failure, and traffic is led to edge clouds with higher delay before the failure is recovered; detecting and deactivating a user through N4 heartbeat can cause the whole edge cloud under the UPF to be unavailable, so that influence is large; in addition, the heartbeat detection cannot sense the increase of local time delay; recovery failures require time to troubleshoot and the recovery process can also cause traffic disruption, affecting services in service level agreements (Service Level Agreement, SLA).
Disclosure of Invention
In view of this, embodiments of the present application provide a cloud node determining method, apparatus, device, and computer readable storage medium.
The technical scheme of the embodiment of the application is realized as follows:
the embodiment of the application provides a cloud node determining method, which comprises the following steps:
acquiring a resource request sent by a cloud computing application to an edge cloud to be accessed;
determining a first request time delay based on the request time corresponding to the resource request and the response time corresponding to the resource request;
acquiring a second request time delay corresponding to the candidate edge cloud outside the edge cloud to be accessed;
and determining a target edge cloud finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and a time delay threshold.
The embodiment of the application provides a cloud node determining device, which comprises:
the first acquisition module is used for acquiring a resource request sent by the cloud computing application to the edge cloud to be accessed;
the first determining module is used for determining a first request time delay based on the request time corresponding to the resource request and the response time corresponding to the resource request;
The second acquisition module is used for acquiring a second request time delay corresponding to the candidate edge cloud outside the edge cloud to be accessed;
and the second determining module is used for determining a target edge cloud finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and a time delay threshold value.
An embodiment of the present application provides a cloud computing device, including:
a processor; and
a memory for storing a computer program executable on the processor;
wherein the computer program, when executed by a processor, implements the above-described determination method.
Embodiments of the present application provide a computer-readable storage medium having stored therein computer-executable instructions configured to perform the above-described determination method.
The embodiment of the application provides a cloud node determining method, a cloud node determining device, cloud node determining equipment and a computer readable storage medium, wherein the cloud node determining method comprises the following steps: the cloud computing equipment acquires a resource request sent by a cloud computing application to an edge cloud to be accessed, wherein the resource request is used for running a corresponding functional program in the cloud computing application; then, acquiring a request time corresponding to the resource request and a response time corresponding to the resource request, and determining a first request time delay of the edge cloud to be accessed based on the request time and the response time; then, obtaining a second request time delay corresponding to the candidate edge cloud outside the access edge cloud from the cloud computing device or other cloud computing devices; finally, determining a target edge cloud with normal time delay finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and the time delay threshold value, so that the edge cloud with faults can be found out in time based on the first request time delay and the second request time delay, and the problem of untimely fault finding is avoided; meanwhile, the target edge cloud with normal time delay can be determined, the target edge cloud with normal time delay can be accessed by cloud computing application, the purpose that service is not interrupted is achieved, and the service level of the edge cloud is improved.
Drawings
In the drawings (which are not necessarily drawn to scale), like numerals may describe similar components in different views. The drawings illustrate generally, by way of example and not by way of limitation, various embodiments discussed herein.
Fig. 1 is a schematic diagram of a structural framework formed by a 5G network and an edge cloud system according to an embodiment of the present application;
fig. 2 is a schematic flow chart of an implementation of a cloud node determining method according to an embodiment of the present application;
fig. 3 is a schematic flow chart of another implementation of the cloud node determining method according to the embodiment of the present application;
FIG. 4 is a schematic flow chart of an implementation of determining a target edge cloud from a plurality of candidate edge clouds according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a deployment framework of an edge cloud selector according to an embodiment of the present application;
fig. 6 is a schematic diagram of a composition structure of a cloud node determining device according to an embodiment of the present application;
fig. 7 is a schematic diagram of a composition structure of a cloud computing device according to an embodiment of the present application.
Detailed Description
The present application will be further described in detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.
In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is to be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with one another without conflict.
In the following description, the terms "first", "second", "third" and the like are merely used to distinguish similar objects and do not represent a particular ordering of the objects, it being understood that the "first", "second", "third" may be interchanged with a particular order or sequence, as permitted, to enable embodiments of the application described herein to be practiced otherwise than as illustrated or described herein.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.
Edge clouds are cloud computing platforms built on top of an edge infrastructure based on the core of cloud computing technology and the capabilities of the edge computing. An elastic cloud platform with comprehensive capabilities of edge position calculation, network, storage, safety and the like is formed, and works such as network forwarding, storage, calculation, intelligent data analysis and the like are put on edge processing, so that response time delay is reduced, cloud pressure is lightened, bandwidth cost is reduced, and cloud services such as whole-network scheduling, calculation power distribution and the like are provided.
Fig. 1 is a schematic diagram of a structural framework formed by a 5G network and an edge cloud system according to an embodiment of the present application, where the system includes a 5G network 101 and an edge computing platform 102,5G network 101, which can provide connection services in multiple scenarios, and the edge computing platform 102 can utilize nodes at edge positions to complete data analysis tasks more timely. In practical applications, the 5G network 101 interfaces with the edge computing technology platform 102 through an interface, so as to efficiently provide computing, networking, storage, security, and other resources for the 5G network through the edge cloud computing technology platform 102.
Here, the user plane function is an important component of the third generation partnership project (3rd Generation Partnership Project,3GPP) 5G core network system architecture, and is mainly responsible for the routing and forwarding related functions of the 5G core network user plane data packet, and performs data packet processing and traffic aggregation for the edge cloud. N4, N6 and N9 represent detection methods.
Based on the problems existing in the related art, the embodiment of the application provides a cloud node determining method, and the method provided by the embodiment of the application can be realized through a computer program, and the computer program completes the cloud node determining method provided by the embodiment of the application when being executed. In some embodiments, the computer program may be executed on a processor in a cloud computing device. Fig. 2 is a flow chart of an implementation of a cloud node determining method according to an embodiment of the present application, where, as shown in fig. 2, the determining method includes:
Step S201, obtaining a resource request sent by a cloud computing application to an edge cloud to be accessed.
Here, the cloud computing application refers to an application that completes a corresponding data computing process by accessing cloud computing resources, and may be a financial application, an educational application, a traffic application, or the like. Because the cloud service has the advantages of calculating, utility calculating, balancing load, parallel calculating, network storing and the like, the operation efficiency of cloud computing application is improved, and great convenience is brought to the cloud computing application.
In the embodiment of the application, cloud computing equipment is deployed between a terminal where a cloud computing application is located and an edge cloud, and the cloud computing equipment is used for determining a target edge cloud with normal time delay from a plurality of edge clouds. The cloud computing application sends a resource request to the edge cloud to be accessed according to the configuration parameters, or the cloud computing application sends the resource request to the edge cloud to be accessed which is accessed historically according to the log. The cloud computing device is reached before the resource request reaches the edge cloud to be accessed, and then the cloud computing device forwards the resource request to the edge cloud to be accessed. In this way, when the cloud computing application sends a resource request to the edge cloud to be accessed, the cloud computing device can obtain the resource request.
Step S202, determining a first request delay based on a request time corresponding to the resource request and a response time corresponding to the resource request.
Here, the resource request carries a request time, where the request time characterizes a time when the cloud computing application sends the resource request, and the cloud computing device may obtain the request time in the resource request by parsing the resource request.
Correspondingly, after the to-be-accessed edge cloud receives the resource request, the to-be-accessed edge cloud can apply for related resources, such as storage resources, computing resources and the like, and after the to-be-accessed edge cloud applies for the resources from the to-be-accessed edge cloud, feedback information is sent to the terminal where the cloud computing application is located through the cloud computing device. The feedback information carries response time, and the response time is the response time corresponding to the resource request. Because the feedback information is sent to the terminal where the cloud computing application is located through the cloud computing equipment, the cloud computing equipment can acquire the feedback information in real time, and the cloud computing equipment acquires the response time carried in the feedback information through analyzing the feedback information.
In an embodiment of the present application, a time difference between the response time and the request time may be determined, and the time difference may be determined as the first request delay.
Step S203, obtaining a second request time delay corresponding to the candidate edge cloud except the edge cloud to be accessed.
Here, the candidate edge cloud is an edge cloud other than the edge cloud to be accessed in the cloud network. In actual implementation, the edge cloud to be accessed and the candidate edge cloud may share one cloud computing device, and the edge cloud to be accessed and the candidate edge cloud may also correspond to different cloud computing devices. The number of candidate edge clouds may be multiple, and for example, the number of candidate edge clouds may be 10, 11, or 12. Based on the above, taking the number of candidate edge clouds as 10 as an example, when the edge clouds to be accessed and the candidate edge clouds share one cloud computing device, the method is equivalent to that the edge clouds to be accessed and the 10 candidate edge clouds share one cloud computing device; while, when the edge cloud to be accessed and the candidate edge clouds correspond to different cloud computing devices, the edge cloud to be accessed and the 10 candidate edge clouds may correspond to 11 different cloud computing devices.
In the embodiment of the application, the obtaining of the second request delay corresponding to the candidate edge cloud includes the following two cases:
in case one, the edge cloud to be accessed and the candidate edge cloud share one cloud computing device.
In this case, the cloud computing device can determine not only the first request delay corresponding to the edge cloud to be accessed through the above-described step S201 and step S202, but also the second request delay of each candidate edge cloud based on a similar method. Based on the first request time delay and the second request time delay are contained in the cloud computing equipment, the second request time delay corresponding to the candidate edge cloud can be obtained through the obtaining instruction.
And in the second case, the edge cloud to be accessed and the candidate edge cloud correspond to different cloud computing devices.
In this case, the cloud computing device corresponding to the edge cloud to be accessed can determine the first request delay of the edge cloud to be accessed, and similarly, the other cloud computing devices corresponding to the candidate edge cloud can determine the second request delay of the candidate edge cloud. In one aspect, after determining the request delay, each cloud computing device may broadcast over the whole network, so that information in each cloud computing device is updated synchronously. Based on the above, after broadcasting, the cloud computing device corresponding to the edge cloud to be accessed includes the first request delay of the edge cloud to be accessed and the second request delay of the candidate edge, and in this case, similar to the above-mentioned case one, the cloud computing device corresponding to the edge cloud to be accessed may acquire the second request delay corresponding to the candidate edge cloud through the acquiring instruction. On the other hand, if the cloud computing device corresponding to the edge cloud to be accessed does not include the second request delay of the candidate edge, then the cloud computing device corresponding to the edge cloud to be accessed may send delay acquisition instructions to other cloud computing devices corresponding to the candidate edge clouds, respectively, so as to obtain the second request delay of the candidate edge clouds.
Step S204, determining a target edge cloud finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and the time delay threshold.
In the embodiment of the application, whether the first request time delay meets the time delay condition can be judged based on the time delay threshold, if the first request time delay meets the time delay condition, the edge cloud to be accessed is characterized as the edge cloud with normal time delay, and the edge cloud to be accessed is determined as the cloud computing application to finally access the target edge cloud; and if the first request time delay does not meet the experimental condition, representing that the edge cloud to be accessed is an edge cloud with abnormal time delay, namely, the edge cloud to be accessed fails, determining a target edge cloud with normal time delay from the candidate edge clouds based on the time delay threshold and the second request time delay, so that the cloud computing application accesses the target edge cloud with normal time delay.
The embodiment of the application provides a cloud node determining method, a cloud node determining device, cloud node determining equipment and a computer readable storage medium, wherein the cloud node determining method comprises the following steps: the cloud computing equipment acquires a resource request sent by a cloud computing application to an edge cloud to be accessed, wherein the resource request is used for running a corresponding functional program in the cloud computing application; then, acquiring a request time corresponding to the resource request and a response time corresponding to the resource request, and determining a first request time delay of the edge cloud to be accessed based on the request time and the response time; then, obtaining a second request time delay corresponding to the candidate edge cloud outside the access edge cloud from the cloud computing device or other cloud computing devices; finally, determining a target edge cloud with normal time delay finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and the time delay threshold value, so that the edge cloud with faults can be found out in time based on the first request time delay and the second request time delay, and the problem of untimely fault finding is avoided; meanwhile, the target edge cloud with normal time delay can be determined, the target edge cloud with normal time delay can be accessed by cloud computing application, the purpose that service is not interrupted is achieved, timely and accurate response to a resource request is ensured, and service execution efficiency is improved.
In some embodiments, as shown in fig. 3, the above step S204 "determining, from the edge cloud to be accessed and the candidate edge cloud, the target edge cloud that the cloud computing application finally accesses based on the first request latency, the second request latency, and the latency threshold" may be implemented by the following steps S2041 to S20412:
step S2041, obtaining a threshold weight, a path record number and a first delay threshold corresponding to the edge cloud to be accessed, and determining a delay critical value based on the threshold weight and the first delay threshold.
Here, in the cloud network, each edge cloud corresponds to a threshold weight, a path recording number and a time delay threshold, wherein the path recording number represents the recording number of the current jump path, and the time delay threshold corresponding to the edge cloud to be accessed is recorded as a first time delay threshold.
In the embodiment of the application, a first sum of the threshold weight and the set constant can be determined, and then a first product of the first sum and the first delay threshold is determined as the delay critical value. The threshold weight may be an initial default value or a custom setting value, and for example, the threshold weight may be any natural number between 0 and 30. The set constant can represent the proportional relation between the first delay threshold and the delay threshold, and the value of the set constant can be 1, 1.5, 2 and the like, and is generally 1. The delay critical value is used for measuring whether the delay of the edge cloud to be accessed is normal or not, and if the delay of the first request is smaller than the Yu Shi delay critical value, the delay of the edge cloud to be accessed is represented to be normal; and if the first request time delay is larger than the time delay critical value, the time delay of the edge cloud to be accessed is abnormal, namely the edge cloud to be accessed fails.
For example, assuming that the set constant has a value of 1, the threshold weight is a, the first delay threshold is B, and the delay threshold is B (1+a).
In some embodiments, if the first request latency is equal to a latency threshold, the latency of the edge cloud to be accessed may be considered normal.
In step S2042, it is determined whether the number of path records is less than a first-time number threshold.
Here, the first-time number threshold may be an initial default value or a custom set value, and may be, for example, 18, 20, 21, or the like.
In the embodiment of the application, the magnitude relation between the first time number threshold value and the first time number threshold value can be determined by a magnitude comparison method. If the number of path records is larger than the first-time number threshold, the number of records representing the current jump path is larger, and the finally determined accuracy can be supported, so that the first request time delay is continuously judged to be the normal time delay, and the step S2043 is entered; if it is determined that the number of path records is smaller than the first-time threshold, the number of records representing the current jump path is smaller, and the jump path is used for multiple times to improve the accuracy of final determination, step S2044 is entered.
In some embodiments, the processing manner in the case where the number of path records is equal to the first time threshold may be equivalent to the processing manner in the case where the number of path records is smaller than the first time threshold.
In step S2043, it is determined whether the first request delay is less than a delay threshold.
Here, whether the first request delay is smaller than the delay critical value can be judged by a size comparison method, if the first request delay is smaller than the delay critical value, the delay of the edge cloud to be accessed is represented to be normal, which also represents that the edge cloud to be accessed has no fault, the step S2044 is entered; if the first request delay is greater than the delay threshold, the delay of the edge cloud to be accessed is abnormal, and the edge cloud to be accessed is also represented to have a fault, then step S2047 is entered.
In some embodiments, the processing manner in which the first request latency is equal to the latency threshold may be identical to the processing manner in which the first request latency is less than the latency threshold.
Step S2044, determining the edge cloud to be accessed as the target edge cloud.
At this time, the number of path records is smaller than the first time threshold or the first request delay is smaller than the delay threshold, and the characterization is that the edge cloud to be accessed needs to be accessed continuously, or the delay of the edge cloud to be accessed is normal, and the edge cloud to be accessed is determined to be the target edge cloud.
Step S2045, determining that the number of path records is less than the second number threshold, and accumulating the number of path records by 1 to obtain updated number of path records.
In the embodiment of the application, after the edge cloud to be accessed is determined as the target edge cloud, the path record times of the edge cloud to be accessed and the first delay threshold are updated.
Here, the second-time threshold may be an initial default value or a custom value, which is greater than the first-time threshold, and may be, for example, 90, 95, 100, or the like.
In the embodiment of the application, the size relation between the path record times and the second time threshold can be determined by a size comparison method, and if the path record times are smaller than the second time threshold, the path record times are represented to be between the first time threshold and the second time threshold, and then the path record times are accumulated by 1 to obtain updated path record times.
In some embodiments, if the number of path records is greater than the second number of times threshold, the number of path records is characterized as having reached the maximum limit, the current number of path records is kept unchanged, and the number of path records may be considered as not being updated, or the number of path records before and after updating remains consistent.
In step S2046, an updated first delay threshold is determined based on the first delay threshold, the number of path records, the first request delay, and the new number of path records.
In the embodiment of the application, the first delay threshold of the edge cloud to be accessed is updated, when the first delay threshold is updated, the second product of the first delay threshold and the path record times can be determined, the second sum of the second product and the first request delay is determined, and finally the quotient of the second sum and the updated path record times is determined as the updated first delay threshold. Wherein the first delay threshold is capable of characterizing an average value of the delay.
For example, assuming that the first delay threshold is B, the number of path records is C, the number of updated path records is c+1, and the first request delay is D, where C is smaller than the second number of times threshold, in the embodiment of the present application, the updated first delay threshold is: (b×c+d)/(c+1).
In step S2047, a target edge cloud is determined from the plurality of candidate edge clouds based on the second request latency and the latency threshold.
At this time, the number of path records is greater than a first time number threshold, the first request time delay is greater than a time delay threshold, the time delay abnormality of the edge cloud to be accessed is represented, the edge cloud to be accessed is also represented to be faulty, the edge cloud with normal time delay is determined from a plurality of candidate edge clouds based on the second request time delay and the time delay threshold, and the edge cloud with normal time delay is determined to be the target edge cloud.
Step S2048, the second path state information of the edge cloud to be accessed is adjusted to an abnormal state.
Here, when determining the target edge cloud from the multiple candidate edge clouds based on the second request delay and the delay threshold, the edge Yun Shi to be accessed is delayed to be abnormal, that is, the edge cloud to be accessed fails, and the second path state information of the edge cloud to be accessed is adjusted from the normal state to the abnormal state, so as to avoid the cloud computing application from accessing the failed edge cloud again.
For example, the second path state information may be adjusted from true to false, thereby enabling adjustment of the second path state information to an abnormal state.
Step S2049, obtaining a retry flag value of the edge cloud to be accessed.
The retry flag value includes two values, namely a first flag value and a second flag value, wherein the retry flag value is that the cloud computing application accesses the edge cloud to be accessed again, and the retry flag value is that the second flag value indicates that the cloud computing application does not access the edge cloud to be accessed again. For example, the first flag value may be 1 and the second flag value may be 0.
In the embodiment of the application, the retry flag value is also stored in the cloud computing device of the edge cloud to be accessed, and the retry flag value of the edge cloud to be accessed can be obtained through a retry flag value obtaining instruction.
Step S20410, determining that the second path state information is in an abnormal state and the retry flag value is in a second flag value, and updating the retry flag value to the first flag value if the resource request sent by the cloud computing application is acquired again when the interval duration is reached.
Here, in order to monitor in real time whether the edge cloud to be accessed with the fault is recovered to be normal, when the second path state information is in an abnormal state and the retry flag value is in a second flag value, starting timing, if the timing duration reaches the interval duration and the resource request is obtained again, updating the retry flag value from the second flag value to the first flag value so as to characterize that the cloud computing application is accessing the edge cloud to be accessed again through the first flag value, thereby avoiding other cloud computing applications accessing the edge cloud to be accessed with the fault and avoiding the problem of causing service interruption.
In some embodiments, if the retry flag value is the first flag value, it is indicated that there are other cloud computing applications that are initiating retries for the edge cloud to be accessed, at which point the flow ends.
Step S20411, obtaining a retry request time delay for accessing the edge cloud to be accessed again.
Here, the implementation procedure of step S20411 is similar to that of step S202 described above, and therefore, the implementation procedure of step S20411 can refer to the implementation procedure of step S202 described above.
In step S20412, it is determined that the retry request delay satisfies the delay condition based on the first delay threshold, the second path state information is updated to the normal state, and the retry flag value is updated to the second flag value, so that the cloud computing application can continue to access the edge cloud to be accessed.
Here, whether the retry request delay meets the delay condition is judged by the first delay threshold, that is, whether the retry request delay is smaller than the delay threshold is judged, and if the retry request delay is smaller than the delay threshold, the retry request delay meets the delay condition is characterized. The determining method may refer to the implementation process of step S2043, and if the retry request delay satisfies the delay condition, it is indicated that the edge cloud to be accessed has recovered to be normal, and the second path state information corresponding to the edge cloud to be accessed is updated from the abnormal state to the normal state, and the retry flag value is updated from the first flag value to the second flag value, so that the cloud computing application can continue to access the edge cloud to be accessed.
In some embodiments, if the retry request latency does not meet the latency condition, the latency of the edge cloud to be accessed is characterized as abnormal, that is, the edge cloud to be accessed still has a fault, the second path state information is kept as an abnormal state, and the retry flag value is the first flag value, so that the cloud computing application does not access the edge cloud to be accessed with the fault.
In the embodiment of the present application, through the steps S2041 to S20412, the cloud computing device can determine, in real time, whether the first request delay of the edge cloud to be accessed is normal based on the delay threshold, and determine the edge cloud to be accessed as the target edge cloud and update the path record number of the edge cloud to be accessed and the first delay threshold under the condition that the first request delay characterizes the normal delay. And under the condition that the first request delay characterizes the abnormal delay, determining a target edge cloud with normal delay from a plurality of candidate edge clouds, adjusting second path information of the edge cloud to be accessed into an abnormal state, then monitoring whether the edge cloud to be accessed is normal or not in real time, and updating the second path information into a normal state when the edge cloud to be accessed is normal, so that cloud computing application can continuously access the edge cloud to be accessed which is normal. In the first aspect, when the edge cloud to be accessed has no fault, a first delay threshold of the edge cloud to be accessed is dynamically updated, so that the target edge cloud with normal delay can be determined; in the second aspect, faults in the edge cloud to be accessed are found in time, and the cloud computing application is controlled to access candidate edge clouds with normal time delay; in the third aspect, whether the edge cloud to be accessed is recovered to be normal can be timely found, and when the edge cloud to be accessed is recovered to be normal, the cloud computing application is controlled to continuously access the edge cloud to be accessed. The purpose that business is not interrupted is achieved, and the service level of the edge cloud is improved.
In some embodiments, when implementing the above step S2047 "determining the target edge cloud from the plurality of candidate edge clouds based on the second request latency and the latency threshold", as shown in fig. 4, it may be implemented by the following steps S471 to S476:
step S471, obtaining first path state information and a second delay threshold corresponding to the plurality of candidate edge clouds.
Here, the cloud computing device corresponding to each edge cloud further stores path state information corresponding to each edge cloud, wherein the path state information corresponding to the candidate edge cloud is recorded as first path state information, and the path state information corresponding to the edge cloud to be accessed is recorded as second path state information. In addition, the time delay threshold corresponding to each candidate edge cloud is recorded as a second time delay threshold, wherein the second time delay threshold can be a default value or a custom set value, and the second time delay threshold can be the same as the second time delay threshold or different from the first time delay threshold. Illustratively, the second latency threshold may be 2.8 seconds, 3 seconds, 3.1 seconds, etc.
In the embodiment of the present application, the method for obtaining the first path state information and the second delay threshold is similar to the method for obtaining the second request delay in the above step S203, and therefore, the implementation process of step S471 may refer to the implementation process of step S203.
Step S472, determining whether there is a target second latency threshold in the second request latency that is less than the second latency threshold.
Here, since there are a plurality of candidate edge clouds, the size relationship between each second request delay and the corresponding second delay threshold can be determined by a size comparison method, and if there is a second request delay less than the corresponding second delay threshold, the second request delay less than the second delay threshold is determined as the target second request delay. If the path state information is still to be judged, the step S473 is entered; if the second request delays are all greater than the corresponding second delay threshold, the characterization indicates that the target edge cloud cannot be determined from the candidate edge clouds by the delays, and the step S475 is performed.
Step S473, based on the first path state information, judging whether a candidate edge cloud with a normal path state exists in the candidate edge clouds corresponding to the target second request time delay.
Here, the path state information has two values, wherein one value characterizes that the path is normal, that is, the path can be normally accessed by the cloud computing application; another value characterizes a path anomaly, i.e., the path is not accessible by the cloud computing application. For example, the path states may take values of "true" and "false," where "true" characterizes the path as normal and "false" characterizes the path as abnormal.
In the embodiment of the present application, if a candidate edge cloud with a normal path state exists in the candidate edge clouds corresponding to the target second request delay, the candidate edge cloud with the normal path state is determined to be the candidate edge cloud with the normal path state, and step S474 is performed; if the candidate edge cloud corresponding to the second request delay of the target does not have the candidate edge cloud with the normal path state, the characterization that the target edge cloud cannot be determined from the candidate edge clouds through the path state information also goes to step S475.
Step S474, determining the edge cloud with the minimum request delay in the path normal edge cloud as the target edge cloud.
Here, if the number of the determined path normal edge clouds is 1, the path normal edge clouds are directly determined to be target edge clouds; and if the number of the determined path normal edge clouds is at least 2, sorting the second request time delay corresponding to the path normal edge clouds, and determining the path normal edge cloud with the minimum time delay as the target edge cloud.
Step S475 determines an idle candidate edge cloud from the candidate edge clouds based on the second request latency.
At this time, if the target second delay threshold value does not exist or the path normal edge cloud does not exist, determining that the edge cloud with the request delay does not exist from the plurality of candidate edge clouds, wherein the edge cloud representation without the request delay is not accessed by the cloud computing application, and recording the edge cloud without the request delay as an idle edge cloud.
Meanwhile, no information is stored in the cloud computing device corresponding to the idle edge cloud, and no path record times, path state information and the like are stored except for no storage request delay.
In step S476, the idle candidate edge cloud is determined as the target edge cloud.
Here, the idle candidate edge cloud is determined as a target edge cloud to be accessed by the cloud computing application.
In the embodiment of the present application, through the steps S471 to S476, when determining the target edge cloud from the plurality of candidate edge clouds based on the second request delay and the delay threshold, if there is a path normal edge cloud, determining the edge cloud with the minimum request delay from the path normal edge clouds as the target edge cloud; and if the target second request delay does not exist or the path normal edge cloud does not exist, determining an idle edge cloud based on the second request delay, and determining the idle edge cloud as the target edge cloud. Therefore, the target edge cloud with normal time delay can be determined from the candidate edge clouds, the target edge cloud with normal time delay can be accessed by cloud computing application, and the purpose that service is not interrupted is achieved.
Based on the above embodiments, the embodiments of the present application provide a determining method, which is applied to a cloud computing device, where the cloud computing device may be an edge cloud selector, and the edge cloud selector may automatically record a buffer, calculate a threshold, detect an edge cloud fault, and attempt to guide traffic to other edge clouds after a delay rise reaches a threshold due to the fault occurrence, so as to reduce the delay. Taking cloud computing equipment as an edge cloud selector as an example, the edge cloud selector can automatically perform path test and correction, and ensure that flow can be correctly guided back to the original edge cloud after fault recovery. The edge cloud selector can be deployed between the UPF and the edge cloud, and can also be deployed on the UPF.
In actual implementation, the cloud computing device can be widely applied to edge cloud selection under the conditions of private network, network slicing and the like, can reduce the failure rate of the private network, ensures SLA service and has wider application prospect.
Taking a cloud computing device as an edge cloud selector as an example, referring to fig. 5, the edge cloud selector 501 is deployed on each edge cloud in the 5G private network, where the edge cloud selector 501 may be a reverse proxy or a gateway; the threshold coefficient x (the value is 0-30) needs to be configured on each edge cloud, the identification list of all edge clouds and center clouds under the current private network and the corresponding access address, the edge cloud selector 501 comprises a cache 5011, and the edge cloud selector 501 can determine whether the source edge cloud 502 and a plurality of edge clouds 503 have faults by using the cache 5011. Wherein the threshold coefficient x corresponds to the threshold weight in the above embodiment.
When the edge cloud selector E is deployed to the edge cloud E and directly connected to the edge cloud E, the edge cloud E is called a source edge cloud of the edge cloud selector E, where the source edge cloud is equivalent to the edge cloud to be accessed in the above embodiment.
In the embodiment of the application, the determining method comprises the following four steps:
Step one, an edge cloud selector counts request time delay and fault conditions of edge cloud in real time, and records the results to a cache, wherein the cache record content can refer to a table 1, and 'mep_path+resource' is used as a cache main key; when the cache is not recorded during the access of the edge cloud resource, the source edge cloud is used by default; and the record is cached, the first path state information is used as the edge cloud with normal path state, and the second path state information is used as the source edge cloud with normal path state in general.
Table 1 cache record content reference table
And step two, when the path record times (count) of the edge cloud E resources E are less than or equal to 20 or the time delay (delay) is not greater than a threshold (1+threshold coefficient x)), updating the cache of the edge cloud E resources E. The threshold corresponds to the first request delay in the above embodiment, and the threshold (1+threshold coefficient x)) corresponds to the delay threshold in the above embodiment.
In some embodiments, the path record number (count) and the first latency threshold (threshold) are refreshed as in equations 1, 2, and 3 below:
count new type ＝count Old one +1 (equation 1);
threshold new type ＝(threshold Old one *count Old one +delay New type )/count New type (equation 2);
when count New type >When=100, count New type =100 (equation 3);
And the second path state information (status) is set to be in a normal state (true) when the second path state information (status) is not in the normal state (true), and other values are refreshed normally; wherein count New type Indicating the updated path record times; count (count) Old one The number of path records before update is represented; threshold (threshold) New type Representing an updated first latency threshold; threshold (threshold) Old one Representing a first delay threshold before updating.
When the path record number (count) of the source edge cloud E resource E is >20, the current delay (delay) is greater than the threshold (threshold x (1+threshold coefficient x)), and the current delay (delay) is also greater than 1000 milliseconds; or, when the number of path records (count) >20 of the edge cloud E resource E and the current delay (delay) is greater than a threshold (threshold×1+threshold coefficient x), and the current delay (delay) is still greater than 30 seconds, setting the second path state information (status) of the source edge cloud E to an abnormal state (false), then searching the cache for the edge cloud F resource E with the delay lower than the delay threshold, and if the delay is not found in the cache, randomly selecting an edge cloud F without the cache record from the edge cloud list (may be an edge cloud, a data center, or the like according to deployment situations, and is omitted below), and attempting to forward a request of the edge cloud E resource E to the resource E of the edge cloud F. The edge cloud E corresponds to the edge cloud to be accessed in the above embodiment, and the edge cloud F corresponds to the candidate edge cloud in the above embodiment.
Step three, when the second path state information (status) of a certain resource E of a certain source edge cloud E is in an abnormal state (false), if the cache retry flag value (retry) is no (false), guiding the traffic to the resource E of the edge cloud E once, setting the cache retry flag value (retry) of the edge cloud E resource E to be true so as to prevent the traffic from being continuously introduced, and then comparing whether the value of the current delay (delay) is greater than 130% of the delay threshold value, if so, indicating that the current interface is not recovered to be normal, and guiding the current traffic to other edge clouds; if the retry flag value (retry) is less than or equal to the latency threshold (threshold), the second path state information (status) is set to a normal state (true) to indicate that the current interface has recovered to normal, and other values in the cache are normally refreshed. The current delay is equivalent to the retry request delay in the above embodiment; whether (false) corresponds to the second flag value in the above embodiment or (true) corresponds to the first flag value in the above embodiment.
And step four, when the time delay of the current edge cloud record is too high, repeating the step two and the step three again.
The embodiment of the application provides a determining method which can be applied to an edge cloud selector on a 5G private network, can continuously record and detect the time delay of each edge cloud so as to judge the state of an interface, select the edge cloud with normal time delay in the current environment and provide edge cloud computing resources.
The cloud node determining method provided by the embodiment of the application replaces the original direct calling mode, so that the risk of direct error reporting of interface calling can be effectively reduced, the average time delay of waiting of a user can be reduced to a certain extent, and the response efficiency of the system is improved; in addition, the cache mode of calling delay, threshold value, state and the like of the edge Yun Jiekou is recorded, so that the basic calling condition of the interface can be judged quickly; the method also comprises an automatic generation and correction mode of the edge cloud time delay threshold value, a reasonable threshold value can be calculated dynamically according to an algorithm, and the selection of a proper edge cloud providing resource is facilitated.
By using the cloud node determining method provided by the embodiment of the application, the request can be automatically forwarded to other edge cloud providing resources after the service delay is increased due to the failure of the edge cloud, the manual intervention is not needed, the response is rapid, the cache is automatically recorded, the threshold is dynamically corrected, the request is automatically forwarded, and the operation and maintenance cost is saved. Compared with the direct use of the edge cloud, the edge cloud low-delay characteristic can be kept to the greatest extent under the condition of local faults, and the SLA service can be timely switched and guaranteed after the faults are recovered.
Based on the foregoing embodiments, the embodiments of the present application provide a cloud node determining apparatus, where each module included in the apparatus and each unit included in each module may be implemented by a processor in a cloud computing device; of course, the method can also be realized by corresponding logic circuits; in practice, the processor may be a central processing unit (Central Processing Unit, CPU), microprocessor (Microprocessor Unit, MPU), digital signal processor (Digital Signal Processing, DSP) or field programmable gate array (Field Programmable Gate Array, FPGA), etc.
An embodiment of the present application further provides a cloud node determining device, fig. 6 is a schematic diagram of a composition structure of the cloud node determining device provided by the embodiment of the present application, as shown in fig. 6, where the cloud node determining device 600 includes:
a first obtaining module 601, configured to obtain a resource request sent by a cloud computing application to an edge cloud to be accessed;
a first determining module 602, configured to determine a first request delay based on a request time corresponding to the resource request and a response time corresponding to the resource request;
a second obtaining module 603, configured to obtain a second request delay corresponding to a candidate edge cloud other than the edge cloud to be accessed;
A second determining module 604, configured to determine, based on the first request latency, the second request latency, and a latency threshold, a target edge cloud that is ultimately accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud.
In some embodiments, the candidate edge cloud comprises a plurality of edge clouds, and the second determining module 604 comprises:
the first determining submodule is used for acquiring the threshold weight, the path record times and the first delay threshold value corresponding to the edge cloud to be accessed, and determining a delay critical value based on the threshold weight and the first delay threshold value;
a second determining submodule, configured to determine that the edge cloud to be accessed is the target edge cloud if the number of path records is less than a first number threshold, or if the first request delay is less than the delay threshold;
and a third determining submodule, configured to determine, if the number of path records is greater than the first number threshold and the first request delay is greater than the delay threshold, the target edge cloud from a plurality of candidate edge clouds based on the second request delay and the delay threshold.
In some embodiments, the third determination submodule includes:
The first acquisition unit is used for acquiring first path state information and a second time delay threshold value corresponding to the plurality of candidate edge clouds;
a first determining unit, configured to determine a second request latency smaller than the second latency threshold as a target second request latency;
the second determining unit is used for determining a candidate edge cloud with a normal path state in the candidate edge clouds corresponding to the target second request delay as a path normal edge cloud based on the first path state information;
and the third determining unit is used for determining the edge cloud with the minimum request delay in the path normal edge cloud as the target edge cloud.
In some embodiments, the third determination submodule further includes:
a fourth determining unit, configured to determine, if the target second request delay does not exist or the path normal edge cloud does not exist, an idle candidate edge cloud from the candidate edge clouds based on the second request delay;
and a fifth determining unit, configured to determine the idle candidate edge cloud as the target edge cloud.
In some embodiments, the second determining module 604 further comprises:
the first updating sub-module is used for if the edge cloud to be accessed is determined to be the target edge cloud, determining that the path record times are smaller than a second time threshold value, and accumulating the path record times by 1 to obtain updated path record times;
And the second updating sub-module is used for determining an updated first delay threshold value based on the first delay threshold value, the path record times, the first request delay and the new path record times.
In some embodiments, the second determining module 604 further comprises:
and the adjustment sub-module is used for adjusting the second path state information of the edge cloud to be accessed to an abnormal state if the target edge cloud is determined from a plurality of candidate edge clouds based on the second request time delay and the time delay threshold value.
In some embodiments, the second determining module 604 further comprises:
the first obtaining submodule is used for obtaining a retry flag value of the edge cloud to be accessed, wherein the retry flag value is a first flag value for representing that the cloud computing application accesses the edge cloud to be accessed again, and the retry flag value is a second flag value for representing that the cloud computing application does not access the edge cloud to be accessed again;
a third updating sub-module, configured to determine that the second path state information is the abnormal state and the retry flag value is the second flag value, and update the retry flag value to the first flag value if a resource request sent by the cloud computing application is acquired again when an interval duration is reached;
The second acquisition sub-module is used for acquiring retry request time delay of revisiting the edge cloud to be accessed;
and a fourth updating sub-module, configured to determine that the retry request delay meets a delay condition based on the first delay threshold, update the second path state information to a normal state, and update the retry flag value to the second flag value, so that the cloud computing application can continue to access the edge cloud to be accessed.
It should be noted that, the description of the cloud node determining device in the embodiment of the present application is similar to the description of the method embodiment described above, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the present apparatus embodiment, please refer to the description of the method embodiment of the present application for understanding.
It should be noted that, in the embodiment of the present application, if the cloud node determining method is implemented in the form of a software functional module, and is sold or used as an independent product, the cloud node determining method may also be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be embodied essentially or in a part contributing to the related art in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, an optical disk, or other various media capable of storing program codes. Thus, embodiments of the application are not limited to any specific combination of hardware and software.
Accordingly, an embodiment of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the cloud node determination method provided in the above embodiment.
An embodiment of the present application provides a cloud computing device, fig. 7 is a schematic diagram of a composition structure of the cloud computing device provided by the embodiment of the present application, as shown in fig. 7, where, the cloud computing device 700 includes: a processor 701, at least one communication bus 702, a user interface 703, at least one external communication interface 704 and a memory 705. Wherein the communication bus 702 is configured to enable connected communication between these components. The user interface 703 may include a display screen, and the external communication interface 704 may include a standard wired interface and a wireless interface, among others. Wherein the processor 701 is configured to execute a program of the cloud node determination method stored in the memory, so as to implement the cloud node determination method provided in the above embodiment.
The description of cloud computing device and storage medium embodiments above is similar to that of method embodiments described above, with similar benefits as method embodiments. For technical details not disclosed in the embodiments of the cloud computing device and the storage medium of the present application, please refer to the description of the method embodiments of the present application for understanding.
It should be noted here that: the description of the storage medium and cloud computing device embodiments above is similar to that of the method embodiments described above, with similar benefits as the method embodiments. For technical details not disclosed in the storage medium and cloud computing device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application. The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In several embodiments provided by the present application, it should be understood that the disclosed cloud computing device and method may be implemented in other manners. The cloud computing device embodiments described above are merely illustrative, and for example, the division of the units is merely a logical function division, and there may be other division manners in actual implementation, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units; can be located in one place or distributed to a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purposes of the embodiment of the present application.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, where the program, when executed, performs steps including the above method embodiments; and the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.
Alternatively, the above-described integrated units of the present application may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied essentially or in a part contributing to the related art in the form of a software product stored in a storage medium, including several instructions for causing an AC to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.
The foregoing is merely an embodiment of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by 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 (10)
1. A cloud node determination method, the method comprising:
Acquiring a resource request sent by a cloud computing application to an edge cloud to be accessed;
determining a first request time delay based on the request time corresponding to the resource request and the response time corresponding to the resource request;
acquiring a second request time delay corresponding to the candidate edge cloud outside the edge cloud to be accessed;
and determining a target edge cloud finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and a time delay threshold.
2. The method of claim 1, wherein the candidate edge cloud comprises a plurality of edge clouds, and wherein the determining, from the edge clouds to be accessed and the candidate edge cloud, a target edge cloud that the cloud computing application ultimately accesses based on the first request latency, the second request latency, and a latency threshold comprises:
acquiring a threshold weight, path record times and a first delay threshold corresponding to the edge cloud to be accessed, and determining a delay critical value based on the threshold weight and the first delay threshold;
if the number of path records is smaller than a first time threshold or the first request time delay is smaller than the time delay critical value, determining that the edge cloud to be accessed is the target edge cloud;
And if the number of path records is greater than the first time threshold and the first request time delay is greater than the time delay critical value, determining the target edge cloud from a plurality of candidate edge clouds based on the second request time delay and the time delay threshold.
3. The method of claim 2, wherein the determining the target edge cloud from a plurality of candidate edge clouds based on the second request latency and the latency threshold comprises:
acquiring first path state information and a second time delay threshold value corresponding to the plurality of candidate edge clouds;
determining a second request delay less than the second delay threshold as a target second request delay;
based on the first path state information, determining a candidate edge cloud with a normal path state in candidate edge clouds corresponding to the target second request time delay as a path normal edge cloud;
and determining the edge cloud with the minimum request delay in the path normal edge cloud as the target edge cloud.
4. A method as claimed in claim 3, further comprising:
if the target second request delay does not exist or the path normal edge cloud does not exist, determining an idle candidate edge cloud from the candidate edge clouds based on the second request delay;
And determining the idle candidate edge cloud as the target edge cloud.
5. The method as recited in claim 2, wherein the method further comprises:
if the edge cloud to be accessed is determined to be the target edge cloud, determining that the path record times are smaller than a second time threshold, and accumulating the path record times by 1 to obtain updated path record times;
and determining an updated first delay threshold based on the first delay threshold, the path record times, the first request delay and the new path record times.
6. The method as recited in claim 2, wherein the method further comprises:
and if the target edge cloud is determined from a plurality of candidate edge clouds based on the second request time delay and the time delay threshold value, adjusting the second path state information of the edge cloud to be accessed to an abnormal state.
7. The method as recited in claim 6, wherein the method further comprises:
obtaining a retry flag value of the edge cloud to be accessed, wherein the retry flag value is a first flag value for representing that the cloud computing application accesses the edge cloud to be accessed again, and the retry flag value is a second flag value for representing that the cloud computing application does not access the edge cloud to be accessed again;
Determining that the second path state information is the abnormal state and the retry flag value is the second flag value, and updating the retry flag value to the first flag value if the resource request sent by the cloud computing application is acquired again when the interval duration is reached;
acquiring retry request time delay for revisiting the edge cloud to be visited;
and determining that the retry request time delay meets a time delay condition based on the first time delay threshold, updating the second path state information to be in a normal state, and updating the retry flag value to be the second flag value so that the cloud computing application can continuously access the edge cloud to be accessed.
8. A cloud node determination apparatus, characterized in that the cloud node determination apparatus comprises:
the first acquisition module is used for acquiring a resource request sent by the cloud computing application to the edge cloud to be accessed;
the first determining module is used for determining a first request time delay based on the request time corresponding to the resource request and the response time corresponding to the resource request;
the second acquisition module is used for acquiring a second request time delay corresponding to the candidate edge cloud outside the edge cloud to be accessed;
And the second determining module is used for determining a target edge cloud finally accessed by the cloud computing application from the edge cloud to be accessed and the candidate edge cloud based on the first request time delay, the second request time delay and a time delay threshold value.
9. A cloud computing device for determining cloud nodes, the cloud computing device comprising:
a processor; and
a memory for storing a computer program executable on the processor;
wherein the computer program when executed by a processor implements the cloud node determination method of any of claims 1 to 7.
10. A computer-readable storage medium having stored therein computer-executable instructions configured to perform the cloud node determination method of any of the preceding claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210412623.4A CN116962395A (en) | 2022-04-19 | 2022-04-19 | Cloud node determining method, device, equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210412623.4A CN116962395A (en) | 2022-04-19 | 2022-04-19 | Cloud node determining method, device, equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116962395A true CN116962395A (en) | 2023-10-27 |
Family
ID=88447931
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210412623.4A Pending CN116962395A (en) | 2022-04-19 | 2022-04-19 | Cloud node determining method, device, equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116962395A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117611045A (en) * | 2024-01-22 | 2024-02-27 | 湖南创亚信息科技有限公司 | Cargo flow monitoring method and system based on cloud computing |
-
2022
- 2022-04-19 CN CN202210412623.4A patent/CN116962395A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117611045A (en) * | 2024-01-22 | 2024-02-27 | 湖南创亚信息科技有限公司 | Cargo flow monitoring method and system based on cloud computing |
| CN117611045B (en) * | 2024-01-22 | 2024-04-19 | 湖南创亚信息科技有限公司 | Cargo flow monitoring method and system based on cloud computing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3379419B1 (en) | Situation analysis | |
| US10432533B2 (en) | Automatic detection and prevention of network overload conditions using SDN | |
| CN110162424B (en) | Fault processing method, system, device and storage medium | |
| EP3806432A1 (en) | Method for changing service on device and service changing system | |
| US10797971B2 (en) | Diagnostic framework in computing systems | |
| CN109586952B (en) | Server capacity expansion method and device | |
| US11316792B2 (en) | Method and system of limiting traffic | |
| US9998381B2 (en) | Quality of service for high network traffic events | |
| CN113163002B (en) | Server switching method and device and storage medium | |
| US11537304B2 (en) | Data verification method and apparatus, and storage medium | |
| JP2015510201A (en) | Method and apparatus for rapid disaster recovery preparation in a cloud network | |
| CN111404713B (en) | Network resource adjusting method, device and storage medium | |
| US10936386B2 (en) | Method, device and computer program product for monitoring access request | |
| US20210065083A1 (en) | Method for changing device business and business change system | |
| CN110166271B (en) | Method and device for detecting network node abnormality | |
| CN112948128A (en) | Target terminal selection method, system and computer readable medium | |
| US20170299645A1 (en) | Fault Analysis Method and Apparatus Based on Data Center | |
| CN116962395A (en) | Cloud node determining method, device, equipment and computer readable storage medium | |
| CN106936926B (en) | Method and system for accessing data node | |
| US20170206125A1 (en) | Monitoring system, monitoring device, and monitoring program | |
| CN116633766A (en) | Fault processing method and device, electronic equipment and storage medium | |
| US9479579B2 (en) | Grouping processing method and system | |
| CN115002205B (en) | Kapacitor clustering method based on table routing proxy mode | |
| CN115378795B (en) | Method and device for monitoring network quality of server, electronic equipment and storage medium | |
| CN116701127B (en) | Big data-based application performance monitoring method and platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |