Transmission method and device based on satellite random access system frame format protocol

Abstract

The present invention provides a transmission method and device based on a satellite random access system frame format protocol. The method comprises: when first target data to be transmitted is application information, heartbeat information, and telemetry information, obtaining a downlink random access channel data frame format protocol; performing data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain converted first target data, and transmitting the converted first target data using the downlink random access channel; when second target data transmitted via an uplink broadcast channel is received, obtaining an uplink broadcast channel data frame format protocol; performing data conversion on the second target data based on the uplink broadcast channel data frame format protocol to obtain converted second target data, and parsing the converted second target data to obtain response information or remote control information.

Description

Technical Field

[0001] The present invention relates to the field of satellite measurement and control technology, and in particular to a transmission method and device based on a satellite random access system frame format protocol. Background Art

[0002] Existing satellite TT&C systems and modes are mission-driven. TT&C missions are typically carried out according to manually pre-arranged plans, coordinating satellite and ground station resources and determining available TT&C time windows. A single TT&C station antenna typically supports only one satellite at a time. Multiple antennas are required for simultaneous TT&C of thousands to tens of thousands of satellites. This significantly increases the number of ground antennas and channels, significantly increasing costs and making it impossible to complete satellite TT&C missions. The existing data frame format protocol for telemetry and telecontrol links was developed based on the aforementioned TT&C system and mode and is only suitable for existing traditional TT&C systems. For new ad-hoc access TT&C systems, the existing traditional frame format cannot meet the TT&C requirements of future mega-constellations. Therefore, a transmission method based on the satellite ad-hoc access system frame format protocol is needed. Summary of the Invention

[0003] In view of this, the present invention provides a transmission method and device based on the satellite random access system frame format protocol. The method can be applied to the new random access measurement and control system and can be suitable for the measurement and control requirements of future giant constellations.

[0004] To achieve the above objectives, the present invention mainly provides the following technical solutions:

[0005] In a first aspect, the present invention provides a transmission method based on a satellite random access system frame format protocol, wherein the data frame format protocol includes a downlink random access channel data frame format protocol and an uplink broadcast channel data frame format protocol, wherein the downlink random access channel data frame format protocol is applied to application information transmission, heartbeat information transmission, and telemetry information transmission, and the uplink broadcast channel data frame format protocol is applied to response information and remote control information. The method comprises:

[0006] When the first target data to be transmitted is application information, heartbeat information and telemetry information, obtaining a downlink random access channel data frame format protocol;

[0007] performing data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain converted first target data, and transmitting the converted first target data using the downlink random access channel;

[0008] When receiving second target data transmitted through the uplink broadcast channel, obtaining an uplink broadcast channel data frame format protocol;

[0009] Based on the uplink broadcast channel data frame format protocol, the second target data is converted to obtain converted second target data, and the converted second target data is parsed to obtain response information or remote control information.

[0010] In a second aspect, the present invention provides a transmission device based on a satellite random access system frame format protocol, wherein the data frame format protocol includes a downlink random access channel data frame format protocol and an uplink broadcast channel data frame format protocol. The downlink random access channel data frame format protocol is applied to application information transmission, heartbeat information transmission, and telemetry information transmission, and the uplink broadcast channel data frame format protocol is applied to response information and remote control information. The device includes:

[0011] A first acquiring unit is configured to acquire a downlink random access channel data frame format protocol when the first target data to be transmitted is application information, heartbeat information, and telemetry information;

[0012] a first conversion unit, configured to perform data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain converted first target data, and transmit the converted first target data using the downlink random access channel;

[0013] a second acquiring unit, configured to acquire an uplink broadcast channel data frame format protocol when receiving second target data transmitted via the uplink broadcast channel;

[0014] The second conversion unit is used to perform data conversion on the second target data based on the uplink broadcast channel data frame format protocol to obtain converted second target data, and parse the converted second target data to obtain response information or remote control information.

[0015] In a third aspect, the present invention further provides an electronic device comprising at least one processor, and at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other via the bus; and the processor is configured to call program instructions in the memory to execute the transmission method based on the satellite random access system frame format protocol of the first aspect.

[0016] In a fourth aspect, the present invention further provides a storage medium, which is used to store a computer program, wherein when the computer program is running, it controls the device where the storage medium is located to execute the transmission method based on the satellite random access system frame format protocol of the above-mentioned first aspect.

[0017] By means of the above technical solution, the present invention provides a transmission method and device based on the satellite random access system frame format protocol. When the first target data to be transmitted is application information, heartbeat information, and telemetry information, the method and device obtain a downlink random access channel data frame format protocol; based on the downlink random access channel data frame format protocol, the first target data is converted to obtain converted first target data, and the converted first target data is transmitted using the downlink random access channel; when second target data transmitted via an uplink broadcast channel is received, the method and device obtain an uplink broadcast channel data frame format protocol; based on the uplink broadcast channel data frame format protocol, the second target data is converted to obtain converted second target data, and the converted second target data is parsed to obtain response information or remote control information. This method can be applied to new random access measurement and control systems and can be suitable for the measurement and control needs of future giant constellations.

[0018] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions and / or embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the technical solutions and / or embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0020] Figure 1 A schematic flow chart of a transmission method based on a satellite random access system frame format protocol disclosed in the present invention;

[0021] Figure 2 A schematic diagram of a protocol template for a downlink random access channel data frame format disclosed in the present invention;

[0022] Figure 3 A schematic diagram of a multi-frame format protocol template for an uplink broadcast channel disclosed in the present invention;

[0023] Figure 4 A schematic diagram of a frame format protocol of a response information frame disclosed in the present invention;

[0024] Figure 5 A schematic diagram of a frame format protocol of a remote control information frame disclosed in the present invention;

[0025] Figure 6A schematic diagram of a specific embodiment of a downlink random access data frame format protocol template disclosed in the present invention;

[0026] Figure 7 A schematic diagram of a specific embodiment of an uplink broadcast channel multiframe format protocol template disclosed in the present invention;

[0027] Figure 8 A schematic diagram of a specific embodiment of a frame format protocol template for a response information frame disclosed in the present invention;

[0028] Figure 9 A schematic diagram of a specific embodiment of a frame format protocol template of a remote control information frame disclosed in the present invention;

[0029] Figure 10 The present invention discloses a schematic diagram of a data frame format protocol transmission device for a satellite measurement and control random access system. DETAILED DESCRIPTION

[0030] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0031] By utilizing the frame format protocol template, the inventors can convert the data to be sent into the target frame format protocol according to the actual on-demand measurement and control needs, thereby improving the capability and efficiency of satellite measurement and control when the number of satellites increases significantly.

[0032] To this end, an embodiment of the present invention provides a transmission method based on a satellite random access system frame format protocol. The data frame format protocol involved in the method includes a downlink random access channel data frame format protocol and an uplink broadcast channel data frame format protocol. The downlink random access channel data frame format protocol is applied to application information transmission, heartbeat information transmission and telemetry information transmission, and the uplink broadcast channel data frame format protocol is applied to response information and remote control information. The specific steps are as follows: Figure 1 As shown, the processing flow includes:

[0033] Step 101: When the first target data to be transmitted is application information, heartbeat information, and telemetry information, a downlink random access channel data frame format protocol is obtained.

[0034] Request information is used to request a connection with ground equipment or satellites. Heartbeat information is periodic feedback from satellites to the ground regarding connection status. Telemetry information includes various data collected by satellites. The downlink ad hoc access channel data frame format protocol includes data used for data transmission using the ad hoc access channel.

[0035] In a specific implementation of this step, whether the first target data is application information, heartbeat information, or telemetry information can be determined based on the service corresponding to the first target data, or based on the data carried in the first target data. For example, when information for applying for connection with ground equipment or a satellite is detected in the first target, the first target data is determined to be application information. Subsequently, when the first target data is application information, heartbeat information, or telemetry information, a pre-stored downlink random access channel data frame format protocol can be obtained.

[0036] Step 102 : performing data conversion on the first target data based on a downlink random access channel data frame format protocol to obtain converted first target data, and transmitting the converted first target data using the downlink random access channel.

[0037] In a specific implementation of this step, when using the downlink ad hoc access channel for data transmission, it is necessary to first convert the format of the first target data. Therefore, the downlink ad hoc access channel data frame format protocol also includes a downlink ad hoc access channel frame format template for format conversion. Then, based on the downlink ad hoc access channel frame format template, data conversion is performed on the first target data to obtain converted first target data, and the converted first target data is transmitted using the downlink ad hoc access channel.

[0038] Optionally, the performing data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain converted second target data specifically includes: obtaining a downlink random access channel frame format template in the downlink random access channel data frame format protocol; performing data conversion on the first target data according to the downlink random access channel data frame format template to obtain converted first target data.

[0039] The downlink ad hoc access channel data frame format protocol includes a downlink ad hoc access channel frame format template, which is used to convert the format of the first target data into a downlink ad hoc access channel frame format. The fields included in the downlink ad hoc access channel frame format may be all fields in the downlink ad hoc access channel frame format template, or may be a portion of the fields in the downlink ad hoc access channel frame format template. In other words, the downlink ad hoc access channel frame format to which the data is converted may vary depending on the data included in the first target data.

[0040] Step 103: When second target data transmitted through the uplink broadcast channel is received, the uplink broadcast channel data frame format protocol is obtained.

[0041] The data transmitted via the uplink broadcast channel is the response information or remote control information that has undergone format conversion. Therefore, in order to obtain the response information or remote control information, it is necessary to first obtain the uplink broadcast channel data frame format protocol, and then convert the format of the already format-converted response information or remote control information based on the protocol to obtain the response information or remote control information.

[0042] Step 104 : performing data conversion on the second target data based on the uplink broadcast channel data frame format protocol to obtain converted second target data, and parsing the converted second target data to obtain response information or remote control information.

[0043] In the specific implementation of this step, in order to obtain response information or remote control information, the second target data can be converted based on the uplink broadcast channel data frame format protocol to obtain the converted second target data, and the converted second target data can be parsed to obtain response information or remote control information.

[0044] Optionally, the second target data is converted based on the uplink broadcast channel data frame format protocol to obtain the converted second target data. The specific steps include: obtaining the uplink broadcast channel data frame format template in the uplink broadcast channel data frame format protocol; performing data conversion on the second target data according to the uplink broadcast channel data frame format template to obtain the converted second target data.

[0045] The uplink broadcast channel data frame format protocol includes an uplink broadcast channel data frame format template, which is used to convert the format of the second target data into the uplink broadcast channel data frame format. The fields included in the uplink broadcast channel data frame format can be all fields in the uplink broadcast channel data frame format template, or can be part of the fields in the uplink broadcast channel data frame format template. In other words, the uplink broadcast channel data frame format to be converted varies depending on the data included in the second target data.

[0046] In an embodiment of the present invention, when the first target data to be transmitted is application information, heartbeat information, and telemetry information, a downlink ad-hoc access channel data frame format protocol is obtained; based on the downlink ad-hoc access channel data frame format protocol, the first target data is converted to obtain converted first target data, and the converted first target data is transmitted using the downlink ad-hoc access channel; when second target data transmitted via an uplink broadcast channel is received, an uplink broadcast channel data frame format protocol is obtained; based on the uplink broadcast channel data frame format protocol, the second target data is converted to obtain converted second target data, and the converted second target data is parsed to obtain response information or remote control information. This method can be applied to new ad-hoc access measurement and control systems and can meet the measurement and control needs of future mega-constellations.

[0047] Furthermore, the present invention provides a downlink random access data frame format protocol in the downlink random access channel frame format template, the specific structure Figure 2 As shown, the content of the downlink random access channel frame format template includes:

[0048] The pilot signal (also called the preamble code) is used to improve the acquisition speed and acquisition probability of the ground receiving system. The length of the pilot signal is variable, and the variable range is 0 to 1024 bits.

[0049] The frame synchronization word is used for access frame synchronization. The field length of the frame synchronization word is variable, ranging from 16 to 256 bits.

[0050] Version number. The length of the version number field is variable, ranging from 1 to 4 bytes.

[0051] Channel Flag field. In this embodiment, the channel flag field includes the following fields:

[0052] The applicant identifier is used to indicate the initiator of random access, including initial applications initiated by the satellite and the ground. The applicant identifier field has a variable length. The authentication flag is used to indicate whether authentication is used and the number of elements involved in the authentication. The authentication flag field has a variable length and can also indicate no authentication, single-element authentication (only verifying the satellite ID), and multiple elements (including verification of the satellite ID, ground segment ID, satellite status, and time code, etc.) involved in the authentication code calculation. The heartbeat cycle flag is used to indicate the heartbeat signal transmission period. The content of this identifier includes at least the heartbeat cycle, heartbeat silence, and future state extensions. The reserved field is mainly used for future expansion. The reserved field has a variable length.

[0053] Space segment identifier: The space segment identifier is used to identify space targets and can be set to a byte length as needed. Among them, constellation category: the identifier length is variable and can accommodate multiple large constellation users; satellite identifier: the identifier length n is variable and can accommodate up to 2 satellites. n . This identifier can be used as one of the authentication elements.

[0054] The ground segment identifier is used to identify ground targets. The ground segment identifier includes at least the ground tracking and control center identifier, the ground node station identifier, the ground user center identifier, and a reserved bit. This identifier can be used as an authentication factor.

[0055] The time code, where the time code represents the time with an accuracy of no less than 1ms, can be used as one of the authentication elements in the authentication code calculation to prevent fake stations from misusing the authentication code and replaying it.

[0056] Track parameters are used to represent real-time track data, and their field length is variable.

[0057] Satellite status is used to indicate the health status of the satellite. The field length is variable and the status flag can be used as one of the authentication factors.

[0058] The authentication vector is the symmetric key used in the authentication operation. It tells the ground party the symmetric key used in the authentication operation. The length of the authentication vector field can be set according to actual needs.

[0059] The access mode field is used to define parameters related to the access method and can set the type and number of access parameters as needed. This field primarily includes: ad hoc access type (contention-based or non-contention-based access); number of random transmissions (1 to 5); priority (normal, important, urgent, etc.); service type (network application frame, heartbeat frame, continuous transmission, etc.); service channel conversion flag (conversion between ad hoc access telemetry and traditional telemetry, measurement and control and data transmission channels, etc.); and next frame modulation and coding mode (specifying the coding mode, carrier modulation mode, spread spectrum modulation mode, information rate, etc. of the next frame, for future ACM applications). This field is variable in length, the order of the flags within it is variable, and an extension bit is reserved.

[0060] Authentication code: Generate an authentication code as needed. The length of this field ranges from 64 to 512 bytes. In this embodiment, the frame format protocol template uses a truncated authentication code, and the length of the truncated authentication code is variable.

[0061] Additional information mainly includes subsequent access information, detailed satellite health status, key telemetry information, etc., and its field length is variable.

[0062] CRC check code, which adopts the international or domestic standard CRC check method.

[0063] FEC coding uses Polar, LDPC, RS, and convolutional coding methods. The coding rates are 1 / 3, 1 / 2, 2 / 3, 3 / 4, and 5 / 6.

[0064] Furthermore, the uplink broadcast channel data frame format protocol in the present invention is an uplink multiframe format protocol, and the uplink multiframe format protocol includes an uplink multiframe protocol template. The specific structure of the uplink multiframe format protocol is as follows: Figure 3 As shown in the figure, the contents of the uplink multiframe format protocol template include:

[0065] The pilot signal (also known as the leading code) is used to improve the acquisition speed and acquisition probability of the satellite transponder. Its field length is variable and the variable range is 0 to 1024 bits.

[0066] The multiframe synchronization word is used for multiframe synchronization of the uplink broadcast channel. Its field length is variable and ranges from 32 to 128 bits.

[0067] The multiframe header can set the header parameters according to actual needs. The parameter identification type and length are variable. The multiframe header includes at least the following fields: version number, whose field length is variable, and the variable length range is 1 to 4 bits; constellation identifier, used to indicate the number of constellations that need to change the broadcast channel transmission mode, and its field length is variable; modulation mode flag, used to indicate multiple modulation modes, whose field length is variable and has extension bits; coding mode flag, used to indicate multiple coding modes, whose field length is variable and the coding rates include 1 / 3, 1 / 2, 2 / 3, 3 / 4 and 5 / 6, and has extension bits; spread spectrum code length flag, whose field length is variable and includes 1023 and 2047, etc., and has extension bits; address code flag, used to indicate the address code sequence used, the number of address codes is variable, and the available number is not less than 64; frequency configuration flag, used to indicate the frequency used, which is not less than 2 working frequency bands and 4 pairs of frequencies; scrambling code configuration flag, used to indicate the scrambling code sequence used. The following fields are provided: a column, including at least 3 scrambling code sequences; a pilot length flag, used to indicate the pilot length used in the broadcast channel, and its field length is variable; a data rate flag, used to indicate the data rate of the uplink broadcast channel, and its binning is variable, and an extension bit is reserved; a node station identifier; a response information frame number flag, used to indicate the number of response information frames in the current broadcast channel multiframe of this node, with a minimum number of 0 and a maximum number of 64; a remote control information frame number flag, used to indicate the number of remote control information frames in the current broadcast channel multiframe of this node, with a minimum number of 0 and a maximum number of 16; reserved: reserved for future expansion; a next broadcast frame configuration field, used to indicate the transmission system of the next broadcast channel multiframe, and its field length is variable; a CRC check code, used to set the CRC-8 or CRC-16 check field in the multiframe header; FEC coding, which adopts Polar, LDPC, RS, convolutional and other coding methods, and the coding rates include 1 / 3, 1 / 2, 2 / 3, 3 / 4 and 5 / 6.

[0068] Subframes are used to transmit response information frames and remote control information frames. The number of subframes can be dynamically configured based on traffic volume, and the subframe field length can be variable. In this embodiment, the length of the remote control information frame and the response information frame are the same or multiple of each other, and the ratio of the response information frame to the remote control information frame is dynamically adjusted.

[0069] Furthermore, the present invention provides a frame format template for a response information frame, the specific structure of which is as follows: Figure 4 As shown, the response information frame protocol includes the following fields:

[0070] Version number, the field length of which is variable, ranging from 1 to 4 bits, can be adjusted according to usage.

[0071] The channel flag field includes a responder identifier, which is used to specify the initiator of the initial application for random access, that is, the satellite party or the ground measurement and control network, and its field length is variable; a frame identification, which is used to indicate the type of the frame and identify whether the frame is a response information frame or a remote control information frame, and includes a reserved bit for future expansion; an authentication flag, which is used to indicate the type of authentication and the elements involved in the authentication, and its field length is variable; and a reserved bit, which is used for future expansion and its field length is variable.

[0072] Access control domain, wherein the access control domain includes: a response type flag, used to indicate a response to contention-based random access and a response to non-contention-based random access (a response to non-contention-based random access refers to a response to random access initiated on a specific wireless resource); an application confirmation flag, which includes authentication success, access allowed, and authentication failure, re-authentication; an access count flag, used to specify the number of times a downlink access frame is randomly sent; a power control flag, used to specify the transponder transmit power; a heartbeat pointer, used to indicate whether the heartbeat signal is generated by the satellite transponder itself or based on the frame signal transmitted from the ground; a heartbeat period flag, including no heartbeat signal (silence), a heartbeat period of 1 minute or 2 minutes; reserved: for future expansion, its field length is variable.

[0073] CRC check code, the CRC check code may be the same as the CRC in the random access channel frame, or may be different.

[0074] The FEC coding and the FEC error correction code may be the same as or different from the FEC of the random access channel frame.

[0075] Furthermore, the uplink multi-frame format protocol in the embodiment of the present invention further includes the response information frame format template and the remote control information frame format template. The specific structure of the remote control information frame format template is as follows: Figure 5 As shown, the remote control information frame includes: a version number, a type flag, a space segment flag, a terrestrial segment flag, an authentication vector, a time code, an extension bit, an authentication code, a remote control data field, and an FEC code. The version number, space segment flag, terrestrial segment flag, terrestrial segment status, authentication vector, time code, and authentication code in the remote control information frame format for the uplink broadcast channel are consistent with those in the response information frame. The channel flag field of the response information frame and the type flag field of the remote control information frame have the same length, but the flag content is different. The access control field of the response information frame and the extension bit length of the remote control information frame have the same length, but the flag content is different. The remote control data field follows the authentication code, and the remote control data field is followed by the FEC code. Furthermore, the field length of the remote control information frame for the uplink broadcast channel is variable.

[0076] Further, such as Figure 6 As shown, a specific embodiment of a downlink frame format protocol template provided by the present invention is shown, and the specific contents are as follows:

[0077] The pilot signal is used to improve the capture speed and capture probability of the ground station demodulation equipment. The field length is 208 bits.

[0078] Frame synchronization word, used for synchronization of random access frames, with a field length of 32 bits.

[0079] Version number, the field length is 2 bytes. The version number can be adjusted according to usage and is currently set to 00.

[0080] Channel flag field. The field length of the channel flag field is 6 bits, where:

[0081] The requester flag indicates the initiator of the random access request. Its field length is 1 bit. Specifically, a value of 0 indicates that the satellite initiates the initial request; a value of 1 indicates that the ground tracking and control network initiates the initial request. This flag is currently set to 0, indicating that the satellite initiates the access request.

[0082] Authentication flag, the field length is 2 bits. Specifically, 00 means no authentication; 01 means normal authentication (the authentication element is only the satellite ID); 11 means more elements participate in the authentication code calculation; 10 is reserved for future expansion.

[0083] Heartbeat period: The field length is 2 bytes. Specifically, 01 indicates a heartbeat with a sending period of 1 minute; 10 indicates a heartbeat with a sending period of 2 minutes; 00 indicates that the heartbeat signal is in silent state; and 11 is reserved for future expansion.

[0084] Reserved for future expansion, its field length is 1b.

[0085] Space segment identifier: The field length of the space segment identifier is 16 bits, of which: the field length of the constellation category is 2 bits, which is used to indicate that a maximum of 4 giant constellation users can be accommodated. 00 is a public constellation; 01, 10, and 11 are dedicated constellations respectively; the field length of the satellite identifier is 14 bits, which is used to indicate that a maximum of 16,384 satellites can be accommodated;

[0086] Ground segment identification: The field length of the ground segment identification is 16 bits, of which: the field length of the ground measurement and control center identification is 2 bits, specifically 11 represents the primary center, 00 represents the backup center, and the others are reserved for future expansion; the field length of the ground node station identification is 5 bits, which can accommodate up to 32 access nodes worldwide; the field length of the ground user center identification is 7 bits, which supports up to 128 ground user centers; the reserved field length is 2 bits for future expansion.

[0087] The time code field has a length of 32 bits and is used to represent time with an accuracy of no less than 1ms.

[0088] Orbital parameters are used to represent real-time satellite orbit data. The field length is 240 bits, and the orbit data format complies with relevant requirements.

[0089] Satellite status: The satellite status field is 64 bits long and is used to indicate the health status of the satellite platform and its payload.

[0090] Authentication vector: The authentication vector field is 10 bits long and is used to represent the symmetric key used in the authentication operation. It informs the ground segment of the symmetric key used in the authentication operation. When all 0s are present, it is non-encrypted authentication.

[0091] Access mode domain, the field length of the access mode domain is 14b, of which: the field length of the random access type is 1b, specifically, 0 represents contention random access (initial access), and 1 represents non-contention random access (random access initiated on a specific wireless resource); the field length of the random number of transmissions is 2b, specifically, 01 represents transmission 1 time, 10 represents transmission 2 times, 11 represents transmission 3 times, and 00 is reserved for future expansion; the field length of the priority level is 2b, specifically, 00 represents normal, 01 represents important, 11 represents urgent, and 10 represents future expansion; the field length of the service type is 2b, specifically, 00 represents the frame is only a network application frame; 01 represents a heartbeat frame (entry network application is authenticated); 11 is continuous transmission (download of initial telemetry data after separation of satellite and rocket, used for initial capture by ground station, and downlink of long telemetry data stream under special circumstances); 10 is reserved for future expansion; the field length of the service channel conversion flag is 2 bits, specifically, 00 means use of this access channel (no conversion); 01 means switching to a traditional telemetry channel, and 10 means switching to a traditional data transmission channel; 11 is reserved for future expansion; the field length of the next frame modulation and coding is 5 bits, which is used to define the coding mode, carrier modulation mode, spread spectrum modulation mode, information rate, etc. of the next frame, among which the first bit is reserved for future expansion and is currently set to 0, and the last 4 bits are used to represent the modulation and coding combination.

[0092] The field length of the truncated authentication code is 16 bits, and it is truncated according to the generated authentication code 256 bits.

[0093] The field length of additional information is 64 bits, and the additional information mainly includes detailed health status, key telemetry information, subsequent access information, etc.

[0094] CRC check: The random access channel uses the CRC-16 check method, and its field length is 16 bits.

[0095] FEC coding uses Polar coding with a coding rate of 2 / 3 and a field length of 264 bits.

[0096] Furthermore, the modulation and coding combinations in this embodiment are shown in Table 1, which are as follows:

[0097]

[0098] Table 1 Modulation and coding combinations [注1]

[0099] Among them, [Note 1] in Table 1: represents the random access channel modulation and coding combination information released by the transmission channel; [Note 2] in Table 1: represents the address code released by the transmission channel, the number of address codes is greater than 16, and the address code is optional.

[0100] Further, such as Figure 7 As shown, a specific embodiment of an uplink multiframe format protocol template provided by the present invention is as follows:

[0101] The pilot field length is 256 bits.

[0102] The multiframe synchronization word field length is 64 bits.

[0103] The length of the multiframe header field is 144 bits, of which the length of the version number field is 2 bits and is set to 00; the length of the constellation identifier field is 6 bits; the length of the modulation mode field is 2 bits, 00 is OQPSK, and the others are reserved for future expansion; the length of the coding mode field is 2 bits, 00 is Polar code, coding rate 3 / 4, and the others are reserved for future expansion; the length of the spreading code length field is 2 bits, 00 is 2047, and the others are reserved for future expansion; the length of the address code field is 6 bits, with a maximum of 64 address codes; the length of the frequency configuration field is 2 bits; the length of the scrambling code configuration field is 2 bits, and when using Polar code, it is not When using scrambling code, this flag is set to 00; the pilot length field is 2 bits long; the data rate field is 2 bits long, with 00 indicating 8 kb / s and 01 indicating 16 kb / s, and others reserved for future expansion; the node station identification field is 5 bits long; the response information frame number indication field is 5 bits long, with a maximum of 32 response information frames; the remote control information frame number indication field is 4 bits long, with a maximum of 16 remote control information frames; the reserved field is 6 bits long; the next broadcast frame configuration field is 48 bits long; the header FEC field is 48 bits long, using Polar code with a coding rate of 2 / 3.

[0104] Subframe. The number of subframes is variable, and the subframe types include: response information frame and remote control information frame.

[0105] Further, such as Figure 8 As shown in FIG. 1 , a specific embodiment of the response information frame protocol provided by the present invention is shown. In this embodiment, the field length of the response information frame is 144 bits, where:

[0106] The version number field is 2 bytes long and is currently set to 00.

[0107] The channel flag field is 6 bits long, of which the responder identification field is 1 bit long, where 0 indicates that the ground measurement and control network is the responder and 1 indicates that the satellite is the responder. In this embodiment, it is set to 0. The frame identification field is 2 bits long, where 00 indicates that the frame is a response information frame; 11 indicates that the frame is a remote control information frame. The other bits are reserved for future use. The authentication flag field is 2 bits long, where 00 indicates no authentication; 01 indicates ordinary authentication (the authentication element is only the satellite ID); 11 indicates that more elements participate in the authentication code calculation; 10 is reserved for future expansion. The reserved field is 1 bit long.

[0108] The access control field is 16 bits long, of which: the response channel mode field is 1 bit long, 0 indicates a contention-based access response, and 1 indicates a non-contention-based access response (a contention-based access response initiated on a specific wireless resource); the application confirmation field is 2 bits long, 11 indicates successful authentication and access is allowed; 00 indicates unsuccessful authentication and re-authentication, and other fields are reserved; the access number control field is 2 bits long, 01 indicates 1 time, 10 indicates 2 times, 11 indicates 3 times, and 00 is reserved for future expansion; the power control field is 2 bits long, 00 indicates the transponder transmit power is rated; other values ​​are reserved for future expansion. The heartbeat pointer field is 1 bit long; 1 indicates the heartbeat signal is generated by the satellite transponder itself; 0 indicates the transponder generates the heartbeat signal based on the frame signal transmitted from the ground. In this embodiment, it is set to 1. The heartbeat period control field is 2 bits long; 00 indicates no heartbeat signal (silence); 01 indicates a heartbeat transmission period of 1 minute; 10 indicates a heartbeat transmission period of 2 minutes; 11 is reserved for future expansion; the default value is 01. The reserved field is 6 bits long. Other fields in this embodiment are consistent with the embodiment shown in the access frame.

[0109] Extension domain, used for future expansion.

[0110] CRC check: In this embodiment, the response information frame adopts the CRC-16 check method.

[0111] FEC coding: In this embodiment, Polar coding is used for the response information frame, and the coding rate is 2 / 3.

[0112] Further, such as Figure 9 As shown in the figure, it is a specific embodiment of the remote control information frame protocol provided by the present invention, wherein the extension bit field length is 8b, which is reserved for future applications; the remote control data field is used to insert the CCSDS remote control transmission frame, and the maximum length field length is 8080b. The remaining other domains or fields in this implementation are consistent with the response information frame.

[0113] Furthermore, as mentioned above Figures 1 to 9The implementation of the processes, protocols and embodiments shown in the figure, the embodiment of the present invention provides a transmission device based on the satellite random access system frame format protocol, the device can be applied to the new random access measurement and control system, and can be suitable for the measurement and control needs of future giant constellations. The embodiment of the device corresponds to the aforementioned protocol and embodiment. For ease of reading, this embodiment will no longer repeat the details of the aforementioned protocol embodiment one by one, but it should be clear that the device in this embodiment can correspond to all the contents of the aforementioned protocol embodiment. The data frame format protocol includes a downlink random access channel data frame format protocol and an uplink broadcast channel data frame format protocol. The downlink random access channel data frame format protocol is used for application information transmission, heartbeat information transmission and telemetry information transmission, and the uplink broadcast channel data frame format protocol is used for response information and remote control information. Figure 10 As shown, the device includes:

[0114] The first acquiring unit 1001 is configured to acquire a downlink random access channel data frame format protocol when the first target data to be transmitted is application information, heartbeat information, and telemetry information;

[0115] A first conversion unit 1002 is configured to perform data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain converted first target data, and transmit the converted first target data using the downlink random access channel;

[0116] The second acquiring unit 1003 is configured to acquire an uplink broadcast channel data frame format protocol when receiving second target data transmitted via the uplink broadcast channel;

[0117] The second conversion unit 1004 is used to perform data conversion on the second target data based on the uplink broadcast channel data frame format protocol to obtain converted second target data, and parse the converted second target data to obtain response information or remote control information.

[0118] Optionally, the first conversion unit 1002 is further configured to:

[0119] Obtaining a downlink random access channel frame format template in a downlink random access channel data frame format protocol;

[0120] The first target data is converted according to the downlink random access channel data frame format template to obtain converted first target data.

[0121] Optionally, the second conversion unit 1004 is further configured to:

[0122] Obtaining an uplink broadcast channel data frame format template in the uplink broadcast channel data frame format protocol;

[0123] The second target data is converted according to the uplink broadcast channel data frame format template to obtain converted second target data.

[0124] Optionally, the fields included in the downlink random access channel frame format template are: pilot, frame synchronization word, version number, channel flag field, space segment identifier, ground segment identifier, time code, orbit parameters, satellite status, authentication vector, access mode field, authentication code, additional information, CRC check code and FEC code, wherein the field length range of the pilot is 0 to 1024b, the field length range of the frame synchronization word is 16 to 256b, the field length range of the version number is 1 to 4b, the field length range of the authentication code is 64 to 512b, and the fields included in the channel flag field are: applicant identifier, authentication flag, heartbeat cycle flag and reserved.

[0125] Optionally, the uplink broadcast channel data frame format protocol is an uplink multiframe format protocol, and the uplink multiframe format protocol includes the response information frame format template and the remote control information frame format template.

[0126] Optionally, the uplink multiframe format template includes fields such as: pilot, multiframe synchronization word, multiframe header and at least one subframe, wherein the field length of the pilot ranges from 0 to 1024b, the field length of the multiframe synchronization word ranges from 32 to 128b, and the fields included in the multiframe header include: version number, constellation identifier, modulation mode flag, coding mode flag, spread spectrum code length flag, address code flag, data rate flag, frequency configuration flag, scrambling code configuration flag, pilot length flag, node station identifier, response information frame number flag, remote control information frame number flag, reserved, next broadcast frame configuration field, CRC check, and FEC encoding.

[0127] Optionally, the response information frame format template includes the following fields: version number, channel flag field, space segment identifier, ground segment identifier, authentication vector, time code, access control field, authentication code, CRC checksum and FEC code, wherein the channel flag field includes the following fields: responder identifier, frame identification, authentication flag and reservation; the access control field includes the following fields: response mode flag, application confirmation flag, access times flag, power control flag, heartbeat pointer, heartbeat cycle flag and reservation; the space segment identifier is used to identify space targets, and includes the following fields: constellation identifier and satellite identifier; the ground segment identifier is used to identify ground targets, and the fields of the package are: measurement and control center identifier, ground station area identifier, user center identifier and reservation; the ground segment status is used for the satellite to understand the working status of the ground equipment.

[0128] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0129] It is understood that the relevant features in the above protocols and devices can refer to each other. In addition, the "first" and "second" in the above embodiments are used to distinguish between the embodiments, and do not represent the advantages and disadvantages of the embodiments.

[0130] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned protocol embodiments and will not be described in detail here.

[0131] The algorithm and display provided herein are not inherently related to any particular computer, virtual system or other device. Various general-purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious that the structure required for constructing such systems. In addition, the present invention is not directed to any specific programming language. It should be understood that various programming languages ​​can be utilized to implement the content of the present invention described herein, and the above description of specific languages ​​is for the purpose of disclosing the best mode of the present invention.

[0132] In addition, the memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0133] Those skilled in the art will appreciate that embodiments of the present invention may be provided as systems, devices, protocols, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0134] The present invention is described with reference to flowcharts and / or block diagrams of protocols, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0135] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0136] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0137] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0138] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0139] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0140] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0141] Those skilled in the art will appreciate that embodiments of the present invention may be provided as protocols, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0142] The above are merely embodiments of the present invention and are not intended to limit the present invention. Those skilled in the art will appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements within the data frame format protocol and implementation principles of the present invention are intended to be included within the scope of the claims of the present invention.

Claims

1. A transmission method based on a satellite random access system frame format protocol, characterized in that: The data frame format protocol includes a downlink random access channel data frame format protocol and an uplink broadcast channel data frame format protocol. The downlink random access channel data frame format protocol is applied to application information transmission, heartbeat information transmission, and telemetry information transmission. The uplink broadcast channel data frame format protocol is applied to response information and remote control information. The method includes: When the first target data to be transmitted is application information, heartbeat information and telemetry information, obtaining a downlink random access channel data frame format protocol; performing data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain converted first target data, and transmitting the converted first target data using the downlink random access channel; When receiving second target data transmitted through the uplink broadcast channel, obtaining an uplink broadcast channel data frame format protocol; Based on the uplink broadcast channel data frame format protocol, the second target data is converted to obtain converted second target data, and the converted second target data is parsed to obtain response information or remote control information.

2. The transmission method according to claim 1, wherein: The step of performing data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain the converted first target data includes: Obtaining a downlink random access channel frame format template in a downlink random access channel data frame format protocol; The first target data is converted according to the downlink random access channel frame format template to obtain converted first target data.

3. The transmission method according to claim 1, wherein: The performing data conversion on the second target data based on the uplink broadcast channel data frame format protocol to obtain the converted second target data includes: Obtaining an uplink broadcast channel data frame format template in the uplink broadcast channel data frame format protocol; The second target data is converted according to the uplink broadcast channel data frame format template to obtain converted second target data.

4. The transmission method according to claim 2, wherein: The downlink random access channel frame format template includes the following fields: pilot, frame synchronization word, version number, channel flag field, space segment identifier, ground segment identifier, time code, orbital parameters, satellite status, authentication vector, access mode field, authentication code, additional information, CRC checksum and FEC code, wherein the field length of the pilot is in the range of 0 to 1024b, the field length of the frame synchronization word is in the range of 16 to 256b, the field length of the version number is in the range of 1 to 4b, and the field length of the authentication code is in the range of 64 to 512b, and the fields included in the channel flag field are: applicant identifier, authentication flag, heartbeat cycle flag and reserved.

5. The transmission method according to claim 3, wherein: The uplink broadcast channel data frame format protocol is an uplink multiframe format protocol, and the uplink multiframe format protocol includes a response information frame format template and a remote control information frame format template. The transmission method according to claim 3, wherein: The uplink broadcast channel data frame format template includes the following fields: a pilot, a multiframe synchronization word, a multiframe header, and at least one subframe. The pilot field length ranges from 0 to 1024 bits, the multiframe synchronization word field length ranges from 32 to 128 bits, and the multiframe header includes the following fields: a version number, a constellation identifier, a modulation mode flag, a coding mode flag, a spreading code length flag, an address code flag, a data rate flag, a frequency configuration flag, a scrambling code configuration flag, a pilot length flag, a node station identifier, a response information frame number flag, a remote control information frame number flag, a reserved field, a next broadcast frame configuration field, a CRC checksum, and an FEC code.

7. The transmission method according to claim 5, characterized in that The fields included in the response information frame format template are: version number, channel flag field, space segment identifier, ground segment identifier, authentication vector, time code, access control field, authentication code, CRC check code and FEC code, wherein the fields included in the channel flag field are: responder identifier, frame identification, authentication flag and reservation; the fields included in the access control field are: response mode flag, application confirmation flag, access number flag, power control flag, heartbeat pointer, heartbeat cycle flag, reservation; the space segment identifier is used to identify space targets, and the fields included are: constellation identifier, satellite identifier; the ground segment identifier is used to identify ground targets, and the fields included are: measurement and control center identifier, ground station area identifier, user center identifier, and reservation; the ground segment status is used for the satellite to understand the working status of the ground equipment.

8. A transmission device based on a satellite random access system frame format protocol, characterized in that: The data frame format protocol includes a downlink random access channel data frame format protocol and an uplink broadcast channel data frame format protocol. The downlink random access channel data frame format protocol is applied to application information transmission, heartbeat information transmission, and telemetry information transmission. The uplink broadcast channel data frame format protocol is applied to response information and remote control information. The device includes: A first acquiring unit is configured to acquire a downlink random access channel data frame format protocol when the first target data to be transmitted is application information, heartbeat information, and telemetry information; a first conversion unit, configured to perform data conversion on the first target data based on the downlink random access channel data frame format protocol to obtain converted first target data, and transmit the converted first target data using the downlink random access channel; a second acquiring unit, configured to acquire an uplink broadcast channel data frame format protocol when receiving second target data transmitted via the uplink broadcast channel; The second conversion unit is used to perform data conversion on the second target data based on the uplink broadcast channel data frame format protocol to obtain converted second target data, and parse the converted second target data to obtain response information or remote control information.

9. A terminal, characterized in that: The terminal is used to run a program, wherein the terminal executes the transmission method based on the satellite random access system frame format protocol according to any one of claims 1 to 7 when running.

10. A storage medium, characterized in that: The storage medium is used to store a computer program, wherein when the computer program is running, it controls the device where the storage medium is located to execute the transmission method based on the satellite random access system frame format protocol according to any one of claims 1 to 7.

Images