Cloud network resource management system

Abstract

The invention relates to a cloud network resource management system, and belongs to the technical field of computers, and the system comprises a 2D / 3D front-end component code generation unit which is used for generating a front-end component code according to user semantics and generating a front-end component based on the front-end component code; the API automatic generation unit is used for generating SQL query statements according to the user semantics and generating APIs based on the SQL query statements; the front-end and rear-end SDK component synthesis unit is used for constructing a mixed assembly of front-end and rear-end SDK components based on the front-end component and the API, and using the mixed assembly of the front-end and rear-end SDK components in the twin scene construction unit; the 2D / 3D component library management unit is used for storing mixed assembly of front and rear end SDK components; and the twinning presenting and dynamic publishing unit is used for receiving the scene built by the twinning scene building unit and previewing the scene. According to the cloud network resource management system, the universality and adaptability of the system are enhanced.

Description

Technical Field

[0001] The present invention belongs to the field of computer technology, and in particular relates to a cloud network resource management system. Background Art

[0002] In the related technologies, the current cloud network resource management methods of resource centers have the characteristics of hierarchical segmentation, static manual, rule-driven, passive response, and closed management, which leads to difficult-to-solve problems such as high operation and maintenance costs, low efficiency, inflexible resource allocation, high cutover / operation risks, and insufficient ability to deal with emergencies. How to better realize cloud network resource management has become an urgent problem to be solved. Summary of the invention

[0003] In view of the above deficiencies in the prior art, an object of the invention is to provide a cloud network resource management system.

[0004] The first aspect of the present invention proposes a cloud network resource management system, including: a 2D / 3D front-end component code generation unit, which is used to generate front-end component code according to user semantics, and generate front-end components based on the front-end component code; an API automatic generation unit, which is used to generate SQL query statements according to the user semantics, and generate APIs based on the SQL query statements; a front-end and back-end SDK component synthesis unit, which is used to build a mixed assembly of front-end and back-end SDK components based on the front-end components and the API, and use the mixed assembly of the front-end and back-end SDK components in a twin scene building unit; a 2D / 3D component library management unit, which is used to store the mixed assembly of the front-end and back-end SDK components; a twin presentation and dynamic publishing unit, which is used to receive the scene built by the twin scene building unit and preview it.

[0005] Furthermore, the 2D / 3D front-end component code generation unit is connected to the intent model, wherein the front-end component code is generated according to user semantics, including: obtaining the user semantics; analyzing the user semantics based on the intent model and the front-end technology stack, and generating multiple types of front-end component codes that meet the target requirements, the multiple types including graph, tree, column, and point.

[0006] Furthermore, the user semantics are analyzed based on the intent model and the front-end technology stack to generate various types of front-end component codes that meet the target requirements, including: inputting the user semantics into the intent model to obtain the intent information of the user semantics, wherein the intent information includes component type and data information; determining the component infrastructure of the component type based on the front-end technology stack, and integrating the component infrastructure of the component type and the data information to generate the front-end component code.

[0007] Furthermore, the API automatic generation unit is connected to the Text2SQL technology, wherein an SQL query statement is generated according to the user semantics, including: performing semantic analysis on the user semantics based on natural language processing technology NLP to obtain the query intent and key information of the user semantics; mapping the key information to the database to construct a statement framework corresponding to the query intent; filling the statement framework based on the mapping result to obtain the SQL query statement.

[0008] Furthermore, it also includes: when generating the SQL query statement, dynamically configuring and modifying the conditions of the SQL query statement in a variable manner based on user needs.

[0009] Furthermore, a mixed assembly of front-end and back-end SDK components is built based on the front-end component and the API, including: when the front-end component is a single component, associating the single component with the API, wherein the path and request parameter information associated with the API are specified in the configuration of the single component; when the front-end component is multiple components, forming the multiple components into a template component; associating each component in the template component with the corresponding API to obtain a component library of the template component.

[0010] Furthermore, the 2D / 3D component library management unit includes component / scene management, component / scene downloading and integration. The component / scene management is used to dynamically generate component management through the mixed assembly of the front-end and back-end SDK components, and to manage the mixed assembly of the front-end and back-end SDK components based on a preset method; the component / scene downloading and integration is used for online compilation, online packaging, packaged storage and downloading of the mixed assembly of the front-end and back-end SDK components.

[0011] Furthermore, the 2D / 3D component library management unit also includes component / scene sharing, which is used for online preview, adding to shopping cart, and one-click subscription of target components or scenes.

[0012] Furthermore, the twin scene building unit is used to support multiple twin scene building methods, multiple scene modes, and visual dynamic configuration of the front-end and back-end SDK components.

[0013] Furthermore, the twin presentation and dynamic publishing unit is also used to publish the constructed scene and generate a corresponding access link for the published scene.

[0014] The beneficial effects of the present invention are as follows:

[0015] The cloud network resource management system described in the present invention includes a 2D / 3D front-end component code generation unit, which is used to generate front-end component code according to user semantics, and generate front-end components based on the front-end component code; an API automatic generation unit, which is used to generate SQL query statements according to user semantics, and generate APIs based on SQL query statements; a front-end and back-end SDK component synthesis unit, which is used to build a mixed assembly of front-end and back-end SDK components based on front-end components and APIs, and use the mixed assembly of front-end and back-end SDK components in a twin scene building unit; a 2D / 3D component library management unit, which is used to store the mixed assembly of front-end and back-end SDK components; a twin presentation and dynamic publishing unit, which is used to receive the scene built by the twin scene building unit and preview it. The units of the entire system of the system cooperate with each other, and can flexibly respond to the diverse needs expressed by different user semantics. Whether it is creating a new front-end display, developing a back-end interface, building a twin scene, etc., it can timely adjust and generate corresponding content according to changes in specific business scenarios, so that the cloud network resource management system can better adapt to the cloud network resource-related management, monitoring and presentation requirements under different scales and different application scenarios, and enhance the versatility and adaptability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings are only used to illustrate specific embodiments and are not considered to limit the present invention. In the entire drawings, the same reference symbols represent the same components. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

[0017] Figure 1 is a schematic diagram of a cloud network resource management system according to an embodiment of the present invention;

[0018] Figure 2 is a flow chart of a cloud network resource management method according to an embodiment of the present invention;

[0019] Figure 3 It is a structural block diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in the field without making creative work should fall within the scope of protection of the present invention.

[0021] Furthermore, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts disclosed in the present invention.

[0022] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the orientation or position relationship indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inside", "outside", etc. is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. In addition, the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. The terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0023] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of methods and systems consistent with some aspects of the present invention as detailed in the appended claims.

[0024] The present invention discloses a cloud network resource management system. Figure 1 is a schematic diagram of a cloud network resource management system according to an embodiment of the present invention. Figure 1 As shown, the cloud network resource management system includes:

[0025] The 2D / 3D front-end component code generation unit 110 is used to generate front-end component codes according to user semantics, and to generate front-end components based on the front-end component codes;

[0026] The API automatic generation unit 120 is used to generate SQL query statements according to user semantics, and generate APIs based on the SQL query statements;

[0027] The front-end and back-end SDK component synthesis unit 130 is used to build a mixed assembly of front-end and back-end SDK components based on the front-end components and APIs, and use the mixed assembly of front-end and back-end SDK components in the twin scene construction unit 140;

[0028] 2D / 3D component library management unit 150, used to store mixed assembly of front-end and back-end SDK components;

[0029] The twin presentation and dynamic publishing unit 160 is used to receive the scene built by the twin scene building unit 140 and preview it.

[0030] That is to say, through the 2D / 3D front-end component code generation unit 110, the front-end component code and corresponding components can be automatically generated according to user semantics, which greatly reduces the workload of front-end developers to manually write codes, speeds up the development speed of front-end interface related functional modules, and improves development efficiency; through the API automatic generation unit 120, SQL query statements are generated according to user semantics and further generate APIs, which avoids the tedious process of developers manually writing complex database query statements and building API interfaces from demand analysis, making back-end interface development more efficient, and can quickly respond to the front-end's needs for data acquisition and interaction, shortening the development cycle of the entire project; through the front-end and back-end SDK component synthesis unit 130, the front-end components and APIs are mixed and combined It realizes the integrated front-end and back-end component building process, without the need for developers to deal with the complex configuration and coordination of the front-end and back-end component integration separately, reducing the difficulty of front-end and back-end fusion development and improving the efficiency of hybrid assembly of front-end and back-end SDK components; the hybrid assembly components built by using the front-end and back-end SDK component synthesis unit 130 can be directly used in the twin scene building unit 140, which can quickly and conveniently build twin scenes; the hybrid assembly of front-end and back-end SDK components is stored through the 2D / 3D component library management unit 150 to form a reusable component resource library; the built scene can be received and previewed through the twin presentation and dynamic publishing unit 160, and developers, operation and maintenance personnel or other relevant personnel can view the actual presentation effect of the twin scene in time.

[0031] In an embodiment of the present invention, a 2D / 3D front-end component code generation unit is connected to an intent model, wherein user semantics are acquired; based on the intent model and the front-end technology stack, the user semantics are analyzed to generate various types of front-end component codes that meet target requirements, including graphical, tree, columnar, and point-like codes.

[0032] Among them, the intent model includes but is not limited to Tele / Qwen2 large model, 3D modeling, TeleChat, etc.

[0033] Among them, the front-end technology stack includes but is not limited to Vue, CSS3, etc.

[0034] Among them, user semantics are input into the intent model to obtain the intent information of user semantics, which includes component type and data information; the component infrastructure of the component type is determined based on the front-end technology stack, and the component infrastructure and data information of the component type are integrated to generate the front-end component code.

[0035] That is to say, by connecting the Tele / Qwen2 large model and various model technologies such as 3D modeling. This means that the 2D / 3D front-end component code generation unit 110 can use these advanced and powerful technical foundations to achieve its own more complex and intelligent functional expansion. For example, the large model has a strong natural language understanding ability and can better interpret the semantic information input by the user. And at the same time, it is connected to different large models such as TeleChat and Qianwen, and focuses on strengthening the prompt word engineering. The prompt word engineering is very critical. By carefully designing and optimizing the prompt words input to the large model, the large model can be guided to generate the corresponding front-end component code more accurately according to the expected requirements, so that the generated results are more in line with the diversified needs in the actual business scenario. Then generate code based on front-end technology stacks such as Vue and CSS3.

[0036] Among them, Vue is a popular progressive framework for building user interfaces, which can efficiently organize and manage the interactive logic, structure and display of front-end components; CSS3 is used to beautify the styles of components so that they can achieve ideal visual presentation effects. It can then intelligently generate various types of front-end component codes, covering cloud network topology diagrams (which can be used to display complex relationships such as network architecture and cloud resource layout), customer resource trees (which facilitate hierarchical and structured presentation of customer-related resources), lists (a general form of information listing and display), as well as 2D / 3D bar charts, 2D / 3D line charts, 2D / 3D heat maps, 2D / 3DGis maps and other different forms of data visualization components, as well as built-in 3D models (such as 3D models used to display some products and other specific application scenarios). Such rich component generation capabilities can basically meet the requirements of many different business fields for front-end visualization.

[0037] In an embodiment of the present invention, an API automatic generation unit is connected to the Text2SQL technology, wherein semantic analysis of user semantics is performed based on natural language processing technology NLP to obtain query intent and key information of user semantics; the key information is mapped to the database to construct a statement framework corresponding to the query intent; the statement framework is filled based on the mapping result to obtain an SQL query statement.

[0038] That is to say, through natural language processing technology NLP, semantic analysis is performed on user semantics to analyze their query intent and key information, such as entities, attributes, relationships, etc. Then the key information is mapped to the table structure, fields and SQL syntax of the database to build a SQL query statement framework corresponding to the query intent. After that, the specific query parameters in the SQL query statement framework are filled in according to the mapping results to generate a complete SQL query statement, and further optimization may be performed to ensure the efficiency and accuracy of the query.

[0039] In an embodiment of the present invention, when a SQL query statement is generated, the conditions of the SQL query statement are dynamically configured and modified in a variable manner based on user requirements.

[0040] In other words, the generated SQL statements are not fixed and immutable, but can be dynamically configured and modified. Because the conditions and logic of data queries in actual business scenarios may change frequently, dynamic configuration can adjust the specific content of the generated SQL statements at any time according to new needs, such as adding filtering conditions, changing sorting rules, etc. The variable dynamic configuration of SQL conditions further enhances flexibility. Setting conditions as variables means that the same SQL statement framework can be reused in different scenarios by assigning different values ​​to the variables, easily realizing data query requirements under different parameters, and improving the reusability of the code and the scalability of the entire data query function.

[0041] In an embodiment of the present invention, the implementation method of building a hybrid assembly of front-end and back-end SDK components based on front-end components and APIs is as follows: when the front-end component is a single component, the single component is associated with the API, wherein the path of the associated API and request parameter information are specified in the configuration of the single component; when the front-end component is multiple components, the multiple components are formed into a template component; each component in the template component is associated with the corresponding API to obtain a component library of the template component.

[0042] For example, when the front-end component is a single component, the REST API, as an important interface for front-end and back-end data interaction, plays a key role in connecting the component with the back-end data. By associating the component with the corresponding API, the component can know where to obtain the required data, thus realizing the dynamic configuration of the data source; when the front-end component is multiple components, each component has different display functions, such as displaying chart data, and displaying text information. Then associate the corresponding data source API for each component, that is, clarify the data acquisition path for each component. In this way, multiple components are organically combined to form a template component with specific functions and layout structure.

[0043] In an embodiment of the present invention, the 2D / 3D component library management unit 150 includes component / scene management, component / scene downloading and integration. The component / scene management is used to dynamically generate component management through the mixed assembly of front-end and back-end SDK components, and to manage the mixed assembly of front-end and back-end SDK components based on a preset method; the component / scene downloading and integration is used for online compilation, online packaging, package storage and downloading of the mixed assembly of front-end and back-end SDK components.

[0044] That is to say, the component / scene management in the 2D / 3D component library management unit 150 provides two main management methods. One is to manage by dynamically generating components through the mixed assembly of front-end and back-end SDK components. This means that the components generated by the front-end and back-end SDK component synthesis unit 130 mentioned above can be directly incorporated into the component library management system, ensuring the consistency and synergy of the component source and component library management; the other is to manage the mixed assembly of front-end and back-end SDK components based on the preset method, that is, to manage the front-end and back-end SDK components by uploading component codes. This method is more flexible. For some existing, externally developed or specially customized component codes, as long as they meet certain specification requirements, they can be uploaded and included in the management, which broadens the component source channel of the component library. Furthermore, through the two management mechanisms, components and scenes generated by various channels can be orderly integrated into the component library, which is convenient for subsequent search, use, and unified maintenance operations, so that the component library can be continuously enriched and improved to meet the needs of different business scenarios for different types of components and scenes.

[0045] Component / scenario download and integration has many practical functions. First, it provides the online compilation function of front-end and back-end SDK components, which can compile the component code according to different usage environments and platform requirements to ensure that it can run correctly; then the online packaging function is used to package and integrate the compiled components for easy transmission and storage; then the components are packaged and stored to form a downloadable component package; finally, the download function is provided to facilitate users to obtain the component package. Moreover, the downloaded component package can be easily and simply integrated and referenced into the corresponding project. Once introduced, the business data can be directly presented, which reduces the technical complexity and workload faced by users in the process of integrating components, making the use of components more convenient and efficient.

[0046] In an embodiment of the present invention, the 2D / 3D component library management unit 150 also includes component / scene sharing, which is used for online preview, adding to a shopping cart, and one-click subscription of a target component or scene.

[0047] In other words, by providing online preview, adding to shopping cart, one-click subscription and other methods, we support other systems to subscribe to and share front-end and back-end SDK components and scenarios. The online preview function allows users of other systems to view the actual effects of components or scenarios in advance and determine whether they meet their needs; the adding to shopping cart method is similar to the operation logic of e-commerce shopping, which is convenient for users to temporarily store and manage components or scenarios of interest; and the one-click subscription function allows systems that want to use these components or scenarios to quickly complete the subscription operation, and then they can easily obtain and use them, realizing efficient sharing of components and scenarios between different systems.

[0048] In an embodiment of the present invention, the twin scene building unit 140 is used to support multiple twin scene building methods, multiple scene modes, and visual dynamic configuration of front-end and back-end SDK components.

[0049] Among them, the multi-scene mode includes but is not limited to 2D, 3D and other multi-scene applications.

[0050] Among them, it supports visual dynamic configuration of front-end and back-end SDK components, including component layout, component size, legend color, legend font, display field, etc.

[0051] That is to say, the twin scene building unit 140 can self-layout and build real-time applications for customized and complex scenes by dragging and dropping. It supports multiple scene modes (2D, 3D, etc.) and multiple data linkage functions (between components, page migration, local data linkage, etc.), and also supports visual dynamic configuration of front-end and back-end SDK components. This unit uses the components generated and managed previously to build a twin scene with practical application value, which is a key link in combining components into a complete application scene.

[0052] In an embodiment of the present invention, the twin presentation and dynamic publishing unit 160 is also used to publish the constructed scene and generate a corresponding access link for the published scene.

[0053] That is to say, the twin presentation and dynamic publishing unit 160 is mainly responsible for the preview and publishing of the twin scene. It can publish the twin scene as a system application for user access with one click, or put the scene component into the 2D / 3D component library for other system integration and application. This enables the twin scene to be truly put into use, and to be shared and reused between different systems, completing the complete process from component generation, synthesis, scene construction to final application release.

[0054] According to the cloud network resource management system of the embodiment of the present invention, the 2D / 3D front-end component code generation unit is used to generate the front-end component code according to the user semantics, and generate the front-end component based on the front-end component code; the API automatic generation unit is used to generate SQL query statements according to the user semantics, and generate APIs based on the SQL query statements; the front-end and back-end SDK component synthesis unit is used to build a mixed assembly of front-end and back-end SDK components based on the front-end components and APIs, and use the mixed assembly of front-end and back-end SDK components in the twin scene building unit; the 2D / 3D component library management unit is used to store the mixed assembly of front-end and back-end SDK components; the twin presentation and dynamic publishing unit is used to receive the scene built by the twin scene building unit and preview it. The various units of the entire system of the system cooperate with each other, and can flexibly respond to the diverse needs expressed by different user semantics. Whether it is creating a new front-end display, developing a back-end interface, building a twin scene, etc., it can timely adjust and generate corresponding content according to the changes in specific business scenarios, so that the cloud network resource management system can better adapt to the cloud network resource-related management, monitoring and presentation requirements under different scales and different application scenarios, and enhance the versatility and adaptability of the system.

[0055] The present invention also proposes a cloud network resource management method, such as Figure 2 As shown, the cloud network resource management method includes:

[0056] S210, obtaining user semantics.

[0057] S220, generating a front-end component code according to user semantics, and generating a front-end component based on the front-end component code.

[0058] S230, generating a SQL query statement according to user semantics, and generating an API based on the SQL query statement.

[0059] S240, builds a mixed assembly of front-end and back-end SDK components based on front-end components and APIs, and uses the mixed assembly of front-end and back-end SDK components in a twin scene construction unit.

[0060] In an embodiment of the present invention, it also includes storing a mixed assembly of front-end and back-end SDK components.

[0061] In an embodiment of the present invention, it also includes receiving a scene built by a twin scene building unit and previewing it.

[0062] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0063] According to one aspect of an embodiment of the present invention, an electronic device is provided.

[0064] Figure 3 Schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Figure 3 As shown, the electronic device may include one or more ( Figure 3 Only one is shown in the figure) processor 102 (processor 102 may include but is not limited to a microprocessor (Microprocessor Unit, referred to as MPU) or a programmable logic device (Programmable logic device, referred to as PLD)) and a memory 104 for storing data. In an exemplary embodiment, the electronic device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 3 The structure shown is for illustration only and does not limit the structure of the above terminal device. Figure 3 More or fewer components as shown, or with Figure 3 Equivalent functions or comparisons shown Figure 3 A different configuration with more features is shown.

[0065] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the cloud network resource management method in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implementing the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the terminal device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0066] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the switching device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0067] The present invention proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to execute a cloud network resource management method.

[0068] The applicant of the present invention has made a detailed explanation and description of the implementation examples of the present invention in conjunction with the drawings in the specification. However, those skilled in the art should understand that the above implementation examples are only preferred implementation schemes of the present invention, and the detailed description is only to help readers better understand the spirit of the present invention, but not to limit the scope of protection of the present invention. On the contrary, any improvements or modifications based on the inventive spirit of the present invention should fall within the scope of protection of the present invention.

[0069] In addition, each functional unit in each embodiment of the present invention may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0070] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present invention. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.

[0071] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, rather than to limit them. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the above embodiments, or replace some of the technical features therein by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. Any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present invention should be covered within the protection scope of the present invention.

Claims

1. A cloud network resource management system, characterized in that: include: A 2D / 3D front-end component code generation unit, used to generate front-end component codes according to user semantics, and generate front-end components based on the front-end component codes; An API automatic generation unit, used to generate a SQL query statement according to the user semantics, and generate an API based on the SQL query statement; A front-end and back-end SDK component synthesis unit, used to build a mixed assembly of front-end and back-end SDK components based on the front-end components and the API, and to use the mixed assembly of the front-end and back-end SDK components in a twin scene building unit; A 2D / 3D component library management unit, used to store the mixed assembly of the front-end and back-end SDK components; The twin presentation and dynamic publishing unit is used to receive the scene built by the twin scene building unit and preview it.

2. The cloud network resource management system according to claim 1, characterized in that: The 2D / 3D front-end component code generation unit is connected to the intent model, wherein the front-end component code is generated according to the user semantics, including: Obtaining the user semantics; The user semantics are analyzed based on the intent model and the front-end technology stack to generate various types of front-end component codes that meet the target requirements, including graph, tree, column, and point types.

3. The cloud network resource management system according to claim 2, characterized in that: The user semantics is analyzed based on the intent model and the front-end technology stack to generate various types of front-end component codes that meet the target requirements, including: Inputting the user semantics into the intention model to obtain intention information of the user semantics, wherein the intention information includes component type and data information; The component infrastructure of the component type is determined based on the front-end technology stack, and the component infrastructure of the component type and the data information are integrated to generate the front-end component code.

4. The cloud network resource management system according to claim 1, characterized in that: The API automatic generation unit is connected to the Text2SQL technology, wherein, according to the user semantics, an SQL query statement is generated, including: Perform semantic analysis on the user semantics based on natural language processing technology NLP to obtain the query intention and key information of the user semantics; Mapping the key information into a database to construct a sentence framework corresponding to the query intent; The statement framework is filled based on the mapping result to obtain the SQL query statement.

5. The cloud network resource management system according to claim 1, characterized in that: Also includes: When the SQL query statement is generated, the conditions of the SQL query statement are dynamically configured and modified in a variable manner based on user needs.

6. The cloud network resource management system according to claim 1, characterized in that: Building a mixed assembly of front-end and back-end SDK components based on the front-end components and the API includes: In the case where the front-end component is a single component, associating the single component with the API, wherein a path and request parameter information associated with the API are specified in the configuration of the single component; In the case where the front-end component is a plurality of components, the plurality of components are formed into a template component; Each component in the template component is associated with the corresponding API to obtain a component library of the template component.

7. The cloud network resource management system according to claim 1, characterized in that: The 2D / 3D component library management unit includes component / scene management, component / scene downloading and integration. The component / scene management is used to dynamically generate component management through the mixed assembly of the front-end and back-end SDK components, and to manage the mixed assembly of the front-end and back-end SDK components based on a preset method; the component / scene downloading and integration is used for online compilation, online packaging, package storage and downloading of the mixed assembly of the front-end and back-end SDK components.

8. The cloud network resource management system according to claim 7, characterized in that: The 2D / 3D component library management unit also includes component / scene sharing, which is used for online preview, adding to shopping cart, and one-click subscription of target components or scenes.

9. The cloud network resource management system according to claim 1, characterized in that: The twin scene building unit is used to support multiple twin scene building methods, multiple scene modes, and visual dynamic configuration of the front-end and back-end SDK components.

10. The cloud network resource management system according to claim 1, characterized in that: The twin presentation and dynamic publishing unit is also used to publish the constructed scene and generate a corresponding access link for the published scene.

Images