A modular rapid deployment method for urban and rural zero-carbon reading space

Abstract

This invention relates to the fields of smart city construction, public cultural services, digital reading, energy conservation in public institutions, and zero-carbon libraries, and particularly to a modular rapid deployment method for urban and rural zero-carbon reading spaces. The method receives the available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements of the target site, and generates deployment task data; it calls a standardized module library and configuration template library to match hardware modules, software modules, and service modules, generating a module combination scheme; based on the module combination scheme, it generates a deployment data package including basic positioning, power supply wiring connection, network equipment debugging, terminal equipment installation, software system activation, content resource injection, and system integration testing; it collects deployment execution data and system integration testing results, generates deployment acceptance data, and inputs it into a remote operation and maintenance platform to generate template update data. This invention effectively improves the consistency of deployment, acceptance, and operation and maintenance updates of urban and rural zero-carbon reading spaces.

Description

Technical Field

[0001] This invention relates to the fields of smart city construction, public cultural services, digital reading, energy conservation in public institutions, and zero-carbon libraries, and particularly to a modular and rapid deployment method for urban and rural zero-carbon reading spaces. Background Technology

[0002] In the fields of smart city construction, public cultural services, digital reading, energy conservation in public institutions, and zero-carbon libraries, existing solutions for urban and rural zero-carbon reading spaces typically involve manual site surveys. Hardware, software, and service modules are selected based on available area, power supply, network conditions, budget constraints, service scope, and operational requirements. Basic positioning, power cabling, network equipment debugging, terminal equipment installation, software system activation, and content resource access are completed on-site. This approach suffers from limitations such as scattered deployment task data, reliance on manual experience for module combination schemes, and a lack of unified data integration between deployment execution data and system integration testing results. Existing methods often handle hardware installation, software configuration, service activation, and remote maintenance separately, leading to issues such as deployment data packages not covering injected content resource data and insufficient correlation between system integration testing data and acceptance criteria.

[0003] In scenarios where there are significant differences in available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements in urban and rural public spaces, existing solutions are prone to issues such as mismatches between hardware configuration lists and installation locations, mismatches between software version requirements and network bandwidth needs, and inconsistencies between content service standards and digital reading platforms. These issues make it difficult to meet the stable implementation requirements for the modular and rapid deployment of zero-carbon reading spaces in urban and rural areas.

[0004] For the joint processing of deployment data packets, deployment execution data, system integration test results, deployment acceptance data, and template update data, existing technologies generally suffer from the shortcoming of fragmented collection, comparison, recording, and updating processes. This makes it difficult to establish a consistent process in urban and rural zero-carbon reading spaces, encompassing deployment data packet generation, deployment execution data collection, system integration test result comparison, deployment acceptance data generation, and template update data write-back. Consequently, the equipment status, energy consumption data, network status, service usage, fault conditions, maintenance instructions, and confirmation results collected by the remote operation and maintenance platform cannot be continuously applied to the standardized module library and configuration template library. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides a modular and rapid deployment method for urban and rural zero-carbon reading spaces, comprising:

[0006] S100 receives the available area, power supply conditions, network conditions, budget constraints, service scope and operation and maintenance requirements of the target site, performs field standardization and installation location organization, and generates deployment task data;

[0007] S200: Based on the deployment task data, call the standardized module library and configuration template library, perform field verification and constraint verification, match hardware modules, software modules and service modules, and generate a module combination scheme;

[0008] S300. Based on the module combination scheme, perform software system activation and joint debugging planning, and generate deployment data packets; the deployment data packets include basic positioning data, power supply cabling connection data, network equipment debugging data, terminal equipment installation data, software system activation data, content resource injection data, and system joint debugging test data;

[0009] S400. Based on the deployment data package, execute the data and system integration test results to generate deployment acceptance data, and input the deployment acceptance data into the remote operation and maintenance platform to generate template update data.

[0010] Furthermore, the deployment task data includes field fields for site identification, available area, power supply capacity, network bandwidth, budget limit, service range, installation location, number of modules, software version, content service, and operation and maintenance requirements.

[0011] Furthermore, the standardized module library includes a hardware module library, a software module library, and a service module library. The hardware module library records the physical specifications, power supply specifications, and network interfaces of digital reading terminals, display devices, network devices, and sensing devices. The software module library records the API interfaces, data exchange formats, and software version requirements of the digital reading platform, carbon emission accounting module, and operation and maintenance management module. The service module library records the process specifications and service quality indicators of green reading service standards, operation and maintenance service standards, and content service standards.

[0012] Furthermore, the configuration template library includes configuration templates for urban center venues, community service stations, rural cultural sites, and public institution reading corners. Each configuration template includes applicable area range, power supply condition range, network condition range, budget constraint range, hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration and testing rules.

[0013] Furthermore, the generation of the module combination scheme includes: matching the deployment task data with the configuration template library to generate candidate configuration templates; performing field verification between the candidate configuration templates and the standardized module library to generate a hardware configuration list, software version requirements, network bandwidth requirements, and estimated total carbon footprint.

[0014] Furthermore, the deployment data package also includes device identifier, network interface, data exchange format, installation order, test order, and acceptance rules. The test order includes network connectivity test, software system activation test, content resource injection test, and system integration test.

[0015] Furthermore, the deployment execution data includes basic positioning completion information, power supply cabling connection completion information, network equipment debugging completion information, terminal equipment installation completion information, software system activation completion information, content resource injection completion information, and system integration test results.

[0016] Furthermore, if the test results of the network connectivity test, software system activation test, content resource injection test, or system integration test are inconsistent with the acceptance rules, configuration adjustment data or maintenance instructions are generated, and the configuration adjustment data or maintenance instructions are associated with and stored with the deployment data packet.

[0017] Furthermore, the remote operation and maintenance platform collects equipment status, energy consumption data, network status, service usage, fault status, maintenance instructions, and confirmation results, and associates the confirmation results with the deployment task data, module combination scheme, and configuration template library to generate the template update data.

[0018] Furthermore, the template update data is used to update the hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, or system integration testing rules in the configuration template library, and to update the applicable conditions of hardware modules, software modules, or service modules in the standardized module library.

[0019] The following are its main beneficial effects:

[0020] (1) To address the problem of the disconnect between hardware installation, software configuration and service activation, a deployment data package is generated by combining modules to form a continuous deployment link, which includes basic positioning data, power supply wiring connection data, network equipment debugging data, terminal equipment installation data, software system activation data, content resource injection data and system joint debugging test data. This facilitates the deployment of urban and rural zero-carbon reading spaces in different target sites according to the same data object.

[0021] (2) To address the lack of unified acceptance of deployment execution data and system integration test results, deployment execution data and system integration test results are used to generate deployment acceptance data. This allows information such as basic positioning completion, power supply wiring connection completion, network equipment debugging completion, terminal equipment installation completion, software system activation completion, and content resource injection completion to be included in the same acceptance record, making it easier for the remote operation and maintenance platform to review the deployment process.

[0022] (3) To address the problem that the results collected by the remote operation and maintenance platform are difficult to continuously apply to the standardized module library and configuration template library, by inputting the deployment acceptance data into the remote operation and maintenance platform and generating template update data, the equipment status, energy consumption data, network status, service usage, fault status, maintenance instructions and confirmation results are written back to the standardized module library and configuration template library.

[0023] (4) To address the inconsistency between content service standards and digital reading platforms, content resource injection data is set in the deployment data package and associated with software system activation data, network device debugging data and system integration test data, so that the content resource injection process is incorporated into the generation chain of deployment acceptance data. Attached Figure Description

[0024] Figure 1 A flowchart illustrating a modular rapid deployment method for urban and rural zero-carbon reading spaces provided in this application embodiment;

[0025] Figure 2 This is a structural block diagram of a modular rapid deployment method for urban and rural zero-carbon reading spaces provided in an embodiment of this application. Detailed Implementation

[0026] Example 1: Refer to Figure 1 This is a flowchart illustrating a modular rapid deployment method for zero-carbon reading spaces in urban and rural areas provided by an embodiment of the present invention. The process may include at least steps S100-S400:

[0027] S100: Receive the available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements of the target site, and generate deployment task data;

[0028] S200: Based on the deployment task data, call the standardized module library and configuration template library, match hardware modules, software modules and service modules, and generate a module combination scheme;

[0029] S300. Generate a deployment data package based on the module combination scheme. The deployment data package includes basic positioning data, power supply cabling connection data, network equipment debugging data, terminal equipment installation data, software system activation data, content resource injection data, and system integration test data.

[0030] S400. Based on the deployment data package, collect deployment execution data and system integration test results, generate deployment acceptance data, and input the deployment acceptance data into the remote operation and maintenance platform to generate template update data.

[0031] S100: Receive the available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements of the target site, and generate deployment task data;

[0032] Specifically, S100 receives information from the remote operation and maintenance platform regarding the available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements of the target site. The target site refers to locations in urban and rural public spaces where zero-carbon reading spaces are planned, including city center libraries, community service stations, rural cultural centers, and reading corners in public institutions. The available area refers to the space within the target site for arranging digital reading terminals, display devices, network equipment, sensing devices, and personnel activities. The power supply conditions refer to the existing high-voltage and low-voltage power supply, power capacity, and power interface status of the target site. The network conditions refer to the existing network interfaces, network bandwidth, network device access locations, and data exchange channel status of the target site. The budget constraint is the upper limit of the budget for the deployment task corresponding to the target site. The service scope refers to the target audience, reading service area, and content service categories of the target site. The operation and maintenance requirements are the requirements for the remote operation and maintenance platform to collect equipment status, energy consumption data, network status, service usage, fault conditions, maintenance instructions, and confirmation results.

[0033] Specifically, when the remote operation and maintenance platform receives target site data, it first reads the site identifier, then writes the available area into the available area field, the power supply conditions into the power supply capacity field, the network conditions into the network bandwidth field, the budget constraints into the budget limit field, the service scope into the service scope field, and the operation and maintenance requirements into the operation and maintenance requirements field. The site identifier is used to distinguish different target sites. The available area field is used for matching the quantity of subsequent hardware configuration lists. The power supply capacity field is used for verifying the power supply specifications of subsequent digital reading terminals, display devices, network devices, and sensing devices. The network bandwidth field is used for verifying the network bandwidth requirements of subsequent digital reading platform, carbon emission accounting module, and operation and maintenance management module. The budget limit field is used for filtering subsequent module combination schemes. The service scope field is used for matching subsequent content service standards and green reading service standards. The operation and maintenance requirements field is used by the remote operation and maintenance platform to collect equipment status, energy consumption data, network status, service usage, and fault conditions.

[0034] Specifically, the remote operation and maintenance platform performs field standardization after the fields are written. Field standardization includes unifying field names, unifying field formats, recording field source information, and marking missing fields. Unifying field names means converting area, power supply, network, budget, service, and operation and maintenance information submitted by different target sites into the same field name. Unifying field formats means writing the available area, power supply capacity, network bandwidth, and budget limit fields into a unified format, and writing the service scope and operation and maintenance requirements fields into a unified text format. Recording field source information means recording that each field comes from site measurements, on-site reporting, network equipment readback, or existing records on the remote operation and maintenance platform. Marking missing fields means that when a target site does not submit a certain field, the remote operation and maintenance platform retains the field position and writes a missing status, without deleting the field.

[0035] Specifically, the remote operation and maintenance platform performs installation location organization after field standardization. The installation location refers to the placement of digital reading terminals, display devices, network devices, and sensing devices within the target site. The remote operation and maintenance platform writes the available device locations within the target site into the installation location field and associates this field with the available area, power supply capacity, and network bandwidth fields. If the installation location lacks a power supply interface, the remote operation and maintenance platform writes a power cabling connection marker into the installation location field. If the installation location lacks a network interface, the remote operation and maintenance platform writes a network device debugging marker into the installation location field. If the installation location conflicts with a personnel activity area, the remote operation and maintenance platform sets the installation location to a pending review status and records the corresponding site identifier.

[0036] Furthermore, the remote operation and maintenance platform generates module quantity, software version, and content service fields based on the service scope field. The module quantity field represents the quantity boundaries of digital reading terminals, display devices, network devices, and sensing devices. The software version field specifies the version requirements for the digital reading platform, carbon emission accounting module, and operation and maintenance management module. The content service field represents the content resource category and service scope corresponding to the content service standard. The remote operation and maintenance platform associates the module quantity field with the available area field, the software version field with the network bandwidth field, and the content service field with the service scope field. These association results are incorporated into the deployment task data and used as input for the S200 to call the standardized module library and configuration template library.

[0037] In this engineering implementation, the target site is a rural cultural center. Maintenance personnel input available area, power supply conditions, network conditions, budget constraints, service scope, and maintenance requirements into the remote operation and maintenance platform. After reading the site identifier, the remote operation and maintenance platform writes the available area into the available area field, the existing power supply interface and capacity into the power supply capacity field, the network access method and bandwidth into the network bandwidth field, the maximum deployment cost into the budget limit field, the reading population and content needs covered by the rural cultural center into the service scope field, and the requirements for remote monitoring, fault diagnosis, and maintenance instruction feedback into the operation and maintenance requirements field. The remote operation and maintenance platform then organizes the installation locations of digital reading terminals, display devices, network devices, and sensing devices, forming an installation location field, and generates module quantity, software version, and content service fields based on the service scope. The resulting deployment task data enters S200 for use by the standardized module library and configuration template library within S200.

[0038] The core fields of the deployment task data include site identifier, available area, power supply capacity, network bandwidth, budget limit, service area, installation location, number of modules, software version, content service, and maintenance requirements. This deployment task data is encapsulated by the remote maintenance platform and written into the deployment task record. The available area, power supply capacity, network bandwidth, budget limit, and service area fields in the deployment task data are entered into the S200 configuration template library matching process. The installation location, number of modules, software version, content service, and maintenance requirements fields in the deployment task data are entered into the S200 standardized module library calling process.

[0039] In summary, the technical effects of this step are as follows: S100 converts the dispersed information of the target site into deployment task data, forming a unified input for hardware modules, software modules, and service modules. S100 writes available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements into corresponding fields, providing direct input for S200 when calling the standardized module library and configuration template library. S100 incorporates the installation location field, module quantity field, software version field, and content service field into the deployment task data, forming a continuous data chain for subsequent module combination schemes.

[0040] S200: Based on the deployment task data, call the standardized module library and configuration template library, match hardware modules, software modules and service modules, and generate a module combination scheme;

[0041] Specifically, S200 receives deployment task data output by S100. The remote operation and maintenance platform calls the standardized module library and configuration template library based on the deployment task data. The standardized module library includes a hardware module library, a software module library, and a service module library. The hardware module library records the physical specifications, power supply specifications, and network interfaces of digital reading terminals, display devices, network devices, and sensing devices. The software module library records the application programming interfaces (APIs), data exchange formats, and software version requirements of the digital reading platform, carbon emission accounting module, and operation and maintenance management module. The service module library records the process specifications and service quality indicators of green reading service standards, operation and maintenance service standards, and content service standards. The configuration template library includes configuration templates for urban center libraries, community service stations, rural cultural points, and public institution reading corners. Each configuration template records the applicable area range, power supply conditions range, network conditions range, budget constraints range, hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration testing rules.

[0042] Specifically, the remote operation and maintenance platform first matches the service scope field in the deployment task data with the configuration templates for urban center venues, community service stations, rural cultural points, and public institution reading corners in the configuration template library to generate candidate configuration templates. The matching process first compares the service scope field, then the available area field, power supply capacity field, network bandwidth field, and budget limit field. If the service scope field of the target site corresponds to a rural cultural point, the remote operation and maintenance platform prioritizes retrieving the rural cultural point configuration template. If the available area field does not fall within the applicable area range of the rural cultural point configuration template, the remote operation and maintenance platform writes the configuration template to a pending review status and continues to call the community service station configuration template for field comparison. If the power supply capacity field or network bandwidth field is lower than the power supply condition range or network condition range in the configuration template, the remote operation and maintenance platform writes the gap into the candidate configuration template record and generates power cabling connection data or network equipment debugging data in subsequent deployment data packets.

[0043] Furthermore, the remote operation and maintenance platform performs field verification on the candidate configuration templates against the standardized module library. Field verification includes hardware field verification, software field verification, and service field verification. Hardware field verification reads the hardware configuration list from the candidate configuration template and compares it with the physical specifications, power supply specifications, and network interfaces of the digital reading terminal, display device, network device, and sensor device in the hardware module library. Software field verification reads the software version requirements and network bandwidth requirements from the candidate configuration template and compares them with the API interfaces, data exchange formats, and software version requirements of the digital reading platform, carbon emission accounting module, and operation and maintenance management module in the software module library. Service field verification reads the content service standards, green reading service standards, and operation and maintenance service standards from the candidate configuration template and compares them with the process specifications and service quality indicators in the service module library. Candidate configuration templates that pass the field verification proceed to the module combination scheme generation process. Fields that fail the field verification are written into configuration adjustment data, which is temporarily stored on the remote operation and maintenance platform and used by the S300 when generating deployment data packages.

[0044] Specifically, when generating a module combination scheme, the remote operation and maintenance platform first selects digital reading terminals, display devices, network devices, and sensing devices from the hardware module library and writes them into a hardware configuration list. The hardware configuration list records the device name, device identifier, physical specifications, power supply specifications, network interface, and installation location. The remote operation and maintenance platform then selects a digital reading platform, a carbon emission accounting module, and an operation and maintenance management module from the software module library and writes them into the software version requirements. The software version requirements record the software name, software version, API interface, data exchange format, and network bandwidth requirements. The remote operation and maintenance platform then selects green reading service standards, operation and maintenance service standards, and content service standards from the service module library and writes them into the service configuration results. The service configuration results record process specifications, service quality indicators, and content service fields.

[0045] Furthermore, the remote operation and maintenance platform performs constraint verification on the module combination scheme based on the power supply capacity field, network bandwidth field, budget limit field, and estimated total carbon footprint. The estimated total carbon footprint is a low-carbon operation association field for hardware modules, software modules, and service modules in the configuration template library. The remote operation and maintenance platform compares the power supply specifications in the hardware configuration list with the power supply capacity field, compares the network bandwidth requirements in the software version requirements with the network bandwidth field, and compares the hardware configuration list, software version requirements, and service configuration results with the budget limit field, then writes the estimated total carbon footprint into the module combination scheme. If the power supply capacity field is insufficient, the remote operation and maintenance platform marks the power cabling connection requirement in the module combination scheme. If the network bandwidth field is insufficient, the remote operation and maintenance platform marks the network device debugging requirement in the module combination scheme. If the budget limit field does not meet the candidate configuration template, the remote operation and maintenance platform adjusts the module quantity field in the hardware configuration list and re-executes the field verification.

[0046] In the engineering implementation, after receiving the deployment task data for rural cultural sites, the remote operation and maintenance platform first matches the service scope field to the rural cultural site configuration template. The rural cultural site configuration template records the applicable area range, power supply condition range, network condition range, budget constraint range, hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration testing rules. After reading the hardware module library, the remote operation and maintenance platform selects digital reading terminals, display devices, network devices, and sensing devices, and writes their physical specifications, power supply specifications, network interfaces, and installation locations into the hardware configuration list. After reading the software module library, the remote operation and maintenance platform selects the digital reading platform, carbon emission accounting module, and operation and maintenance management module, and writes the software version requirements, API interfaces, and data exchange formats. After reading the service module library, the remote operation and maintenance platform selects the green reading service standard, operation and maintenance service standard, and content service standard, and writes the service configuration results. After completing the verification of power supply, network, budget, and estimated total carbon footprint, the remote operation and maintenance platform generates a module combination scheme and inputs the module combination scheme into S300.

[0047] The core fields of the module combination scheme include candidate configuration templates, hardware configuration lists, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, system integration testing rules, and estimated total carbon footprint. The candidate configuration templates are from a configuration template library. The hardware configuration lists are from a hardware module library. The software version requirements and network bandwidth requirements are from a software module library. The content service standards and operation and maintenance service standards are from a service module library. The system integration testing rules are from a configuration template library. This module combination scheme, after being encapsulated by the remote operation and maintenance platform, serves as direct input for generating deployment data packets for the S300.

[0048] In summary, the technical effects of this step are as follows: Step S200 associates deployment task data with a standardized module library and a configuration template library, forming an integrated module combination scheme comprising hardware modules, software modules, and service modules. Step S200, through candidate configuration templates and field validation, fixes the correspondence between hardware configuration lists, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration testing rules. Step S200 incorporates the estimated total carbon footprint into the module combination scheme, ensuring that Step S300 simultaneously carries low-carbon operation-related fields when generating deployment data packets.

[0049] S300. Generate a deployment data package based on the module combination scheme. The deployment data package includes basic positioning data, power supply cabling connection data, network equipment debugging data, terminal equipment installation data, software system activation data, content resource injection data, and system integration test data.

[0050] Specifically, S300 receives the module combination scheme output by S200. The remote operation and maintenance platform generates a deployment data package based on the module combination scheme. The deployment data package is a data set jointly invoked by on-site deployment and remote recording, including basic positioning data, power supply cabling connection data, network equipment debugging data, terminal equipment installation data, software system activation data, content resource injection data, and system integration test data. The basic positioning data records the site identifier, installation location field, hardware configuration list, and installation order of the target site. The power supply cabling connection data records the power supply specifications, power supply interfaces, and power supply cabling connection requirements corresponding to the digital reading terminal, display device, network device, and sensor device. The network equipment debugging data records the network interface, network bandwidth requirements, and data exchange format of the network device. The terminal equipment installation data records the device identifier, physical specifications, installation location, and connection status of the digital reading terminal, display device, and sensor device. The software system activation data records the software version requirements, API interfaces, and activation status of the digital reading platform, carbon emission accounting module, and operation and maintenance management module. The content resource injection data records the content service standard, content service field, data exchange format, and content resource injection status. The system integration test data records network connectivity test, software system activation test, content resource injection test, system integration test, test order, and acceptance rules.

[0051] Specifically, the remote operation and maintenance platform first reads the hardware configuration list from the module combination scheme and generates basic positioning data based on the installation location field. The basic positioning data first records the installation locations of the digital reading terminal, display device, network device, and sensor device, then records the device identifier and installation order. If a power supply cabling connection marker exists in the installation location field, the remote operation and maintenance platform writes that installation location into the power supply cabling connection data. If a network device debugging marker exists in the installation location field, the remote operation and maintenance platform writes that installation location into the network device debugging data. After the basic positioning data is generated, the remote operation and maintenance platform associates it with the hardware configuration list to form the first segment of execution data for on-site deployment.

[0052] Furthermore, the remote operation and maintenance platform generates power supply cabling connection data based on the hardware configuration list and power supply capacity field. The power supply cabling connection data reads the power supply specifications of each digital reading terminal, display device, network device, and sensor device, and matches these specifications with the power supply capacity field. After matching, the remote operation and maintenance platform records the power supply interface, power supply connection sequence, and power supply cabling connection status for each hardware module. If the power supply specifications of a hardware module are inconsistent with the power supply capacity field, the remote operation and maintenance platform writes that hardware module into the configuration adjustment data and stores the configuration adjustment data in association with the deployment data package. The configuration adjustment data enters S400 for use by S400 when collecting deployment execution data and system integration test results.

[0053] Furthermore, the remote operation and maintenance platform generates network device debugging data and software system activation data based on software version requirements, network bandwidth requirements, and network interfaces. The network device debugging data reads the network interface and network bandwidth requirements of the network device and records the test order of network connectivity tests. The software system activation data reads the software version requirements, API interfaces, and data exchange formats of the digital reading platform, carbon emission accounting module, and operation and maintenance management module, and records the test order of software system activation tests. The first API mentioned is the Application Programming Interface (API). The remote operation and maintenance platform associates the network device debugging data with the software system activation data, ensuring that the software system activation test proceeds only after the network connectivity test is completed. If the network connectivity test fails to produce a connectivity state, the remote operation and maintenance platform writes the software system activation data to a waiting state and generates maintenance instructions.

[0054] Furthermore, the remote operation and maintenance platform generates content resource injection data based on content service standards and content service fields. This content resource injection data is used to write the content resources corresponding to the content service standards into the digital reading platform and associate them with the digital reading terminal and display device. In specific implementation, the remote operation and maintenance platform reads the content service fields, extracts the content resource category, service scope, and content service standards, and then reads the API interface and data exchange format of the digital reading platform to associate the content resources with the digital reading platform, digital reading terminal, and display device. After the content resource injection data is generated, the remote operation and maintenance platform writes the test order for content resource injection testing. If the content service fields are inconsistent with the data exchange format of the digital reading platform, the remote operation and maintenance platform generates configuration adjustment data and writes it to the exception record section of the deployment data package.

[0055] Furthermore, the remote operation and maintenance platform generates system integration testing data according to the system integration testing rules. This system integration testing data includes network connectivity testing, software system activation testing, content resource injection testing, and system integration testing. Network connectivity testing reads network interface and bandwidth requirements from network device debugging data and generates network connectivity information. Software system activation testing reads software version requirements, API interfaces, and activation status from software system activation data and generates software system activation information. Content resource injection testing reads content service standards and content resource injection status from content resource injection data and generates content resource injection information. System integration testing reads network connectivity information, software system activation information, content resource injection information, and the device status corresponding to the hardware configuration list, and generates system integration testing results. The system integration testing data is also written into acceptance rules, which are entered into the S400 system for use when generating deployment acceptance data.

[0056] In the engineering implementation, after the modular combination scheme of the rural cultural point enters the S300, the remote operation and maintenance platform first generates basic positioning data, then places digital reading terminals in the reading area, display devices in public display locations, network devices near network interfaces, and sensor devices at locations for collecting device status and energy consumption data. The remote operation and maintenance platform then generates power supply cabling connection data, recording the power supply specifications and interfaces of each hardware module. Next, the platform generates network device debugging data, recording network interfaces, network bandwidth requirements, and the network connectivity test sequence. Then, it generates software system activation data, recording the software version requirements, API interfaces, and data exchange formats of the digital reading platform, carbon emission accounting module, and operation and maintenance management module. Following this, the platform generates content resource injection data, associating the content resources corresponding to the content service standards with the digital reading platform, digital reading terminals, and display devices. Finally, the platform generates system integration test data, writing the network connectivity test, software system activation test, content resource injection test, and system integration test into the test sequence.

[0057] The core fields of the deployment data packet include basic location data, power supply cabling connection data, network equipment debugging data, terminal equipment installation data, software system activation data, content resource injection data, and system integration test data. The extended fields of the deployment data packet include device identifier, network interface, data exchange format, installation order, test order, acceptance rules, configuration adjustment data, and maintenance instructions. The deployment data packet is encapsulated by the remote operation and maintenance platform and input into the S400. The S400 collects deployment execution data and system integration test results based on the deployment data packet and generates deployment acceptance data according to the acceptance rules.

[0058] In summary, the technical effects of this step are as follows: S300 converts the module combination scheme into a deployment data package and writes basic positioning, power supply cabling connection, network equipment debugging, terminal equipment installation, software system activation, content resource injection, and system integration testing into the same execution chain. S300 incorporates the test sequence and acceptance rules into the deployment data package, ensuring that S400 has corresponding fields when collecting deployment execution data and system integration testing results. S300 associates the content resource injection data with the digital reading platform, digital reading terminal, and display device, forming a reading space deployment data chain that differs from ordinary modular public facility deployments.

[0059] S400. Based on the deployment data package, collect deployment execution data and system integration test results, generate deployment acceptance data, and input the deployment acceptance data into the remote operation and maintenance platform to generate template update data.

[0060] Specifically, S400 receives the deployment data packet output by S300. The remote operation and maintenance platform collects deployment execution data and system integration test results based on the deployment data packet, generates deployment acceptance data, and inputs the deployment acceptance data into the remote operation and maintenance platform to generate template update data. The deployment execution data includes basic positioning completion information, power supply cabling connection completion information, network equipment debugging completion information, terminal equipment installation completion information, software system activation completion information, content resource injection completion information, and system integration test results. The deployment acceptance data is a set of fields formed by comparing the deployment execution data with acceptance rules. The template update data consists of updated fields from the configuration template library and standardized module library generated by the remote operation and maintenance platform based on the deployment acceptance data, equipment status, energy consumption data, network status, service usage, fault conditions, maintenance instructions, and confirmation results.

[0061] Specifically, the remote maintenance platform first collects basic positioning completion information. This information comes from the installation location and device identifier corresponding to the basic positioning data. After maintenance personnel complete the basic positioning of the digital reading terminal, display device, network device, and sensor device, the remote maintenance platform reads the device identifier and installation location status, and writes the reading results into the basic positioning completion information. If the device identifier does not match the basic positioning data, the remote maintenance platform writes the fault condition and generates a maintenance command. If the installation location status matches the basic positioning data, the remote maintenance platform inputs the basic positioning completion information into the power supply cabling connection information collection process.

[0062] Furthermore, the remote operation and maintenance platform collects information on power cabling connection completion and network device debugging completion. The power cabling connection completion information comes from the power interface and power connection status corresponding to the power cabling connection data. The network device debugging completion information comes from the network interface, network bandwidth requirements, and network connectivity information corresponding to the network device debugging data. The remote operation and maintenance platform reads the network connectivity test results and compares them with the acceptance rules. If the network connectivity test results are inconsistent with the acceptance rules, the remote operation and maintenance platform generates configuration adjustment data or maintenance instructions and stores them in association with the deployment data package. If the network connectivity test results are consistent with the acceptance rules, the remote operation and maintenance platform inputs the network device debugging completion information into the software system to activate and complete the information collection process.

[0063] Furthermore, the remote operation and maintenance platform collects information on terminal device installation completion, software system activation completion, and content resource injection completion. Terminal device installation completion information comes from the device status of the digital reading terminal, display device, and sensor device corresponding to the terminal device installation data. Software system activation completion information comes from the software version requirements, API interfaces, and activation status of the digital reading platform, carbon emission accounting module, and operation and maintenance management module corresponding to the software system activation data. Content resource injection completion information comes from the content service standards, content service fields, and content resource injection status corresponding to the content resource injection data. The remote operation and maintenance platform executes software system activation tests and content resource injection tests in the test order. If the software system activation test results are inconsistent with the acceptance rules, the remote operation and maintenance platform generates maintenance instructions and associates the maintenance instructions with the software system activation data. If the content resource injection test results are inconsistent with the acceptance rules, the remote operation and maintenance platform generates configuration adjustment data and associates the configuration adjustment data with the content resource injection data.

[0064] Furthermore, the remote operation and maintenance platform collects system integration test results based on network connectivity information, software system activation information, content resource injection information, and device status. These system integration test results record the status of the digital reading terminal accessing the digital reading platform, the status of the display device displaying content resources, the status of the sensor device collecting device status and energy consumption data, the status of the carbon emission accounting module receiving energy consumption data, and the status of the operation and maintenance management module transmitting fault information and maintenance instructions. The remote operation and maintenance platform compares the system integration test results with the system integration test rules and generates deployment acceptance data. This deployment acceptance data includes deployment task data reference fields, module combination scheme reference fields, deployment data package reference fields, deployment execution data, system integration test results, acceptance rule comparison results, configuration adjustment data, and maintenance instructions.

[0065] Furthermore, after receiving the deployment acceptance data, the remote operation and maintenance platform initiates operational status collection. This collection includes device status, energy consumption data, network status, service usage, fault conditions, maintenance instructions, and confirmation results. Device status data comes from digital reading terminals, display devices, network devices, and sensor devices. Energy consumption data comes from sensor devices and the carbon emission accounting module. Network status data comes from network devices. Service usage data comes from the service records corresponding to the digital reading platform and content service standards. Fault conditions come from the operation and maintenance management module. Maintenance instructions come from the remote operation and maintenance platform. Confirmation results come from records of the completion status of maintenance instructions by maintenance personnel or the remote operation and maintenance platform. The remote operation and maintenance platform associates the confirmation results with deployment task data, module combination schemes, and configuration template libraries to generate template update data.

[0066] Specifically, the template update data is used to update the hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration testing rules in the configuration template library, and to update the applicable conditions of hardware modules, software modules, or service modules in the standardized module library. When network connectivity test results repeatedly contradict the acceptance rules in the deployment acceptance data, the remote operation and maintenance platform writes the network bandwidth requirements for the corresponding target site into the template update data. When content resource injection test results contradict the acceptance rules, the remote operation and maintenance platform writes the corresponding content service standards and data exchange formats into the template update data. When equipment status or energy consumption data malfunctions during operation data collection, the remote operation and maintenance platform writes the applicable conditions for the corresponding hardware module into the template update data. When a maintenance instruction is completed and a confirmation result is generated, the remote operation and maintenance platform writes the confirmation result into the corresponding urban center hall configuration template, community service station configuration template, rural cultural point configuration template, or public institution reading corner configuration template in the configuration template library.

[0067] In this engineering implementation, after the rural cultural site completes the deployment data package execution, the remote operation and maintenance platform first collects basic positioning completion information, reading the device identifiers and installation location status of the digital reading terminal, display device, network device, and sensor device. Subsequently, the remote operation and maintenance platform collects power supply cabling connection completion information and network device debugging completion information, and performs a network connectivity test. After the network connectivity test passes, the remote operation and maintenance platform collects software system activation completion information and performs software system activation tests on the digital reading platform, carbon emission accounting module, and operation and maintenance management module. After the software system activation test passes, the remote operation and maintenance platform performs a content resource injection test, verifying access to the content resources corresponding to the content service standard with the digital reading platform, digital reading terminal, and display device. After completing the above tests, the remote operation and maintenance platform performs a system integration test, reading the access status of the digital reading terminal, the display status of the display device, the data collection status of the sensor device, the receiving status of the carbon emission accounting module, and the feedback status of the operation and maintenance management module, and generates deployment acceptance data. After the deployment and acceptance data is entered into the remote operation and maintenance platform, the platform collects equipment status, energy consumption data, network status, service usage, fault status, maintenance instructions and confirmation results during subsequent operation. It also associates the confirmation results with the rural cultural point configuration template to generate template update data.

[0068] Understandably, the core field set in S400 includes deployment execution data, system integration test results, deployment acceptance data, and template update data. The deployment execution data comes from the completion information corresponding to each execution item in the deployment data package. The system integration test results come from network connectivity tests, software system activation tests, content resource injection tests, and system integration tests. The deployment acceptance data comes from the deployment execution data, system integration test results, and acceptance rule comparison results. The template update data comes from deployment acceptance data, device status, energy consumption data, network status, service usage, fault conditions, maintenance instructions, and confirmation results. The template update data is written back to the standardized module library and configuration template library, and is called as update content for the standardized module library and configuration template library in the next round of S200.

[0069] In summary, the technical effects of this step are as follows: Step S400 converts the execution items in the deployment data package into deployment execution data and system integration test results, and forms deployment acceptance data according to acceptance rules. Step S400 inputs the deployment acceptance data into the remote operation and maintenance platform, and incorporates equipment status, energy consumption data, network status, service usage, fault status, maintenance instructions, and confirmation results into the template update data. Step S400 returns the deployment acceptance data and template update data to the standardized module library and configuration template library, forming a closed-loop operation from S100 to S400.

[0070] Example 2: Figure 2 A structural block diagram of a modular rapid deployment method for urban and rural zero-carbon reading spaces according to an embodiment of the present invention is shown. Figure 2 As shown, the structure may include:

[0071] The deployment task generation module 01 receives the available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements of the target site, and generates deployment task data. Specifically, the deployment task generation module receives the available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements input from the target site, and writes the available area into the available area field, the power supply conditions into the power supply capacity field, the network conditions into the network bandwidth field, the budget constraints into the budget limit field, the service scope into the service scope field, and the operation and maintenance requirements into the operation and maintenance requirements field. The deployment task generation module performs name unification, format unification, source record, and missing tag processing on the above fields, and generates site identifier, installation location field, module quantity field, software version field, and content service field. The deployment task generation module transmits the deployment task data to the module library management module and the configuration template matching module, and the deployment task data serves as the input object for matching hardware modules, software modules, and service modules.

[0072] The module library management module 02, connected to the deployment task generation module, stores hardware modules, software modules, and service modules, and records information on digital reading terminals, display devices, network devices, sensing devices, digital reading platforms, carbon emission accounting modules, operation and maintenance management modules, green reading service standards, operation and maintenance service standards, and content service standards. Specifically, the module library management module receives deployment task data provided by the deployment task generation module and retrieves hardware modules, software modules, and service modules from the standardized module library. The module library management module records the physical specifications, power supply specifications, network interfaces, and installation locations of digital reading terminals, display devices, network devices, and sensing devices in the hardware modules; it records the software version requirements, data exchange formats, and network bandwidth requirements of the digital reading platform, carbon emission accounting module, and operation and maintenance management module in the software modules; and it records the process specifications, service quality indicators, and content service fields of the green reading service standards, operation and maintenance service standards, and content service standards in the service modules. The module library management module organizes the above records into callable module records and provides the hardware modules, software modules, and service modules to the configuration template matching module.

[0073] The configuration template matching module 03, connected to the deployment task generation module and the module library management module, is used to call the standardized module library and configuration template library based on the deployment task data, match the hardware modules, software modules, and service modules, and generate a module combination scheme. Specifically, the configuration template matching module receives the deployment task data output by the deployment task generation module and receives the hardware modules, software modules, and service modules provided by the module library management module. The configuration template matching module calls the configuration template library, matches the service scope field with the configuration templates for city center venues, community service stations, rural cultural points, and public institution reading corners, and generates candidate configuration templates by combining the available area field, power supply capacity field, network bandwidth field, and budget limit field. The configuration template matching module performs field verification on the candidate configuration templates with the standardized module library and generates a hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, system integration testing rules, and estimated total carbon footprint. The configuration template matching module encapsulates the above fields into a module combination scheme and passes the module combination scheme to the deployment data packet generation module.

[0074] A deployment data packet generation module 04, connected to the configuration template matching module, is used to generate a deployment data packet based on the module combination scheme. The deployment data packet includes basic positioning data, power supply cabling connection data, network device debugging data, terminal device installation data, software system activation data, content resource injection data, and system integration testing data. Specifically, the deployment data packet generation module receives the module combination scheme output by the configuration template matching module and reads the hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration testing rules. The deployment data packet generation module generates basic positioning data, power supply cabling connection data, network device debugging data, and terminal device installation data based on the hardware configuration list; generates software system activation data based on the software version requirements; generates content resource injection data based on the content service standards; and generates system integration testing data based on the system integration testing rules. The deployment data packet generation module writes device identifiers, network interfaces, data exchange formats, installation order, test order, and acceptance rules into the deployment data packet. The deployment data packet generation module transmits the deployment data packet to the deployment execution acquisition module and retains the associated locations of configuration adjustment data and maintenance instructions.

[0075] The deployment execution acquisition module 05, connected to the deployment data packet generation module, is used to collect deployment execution data and system integration test results based on the deployment data packet, and generate deployment acceptance data. Specifically, the deployment execution acquisition module receives the deployment data packet output by the deployment data packet generation module, and collects basic positioning completion information, power supply cabling connection completion information, network equipment debugging completion information, terminal equipment installation completion information, software system activation completion information, and content resource injection completion information according to the installation order. The deployment execution acquisition module collects network connectivity test results, software system activation test results, content resource injection test results, and system integration test results according to the test order, and compares the above test results with the acceptance rules. When the test results are inconsistent with the acceptance rules, the deployment execution acquisition module generates configuration adjustment data or maintenance instructions, and stores the configuration adjustment data or maintenance instructions in association with the deployment data packet. The deployment execution acquisition module encapsulates the deployment execution data, the system integration test results, and the acceptance rule comparison results into deployment acceptance data, and transmits the deployment acceptance data to the remote operation and maintenance module.

[0076] The remote operation and maintenance module 06, connected to the deployment execution and acquisition module, receives the deployment acceptance data, collects equipment status, energy consumption data, network status, service usage, fault conditions, maintenance instructions, and confirmation results, and generates template update data. Specifically, the remote operation and maintenance module receives the deployment acceptance data output by the deployment execution and acquisition module and reads the deployment task data reference field, module combination scheme reference field, deployment data packet reference field, deployment execution data, and system integration test results from the deployment acceptance data. The remote operation and maintenance module collects the equipment status of digital reading terminals, display devices, network devices, and sensing devices; collects energy consumption data generated by sensing devices and the carbon emission accounting module; collects network status generated by network devices; collects service usage data generated by the digital reading platform; collects fault conditions generated by the operation and maintenance management module; and records maintenance instructions and confirmation results. The remote operation and maintenance module associates the confirmation results with the deployment task data, the module combination scheme, and the configuration template library to generate template update data. The remote operation and maintenance module transmits the template update data to the template update module.

[0077] The template update module 07, connected to the remote operation and maintenance module, the module library management module, and the configuration template matching module, is used to update the standardized module library and the configuration template library based on the template update data. Specifically, the template update module receives template update data output by the remote operation and maintenance module and reads the device status, energy consumption data, network status, service usage, fault status, maintenance instructions, and confirmation results from the template update data. The template update module updates the hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration testing rules in the configuration template library according to the template update data, and updates the applicability conditions of hardware modules, software modules, and service modules in the standardized module library. The template update module provides the updated standardized module library to the module library management module and the updated configuration template library to the configuration template matching module.

Claims

1. A modular and rapid deployment method for zero-carbon reading spaces in urban and rural areas, characterized in that, include: S100: Receive the available area, power supply conditions, network conditions, budget constraints, service scope, and operation and maintenance requirements of the target site, standardize the fields and organize the installation locations, and generate deployment task data; S200: Based on the deployment task data, call the standardized module library and configuration template library, perform field verification and constraint verification, match hardware modules, software modules and service modules, and generate a module combination scheme; S300. Based on the module combination scheme, perform software system activation and joint debugging planning, and generate deployment data packets; the deployment data packets include basic positioning data, power supply cabling connection data, network equipment debugging data, terminal equipment installation data, software system activation data, content resource injection data, and system joint debugging test data; S400. Based on the deployment data package, execute the data and system integration test results to generate deployment acceptance data, and input the deployment acceptance data into the remote operation and maintenance platform to generate template update data.

2. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 1, characterized in that, The deployment task data includes field fields for site identification, available area, power supply capacity, network bandwidth, budget limit, service scope, installation location, number of modules, software version, content service, and operation and maintenance requirements.

3. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 1, characterized in that, The standardized module library includes a hardware module library, a software module library, and a service module library. The hardware module library records the physical specifications, power supply specifications, and network interfaces of digital reading terminals, display devices, network devices, and sensing devices. The software module library records the API interfaces, data exchange formats, and software version requirements of the digital reading platform, carbon emission accounting module, and operation and maintenance management module. The service module library records the process specifications and service quality indicators of green reading service standards, operation and maintenance service standards, and content service standards.

4. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 1, characterized in that, The configuration template library includes configuration templates for urban center venues, community service stations, rural cultural sites, and public institution reading corners. Each configuration template includes applicable area range, power supply conditions range, network conditions range, budget constraints range, hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, and system integration and testing rules.

5. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 4, characterized in that, The generation of the module combination scheme includes: matching the deployment task data with the configuration template library to generate candidate configuration templates; performing field verification between the candidate configuration templates and the standardized module library to generate a hardware configuration list, software version requirements, network bandwidth requirements, and estimated total carbon footprint.

6. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 1, characterized in that, The deployment data package also includes device identifier, network interface, data exchange format, installation order, test order, and acceptance rules. The test order includes network connectivity test, software system activation test, content resource injection test, and system integration test.

7. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 1, characterized in that, The deployment execution data includes basic positioning completion information, power supply cabling connection completion information, network equipment debugging completion information, terminal equipment installation completion information, software system activation completion information, content resource injection completion information, and system integration test results.

8. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 6, characterized in that, When the test results of the network connectivity test, software system activation test, content resource injection test, or system integration test are inconsistent with the acceptance rules, configuration adjustment data or maintenance instructions are generated, and the configuration adjustment data or maintenance instructions are associated with and stored with the deployment data packet.

9. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 1, characterized in that, The remote operation and maintenance platform collects equipment status, energy consumption data, network status, service usage, fault status, maintenance instructions, and confirmation results, and associates the confirmation results with the deployment task data, module combination scheme, and configuration template library to generate the template update data.

10. The modular rapid deployment method for urban and rural zero-carbon reading spaces according to claim 9, characterized in that, The template update data is used to update the hardware configuration list, software version requirements, network bandwidth requirements, content service standards, operation and maintenance service standards, or system integration testing rules in the configuration template library, and to update the applicable conditions of hardware modules, software modules, or service modules in the standardized module library.

Images