Satellite network congestion processing method, communication device, chip system, storage medium and program product

Abstract

The invention provides a satellite network congestion processing method, communication equipment, a chip system, a storage medium and a program product, and relates to the technical field of satellite communication. The satellite network congestion processing method provided by the invention comprises the following steps: under the condition that a first feed link connected with a first spaceborne routing node is congested, the first spaceborne routing node sends a congestion state notification to a second spaceborne routing node, the congestion state notification comprises a congestion occurrence notification, the congestion occurrence notification is used for instructing the second satellite-borne routing node to execute a congestion assistance operation, and the congestion assistance operation comprises pausing the transmission of the first data and caching the first data. According to the invention, mutual assistance coordination within a certain range is formed from the routing node cluster level, the data sending pressure of the first satellite-borne routing node is relieved, efficient utilization of resources is realized, the situations of service packet loss, retransmission and the like are reduced, and the service providing capability is improved.

Description

Technical Field

[0001] The present application relates to the field of satellite communication technology, and in particular to a satellite network congestion processing method, communication equipment, chip system, storage medium and program product. Background Art

[0002] Multiple onboard routing nodes form a space bearer network, connected by inter-satellite links. Once a connection is established between a satellite routing node and a ground gateway, the feeder link between the node and the gateway becomes available, serving as a physical path between the space bearer network and the ground bearer network, providing traffic transmission.

[0003] Due to the limited service area of ​​satellite-borne routing nodes, the small number of ground gateways, and unstable link quality, the feeder links are characterized by small number, periodic interruptions, low bandwidth, and unstable links. They are critical paths and scarce resources in space-borne networks.

[0004] Due to the service characteristics of satellite constellations, space service traffic often converges on the feeder link. When traffic in the space bearer network converges on the limited feeder link, the feeder link is likely to become congested, leading to packet loss and retransmission, which in turn reduces the system's ability to provide external services. Summary of the Invention

[0005] In order to alleviate, mitigate or eliminate the above-mentioned technical problems, the present application provides a satellite network congestion processing method, communication equipment, chip system, storage medium and program product to enhance the service provision capability of the satellite network.

[0006] In a first aspect, the present application provides a method for handling satellite network congestion, comprising: In the event that congestion occurs in a first feeder link connected to a first onboard routing node, the first onboard routing node sends a congestion status notification to a second onboard routing node, where the congestion status notification includes a congestion occurrence notification, and the congestion occurrence notification is used to instruct the second onboard routing node to perform a congestion assistance operation, and after completing the congestion assistance operation, send first data to the first onboard routing node, where the congestion assistance operation includes suspending the sending of the first data and caching the first data.

[0007] In a second aspect, the present application provides a method for handling satellite network congestion, comprising: The second onboard routing node receives a congestion status notification sent by the first onboard routing node; In a case where the congestion status notification is a congestion occurrence notification, the second onboard routing node performs a congestion assistance operation, the congestion assistance operation including suspending the sending of the first data and buffering the first data; After completing the congestion assistance operation, the second onboard routing node sends the first data to the first onboard routing node.

[0008] In a third aspect, the present application provides a communication device, including: at least one processor; and At least one memory having instructions stored thereon, wherein when the instructions are executed individually or collectively by the at least one processor, the communication device executes the method according to the first aspect or the second aspect.

[0009] In a fourth aspect, the present application provides a computer storage medium having instructions stored thereon, which, when executed individually or collectively by at least one processor of a communication device, causes the communication device to execute the method according to the first aspect or the second aspect.

[0010] In a fifth aspect, the present application provides a chip system comprising at least one processor, wherein the at least one processor is configured to individually or collectively execute instructions stored in at least one memory of a communication device, so that the communication device executes the method described in the first aspect or the second aspect.

[0011] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed individually or collectively by at least one processor of a communication device, cause the communication device to execute the method according to the first aspect or the second aspect.

[0012] It should be understood that the summary of the invention is not intended to identify the key or essential features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are included to provide a further understanding of the present application. They are incorporated into and constitute a part of this application. The accompanying drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the accompanying drawings: Figure 1 is a schematic diagram of a communication system provided in an embodiment of the present application; Figure 2 is a schematic diagram of a satellite network congestion processing method provided by an embodiment of the present application; Figure 3 This is a schematic diagram of a notification forwarding provided in an embodiment of the present application; Figure 4 This is a schematic diagram of a congestion occurrence notification provided by an embodiment of the present application; Figure 5 This is a schematic diagram of a congestion relief notification provided by an embodiment of the present application; Figure 6 This is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0014] The principle of the present application will now be described with reference to some embodiments. It should be understood that the description of these embodiments is merely for illustrative purposes and helps those skilled in the art to understand and implement the present application without placing any restriction on the scope of the present application. The disclosure described herein can be implemented in a manner different from that described below.

[0015] In the following description, unless defined otherwise, 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.

[0016] References in this application to "one embodiment," "an embodiment," "an exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an exemplary embodiment, whether or not explicitly described, those skilled in the art will recognize that such feature, structure, or characteristic may be combined with other embodiments.

[0017] The terms used herein are intended only to describe specific embodiments and are not intended to limit exemplary embodiments. As used herein, the singular forms "a," "an," and "the" also include the plural forms, unless the context clearly indicates otherwise. As used herein, "a group of elements" or "a set of elements" is intended to include one or more elements. It should also be understood that the terms "comprise," "include," "have," "have," "include," and / or "comprising," when used herein, specify the presence of the features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0018] Flowcharts are used in this application to illustrate the operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, the various steps may be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0019] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implementation only in analog and / or digital circuits) (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any portion of a hardware processor (including a digital signal processor) with software, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions, and (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (eg, firmware) to operate, but where software is not required for operation, the software may not be present.

[0020] This definition of circuitry applies to all uses of the term in this application. As another example, as used in this application, the term circuitry also includes merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware implementation. The term circuitry also includes, for example, if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing network device.

[0021] As used herein, the term "communication system" refers to a network system that complies with any appropriate communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), New Radio (NR), Non-Terrestrial Network (NTN), etc. Furthermore, communications between terminal devices and network devices in a communication system can be performed according to any appropriate generation of communication protocols, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), future sixth generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. The embodiments of the present application can be applied to a satellite-based routing node communication system. Given the rapid developments in communications, there will certainly be future types of communication technologies and systems, and the present application can be implemented using these technologies and systems. The scope of the present application should not be considered limited to the aforementioned systems.

[0022] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a notebook embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless user equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, an unmanned aerial vehicle, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated process chain), consumer electronic devices, relay nodes, devices operating on commercial and / or industrial wireless networks, and the like. The mobile terminal (MT) portion of the IAB node may perform the functionality of a "terminal device" and thus may operate as a terminal device. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0023] While the functionality described herein may be performed in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments, the functionality may be implemented in a user equipment device (such as a cell phone, tablet computer, laptop computer, desktop computer, mobile IoT device, or fixed IoT device). For example, the user equipment device may appropriately have the corresponding capabilities described in connection with fixed and / or wireless network nodes. The user equipment device may be a user device and / or a control device, such as a chipset or processor, configured to control the user device when installed therein. Examples of these functions include boot server functionality and / or home subscriber server functionality, which may be implemented in the user equipment device by providing the user equipment device with software configured to cause the user equipment device to perform from the perspective of these functions / nodes.

[0024] Figure 1 This is a schematic diagram of a communication system provided by an embodiment of the present application. Figure 1As shown, the communication system includes a space carrier network 100 and a ground carrier network 200, and the space carrier network 100 and the ground carrier network 200 can perform data transmission. The space carrier network 100 can transmit data to the terminal device 10 or the ground carrier network 200, and the terminal device 10 or the ground carrier network 200 can also transmit data to the space carrier network 100. The link from the space carrier network 100 to the terminal device 10 or the ground carrier network 200 is called a downlink (DL) or forward link, and the link from the terminal device 10 or the ground carrier network 200 to the space carrier network 100 is called an uplink (UL) or reverse link.

[0025] The space bearer network 100 includes multiple onboard routing nodes. Data transmission can be achieved between the multiple onboard routing nodes in the space bearer network 100 via inter-satellite links. The satellite representing the onboard routing node connecting the gateway 20 and the space bearer network 100 is called a landing satellite. This also represents the last onboard routing node in the data transmission process of the space bearer network 100, which leaves the space bearer network 100 and is forwarded to the gateway 20. The space bearer network 100 and the gateway 20 can be connected via a feeder link.

[0026] The satellite orbit of the satellite to which the onboard routing node in the space carrier network 100 belongs may be a low earth orbit (LEO), a medium earth orbit (MEO), a geosynchronous orbit (GEO) or a non-geosynchronous orbit (NGSO). It will be understood that the communication system is not required to include Figure 1 All elements shown in FIG. The number of terminal devices, gateways, satellite-based routing nodes, etc. in the communication system is for illustrative purposes only and is not intended to be limiting. The communication system may include any appropriate number of terminal devices, gateways, satellite-based routing nodes, etc. suitable for implementing the embodiments of the present application.

[0027] In some embodiments, the space bearer network 100 functions as a relay station. For example, the space bearer network 100 forwards data sent from the terminal device 10 to the terrestrial bearer network 200, or vice versa, to the terminal device 10, thereby enabling data transmission between the terminal device 10 and the terrestrial bearer network 200. It should be understood that the terminal device 10 can communicate directly with the space bearer network 100 or through a gateway.

[0028] Specifically, a terminal device 10 (i.e., data source) sends data to a space-based bearer network 100. The onboard routing nodes in the space-based bearer network 100 forward the data according to certain inter-satellite routing rules. Through the routing between the onboard routing nodes, the data sent by the terminal device 10 is forwarded to the landing satellite. The landing satellite then forwards the data to a gateway 20 for landing. Finally, the data is forwarded to the service provider via the ground-based bearer network 200. Conversely, the service provider (i.e., data source) can also send data to the terminal device 10.

[0029] For example, Figure 1 As shown, the space bearer network 100 includes 18 onboard routing nodes, which can be divided into three orbital planes. Each orbital plane includes six onboard routing nodes. Orbital plane 1 includes onboard routing nodes S-Router11-S-Router16, orbital plane 2 includes onboard routing nodes S-Router21-S-Router26, and orbital plane 3 includes onboard routing nodes S-Router31-S-Router36. For example, terminal device 10 sends data to onboard routing node S-Router11, which then routes and forwards the data to onboard routing nodes S-Router12, S-Router22, S-Router32, and S-Router33 in sequence. The satellite to which onboard routing node S-Router33 belongs, i.e., the landed satellite, then forwards the data to gateway 20. For another example, the terminal device 10 sends data to the satellite-borne routing node S-Router36, and then the satellite-borne routing node S-Router36 routes and forwards the data to the satellite-borne routing node S-Router35, the satellite-borne routing node S-Router25, and the satellite-borne routing node S-Router24 in sequence. The satellite to which the satellite-borne routing node S-Router24 belongs is the landing satellite, and then forwards the data to the gateway station 20.

[0030] Due to the limited service areas of onboard routing nodes, the small number of ground gateways, and unstable link quality, feeder links are characterized by their small number, periodic interruptions, low bandwidth, and unstable links. They are critical paths and scarce resources in the space bearer network. When traffic in the space bearer network converges on the limited feeder links, congestion is likely to occur on the feeder links, leading to packet loss and retransmissions, which in turn impairs the system's ability to provide external services.

[0031] Current designs for common onboard routing components rely on existing terrestrial congestion control technologies for feeder link congestion control, such as congestion management, congestion avoidance, and priority-based flow control. These congestion control technologies typically only consider processing between the sender and receiver ends of a link, failing to form a coordinated mechanism across the broader network. Furthermore, backpressure and discard operations are implemented at granular levels, such as priority, port, and queue, without considering the unique scenarios of feeder link congestion and implementing fine-grained backpressure and discard.

[0032] An embodiment of the present application provides a method for handling satellite network congestion. When congestion occurs on a connected first feeder link, a first onboard routing node may send a congestion status notification to a second onboard routing node indicating the occurrence of congestion. The congestion status notification may be a congestion occurrence notification, or the congestion status notification may include a parameter indicating that the congestion status notification is a congestion occurrence notification. For example, the first onboard routing node may send a congestion status notification to a surrounding second onboard routing node via a routing control plane message. The control plane protocol may select a routing protocol suitable for the satellite network, such as the Border Gateway Protocol-Link State (BGP-LS) protocol or the Open Shortest Path First (OSPF) protocol, to support fast and accurate notification transmission.

[0033] After receiving the congestion status notification sent by the first satellite routing node, the second satellite routing node performs a congestion assistance operation on the first satellite routing node, namely, suspending the transmission of the first data to the first satellite routing node and buffering the first data. After completing the congestion assistance operation, the second satellite routing node sends the first data to the first satellite routing node, and the first satellite routing node then forwards the first data to the next station, such as another satellite routing node or a gateway.

[0034] The embodiment of the present application forms mutual assistance and coordination within a certain range at the routing node cluster level, alleviates the data transmission pressure of the first satellite-borne routing node, realizes efficient utilization of resources, reduces service packet loss and retransmission, and improves service provision capabilities.

[0035] In some embodiments, the first onboard routing node may further instruct the second onboard routing node to forward the congestion status notification to a third onboard routing node, where the third onboard routing node represents another onboard routing node other than the first and second onboard routing nodes, thereby expanding the assisting cluster. For example, the first onboard routing node includes a first parameter in the congestion status notification, and the second onboard routing node sends the congestion status notification to the third onboard routing node based on the indication of the first parameter. For example, the first onboard routing node includes orbital information in the congestion status notification, and the second onboard routing node forwards the congestion status notification to the onboard routing node on the orbit indicated by the orbital information. For another example, the first onboard routing node includes a natural number N representing the maximum number of diffusion hops in the congestion status notification, indicating that the congestion status notification is to be sent to onboard routing nodes within an initial range of N hops from the first onboard routing node. The second onboard routing node may forward the congestion status notification to adjacent onboard routing nodes until it reaches an onboard routing node N hops away from the first onboard routing node. The second onboard routing node can send congestion status notifications to all adjacent onboard routing nodes to alleviate the pressure on the first onboard routing node to a greater extent. It can also send congestion status notifications only to the onboard routing nodes among the adjacent onboard routing nodes that have newly joined the service area where the onboard routing node is located and provide services for the service area, thereby ensuring that the cached data will not be lost with a greater probability.

[0036] For example, the first onboard routing node sets an initial N value. Each onboard routing node that receives a congestion status notification updates the N value until the updated N value equals zero. The onboard routing node that receives the congestion status notification then stops forwarding the congestion status notification. The first onboard routing node may set the initial N value to be greater than or equal to 1. Each time a congestion status notification is sent, the N value is decremented by 1 until the N value equals zero. It should be understood that the initial N value may also be a system default value, which is not limited in this embodiment of the present application.

[0037] For example, the second onboard routing node is a satellite routing node adjacent to the first onboard routing node, wherein the second onboard routing node may include all satellite routing nodes adjacent to the first onboard routing node, or may include only satellite routing nodes adjacent to the first onboard routing node that have newly joined the service area where the first onboard routing node is located and provide service for the service area. When the initial value of N is 1, the second onboard routing node subtracts 1 from the initial value of N to obtain 0, and thus the second onboard routing node stops forwarding the congestion status notification to the adjacent onboard routing node. When the initial value of N is 2, the second onboard routing node subtracts 1 from the initial value of N to obtain 1, and thus the second onboard routing node forwards the congestion status notification to the adjacent onboard routing node, and the satellite routing node that receives the congestion status notification forwarded by the second onboard routing node stops forwarding the congestion status notification to the adjacent onboard routing node.

[0038] The second onboard routing node or other onboard routing nodes that receive the congestion status notification may terminate the congestion assistance operation according to their own strategies, such as terminating the congestion assistance operation after executing the congestion assistance operation for a preset time, or terminating the congestion assistance operation when their own data pressure is high.

[0039] The second onboard routing node or other onboard routing nodes that receive the congestion status notification may also terminate the congestion assistance operation according to the instruction of the first onboard routing node. For example, the first onboard routing node includes a parameter indicating the conditions for terminating the congestion assistance operation in the congestion status notification, such as the congestion status notification includes a second parameter for instructing to perform the congestion assistance operation within a preset time. The second onboard routing node performs the congestion assistance operation within the preset time according to the instruction of the second parameter and terminates the congestion assistance operation after the preset time expires. The second parameter may not change during the forwarding process of the congestion status notification. The onboard routing node that receives the congestion status notification may also update the second parameter according to a certain strategy, such as increasing or decreasing the duration of the preset time indicated by the second parameter according to a preset strategy. In some embodiments, the onboard routing node closer to the first onboard routing node has a longer cache time, and the onboard routing node farther away from the first onboard routing node has a shorter cache time, and vice versa.

[0040] In another example, a first onboard routing node sends a congestion status notification indicating congestion relief to a second onboard routing node. The congestion status notification may be a congestion relief notification, or the congestion status notification may include a parameter indicating that the congestion status notification is a congestion relief notification. The second onboard routing node terminates the congestion assistance operation after receiving the congestion relief notification sent by the first onboard routing node. It should be noted that if a parameter indicates whether the congestion status notification is a congestion occurrence notification or a congestion relief notification, then upon receiving the congestion status notification, the second onboard routing node needs to determine whether it is a congestion occurrence notification or a congestion relief notification based on the parameter in the congestion status notification and then perform the corresponding operation.

[0041] In some embodiments, after receiving the congestion status notification sent by the first satellite routing node, the second satellite routing node may send a congestion status response to the first satellite routing node to confirm receipt of the congestion status notification, or indicate in the congestion status response whether to perform congestion assistance operations, etc.

[0042] Figure 2 FIG is a schematic diagram of a satellite network congestion processing method provided by an embodiment of the present application. Figure 2 As shown, the satellite network congestion handling method includes the following: Step 201: When congestion occurs in a first feeder link connected to a first onboard routing node, the first onboard routing node sends a congestion occurrence notification to a second onboard routing node.

[0043] The first onboard routing node can send a congestion notification to the second onboard routing node based on its own strategy or when certain conditions are met, requesting the second onboard routing node to perform congestion assistance operations to alleviate the pressure on the first onboard routing node to send data. The satellite to which the first onboard routing node belongs can be a landing satellite, that is, the last onboard routing node forwarded by the space bearer network to the ground, or an intermediate node in the routing path, that is, an intermediate onboard routing node forwarded by the space bearer network to the ground.

[0044] In some embodiments, the first onboard routing node may send a congestion occurrence notification to the second onboard routing node only when congestion assistance is needed, or may periodically send a congestion occurrence notification to the second onboard routing node until congestion assistance from the second onboard routing node is no longer needed.

[0045] It should be noted that the first onboard routing node can send a congestion status notification to one or more onboard routing nodes, that is, the second onboard routing node may include one or more onboard routing nodes. The second onboard routing node can be one or more onboard routing nodes selected by the first onboard routing node according to its own strategy, such as an onboard routing node adjacent to the first onboard routing node, or an onboard routing node included in a routing path including the first onboard routing node, or one or more onboard routing nodes selected by the first onboard routing node according to manually set conditions. For example, the first onboard routing node can send a congestion status notification to all adjacent onboard routing nodes, or it can select some of the adjacent onboard routing nodes to send the congestion status notification based on the constellation configuration, satellite movement direction, etc. The part of the onboard routing nodes can be onboard routing nodes that have newly joined the service area where the first onboard routing node is located and provide services for the service area, that is, onboard routing nodes that enter the service area after the first onboard routing node, thereby ensuring with a greater probability that the cached first data will not be lost.

[0046] Step 202: The second satellite-borne routing node performs a congestion assistance operation.

[0047] After receiving the congestion status notification sent by the first satellite routing node, the second satellite routing node may perform congestion assistance operations according to its own strategy or when certain conditions are met.

[0048] In some embodiments, upon receiving a congestion occurrence notification from the first satellite routing node, the second satellite routing node may perform congestion assistance for the first satellite routing node. For example, after receiving the congestion occurrence notification from the first satellite routing node, if the second satellite routing node receives first data intended for transmission to the first satellite routing node, the second satellite routing node may cache the first data and temporarily not transmit the first data to the first satellite routing node.

[0049] The second onboard routing node can cache the first data according to a certain strategy. For example, the second onboard routing node can introduce a dedicated preset cache area during the route selection process, and cache the first data in the preset cache area during route selection until the preset cache area overflows. The size of the preset cache area can be set by the maximum value of the amount of cached data, storage space, queue length, or other parameters, and the above parameters support initial configuration and modification. For another example, the second onboard routing node can cache the first data for a preset time according to its own strategy or relevant instructions, and stop caching the first data after the preset time expires.

[0050] The second onboard routing node can also select which data to cache based on a specific strategy, enabling fine-grained service flow control based on information at the IP routing layer. For example, the second onboard routing node can cache all data to be sent to the first onboard routing node, or cache data (i.e., first data) to be sent to the first onboard routing node with a destination address that is a preset address, or cache data (i.e., first data) to be sent to the first onboard routing node with a next-hop address indicating a border gateway connected to the first onboard routing node, or cache data (i.e., first data) to be sent to the first onboard routing node with an IPv6 address list that includes information about the first onboard routing node or information about a border gateway connected to the first onboard routing node.

[0051] In some other embodiments, after receiving the congestion occurrence notification sent by the first satellite routing node, the second satellite routing node may first determine whether it performs congestion assistance operations for the first satellite routing node. Only when its own conditions permit, it performs congestion assistance operations to improve assistance efficiency. For example, the second satellite routing node determines whether it is connected to the feeder link. If the second satellite routing node is not connected to the feeder link, the second satellite routing node performs congestion assistance operations. Otherwise, the second satellite routing node does not perform congestion assistance operations to avoid further pressure on already strained resources. For another example, the second satellite routing node determines the number of congestion assistance operations it has participated in. If the number of congestion assistance operations the second satellite routing node has participated in is less than a preset threshold, the second satellite routing node performs congestion assistance operations. Otherwise, the second satellite routing node does not perform congestion assistance operations. The maximum number of congestion assistance operations that the second satellite routing node can participate in can be determined based on its own computing power and data caching capacity.

[0052] In some embodiments, after receiving the congestion occurrence notification sent by the first satellite routing node, the second satellite routing node may also send a congestion occurrence response to the first satellite routing node to confirm receipt of the congestion occurrence notification, or may also indicate whether to participate in congestion assistance in the congestion occurrence response.

[0053] Step 203: The second satellite-borne routing node ends the congestion assistance operation.

[0054] The second onboard routing node may terminate the congestion assistance operation according to its own policy or an instruction from the first onboard routing node. For example, the first onboard routing node sends a congestion relief notification to the second onboard routing node, and the second onboard routing node terminates the congestion assistance operation based on the congestion relief notification.

[0055] In some embodiments, after receiving the congestion relief notification sent by the first satellite routing node, the second satellite routing node may further send a congestion relief response to the first satellite routing node to confirm receipt of the congestion relief notification.

[0056] Step 204: The second onboard routing node sends the first data to the first onboard routing node.

[0057] After the congestion assistance operation ends, the second onboard routing node sends the first data to the first onboard routing node. The first data sent by the second onboard routing node to the first onboard routing node includes both the first data cached by the second onboard routing node and the first data to be sent to the first onboard routing node during subsequent route selection.

[0058] Step 205: The first satellite-borne routing node sends the first data to the next station.

[0059] If the satellite to which the first onboard routing node belongs is a landed satellite, the first onboard routing node sends the first data to the gateway to achieve the landing of the first data. Otherwise, the first onboard routing node sends the first data to other onboard routing nodes in the routing path to achieve routing forwarding of the first data.

[0060] In some embodiments, the first onboard routing node may further include a first parameter in the congestion status notification, and the second onboard routing node may determine whether to forward the congestion status notification to a third onboard routing node based on the indication of the first parameter. In this embodiment, participating in congestion assistance includes performing congestion assistance operations and / or forwarding the congestion status notification. The operations of the third onboard routing node may refer to those of the second onboard routing node and will not be described in detail here.

[0061] For example, the onboard routing node that is 1 hop away from the first onboard routing node and the onboard routing node that is 2 hops away can refer to Figure 3 .like Figure 3 As shown, onboard routing node S-Router33 serves as the first onboard routing node. Onboard routing nodes S-Router23, S-Router32, and S-Router43 are all onboard routing nodes one hop away from S-Router33. The second onboard routing node can be selected from these onboard routing nodes. Onboard routing nodes S-Router13, S-Router22, S-Router31, S-Router42, and S-Router53 are all onboard routing nodes two hops away from S-Router33. The third onboard routing node can be selected from these onboard routing nodes.

[0062] In order to better understand this application, the following Figure 4 and Figure 5 , the following is further explained by taking the example that the first satellite routing node is the satellite routing node S-Router3, and when the feeder link between the satellite routing node S-Router3 and the gateway station is congested, the assistance of the surrounding satellite routing nodes is needed.

[0063] When congestion occurs on the feeder link between satellite routing node S-Router3 and the gateway, a congestion notification is issued to satellite routing nodes within N hops, forming an assisting cluster for satellite routing node S-Router3. When the congestion on the feeder link eases, a congestion relief notification is issued to satellite routing nodes within N hops, halting their congestion assistance operations for S-Router3. The surrounding satellite routing nodes then continue to send data to S-Router3 as normal. Based on the link conditions of satellite routing components near the feeder link, a congestion backpressure and caching mechanism is designed at the routing node cluster level to achieve mutual assistance and collaboration within a certain range. This eliminates the need to further enhance the capabilities of individual nodes and instead fully utilizes the idle capacity of surrounding nodes to form a short-term, small-scale assisting cluster, achieving efficient resource utilization.

[0064] In some embodiments, the satellite-borne routing node S-Router3 may immediately send a congestion notification when it detects that the feeder link is congested, and then periodically send congestion notifications until the feeder link congestion state is relieved. The satellite-borne routing node S-Router3 may immediately send a congestion relief notification when it detects that the feeder link congestion is relieved, and then periodically send congestion relief notifications and end the sending according to a certain strategy. The strategy for ending the periodic sending of congestion relief notifications can be selected after a certain number of times, or after receiving a response from the notified satellite-borne routing node. Among them, the period for sending notifications can support parameterized configuration and dynamic modification, and the period for sending notifications can follow the period of an existing protocol on the control plane (such as the period of BGP (Border Gateway Protocol) update messages).

[0065] Figure 4 Schematic diagram of a congestion notification provided by an embodiment of the present application. Figure 4 As shown, after the satellite-borne routing node S-Router3 establishes a feeder link connection with the gateway, it determines whether the feeder link is congested. If congestion occurs, it completes the preparation for the feeder link congestion notification, sets corresponding parameters in the congestion notification, such as parameter N and / or preset time t, and then sends the congestion notification to the satellite-borne routing nodes S-Router2 and S-Router4 with adjacent preset step sizes.

[0066] In some embodiments, the landing satellite S-Router3 can obtain the connection status of the feed link of the onboard routing node by communicating with the baseband, antenna, integrated electronics and other payloads. The onboard routing node S-Router3 can further judge the congestion status of the feed link according to the sending port queue status corresponding to the feed link on the routing component. Among them, the sending port queue status includes but is not limited to real-time status data such as queue buffer length and port packet loss number, and the corresponding parameter threshold is configured. When one status data or multiple status data exceed the configured threshold, it can be considered that the feed link is congested; otherwise, as long as the above conditions are not met, it is considered that the feed link congestion state is relieved. In some embodiments, in order to avoid frequent switching of the feed link congestion state due to real-time changes in status data, a smoothing operation can be added, and the congestion state is set and / or released only after a certain number of times. It should be understood that the above-mentioned parameters such as status data threshold and smoothing times support initialization configuration and can be modified during operation.

[0067] After receiving the congestion notification, the satellite routing nodes S-Router2 and S-Router4 can send a congestion response to the satellite routing node S-Router3 to acknowledge receipt of the congestion notification. Alternatively, they can choose not to send a congestion response, thereby reducing signaling interactions and improving congestion handling efficiency.

[0068] Onboard routing nodes S-Router2 and S-Router4 perform caching decisions, that is, determine whether to participate in congestion assistance. If they do not participate, such as detecting that they are connected to a feeder link or the number of congestion assistance they participate in reaches a preset threshold, they send a response to onboard routing node S-Router3, instructing them not to perform data caching and congestion notification diffusion. They can also choose not to send a response to onboard routing node S-Router3 to simplify the exchange of control plane messages and make the solution more efficient.

[0069] If participation is possible, such as when it detects it is not connected to a feeder link or the number of congestion assistance sessions it is participating in is less than a preset threshold, it performs congestion assistance and activates caching. It also sends a congestion notification to adjacent onboard routing nodes S-Router1 and S-Router6. Furthermore, prior to sending the notification, it may update the corresponding parameters in the congestion notification, such as parameter N and / or the preset time t.

[0070] In some embodiments, the onboard routing nodes S-Router1 and S-Router6 can determine which data to cache based on certain policies. This embodiment implements fine-grained service flow control based on information at the IP routing level, which is more accurate than traditional port- and queue-based congestion control. An example is as follows: (1) Port-based coarse-grained caching strategy All data sent to the onboard routing node S-Router3 is cached. While this strategy is relatively straightforward to implement, it effectively captures all data potentially affected by congestion, enabling a rapid response when congestion occurs and improving overall network throughput and stability.

[0071] (2) Fine-grained caching strategy based on IP address (2.a) Filter data based on its destination IP address. For example, if the cached destination IP address points to a specific terminal or service node in the ground bearer network and the data is to be sent to the satellite routing node S-Router3 and lands on a congested feeder link,

[0072] (2.b) Filtering is performed based on the next-hop IP address. For example, if the next-hop IP address is identified as the IP address of the border gateway connected to the satellite-borne routing node S-Router3, that is, the IP address of the border gateway connected to the feeder link, it is determined that the data needs to be cached.

[0073] (3) Cache strategy based on SRV6 SID List (i.e. IPv6 address list) If IP packets are transmitted using SRV6, the information in the SRv6 SID List can be used as the basis for caching decisions. When the SID List contains information about the onboard routing node S-Router3 or the IP address of the border gateway connected to the onboard routing node S-Router3 during route selection, the packet is determined to be cached.

[0074] The operations of the satellite routing nodes S-Router1 and S-Router6 after receiving the congestion notification can be referred to those of the satellite routing nodes S-Router2 and S-Router4, and will not be described in detail here.

[0075] When the onboard routing node S-Router3 detects that the feeder link congestion is released, it completes the feeder link congestion release notification preparation and then sends the congestion release notification, such as Figure 5 The sending of congestion relief notifications can be found in the sending of congestion occurrence notifications and will not be detailed here. Upon receiving the congestion relief notification, the onboard routing node terminates congestion assistance, disables its caching function, and sends data normally to onboard routing node S-Router3. S-Router3 then forwards the data to the gateway for data delivery.

[0076] The present application also provides a chip system, comprising: a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, a pin, or a circuit. The processing unit may execute computer instructions. For example, at least one processor may be configured to execute instructions stored in at least one memory of a communication device, either individually or collectively, to cause the communication device to execute the method described in the above embodiment.

[0077] In some embodiments, the computer instructions are stored in a memory unit.

[0078] In some embodiments, the storage unit is an on-chip storage unit, such as a register or cache. Alternatively, the storage unit may be an external storage unit within the terminal, such as a ROM or other static storage device capable of storing static information and instructions, or a RAM. The processor mentioned in any of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program for the satellite network congestion handling method. The processing unit and the storage unit may be decoupled and disposed on separate physical devices, connected via wired or wireless means to implement their respective functions, thereby supporting the chip system in implementing the various functions described in the above embodiments. Alternatively, the processing unit and the memory may be coupled on the same device.

[0079] Figure 6 6 is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. For example, the terminal device, the first satellite routing node, the second satellite routing node, the third satellite routing node, and the gateway station can be implemented by the communication device 600. The communication device 600 can also include the above-mentioned chip system. Figure 6 As shown, the communication device 600 includes one or more processors 610 , one or more memories 620 coupled to the processor 610 , and one or more communication modules 640 coupled to the processor 610 .

[0080] The communication module 640 is used for two-way communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communicating with other network elements.

[0081] Processor 610 may be of any type suitable for the local technology network and may include, by way of non-limiting example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Communication device 600 may have multiple processors, such as application specific integrated circuit chips, which are driven in time to a clock that synchronizes the master processor.

[0082] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist across a power outage.

[0083] Computer program 630 includes computer executable instructions for execution by associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any appropriate actions and processes by loading program 630 into RAM 622.

[0084] The embodiments of the present application can be implemented through the program 630, so that the communication device 600 can perform any process disclosed by the method described in the above embodiments. The embodiments of the present application can also be implemented through hardware or a combination of software and hardware.

[0085] In some embodiments, program 630 may be tangibly embodied on a computer-readable medium, which may be contained in communication device 600 (e.g., memory 620) or other storage device accessible to communication device 600. Communication device 600 may load program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Program 630 is stored on the computer-readable medium.

[0086] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present application are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0087] The present application also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the methods described in the above embodiments. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or separated between program modules as needed. The machine-executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0088] The program code that is used to carry out the method for the present application can be written with any combination of one or more programming languages.These program codes can be provided to the processor or controller of general-purpose computer, special-purpose computer or other programmable data processing equipment, make when program code is carried out by processor or controller, the function / operation specified in flow chart and / or block diagram is realized.Program code can be carried out fully on machine as independent software package, partly on machine, partly on machine, partly on remote machine, partly on remote machine, or all on remote machine or server.

[0089] In the context of this application, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0090] A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0091] In addition, although operations are described in a specific order, this should not be understood as requiring the specific order or sequence shown to perform these operations, or to perform all operations shown, to obtain the required result. In some cases, multi-tasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limiting the scope of the application, but can be interpreted as a description of the specific features of a particular embodiment. Some features described in the context of a separate embodiment also can be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment also can be realized individually or in any suitable sub-combination in multiple embodiments.

[0092] Although the present application has been described in language specific to structural features and / or methodological acts, it should be understood that the present application defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0093] It should be understood that the use of personally identifiable information should be subject to privacy policies and practices generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

1. A satellite network congestion processing method, characterized in that: include: In the event that congestion occurs in a first feeder link connected to a first satellite-borne routing node, the first satellite-borne routing node sends a congestion status notification to a second satellite-borne routing node, wherein the congestion status notification includes a congestion occurrence notification, and the congestion occurrence notification is used to instruct the second satellite-borne routing node to perform a congestion assistance operation, and after ending the congestion assistance operation, send first data to the first satellite-borne routing node, wherein the congestion assistance operation includes suspending the sending of the first data and caching the first data.

2. The method according to claim 1, characterized in that The congestion status notification includes a first parameter, where the first parameter is used to indicate whether the second onboard routing node sends a congestion status notification to the third onboard routing node.

3. The method according to claim 2, characterized in that The first parameter is a natural number N, which is used to indicate that a congestion status notification is sent to the satellite routing nodes within an initial N hops from the first satellite routing node.

4. The method according to claim 3, characterized in that The initial value of N is greater than or equal to 1, the congestion status notification further instructs the second onboard routing node to update a first parameter in the congestion status notification, and the updating of the first parameter in the congestion status notification includes subtracting 1 from the value of the first parameter to obtain a new first parameter; When the new first parameter is greater than zero, the second onboard routing node is instructed to send a congestion status notification to an adjacent onboard routing node; when the new first parameter is equal to zero, the second onboard routing node is instructed to stop sending a congestion status notification to an adjacent onboard routing node.

5. The method according to claim 4, characterized in that The sending of the congestion status notification to the adjacent onboard routing node includes: A congestion status notification is sent to a target satellite routing node among the adjacent satellite routing nodes, wherein the target satellite routing node includes a satellite routing node that is newly added to the service area where the satellite routing node is located and provides services for the service area.

6. The method according to any one of claims 1 to 5, characterized in that The congestion occurrence notification includes a second parameter, and the second parameter is used to instruct the second onboard routing node to perform the congestion assistance operation within a preset time.

7. The method according to claim 6, characterized in that The congestion occurrence notification further instructs the second onboard routing node to update a second parameter in the congestion occurrence notification, wherein updating the second parameter in the congestion occurrence notification includes increasing the duration of the preset time or decreasing the duration of the preset time according to a preset strategy.

8. The method according to any one of claims 1 to 5, characterized in that The congestion status notification also includes a congestion relief notification. After the first onboard routing node sends the congestion occurrence notification to the second onboard routing node, the first onboard routing node sends the congestion relief notification to the second onboard routing node, and the congestion relief notification is used to instruct the second onboard routing node to end the congestion assistance operation.

9. The method according to any one of claims 1 to 5, characterized in that Also includes: The first onboard routing node receives a congestion status response sent by the second onboard routing node, where the congestion status response includes a congestion occurrence response, and the congestion occurrence response is used to indicate whether the second onboard routing node participates in congestion assistance.

10. The method according to any one of claims 1 to 5, characterized in that Also includes: When a first feeder link between the first onboard routing node and the gateway is in a connected state, the first onboard routing node determines whether the first feeder link is congested.

11. A method for processing satellite network congestion, characterized in that: include: The second onboard routing node receives a congestion status notification sent by the first onboard routing node; In a case where the congestion status notification is a congestion occurrence notification, the second onboard routing node performs a congestion assistance operation, the congestion assistance operation including suspending the sending of the first data and buffering the first data; After completing the congestion assistance operation, the second onboard routing node sends the first data to the first onboard routing node.

12. The method according to claim 11, characterized in that The congestion status notification includes a first parameter, and the method further includes: The second onboard routing node determines whether to send a congestion status notification to a third onboard routing node according to an indication of the first parameter.

13. The method according to claim 12, characterized in that The first parameter is a natural number N, which is used to indicate that a congestion status notification is sent to the satellite routing nodes within an initial N hops from the first satellite routing node.

14. The method according to claim 13, characterized in that The value of the initial N is greater than or equal to 1, and the method further includes: The second onboard routing node updates a first parameter in the congestion status notification, wherein updating the first parameter in the congestion status notification includes subtracting 1 from a value of the first parameter to obtain a new first parameter; When the new first parameter is greater than zero, the second onboard routing node sends a congestion status notification to an adjacent onboard routing node; when the new first parameter is equal to zero, the second onboard routing node stops sending a congestion status notification to an adjacent onboard routing node.

15. The method according to any one of claims 11 to 14, characterized in that The congestion occurrence notification includes a second parameter, and the second onboard routing node performs a congestion assistance operation including: The second onboard routing node performs the congestion assistance operation within a preset time indicated by the second parameter.

16. The method according to claim 15, characterized in that Also includes: The second onboard routing node updates a second parameter in the congestion occurrence notification, and the updating of the second parameter in the congestion occurrence notification includes increasing a duration of the preset time or decreasing a duration of the preset time according to a preset strategy.

17. The method according to any one of claims 11 to 14, characterized in that Also includes: In a case where the congestion status notification is a congestion relief notification, the second onboard routing node ends the congestion assistance operation.

18. The method according to any one of claims 11 to 14, characterized in that The second onboard routing node performing the congestion assistance operation includes: The second onboard routing node determines whether it is connected to the feeder link; If the second onboard routing node is not connected to the feeder link, the second onboard routing node performs a congestion assistance operation.

19. The method according to any one of claims 11 to 14, characterized in that The second onboard routing node performing the congestion assistance operation includes: The second onboard routing node determines the number of congestion assistances in which it has participated; If the number of congestion assistance operations in which the second onboard routing node has participated is less than a preset threshold, the second onboard routing node performs a congestion assistance operation.

20. The method according to any one of claims 11 to 14, characterized in that The caching the first data comprises: The first data is cached in a preset cache area until the preset cache area overflows.

21. The method according to any one of claims 11 to 14, characterized in that The caching the first data comprises: caching data in the first data whose destination address is a preset address; or Cache data in the first data indicating a border gateway connected to the first onboard routing node with a next hop address; or The IPv6 address list in the first data is cached and includes data of the first onboard routing node information or border gateway information connected to the first onboard routing node.

22. A communication device, characterized in that: include: at least one processor; as well as At least one memory having instructions stored thereon, which, when executed individually or collectively by the at least one processor, cause the communication device to perform the method according to any one of claims 1-21.

23. A computer storage medium, characterized in that The computer storage medium stores instructions, which, when executed individually or collectively by at least one processor of a communication device, cause the communication device to perform a method according to any one of claims 1 to 21.

24. A chip system, characterized in that: The device comprises at least one processor, wherein the at least one processor is configured to execute, individually or collectively, instructions stored in at least one memory of a communication device, so that the communication device executes the method according to any one of claims 1 to 21.

25. A computer program product, characterized in that The method comprises instructions which, when executed individually or collectively by at least one processor of a communication device, cause the communication device to perform a method according to any one of claims 1 to 21.

Images