An architecture design method and system for industrial internet building space identification
By constructing an industrial internet-based building space identification system, the problems of difficulty in finding locations and non-standard naming caused by the complex spatial layout of hospitals have been solved, achieving efficient and secure space management and data support, and improving the quality of medical services.
Patent Information
- Application Number
- CN202610265236.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-03-05
- Publication Date
- 2026-07-10
AI Technical Summary
The complex spatial layout of hospitals leads to inefficiency for patients and staff when finding their way, traditional signage systems cannot be updated in a timely manner, and non-standard naming causes confusion in information transmission, affecting the quality of medical services and operational efficiency.
An industrial internet building space identification system is constructed, which connects devices and data through an industrial internet platform to generate a dynamic identification system. It uses attribute-free spatial codes to bind building space master data to achieve efficient management and location identification.
It improves the efficiency of hospital space management, reduces the time cost of finding locations, ensures data security and system performance, and adapts to the complex and ever-changing business needs of hospitals.
Smart Images

Figure CN122363659A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the technical field of industrial internet, and in particular to an architectural design method and system for industrial internet building space identification. Background Technology
[0002] In today's society, hospitals, as key locations for safeguarding public health, shoulder an extremely important mission of providing medical services. With the booming development of the medical industry and the ever-increasing demand for medical services, hospitals are continuously expanding in scale and becoming increasingly diversified in function. This makes the spatial layout of hospitals more complex, bringing many challenges to hospital operation and management, as well as to the activities of patients and staff.
[0003] From an architectural perspective, a hospital typically consists of multiple buildings of varying styles and functions. These buildings are numerous and staggered in height; some are main buildings carrying core medical functions, some are auxiliary buildings focusing on specific specialty treatments, and others are auxiliary buildings providing logistical support services. Each building contains multiple floors, ranging from a few to dozens of floors, with each floor having a distinct functional layout.
[0004] Each floor houses a large number of rooms with diverse functions, covering all aspects of the hospital's daily operations and medical services. Among them, wards are the primary locations for patient treatment and rehabilitation, requiring a warm and comfortable environment conducive to physical and mental recovery; operating rooms are crucial areas for performing various complex surgeries, demanding extremely stringent requirements for cleanliness, temperature, humidity, and sterility, as even minor environmental changes can affect the success of the surgery and the patient's safety; pharmacies, as vital departments for drug storage and dispensing, require excellent ventilation, moisture control, and fire prevention to ensure drug quality and safety; and laboratories are research bases for medical studies, disease detection, and diagnosis, with specific standards for the operating environment of experimental equipment, the stability of power supply, and the effectiveness of ventilation systems to guarantee the accuracy and reliability of experimental results.
[0005] Furthermore, the distribution of departments within the hospital is quite dispersed. Due to differences in their areas of expertise and functional needs, different departments may be located in different buildings, on different floors, and even different sections of the same department may be scattered throughout the hospital. For example, the cardiology department might be located on a high floor of the main building, while the dermatology department might be on a lower floor of another building; the outpatient clinic, inpatient ward, and examination rooms of the same department may also be in different areas. While this dispersed layout facilitates specialized medical services, it undoubtedly presents significant challenges to the hospital's daily operations.
[0006] For the daily operations of a hospital, efficient space management and accurate location identification are fundamental to ensuring the smooth operation of medical services. Clinical trial personnel frequently need to move between different departments, wards, and laboratories. They may need to retrieve test reports from the laboratory and deliver them to the relevant doctors within a short timeframe, or travel to wards to observe patients and collect data. However, the complex spatial layout of hospitals often causes them to struggle to find their target locations, spending a significant amount of time searching for routes. This not only reduces work efficiency but can also disrupt the entire medical process by delaying information transmission or operation time, ultimately negatively impacting the quality of medical services.
[0007] For patients, finding the correct department, ward, or examination room in the unfamiliar and complex environment of a hospital is undoubtedly a daunting task. Patients are often physically unwell and under considerable psychological stress when seeking medical care; having to spend a significant amount of time and energy searching for the correct location only exacerbates their burden and reduces their satisfaction with the healthcare experience. Some patients may miss their scheduled examinations because they cannot find the correct department, leading to delays in their treatment; others may become exhausted from running around the hospital, which is extremely detrimental to their recovery.
[0008] In the current development of hospital management information systems, a prominent and urgent problem is the severe lack of attention and development of master data on building spaces. Traditional signage systems, such as static signs and maps, while providing some location information for patients and staff, reveal significant limitations when dealing with real-time changes in the hospital environment.
[0009] Hospital space utilization is not static but constantly evolving. As medical services expand and adjust, departments may relocate or be added, and temporary medical facilities may be set up according to actual needs. For example, to respond to public health emergencies, hospitals may temporarily add fever clinics or isolation wards; as disciplines develop and patient needs change, some departments may expand, occupying more space. However, static signage and maps often fail to reflect these changes in a timely and accurate manner. When patients or staff rely on outdated signage to find their way, they are likely to become disoriented, resulting in a waste of time and effort.
[0010] Furthermore, traditional signage systems present information in a relatively simple and limited way, lacking sufficient detail and logic. Signs may simply indicate the department name and general direction, failing to provide clear and explicit guidance on crucial information such as specific floors, room numbers, and how to get there. Moreover, signs in different areas may vary in design style, content, and information layout, easily causing confusion for users. For example, some signs may only indicate the abbreviation of the department, leaving patients unclear about its specific meaning; others may be poorly positioned, obstructed by objects, and difficult to find.
[0011] In a healthcare environment, clear, consistent, and logical spatial naming conventions are crucial for ensuring efficient hospital operations and patient safety. A good naming system not only helps patients, visitors, and healthcare staff quickly locate their destinations, reducing getting lost and waiting time and improving medical and work efficiency, but also accelerates the response time of maintenance engineers in emergencies such as equipment malfunctions, ensuring that medical services are provided in a timely and accurate manner.
[0012] However, the naming of hospital spaces currently suffers from numerous irregularities. Different departments, floors, and even staff members may use different names for the same space, lacking unified standards and rules. For example, some departments may call a particular ward area "Internal Medicine Ward Area," while others may call it "Inpatient Department 1 Internal Medicine Area." Similarly, different rooms on the same floor may be named differently, some by room number, others by department and function. This lack of standardization and consistency can easily lead to misunderstandings and confusion in information transmission and communication, increasing the risk of errors. When medical staff need to urgently allocate equipment or supplies, the lack of standardized space naming may prevent them from accurately locating the storage locations, causing delays in medical work. During patient transfers or consultations, unclear space naming may force patients to search and wander around the hospital, severely impacting medical efficiency and patient well-being.
[0013] In conclusion, the complex spatial layout of hospitals and the current deficiencies in the construction and naming standards of architectural space master data have had a serious negative impact on the daily operation of hospitals, patients' medical experience, and the quality and efficiency of medical services. Therefore, it is urgent to explore effective solutions to improve the spatial management level of hospitals, optimize the medical environment for patients, and ensure the efficient and high-quality provision of medical services. Summary of the Invention
[0014] To address the aforementioned issues, the present invention aims to provide an architectural design method and system for industrial internet building space identification. By constructing industrial internet master data for building space and connecting various devices, systems, and data, an intelligent and efficient information network is formed, which can improve hospital space management.
[0015] The above-mentioned objective of this invention is achieved through the following technical solutions: An architectural design method for industrial internet building space identification includes the following steps: S100: Construct an industrial internet building space management platform architecture that includes a front-end presentation layer, business logic layer, IoT and device access layer, data storage and management layer, and security and compliance layer; S200: Establish building space master data based on the industrial internet building space management platform. The building space master data is used to maintain basic information about each location in the building. S300: Batch generate industrial internet identifiers set at various locations in the building, and after fixing the industrial internet identifiers at various locations, start the industrial internet identifiers to complete the binding with the building space master data; S400: Based on the industrial internet identifier that has been bound to the building space master data, initiate various application scenarios at various locations in the building, wherein the application scenarios are applications preset in the industrial internet building space management platform that correspond to the current building space master data in the building.
[0016] Further, in step S100, the front-end presentation layer in the industrial internet building space management platform architecture specifically includes: S111: Construct the basic framework of the front-end presentation layer under the architecture of the industrial internet building space management platform, including introducing the React JavaScript library developed based on Facebook to build the basic structure of the front-end presentation layer, introducing Redux as a global state management tool, using the React Router library to render different components according to URL changes, realizing the single-page application (SPA) function, configuring nested routes and dynamic route matching functions, and introducing Axios as an HTTP client for front-end and back-end data interaction. S112: Construct the front-end display by combining the master data of the building space and the requirements of the application scenario to be preset, including designing the page structure and style based on HTML5 and CSS3, selecting Element UI as the UI framework, integrating it with React through the adaptation layer, and splitting the UI into multiple independent widgets according to the React component design concept. S113: To achieve front-end interaction in conjunction with the industrial internet identification coding, the data flow in the application is designed according to the request-response pattern. When the operation is related to industrial internet identification coding, the front-end triggers the corresponding operation and sends an HTTP request to the back-end microservice. The back-end processes and returns the result. The front-end updates the UI according to the response. To address the complexity of asynchronous operations during the coding process, the Redux Thunk middleware is used to write an action creator that can return a function. This function receives the store's dispatch method, allowing multiple actions to be dispatched on demand or actions to be dispatched after the asynchronous operation is completed, ensuring the correct processing of the data flow. S114: Supports the construction of front-end functions initiated by the application scenario, including: enabling communication between the front-end and the back-end using a Spring Cloud microservice architecture via RESTful API; setting Spring Cloud Gateway as a unified API entry point for request routing, rate limiting, authentication, configuring Cross-Origin Resource Sharing (CORS) policies to ensure the front-end can securely call the back-end API; configuring different API base addresses for different environments to achieve environment isolation; defining standardized error codes and message formats to facilitate joint handling of exceptions by the front-end and back-end; and configuring interaction with the back-end service architecture, including lazy loading using React.lazy and Suspense for components related to the application scenario that are not displayed on the first screen to reduce initial loading time; code splitting using Webpack's Code Splitting function to load only the currently needed parts; setting HTTP cache headers appropriately to reduce duplicate requests using browser caching; optimizing images, compressing file sizes, using modern image formats, generating thumbnails when necessary, and using CDN to accelerate static resource loading. It also includes performance optimization settings such as using HTTPS encrypted transmission, CSRF protection, and XSS defense measures to ensure user data security; strictly validating and filtering user input to prevent malicious script injection attacks; and using Element... When designing the UI, pay attention to security-related attributes and methods, and implement security protection strategies to avoid introducing new security risks.
[0017] Furthermore, in step S1, the business logic layer in the industrial internet building space management platform architecture specifically comprises: S121: Construct the architecture of the industrial internet building space management platform, including clarifying the position and role of the business logic layer in the entire industrial internet building space management platform architecture, establishing a collaborative relationship with the front-end presentation layer, the data storage and management layer, and the security and compliance layer, and providing a basic framework for the implementation of subsequent specific business logic; S122: Establish the building space master data, including activating the building space master data management function module in the business logic layer, collecting basic information of each location in the building, entering the collected basic information into the industrial internet building space management platform, and storing the organized building space master data in the data storage and management layer. S123: Implement industrial internet identification-related operations, including batch generating industrial internet identifications for various locations in a building, fixing the generated industrial internet identifications at the corresponding locations in the building, triggering the binding process between the industrial internet identifications and the building space master data, and associating the identification information with the corresponding master data in the business logic layer so that each identification can accurately point to the corresponding building space location and its basic information. S124: Conducting business based on bound identifiers, including when it is necessary to obtain detailed building space information, the business logic layer calls the Industrial Internet Identifier Resolution Service, connects to the Industrial Internet Identifier Resolution System, and through interaction with the Industrial Internet Identifier Resolution System, quickly resolves the building space identifier, extracts the detailed building space information corresponding to the identifier, and provides the resolved detailed building space information to other business modules, providing data support for various application scenarios initiated based on the bound identifiers, so that various applications preset in the Industrial Internet Building Space Management Platform can run accurately and effectively in the corresponding building space locations.
[0018] Furthermore, in step S1, the IoT and device access layer in the industrial internet building space management platform architecture specifically refers to: S131: Select and deploy IoT devices, including temperature monitoring devices, humidity monitoring devices, and IoT gateway devices; S132: Dynamic environment identifiers for different IoT devices integrate multiple networking and communication technologies, including 5G, Cat1, NB-IoT, LoRaWAN, Wi-Fi, and BLE, based on different application scenarios and data transmission requirements; S133: Sampling is performed based on the default sampling frequency of the IoT device, and the processed collected data is sent to the gateway device through a wireless communication protocol; S134: Based on the usage requirements and environmental standards of the building space, set abnormal thresholds for environmental parameters, including temperature and humidity, on a remote server or a gateway device with intelligent processing capabilities, and perform abnormal detection and alarm triggering based on the abnormal thresholds, wherein the alarm triggering adopts methods including real-time push, notification mechanism, and automatic response. S135: Utilize BIM technology to construct a three-dimensional digital twin model of the building space, accurately presenting the building structure and equipment layout, and implement the application scenarios including energy management, fault early warning, and user experience.
[0019] Furthermore, in step S1, the data storage and management layer in the industrial internet building space management platform architecture specifically includes: S141: Design and implement a data storage strategy that includes IoT data storage, structured data storage, unstructured and semi-structured data storage. The IoT data storage is for the large amount of time-series data generated by IoT devices, and a high-performance TDengine database designed specifically for time-series data is selected for storage. The structured data storage is for relational structured data, and a PostgreSQL database is selected for storage. The unstructured and semi-structured data storage introduces HDFS from the Hadoop ecosystem to handle the storage and analysis of large-scale unstructured or semi-structured data. S142: Data query and report statistics are implemented by using Flink CDC combined with Flink real-time computing engine.
[0020] Furthermore, in step S1, the security and compliance layer in the industrial internet building space management platform architecture specifically comprises: S151: Deploy the system in an isolated private cloud environment, with all external services forwarded through a unified security gateway; S152: Set up the first layer of security protection barrier as the gateway-level security control, including traffic control and load balancing, access logging, malicious access protection, and WAF firewall protection; S153: Set up a second layer of security protection as an application-level security enhancement, including SSL / TLS encrypted communication, user activity logs, password policy configuration, and encrypted data transmission; S154: Set up a security policy for sensitive data storage, including selecting the Bcrypt algorithm for one-way hash encryption of critical user password information, selecting the RSA algorithm for sensitive data that requires two-way encryption, and equipping a database auditing system to monitor and record all database operations in real time. S155: Configure regular vulnerability scanning and incident response, including regular system vulnerability scanning and timely handling of security hotspots and vulnerabilities; S156: Establish a strict safety management system, including safety policies and standards, safety training and awareness enhancement, and safety audits and assessments.
[0021] Further, in step S200, building space master data is established based on the industrial internet building space management platform. This building space master data is used to maintain basic information about various locations within the building, specifically: A campus is created in the industrial internet building space management platform, which supports the management of multiple campuses. After the campus is created, maintain the buildings in the campus, and maintain the floors and rooms on each floor in turn.
[0022] Further, in step S300, industrial internet identifiers are generated in batches and set at various locations within the building. After fixing the industrial internet identifiers at each location, the industrial internet identifiers are activated to complete the binding with the building space master data. Specifically: The industrial internet identifiers are generated in batches as needed. The industrial internet identifiers are attribute-free spatial codes. After fixing the industrial internet identifiers in various locations, the industrial internet identifiers are scanned and the binding with the building space master data is completed according to the page prompts.
[0023] Further, in step S400, various application scenarios are initiated at different locations within the building based on the industrial internet identifier already bound to the building space master data. These application scenarios are pre-set applications in the industrial internet building space management platform corresponding to the current location in the building space master data. Specifically: Scanning the corresponding industrial internet identifier initiates various application scenarios at different locations within the building; The application scenarios include those related to reporting repairs, inspecting equipment and facilities, maintaining usage information, and environmental monitoring and early warning.
[0024] An architecture design system for industrial internet building spatial identifiers, used to implement the architecture design method for industrial internet building spatial identifiers as described above, includes: The management platform architecture building module is used to construct an industrial internet building space management platform architecture that includes a front-end presentation layer, a business logic layer, an IoT and device access layer, a data storage and management layer, and a security and compliance layer. The building space master data establishment module is used to establish building space master data based on the industrial internet building space management platform. The building space master data is used to maintain basic information of various locations in the building. The Industrial Internet Identifier Generation Module is used to generate Industrial Internet Identifiers in batches and set in various locations in a building. After fixing the Industrial Internet Identifiers in various locations, it activates the Industrial Internet Identifiers to complete the binding with the building space master data. The application scenario initiation module is used to initiate various application scenarios at various locations in the building based on the industrial internet identifier that has been bound to the building space master data. The application scenarios are applications that are preset in the industrial internet building space management platform and correspond to the current building space master data in the building.
[0025] Compared with the prior art, the present invention has at least one of the following beneficial effects: (1) Addressing Management Pain Points: In the past, hospital building space data was not valued or utilized. This invention establishes a unified standard for building space master data, integrating various data such as medical equipment location, room usage information, and environmental monitoring, deeply exploring the value of building space data and providing rich data support for hospital management. It enables quick acquisition of location information by scanning building space markers and performs operations such as reporting repairs, inventory, and location updates, changing the traditional cumbersome management methods, greatly improving the efficiency of hospital building space management, and saving manpower and time costs.
[0026] (2) System design and architecture level: The functional modules and technical architecture of the system are carefully planned, covering the front-end display layer, business logic layer, Internet of Things and device access layer, data storage and management layer, and security and compliance layer. Each layer works closely together to ensure that the system as a whole meets the requirements of high performance, security and scalability, and can adapt to the complex and ever-changing business needs and future development of the hospital.
[0027] (3) System Development and Operation: During the system design and development phase, functional modules such as industrial internet identifier resolution, QR code identifier design, and identifier-based applications were developed one by one and rigorously tested to ensure complete functionality and stable operation. Simultaneously, sufficient cloud service resources were ensured during system environment setup to support stable system operation and provide reliable technical support for the hospital's daily management. Through multiple measures such as firewall settings, data encryption, and user access control, data security was comprehensively protected to prevent data leakage and unauthorized access, meeting the hospital's highly sensitive security needs for patient and business data. Attached Figure Description
[0028] Figure 1 This is an overall flowchart of the architectural design method for the industrial internet building space identification of the present invention; Figure 2 This is a schematic diagram of the technical architecture of the industrial internet building space management platform of the present invention; Figure 3 This is a schematic diagram illustrating the hospital campus management of this invention; Figure 4 This is a schematic diagram illustrating the new management features added to this invention; Figure 5 This is a schematic diagram of the spatial code of the present invention; Figure 6 This is a schematic diagram of the spatial code pasting method of the present invention; Figure 7 This is a schematic diagram illustrating the activation of the spatial code by scanning a QR code according to the present invention; Figure 8 This is a schematic diagram illustrating the binding of spatial master data according to the present invention; Figure 9 This is a schematic diagram illustrating the deployment of spatial codes according to the present invention; Figure 10 This is a schematic diagram illustrating the application of the spatial code in this invention; Figure 11 This is a schematic diagram illustrating the fault reporting mechanism of the present invention. Figure 12 This is a schematic diagram of the equipment and facilities of the present invention; Figure 13 This is a schematic diagram illustrating the room information viewing process according to the present invention; Figure 14 This is a schematic diagram of room information editing according to the present invention; Figure 15 This is a schematic diagram illustrating the room environment requirements for maintenance according to the present invention; Figure 16 This is a schematic diagram of the departmental environmental monitoring of the present invention; Figure 17 This is a schematic diagram of the abnormal event monitoring of the present invention; Figure 18 This is a schematic diagram of the room temperature, humidity and pressure monitoring system of the present invention; Figure 19 This is an overall structural diagram of the industrial internet building space identification architecture design system of the present invention. Detailed Implementation
[0029] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0030] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this specification means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0031] This invention uses the medical industry as an example, integrating Industrial Internet Identifier Resolution with unique building space identifiers. Through the construction of a building space master data system, it creates innovative applications for building space identifiers based on the Industrial Internet. Using the building space Industrial Internet identifier as an entry point, it links to more Industrial Internet application scenarios and lays the foundation for cross-departmental data sharing and integration between hospital information systems. A collection of innovative building space identifier applications based on the Industrial Internet has been constructed. The system adopts a responsive web and mobile interface, allowing administrators to collect building space master data and assign Industrial Internet identifiers. Clinical and frontline staff can scan the identifier QR code to quickly access the associated Industrial Internet identifier object, initiate repair requests, perform inspections, report adverse events, view room equipment assets, maintain room usage information, and perform equipment and facility inventory checks. Patients can scan the identifier QR code to learn about the usage information of the building space.
[0032] This case study enables hospitals to achieve efficient management of their building spaces, significantly improving the ease of use and management efficiency of location-based hospital operations management applications. It lays the foundation for cross-system data governance and interoperability within the hospital, thereby enhancing patient safety and the quality of medical services. The project is easy to implement, low-cost, and highly replicable and scalable.
[0033] This invention, through the construction of an industrial internet master data system for building space, connects various devices, systems, and data to form an intelligent and efficient information network. This network can improve hospital space management, including: (1) Data integration and analysis Industrial Internet platforms can collect and analyze data from various parts of the hospital, including equipment status, personnel flow, and environmental parameters, providing hospital managers with decision-making support and enabling refined management.
[0034] (2) Dynamic Identification System By combining technologies such as the Industrial Internet, QR codes, and RFID, the Industrial Internet can build a dynamic identification system. This system can provide static location information, such as repair locations, inspection points, and fire safety locations. It can also be updated in real time according to actual conditions, such as changes in the department using the equipment, real-time equipment location, and personnel location.
[0035] (3) Data security In terms of data security and privacy protection, the Industrial Internet adopts advanced encryption technology and access control mechanisms to ensure the security of patient information.
[0036] With the maturation of technologies such as 5G, IoT, cloud computing, and AI, the potential of the Industrial Internet in hospital spatial signage applications will be further explored. In the future, we can expect to see more intelligent and personalized medical services, as well as more efficient and secure hospital operation models. This will not only improve patient experience but also help hospitals optimize resource allocation and improve the overall level of medical services. With continuous technological innovation, the Industrial Internet will lead the healthcare industry towards a more intelligent and human-centered direction.
[0037] The following is an illustration through specific examples: First Embodiment like Figure 1 As shown, this embodiment provides an architectural design method for industrial internet building space identification, including the following steps: S100: Construct an industrial internet building space management platform architecture that includes a front-end presentation layer, a business logic layer, an IoT and device access layer, a data storage and management layer, and a security and compliance layer.
[0038] Leveraging mobile internet, industrial internet, and big data technologies, this project aims to build an innovative application for building space identification based on the industrial internet. The platform's technical architecture is designed around the core needs of industrial internet identification, building space management, and innovative applications, aiming to construct an efficient, intelligent, and secure data-driven system. The following is an overview of the technical architecture based on microservices, big data analytics, and IoT technologies: (1) Front-end presentation layer S111: Construct the basic framework of the front-end presentation layer under the architecture of the industrial internet building space management platform, including introducing the React JavaScript library developed based on Facebook to build the basic structure of the front-end presentation layer, introducing Redux as a global state management tool, using the React Router library to render different components according to URL changes to realize the single-page application (SPA) function, configuring nested routes and dynamic route matching functions, and introducing Axios as an HTTP client for front-end and back-end data interaction.
[0039] S112: Construct the front-end display by combining the master data of the building space and the requirements of the preset application scenario, including designing the page structure and style based on HTML5 and CSS3, selecting Element UI as the UI framework, integrating it with React through the adaptation layer, and splitting the UI into multiple independent widgets according to the React component design concept.
[0040] S113: To facilitate front-end interaction in conjunction with the industrial internet identifier coding, the application's data flow is designed according to a request-response pattern. When an operation related to industrial internet identifier coding is involved, the front-end triggers the corresponding operation and sends an HTTP request to the back-end microservice. The back-end processes the request and returns the result. The front-end updates the UI based on the response. To address the complexity of asynchronous operations during the coding process, the Redux Thunk middleware is used to write an action creator that can return a function. This function receives the store's dispatch method, allowing multiple actions to be dispatched on demand or dispatched after the asynchronous operation is completed, ensuring the correct processing of the data flow.
[0041] S114: Supports the construction of front-end functions initiated by the application scenario, including: enabling communication between the front-end and the back-end using a Spring Cloud microservice architecture via RESTful API; setting Spring Cloud Gateway as a unified API entry point for request routing, rate limiting, authentication, configuring Cross-Origin Resource Sharing (CORS) policies to ensure the front-end can securely call the back-end API; configuring different API base addresses for different environments to achieve environment isolation; defining standardized error codes and message formats to facilitate joint handling of exceptions by the front-end and back-end; and configuring interaction with the back-end service architecture, including lazy loading using React.lazy and Suspense for components related to the application scenario that are not displayed on the first screen to reduce initial loading time; code splitting using Webpack's Code Splitting function to load only the currently needed parts; setting HTTP cache headers appropriately to reduce duplicate requests using browser caching; optimizing images, compressing file sizes, using modern image formats, generating thumbnails when necessary, and using CDN to accelerate static resource loading. It also includes performance optimization settings such as using HTTPS encrypted transmission, CSRF protection, and XSS defense measures to ensure user data security; strictly validating and filtering user input to prevent malicious script injection attacks; and using Element... When designing the UI, pay attention to security-related attributes and methods, and implement security protection strategies to avoid introducing new security risks.
[0042] The technical solutions involved in the above process steps are analyzed in detail as follows: 1. React framework The front-end presentation layer of this project is built on the React JavaScript library developed by Facebook. React is known for its efficient virtual DOM mechanism and component-based development model, providing a fast-response user interface and supporting code reuse and maintainability. React also has a large community support and a wealth of third-party libraries, which can accelerate the development process and improve application stability.
[0043] 2. Redux State Management To better manage the state of complex applications, we introduced Redux as a global state management tool. Redux adheres to the single source principle, storing all state in a single object tree, the store. Pure functions (reducers) are defined to respond to actions in the application, thereby updating the state in the store. This pattern not only improves the transparency of state management but also facilitates debugging and testing.
[0044] 3. React Router Route Management React Router is the most commonly used routing management library in React applications. It allows us to render different components based on changes in the URL, enabling the functionality of a single-page application (SPA). React Router supports features such as nested routes and dynamic route matching, meeting the needs of complex business logic.
[0045] 4. Axios network requests Axios is a Promise-based HTTP client that can be used in both browsers and Node.js environments. We chose Axios for front-end and back-end data interaction because it provides a concise API, supports the interceptor pattern, and is easy to handle request and response preprocessing and error handling.
[0046] 5. Element UI framework To accelerate UI development and ensure design consistency, we chose Element UI as our UI framework. Element UI is a Vue-based desktop component library for developers, designers, and product managers. Although this project uses React, we seamlessly integrated Element UI with React through an adaptation layer. Element UI provides a rich set of high-quality components, such as tables, forms, and dialog boxes, greatly simplifying complex UI layouts and interaction designs. Furthermore, Element UI supports internationalization and theme customization to meet the personalized needs of users in different regions.
[0047] 6. HTML5 and CSS3 The front-end pages of this project are built entirely on the latest HTML5 standards, leveraging HTML5's semantic tags, multimedia support, and offline storage features to enhance webpage expressiveness and user experience. Simultaneously, we extensively adopted new CSS3 features, including but not limited to the Flexbox model, grid layout, animation effects, gradients, and shadows, to achieve a more aesthetically pleasing and modern design. CSS3's media queries enable our pages to adapt to different devices, ensuring cross-platform consistency and usability.
[0048] 7. Component-based design React encourages breaking down the UI into multiple independent widgets, or components. Each component is responsible for its own small portion of the view and can receive external data or behaviors through props. Our application employs advanced features such as Higher-Order Components (HOCs) and custom Hooks to enhance component composability and reusability. At the same time, we strictly adhere to the principle of unidirectional data flow, ensuring that parent components pass data to child components, while child components can only affect the state of parent components through callback functions. In component design, we also fully utilize ready-made components provided by Element UI, reducing the workload of reinventing the wheel and focusing on implementing business logic.
[0049] 8. Data Flow Management The data flow in the application follows a "request-response" pattern: when a user triggers an action, the frontend sends an HTTP request to the backend microservice; upon receiving the request, the backend executes the corresponding business logic and returns the result; the frontend updates the UI based on the response. To address the complexity of asynchronous operations, we utilize the Redux Thunk middleware, which allows us to write action creators that return a function instead of a regular object. This function accepts the store's `dispatch` method as a parameter, allowing us to dispatch multiple actions as needed, or dispatch actions only after the asynchronous operation is complete.
[0050] 9. Interaction with the backend Spring Cloud microservice architecture The backend adopts a Spring Cloud microservice architecture, which includes, but is not limited to, Eureka service registration and discovery, Ribbon load balancing, Feign declarative REST client, and Hystrix circuit breaker. Communication between the frontend and backend is achieved through a RESTful API. To improve system reliability and performance, we implemented the following measures: API Gateway: Set up a unified API entry point through Spring Cloud Gateway to perform operations such as request routing, rate limiting, and authentication.
[0051] Cross-Origin Resource Sharing (CORS): Configure CORS policies to enable the front end to safely call APIs provided by the back end.
[0052] Environment isolation: Configure different API base addresses for different environments (such as development, testing, and production) to ensure that the environments do not interfere with each other.
[0053] Error handling: A standardized set of error codes and message formats is defined to facilitate joint understanding and handling of abnormal situations by both the front-end and back-end.
[0054] 10. Performance optimization To ensure a good user experience, we have optimized performance in the following aspects: Lazy loading: For components that are not displayed on the first screen, React.lazy and Suspense are used to load them on demand, reducing the initial loading time.
[0055] Code splitting: Using Webpack's Code Splitting feature, the application is divided into multiple smaller chunks, and only the parts that are currently needed are loaded.
[0056] Caching strategy: Configure HTTP cache headers appropriately and utilize browser caching to reduce duplicate requests.
[0057] Image optimization: Compress image file size, use modern image formats (such as WebP), and generate thumbnails when necessary.
[0058] Using a CDN: For static resources (such as images, fonts, JavaScript, and CSS files), we accelerate them using a Content Delivery Network (CDN) to reduce resource loading time.
[0059] 11. Safety considerations Security is a crucial component of this project. We have implemented a series of measures to ensure the security of user data, including but not limited to HTTPS encrypted transmission, CSRF protection, and XSS prevention. Furthermore, we have rigorously validated and filtered user input to prevent malicious script injection attacks. When using Element UI, we have also paid special attention to its security-related properties and methods to ensure that the UI framework does not introduce new security vulnerabilities.
[0060] The responsive web and mobile application interfaces provide an intuitive and user-friendly experience. Users can quickly manage building space master data, assign industrial internet identifiers, and initiate innovative applications.
[0061] (2) Business Logic Layer S121: Construct the architecture of the industrial internet building space management platform, including clarifying the position and role of the business logic layer in the entire industrial internet building space management platform architecture, establishing a collaborative relationship with the front-end presentation layer, the data storage and management layer, and the security and compliance layer, and providing a basic framework for the implementation of subsequent specific business logic.
[0062] S122: Establish the building space master data, including activating the building space master data management function module in the business logic layer, collecting basic information of each location in the building, entering the collected basic information into the industrial internet building space management platform, and storing the organized building space master data into the data storage and management layer.
[0063] S123: Implement industrial internet identification-related operations, including batch generating industrial internet identifications for various locations in the building, fixing the generated industrial internet identifications to the corresponding locations in the building, triggering the binding process between the industrial internet identifications and the building space master data, and associating the identification information with the corresponding master data in the business logic layer so that each identification can accurately point to the corresponding building space location and its basic information.
[0064] S124: Conducting business based on bound identifiers, including when it is necessary to obtain detailed building space information, the business logic layer calls the Industrial Internet Identifier Resolution Service, connects to the Industrial Internet Identifier Resolution System, and through interaction with the Industrial Internet Identifier Resolution System, quickly resolves the building space identifier, extracts the detailed building space information corresponding to the identifier, and provides the resolved detailed building space information to other business modules, providing data support for various application scenarios initiated based on the bound identifiers, so that various applications preset in the Industrial Internet Building Space Management Platform can run accurately and effectively in the corresponding building space locations.
[0065] (3) Internet of Things and Device Access Layer S131: Select and deploy IoT devices, including temperature monitoring devices, humidity monitoring devices, and IoT gateway devices.
[0066] S132: Dynamic environment identifiers for different IoT devices integrate multiple networking and communication technologies, including 5G, Cat1, NB-IoT, LoRaWAN, Wi-Fi, and BLE, based on different application scenarios and data transmission requirements.
[0067] S133: Sampling is performed based on the default sampling frequency of the IoT device, and the processed collected data is sent to the gateway device through a wireless communication protocol; S134: Based on the usage requirements and environmental standards of the building space, set abnormal thresholds for environmental parameters, including temperature and humidity, on a remote server or a gateway device with intelligent processing capabilities, and perform abnormal detection and alarm triggering based on the abnormal thresholds, wherein the alarm triggering adopts methods including real-time push, notification mechanism, and automatic response. S135: Utilize BIM technology to construct a three-dimensional digital twin model of the building space, accurately presenting the building structure and equipment layout, and implement the application scenarios including energy management, fault early warning, and user experience.
[0068] The technical solutions involved in the above process steps are analyzed in detail as follows: 1. IoT Device Selection and Deployment 1.1 Equipment Selection Based on the needs of building space environmental monitoring, we carefully selected suitable sensors and IoT devices to ensure accurate and efficient collection and transmission of environmental data.
[0069] Temperature monitoring: High-precision temperature sensors: Employ the DS18B20 digital temperature sensor (suitable for wired connections and meeting requirements), or a temperature sensor module with wireless communication capabilities, such as the DHT22. These sensors feature high precision, low power consumption, and stable operation in various environments.
[0070] Humidity monitoring: Humidity sensor: High-performance humidity sensors such as the HIH-4000-001 are selected to ensure accurate humidity measurements. This sensor features fast response and a wide measurement range, making it suitable for indoor environmental monitoring.
[0071] IoT gateway: Communication protocol support: Select an IoT gateway device that supports LoRaWAN or NB-IoT communication protocols, such as Helium Hotspot or NBIoT Gateway. These gateway devices have wide network coverage and stable communication performance, enabling them to effectively connect sensors and transmit data to remote servers.
[0072] Intelligent processing capabilities: Some gateway devices have built-in edge computing capabilities, which can perform preliminary data processing and anomaly detection locally, reducing the burden on remote servers and improving response speed.
[0073] 1.2 Equipment Deployment Deploy sensors and gateway devices appropriately within the building space to ensure the accuracy and comprehensiveness of data collection.
[0074] Temperature sensor: Avoid direct sunlight and proximity to heat sources. Place it in the center of the room or a representative area to obtain data that best reflects the overall ambient temperature.
[0075] Humidity sensor: Place it in a well-ventilated location, away from water sources or humid areas, to ensure the accuracy of humidity data.
[0076] Gateway devices: Based on the building structure and sensor distribution, select appropriate locations to install gateway devices, ensuring their communication range covers the entire building space. For large buildings, multiple gateways may need to be deployed to achieve seamless coverage.
[0077] 2. Network connectivity and communication protocols Our IoT device dynamic environment identifiers have the capability to integrate multiple networking and communication technologies, including but not limited to 5G, Cat1, NB-IoT, LoRaWAN, Wi-Fi, and BLE. This multi-protocol support enables the system to adapt to different network environments and application scenarios, providing extensive network connectivity and strong adaptability.
[0078] 5G / Cat1: Provides high-speed, low-latency network connectivity, suitable for scenarios requiring real-time data transmission.
[0079] NB-IoT: Designed specifically for low-power wide-area networks, suitable for long-distance, low-bandwidth environmental monitoring applications.
[0080] LoRaWAN features long range and low power consumption, making it suitable for large-scale distributed sensor networks.
[0081] Wi-Fi / BLE: Suitable for short-range, high-frequency data transmission, ideal for interconnecting devices within a local area.
[0082] 3. Environmental monitoring and data collection 3.1 Sensor Data Acquisition Our IoT device dynamic environment identifiers support custom sampling frequencies for collecting environmental data, ensuring the timeliness and accuracy of the data.
[0083] Default sampling frequency: Temperature sensor: Collects temperature data every 1 minute.
[0084] Humidity sensor: Collects humidity data every 5 minutes.
[0085] Data preprocessing: The sensor performs preliminary processing on the collected data, including analog-to-digital conversion and data filtering, to improve the accuracy and usability of the data.
[0086] 3.2 Data Transmission and Aggregation The sensors transmit the processed data to the gateway device via a wireless communication protocol. After receiving the data from each sensor, the gateway device aggregates and organizes the data, combining data from different sensors at the same timestamp into a data packet containing multiple environmental parameters.
[0087] Data transmission: The gateway device sends the aggregated data to a remote server via a network connection for further analysis and processing.
[0088] Data redundancy and backup: To ensure data security and reliability, the system supports redundant data storage and regular backups to prevent data loss.
[0089] 4. Abnormal alarm mechanism 4.1 Setting the abnormal threshold Based on the usage requirements of the building space and environmental standards, set abnormal thresholds for various environmental parameters. These thresholds can be stored on a remote server or configured on a gateway device with intelligent processing capabilities.
[0090] Temperature: The normal range is 18-26°C. Anything outside this range is considered abnormal.
[0091] Humidity: The normal range is 40%-65%. Anything outside this range is considered abnormal.
[0092] 4.2 Anomaly Detection and Alarm Triggering When the server or gateway device receives sensor data, it compares the data with anomaly thresholds. If the data exceeds the thresholds, an anomaly is considered to have occurred, and an alarm mechanism is triggered.
[0093] Alarm methods: Real-time push: Pushes data to the system monitoring dashboard in real time via WebSocket, ensuring that administrators can understand abnormal situations immediately.
[0094] Notification mechanism: Send emails and push notifications to relevant responsible persons, informing them of the specific content and location of the anomaly.
[0095] Automatic response: Based on preset rules, the system can automatically take corresponding measures, such as adjusting the air conditioning temperature and starting the dehumidification equipment, to quickly restore normal environmental conditions.
[0096] 5. Dynamic energy identification and positioning function 5.1 Digital Twin Binding The dynamic environmental identifiers of IoT devices are linked to the digital twin model of the building space, enabling real-time monitoring of the building space and location of dynamic energy identifiers.
[0097] Digital twin model: Using BIM (Building Information Modeling) technology to construct a three-dimensional digital twin model of the building space, accurately reflecting the building structure and equipment layout.
[0098] Real-time data synchronization: Environmental data collected by sensors is synchronized to the digital twin model in real time, enabling managers to intuitively view the environmental conditions of each area.
[0099] Dynamic energy identification: By associating IoT devices with specific locations in a digital twin model, the system can generate a unique dynamic energy identification for each device to track and manage the device's energy consumption.
[0100] 5.2 Application Scenarios Energy Management: By monitoring environmental parameters such as temperature and humidity in various areas of the building space in real time, the system can optimize the operation strategies of equipment such as air conditioning and lighting, reduce energy consumption, and improve energy efficiency.
[0101] Fault warning: By combining historical data and machine learning algorithms, the system can predict potential equipment failures, perform maintenance in advance, and reduce downtime.
[0102] User experience: Based on users' personalized needs, the system can automatically adjust indoor environmental parameters to provide a more comfortable working and living environment.
[0103] By integrating IoT technologies (such as LoRaWAN and NB-IoT) into building spaces, environmental monitoring, data collection, and anomaly alarms can be achieved, enhancing the real-time performance and accuracy of the system.
[0104] Message push service Integrate message queue technologies (such as RabbitMQ and Kafka) to achieve efficient delivery of real-time messages and ensure that critical information is delivered to the relevant responsible persons in a timely manner.
[0105] (4) Data storage and management layer S141: Design and implement a data storage strategy that includes IoT data storage, structured data storage, unstructured and semi-structured data storage. The IoT data storage is for the large amount of time-series data generated by IoT devices, and a high-performance TDengine database designed specifically for time-series data is selected for storage. The structured data storage is for relational structured data, and a PostgreSQL database is selected for storage. The unstructured and semi-structured data storage introduces HDFS from the Hadoop ecosystem to handle the storage and analysis of large-scale unstructured or semi-structured data. S142: Data query and report statistics are implemented by using Flink CDC combined with Flink real-time computing engine.
[0106] The technical solutions involved in the above process steps are analyzed in detail as follows: 1. Data storage strategy This system employs a scientific data separation and storage strategy, selecting the most suitable storage solution based on the characteristics of different data types and application scenarios. This tiered storage design not only improves data processing efficiency but also ensures the system's scalability and high availability.
[0107] 1.1 IoT Data: TDengine Time Series Database Cluster For the large amounts of time-series data generated by IoT devices, we chose the high-performance TDengine database, specifically designed for time-series data. TDengine offers the following significant advantages: High throughput: Supports write speeds of millions of data points per second, meeting the real-time data acquisition needs of massive data in IoT scenarios.
[0108] High compression ratio: Utilizing advanced compression algorithms, it can significantly reduce storage space usage and lower storage costs.
[0109] Excellent query performance: The optimized index structure and query engine enable TDengine to perform exceptionally well when handling complex queries, making it particularly suitable for real-time monitoring and alerting systems that require fast responses.
[0110] Distributed architecture: By building a TDengine cluster, horizontal data scaling and automatic failover are achieved, ensuring the stability and reliability of the system.
[0111] 1.2 Structured Data: PostgreSQL Database Cluster For relational structured data, we chose the powerful and stable PostgreSQL database. PostgreSQL has a wealth of features, including but not limited to: ACID transaction support: ensures consistency, isolation, durability and atomicity of data operations, and is suitable for industries such as finance and healthcare that have extremely high requirements for data accuracy.
[0112] Flexible query language: Supports complex SQL queries and advanced features (such as window functions and recursive queries), facilitating data analysis and report generation.
[0113] Highly scalable: Full-text search, geographic information system (GIS) and other functions can be easily integrated through the plug-in mechanism to meet diverse business needs.
[0114] High availability: By leveraging PostgreSQL's streaming replication and hot standby capabilities, a highly available database cluster was built, ensuring service continuity and data security.
[0115] 1.3 Data Utilization and Analysis: Hadoop HDFS To address the storage and analysis of large-scale unstructured or semi-structured data, we introduced HDFS (Hadoop Distributed File System) from the Hadoop ecosystem. HDFS has the following characteristics: Distributed storage: Data is distributed across multiple nodes, providing excellent fault tolerance and horizontal scalability.
[0116] Large-capacity storage: Suitable for storing petabyte-level massive amounts of data, applicable to big data scenarios such as log recording, images and videos.
[0117] High-efficiency reading: Through batch reading and parallel processing, HDFS can complete the loading and preprocessing of large amounts of data in a short time.
[0118] Rich ecosystem: Seamlessly integrates with tools such as MapReduce, Spark, and Hive, supporting a variety of data analysis and mining tasks, and providing strong technical support for data scientists and analysts.
[0119] 2. Data Query and Real-time Calculation 2.1 Real-time data query and report statistics To achieve efficient and real-time data querying and reporting, we adopted a solution combining Flink CDC (Change DataCapture) with the Flink real-time computing engine. Specifically: Flink CDC: By capturing change events in databases such as PostgreSQL and MySQL, Flink CDC can synchronize data to the Flink stream processing platform in real time. This approach avoids the data latency issues that may occur in traditional ETL processes, ensuring data timeliness and consistency.
[0120] Flink Real-Time Computing Engine: Flink is an open-source stream processing framework characterized by low latency, high throughput, and exact-first-time semantics. It can process streaming data from multiple data sources in real time, performing complex aggregation, filtering, and windowing operations. Finally, Flink outputs the processing results to a visualization platform, enabling the display and interaction of real-time data reports.
[0121] 2.2 Innovation Points and Advantages Seamless integration: The tight integration of Flink CDC with Flink simplifies the data pipeline construction process and reduces the workload of development and maintenance.
[0122] High performance: Flink's streaming capabilities enable the system to respond to user requests within milliseconds, providing instant data feedback.
[0123] Flexibility: It supports custom calculation logic and business rules, and can adjust the content and format of reports according to different application scenarios.
[0124] Scalability: As the amount of data increases, the system's processing capacity can be linearly improved by adding computing nodes, ensuring long-term sustainable development.
[0125] Distributed databases (such as Hadoop HDFS and NoSQL databases) are used to store massive amounts of data, while data warehouse technology is used to integrate data and optimize query performance.
[0126] (5) Security and Compliance Layer S151: Deploy the system in an isolated private cloud environment, with all external services forwarded through a unified security gateway; S152: Set up the first layer of security protection barrier as the gateway-level security control, including traffic control and load balancing, access logging, malicious access protection, and WAF firewall protection; S153: Set up a second layer of security protection as an application-level security enhancement, including SSL / TLS encrypted communication, user activity logs, password policy configuration, and encrypted data transmission; S154: Set up a security policy for sensitive data storage, including selecting the Bcrypt algorithm for one-way hash encryption of critical user password information, selecting the RSA algorithm for sensitive data that requires two-way encryption, and equipping a database auditing system to monitor and record all database operations in real time. S155: Configure regular vulnerability scanning and incident response, including regular system vulnerability scanning and timely handling of security hotspots and vulnerabilities; S156: Establish a strict safety management system, including safety policies and standards, safety training and awareness enhancement, and safety audits and assessments.
[0127] The technical solutions involved in the above process steps are analyzed in detail as follows: 1. System Deployment Environment This system is deployed in an isolated private cloud environment, with all external services forwarded through a unified security gateway. This deployment method ensures that the internal network is not affected by direct access from the external Internet, thereby improving the overall security of the system.
[0128] 2. First layer of security protection: Gateway-level security control 2.1 Flow Control and Load Balancing To handle high concurrency requests and ensure service stability, we designed a gateway-based traffic control system. This system can monitor and adjust incoming request traffic in real time, implementing rate limiting measures according to preset policies to prevent service unavailability due to overload. Simultaneously, the gateway incorporates an intelligent load balancing algorithm that dynamically distributes requests to multiple backend instances, achieving efficient resource utilization and failover.
[0129] 2.2 Access Log Recording The gateway is responsible for collecting and storing detailed log information for every external access, including but not limited to source IP address, request time, request method, and URL path. These logs not only help in auditing and tracking potential security incidents, but also serve as foundational data for subsequent analysis and optimization.
[0130] 2.3 Malicious Access Protection To prevent malicious attacks, the gateway integrates an automated threat detection mechanism. Upon detecting abnormal behavior patterns (such as frequent failed login attempts or a large number of invalid requests), the gateway immediately adds the relevant IP addresses to a blacklist, preventing them from accessing the system. Furthermore, the gateway supports custom rule configuration, allowing administrators to set more granular access control policies based on specific business needs.
[0131] 2.4 WAF Firewall Protection All external access requests must first be filtered through a Web Application Firewall (WAF). WAF can identify and block various common web attacks, such as SQL injection, cross-site scripting (XSS), and file inclusion vulnerabilities. It not only provides protection against known attack patterns but also detects new or unknown threats through machine learning and behavioral analysis. Deploying a WAF builds the first robust line of defense for the system, ensuring that only legitimate requests reach the backend services. WAF also features real-time alerts, immediately notifying the security team when a serious threat is detected for rapid response.
[0132] 3. Second layer of security protection: Application-level security enhancement 3.1 SSL / TLS Encrypted Communication The platform fully utilizes the SSL / TLS protocol, and all external interfaces and services must communicate via HTTPS. This not only ensures the confidentiality and integrity of data transmission but also effectively prevents man-in-the-middle attacks. For certificate management, we employ automated tools to regularly update and verify SSL certificates, ensuring the use of the latest encryption standards at all times.
[0133] 3.2 User Activity Log The system keeps detailed logs of user login and logout operations. Each log entry includes the operation timestamp, user ID, device information, and other details. These logs can be used for subsequent security audits and troubleshooting, while also providing users with a transparent view of their operation history.
[0134] 3.3 Password Policy Configuration To enhance account security, the system has implemented a strict password policy. This includes: Password Expiration: Forces users to change their passwords within a certain period to avoid the risks associated with passwords remaining unchanged for a long time.
[0135] Complexity requirements: Passwords must contain uppercase and lowercase letters, numbers, and special characters, and must be at least 8 characters long to increase the difficulty of cracking them.
[0136] 3.4 Encrypted Data Transmission For communications involving sensitive information, we have implemented additional encryption measures. Important data is encrypted before transmission, making it difficult to decipher even if intercepted within the network. This further enhances data security, especially in data exchange scenarios across network boundaries.
[0137] 4. Security of sensitive data storage 4.1Bcrypt password encryption For critical information such as user passwords, we chose the Bcrypt algorithm for one-way hash encryption. Bcrypt is a strong hash function specifically designed for password protection and has the following characteristics: Resistance to brute-force attacks: Because Bcrypt takes a long time to compute (about 0.3 seconds), brute-force attacks are extremely costly, greatly reducing the risk of passwords being cracked.
[0138] Salting mechanism: A randomly generated salt value is added to each password before hashing. Even if two users have the same password, their hash results will be completely different, increasing the difficulty of cracking.
[0139] 4.2 RSA Asymmetric Encryption For sensitive data requiring two-way encryption (such as personal identification information and payment details), we adopted the RSA algorithm. RSA is an asymmetric encryption technology that uses a pair of public and private keys to achieve secure data transmission and storage. Specifically, the sender uses the receiver's public key to encrypt the data, and only the party holding the corresponding private key can decrypt and recover the original data. This mechanism not only ensures data confidentiality but also provides authentication functionality.
[0140] 4.3 A complete database auditing system The system is equipped with a comprehensive database auditing system capable of monitoring and recording all database operations in real time, including queries, inserts, updates, and deletions. The audit logs detail the operation's time, executor, SQL statement, and the number of rows affected. These logs allow tracing the source of any data changes, helping to identify potential security vulnerabilities and violations. Furthermore, the auditing system supports custom alert rules, triggering immediate notifications when suspicious activity is detected, facilitating timely action.
[0141] 5. Regular vulnerability scanning and incident response 5.1 Regular system vulnerability scanning To ensure the continued security of the system, we have established a regular vulnerability scanning mechanism. Using professional vulnerability scanning tools, the system undergoes a comprehensive security check at least once a week, covering multiple levels including the operating system, applications, and network configuration. Each scan generates a detailed report listing all discovered vulnerabilities and their risk levels. Based on the report, the security team prioritizes fixing high-risk vulnerabilities and tracks the remediation of low-risk vulnerabilities to ensure all issues are properly resolved.
[0142] 5.2 Address security hotspots and vulnerabilities promptly In response to the constant emergence of new threats and security hotspots, we have established a rapid response mechanism. Our security team closely monitors domestic and international security information, promptly obtaining the latest vulnerability announcements and attack methods. Once a security vulnerability that may affect the system is discovered, we immediately assess its scope and initiate the emergency response process. Through measures such as emergency patch releases and configuration adjustments, we quickly eliminate security risks and ensure the stable operation of the system. Furthermore, we actively participate in open-source communities and technical forums, exchanging experiences with other security experts to jointly improve the system's security level.
[0143] 6. Establish strict safety management systems 6.1 Safety Policies and Regulations The company has established a strict security management system, clearly defining the security responsibilities and codes of conduct for personnel at all levels. The system covers multiple aspects, including account management, access control, data protection, and physical security, ensuring that all employees understand and comply with security regulations. For example, employees must use strong passwords and change them regularly; access to sensitive data requires strict approval; and unauthorized external devices are prohibited from accessing the office area.
[0144] 6.2 Safety Training and Awareness Enhancement To enhance the security awareness of all employees, we regularly organize security training courses covering topics such as basic cybersecurity knowledge, prevention of common attack methods, and emergency response procedures. Through these trainings, employees gain a better understanding of the importance of security, acquire necessary protective skills, and reduce security incidents caused by human error. In addition, we continuously disseminate security knowledge and foster a positive security culture through internal communication platforms, promotional posters, and other means.
[0145] 6.3 Safety Audit and Assessment The company has established a dedicated security audit department responsible for regularly checking the implementation of various security measures. Audit content includes, but is not limited to, the execution of security policies, the progress of vulnerability remediation, and the completeness of log records. For departments and individuals that fail to meet standards, the company will take corresponding corrective measures and incorporate them into the performance evaluation system. Through rigorous audits and evaluations, the company aims to drive continuous improvement in security management across all departments, creating a virtuous cycle.
[0146] Implement strict data encryption, access control, and auditing policies to ensure the security and privacy of medical data, while complying with relevant laws and regulations such as HIPAA and GDPR.
[0147] The entire technical architecture emphasizes modularity and loose coupling, supporting horizontal scaling and elasticity to cope with ever-increasing data volumes and user demands. Simultaneously, it achieves seamless integration with external systems through an API gateway, promoting collaboration and information sharing across organizations. For example... Figure 2 The diagram shown is a technical architecture diagram of the industrial internet building space management platform built based on the above process.
[0148] Hospitals, as complex public buildings, face numerous challenges in managing their architectural spaces. Data based on these spaces has been largely overlooked and underutilized, its value yet to be fully explored. This includes data such as the location of medical equipment, room usage information, and environmental monitoring.
[0149] Based on these management pain points, the system's objectives were clearly defined, including establishing unified standard master data for building spaces, enabling rapid location reporting, inventory checks, and location updates by scanning building space markers. These were the starting points for the platform design. Subsequently, the system's functional modules and technical architecture were planned to ensure that each part met the requirements of high performance, security, and scalability.
[0150] During the system design and development phase, we developed industrial internet identifier resolution, QR code identifier design, and identifier-based applications one by one, and conducted rigorous testing to ensure that the functions were complete and the operation was worry-free.
[0151] With the system environment set up, it is necessary to ensure sufficient cloud service resources to support the stable operation of the system. At the same time, data security should be protected through firewall settings, data encryption, and user access control.
[0152] After the platform officially went live, the daily operations and maintenance team was responsible for system monitoring, troubleshooting, and performance optimization. A user feedback mechanism was established to regularly collect opinions as a basis for system improvement. Based on user feedback and system performance, we continuously optimized the features to ensure the platform always remained in optimal condition.
[0153] By following this detailed implementation path, we can systematically advance the construction of the building space identification creation application based on the Industrial Internet, ensuring its smooth launch and continuous operation. This will greatly promote the intelligent management of hospitals and significantly improve patient safety and the quality of medical services. The application scenarios in this embodiment include establishing building space master data, assigning Industrial Internet identification codes, and initiating applications based on the identifications. Steps S200-S400 below will elaborate on the actual application scenarios. However, it should be noted that this invention is applicable to any Industrial Internet of Things scenario; the application scenario used in a hospital is merely a specific example.
[0154] S200: Based on the industrial internet building space management platform, establish building space master data, which is used to maintain basic information of various locations in the building.
[0155] Campuses are created within the industrial internet building space management platform, which supports the management of multiple campuses. For example... Figure 3 The diagram shown illustrates the management of the hospital campus.
[0156] After the campus is created, maintain the buildings within the campus, and then maintain the floors and rooms on each floor in sequence. For example... Figure 4The above is a schematic diagram of adding a new management area. After the area is established, clicking "Enter Management" will redirect you to a new page where you can maintain the buildings in the area and sequentially maintain the floors and rooms on each floor.
[0157] S300: Batch generate industrial internet identifiers set at various locations in the building, and after fixing the industrial internet identifiers at various locations, start the industrial internet identifiers to complete the binding with the building space master data.
[0158] The industrial internet identifiers are generated in batches as needed. The industrial internet identifiers are attribute-free spatial codes. After fixing the industrial internet identifiers in various locations, the industrial internet identifiers are scanned and the binding with the building space master data is completed according to the page prompts.
[0159] A specific example is as follows: Before assigning industrial internet identifiers, we will generate industrial internet identifiers in batches as needed, namely "spatial codes," which are attribute-free QR codes whose appearance can be designed according to the hospital's requirements. For example... Figure 5 As shown.
[0160] Next, we will produce the generated spatial code image using a material that is aesthetically pleasing, lightweight, firmly adheres, is wear-resistant, corrosion-resistant, and easy to scan. Once production is complete, we will begin the coding process.
[0161] Step 1: Affix attribute-free space codes to commonly used locations within the building space, such as nurse stations, clinic entrances, payment windows, and parking lot pillars. For example... Figure 6 A diagram showing how to paste the space code.
[0162] Step 2: Open the WeChat app on your phone, tap "Scan," and then point the scan barcode at the pasted QR code. Once successfully recognized, you will be automatically taken to the QR code activation page. For example... Figure 7 The image shows a diagram illustrating how to activate the space code by scanning a QR code.
[0163] Step 3: Following the on-screen instructions, select the location where you will paste the space code (the master data of the building space under the organization). For example... Figure 8 The diagram shown illustrates the binding of master data in the space.
[0164] Step 4: Click "Complete" to complete the deployment of the spatial code and successfully assign the industrial internet identifier. The page will automatically redirect to the application page for that spatial code. Figure 9 The diagram shown illustrates the completion of spatial code deployment.
[0165] S400: Based on the industrial internet identifier that has been bound to the building space master data, initiate various application scenarios at various locations in the building, wherein the application scenarios are applications preset in the industrial internet building space management platform that correspond to the current building space master data in the building.
[0166] After the industrial internet identification code is assigned, the spatial code can serve as a unique identifier for the bound building space, expanding into more application scenarios. Different application scenarios can be used to grant permissions to users. Users can initiate various applications by scanning the spatial code. For example... Figure 10 The image shows a schematic diagram of spatial code application.
[0167] Below, we will introduce several common application scenarios: (1) Fault reporting like Figure 11 The diagram illustrates the fault reporting process. Users can initiate a fault report by scanning the space code. The reporter's name and contact number are automatically populated based on the user's registration information. The building space information bound to the space code, serving as the reported location, is also automatically displayed. The department using this location is automatically displayed as the reporting department. Users only need to fill in the faulty equipment information and the details of the fault to complete the fault report. Standardized location information helps maintenance engineers clearly identify the location of the fault, allowing for faster arrival and repair.
[0168] (2) Inspection of equipment and facilities like Figure 12 The diagram shows a view of the equipment and facilities. On the homepage of the space code, the number of devices in the room and their usage status are clearly displayed. Clicking on the statistics will take you to the equipment list page to view detailed equipment information. Based on this application scenario, combined with IoT positioning tags, the location of equipment and facilities can be dynamically updated in real time, facilitating quick device location for managers and enabling emergency equipment deployment.
[0169] (3) Use of information maintenance like Figure 13 The image shown is a diagram illustrating how to view room information. Figure 14 The image shows a diagram illustrating room information editing. Clicking "Details" on the space code homepage will take you to the room details page. Here you can view basic room information, environmental requirements, and images. Clicking the edit button allows you to maintain relevant information on the information editing page, enabling real-time updates of room information. When there are departmental changes or mergers within the hospital, space usage information can be quickly modified remotely, allowing clinical staff to quickly familiarize themselves with the changes.
[0170] (4) Environmental information early warning like Figure 14 The diagram shown illustrates the room environment maintenance requirements. Figure 15The diagram shown is a schematic diagram of the department's environmental monitoring. Figure 16 This is a diagram illustrating abnormal event monitoring, such as... Figure 17 This is a diagram illustrating temperature, humidity, and pressure monitoring in a room list. The room's environmental requirements can be maintained in the "Details" section of the spatial code. IoT-based intelligent environmental monitoring devices monitor room temperature, humidity, and pressure, comparing these readings with the required environmental standards to generate alerts for abnormalities. Users can view the room monitoring status, abnormal event alert records, and real-time temperature, humidity, and pressure data for their department on a PC. This application is suitable for laboratories, ICUs, cold storage rooms, and other locations with high environmental requirements. Managers can access real-time room data anytime, anywhere, and react quickly to abnormal temperature, humidity, and pressure conditions.
[0171] This embodiment takes the medical industry as an application scenario, integrates industrial internet identifier resolution with unique building space identifiers, and constructs a set of innovative building space identifier applications based on industrial internet through the construction of a building space master data system. Using the building space industrial internet identifier as the entry point, it links more industrial internet scenario applications and lays the foundation for cross-departmental data sharing and integration between hospital information systems.
[0172] Taking a top-tier hospital as an example, the hospital collected over 5200 building space data entries, achieving a coverage rate of 98.5%. In the case of repair management, over 150 room codes were implemented in areas with previously high repair volume. Within three months, over 400 repair work orders were initiated via these room codes, allowing for real-time tracking of each work order's progress without the need for phone calls. This effectively saved clinical repair staff and the customer service center approximately 8000 minutes of communication time. Repair work order data records are complete and accurate, and the quality of data reports has significantly improved. Overall, repair management efficiency has increased by over 15% annually.
[0173] A standardized naming system facilitates integration with hospital information systems, ensuring data accuracy and consistency, and enabling cross-departmental collaboration and information exchange. For managers, establishing a unified and standardized building space ledger helps them better understand whether building space is being used scientifically and rationally, maximizing the utilization of existing building space resources. For medical staff, unified naming rules help improve workflow efficiency, reduce delays caused by poor communication, ensure the effective allocation and use of medical resources, and allow for quick access to the associated industrial internet identifier by scanning the QR code, initiating repair requests, performing inspections, reporting adverse events, viewing room equipment assets, maintaining room usage information, and performing equipment and facility inventory checks. For patients, scanning the QR code provides information on building space usage and environmental details.
[0174] The hospital not only solved the traditional challenges of space and asset management, but also created a more intelligent, efficient, and safe medical environment. This innovative practice not only improved patient satisfaction but also laid a solid foundation for the hospital's sustainable development.
[0175] This case study enables hospitals to achieve efficient management of their building spaces, significantly improving the ease of use and management efficiency of location-based hospital operations management applications. It lays the foundation for cross-system data governance and interoperability within the hospital, ultimately enhancing patient safety and the quality of medical services. The project is easy to implement, cost-effective, and, based on the commonalities of building space management, has strong potential for cross-industry replication.
[0176] With continuous technological advancements, future hospitals will become more intelligent, providing higher-quality services to patients and medical staff. As industrial internet technology continues to advance, the Smart Code Space Management System will integrate more AI and big data analytics capabilities, further optimizing space management and creating a smarter, safer, and more human-centered building environment. Through the Zhishu Smart Space Management System, the application of QR codes for building space identification not only revolutionizes traditional building management models but also provides users with a more intelligent, efficient, and secure building environment, demonstrating the enormous potential of the industrial internet in the modern construction field.
[0177] Second Embodiment like Figure 19 As shown, this embodiment provides an industrial internet building space identifier architecture design system for executing the industrial internet building space identifier architecture design method as described in the first embodiment, comprising: The management platform architecture building module 100 is used to build an industrial internet building space management platform architecture that includes a front-end presentation layer, a business logic layer, an IoT and device access layer, a data storage and management layer, and a security and compliance layer. Building space master data establishment module 200 is used to establish building space master data based on the industrial internet building space management platform. The building space master data is used to maintain basic information of each location in the building. The Industrial Internet Identifier Generation Module 300 is used to generate Industrial Internet Identifiers in batches and set in various locations in a building. After fixing the Industrial Internet Identifiers in various locations, it activates the Industrial Internet Identifiers to complete the binding with the building space master data. The application scenario initiation module 400 is used to initiate various application scenarios at various locations in the building based on the industrial internet identifier that has been bound to the building space master data. The application scenarios are applications that are preset in the industrial internet building space management platform and correspond to the current building space master data in the building.
[0178] A computer-readable storage medium stores computer code that, when executed, performs the methods described above. Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. This program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0179] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of the present invention should also be considered within the scope of protection of the present invention.
[0180] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0181] It should be noted that the above embodiments can be freely combined as needed. The above description is only a preferred embodiment of the present invention. It should be pointed out that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.
Claims
1. An architectural design method for industrial internet building space identification, characterized in that, Includes the following steps: S100: Construct an industrial internet building space management platform architecture that includes a front-end presentation layer, business logic layer, IoT and device access layer, data storage and management layer, and security and compliance layer; S200: Establish building space master data based on the industrial internet building space management platform. The building space master data is used to maintain basic information about each location in the building. S300: Batch generate industrial internet identifiers set at various locations in the building, and after fixing the industrial internet identifiers at various locations, start the industrial internet identifiers to complete the binding with the building space master data; S400: Based on the industrial internet identifier that has been bound to the building space master data, initiate various application scenarios at various locations in the building, wherein the application scenarios are applications preset in the industrial internet building space management platform that correspond to the current building space master data in the building.
2. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S100, the front-end presentation layer in the industrial internet building space management platform architecture specifically includes: S111: Construct the basic framework of the front-end presentation layer under the architecture of the industrial internet building space management platform, including introducing the React JavaScript library developed based on Facebook to build the basic structure of the front-end presentation layer, introducing Redux as a global state management tool, using the React Router library to render different components according to URL changes, realizing the single-page application (SPA) function, configuring nested routes and dynamic route matching functions, and introducing Axios as an HTTP client for front-end and back-end data interaction. S112: Construct the front-end display by combining the master data of the building space and the requirements of the application scenario to be preset, including designing the page structure and style based on HTML5 and CSS3, selecting Element UI as the UI framework, integrating it with React through the adaptation layer, and splitting the UI into multiple independent widgets according to the React component design concept. S113: To achieve front-end interaction in conjunction with the industrial internet identification coding, the data flow in the application is designed according to the request-response pattern. When the operation is related to industrial internet identification coding, the front-end triggers the corresponding operation and sends an HTTP request to the back-end microservice. The back-end processes and returns the result. The front-end updates the UI according to the response. To address the complexity of asynchronous operations during the coding process, the Redux Thunk middleware is used to write an action creator that can return a function. This function receives the store's dispatch method, allowing multiple actions to be dispatched on demand or actions to be dispatched after the asynchronous operation is completed, ensuring the correct processing of the data flow. S114: Supports the construction of front-end functions initiated by the application scenario, including: enabling communication between the front-end and the back-end using a Spring Cloud microservice architecture via RESTful API; setting Spring Cloud Gateway as a unified API entry point for request routing, rate limiting, authentication, configuring Cross-Origin Resource Sharing (CORS) policies to ensure the front-end can securely call the back-end API; configuring different API base addresses for different environments to achieve environment isolation; defining standardized error codes and message formats to facilitate joint handling of exceptions by the front-end and back-end; and configuring interaction with the back-end service architecture, including lazy loading using React.lazy and Suspense for components related to the application scenario that are not displayed on the first screen to reduce initial loading time; code splitting using Webpack's Code Splitting function to load only the currently needed parts; setting HTTP cache headers appropriately to reduce duplicate requests using browser caching; optimizing images, compressing file sizes, using modern image formats, generating thumbnails when necessary, and using CDN to accelerate static resource loading. It also includes performance optimization settings such as using HTTPS encrypted transmission, CSRF protection, and XSS defense measures to ensure user data security; strictly validating and filtering user input to prevent malicious script injection attacks; and using Element... When designing the UI, pay attention to security-related attributes and methods, and implement security protection strategies to avoid introducing new security risks.
3. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S1, the business logic layer in the industrial internet building space management platform architecture specifically includes: S121: Construct the architecture of the industrial internet building space management platform, including clarifying the position and role of the business logic layer in the entire industrial internet building space management platform architecture, establishing a collaborative relationship with the front-end presentation layer, the data storage and management layer, and the security and compliance layer, and providing a basic framework for the implementation of subsequent specific business logic; S122: Establish the building space master data, including activating the building space master data management function module in the business logic layer, collecting basic information of each location in the building, entering the collected basic information into the industrial internet building space management platform, and storing the organized building space master data in the data storage and management layer. S123: Implement industrial internet identification-related operations, including batch generating industrial internet identifications for various locations in a building, fixing the generated industrial internet identifications at the corresponding locations in the building, triggering the binding process between the industrial internet identifications and the building space master data, and associating the identification information with the corresponding master data in the business logic layer so that each identification can accurately point to the corresponding building space location and its basic information. S124: Conducting business based on bound identifiers, including when it is necessary to obtain detailed building space information, the business logic layer calls the Industrial Internet Identifier Resolution Service, connects to the Industrial Internet Identifier Resolution System, and through interaction with the Industrial Internet Identifier Resolution System, quickly resolves the building space identifier, extracts the detailed building space information corresponding to the identifier, and provides the resolved detailed building space information to other business modules, providing data support for various application scenarios initiated based on the bound identifiers, so that various applications preset in the Industrial Internet Building Space Management Platform can run accurately and effectively in the corresponding building space locations.
4. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S1, the IoT and device access layer in the industrial internet building space management platform architecture specifically refers to: S131: Select and deploy IoT devices, including temperature monitoring devices, humidity monitoring devices, and IoT gateway devices; S132: Dynamic environment identifiers for different IoT devices integrate multiple networking and communication technologies, including 5G, Cat1, NB-IoT, LoRaWAN, Wi-Fi, and BLE, based on different application scenarios and data transmission requirements; S133: Sampling is performed based on the default sampling frequency of the IoT device, and the processed collected data is sent to the gateway device through a wireless communication protocol; S134: Based on the usage requirements and environmental standards of the building space, set abnormal thresholds for environmental parameters, including temperature and humidity, on a remote server or a gateway device with intelligent processing capabilities, and perform abnormal detection and alarm triggering based on the abnormal thresholds, wherein the alarm triggering adopts methods including real-time push, notification mechanism, and automatic response. S135: Utilize BIM technology to construct a three-dimensional digital twin model of the building space, accurately presenting the building structure and equipment layout, and implement the application scenarios including energy management, fault early warning, and user experience.
5. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S1, the data storage and management layer in the industrial internet building space management platform architecture specifically includes: S141: Design and implement a data storage strategy that includes IoT data storage, structured data storage, unstructured and semi-structured data storage. The IoT data storage is for the large amount of time-series data generated by IoT devices, and a high-performance TDengine database designed specifically for time-series data is selected for storage. The structured data storage is for relational structured data, and a PostgreSQL database is selected for storage. The unstructured and semi-structured data storage introduces HDFS from the Hadoop ecosystem to handle the storage and analysis of large-scale unstructured or semi-structured data. S142: Data query and report statistics are implemented by using Flink CDC combined with Flink real-time computing engine.
6. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S1, the security and compliance layer in the industrial internet building space management platform architecture specifically includes: S151: Deploy the system in an isolated private cloud environment, with all external services forwarded through a unified security gateway; S152: Set up the first layer of security protection barrier as the gateway-level security control, including traffic control and load balancing, access logging, malicious access protection, and WAF firewall protection; S153: Set up a second layer of security protection as an application-level security enhancement, including SSL / TLS encrypted communication, user activity logs, password policy configuration, and encrypted data transmission; S154: Set up a security policy for sensitive data storage, including selecting the Bcrypt algorithm for one-way hash encryption of critical user password information, selecting the RSA algorithm for sensitive data that requires two-way encryption, and equipping a database auditing system to monitor and record all database operations in real time. S155: Configure regular vulnerability scanning and incident response, including regular system vulnerability scanning and timely handling of security hotspots and vulnerabilities; S156: Establish a strict safety management system, including safety policies and standards, safety training and awareness enhancement, and safety audits and assessments.
7. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S200, building space master data is established based on the industrial internet building space management platform. This building space master data is used to maintain basic information about various locations within the building, specifically: A campus is created in the industrial internet building space management platform, which supports the management of multiple campuses. After the campus is created, maintain the buildings in the campus, and maintain the floors and rooms on each floor in turn.
8. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S300, industrial internet identifiers are generated in batches and set at various locations within the building. After fixing the industrial internet identifiers at each location, the industrial internet identifiers are activated to complete the binding with the building space master data. Specifically: The industrial internet identifiers are generated in batches as needed. The industrial internet identifiers are attribute-free spatial codes. After fixing the industrial internet identifiers in various locations, the industrial internet identifiers are scanned and the binding with the building space master data is completed according to the page prompts.
9. The architectural design method for industrial internet building space identification according to claim 1, characterized in that, In step S400, various application scenarios are initiated at different locations within the building based on the industrial internet identifier already bound to the building space master data. These application scenarios are pre-defined in the industrial internet building space management platform and correspond to the locations within the current building space master data. Specifically: Scanning the corresponding industrial internet identifier initiates various application scenarios at different locations within the building; The application scenarios include those related to reporting repairs, inspecting equipment and facilities, maintaining usage information, and environmental monitoring and early warning.
10. An architecture design system for industrial internet building spatial identifiers for executing the architecture design method for industrial internet building spatial identifiers as described in any one of claims 1-9, characterized in that, include: The management platform architecture building module is used to construct an industrial internet building space management platform architecture that includes a front-end presentation layer, a business logic layer, an IoT and device access layer, a data storage and management layer, and a security and compliance layer. The building space master data establishment module is used to establish building space master data based on the industrial internet building space management platform. The building space master data is used to maintain basic information of various locations in the building. The Industrial Internet Identifier Generation Module is used to generate Industrial Internet Identifiers in batches and set in various locations in a building. After fixing the Industrial Internet Identifiers in various locations, it activates the Industrial Internet Identifiers to complete the binding with the building space master data. The application scenario initiation module is used to initiate various application scenarios at various locations in the building based on the industrial internet identifier that has been bound to the building space master data. The application scenarios are applications that are preset in the industrial internet building space management platform and correspond to the current building space master data in the building.