Same house type smart home system batch configuration method, system, device and medium

Abstract

The application discloses a same-house-type smart home system batch configuration method, system, device and medium, and the method comprises the following steps: establishing a benchmark house type configuration template, including logical slots, logical identifiers and space attributes and business attributes formed by abstracting physical devices in the benchmark house type; creating a home instance for a target family, generating a home project template based on the benchmark template, and establishing a dynamic deployment state machine; scanning a unique serial number of a physical device, positioning the target family based on the home instance, filling the serial number into the corresponding logical slots of the template, and establishing a pre-binding relationship; a smart home gateway obtains a device whitelist based on the pre-binding relationship, performs exclusive network access, and only allows devices in the whitelist to access the network; after the device accesses the network, configuration parameters of the home project template are injected into the corresponding physical device according to the pre-binding relationship; and the delivery is completed after the state machine state bit is checked and the injection state is checked. The application can realize rapid batch configuration of the same-house-type smart home system.

Description

Technical Field

[0001] This invention relates to the field of smart home technology, specifically to a method, system, device, and medium for batch configuration of smart home systems for the same apartment type. Background Technology

[0002] In B2B customer application scenarios, especially in real estate projects, it is often necessary to deploy and deliver smart home systems in batches across multiple residential units with the same or similar floor plans within the same project. Current technologies typically deliver smart home systems in the following way: engineers install devices individually for each household, connect each device to the network, configure the region and name, and then edit and debug the device's region, name, and corresponding scene mode on the application side. This approach has at least the following problems: high repetitiveness in the configuration process, requiring repeated operations for the same floor plan; low on-site debugging efficiency, as devices need to be connected to the network and manually configured, resulting in a long construction cycle; high labor costs, complex operations for engineers, and a high risk of errors; and poor consistency, with inconsistencies in device names, regions, and scene configurations easily occurring between different residences.

[0003] Therefore, there is an urgent need in this field for a smart home system configuration solution that can be applied to B-end scenarios such as real estate, so as to achieve rapid batch configuration and efficient delivery of residential units of the same type. Summary of the Invention

[0004] To address the problems of low configuration efficiency, high labor costs, and poor consistency in the batch configuration of smart home systems with the same floor plan in existing technologies, this invention provides a method, system, device, and medium for batch configuration of smart home systems with the same floor plan, thereby resolving the aforementioned technical deficiencies.

[0005] This invention proposes a method for batch configuration of smart home systems for the same apartment layout, comprising the following steps: S1. Establish a baseline apartment configuration template. The baseline apartment configuration template includes logical slots formed by abstracting the physical equipment in the baseline apartment that has been configured, logical identifiers corresponding to each logical slot, and spatial and business attributes corresponding to each logical slot. S2. Create a family instance for the target family, and clone the family project template for the target family based on the baseline house type configuration template, while establishing a dynamic deployment state machine for the target family. S3. By scanning the unique serial number of the physical device, the target family for the current construction is determined based on the family instance. The obtained unique serial number is filled into the corresponding logical slot in the family project template corresponding to the target family, and a pre-binding relationship is established between the unique serial number of the physical device and the logical identifier of the logical slot. S4. The smart home gateway obtains a device whitelist based on pre-binding relationships and executes an exclusive network access policy according to the device whitelist, allowing only physical devices with unique serial numbers in the device whitelist to access the network. S5. After the physical device is connected to the network, the configuration parameters in the home project template are injected into the corresponding physical device according to the pre-binding relationship. S6. Verify the network access status and configuration parameter injection status of the device based on the status bits of the dynamically deployed state machine. After the verification is successful, the construction and delivery are completed.

[0006] Preferably, in step S1, a baseline apartment layout template is established, including the following sub-steps: S11. Select a baseline apartment type where equipment installation and configuration have been completed; S12. Extract equipment information, scenario mode information, and area information within the baseline unit type through the interface; S13. Solidify the extracted equipment information, scenario mode information and regional information into a benchmark unit configuration template, and bind the benchmark unit configuration template with the unit identifier.

[0007] Preferably, in step S2, establishing a dynamic deployment state machine for the target family includes the following sub-steps: S21. Set multiple status bits for the dynamic deployment state machine. The status bits include not started, waiting to scan code for pre-binding, gateway configuration in progress, sub-device automatic network access in progress, configuration logic import in progress, verification error, and construction completed. S22. Monitor the current status position and control the construction process to jump to the next status position only after the step corresponding to the previous status position has been verified.

[0008] Preferably, in step S3, establishing a pre-binding relationship between the unique serial number of the physical device and the logical identifier of the logical slot includes the following sub-steps: S31. Scan the physical identifier on the physical device using the mobile client to obtain the unique serial number of the physical device; S32. Based on the family instance, determine the target family for the current construction, locate the corresponding family project template, and fill the obtained unique serial number into the corresponding logical slot in the family project template. S33. Based on the input results, the cloud server establishes and stores the pre-binding relationship between the unique serial number and the logical identifier of the logical slot.

[0009] Preferably, in step S4, the smart home gateway obtains a device whitelist based on pre-binding relationships, including the following sub-steps: S41. The cloud server generates a device whitelist containing unique serial numbers based on the pre-binding relationship; S42, The cloud server sends the device whitelist to the smart home gateway; The exclusive network access policy includes: when verifying the network access request of a physical device, the smart home gateway only allows physical devices whose unique serial numbers match the serial numbers in the device whitelist to access the network.

[0010] Preferably, in step S5, the configuration parameters in the home project template are injected into the corresponding physical device, including the following sub-steps: S51. Establish a mapping table between the logical identifier of the benchmark apartment configuration template and the unique serial number of the physical equipment of the target family; S52. Based on the mapping table, replace the scenario logic and spatial topology relationship in the baseline apartment configuration template with the physical control commands of the target family. S53. Identify the hardware characteristics of the physical device through the device adapter and inject the functional cluster attributes in the baseline unit configuration template into the target physical device.

[0011] Preferably, in step S6, the verification is performed based on the state bits of the dynamically deployed state machine, including the following sub-steps: S61. Before injecting configuration parameters, poll the online status of all physical devices with established pre-binding relationships to obtain the online status polling results. If there are offline devices, interrupt the process. S62. During the configuration parameter injection process, after each level of configuration parameter injection, receive the asynchronous execution receipt returned by the gateway to confirm that the underlying attribute has been successfully written. S63. Update the status bits of the dynamically deployed state machine based on the online status polling results and the receipt of asynchronous execution receipts.

[0012] This invention also proposes a batch configuration system for smart home systems of the same type, used to implement any of the above methods, the system comprising: The mobile client is configured to scan the unique serial number of the physical device and send the obtained unique serial number to the cloud server. The cloud server is configured to store the baseline apartment configuration template, create a family instance for the target family and clone the family project template based on the baseline apartment configuration template, establish a dynamic deployment state machine for the target family, establish a pre-binding relationship between the unique serial number sent by the mobile client and the logical identifier of the logical slot, and generate a device whitelist based on the pre-binding relationship. The smart home gateway is configured to obtain a device whitelist from the cloud server, execute an exclusive network access policy based on the device whitelist, and only allow physical devices with unique serial numbers in the device whitelist to enter the network. After the physical device enters the network, the configuration parameters in the home project template are injected into the corresponding physical device according to the pre-binding relationship. Multiple physical devices, each with a physical identifier containing a unique serial number on its surface, are configured to establish a communication connection with the smart home gateway and receive configuration parameters.

[0013] The present invention also proposes a terminal device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to implement the steps of the batch configuration method for a smart home system of the same type as described above.

[0014] The present invention also proposes a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the batch configuration method for a smart home system of the same type as described above.

[0015] Compared with the prior art, the beneficial effects of the present invention are as follows: (1) By establishing a benchmark household configuration template, the physical equipment of the benchmark household is abstracted into logical slots to achieve the standardization of configuration information; a household project template is generated for the target household to clone, so that different households of the same type do not need to repeat the equipment configuration, which significantly reduces repetitive operations.

[0016] (2) By scanning the unique serial number of the physical device and filling it into the logical slot, a pre-binding relationship is established. Combined with the device whitelist generated by the cloud server, the smart home gateway executes an exclusive network access policy to realize the automatic network access of the device. By establishing a mapping table and device adapter, the configuration parameter injection and hardware difference alignment are automatically completed, which greatly reduces the workload of manual debugging.

[0017] (3) By using the cloning mechanism of the baseline apartment configuration template, the configuration information such as equipment name, area division, and scenario mode of different families under the same apartment type is completely consistent; by using the dynamic deployment state machine status bit monitoring and verification mechanism, online status polling is performed before the configuration parameters are injected, and asynchronous execution receipts are received during the injection process, which effectively avoids human configuration errors.

[0018] (4) By combining template cloning, automatic network access, automatic configuration injection and automatic verification, construction of multiple households can be carried out in parallel, which significantly improves construction efficiency, shortens the overall project delivery cycle and reduces engineering labor costs.

[0019] (5) This invention is particularly suitable for large-scale smart home delivery scenarios of B-end projects such as real estate, and can effectively cope with the complex environment of multiple house types and multiple construction sites being constructed simultaneously. Attached Figure Description

[0020] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments, taken with reference to the accompanying drawings: Figure 1 This is a flowchart of the batch configuration method for a smart home system of the same type of house according to the present invention; Figure 2 This is a flowchart illustrating the engineering implementation process of batch configuration of the smart home system for the same apartment type according to the present invention. Figure 3 This is a unified Wi-Fi network configuration flowchart; Figure 4 This is a flowchart illustrating the verification types of SN codes between template devices and real devices; Figure 5 This is a system architecture diagram for batch configuration of the smart home system for the same apartment type according to the present invention; Figure 6 This is a schematic diagram of the structure of a computer system suitable for implementing the embodiments of the present invention. Detailed Implementation

[0021] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. The specific embodiments described herein are merely illustrative of the invention and not intended to limit it. It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the drawings. Unless otherwise specified, the embodiments and features described herein can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0022] This invention provides a method for batch configuration of smart home systems for apartments with the same floor plan. This method can be applied to the batch delivery of smart home systems for apartments with the same floor plan in real estate projects. Figure 1 As shown, the method includes the following steps S1 to S6. Figure 2 The engineering implementation process of this method is shown. Figure 3 The process of unified Wi-Fi network configuration is shown. Figure 4 The process for verifying the serial number (SN) of the template device and the real device is shown.

[0023] S1. Establish a baseline apartment configuration template. The baseline apartment configuration template includes logical slots formed by abstracting the physical equipment in the baseline apartment that has been configured, logical identifiers corresponding to each logical slot, and spatial and business attributes corresponding to each logical slot.

[0024] First, a unique serial number (SN) is assigned to all smart home devices before they leave the factory. This serial number is then bound to the device's hardware information, functional clusters, and communication protocols, and pre-entered into the device association database on a cloud server. The serial number is attached to the device surface in the form of a QR code or NFC tag for easy scanning later.

[0025] Then, select a baseline apartment type (e.g., a model apartment) with completed equipment installation and configuration as the source, and create a baseline apartment type configuration template according to the following sub-steps: S11. Select a baseline apartment type where equipment installation and configuration have been completed.

[0026] S12. Extract equipment information, scenario mode information, and area information within the baseline apartment type via the interface. Equipment information includes the model, function cluster, and communication protocol of each physical device; scenario mode information includes preset scenarios (such as home mode and sleep mode) and their corresponding device actions; area information includes spatial division data such as floors and rooms.

[0027] S13. Solidify the extracted equipment information, scenario mode information and regional information into a benchmark unit configuration template, and bind the benchmark unit configuration template with the unit identifier.

[0028] During the template solidification process, the system abstracts each physical device into a logical slot, and each logical slot is assigned a unique logical identifier (Template_Device_ID). The template records the spatial attributes (such as the room and floor) and business attributes (such as which scenarios it participates in, its ranking in the frequently used devices on the homepage, etc.) corresponding to each logical slot. In this way, the basic apartment configuration template contains a series of logical slots and their attributes, without directly binding to the actual serial number of any physical device, thus achieving decoupling between logic and physical.

[0029] During template generation, the system uses distributed locks to ensure template uniqueness. Before binding the apartment type identifier, the system automatically verifies whether there are already any households under that apartment type undergoing construction. If a household is detected to have entered the subsequent QR code configuration stage, the binding permission is locked, prohibiting modification or rebinding of the baseline apartment type configuration template to maintain template consistency. The generated baseline apartment type configuration template is stored on a cloud server.

[0030] S2. Create a family instance for the target family, and clone the family project template for the target family based on the baseline house type configuration template, while establishing a dynamic deployment state machine for the target family.

[0031] For each target household to be delivered (e.g., Room 102, Building 1), construction workers locate the specific physical room using a smart home app. The system automatically retrieves the building unit information and room number, synthesizes a unique household name (e.g., "Building 1, Room 102"), and creates a real household instance on the cloud server, assigning a unique household ID (homeId). This process can be referenced... Figure 5 The system architecture shown is such that the cloud server is responsible for the creation and management of home instances.

[0032] While creating a family instance, the system triggers a deep clone of the target family's family project template from the baseline apartment configuration template: it iterates through the contents of the baseline apartment configuration template, batch-injecting the preset logical slot information, scenario content, and spatial layout data into the specific family's project template library, forming a family project template belonging to that family instance. This family project template inherits all logical slots and their attributes from the baseline template, but has not yet been associated with a unique serial number for any physical device.

[0033] Simultaneously, a dynamically deployed state machine is established for the target households, executed according to the following sub-steps: S21. Set multiple status bits for the dynamic deployment state machine. The status bits include Not Started, Waiting for QR Code Scanning and Pre-binding, Gateway Configuration in Progress, Sub-device Automatic Network Access in Progress, Configuration Logic Import in Progress, Verification Error, and Construction Completed.

[0034] S22. Monitor the current state bit and control the construction process to only jump to the next state bit after the step corresponding to the previous state bit has passed the verification. For example, the state machine is only allowed to enter the gateway configuration state after the QR code pre-binding step is completed.

[0035] In addition, when creating a home instance, the name and password of the target Wi-Fi network are preset, enabling Wi-Fi-enabled physical devices to automatically join the designated Wi-Fi network after power-on. Specifically, after completing the creation of the home instance and cloning the home project template, construction personnel can perform unified Wi-Fi network configuration operations through a mobile client (APP) to pre-configure network connections for Wi-Fi-enabled physical devices. Figure 3 As shown, the process includes the following interactive steps: First, construction workers scan a QR code on the home's QR code using the app to log in to the target home. Then, they connect their phones to the target Wi-Fi network and access the app's unified Wi-Fi configuration page. On this page, they select the target Wi-Fi name and enter the password. The app then uploads the Wi-Fi information to the cloud server, which binds the Wi-Fi name and password to the target home.

[0036] Next, the app prompts the device to enter network configuration mode. After the physical device is powered on, a Wi-Fi hotspot is turned on (for example, the hotspot name is "Intre_eLink" and the password is "12345678"). The app automatically connects to the device's hotspot and requests the Wi-Fi information of the home to which the device belongs from the cloud server. The cloud server returns the pre-bound target Wi-Fi name and password, and the app disconnects the device's hotspot accordingly and reconnects to the target Wi-Fi network. After obtaining the target Wi-Fi information, the device automatically connects to the network and logs into the cloud backend, completing the Wi-Fi network configuration process.

[0037] like Figure 4 As shown, during the QR code pre-binding process in step S3, the system executes an automated verification sub-process to distinguish between template devices and real devices and ensure the validity of the binding. Specifically, this includes: After the construction workers scan the unique serial number (SN code) on the physical device through the mobile client (smart home APP), the client uploads the SN code and the target home information to the cloud server to request device verification.

[0038] The cloud server first queries the device association database of the baseline apartment configuration template for the SN code.

[0039] If found, the device is determined to be a template device used to generate the baseline apartment configuration template. The system will return a "binding prohibited" message to prevent the original device of the baseline template from being incorrectly bound to other households. If not found, proceed to the next step of real device verification.

[0040] The cloud server queries the SN code in its device association database, which stores information about all manufactured devices.

[0041] If the device is found, it is determined to be a legitimate device available for binding. The system further verifies whether the SN code already exists in the pre-binding relationship or mapping table of other households. If not bound, the SN code is allowed to be entered into the corresponding logical slot in the current target household's household project template to establish a pre-binding relationship. If already bound, a device conflict warning is returned. If not found, the SN code is deemed invalid, and an error message is returned.

[0042] Through the above verification process, the system ensures that only legitimate and unoccupied real devices can be successfully pre-bound, laying the foundation for the subsequent accurate generation of a mapping table between device serial numbers, real device IDs, and template logical IDs.

[0043] S3. By scanning the unique serial number of the physical device, the target family for the current construction is determined based on the family instance. The obtained unique serial number is filled into the corresponding logical slot in the family project template corresponding to the target family, and a pre-binding relationship is established between the unique serial number of the physical device and the logical identifier of the logical slot.

[0044] After the construction workers enter the target family's site, they establish a pre-binding relationship by following these sub-steps: S31. Scan the physical identifier (such as a QR code or NFC tag) on ​​the physical device using a mobile client (smart home APP) to obtain the unique serial number of the physical device.

[0045] S32. Based on the home instance, determine the target home for the current construction, locate the corresponding home project template, and fill the obtained unique serial number into the corresponding logical slot in the home project template. The smart home APP fills the scanned serial number into the corresponding logical slot in the template according to the preset construction sequence or UI guidance. For example, fill the serial number of the living room main light into the logical slot representing "living room main light".

[0046] S33. Based on the input results, the cloud server establishes and stores the pre-binding relationship between the unique serial number and the logical identifier of the logical slot, and generates a dynamic mapping table. This mapping table maps the unique serial number of the physical device, the real device ID assigned by the cloud after the device enters the network, and the template logical ID one by one.

[0047] During the batch scanning process, in order to avoid data chaos caused by multiple construction terminals operating the same household at the same time, the system will use a distributed lock (such as a Redis distributed lock) to lock the project ID of the current target household before the configuration import is executed, so as to ensure that the configuration process of a single household is exclusive and atomic.

[0048] S4. The smart home gateway obtains a device whitelist based on pre-binding relationships and executes an exclusive network access policy according to the device whitelist, allowing only physical devices with unique serial numbers in the device whitelist to access the network.

[0049] After completing the device-logic pre-binding, the construction personnel can start the network via the APP by following these sub-steps: S41. The cloud server generates a whitelist of devices containing unique serial numbers based on the pre-binding relationship.

[0050] S42, the cloud server distributes the device whitelist to the smart home gateway. This process can be found in [reference needed]. Figure 5 The smart home gateway communicates with the cloud server to obtain a whitelist.

[0051] Among them, the exclusive network access policy includes: when the smart home gateway verifies the network access request of a physical device, it only allows physical devices whose unique serial numbers match the serial numbers in the device whitelist to access the network.

[0052] Specifically, the gateway distributes the whitelist to its internal coordination program (such as the ZigBee coordinator). Upon successful receipt, the gateway enables device access. During network access, the gateway verifies the device initiating the request: only devices with unique serial numbers on the whitelist are allowed to connect; devices with serial numbers not on the whitelist (such as devices interfering with neighboring devices) are rejected. The gateway also verifies the validity and integrity of the device data, pushing the data of devices that pass verification to the cloud. The system continuously monitors whether all devices on the whitelist have completed network access; once all are connected, the coordination program's network access permission is terminated.

[0053] S5. After the physical device is connected to the network, the configuration parameters in the home project template are injected into the corresponding physical device according to the pre-binding relationship.

[0054] After all whitelisted devices have successfully joined the network, the system will automatically inject the configuration parameters from the home project template into the corresponding physical devices, including the following sub-steps: S51. Establish a mapping table between the logical identifiers of the baseline apartment configuration template and the unique serial numbers of the physical equipment in the target home. This mapping table associates each logical slot in the template with the unique serial number of the actual equipment on site.

[0055] S52. Based on the mapping table, replace the scenario logic and spatial topology relationships in the baseline apartment configuration template with the physical control commands of the target family. The server parses the scenario execution chain in the baseline template, performs recursive mapping and replacement on the execution list including device actions, nested scenarios, and object model objects, and uses the scenario mapping table to redirect the virtual logic pointers in the template to the real physical control commands of the target family, while replacing the spatial topology relationships with the actual spatial data of the target family.

[0056] S53. Identify the hardware characteristics of the physical device through the device adapter and inject the functional cluster attributes from the baseline unit configuration template into the target physical device. The server calls the device adapter, identifies its hardware characteristics based on the physical device's Product Key, and reads the device's functional cluster attributes (such as dimming mode parameters, baud rate settings, etc.) from the baseline template. It then maps these underlying register configurations across models and injects them into the target physical device to achieve automatic alignment of hardware differences.

[0057] The injection of configuration parameters is performed hierarchically in the order of "basic equipment → smart scenarios → spatial topology → common configurations". After each level of import, the system needs to receive an asynchronous execution receipt (Ack) from the gateway to confirm that the underlying attributes have been written successfully.

[0058] S6. Verify the network access status and configuration parameter injection status of the device based on the status bits of the dynamically deployed state machine. After the verification is successful, the construction and delivery are completed.

[0059] Before and during the configuration parameter injection process, the system performs automated verification based on the state bits of the dynamically deployed state machine, including the following sub-steps: S61. Before injecting configuration parameters, poll the online status of all physical devices with established pre-binding relationships to obtain the online status polling results. If any offline devices are found, the process is interrupted. This pre-configuration interception mechanism can avoid invalid configurations caused by devices not being powered on or malfunctioning.

[0060] S62. During the configuration parameter injection process, after each level of configuration parameter injection, receive the asynchronous execution receipt returned by the gateway to confirm that the underlying attribute has been successfully written.

[0061] S63. Based on the online status polling results and the receipt of asynchronous execution receipts, update the status bits of the dynamic deployment state machine. If the import at a certain level fails or a receipt is not received within a timeout period, the system records a fault log, suspends the state machine, jumps to the verification anomaly state, and prompts for manual intervention. Only when the online status polling shows no offline devices and all levels have successfully received asynchronous execution receipts, does the system release the distributed lock and update the dynamic deployment state machine to construction complete.

[0062] At this point, the smart home system configuration for the target household is complete and ready for delivery. Figure 2 The illustrated project implementation process visually demonstrates the complete process from associating template families and batch configuring on-site to project delivery.

[0063] Through the above steps, the present invention enables rapid batch configuration of smart home systems for residential buildings of the same type, greatly improving construction efficiency and configuration consistency.

[0064] Further reference Figure 5 This invention also proposes a batch configuration system for smart home systems with the same floor plan, used to implement any of the methods described above. This system can be specifically applied to various electronic devices. The system includes: The mobile client is configured to scan the unique serial number of the physical device and send the obtained unique serial number to the cloud server. The cloud server is configured to store the baseline apartment configuration template, create a family instance for the target family and clone the family project template based on the baseline apartment configuration template, establish a dynamic deployment state machine for the target family, establish a pre-binding relationship between the unique serial number sent by the mobile client and the logical identifier of the logical slot, and generate a device whitelist based on the pre-binding relationship. The smart home gateway is configured to obtain a device whitelist from the cloud server, execute an exclusive network access policy based on the device whitelist, and only allow physical devices with unique serial numbers in the device whitelist to enter the network. After the physical device enters the network, the configuration parameters in the home project template are injected into the corresponding physical device according to the pre-binding relationship. Multiple physical devices, each with a physical identifier containing a unique serial number on its surface, are configured to establish a communication connection with the smart home gateway and receive configuration parameters.

[0065] The present invention also proposes a terminal device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to implement the steps of the batch configuration method for a smart home system of the same type as described above.

[0066] The present invention also proposes a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the batch configuration method for a smart home system of the same type as described above.

[0067] The following is for reference. Figure 6 It shows a schematic diagram of the structure of a computer system 600 suitable for implementing terminal devices or servers in the embodiments of this application. Figure 6 The terminal device or server shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0068] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the computer system 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0069] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a liquid crystal display (LCD) and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card and a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0070] Specifically, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined in the methods of this application. It should be noted that the computer-readable medium described in this application can be a computer-readable signal medium or a computer-readable medium or any combination thereof. The computer-readable medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. Program code contained on a computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0071] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0072] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0073] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method for batch configuration of a smart home system for the same apartment type, characterized in that, Includes the following steps: S1. Establish a baseline apartment configuration template, which includes logical slots formed by abstracting the physical equipment in the baseline apartment that has been configured, logical identifiers corresponding to each logical slot, and spatial and business attributes corresponding to each logical slot. S2. Create a family instance for the target family, and clone and generate a family project template for the target family based on the baseline house type configuration template, while establishing a dynamic deployment state machine for the target family; S3. By scanning the unique serial number of the physical device, the target family for the current construction is determined based on the family instance. The obtained unique serial number is filled into the corresponding logical slot in the family project template corresponding to the target family, and a pre-binding relationship is established between the unique serial number of the physical device and the logical identifier of the logical slot. S4. The smart home gateway obtains the device whitelist formed based on the pre-binding relationship, and executes an exclusive network access policy according to the device whitelist, allowing only physical devices with the unique serial number in the device whitelist to access the network; S5. After the physical device is connected to the network, the configuration parameters in the home project template are injected into the corresponding physical device according to the pre-binding relationship. S6. Verify the network access status and configuration parameter injection status of the device according to the status bits of the dynamic deployment state machine, and complete the construction and delivery after the verification is passed.

2. The method for batch configuration of a smart home system with the same floor plan as described in claim 1, characterized in that, In step S1, a baseline apartment layout template is established, including the following sub-steps: S11. Select a baseline apartment type where equipment installation and configuration have been completed; S12. Extract the equipment information, scenario mode information and area information of the benchmark apartment type through the interface; S13. The extracted device information, scenario mode information and area information are solidified into the benchmark apartment configuration template, and the benchmark apartment configuration template is bound to the apartment identifier.

3. The method for batch configuration of a smart home system with the same floor plan as described in claim 1, characterized in that, In step S2, establishing a dynamic deployment state machine for the target family includes the following sub-steps: S21. Set multiple status bits for the dynamic deployment state machine, including not started, waiting to scan code for pre-binding, gateway configuration in progress, sub-device automatic network access in progress, configuration logic import in progress, verification error, and construction completed. S22. Monitor the current status position and control the construction process to jump to the next status position only after the step corresponding to the previous status position has been verified.

4. The method for batch configuration of a smart home system with the same floor plan as described in claim 1, characterized in that, In step S3, establishing a pre-binding relationship between the unique serial number of the physical device and the logical identifier of the logical slot includes the following sub-steps: S31. Scan the physical identifier on the physical device using a mobile client to obtain the unique serial number of the physical device; S32. Based on the family instance, determine the target family for the current construction, locate the corresponding family project template, and fill the obtained unique serial number into the corresponding logical slot in the family project template; S33. Based on the input results, the cloud server establishes and stores the pre-binding relationship between the unique serial number and the logical identifier of the logical slot.

5. The method for batch configuration of a smart home system with the same floor plan as described in claim 1, characterized in that, In step S4, the smart home gateway obtains the device whitelist based on the pre-binding relationship, including the following sub-steps: S41. The cloud server generates a device whitelist containing the unique serial number based on the pre-binding relationship; S42. The cloud server sends the device whitelist to the smart home gateway; The exclusive network access policy includes: when the smart home gateway verifies the network access request of a physical device, it only allows physical devices whose unique serial numbers match the serial numbers in the device whitelist to access the network.

6. The method for batch configuration of a smart home system with the same floor plan as described in claim 1, characterized in that, In step S5, the configuration parameters in the home project template are injected into the corresponding physical device, including the following sub-steps: S51. Establish a mapping table between the logical identifier of the benchmark apartment configuration template and the unique serial number of the physical equipment of the target family; S52. Based on the mapping table, replace the scenario logic and spatial topology relationship in the baseline apartment configuration template with the physical control instructions of the target family. S53. Identify the hardware characteristics of the physical device through the device adapter and inject the functional cluster attributes in the baseline unit configuration template into the target physical device.

7. The method for batch configuration of a smart home system with the same floor plan as described in claim 1, characterized in that, In step S6, verification is performed based on the state bits of the dynamically deployed state machine, including the following sub-steps: S61. Before injecting configuration parameters, poll the online status of all physical devices with established pre-binding relationships to obtain the online status polling results. If there are offline devices, interrupt the process. S62. During the configuration parameter injection process, after each level of configuration parameter injection, receive the asynchronous execution receipt returned by the gateway to confirm that the underlying attribute has been successfully written. S63. Update the status bits of the dynamically deployed state machine based on the online status polling results and the receipt status of the asynchronous execution receipt.

8. A batch configuration system for smart home systems of the same apartment type, characterized in that, The system for implementing the method of any one of claims 1 to 7 comprises: A mobile client is configured to scan the unique serial number of a physical device and send the obtained unique serial number to a cloud server; The cloud server is configured to store the baseline apartment configuration template, create a family instance for the target family and clone the family project template based on the baseline apartment configuration template, establish a dynamic deployment state machine for the target family, establish a pre-binding relationship between the unique serial number sent by the mobile client and the logical identifier of the logical slot, and generate a device whitelist based on the pre-binding relationship. The smart home gateway is configured to obtain the device whitelist from the cloud server, execute an exclusive network access policy based on the device whitelist, and only allow physical devices whose unique serial numbers exist in the device whitelist to access the network. After the physical device is accessed, the configuration parameters in the home project template are injected into the corresponding physical device according to the pre-binding relationship. Multiple physical devices, each with a physical identifier containing a unique serial number on its surface, are configured to establish a communication connection with the smart home gateway and receive the configuration parameters.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the batch configuration method for a smart home system of the same type as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the batch configuration method for smart home systems of the same type as described in any one of claims 1 to 7.

Images