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

Abstract

The present application provides a satellite network congestion processing method, communication equipment, chip system, storage medium and program product, and relates to the field of satellite communication technology. The satellite network congestion processing method provided by the present application includes: when the first feeder link connected to the first satellite routing node is congested, the first satellite routing node sends a congestion status notification to the second satellite routing node, and the congestion status notification includes a congestion occurrence notification, and the congestion occurrence notification is used to instruct the second satellite routing node to perform a congestion assistance operation, and the congestion assistance operation includes suspending the transmission of the first data and caching the first data. 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 routing node, realizes efficient use of resources, reduces service packet loss, retransmission, etc., and improves service provision capabilities.

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 satellite-borne routing nodes can form a space bearer network, and the satellite-borne routing nodes in the space bearer network are connected through inter-satellite links. When the satellite-borne routing node establishes a connection with the ground gateway, the feeder link between the satellite-borne routing node and the gateway becomes available from unavailable, and provides traffic transmission as a physical path between the space bearer network and the ground bearer network.

[0003] Due to the limitations of the service area of ​​satellite 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 bearer networks.

[0004] According to the service characteristics of satellite constellations, space service traffic will converge to the feeder link in many scenarios. When the traffic in the space bearer network converges to the limited feeder link, the feeder link is likely to be congested, which is prone to service packet loss and retransmission, resulting in low ability of the system 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 satellite network congestion processing method, comprising:

[0007] 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.

[0008] In a second aspect, the present application provides a satellite network congestion processing method, comprising:

[0009] The second onboard routing node receives a congestion status notification sent by the first onboard routing node;

[0010] 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;

[0011] After completing the congestion assistance operation, the second onboard routing node sends the first data to the first onboard routing node.

[0012] In a third aspect, the present application provides a communication device, including:

[0013] at least one processor; and

[0014] At least one memory stores instructions thereon, and 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.

[0015] 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 described in the first aspect or the second aspect.

[0016] 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.

[0017] 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.

[0018] It should be understood that the invention summary 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 easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings are included to provide a further understanding of the present application. They are included and constitute a part of the present application. The accompanying drawings illustrate embodiments of the present application and together with the present specification serve to explain the principles of the present application. In the accompanying drawings:

[0020] Figure 1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0021] Figure 2 is a schematic diagram of a satellite network congestion processing method provided by an embodiment of the present application;

[0022] Figure 3 It is a schematic diagram of a notification forwarding provided in an embodiment of the present application;

[0023] Figure 4 It is a schematic diagram of a congestion occurrence notification provided by an embodiment of the present application;

[0024] Figure 5 is a schematic diagram of a congestion relief notification provided by an embodiment of the present application;

[0025] Figure 6 It is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] 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 only for illustrative purposes, and helps those skilled in the art to understand and implement the present application, without any limitation to the scope of the present application. The disclosure described herein can be implemented in a manner different from that described below.

[0027] 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.

[0028] 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 affect incorporation into other embodiments.

[0029] The terms used herein are only for describing specific embodiments, rather than for limiting exemplary embodiments. The singular forms "one", "an", and "the" used herein also include plural forms, unless the context clearly indicates otherwise. "A group of elements" or "element set" used herein is intended to include one or more elements. It should also be understood that the terms "include", "comprise", "have", "have", "include" and / or "include", when used herein, specify the presence of the features, elements and / or parts, etc., but do not exclude the presence or addition of one or more other features, elements, parts and / or combinations thereof.

[0030] Flowcharts are used in the present application to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed accurately in order. On the contrary, various steps may be processed in reverse order or simultaneously. At the same time, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0031] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0032] (a) Hardware circuit implementation only (e.g., implementation only in analog and / or digital circuits)

[0033] (b) a combination of hardware circuitry and software, such as (where applicable):

[0034] (i) a combination of analog and / or digital hardware circuits and software / firmware; and

[0035] (ii) any part 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

[0036] (c) A hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that requires software (eg, firmware) to operate, but where software is not required for operation, the software may not be present.

[0037] 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 an implementation of 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. 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.

[0038] 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. In addition, the communication between the terminal equipment and the network equipment in the communication system can be performed according to any appropriate generation of communication protocols, including but not limited to the 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 the satellite routing node communication system. In view of the rapid development in communication, there will certainly be future types of communication technologies and systems, and the present application can be implemented with these technologies and systems. It should not be considered that the scope of the present application is limited to the aforementioned system.

[0039] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a user station (SS), a portable user station, a mobile station (MS), or an 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 game 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 (Lot) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, 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 processing chain), consumer electronic devices, relay nodes, devices operating on commercial and / or industrial wireless networks, etc. The mobile terminal (MT) part of the IAB node may perform the functions 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.

[0040] Although the functions described herein may be performed in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments, the functions may be implemented in a user equipment device (such as a cellular phone, or a tablet computer, or a laptop computer, or a desktop computer, or a mobile Internet of Things device, or a fixed Internet of Things device). For example, the user equipment device may appropriately have the corresponding capabilities described in relation to 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 a processor, which is configured to control the user device when the user device is installed therein. Examples of these functions include boot server functions and / or home user servers, which may be implemented in a user equipment device by providing the user equipment device with software configured to cause the user equipment device to execute from the perspective of these functions / nodes.

[0041] Figure 1 Schematic diagram of a communication system provided by an embodiment of the present application. Figure 1 As 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 a 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 a reverse link.

[0042] The space bearer network 100 includes a plurality of satellite-borne routing nodes, and data transmission can be realized between the plurality of satellite-borne routing nodes in the space bearer network 100 through inter-satellite links. The satellite to which the satellite-borne routing node connecting the gateway station 20 and the space bearer network 100 belongs is called a landing satellite, and also represents the last-hop satellite-borne routing node that leaves the space bearer network 100 and is forwarded to the gateway station 20 during the data transmission process of the space bearer network 100. The space bearer network 100 and the gateway station 20 can be connected through a feeder link.

[0043] 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 1The number of terminal devices, gateways, satellite-borne routing nodes, etc. in the communication system is for illustrative purposes only and is not intended to impose any limitation. The communication system may include any appropriate number of terminal devices, gateways, satellite-borne routing nodes, etc. suitable for implementing the embodiments of the present application.

[0044] In some embodiments, the space bearer network 100 plays the role of a relay station, such as the space bearer network 100 forwards the data sent by the terminal device 10 to the ground bearer network 200, or forwards the data sent by the ground bearer network 200 to the terminal device 10, so as to realize the data transmission between the terminal device 10 and the ground bearer network 200. It should be understood that the terminal device 10 can directly connect to the space bearer network 100 for communication, or connect to the space bearer network 100 for communication through a gateway.

[0045] Specifically, the terminal device 10 (i.e., the data source) sends data to the space bearer network 100. The satellite-borne routing nodes in the space bearer network 100 forward the data according to certain inter-satellite routing rules. Through the routing between the satellite-borne routing nodes, the data sent by the terminal device 10 is forwarded to the landing satellite, and then the landing satellite forwards the data to the gateway station 20 to achieve data landing, and finally forwards it to the service provider through the ground bearer network 200. Conversely, the service provider (i.e., the data source) can also send data to the terminal device 10.

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

[0047] Due to the limited service area of ​​satellite routing nodes, the small number of ground gateways, and unstable link quality, the feeder links are characterized by small number, periodic interruption, low bandwidth, and unstable links. They are critical paths and scarce resources in the space bearer network. When the traffic in the space bearer network converges to the limited feeder links, the feeder link congestion is likely to occur, and service packet loss and retransmission are prone to occur, resulting in the system's ability to provide services to the outside world being low.

[0048] In the current design of general satellite routing component solutions, the existing congestion control technologies on the ground are used in feeder link congestion control, such as congestion management, congestion avoidance, priority-based flow control, etc. These congestion control technologies usually only consider the processing between the two ends of the link, and do not form a coordination mechanism for a larger network range. At the same time, back pressure and discard operations are performed based on granularity such as priority, port level, and queue level, without considering the unique scenarios of feeder link congestion, and no fine-grained back pressure and discard are performed.

[0049] An embodiment of the present application provides a method for processing satellite network congestion, in which a first satellite-borne routing node may send a congestion status notification indicating the occurrence of congestion to a second satellite-borne routing node when congestion occurs in a connected first feeder link, and the congestion status notification may be a congestion occurrence notification, or the congestion status notification may contain a parameter indicating that the congestion status notification is a congestion occurrence notification. For example, the first satellite-borne routing node may send a congestion status notification to the surrounding second satellite-borne routing nodes via a routing control plane message, and 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 sending.

[0050] 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, that is, suspends the sending of the first data to be sent to the first satellite routing node, and caches 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 forwards the first data to the next station, such as other satellite routing nodes or a gateway station.

[0051] 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 use of resources, reduces service packet loss and retransmission, and improves service provision capabilities.

[0052] In some embodiments, the first satellite routing node may also instruct the second satellite routing node to forward the congestion status notification to the third satellite routing node, and the third satellite routing node represents other satellite routing nodes other than the first satellite routing node and the second satellite routing node, so as to expand the assistance cluster. For example, the first satellite routing node includes a first parameter in the congestion status notification, and the second satellite routing node sends the congestion status notification to the third satellite routing node according to the indication of the first parameter. For example, the first satellite routing node includes orbital information in the congestion status notification, and the second satellite routing node forwards the congestion status notification to the satellite routing node on the orbit indicated by the orbital information. For another example, the first satellite routing node includes a natural number N representing the maximum number of diffusion hops in the congestion status notification, that is, it indicates that the congestion status notification is sent to the satellite routing nodes within the initial N hops from the first satellite routing node, and the second satellite routing node may forward the congestion status notification to the adjacent satellite routing nodes until it is forwarded to the satellite routing node N hops away from the first satellite routing node. The second satellite routing node may send a congestion status notification to all adjacent satellite routing nodes to alleviate the pressure on the first satellite routing node to a greater extent, or may send a congestion status notification only to the satellite routing nodes among the adjacent satellite routing nodes that have newly joined the service area where the satellite 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.

[0053] For example, the first satellite routing node sets the initial value of N, and the satellite routing node that receives the congestion status notification updates the value of N until the updated value of N is equal to zero, and the satellite routing node that receives the congestion status notification stops forwarding the congestion status notification. The first satellite routing node may set the initial value of N to be greater than or equal to 1, and each time the congestion status notification is sent, the value of N is subtracted by 1 until the value of N is equal to zero. It should be understood that the initial value of N may also be a system default value, and the embodiments of the present application are not limited to this.

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

[0055] 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.

[0056] The second satellite routing node or other satellite routing nodes that receive the congestion status notification may also end the congestion assistance operation according to the instruction of the first satellite routing node. For example, the first satellite routing node includes a parameter indicating the condition for ending the congestion assistance operation in the congestion status notification, such as the congestion status notification includes a second parameter for indicating that the congestion assistance operation is to be performed within a preset time, and the second satellite routing node performs the congestion assistance operation within the preset time according to the instruction of the second parameter, and ends the congestion assistance operation after the preset time ends. The second parameter may not change during the forwarding process of the congestion status notification, and the satellite routing node that receives the congestion status notification may also update the second parameter according to a certain strategy, such as increasing the duration of the preset time indicated by the second parameter or reducing the duration of the preset time indicated by the second parameter according to the preset strategy. In some embodiments, the satellite routing node that is closer to the first satellite routing node has a longer cache time, and the satellite routing node that is farther away from the first satellite routing node has a shorter cache time, and vice versa.

[0057] For another example, the first satellite-borne routing node sends a congestion status notification indicating congestion relief to the second satellite-borne routing node, and the congestion status notification may be a congestion relief notification, or the congestion status notification includes a parameter indicating that the congestion status notification is a congestion relief notification, and the second satellite-borne routing node ends the congestion assistance operation after receiving the congestion relief notification sent by the first satellite-borne routing node. It should be noted that if the parameter indicates whether the congestion status notification is a congestion occurrence notification or a congestion relief notification, then after receiving the congestion status notification, the second satellite-borne routing node needs to determine whether it is a congestion occurrence notification or a congestion relief notification according to the parameter in the congestion status notification, and then perform the corresponding operation.

[0058] 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 a congestion assistance operation, etc.

[0059] Figure 2 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 processing method includes the following contents:

[0060] Step 201: When congestion occurs in a first feeder link connected to a first satellite routing node, the first satellite routing node sends a congestion occurrence notification to a second satellite routing node.

[0061] The first satellite-borne routing node may send a congestion occurrence notification to the second satellite-borne routing node according to its own strategy or when certain conditions are met, and request the second satellite-borne routing node to perform a congestion assistance operation to relieve the pressure of data transmission of the first satellite-borne routing node. The satellite to which the first satellite-borne routing node belongs may be a landed satellite, that is, the last-hop satellite-borne routing node forwarded from the space bearer network to the ground, or an intermediate node in the routing path, that is, an intermediate-hop satellite-borne routing node forwarded from the space bearer network to the ground.

[0062] 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.

[0063] It should be noted that the first satellite-borne routing node may send a congestion status notification to one or more satellite-borne routing nodes, that is, the second satellite-borne routing node may include one or more satellite-borne routing nodes. The second satellite-borne routing node may be one or more satellite-borne routing nodes selected by the first satellite-borne routing node according to its own strategy, such as a satellite-borne routing node adjacent to the first satellite-borne routing node, or a satellite-borne routing node included in a routing path including the first satellite-borne routing node, or one or more satellite-borne routing nodes selected by the first satellite-borne routing node according to artificially set conditions. For example, the first satellite-borne routing node may send a congestion status notification to all adjacent satellite-borne routing nodes, or may select some satellite-borne routing nodes from the adjacent satellite-borne routing nodes to send a congestion status notification according to the constellation configuration, the direction of satellite movement, etc., and the part of the satellite-borne routing nodes may be satellite-borne routing nodes newly added to the service area where the first satellite-borne routing node is located to provide services for the service area, that is, satellite-borne routing nodes that enter the service area after the first satellite-borne routing node, which can ensure that the cached first data does not cause packet loss with a greater probability.

[0064] Step 202: The second onboard routing node performs a congestion assistance operation.

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

[0066] In some embodiments, as long as the second onboard routing node receives the congestion occurrence notification sent by the first onboard routing node, it performs the congestion assistance operation on the first onboard routing node. For example, after the second onboard routing node receives the congestion occurrence notification sent by the first onboard routing node, if the second onboard routing node receives the first data to be sent to the first onboard routing node, the second onboard routing node caches the first data and temporarily does not send the first data to the first onboard routing node.

[0067] The second satellite-borne routing node can cache the first data according to a certain strategy. For example, the second satellite-borne routing node can introduce a special preset cache area during the route selection process, and cache the first data to the preset cache area during route selection until the preset cache area overflows. Among them, 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 initialization configuration and modification. For another example, the second satellite-borne routing node can cache the first data within a preset time according to its own strategy or related instructions, and stop caching the first data after the preset time ends.

[0068] The second satellite-borne routing node can also select which data to cache according to a certain strategy, and implement fine-grained service flow control according to the information at the IP routing level. For example, the second satellite-borne routing node can cache all data to be sent to the first satellite-borne routing node, or cache data whose destination address is a preset address in the data to be sent to the first satellite-borne routing node (i.e., the first data), or cache data whose next hop address indicates a border gateway connected to the first satellite-borne routing node in the data to be sent to the first satellite-borne routing node (i.e., the first data), or cache data whose IPv6 address list in the data to be sent to the first satellite-borne routing node (i.e., the first data) contains information about the first satellite-borne routing node or information about a border gateway connected to the first satellite-borne routing node.

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

[0070] 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.

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

[0072] The second onboard routing node may terminate the congestion assistance operation according to its own strategy or the instruction of 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.

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

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

[0075] The second onboard routing node sends the first data to the first onboard routing node after the congestion assistance operation ends. 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.

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

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

[0078] In some embodiments, the first satellite-borne routing node may further include a first parameter in the congestion status notification, and the second satellite-borne routing node determines whether to forward the congestion status notification to the third satellite-borne routing node according to the indication of the first parameter. In this embodiment, participating in congestion assistance includes performing congestion assistance operations and / or forwarding congestion status notifications. The operation of the third satellite-borne routing node can refer to the second satellite-borne routing node, and will not be described in detail here.

[0079] 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, the satellite routing node S-Router33 is used as the first satellite routing node, and the satellite routing node S-Router23, the satellite routing node S-Router32 and the satellite routing node S-Router43 are satellite routing nodes with a distance of 1 hop from the satellite routing node S-Router33, and the second satellite routing node can be selected from these satellite routing nodes. The satellite routing node S-Router13, the satellite routing node S-Router22, the satellite routing node S-Router31, the satellite routing node S-Router42 and the satellite routing node S-Router53 are satellite routing nodes with a distance of 2 hops from the satellite routing node S-Router33, and the third satellite routing node can be selected from these satellite routing nodes.

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

[0081] When the feeder link between the satellite routing node S-Router3 and the gateway is congested, a congestion notification is issued to the satellite routing nodes within the surrounding N-hop range to form an assisting cluster of the satellite routing node S-Router3. When the congestion state of the feeder link is relieved, a congestion relief notification is issued to the satellite routing nodes within the surrounding N-hop range, and the surrounding satellite routing nodes stop assisting the satellite routing node S-Router3 in congestion. The surrounding satellite routing nodes send data to the satellite routing node S-Router3 normally. According to the link status of the satellite routing components near the feeder link, the congestion backpressure and cache mechanism are designed at the routing node cluster level to form mutual assistance and coordination within a certain range. There is no need to enhance the capacity of a single node, but to make full use of the idle capacity of the surrounding nodes to form a short-term, small-scale assisting cluster, realizing efficient resource utilization.

[0082] In some embodiments, the satellite routing node S-Router3 may immediately send a congestion occurrence notification when it detects that the feeder link is congested, and then periodically send congestion occurrence notifications until the feeder link congestion state is relieved. The satellite 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 a congestion relief notification 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 is met, or after receiving a response from the notified satellite routing node. Among them, the notification sending period can support parameterized configuration and dynamic modification, and the notification sending period can follow the period of the existing protocol on the control plane (such as the period of BGP (Border Gateway Protocol) update message).

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

[0084] 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 state of the feed link according to the state of the sending port queue corresponding to the feed link on the routing component. Among them, the sending port queue state 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 or more status data exceeds the configured threshold, it can be considered that the feed link is congested; otherwise, as long as the above conditions are not met, the feed link congestion state is considered to be released. In some embodiments, in order to avoid frequent switching of the feed link congestion state caused by real-time changes in status data, a smoothing operation can be added, and the setting and / or release of the congestion state can be performed 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 support modification during operation.

[0085] After receiving the congestion occurrence notification, the satellite routing nodes S-Router2 and S-Router4 may send a congestion occurrence response to the satellite routing node S-Router3 to confirm receipt of the congestion occurrence notification, or may not send a congestion occurrence response to reduce signaling interaction and improve congestion handling efficiency.

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

[0087] If it can participate, such as detecting that it is not connected to the feeder link, or the number of congestion assistances it participates in is less than the preset threshold, it performs congestion assistance operations and starts the cache function. It also sends a congestion occurrence notification to the adjacent onboard routing nodes S-Router1 and S-Router6. Furthermore, before sending, the corresponding parameters in the congestion occurrence notification can be updated, such as updating the parameter N and / or the preset time t.

[0088] In some embodiments, the satellite routing nodes S-Router1 and S-Router6 can determine which data needs to be cached according to certain policies. This embodiment implements fine-grained service flow control based on information at the IP routing level, which is more accurate than traditional congestion control based on port and queue levels. Examples are as follows:

[0089] (1) Port-based coarse-grained caching strategy

[0090] All data sent to the satellite routing node S-Router3 is cached uniformly. Although this strategy is relatively simple and direct in implementation, it can effectively capture all data that may be affected by congestion, so as to respond quickly when congestion occurs and improve the overall network throughput and stability.

[0091] (2) Fine-grained caching strategy based on IP address

[0092] (2.a) Filter the data based on its destination IP address, such as data whose cached destination IP address points to a specific terminal or service node in the ground bearer network and is to be sent to the satellite routing node S-Router3 and landed through a congested feeder link.

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

[0094] (3) Cache strategy based on SRV6 SID List (i.e. IPv6 address list)

[0095] If the IP message is transmitted using SRV6, the information in the SRv6 SID List can be used as the basis for caching decisions. When the SID List contains the information of the satellite routing node S-Router3 or the border gateway IP connected to the satellite routing node S-Router3 during route selection, it is determined that the message needs to be cached.

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

[0097] When the onboard routing node S-Router3 detects that the feeder link congestion is released, the feeder link congestion release notification preparation is completed, and then the congestion release notification is sent, such as Figure 5 As shown. The sending of congestion relief notification can refer to the sending of congestion occurrence notification, which will not be described in detail here. The satellite routing node that receives the congestion relief notification ends the congestion assistance operation, turns off the cache function, and sends data to the satellite routing node S-Router3 normally. The satellite routing node S-Router3 then forwards the data to the signal gateway to implement the data landing.

[0098] The embodiment of the present application also provides a chip system, which includes: a processing unit and a communication unit, wherein 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, etc. The processing unit may execute computer instructions, such as at least one processor being configured to execute instructions stored in at least one memory of a communication device alone or together, so that the communication device executes the method described in the above embodiment.

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

[0100] In some embodiments, the storage unit is a storage unit in the chip, such as a register, a cache, etc. The storage unit can also be a storage unit located outside the chip in the terminal, such as a ROM or other types of static storage devices that can store static information and instructions, RAM, etc. Among them, the processor mentioned in any of the above can be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the above-mentioned satellite network congestion processing method. The processing unit and the storage unit can be decoupled and respectively set on different physical devices, and connected by wired or wireless means to realize the respective functions of the processing unit and the storage unit, so as to support the chip system to realize the various functions in the above-mentioned embodiments. Alternatively, the processing unit and the memory can also be coupled on the same device.

[0101] Figure 6 6 is a schematic diagram of the structure of a communication device provided in 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 .

[0102] 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 may represent any interface necessary for communicating with other network elements.

[0103] Processor 610 may be of any type suitable for the local technology network, and may include, as non-limiting examples, 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 a main processor.

[0104] The 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 disk, compact disk (CD), digital video disk (DVD), 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 during the duration of a power outage.

[0105] The computer program 630 includes computer executable instructions that are executed by the associated processor 610. The program 630 may be stored in the ROM 624. The processor 610 may perform any appropriate actions and processes by loading the program 630 into the RAM 622.

[0106] The embodiments of the present application can be implemented by 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 by hardware or by a combination of software and hardware.

[0107] In some embodiments, the program 630 may be tangibly contained in a computer-readable medium, which may be contained in the communication device 600 (e.g., memory 620) or other storage device accessible to the communication device 600. The communication device 600 may load the program 630 from the computer-readable medium to the 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. The computer-readable medium has the program 630 stored thereon.

[0108] Generally, 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 performed 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 hardware or controllers or other computing devices, or some combination thereof.

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

[0110] The program code for executing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing equipment so that when the program code is executed by the processor or controller, the function / operation specified in the flow chart and / or the block diagram is realized. The program code can be executed completely on the machine as an independent software package, partially on the machine, partially on the machine, partially on a remote machine, partially on a remote machine, or all on a remote machine or server.

[0111] In the context of this application, computer program codes or related data may be carried by any appropriate 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.

[0112] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is 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 conductors, 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), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0113] In addition, although the operations are described in a specific order, this should not be construed as requiring to perform these operations in the specific order or sequence shown, or to perform all the operations shown, to obtain the desired result. In some cases, multitasking 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 of the features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0114] 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. Instead, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0115] It should be fully 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 case that a first feeder link connected to a first onboard routing node is congested, the first onboard routing node sends a congestion status notification to a second onboard routing node, the congestion status notification includes a congestion occurrence notification, the congestion occurrence notification is used to instruct the second onboard routing node to perform a congestion assistance operation, and after ending the congestion assistance operation, send first data to the first onboard routing node, the congestion assistance operation includes suspending the sending of the first data and caching the first data; The congestion status notification includes a first parameter, and the first parameter is used to indicate whether the second onboard routing node sends a congestion status notification to the third onboard routing node; the first parameter is a natural number N, used to indicate that the congestion status notification is sent to the onboard routing nodes within an initial N hop range from the first onboard routing node; 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.

2. The method according to claim 1, 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.

3. The method according to any one of claims 1 to 2, 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.

4. The method according to claim 3, 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.

5. The method according to any one of claims 1 to 2, 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.

6. The method according to any one of claims 1 to 2, 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.

7. The method according to any one of claims 1 to 2, 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.

8. 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 the congestion assistance operation is finished, the second onboard routing node sends the first data to the first onboard routing node; 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; The first parameter is a natural number N, which is used to indicate that a congestion status notification is sent to a satellite routing node within an initial N hops from the first satellite routing node, and the initial value of N is greater than or equal to 1. 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.

9. The method according to claim 8, 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.

10. The method according to claim 9, 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.

11. The method according to claim 8, 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.

12. The method according to claim 8, 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.

13. The method according to claim 8, 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.

14. The method according to claim 8, 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.

15. The method according to claim 8, 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.

16. 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-15.

17. 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, enable the communication device to perform a method according to any one of claims 1 to 15.

18. A chip system, characterized in that: The device comprises at least one processor, wherein the at least one processor is configured to execute, alone or together, instructions stored in at least one memory of the communication device, so that the communication device executes the method according to any one of claims 1 to 15.

19. 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 the method according to any one of claims 1 to 15.

Images