Code backpack system and code packaging method of AI graphical programming platform
By introducing a code backpack system into the graphical programming platform, the problem of inconvenience in code snippets and role management is solved, efficient code management and reuse is achieved, and programming efficiency and user experience are improved.
Patent Information
- Application Number
- CN202411455184.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-18
- Publication Date
- 2025-02-14
AI Technical Summary
The existing graphical programming platform lacks effective code snippets and role management tools, which leads to users who need to create repeatedly when using the same code snippets or roles multiple times, wasting time and prone to error introduction.
It provides a code backpack system for AI graphical programming platform, including collection modules and backpack management modules. Users can collect code snippets and roles and efficiently reuse them in the graphical programming platform through classification management functions.
Through the code backpacking system, users can easily manage and reuse code snippets and roles, reduce duplicate labor, improve programming efficiency, reduce error rates, and improve user experience.
Smart Images

Figure CN119440516A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer graphical programming, and in particular to a code backpack system and a code packaging method for an AI graphical programming platform. Background Art
[0002] With the widespread application of graphical programming in education and development, users often need to reuse certain code snippets or roles during programming. In order to improve programming efficiency and reduce repetitive work, it is particularly important to provide a convenient function for collecting and managing code snippets and roles. The current graphical programming platform lacks effective code snippet and role management tools, which causes users to repeatedly create the same code snippet or role when using it multiple times, which not only wastes time but also easily introduces errors.
[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention
[0004] The embodiments of the present invention provide a code backpack system and a code packaging method for an AI graphical programming platform, so as to at least solve the technical problem that the graphical programming platform lacks code snippets or role management.
[0005] According to one aspect of an embodiment of the present invention, a code backpack system of an AI graphical programming platform is provided, comprising: a collection module, configured to collect selected collection content, wherein the collection content includes code snippets and / or characters; a backpack management module, configured to classify the collection content and embed the classified collection content into the graphical programming platform.
[0006] According to another aspect of an embodiment of the present invention, a code packaging method for an AI graphical programming platform is also provided, comprising: collecting selected collection content, wherein the collection content includes code snippets and / or characters; classifying the collection content, and embedding the classified collection content into the graphical programming platform.
[0007] In an embodiment of the present invention, selected collection contents are collected, wherein the collection contents include code snippets and / or roles; the collection contents are classified, and the classified collection contents are embedded into the graphical programming platform, thereby solving the problem that the graphical programming platform lacks code snippet or role management technology. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:
[0009] Figure 1 is an architectural diagram of a code backpack system of a graphical programming platform according to an embodiment of the present invention;
[0010] Figure 2 is a flow chart of a code packaging method of a graphical programming platform according to an embodiment of the present invention;
[0011] Figure 3 is a flowchart of a collection processing method according to an embodiment of the present invention;
[0012] Figure 4 is a flowchart of a backpack management method according to an embodiment of the present invention;
[0013] Figure 5 is a flow chart of a data processing and multiplexing method according to an embodiment of the present invention. DETAILED DESCRIPTION
[0014] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.
[0015] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0016] Figure 1 The present invention is a code backpack system for a graphical programming platform according to an embodiment of the present invention. The code backpack system is used for a graphical programming platform to improve programming efficiency and user experience. The system provided by the present application allows users to easily collect, manage and reuse code snippets and roles, making it more efficient to reuse commonly used code blocks. Figure 1 As shown, the system includes a collection module 10 , a backpack management module 12 , and a data processing and multiplexing module 14 .
[0017] The collection module 10 is configured to collect the selected collection content, wherein the collection content includes code snippets and / or roles. Specifically, in response to receiving a collection instruction sent by the user through a right-click menu or a long-press operation, a collection pop-up window is popped up, and the collection pop-up window is used to prompt the user to fill in the description information of the code snippet or the role; in response to receiving the description information, the code snippet or the role is collected according to the description information.
[0018] A code snippet is a short code paragraph that can implement a specific function. A code snippet is a reusable block of program code that a developer writes or uses during the programming process. These code blocks are used to perform specific tasks or functions, have certain independence, and can be used in a specific programming environment or context. The main purpose of a code snippet is to improve programming efficiency, reduce duplication of effort, and reduce the probability of error. The code snippet in the embodiment of the present application mainly refers to the building blocks used in the graphical programming platform. In the graphical programming platform, building blocks are visual code representations that are used to simplify the programming process so that users can program without writing traditional text codes. Building blocks are presented in graphical modules or block structures (similar to building blocks), and users can combine these building blocks together to build program logic and functions through operations such as dragging and splicing.
[0019] The characters in the embodiments of the present application are one or more operable objects in a programming project in a graphical programming platform. The characters are visual and have specific appearances (such as pictures or animations) and behaviors (such as moving, rotating, speaking, etc.). During the programming process, users can control the actions, appearance changes, and interactions with other characters or backgrounds of these characters by writing codes or using building blocks.
[0020] The backpack management module 12 is configured to classify the collection content and embed the classified collection content into the graphical programming platform. Specifically, based on the classification result, the appearance and naming information of the building blocks corresponding to the code snippet and / or the thumbnail and attribute information of the character are displayed on the graphical programming platform; in response to receiving an editing instruction, the naming information and / or the attribute information are edited.
[0021] The backpack management module 12 is also configured to determine whether the number of selected collection contents exceeds a set threshold in response to receiving a content selection instruction, wherein the selection instruction is used to indicate one or more code blocks and / or roles selected by the user; if the number does not exceed the set threshold, the selected collection contents are added to the current project, otherwise, the user is prompted that the number exceeds the set threshold.
[0022] The data processing and reuse module 14 is configured to reuse the classified collection content, for example, to process cross-domain data conflicts, wherein the cross-domain data conflicts include duplicate variable names and / or missing resources.
[0023] The embodiments of the present application greatly improve programming efficiency and user experience by providing a unified platform for collecting, managing and reusing code snippets and roles. First, users can easily collect commonly used code snippets and roles in a backpack and reuse them at any time as needed, which reduces the time and workload of writing duplicate code and improves development efficiency. Secondly, the classification management function of the system enables users to find the required code snippets and roles more conveniently, enhancing the usability and user-friendliness of the platform. In addition, the data processing and reuse module further improves the compatibility and portability of code snippets and roles, avoids the problem of cross-domain data conflicts, and ensures the stability and reliability of the code. In summary, the graphical programming platform code backpack system of the present invention significantly improves the user's programming experience and development efficiency through efficient code management and reuse mechanisms.
[0024] The embodiment of the present application provides another code backpack system based on a graphical programming platform of a Web browser. The system aims to improve programming efficiency, reduce duplication of work, and ensure data consistency and system stability by collecting, managing and reusing code snippets and roles.
[0025] The system architecture is described below.
[0026] The system provided in the embodiment of the present application mainly includes the following three modules: a collection module, a backpack management module, and a data processing and reuse module.
[0027] The collection module is used by users to collect commonly used code snippets and roles. This module provides a convenient user interface, allowing users to collect commonly used code snippets and roles into the system through the right-click menu or long-press operation, and requires users to fill in the corresponding name and description information. This information is helpful for subsequent management and quick search.
[0028] The backpack management module is responsible for classifying and managing the user's favorite code snippets and roles. This module provides a unified interface to display all the favorite content, supports users to view, classify and manage the favorite code snippets and roles, and supports multi-select addition operations and re-editing functions, allowing users to flexibly manage and use the favorite content. Users can select code snippets or roles in batches and add them to the current programming project at one time.
[0029] The data processing and reuse module is configured to handle data conflicts, such as duplicate variable names, missing resources, etc., when users reuse favorite code snippets or roles in different projects. This module ensures data consistency and system stability through an automated data processing mechanism. It can automatically adjust variable names, resource paths, etc. to avoid data problems caused by cross-domain additions.
[0030] The following is a detailed description of the operation process of this system. Figure 2 As shown, the operation process includes the following steps:
[0031] Step S202, collection processing.
[0032] When a user creates a useful code snippet or role in the graphical programming platform, the user can right-click the code block or long-press the role, and the system will pop up a collection window, prompting the user to fill in the name and description of the code snippet or role. After confirmation, the code snippet or role will be added to the collection library for quick subsequent use. Figure 3 The specific steps are as follows:
[0033] Step S2022, select content.
[0034] The user selects the code snippets or characters that they want to collect. These code snippets or characters are presented in a modular form, such as building blocks (for code snippets) or operable objects (for characters). The user can mark these contents as favorite objects by clicking, dragging or other selection operations.
[0035] Step S2024, the system pops up a collection window, and the user fills in the name and description information.
[0036] Once the user selects the content to be collected, the system will automatically respond to this operation and pop up a collection window. This window is used to collect detailed information about the selected content for subsequent management and retrieval. The specific functions and operation steps of the collection window are as follows:
[0037] 1) Pop-up window: After the user selects the favorite content, the system immediately pops up a dialog box or window, which is designed to be easy for the user to operate.
[0038] 2) Fill in the name and description information. The collection window contains two main input fields: the name field and the description field. The user needs to enter a name for the selected content. The name is used to uniquely identify the code snippet or role, which is convenient for subsequent search and use. In addition, the user can enter a detailed description or notes about the content in the description field. The description information can include the purpose of the content, function description, usage precautions, etc., to help users or other project members better understand the function and application scenarios of the content.
[0039] 3) Input validation. The system can perform basic input validation to ensure that the information filled in by the user is complete and meets the format requirements. For example, the system requires that the name field cannot be empty, and the description field can be optional but should meet the character limit.
[0040] Step S2026: After the user confirms the collection, the system saves the content to the collection module and displays a success prompt.
[0041] When the user completes filling in the information in the collection window, the system provides a button to confirm the operation. The user clicks the button to complete the collection process. At this time, the system will perform the following operations:
[0042] 1) Save the content. The system saves the name, description, and selected code snippet or role filled in by the user to the collection module. The collection module is a database or data storage area that is specifically used to store all the content collected by the user and supports subsequent retrieval and management of these contents.
[0043] 2) Update the favorites list. After the save operation is completed, the system will update the favorites list to ensure that the newly collected content can be displayed in the user's collection library in a timely manner. The update of the favorites list enables the user to immediately see the newly collected code snippets or roles and perform further operations.
[0044] 3) Display a success prompt. To confirm the success of the collection operation, the system will display a success prompt message after the save operation is completed. This prompt message is usually presented in the form of a pop-up window, notification bar or status bar to inform the user that the collection operation has been successfully completed. This prompt can enhance the user's operation feedback experience and confirm that their collection operation has taken effect.
[0045] Through the above process, the code backpack system of the present invention can provide users with a simple and efficient way to manage commonly used code snippets and roles, greatly improving programming efficiency and optimizing user experience.
[0046] Step S204: backpack management.
[0047] Users can view all the collected code snippets and roles in the backpack management interface. The interface displays the collection content by category, and users can view and edit it as needed. Users can also select multiple code snippets or roles and add them to the current project in batches. If the collection content selected by the user exceeds the limit of the current project, the system will prompt the user to make corresponding adjustments. The specific operation process is as follows Figure 4 As shown, the following steps are included:
[0048] Step S2042, viewing and classification display.
[0049] After the user enters the backpack management interface, the system will display all the collected content according to the preset classification standards. These categories can include function type, purpose, creation time, etc. The content under each category will be displayed in a list or grid format for easy browsing by users.
[0050] The system organizes the collected code snippets and roles according to the preset classification standards. For example, they can be classified by functional module, project type or user-defined tags. The content displayed under each category includes the functional description of the code snippet, the thumbnail of the role, the name and related attributes.
[0051] Users can click on each code snippet or role to view its detailed information. This information usually includes the specific implementation instructions of the code snippet, usage examples, the animation effects of the role, interactive behaviors, etc., to help users understand and select the required content.
[0052] Step S2044, content review and re-editing.
[0053] In the backpack management interface, users can view and edit the collected code snippets and roles in detail to suit the needs of the current project. Users can view the complete description of each collection, including name, function, instructions, etc. Users can modify the name, description, and other related properties of the code snippet or role. The editing interface usually provides intuitive input boxes and editing tools, allowing users to quickly adjust the content. In this way, users can personalize the collection content according to the specific needs of the project.
[0054] Step S2046, batch operation.
[0055] The backpack management interface supports batch selection and operation functions, which greatly improves the user's operation efficiency, especially when multiple collections need to be added at the same time. Specifically, users can select multiple code snippets or roles by checking boxes or multi-select tools. After selecting, users can perform batch operations, such as adding to the current project at one time. Multiple collections selected by the user can be added to the current programming project at the same time. In this way, the adding process can be simplified and the time for repeated operations can be reduced.
[0056] Step S2048, add restrictions and prompts.
[0057] During the batch adding process, the system will check whether the selected content meets the restrictions of the current project. If the selected content exceeds these restrictions, the system will provide corresponding prompts and suggestions. The restrictions include the maximum number of code snippets, roles, resource capacity, etc. allowed to be added to the current project. When the content selected by the user exceeds the limit, the system will pop up a prompt window or dialog box to inform the user that the number of selected content exceeds the limit and provide adjustment suggestions or operation guidelines. The prompt information includes suggestions to reduce the number of selections, adjust project settings, or optimize the current project.
[0058] Through the above functions, the backpack management interface not only provides a centralized management platform that allows users to easily view and edit collected content, but also significantly improves operational efficiency and system stability through batch operations and automatic limit prompt functions, thereby greatly optimizing the user's workflow in the graphical programming platform and improving programming efficiency and user experience.
[0059] Step S206: data processing and multiplexing.
[0060] When users add favorites to a new project, the system will automatically detect and handle cross-domain data conflicts, such as duplicate variable names, missing resources, etc. The system ensures data consistency by adjusting variable names, updating resource paths, etc. At the same time, the system will automatically initialize the required building blocks and resources to ensure that the code snippets or roles can run normally in the new project. Figure 5 As shown, data processing and multiplexing includes the following steps:
[0061] Step S2062: automatically detect and process cross-domain data conflicts.
[0062] When a user adds a favorite code snippet or role to a new project, the system will first automatically perform a data conflict detection operation. In this way, various data conflict issues that may be caused by cross-project reuse can be identified. Data conflicts include but are not limited to duplicate variable names and missing resources. Code snippets in different projects may use the same variable names, which will cause variable overwriting or undefined situations when these code snippets are loaded and run in the new project. In addition, some code snippets or roles rely on specific resource files (such as images, audio, or external libraries). If these resources do not exist in the target project, reference errors or runtime exceptions will result.
[0063] To resolve the above data conflict problem, the system will automatically perform the following processing steps:
[0064] 1) Variable renaming. For detected variable duplication problems, the system will automatically generate unique variable names based on predefined rules (such as appending the project name or random characters to the original variable name) and update these new variable names in all references of the code snippet. This can effectively avoid variable overwriting and conflict issues.
[0065] 2) Update resource paths. For conflicts caused by missing resources, the system will automatically search the resource library of the current project. If the target resource does not exist, the system will try to copy the required resource file to the project and update all references to related resource paths in the code snippet. In this way, the availability and correctness of resources are ensured.
[0066] Step S2064: Data consistency and system stability
[0067] To further ensure data consistency and system stability, the system also performs data verification and integrity checks during the addition process. The system verifies the integrity of code snippets and roles to ensure the correctness of all dependencies and references. For example, if a code snippet depends on a specific function library or external module, the system checks whether these dependencies are available in the target project and imports and configures them if necessary. In addition, the system resolves the dependencies between code snippets and roles to ensure that all interdependent modules are loaded and initialized correctly. This parsing mechanism can effectively prevent errors caused by loading order or missing dependencies.
[0068] Traditional dependency checking simply checks whether there is a direct dependency between modules or components, but in complex systems, dependencies may be multi-layered, involving mutual dependencies between multiple modules. In order to address this complexity, this embodiment uses a dependency graph to represent the dependencies between modules. A directed graph is used to represent the dependencies between modules, where each node represents a module and the edge represents the dependencies between modules. Then, a topological sorting algorithm is used to sort the dependency graph. Ensure that for each directed edge (U, V), node U (depending party) is ranked before node V (dependent party).
[0069] Specifically, based on the traditional topological sorting algorithm, the present application adopts the following improved topological sorting method for large-scale complex dependency graphs and dynamic changes.
[0070] 1) Multi-level priority queue.
[0071] In traditional topological sorting, all nodes with zero in-degree are added to a simple initial queue. The improved scheme of the present application uses a multi-level priority queue to further distinguish and sort these nodes according to the loading priority, computing resource requirements, and potential execution time of the nodes. Nodes with zero in-degree are assigned to different priority queues according to priority (e.g., loading time, resource occupancy, importance of dependency, etc.). And in the sorting process, the priority of each node is dynamically adjusted according to the current system load and resource status, thereby optimizing the entire dependency resolution process.
[0072] 2) Parallel loading based on batch processing.
[0073] In the traditional method, the loading of nodes is carried out sequentially, while the improved scheme of this application supports parallel loading based on batch processing. All nodes with current in-degree of zero are divided into multiple batches at one time and loaded in parallel. In each batch, the system can parse and load multiple nodes without dependencies in parallel, thereby making full use of multi-core processors and parallel computing resources. This method greatly reduces the loading time and can significantly improve the startup speed and response time of the system.
[0074] 3) Real-time loop detection and partial reordering
[0075] Traditional topological sorting only performs cycle detection after the sorting is completed. The present application performs cycle detection in real time during the sorting process, and supports partial reordering to handle circular dependencies. Specifically, each time an edge is removed and the node in-degree is updated, it is immediately detected whether there is a new circular dependency. Once a circular dependency is detected, the sorting process is not terminated immediately, but local dependency reordering or ring-breaking operations are performed by analyzing the strength and association of the circular dependency. In this way, circular dependencies can be detected and handled earlier, avoiding problems until the end of the sorting, thereby reducing the time and resources required to correct errors.
[0076] 4) Utilize dependency weight and dependency propagation delay optimization.
[0077] In traditional schemes, all edge weights are considered equal. The present application optimizes the loading process through dependency weights and dependency propagation delays. Specifically, a weight is set for each edge, representing the importance of the dependency or the priority of data transmission. The edge weight can be dynamically adjusted based on the access frequency of the module, the amount of data transmission, the computing requirements, etc. After each module is loaded, the delay time of its dependency propagation is recorded and predicted, and the module loading order is optimized to minimize the overall delay. In this way, the sorting process can be made more efficient and flexible, and can adapt to the dynamically changing complex system environment.
[0078] Step S2066, automatic initialization and compatibility assurance.
[0079] After data processing and verification are completed, the system will automatically perform initialization operations to ensure the normal operation of the code snippet or role in the new project. For code snippets in the graphical programming platform, the system will automatically initialize the required building blocks. These building blocks usually contain visual code blocks and functional components to ensure that users can successfully call and use these code snippets in new projects. The system will also automatically load and initialize the resources required by the code snippet or role, such as images, audio, and external data files. In this way, the normal presentation and interaction effects of the code snippet or role in the new project can be guaranteed. For specific code snippets or roles, the system may need to adjust some environment configurations, such as screen size, background color, or default parameters, according to the characteristics of the target project. The system will automatically detect these configuration differences and make adjustments when necessary to ensure the compatibility and optimal performance of the code snippet or role.
[0080] During the entire data processing and reuse process, the system will provide users with operation prompts and feedback information in real time. Including: If any data conflict is detected during the addition process (such as duplicate variable names or missing resources), the system will pop up a warning window to describe the specific conflict to the user and provide optional solutions (such as automatic renaming or manual adjustment). After the data processing, verification and initialization are successfully completed, the system will display a success prompt message to the user to confirm that the collection content has been successfully added to the new project and can run normally.
[0081] Through the above steps and mechanisms, the code backpack system of the present invention can efficiently and intelligently handle the complex situation of cross-project data reuse, ensure data consistency and system stability, and significantly improve the user experience and development efficiency of the graphical programming platform.
[0082] The embodiments of the present application improve the work efficiency of users in the graphical programming process, and enable quick call and reuse of commonly used code snippets and roles by providing convenient collection and management tools. At the same time, it reduces duplication of work and human errors, and ensures data consistency by automatically handling cross-domain data issues, thereby improving system stability and reliability. In addition, the present application also provides a more user-friendly experience, and enables users to manage and use the collected content more flexibly through the multi-select addition and re-editing functions.
[0083] As another aspect, the present application further provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device.
[0084] The computer-readable medium carries one or more programs, and when the one or more programs are executed by an electronic device, the electronic device implements the method described in the following embodiments. For example, the electronic device can implement each step of the method embodiment.
[0085] As another aspect, the present application further provides an electronic device, comprising: at least one processor; and a memory connected to the at least one processor in communication. The memory stores a computer program executable by the at least one processor, and the computer program is used to enable the electronic device to perform the method of the embodiment of the present application when executed by the at least one processor.
[0086] As another aspect, the present application further provides a computer program product, including a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute the method of the embodiment of the present application.
[0087] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. A code backpack system for an AI graphical programming platform, characterized in that: include: A collection module, configured to collect selected collection content, wherein the collection content includes code snippets and / or roles; The backpack management module is configured to classify the collection content and embed the classified collection content into the graphical programming platform.
2. The system according to claim 1, characterized in that The code backpack system also includes a data processing and reuse module, which is configured to reuse the classified collection content.
3. The system according to claim 1, characterized in that The collection module is also configured to: In response to receiving a collection instruction sent by the user through a right-click menu or a long-press operation, a collection pop-up window is popped up, where the collection pop-up window is used to prompt the user to fill in the description information of the code snippet or the role; In response to receiving the description information, a collection operation is performed on the code snippet or the role according to the description information.
4. The system according to claim 1, characterized in that The backpack management module is also configured as follows: Based on the classification result, displaying the appearance and naming information of the building blocks corresponding to the code snippet, and / or the thumbnail and attribute information of the character on the graphical programming platform; In response to receiving the editing instruction, the naming information and / or the attribute information is edited.
5. The system according to claim 4, characterized in that The backpack management module is also configured as follows: In response to receiving a content selection instruction, determining whether the number of selected collection contents exceeds a set threshold, wherein the selection instruction is used to indicate one or more code blocks and / or roles selected by a user; If the number does not exceed the set threshold, the selected favorite content is added to the current project; otherwise, the user is prompted that the number exceeds the set threshold.
6. The system according to claim 2, characterized in that The data processing and reuse module is further configured to handle cross-domain data conflicts, wherein the cross-domain data conflicts include duplicate variable names and / or missing resources.
7. A code packaging method for an AI graphical programming platform, characterized in that: include: Collecting the selected collection content, wherein the collection content includes code snippets and / or roles; The collection contents are classified, and the classified collection contents are embedded into the graphical programming platform.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to claim 7.
9. A computer device, characterized in that: include: Memory and processor, The memory stores a computer program; The processor is used to execute the computer program stored in the memory, and the computer program enables the processor to execute the method according to claim 7 when running.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to claim 7 are implemented.