A resource matching method and system for sponge cities

Abstract

This invention discloses a resource matching method and system for sponge cities, belonging to the field of smart city management technology. The system includes a resource acquisition unit, a first processing unit, a correction unit, a second processing unit, an update unit, a matching unit, and a response unit. Through multi-dimensional data acquisition and dynamic risk assessment, the system achieves intelligent matching of sponge city resources. Specifically, it includes: a dynamic risk early warning mechanism based on water accumulation status and precipitation characteristics, optimizing the early warning threshold through secondary correction; risk analysis combined with historical resource allocation data; optimization of resource allocation strategies based on multi-source data updates; and adaptive resource matching schemes according to risk levels. This invention significantly improves the scientificity and efficiency of sponge city resource allocation by establishing a closed-loop optimized resource matching process, effectively solving problems such as data isolation, static assessment, and extensive decision-making in traditional methods, and providing an intelligent management tool for sponge city construction.

Description

Technical Field

[0001] This application relates to the field of smart city management technology, and in particular to a resource matching method and system for sponge cities. Background Technology

[0002] With the acceleration of urbanization, urban flooding has become an increasingly prominent problem, and traditional urban drainage systems are no longer sufficient to meet the rainwater discharge demands under extreme weather conditions. The concept of sponge cities offers a new approach to solving this problem. By constructing a comprehensive rainwater management system that combines infiltration, retention, storage, purification, utilization, and drainage, it effectively enhances the city's ability to cope with extreme weather events such as rainstorms. However, in the process of constructing sponge cities, how to scientifically and rationally allocate various sponge facility resources and achieve optimal resource matching still faces many technical challenges.

[0003] While some studies have attempted to introduce intelligent technologies to improve sponge city management—for example, CN116346940A proposes a monitoring and management system for smart sponge cities—it primarily focuses on data collection. CN118052469A discloses a comprehensive rainwater management method and system for sponge cities, emphasizing rainwater discharge control with limited attention to resource optimization. These existing technologies have failed to effectively address the core issue of dynamic resource matching in sponge cities.

[0004] Therefore, there is an urgent need to develop an intelligent sponge city resource matching system that can achieve comprehensive collection and fusion analysis of multi-source data, establish a dynamic risk assessment model, provide scientific resource allocation decision support, and have continuous optimization capabilities. Summary of the Invention

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] According to a first aspect of the present invention, the present invention claims protection for a resource matching system for sponge cities, comprising,

[0007] The resource acquisition unit collects past sponge structure data, water accumulation data, and matching sponge structures for the sponge city to be matched.

[0008] The first processing unit performs water accumulation risk alerts based on the water accumulation status of the sponge city to be matched during the assessment period, and performs first risk processing on the sponge city to be matched based on the water accumulation alert records.

[0009] The correction unit performs a first correction based on the precipitation time of the sponge city to be matched within the assessment period, and performs a second correction based on the number of times the sponge city to be matched did not have precipitation within the assessment period.

[0010] The second processing unit performs risk processing on the past resource allocation data of the sponge city to be matched based on the collected past resource allocation data of the sponge city to be matched, and performs a second risk processing on the sponge city based on the risky past resource allocation data of the sponge city to be matched.

[0011] The update unit performs an update based on the past resource allocation data of all sponge cities corresponding to the risk of the sponge city to be matched, and also performs a second update based on the number of resource allocations of the sponge city to be matched within the urban management period, to handle the second risk of the sponge city to be matched.

[0012] The matching unit performs time matching of sponge structures and resource allocation for the sponge city to be matched, based on the records of the first risk handling and the second risk handling of the sponge city to be matched.

[0013] The response unit performs a correction step for the next resource allocation time based on the number of risks in the resource allocation data parameters of the sponge city to be matched.

[0014] Furthermore, the first processing unit is equipped with a reminder processing module. This module compares the water accumulation status m0 of the sponge city to be matched within the evaluation time period with a preset water accumulation status m1, performs water accumulation risk processing based on the comparison record, and issues a water accumulation risk reminder based on the processing record. Specifically:

[0015] If m0≤m1, the reminder processing module diagnoses the water accumulation status of the sponge city to be matched as safe and does not issue a water accumulation risk reminder.

[0016] If m0 > m1, the reminder processing module diagnoses the risk of water accumulation in the sponge city to be matched and issues a water accumulation risk reminder.

[0017] The first processing unit further includes a first risk processing module. This module compares the number of water accumulation risk alerts (n0) within the assessment period with the preset number of alerts (n1), and performs first risk processing on the sponge city to be matched based on the comparison record. Specifically:

[0018] If n0≤n1, the first risk processing module diagnoses the safety of the number of water accumulation reminders for the sponge city to be matched;

[0019] If n0 > n1, the first risk processing module diagnoses the risk of the number of water accumulation reminders for the sponge city to be matched.

[0020] Furthermore, the correction unit includes a first correction unit, which performs the following steps: comparing the precipitation time z0 of the sponge city to be matched with the preset precipitation time z1 within the evaluation time period; performing risk processing on the precipitation time based on the comparison record; and performing a correction based on the processing record of the first risk processing of the sponge city to be matched.

[0021] If z0≤z1, the first correction unit diagnoses the safety of the rainfall time in the sponge city to be matched;

[0022] If z0 > z1, and if z0 - z1 ≤ z2, the first correction unit diagnoses the safety of the rainfall time of the sponge city to be matched. If z0 - z1 > z2, the first correction unit diagnoses the risk of the rainfall time of the sponge city to be matched, and corrects the first risk handling steps of the sponge city to be matched. The corrected preset reminder number is set to n1', and n1' = n1 × {1 + win[p0 × (π / 2) / p1]}.

[0023] Where p0 represents the number of rainfall events to be matched with sponge city during the assessment period, and p1 represents the number of days in the assessment period.

[0024] Furthermore, the correction unit includes a second correction module. This second correction module performs a second correction by comparing the number of days q0 without rainfall in the sponge city to be matched within the evaluation period with a preset number of days q1, and then performing a second correction based on the comparison record of the first risk handling steps for the sponge city to be matched. Specifically:

[0025] If q0≤q1, the second correction module diagnoses the number of days without precipitation in the sponge city to be matched as safe, and does not perform a second correction.

[0026] If q0 > q1, the second correction module diagnoses the risk of the number of days of precipitation in the sponge city to be matched, and performs a second correction on the first risk handling steps of the sponge city to be matched, setting the corrected preset reminder number to n1”, and setting n1” = n1' × [1 - 0.8 × (q0 - q1) / (q0 + q1)].

[0027] Furthermore, the second processing unit uses the collected past resource allocation data R of the sponge city to be matched within the urban management time period to further process the data. R r is compared with standard resource allocation data, and the risk of the past resource allocation data of the sponge city to be matched is processed based on the comparison records, where:

[0028] If R R r < Rr1 or R RIf r > Rr2, the second processing unit diagnoses the risk of the past resource allocation data of the sponge city to be matched. If Ri / (RZ×r)≤Rri0, the second processing unit diagnoses the sponge structure as a safe sponge structure. If Ri / (RZ×r)>Rri0, the second processing unit diagnoses the sponge structure as a risky sponge structure.

[0029] If Rr1≤R R If r≤Rr2, the second processing unit diagnoses the security of the past resource configuration data of the sponge city to be matched;

[0030] Among them, R R r represents the past resource configuration data of the r-th parameter of the R-th sponge city project R to be matched, 0 < R ≤ r, r represents the number of past resource configurations of the sponge city to be matched, R represents the category of sponge structure, 0 < r < RZ, RZ represents the number of resource configuration parameters of project R; Rr1 represents the minimum standard resource configuration data of the r-th parameter of project R, Rr2 represents the maximum standard resource configuration data of the r-th parameter of project R, and Ri represents the number of past resource configuration data of the sponge city to be matched in the risk of project R.

[0031] Furthermore, the updating unit includes a first updating unit, which executes the process of updating all sponge city past resource configuration data R corresponding to the risk past resource configuration data. R The mean value of "r" is calculated, and the calculated record is compared with the standard resource configuration data. Based on the comparison record, an update is performed as part of the second risk processing step for the sponge city to be matched.

[0032] If Rr 均 "<Rr1 or Rr 均 >Rr2, the first update unit updates the step of the second risk processing for the sponge city to be matched once, if Rr 均 "<Rr1, the first update unit sets the preset risk ratio to Rri0', and sets Rri0' = Rri0 × [1 - 0.23 × (Rr1 - Rr 均 ”) / (Rr1+Rr 均 ")], if Rr 均 >Rr2, the first update unit sets the preset risk ratio to Rri0", and sets Rri0" = Rri0 × [1 - 0.23 × (Rr 均 "-Rr2) / (Rr2+Rr 均 ")];

[0033] If Rr1≤Rr 均 If Rr2 ≤ Rr2, the first update unit will not perform an update;

[0034] Among them, Rr均 "=(Rr1”+Rr2”+...+Rrm”) / M, where Rr1” is the past resource allocation data of the first sponge city of the r-th parameter of project R, Rr2” is the past resource allocation data of the second sponge city of the r-th parameter of project R, Rrm” is the past resource allocation data of the m-th sponge city of the r-th parameter of project R, 0<m≤M, and M is the number of past resource allocation data of sponge cities of the r-th parameter of project R.

[0035] Furthermore, the updating unit also includes a second updating unit, which performs a second update by comparing the number of resource allocations n0 to be matched with the preset number of resource allocations n1 within the urban management time period, and performing a second risk handling on the sponge city to be matched based on the comparison record.

[0036] If n0 < n1, the second update unit diagnoses the risk of resource allocation times for the sponge city to be matched, and performs a second update on the steps of second risk handling for the sponge city to be matched, setting the updated preset risk ratio to Rri0”, and setting Rri0” = Rri0' × {1 + 0.75 × mrpzmn[(n1 - n0) / (n0 + n1) × (π / 4)]};

[0037] If n0 ≥ n1, the second update unit diagnoses the resource configuration count of the sponge city to be matched as safe and does not perform an update.

[0038] Furthermore, the matching unit compares the risky sponge structure k0 of the sponge city to be matched within the urban management time period with the number of each preset risk item, and performs sponge structure and resource allocation time matching for the sponge city to be matched based on the comparison record and the record of the first risk treatment of the sponge city to be matched, wherein:

[0039] If k≤k1, the matching unit diagnoses that the number of risky sponge structures in the sponge city to be matched is small. If the number of water accumulation reminders in the sponge city to be matched is safe, the matching unit does not perform resource allocation matching for the sponge city to be matched. If the number of water accumulation reminders in the sponge city to be matched is risky, the matching unit sets the matching resource allocation time to U1, sets U1=u0, and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource allocation time U1 and the matching sponge structure to the sponge city to be matched.

[0040] If k1 < k0 < k2, the matching unit diagnoses that the number of risky sponge structures in the sponge city to be matched is safe. If the number of water accumulation reminders in the sponge city to be matched is safe, the matching unit sets the matching resource configuration time to U2, sets U2 = u0, and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource configuration time U2 and the matching sponge structure to the sponge city to be matched. If the number of water accumulation reminders in the sponge city to be matched is risky, the matching unit sets the matching resource configuration time to U3, sets U3 = u0 × [1 - (n0 - n1) / (n0 + n1)], and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource configuration time U3 and the matching sponge structure to the sponge city to be matched.

[0041] If k0 ≥ k2, the matching unit diagnoses a large number of risky sponge structures in the sponge city to be matched. If the number of water accumulation warnings in the sponge city to be matched is safe, the matching unit sets the matching resource configuration time to U4, where U4 = u0 × [1 - 0.8 × (k0 - k2) / (k0 + k2)], and uses the risky sponge structures as matching sponge structures. The matching unit then pushes the matching resource configuration time U4 and the matching sponge structures to the sponge city to be matched. If the number of water accumulation warnings in the sponge city to be matched is risky, the matching unit sets the matching resource configuration time to U5, where U5 = u0 × [1 - (n0 - n1) / (n0 + n1)] × [1 - 0.8 × (k0 - k2) / (k0 + k2)], and uses the risky sponge structures and the matching sponge structures as matching sponge structures. The matching unit then pushes the matching resource configuration time U5 and the matching sponge structures to the sponge city to be matched.

[0042] Where k1 is the minimum number of preset risk items, k2 is the maximum number of preset risk items, and u0 is the preset resource allocation time.

[0043] Furthermore, the response unit compares the number w0 of the resource allocation data parameter risks of the sponge city to be matched with each preset risk coefficient, and corrects the matching steps for the next resource allocation time based on the comparison record, wherein:

[0044] If w0≤w1, the response unit diagnoses a small number of risk factors in the resource configuration data parameters of the sponge city to be matched, and corrects the matching steps of the next resource configuration time, setting the corrected preset resource configuration time as u0', and setting u0'=u0×[1+0.2×(w0-w1) / (w0+w1)];

[0045] If w1 < w0 < w2, the response unit diagnoses the number of risks in the resource configuration data parameters of the sponge city to be matched and does not perform correction.

[0046] If w0≥w1, the response unit diagnoses a large number of risk factors in the resource configuration data parameters of the sponge city to be matched, and corrects the matching step of the next resource configuration time, setting the corrected preset resource configuration time as u0”, and setting u0”=u0×[1-(w0-w1) / (w0+w1)];

[0047] Where w1 is the minimum preset risk coefficient and w2 is the preset maximum risk coefficient.

[0048] According to a second aspect of the present invention, the present invention claims protection for a resource matching method for sponge cities, applied to a resource matching system for sponge cities, characterized in that it includes,

[0049] Collect past sponge structure data, water accumulation data, and matching sponge structures for the sponge city to be matched;

[0050] Based on the water accumulation status of the sponge cities to be matched during the assessment period, water accumulation risk warnings are issued, and the first risk treatment is carried out on the sponge cities to be matched based on the water accumulation warning records.

[0051] The first step of handling the first risk of the sponge city to be matched is revised based on the precipitation time of the sponge city to be matched during the assessment period. The second step of handling the first risk of the sponge city to be matched is also revised based on the number of times the sponge city to be matched did not have precipitation during the assessment period.

[0052] Based on the collected past resource allocation data of the sponge cities to be matched, risk processing is performed on the past resource allocation data of the sponge cities to be matched, and a second risk processing is performed on the sponge cities based on the risky past resource allocation data of the sponge cities to be matched.

[0053] The process of handling the second risk of the sponge city to be matched is updated once based on the past resource allocation data of all sponge cities corresponding to the past resource allocation data of the sponge city to be matched. The process of handling the second risk of the sponge city to be matched is also updated a second time based on the number of resource allocations of the sponge city to be matched within the urban management period.

[0054] Based on the records of the first and second risk treatments of the sponge city to be matched, the sponge structure and resource allocation time of the sponge city to be matched are matched.

[0055] The matching steps for the next resource allocation time are corrected based on the number of risks in the resource allocation data parameters of the sponge city to be matched.

[0056] This invention discloses a resource matching method and system for sponge cities, belonging to the field of smart city management technology. The system includes a resource acquisition unit, a first processing unit, a correction unit, a second processing unit, an update unit, a matching unit, and a response unit. Through multi-dimensional data acquisition and dynamic risk assessment, the system achieves intelligent matching of sponge city resources. Specifically, it includes: a dynamic risk early warning mechanism based on water accumulation status and precipitation characteristics, optimizing the early warning threshold through secondary correction; risk analysis combined with historical resource allocation data; optimization of resource allocation strategies based on multi-source data updates; and adaptive resource matching schemes according to risk levels. This invention significantly improves the scientificity and efficiency of sponge city resource allocation by establishing a closed-loop optimized resource matching process, effectively solving problems such as data isolation, static assessment, and extensive decision-making in traditional methods, and providing an intelligent management tool for sponge city construction. Attached Figure Description

[0057] Figure 1 This is a schematic diagram of the structure of a resource matching system for sponge cities claimed in an embodiment of this application;

[0058] Figure 2 A schematic diagram of the second structure of a resource matching system for sponge cities claimed in an embodiment of this application;

[0059] Figure 3 This is a flowchart illustrating a resource matching method for sponge cities claimed in an embodiment of this application. Detailed Implementation

[0060] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0061] The terms "first," "second," and "third" in this application are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. All directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of this application are only used to explain the relative positional relationships and movements between components in a specific orientation (as shown in the figures). If the specific orientation changes, the directional indications also change accordingly. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a step, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these steps, methods, products, or devices.

[0062] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0063] Please see Figure 1 As shown, this is a schematic diagram of a resource matching system for sponge cities according to this embodiment. The system includes,

[0064] The resource acquisition unit collects past sponge structure data, water accumulation data, and matching sponge structures of the sponge city to be matched. In this embodiment, no specific limitation is made on the acquisition method of the past sponge structure data, water accumulation data, and matching sponge structures of the sponge city to be matched. Those skilled in the art can set it freely, as long as the acquisition requirements of the past sponge structure data, water accumulation data, and matching sponge structures of the sponge city to be matched are met. The past sponge structure data, water accumulation data, and matching sponge structures of the sponge city to be matched can be acquired interactively.

[0065] The first processing unit performs water accumulation risk alerts based on the water accumulation status of the sponge city to be matched collected during the assessment period, and performs first risk processing on the sponge city to be matched based on the water accumulation alert records. The first processing unit is connected to the resource collection unit. In this embodiment, the setting of the assessment period is not specifically limited. Those skilled in the art can set it freely, as long as the setting requirements of the assessment period are met. The assessment period can be set to 20 days, 30 days, and 40 days, etc.

[0066] In this embodiment, the first processing unit collects and compares water accumulation data, collecting real-time water accumulation depth m0 (unit: cm), and presets a safety threshold m1=15cm (according to the "Urban Drainage Design Code").

[0067] Judgment logic:

[0068] if m0 <= 15:

[0069] return "safe status"

[0070] else:

[0071] trigger_alert("Risk of water accumulation, it is recommended to check drainage facilities") # Push to the management platform;

[0072] The number of risk alerts within 30 days is counted (n0), with a preset threshold of n1=3.

[0073] Handling measures:

[0074] If n0 > 3, generate a high-risk area report and mark facilities that need priority renovation (such as increasing the area of ​​permeable pavement).

[0075] The correction unit performs a first correction based on the precipitation time of the sponge city to be matched within the collected assessment period, and performs a second correction based on the number of times the sponge city to be matched did not have precipitation within the assessment period, and the correction unit is connected to the first processing unit.

[0076] In this embodiment, the precipitation time correction unit is used to correct the precipitation time. The ideal precipitation time is preset to z1=8:00 (to avoid water accumulation during morning and evening rush hours), and the allowable deviation is z2=2h.

[0077] Correction formula:

[0078] n1' = n1 × [1 + (Number of abnormal precipitation events / Total number of days)] # Linearly adjusted threshold

[0079] Example: If there are 3 nighttime rainstorms within 10 days (z0=22:00), then n1'=3×1.3=3.9 (rounded up to 4 times).

[0080] The correction unit also corrects for the number of days without precipitation.

[0081] The preset allowable number of consecutive days without precipitation is q1=5 days; if this number is exceeded, the risk threshold is lowered.

[0082] n1” = n1' × [1 - 0.5×(q0 - q1) / q0] # Reduce false alarms during drought periods.

[0083] The second processing unit performs risk processing on the past resource allocation data of the sponge city to be matched based on the collected past resource allocation data of the sponge city to be matched, and performs a second risk processing on the sponge city based on the risky past resource allocation data of the sponge city to be matched. The second processing unit is connected to the correction unit.

[0084] The update unit performs an update based on the past resource allocation data of all sponge cities corresponding to the risk of the sponge city to be matched, and performs a second update based on the number of resource allocations of the sponge city to be matched within the urban management period, to address the second risk of the sponge city to be matched. The update unit is connected to the second processing unit. In this embodiment, the setting of the urban management period is not specifically limited. Those skilled in the art can set it freely, as long as the requirements for setting the urban management period are met. It is worth noting that the setting time of the urban management period should be longer than the setting time of the evaluation period. The urban management period can be set to 1 year, 2 years, 3 years, etc.

[0085] In this embodiment, a sponge structure refers to infrastructure with rainwater infiltration, storage, or purification functions, including but not limited to:

[0086] Permeable pavement (such as permeable asphalt and permeable concrete);

[0087] Bioretention facilities (such as rain gardens and ecological tree pits);

[0088] Water storage modules (such as underground water storage tanks and regulating reservoirs);

[0089] Green roof;

[0090] Resource configuration data parameters include the following quantifiable indicators in Table 1:

[0091] Table 1 Resource Configuration Data Parameter Table

[0092] Parameter type illustrate unit Construction costs Cost per unit area of ​​facilities 10,000 yuan / m² Penetration Rainwater infiltration rate mm / h Maintenance frequency Annual maintenance count Next / Year Service life Effective service life of facilities Year

[0093] The matching unit performs time matching of sponge structure and resource allocation for the sponge city to be matched based on the records of the first risk processing and the second risk processing of the sponge city to be matched. The matching unit is connected to the update unit.

[0094] In this embodiment, the matching unit performs resource configuration matching using a matching rule table, as shown in Table 2.

[0095] Table 2 Matching Rules Table

[0096] Risk level Matching facility types Resource allocation time (days) Low risk (k0≤2) Permeable pavement 30 Medium risk (2) <k0<4) Bioretention tank 20 High risk (k0≥4) Water storage modules + green roof 10

[0097] The response unit performs a correction step for the next resource allocation time based on the number of risk parameters of the resource allocation data parameters of the sponge city to be matched. The response unit is connected to the matching unit. In this embodiment, the method of collecting the number of risk parameters of the resource allocation data parameters of the resource allocation to be matched is not specifically limited. Those skilled in the art can set it freely, as long as the collection requirements of the number of risk parameters of the resource allocation data parameters of the resource allocation to be matched are met. The number of risk parameters of the resource allocation data parameters of the resource allocation to be matched can be collected interactively.

[0098] In this embodiment, the water accumulation data is collected in real time by an IoT water level sensor (such as an ultrasonic water level gauge), and the unit is cm.

[0099] Precipitation data is obtained by accessing the meteorological bureau's API to obtain the timing and duration of precipitation.

[0100] The first processing unit includes,

[0101] The reminder processing module performs water accumulation risk reminders based on the water accumulation status of the sponge cities to be matched during the assessment period.

[0102] The first risk processing module performs first risk processing on the sponge city to be matched based on the water accumulation reminder records within the assessment period. The first risk processing module is connected to the reminder processing module.

[0103] The correction unit includes,

[0104] The first correction unit performs a correction based on the precipitation time of the sponge city to be matched within the collected assessment period to perform the first risk handling steps for the sponge city to be matched.

[0105] The second correction module performs a second correction based on the number of times the sponge city to be matched experienced no rainfall during the assessment period, and performs the first risk treatment steps for the sponge city to be matched. The second correction module is connected to the first correction unit.

[0106] Please see Figure 2As shown, this is a schematic diagram of the structure of the update unit in this embodiment. The update unit includes,

[0107] The data collection unit collects all past resource allocation data of sponge cities corresponding to the past resource allocation data of the sponge city risk to be matched. In this embodiment, the method of collecting all past resource allocation data of sponge cities corresponding to the past resource allocation data of the sponge city risk to be matched is not specifically limited. Those skilled in the art can set it freely, as long as the collection requirements of all past resource allocation data of sponge cities corresponding to the past resource allocation data of the sponge city risk to be matched are met. The past resource allocation data of sponge cities corresponding to the past resource allocation data of the sponge city risk to be matched can be imported and collected through the background data of the resource allocation platform.

[0108] The first update unit performs an update based on the second risk processing step of the sponge city to be matched, according to all past resource allocation data of sponge cities corresponding to the past resource allocation data of the sponge city to be matched for risk. The first update unit is connected to the acquisition unit.

[0109] The second update unit performs a second update based on the number of times the resources of the sponge city to be matched are allocated within the urban management time period, and performs a second risk handling step for the sponge city to be matched. The second update unit is connected to the first update unit.

[0110] Specifically, this embodiment is applied to resource allocation and matching for sponge cities. It performs risk processing on the water accumulation and precipitation data of sponge cities, and performs secondary processing on sponge cities based on their past resource allocation data. Combining the records of the two risk processing, the invention performs resource allocation and matching for sponge cities from multiple dimensions, thereby improving the accuracy and efficiency of resource allocation and matching for sponge cities.

[0111] Specifically, the reminder processing module compares the water accumulation status m0 of the sponge city to be matched within the evaluation time period with the preset water accumulation status m1, performs water accumulation risk processing based on the comparison record, and issues water accumulation risk reminders based on the processing record, wherein:

[0112] If m0≤m1, the reminder processing module diagnoses the water accumulation status of the sponge city to be matched as safe and does not issue a water accumulation risk reminder.

[0113] If m0 > m1, the reminder processing module diagnoses the risk of water accumulation in the sponge city to be matched and issues a water accumulation risk reminder.

[0114] Specifically, the reminder processing module improves the accuracy of water accumulation risk handling by setting a preset water accumulation state, thereby improving the accuracy of water accumulation risk reminders, which in turn improves the accuracy of the first risk handling for the sponge city to be matched, and ultimately improves the accuracy and efficiency of resource allocation and matching for the sponge city to be matched. In this embodiment, the value of the preset water accumulation state is not specifically limited. Those skilled in the art can set it freely, as long as the setting requirements of the preset water accumulation state are met. The optimal value of the preset water accumulation state is 6.1 mmol / L.

[0115] Specifically, the first risk processing module compares the number of water accumulation risk alerts n0 within the assessment period with the preset number of alerts n1, and performs the first risk processing on the sponge city to be matched based on the comparison record, wherein:

[0116] If n0≤n1, the first risk processing module diagnoses the safety of the number of water accumulation reminders for the sponge city to be matched;

[0117] If n0 > n1, the first risk processing module diagnoses the risk of the number of water accumulation reminders for the sponge city to be matched.

[0118] Specifically, the first risk handling module improves the accuracy of water accumulation risk warnings by setting a preset number of reminders, thereby improving the accuracy of the first risk handling for the sponge city to be matched, and ultimately improving the accuracy and efficiency of resource allocation and matching for the sponge city to be matched. In this embodiment, the value of the preset number of reminders is not specifically limited. Those skilled in the art can set it freely, as long as the setting requirements of the preset number of reminders are met. For example, if the evaluation period is 30 days, the optimal value of the preset number of reminders is 3.

[0119] Specifically, the first correction unit compares the precipitation time z0 of the sponge city to be matched with the preset precipitation time z1 within the evaluation period, performs risk processing on the precipitation time based on the comparison record, and corrects the first risk processing step of the sponge city to be matched based on the processing record, wherein:

[0120] If z0≤z1, the first correction unit diagnoses the safety of the rainfall time in the sponge city to be matched;

[0121] If z0 > z1, and if z0 - z1 ≤ z2, the first correction unit diagnoses the safety of the rainfall time of the sponge city to be matched. If z0 - z1 > z2, the first correction unit diagnoses the risk of the rainfall time of the sponge city to be matched, and corrects the first risk handling steps of the sponge city to be matched. The corrected preset reminder number is set to n1', and n1' = n1 × {1 + win[p0 × (π / 2) / p1]}.

[0122] Where p0 is the number of sponge city precipitation time risks to be matched within the assessment period, p1 is the number of days in the assessment period, and z2 is the preset time difference.

[0123] Specifically, the first correction unit improves the accuracy of water accumulation risk warning by setting a preset time difference, thereby improving the accuracy of the first risk handling for the sponge city to be matched, and ultimately improving the accuracy and efficiency of resource allocation and matching for the sponge city to be matched. In this embodiment, the values ​​of the preset time difference and the preset precipitation time are not specifically limited. Those skilled in the art can set them freely, as long as the value requirements of the preset time difference and the preset precipitation time are met. The optimal value of z1 is 8 o'clock, and the optimal value of z2 is 2h.

[0124] Specifically, the second correction module compares the number of days q0 without rainfall in the sponge city to be matched within the evaluation period with the preset number of days q1, and performs a second correction based on the comparison record of the first risk handling steps of the sponge city to be matched, wherein:

[0125] If q0≤q1, the second correction module diagnoses the number of days without precipitation in the sponge city to be matched as safe, and does not perform a second correction.

[0126] If q0 > q1, the second correction module diagnoses the risk of the number of days of precipitation in the sponge city to be matched, and performs a second correction on the first risk handling steps of the sponge city to be matched, setting the corrected preset reminder number to n1”, and setting n1” = n1' × [1 - 0.8 × (q0 - q1) / (q0 + q1)].

[0127] Specifically, the second correction module improves the accuracy of water accumulation risk warnings by setting a preset number of days, thereby improving the accuracy of the first risk handling for the matching sponge cities and ultimately improving the accuracy and efficiency of resource allocation and matching for the matching sponge cities. In this embodiment, the value of the preset number of days is not specifically limited. Those skilled in the art can set it freely, as long as the value of the preset number of days is met. If the evaluation period is 30 days, the optimal value of q1 is 3.

[0128] Specifically, the second processing unit uses the collected past resource allocation data R of the sponge city to be matched within the urban management time period. R r is compared with standard resource allocation data, and the risk of the past resource allocation data of the sponge city to be matched is processed based on the comparison records, where:

[0129] If R R r < Rr1 or R RIf r > Rr2, the second processing unit diagnoses the risk of the past resource allocation data of the sponge city to be matched. If Ri / (RZ×r)≤Rri0, the second processing unit diagnoses the sponge structure as a safe sponge structure. If Ri / (RZ×r)>Rri0, the second processing unit diagnoses the sponge structure as a risky sponge structure.

[0130] If Rr1≤R R If r≤Rr2, the second processing unit diagnoses the security of the past resource configuration data of the sponge city to be matched;

[0131] Among them, R R r represents the past resource configuration data of the r-th parameter of the R-th sponge city project R to be matched, 0 < r < RZ, where RZ is the number of resource configuration parameters of project R; Rr1 represents the minimum standard resource configuration data of the r-th parameter of project R, Rr2 represents the maximum standard resource configuration data of the r-th parameter of project R, Ri represents the number of past resource configuration data of the sponge city to be matched in project R, and Rri0 represents the preset risk ratio.

[0132] Specifically, the second processing unit improves the accuracy of the second risk processing for the sponge cities to be matched by setting a preset risk ratio. This allows for risk processing of the sponge cities to be matched from multiple dimensions, improving the accuracy and efficiency of resource allocation and matching for the sponge cities. In this embodiment, the value of the preset risk ratio is not specifically limited; those skilled in the art can set it freely, as long as the requirements for setting the preset risk ratio are met. The optimal value for the preset risk ratio is 0.25. It is worth noting that this embodiment does not specifically limit the setting of the standard resource configuration data; those skilled in the art can set it freely, as long as the requirements for setting the standard resource configuration data are met. The standard resource configuration data can be set interactively.

[0133] Specifically, the first update unit calculates the average of all past resource allocation data (RRr) corresponding to the past resource allocation data of the sponge city to be matched for risk, compares the calculated data with the standard resource allocation data, and updates the data based on the comparison records to perform the second risk processing step for the sponge city to be matched.

[0134] If Rr_average" < Rr1 or Rr_average" > Rr2, the first update unit updates the second risk processing step for the sponge city to be matched. If Rr_average" < Rr1, the first update unit sets the preset risk ratio to Rri0', and sets Rri0' = Rri0 × [1 - 0.23 × (Rr1 - Rr_average") / (Rr1 + Rr_average")]. If Rr_average" > Rr2, the first update unit sets the preset risk ratio to Rri0", and sets Rri0" = Rri0 × [1 - 0.23 × (Rr_average" - Rr2) / (Rr2 + Rr_average")].

[0135] If Rr1 ≤ Rr1 ≤ Rr2, the first update unit does not perform an update.

[0136] Where Rr_u_u = (Rr1_u + Rr2_u + ... + Rrm_u_u) / M, Rr1_u_u is the past resource allocation data of the first sponge city of the r-th parameter of project R, Rr2_u_u is the past resource allocation data of the second sponge city of the r-th parameter of project R, Rrm_u_u_u is the past resource allocation data of the m-th sponge city of the r-th parameter of project R, 0 < m ≤ M, and M is the number of past resource allocation data of sponge cities of the r-th parameter of project R.

[0137] Specifically, the first update unit processes the past resource allocation data of all sponge cities corresponding to the risk past resource allocation data of the sponge city to be matched, so as to improve the accuracy of the second risk processing of the sponge city to be matched. This allows for risk processing of the sponge city to be matched from multiple dimensions, thereby improving the accuracy and efficiency of resource allocation matching for the sponge city to be matched.

[0138] Specifically, the second update unit compares the number of resource allocations n0 for the sponge city to be matched within the urban management time period with the preset number of resource allocations n1, and performs a second update based on the comparison record for the second risk handling steps of the sponge city to be matched, wherein:

[0139] If n0 < n1, the second update unit diagnoses the risk of resource allocation times for the sponge city to be matched, and performs a second update on the steps of second risk handling for the sponge city to be matched, setting the updated preset risk ratio to Rri0”, and setting Rri0” = Rri0' × {1 + 0.75 × mrpzmn[(n1 - n0) / (n0 + n1) × (π / 4)]};

[0140] If n0 ≥ n1, the second update unit diagnoses the resource configuration count of the sponge city to be matched and does not perform an update.

[0141] Specifically, the second update unit improves the accuracy of the second risk handling for the sponge city to be matched by setting a preset number of resource configurations. This allows for risk handling of the sponge city to be matched from multiple dimensions, improving the accuracy and efficiency of resource allocation and matching for the sponge city to be matched. In this embodiment, the value of the preset number of resource configurations is not specifically limited. Those skilled in the art can set it freely, as long as the setting requirements of the preset number of resource configurations are met. If the city management period is 2 years, the optimal value of the preset number of resource configurations is 8.

[0142] Specifically, the matching unit compares the risky sponge structure k0 of the sponge city to be matched within the urban management time period with the number of each preset risk item, and matches the sponge structure and resource allocation time of the sponge city to be matched based on the comparison record and the record of the first risk treatment of the sponge city to be matched, wherein:

[0143] If k≤k1, the matching unit diagnoses that the number of risky sponge structures in the sponge city to be matched is small. If the number of water accumulation reminders in the sponge city to be matched is safe, the matching unit does not perform resource allocation matching for the sponge city to be matched. If the number of water accumulation reminders in the sponge city to be matched is risky, the matching unit sets the matching resource allocation time to U1, sets U1=u0, and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource allocation time U1 and the matching sponge structure to the sponge city to be matched.

[0144] If k1 < k0 < k2, the matching unit diagnoses that the number of risky sponge structures in the sponge city to be matched is safe. If the number of water accumulation reminders in the sponge city to be matched is safe, the matching unit sets the matching resource configuration time to U2, sets U2 = u0, and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource configuration time U2 and the matching sponge structure to the sponge city to be matched. If the number of water accumulation reminders in the sponge city to be matched is risky, the matching unit sets the matching resource configuration time to U3, sets U3 = u0 × [1 - (n0 - n1) / (n0 + n1)], and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource configuration time U3 and the matching sponge structure to the sponge city to be matched.

[0145] If k0 ≥ k2, the matching unit diagnoses a large number of risky sponge structures in the sponge city to be matched. If the number of water accumulation warnings in the sponge city to be matched is safe, the matching unit sets the matching resource configuration time to U4, where U4 = u0 × [1 - 0.8 × (k0 - k2) / (k0 + k2)], and uses the risky sponge structures as matching sponge structures. The matching unit then pushes the matching resource configuration time U4 and the matching sponge structures to the sponge city to be matched. If the number of water accumulation warnings in the sponge city to be matched is risky, the matching unit sets the matching resource configuration time to U5, where U5 = u0 × [1 - (n0 - n1) / (n0 + n1)] × [1 - 0.8 × (k0 - k2) / (k0 + k2)], and uses the risky sponge structures and the matching sponge structures as matching sponge structures. The matching unit then pushes the matching resource configuration time U5 and the matching sponge structures to the sponge city to be matched.

[0146] Where k1 is the minimum number of preset risk items, k2 is the maximum number of preset risk items, and u0 is the preset resource allocation time.

[0147] Specifically, the matching unit improves the accuracy and efficiency of resource allocation matching for sponge cities by setting a preset number of risk items. It can be understood that the preset resource allocation time in this embodiment is u0 days after the push ends. This embodiment does not specifically limit the setting of the preset number of risk items and the preset resource allocation time. Those skilled in the art can set them freely, as long as the setting requirements of the preset number of risk items and the preset resource allocation time are met. The optimal value of k1 is 2, the optimal value of k2 is 4, and the optimal value of u0 is 30 days.

[0148] Specifically, the response unit compares the number w0 of the resource allocation data parameter risks of the sponge city to be matched with each preset risk coefficient, and corrects the matching steps for the next resource allocation time based on the comparison record, wherein:

[0149] If w0≤w1, the response unit diagnoses a small number of risk factors in the resource configuration data parameters of the sponge city to be matched, and corrects the matching steps of the next resource configuration time, setting the corrected preset resource configuration time as u0', and setting u0'=u0×[1+0.2×(w0-w1) / (w0+w1)];

[0150] If w1 < w0 < w2, the response unit diagnoses the number of risks in the resource configuration data parameters of the sponge city to be matched and does not perform correction.

[0151] If w0≥w1, the response unit diagnoses a large number of risk factors in the resource configuration data parameters of the sponge city to be matched, and corrects the matching step of the next resource configuration time, setting the corrected preset resource configuration time as u0”, and setting u0”=u0×[1-(w0-w1) / (w0+w1)];

[0152] Where w1 is the minimum preset risk coefficient and w2 is the preset maximum risk coefficient.

[0153] Specifically, the response unit improves the accuracy of the next resource allocation time matching by setting a preset risk coefficient, thereby improving the accuracy and efficiency of resource allocation matching for the sponge city to be matched. In this embodiment, the setting of the preset risk coefficient is not specifically limited. Those skilled in the art can set it freely, as long as the setting requirements of the preset risk coefficient are met. The optimal value of w1 is 3, and the optimal value of w2 is 6.

[0154] According to a second embodiment of the present invention, referring to Figure 3 This invention claims protection for a resource matching method for sponge cities, applied to a resource matching system for sponge cities, comprising,

[0155] Collect past sponge structure data, water accumulation data, and matching sponge structures for the sponge city to be matched;

[0156] Based on the water accumulation status of the sponge cities to be matched during the assessment period, water accumulation risk warnings are issued, and the first risk treatment is carried out on the sponge cities to be matched based on the water accumulation warning records.

[0157] The first step of handling the first risk of the sponge city to be matched is revised based on the precipitation time of the sponge city to be matched during the assessment period. The second step of handling the first risk of the sponge city to be matched is also revised based on the number of times the sponge city to be matched did not have precipitation during the assessment period.

[0158] Based on the collected past resource allocation data of the sponge cities to be matched, risk processing is performed on the past resource allocation data of the sponge cities to be matched, and a second risk processing is performed on the sponge cities based on the risky past resource allocation data of the sponge cities to be matched.

[0159] The process of handling the second risk of the sponge city to be matched is updated once based on the past resource allocation data of all sponge cities corresponding to the past resource allocation data of the sponge city to be matched. The process of handling the second risk of the sponge city to be matched is also updated a second time based on the number of resource allocations of the sponge city to be matched within the urban management period.

[0160] Based on the records of the first and second risk treatments of the sponge city to be matched, the sponge structure and resource allocation time of the sponge city to be matched are matched.

[0161] The matching steps for the next resource allocation time are corrected based on the number of risks in the resource allocation data parameters of the sponge city to be matched.

[0162] The following is a specific example:

[0163] Permeable pavement matching process:

[0164] Data input:

[0165] If the water depth m0=18cm (exceeding m1=15cm), warnings will be issued n0=4 times within 30 days.

[0166] Resource allocation parameters: penetration rate requirement ≥ 20 mm / h, cost ≤ 12,000 yuan / m².

[0167] System output:

[0168] Matching result: Permeable concrete (permeability 25mm / h, cost 0.9 million yuan / m²).

[0169] Configuration time: U3 = 20 days (dynamically calculated based on n0 and k0).

[0170] Response to extreme precipitation events:

[0171] Scenario: Three consecutive days of heavy rain (rainfall time z0=23:00, exceeding z1±z2).

[0172] System actions:

[0173] The warning threshold has been adjusted to n1'=5 times.

[0174] Emergency response plan: Deployment of temporary storage tanks (to be completed within 48 hours).

[0175] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0176] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units. The above are merely embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made based on the description and drawings of this application, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

[0177] The specific embodiments of the invention have been described in detail above, but they are only examples, and this application is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications or substitutions to the invention are also within the scope of this application. Therefore, all equivalent changes, modifications, and improvements made without departing from the spirit and principles of this application should be covered within the scope of this application.

Claims

1. A resource matching system for sponge cities, characterized in that, include, The resource acquisition unit collects past sponge structure data, water accumulation data, and matching sponge structures for the sponge city to be matched. The first processing unit performs water accumulation risk alerts based on the water accumulation status of the sponge city to be matched during the assessment period, and performs first risk processing on the sponge city to be matched based on the water accumulation alert records. The correction unit performs a first correction based on the precipitation time of the sponge city to be matched within the collected assessment period, and performs a second correction based on the number of times the sponge city to be matched did not have precipitation within the assessment period, in order to handle the first risk of the sponge city to be matched. The second processing unit performs risk processing on the past resource allocation data of the sponge city to be matched based on the collected past resource allocation data of the sponge city to be matched, and performs a second risk processing on the sponge city based on the risky past resource allocation data of the sponge city to be matched. The update unit performs an update based on the past resource allocation data of all sponge cities corresponding to the risk of the sponge city to be matched, and also performs a second update based on the number of resource allocations of the sponge city to be matched within the urban management period, to handle the second risk of the sponge city to be matched. The matching unit performs time matching of sponge structures and resource allocation for the sponge city to be matched, based on the records of the first risk handling and the second risk handling of the sponge city to be matched. The response unit performs a correction step for the next resource allocation time based on the number of risks in the resource allocation data parameters of the sponge city to be matched.

2. The resource matching system for sponge cities as described in claim 1, characterized in that, The first processing unit is equipped with a reminder processing module. This module compares the water accumulation status m0 of the sponge city to be matched within the evaluation time period with a preset water accumulation status m1, performs water accumulation risk processing based on the comparison record, and issues a water accumulation risk reminder based on the processing record. Specifically: If m0≤m1, the reminder processing module diagnoses the water accumulation status of the sponge city to be matched as safe and does not issue a water accumulation risk reminder. If m0 > m1, the reminder processing module diagnoses the risk of water accumulation in the sponge city to be matched and issues a water accumulation risk reminder. The first processing unit further includes a first risk processing module. This module compares the number of water accumulation risk alerts (n0) within the assessment period with the preset number of alerts (n1), and performs first risk processing on the sponge city to be matched based on the comparison record. Specifically: If n0≤n1, the first risk processing module diagnoses the safety of the number of water accumulation reminders for the sponge city to be matched; If n0 > n1, the first risk processing module diagnoses the risk of the number of water accumulation reminders for the sponge city to be matched.

3. The resource matching system for sponge cities as described in claim 2, characterized in that, The correction unit includes a first correction unit, which performs the following steps: comparing the precipitation time z0 of the sponge city to be matched with the preset precipitation time z1 within the evaluation period; performing risk processing on the precipitation time based on the comparison record; and performing a correction based on the processing record of the first risk processing of the sponge city to be matched. If z0≤z1, the first correction unit diagnoses the safety of the rainfall time in the sponge city to be matched; If z0 > z1, and z0 - z1 ≤ z2, the first correction unit diagnoses the safety of the rainfall time of the sponge city to be matched. If z0 - z1 > z2, the first correction unit diagnoses the risk of the rainfall time of the sponge city to be matched, and corrects the first risk handling step of the sponge city to be matched, setting the corrected preset reminder number to n1'.

4. The resource matching system for sponge cities as described in claim 3, characterized in that, The correction unit includes a second correction module. This second correction module compares the number of days q0 without rainfall in the sponge city to be matched within the evaluation period with a preset number of days q1, and performs a second correction based on the comparison record and the first risk handling steps for the sponge city to be matched. Specifically: If q0≤q1, the second correction module diagnoses the number of days without precipitation in the sponge city to be matched as safe, and does not perform a second correction. If q0 > q1, the second correction module diagnoses the risk of the number of days of precipitation in the sponge city to be matched, and performs a second correction on the first risk handling steps of the sponge city to be matched, setting the corrected preset reminder number to n1”, and setting n1” = n1' × [1 - 0.8 × (q0 - q1) / (q0 + q1)].

5. The resource matching system for sponge cities as described in claim 1, characterized in that, The second processing unit uses the collected past resource allocation data R of the sponge city to be matched within the urban management time period. R r is compared with standard resource allocation data, and the risk of the past resource allocation data of the sponge city to be matched is processed based on the comparison records, where: If R R r < Rr1 or R R If r > Rr2, the second processing unit diagnoses the risk of the past resource allocation data of the sponge city to be matched. If Ri / (RZ×r)≤Rri0, the second processing unit diagnoses the sponge structure as a safe sponge structure. If Ri / (RZ×r)>Rri0, the second processing unit diagnoses the sponge structure as a risky sponge structure. If Rr1≤R R If r≤Rr2, the second processing unit diagnoses the security of the past resource configuration data of the sponge city to be matched; Among them, R R r represents the past resource allocation data of the r-th parameter of the R-th sponge city project R to be matched, 0 < r < RZ, where RZ is the number of resource allocation parameters of project R; Rr1 represents the minimum standard resource allocation data of the r-th parameter of project R, Rr2 represents the maximum standard resource allocation data of the r-th parameter of project R, and Ri represents the number of past resource allocation data of the sponge city to be matched in project R for risk.

6. The resource matching system for sponge cities as described in claim 1, characterized in that, The updating unit includes a first updating unit, which executes the process of updating all sponge city past resource configuration data R corresponding to the risk past resource configuration data. R The mean value of "r" is calculated, and the calculated record is compared with the standard resource configuration data. Based on the comparison record, an update is performed as part of the second risk processing step for the sponge city to be matched. If Rr 均 "<Rr1 or Rr 均 >Rr2, the first update unit performs an update on the second risk processing step for the sponge city to be matched, if Rr 均 "<Rr1, the first update unit sets the preset risk ratio to Rri0', and sets Rri0' = Rri0 × [1 - 0.23 × (Rr1 - Rr 均 ”) / (Rr1+Rr 均 ")], if Rr 均 >Rr2, the first update unit sets the preset risk ratio to Rri0", and sets Rri0" = Rri0 × [1 - 0.23 × (Rr 均 "-Rr2) / (Rr2+Rr 均 ")]; If Rr1≤Rr 均 If Rr2 ≤ Rr2, the first update unit will not perform an update; Among them, Rr 均 "=(Rr1”+Rr2”+...+Rrm”) / M, where Rr1” is the past resource allocation data of the first sponge city of the r-th parameter of project R, Rr2” is the past resource allocation data of the second sponge city of the r-th parameter of project R, Rrm” is the past resource allocation data of the m-th sponge city of the r-th parameter of project R, 0<m≤M, and M is the number of past resource allocation data of sponge cities of the r-th parameter of project R.

7. The resource matching system for sponge cities as described in claim 6, characterized in that, The updating unit further includes a second updating unit, which performs a second update by comparing the number of resource allocations n0 to be matched for sponge cities within the urban management time period with the preset number of resource allocations n1, and performing a second risk handling for the sponge cities to be matched based on the comparison record. If n0 < n1, the second update unit diagnoses the risk of resource allocation times for the sponge city to be matched, and performs a second update on the steps of the second risk handling for the sponge city to be matched, setting the updated preset risk ratio to Rri0”. If n0 ≥ n1, the second update unit diagnoses the resource configuration count of the sponge city to be matched as safe and does not perform an update.

8. The resource matching system for sponge cities as described in claim 3, characterized in that, The matching unit compares the risky sponge structure k0 of the sponge city to be matched within the urban management time period with the number of each preset risk item, and matches the sponge structure and resource allocation time of the sponge city to be matched based on the comparison record and the record of the first risk treatment of the sponge city to be matched, wherein: If k≤k1, the matching unit diagnoses that the number of risky sponge structures in the sponge city to be matched is small. If the number of water accumulation reminders in the sponge city to be matched is safe, the matching unit does not perform resource allocation matching for the sponge city to be matched. If the number of water accumulation reminders in the sponge city to be matched is risky, the matching unit sets the matching resource allocation time to U1, sets U1=u0, and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource allocation time U1 and the matching sponge structure to the sponge city to be matched. If k1 < k0 < k2, the matching unit diagnoses that the number of risky sponge structures in the sponge city to be matched is safe. If the number of water accumulation reminders in the sponge city to be matched is safe, the matching unit sets the matching resource configuration time to U2, sets U2 = u0, and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource configuration time U2 and the matching sponge structure to the sponge city to be matched. If the number of water accumulation reminders in the sponge city to be matched is risky, the matching unit sets the matching resource configuration time to U3, sets U3 = u0 × [1 - (n0 - n1) / (n0 + n1)], and uses the risky sponge structure as the matching sponge structure. The matching unit pushes the matching resource configuration time U3 and the matching sponge structure to the sponge city to be matched. If k0 ≥ k2, the matching unit diagnoses a large number of risky sponge structures in the sponge city to be matched. If the number of water accumulation warnings in the sponge city to be matched is safe, the matching unit sets the matching resource configuration time to U4, where U4 = u0 × [1 - 0.8 × (k0 - k2) / (k0 + k2)], and uses the risky sponge structures as matching sponge structures. The matching unit then pushes the matching resource configuration time U4 and the matching sponge structures to the sponge city to be matched. If the number of water accumulation warnings in the sponge city to be matched is risky, the matching unit sets the matching resource configuration time to U5, where U5 = u0 × [1 - (n0 - n1) / (n0 + n1)] × [1 - 0.8 × (k0 - k2) / (k0 + k2)], and uses the risky sponge structures and the matching sponge structures as matching sponge structures. The matching unit then pushes the matching resource configuration time U5 and the matching sponge structures to the sponge city to be matched. Where k1 is the minimum number of preset risk items, k2 is the maximum number of preset risk items, and u0 is the preset resource allocation time.

9. The resource matching system for sponge cities as described in claim 8, characterized in that, The response unit compares the number w0 of the risk parameters of the resource allocation data parameters of the sponge city to be matched with each preset risk coefficient, and corrects the matching steps for the next resource allocation time according to the comparison record, wherein: If w0≤w1, the response unit diagnoses a small number of risk factors in the resource configuration data parameters of the sponge city to be matched, and corrects the matching steps of the next resource configuration time, setting the corrected preset resource configuration time as u0', and setting u0'=u0×[1+0.2×(w0-w1) / (w0+w1)]; If w1 < w0 < w2, the response unit diagnoses the number of risks in the resource configuration data parameters of the sponge city to be matched and does not perform correction. If w0≥w1, the response unit diagnoses a large number of risk factors in the resource configuration data parameters of the sponge city to be matched, and corrects the matching step of the next resource configuration time, setting the corrected preset resource configuration time as u0”, and setting u0”=u0×[1-(w0-w1) / (w0+w1)]; Where w1 is the minimum preset risk coefficient and w2 is the preset maximum risk coefficient.

10. A resource matching method for sponge cities, applied to a resource matching system for sponge cities as described in any one of claims 1-9, characterized in that, include, Collect past sponge structure data, water accumulation data, and matching sponge structures for the sponge city to be matched; Based on the water accumulation status of the sponge cities to be matched during the assessment period, water accumulation risk warnings are issued, and the first risk treatment is carried out on the sponge cities to be matched based on the water accumulation warning records. The first step of handling the first risk of the sponge city to be matched is revised based on the precipitation time of the sponge city to be matched during the assessment period. The second step of handling the first risk of the sponge city to be matched is also revised based on the number of times the sponge city to be matched did not have precipitation during the assessment period. Based on the collected past resource allocation data of the sponge cities to be matched, risk processing is performed on the past resource allocation data of the sponge cities to be matched, and a second risk processing is performed on the sponge cities based on the risky past resource allocation data of the sponge cities to be matched. The process of handling the second risk of the sponge city to be matched is updated once based on the past resource allocation data of all sponge cities corresponding to the past resource allocation data of the sponge city to be matched. The process of handling the second risk of the sponge city to be matched is also updated a second time based on the number of resource allocations of the sponge city to be matched within the urban management period. Based on the records of the first and second risk treatments of the sponge city to be matched, the sponge structure and resource allocation time of the sponge city to be matched are matched. The matching steps for the next resource allocation time are corrected based on the number of risks in the resource allocation data parameters of the sponge city to be matched.

Images