Graphical intent driven modeling system and method for modeling telemetry services templates

Abstract

The application discloses a kind of based on graphics intention drive's measurement and control service template modeling system and method, belong to the field of space measurement and control, include: graphics intention expression layer module, intention analysis layer module and template library management layer module;Graphics intention expression layer module is used to provide graphical interface, expresses measurement and control service template construction intention;Intention analysis layer module is used to understand the intention of user measurement and control service graphical expression, verifies its correctness, and generates measurement and control service template description file;Template library management layer module is used to provide the whole life cycle management of template, supports the storage, retrieval, version control and reuse of template.The application enhances the response capability of system to task change, improves construction efficiency, guarantees the correctness and integrity of template, improves system stability.

Description

Technical Field

[0001] This invention relates to the field of aerospace telemetry and control, and more specifically, to a modeling system and method for telemetry and control service templates based on graphical intent-driven approaches. Background Technology

[0002] To meet the demands of large-scale satellite networking for on-demand allocation, flexible deployment, and rapid upgrades of future telemetry, tracking, and command (TT&C) ground stations, satellite TT&C systems are evolving towards a "cloud-based TT&C" architecture. While existing cloud-based TT&C solutions achieve resource allocation and deployment by template-based representation of virtualized function lists for TT&C services such as noncoherent spread spectrum, medium- and low-speed data transmission, and high-speed data transmission, these template-based modeling methods have significant shortcomings when facing the wide range of TT&C business applications, diverse functional implementations, strong function reusability, and flexible configuration of function chains. (1) The template abstraction level is simple: the existing template technology takes the complete measurement and control function as the smallest granularity, lacks the hierarchical abstraction of working system, measurement and control function and atomic components, and cannot effectively describe the hierarchical structure of measurement and control services under different working systems, resulting in limited template reusability and adaptability; (2) Template construction relies on manual coding: The current template definition is mainly based on text configuration file XML / JSON format, which requires users to be proficient in both measurement and control business and template syntax. This method is difficult to intuitively express the data flow and processing logic between measurement and control functions. In particular, it is inefficient and prone to errors when facing complex signal link processing scenarios. (3) Insufficient component management: The existing solution lacks standardized encapsulation and unified interface specifications for atomic components. The component deployment specifications are tightly coupled with the functional implementation, which hinders fine-grained functional reuse and flexible combination. (4) Insufficient template verification mechanism: There is a lack of automated verification methods for the consistency, completeness and legality of template configurations. The quality of templates is highly dependent on human experience, which affects the reliability of the system.

[0003] These problems severely restrict the rapid construction of measurement and control service templates and the reliable operation of service instantiation. Therefore, a template construction technology solution that supports graphical modeling, hierarchical abstraction, and automated verification is needed. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a graphical intent-driven measurement and control service template modeling system and method, which enhances the system's responsiveness to task changes, improves construction efficiency, ensures the correctness and integrity of the template, and improves system stability.

[0005] The objective of this invention is achieved through the following solution: A graphical intent-driven measurement and control service template modeling system includes: a graphical intent expression layer module, an intent parsing layer module, and a template library management layer module; The graphical intent expression layer module is used to provide a graphical interface to express the intent of constructing the measurement and control service template; The intent parsing layer module is used to understand the intent expressed graphically by the user's measurement and control service, verify its correctness, and generate a measurement and control service template description file. The template library management layer module is used to provide full lifecycle management of templates, supporting template storage, retrieval, version control, and reuse.

[0006] Furthermore, the provision of a graphical interface to express the intent of constructing the measurement and control service template specifically includes: firstly, editing the measurement and control function templates and the dependencies between function templates through a graphical canvas and drag-and-drop arrangement engine via a visual template library navigation and selector; secondly, configuring the attributes of measurement and control functions, service templates, and atomic-level components through an attribute configuration panel; and finally, generating a graphical intent model file after successful verification.

[0007] Furthermore, the process of understanding the intent of the user's graphical representation of the measurement and control service, verifying its correctness, and generating a measurement and control service template description file specifically includes: parsing the JSON / XML structure of the graphical model generated by the graphical intent expression layer module through a model semantic extractor, extracting the measurement and control function relationship topology graph, identifying business semantics including phase-locked loop, modulation, demodulation, and decoding, identifying component relationships by a dependency analyzer, including startup order dependencies and data flow transmission paths, and then performing integrity verification and business specification verification on each component, component relationships, and measurement and control function relationships by a consistency verification engine. After successful verification, a standardized template description file that can be recognized by various resource pools is generated by a model description file generator, and the standardized template description file contains complete configuration parameters and deployment specifications.

[0008] Furthermore, the module provides full lifecycle management of templates, supporting template storage, retrieval, version control, and reuse. Specifically, it includes: a hierarchical template storage repository that stores work system templates, measurement and control function templates, and atomic component repositories according to a hierarchical principle; template version control that manages versions of various templates and supports rollback and upgrades; template classification and retrieval that classifies and retrieves templates according to keywords, application areas, and resource requirements; and template usage statistics and recommendations that rank popular templates and recommend templates based on historical similarity.

[0009] Furthermore, in the graphical intent expression layer module, the graphical interface specifically includes three areas: the left side is the template library navigation area, the middle part is the graphical canvas, and the right side is the attribute configuration panel.

[0010] Furthermore, the template library navigation area specifically includes: a working system template library, a measurement and control function template library, and an atomic component toolbox; The work system template library is used to manage top-level templates, including work system types and the creation, deletion, modification, and querying of templates under that work system type; The measurement and control function template library is used to manage measurement and control function templates, including the creation, deletion, modification and query of function units; The atomic component toolbox is used to manage virtualization components, including the creation, deletion, modification, and querying of virtualization components.

[0011] Furthermore, the graphical canvas specifically includes: an upper canvas, a middle canvas, and a lower canvas; The upper canvas is used to display a working system service template formed by combining multiple measurement and control function modules and configuring the measurement and control function forwarding chain through a directed connection graph. The intermediate canvas is used to demonstrate that when a certain measurement and control function is selected in the service template construction of the upper canvas, an internal view can be entered; the internal view shows how to drag and drop multiple components from the atomic component toolbox and connect them to form a measurement and control function template. The lower canvas is used to display the component creation process, including defining the component name, using icons, and describing the component's functions. Once created, it forms a column in the atomic component toolbox of the template library navigation area, specifically including the component name and component identifier.

[0012] Furthermore, the attribute configuration panel specifically includes: an attribute configuration panel and attribute controls, which are used to configure attributes, including service template attribute configuration, measurement and control function template attribute configuration, and atomic component attribute configuration.

[0013] Furthermore, the service template attribute configuration specifically includes: service template basic information configuration, external input point configuration, external output point configuration, measurement and control function forwarding chain configuration, and scheduling strategy configuration; The basic information configuration of the service template specifically includes: the service template's working system, target number, version number, creation time, creator, creation department, and application field; wherein, the working system is selected via a drop-down list; the target number and version number are entered via text boxes; the creation time is automatically filled with the current time via a time page component element; the creation department and creator are selected via drop-down lists; and the application field is selected via a drop-down list; the drop-down list options include UAV telemetry and control, space-based telemetry and control, ground-based telemetry and control, and sea-based telemetry and control; The configuration of external input points specifically includes: the requirements for external data access to the measurement and control service template include the communication protocol TCP / UDP / HTTP, the access port range, bandwidth requirements, latency requirements, and IP range; among which, the communication protocol is selected using a drop-down box, the port range is filled in using the start and end range page elements, and the bandwidth and latency requirements are configured using text boxes, with the bandwidth requirements divided into multiple levels; The configuration of the external output point specifically includes: the output requirements after the measurement and control service template is processed, including the communication protocol TCP / UDP / HTTP, the output port range, bandwidth requirements, latency requirements, and IP range; wherein, the communication protocol is selected using a drop-down list, the port range is filled in using the start and end range page elements, and the bandwidth and latency requirements are filled in using text boxes; The configuration of the measurement and control function forwarding chain specifically includes: configuration through multiple arrow connection relationships, and the bandwidth and latency requirements under the connection point are configured using text boxes; The scheduling strategy configuration specifically includes: the strategy configuration used when the service template is instantiated, specifically including lowest cost, lowest power consumption, load balancing and high security, and the scheduling strategy list is configured through a drop-down box.

[0014] Furthermore, the measurement and control function template attribute configuration specifically includes: measurement and control function template basic information configuration, input point configuration, output point configuration, atomic component forwarding chain configuration, and atomic component startup order dependency configuration; The basic information configuration of the measurement and control function template specifically includes: the measurement and control function name, measurement and control function description, and basic parameter information are all configured through text boxes; The configuration of input points for external measurement and control functions includes: the communication constraints for external measurement and control functions as clients accessing this measurement and control function. The specific configuration is as follows: <Measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. Among them, the communication protocol is selected using a drop-down list, and the communication protocol includes TCP / UDP. The port range is filled in using the start and end range page elements. The bandwidth requirement and latency requirement are filled in using text boxes. This measurement and control function configures the external output points of external measurement and control functions. Specifically, it defines the communication constraints for this measurement and control function to access external measurement and control functions. The specific configuration is as follows: <Next measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. The communication protocol is selected using a dropdown menu, the port range is entered using the start and end range page elements, and the bandwidth and latency requirements are filled in using text boxes. The protocol between this measurement and control function and the next measurement and control function should be consistent. Within this measurement and control function, the atomic component forwarding chain configures related components using a <component A, component B, bandwidth, delay> structure to form communication constraints between two components A and B. This results in a list of communication constraints between N components: <component A, component B, bandwidth, delay>, <component B, component C, bandwidth, delay>, <component C, component D, bandwidth, delay>, ..., <component N, component N-1, bandwidth, delay>, forming an atomic forwarding chain. Configuration is achieved using a combination of text boxes and arrows. Within the <component A, component B, bandwidth, delay> communication constraint structure, components A and B interact with each other, maintaining a consistent communication protocol. The atomic component startup order dependency graph is {<atomic component 1, startup level 1>, <atomic component 2, startup level 2>, <atomic component 3, startup level 3>, <atomic component 4, startup level 3>, ..., <atomic component N, startup level N>}. Component lists formed by components at different startup levels are {<startup level 1, (<atomic component 1, atomic component I, ...>)>, <startup level 2, (<atomic component 2, atomic component K, ...>)>, <startup level 3, (<atomic component 3, atomic component 4, ...>)>, ...}. Components with lower startup levels must be started first. Atomic components at the same startup level have no startup order and can be started freely. Configuration is done using a combination of text boxes and arrows. Text boxes are used for startup level configuration, and arrows represent dependencies between components. The component at the tail of the arrow depends on the component it points to.

[0015] Furthermore, the attribute configuration of the atomic component specifically includes: basic information configuration of the atomic component, specifically including basic information configuration, business parameter configuration, deployment specification configuration, and virtualization form configuration; The basic information configuration specifically includes: atomic component name and atomic component function description, and basic parameter information is configured through text boxes; The service parameter configuration specifically includes: service-level parameters, which include transmission frequency, reception frequency, sampling rate, modulation method, and decoding method; among which, discontinuous attributes are configured through text boxes, and optional items are configured through drop-down lists; The deployment specifications include: CPU core requirements, whether a GPU is needed, the number of GPUs required, whether an FPGA is needed, the number of FPGA resources required, the number of memory requirements, and the number of storage volumes required. The number of CPU cores, the number of FPGAs required, and the number of memory requirements are configured via text boxes; the requirement for a GPU and FPGA is configured via checkboxes. The virtualization form specifically includes the configuration of bare metal binary files, virtual machine images, and container images. The virtualization form is configured through a drop-down list and is used to determine the form in which components are deployed on the cloud platform when the service template is instantiated. Bare metal uses a script to start the bare metal binary executable file, virtual machine images are started by calling the cloud platform virtual machine image interface, and container images are started by calling the cloud platform container POD start interface.

[0016] A graphical intent-driven measurement and control service template modeling method, based on the graphical intent-driven measurement and control service template modeling system described in any of the preceding claims, includes the following steps: Step 1, Initialization Phase: First, determine the working system to which the measurement and control service template to be built belongs, providing a framework for subsequent function selection; Step 2, Function Acquisition Phase: Check if there are any available measurement and control function templates in the template library. If not, proceed to the measurement and control function template construction process; if so, proceed to the service assembly phase. Step 3, Service Assembly Phase: Add the selected or newly created function template to the service canvas, and then execute: Measurement and control function chain configuration: The data flow between measurement and control functions is defined by connecting them to form a measurement and control function chain forwarding diagram <Measurement and control function 1, Measurement and control function 2, Communication service type, Communication protocol, Bandwidth, Delay>, <Measurement and control function 2, Measurement and control function 3, Communication service type, Communication protocol, Bandwidth, Delay>, ..., <Measurement and control function N-1, Measurement and control function N, Communication service type, Communication protocol, Bandwidth, Delay>; Configure service parameters: Configure global parameters for the entire service template, including supported frequency bands, number of targets, sampling rate, supported service functions and application areas; Step 4: The intent parsing module enters the verification and optimization phase. It determines whether the current service template meets the expected business requirements. If it does not meet the requirements, it returns for adjustment. If it meets the requirements, it enters the integrity verification phase. In the integrity verification phase, the template is checked for technical integrity and the template configuration is continuously optimized through feedback loop to ensure the quality of the final result. Step 5, Completion Stage: Save the verified graphical service template to the template database for subsequent reuse, and for instantiation of the measurement and control service when the center's work plan / measurement and control task is issued; Step 6, Service Instantiation Phase: When the telemetry, tracking, and command center issues satellite work plans or telemetry, tracking, and command tasks to the ground station, the ground station manages and receives the plan, parses the plan, and intelligently matches the corresponding service template files in the template library according to the telemetry, tracking, and command links and data transmission links configured in the plan. This process involves reorganizing resources within the ground station's resource pool and scheduling and deploying atomic components.

[0017] Furthermore, in step 2, the measurement and control function template construction process specifically includes the following sub-steps: First, select components: choose atomic components from the atomic component library; Then, configure the data flow: establish signal processing links between components to form a component link forwarding graph <Component 1, Component 2, communication service type, communication protocol, bandwidth, latency>, <Component 2, Component 3, communication service type, communication protocol, bandwidth, latency>, ..., <Component N-1, Component N, communication service type, communication protocol, bandwidth, latency>; Next, set the parameters: configure the measurement and control function service parameters and deployment specification parameters; Finally, verify and save: After verifying that the functional logic is correct, save it as a new measurement and control function template.

[0018] Further, in step 4, the integrity verification specifically includes: Template required parameters are checked, specifically including required parameters for functional templates; required parameters for components; and required parameters for service templates. Business parameter range check, specifically including the legality check of the input frequency points of the measurement and control function and the S / L / X / KA frequency band range of the service template configuration, and the legality check of the discrete state of link establishment between components; Data type checks specifically include bit error rate test result type checks, frame synchronization code hexadecimal data type checks, and ranging and velocity measurement result type checks. The verification of the measurement and control protocol compliance includes, in particular, checking the semantic consistency between the UDP and HTTP protocols of the digital front-end and signal processing functions; checking the protocol consistency between the signal processing functions and the monitoring; and checking the protocol between telemetry data and storage devices. Verification of the integrity of the telemetry and control function forwarding chain specifically verifies the consistency of communication protocols, chain establishment parameters, and bandwidth between adjacent telemetry and control functions; as well as the link consistency verification between the telemetry and control function and the uplink and downlink channels of the digital front end, and the verification of gaps in the forwarding chain.

[0019] The beneficial effects of this invention include: (1) This invention proposes a hierarchical abstraction and intent-driven overall architecture. Through the three-level abstraction of working system, measurement and control function and components, a hierarchical architecture of "graphic expression - intent parsing - template management" is established, which solves the problem of traditional templates being single-level and having poor adaptability, and greatly enhances the system's ability to respond to task changes.

[0020] (2) This invention is the first to create a graphical modeling interface for the field of measurement and control. It replaces traditional text encoding with intuitive operations such as drag and drop and connecting lines, supports the configuration of complex data streams, solves the problems of unintuitive expression and easy error in configuration of traditional methods, and improves the construction time of measurement and control service templates from "days" to "hours", significantly improving the construction efficiency.

[0021] (3) This invention proposes a standardized model building process, designs a progressive modeling process of "component-function-service template", integrates a real-time verification mechanism, solves the problem of traditional template quality relying on manual labor and low reliability, ensures the correctness and integrity of the template, and improves system stability. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a system overall block diagram according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the graphical modeling interface of the system in an embodiment of the present invention; Figure 3 This is a flowchart illustrating the construction process of the measurement and control service template in an embodiment of the present invention. Detailed Implementation

[0024] All features disclosed in all embodiments of this specification, or steps in all methods or processes implied in the disclosure, may be combined and / or extended or replaced in any way, except for mutually exclusive features and / or steps.

[0025] It should be noted that relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0026] As a first aspect of the present invention, a hierarchical decoupling approach is adopted to design an overall architecture for a measurement and control service template modeling system based on graphical intent-driven principles. An embodiment provides a measurement and control service template modeling system based on graphical intent-driven principles, such as... Figure 1 As shown, it includes a graphical intent expression layer module, an intent parsing layer module, and a template library management layer module, which are described in detail below: (1) Graphical Intent Expression Layer Module: This module provides users with an intuitive and easy-to-use graphical interface, supporting the expression of measurement and control service template construction intent through drag-and-drop, connection, and other methods. First, the visual template library navigation and selector edit the measurement and control function templates and the dependencies between function templates through the graphical canvas and drag-and-drop arrangement engine. Then, the attribute configuration panel configures the attributes of measurement and control functions, service templates, and atomic-level components. Finally, after successful verification, a graphical intent model file is generated.

[0027] (2) The intent parsing layer module understands the intent of the user's graphical expression of the measurement and control service, verifies its correctness, and generates a standardized measurement and control service template description file. The model semantic extractor parses the JSON / XML structure of the graphical model generated by the graphical intent expression layer, extracts the measurement and control function relationship topology, and identifies business semantics including phase-locked loop, modulation, demodulation, decoding, etc. The dependency relationship analyzer identifies component relationships including startup order dependency relationships, data flow transmission paths, etc. Then, the consistency verification engine performs integrity verification and business specification verification on each component and component relationships, measurement and control function relationships, etc. After successful verification, the model description file generator generates a standardized template description file that can be recognized by various resource pools (virtual machine pool, container pool, bare metal pool), containing complete configuration parameters and deployment specifications.

[0028] (3) Template library management layer module, which provides full lifecycle management of templates and supports template storage, retrieval, version control and reuse. It consists of a hierarchical template storage repository, template classification and retrieval, template version control, and template usage statistics and recommendations. The hierarchical template storage repository stores the work system template library, the measurement and control function template library and the atomic component library according to the hierarchical principle; the template version control manages the versions of various templates and supports rollback and upgrade; the template classification and retrieval classifies and retrieves templates according to keywords, application fields, resource requirements, etc.; the template usage statistics and recommendations recommend templates based on popular template rankings and historical similarity.

[0029] Furthermore, Figure 2 This is a schematic diagram of graphical modeling of a service template driven by graphical intent, according to an embodiment of the present invention. Figure 2 As can be seen, it comprises three areas: the left side is the template library navigation area, the middle is the graphical canvas (main workspace), and the right side is the property configuration panel. More specifically, each area of ​​the interface is described in detail below: (a) Left side: Template library navigation area.

[0030] Operating System Template Library: Manages top-level templates, including operating system types (e.g., noncoherent spread spectrum, medium-low speed, etc.), and allows creation (+), deletion (-), modification (#), and querying of templates under that operating system type. wait.

[0031] Measurement and Control Function Template Library: Manages measurement and control function templates, including creating, deleting, modifying, and querying functional units (such as "carrier acquisition", "pseudocode synchronization", "telemetry decoding", etc.). wait.

[0032] Atomic Component Toolbox: Manages the most basic virtualization components (such as "DDC", "NCO", "ViterbiDecoder", etc.), including component creation (+), deletion (-), modification (#), and querying. .

[0033] (ii) Middle section: Graphical canvas (main work area), consisting of upper canvas, middle canvas and lower canvas.

[0034] Upper Canvas: Service Template Construction Content: This demonstrates how to combine multiple "measurement and control function" modules and configure the measurement and control function forwarding chain through a directed connection graph to form a working system service template.

[0035] Intermediate Canvas: Functional Template Construction Content: This section demonstrates how double-clicking a "Testing and Control Function" in the upper-level canvas-service template construction opens an internal view. This view shows how to drag and drop multiple components from the "Atomic Component Toolbox" and connect them to form the testing and control function template.

[0036] Lower Canvas: Atomic Component Construction Content: This demonstrates the component creation process, including defining the component name, using an icon, and describing the component's functionality. Once created, the component is listed in a column in the Atomic Component Toolbox of the template library navigation area, including the component name and component identifier.

[0037] (III) Right side: Property configuration panel and property control. The property control is used to configure properties, including service templates, measurement and control function templates, and atomic component property configurations, as detailed below: Service template attribute configuration: This includes configuration of basic service template information, external input points, output points, measurement and control function forwarding chains, scheduling strategies, etc. After selecting a service template in the upper-level canvas, you can configure that service template.

[0038] Service template basic information configuration: Service template working mode (medium-low speed / non-coherent spread spectrum / high-speed data transmission / standard mode / spread spectrum / anomaly detection / active / passive detection, etc.), target number, version number, creation time, creator, creation department, and application field; where working mode is selected via drop-down list, target number and version number are entered via text boxes, creation time is automatically filled with the current time via the time page component element, creation department and creator are selected via drop-down list, and application field is selected via drop-down list options include UAV telemetry and control, space-based telemetry and control, ground-based telemetry and control, sea-based telemetry and control, etc.

[0039] External input point configuration: The requirements for external data access to this measurement and control service template include the communication protocol (TCP / UDP / HTTP, etc.), the range of access ports, bandwidth requirements, latency requirements, IP range, etc. The communication protocol is selected using a drop-down list, the port range is filled in using the start-end range page element, and the bandwidth and latency requirements are configured in text boxes. The bandwidth requirements are divided into multiple levels, including 1Gbps, 2Gbps, 40Gbps, and 100Gbps.

[0040] External output point configuration: The output requirements after the measurement and control service template is processed include the communication protocol used (TCP / UDP / HTTP, etc.), the output port range, bandwidth requirements, latency requirements, IP range, etc. The communication protocol is selected using a drop-down list, the port range is filled in using the start-end range page element, and the bandwidth and latency requirements are filled in text boxes.

[0041] The configuration of the telemetry and control function forwarding chain (arrow flow direction between adjacent telemetry and control functions, bandwidth requirements, etc.) is configured through multiple arrow connection relationships, while the bandwidth and latency requirements under the connection point are configured using text boxes.

[0042] Scheduling strategy configuration: The strategy configuration used when instantiating the service template includes lowest cost, lowest power consumption, load balancing, high security, etc. The scheduling strategy list is configured through a drop-down box.

[0043] Measurement and control function template attribute configuration: This includes basic information configuration for the measurement and control function template, input point (external access point), output point (external output point), atomic component forwarding chain configuration, and atomic component startup order dependency configuration. Select the target measurement and control template in the intermediate canvas to configure its attributes, as follows: Basic information configuration for measurement and control function template: Measurement and control function name (modulator / demodulator / decoder, etc.), measurement and control function description, and basic parameter information are all configured through text boxes.

[0044] External measurement and control function input point configuration: The external measurement and control function input point configuration refers to the communication constraints for the external measurement and control function as a client to access this measurement and control function. The specific configuration is as follows: <Measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. The communication protocol is selected from the drop-down list, including TCP / UDP. The port range is filled in using the start-end range page element. The bandwidth requirement and latency requirement are filled in the text boxes.

[0045] The configuration of external output points for this measurement and control function refers to the communication constraints for this measurement and control function to access external measurement and control functions. The specific configuration is as follows: <Next measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. The communication protocol is selected using a drop-down list, the port range is filled in using the start-end range page element, and the bandwidth requirement and latency requirement are filled in text boxes. The protocol between this measurement and control function and the next measurement and control function should be consistent.

[0046] Within this measurement and control function, the configuration of related components in the atomic component forwarding chain adopts the structure <Component A, Component B, Bandwidth, Delay> to form communication constraints (bandwidth and delay value requirements) between two components A (atoms) and component B (atoms). Thus, the list of communication constraints between N components, namely <Component A, Component B, Bandwidth, Delay>, <Component B, Component C, Bandwidth, Delay>, <Component C, Component D, Bandwidth, Delay>, ..., <Component N, Component N-1, Bandwidth, Delay>, can form an atomic forwarding chain. For example, {<Atomic Component 1, Atomic Component 2, Bandwidth, Delay>, <Atomic Component 2, Atomic Component 3, Bandwidth, Delay>, ..., <Atomic Component N-1, Atomic Component N, Bandwidth, Delay>}, is configured using a combination of text boxes and arrows. In the <Component A, Component B, Bandwidth, Delay> communication constraint structure, the communication protocol between components A and B remains consistent.

[0047] The atomic component startup order dependency graph is {<atomic component 1, startup level 1>, <atomic component 2, startup level 2>, <atomic component 3, startup level 3>, <atomic component 4, startup level 3>, ..., <atomic component N, startup level N>}. Component lists that can be formed by components at different startup levels are {<startup level 1, (<atomic component 1, atomic component I, ...>)>, <startup level 2, (<atomic component 2, atomic component K, ...>)>, <startup level 3, (<atomic component 3, atomic component 4, ...>)>, ...}. Components with lower startup levels must be started first. Atomic components at the same startup level do not have a startup order and can be started freely. Configuration is done using a combination of text boxes and arrows. Text boxes are used for startup level configuration, and arrows represent dependencies between components. The component at the tail of the arrow depends on the component it points to.

[0048] Atomic component configuration: This includes basic information configuration, business parameter configuration, deployment specification configuration, and virtualization mode configuration for atomic components. Select the target component in the lower-level canvas to configure its properties, as follows: Basic information configuration: The atomic component name, atomic component function description, and basic parameter information are all configured through text boxes.

[0049] Service parameter configuration: Service-level parameters such as transmit frequency, receive frequency, sampling rate, modulation method, and decoding method. Non-continuous attributes are configured through text boxes, while optional items are configured through drop-down lists.

[0050] Deployment specification configuration: CPU core requirements, whether a GPU is required, number of GPUs required, whether an FPGA is required, number of FPGA resources required, number of memory requirements, number of storage volumes required, etc. The number of CPU cores, number of FPGAs required, and number of memory requirements are configured via text boxes; whether a GPU or FPGA is required is configured via check boxes.

[0051] Virtualization mode: configuration of bare metal binary files / virtual machine images / container images, etc. The virtualization mode is configured through drop-down menus and is used to determine the form in which components are deployed on the cloud platform when the service template is instantiated. Bare metal is to start the bare metal binary executable file using a script. Virtual machine images are started by calling the cloud platform virtual machine image interface. Container images are started by calling the cloud platform container POD start interface.

[0052] As a second aspect of the invention, a method for modeling measurement and control service templates based on graphical intent-driven approaches is provided, highlighting the two-tiered construction concept of "function first, service later" and iterative optimization characteristics. For example... Figure 3 As shown, the complete process of building a measurement and control service template based on graphical intent is clearly demonstrated, including the following steps: Step 1, Initialization Phase: First, determine the operating system of the measurement and control service template to be built (such as non-coherent spread spectrum, high-speed data transmission, medium and low speed data transmission, etc.) to provide a framework for subsequent function selection.

[0053] Step 2, Function Acquisition Phase: Template reuse judgment: Check if there is already a usable measurement and control function template in the template library. If not, proceed to the measurement and control function template construction process; if so, proceed to the service assembly stage.

[0054] Measurement and control function template construction process Select Components: Choose suitable atomic components from the atomic component library. Configure data flow: Establish signal processing links between components, forming a component link forwarding diagram: <Component 1, Component 2, Communication Service Type, Communication Protocol, Bandwidth, Latency>, <Component 2, Component 3, Communication Service Type, Communication Protocol, Bandwidth, Latency>, ..., <Component N-1, Component N, Communication Service Type, Communication Protocol, Bandwidth, Latency> Configuration parameters: Configure measurement and control function service parameters and deployment specification parameters. Verification and Saving: After verifying that the functional logic is correct, save it as a new measurement and control function template. Step 3, Service Assembly Phase Feature Combinations: Add selected or newly created feature templates to the service canvas. Measurement and control function chain configuration: Data flow between measurement and control functions is defined by connections, forming a measurement and control function chain forwarding diagram: <Measurement and control function 1, Measurement and control function 2, Communication service type, Communication protocol, Bandwidth, Delay>, <Measurement and control function 2, Measurement and control function 3, Communication service type, Communication protocol, Bandwidth, Delay>, ..., <Measurement and control function N-1, Measurement and control function N, Communication service type, Communication protocol, Bandwidth, Delay> Configure service parameters: Configure global parameters for the entire service template, including supported frequency bands, number of targets, sampling rate, supported service functions (telemetry, remote control, ranging and velocimetry, tracking, etc.), and application areas (UAV telemetry and control, deep space exploration, lunar exploration projects, etc.). Step 4: The intent parsing module enters the verification and optimization phase. Business requirement verification: Determine whether the current service template meets the expected business requirements (frequency band range: S / KA / L, etc.; business functions: telemetry, remote control, data transmission, orbit determination, anomaly detection; application areas: satellite navigation data, satellite remote sensing data transmission, space payload telemetry data, UAV detection data, spacecraft positioning, etc.; code rate requirement: 128k-20Mbps). If not, return for adjustment. Integrity verification: Performing a technical integrity check on the template. Template required parameter checks: including functional template required parameter checks (function type, link building parameter non-empty parameter checks); component required parameter checks (component type, component name non-empty checks); service template required parameter checks (template system type non-empty determination, whether the service template test and control functions match the business requirements and whether the test and control functions are complete); Business parameter range check: Check the legality of the input frequency points of the measurement and control function and the S / L / X / KA frequency band range configured in the service template; check the legality of the discrete state of link establishment between components, etc. Data type checks: Bit error rate test result type check; frame synchronization code hexadecimal data type check; ranging and velocity measurement result type check, etc. Checking the compliance of measurement and control protocols: semantic consistency check between UDP and HTTP protocols between digital front-end and signal processing functions; protocol consistency check between signal processing functions and monitoring; protocol check between telemetry data and storage devices, etc. Verification of the integrity of the telemetry and control function forwarding chain: consistency of communication protocols, chain establishment parameters, and bandwidth between adjacent telemetry and control functions; verification of the link consistency between the telemetry and control functions and the uplink and downlink channels of the digital front end; verification of gaps in the forwarding chain. Iterative optimization: The template configuration is continuously optimized through a feedback loop to ensure the quality of the final result; Step 5, Completion Stage: Template storage: Save the verified graphical service templates to the template database for later reuse, and for instantiation of the measurement and control service when the center's work plan / measurement and control task is issued; Step 6, Service Instantiation Phase: When the telemetry, tracking, and command center issues satellite work plans or telemetry, tracking, and command tasks to the ground station, the ground station receives and manages the plans, parses them, and intelligently matches the corresponding service template files in the template library with the telemetry, tracking, and command links and data transmission links configured according to the plan content. This process is used to reorganize resources in the ground station's resource pool and schedule and deploy atomic components.

[0055] It should be noted that, within the scope of protection defined in the claims of this invention, the following embodiments can be combined and / or extended or replaced in any logical manner from the above specific embodiments, such as the disclosed technical principles, disclosed technical features or implicitly disclosed technical features.

[0056] Example 1 A graphical intent-driven measurement and control service template modeling system includes: a graphical intent expression layer module, an intent parsing layer module, and a template library management layer module; The graphical intent expression layer module is used to provide a graphical interface to express the intent of constructing the measurement and control service template; The intent parsing layer module is used to understand the intent expressed graphically by the user's measurement and control service, verify its correctness, and generate a measurement and control service template description file. The template library management layer module is used to provide full lifecycle management of templates, supporting template storage, retrieval, version control, and reuse.

[0057] Example 2 Based on Example 1, the provision of a graphical interface to express the intent of constructing the measurement and control service template specifically includes: firstly, editing the measurement and control function templates and the dependencies between function templates through a graphical canvas and drag-and-drop arrangement engine via a visual template library navigation and selector; secondly, configuring the attributes of measurement and control functions, service templates, and atomic-level components through an attribute configuration panel; and finally, generating a graphical intent model file after successful verification.

[0058] Example 3 Based on Example 1, the process of understanding the intent of the graphical representation of the user's measurement and control service, verifying its correctness, and generating a measurement and control service template description file specifically includes: parsing the JSON / XML structure of the graphical model generated by the graphical intent expression layer module through a model semantic extractor, extracting the measurement and control function relationship topology graph, identifying business semantics including phase-locked loop, modulation, demodulation, and decoding, identifying component relationships by a dependency analyzer, including startup order dependencies and data flow transmission paths, and then performing integrity verification and business specification verification on each component, component relationships, and measurement and control function relationships by a consistency verification engine. After successful verification, a standardized template description file that can be recognized by various resource pools is generated by a model description file generator, and the standardized template description file contains complete configuration parameters and deployment specifications.

[0059] Example 4 Based on Example 1, the module provides full lifecycle management of templates, supporting template storage, retrieval, version control, and reuse. Specifically, it includes: a hierarchical template storage repository that stores work system templates, measurement and control function templates, and atomic component repositories according to a hierarchical principle; template version control that manages versions of various templates and supports rollback and upgrades; template classification and retrieval that classifies and retrieves templates according to keywords, application areas, and resource requirements; and template usage statistics and recommendations that rank popular templates and recommend templates based on historical similarity.

[0060] Example 5 Based on Example 1, in the graphical intent expression layer module, the graphical interface specifically includes three areas: the left side is the template library navigation area, the middle part is the graphical canvas, and the right side is the attribute configuration panel.

[0061] Example 6 Based on Example 5, the template library navigation area specifically includes: a working system template library, a measurement and control function template library, and an atomic component toolbox; The work system template library is used to manage top-level templates, including work system types and the creation, deletion, modification, and querying of templates under that work system type; The measurement and control function template library is used to manage measurement and control function templates, including the creation, deletion, modification and query of function units; The atomic component toolbox is used to manage virtualization components, including the creation, deletion, modification, and querying of virtualization components.

[0062] Example 7 Based on Example 5, the graphical canvas specifically includes: an upper canvas, a middle canvas, and a lower canvas; The upper canvas is used to display a working system service template formed by combining multiple measurement and control function modules and configuring the measurement and control function forwarding chain through a directed connection graph. The intermediate canvas is used to demonstrate that when a certain measurement and control function is selected in the service template construction of the upper canvas, an internal view can be entered; the internal view shows how to drag and drop multiple components from the atomic component toolbox and connect them to form a measurement and control function template. The lower canvas is used to display the component creation process, including defining the component name, using icons, and describing the component's functions. Once created, it forms a column in the atomic component toolbox of the template library navigation area, specifically including the component name and component identifier.

[0063] Example 8 Based on Example 5, the attribute configuration panel specifically includes: an attribute configuration panel and attribute controls. The attribute controls are used to configure attributes, including service template attribute configuration, measurement and control function template attribute configuration, and atomic component attribute configuration.

[0064] Example 9 Based on Example 8, the service template attribute configuration specifically includes: service template basic information configuration, external input point configuration, external output point configuration, measurement and control function forwarding chain configuration, and scheduling strategy configuration; The basic information configuration of the service template specifically includes: the service template's working system, target number, version number, creation time, creator, creation department, and application field; among which, the working system is selected via a drop-down list; the target number and version number are entered via text boxes; the creation time is automatically filled with the current time using the time page component element; the creation department and creator are selected via drop-down lists; and the application field is selected via a drop-down list; the drop-down list options include UAV telemetry and control, space-based telemetry and control, ground-based telemetry and control, and sea-based telemetry and control; The configuration of external input points specifically includes: the requirements for external data access to the measurement and control service template include the communication protocol TCP / UDP / HTTP, the access port range, bandwidth requirements, latency requirements, and IP range; among which, the communication protocol is selected using a drop-down box, the port range is filled in using the start and end range page elements, and the bandwidth and latency requirements are configured using text boxes, with the bandwidth requirements divided into multiple levels; The configuration of the external output point specifically includes: the output requirements after the measurement and control service template is processed, including the communication protocol TCP / UDP / HTTP, the output port range, bandwidth requirements, latency requirements, and IP range; wherein, the communication protocol is selected using a drop-down list, the port range is filled in using the start and end range page elements, and the bandwidth and latency requirements are filled in using text boxes; The configuration of the measurement and control function forwarding chain specifically includes: configuration through multiple arrow connection relationships, and the bandwidth and latency requirements under the connection point are configured using text boxes; The scheduling strategy configuration specifically includes: the strategy configuration used when the service template is instantiated, specifically including lowest cost, lowest power consumption, load balancing and high security, and the scheduling strategy list is configured through a drop-down box.

[0065] Example 10 Based on Example 8, the configuration of the measurement and control function template attributes specifically includes: configuration of basic information of the measurement and control function template, configuration of input points, configuration of output points, configuration of atomic component forwarding chain, and configuration of atomic component startup order dependency relationship. The basic information configuration of the measurement and control function template specifically includes: the measurement and control function name, measurement and control function description, and basic parameter information are all configured through text boxes; The configuration of input points for external measurement and control functions includes: the communication constraints for external measurement and control functions as clients accessing this measurement and control function. The specific configuration is as follows: <Measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. Among them, the communication protocol is selected using a drop-down list, and the communication protocol includes TCP / UDP. The port range is filled in using the start and end range page elements. The bandwidth requirement and latency requirement are filled in using text boxes. This measurement and control function configures the external output points of external measurement and control functions. Specifically, it defines the communication constraints for this measurement and control function to access external measurement and control functions. The specific configuration is as follows: <Next measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. The communication protocol is selected using a dropdown menu, the port range is entered using the start and end range page elements, and the bandwidth and latency requirements are filled in using text boxes. The protocol between this measurement and control function and the next measurement and control function should be consistent. Within this measurement and control function, the atomic component forwarding chain configures related components using a <component A, component B, bandwidth, delay> structure to form communication constraints between two components A and B. This results in a list of communication constraints between N components: <component A, component B, bandwidth, delay>, <component B, component C, bandwidth, delay>, <component C, component D, bandwidth, delay>, ..., <component N, component N-1, bandwidth, delay>, forming an atomic forwarding chain. Configuration is achieved using a combination of text boxes and arrows. Within the <component A, component B, bandwidth, delay> communication constraint structure, components A and B interact with each other, maintaining a consistent communication protocol. The atomic component startup order dependency graph is {<atomic component 1, startup level 1>, <atomic component 2, startup level 2>, <atomic component 3, startup level 3>, <atomic component 4, startup level 3>, ..., <atomic component N, startup level N>}. Component lists formed by components at different startup levels are {<startup level 1, (<atomic component 1, atomic component I, ...>)>, <startup level 2, (<atomic component 2, atomic component K, ...>)>, <startup level 3, (<atomic component 3, atomic component 4, ...>)>, ...}. Components with lower startup levels must be started first. Atomic components at the same startup level have no startup order and can be started freely. Configuration is done using a combination of text boxes and arrows. Text boxes are used for startup level configuration, and arrows represent dependencies between components. The component at the tail of the arrow depends on the component it points to.

[0066] Example 11 Based on Example 8, the attribute configuration of the atomic component specifically includes: atomic component basic information configuration, specifically including basic information configuration, business parameter configuration, deployment specification configuration, and virtualization form configuration; The basic information configuration specifically includes: atomic component name and atomic component function description, and basic parameter information is configured through text boxes; The service parameter configuration specifically includes: service-level parameters, which include transmission frequency, reception frequency, sampling rate, modulation method, and decoding method; among which, discontinuous attributes are configured through text boxes, and optional items are configured through drop-down lists; The deployment specifications include: CPU core requirements, whether a GPU is needed, the number of GPUs required, whether an FPGA is needed, the number of FPGA resources required, the number of memory requirements, and the number of storage volumes required. The number of CPU cores, the number of FPGAs required, and the number of memory requirements are configured via text boxes; the requirement for a GPU and FPGA is configured via checkboxes. The virtualization form specifically includes the configuration of bare metal binary files, virtual machine images, and container images. The virtualization form is configured through a drop-down list and is used to determine the form in which components are deployed on the cloud platform when the service template is instantiated. Bare metal uses a script to start the bare metal binary executable file, virtual machine images are started by calling the cloud platform virtual machine image interface, and container images are started by calling the cloud platform container POD start interface.

[0067] Example 12 A graphical intent-driven measurement and control service template modeling method, based on any one of Embodiments 1 to 11, includes the following steps: Step 1, Initialization Phase: First, determine the working system to which the measurement and control service template to be built belongs, providing a framework for subsequent function selection; Step 2, Function Acquisition Phase: Check if there are any available measurement and control function templates in the template library. If not, proceed to the measurement and control function template construction process; if so, proceed to the service assembly phase. Step 3, Service Assembly Phase: Add the selected or newly created function template to the service canvas, and then execute: Measurement and control function chain configuration: The data flow between measurement and control functions is defined by connecting them to form a measurement and control function chain forwarding diagram <Measurement and control function 1, Measurement and control function 2, Communication service type, Communication protocol, Bandwidth, Delay>, <Measurement and control function 2, Measurement and control function 3, Communication service type, Communication protocol, Bandwidth, Delay>, ..., <Measurement and control function N-1, Measurement and control function N, Communication service type, Communication protocol, Bandwidth, Delay>; Configure service parameters: Configure global parameters for the entire service template, including supported frequency bands, number of targets, sampling rate, supported service functions and application areas; Step 4: The intent parsing module enters the verification and optimization phase. It determines whether the current service template meets the expected business requirements. If it does not meet the requirements, it returns for adjustment. If it meets the requirements, it enters the integrity verification phase. In the integrity verification phase, the template is checked for technical integrity and the template configuration is continuously optimized through feedback loop to ensure the quality of the final result. Step 5, Completion Stage: Save the verified graphical service template to the template database for subsequent reuse, and for instantiation of the measurement and control service when the center's work plan / measurement and control task is issued; Step 6, Service Instantiation Phase: When the telemetry, tracking, and command center issues satellite work plans or telemetry, tracking, and command tasks to the ground station, the ground station manages and receives the plan, parses the plan, and intelligently matches the corresponding service template files in the template library according to the telemetry, tracking, and command links and data transmission links configured in the plan. This process involves reorganizing resources within the ground station's resource pool and scheduling and deploying atomic components.

[0068] Example 13 Based on Example 12, step 2 of the measurement and control function template construction process specifically includes the following sub-steps: First, select components: choose atomic components from the atomic component library; Then, configure the data flow: establish signal processing links between components to form a component link forwarding graph <Component 1, Component 2, communication service type, communication protocol, bandwidth, latency>, <Component 2, Component 3, communication service type, communication protocol, bandwidth, latency>, ..., <Component N-1, Component N, communication service type, communication protocol, bandwidth, latency>; Next, set the parameters: configure the measurement and control function service parameters and deployment specification parameters; Finally, verify and save: After verifying that the functional logic is correct, save it as a new measurement and control function template.

[0069] Example 14 Based on Example 12, in step 4, the integrity verification specifically includes: Template required parameters are checked, specifically including required parameters for functional templates; required parameters for components; and required parameters for service templates. Business parameter range check, specifically including the legality check of the input frequency points of the measurement and control function and the S / L / X / KA frequency band range of the service template configuration, and the legality check of the discrete state of link establishment between components; Data type checks specifically include bit error rate test result type checks, frame synchronization code hexadecimal data type checks, and ranging and velocity measurement result type checks. The verification of the measurement and control protocol compliance includes, in particular, checking the semantic consistency between the UDP and HTTP protocols of the digital front-end and signal processing functions; checking the protocol consistency between the signal processing functions and the monitoring; and checking the protocol between telemetry data and storage devices. Verification of the integrity of the telemetry and control function forwarding chain specifically verifies the consistency of communication protocols, chain establishment parameters, and bandwidth between adjacent telemetry and control functions; as well as the link consistency verification between the telemetry and control function and the uplink and downlink channels of the digital front end, and the verification of gaps in the forwarding chain.

[0070] The units described in the embodiments of the present invention can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0071] According to one aspect of the present invention, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described above.

[0072] In another aspect, embodiments of the present invention also provide a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

Claims

1. A measurement and control service template modeling system based on graphical intent-driven design, characterized in that, include: The module consists of a graphical intent expression layer, an intent parsing layer, and a template library management layer. The graphical intent expression layer module is used to provide a graphical interface to express the intent of constructing the measurement and control service template; The intent parsing layer module is used to understand the intent expressed graphically by the user's measurement and control service, verify its correctness, and generate a measurement and control service template description file. The template library management layer module is used to provide full lifecycle management of templates, supporting template storage, retrieval, version control, and reuse.

2. The graphical intent-driven measurement and control service template modeling system according to claim 1, characterized in that, The provision of a graphical interface to express the intent of constructing measurement and control service templates specifically includes: firstly, editing measurement and control function templates and dependencies between function templates through a visual template library navigation and selector, using a graphical canvas and drag-and-drop arrangement engine; secondly, configuring the attributes of measurement and control functions, service templates, and atomic-level components through an attribute configuration panel; and finally, generating a graphical intent model file after successful verification.

3. The measurement and control service template modeling system based on graphical intent-driven according to claim 1, characterized in that, The process of understanding the user's intent in the graphical representation of the measurement and control service, verifying its correctness, and generating a measurement and control service template description file specifically includes: parsing the JSON / XML structure of the graphical model generated by the graphical intent expression layer module through a model semantic extractor, extracting the measurement and control function relationship topology graph, identifying business semantics including phase-locked loop, modulation, demodulation, and decoding, identifying component relationships by a dependency analyzer, including startup order dependencies and data flow transmission paths, and then performing integrity verification and business specification verification on each component, component relationships, and measurement and control function relationships by a consistency verification engine. After successful verification, a standardized template description file that can be recognized by various resource pools is generated by a model description file generator, and the standardized template description file contains complete configuration parameters and deployment specifications.

4. The measurement and control service template modeling system based on graphical intent-driven according to claim 1, characterized in that, The module provides full lifecycle management of templates, supporting template storage, retrieval, version control, and reuse. Specifically, it includes: a hierarchical template storage repository that stores work system templates, measurement and control function templates, and atomic component repositories according to a hierarchical principle; template version control that manages versions of various templates and supports rollback and upgrades; template classification and retrieval that classifies and retrieves templates according to keywords, application areas, and resource requirements; and template usage statistics and recommendations that rank popular templates and recommend templates based on historical similarity.

5. The measurement and control service template modeling system based on graphical intent-driven according to claim 1, characterized in that, In the graphical intent expression layer module, the graphical interface specifically includes three areas: the left side is the template library navigation area, the middle part is the graphical canvas, and the right side is the attribute configuration panel.

6. The measurement and control service template modeling system based on graphical intent-driven according to claim 5, characterized in that, The template library navigation area specifically includes: a working system template library, a measurement and control function template library, and an atomic component toolbox; The work system template library is used to manage top-level templates, including work system types and the creation, deletion, modification, and querying of templates under that work system type; The measurement and control function template library is used to manage measurement and control function templates, including the creation, deletion, modification and query of function units; The atomic component toolbox is used to manage virtualization components, including the creation, deletion, modification, and querying of virtualization components.

7. The measurement and control service template modeling system based on graphical intent-driven according to claim 5, characterized in that, The graphical canvas specifically includes: an upper canvas, a middle canvas, and a lower canvas; The upper canvas is used to display a working system service template formed by combining multiple measurement and control function modules and configuring the measurement and control function forwarding chain through a directed connection graph. The intermediate canvas is used to demonstrate that when a certain measurement and control function is selected in the service template construction of the upper canvas, an internal view can be entered; the internal view shows how to drag and drop multiple components from the atomic component toolbox and connect them to form a measurement and control function template. The lower canvas is used to display the component creation process, including defining the component name, using icons, and describing the component's functions. Once created, it forms a column in the atomic component toolbox of the template library navigation area, specifically including the component name and component identifier.

8. The graphical intent-driven measurement and control service template modeling system according to claim 5, characterized in that, The attribute configuration panel specifically includes an attribute configuration panel and attribute controls. The attribute controls are used to configure attributes, including service template attribute configuration, measurement and control function template attribute configuration, and atomic component attribute configuration.

9. The graphical intent-driven measurement and control service template modeling system according to claim 8, characterized in that, The service template attribute configuration specifically includes: service template basic information configuration, external input point configuration, external output point configuration, measurement and control function forwarding chain configuration, and scheduling strategy configuration; The basic information configuration of the service template specifically includes: the service template's working system, target number, version number, creation time, creator, creation department, and application field; wherein, the working system is selected via a drop-down list; the target number and version number are entered via text boxes; the creation time is automatically filled with the current time via a time page component element; the creation department and creator are selected via drop-down lists; and the application field is selected via a drop-down list; the drop-down list options include UAV telemetry and control, space-based telemetry and control, ground-based telemetry and control, and sea-based telemetry and control; The configuration of external input points specifically includes: the requirements for external data access to the measurement and control service template include the communication protocol TCP / UDP / HTTP, the access port range, bandwidth requirements, latency requirements, and IP range; among which, the communication protocol is selected using a drop-down box, the port range is filled in using the start and end range page elements, and the bandwidth and latency requirements are configured using text boxes, with the bandwidth requirements divided into multiple levels; The configuration of the external output point specifically includes: the output requirements after the measurement and control service template is processed, including the communication protocol TCP / UDP / HTTP, the output port range, bandwidth requirements, latency requirements, and IP range; wherein, the communication protocol is selected using a drop-down list, the port range is filled in using the start and end range page elements, and the bandwidth and latency requirements are filled in using text boxes; The configuration of the measurement and control function forwarding chain specifically includes: configuration through multiple arrow connection relationships, and the bandwidth and latency requirements under the connection point are configured using text boxes; The scheduling strategy configuration specifically includes: the strategy configuration used when the service template is instantiated, specifically including lowest cost, lowest power consumption, load balancing and high security, and the scheduling strategy list is configured through a drop-down box.

10. The graphical intent-driven measurement and control service template modeling system according to claim 8, characterized in that, The measurement and control function template attribute configuration specifically includes: measurement and control function template basic information configuration, input point configuration, output point configuration, atomic component forwarding chain configuration, and atomic component startup order dependency configuration. The basic information configuration of the measurement and control function template specifically includes: the measurement and control function name, measurement and control function description, and basic parameter information are all configured through text boxes; The configuration of input points for external measurement and control functions includes: the communication constraints for external measurement and control functions as clients accessing this measurement and control function. The specific configuration is as follows: <Measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. Among them, the communication protocol is selected using a drop-down list, and the communication protocol includes TCP / UDP. The port range is filled in using the start and end range page elements. The bandwidth requirement and latency requirement are filled in using text boxes. This measurement and control function configures the external output points of external measurement and control functions. Specifically, it defines the communication constraints for this measurement and control function to access external measurement and control functions. The specific configuration is as follows: <Next measurement and control function, external access point protocol, access point port range, access point IP range, bandwidth requirement, latency requirement>. The communication protocol is selected using a dropdown menu, the port range is entered using the start and end range page elements, and the bandwidth and latency requirements are filled in using text boxes. The protocol between this measurement and control function and the next measurement and control function should be consistent. Within this measurement and control function, the atomic component forwarding chain configures related components using a <component A, component B, bandwidth, delay> structure to form communication constraints between two components A and B. This results in a list of communication constraints between N components: <component A, component B, bandwidth, delay>, <component B, component C, bandwidth, delay>, <component C, component D, bandwidth, delay>, ..., <component N, component N-1, bandwidth, delay>, forming an atomic forwarding chain. Configuration is achieved using a combination of text boxes and arrows. Within the <component A, component B, bandwidth, delay> communication constraint structure, components A and B interact with each other, maintaining a consistent communication protocol. The atomic component startup order dependency graph is {<atomic component 1, startup level 1>, <atomic component 2, startup level 2>, <atomic component 3, startup level 3>, <atomic component 4, startup level 3>, ..., <atomic component N, startup level N>}. Component lists formed by components at different startup levels are {<startup level 1, (<atomic component 1, atomic component I, ...>)>, <startup level 2, (<atomic component 2, atomic component K, ...>)>, <startup level 3, (<atomic component 3, atomic component 4, ...>)>, ...}. Components with lower startup levels must be started first. Atomic components at the same startup level have no startup order and can be started freely. Configuration is done using a combination of text boxes and arrows. Text boxes are used for startup level configuration, and arrows represent dependencies between components. The component at the tail of the arrow depends on the component it points to.

11. The measurement and control service template modeling system based on graphical intent-driven according to claim 8, characterized in that, The attribute configuration of the atomic component specifically includes: basic information configuration of the atomic component, including basic information configuration, business parameter configuration, deployment specification configuration, and virtualization form configuration; The basic information configuration specifically includes: atomic component name and atomic component function description, and basic parameter information is configured through text boxes; The service parameter configuration specifically includes: service-level parameters, which include transmission frequency, reception frequency, sampling rate, modulation method, and decoding method; among which, discontinuous attributes are configured through text boxes, and optional items are configured through drop-down lists; The deployment specifications include: CPU core requirements, whether a GPU is needed, the number of GPUs required, whether an FPGA is needed, the number of FPGA resources required, the number of memory requirements, and the number of storage volumes required. The number of CPU cores, the number of FPGAs required, and the number of memory requirements are configured via text boxes; the requirement for a GPU and FPGA is configured via checkboxes. The virtualization form specifically includes the configuration of bare metal binary files, virtual machine images, and container images. The virtualization form is configured through a drop-down list and is used to determine the form in which components are deployed on the cloud platform when the service template is instantiated. Bare metal uses a script to start the bare metal binary executable file, virtual machine images are started by calling the cloud platform virtual machine image interface, and container images are started by calling the cloud platform container POD start interface.

12. A method for modeling measurement and control service templates based on graphical intent-driven methods, characterized in that, The measurement and control service template modeling system based on any one of claims 1 to 11, comprising the following steps: Step 1, Initialization Phase: First, determine the working system to which the measurement and control service template to be built belongs, providing a framework for subsequent function selection; Step 2, Function Acquisition Phase: Check if there are any available measurement and control function templates in the template library. If not, proceed to the measurement and control function template construction process; if so, proceed to the service assembly phase. Step 3, Service Assembly Phase: Add the selected or newly created function template to the service canvas, and then execute: Measurement and control function chain configuration: The data flow between measurement and control functions is defined by connecting them to form a measurement and control function chain forwarding diagram <Measurement and control function 1, Measurement and control function 2, Communication service type, Communication protocol, Bandwidth, Delay>, <Measurement and control function 2, Measurement and control function 3, Communication service type, Communication protocol, Bandwidth, Delay>, ..., <Measurement and control function N-1, Measurement and control function N, Communication service type, Communication protocol, Bandwidth, Delay>; Configure service parameters: Configure global parameters for the entire service template, including supported frequency bands, number of targets, sampling rate, supported service functions and application areas; Step 4: The intent parsing module enters the verification and optimization phase. It determines whether the current service template meets the expected business requirements. If it does not meet the requirements, it returns for adjustment. If it meets the requirements, it enters the integrity verification phase. In the integrity verification phase, the template is checked for technical integrity and the template configuration is continuously optimized through feedback loop to ensure the quality of the final result. Step 5, Completion Stage: Save the verified graphical service template to the template database for subsequent reuse, and for instantiation of the measurement and control service when the center's work plan / measurement and control task is issued; Step 6, Service Instantiation Phase: When the telemetry, tracking, and command center issues satellite work plans or telemetry, tracking, and command tasks to the ground station, the ground station manages and receives the plan, parses the plan, and intelligently matches the corresponding service template files in the template library according to the telemetry, tracking, and command links and data transmission links configured in the plan. This process involves reorganizing resources within the ground station's resource pool and scheduling and deploying atomic components.

13. The method for modeling measurement and control service templates based on graphical intent-driven principles according to claim 12, characterized in that, In step 2, the construction process of the measurement and control function template specifically includes the following sub-steps: First, select components: choose atomic components from the atomic component library; Then, configure the data flow: establish signal processing links between components to form a component link forwarding graph <Component 1, Component 2, communication service type, communication protocol, bandwidth, latency>, <Component 2, Component 3, communication service type, communication protocol, bandwidth, latency>, ..., <Component N-1, Component N, communication service type, communication protocol, bandwidth, latency>; Next, set the parameters: configure the measurement and control function service parameters and deployment specification parameters; Finally, verify and save: After verifying that the functional logic is correct, save it as a new measurement and control function template.

14. The method for modeling measurement and control service templates based on graphical intent-driven principles according to claim 12, characterized in that, In step 4, the integrity verification specifically includes: Template required parameters are checked, specifically including required parameters for functional templates; required parameters for components; and required parameters for service templates. Business parameter range check, specifically including the legality check of the input frequency points of the measurement and control function and the S / L / X / KA frequency band range of the service template configuration, and the legality check of the discrete state of link establishment between components; Data type checks specifically include bit error rate test result type checks, frame synchronization code hexadecimal data type checks, and ranging and velocity measurement result type checks. The verification of the measurement and control protocol compliance includes, in particular, checking the semantic consistency between the UDP and HTTP protocols of the digital front-end and signal processing functions; checking the protocol consistency between the signal processing functions and the monitoring; and checking the protocol between telemetry data and storage devices. Verification of the integrity of the telemetry and control function forwarding chain specifically verifies the consistency of communication protocols, chain establishment parameters, and bandwidth between adjacent telemetry and control functions; as well as the link consistency verification between the telemetry and control function and the uplink and downlink channels of the digital front end, and the verification of gaps in the forwarding chain.

Images