Implementation method of an underground parking coordination monitoring system

Abstract

The application provides an implementation method of a coordinated monitoring system of an underground parking lot. The system comprises edge devices and monitoring devices which are uniformly distributed in the underground parking lot. The system has the following functions: (1) realizing coordinated real-time monitoring of the underground parking lot, significantly improving monitoring efficiency and accuracy; (2) realizing full coverage of monitoring, simultaneously acquiring data of multiple parking areas and comprehensively analyzing the data; (3) efficiently recording data such as parking space utilization rate and peak period, providing strong support for optimized management, dynamic pricing and reconstruction and expansion. The application of the system can effectively improve the monitoring and use efficiency of the underground parking lot and reduce the management cost, and has a wide application prospect in the field of intelligent transportation.

Description

Technical Field

[0001] This invention relates to an implementation method, and more particularly to an implementation method for a collaborative monitoring system for underground parking lots. Background Technology

[0002] Underground parking lots currently rely mainly on the traditional method of manual inspection and checking of parking spaces. This method has the following shortcomings: (1) Low efficiency and inability to achieve collaborative monitoring: Manual inspection requires checking each floor and area, which is time-consuming and has limited coverage. It is impossible to obtain parking space information and environmental information in other areas, and it is also impossible to achieve collaborative monitoring, analysis of comprehensive data, and timely alarm for emergencies. (2) Information lag and inaccuracy: There is a delay in manual recording or visual judgment of parking space status, and it is impossible to update the parking space occupancy status in real time, often resulting in misjudgment. (3) High labor costs: Multiple staff members need to be deployed to patrol in shifts, and the pressure is high during peak hours, resulting in high long-term operating costs. (4) Management blind spots and safety hazards: Manual inspection is difficult to cover all corners, and monitoring blind spots are easy to occur. It is also difficult to respond to emergencies such as illegal parking and fires in a timely manner. (5) Insufficient data utilization: Manual methods are difficult to systematically record data such as parking space utilization rate and peak hours, which cannot provide effective support for optimizing management, dynamic pricing, or renovation and expansion.

[0003] The present invention aims to solve the above problems and realize collaborative real-time monitoring of underground parking lots. Summary of the Invention

[0004] Purpose of the invention: The technical problem to be solved by the present invention is to provide a method for implementing a collaborative monitoring system for underground parking lots, addressing the shortcomings of existing technologies.

[0005] Technical Solution: This invention discloses a method for implementing a collaborative monitoring system for underground parking lots. The system includes edge devices and monitoring devices, which are evenly distributed throughout the underground parking lot. The monitoring devices send registration messages to establish a local table; the edge devices send edge messages from each wired interface to establish an edge table; and the monitoring devices send block request messages to obtain target data blocks. The monitoring device sends a collaborative message to obtain all data blocks contained in the target data; the edge device that receives the collaborative message creates a reverse entry. If the edge device does not have a local table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, it forwards the collaboration message from the wired interface; otherwise, the edge device forwards the collaboration message from the wireless interface. The monitoring device that receives the collaboration message sends a parking message, which contains a data block table entry and a set of data block IDs. The name and data block ID of the data block table entry are equal to the name and data block ID of the collaboration message, respectively. The set of data block IDs contains the data block IDs in all search entries whose names are equal to the name of the collaboration message. Upon receiving the parking message, the edge device creates a remote entry for each data block ID in the parking message data block ID set. The name of the remote entry is equal to the name of the data block entry in the parking message, the data block ID is equal to the data block ID, and the edge ID is equal to the edge ID in the parking message. For each reverse entry whose name and data block ID are equal to the name and data block ID in the parking message data block entry, the edge device forwards the parking message from the interface identified by the interface ID of the reverse entry. If the monitoring device that sent the collaborative message receives the parking lot message, it creates a data block table entry. The name, data block ID, and data block of this data block table entry are equal to the name, data block ID, and data block of the data block table entry in the parking lot message, respectively.

[0006] The method further includes: For each data block contained in the target data, the monitoring device sends a coordination message. The name of the coordination message is the name that identifies the target data, the data block ID is the data block ID of the data block, and the edge ID is empty. If the edge device that receives the collaboration message does not have a local table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, and the edge ID of the collaboration message is not empty, the edge device will select the edge table entry whose edge ID is equal to the edge ID of the collaboration message and forward the collaboration message from the interface identified by the interface ID of the edge table entry. If the edge device does not have a local table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, and the edge ID of the collaboration message is empty, and there is a remote table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, the edge device sets the edge ID of the collaboration message to the edge ID of the remote table entry, selects the edge table entry whose edge ID is equal to the edge ID of the collaboration message, and forwards the collaboration message from the interface identified by the interface ID of the edge table entry; If the edge device does not have a local entry whose name and data block ID are equal to the name and data block ID in the collaboration message, and the edge ID of the collaboration message is empty, and there is no remote entry whose name and data block ID are equal to the name and data block ID in the collaboration message, the edge device forwards the collaboration message from each wired interface.

[0007] The method further includes: In the block request message sent by the monitoring device, the name and data block ID are equal to the name and data block ID that identify the target data block, respectively, and the edge ID is empty; Upon receiving the block request message, the edge device creates a reverse entry. If the edge device does not have a local entry whose name and block ID are equal to the name and block ID in the block request message, it forwards the block request message from the wired interface. Otherwise, the edge device forwards the block request message from the wireless interface. The monitoring device that receives the block request message sends a block response message containing a block entry and a set of block IDs. The name and block ID of the block entry are equal to the name and block ID of the block request message, and the set of block IDs contains the block IDs from all retrieved entries whose names are equal to the names in the block request message. Upon receiving the block response message, the edge device creates a remote entry for each block ID in the block response message's block ID set. The remote entry's name is equal to the name of the block entry in the block response message, the block ID is equal to the block ID, and the edge ID is equal to the edge ID in the block response message. For each reverse entry whose name and block ID are equal to the name and block ID in the block response message's block entry, the edge device forwards the block response message from the interface identified by the interface ID of the reverse entry. If the monitoring device that sent the block request message receives the block response message, it creates a data block table entry. The name, data block ID, and data block of this data block table entry are equal to the name, data block ID, and data block of the data block table entry in the block response message, respectively.

[0008] The method further includes: If the edge device that receives the block request message does not have a local table entry whose name and data block ID are equal to the name and data block ID in the block request message, and the edge ID of the block request message is not empty, the edge device will select the edge table entry whose edge ID is equal to the edge ID of the block request message and forward the block request message from the interface identified by the interface ID of the edge table entry. If the edge device does not have a local table entry whose name and data block ID are equal to the name and data block ID in the block request message, and the edge ID of the block request message is empty, and there is a remote table entry whose name and data block ID are equal to the name and data block ID in the block request message, the edge device sets the edge ID of the block request message to the edge ID of the remote table entry, selects the edge table entry whose edge ID is equal to the edge ID of the block request message, and forwards the block request message from the interface identified by the interface ID of the edge table entry; If the edge device does not have a local entry whose name and data block ID are equal to the name and data block ID in the block request message, and the edge ID of the block request message is empty, and there is no remote entry whose name and data block ID are equal to the name and data block ID in the block request message, the edge device forwards the block request message from each wired interface.

[0009] The method further includes: Each edge device maintains a local table, and each local table entry contains the name, data block ID, and lifecycle; the registration message sent by the monitoring device retrieves its own retrieval table. After receiving the registration message, the edge device connected to the monitoring equipment sets a search entry variable with an empty value; the edge device selects the first search entry from the search table of the registration message, sets the value of the variable to the search entry, and deletes the selected search entry from the search table of the registration message; the edge device creates a local entry, and the name and data block ID of the local entry are equal to the name and data block ID of the variable, respectively.

[0010] The method further includes: Each edge device maintains an edge table, with each entry containing the edge ID, interface ID, and lifecycle; each edge device also maintains a deduplication table, with each entry containing the serial number and lifecycle. The edge device sending the edge message creates a random number. The edge ID is its own edge ID and the sequence number is the random number in the edge message sent by the edge device from each wired interface. If the edge device that receives the edge message does not have a duplicate entry with a serial number equal to the serial number in the edge message, then it creates a duplicate entry with a serial number equal to the serial number in the edge message. The edge device creates an edge entry, the edge ID of which is equal to the edge ID in the edge message, and the interface ID is equal to the interface ID of the interface receiving the edge message; the edge device forwards the edge message from each wired interface except the interface receiving the edge message.

[0011] The method further includes: Each edge device maintains a remote table, and each remote table entry contains the edge ID, name, data block ID, and lifecycle. Each edge device maintains a reverse table, and each reverse table entry contains a name, a data block ID, and an interface ID.

[0012] The method further includes: A type of data is uniquely identified by a name and consists of multiple data blocks. Each data block is configured with a data block ID. A data block in a type of data is uniquely identified by the name of the data and the data block ID of the data block. Each monitoring device maintains a data block table. A data block table entry contains a name, data block ID, data block, and lifecycle. After a monitoring device collects a data block, it creates a data block table entry. The name and data block ID of this data block table entry are equal to the name and data block ID that identify the data block, respectively. The data block is the collected data block. Each monitoring device maintains a retrieval table, and each retrieval table entry contains the name, data block ID, and lifespan.

[0013] The method further includes: The monitoring device sets a data block table variable whose value is equal to its own data block table. It also sets a data block table variable whose value is empty. The monitoring device selects the first data block table entry from the data block table variable, sets the value of the data block table entry variable to the data block table entry, and deletes the selected data block table entry from the data block table variable; the monitoring device creates a retrieval table entry, the name and data block ID of which are equal to the name and data block ID in the data block table entry variable, respectively.

[0014] The method further includes: Each edge device is configured with multiple wired interfaces and one wireless interface. The wired interfaces connect to other edge devices, and the wireless interface connects to the monitoring device. Each monitoring device is configured with one wireless interface, which connects to the wireless interface of one edge device. Each wired or wireless interface is uniquely identified by an interface ID. An edge device is uniquely identified by an edge ID.

[0015] Beneficial Effects: This invention provides a method for implementing a collaborative monitoring system for underground parking lots. The system has the following functions: (1) It enables collaborative real-time monitoring of underground parking lots, significantly improving monitoring efficiency and accuracy; (2) It achieves full monitoring coverage, simultaneously acquiring data from multiple parking areas and performing comprehensive analysis; (3) It efficiently records data such as parking space utilization and peak hours, providing strong support for optimized management, dynamic pricing, and renovation / expansion. The application of this system can effectively improve the monitoring and utilization efficiency of underground parking lots, reduce management costs, and has broad application prospects in the field of intelligent transportation. Attached Figure Description

[0016] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments, and the advantages of the present invention in the above and / or other aspects will become clearer.

[0017] Figure 1 This is a schematic diagram of the underground parking lot collaborative monitoring system described in this invention.

[0018] Figure 2 This is a schematic diagram of the process for creating a search table as described in this invention.

[0019] Figure 3 This is a schematic diagram of the process for creating a local table as described in this invention.

[0020] Figure 4 This is a schematic diagram of the process for creating an edge table according to the present invention.

[0021] Figure 5 This is a schematic diagram of the collaborative monitoring data block process described in this invention.

[0022] Figure 6 This is a schematic diagram of the collaborative monitoring data flow described in this invention. Detailed Implementation

[0023] To enable those skilled in the art to better understand the technical solutions of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the described embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0024] Figure 1 This is a schematic diagram of the underground parking lot collaborative monitoring system described in this invention. Figure 2 This is a schematic diagram of the process for establishing a retrieval table according to the present invention. The system includes edge devices and monitoring devices. The edge devices can be routers, and the monitoring devices can be probes, cameras, sensor nodes, etc. The edge devices and monitoring devices are evenly distributed in the underground parking lot, for example, mounted on a wall. Each edge device is equipped with multiple wired interfaces and one wireless interface. The wired interfaces connect to other edge devices, and the wireless interface connects to the monitoring devices. Each monitoring device is equipped with one wireless interface, which is connected to the wireless interface of one edge device. A type of data is uniquely identified by a name and consists of multiple data blocks. Each data block is configured with a data block ID. A data block in a type of data is uniquely identified by the name of the data and the data block ID of the data block. For example, the name can be the identifier of a certain area in an underground parking lot, such as Area A. The data identified by the name can be all the underground parking lot information in that area. A data block of the data can be the road obstacles, number of parking spaces, temperature, humidity, water accumulation, etc. in that area. Each wired and wireless interface is uniquely identified by an interface ID, and the interface with interface ID x is abbreviated as interface x; an edge device is uniquely identified by an edge ID, which can be a hardware address, such as a MAC address; each message is uniquely identified by a message ID; each monitoring device is pre-configured with the edge IDs of the edge devices it connects to. Each monitoring device maintains a data block table. A data block table entry contains a name, data block ID, data block, and lifespan. The initial value of the data block table is an empty table. After the monitoring device collects a data block named NA1 with data block ID DID1, it creates a data block table entry. The name of this data block table entry is NA1, the data block ID is DID1, the data block is the collected data block, and the lifespan is the maximum lifespan, such as 30 minutes. Each monitoring device maintains a lookup table. Each lookup table entry contains the name, data block ID, and lifecycle. The initial value of the lookup table is an empty table. If the data block table of monitoring device H1 is not empty, perform the following operations periodically: Step 101: Begin; Step 102: The monitoring device H1 sets a data block table variable cv1, the value of which is its own data block table, and sets a data block table entry variable cev1, the value of which is empty. Step 103: Monitoring device H1 selects the first data block table entry from variable cv1, sets the value of variable cev1 to the data block table entry, and deletes the selected data block table entry from variable cv1; Step 104: Monitoring device H1 determines whether there is a search entry whose name and data block ID are equal to the name and data block ID in variable cev1, respectively. If it exists, the lifetime of the search entry is set to the maximum value; otherwise, a search entry is created whose name and data block ID are equal to the name and data block ID in variable cev1, and the lifetime of the search entry is set to the maximum value. Step 105: Monitoring device H1 determines whether variable cv1 is an empty table. If it is, proceed to step 106; otherwise, proceed to step 103. Step 106: End.

[0025] The above process has the following innovations: (1) The monitoring equipment uses the data block table to establish a retrieval table through the above process, and notifies the connected edge device of the data block ID that it can provide, thereby ensuring that it can provide data blocks quickly and correctly; (2) The above process is implemented locally without data interaction, so it can ensure the real-time performance and correctness of the retrieval table, thereby improving the real-time performance and correctness of underground parking lot monitoring.

[0026] Figure 3 This is a schematic diagram illustrating the process of establishing a local table as described in this invention. Each edge device stores a local table, and each local table entry includes a name, data block ID, and lifecycle; the initial value of the local table is an empty table. The registration message includes a message ID and a search table; Monitoring device H1 is connected to edge device E1. If the lookup table of monitoring device H1 is not empty, the following operation is performed periodically: Step 201: Begin; Step 202: Monitoring device H1 sends a registration message with message ID 1 and its own search table. Step 203: After receiving the registration message, edge device E1 sets a retrieval table entry variable cev11, and the value of variable cev11 is empty; Step 204: The edge device E1 that receives the registration message selects the first search term from the search table of the registration message, sets the value of the variable cev11 to the search term, and deletes the selected search term from the search table of the registration message. Step 205: The edge device E1 that receives the registration message determines whether a local table entry exists. The name and data block ID of the local table entry are equal to the name and data block ID in the variable cev11, respectively. If it exists, the lifetime of the local table entry is set to the maximum value. Otherwise, the edge device E1 creates a local table entry. The name and data block ID of the local table entry are equal to the name and data block ID in the variable cev11, respectively. The lifetime of the local table entry is set to the maximum value, for example, 30 minutes. Step 206: The edge device E1 that receives the registration message determines whether the retrieval table of the registration message is empty. If it is, proceed to step 207; otherwise, proceed to step 204. Step 207: End.

[0027] The above process has the following innovations: (1) The monitoring device sends a registration message to the edge device to establish its own local table entry. In this way, the edge device can obtain the data block ID that the connected monitoring device can provide through the local table entry, thereby providing data quickly; (2) The monitoring device and the edge device are neighboring nodes, so they can quickly create local tables and ensure the real-time and correctness of local tables, reduce the delay in creating local tables, and also ensure the real-time monitoring of underground parking lots.

[0028] Figure 4 This is a schematic diagram of the edge table establishment process described in this invention. Each edge device stores an edge table, and each edge table entry contains an edge ID, an interface ID, and a lifecycle; each edge device stores a deduplication table, and each deduplication table entry contains a sequence number and a lifecycle; the edge table is initially empty, and the deduplication table is also initially empty. Edge messages contain a message ID, an edge ID, and a sequence number; Edge device E1 has an edge ID of EID1 and performs the following operations periodically: Step 301: Begin; Step 302: Edge device E1 creates a random number R1 and sends an edge message from each wired interface. The message ID is 2, the edge ID is EID1, and the sequence number is R1. Step 303: The edge device that receives the edge message from interface y1 determines whether there is a duplicate entry in the table. The sequence number of the entry is equal to the sequence number in the edge message. If it exists, proceed to step 306; otherwise, proceed to step 304. Step 304: The edge device that receives the edge message from interface y1 creates a deduplication entry. The sequence number of the deduplication entry is equal to the sequence number in the edge message, and the lifespan is the maximum lifespan value, such as 30 minutes. The edge device determines whether there is an edge entry. The edge ID of the edge entry is equal to the edge ID in the edge message. If it exists, the interface ID of the edge entry is set to y1, and the lifespan is set to the maximum value. Otherwise, an edge entry is created. The edge ID of the edge entry is equal to the edge ID in the edge message. The interface ID of the edge entry is set to y1, and the lifespan is set to the maximum value. Step 305: The edge device that receives the edge message from interface y1 forwards the edge message from each wired interface other than interface y1, and executes step 303; Step 306: End.

[0029] The above process has the following innovations: (1) Edge devices send edge messages to other edge devices to establish their own edge entries, thereby establishing routing paths for other edge devices to reach themselves, realizing efficient data transmission and monitoring of underground parking lots; (2) The above process establishes edge entries through a deduplication table, effectively avoiding repeated forwarding of edge messages, reducing the creation delay and cost of edge tables, and realizing the real-time nature of collaborative monitoring of underground parking lots.

[0030] Figure 5 This is a schematic diagram of the collaborative monitoring data block process described in this invention. Each edge device stores a remote table, and each remote table entry contains the edge ID, name, data block ID, and lifecycle; the initial value of the remote table is an empty table; Each edge device maintains a reverse table, and each reverse table entry contains a name, data block ID, and interface ID; the reverse table is initially empty; data DA1 is defined by the name NA1. The block request message includes the message ID, name, data block ID, and edge ID; The block response message contains a message ID, an edge ID, a data block table entry, and a set of data block IDs; Monitoring device H2 is connected to edge device E2. If a monitoring device exists in the system and can provide a data block named NA1 with data block ID CID1, monitoring device H2 obtains the data block named NA1 with data block ID CID1 through the following process: Step 401: Begin; Step 402: Monitoring device H1 sends a block request message with message ID 3, name NA1, data block ID CID1, and edge ID empty; Step 403: The edge device that receives the block request message from interface y2 determines whether there is a reverse entry. The name and data block ID of the reverse entry are equal to the name and data block ID in the block request message, and the interface ID is equal to y2. If it exists, proceed to step 414; otherwise, proceed to step 404. Step 404: The edge device that receives the block request message from interface y2 determines whether there is a reverse entry. The name and data block ID of the reverse entry are equal to the name and data block ID in the block request message, respectively. If it exists, proceed to step 405; otherwise, proceed to step 406. Step 405: The edge device that receives the block request message from interface y2 creates a reverse entry. The name and data block ID of the reverse entry are equal to the name and data block ID in the block request message, respectively. The interface ID is y2. Then proceed to step 414. Step 406: The edge device that receives the block request message from interface y2 creates a reverse entry. The name and data block ID of the reverse entry are equal to the name and data block ID in the block request message, respectively. The interface ID is y2. The edge device determines whether there is a local entry. The name and data block ID of the local entry are equal to the name and data block ID in the block request message, respectively. If there is, proceed to step 407; otherwise, proceed to step 409. Step 407: The edge device that receives the block request message from interface y2 forwards the block request message from the wireless interface. The monitoring device that receives the block request message determines whether it has a data block table entry. The name and data block ID of the entry are equal to the name and data block ID of the block request message, respectively. If it exists, proceed to step 408; otherwise, proceed to step 419. Step 408: The monitoring device that receives the block request message selects a data block table entry. The name and data block ID of this entry are equal to the name and data block ID of the block request message, respectively. It selects all retrieval entries whose names are equal to the name of the block request message, and sends a block response message. The message ID of this message is 4, the edge ID is the edge ID of the connected edge device, the data block table entry is the selected data block table entry, and the data block ID set contains the data block IDs of all selected retrieval entries. Then, proceed to step 414. Step 409: The edge device that receives the block request message from interface y2 determines whether the edge ID of the block request message is empty. If it is, proceed to step 411; otherwise, proceed to step 410. Step 410: The edge device that receives the block request message from interface y2 selects an edge entry, the edge ID of which is equal to the edge ID in the block request message, and forwards the block request message from the interface identified by the interface ID of the edge entry, and executes step 403; Step 411: The edge device that receives the block request message from interface y2 determines whether there is a remote entry whose name and data block ID are equal to the name and data block ID in the block request message, respectively. If it exists, proceed to step 412; otherwise, proceed to step 413. Step 412: The edge device that receives the block request message from interface y2 selects a remote table entry. The name and data block ID of the table entry are equal to the name and data block ID in the block request message, respectively. The edge ID of the block request message is set to the edge ID in the remote table entry. An edge table entry is selected. The edge ID of the table entry is equal to the edge ID in the block request message. The block request message is forwarded from the interface identified by the interface ID of the edge table entry. Step 403 is then executed. Step 413: The edge device that receives the block request message from interface y2 determines whether interface y2 is a wired interface. If it is, the edge device forwards the block request message from each wired interface except interface y2. Otherwise, the edge device forwards the block request message from each wired interface. The edge device then executes step 403. Step 414: If monitoring device H2 receives the block response message, proceed to step 418; otherwise, proceed to step 415. Step 415: If the data block ID set in the received block response message is not empty, the edge device performs the following operation on each data block ID CID3 in the data block ID set: Determine whether there exists a remote entry whose name is equal to the name of the data block entry in the message, whose data block ID is equal to CID3, and whose edge ID is equal to the edge ID in the block response message. If it exists, set the lifetime of the remote entry to the maximum value; otherwise, create a remote entry whose name is equal to the name of the data block entry in the message, whose data block ID is equal to CID3, set the edge ID of the entry to the edge ID in the block response message, and set the lifetime to the maximum value. Step 416: The edge device that receives the block response message determines whether there is a reverse entry, the name and data block ID of which are equal to the name and data block ID of the data block entry in the message, respectively. If it exists, proceed to step 417; otherwise, proceed to step 419. Step 417: The edge device that receives the block response message selects all reverse entries whose names and data block IDs are equal to the name and data block ID of the data block table entry in the block response message, respectively. For each selected reverse entry, the edge device forwards the block response message from the interface identified by the interface ID of the reverse entry. The edge device deletes all selected reverse entries and executes step 414. Step 418: The monitoring device H2 that receives the block response message determines whether there is a data block table entry. The name and data block ID of the entry are equal to the name and data block ID of the data block table entry in the block response message, respectively. If it exists, the lifetime of the entry is set to the maximum value. Otherwise, a data block table entry is created. The name, data block ID, and data block of the data block table entry are equal to the name, data block ID, and data block of the data block table entry in the block response message, respectively. The lifetime is set to the maximum value. Step 419: End.

[0031] The above process has the following innovations: (1) The monitoring device obtains the target data block by sending a block request message to the connected edge device. The edge device sends the block request message to the nearest monitoring device through the local table, remote table and reverse table to obtain the underground parking lot data block; (2) The edge device establishes a remote table through the above process, and can then quickly provide underground parking lot data; (3) The above process enables multiple monitoring devices to obtain underground parking lot data blocks at the same time through the reverse table, which improves the data block monitoring efficiency and the safety and efficiency of parking; (4) The monitoring device obtains the data blocks collected by other monitoring devices through the above process, realizing collaborative monitoring, for example, obtaining empty parking location information or parking lot environment data, which improves the safety and efficiency of parking.

[0032] Figure 6 This is a schematic diagram of the collaborative monitoring data flow described in this invention. Data DA1 is defined by the name NA1, and the data block ID set IDS1 contains the data block IDs of all data blocks in data DA1; The collaborative message includes a message ID, name, data block ID, and edge ID; The parking lot message includes a message ID, an edge ID, a data block table entry, and a set of data block IDs; Monitoring device H2 is connected to edge device E2. When the monitoring device of the system is capable of providing all data blocks contained in data DA1, monitoring device H2 obtains all data blocks in data DA1 through the following process: Step 501: Begin; Step 502: Monitoring device H2 sends a coordination message for each data block ID in IDS1. The message ID is 5, the name is NA1, the data block ID is the data block ID, and the edge ID is empty. Step 503: The edge device that receives the coordination message from interface z1 determines whether there is a reverse entry. The name and data block ID of the reverse entry are equal to the name and data block ID in the coordination message, respectively, and the interface ID is equal to z1. If it exists, proceed to step 514; otherwise, proceed to step 504. Step 504: The edge device that receives the collaboration message from interface z1 determines whether there is a reverse entry whose name and data block ID are equal to the name and data block ID in the collaboration message, respectively. If it exists, proceed to step 505; otherwise, proceed to step 506. Step 505: The edge device that receives the collaboration message from interface z1 creates a reverse entry. The name and data block ID of the entry are equal to the name and data block ID in the collaboration message, respectively. The interface ID is z1. Then proceed to step 514. Step 506: The edge device that receives the collaboration message from interface z1 creates a reverse entry. The name and data block ID of the entry are equal to the name and data block ID in the collaboration message, respectively. The interface ID is z1. The edge device determines whether there is a local entry. The name and data block ID of the entry are equal to the name and data block ID in the collaboration message, respectively. If there is, proceed to step 507; otherwise, proceed to step 509. Step 507: The edge device that receives the coordination message from interface z1 forwards the coordination message from the wireless interface. The monitoring device that receives the coordination message determines whether it has a data block table entry. The name and data block ID of the entry are equal to the name and data block ID of the coordination message, respectively. If it exists, proceed to step 508; otherwise, proceed to step 520. Step 508: The monitoring device that receives the collaborative message selects a data block table entry. The name and data block ID of the entry are equal to the name and data block ID of the collaborative message, respectively. It selects all search entries whose names are equal to the name of the collaborative message. It sends a parking lot message with message ID 6 and edge ID equal to the edge ID of the edge device it is connected to. The selected data block table entry is the data block table entry. The data block ID set contains the data block IDs of all selected search entries. Then, proceed to step 514. Step 509: The edge device that receives the collaboration message from interface z1 determines whether the edge ID of the collaboration message is empty. If it is, proceed to step 511; otherwise, proceed to step 510. Step 510: The edge device that receives the collaboration message from interface z1 selects an edge entry, the edge ID of which is equal to the edge ID in the collaboration message, and forwards the collaboration message from the interface identified by the interface ID of the edge entry, and executes step 503; Step 511: The edge device that receives the collaboration message from interface z1 determines whether there is a remote entry whose name and data block ID are equal to the name and data block ID in the collaboration message, respectively. If it exists, proceed to step 512; otherwise, proceed to step 513. Step 512: The edge device that receives the coordination message from interface z1 selects a remote entry whose name and data block ID are equal to the name and data block ID in the coordination message, respectively. The edge ID of the coordination message is set to the edge ID in the remote entry. An edge entry is selected whose edge ID is equal to the edge ID in the coordination message. The coordination message is forwarded from the interface identified by the interface ID of the edge entry. Step 503 is then executed. Step 513: The edge device that receives the coordination message from interface z1 determines whether interface z1 is a wired interface. If it is, the coordination message is forwarded from each wired interface except interface z1. Otherwise, the coordination message is forwarded from each wired interface, and step 503 is executed. Step 514: If the monitoring device H2 receives the parking lot message, proceed to step 518; otherwise, proceed to step 515. Step 515: The edge device that receives the parking message performs the following operation for each data block ID CID5 in the data block ID set in the message: Determine whether there exists a remote entry whose name is equal to the name of the data block entry in the message, whose data block ID is equal to CID5, and whose edge ID is equal to the edge ID in the parking message. If it exists, set the lifetime of the entry to the maximum value. Otherwise, create a remote entry whose name is equal to the name of the data block entry in the message, whose data block ID is equal to CID5, set the edge ID of the entry to the edge ID in the parking message, and set the lifetime to the maximum value. Step 516: The edge device that receives the parking message determines whether there is a reverse entry. The name and data block ID of the reverse entry are equal to the name and data block ID of the data block entry in the message, respectively. If it exists, proceed to step 517; otherwise, proceed to step 520. Step 517: The edge device that receives the parking message selects all reverse entries whose names and data block IDs are equal to the data block table entry name and data block ID in the parking message, respectively. For each selected reverse entry, the edge device forwards the parking message from the interface identified by the interface ID of the reverse entry. The edge device deletes all selected reverse entries and executes step 514. Step 518: The monitoring device H2 that receives the parking lot message determines whether there is a data block table entry. The name and data block ID of the entry are equal to the name and data block ID of the data block table entry in the parking lot message, respectively. If it exists, the lifespan of the entry is set to the maximum value. Otherwise, a data block table entry is created. The name, data block ID, and data block of the data block table entry are equal to the name, data block ID, and data block of the data block table entry in the parking lot message, respectively. The lifespan is set to the maximum value. Step 519: The monitoring device H2 that receives the parking lot message constructs a data block ID set IDS2, which contains the data block IDs in all data block table entries. If the intersection of the data block ID set IDS1 and the data block ID set IDS2 is equal to the set IDS1, then proceed to step 520; otherwise, proceed to step 514. Step 520: End.

[0033] The above process has the following innovative points: (1) The monitoring equipment sends a collaborative message to the edge device, and the edge device sends the collaborative message to the nearest monitoring equipment through the local table, remote table and reverse table to obtain underground parking lot data; (2) The edge device establishes a remote table through the parking lot message in the above process, and can then quickly provide underground parking lot data; (3) The above process enables multiple monitoring devices to obtain underground parking lot data at the same time through the reverse table, realizes collaborative monitoring, improves the overall data monitoring efficiency of the underground parking lot, and ensures the safety and efficiency of parking; (4) The monitoring equipment obtains data collected by other monitoring equipment through the above process to realize collaborative monitoring, for example, collaborative analysis of comprehensive data to realize emergency alarm.

[0034] Example 1 This embodiment simulates the implementation method of a collaborative monitoring system for underground parking lots according to the present invention. In this embodiment, the monitoring device acquires underground parking lot data in two ways: the monitoring device acquires monitoring data blocks through steps 401-419, and the monitoring device acquires monitoring data through steps 501-520. The evaluated system parameter is the average success rate of underground parking lot monitoring, which is defined as: the average success rate of the monitoring device acquiring data blocks or data through the above two methods. Based on the following simulation parameters, the average success rate is 98.23%: MAC protocol is IEEE 802.11, transmission radius is 100 meters, simulation time is 2 hours, and the number of simulations is 50. Example 1 verifies that the present invention has the following inventiveness and progressiveness: (1) The monitoring device sends a block request message or a collaborative message to the edge device, and the edge device sends the collaborative message to the nearest monitoring device to obtain underground parking lot data through the local table, remote table and reverse table; (2) The edge device establishes a remote table, which can then quickly provide underground parking lot data; (3) Through the reverse table, multiple monitoring devices can simultaneously obtain underground parking lot data, realizing collaborative monitoring, improving the overall data monitoring efficiency of the underground parking lot, and ensuring the safety and efficiency of parking; (4) The monitoring device achieves collaborative monitoring by obtaining data collected by other monitoring devices, for example, obtaining empty parking location information or parking lot environment data, improving the safety and efficiency of parking, and achieving early warning of danger through collaborative monitoring of comprehensive data.

[0035] This invention provides a method for implementing a collaborative monitoring system for underground parking lots. Many methods and approaches exist for implementing this technical solution; the above description is merely a preferred embodiment. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this invention, and these improvements and modifications should also be considered within the scope of protection of this invention. All components not explicitly stated in this embodiment can be implemented using existing technologies.

Claims

1. A method for implementing a collaborative monitoring system for underground parking lots, characterized in that, The system includes edge devices and monitoring devices, which are evenly distributed in the underground parking lot; the monitoring devices send registration messages to establish local tables; the edge devices send edge messages from each wired interface to establish edge tables; and the monitoring devices send block request messages to obtain target data blocks. The monitoring device sends a collaborative message to obtain all data blocks contained in the target data; the edge device that receives the collaborative message creates a reverse entry. If the edge device does not have a local table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, it forwards the collaboration message from the wired interface; otherwise, the edge device forwards the collaboration message from the wireless interface. The monitoring device that receives the collaboration message sends a parking message, which contains a data block table entry and a set of data block IDs. The name and data block ID of the data block table entry are equal to the name and data block ID of the collaboration message, respectively. The set of data block IDs contains the data block IDs in all search entries whose names are equal to the name of the collaboration message. Upon receiving the parking message, the edge device creates a remote entry for each data block ID in the parking message data block ID set. The name of the remote entry is equal to the name of the data block entry in the parking message, the data block ID is equal to the data block ID, and the edge ID is equal to the edge ID in the parking message. For each reverse entry whose name and data block ID are equal to the name and data block ID in the parking message data block entry, the edge device forwards the parking message from the interface identified by the interface ID of the reverse entry. If the monitoring device that sent the collaborative message receives the parking lot message, it creates a data block table entry. The name, data block ID, and data block of this data block table entry are equal to the name, data block ID, and data block of the data block table entry in the parking lot message, respectively.

2. The method for implementing a collaborative monitoring system for underground parking lots according to claim 1, characterized in that, For each data block contained in the target data, the monitoring device sends a coordination message. The name of the coordination message is the name that identifies the target data, the data block ID is the data block ID of the data block, and the edge ID is empty. If the edge device that receives the collaboration message does not have a local table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, and the edge ID of the collaboration message is not empty, the edge device will select the edge table entry whose edge ID is equal to the edge ID of the collaboration message and forward the collaboration message from the interface identified by the interface ID of the edge table entry. If the edge device does not have a local table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, and the edge ID of the collaboration message is empty, and there is a remote table entry whose name and data block ID are equal to the name and data block ID in the collaboration message, the edge device sets the edge ID of the collaboration message to the edge ID of the remote table entry, selects the edge table entry whose edge ID is equal to the edge ID of the collaboration message, and forwards the collaboration message from the interface identified by the interface ID of the edge table entry; If the edge device does not have a local entry whose name and data block ID are equal to the name and data block ID in the collaboration message, and the edge ID of the collaboration message is empty, and there is no remote entry whose name and data block ID are equal to the name and data block ID in the collaboration message, the edge device forwards the collaboration message from each wired interface.

3. The implementation method of the collaborative monitoring system for underground parking lots according to claim 1, characterized in that, In the block request message sent by the monitoring device, the name and data block ID are equal to the name and data block ID that identify the target data block, respectively, and the edge ID is empty; The edge device that receives the block request message creates a reverse entry; If the edge device does not have a local table entry whose name and data block ID are equal to the name and data block ID in the block request message, the block request message is forwarded from the wired interface; otherwise, the edge device forwards the block request message from the wireless interface. The monitoring device that receives the block request message sends a block response message containing a data block table entry and a set of data block IDs, wherein the name and data block ID of the data block table entry are equal to the name and data block ID of the block request message, and the set of data block IDs contains the data block IDs in all search entries whose names are equal to the names in the block request message. Upon receiving the block response message, the edge device creates a remote entry for each block ID in the block response message's block ID set. The remote entry's name is equal to the name of the block entry in the block response message, the block ID is equal to the block ID, and the edge ID is equal to the edge ID in the block response message. For each reverse entry whose name and block ID are equal to the name and block ID in the block response message's block entry, the edge device forwards the block response message from the interface identified by the interface ID of the reverse entry. If the monitoring device that sent the block request message receives the block response message, it creates a data block table entry. The name, data block ID, and data block of this data block table entry are equal to the name, data block ID, and data block of the data block table entry in the block response message, respectively.

4. A method for implementing a collaborative monitoring system for underground parking lots according to any one of claims 1 to 3, characterized in that, If the edge device that receives the block request message does not have a local table entry whose name and data block ID are equal to the name and data block ID in the block request message, and the edge ID of the block request message is not empty, the edge device will select the edge table entry whose edge ID is equal to the edge ID of the block request message and forward the block request message from the interface identified by the interface ID of the edge table entry. If the edge device does not have a local table entry whose name and data block ID are equal to the name and data block ID in the block request message, and the edge ID of the block request message is empty, and there is a remote table entry whose name and data block ID are equal to the name and data block ID in the block request message, the edge device sets the edge ID of the block request message to the edge ID of the remote table entry, selects the edge table entry whose edge ID is equal to the edge ID of the block request message, and forwards the block request message from the interface identified by the interface ID of the edge table entry; If the edge device does not have a local entry whose name and data block ID are equal to the name and data block ID in the block request message, and the edge ID of the block request message is empty, and there is no remote entry whose name and data block ID are equal to the name and data block ID in the block request message, the edge device forwards the block request message from each wired interface.

5. A method for implementing a collaborative monitoring system for underground parking lots according to any one of claims 1 to 3, characterized in that, Each edge device maintains a local table, and each local table entry contains the name, data block ID, and lifecycle; the registration message sent by the monitoring device retrieves its own retrieval table. After receiving the registration message, the edge device connected to the monitoring equipment sets a search entry variable with an empty value; the edge device selects the first search entry from the search table of the registration message, sets the value of the variable to the search entry, and deletes the selected search entry from the search table of the registration message; the edge device creates a local entry, and the name and data block ID of the local entry are equal to the name and data block ID of the variable, respectively.

6. A method for implementing a collaborative monitoring system for underground parking lots according to any one of claims 1 to 3, characterized in that, Each edge device maintains an edge table, with each entry containing the edge ID, interface ID, and lifecycle; each edge device also maintains a deduplication table, with each entry containing the serial number and lifecycle. The edge device sending the edge message creates a random number. The edge ID is its own edge ID and the sequence number is the random number in the edge message sent by the edge device from each wired interface. If the edge device that receives the edge message does not have a duplicate entry with a serial number equal to the serial number in the edge message, then it creates a duplicate entry with a serial number equal to the serial number in the edge message. The edge device creates an edge entry, the edge ID of which is equal to the edge ID in the edge message, and the interface ID is equal to the interface ID of the interface receiving the edge message; the edge device forwards the edge message from each wired interface except the interface receiving the edge message.

7. A method for implementing a collaborative monitoring system for underground parking lots according to any one of claims 1 to 3, characterized in that, Each edge device maintains a remote table, and each remote table entry contains the edge ID, name, data block ID, and lifecycle. Each edge device maintains a reverse table, and each reverse table entry contains a name, a data block ID, and an interface ID.

8. A method for implementing a collaborative monitoring system for underground parking lots according to any one of claims 1 to 3, characterized in that, A type of data is uniquely identified by a name and consists of multiple data blocks. Each data block is configured with a data block ID. A data block in a type of data is uniquely identified by the name of the data and the data block ID of the data block. Each monitoring device maintains a data block table. A data block table entry contains a name, data block ID, data block, and lifecycle. After a monitoring device collects a data block, it creates a data block table entry. The name and data block ID of this data block table entry are equal to the name and data block ID that identify the data block, respectively. The data block is the collected data block. Each monitoring device maintains a retrieval table, and each retrieval table entry contains the name, data block ID, and lifespan.

9. The method for implementing a collaborative monitoring system for underground parking lots according to claim 8, characterized in that, The monitoring device sets a data block table variable whose value is equal to its own data block table. It also sets a data block table variable whose value is empty. The monitoring device selects the first data block table entry from the data block table variable, sets the value of the data block table entry variable to the data block table entry, and deletes the selected data block table entry from the data block table variable; the monitoring device creates a retrieval table entry, the name and data block ID of which are equal to the name and data block ID in the data block table entry variable, respectively.

10. A method for implementing a collaborative monitoring system for underground parking lots according to any one of claims 1 to 3, characterized in that, Each edge device is configured with multiple wired interfaces and one wireless interface. The wired interfaces connect to other edge devices, and the wireless interface connects to the monitoring device. Each monitoring device is configured with one wireless interface, which connects to the wireless interface of one edge device. Each wired or wireless interface is uniquely identified by an interface ID. An edge device is uniquely identified by an edge ID.

Images