An Agile Development and Deployment Method for Desktop Clients Based on a Data Network Architecture

Abstract

The present invention provides a method, device and equipment for agile development and deployment of desktop clients based on a data networking architecture. Obtain client configuration parameters; the client configuration parameters include: functional parameters and interface parameters corresponding to the client; determine the corresponding data networking architecture components according to the functional parameters, and connect the service interface corresponding to the data networking architecture components to the middleware; the data networking architecture components are used to provide data networking services, and the middleware is used to realize the communication between the client and the data networking architecture components; generate components for each function according to the functional parameters and the data networking architecture components, and generate the user interface of the client according to the interface parameters; package the functional components, the user interface and the target program corresponding to the middleware into an executable file for deploying the data networking client. The functional components of the client communicate with the data networking architecture components through the middleware, and the functional components are separately encapsulated, which improves the deployment efficiency while realizing the data networking services of the client.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and storage medium for agile development and deployment of a desktop client based on a digital networking architecture. Background Art

[0002] In the long history of technological development, the emergence of the Internet is undoubtedly a great milestone. It connects global information in a digital form and has greatly changed the way people live and work. In the Internet era, information dissemination and simple application interaction are its main features, and the client mainly plays the role of displaying information and realizing basic functions. However, with the rapid development of the times, the amount of data has shown a geometric growth, and the sources of data have become more and more extensive, including various fields such as IoT devices, industrial control systems, and medical monitoring systems. These massive, multi-source, and heterogeneous data have put forward higher requirements for data processing and utilization. When facing such a complex data environment, the Internet gradually exposed its limitations. Its architecture is unable to cope with data integration, in-depth analysis, and cross-domain data interaction. At this time, the Internet of Data came into being, which is an inevitable product of the development of the Internet to a certain stage.

[0003] The Internet of Data is a virtual data network based on the Internet. Through open software architecture and standardized protocols, it efficiently connects various data platforms and systems, supports the interconnection and interoperability of heterogeneous, heterogeneous, and heterogeneous data, and forms a data space of "data interconnection, on-demand scheduling, intra-domain autonomy, and inter-domain collaboration". In the Internet of Data environment, the functions undertaken by the client are no longer limited to information display and simple interaction in the Internet era. It needs to become a powerful data interaction and processing terminal, supporting complex data analysis and visualization functions, and meeting the personalized needs of different industries and users for data utilization. This makes the market's demand for clients increasingly diversified and complex, with new standards from functional requirements to performance requirements, from user experience to data security. With a new perspective and architectural design, the Internet of Data is committed to breaking data silos and realizing data interconnection and deep mining in a broader sense. Its infrastructure is becoming increasingly rich in its continuous development, covering more advanced data transmission protocols, storage methods, and processing algorithms, and can better cope with the challenges brought by complex data.

[0004] However, the waterfall model or iterative model used in traditional client development and deployment was formed in the context of the Internet era. Although these models were reasonable in relatively simple data and application scenarios at the time, the disadvantages of the waterfall model and iterative model became increasingly obvious in the complex data ecology and application scenarios of the Internet of Things: the long development cycle makes it difficult for the client to keep up with the rapid development of the Internet of Things, and the inability to respond to changes in user needs in a timely manner makes the client clumsy when facing diverse data application needs; and the lack of user participation and feedback in the development process makes it impossible for the client to accurately meet the high expectations of Internet of Things users for data processing and utilization, resulting in a huge gap between the client and user expectations. This gap has seriously hindered the promotion and development of Internet of Things applications, prompting us to seek a new model that is more suitable for Internet of Things client development and deployment. Summary of the invention

[0005] In view of the above problems, embodiments of the present invention are proposed to provide a method, device and equipment for agile development and deployment of desktop clients based on a data networking architecture, which overcome the above problems or at least partially solve the above problems.

[0006] In a first aspect, an embodiment of the present application discloses a method for agile development and deployment of a desktop client based on a data networking architecture, the method comprising:

[0007] Obtain client configuration parameters; the client configuration parameters include: functional parameters and interface parameters corresponding to the client;

[0008] Determine the corresponding data networking architecture component according to the functional parameters, and connect the service interface corresponding to the data networking architecture component to the middleware; the data networking architecture component is used to provide data networking services, and the middleware is used to realize the communication between the client and the data networking architecture component;

[0009] Generate a functional component for each function according to the functional parameters and the data networking architecture component, and generate a user interface of the client according to the interface parameters;

[0010] The functional components, the user interface and the target program corresponding to the middleware are packaged into an executable file for deploying a data networking client.

[0011] Optionally, generating a functional component for each function according to the functional parameter and the data networking architecture component includes:

[0012] Encapsulate the functional components of each function separately to form a functional component library;

[0013] Generating a user interface of the client according to the interface parameters includes:

[0014] A user interface of the client is generated according to the interface parameters and preset template data.

[0015] Optionally, packaging the functional components, the user interface, and the target program corresponding to the middleware into an executable file for deploying a data networking client includes:

[0016] The dependent libraries, function libraries, environment parameters, and configuration information corresponding to the target program are packaged into a container image through a container engine;

[0017] The container image of the client is deployed to the cloud through the kubernetes tool.

[0018] Optionally, after generating a functional component for each function according to the functional parameters and the data networking architecture component, and generating a user interface of the client according to the interface parameters, the method further includes:

[0019] Testing the functional component and the user interface by using a preset first test command;

[0020] The interactive operation of the user interface and the communication between the functional component and the data network architecture component are tested through a preset second test command to obtain a test result.

[0021] Optionally, the step of connecting the service interface corresponding to the data networking architecture component to a middleware includes:

[0022] Determine the target function that the middleware needs to provide according to the functional parameters and the data network architecture components;

[0023] According to the target function, the service interface corresponding to the data network architecture component is implemented in the middleware.

[0024] Optionally, after the functional components of each function are individually packaged to form a functional component library, the method further includes:

[0025] For any functional component, iteratively update the functional component;

[0026] The target programs corresponding to the iteratively updated functional components, middleware and user interface are repackaged into executable files.

[0027] Optionally, the method further comprises:

[0028] Generate different script files for deploying the executable files according to different deployment environments;

[0029] Run the script file and deploy the executable file on the client.

[0030] In a second aspect, the embodiment of the present application discloses a desktop client agile development and deployment device based on a data networking architecture, including:

[0031] The acquisition module is used to acquire client configuration parameters; the client configuration parameters include: function parameters and interface parameters corresponding to the client;

[0032] A matching module, used to determine the corresponding data networking architecture component according to the functional parameters, and connect the service interface corresponding to the data networking architecture component to the middleware; the data networking architecture component is used to provide data networking services, and the middleware is used to realize the communication between the client and the data networking architecture component;

[0033] A packaging module, used to generate a functional component for each function according to the functional parameters and the data networking architecture component, and to generate a user interface of the client according to the interface parameters;

[0034] The packaging module is used to package the functional components, the user interface and the target program corresponding to the middleware into an executable file for deploying a data networking client.

[0035] In a fourth aspect, an embodiment of the present application further discloses an electronic device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the agile development and deployment method of desktop clients based on the Internet of Things architecture as described in the first aspect are implemented.

[0036] In a fifth aspect, an embodiment of the present application further discloses a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the agile development and deployment method of a desktop client based on a digital networking architecture as described in the first aspect are implemented.

[0037] In an embodiment of the present application, client configuration parameters are obtained; the client configuration parameters include: functional parameters and interface parameters corresponding to the client; the corresponding digital networking architecture component is determined according to the functional parameters, and the service interface corresponding to the digital networking architecture component is connected to the middleware; the digital networking architecture component is used to provide digital networking services, and the middleware is used to realize communication between the client and the digital networking architecture component; a functional component for each function is generated according to the functional parameters and the digital networking architecture component, and a user interface of the client is generated according to the interface parameters; the functional component, the user interface and the target program corresponding to the middleware are packaged into an executable file for deploying the digital networking client. When generating a client program, the present application first obtains the client configuration parameters, determines the functional requirements of the client, determines the corresponding digital networking architecture components based on the functional requirements of the client, and connects the service interface that realizes the communication between the client and the digital networking architecture components to the middleware. At the same time, each function of the client is separately encapsulated as a functional component, so that after the executable file is formed to deploy the digital networking client, the functional components of the client can communicate with the digital networking architecture components through the middleware to realize the digital networking services of the client. In addition, since the present application has separately encapsulated the functions, when the functions are iterated, only the functional components need to be iteratively updated, which simplifies the cumbersome process of developing digital networking clients in related technologies, and can conveniently realize the deployment of digital networking clients through executable files, thereby improving deployment efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a flowchart of the steps of a method for agile development and deployment of a desktop client based on a data networking architecture provided by an embodiment of the present invention;

[0039] Figure 2 This is a diagram of a data network architecture provided by an embodiment of the present invention;

[0040] Figure 3 It is a schematic diagram of a scaffold based on a data networking architecture provided by an embodiment of the present invention used in a business scenario;

[0041] Figure 4 It is a development flow chart of a digital networking client program provided by an embodiment of the present invention;

[0042] Figure 5 A block diagram of the development, deployment and maintenance architecture of a digital networking client program provided by an embodiment of the present application is shown;

[0043] Figure 6 It is a block diagram of a desktop client agile development and deployment device based on a data networking architecture provided by an embodiment of the present invention;

[0044] Figure 7An electronic device provided by an embodiment of the present invention;

[0045] Figure 8 This is another electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0046] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0047] The concepts and background involved in this application are explained below.

[0048] Digital Internet Architecture: Digital Internet refers to a network that uses digital objects as the core and realizes the unique identification, location, access and management of data through digital object identifiers (DOI). It is an important symbol of the development of the big data era towards data integration. The basic architecture of the digital Internet mainly includes digital object registration agencies, digital object analysis agencies, digital object storage agencies, digital object service agencies, etc., which provide support for the interconnection and interoperability of data.

[0049] The infrastructure in the Internet of Things architecture includes the following key components:

[0050] Data Entity or System: Each data entity consists of three parts: unique identification, metadata, and data entity. The representation object can be any person, object, process, service, and various types of data.

[0051] Data Acquisition: Data entities maintained in the Internet of Things collect required data, such as temperature, pressure, vibration, position, speed, etc. These data collected by special means are the basis for creating and maintaining data entities.

[0052] Network Organizing: Organizing independent nodes and sites into a customized data network, and transmitting the data generated by the nodes at the designated site to each site, node or cloud platform.

[0053] Data Storage and Processing: The collected data needs to be stored in a safe place (usually a node or site) and preprocessed to remove noise and outliers. Traditional data warehouses and database management systems are important components of this layer, and of course there are some new methods for data storage and processing.

[0054] Digital Model and Simulation: Based on the collected data, one or more virtual models are created to represent the behavior of a physical entity or system. This may involve complex mathematical models and simulation tools. Digital models can be updated in real time to reflect changes in the physical world and predict future behavior.

[0055] Analysis and Visualization: Using data analysis and machine learning algorithms, the collected data is deeply studied to extract useful information and insights. The results can be presented to users through visualization tools for easy understanding and decision-making.

[0056] Control and Optimization: Based on the results produced by digital entities after calculation, physical entities or systems can be controlled and optimized. This may involve automatically adjusting settings, predictive maintenance, fault diagnosis, etc.

[0057] Security and Privacy: Security and privacy are very important aspects of the entire Internet of Things infrastructure. It is necessary to ensure the secure transmission, storage, and processing of data and comply with relevant regulations, such as the General Data Protection Regulation (GDPR).

[0058] Each of the above parts constitutes the basic architecture of the data network. Currently, a complete set of client development and deployment processes is urgently needed for subsequent maintenance and iteration under the current architecture. Based on the above data network structure, this application provides an agile development and deployment method for desktop clients based on the data network architecture.

[0059] Specifically, agile development is an iterative, incremental methodology used in software engineering and other project management fields that emphasizes flexibility and the ability to respond to changes. It aims to adapt to changes in demand and market uncertainty through rapid feedback loops and continuous delivery of value. Agile development methods are particularly suitable for the development of digital Internet projects because the digital Internet environment is often highly complex and uncertain. Agile methods allow development teams to quickly adjust their direction in the face of uncertainty and change, which is very valuable for dealing with the diversity of digital Internet devices, large amounts of data, and potential security challenges. Agile methods emphasize the rapid construction of minimum viable products (MVPs) and then iterate through user feedback and market reactions. In the digital Internet environment, it can help companies test new devices, services, and business models faster, reduce risks, and accelerate the pace of innovation. Agile methods emphasize customer participation and continuous integration. In digital Internet projects, this can be achieved through real-time data feedback and user interaction, so that products and services can more closely reflect real needs and evolve with technological development and market demand. Agile methods use flexible architectural design to support scalability and rapid adaptation to changes. In the Internet of Things, this architectural design helps cope with the growth in the number of devices, the addition of new device types, and changes in data analysis needs.

[0060] In summary, agile development can improve the scalability and compatibility of the Internet of Things, and use digital object identifiers (DOI) and digital object metadata (DOM) as interfaces of components of the Internet of Things infrastructure to achieve communication and interaction between the client and components of the Internet of Things infrastructure. The specific contents of deploying the Internet of Things client using agile development provided in this application are as follows.

[0061] refer to Figure 1 , which shows a flowchart of the steps of a method for agile development and deployment of a desktop client based on a data networking architecture provided by an embodiment of the present application, the method comprising:

[0062] Step 101, obtaining client configuration parameters; the client configuration parameters include: functional parameters and interface parameters corresponding to the client.

[0063] In the embodiment of the present invention, the client configuration parameters may be determined based on user requirements and application scenarios, including: functional parameters and interface parameters.

[0064] Specifically, before developing the client program, the client prototype needs to be designed. First, user needs analysis and design are carried out. User needs and functional requirements are determined by analyzing user needs and application scenarios to ensure that the software prototype can meet the actual needs of users. Interface design, design the layout, color matching, font size, etc. of the user interface, so that users can easily interact based on the user interface to ensure a good user experience. Interaction design: including navigation design, interaction logic, feedback mechanism, etc. Functional design, to ensure the functional completeness and good extensibility of the software, to meet the basic needs of users, and to expand and optimize functions according to user feedback and needs. The above design can form design documents such as prototype drawings. The above design process can obtain client configuration parameters that characterize client needs, which are used for the subsequent development of client programs based on client configuration parameters.

[0065] Step 102, determine the corresponding digital networking architecture component according to the functional parameters, and connect the service interface corresponding to the digital networking architecture component to the middleware; the digital networking architecture component is used to provide digital networking services, and the middleware is used to realize communication between the client and the digital networking architecture component.

[0066] In the embodiment of the present invention, the data networking architecture component corresponding to the client can be determined based on the function parameter. The data networking architecture component is a component used to provide data networking services to the client. Based on the function parameter, it can be determined which data networking architecture components the client needs to interact with in order to implement the function. Figure 2 , Figure 2 A diagram of a digital networking architecture is shown. Specifically, based on the prototype of the client mentioned in step 101, appropriate components of the digital networking architecture can be matched, such as: digital object registration service, digital object resolution service, digital object storage service, digital object service, etc. In order to achieve communication between the client and the components of the digital networking architecture, middleware needs to be deployed on the client. The middleware is software between the operating system and the applications running on it. It implements communication and data management of distributed applications and is used to coordinate communication between different systems and components. It is a bridge that connects applications directly to underlying resources. Based on the functional design corresponding to the functional parameters, the service interface that implements communication between the functional components and the digital networking architecture components can be connected to the middleware. For example, based on the digital networking architecture, the application programming interface (API) provided by the following services can be connected to the middleware:

[0067] Data Service Node And Site (DSNS): It is the basic unit of the data network, responsible for encapsulating raw data into digital objects (DO) and providing data service interfaces. The middleware supports operations such as creation, access, update and deletion of digital objects.

[0068] Data Service Register (DSR): It is the core component of the Internet of Things. It is responsible for managing the metadata of digital objects and providing metadata registration and search services. The middleware supports the discovery and retrieval of digital objects.

[0069] Data Resources Manager (DRM): It is the management component of the data network and is responsible for managing the data resource directory of the data network, including data service nodes, data service registration center, data service gateway, etc., as well as the classification, labeling, evaluation and other information of data resources. The middleware supports the organization and management of access data resources.

[0070] Data Service Gateway (DSG): It is the access component of the data network and is responsible for providing a unified data service access portal. The middleware supports access control and protocol forwarding to multiple data service nodes, as well as data service aggregation and conversion.

[0071] Data Service Search Engine (DSSE): It is the search component of the Internet of Things, responsible for providing cross-domain, cross-platform, and cross-system data service search functions. The middleware supports access to data service retrieval based on multiple dimensions such as keywords, semantics, and location, as well as data service recommendation and ranking functions.

[0072] Data Integration Services (DIS): It is an application component of the Internet of Things and is responsible for providing data fusion services. The middleware supports access to digital object-based data analysis, mining, visualization and other functions, as well as the orchestration and combination of data services.

[0073] Data Service Assistant Management (DSAM): It is an auxiliary component of the data network and is responsible for providing auxiliary management functions for data services, including monitoring, evaluation, optimization, and scheduling of data services, as well as measurement and evaluation of indicators such as the quality and performance of data services.

[0074] After the above service interface is connected to the middleware, the functional components of the client and the data network architecture components can communicate with each other through the services provided by the middleware.

[0075] Optionally, step 102 includes:

[0076] Sub-step 1021, determining the target function that the middleware needs to provide according to the functional parameters and the data network architecture components;

[0077] Sub-step 1022: Implementing the service interface corresponding to the data networking architecture component in the middleware according to the target function.

[0078] In the embodiment of the present invention, for sub-steps 1021 and 1022, by referring to the components of the data networking infrastructure, it is possible to ensure that the design and implementation of the client are more in line with the overall requirements of the system, and improve the overall performance of the system and user experience. Specifically, after determining the functional parameters of the client, the client functional program design can be implemented by referring to the components of the data networking architecture.

[0079] Furthermore, according to the functional design of the client determined by the functional parameters, the API provided by the Internet of Things infrastructure component service can be connected to the middleware. The API provides a standardized way for different software systems, services and applications to communicate and interact with each other to achieve data and function sharing. By accessing the API of the middleware, the client can interact with the Internet of Things architecture component, obtain or submit data, and achieve connection with the Internet of Things infrastructure component.

[0080] Step 103: Generate a functional component for each function according to the functional parameters and the data network architecture component, and generate a user interface of the client according to the interface parameters.

[0081] In an embodiment of the present invention, the client code can be written according to the functional parameters and interface parameters of the client, as well as the components of the selected digital networking architecture. The client code can be implemented using a customized template to realize modular, componentized, and reusable client functional components and back-end services (middleware) that interact with digital object services, and realize the client functions and interfaces according to the API requirements of the digital networking architecture.

[0082] Specifically, a high-performance system programming language (Rust) can be used as the back-end development language of the client, and Rust's high performance, security, concurrency and cross-platform nature can be used to achieve communication and interaction between the client and components of the Internet of Things infrastructure, as well as the client's business logic and data processing; for example, the process of implementing middleware in Rust can include: defining the structure of the middleware, including the input and output of the middleware, implementing the business logic of the middleware, and designing the middleware to be modular to make the code easier to maintain and expand.

[0083] For generating user interfaces based on interface parameters, the front-end view framework (Vue.js, Vue) can be used as the client-side front-end development framework, and the responsiveness, componentization, ease of use and ecosystem of Vue can be used to implement the client-side user interface and user interaction, as well as the client-side data binding and state management. Using the network assembly binding generator (wasm-bindgen), rust is compiled into a network assembly module (WebAssembly, wasm), and the interaction between the back-end using rust and the front-end using vue is implemented, improving the performance and compatibility of the client.

[0084] In this application, the functions of the client are split and each function is encapsulated as a separate functional component, so that when the functions are subsequently iterated, only a single functional component needs to be iteratively updated, thereby improving the scalability of the client.

[0085] Optionally, step 103 includes:

[0086] Sub-step 1031, encapsulating the functional components of each function separately to form a functional component library;

[0087] Sub-step 1032, generating a user interface of the client according to the interface parameters and preset template data.

[0088] In the embodiment of the present invention, for sub-step 1031 and sub-step 1032, reference may be made to the description of step 103, which will not be repeated here.

[0089] Step 104: Pack the functional components, the user interface and the target program corresponding to the middleware into an executable file for deploying a data networking client.

[0090] In an embodiment of the present invention, the client program and middleware implemented through the above steps can be packaged into an executable file, and the executable file can be run on the client to implement the deployment of the data network service on the client.

[0091] For example, you can use a module packaging tool (Webpack) to package the client code into an executable file to build and optimize the client.

[0092] Optionally, step 104 includes:

[0093] Sub-step 1041, packaging the dependency library, function library, environment parameters, and configuration information corresponding to the target program into a container image through a container engine;

[0094] Sub-step 1042, deploying the container image of the client to the cloud through the container orchestration system tool (Kubernetes, k8s).

[0095] In an embodiment of the present invention, for sub-step 1041 and sub-step 1042, the client code can be packaged into an executable file and deployed to the target platform and environment, such as a PC (personal computer), a mobile device, the cloud, etc., and the communication and interaction between the client and the components of the Internet of Things infrastructure can be achieved through the digital object resolution mechanism.

[0096] For example, before deployment, you can use container management tools (Docker) to package the client code into a container image to achieve cross-platform and cross-environment deployment of the client; use kubernetes tools to deploy the client's container image to the cloud to achieve elastic, scalable and manageable deployment of the client; use a network server and reverse proxy tool (Nginx) as the client's reverse proxy and load balancer to achieve high availability and high performance deployment of the client.

[0097] Optionally, after step 103, the method further includes:

[0098] Step 105, testing the functional component and the user interface by using a preset first test command;

[0099] Step 106, testing the interactive operation of the user interface and the communication between the functional component and the data network architecture component through a preset second test command to obtain a test result.

[0100] In the embodiment of the present invention, after the client code is generated, the client code is also tested, including unit testing, integration testing and system testing, to check whether the client's functions, interfaces, performance, security and other aspects conform to the Internet of Things architecture and application scenarios. The first test command and the second test command can be constructed through a preset test template.

[0101] Specifically, you can use the build system and package manager (cargo) to manage Rust-based dependencies and tests, run Rust unit tests and integration tests, and check Rust's code quality and functional correctness; use the test framework tool (Jest) to run front-end Vue unit tests and integration tests to check Vue's code quality and functional correctness; use the automated testing tool (Selenium) to run client system tests to check the client's user interface and user interaction, as well as the communication and interaction between the client and components of the Internet of Things infrastructure.

[0102] Optionally, after sub-step 1031, the method further includes:

[0103] Step 107, for any functional component, iteratively update the functional component;

[0104] Step 108: repackage the target programs corresponding to the iteratively updated functional components, middleware, and user interface into an executable file.

[0105] In the embodiment of the present invention, for any functional component, the functional component can be iteratively updated, and the target program corresponding to the iteratively updated functional component, middleware and user interface can be repackaged into an executable file to implement a version update of the program.

[0106] Optionally, the method further comprises:

[0107] Step 109, generating different script files for deploying the executable file for different deployment environments;

[0108] Step 110: Run the script file to deploy the executable file on the client.

[0109] In the embodiment of the present invention, with respect to step 109 and step 110, after the executable file is generated, the executable file may be deployed on the client.

[0110] Specifically, after the development is completed, all dependencies, execution commands, deployment commands, unit tests, packaging commands, etc. included in the development are integrated into a complete set of scaffolding instructions for maintenance. Scaffolding instructions can exist in the form of script files. When users deploy the data networking client, they can implement one-click deployment of the client by running the script file.

[0111] Specifically, the one-click deployment process may include: running a script file; parsing the script file to obtain corresponding parsing parameters, which may include functional components and middleware required by the client; selecting a pre-set corresponding template framework based on the parsing parameters, which may be an architecture formed by a client program and middleware; downloading the template framework to generate project files required to build the client based on the template framework.

[0112] refer to Figure 3 , Figure 3A schematic diagram of a scaffold based on a data networking architecture provided by an embodiment of the present application is shown for use in a business scenario, wherein a client program and a middleware service are deployed on the client through scaffolding instructions, and the front end of the client program can be a front-end page formed by a front-end development framework such as Hypertext Markup Language (HTML), a framework for application user interface (JavaServer Faces, JSF), a dynamic web page development tool (Java Server Pages, JSP), a server-side applet (Servlet), an asynchronous script and extensible markup language (Asynchronous JavaScript and XML, Ajax), and Vue. The back-end functional components of the client may include basic client functions and client extension functions. The basic client functions include: user management component, authority management component, Really Simple Syndication component (RSS), and publishing component (News Release), and other basic functional components of the client program. For example, the client extension functions include: data service search engine, data service auxiliary management, data directory management and other functional components related to the Internet of Things architecture services. The client is also deployed with middleware implemented in Rust, which is connected to the data service nodes and sites, and the API of the Internet of Things services. Through the middleware, the client's functional components can interact with the services provided by components such as data service objects, data object resolution services, digital object storage services, and digital object registration services in the Internet of Things architecture components to obtain corresponding service support. In addition, the client program can use the wasm-bindgen library to compile the backend implemented in rust into a WebAssembly (wasm) module to achieve interactive operations between the backend and the frontend, and improve the performance and compatibility of the client; and after generating the client program, the cargo tool, jest tool, and selenium tool are also used to test the performance of the entire program. The above-mentioned digital network client of the present application can be applied in the fields of government affairs, finance, education, medical care, etc. to realize the interconnection and interoperability of data. For example, in medical application scenarios, medical institutions can use the digital network client to meet the medical industry's needs to release data value while ensuring that medical data does not leave the domain and meets privacy security, thereby realizing efficient circulation of medical data value within the hospital, between hospitals, and internationally.

[0113] refer to Figure 4 , Figure 4A development flow chart of a digital networking client program provided by an embodiment of the present application is shown. It includes: a stage of confirming requirements, a stage of setting component modular standards, a stage of client development and testing, and a stage of client deployment and maintenance. Specifically, in the stage of confirming requirements, based on user requirements, the functions of the client are determined, and an interface prototype is designed. In the stage of setting component modular standards, based on the client functions determined in the requirements stage, the standards of middleware, digital networking modules and components are designed according to the digital networking architecture. After the design is completed, if the requirements change, the interface prototype is updated. If the requirements have not changed and the review is passed, the client development and testing stage is entered. Through iterative design, the modularization and componentization of client functions are realized, the middleware is realized, the requirements are refined, and the development is completed and entered into testing. If the test is correct, the client deployment and maintenance stage is entered, and the gray version of the client is deployed. After going online, wait for user feedback, and iteratively update the client components based on user feedback.

[0114] refer to Figure 5 , Figure 5 The following is a block diagram of a development, deployment and maintenance architecture of a digital networking client program provided by an embodiment of the present application, including:

[0115] Requirements analysis: Determine the functional and interface requirements of the client. Analyze user needs and application scenarios.

[0116] Configuration parameter acquisition: Determine the client configuration parameters based on demand analysis, including functional parameters and interface parameters.

[0117] Matching of data networking architecture components: Determine the corresponding data networking architecture components according to the functional parameters. Connect the service interface of the data networking architecture component to the middleware to realize the communication between the client and the data networking architecture component through the middleware.

[0118] Functional component generation: Generate a functional component for each function. Each functional component is packaged separately to form a functional component library for subsequent iterations.

[0119] User interface generation: Generate the client's user interface based on interface parameters and preset template data.

[0120] Middleware implementation: Implement middleware to support communication between clients and components of the Internet of Things architecture. Middleware can include functions such as API calls, data transmission, and protocol conversion.

[0121] Packaging and deployment: Packaging the target programs corresponding to functional components, user interfaces, and middleware into executable files. This includes packaging executable files into files that are suitable for containerization and cloud deployment according to actual needs.

[0122] Testing: Unit testing and integration testing of functional components and user interfaces. Testing of user interface interaction and communication.

[0123] Iterative update: Iteratively update functional components based on test results and user feedback. Repackage the updated functional components.

[0124] Deployment script generation: Generate deployment scripts for different deployment environments. Run the script to deploy the executable file to the client.

[0125] User documentation and help: Create user manuals and help documents. Provide user support and training.

[0126] Maintenance and support: Maintain the deployed client programs and solve the problems encountered by users during use.

[0127] Feedback collection and analysis: Collect user feedback. Analyze user behavior and system performance to guide future iterations.

[0128] Version management: Manage different version releases. Ensure backward compatibility and smooth transition between versions.

[0129] This application forms a set of agile iterations and provides a one-click deployment and management platform for large-scale digital objects under the data networking or data interconnection system to simplify the cumbersome and complicated development process of iterative development under the current data networking system. At the same time, this scaffolding not only covers the client of the data networking but also includes the server (middleware) that interacts with the data networking infrastructure. This method can solve the following problems faced in the current development of the data networking:

[0130] The cost of data circulation in the Internet of Things system is high and the efficiency is low. Traditional client development and deployment methods often adopt waterfall models or iterative models, which have problems such as long development cycle, lack of user participation and feedback, lack of testing and verification, and complex deployment process. This application adopts the concept and method of agile development, which can realize the rapid, efficient and flexible development and deployment of the client to meet different application scenarios and user needs. The risk of data security and compliance is high. Data circulation involves multiple subjects and links. How to ensure the security, privacy, legality, credibility, etc. of data is an important challenge facing the field of Internet of Things. If a modular, componentized and reusable approach is adopted, the functions and interfaces of the client can be quickly realized by relying on the components of the Internet of Things infrastructure, which can improve the development efficiency and quality of the client and reduce the development cost and risk. At the same time, if digital object identifiers (DOI) and digital object metadata (DOM) are used as interfaces of components of the Internet of Things infrastructure, communication and interaction between the client and the components of the Internet of Things infrastructure can be realized, and the scalability and compatibility of the client can be improved. And there are problems such as insufficient mining and release of the value of data entities. How to use digital objects to drive technological innovation and business innovation is the core goal of the development of the Internet of Things. If user participation and feedback are adopted, the client based on the Internet of Things can achieve consistency with user expectations, improving the client's user satisfaction and user experience. At the same time, the use of data analysis, mining, visualization and other technologies can realize data value discovery, value enhancement, value exchange, value sharing, etc., and realize data security, compliance integration and value enhancement.

[0131] In summary, in an embodiment of the present application, client configuration parameters are obtained; the client configuration parameters include: functional parameters and interface parameters corresponding to the client; the corresponding digital networking architecture component is determined according to the functional parameters, and the service interface corresponding to the digital networking architecture component is connected to the middleware; the digital networking architecture component is used to provide digital networking services, and the middleware is used to realize communication between the client and the digital networking architecture component; a functional component for each function is generated according to the functional parameters and the digital networking architecture component, and a user interface of the client is generated according to the interface parameters; the functional components, the user interface and the target program corresponding to the middleware are packaged into an executable file for deploying the digital networking client. When generating a client program, the present application first obtains the client configuration parameters, determines the functional requirements of the client, determines the corresponding digital networking architecture components based on the functional requirements of the client, and connects the service interface that realizes the communication between the client and the digital networking architecture components to the middleware. At the same time, each function of the client is separately encapsulated as a functional component, so that after the executable file is formed to deploy the digital networking client, the functional components of the client can communicate with the digital networking architecture components through the middleware to realize the digital networking services of the client. In addition, since the present application has separately encapsulated the functions, when the functions are iterated, only the functional components need to be iteratively updated, which simplifies the cumbersome process of developing digital networking clients in related technologies, and can conveniently realize the deployment of digital networking clients through executable files, thereby improving deployment efficiency.

[0132] refer to Figure 6 , which shows a desktop client agile development and deployment device 20 based on a data networking architecture provided by an embodiment of the present application, including:

[0133] The acquisition module 201 is used to acquire client configuration parameters; the client configuration parameters include: function parameters and interface parameters corresponding to the client;

[0134] A matching module 202 is used to determine a corresponding data networking architecture component according to the functional parameters, and connect a service interface corresponding to the data networking architecture component to a middleware; the data networking architecture component is used to provide data networking services, and the middleware is used to implement communication between the client and the data networking architecture component;

[0135] The encapsulation module 203 is used to generate a functional component for each function according to the functional parameters and the data networking architecture component, and to generate a user interface of the client according to the interface parameters;

[0136] The packaging module 204 is used to package the functional components, the user interface and the target program corresponding to the middleware into an executable file for deploying a data networking client.

[0137] Optionally, the encapsulation module includes:

[0138] Separately encapsulate submodules to encapsulate the functional components of each function separately to form a functional component library;

[0139] The interface generation submodule is used to generate a user interface of the client according to the interface parameters and preset template data.

[0140] Optionally, the packaging module includes:

[0141] The image generation submodule is used to package the dependency library, function library, environment parameters, and configuration information corresponding to the target program into a container image through the container engine;

[0142] The image deployment submodule is used to deploy the container image of the client to the cloud through the kubernetes tool.

[0143] Optionally, after generating a functional component for each function according to the functional parameters and the data networking architecture component, and generating a user interface of the client according to the interface parameters, the desktop client agile development and deployment device 20 based on the data networking architecture further includes:

[0144] A first testing module, used to test the functional component and the user interface through a preset first testing command;

[0145] The second test module is used to test the interactive operation of the user interface and the communication between the functional component and the data network architecture component through a preset second test command to obtain a test result.

[0146] Optionally, the matching module includes:

[0147] A function determination submodule, used to determine the target function that the middleware needs to provide according to the function parameters and the data network architecture components;

[0148] The interface implementation submodule is used to implement the service interface corresponding to the data network architecture component in the middleware according to the target function.

[0149] Optionally, after the functional components of each function are individually packaged to form a functional component library, the desktop client agile development and deployment device 20 based on the data network architecture further includes:

[0150] An update module, used for iteratively updating any functional component;

[0151] The repackaging module is used to repack the target programs corresponding to the iteratively updated functional components, middleware and user interface into an executable file.

[0152] Optionally, the desktop client agile development and deployment device 20 based on the data network architecture further includes:

[0153] A script generation module, used to generate different script files for deploying the executable file according to different deployment environments;

[0154] The client deployment module is used to run the script file and deploy the executable file on the client.

[0155] In summary, in an embodiment of the present application, client configuration parameters are obtained; the client configuration parameters include: functional parameters and interface parameters corresponding to the client; the corresponding digital networking architecture component is determined according to the functional parameters, and the service interface corresponding to the digital networking architecture component is connected to the middleware; the digital networking architecture component is used to provide digital networking services, and the middleware is used to realize communication between the client and the digital networking architecture component; a functional component for each function is generated according to the functional parameters and the digital networking architecture component, and a user interface of the client is generated according to the interface parameters; the functional components, the user interface and the target program corresponding to the middleware are packaged into an executable file for deploying the digital networking client. When generating a client program, the present application first obtains the client configuration parameters, determines the functional requirements of the client, determines the corresponding digital networking architecture components based on the functional requirements of the client, and connects the service interface that realizes the communication between the client and the digital networking architecture components to the middleware. At the same time, each function of the client is separately encapsulated as a functional component, so that after the executable file is formed to deploy the digital networking client, the functional components of the client can communicate with the digital networking architecture components through the middleware to realize the digital networking services of the client. In addition, since the present application has separately encapsulated the functions, when the functions are iterated, only the functional components need to be iteratively updated, which simplifies the cumbersome process of developing digital networking clients in related technologies, and can conveniently realize the deployment of digital networking clients through executable files, thereby improving deployment efficiency.

[0156] Figure 7 is a block diagram of an electronic device 600 according to an exemplary embodiment. For example, the electronic device 600 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0157] Reference Figure 7 , the electronic device 600 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input / output (I / O) interface 612 , a sensor component 614 , and a communication component 616 .

[0158] The processing component 602 generally controls the overall operation of the electronic device 600, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 602 may include one or more modules to facilitate the interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate the interaction between the multimedia component 608 and the processing component 602.

[0159] The memory 604 is used to store various types of data to support the operation of the electronic device 600. Examples of such data include instructions for any application or method operating on the electronic device 600, contact data, phone book data, messages, pictures, multimedia, etc. The memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0160] The power supply component 606 provides power to the various components of the electronic device 600. The power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 600.

[0161] The multimedia component 608 includes a screen that provides an output interface between the electronic device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front camera and / or a rear camera. When the electronic device 600 is in an operating mode, such as a shooting mode or a multimedia mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0162] The audio component 610 is used to output and / or input audio signals. For example, the audio component 610 includes a microphone (MIC), and when the electronic device 600 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is used to receive an external audio signal. The received audio signal can be further stored in the memory 604 or sent via the communication component 616. In some embodiments, the audio component 610 also includes a speaker for outputting audio signals.

[0163] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0164] The sensor assembly 614 includes one or more sensors for providing various aspects of status assessment for the electronic device 600. For example, the sensor assembly 614 can detect the open / closed state of the electronic device 600, the relative positioning of the components, such as the display and keypad of the electronic device 600, and the sensor assembly 614 can also detect the position change of the electronic device 600 or a component of the electronic device 600, the presence or absence of contact between the user and the electronic device 600, the orientation or acceleration / deceleration of the electronic device 600, and the temperature change of the electronic device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0165] The communication component 616 is used to facilitate wired or wireless communication between the electronic device 600 and other devices. The electronic device 600 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0166] In an exemplary embodiment, the electronic device 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to implement the above-mentioned methods provided in the embodiments of the present application.

[0167] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions, and the instructions can be executed by a processor 620 of an electronic device 600 to perform the above method. For example, the non-transitory storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0168] Figure 8 is a block diagram of an electronic device 700 according to an exemplary embodiment. For example, the electronic device 700 may be provided as a server. Figure 8 The electronic device 700 includes a processing component 722, which further includes one or more processors, and a memory resource represented by a memory 732 for storing instructions that can be executed by the processing component 722, such as an application. The application stored in the memory 732 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 722 is configured to execute instructions to perform the above method provided in the embodiment of the present application.

[0169] The electronic device 700 may also include a power supply component 726 configured to perform power management of the electronic device 700, a wired or wireless network interface 750 configured to connect the electronic device 700 to a network, and an input / output (I / O) interface 758. The electronic device 700 may operate based on an operating system stored in the memory 732, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

[0170] An embodiment of the present application also provides a computer program product, including a computer program, which implements the method when executed by a processor.

[0171] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0172] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A desktop client agile development and deployment method based on a data networking architecture, characterized in that: The method comprises: Obtain client configuration parameters; the client configuration parameters include: functional parameters and interface parameters corresponding to the client; Determine the corresponding data networking architecture component according to the functional parameters, and connect the service interface corresponding to the data networking architecture component to the middleware; the data networking architecture component is used to provide data networking services, and the middleware is used to realize the communication between the client and the data networking architecture component; the middleware is implemented by the system programming language rust; Generate a functional component for each function according to the functional parameters and the data network architecture components, and generate a user interface of the client according to the interface parameters; the user interface is developed using a front-end view framework; the interactive operation of the user interface is achieved by compiling rust into a network assembly module; Packaging the functional components, the user interface and the target program corresponding to the middleware into an executable file for deploying a data networking client; After generating a functional component for each function according to the functional parameters and the data networking architecture component, and generating a user interface of the client according to the interface parameters, the method further includes: Testing the functional component and the user interface by using a preset first test command; Testing the interactive operation of the user interface and the communication between the functional component and the data networking architecture component through a preset second test command to obtain a test result; The first test command and the second test command are constructed by a preset test template.

2. The method for agile development and deployment of desktop clients based on a data networking architecture according to claim 1 is characterized in that: The generating a functional component for each function according to the functional parameter and the data networking architecture component comprises: Encapsulate the functional components of each function separately to form a functional component library; Generating a user interface of the client according to the interface parameters includes: A user interface of the client is generated according to the interface parameters and preset template data.

3. The method for agile development and deployment of desktop clients based on a data networking architecture according to claim 1 is characterized in that: The step of packaging the functional components, the user interface and the target program corresponding to the middleware into an executable file for deploying a data networking client includes: The dependent libraries, function libraries, environment parameters, and configuration information corresponding to the target program are packaged into a container image through a container engine; The container image of the client is deployed to the cloud through the kubernetes tool.

4. The method for agile development and deployment of desktop clients based on a data networking architecture according to claim 1 is characterized in that: The step of connecting the service interface corresponding to the data networking architecture component to the middleware includes: Determine the target function that the middleware needs to provide according to the functional parameters and the data network architecture components; According to the target function, the service interface corresponding to the data network architecture component is implemented in the middleware.

5. The method for agile development and deployment of desktop clients based on a data networking architecture according to claim 2 is characterized in that: After the functional components of each function are individually encapsulated to form a functional component library, the method further includes: For any functional component, iteratively update the functional component; The target programs corresponding to the iteratively updated functional components, middleware and user interface are repackaged into executable files.

6. The method for agile development and deployment of desktop clients based on a data networking architecture according to claim 1 is characterized in that: The method further comprises: Generate different script files for deploying the executable files according to different deployment environments; Run the script file and deploy the executable file on the client.

7. A desktop client agile development and deployment device based on a digital networking architecture, characterized in that: include: The acquisition module is used to obtain client configuration parameters; The client configuration parameters include: functional parameters and interface parameters corresponding to the client; A matching module, used for determining a corresponding data networking architecture component according to the functional parameters, and connecting a service interface corresponding to the data networking architecture component to a middleware; the data networking architecture component is used for providing data networking services, and the middleware is used for realizing communication between the client and the data networking architecture component; the middleware is implemented in a system programming language rust; An encapsulation module is used to generate a functional component for each function according to the functional parameters and the data network architecture component, and to generate a user interface of the client according to the interface parameters; the user interface is developed using a front-end view framework; the interactive operation of the user interface is achieved by compiling rust into a network assembly module; A packaging module, used to package the functional components, the user interface and the target program corresponding to the middleware into an executable file for deploying a data networking client; The device also includes: A first testing module, used for testing the functional component and the user interface through a preset first testing command; The second test module is used to test the interactive operation of the user interface and the communication between the functional component and the data network architecture component through a preset second test command to obtain a test result; wherein the first test command and the second test command are constructed through a preset test template.

8. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the agile development and deployment method of desktop client based on the Internet of Things architecture as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the agile development and deployment method for desktop clients based on a data networking architecture as described in any one of claims 1 to 6.

Images