Satellite network non-time-sensitive data delay forwarding method based on traffic prediction
By predicting the idle location of satellite nodes and delaying the forwarding of non-time-sensitive data packets, the problem of low utilization of satellite network links is solved, achieving efficient resource utilization and reliable data transmission.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- BEIJING UNIV OF TECH
- Filing Date
- 2024-01-10
- Publication Date
- 2026-06-19
AI Technical Summary
The low utilization rate of satellite network links leads to resource waste, and the existing non-time-sensitive service routing scheme increases the number of intermediate nodes that data packets pass through and the risk of loss.
The non-time-sensitive data delay forwarding method based on traffic prediction predicts the idle state location of satellite nodes, delays the forwarding of non-time-sensitive data packets, reduces the number of intermediate nodes, and utilizes idle satellite links.
It improved the throughput of satellite networks, reduced the risk of data loss and congestion, and optimized resource utilization.
Smart Images

Figure CN117856867B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of space communication network technology, and specifically to a non-time-sensitive data delay forwarding method for satellite networks based on traffic prediction. Background Technology
[0002] With the widespread application of high-speed mobile internet and the rapid development of space technology, satellite networks have become an important component of global coverage. Satellite networks can provide highly reliable communication services in areas where traditional terrestrial networks cannot reach. Through satellite communication, people can communicate in remote areas, oceans, mountains, and sparsely populated regions, thus breaking geographical limitations. Furthermore, the communication quality and reliability of satellite networks have been significantly improved; advancements in satellite communication technology have resulted in faster data transmission speeds and lower latency.
[0003] The convergence of satellite and terrestrial networks is a future trend in mobile communication systems. While satellite nodes and links in a satellite constellation are evenly distributed, uneven distribution across the Earth's surface (ocean and land), population and regional distribution, and differences in economic development levels lead to significant variations in service demands between satellite and terrestrial nodes. This results in uneven distribution of satellite network traffic, with some links congested and others idle. Given the limited bandwidth of satellite networks, this situation represents a significant waste. Utilizing idle links can improve satellite network throughput without increasing physical investment. In a converged satellite-terrestrial network environment, there are diverse service types, varying service traffic characteristics, and significant differences in service quality requirements. Some non-time-sensitive services, such as backup services, can tolerate a certain degree of transmission delay. Therefore, designing different routing schemes for different types of services and for data transmission with varying needs can better utilize network resources and promote the development of space networks.
[0004] In the field of network communication, based on the requirements for data transmission timeliness, services can be divided into two main categories: real-time and non-real-time. Real-time services refer to service types with high requirements for data transmission timeliness. These services typically require rapid and timely data delivery to ensure that real-time and immediacy needs are met; examples include real-time voice communication, real-time video communication, and real-time data transmission. Non-real-time services, on the other hand, refer to service types with relatively low requirements for data transmission timeliness. Data transmission for these services can occur over a longer period and does not require real-time guarantees; examples include file transfer and email communication.
[0005] For non-time-sensitive services, the current mature routing scheme is to bypass busy or congested nodes. However, busy or congested satellites may become available in the next moment, and detouring inevitably increases the number of intermediate nodes that data packets pass through, leading to a greater risk of data loss and increasing the complexity and uncertainty of routing. Satellite networks have strong periodicity, which can provide good predictability for routing. Based on this characteristic, this invention designs a delay-based forwarding routing scheme based on traffic prediction for non-time-sensitive services. Summary of the Invention
[0006] To address the problem of low utilization of satellite network links and resource waste in existing technologies, this invention provides a non-time-sensitive data delay forwarding method for satellite networks based on traffic prediction. By predicting traffic data, it utilizes idle satellite links to forward data packets, thereby improving the utilization rate of idle satellite link resources. At the same time, it reduces the number of intermediate nodes that data packets pass through by delay forwarding, thus reducing the risk of data loss and congestion.
[0007] This invention discloses a method for delayed forwarding of non-time-sensitive data in satellite networks based on traffic prediction. The routing and forwarding method of this invention is based on satellite geographic routing protocols, achieving delayed forwarding of non-time-sensitive data between source and destination satellite nodes, including:
[0008] The satellite nodes involved in the data delay forwarding predict one or more idle positions in orbit with low data traffic for the current satellite node in one cycle based on their own traffic data from the most recent historical operating cycle.
[0009] The source satellite node receives the data packet and determines whether the data packet is a non-time-sensitive data packet;
[0010] If it is a non-time-sensitive data packet, the direction of the data packet transmitted between orbits is determined based on the longitude information of the source satellite node and the longitude information of the destination geographical location contained in the non-time-sensitive data packet.
[0011] The satellite node that receives the data packet carries the non-time-sensitive data packet to its first idle position and forwards the non-time-sensitive data packet to the next-hop neighbor satellite node in the adjacent orbit according to the determined direction of inter-orbit data packet transmission. The next-hop neighbor satellite node continues to carry the non-time-sensitive data packet to its first idle position and then forwards it until it reaches the destination satellite node.
[0012] As a further improvement of the present invention, the satellite nodes involved in the data delay forwarding predict one or more idle positions in orbit with low data traffic for the current satellite node during one cycle of operation, based on their own traffic data from the most recent historical operating cycle; including:
[0013] The current satellite node collects traffic data from its most recent historical operating cycles and predicts traffic data for the next cycle based on the traffic data from these historical operating cycles.
[0014] Select one or more time nodes with the lowest traffic data from the traffic data of the next cycle; based on the satellite node's corresponding geographical location at different times within a cycle, obtain one or more locations as the current idle state location of the satellite.
[0015] As a further improvement of the present invention, one or more locations below a preset traffic threshold are selected as the current idle state locations of the satellite.
[0016] As a further improvement of the present invention, the source satellite node receives data packets and determines whether the data packets are non-time-sensitive data packets; including:
[0017] The packet header uses different Traffic Class fields from IPv6 to distinguish the service type of the packet, which includes time-sensitive services and non-time-sensitive services;
[0018] The source satellite node receives data packets, identifies the Traffic Class field in the data packet header, and determines whether the data packet is a time-sensitive data packet or a non-time-sensitive data packet based on the identification result of the Traffic Class field.
[0019] As a further improvement to the present invention, it also includes:
[0020] If the data packet is determined to be time-sensitive, it will be forwarded according to the normal routing policy.
[0021] As a further improvement of the present invention, the method of determining the direction of inter-orbit data transmission based on the longitude information of the source satellite node and the longitude information of the destination geographical location contained in the non-time-sensitive data packet includes:
[0022] The difference between the longitude information of the destination geographic location contained in the non-time-sensitive data packet and the longitude information of the source satellite node is calculated.
[0023] The direction of data packet transmission between the next hop orbits is determined by the sign of the difference. If the difference is positive, it means that the destination satellite node is located to the east of the current satellite, and the east direction is selected as the direction of data packet transmission between orbits. If the difference is negative, it means that the destination satellite node is located to the west of the current satellite, and the west direction is selected as the direction of data packet transmission between orbits.
[0024] Compared with the prior art, the beneficial effects of the present invention are as follows:
[0025] The satellite node of this invention first predicts which locations in its orbit will have lower data traffic during a given cycle based on its most recent historical traffic data. When the satellite node receives a data packet with a non-time-sensitive route, it does not forward the packet directly. Instead, it holds the packet until it reaches the first predicted location with lower data traffic and then forwards it to the next-hop satellite node in the adjacent orbit according to the selected route, thus completing the data packet transmission. In this way, while meeting the requirements for non-time-sensitive data transmission, the utilization rate of idle satellite node links is improved, thereby increasing the throughput of the entire network. Attached Figure Description
[0026] Figure 1 This is a flowchart of the non-time-sensitive data delay forwarding method for satellite networks based on traffic prediction disclosed in this invention;
[0027] Figure 2 This is a diagram showing the communication data traffic of a satellite operating for one cycle as disclosed in this invention;
[0028] Figure 3 This is a schematic diagram of satellite forwarding data packets in an idle state as disclosed in this invention. Detailed Implementation
[0029] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0030] The present invention will now be described in further detail with reference to the accompanying drawings:
[0031] like Figure 1 As shown, this invention provides a method for delayed forwarding of non-time-sensitive data in satellite networks based on traffic prediction, achieving delayed forwarding of non-time-sensitive data between source and destination satellite nodes; including:
[0032] Step 1: The satellite nodes involved in the data delay forwarding predict one or more idle positions in orbit with low data traffic for the current satellite node in one cycle based on their own traffic data from the most recent historical operating cycle.
[0033] Specifically, it includes:
[0034] The current satellite node collects traffic data from its most recent historical operating cycles and predicts the traffic data for the next cycle based on the traffic data from the multiple historical operating cycles; it selects one or more time nodes with the lowest traffic data from the traffic data of the next cycle; based on the satellite node's different geographical locations at different times within a cycle, it obtains one or more locations as the current idle state location of the satellite.
[0035] One embodiment is as follows:
[0036] Each low-Earth orbit (LEO) satellite in a satellite network has four interfaces, establishing inter-satellite links with two neighboring satellites within its orbit and two between orbits, for a total of four satellites. The sum of the number of data packets transmitted through these four interfaces over a period of time represents the traffic data for that period. After one cycle of satellite operation, the communication traffic at different locations is determined within that cycle. The traffic data for a historical operating cycle is as follows: Figure 2 As shown, Figure 2 The diagram shows traffic data for a portion of historical operating cycles at 1-minute intervals. Using traffic data from the satellite's most recent five historical operating cycles (one orbit around the Earth constitutes one operating cycle) as raw data, each cycle contains minute-by-minute records, the time when satellite data traffic is low is predicted. That is, based on the traffic data for the first minute of the five historical operating cycles, the traffic data for the first minute of the next cycle is predicted; similarly, the traffic data for the second minute, third minute, and so on, in the next cycle are predicted. Since the satellite's orbital parameters are fixed, it completes one revolution in its orbit within a cycle. The satellite's position in orbit can be determined based on the time it spends within that cycle. Therefore, by predicting the time when satellite data traffic is low, the corresponding position in orbit during this period can be determined. When the satellite reaches these predicted positions along its operating direction, it is considered to be in a relatively idle state; that is, at these positions, the satellite may encounter less communication traffic, providing a relatively ideal time window for the transmission of non-time-sensitive service data packets. Furthermore, one prediction method involves selecting one or more positions below a preset traffic threshold as the current idle positions of the satellite.
[0037] Step 2: The source satellite node receives the data packet and determines whether the data packet is a non-time-sensitive data packet;
[0038] Specifically, it includes:
[0039] The packet header uses different Traffic Class fields in IPv6 to distinguish the service type of the packet. The service type includes time-sensitive services and non-time-sensitive services. The source satellite node receives the packet, identifies the Traffic Class field in the packet header, and determines whether the packet is a time-sensitive packet or a non-time-sensitive packet based on the identification result of the Traffic Class field. If it is determined to be a time-sensitive packet, it is forwarded according to the normal routing policy; if it is determined to be a non-time-sensitive packet, it proceeds to step 3.
[0040] One embodiment is as follows:
[0041] The IPv6 Traffic Class field (8 bits) is used to identify service types. This field is similar to the IPv4 Type of Service field, distinguishing an IPv6 packet by its Distributed Service Code Point (DSCP) to indicate how the packet should be processed. This invention assigns different Traffic Class values to time-sensitive and non-time-sensitive services to identify their types. For time-sensitive services, a specific Traffic Class value of 00000001 is assigned, and the Traffic Class field is set to 00000001 when generating time-sensitive service packets. For non-time-sensitive services, a specific Traffic Class value of 00000010 is assigned, and the Traffic Class field is set to 00000010 when generating non-time-sensitive service packets. When a satellite receives a packet, it first analyzes the Traffic Class field in the packet header. When this field value is 00000001, it indicates that the packet is a time-sensitive service packet; when the field value is 00000010, it indicates that the packet is a non-time-sensitive service packet.
[0042] Step 3: If it is a non-time-sensitive data packet, determine the direction of the data packet transmission between orbits based on the longitude information of the source satellite node and the longitude information of the destination geographical location contained in the non-time-sensitive data packet.
[0043] Specifically, it includes:
[0044] The longitude information of the destination geographical location contained in the non-time-sensitive data packet is compared with the longitude information of the source satellite node. The direction of the next-hop inter-orbit data packet transmission is determined according to the sign of the difference. If the difference is positive, it means that the destination satellite node is located to the east of the current satellite, and the east direction is selected as the direction of inter-orbit data packet transmission. If the difference is negative, it means that the destination satellite node is located to the west of the current satellite, and the west direction is selected as the direction of inter-orbit data packet transmission.
[0045] One embodiment is as follows:
[0046] The routing and forwarding mechanism of this invention is based on a satellite-based geographic routing protocol. Therefore, an extended address location information header is added to IPv6 to store the address information of the destination node. The fields and their meanings are as follows:
[0047] Ext Length: The length of the extension header.
[0048] Option Type: A custom option type used to identify the option that stores the latitude and longitude information of the destination address. The value is 0xAA.
[0049] Option Length: The length of the option field, excluding the Option Type and Option Length fields themselves, with a value of 8 bytes.
[0050] Latitude: Used to store the latitude information of the destination address, represented by a 32-bit unsigned integer. For a destination satellite with a latitude of 40.7128°N, it can be converted to the integer 40712800.
[0051] Longitude: Used to store the longitude information of the destination address, represented by a 32-bit unsigned integer. For a destination satellite with a longitude of 74.0060°W, it can be converted to the integer 74006000.
[0052] Obtain the longitude (LTA) of the destination node from the Longitude field in the extended header. T The destination longitude LAT T LAT of the current satellite S Perform difference calculation:
[0053] ΔLON=LON T -LON S
[0054] If ΔLON>0, the destination node is located to the east of the current satellite, and the eastward direction is selected as the inter-orbit routing direction;
[0055] If ΔLON<0, the destination node is located to the west of the current satellite, and the westward direction is selected as the inter-orbit routing direction.
[0056] For example: Based on the value of the Longitude field in the extended header, such as 74006000, the longitude of the destination satellite is obtained, such as 74.0060°W. The longitude of the destination node is then compared with the longitude of the current satellite, such as 116.0750°E, and the difference is calculated (east longitude is positive, west longitude is negative). For example, the longitude difference is -74.0060-116.0750=-190.0810. The difference is negative, indicating that the destination satellite is west of the current satellite, and the westward direction is selected as the inter-orbit routing direction.
[0057] Step 4: The satellite node that receives the data packet carries the non-time-sensitive data packet to its first idle position and forwards it to the next-hop neighbor satellite node in the adjacent orbit according to the determined direction of inter-orbit data packet transmission. The next-hop neighbor satellite node continues to carry the non-time-sensitive data packet to its first idle position and then forwards it until it reaches the destination satellite node. Figure 3 As shown.
[0058] The advantages of this invention are:
[0059] This invention uses satellites to predict idle locations based on their historical traffic data and postpones the forwarding of non-time-sensitive data to those locations. This effectively utilizes satellite link resources and improves resource utilization. Delayed forwarding reduces the number of intermediate nodes that data packets pass through compared to schemes that detour to use idle links. This reduces the computational and network resources consumed by intermediate nodes when processing data packets, lowers transmission risks and potential errors, reduces the complexity of routing protocols, and decreases the occurrence of loops.
[0060] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A method for delayed forwarding of non-time-sensitive data in satellite networks based on traffic prediction, characterized in that, delayed forwarding of non-time-sensitive data is achieved between source satellite nodes and destination satellite nodes, include: The satellite nodes involved in the data delay forwarding predict one or more idle positions in orbit with low data traffic for the current satellite node in one cycle based on their own traffic data from the most recent historical operating cycle. The source satellite node receives the data packet and determines whether the data packet is a non-time-sensitive data packet; If it is a non-time-sensitive data packet, the direction of the data packet transmitted between orbits is determined based on the longitude information of the source satellite node and the longitude information of the destination geographical location contained in the non-time-sensitive data packet. The satellite node that receives the data packet carries the non-time-sensitive data packet to its first idle position and forwards the non-time-sensitive data packet to the next-hop neighbor satellite node in the adjacent orbit according to the determined direction of inter-orbit data packet transmission. The next-hop neighboring satellite node continues to carry non-time-sensitive data packets to its first idle position and then forwards them until they reach the destination satellite node.
2. The satellite network non-time-sensitive data delay forwarding method based on traffic prediction as described in claim 1, characterized in that, The data delay forwarding involves satellite nodes that, based on their recent historical operational cycle traffic data, predict one or more idle positions in orbit where data traffic is low for the current satellite node during one operational cycle; including: The current satellite node collects traffic data from its most recent historical operating cycles and predicts traffic data for the next cycle based on the traffic data from these historical operating cycles. Select one or more time nodes with the lowest traffic data from the traffic data of the next cycle; based on the satellite node's corresponding geographical location at different times within a cycle, obtain one or more locations as the current idle state location of the satellite.
3. The method of claim 1, wherein the satellite network non-time-critical data delay-and-forwarding method based on traffic prediction is characterized by, The source satellite node receives data packets and determines whether the data packets are non-time-sensitive data packets; including: The packet header uses different Traffic Class fields from IPv6 to distinguish the service type of the packet, which includes time-sensitive services and non-time-sensitive services; The source satellite node receives data packets, identifies the Traffic Class field in the data packet header, and determines whether the data packet is a time-sensitive data packet or a non-time-sensitive data packet based on the identification result of the Traffic Class field.
4. The method of claim 3, wherein the satellite network non-time-critical data delay-and-forwarding method based on traffic prediction is characterized by, Also includes: If the data packet is determined to be time-sensitive, it will be forwarded according to the normal routing policy.
5. The method of claim 1, wherein the satellite network non-time-critical data delay-and-forwarding method based on traffic prediction is characterized by, The direction of the inter-orbit data packet transmission is determined based on the longitude information of the source satellite node and the longitude information of the destination geographical location contained in the non-time-sensitive data packet; including: The difference between the longitude information of the destination geographic location contained in the non-time-sensitive data packet and the longitude information of the source satellite node is calculated. The direction of data packet transmission between the next hop orbits is determined by the sign of the difference. If the difference is positive, it means that the destination satellite node is located to the east of the current satellite, and the east direction is selected as the direction of data packet transmission between orbits. If the difference is negative, it means that the destination satellite node is located to the west of the current satellite, and the west direction is selected as the direction of data packet transmission between orbits.