Satellite gateway station access anti-collision method and satellite Internet of Things system

Abstract

The invention provides a satellite gateway station access anti-collision method and a satellite Internet of Things system, and the method comprises the steps: enabling a plurality of gateway stations to receive downlink signals of the same satellite, and building a unified system time synchronization reference; each gateway station determines a basic sending period of the gateway station according to the unique identifier of the gateway station, so that the basic sending periods of the gateway stations are co-prime pairwise and are smaller than a heartbeat success window preset by the system; and by taking the system time synchronization reference as a starting point, each gateway station continuously sends a plurality of heartbeat frames to the satellite in each heartbeat success window according to a basic sending period of the gateway station, and at least one heartbeat frame successfully arrives at the satellite. According to the method and the device, a heartbeat sending mechanism is designed by adopting a co-prime period, so that the problem that a gateway station is offline due to heartbeat frame sending collision is solved, and distributed, low-complexity and high-reliability heartbeat reporting is realized.

Description

Technical Field

[0001] This application relates to the field of satellite Internet of Things (IoT) communication technology, and in particular to a satellite gateway station access anti-collision method and a satellite IoT system. Background Technology

[0002] In narrowband IoT systems based on low-Earth orbit satellites, a massive number of gateway stations distributed on the ground undertake the critical task of aggregating data from IoT terminals and transmitting it back to the data center via satellite links. To maintain an active communication link with the satellite, the gateway stations need to periodically send heartbeat frames to the satellite. Once the satellite successfully receives and identifies a gateway station's heartbeat frame, it determines that the gateway station is online and can then establish or maintain a subsequent data transmission channel for it.

[0003] However, in a typical system architecture, a satellite is usually configured with only one narrowband channel for receiving such uplink signaling at any given time. When multiple gateway stations within the coverage area of ​​the same satellite beam need to remain online simultaneously, they will compete for the use of this shared channel to send heartbeat frames. Because gateway stations are deployed in diverse environments and often require low-power operation, precise, centralized, real-time scheduling is difficult to achieve. Therefore, the heartbeat frame transmission times of multiple gateway stations may overlap randomly or periodically, causing signal collisions at the satellite receiver. This prevents the satellite from parsing any frame, leading to an incorrect determination that the relevant gateway station is offline, resulting in communication link interruptions and severely impacting system reliability and service continuity.

[0004] To address the collision issue in communication access, various access control schemes exist in existing technologies, but they all have significant limitations in the heartbeat reporting scenario of gateway stations for low-Earth orbit satellite narrowband IoT:

[0005] Fixed time slot allocation methods based on centralized scheduling (such as TDMA): This method allocates fixed, non-overlapping time slots to each gateway station for transmission. While it can completely avoid collisions, it relies on a powerful central controller for precise time slot planning and network-wide time synchronization. This not only increases the complexity and cost of the system, but also makes it inflexible to adapt to situations where gateway stations dynamically join, leave, or fail, and is unsuitable for satellite IoT scenarios that pursue distributed, autonomous access.

[0006] Contention-based methods using random access (such as pure ALOHA, slotted ALOHA, and their variants): These methods allow gateway stations to randomly select a time to transmit when needed. Their advantage is complete distribution, requiring no central coordination. However, their fundamental drawback is that as the number of active gateway stations increases, leading to increased channel load, the collision probability grows exponentially. To ensure a certain success rate, the transmission frequency must be significantly reduced, which directly prolongs the heartbeat reporting delay, failing to meet the system's requirement for rapid confirmation of gateway station online status. Although there are improved mechanisms such as Carrier Sense Multiple Access (CSMA), the long propagation delay characteristic of satellite communication limits the effectiveness of CSMA and cannot effectively avoid collisions.

[0007] Collision decomposition or retransmission coordination methods: These schemes, upon detecting a collision, use specific algorithms (such as tree splitting or backoff algorithms) to allow the colliding station to retry transmitting. While this can improve the final success rate, it introduces additional signaling interactions, complex processing logic, and unpredictable latency. For gateway stations with simple structures, limited resources, and that only transmit short small-bounce frames, this means a significant increase in hardware cost, power consumption, and processing complexity, making it unsuitable for large-scale, low-cost IoT infrastructure deployments.

[0008] In summary, existing technologies struggle to achieve a good balance between key requirements such as no need for central scheduling, low implementation complexity, high access reliability, and low communication latency. Therefore, a distributed access method is urgently needed that enables multiple gateway stations to ensure, with a high probability of deterministic delivery of their heartbeat frames to the satellite within a specified time window, even without real-time coordination, thereby robustly maintaining network connectivity. Summary of the Invention

[0009] In view of this, this application proposes a satellite gateway station access anti-collision method and a satellite Internet of Things system. By adopting a coprime periodic design heartbeat transmission mechanism, the problem of gateway station offline caused by heartbeat frame transmission collision is solved, realizing distributed, low-complexity, and highly reliable heartbeat reporting.

[0010] Firstly, this application provides a satellite gateway station access anti-collision method, including:

[0011] Multiple gateway stations receive downlink signals from the same satellite, establishing a unified system time synchronization reference;

[0012] Each gateway station determines its basic transmission period based on its unique identifier, so that the basic transmission periods of each gateway station are coprime to each other and are less than the system's preset heartbeat success window.

[0013] Starting from the system time synchronization reference, each gateway station continuously sends several heartbeat frames to the satellite within each heartbeat success window according to its basic transmission cycle, and at least one heartbeat frame successfully reaches the satellite.

[0014] Therefore, the satellite gateway station access anti-collision method provided in this application establishes a unified system time synchronization benchmark and mutually prime basic transmission periods for each gateway station. Within any heartbeat success window, due to the mutually prime period characteristics, the transmission sequences of each gateway station have a very high probability of being misaligned, ensuring that each gateway station has at least one opportunity to transmit a heartbeat frame without collision. This reliably maintains the online state, realizing a highly reliable, fully distributed, and zero-scheduling-overhead access mechanism, significantly improving the utilization efficiency of satellite single-channel resources and the determinism of maintaining the system's online state.

[0015] Optionally, each gateway station determines its basic transmission period based on its unique identifier, specifically including:

[0016] Each gateway station selects a base transmission period from a predefined set of coprime numbers based on its unique identifier. This set of coprime numbers is a set of prime numbers.

[0017] As described above, by using a set of prime numbers as a predefined set of coprime numbers, where elements in the set are pairwise coprime, each gateway station selects its basic transmission period from this set of prime numbers based on a unique identifier (such as an ID hash). This naturally guarantees the coprime nature of the basic transmission periods of each gateway station, eliminating the need for complex calculations or rules and simplifying the process of determining the basic transmission period.

[0018] Optionally, the gateway station sends heartbeat frames in a deterministic manner. When heartbeat frames sent by two gateway stations collide, the collision is ignored and the next heartbeat frame is sent.

[0019] As described above, by adopting a deterministic transmission method, when a heartbeat frame collision occurs, the collision is ignored and the system waits to send the next heartbeat frame. This ensures that the gateway station can continuously send signals to the satellite without interrupting the communication process due to occasional collisions, thus maintaining the continuity of communication between the gateway station and the satellite. This approach eliminates the need for complex collision detection and resolution mechanisms, reducing system complexity, decreasing the processing burden on the gateway station and the satellite, and improving system operating efficiency.

[0020] Optionally, when the preset time node is reached, each gateway station will receive the downlink signal from the satellite again, and re-establish a unified system time synchronization reference based on the downlink signal. Starting from the re-established system time synchronization reference, the periodic transmission of heartbeat frames will be re-executed.

[0021] The preset time node is the moment after an integer number of successful heartbeat windows have passed, starting from the system time synchronization benchmark.

[0022] As mentioned above, during actual operation, the system time may be affected by various factors (such as hardware precision, environmental interference, etc.). By periodically resynchronizing, these time errors can be effectively compensated, ensuring the time synchronization accuracy of each gateway station, thereby maintaining the accuracy and stability of signal transmission.

[0023] Optional, also includes:

[0024] The number of times each gateway station successfully receives a heartbeat frame from the satellite within multiple consecutive successful heartbeat windows is counted. When the number of successful arrivals of a certain gateway station is lower than a preset threshold, a new basic transmission period that is coprime to the basic transmission periods of other gateway stations is determined for that gateway station.

[0025] As described above, by statistically analyzing the number of heartbeat frames successfully reaching the satellite from each gateway station within multiple consecutive successful heartbeat windows, when the number of successful arrivals for a particular gateway station falls below a preset threshold, its base transmission period is redefined to be coprime with the base transmission periods of other gateway stations. This dynamic adjustment mechanism can promptly identify gateway stations with poor communication performance based on their actual communication conditions, and optimize the overall system's communication performance by adjusting their transmission periods, thereby improving the signal transmission success rate and ensuring the stability and reliability of communication between gateway stations and the satellite.

[0026] Secondly, this application provides a satellite Internet of Things (IoT) system, including interconnected satellites, a data center, and multiple gateway stations, each gateway station comprising:

[0027] The synchronization module is used to receive downlink signals from the satellite and establish a unified system time synchronization reference.

[0028] The period generation module is used to determine the basic transmission period of each gateway station based on its unique identifier, so that the basic transmission periods of each gateway station are coprime and less than the system's preset heartbeat success window.

[0029] The transmission control module is used to continuously send several heartbeat frames to the satellite within each heartbeat success window, starting from the system time synchronization reference and according to a determined basic transmission period, and at least one heartbeat frame successfully reaches the satellite.

[0030] Optionally, the data center stores a predefined set of coprime numbers, and the period generation module selects one from the set of coprime numbers as its basic transmission period based on the unique identifier of the gateway station. The set of coprime numbers is a set of prime numbers.

[0031] Thirdly, this application provides a computing device, the computing device comprising:

[0032] processor;

[0033] Memory, used to store one or more programs;

[0034] When the processor executes one or more programs, it enables the processor to implement the aforementioned satellite gateway station access anti-collision method.

[0035] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, implements the aforementioned satellite gateway station access anti-collision method.

[0036] These and other aspects of this application will become more apparent in the description of the following embodiments(s). Attached Figure Description

[0037] Figure 1 This is an architectural diagram of a satellite Internet of Things system according to an embodiment of this application;

[0038] Figure 2 A flowchart illustrating a satellite gateway station access anti-collision method provided in this application embodiment;

[0039] Figure 3 This is a schematic diagram of the transmission timing of the gateway station within the heartbeat success window in an embodiment of this application;

[0040] Figure 4 A structural diagram of a gateway station provided in an embodiment of this application;

[0041] Figure 5 This is a structural diagram of a computing device provided in an embodiment of this application.

[0042] It should be understood that the dimensions and shapes of the block diagrams in the above structural diagrams are for reference only and should not constitute an exclusive interpretation of the embodiments of this application. The relative positions and inclusion relationships between the block diagrams presented in the structural diagrams are only schematic representations of the structural relationships between the block diagrams, and are not intended to limit the physical connection methods of the embodiments of this application. Detailed Implementation

[0043] The technical solutions provided in this application will be further described below with reference to the accompanying drawings and embodiments. It should be understood that the system architecture and business scenarios provided in the embodiments of this application are mainly for illustrating possible implementations of the technical solutions of this application and should not be construed as the sole limitation on the technical solutions of this application. Those skilled in the art will recognize that the technical solutions provided in this application are equally applicable to similar technical problems as system architectures evolve and new business scenarios emerge.

[0044] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. In case of any inconsistency, the meaning set forth in this specification or derived from the content described herein shall prevail. Furthermore, the terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit the scope of this application.

[0045] The solutions provided in this application will now be described in detail with reference to the accompanying drawings and embodiments.

[0046] This application proposes a collision avoidance method for satellite gateway station access. Under a unified time reference, by assigning each gateway station a unique, coprime-to-prime base transmission period, it ensures that within any time window of any length, each gateway station has at least one opportunity to send a heartbeat frame without colliding with other gateway stations, thus reliably maintaining its online status. This method offers advantages such as high reliability, full distribution, low complexity, low latency, good scalability, and backward compatibility, making it suitable for large-scale gateway station deployment scenarios in satellite IoT systems.

[0047] like Figure 1 The diagram illustrates a satellite Internet of Things (IoT) system architecture provided in this application embodiment. The satellite IoT system includes low-Earth orbit (LEO) satellites communicating with each other and N ground gateway stations (N≥3). The LEO satellites are configured with a single uplink receiving channel that supports millisecond-level short frame reception, used to receive heartbeat frames sent by each gateway station. After successfully receiving and identifying the heartbeat frame of a gateway station, the satellite determines that the gateway station is online and establishes or maintains a subsequent data transmission channel with it.

[0048] In some embodiments, the satellite IoT system may also set up a ground data center that communicates with the satellite and N ground gateway stations respectively. The ground data center can be used to preconfigure coprime period sets, allocate unique identifiers for gateway stations, and monitor the heartbeat reporting status of gateway stations.

[0049] based on Figure 1 The satellite IoT system shown in this application provides a satellite gateway station access anti-collision method, referring to... Figure 2 As shown, the method includes:

[0050] S110: Multiple gateway stations receive downlink signals from the same satellite to establish a unified system time synchronization reference.

[0051] In this step, the satellite can continuously broadcast downlink signals to the ground according to the broadcast period (e.g., 100ms). The downlink signal contains a system timestamp. Each gateway station connected to the satellite continuously listens to the downlink signal and extracts the system timestamp in the downlink signal as a local time reference, thereby establishing a unified system time synchronization reference T0 and ensuring that all gateway stations can work based on the same satellite time reference.

[0052] S120: Each gateway station determines its basic transmission period based on its unique identifier, so that the basic transmission periods of each gateway station are coprime to each other and are less than the system's preset heartbeat success window.

[0053] After establishing a unified system time synchronization reference T0, each gateway station can select one from a predefined set of coprime numbers as its basic transmission period T based on its assigned unique identifier (such as ID1, ID2, ID3...IDN). i Among them, the gateway station determines its basic transmission period T. i The method can be a simple mapping (such as the ID order corresponding to the element order in the set of coprime numbers), or a hash algorithm can be used to calculate the index, thereby ensuring the T of each gateway station. i The values ​​are pairwise coprime, and each T i The values ​​are all less than the system's preset heartbeat success window T. win The heartbeat success window T win Typically, this is the core time threshold for the system to determine if a gateway station is online. The gateway station must be online within any heartbeat success window T. win A gateway station must complete at least one valid heartbeat report within a given timeframe to enable the satellite to determine that the gateway is online and to establish or maintain a subsequent data transmission channel with it.

[0054] In some embodiments, the predefined set of coprime numbers can be a set of prime numbers. Since the elements in the set of prime numbers are pairwise coprime and are infinitely distributed among natural numbers, the coprimeness of the basic transmission period of each gateway station can be naturally guaranteed, without the need for complex calculations or complex rules, thus simplifying the process of determining the basic transmission period.

[0055] S130: Starting from the system time synchronization reference, each gateway station continuously sends several heartbeat frames to the satellite within each heartbeat success window according to its basic transmission cycle, and at least one heartbeat frame successfully reaches the satellite.

[0056] Complete the system time synchronization reference T0 and the basic transmission period T i Once the system time synchronization reference T0 is determined, each gateway station can use it as the starting point and proceed according to its basic transmission period T. i Generate heartbeat transmission sequence: S i = { k * T i| k = 1,2, 3, ...}, and continuously send heartbeat frames to the satellite according to this heartbeat transmission sequence, that is, at T0+T respectively. i T0+2T i T0+3T i Heartbeat frames are sent at all times. This transmission process is deterministic and does not require listening to the channel state. If the transmission times of two or more gateway stations overlap (i.e., a collision occurs), the gateway station does not perform any collision detection, backoff, or retransmission operations, but simply waits for the next transmission time to continue sending heartbeat frames according to the original transmission sequence.

[0057] In some embodiments, after receiving a heartbeat frame, the satellite demodulates and decodes the frame. If the unique identifier of the gateway station is successfully identified, the online status of the gateway station is recorded, and the successful reception information is fed back to the data center via the downlink channel. The data center counts the number of times each gateway station's heartbeat frames successfully reach the satellite within multiple consecutive (e.g., 3) heartbeat success windows. When the number of successful arrivals for a gateway station falls below a preset threshold (e.g., 2 times), a period reallocation process is triggered. A prime number that is not occupied by other gateway stations and is coprime to the basic transmission period of other gateway stations is selected from the predefined set of coprime numbers as the new basic transmission period for that gateway station. This ensures that the gateway station transmits heartbeat frames according to the new basic transmission period after the next system time synchronization reference takes effect. This mechanism can dynamically optimize the channel access mode of the entire network and automatically adapt to slow changes in network topology.

[0058] In some embodiments, to compensate for clock drift of the local crystal oscillator at the gateway station and maintain long-term time alignment accuracy, periodic time resynchronization is required. For example, starting from the system time synchronization reference T0, after every integer number of successful heartbeat windows, each gateway station actively listens for and waits for the satellite's downlink signal, and re-establishes a unified system time synchronization reference based on this downlink signal. Subsequently, each gateway station uses this re-established system time synchronization reference as a starting point to re-execute the periodic transmission of heartbeat frames. This time resynchronization process ensures that even after long-term operation, the transmission sequences of each gateway station maintain a strict mathematical relationship, preventing the anti-collision mechanism from gradually failing due to clock drift.

[0059] The following reference Figure 3 As shown, an exemplary description is provided of the heartbeat transmission sequence and collision count of gateway station A and gateway station B within the set heartbeat success window, such as... Figure 3 As shown, let the heartbeat success window T winThe system time synchronization reference T0 is 0ms, with a time interval of 500ms. The available set of coprime numbers is {11, 13, 17, 19, 23, 29, 31, 37, 41}. The basic transmission period of gateway station A can be determined to be 13ms, and the basic transmission period of gateway station B can be determined to be 17ms. The heartbeat transmission sequence of gateway station A and gateway station B within the heartbeat success window is as follows:

[0060] Gateway A: 13ms, 26ms, 39ms, ..., 494ms (38 transmissions within a 500ms window);

[0061] Gateway B: 17ms, 34ms, 51ms, ..., 493ms (29 transmissions within a 500ms window).

[0062] Based on the above heartbeat transmission sequence, the heartbeat frames transmitted by gateway station A and gateway station B within the 500ms time window collide only at 221ms and 442ms, with no overlap at other transmission times. This greatly improves the success rate of heartbeat frame transmission, thereby ensuring that gateway station A and gateway station B can reliably maintain their online status.

[0063] In summary, the satellite gateway station access anti-collision method provided in this application establishes a unified system time synchronization benchmark and mutually prime basic transmission periods for each gateway station. Within any heartbeat success window, due to the mutually prime period characteristics, the transmission sequences of each gateway station have a very high probability of being misaligned, ensuring that each gateway station has at least one opportunity to transmit a heartbeat frame without collision. This reliably maintains the online state, achieving a highly reliable, fully distributed, and zero-scheduling-overhead access mechanism, significantly improving the utilization efficiency of satellite single-channel resources and the determinism of maintaining the system's online state.

[0064] like Figure 4 As shown, the satellite IoT system provided in this application includes multiple gateway stations communicating with a satellite. These gateway stations can be used to implement any step of the aforementioned satellite gateway station access anti-collision method and its optional embodiments, as described above. Figure 4 As shown, each gateway station includes a synchronization module 210, a period generation module 220, and a transmission control module 230.

[0065] The synchronization module 210 is used to receive the downlink signal from the satellite and establish a unified system time synchronization reference; the period generation module 220 is used to determine the basic transmission period of each gateway station according to its unique identifier, so that the basic transmission periods of each gateway station are coprime and less than the preset heartbeat success window of the system; the transmission control module 230 is used to continuously send several heartbeat frames to the satellite in each heartbeat success window, starting from the system time synchronization reference and according to the determined basic transmission period, and at least one heartbeat frame successfully reaches the satellite.

[0066] It should be understood that the apparatus or module in the embodiments of this application can be implemented by software, for example, by a computer program or instruction having the above-described functions. The corresponding computer program or instruction can be stored in the internal memory of the terminal, and the above functions can be implemented by the processor reading the corresponding computer program or instruction in the memory. Alternatively, the apparatus or module in the embodiments of this application can also be implemented by hardware. Or, the apparatus or module in the embodiments of this application can also be implemented by a combination of a processor and a software module.

[0067] It should be understood that the processing details of the apparatus or module in the embodiments of this application can be found by referring to... Figures 1-3 The descriptions of the embodiments and related extended embodiments shown will not be repeated in this application.

[0068] Figure 5 This is a structural diagram of a computing device 1000 provided in an embodiment of this application. The computing device 1000 includes: a processor 1010, a memory 1020, a communication interface 1030, and a bus 1040.

[0069] It should be understood that Figure 5 The communication interface 1030 in the computing device 1000 shown can be used to communicate with other devices.

[0070] The processor 1010 can be connected to the memory 1020. The memory 1020 can be used to store the program code and data. Therefore, the memory 1020 can be a storage unit inside the processor 1010, an external storage unit independent of the processor 1010, or a component that includes both the storage unit inside the processor 1010 and the external storage unit independent of the processor 1010.

[0071] Optionally, the computing device 1000 may also include a bus 1040. The memory 1020 and communication interface 1030 can be connected to the processor 1010 via the bus 1040. The bus 1040 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus 1040 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The symbol is represented by only one line, but this does not mean that there is only one bus or one type of bus.

[0072] It should be understood that in the embodiments of this application, the processor 1010 may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. Alternatively, the processor 1010 may employ one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0073] The memory 1020 may include read-only memory and random access memory, and provides instructions and data to the processor 1010. A portion of the processor 1010 may also include non-volatile random access memory. For example, the processor 1010 may also store device type information.

[0074] When the computing device 1000 is running, the processor 1010 executes the computer execution instructions in the memory 1020 to perform the operation steps of the above method.

[0075] It should be understood that the computing device 1000 according to the embodiments of this application can correspond to the corresponding subject in executing the methods according to the various embodiments of this application, and the other operations and / or functions of each module in the computing device 1000 are respectively for implementing the corresponding processes of the methods of this embodiment. For the sake of brevity, they will not be described in detail here.

[0076] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0077] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

[0079] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0080] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0081] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0082] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is used to perform the above-described method, which includes at least one of the schemes described in the above embodiments.

[0083] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0084] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0085] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including, but not limited to, wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0086] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0087] It should be noted that the embodiments described in this application are merely some embodiments, not all embodiments. The components of the embodiments of this application typically described and shown in the accompanying drawings can be arranged and designed in various different configurations. Therefore, the above detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0088] The terms "first, second, third, etc." or similar terms such as module A, module B, module C, etc., used in the specification and claims are only used to distinguish similar objects and do not represent a specific ordering of objects. It is understood that a specific order or sequence may be interchanged where permitted so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0089] In the above description, the labels indicating the steps do not necessarily mean that the steps will be executed. They may include intermediate steps or be replaced by other steps. Where permissible, the order of the steps may be interchanged or executed simultaneously.

[0090] The term "comprising" as used in the specification and claims should not be construed as limiting itself to what follows; it does not exclude other elements or steps. Therefore, it should be interpreted as specifying the presence of the mentioned feature, integral, step, or component, but does not exclude the presence or addition of one or more other features, integrals, steps, or components, or groups thereof. Thus, the statement "device comprising means A and B" should not be limited to a device consisting solely of components A and B.

[0091] The terms "an embodiment" or "an embodiment" as used in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in at least one embodiment of this application. Therefore, the terms "in one embodiment" or "in an embodiment" appearing throughout this specification do not necessarily refer to the same embodiment, but may refer to the same embodiment. Furthermore, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0092] Note that the above are merely preferred embodiments and the technical principles employed in this application. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present application has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, all of which fall within the scope of protection of the present invention.

Claims

1. A method for preventing collisions when accessing a satellite gateway station, characterized in that, include: Multiple gateway stations receive downlink signals from the same satellite, establishing a unified system time synchronization reference; Each gateway station determines its basic transmission period based on its unique identifier, so that the basic transmission periods of each gateway station are coprime to each other and are less than the system's preset heartbeat success window. Starting from the system time synchronization reference, each gateway station continuously sends several heartbeat frames to the satellite within each heartbeat success window according to its basic transmission cycle, and at least one heartbeat frame successfully reaches the satellite.

2. The method according to claim 1, characterized in that, Each gateway station determines its basic transmission period based on its unique identifier, specifically including: Each gateway station selects a base transmission period from a predefined set of coprime numbers based on its unique identifier. This set of coprime numbers is a set of prime numbers.

3. The method according to claim 1, characterized in that, The gateway station sends heartbeat frames deterministically. When heartbeat frames sent by two gateway stations collide, the collision is ignored and the next heartbeat frame is sent.

4. The method according to claim 1, characterized in that, When the preset time node is reached, each gateway station will receive the downlink signal from the satellite again, and re-establish a unified system time synchronization reference based on the downlink signal. Starting from the re-established system time synchronization reference, the periodic transmission of heartbeat frames will be resumed. The preset time node is the moment after an integer number of successful heartbeat windows have passed, starting from the system time synchronization benchmark.

5. The method according to claim 1, characterized in that, Also includes: The number of times each gateway station successfully receives a heartbeat frame from the satellite within multiple consecutive successful heartbeat windows is counted. When the number of successful arrivals of a certain gateway station is lower than a preset threshold, a new basic transmission period that is coprime to the basic transmission periods of other gateway stations is determined for that gateway station.

6. A satellite Internet of Things (IoT) system, characterized in that, This includes interconnected satellites, data centers, and multiple gateway stations, each of which includes: The synchronization module is used to receive downlink signals from the satellite and establish a unified system time synchronization reference. The period generation module is used to determine the basic transmission period of each gateway station based on its unique identifier, so that the basic transmission periods of each gateway station are coprime and less than the system's preset heartbeat success window. The transmission control module is used to continuously send several heartbeat frames to the satellite within each heartbeat success window, starting from the system time synchronization reference and according to a determined basic transmission period, and at least one heartbeat frame successfully reaches the satellite.

7. The system according to claim 6, characterized in that, The data center stores a predefined set of coprime numbers. The period generation module selects one of these coprime numbers as its basic transmission period based on the unique identifier of the gateway station. This set of coprime numbers is a set of prime numbers.

8. A computing device, characterized in that, include: processor; Memory, used to store one or more programs; When the processor executes one or more programs, the processor implements a satellite gateway access anti-collision method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a computer, implements a satellite gateway station access anti-collision method as described in any one of claims 1 to 6.

Images