feat: 制式标注改为2.6G/700M/TDD/FDD

This commit is contained in:
2026-08-11 16:45:32 +08:00
parent 87a66a88ae
commit eca4c5cbb1
4 changed files with 38 additions and 18 deletions
+7
View File
@@ -109,6 +109,13 @@
- The current `2026-08-07 14:00:00` database result was exported directly through the history-only path and replaced in Storage as a verified GBK CSV: 1,082 rows, 150,251 bytes, no UTF-8 BOM, and the expected eleven columns. The temporary UTF-8 backup was deleted after validation.
- The newer `2026-08-07 15:00:00` source group currently contains duplicate CGI rows, for example `460-00-122737-22`. Its database transaction rolled back on the existing `(metric_time, cgi)` primary key, so the retained `14:00` database and history result were not replaced. Duplicate-row selection requires a separate business rule.
## 2026-08-11: Network type relabeled to 2.6G/700M/TDD/FDD
- `network_type` keeps its column name but now labels radio type per source prefix: `5G干扰监控` is `2.6G` (the user treats 2.6G as the unambiguous 5G label because 700M is also 5G), `700M干扰监控` is `700M`, `SDR_TDD干扰监控` and `反开RD干扰监控` are `TDD`, and the three FDD-schema sources (`SDR_FDD干扰监控`, `5G下FDD干扰监控`, `700M下FDD干扰监控`) are `FDD`. The old `2.6G/700M/4G` grouping is gone.
- Real source filenames only carry these keywords in the fixed prefix; the middle text (for example `LWP_每小时_过滤110`) has no usable network keyword.
- High-interference thresholds are unchanged and now keyed per source type through `MIN_INTERFERENCE_BY_SOURCE`: the two 5G-directory sources keep `-107` and the other five keep `-110`, so relabeling `5G下FDD干扰监控` to `FDD` does not change which rows are kept.
- No database migration is needed: the column type stays `VARCHAR(16)` and old-label rows disappear on the next successful replacement run. Twenty-two tests pass locally.
## 2026-08-07: Duplicate CGI selection
- Retained high-interference rows are deduplicated by CGI before nearby counting and database insertion. When duplicates exist, the row with the numerically largest `interference_dbm` is kept; equal values keep the first encountered row. Converted source CSVs remain complete.