A method for congestion warning and access control of a satellite cluster public signaling channel

Abstract

This invention discloses a method for congestion warning and access control of a satellite trunking common signaling channel. A State Service (STS) server uses statistical information on random satellite access and radio resource management (RRM) allocation from the terminal as a traffic status report, which is broadcast to users in real time via the common signaling channel. The satellite trunking terminal adjusts its access based on the user priority assigned at activation and the current system broadcast, forming a congestion warning and flow control mechanism. Based on the random access RACH information, users can obtain the uplink access traffic on the common channel of their respective beam within a unit of time. Based on the satellite resource management (RRM) information, users can obtain the probability of successfully requesting access beam resources within a unit of time. According to a predetermined access control strategy, the terminal initiates uplink traffic tiered restrictions before beam congestion, ensuring that users with different priorities receive corresponding communication connection rates. This provides users with better tiered satellite trunking access services and effectively prevents systemic traffic paralysis due to channel resource exhaustion.

Description

Technical Field

[0001] This invention belongs to the field of satellite communication, specifically relating to a method for congestion warning and access control of a satellite cluster public signaling channel. Background Technology

[0002] A satellite mobile communication system refers to a system that uses the relay or switching functions of geostationary orbit communication satellites to connect mobile terminals (stations) within its coverage area to the core network of a ground gateway station (system) for service exchange to achieve mobile communication. When the services supported by the satellite mobile communication system are point-to-point voice and SMS services, we call them conventional services; when the services supported by the satellite mobile communication system are point-to-multipoint voice and SMS services, we call them trunking services.

[0003] Satellite trunking communication is a one-to-many communication system among a group of satellite users, effectively improving communication efficiency. In emergencies, satellite trunking communication can provide rapid call connections between satellite users for command and control. Satellite mobile communication has advantages such as wide coverage, minimal impact from the ground environment, and suitability for field communication, leading to its increasingly widespread use.

[0004] In addition to the advantages of rapid communication with one call and efficient resource utilization through channel sharing, satellite trunking communication also supports user priority calls to ensure the special communication needs of important customers. When channel resources are scarce, higher-level users will have priority to obtain radio resources than lower-level users, so as to ensure uninterrupted command and communication in emergency situations.

[0005] In satellite mobile communication systems, trunking communication and satellite phone services share the same common control channel frequency, but are distinguished by different time slots with orthogonal timing. Users waiting to listen for signaling broadcasts on the downlink channel can hear satellite phone paging or satellite trunking calls in different time slots without leaving their current frequency. Mobile stations can easily achieve dual-mode standby and single-mode transmission.

[0006] In the uplink direction of the common control channel, the terminal uses random access RACH for competitive satellite access. After receiving the RACH, the satellite ground station transceiver station (GTS) delivers the RACH to the GSC (Gateway Station Controller) that handles telephone services or the GSC that handles trunking services, according to the service type identifier.

[0007] The satellite trunking access network has a separate GSC. In the downlink direction of the common control channel, the satellite trunking GSC independently broadcasts trunking signaling. In the uplink direction of the common control channel, the satellite trunking GSC receives the RACH of the trunking call from the GTS.

[0008] A satellite constellation (GSC) consists of entities such as the Satellite Channel Control (SCC), the Satellite Channel Processor (SCP), and the Radio Resource Management (RRM).

[0009] After a satellite terminal accesses the gateway station, the trunking gateway station controller can only receive the trunking RACH. The trunking RACH reflects the trunking terminal access information and does not reflect the total access traffic of satellite calls for the current beam. Similarly, the number of service channels occupied by the trunking is not the total number of channels occupied for the current beam. If a satellite phone occupies all service channel resources, even if no satellite trunking channel is occupied, the trunking resource request will be rejected.

[0010] For trunked radio communication, the number of trunked RACHs we can statistically track can never exceed the overall receiving capacity of the current beam. The RACH acceptance capacity of a satellite beam's common channel can be calculated. The RACH uses slotted ALOHA access, with a maximum channel utilization of 36.8%. When the satellite time slot channel frame length is 60ms, the maximum theoretical number of successful RACHs is 6.13 times per second. If we allocate traffic proportionally to telephone and trunked radio traffic, the theoretical number of trunked RACHs will not exceed 3.06 times per second.

[0011] Since the number of service channels occupied by the cluster is not the total number of channels occupied by the current beam, we cannot use the number of service channels occupied by the cluster to measure whether or about to enter a congested state. The absolute value of cluster service resource occupancy provided by RRM is not a reasonable basis for congestion control. We can only infer whether or about to enter a congested state based on the success rate of current RRM resource requests. When the probability of cluster request failure changes significantly when a user terminal accesses and requests resources, an access restriction process based on user priority should be initiated.

[0012] Existing satellite mobile communication systems are often designed with reference to terrestrial 3G mobile network wireless access specifications, lacking specific satellite channel early warning and access control mechanisms. Satellite phones use public mobile network AS (Access Stratum) access signaling and NAS (Non-Access Stratum) non-access signaling for calls to facilitate integration with terrestrial networks. However, this leads to a problem: because satellite resources are far scarcer than terrestrial network resources, a large number of user accesses can cause a rapid decline in call success rate. For example, during the flood relief efforts in Zhuozhou, Hebei Province, in July and August 2023, the high volume of calls to Tiantong satellite phones resulted in a reduced call connection rate. The more calls users couldn't get through, the more they had to initiate calls, leading to a surge in access requests and strong negative user feedback. Therefore, setting user priorities is a necessary means to ensure smooth communication for important customers, and setting a user access strategy based on priority control is a key step in avoiding channel congestion or even deadlock. Summary of the Invention

[0013] To address the aforementioned problems, the present invention aims to provide a method for early warning and access control of congestion in the common signaling channel of a satellite constellation.

[0014] The specific technical solution for achieving the objective of this invention is as follows:

[0015] A method for congestion warning and access control of a satellite cluster public signaling channel utilizes a status server (STS) deployed in the ground station core network to receive working information submitted by the satellite channel controller (SCC) entity and the satellite radio resource management (RRM) entity of the gateway station access network.

[0016] The gateway station access network satellite channel controller entity SCC executes the original communication task process, and submits all the uplink random access RACH information from the trunk common control channel that it is processing to the state server STS with the beam number attached.

[0017] When allocating resources, the Satellite Radio Resource Management Entity (RRM) will attach a beam number to the information of successfully allocated resources, or attach a beam number to the information of unallocated resources, and submit it to the Status Server (STS).

[0018] The State Server (STS) also receives instructions from the core network OAM operation and maintenance console, generates beam passage indications, counts the beam number information received from the gateway access network satellite channel controller entity (SCC) and satellite radio resource management entity (RRM), and uses the count value and passage indication value together as a congestion warning message for the satellite cluster public signaling channel, which is then broadcast to all waiting cluster terminals through the beam downlink broadcast channel.

[0019] The cluster terminal determines whether to restrict local RACH access based on the access indication, beam count value, and user priority of the terminal itself, according to the current access status, the fallback time value when local RACH fails based on the current traffic status, and whether to activate local traffic control policy based on the current probability of successful resource requests from the satellite radio resource management entity (RRM).

[0020] Furthermore, the State Server STS includes a State Master Processing Module (ST MPU), a State Storage Module (Storage Queue), Beam Counters, and a Notify Module.

[0021] The status main processing module ST MPU is used to collect statistics on the RACH and RRM information of the terminal access, and provides an interactive interface with the gateway station access network entity SCC, RRM and core network entity cluster operation and maintenance console OAM.

[0022] The state storage module is used to store RACH and related information in the state queue according to the write requirements of the state main processing module ST MPU.

[0023] The beam counters use counters to record the access traffic and resource allocation quantity of the public signaling channel per unit time.

[0024] The broadcast module Notify is used to broadcast traffic warning information to a designated beam through the gateway station access network satellite channel controller entity SCC, according to the request of the status master processing module ST MPU.

[0025] Furthermore, the State Server STS uses four counters to count beams: RACH Access Counter, RRM DistributeCounter, RRM Allocate Counter, and Time Counter.

[0026] During counting, the RACH Access Counter increments by 1 for each RACH access message received; the RRM Distribute Counter increments by 1 for each RRM allocation message received, regardless of whether the allocation is successful or not; the RRM Allocate Counter increments by 1 for each successful RRM allocation message received; and the Time Counter increments by 1 every second.

[0027] Whenever the Time Counter expires, the Status Main Processing Module (ST MPU) publishes the count values ​​of the four counters to all waiting cluster terminals through the downlink broadcast channel of this beam. After the publication is completed, the four counters are cleared to zero and the counting continues, waiting for the next publication.

[0028] Furthermore, the satellite cluster public signaling channel congestion warning message includes beam passage indication and counter count value;

[0029] The beam pass indicator is used to display the traffic light status. The cluster terminal determines whether to access the satellite based on the traffic light status and its own terminal priority.

[0030] The counter value is used to display the access traffic and resource allocation quantity of the previous cycle. The cluster terminal determines whether to access the satellite based on the access traffic, resource allocation quantity, and its own terminal priority.

[0031] Furthermore, the priorities of the cluster terminals are 0, 1, 2, and 3 from high to low. The priority is set by the cluster gateway station and is automatically obtained after the terminal joins the network. The beam pass indicator sets a traffic light for the cluster terminals. The traffic light uses 4-bit encoding, with each bit corresponding to one user priority. BIT=1 is green and BIT=0 is red. When the green light is on, the cluster terminal user with that priority can access the network, and when the red light is on, the cluster terminal user cannot access the network.

[0032] Furthermore, after the cluster terminal receives the congestion warning signal for the satellite cluster's common signaling channel:

[0033] (1) Based on the priority user access traffic light indication, determine whether the local machine can perform random access. If it is red, the cluster terminal indicates that satellite access is temporarily prohibited. If it is green, the cluster terminal will determine the access strategy based on the counter count value.

[0034] (2) Based on the RACH Access Counter and Time Counter, calculate the current RACH traffic status of this beam, and decide whether access is possible based on its own priority. If access is possible, determine the backoff time for RACH to request again.

[0035] (3) Calculate the current resource request success rate of this beam according to the RRM Distribute Counter and RRM AllocateCounter. Based on its own priority, determine whether the resource request type RACH can be accessed. If it can be accessed, determine the backoff time for the RACH to request again.

[0036] Furthermore, the Status Server (STS) distributes the satellite cluster common signaling channel congestion warning message to the Cluster Operation and Maintenance Console (OAM).

[0037] The cluster operation and maintenance console (OAM) constructs a real-time traffic display map based on the traffic status of each satellite beam, showing the traffic status of each beam cluster service.

[0038] When the traffic of a certain beam is abnormal, the cluster operation and maintenance console (OAM) can intervene in the flow control and notify the status server (STS) to temporarily light up the red light for a certain priority user of that beam and observe the traffic effect.

[0039] Once the traffic returns to normal, the cluster operation and maintenance console (OAM) promptly activates the green light for users with that priority in the beam. Users then decide their access strategy based on the beam counter value and their own priority.

[0040] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0041] The present invention utilizes a counter set in the State Server (STS) to count information from the Gateway Access Network Satellite Channel Controller (SCC) and Satellite Radio Resource Management (RRM) entities, sets priorities for cluster terminals, and sends congestion warning messages for the satellite cluster common signaling channel. This allows cluster terminals to determine whether to access the network and their access strategies based on their own priorities and message content.

[0042] Meanwhile, OAM can also construct a real-time traffic display map based on the traffic status of each satellite beam to show the traffic status of each beam cluster service, so as to determine whether to intervene in traffic control; this solution can realize congestion warning and access control for satellite cluster service resource occupancy.

[0043] Furthermore, due to engineering configuration reasons, satellite resource management is often performed by the operations control system, while the station control system is only responsible for the management of equipment within the station. Ground station operation and maintenance personnel cannot intuitively understand the current trunking communication services and resource allocation status of each beam, making it difficult to locate the fault point when communication problems occur. The ground station core network OAM operation and maintenance console set up in this solution can not only clearly understand the current satellite trunking working status, but also intervene in trunking communication management in real time.

[0044] Through the congestion warning and access control mechanism, cluster terminal users can intuitively understand the current access traffic status of satellite cluster communication on the cluster APP. Users have changed from disorderly competition to orderly passage. The traffic flow of the satellite cluster has been well controlled, avoiding systemic congestion and traffic paralysis.

[0045] The present invention will be further described below with reference to specific embodiments. Attached Figure Description

[0046] Figure 1 This is a diagram illustrating the architecture of the satellite cluster common signaling channel congestion early warning and access control system of the present invention.

[0047] Figure 2 This is a schematic diagram illustrating the association between the State Server (STS) and the core network service entity of the present invention.

[0048] Figure 3 This is a schematic diagram of information sorting in the ST MPU (Status Server Service) main processing module of the present invention.

[0049] Figure 4 This is a schematic diagram of the beam counter broadcast warning of the State Server (STS) of the present invention.

[0050] Figure 5 This is a schematic diagram of the RACH and RRM information processing flow of the present invention.

[0051] Figure 6 This is a schematic diagram of the highest and second-highest priority terminal congestion warning and access control strategies of the present invention.

[0052] Figure 7 This is a schematic diagram of the ordinary and lowest priority terminal congestion warning and access control strategies of the present invention. Detailed Implementation

[0053] Example

[0054] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. The described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0055] As indicated in this application and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of explicitly identified steps and elements, which do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

[0056] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of this application. It should also be understood that, for ease of description, the dimensions of the various parts shown in the drawings are not drawn to actual scale. Techniques, methods, and devices known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and devices should be considered part of the specification. In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters in the following drawings denote similar items; therefore, once an item is defined in one drawing, it need not be further discussed in subsequent drawings.

[0057] The common signaling channel for satellite clusters is a cluster control channel with a pair of frequency points and designated time slots for each beam. All idle cluster terminals under this beam listen to the downlink broadcast of the common signaling channel. The downlink broadcast includes information such as cluster group calls, individual calls, group SMS, individual SMS, late-arriving calls, group messages, status messages, and broadcast notifications.

[0058] The common signaling channel for satellite trunking is a trunking control channel with a pair of frequency points and designated time slots for each beam. All trunking terminals that are idle under this beam must request services from the gateway station using uplink random access (RACH) signaling when initiating terminal network access, trunking calls, sending SMS messages, or sending status messages. Users who receive services from the gateway station obtain service channel resources or receive status message responses through downlink broadcasts on the common signaling channel.

[0059] The common signaling channel of satellite clusters and the cluster service channel obtained by users are different. The common signaling channel of satellite clusters is a shared uplink and downlink channel, and users obtain services through contention. The cluster service channel obtained by users through contention is a dedicated channel. Once a dedicated service channel is obtained, it is exclusively used by the user or user group, and no flow control or congestion avoidance is required. They obtain dedicated service channel resources with constant bandwidth.

[0060] The information used for the satellite cluster public signaling channel congestion warning is terminal access information, which comes from the terminal uplink random access (RACH) request in the ground station's satellite feeder circuit and the channel resource allocation (RRM) caused by the RACH. This information comes from the communication process information generated by the terminal or access network associated entities at each stage of satellite communication. As outdated information that would normally be discarded in the communication process, we are now reusing this original information as raw material to generate a new public signaling channel congestion warning for users.

[0061] The satellite cluster public signaling channel congestion early warning and access control method of this scheme is a closed-loop feedback control method that uses the gateway station access network to statistically analyze the current uplink traffic status of the current beam in real time, broadcast it through the downlink channel, and adjust the uplink access traffic according to the early warning strategy.

[0062] Specifically, combined Figure 1 A method for congestion warning and access control of a satellite cluster public signaling channel utilizes a State Server (STS) deployed in the ground station core network to receive information from the Satellite Channel Controller (SCC) and Radio Resource Management (RRM) entities in the gateway station access network.

[0063] The Status Server (STS) is an application server deployed on the core network. It obtains raw terminal access information data from the ground station access network entity, and then calculates the current uplink traffic and resource allocation status from the raw data. The STS communicates with other service function entities through the internal IP network of the gateway station to realize terminal status services.

[0064] The original communication task execution process of the gateway station access network satellite channel controller entity SCC remains unchanged, but a processing breakpoint is added: all uplink random access RACH information from the trunk common control channel that it is currently processing is submitted to STS with the beam number attached. After the SCC completes the breakpoint service, it continues to execute the original command control process.

[0065] When the satellite radio resource management entity (RRM) allocates resources, it also adds a processing breakpoint: attaching the beam number to the successfully allocated resource information, or attaching the beam number to the unallocated resource information and submitting it to the STS. After the RRM completes the breakpoint service, it continues to execute the original resource allocation process.

[0066] The State Server (STS) also receives instructions from the core network OAM operation and maintenance console, generates beam passage indications, counts the beam number information received from the gateway access network satellite channel controller entity (SCC) and satellite radio resource management entity (RRM), and uses the count value and passage indication value together as a congestion warning message for the satellite cluster public signaling channel, which is then broadcast to all waiting cluster terminals through the beam downlink broadcast channel.

[0067] The cluster terminal determines whether to restrict local RACH access based on the access indication, beam count value, and user priority of the terminal itself, according to the current access status, the fallback time value when local RACH fails based on the current traffic status, and whether to activate local traffic control policy based on the current probability of successful resource requests from the satellite radio resource management entity (RRM).

[0068] Combination Figure 1 and Figure 2 The State Server (STS) and other related service entities work together to extract, store, analyze, and distribute alerts for RACH and RRM information; the relevant cooperating service entities are:

[0069] 1) The Satellite Channel Control (SCC) is an access network entity that provides RACH Information;

[0070] 2) Satellite Radio Resource Management (RRM) is an access network entity that provides RRM Information;

[0071] 3) The cluster operation and maintenance console (OAM) is a core network entity responsible for monitoring or intervening in the flow control of the public signaling channel.

[0072] The interface between the State Server (STS) and other functional entities in the core network uniformly adopts the IP network interface protocol.

[0073] The State Server (STS) includes a State Main Processing Module (ST MPU), a State Storage Module (Storage Queue), Beam Counters, and a Notify Module.

[0074] The status main processing module ST MPU is used to collect statistics on the RACH and RRM information of the terminal access, and provides an interactive interface with the gateway station access network entity SCC, RRM and core network entity cluster operation and maintenance console OAM.

[0075] The state storage module is used to store RACH and related information in the state queue according to the write requirements of the state main processing module ST MPU.

[0076] The beam counters use counters to record the access traffic and resource allocation quantity of the public signaling channel per unit time.

[0077] The broadcast module Notify is used to broadcast traffic warning information to a designated beam through the gateway station access network satellite channel controller entity SCC, according to the request of the status master processing module ST MPU.

[0078] Combination Figure 3 This is a schematic diagram of information sorting in the ST MPU (Stationary Management Processing Unit) of the State Server (STS). The STS RACH state data storage uses the terminal user number (MSISDN), cluster identifier (TEID), and cluster group number as indexes to form a time-based storage queue. RACH and RRM access information uses the beam number as an index to form a statistical structure based on a four-type classification counter. The interface between the STS and external entities is as follows:

[0079] 1) SCC Interface: The interface through which the terminal MES sends terminal access information and beam warning broadcast information issued by STS to the STS server via the random access RACH process.

[0080] 2) RRM Interface: The interface for beam resource occupancy information sent to the STS server by the RRM resource allocation caused by the RACH processing procedure of the access network SCC.

[0081] 3) OAM Interface: The interface for exchanging information between the STS status server and the OAM operation and maintenance console.

[0082] The State Server (STS) uses four counters to count beams: RACH Access Counter, RRM Distribute Counter, RRM Allocate Counter, and Time Counter.

[0083] During counting, the RACH Access Counter increments by 1 for each RACH access message received; the RRM Distribute Counter increments by 1 for each RRM allocation message received, regardless of whether the allocation is successful or not; the RRM Allocate Counter increments by 1 for each successful RRM allocation message received; and the Time Counter increments by 1 every second.

[0084] Whenever the Time Counter expires, the Status Main Processing Module (ST MPU) publishes the count values ​​of the four counters to all waiting cluster terminals through the downlink broadcast channel of this beam. After the publication is completed, the four counters are cleared to zero and the counting continues, waiting for the next publication.

[0085] Combination Figure 4 The satellite cluster public signaling channel congestion warning message includes a passage indication and a counter count value, B7-B4 are broadcast beam information type codes, and B3-B0 are hierarchical traffic lights;

[0086] The beam pass indicator is used to display the traffic light status. The cluster terminal determines whether to access the satellite based on the traffic light status and its own terminal priority.

[0087] The counter value is used to display the access traffic and resource allocation quantity of the previous cycle. The cluster terminal determines whether to access the satellite based on the access traffic, resource allocation quantity, and its own terminal priority.

[0088] The priorities of the cluster terminals are 0, 1, 2, and 3 from high to low. The priority is set by the cluster gateway station and is automatically obtained after the terminal joins the network. The beam pass indicator sets a traffic light for the cluster terminals. The traffic light uses 4-bit encoding, with each bit corresponding to one user priority. BIT=1 is green and BIT=0 is red. When the green light is on, the cluster terminal user with that priority can access the network. When the red light is on, the cluster terminal user cannot access the network.

[0089] 1) The highest user priority of the terminal is 0, which is set by the trunking gateway station. The terminal will automatically obtain the priority after joining the network. A traffic light is set. When the green light is on, the user can access the network. When the red light is on, the user cannot access the network. BIT=1 is green light and BIT=0 is red light.

[0090] 2) The second highest user priority of the terminal is 1, which is set by the trunking gateway station. The terminal will automatically obtain the priority after joining the network. A traffic light is set. When the green light is on, the user can access the network. When the red light is on, the user cannot access the network. BIT=1 is green light and BIT=0 is red light.

[0091] 3) The terminal's general user priority is 2, which is set by the trunking gateway station. The terminal will automatically obtain the priority after joining the network. A traffic light is set. When the green light is on, the user can access the network. When the red light is on, the user cannot access the network. BIT=1 is the green light and BIT=0 is the red light.

[0092] 4) The minimum user priority for the terminal is 3, which is set by the trunking gateway station and is automatically obtained after the terminal joins the network. A traffic light is set. When the green light is on, the user can access the network. When the red light is on, the user cannot access the network. BIT=1 is the green light and BIT=0 is the red light.

[0093] The traffic lights in this embodiment:

[0094] 1) B3=0 is a red light, B3=1 is a green light. Terminal priority 3 users can access the satellite according to the green light.

[0095] 2) B2=0 is a red light, B2=1 is a green light. Terminals with priority level 2 can access the satellite based on the green light.

[0096] 3) B1=0 is a red light, B1=1 is a green light. Terminals with priority 1 can access the satellite based on the green light.

[0097] 4) B0=0 is a red light, B0=1 is a green light, and terminal priority 0 users can access the satellite according to the green light;

[0098] Counter count value:

[0099] Four counters per beam:

[0100] 1) RACH Access Counter, 1-byte encoding, indicates the number of RACH accesses in the previous cycle;

[0101] 2) RRM Distribute Counter, 1-byte encoding, indicates the total number of RRM allocations in the previous cycle;

[0102] 3) RRM Allocate Counter, 1-byte encoding, indicates the number of successful RRM allocations in the previous cycle;

[0103] 4) Time Counter, 1-byte encoding, indicates the length of the previous cycle.

[0104] This embodiment combines Figure 5 The diagram illustrates the RACH and RRM information processing flow, showing how STS collects, sorts, analyzes, publishes, and interacts with OAM regarding RACH and RRM allocation information for terminal access:

[0105] Processing steps 1-2: The terminal MESs uses RACH random access to initiate a request to the gateway transceiver GTS, and the GTS transfers the RACH to the SCC.

[0106] Processing step 3: SCC marks the received RACH with a beam number, makes a copy, and submits it to the STS main control processor STMPU.

[0107] Processing flow 4: SCC parses the RACH and finds it to be a resource request type random access request, requesting resources to the RRM in a per-direction manner: RRM Request;

[0108] Processing step 5: RRM performs resource allocation and submits a copy of the resource allocation result to the STS main control processor ST MPU: RRM Distribute;

[0109] Processing flow 6: RRM allocates resources and submits the allocation results as a response to SCC: RRMDistribute;

[0110] In the processing flow 7-8, the SCC sends the RRC immediate allocation instruction AGCH RRM back to the initiating terminal via the local beam trunking common signaling control channel and GTS; at this time, the initiating user MES receives the resource allocation instruction and switches to the trunking service channel.

[0111] Processing step 9: The STS main control processor instructs the beam counter to increment RACH by 1;

[0112] Processing flow 10: The STS main control processor instructs the beam counter to increment the RRM by 1.

[0113] Processing flow 9 and collection flow 10 will be repeated. The count values ​​of the four counters will be continuously monitored by the STS main processor until the timer expires. When the time counter expires, an early warning statistical release will be generated.

[0114] Processing flow 11: When the Time Counter timer expires, the STS is reminded to issue a warning message: Time Out;

[0115] Processing flow 12: The STS main control processor requests the counter to submit the count value: Get Counters;

[0116] Processing flow 13: The beam counter submits its count value to the STS main control processor: Counters Response; After the beam counter completes the submission, all four counters are cleared to zero, waiting for the next count;

[0117] Processing steps 14-16: The STS main control processor broadcasts a warning to all MESs users of the beam via SCC and GTS: Notify Beam Counters;

[0118] Processing flow 17: The STS main control processor copies and broadcasts the warning to OAM: Notify Beam Counters;

[0119] Processing flow 18: If necessary, OAM requests STS to intervene in traffic control and control the lighting of the traffic lights: red or green.

[0120] Processing flow 19, STS responds to OAM: Traffic Control OK, OAM's traffic light control information will be released by STS at the next warning issuance.

[0121] After the cluster terminal receives the satellite cluster public signaling channel congestion warning message:

[0122] (1) Based on the priority user access traffic light indication, determine whether the local machine can perform random access. If it is red, the cluster terminal indicates that satellite access is temporarily prohibited. If it is green, the cluster terminal will determine the access strategy based on the counter count value.

[0123] (2) Based on the RACH Access Counter and Time Counter, calculate the current RACH traffic status of this beam, and decide whether access is possible based on its own priority. If access is possible, determine the backoff time for RACH to request again.

[0124] (3) Calculate the current resource request success rate of this beam according to the instructions of the RRM Distribute Counter and RRM AllocateCounter. Based on its own priority, determine whether the resource request RACH can be accessed. If it can be accessed, determine the backoff time for the RACH to be requested again.

[0125] Combination Figure 6 and Figure 7 A diagram illustrating the highest, second-highest, normal, and lowest priority terminal congestion warning and access control strategies, explaining the priority user traffic warning and access control methods:

[0126] (1) Traffic flow warning

[0127] Each terminal app can display the current cluster traffic status:

[0128] 1) Red, severe congestion, access prohibited;

[0129] 2) Orange: Congested, conditional access possible;

[0130] 3) Yellow: Slight congestion, conditional access possible;

[0131] 4) Green, smooth, and accessible at any time.

[0132] (2) Hierarchical congestion control

[0133] After receiving the warning broadcast from STS, the user terminal parses it according to its own priority:

[0134] Traffic lights for this level: R (red) or G (green);

[0135] RACH count per second:

[0136] A=RACH Access Counter / Time Counter;

[0137] RRM success probability calculation:

[0138] P=RRM Allocate Counter / RRM Distribute Counter;

[0139] After parsing and calculation are completed, each terminal executes the following access control policy:

[0140] 1) If the traffic light for this level is R:

[0141] The app marks traffic flow status as "red";

[0142] Local state-based RACH (no resource request required) access is prohibited;

[0143] Access to RACH systems that require local resources (requiring resource application) is prohibited.

[0144] 2) If the traffic light for this level is G:

[0145] For priority 0 users: A > 4 times / second;

[0146] For priority 1 users: A > 3 times / second;

[0147] For priority 2 users: A > 2 times / second;

[0148] For priority 3 users: A > 1 time / second;

[0149] The app marks traffic flow status as "red";

[0150] Local state-based RACH (no resource request required) access is prohibited;

[0151] Access to RACH systems that require local resources (requiring resource application) is prohibited.

[0152] 3) If the traffic light for this level is G:

[0153] For priority 0 users: 3 times / second < A ≤ 4 times / second, and P ≤ 50%.

[0154] For priority 1 users: 2 times / second < A ≤ 3 times / second, and P ≤ 60%;

[0155] For priority 2 users: 1 time / second < A ≤ 2 times / second, and P ≤ 70%;

[0156] For priority 3 users: 1 time / 2 seconds < A ≤ 1 time / second, and P ≤ 80%;

[0157] The app marks traffic flow status as "orange";

[0158] Local stateful RACH (no resource request required) is allowed.

[0159] If RACH fails to connect, you can go back about 3 seconds and try connecting again.

[0160] Access to RACH systems that require local resources (requiring resource application) is prohibited.

[0161] 4) If the traffic light for this level is G:

[0162] For priority 0 users: 3 times / second < A ≤ 4 times / second, and P > 50%.

[0163] For priority 1 users: 2 times / second < A ≤ 3 times / second, and P > 60%;

[0164] For priority 2 users: 1 time / second < A ≤ 2 times / second, and P > 70%;

[0165] For priority 3 users: 1 time / 2 seconds < A ≤ 1 time / second, and P > 80%;

[0166] The app marks traffic flow status as "orange";

[0167] Local stateful RACH (no resource request required) is allowed.

[0168] Local resource-based RACH (requires resource application) is allowed access;

[0169] If RACH fails to connect, you can go back about 3 seconds and try connecting again.

[0170] 5) If the traffic light for this level is G:

[0171] For priority 0 users: 2 times / second < A ≤ 3 times / second, and P ≤ 50%.

[0172] For priority 1 users: 1 time / second < A ≤ 2 times / second, and P ≤ 60%;

[0173] For priority 2 users: 1 time / 2 seconds < A ≤ 1 time / second, and P ≤ 70%;

[0174] For priority 3 users: 1 time / 3 seconds < A ≤ 1 time / 2 seconds, and P ≤ 80%;

[0175] The app marks traffic flow status as "yellow";

[0176] Local stateful RACH (no resource request required) is allowed.

[0177] If RACH fails to connect, you can go back about 2 seconds and try connecting again.

[0178] Access to RACH systems that require local resources (requiring resource application) is prohibited.

[0179] 6) If the traffic light for this level is G:

[0180] For priority 0 users: 2 times / second < A ≤ 3 times / second, and P > 50%.

[0181] For priority 1 users: 1 time / second < A ≤ 2 times / second, and P > 60%;

[0182] For priority 2 users: 1 time / 2 seconds < A ≤ 1 time / second, and P > 70%;

[0183] For priority 3 users: 1 time / 3 seconds < A ≤ 1 time / 2 seconds, and P > 80%;

[0184] The app marks traffic flow status as "yellow";

[0185] Local stateful RACH (no resource request required) is allowed.

[0186] Local resource-based RACH (requires resource application) is allowed access;

[0187] If RACH fails to connect, you can go back about 2 seconds and try connecting again.

[0188] 7) If the traffic light for this level is G:

[0189] For users with priority 0: A ≤ 2 times / second;

[0190] For priority 1 users: A ≤ 1 time / second;

[0191] For priority 2 users: A ≤ 1 time / 2 seconds;

[0192] For priority 3 users: A ≤ 1 time / 3 seconds;

[0193] The app marks traffic flow status as "green";

[0194] Local stateful RACH (no resource request required) is allowed.

[0195] Local resource-based RACH (requires resource application) is allowed access;

[0196] If RACH fails to connect, you can go back about 1 second and try connecting again.

[0197] In addition, the Status Server (STS) distributes the satellite cluster common signaling channel congestion warning message to the Cluster Operation and Maintenance Console (OAM).

[0198] The cluster operation and maintenance console (OAM) constructs a real-time traffic display map based on the traffic status of each satellite beam, showing the traffic status of each beam cluster service.

[0199] When the traffic of a certain beam is abnormal, the cluster operation and maintenance console (OAM) can intervene in the flow control and notify the status server (STS) to temporarily light up the red light for the priority users of that beam and observe the traffic effect.

[0200] Once the traffic returns to normal, the cluster operation and maintenance console (OAM) promptly activates the green light for beam priority access users. Users then decide their access strategy based on the beam counter value and their own priority.

[0201] The embodiments described above are merely one implementation method of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for congestion warning and access control of a common signaling channel for satellite constellations, characterized in that, The status server STS deployed in the ground station core network receives working information from the satellite channel controller entity SCC and the satellite radio resource management entity RRM of the gateway station access network. The gateway station access network satellite channel controller entity SCC executes the original communication task process, and submits all the uplink random access RACH information from the trunk common control channel that it is processing to the state server STS with the beam number attached. When allocating resources, the Satellite Radio Resource Management Entity (RRM) will attach a beam number to the information of successfully allocated resources, or attach a beam number to the information of unallocated resources, and submit it to the Status Server (STS). The State Server (STS) also receives instructions from the core network OAM operation and maintenance console, generates beam passage indications, counts the beam number information received from the gateway access network satellite channel controller entity (SCC) and satellite radio resource management entity (RRM), and uses the count value and passage indication value together as a congestion warning message for the satellite cluster public signaling channel, which is then broadcast to all waiting cluster terminals through the beam downlink broadcast channel. The cluster terminal determines whether to restrict local RACH access based on the access indication, beam count value, and user priority of the terminal itself, according to the current access status, the fallback time value when local RACH fails based on the current traffic status, and whether to activate local traffic control policy based on the current probability of successful resource requests from the satellite radio resource management entity (RRM).

2. The satellite cluster common signaling channel congestion early warning and access control method according to claim 1, characterized in that, The State Server (STS) includes a State Main Processing Module (ST MPU), a State Storage Module (Storage Queue), Beam Counters, and a Notify Module. The status main processing module ST MPU is used to collect statistics on the RACH and RRM information of the terminal access, and provides an interactive interface with the gateway station access network entity SCC, RRM and core network entity cluster operation and maintenance console OAM. The state storage module is used to store RACH and related information in the state queue according to the write requirements of the state main processing module ST MPU. The beam counters use counters to record the access traffic and resource allocation quantity of the public signaling channel per unit time. The broadcast module Notify is used to broadcast traffic warning information to a designated beam through the gateway station access network satellite channel controller entity SCC, according to the request of the status master processing module ST MPU.

3. The satellite cluster common signaling channel congestion early warning and access control method according to claim 2, characterized in that, The State Server (STS) uses four counters to count beams: RACH Access Counter, RRM Distribute Counter, RRM Allocate Counter, and Time Counter. During counting, the RACH Access Counter increments by 1 for each RACH access message received; the RRM Distribute Counter increments by 1 for each RRM allocation message received, regardless of whether the allocation is successful or not; the RRM Allocate Counter increments by 1 for each successful RRM allocation message received; and the Time Counter increments by 1 every second. Whenever the Time Counter expires, the Status Main Processing Module (ST MPU) publishes the count values ​​of the four counters to all waiting cluster terminals through the downlink broadcast channel of this beam. After the publication is completed, the four counters are cleared to zero and the counting continues, waiting for the next publication.

4. The satellite cluster common signaling channel congestion early warning and access control method according to claim 2, characterized in that, The satellite cluster public signaling channel congestion warning message includes beam passage indication and counter count value; The beam pass indicator is used to display the traffic light status. The cluster terminal determines whether to access the satellite based on the traffic light status and its own terminal priority. The counter value is used to display the access traffic and resource allocation quantity of the previous cycle. The cluster terminal determines whether to access the satellite based on the access traffic, resource allocation quantity, and its own terminal priority.

5. The satellite cluster common signaling channel congestion early warning and access control method according to claim 4, characterized in that, The priorities of the cluster terminals are 0, 1, 2, and 3 from high to low. The priority is set by the cluster gateway station and is automatically obtained after the terminal joins the network. The beam pass indicator sets a traffic light for the cluster terminals. The traffic light uses 4-bit encoding, with each bit corresponding to one user priority. BIT=1 is green and BIT=0 is red. When the green light is on, the cluster terminal user with that priority can access the network. When the red light is on, the cluster terminal user cannot access the network.

6. The satellite cluster common signaling channel congestion early warning and access control method according to claim 4, characterized in that, After the cluster terminal receives the congestion warning signal of the satellite cluster common signaling channel: (1) Based on the priority user traffic light indication, determine whether the local machine can perform random access. If it is red, the cluster terminal indicates that satellite access is temporarily prohibited. If it is a green light, the cluster terminal will determine the access strategy based on the counter value; (2) Based on the RACH Access Counter and Time Counter, calculate the current RACH traffic status of this beam, and decide whether access is possible based on its own priority. If access is possible, determine the backoff time for RACH to request again. (3) Calculate the current resource request success rate of this beam according to the RRM Distribute Counter and RRM AllocateCounter. Based on its own priority, determine whether the resource request type RACH can be accessed. If it can be accessed, determine the backoff time for the RACH to request again.

7. The satellite cluster common signaling channel congestion early warning and access control method according to claim 4, characterized in that, The Status Server (STS) distributes the satellite cluster common signaling channel congestion warning message to the cluster operation and maintenance console (OAM). The cluster operation and maintenance console (OAM) constructs a real-time traffic display map based on the traffic status of each satellite beam, showing the traffic status of each beam cluster service. When the traffic of a certain beam is abnormal, the cluster operation and maintenance console (OAM) can intervene in the flow control and notify the status server (STS) to temporarily light up the red light for a certain priority user of that beam and observe the traffic effect. Once the traffic returns to normal, the cluster operation and maintenance console (OAM) promptly activates the green light for users with that priority in the beam. Users then decide their access strategy based on the beam counter value and their own priority.

Images