A reconstruction method for ITU space service database

Abstract

The present invention provides a method for reconstructing an ITU space service database. The method creates an SRS base database in a MySQL database and sets ShardingsPhere sharding rules. It also creates an SRS database auxiliary table in the SRS base database and database tables outside the ShardingsPhere sharding rules. It also creates an SRS database shard in a MySQL database and database tables within the ShardingsPhere sharding rules. Finally, the method uses the "A-M-D" comparison rule to determine the addition, modification, and deletion of data from two adjacent periods of the MS-Access SRS database, thereby reconstructing the data into the SRS database shard. By reconstructing and merging SRS databases from different periods, the method constructs a unified, comprehensive database of satellite network data, enabling full lifecycle management of satellite network data and improving the unified management and query efficiency of space frequency and orbital resource data.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to a method for reconstructing an ITU space service database. Background Art

[0002] Satellite frequencies and orbital resources are international resources shared by all mankind. Any country can develop and utilize them in accordance with international regulations and implement its own satellite systems. However, to obtain legitimate international protection, each administration must declare satellite network information to the ITU before a satellite is launched. The SRS database, published by the ITU, contains information on various satellite networks and earth stations submitted by administrations to the ITU, along with the actual status of each entry. Compiled in MS-Access format, it is used for international declaration, coordination, notification, and registration of satellite network information.

[0003] The SRS database is released every two weeks. For example, issue 2989, released on February 7, 2023, contains 4.2GB of data. As the database continues to update, the volume of data continues to grow, and there is a significant amount of duplication between different issues. The SRS database contains a vast amount of content, with complex relationships between tables. Data stored in MS-Access format is difficult to query and retrieve. Furthermore, a single issue of the SRS database cannot provide information about the entire life cycle of a satellite network.

[0004] Therefore, it is necessary to provide a reconstruction method for the ITU space service database. Summary of the Invention

[0005] The object of the present invention is to provide a method for reconstructing an ITU space service database, thereby solving the above-mentioned problems existing in the prior art.

[0006] In order to achieve the above object, the technical solution adopted by the present invention is as follows:

[0007] A method for reconstructing an ITU space service database comprises the following steps:

[0008] S1, create the SRS basic database in the MySQL database and set the ShardingsPhere database rules;

[0009] S2, create an SRS database auxiliary table in the SRS basic database, and create a database table outside the ShardingsPhere sharding rule;

[0010] S3, create the SRS database shard in the MySQL database and create the database table within the ShardingsPhere sharding rule;

[0011] S4, the data in the SRS database in MS-Access format is compared with the "AMD" rule to determine the addition, modification, and deletion of data in two adjacent periods, and thus the data is reconstructed into the SRS database sub-database.

[0012] Preferably, step S1 specifically includes:

[0013] Create an SRS base database and set the SRS base database name to SRS_Base. Configure the five data table names freq, grp, assgn, srv_cls, and provn to the ShardingsPhere sharding rule, and add the table prefix srs_ to the tables in MS-Access. The renamed data table names are srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn.

[0014] Preferably, step S2 specifically includes:

[0015] Create a database auxiliary table srs_info in the SRS_Base database to record the basic attribute information and operation information of each SRS spatial business database;

[0016] Create database tables outside the ShardingsPhere sharding rule and add the srs_version and operation_tag fields to each table.

[0017] Preferably, step S3 specifically includes:

[0018] The horizontal database method is used to dynamically create n data sub-databases, denoted as SRS_1 to SRS_n; for each data sub-database, five database tables, srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn, are created respectively; and three fields, srs_version, operation_tag, and row_num, are added to each database table.

[0019] Preferably, step S4 specifically includes:

[0020] Use the jackcess technology to obtain data from the original SRS database in MS-Access format. Obtain the contents of the srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn database tables in turn. Determine whether the database table contents corresponding to the obtained data belong to the database tables within the ShardingsPhere sharding rule. If so, proceed to step A1; otherwise, proceed to step B1:

[0021] A1: If the database table has been configured in the ShardingsPhere sharding rule, you need to add the acquired data records to the SRS_n shard.

[0022] B1. If the database table is not included in the ShardingsPhere sharding rule, the data record is directly added to the corresponding table in the SRS_Base database in a non-invasive manner, and the SRS issue number is written into the srs_version field in the database auxiliary table srs_info.

[0023] Preferably, step A1 specifically includes:

[0024] Determine the data sub-library number, enter the data into the corresponding data sub-library and identify the data status, use the satellite network ID as the unique identifier, and compare the data record with the data record already entered into the sub-library;

[0025] 1) If the same data record does not exist in the data sub-database, it will be processed into the database, the operation_tag field will be set to A, and the SRS issue number will be written into the srs_version field;

[0026] 2) If the same data record already exists in the data sub-database, it will be skipped without any processing;

[0027] 3) If some identical data records exist in the data sub-database, they are entered into the database, and the operation_tag field is set to M. At the same time, the SRS issue number is written into the srs_version field;

[0028] 4) If the data record of the previous period does not exist in the current database, the operation_tag field of the data record is set to D, and the SRS issue number is written into the srs_version field.

[0029] The beneficial effects of the present invention are:

[0030] The present invention provides a method for reconstructing the ITU space service database. The method constructs a unified satellite network data database by reconstructing and merging SRS databases of different periods, realizes the full life cycle management of satellite network data, and improves the unified management and query efficiency of space frequency orbit resource data. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 is a flow chart of the method for reconstructing the ITU space service database provided in Example 1;

[0032] Figure 2 : is an entity relationship diagram of the sub-library data table used in the embodiment;

[0033] Figure 3 This is a timing diagram for synchronizing Access database based on jackcess technology. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0035] Example 1

[0036] This embodiment provides a method for reconstructing the ITU space service database. The process is as follows: Figure 1 As shown, the following steps are included:

[0037] Step 1: Create an SRS basic database in the MySQL database and set the ShardingsPhere database rules:

[0038] Create an SRS base database and set the SRS base database name to SRS_Base. Configure the five data table names of freq, grp, assgn, srv_cls, and provn to the ShardingsPhere sharding rule, and add the table prefix srs_ to the tables in MS-Access. The renamed data table names are srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn.

[0039] Step 2: Create an auxiliary table for the SRS database in the SRS basic database, and create a database table outside the ShardingsPhere sharding rule:

[0040] Create a database auxiliary table srs_info in the SRS_Base database to record the basic attribute information and operation information of each SRS spatial business database. The specific content is shown in Table 1:

[0041] Table 1 srs_info attribute table

[0042] Serial number Field Name Data Type length Field Description 1 id int 11 Identifier 2 publish_date varchar 255 release date 3 deleted int 11 Enable or disable 4 create_time datetime Creation time 5 update_time datetime Update Time 6 srs_version varchar 255 SRS issue number 7 operation_tag varchar 10 Data Identification

[0043] Create database tables outside the ShardingsPhere sharding rule and add the srs_version and operation_tag fields to each table.

[0044] Step 3: Create an SRS database shard in the MySQL database and create the database table within the ShardingsPhere sharding rule:

[0045] Sub-databases SRS_1 through SRS_n are dynamically created using the rule of dividing the number of table records by 5 million. For example, if the total number of records in the sub-database table is 0 and the quotient of this number is 5 million, then sub-database SRS_1 is created. If the total number of records in the sub-database table is 5 million and the quotient of this number is 1, then sub-database SRS_2 is created. This continues in this order, creating sub-databases dynamically.

[0046] For each data sub-database, create five database tables: srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn, as shown in Table 2-6:

[0047] Table 2 srs_provn attribute table

[0048]

[0049]

[0050] Table 3 srs_freq attribute table

[0051] Serial number Field Name Data Type length Field Comments 1 ntc_id int 11 Profile ID 2 emi_rcp varchar 10 Transmit or receive code 3 beam_name varchar 16 Beam name 4 grp_id int 11 Group ID 5 seq_no int 11 Sequence number 6 freq_sym varchar 10 Unit symbol 7 freq_assgn double Assigned frequency 8 freq_mhz double Assigned frequency in MHz 9 freq_min double Minimum frequency 10 freq_max double Maximum frequency 11 bdwdth int 11 bandwidth 12 fdg_reg varchar 10 Review Conclusion 13 d_prot_eff datetime date 14 wic_no int 11 Weekly Report Number 15 ntc_type varchar 10 Data Type 16 srs_id int 11 SRS database ID 17 srs_version varchar 255 SRS database version 18 operation_tag varchar 10 Data Identification 19 row_num int 11 Table row data row number

[0052] Table 4 srs_grp attribute table

[0053]

[0054]

[0055]

[0056]

[0057]

[0058] Table 5 srs_assgn attribute table

[0059] Serial number Field Name Data Type length Field Comments 1 grp_id int 11 Group ID 2 seq_no int 11 Sequence number 3 freq_sym varchar 10 Unit symbol 4 freq_assgn double Assigned frequency 5 freq_mhz double Assigned frequency in MHz 6 f_cmp_rec varchar 10 The difference code between the two records 7 srs_version varchar 255 SRS database version 8 operation_tag varchar 10 Data Identification 9 row_num int 11 Table row data row number

[0060] Table 6 srs_srv_cls attribute table

[0061] Serial number Field Name Data Type length Field Comments 1 grp_id int 11 Group ID 2 seq_no int 11 Sequence number 3 stn_cls varchar 10 Station type 4 nat_srv varchar 10 Nature of business 5 srs_version varchar 255 SRS database version 6 operation_tag varchar 10 Data Identification 7 row_num int 11 Table row data row number

[0062] Three fields, srs_version, operation_tag, and row_num, have been added to each database table. row_num represents the table row number and serves as the database sharding key. The newly added fields for the srs_freq, srs_grp, srs_assgn, and srs_src_cls tables are consistent with those for srs_provn.

[0063] srs_id is the ID of the SRS database, used to identify the source of a data record. srs_version is the SRS database issue number, used to identify the SRS database issue in which a data record appears. operation_tag is the identifier of the data record, indicating the change between two consecutive issues of data, including A (addition), M (modification), and D (deletion).

[0064] Step 4: Use the "AMD" comparison rule to determine the addition, modification, and deletion of data in two adjacent periods of the SRS database in MS-Access format, and reconstruct the data into the SRS database sub-database:

[0065] Use the jackcess technology to obtain data from the original SRS database in MS-Access format. Obtain the contents of the srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn database tables in turn. Determine whether the database table contents corresponding to the obtained data belong to the database tables within the ShardingsPhere sharding rule. If so, proceed to step A1; otherwise, proceed to step B1:

[0066] A1. If the database table has been configured in the ShardingsPhere sharding rule, you need to add the acquired data records to the SRS_n shard. The specific steps include:

[0067] 1) If the same data record does not exist in the database, it will be processed into the database, the operation_tag field will be set to A, and the SRS issue number will be written into the srs_version field;

[0068] 2) If the same data record already exists in the database, it will be skipped without any processing;

[0069] 3) If some of the same data records exist in the database, they are put into storage, the operation_tag field is set to M, and the SRS issue number is written into the srs_version field;

[0070] 4) If the data record of the previous period does not exist in the current database, the operation_tag field of the data record is set to D;

[0071] B1. If the database table is not included in the ShardingsPhere sharding rule, the data record is directly added to the corresponding table in the SRS_Base database in a non-invasive manner, and the SRS issue number is written into the srs_version field in the database auxiliary table srs_info.

[0072] According to the above processing logic, the data in the srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn tables are processed in turn to complete the reconstruction of the ITU space service database.

[0073] Example 2

[0074] This embodiment provides a method for reconstructing an ITU space service database. Taking the SRS databases of issues 2973, 2974, 2975, 2976, 2977, 2978, 2979, 2980, 2981, and 2982 as examples, the reconstruction process of the ITU space service database is described. This embodiment selects a MySQL database as the target database after reconstruction, and includes the following steps:

[0075] Step 1: Create the SRS_Base basic database in the MySQL database.

[0076] Configure ShardingsPhere sharding rules for the srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn tables;

[0077] Step 2: In the SRS_Base database, create the srs_info data table, write the basic information of the 2973th SRS database into the data table, and then import the SRS data in MS-Access format into the SRS_Base database using the jackcess technology, including 57 tables such as adm_assoc, alloc_id, ant_type, geo, e_stn, and e_as_stn.

[0078] Step 3: In a MySQL database, performance degrades dramatically when a single table exceeds 5 million rows, severely impacting database efficiency. Therefore, the maximum capacity of a single table in a shard is limited to 5 million rows. If a single shard table exceeds 5 million rows, a new shard is automatically created.

[0079] Starting with the 2973rd issue of the SRS database, create the SRS_1 sub-database, and in the sub-database, create the srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn attribute tables in sequence according to the attribute table structures of Tables 2, 3, 4, 5, and 6. The relationship between the attribute tables in the sub-database is as follows: Figure 2 As shown, each attribute table is associated with each other through primary keys and foreign keys.

[0080] Step 4, through the database script based on jackcess technology, reconstruct the SRS data in MS-Access format into the SRS_Base basic library and SRS_1 sub-library, such as Figure 3 The following is a timing diagram of synchronizing the Access database based on the jackcess technology. The "AMD" comparison rule logic is written in the database script to implement the identification judgment of the addition, modification, and deletion of data in two adjacent periods.

[0081] After the reconstruction of 10 phases of SRS data is completed, the contents of the srs_info table are as follows.

[0082]

[0083]

[0084] When the provn table of the 2973th SRS database was reconstructed to the sub-database, the capacity of the srs_provn table of the SRS_1 sub-database had reached 5 million rows, so the srs_provn table under the SRS_1 sub-database was automatically created.

[0085] When the provn table of the 2973th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_2 sub-database reached 5 million rows, so the srs_provn table in the SRS_3 sub-database was automatically created.

[0086] When the provn table of the 2973th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_3 sub-database had reached 5 million rows, so the srs_provn table in the SRS_4 sub-database was automatically created.

[0087] When the provn table of the 2974th SRS database was restructured to a shard, the capacity of the srs_provn table in the SRS_4 shard reached 5 million rows, so the srs_provn table in the SRS_5 shard was automatically created.

[0088] When the provn table of the 2974th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_5 sub-database reached 5 million rows, so the srs_provn table in the SRS_6 sub-database was automatically created.

[0089] When the provn table of the 2974th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_6 sub-database reached 5 million rows, so the srs_provn table in the SRS_7 sub-database was automatically created.

[0090] When the assgn table of the 2974th SRS database was restructured into a sub-library, the capacity of the SRS_1 sub-library reached 5 million rows. Since the SRS_2 sub-library had already been created, the srs_assgn table was automatically created under the SRS_2 sub-library.

[0091] When the provn table of the 2975th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_6 sub-database had reached 5 million rows, so the srs_provn table in the SRS_7 sub-database was automatically created.

[0092] When the provn table of the 2975th SRS database was reconstructed to the sub-database, the capacity of the srs_provn table of the SRS_7 sub-database had reached 5 million rows, so the srs_provn table of the SRS_8 sub-database was automatically created.

[0093] When the provn table of the 2975th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_8 sub-database had reached 5 million rows, so the srs_provn table in the SRS_9 sub-database was automatically created.

[0094] When the assgn table of the 2975th issue of the SRS database was restructured to a sub-library, the capacity of the SRS_2 sub-library had reached 5 million rows. Since the SRS_3 sub-library had already been created, the srs_assgn table was automatically created under the SRS_3 sub-library.

[0095] When the srv_cls table of the 2975th SRS database was reconstructed into a shard, the capacity of the srs_srv_cls table of the SRS_1 shard reached 5 million rows. Since the SRS_1 shard had already been created, the srs_srv_cls table under the SRS_2 shard was automatically created.

[0096] When the provn table of the 2976th SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS_9 sub-database had reached 5 million rows, so the srs_provn table of the SRS_10 sub-database was automatically created.

[0097] When the provn table of the 2976th SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS_10 sub-database had reached 5 million rows, so the srs_provn table of the SRS_11 sub-database was automatically created.

[0098] When the provn table of the 2976th SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS_11 sub-database had reached 5 million rows, so the srs_provn table of the SRS_12 sub-database was automatically created.

[0099] When the assgn table of the 2976th SRS database was restructured into a sub-library, the capacity of the SRS_3 sub-library reached 5 million rows. Since the SRS_4 sub-library had already been created, the srs_assgn table was automatically created under the SRS_4 sub-library.

[0100] When the freq table of the 2976th SRS database was restructured to a shard, the capacity of the srs_freq table in the SRS_1 shard reached 5 million rows. Since the SRS_2 shard had already been created, the srs_freq table in the SRS_2 shard was automatically created.

[0101] When the srv_cls table of the 2976th SRS database was reconstructed to the sub-library, the capacity of the srs_srv_cls table of the SRS_2 sub-library had reached 5 million rows. Since the SRS_3 sub-library had been created, the srs_srv_cls table under the SRS3 sub-library was automatically created.

[0102] When the provn table of the 2977th SRS database was restructured to a sub-database, the capacity of the provn table in the SRS_12 sub-database had reached 5 million rows, so the srs_provn table in the SRS_13 sub-database was automatically created.

[0103] When the provn table of the 2977th SRS database was restructured to a sub-database, the capacity of the provn table in the SRS_13 sub-database had reached 5 million rows, so the srs_provn table in the SRS_14 sub-database was automatically created.

[0104] When the provn table of the 2977th SRS database was restructured to a sub-database, the capacity of the provn table in the SRS_14 sub-database had reached 5 million rows, so the srs_provn table in the SRS_15 sub-database was automatically created.

[0105] When the srv_cls table of the 2977th SRS database was reconstructed to the sub-library, the capacity of the srs_srv_cls table of the SRS_3 sub-library had reached 5 million rows. Since the SRS_4 sub-library had been created, the srs_srv_cls table under the SRS_4 sub-library was automatically created.

[0106] When the assgn table of the 2977th SRS database was restructured into a sub-library, the capacity of the SRS_4 sub-library reached 5 million rows. Since the SRS_5 sub-library had already been created, the srs_assgn table was automatically created under the SRS_5 sub-library.

[0107] When the grp table of the 2977th SRS database was restructured to a shard, the capacity of the srs_grp table in the SRS_1 shard reached 5 million rows, so the srs_grp table in the SRS_2 shard was automatically created.

[0108] When the provn table of the 2978th ​​SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_15 sub-database had reached 5 million rows, so the srs_provn table in the SRS_16 sub-database was automatically created.

[0109] When the provn table of the 2978th ​​SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS16 sub-database had reached 5 million rows, so the srs_provn table of the SRS_17 sub-database was automatically created.

[0110] When the provn table of the 2978th ​​SRS database was restructured to a sub-database, the capacity of the provn table in the SRS_17 sub-database had reached 5 million rows, so the srs_provn table in the SRS_18 sub-database was automatically created.

[0111] When the assgn table of the 2978th ​​SRS database was restructured into a sub-library, the capacity of the SRS_5 sub-library reached 5 million rows. Since the SRS_6 sub-library had already been created, the srs_assgn table was automatically created under the SRS_6 sub-library.

[0112] When the provn table of the 2979th SRS database was reconstructed to a sub-library, the capacity of the srs_provn table of the SRS_18 sub-library reached 5 million rows. Since the SRS_19 sub-library had been created, the srs_provn table under the SRS_19 sub-library was automatically created.

[0113] When the provn table of the 2979th SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS_19 sub-database had reached 5 million rows, so the srs_provn table of the SRS_20 sub-database was automatically created.

[0114] When the provn table of the 2979th SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS_20 sub-database reached 5 million rows, so the srs_provn table of the SRS_21 sub-database was automatically created.

[0115] When the srv_cls table of the 2979th SRS database was reconstructed into a sub-library, the capacity of the srs_srv_cls table of the SRS_4 sub-library reached 5 million rows. Since the SRS_5 sub-library had been created, the srs_srv_cls table was automatically created under the SRS_5 sub-library.

[0116] When the freq table of the 2979th SRS database was reconstructed to the shard database, the capacity of the srs_freq table in the SRS_2 shard database had reached 5 million rows. Since the SRS_3 shard database had been created, the srs_freq table in the SRS_3 shard database was automatically created.

[0117] When the assgn table of the 2979th SRS database was restructured into a sub-library, the capacity of the SRS_6 sub-library reached 5 million rows. Since the SRS_7 sub-library had already been created, the srs_assgn table was automatically created under the SRS_7 sub-library.

[0118] When the provn table of the 2980th SRS database was restructured to a sub-database, the capacity of the provn table in the SRS_21 sub-database had reached 5 million rows, so the srs_provn table in the SRS_22 sub-database was automatically created.

[0119] When the provn table of the 2980th SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS_22 sub-database had reached 5 million rows, so the srs_provn table of the SRS_23 sub-database was automatically created.

[0120] When the provn table of the 2980th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_23 sub-database had reached 5 million rows, so the srs_provn table in the SRS_24 sub-database was automatically created.

[0121] When the srs_assgn table of the 2980th SRS database was restructured into a sub-library, the capacity of the SRS_7 sub-library had reached 5 million rows. Since the SRS8 sub-library had been created, the srs_assgn table was automatically created under the SRS_8 sub-library.

[0122] When the grp table of the 2980th SRS database was reconstructed into a shard, the capacity of the srs_grp table in the SRS_2 shard reached 5 million rows. Since the SRS_3 shard had already been created, the srs_grp table in the SRS_3 shard was automatically created.

[0123] When the provn table of the 2981th SRS database was restructured to a sub-database, the capacity of the srs_provn table of the SRS_24 sub-database had reached 5 million rows, so the srs_provn table of the SRS_25 sub-database was automatically created.

[0124] When the provn table of the 2981th SRS database was restructured to a sub-database, the capacity of the srs_provn table in the SRS_25 sub-database had reached 5 million rows, so the srs_provn table in the SRS_26 sub-database was automatically created.

[0125] When the tables of the 2981th SRS database were restructured to the sub-database, the capacity of the srs_provn table in the SRS_26 sub-database reached 5 million rows, so the srs_provn table in the SRS_27 sub-database was automatically created.

[0126] When the srv_cls table of the 2981th SRS database was reconstructed into a sub-library, the capacity of the srs_srv_cls table of the SRS_5 sub-library had reached 5 million rows. Since the SRS_6 sub-library had been created, the srs_srv_cls table under the SRS6 sub-library was automatically created.

[0127] When the srs_assgn table of the 2981th SRS database was restructured into a sub-library, the capacity of the SRS_8 sub-library had reached 5 million rows. Since the SRS_9 sub-library had been created, the srs_assgn table was automatically created under the SRS9 sub-library.

[0128] When the provn table of the 2982nd SRS database was reconstructed to the sub-database, the capacity of the srs_provn table of the SRS_28 sub-database had reached 5 million rows, so the srs_provn table under the SRS_28 sub-database was automatically created.

[0129] When the provn table of the 2982nd SRS database was reconstructed into a sub-database, the capacity of the srs_provn table of the SRS_29 sub-database had reached 5 million rows, so the srs_provn table under the SRS_29 sub-database was automatically created.

[0130] When the provn table of the 2982nd SRS database was reconstructed into a sub-database, the capacity of the srs_provn table of the SRS_30 sub-database had reached 5 million rows, so the srs_provn table under the SRS_30 sub-database was automatically created.

[0131] When the assgn table of the 2982nd SRS database was restructured into a sub-library, the capacity of the SRS_9 sub-library had reached 5 million rows. Since the SRS_10 sub-library had already been created, the srs_assgn table was automatically created under the SRS_10 sub-library.

[0132] When the grp table of the 2982nd SRS database was reconstructed into a sub-library, the capacity of the srs_grp table of the SRS_3 sub-library reached 5 million rows. Since the SRS_4 sub-library had been created, the srs_grp table under the SRS_4 sub-library was automatically created.

[0133] 2973, 2974, 2975, 2976, 2977, 2978, 2979, 2980, 2981, and 2982, a total of 1 basic database and 30 sub-databases were reconstructed in the 10 SRS databases.

[0134] The 2973th SRS data contains a total of 41,342,376 rows, which are reconstructed into the SRS_1, SRS_2, and SRS_3 sub-databases.

[0135] The 2974th issue of SRS data contains 41,672,780 rows, which are reconstructed into the SRS_2, SRS_4, SRS_5, and SRS_6 sub-databases.

[0136] The 2975th issue of SRS data contains 41,882,684 rows, which are reconstructed into the SRS_2, SRS_3, SRS_7, SRS_8, and SRS_9 sub-databases.

[0137] The 2976th issue of SRS data has a total of 41,036,625 rows, which are reconstructed into the SRS_2, SRS_3, SRS_4, SRS_10, SRS_11, and SRS_12 sub-databases.

[0138] The 2977th issue of SRS data contains a total of 41,288,402 rows, which are reconstructed into the SRS_2, SRS_4, SRS_5, SRS_13, SRS_14, and SRS_15 sub-databases.

[0139] The 2978th ​​SRS data contains 41,302,593 rows, which are reconstructed into the SRS_6, SRS_26, SRS_17, and SRS_18 sub-databases.

[0140] The 2979th SRS data has a total of 41,408,524 rows, which are reconstructed into the SRS_3, SRS_5, SRS_7, SRS_29, SRS_20, and SRS_21 sub-databases.

[0141] The 2980th issue of SRS data contains 41,836,727 rows, which are reconstructed into the SRS_3, SRS_8, SRS_22, SRS_23, and SRS_24 sub-databases.

[0142] The 2981th SRS data has a total of 41,925,684 rows, which are reconstructed into the SRS_6, SRS_8, SRS_25, SRS_26, and SRS_27 sub-databases.

[0143] The 2982nd SRS data has a total of 41,936,404 rows, which are reconstructed into the SRS_4, SRS_9, SRS_28, SRS_29, and SRS_30 sub-databases.

[0144] By adopting the above technical solution disclosed in the present invention, the following beneficial effects are obtained:

[0145] The present invention provides a method for reconstructing the ITU space service database. The method constructs a unified satellite network data database by reconstructing and merging SRS databases of different periods, realizes the full life cycle management of satellite network data, and improves the unified management and query efficiency of space frequency orbit resource data.

[0146] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for reconstructing an ITU space service database, characterized in that: The following steps are involved: S1, create the SRS basic database in the MySQL database and set the ShardingsPhere database rules; S2, create an SRS database auxiliary table in the SRS basic database, and create a database table outside the ShardingsPhere sharding rule; S3, create the SRS database shard in the MySQL database and create the database table within the ShardingsPhere sharding rule; S4: Data in the MS-Access format SRS database is compared with the "A: Added - M: Modified - D: Deleted" rule to determine the addition, modification, and deletion of data in two consecutive periods, thereby reconstructing the data into the SRS database sub-database; Step S1 specifically includes: Create an SRS base database and set the name of the SRS base database to SRS_Base. Configure the five data table names of freq, grp, assgn, srv_cls, and provn to the ShardingsPhere sharding rule, and add the table prefix srs_ to the tables in MS-Access. The renamed data table names are srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn. Step S2 specifically includes: Create a database auxiliary table srs_info in the SRS_Base database to record the basic attribute information and operation information of each SRS spatial business database; Create database tables outside the ShardingsPhere sharding rule and add two fields, srs_version and operation_tag, to each table; Step S3 specifically includes: Use the horizontal database method to dynamically create n data sub-databases, denoted as SRS_1 to SRS_n; for each data sub-database, create five database tables: srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn; and add three fields: srs_version, operation_tag, and row_num to each database table; srs_version is the SRS database issue number; operation_tag is the identifier of the data record; row_num is the row number of the table row data; Step S4 specifically includes: Use the jackcess technology to obtain data from the original SRS database in MS-Access format. Obtain the contents of the srs_freq, srs_grp, srs_assgn, srs_src_cls, and srs_provn database tables in turn. Determine whether the database table contents corresponding to the obtained data belong to the database tables within the ShardingsPhere sharding rule. If so, proceed to step A1; otherwise, proceed to step B1: A1: If the database table has been configured in the ShardingsPhere sharding rule, you need to add the acquired data records to the SRS_n shard. B1. If the database table is not included in the ShardingsPhere sharding rule, the data record is directly added to the corresponding table in the SRS_Base database in a non-invasive manner, and the SRS issue number is written into the srs_version field in the database auxiliary table srs_info; Step A1 specifically includes: Determine the data sub-library number n, enter the data into the corresponding data sub-library and identify the data status, use the satellite network ID as the unique identifier, and compare the data record with the data record already entered into the sub-library; 1) If the same data record does not exist in the data sub-database, it is processed into the database, the operation_tag field is set to A, the SRS issue number is written to the srs_version field, and the row_num value is automatically incremented; 2) If the same data record already exists in the data sub-database, it will be skipped without any processing; 3) If some identical data records exist in the data sub-database, they are entered into the database, and the operation_tag field is set to M. At the same time, the SRS issue number is written into the srs_version field; 4) If the data record of the previous period does not exist in the current database, the operation_tag field of the data record is set to D, and the SRS issue number is written into the srs_version field.

Images