Method for implementing edge function of clocked flip-flop type

Abstract

The present application relates to the technical field of edge function computing, and to a method for implementing an edge function of a clocked flip-flop type, aiming to solve the problem that traditional methods for triggering an edge function by http cannot meet the data processing requirements of some Internet of Things devices. The key points of the technical solution of the method comprise S1: setting an edge function, causing an edge function of a flip-flop type to rely on a CDN, setting a corresponding script and trigger frequency, and deploying the script to an edge environment; S2, triggering and updating a timed task; S3, when the script is not bound with a domain name, responding to the function of a clocked flip-flop type; S4, responding to the timed task during operation and executing access authentication; and S5, data acquisition: acquiring and monitoring logs in a domain-name-free state to acquire data. More efficient and reliable task scheduling and data processing effects are achieved in edge computing environments.

Description

A method for implementing edge functions of timing trigger type

[0001] Related applications

[0002] This application claims priority to Chinese patent application number 2023117126843, filed on December 13, 2023, entitled “A method for implementing an edge function of a timing trigger type,” the entire text of which is hereby incorporated by reference. Technical Field

[0003] The present application relates to the field of edge function calculation technology, and in particular to a method for implementing an edge function of a timing trigger type. Background Art

[0004] Thanks to advances in mobile computing and the Internet of Things, billions of mobile and IoT devices are connected to the Internet, generating hundreds of millions of bytes of data at the edge of the network. Driven by artificial intelligence and the Internet of Things, it is imperative to push the frontier of artificial intelligence to the edge of the network and fully tap the potential of edge big data.

[0005] To achieve this trend, edge function computing is a promising artificial intelligence technology that supports the application of edge computing technology to edge devices. This technology can provide various forms of business services such as authentication, encryption and decryption, data storage, and data cleaning.

[0006] The traditional technical solutions mentioned above have the following defects: the traditional method of triggering edge functions by HTTP can no longer meet the data processing needs of some IoT devices. The demand for edge function calculations triggered at different frequencies for different scenarios is also increasing. Currently, there is no technology that can increase the efficiency of edge function calculations, resulting in poor data processing speed of IoT devices. Summary of the Invention

[0007] The purpose of this application is to provide an edge function that provides a consistent trigger frequency based on the particularity of the business scenario, so that the function on the edge device or edge node can be automatically triggered and executed according to a predetermined schedule. Edge function implementation method of the timed trigger type.

[0008] To achieve the above objectives, this application provides the following technical solutions:

[0009] A method for implementing an edge function of a timing trigger type is as follows:

[0010] S1: Set up edge functions. Deploy trigger-type edge functions to the CDN, set the corresponding script and trigger frequency, and deploy the script to the edge environment.

[0011] Create a scheduled task script and deploy it as follows:

[0012] A1: Compile the script to generate the corresponding artifact file;

[0013] A2: Send the artifact file to the global resource pool;

[0014] S2: Triggering and updating scheduled tasks. The task center obtains the successfully issued scripts that need to be executed on a scheduled basis within ten minutes and generates scheduled tasks with the same frequency. Scheduled tasks trigger the script content in a specific way to meet customer needs.

[0015] S3: Implements the response of a timed trigger type function when the script is not bound to a domain name;

[0016] S4: Runtime response to scheduled tasks and access authentication;

[0017] S5: Data collection, collect and monitor logs without domain name to achieve data collection.

[0018] Furthermore, the triggering and updating of the scheduled task in S2 is specifically as follows:

[0019] B1: Every ten minutes, retrieve the task scripts that meet the requirements and put them into the cronMap;

[0020] B2: Traverse the cronMap and start each scheduled task;

[0021] B3: After ten minutes, retrieve the new data and compare it with the old data. Mark the newly added content and add it to the scheduled task. Mark the content to be deleted and stop the scheduled task.

[0022] Furthermore, in B3, the changed scheduled tasks are accurately identified and the scheduled tasks are updated after being marked.

[0023] Furthermore, the specific steps of S3 are as follows:

[0024] C1: Set a special domain name specifically for processing timer trigger type functions;

[0025] C2: Configure a special header to store the address of the wasm file generated after the function is compiled;

[0026] C3: Configure a special header for authentication to prevent external malicious attacks from imitating this function trigger;

[0027] C4: Configure load balancing.

[0028] Furthermore, the load balancing configuration in C4 is specifically to randomly obtain an IP address corresponding to a special domain name for responding to script access, and perform load balancing through a random method.

[0029] Furthermore, the specific steps of S4 are:

[0030] D1: When accessing a special domain name, check whether it has a token.

[0031] D2: Access the corresponding artifact according to the wasm file address stored in the special header;

[0032] D3: Returns the response content of the script corresponding to the product file.

[0033] Furthermore, in order to collect and monitor logs in S5, a special header must be configured to store the function ID, and the subsequent function logs are bound to the ID.

[0034] Furthermore, after the function log in S5 is bound to the id, the response, traffic and other information of the function are bound to the user id and script id, and reported to the monitoring system for data collection.

[0035] Furthermore, the edge function in S1 is used to regularly back up and synchronize data to edge devices or cloud storage, extract data from data sources and generate reports, and then send the reports to relevant users or systems. The edge function is used to distribute computing tasks to edge devices or edge nodes for execution to reduce data transmission and delay.

[0036] Furthermore, the edge function in S1 is used to periodically trigger edge functions to check sensor status, execute device control operations or perform device status monitoring, and is used to periodically trigger edge functions to read data from sensors, and then perform real-time analysis and processing to promptly detect abnormal situations or optimize system performance. At the same time, it is used to periodically trigger edge functions to monitor device load conditions, and dynamically adjust task allocation and resource allocation according to load conditions to achieve optimal resource utilization. A trigger is a mechanism used to trigger an operation or event at a specific time point or time interval.

[0037] In summary, the beneficial technical effects of this application are:

[0038] 1. This application monitors changes in scheduled tasks and updates scheduled tasks in a timely manner, including the addition and deletion of scheduled tasks, changes in scheduled frequency, changes in task content, etc., and can trigger scripts on a scheduled basis without a domain name, reducing the complexity of domain name configuration and the workload of deployment. When implementing edge functions of the timed trigger type, unauthorized access and operation are avoided, and security measures such as token verification mechanisms are used to protect the security of edge functions. At the same time, when executing scheduled tasks, information such as script ID and user ID is brought in, logs and indicators are obtained and reported to the monitoring center to help diagnose problems, optimize performance, and provide a visual report on the execution of edge functions;

[0039] 2. The timed trigger of this application can avoid continuous consumption of computing resources. The computing resources of edge devices are usually limited. By timing the triggering of edge functions, the function can be started when the task needs to be executed, and the resources can be released after the task is completed. This method can effectively save computing resources and improve the resource utilization of edge devices, and timed triggers can be used to regularly collect, process and synchronize data. For example, in the Internet of Things scenario, edge functions can be triggered regularly to collect sensor data and perform real-time processing and analysis, which helps to ensure the timeliness and consistency of the data so that subsequent decisions and operations can be based on the latest data. These advantages of edge functions of the timed trigger type make task scheduling and data processing in edge computing environments more efficient and reliable;

[0040] 3. The timing trigger of this application can be used to schedule edge functions to perform different tasks. Different tasks can be scheduled to be executed at appropriate times through predetermined time intervals or time points, which helps to optimize the execution order and timing of tasks to maximize the efficiency and performance of the overall system. The timing trigger makes the execution of edge functions automated without manual intervention. Edge functions can be automatically triggered and executed according to a predetermined schedule, which reduces the need for manual operation, improves the degree of automation of the system, and reduces the risk of human error. The created timed edge function can also be automatically triggered according to a predetermined schedule without configuring a domain name, simplifying the domain name registration, DNS resolution and other steps, reducing the complexity of domain name configuration and the workload of deployment. For end users or other systems, they do not need to care about how the edge function is triggered, they only need to use the provided interfaces and services, which can improve the security and maintainability of the system, while simplifying the integration of external systems and adjustments to the internal architecture. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the conventional technology, the following briefly introduces the drawings required for use in the embodiments or the conventional technology descriptions. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the disclosed drawings without any creative work.

[0042] Figure 1 is a schematic diagram of the overall process structure of this application. DETAILED DESCRIPTION

[0043] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0044] The present application method is further described in detail below with reference to the accompanying drawings.

[0045] Example 1

[0046] Referring to FIG1 , a method for implementing an edge function of a timing trigger type is as follows:

[0047] S1: Set up edge functions. Deploy trigger-type edge functions to the CDN, set the corresponding script and trigger frequency, and deploy the script to the edge environment.

[0048] Create a scheduled task script and deploy it as follows:

[0049] A1: Compile the script to generate the corresponding artifact file;

[0050] A2: Send the artifact file to the global resource pool;

[0051] A timed trigger edge function is a function that is triggered by a timed trigger to execute at the edge in an edge computing environment. The following is an explanation of the relevant terms:

[0052] Scheduled trigger: A scheduled trigger is a mechanism used to trigger an action or event at a specific time point or time interval. In edge computing, a scheduled trigger can be used to periodically execute edge functions, for example, at intervals or at specific time points.

[0053] Edge functions: Edge functions are a computing model that distributes computing tasks to edge devices or edge nodes to reduce data transmission and latency. Edge functions are typically lightweight, short-running tasks that can be quickly started and stopped as needed.

[0054] S2: Triggering and updating scheduled tasks. The task center obtains the successfully issued scripts that need to be executed on a scheduled basis within ten minutes and generates scheduled tasks with the same frequency. Scheduled tasks trigger the script content in a specific way to meet customer needs.

[0055] B1: Every ten minutes, retrieve the task scripts that meet the requirements and put them into the cronMap;

[0056] B2: Traverse the cronMap and start each scheduled task;

[0057] B3: After ten minutes, retrieve the new data and compare it with the old data. Mark the newly added content and add it to the scheduled task. Mark the content to be deleted and stop the scheduled task. After the scheduled task is successfully stopped, delete the content in the cronMap.

[0058] S3: Implements the response of a timed trigger type function when the script is not bound to a domain name;

[0059] C1: Set a special domain name specifically for processing timer trigger type functions;

[0060] C2: Configure a special header to store the address of the wasm file generated after the function is compiled;

[0061] C3: Configure a special header for authentication to prevent external malicious attacks from imitating this function trigger;

[0062] C4: Configure load balancing, randomly obtain the IP address corresponding to a special domain name to respond to script access, and perform load balancing through random methods;

[0063] S4: Runtime response to scheduled tasks and access authentication;

[0064] D1: When accessing a special domain name, check whether it has a token.

[0065] D2: Access the corresponding artifact according to the wasm file address stored in the special header;

[0066] D3: Returns the response content of the script corresponding to the product file;

[0067] S5: Data collection: collect and monitor logs without domain names to achieve data collection;

[0068] Configure a special header to store the function ID, and subsequent function logs are bound to the ID;

[0069] After the function log is bound to the ID, the function's response, traffic, and other information are bound to the user ID and script ID and reported to the monitoring system for data collection.

[0070] Edge functions are used to regularly back up and synchronize data to edge devices or cloud storage, extract data from data sources and generate reports, and then send the reports to relevant users or systems. Edge functions are used to distribute computing tasks to edge devices or edge nodes for execution to reduce data transmission and latency. Edge functions are used to regularly trigger edge functions to check sensor status, perform device control operations, or perform device status monitoring. They are also used to regularly trigger edge functions to read data from sensors and then perform real-time analysis and processing to promptly detect abnormal situations or optimize system performance. At the same time, they are used to periodically trigger edge functions to monitor device load conditions, dynamically adjust task allocation and resource allocation according to load conditions, and achieve optimal resource utilization. A trigger is a mechanism used to trigger an operation or event at a specific time point or time interval.

[0071] Example 2

[0072] Thanks to advances in mobile computing and the Internet of Things (IoT), billions of mobile and IoT devices are connected to the internet, generating hundreds of millions of bytes of data at the edge of the network. Driven by AI and the IoT, it's imperative to push the frontiers of AI to the edge of the network and fully leverage the potential of edge big data. To achieve this trend, edge function computing is a promising AI technology that supports the application of edge computing to edge devices. This technology can provide various business services, such as authentication, encryption and decryption, data storage, and data cleansing. However, the traditional method of triggering edge functions via HTTP no longer meets the data processing needs of some IoT devices. The demand for edge function computing triggered at different frequencies for different scenarios is also increasing. This has led to the emergence of timed trigger-based edge function technology. In edge computing environments, timed triggers can trigger an operation or event at a predetermined time interval or at a specific point in time, such as collecting, processing, analyzing, or sending data at a specific time.

[0073] The purpose of this application is to provide an edge function that can be triggered on a scheduled basis, whose trigger frequency can be modified centrally, and which takes effect within a certain period of time. This function is used to provide edge computing for various scenarios while providing edge functions with trigger frequencies tailored to the particularities of business scenarios. This allows functions on edge devices or edge nodes to be automatically triggered and executed according to a predetermined schedule. This technology can be used in various edge computing application scenarios, such as data processing, real-time monitoring and analysis of IoT devices, and edge artificial intelligence. Through timed triggers, edge computing can respond to and process data more intelligently, providing more efficient computing capabilities and faster response times.

[0074] Overall architecture: Trigger-type edge functions rely on CDN. Customers set the corresponding script and trigger frequency, deploy the script to the edge environment, and the task center obtains the relevant scripts that need to be executed on a scheduled basis within 10 minutes. It generates a scheduled task with the same frequency. The scheduled task triggers the script content in a specific way to meet customer needs. Trigger-type edge functions are composed of the following five points:

[0075] 1. Create a scheduled task script and deploy it

[0076] a) Compile the script to generate the corresponding product file;

[0077] b) Send the product files to the global resource pool;

[0078] 2. Triggering and updating of scheduled tasks;

[0079] a) Every ten minutes (modifiable), take out the task script that meets the conditions and put it into cronMap (to prevent the function with the timed trigger from changing, and refresh the scheduled task every ten minutes);

[0080] b) Traverse the cronMap and start each scheduled task (for the first time);

[0081] c) After ten minutes, take out the new data and compare it with the old data. Mark the newly added content and add it to the scheduled task. Mark the content to be deleted and stop the scheduled task. After the scheduled task is successfully stopped, delete the content in the cronMap.

[0082] 3. When the function script is not bound to a domain name, the response of the timer trigger type function is realized

[0083] a) Set up a special domain name specifically for processing timer trigger type functions;

[0084] b) Configure a special header to store the address of the wasm file generated after the function is compiled;

[0085] c) Configure a special header for authentication to prevent external malicious attacks from imitating the function trigger;

[0086] d) Randomly obtain the IP address corresponding to a special domain name to respond to script access and perform load balancing through random methods;

[0087] 4. Response to scheduled tasks at runtime

[0088] a) When accessing a special domain name, check whether it contains a token;

[0089] b) Access the corresponding artifact according to the wasm file address stored in the special header;

[0090] c) Return the response content of the script corresponding to the product file;

[0091] 5. Log collection and monitoring without domain name

[0092] a) Configure a special header to store the function ID, and bind subsequent function logs to the ID;

[0093] b) The function's response, traffic, and other information are bound to the user ID and script ID and reported to the monitoring system for data collection;

[0094] Through the method provided in this application, with the help of CDN and the deployment and distribution method of traditional edge functions, fixed-frequency function response is achieved, helping customers to realize customized function requirements and trigger frequency.

[0095] Applications in the field of function computing are as follows:

[0096] 1. Regularly back up and synchronize data to edge devices or cloud storage;

[0097] 2. Extract data from data sources and generate reports, then send the reports to relevant users or systems;

[0098] 3. Periodically trigger edge functions to check sensor status, perform device control operations, or perform device status monitoring;

[0099] 4. Regularly trigger edge functions to read data from sensors, and then perform real-time analysis and processing to promptly detect abnormal situations or optimize system performance;

[0100] 5. Edge functions can be triggered regularly to monitor device load conditions, and task allocation and resource allocation can be dynamically adjusted according to load conditions to achieve optimal resource utilization;

[0101] Application of this design

[0102] 1. Monitor the changes of scheduled tasks and update them in time, including the addition, deletion, frequency change, and task content change of scheduled tasks;

[0103] 2. Timed triggering of scripts without domain names reduces the complexity of domain name configuration and the workload of deployment;

[0104] 3. Ensure security when implementing timed trigger-type edge functions to prevent unauthorized access and operation. Use security measures such as token verification mechanisms to protect the security of edge functions.

[0105] 4. When executing scheduled tasks, include information such as the script ID and user ID, obtain logs and metrics, and report them to the monitoring center to help diagnose problems, optimize performance, and provide visualization and reporting of edge function execution;

[0106] Compared with traditional methods, this application has the following advantages and effects:

[0107] Precise control: Scheduled triggers allow edge functions to be triggered at specific intervals or at specific points in time. This allows for precise control over the execution time of functions, ensuring that tasks are executed within the scheduled time. This is very useful for scenarios where tasks need to be executed on a schedule, such as scheduled data collection and report generation.

[0108] Resource Saving: Timed triggers can avoid continuous consumption of computing resources. Edge devices typically have limited computing resources. By timing edge functions, functions can be started when tasks are needed and resources released after the tasks are completed. This approach can effectively save computing resources and improve resource utilization of edge devices.

[0109] Data synchronization: Scheduled triggers can be used to periodically collect, process, and synchronize data. For example, in IoT scenarios, edge functions can be periodically triggered to collect sensor data and perform real-time processing and analysis. This helps ensure the timeliness and consistency of data so that subsequent decisions and actions are based on the latest data.

[0110] Scheduled task scheduling: Scheduled triggers can be used to schedule edge functions to execute different tasks. By pre-determined time intervals or time points, different tasks can be scheduled to execute at appropriate times. This helps optimize the execution order and timing of tasks to maximize the efficiency and performance of the overall system.

[0111] Automated operation: Timed triggers automate the execution of edge functions without manual intervention. Edge functions can be automatically triggered and executed according to a predetermined schedule, which reduces the need for manual operation, improves the system's automation level, and reduces the risk of human error.

[0112] Domain-free triggering: Scheduled edge functions can be automatically triggered according to a predetermined schedule even without a domain name configuration. This simplifies domain name registration and DNS resolution, reduces the complexity of domain name configuration and deployment workload. End users or other systems do not need to worry about how edge functions are triggered; they only need to use the provided interfaces and services. This improves system security and maintainability, while simplifying external system integration and internal architecture adjustments.

[0113] In summary, these advantages of the timer trigger type edge function make task scheduling and data processing in the edge computing environment more efficient and reliable.

[0114] It is important to note that the construction and arrangement of the present application shown in a number of different exemplary embodiments are merely illustrative. Although only a few embodiments are described in detail in this disclosure, it should be readily understood by those reading this disclosure that many modifications are possible (e.g., the size, scale, structure, shape and proportion of various elements, as well as parameter values ​​(e.g., temperature, pressure, etc.), mounting arrangements, use of materials, color, changes in orientation, etc.) without materially departing from the novel teachings and advantages of the subject matter described in this application. For example, elements shown as integrally formed may be composed of multiple parts or elements, the positions of elements may be inverted or otherwise changed, and the nature or number or position of discrete elements may be altered or changed, and therefore, all such modifications are intended to be included within the scope of this application. The order or sequence of any process or method steps may be changed or reordered according to alternative embodiments. In the claims, any "means plus function" clause is intended to cover the structures described herein that perform the function, and not only structural equivalence but also equivalent structures. Without departing from the scope of the present application, other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments. Therefore, the present application is not limited to a specific embodiment, but extends to various modifications that still fall within the scope of the appended claims.

[0115] Additionally, in order to provide a concise description of example embodiments, all features of an actual embodiment (ie, those features not relevant to the best mode presently contemplated for carrying out the application or those not relevant to implementing the application) may not be described.

[0116] It will be appreciated that in the development of any actual embodiment, as in any engineering or design project, numerous implementation-specific decisions may be made. Such a development effort may be complex and time-consuming, but will, for those of ordinary skill having the benefit of this disclosure, be a routine undertaking of design, fabrication, and production without undue experimentation.

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

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

Claims

1. A method for implementing an edge function of a timing trigger type, characterized in that: The method is as follows: S1: Set up edge functions, rely on CDN for trigger-type edge functions, set the corresponding scripts and trigger frequency, and deploy and send the scripts to the edge environment; Create a scheduled task script and deploy it as follows: A1: Compile the script to generate the corresponding artifact file; A2: Send the product file to the global resource pool; S2: Triggering and updating of scheduled tasks. The task center obtains the scripts that need to be executed on a scheduled basis and has been successfully issued within ten minutes, and generates scheduled tasks with the same frequency. Scheduled tasks trigger the script content in a specific way to meet customer needs. S3: When the script is not bound to a domain name, it implements the response of the timed trigger type function; S4: Response to scheduled tasks and access authentication during runtime; S5: Data collection: collect and monitor logs without domain names to achieve data collection.

2. The method for implementing an edge function of a timing trigger type according to claim 1, characterized in that: The triggering and updating of the scheduled task in S2 are specifically as follows: B1: Take out the task scripts that meet the conditions and put them into cronMap every ten minutes; B2: Traverse the cronMap and start each scheduled task; B3: After ten minutes, take out the new data and compare it with the old data, mark the newly added content and add it to the scheduled task, mark the content to be deleted and stop the scheduled task.

3. The method for implementing an edge function of a timing trigger type according to claim 2, characterized in that: In B3, the changed scheduled tasks are accurately identified and the scheduled tasks are updated after marking.

4. The method for implementing an edge function of a timing trigger type according to claim 3, characterized in that: The specific steps of S3 are as follows: C1: Set a special domain name specifically for processing timer trigger type functions; C2: Configure a special header to store the address of the wasm file generated after the function is compiled; C3: Configure a special header for authentication to prevent external malicious attacks from imitating the function trigger; C4: Configure load balancing.

5. The method for implementing an edge function of a timing trigger type according to claim 4, characterized in that: The configuration of load balancing in the C4 is specifically to randomly obtain an IP corresponding to a special domain name for responding to script access, and perform load balancing through a random method.

6. The method for implementing an edge function of a timing trigger type according to claim 5, characterized in that: The specific steps of S4 are: D1: When the accessed domain name is a special domain name, check whether it has a token; D2: Access the corresponding product according to the wasm file address stored in the special header; D3: Returns the response content of the script corresponding to the product file.

7. The method for implementing an edge function of a timing trigger type according to claim 6, characterized in that: In the S5, to collect and monitor logs, a special header must be configured to store the function ID, and the subsequent function logs are bound to the ID.

8. The method for implementing an edge function of a timing trigger type according to claim 7, characterized in that: After the function log in S5 is bound to the id, the response, flow and other information of the function are bound to the user id and script id, and reported to the monitoring system for data collection.

9. The method for realizing an edge function of a timing trigger type according to claim 8, characterized in that: The edge function in S1 is used to regularly back up and synchronize data to edge devices or cloud storage, extract data from data sources and generate reports, and then send the reports to relevant users or systems. The edge function is used to distribute computing tasks to edge devices or edge nodes for execution to reduce data transmission and latency.

10. The method for realizing an edge function of a timing trigger type according to claim 9, characterized in that: The edge function in S1 is used to periodically trigger edge functions to check sensor status, execute device control operations or monitor device status, and to periodically trigger edge functions to read data from sensors, and then perform real-time analysis and processing to promptly detect abnormal situations or optimize system performance. It is also used to periodically trigger edge functions to monitor device load conditions, dynamically adjust task allocation and resource allocation according to load conditions, so as to achieve optimal utilization of resources, and a trigger is a mechanism used to trigger an operation or event at a specific time point or time interval.

Images