CN113296743B - SpaceCap software mapping method based on GSO C data declaration - Google Patents
SpaceCap software mapping method based on GSO C data declaration Download PDFInfo
- Publication number
- CN113296743B CN113296743B CN202110532963.6A CN202110532963A CN113296743B CN 113296743 B CN113296743 B CN 113296743B CN 202110532963 A CN202110532963 A CN 202110532963A CN 113296743 B CN113296743 B CN 113296743B
- Authority
- CN
- China
- Prior art keywords
- corresponds
- layer
- spacecap
- software
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Radio Relay Systems (AREA)
Abstract
The invention discloses a SpaceCap software mapping method based on GSO C data declaration. The method comprises the following steps: the structure of the satellite communication system is arranged according to the basic elements of the satellite communication, and comprises a basic information layer, a beam layer, a transponder group layer, an earth station layer and a carrier layer; analyzing a storage structure of SpaceCap software, and confirming the content stored in each data table; the method comprises the steps that each layer is mapped with SpaceCap software, a basic information layer is used for storing a basic general data beam layer of a satellite, the beam layer is used for storing information of satellite beams, a repeater group layer is used for storing the characteristics of each group of repeaters in the beams, an earth station layer is used for storing the characteristic contents of the satellite repeaters corresponding to a ground station, and a carrier layer is used for recording the characteristics of all carriers under the repeater group. The method is simple, convenient and quick to operate, can obviously reduce the dependence of the work on talents, and is favorable for quickly acquiring the priority use right of more frequency-track resources.
Description
Technical Field
The invention relates to the field of satellite frequency orbits, in particular to a SpaceCap software mapping method based on GSO C data declaration.
Background
With the development of scientific technology and the rapid increase of human communication demand, the number and scale of artificial satellites are larger and larger, the importance and the competitive degree of frequency orbit resources reach unprecedented heights, and a series of difficulties including declaration, coordination and the like are met from the practical demand to the aspect of putting into use. The existing data declaration is that the competent department uses SpaceCap software to send the generated satellite network data to ITU (international telecommunication union) to complete the application.
Taking an ITU database in 1 month in 2020 as an example, C data of Ku, Ka, V and E frequency bands reported by GSO communication satellites reaches hundreds, and due to exclusivity of frequency-rail resources and a principle of 'preferential registration and preferential use' followed by reporting, rapid reporting of the frequency-rail resources has a very important meaning.
The existing track resource declaration completely depends on manual work, and experts declaring multi-year frequency resources fill in the track resource declaration through SpaceCap software according to use requirements. SpaceCap software is complex in declaration, the method completely depends on professional talents, the efficiency is low, the cost is high, and large-scale frequency-track resource declaration is difficult to realize.
Disclosure of Invention
The invention aims to provide a SpaceCap software mapping method based on GSO C data declaration, which is simple, convenient and quick to operate.
The technical solution for realizing the purpose of the invention is as follows: a SpaceCap software mapping method based on GSO C data declaration comprises the following steps:
and 7, mapping the carrier layer of the satellite communication system with SpaceCap software for recording the characteristics of all carriers under the transponder group.
Compared with the prior art, the invention has the following remarkable advantages: (1) the thinking logic and the use habit of frequency track resource users are more met, the operation is simple, convenient and quick, and the dependence of the work on talents can be obviously reduced; (2) the method is favorable for rapidly acquiring the priority of the multi-frequency-track resources and promoting the development of the career such as aerospace and the like, and has strong engineering realizability.
Drawings
Fig. 1 is a block diagram of a satellite communication system.
Fig. 2 is a structure diagram of a SpaceCap storage structure.
Fig. 3 is a schematic diagram of a note page.
FIG. 4 is a diagram of a Station page.
Fig. 5 is a schematic diagram of a Beam page.
Fig. 6 is a schematic diagram of a Group page under a receive beam.
Fig. 7 is a schematic diagram of a Group page under a transmit beam.
Fig. 8 is a schematic diagram of frequency pages.
FIG. 9 is a schematic view of an Assoc Earth Station page.
FIG. 10 is a schematic view of the Assoc Earth Station page.
FIG. 11 is a schematic diagram of an emulsions page.
FIG. 12 is a diagram illustrating a Notice page in an embodiment.
FIG. 13 is a diagram of an embodiment of a Station page.
FIG. 14 is a schematic diagram of a Beam page in the embodiment.
FIG. 15 is a schematic diagram of a Group page in the embodiment.
FIG. 16 is a schematic diagram of frequency pages in the embodiment.
FIG. 17 is a schematic diagram of the AssocEarth Station page in the embodiment.
FIG. 18 is a schematic diagram of an embodiment of an emulsions page.
Detailed Description
The invention is further described in detail below with reference to the drawings and specific embodiments.
As shown in fig. 1, a method for mapping a space cap software based on GSO C data declaration includes the following steps:
and 7, mapping the carrier layer of the satellite communication system with SpaceCap software for recording the characteristics of all carriers under the transponder group.
Further, as a specific example, the structure of the satellite communication system is organized according to the basic elements of satellite communication in step 1 as shown in fig. 1. The satellite communication system comprises a general data layer, a beam layer, a transponder layer, an earth station layer and a carrier layer according to a logic sequence, wherein in the structure of the satellite communication system in the step 1, according to the logic sequence, a first layer is a basic information layer, a second layer is the beam layer, a third layer is the transponder group layer, a fourth layer is the earth station layer and a fifth layer is the carrier layer.
Further, as a specific example, the analyzing the SpaceCap software storage structure in step 2 confirms the content stored in each data table, specifically: analyzing a SpaceCap software storage structure, wherein frequency declaration relates to 16 data tables, wherein a note table stores general data of notification, an attch table stores appendix information of declaration data on the basis of the note table, a com _ el table stores other public contents of declaration data on the basis of the note table, a geo table stores ground-to-geostationary-space-station-related data, an s _ beam table stores beam information of a space station, a beam _ tr stores beam information, a grp table stores public data of frequencies, a strap stores a link between beams/frequencies of an uplink and a downlink, a freq stores frequency data, a ngma stores link noise or transmission gain of a link group, an e _ as _ stn stores related earth stations, an srv _ cls stores service properties and station classes of an allocation group, an ass stores allocated frequencies, an emiss stores characteristics of carriers, and an e _ srvcls stores service properties and station classes of the earth stations, carrier _ fr stores the carrier frequency of the transmission, mod _ char stores the general characteristics of the transmission.
Further, as a specific example, step 3 is to map the basic information layer of the satellite communication system with the SpaceCap software, so as to store the basic general data of the satellite, which is specifically as follows:
the basic information layer in step 3 is used to store basic general data of the satellite, and the contents are shown in table 1, which corresponds to the notice table, the com _ el table and the attch table in fig. 2. The basic information layer corresponds to the information layers shown in fig. 3 and 4, namely a note page and a Station page of the SpaceCap software. Specifically, as the present invention is based on the data report of GeoStationary Satellite C, the light blue area in fig. 3 is default to No.9.6, the Type of Satellite Network or Earth Station is default to GeoStationary Satellite Network, and the Notice interpolated for is default to Addition. In addition, on the Notice page, A1f1 corresponds to the department of authority name in Table 1, and A1f3 corresponds to the intergovernmental organization name in Table 1; on a Station page, A1a corresponds to a satellite network name in table 1, A4A1 corresponds to a nominal geographic longitude in table 1, a and b in A4a2 correspond to east longitude and west longitude tolerance values in table 1 respectively, A4a2c corresponds to an inclination angle in table 1, A16a corresponds to whether off-axis power in table 1 meets requirements, A17a corresponds to whether power flux density in table 1 meets requirements, and A18a corresponds to whether an aviation earth Station in table 1 meets characteristic requirements;
in order to simplify the declaration content, except for data items which need to be manually input or selected, the judgment of the off-axis power, the flux density and the satisfaction characteristic of the aviation earth station is finished by judging by the system according to a network limit value provided by the ITU.
TABLE 1 basic general data items
Further, as a specific example, in step 4, the beam layer of the satellite communication system is mapped with the SpaceCap software, and is used to store information of a satellite beam, which is specifically as follows:
the second layer is a beam layer, and is configured to store information of satellite beams, where the content is shown in table 2 and corresponds to an s _ beam table, a strap table, and a beam _ tr table in fig. 2. The Beam layer corresponds to fig. 5, i.e., the Beam page of the SpaceCap software. Specifically, B1a corresponds to the antenna beam name and original name in table 2, B1B corresponds to whether the beam in table 2 is movable, B2 corresponds to the beam property in table 2, B3a1 corresponds to the maximum co-polarization omnidirectional gain in table 2, B3a 3d corresponds to the antenna pointing longitude in table 2, and B3c1 corresponds to the co-polarization antenna radiation pattern id.
Wherein each data item of the beam layer is obtained by manual input;
table 2 beam layer data entry
| Serial number | Data item | Types of | Length of | |
|
| 1 | Antenna beam name and original name | varchar | 8 | |
|
| 2 | Whether the beam is | varchar | 1 | |
|
| 3 | Beam properties | varchar | 1 | |
|
| 4 | Maximum co-polarized | float | 5 | |
|
| 5 | Antenna pointing | float | 4 | |
|
| 6 | Co-polarized antenna radiation | int | 2 | Manual input |
Further, as a specific example, the third layer in step 5 is a repeater group layer, which is used for storing the characteristics of each group of repeaters inside the beam, and the contents are shown in table 3, corresponding to grp table, freq table, ngma table, srv _ cls table, assgn table and carrier _ fr table in fig. 2. When the repeater is in the receive beam, corresponding to fig. 6, and when the repeater is in the transmit beam, corresponding to fig. 7, fig. 6 and 7 are the group pages of the SpaceCap software for different beam attributes, respectively. Specifically, C3a corresponds to the frequency band bandwidth of the repeater in table 3, C4a corresponds to the site type in table 3, C4b corresponds to the site service property in table 3, C5a corresponds to the noise temperature in table 3, C8d1 corresponds to the maximum total peak power in table 3, C8d2 corresponds to the adjacent bandwidth in table 3, C2C corresponds to whether the frequency assignment in table 3 is in the 4.4 clause record, C11a corresponds to the beam service area in table 3, C2a1 in fig. 8 corresponds to the frequency in table 3, the center frequency point is an array, and the number in the array corresponds to the number of repeaters in the repeater group.
In order to simplify the declaration content, except for the data items which need to be manually input or selected in a list, the judgment of other data items is completed by the system. In addition, the station types are automatically matched by the system according to the attributes of the corresponding earth stations, and the specific matching condition is shown in table 4. The maximum total peak power is obtained by judging the maximum value after the system reads the peak envelope power of all the carriers under the transponder group.
Table 3 transponder data entry
TABLE 4 spatial station to Earth station matching
Further, as a specific example, step 6 is to map the earth station layer of the satellite communication system with the SpaceCap software, so as to store the characteristic content of the ground station corresponding to the satellite transponder, which is specifically as follows:
the fourth layer is the earth station layer, which is used to store the characteristic contents of the satellite transponder corresponding to the ground station, as shown in table 5, corresponding to the e _ as _ stn table and e _ srvcls table in fig. 2. The Earth Station layer corresponds to fig. 9 when the repeater is located on the receive beam, and corresponds to fig. 10 when the repeater is located on the transmit beam, fig. 9 and 10 being Assoc Earth Station pages of the SpaceCap software. Specifically, as follows, C10b1 corresponds to the name and original name in table 5, C10b2 corresponds to the type in table 5, C10d1 corresponds to the level in table 5, C10d2 corresponds to the service property in table 5, C10d3 corresponds to the maximum isotropic gain of the earth station in table 5, C10d4 corresponds to the main axis beam width in table 5, C10d7 corresponds to the earth station antenna diameter in table 5, in fig. 10, C8g1, C8g2, and C8g3 respectively correspond to whether the power amplifier, total bandwidth, and repeater bandwidth in table 5 are equal to the total bandwidth, C10d5a1 corresponds to the homopolar radiation id, and C10d5a2 corresponds to the homopolar radiation graph.
In order to simplify the declaration content, except for the data items which need to be manually input, the judgment of other data items is completed by the system. The earth station grade is selected from table 4 according to function, property and usage, and the service property is fixed as CP. Power amplifier 10log (P)t) In which P istThe value is the maximum value of the peak envelope power of all carriers, which is located at C8a1 of the Emission page, the total bandwidth is the maximum bandwidth value of all carriers under the repeater group, and the repeater bandwidth is always equal to the total bandwidth by default.
TABLE 5 Earth station data items
| Serial number | Data item | Type (B) | Length of | |
|
| 1 | Name and original name | varchar | 20 | |
|
| 2 | Types of | |
1 | |
|
| 3 | | varchar | 2 | |
|
| 4 | Nature of | varchar | 2 | |
|
| 5 | Maximum isotropic gain of | float | 5 | |
|
| 6 | Spindle | float | 6 | |
|
| 7 | Earth station antenna diameter | float | 8 | Manual input | |
| 8 | | float | 5 | |
|
| 9 | | int | 6 | System determination | |
| 10 | Whether the repeater bandwidth is equal to the | varchar | 1 | |
|
| 11 | | int | 4 | |
|
| 12 | Homopolar | int | 2 | Manual input |
Further, as a specific example, mapping is performed on a carrier layer of a satellite communication system and SpaceCap software, so as to record characteristics of all carriers under the transponder group, which is specifically as follows:
the fifth layer in step 7 is a carrier layer, and is configured to record characteristics of all carriers under the repeater group, as shown in table 6, which corresponds to the emiss table, carrier _ fr table, and mod _ char table in fig. 2. The carrier layer corresponds to fig. 11, that is, an emulsions page of the SpaceCap software, where the page stores information of all carriers in the same transponder group, and each row of the table in fig. 11 represents one carrier. In a practical satellite system, each carrier represents the link properties of a transponder and an earth station, so from a logical point of view, a mapping between the carrier layer and the transponder and earth station is established as shown in table 7.
Table 6 carrier data items
TABLE 7 Carrier data items
| |
|
|
|
|
|
| |
|
|
|
|
… |
| |
|
… | … | |
Carrier wave 8 |
| Earth station n-1 | … | |
… | Carrier n-1 | |
| Earth station n | … | … | … | … | Carrier n |
The data items in fig. 11 are specifically as follows, C7a corresponds to the carrier name in table 6, C8a1/C8b1 corresponds to the peak envelope power maximum value in table 6, C8a2/C8b2 corresponds to the maximum power density, C8C1 corresponds to the peak envelope power minimum value, C8C3 corresponds to the minimum power density, C8e1 corresponds to the carrier-to-noise ratio (guard threshold), and C9 corresponds to the modulation type.
The invention is described in further detail below with reference to the figures and the embodiments.
Example 1
Firstly, according to basic elements of satellite communication, a satellite communication system is arranged to respectively comprise a general data layer, a beam layer, a transponder layer, an earth station layer and a carrier layer according to a logic sequence.
The universal data layer is used for describing unique satellite network data, namely the satellite network data is static satellite C data, the network name is CHNNEWSAT-G1-34E, the orbit is 34 degrees from east longitude, the declaration department is China, and the total number of the satellite network data is 54 beams, wherein 26 transmitting beams and 24 receiving beams are provided.
The beam layer refers to the properties of each beam of the satellite network, and takes the beam named CU under the data as an example, the beam is a movable receiving beam, the maximum co-polarization omnidirectional gain is 28, and the antenna pointing accuracy is 0.1, and the total number of the antenna is 10 transponder groups. The repeater layer includes the capability of repeaters under the beam, taking the first repeater group under the CU beam as an example, the bandwidth of the repeater group is 40000KHz, the type is EC, the service property is CP, the polarization type is hybrid polarization, the noise temperature is 1000Kelvins, the beam service area is 1, and includes 31 repeaters, and the center frequency of the repeaters ranges from 5870MHz to 6665 MHz.
The earth station layer is used for referring to various attributes of an earth station corresponding to one repeater group, in general, one repeater group corresponds to one earth station, the earth station corresponding to the first repeater group under a beam of a CU is a TYPICAL earth station, the name is typicall-C5 (1.2M) type is TC, the service property is CP, the maximum isotropic gain is 35.3dBi, the width of a main shaft beam is 2.92 degrees, the diameter of an antenna is 1.2 meters, a power amplifier is 32dBW, the total bandwidth is 40000KHz, the bandwidth of a repeater is equal to the total bandwidth, and the homopolar radiation model is a radiation model with id of 606 in a file library provided by the international union.
In addition, the properties of the communication link between the transponder inside the satellite and the ground earth station need to be defined, that is, a carrier is defined, the name of the earth station and the transponder is TYPICAL-C5(1.2M), the name of the carrier is 36M0G9W, the maximum value of the peak envelope power is 31.1, the maximum power density is-44.5, the minimum value of the peak envelope power is 27.1, the minimum power density is-48.5, and the protection threshold of the carrier is 12.
Then, the sorted satellite system data is mapped into the SpaceCap software, and the results are shown in fig. 12 to fig. 18, namely, a note page in fig. 12, a Station page in fig. 13, a Beam page in fig. 14, a Group page in fig. 15, a frequency page in fig. 16, an AssocEarth Station page in fig. 17, and an emission page in fig. 18. Therefore, the invention is more in line with the thinking logic and the use habit of frequency track resource users, has simple, convenient and quick operation, and can obviously reduce the dependence of the work on talents; the method is beneficial to rapidly acquiring the priority of the multi-frequency-orbit resources, promotes the development of the aviation and aerospace industries and has strong engineering realizability.
Claims (7)
1. A space map software mapping method based on GSOC data declaration is characterized by comprising the following steps:
step 1, arranging the structure of a satellite communication system according to basic elements of satellite communication, wherein the structure comprises a basic information layer, a beam layer, a transponder group layer, an earth station layer and a carrier layer;
step 2, analyzing the storage structure of the SpaceCap software, and confirming the contents stored in each data table, wherein the specific steps are as follows:
analyzing a SpaceCap software storage structure, the frequency declaration relating to 16 data tables, wherein a note table stores general data of notification, an attch table stores appendix information of declaration data on the basis of the note table, a com _ el table stores other common contents of declaration data on the basis of the note table, a geo table stores geostationary-space-station-related data, an s _ beam table stores beam information of space stations, a beam _ tr stores beam information, a grp table stores common data of frequencies, a strap stores a link between beams/frequencies of uplink and downlink, a frq stores frequency data, an ngma stores link noise or transmission gain of a link group, an e _ as _ stn stores related earth stations, an srv _ cls stores service properties and station classes of an allocation group, an ass stores allocated frequencies, properties of emiss stores characteristics of carriers, an e _ srvcls stores service properties and station classes of earth stations, carrier _ fr stores the carrier frequency of the transmission, mod _ char stores the general characteristics of the transmission;
step 3, mapping a basic information layer of the satellite communication system and SpaceCap software for storing basic general data of the satellite;
step 4, mapping a beam layer of the satellite communication system with SpaceCap software for storing information of satellite beams;
step 5, mapping a transponder group layer of the satellite communication system with SpaceCap software for storing the characteristics of each group of transponders in the wave beam;
step 6, mapping an earth station layer of the satellite communication system and SpaceCap software, and storing the characteristic content of the ground station corresponding to the satellite transponder;
and 7, mapping the carrier layer of the satellite communication system with SpaceCap software for recording the characteristics of all carriers under the transponder group.
2. The GSOC data declaration based SpaceCap software mapping method of claim 1, wherein the satellite communication system in step 1 has a structure that the first layer is a basic information layer, the second layer is a beam layer, the third layer is a repeater group layer, the fourth layer is an earth station layer, and the fifth layer is a carrier layer according to a logical sequence.
3. The GSOC-data-declaration-based SpaceCap software mapping method of claim 1, wherein in step 3, a basic information layer of a satellite communication system is mapped with SpaceCap software for storing basic general data of a satellite, which is specifically as follows:
the basic information layer is used for storing basic general data of the satellite, and the contents of the basic general data are shown in a table 1 and correspond to a notice table, a com _ el table and an attch table; the basic information layer corresponds to a Notice page and a Station page of the SpaceCap software, in the Notice page, A1f1 corresponds to the names of departments in charge in the table 1, and A1f3 corresponds to the names of organizations between governments in the table 1; on a Station page, A1a corresponds to a satellite network name in table 1, A4A1 corresponds to a nominal geographic longitude in table 1, a and b in A4a2 correspond to east longitude and west longitude tolerance values in table 1 respectively, A4a2c corresponds to an inclination angle in table 1, A16a corresponds to whether off-axis power in table 1 meets requirements, A17a corresponds to whether power flux density in table 1 meets requirements, and A18a corresponds to whether an aviation earth Station in table 1 meets characteristic requirements;
TABLE 1 basic general data items
The judgment of the off-axis power, the flux density and the aeronautical earth station satisfaction characteristics is finished by the system according to the network limit judgment provided by the ITU except for the data items which need to be manually input or selected.
4. The GSOC-data-declaration-based SpaceCap software mapping method of claim 1, wherein in step 4, a beam layer of a satellite communication system is mapped with SpaceCap software for storing satellite beam information, which specifically comprises the following steps:
the beam layer is used for storing information of satellite beams, and the content of the information is shown in table 2 and corresponds to an s _ beam table, a strap table and a beam _ tr table; the Beam layer corresponds to a Beam page of the SpaceCap software, B1a corresponds to an antenna Beam name and an original name in the table 2, B1B corresponds to whether a Beam in the table 2 is movable or not, B2 corresponds to Beam properties in the table 2, B3a1 corresponds to maximum homopolarity omnidirectional gain in the table 2, B3d corresponds to antenna pointing longitude in the table 2, and B3c1 corresponds to a homopolarity antenna radiation pattern id;
table 2 beam layer data entry
Wherein each data item of the beam layer is obtained by manual input.
5. The GSOC data declaration-based SpaceCap software mapping method of claim 1, wherein in step 5, the transponder group layer of the satellite communication system is mapped with SpaceCap software for storing the characteristics of each group of transponders inside a beam, which is specifically as follows:
the repeater group layer is used for storing the characteristics of each group of repeaters in the beam, and the content of the characteristics is shown in table 3 and corresponds to a grp table, a freq table, an ngma table, an srv _ cls table, an assgn table and a carrier _ fr table; when the repeater is in a receiving beam, the Group page of the SpaceCap software under the receiving beam corresponds to the Group page of the SpaceCap software under the transmitting beam, and when the repeater is in a transmitting beam, the Group page of the SpaceCap software under the transmitting beam corresponds to the Group page of the SpaceCap software under the transmitting beam: c3a corresponds to the transponder band bandwidth in table 3, C4a corresponds to the site type in table 3, C4b corresponds to the site service property in table 3, C5a corresponds to the noise temperature in table 3, C8d1 corresponds to the maximum total peak power in table 3, C8d2 corresponds to the contiguous bandwidth in table 3, C2C corresponds to whether the frequency assignment in table 3 is filed under 4.4 clause, and C11a corresponds to the beam service area in table 3; c2a1 in the queries page corresponds to the frequency in the table 3, the central frequency point is an array, and the number in the array corresponds to the number of repeaters in the repeater group;
table 3 transponder data entry
In order to simplify the declared content, except the data items which need to be manually input or selected in a list, the judgment of other data items is completed by the system; in addition, the station types are automatically matched by the system according to the attributes of the corresponding earth stations, the specific matching condition is shown in table 4, and the maximum total peak power is obtained by judging the maximum value after the system reads the peak envelope power of all carriers under the repeater group;
TABLE 4 spatial station to Earth station matching
6. The GSOC data declaration based SpaceCap software mapping method of claim 1, wherein the step 6 maps the earth station layer of the satellite communication system with SpaceCap software for storing the characteristic content of the ground station corresponding to the satellite transponder, which is as follows:
the earth station layer is used for storing the characteristic content of the satellite transponder corresponding to the ground station, and corresponds to an e _ as _ stn table and an e _ srvcls table as shown in table 5; when the repeater is positioned at a receiving beam and a transmitting beam, the Earth Station layer corresponds to an Assoc Earth Station page of space cap software, C10b1 corresponds to a name and an original name in table 5, C10b2 corresponds to a type in table 5, C10d1 corresponds to a grade in table 5, C10d2 corresponds to a service property in table 5, C10d3 corresponds to the Earth Station maximum isotropic gain in table 5, C10d4 corresponds to a main axis beam width in table 5, C10d7 corresponds to an Earth Station antenna diameter in table 5, C8g1, C8g2 and C8g3 in the asoc Earth Station page respectively correspond to a power amplifier, a total bandwidth and a repeater bandwidth in table 5 or not equal to the total bandwidth, C10d5a1 corresponds to a homopolar radiation id, and C10d5a2 corresponds to a homopolar radiation graph;
TABLE 5 Earth station data items
Judging other data items except the data items needing to be manually input by the system; the earth station grade is selected from the table 4 according to the function, the property and the purpose, and the service property is fixed as CP; power amplifier 10log (P)t) In which P istThe value is the maximum value of the peak envelope power of all carriers, which is located at C8a1 of the Emission page, the total bandwidth is the maximum bandwidth value of all carriers under the repeater group, and the repeater bandwidth is always equal to the total bandwidth by default.
7. The GSOC-data-declaration-based SpaceCap software mapping method of claim 1, wherein in step 7, the carrier layer of the satellite communication system is mapped with the SpaceCap software for recording the characteristics of all carriers under the transponder group, which is specifically as follows:
the carrier layer is used for recording the characteristics of all carriers under the repeater group and corresponds to an emiss table, a carrier _ fr table and a mod _ char table; the carrier layer corresponds to an emulsions page of the SpaceCap software, the page stores all carrier information under the same transponder group, and each line of a table in the emulsions page represents a carrier; in an actual satellite system, each carrier represents the link attribute of a transponder and an earth station, so from the logic point of view, a mapping relation between a carrier layer and the transponder and the earth station is established;
table 6 carrier data items
The carrier layer corresponds to an emulsions page of the SpaceCap software, the page stores all carrier information under the same transponder group, each row of a table in the emulsions page of the SpaceCap software represents a carrier, data items are as follows, C7a corresponds to a carrier name in the table 6, C8a1/C8b1 corresponds to a peak envelope power maximum value in the table 6, C8a2/C8b2 corresponds to a maximum power density, C8C1 corresponds to a peak envelope power minimum value, C8C3 corresponds to a minimum power density, C8e1 corresponds to a carrier-to-noise ratio, and C9 corresponds to a modulation type;
for simplicity of reporting, the maximum power density and the minimum power density are calculated by the system, and the maximum power density is the maximum peak envelope power value/bandwidth, and the minimum power density is the minimum peak envelope power value/bandwidth.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110532963.6A CN113296743B (en) | 2021-05-17 | 2021-05-17 | SpaceCap software mapping method based on GSO C data declaration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110532963.6A CN113296743B (en) | 2021-05-17 | 2021-05-17 | SpaceCap software mapping method based on GSO C data declaration |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113296743A CN113296743A (en) | 2021-08-24 |
| CN113296743B true CN113296743B (en) | 2022-07-22 |
Family
ID=77322339
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110532963.6A Active CN113296743B (en) | 2021-05-17 | 2021-05-17 | SpaceCap software mapping method based on GSO C data declaration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113296743B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6226494B1 (en) * | 1997-09-23 | 2001-05-01 | Teledesic Llc | System and method for intermittent satellite communication with a fixed antenna |
| EP1104123A2 (en) * | 1999-11-29 | 2001-05-30 | Nortel Networks Limited | On-board processor for satellite communications |
| WO2001097388A2 (en) * | 2000-06-15 | 2001-12-20 | Hughes Electronics Corporation | Satellite communication system having frequency reuse in non-blocking manner |
| CN106648582A (en) * | 2016-09-19 | 2017-05-10 | 济南浪潮高新科技投资发展有限公司 | Implementation method for internationalized homonymous resource file deploying updating |
| CN109451024A (en) * | 2018-11-14 | 2019-03-08 | 国网浙江省电力有限公司 | Power grid resource data updating mobile operation terminal protection method based on Beidou system |
| CN109858693A (en) * | 2019-01-25 | 2019-06-07 | 中国科学院国家空间科学中心 | A kind of prediction technique for declaring situation towards satellite network data |
| CN110190890A (en) * | 2019-05-09 | 2019-08-30 | 中国人民解放军32039部队 | A kind of spacecraft online application method and system based on communication satellite system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9826537B2 (en) * | 2004-04-02 | 2017-11-21 | Rearden, Llc | System and method for managing inter-cluster handoff of clients which traverse multiple DIDO clusters |
-
2021
- 2021-05-17 CN CN202110532963.6A patent/CN113296743B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6226494B1 (en) * | 1997-09-23 | 2001-05-01 | Teledesic Llc | System and method for intermittent satellite communication with a fixed antenna |
| EP1104123A2 (en) * | 1999-11-29 | 2001-05-30 | Nortel Networks Limited | On-board processor for satellite communications |
| WO2001097388A2 (en) * | 2000-06-15 | 2001-12-20 | Hughes Electronics Corporation | Satellite communication system having frequency reuse in non-blocking manner |
| CN106648582A (en) * | 2016-09-19 | 2017-05-10 | 济南浪潮高新科技投资发展有限公司 | Implementation method for internationalized homonymous resource file deploying updating |
| CN109451024A (en) * | 2018-11-14 | 2019-03-08 | 国网浙江省电力有限公司 | Power grid resource data updating mobile operation terminal protection method based on Beidou system |
| CN109858693A (en) * | 2019-01-25 | 2019-06-07 | 中国科学院国家空间科学中心 | A kind of prediction technique for declaring situation towards satellite network data |
| CN110190890A (en) * | 2019-05-09 | 2019-08-30 | 中国人民解放军32039部队 | A kind of spacecraft online application method and system based on communication satellite system |
Non-Patent Citations (1)
| Title |
|---|
| 主要国家卫星频率轨道资源的国际申报与使用情况研究;张余等;《中国无线电》;20130926(第09期) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113296743A (en) | 2021-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| De Matthaeis et al. | Spectrum management and its importance for microwave remote sensing [technical committees] | |
| CN112835868A (en) | Method for constructing space frequency track resource comprehensive database | |
| CN113296743B (en) | SpaceCap software mapping method based on GSO C data declaration | |
| Kerczewski et al. | UAS CNPC satellite link performance—Sharing spectrum with terrestrial systems | |
| Marschak | Strategy and organization in a system development project | |
| Li et al. | Satellite communication on the non-geostationary system and the geostationary system in the Fixed-satellite service | |
| CN114002717A (en) | GSO rail position selection method based on operational risk | |
| De Matthaeis et al. | Agenda items of the world radiocommunication conference 2023 relevant to remote sensing | |
| Wilson | Modeling c-band co-channel interference from aeromacs omni-directional antennas to mobile satellite service feeder uplinks | |
| CN108282218B (en) | Networking planning method for satellite communication network | |
| CN113346941B (en) | Frequency-orbit database pre-storage compilation method based on system model | |
| Tornatore et al. | VGOS Wideband Reception and Emerging Competitor Occupations of the VLBI Spectrum | |
| Shi et al. | The interference analysis of satellite services in the 8025–8400 MHz frequency band | |
| Railton | The WARC-79 and Papua New Guinea | |
| Situmorang et al. | Indonesia Satellite Supply Profile based on ITU Filings Year 2017-2035 | |
| Smith III | The orbit/spectrum resource and the technology of satellite telecommunications: an overview | |
| Matos | Spectrum resource assessment of the aeronautical mobile service between 400 MHz and 17.7 GHz | |
| Center | George C. Marshall Space Flight Center, A! abam 35812 | |
| Garber | Spectrum management data bases | |
| ALBAJI et al. | INVESTIGATION OF THE SATELLITE MOBILE TELEPHONE PERSPECTIVES IN LIBYA | |
| CN117955546A (en) | Space-frequency domain isolation-based low-orbit constellation ground data transmission frequency division method and system | |
| Wilson | Simulating Global AeroMACS Airport Ground Station Antenna Power Transmission Limits to Avoid Interference with Mobile Satellite Service Feeder Uplinks | |
| Aguilar | Broadband Technology Roadmap for Rural Areas in the Andes and Amazon Regions of Peru | |
| Bartholomé | The Orbital Test Programme | |
| CN117083899A (en) | Measurement method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |