Data communication method and system, and electronic device

Abstract

The present invention relates to the field of communications, and provides a data communication method and system and an electronic device. The method comprises: by means of a pre-constructed satellite data warehouse, receiving data name information uploaded by a producer, the satellite data warehouse comprising at least three geosynchronous orbit satellites and a plurality of low earth orbit satellites, and the data name information representing the position of the moved producer; and, on the basis of the data name information, updating data in the satellite data warehouse. The present invention solves the defect in NDN network architecture that after producers have moved, it is difficult for consumers to determine new positions of the producers and thus sent packets of interest will reach old positions of the producers, such that the packets are lost, greatly affecting the accuracy and efficiency of data transmission. The solution of the present application can buffer data packets of moved producers in pre-constructed satellite data warehouses, thereby effectively avoiding effects on network performance caused by movement of the producers.

Description

Data communication methods and systems, electronic devices Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a data communication method and system, and an electronic device. Background Technology

[0002] With the rapid development of data communication technology and its hardware technology, the connectivity and low storage cost provided by the Internet have enabled a large amount of new content to be accessed. The amount of data in the network is growing at an astonishing rate, which puts forward higher requirements for the bandwidth and latency of network architecture for content transmission. Named data networking (NDN) is one of the future network architectures that meets these higher requirements.

[0003] In the NDN network architecture, a producer refers to a node or device that can provide data or content to meet the needs of consumers. It is important to note that in practical applications, producers are often mobile. When a producer moves, it becomes difficult for consumers to locate the producer's new location, causing interest packets to arrive at the producer's old location, resulting in packet loss. This will greatly affect the accuracy and efficiency of data transmission.

[0004] Summary of the Invention

[0005] This invention provides a data communication method, system, and electronic device to address the problem in NDN network architecture where, after a producer moves, consumers struggle to locate the producer's new location, causing sent interest packets to arrive at the producer's old location, resulting in packet loss and significantly impacting the accuracy and efficiency of data transmission. The solution in this application can cache the producer's data based on a pre-built satellite data warehouse, thus effectively shielding the network performance from the impact of producer movement.

[0006] This invention provides a data communication method, comprising:

[0007] The system receives data name information uploaded by producers through a pre-built satellite data warehouse, which includes at least three geostationary orbit satellites and several low orbit satellites. The data name information represents the data generated by the producers.

[0008] Update the data in the satellite data warehouse based on the data name information.

[0009] The data communication method provided by the present invention further includes:

[0010] Once the satellite data warehouse receives a request packet from a consumer, it forwards the request packet to the producer.

[0011] The satellite data warehouse receives data packets uploaded by producers based on request packets and forwards the data packets to consumers.

[0012] According to the data communication method provided by the present invention, when a satellite data warehouse receives a request packet from a consumer, it forwards the request packet to a producer, including:

[0013] Receive consumer request packets via low-Earth orbit satellites;

[0014] The request packet is marked based on the data name information;

[0015] Based on the tags, the request packets are routed to the producer.

[0016] According to the data communication method provided by the present invention, the satellite data warehouse receives data name information uploaded by the producer through a target satellite, which is one of several low-orbit satellites;

[0017] Based on tags, the request packet is routed to the producer, including:

[0018] Based on preset routing rules, the request packet is routed to the target satellite, and the address of the target satellite corresponds to the tag;

[0019] The target satellite forwards the request packet to the producer based on the producer's data name information.

[0020] The data communication method provided by the present invention further includes:

[0021] When the satellite data warehouse receives a request packet from a consumer, if it determines that the satellite data warehouse has cached the data packet corresponding to the request packet, it will forward the cached data packet to the consumer.

[0022] According to the data communication method provided by the present invention, the satellite data warehouse caches data packets using the following method:

[0023] Determine the number of times the data packet was requested;

[0024] Determine the number of hops for each low-Earth orbit satellite each time a data packet is requested;

[0025] The probability of each low-Earth orbit satellite caching data packets is calculated based on the number of times the data packets are requested and the number of hops.

[0026] Each low-Earth orbit satellite caches data packets based on a cache probability.

[0027] According to the data communication method provided by the present invention, a routing table is set up in the satellite data warehouse. The routing table includes a satellite-to-ground communication routing table and an inter-satellite communication routing table. The low-Earth orbit satellites are distributed in several orbits. The method for constructing the inter-satellite communication routing table includes:

[0028] For each low-Earth orbit satellite, send the first information to other low-Earth orbit satellites in the same orbit. The first information represents the position of the low-Earth orbit satellite.

[0029] When a low-Earth orbit satellite in the same orbit receives the first information, if the low-Earth orbit satellite in the same orbit does not have an inter-satellite communication routing table corresponding to the low-Earth orbit satellite, then an inter-satellite communication routing table is created and stored in the low-Earth orbit satellite in the same orbit; if it has already been stored, then the inter-satellite communication routing table is updated based on the first information.

[0030] For each low-Earth orbit satellite, at set intervals, a second message is sent to low-Earth orbit satellites in different orbits. The second message represents the position of the low-Earth orbit satellite.

[0031] When low-Earth orbit satellites in different orbits receive the second information, if the inter-satellite communication routing table corresponding to the low-Earth orbit satellite is not stored in the low-Earth orbit satellites in different orbits, then the inter-satellite communication routing table is created and stored in the low-Earth orbit satellites in different orbits; if it has been stored, then the inter-satellite communication routing table is updated based on the second information.

[0032] According to the data communication method provided by the present invention, updating data in a satellite data warehouse based on data name information includes:

[0033] Update the target satellite's data based on the data name information;

[0034] Update the data of all low-Earth orbit satellites and geostationary orbit satellites in the satellite data warehouse.

[0035] The present invention also provides a data communication system, comprising:

[0036] The information receiving module is used to receive data name information uploaded by producers through a pre-built satellite data warehouse, which includes at least three geostationary orbit satellites and several low orbit satellites. The data name information represents the data generated by the producers.

[0037] The information update module is used to update the data in the satellite data warehouse based on the data name information.

[0038] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement any of the data communication methods described above.

[0039] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements any of the data communication methods described above.

[0040] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements any of the data communication methods described above.

[0041] In the data communication method provided by this invention, a satellite data warehouse can be pre-built. This satellite data warehouse can receive data name information uploaded by producers. Since the data name information can characterize the data generated by the producers, the satellite data warehouse can obtain the data produced by the producers even when the producers are in motion. In this way, efficient communication between producers and consumers is realized, and the accuracy and efficiency of data transmission are improved. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0043] Figure 1 is a flowchart illustrating one of the data communication methods provided in an embodiment of the present invention;

[0044] Figure 2 is one of the structural schematic diagrams of the satellite data warehouse provided in an embodiment of the present invention;

[0045] Figure 3 is a second schematic diagram of the structure of the satellite data warehouse provided in an embodiment of the present invention;

[0046] Figure 4 is a schematic diagram of the routing table structure provided in an embodiment of the present invention;

[0047] Figure 5 is a second schematic flowchart of the data communication method provided in an embodiment of the present invention;

[0048] Figure 6 is a third schematic flowchart of the data communication method provided in an embodiment of the present invention;

[0049] Figure 7 is a fourth flowchart illustrating the data communication method provided in an embodiment of the present invention;

[0050] Figure 8 is a consumer delay diagram under different numbers of managers provided in an embodiment of the present invention;

[0051] Figure 9 is a signaling overhead diagram for different numbers of managers provided in the embodiments of the present invention;

[0052] Figure 10 is a delivery rate chart for different numbers of managers provided in the embodiments of the present invention;

[0053] Figure 11 shows the impact of different intranet caching strategies provided in the embodiments of the present invention on MsDD performance;

[0054] Figure 12 is a consumer delay diagram under different producer movement rates provided in an embodiment of the present invention;

[0055] Figure 13 is a delivery rate diagram under different producer movement rates provided in the embodiments of the present invention;

[0056] Figure 14 is a signaling overhead diagram under different producer movement rates provided in the embodiments of the present invention;

[0057] Figure 15 is a schematic diagram of the data communication system provided in an embodiment of the present invention;

[0058] Figure 16 is a schematic diagram of the physical structure of the electronic device provided in an embodiment of the present invention. Detailed Implementation

[0059] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this 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 this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0060] Figure 1 is a flowchart of one of the data communication methods provided in an embodiment of the present invention.

[0061] As shown in Figure 1, this embodiment provides a data communication method, including:

[0062] Step 101: Receive data name information uploaded by producers through a pre-built satellite data warehouse. The satellite data warehouse includes at least three geostationary orbit satellites and several low orbit satellites. The data name information represents the data generated by the producers.

[0063] Step 102: Update the data in the satellite data warehouse based on the data name information.

[0064] Figure 2 is one of the structural schematic diagrams of the satellite data warehouse provided in an embodiment of the present invention.

[0065] As shown in Figure 2, the satellite data warehouse provided in this embodiment consists of a Low Earth Orbit (LEO) satellite constellation and a Geosynchronous Earth Orbit (GEO) satellite constellation. The GEO satellite constellation consists of at least three GEO satellites evenly spaced above the equator, with their orbital planes coinciding with the equatorial plane. The LEO satellite constellation is a Walker constellation composed of m ordered polar orbit planes, with n ordered LEO satellites evenly distributed in each orbit. Therefore, the data warehouse consists of m×n+3 LEO satellites. Ground-based producers and consumers in the NDN architecture can communicate directly with the LEO layer satellites via hardware devices.

[0066] In practical applications, LEO satellites can be distributed in different orbits, and can be prefixed with / sat / OP. h / SP i The definition is as follows: / sat indicates that the node is a satellite node, and / OP... h For its orbit, / SP i Let h represent the orbit of the LEO satellite and i be its number in the current orbit. Therefore, the set of LEO satellite nodes satisfies S = {S h,i ,h=1,2,…,m,i=1,2,…n}.

[0067] Figure 3 is a second schematic diagram of the structure of the satellite data warehouse provided in an embodiment of the present invention.

[0068] In practice, as shown in Figure 3, LEO satellites include both administrators and non-administrators. For example, the number of administrators in each orbital plane is M, and they are spaced apart within the orbit. Each node is placed. Additionally, when the track OP... h A manager on the platform is S h,i When that happens, the adjacent orbit OP h+1 The manager is S h+1,i+1 Other orbits follow the same pattern. This arrangement ensures that the number of administrators at each latitude remains relatively consistent. Figure 3 illustrates the arrangement of LEO satellites when n=11, m=6, and M=4.

[0069] In implementation, a Data List (DL) table can be set up within the satellite data warehouse, where data name information can be stored. The DL table can have multiple entries. Preferably, each administrator can share a single, identical DL table with three GEO satellites. When the information in one administrator's DL table changes, an update is sent to the GEO satellite that overwrites it. The GEO satellite then sends this update to the other administrators, achieving a global update. A DL entry includes the data packet storage location (node ​​prefix) and the data packet name prefix.

[0070] In practice, data name information can also represent the location of the producer after it moves.

[0071] In the data communication method provided in this embodiment, a satellite data warehouse can be pre-built. This satellite data warehouse can receive data name information uploaded by producers. Since the data name information can represent the producer's address, the satellite data warehouse can obtain the data produced by the producer even when the producer is in motion. In this way, efficient communication between producers and consumers is realized, and the accuracy and efficiency of data transmission are improved.

[0072] In an exemplary embodiment, the data communication method further includes:

[0073] Once the satellite data warehouse receives a request packet from a consumer, it forwards the request packet to the producer.

[0074] The satellite data warehouse receives data packets uploaded by producers based on request packets and forwards the data packets to consumers.

[0075] In practical applications, satellite data warehouses receive data name information uploaded by producers and request packets from consumers via low-Earth orbit (LEO) satellites. However, the LEO satellite receiving the data name information uploaded by producers and the LEO satellite receiving the request packets from consumers may not be the same. In this case, it is necessary to forward the received request packets from consumers to the LEO satellite corresponding to the producer. During this process, the request packets can be forwarded through the DL table managed by the administrator. After the request packet is forwarded to the LEO satellite corresponding to the producer, the LEO satellite forwards the request packet to the producer based on the stored data name information. Then, it receives the data packets uploaded by the producer based on the request packets and forwards these data packets to the consumers who sent the request packets step by step.

[0076] In this embodiment, the consumer acts as the one requesting data packets from the producer. Given that the satellite data warehouse can accurately locate the producer's position through data name information, the consumer can obtain the required data packets accurately and in real time, thus improving the efficiency of data communication.

[0077] In an exemplary embodiment, after the satellite data warehouse receives a request packet from a consumer, it forwards the request packet to the producer, including:

[0078] Receive consumer request packets via low-Earth orbit satellites;

[0079] The request packet is marked based on the data name information;

[0080] Based on the tags, the request packets are routed to the producer.

[0081] In practical applications, during the forwarding of request packets to producers, since non-managers do not carry the Data Link Detail (DL), they need to obtain the prefix name of the LEO satellite corresponding to the producer from the DL carried by the manager. Therefore, non-manager LEO satellites need to first forward the interest packet to the nearest manager in the same orbit via the FIB entry. The data packet is sent by the consumer and carries the request packet. Then, the manager adds a forwarding hint to the interest packet, that is, marks the request packet. The forwarding hint is a locator carried in the interest packet, indicating "where" to forward the interest packet. Through the forwarding hint, the NDN core network can only announce the location in the form of a prefix, which is more scalable than announcing a data name prefix. Since a unique prefix name has been set for each satellite in the LEO layer when it is constructed, the prefix name of the target node can be used as a forwarding hint to route the interest packet in the implementation.

[0082] In this embodiment, by attaching a tag to the request packet, the request packet can be accurately forwarded to the producer.

[0083] In an exemplary embodiment, the satellite data warehouse receives data name information uploaded by the producer through a target satellite, which is one of several low-orbit satellites;

[0084] Based on tags, the request packet is routed to the producer, including:

[0085] Based on preset routing rules, the request packet is routed to the target satellite, and the address of the target satellite corresponds to the tag;

[0086] The target satellite forwards the request packet to the producer based on the producer's data name information.

[0087] In practical applications, the preset routing rules are as follows:

[0088] In an exemplary embodiment, the data communication method further includes:

[0089] When the satellite data warehouse receives a request packet from a consumer, if it determines that the satellite data warehouse has cached the data packet corresponding to the request packet, it will forward the cached data packet to the consumer.

[0090] In practical applications, consumers may repeatedly request data packets from the same producer, or different consumers may request the same data packets from the same producer. In these cases, the satellite data warehouse can cache the data packets uploaded by the producer. Thus, when it is confirmed that the request packets are requesting the same data packets, the pre-cached data packets can be directly forwarded from within the satellite data warehouse to the consumer that sent the request packet, without having to forward the request packet to the producer again. This can improve the efficiency of data communication.

[0091] In an exemplary embodiment, the satellite data warehouse caches data packets using the following method:

[0092] Determine the number of times the data packet was requested;

[0093] Determine the number of hops for each low-Earth orbit satellite each time a data packet is requested;

[0094] The probability of each low-Earth orbit satellite caching data packets is calculated based on the number of times the data packets are requested and the number of hops.

[0095] Each low-Earth orbit satellite caches data packets based on a cache probability.

[0096] In practical applications, the number of hops a producer's data packet takes can be represented by the number of hops a consumer's request packet is forwarded to the producer. In implementation, when the satellite data warehouse receives a consumer's request packet, a TLV element named ISLhop can be added to the interest packet. This element records the number of hops the interest packet takes after passing through a manager node when forwarding between different orbits. When the interest packet is forwarded within the same orbit, ISLhop = 0. Each time the request packet is forwarded to a new node, i.e., to a new low-Earth orbit satellite, that low-Earth orbit satellite records and updates the ISLhop of the interest packet received from the interface communicating with satellites in two different orbits.

[0097] When a data packet sent by a producer based on a request packet is forwarded between low-Earth orbit (LEO) satellites, since the producer's forwarding path is the same as the consumer's forwarding path, each LEO satellite traversed by the producer records a TLV element named ISLhop. Therefore, when a data packet sent by the producer is forwarded to each LEO satellite, the probability that the LEO satellite will cache the data packet can be calculated based on the number of hops recorded in the ISLhop and the number of times the data packet has been requested. Specifically, the probability can be calculated using the following formula:

[0098] Where P (h,i),DThe cache probability for each low-Earth orbit satellite. This represents the probability that a low-Earth orbit satellite buffers data packets when they are relayed through different orbits. P is the probability that a low-Earth orbit satellite buffers data packets when the data packets are relayed via the same orbit. D The cache probability is calculated based on the CCS (Cache in the Core Strategy) scheme, where ε is the descent weight, ε∈(0,1), and P is higher when ε is larger. h,i The greater the downward trend, the stronger the decline. ISLhop h,i The value of ISLhop for the corresponding low-Earth orbit satellite, hop max It is the maximum number of hops from a non-administrator low-Earth orbit satellite to an administrator low-Earth orbit satellite within the same orbit. h,i This is the number of hops between a low-Earth orbit satellite and the nearest manager in the same orbit.

[0099] In practical applications, hop max hop h,i and ISLhop h,i It can be calculated using the following formula:

[0100] in, For the current low-Earth orbit satellite, the interface f is recorded. a The passed-in ISLhop value, Recorded from the interface f for low-Earth orbit satellites b The passed-in ISLhop value, where f a f is an interface for communication between low-Earth orbit satellites and satellites in different orbits. b This is the interface for communication between LEO satellites and satellites in the same orbit. h represents the orbit where the LEO satellite is located, i is the LEO satellite's number in the current orbit, m represents the number of orbits in which the LEO satellite is distributed, M represents the number of administrators in each orbit, and j represents the administrator satellite's number in the current orbit.

[0101] In an exemplary embodiment, when a target satellite in the satellite data warehouse receives a data packet uploaded by a producer, the data packet can be cached in the target satellite, which is a low-orbit satellite that receives the data name information from the producer.

[0102] In practical applications, when the satellite data warehouse does not cache data packets, the consumer's request packet needs to be forwarded to the producer via the target satellite. In this embodiment, when the consumer requests a data packet from the producer for the first time, the target satellite can cache the data packet. In this way, when other consumers or the consumer requests a data packet from the producer again, the request packet can be directly obtained after being forwarded to the target satellite, without having to be forwarded to the producer again. This can also improve the efficiency of data communication.

[0103] In an exemplary embodiment, a routing table is set up in the satellite data warehouse. The routing table includes a satellite-to-ground communication routing table and an inter-satellite communication routing table. The low-Earth orbit satellites are distributed in several orbits. The method for constructing the inter-satellite communication routing table includes:

[0104] For each low-Earth orbit satellite, send the first information to other low-Earth orbit satellites in the same orbit. The first information represents the position of the low-Earth orbit satellite.

[0105] When a low-Earth orbit satellite in the same orbit receives the first information, if the low-Earth orbit satellite in the same orbit does not have an inter-satellite communication routing table corresponding to the low-Earth orbit satellite, then an inter-satellite communication routing table is created and stored in the low-Earth orbit satellite in the same orbit; if it has already been stored, then the inter-satellite communication routing table is updated based on the first information.

[0106] For each low-Earth orbit satellite, at set intervals, a second message is sent to low-Earth orbit satellites in different orbits. The second message represents the position of the low-Earth orbit satellite.

[0107] When low-Earth orbit satellites in different orbits receive the second information, if the inter-satellite communication routing table corresponding to the low-Earth orbit satellite is not stored in the low-Earth orbit satellites in different orbits, then the inter-satellite communication routing table is created and stored in the low-Earth orbit satellites in different orbits; if it has been stored, then the inter-satellite communication routing table is updated based on the second information.

[0108] In practical applications, the Forwarding Information Base (FIB) table is a key data structure in NDN networks used to determine how interest packets are forwarded through the network. The FIB itself is filled with routing protocols for name prefixes, and each prefix can have multiple interfaces, which is crucial for data communication. This embodiment involves communication between satellites and communication between satellites and ground producers or consumers. Therefore, the routing table can include a satellite-to-ground communication routing table and an inter-satellite communication routing table. The satellite-to-ground communication routing table can be represented using FIB. FIB entries on low-Earth orbit (LEO) satellites only include different interfaces in the downlink divided by frequency bands. The inter-satellite communication routing table can be represented using Satellite FIB. An SFIB entry includes the LEO satellite's prefix, interface, and administrator identifier. The administrator identifier indicates whether the LEO satellite is the administrator. Furthermore, in this embodiment, since the satellite data warehouse involves LEO satellites in different orbits, different routing rules are required when data packets communicate between different orbits and within the same orbit. Therefore, this embodiment constructs two different routing tables. The inter-satellite communication routing table within the same orbit is established as follows:

[0109] Step 1: For each low-Earth orbit satellite S h,i It sends a Pub-A message from each of its two relay interfaces that communicate with satellites in the same orbit. The Pub-A message includes the low-orbit satellite's own prefix information, relay hop count, and administrator identifier.

[0110] Step 2: Adjacent low-Earth orbit satellite nodes interface f a Received S h,i The Pub-A message is processed as follows after it is sent:

[0111] • If a node contains a prefix equal to / sat / OP h / SP i If the SFIB entry has fewer forwarding hops than Pub-A, then update that entry.

[0112] • If a node contains a prefix equal to / sat / OP h / SP i If the SFIB entry has a higher forwarding hop count, no adjustment will be made.

[0113] • If the node does not contain a prefix equal to / sat / OP h / SP i SFIB entries, satellite nodes Create this SFIB entry with the prefix equal to / sat / OP. h / SP iThe interface is equal to f a And record the administrator's identifier.

[0114] Because the order of satellites in the same orbit will not change, once the SFIB entries for satellites in the same orbit are constructed, the node does not need to send a Pub-A message again to create entries.

[0115] Inter-satellite communication routing tables for different orbits are established in the following way:

[0116] Step 1: S h,i At regular intervals τ, a Pub-B message is sent from each of its two relay interfaces communicating with satellites in different orbits. The specific value of τ is determined by the characteristics of different satellite constellations. The Pub-B message contains S... h,i Position (prefix).

[0117] Step 2: Satellite Node interface f b Received S h,i The following processing is performed after the Pub-B message is sent:

[0118] • If a node contains a prefix equal to / sat / OP h If the SFIB entries are consistent with the interface, no adjustments are needed.

[0119] • If a node contains a prefix equal to / sat / OP h If an SFIB entry exists but the interface is inconsistent, then update that entry.

[0120] • If the node does not contain a prefix equal to / sat / OP h SFIB entries, satellite nodes Create this SFIB entry with the prefix equal to / sat / OP. h The interface is equal to f b .

[0121] Figure 4 is a schematic diagram of the routing table structure provided in an embodiment of the present invention.

[0122] By following the steps above, an SFIB can be created for each LEO satellite node in MsDD. Each satellite node can then communicate with other satellites in the LEO layer through its own SFIB entries. Figure 4 illustrates the satellite S... 1,1 The state after SFIB is built.

[0123] Due to the characteristics of polar orbit satellite constellations, when a satellite passes the North and South Poles, its adjacent orbits will switch left and right. Therefore, it is necessary to dynamically adjust the SFIB entries for different orbits. Based on this, in this embodiment, when constructing the inter-satellite communication routing table for different orbits, it is necessary to update the routing table every once in a while.

[0124] In an exemplary embodiment, updating data in the satellite data warehouse based on data name information includes:

[0125] Update the target satellite's data based on the data name information;

[0126] Update the data of all low-Earth orbit satellites and geostationary orbit satellites in the satellite data warehouse.

[0127] [Corrected according to Rule 91 24.09.2024] In practical applications, after the target satellite receives the data name information from the producer, it can update the satellite-to-ground communication routing table inside the target satellite based on the data name information. After that, the target satellite can send update information to the geostationary orbit satellite. The geostationary orbit satellite can issue a global update command. Based on the command, the satellites in the satellite data warehouse update their respective DL forms.

[0128] Figure 5 is a second schematic flowchart of the data communication method provided in an embodiment of the present invention.

[0129] As shown in Figure 5, in the exemplary embodiment, to prevent data packet loss due to link switching at the Walker constellation cross-seam, this embodiment addresses this issue using the following method: When a satellite node wants to send an interest packet via the inter-satellite link of the cross-seam, the satellite node sends an A-interest packet (AuxiliaryInterest) to its neighboring satellite nodes in the same orbit. The A-interest packet differs from a regular interest packet in that its hop limit is 2. The sending process of the A-interest packet is as follows. The purpose of sending the A-interest packet is to reconstruct a reverse path for the data packet.

[0130] Figure 5 illustrates this process, showing that when a link switch occurs, S m,2 and S 1,3 The connection was re-established, and an S-shaped path was constructed. m,2 →S 1,3 →S 1,2 The reverse path.

[0131] Figure 6 is a flowchart of the data communication method provided in an embodiment of the present invention.

[0132] Figure 7 is a flowchart of the data communication method provided in the embodiment of the present invention.

[0133] The overall flow of the data communication method in this application is described below:

[0134] As shown in Figures 6 and 7, when a consumer from the ground sends a request data packet D, the interest packet D... int Forwarded to satellites in the LEO layer At that time, the data packet acquisition process begins.

[0135] Step 1: D through SFIB entries int Forward to the nearest administrator

[0136] Step 2: Query the DL entries carried by itself and perform the following operations:

[0137] • If DL has an entry named D, and its location is S h,i Then proceed to step 3;

[0138] • If DL does not contain an entry named D, then D int In Wait here and repeat step 2.

[0139] Step 3: D int S h,i The prefix name is used as a forwarding prompt, and then Forward D according to the preset routing algorithm int .

[0140] Step 4: D int It will attempt to hit D in the cache, and if it hits S... h,i Cache not hit, S h,i Send an SReq request for packet D to P based on the FIB entry.

[0141] Figure 8 shows the consumer latency under different numbers of managers according to the embodiments of the present invention. The results in Figure 8 show that the consumer latency of MsDD decreases significantly as the number of managers increases. This is because the more managers on a track plane, the fewer extra hops interest packets and data packets need to be transmitted to their nearest manager on that track plane. When the number of managers on each track is 11, the number of extra hops is 0, and therefore the consumer latency is also the lowest.

[0142] Figure 9 shows the signaling overhead under different numbers of administrators according to the embodiments of the present invention. The results in Figure 9 indicate that as the number of administrators increases, the signaling overhead for each DL update during the data collection phase also increases. This is because during the data collection phase, administrators need to send update information to the GEO satellite, and as the number of administrators increases, the GEO satellite needs to send update information to more administrators.

[0143] Figure 9 shows the signaling overhead diagram for different numbers of managers provided in the embodiments of the present invention. The schemes with 2, 3, and 4 managers can be named MsDD-2, MsDD-3, and MsDD-4, respectively, and their average delivery rates are compared under increasing data rates. Figure 9 shows that as the interest rate increases, the packet delivery rate of all three schemes decreases due to the increased amount of data in the network, with MsDD-2 and MsDD-3 showing a more significant decrease. This is because in MsDD, the manager node carries a large amount of network traffic, and the fewer managers there are, the greater the load on each manager and the inter-satellite links between different orbits. Therefore, we believe that when the number of managers on each orbit is 2 and 3, the performance of MsDD cannot reach its optimal level. Therefore, in subsequent experiments, we excluded schemes MsDD-2 and MsDD-3 and selected MsDD-4 for further experiments.

[0144] Figure 11 shows the impact of different intranet caching strategies provided in this embodiment of the invention on MsDD performance. As can be seen from Figure 11, when the request rate increases, MsDD-4's cache hit rate and consumer latency are significantly better than other schemes. This is because MsDD-4's intranet caching scheme reduces cache redundancy by probabilistically prioritizing caching of more popular content in the network, and also reduces the probability of requested content being replaced. Simultaneously, MsDD-4 increases the probability of data packets being cached on nodes closer to the administrator, allowing interest packets to hit the cache with fewer hops.

[0145] Figure 12 shows the consumer latency under different producer movement rates provided in this embodiment of the invention. The results in Figure 12 indicate that, with the increase of producer movement speed, except for PureNDN, the other schemes all exhibit good performance in terms of consumer latency, and remain stable within a reasonable range. MsDD-4 shows the most stable performance and improves consumer latency by approximately 5% compared to the other schemes.

[0146] [Corrected according to Rule 91, 24.09.2024] Figure 13 is a delivery rate diagram for different producer movement speeds provided in the embodiments of the present invention. The results in Figure 13 show that MsDD-4 has a significantly better delivery rate than other schemes, and this advantage becomes more pronounced as the producer movement speed increases. This is because while other schemes can reduce packet loss during handover to some extent, the delivery rate inevitably decreases when the number of handover events increases. For example, in Kite, as the producer movement speed increases, the frequency of producer switching between APs also increases, which leads to stale path problems and thus packet loss.

[0147] Figure 14 shows the signaling overhead under different producer movement rates provided in this embodiment of the invention. Figure 14 illustrates the change in signaling overhead as the producer movement speed increases; here, we calculate the signaling overhead during MsDD satellite handover. It can be seen that the signaling overhead of MsDD remains stable with changes in producer movement speed and is superior to Kite and T-Move. This is because during producer movement, Kite needs to frequently send TI / TD packets to the producer to update the tracking path, while T-Move needs to send messages to update the FIB before and after handover. The signaling overhead of MsDD is only related to the number of managers, because the GEO controller only sends update information to the managers.

[0148] The data communication system provided by the present invention is described below. The data communication system described below and the data communication method described above can be referred to in correspondence.

[0149] Figure 15 is a schematic diagram of the data communication system provided in an embodiment of the present invention.

[0150] As shown in Figure 15, the data communication system provided in this embodiment includes:

[0151] The information receiving module 1501 is used to receive data name information uploaded by the producer through a pre-built satellite data warehouse. The satellite data warehouse includes at least three geostationary orbit satellites and several low orbit satellites. The data name information represents the data generated by the producer.

[0152] The information update module 1502 is used to update the data in the satellite data warehouse based on the data name information.

[0153] In an exemplary embodiment, the data communication system further includes a data forwarding module, which is specifically used for:

[0154] Once the satellite data warehouse receives a request packet from a consumer, it forwards the request packet to the producer.

[0155] The satellite data warehouse receives data packets uploaded by producers based on request packets and forwards the data packets to consumers.

[0156] In an exemplary embodiment, the data forwarding module is further configured to:

[0157] Receive consumer request packets via low-Earth orbit satellites;

[0158] The request packet is marked based on the data name information;

[0159] Based on the tags, the request packets are routed to the producer.

[0160] In an exemplary embodiment, the data forwarding module is further configured to:

[0161] [Corrected according to Rule 91 24.09.2024] Based on the preset routing rules, the request packet is routed to the target satellite, and the address of the target satellite corresponds to the tag;

[0162] Based on preset routing rules, the request packet is routed to the target satellite, and the address of the target satellite corresponds to the tag;

[0163] The target satellite forwards the request packet to the producer based on the producer's data name information.

[0164] In an exemplary embodiment, the data communication system further includes a buffer forwarding module, which is specifically used for:

[0165] When the satellite data warehouse receives a request packet from a consumer, if it determines that the satellite data warehouse has cached the data packet corresponding to the request packet, it will forward the cached data packet to the consumer.

[0166] In an exemplary embodiment, the data communication system further includes a caching module, which is specifically used for:

[0167] Determine the number of times the data packet was requested;

[0168] Determine the number of hops for each low-Earth orbit satellite each time a data packet is requested;

[0169] The probability of each low-Earth orbit satellite caching data packets is calculated based on the number of times the data packets are requested and the number of hops.

[0170] Each low-Earth orbit satellite caches data packets based on a cache probability.

[0171] In an exemplary embodiment, the data communication system further includes a routing table construction module, which is specifically used for:

[0172] For each low-Earth orbit satellite, send the first information to other low-Earth orbit satellites in the same orbit. The first information represents the position of the low-Earth orbit satellite.

[0173] When a low-Earth orbit satellite in the same orbit receives the first information, if the low-Earth orbit satellite in the same orbit does not have an inter-satellite communication routing table corresponding to the low-Earth orbit satellite, then an inter-satellite communication routing table is created and stored in the low-Earth orbit satellite in the same orbit; if it has already been stored, then the inter-satellite communication routing table is updated based on the first information.

[0174] For each low-Earth orbit satellite, at set intervals, a second message is sent to low-Earth orbit satellites in different orbits. The second message represents the position of the low-Earth orbit satellite.

[0175] When low-Earth orbit satellites in different orbits receive the second information, if the inter-satellite communication routing table corresponding to the low-Earth orbit satellite is not stored in the low-Earth orbit satellites in different orbits, then the inter-satellite communication routing table is created and stored in the low-Earth orbit satellites in different orbits; if it has been stored, then the inter-satellite communication routing table is updated based on the second information.

[0176] In an exemplary embodiment, the data communication system is further used for:

[0177] Update the target satellite's data based on the data name information;

[0178] Update the data of all low-Earth orbit satellites and geostationary orbit satellites in the satellite data warehouse.

[0179] The specific implementation method of the data communication system provided in this embodiment can be implemented with reference to the above embodiments, and will not be repeated here.

[0180] [Corrected according to Rule 91, 24.09.2024] Figure 16 illustrates a schematic diagram of the physical structure of an electronic device. As shown in Figure 16, the electronic device may include: a processor 910, a communication interface 920, a memory 930, and a communication bus 940. The processor 910, communication interface 920, and memory 930 communicate with each other via the communication bus 940. The processor 910 can call logical instructions in the memory 930 to execute a data communication method, which includes:

[0181] The system receives data name information uploaded by producers through a pre-built satellite data warehouse, which includes at least three geostationary orbit satellites and several low orbit satellites. The data name information represents the data generated by the producers.

[0182] Update the data in the satellite data warehouse based on the data name information.

[0183] [Corrected according to Rule 91, September 24, 2024] Furthermore, when the logical instructions in the aforementioned memory 930 can be implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes: USB flash drive, mobile hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, and other media capable of storing program code.

[0184] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer is able to perform the data communication methods provided by the methods described above. Furthermore, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the data communication methods provided by the methods described above.

[0185] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0186] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A data communication method, characterized in that, include: The system receives data name information uploaded by producers through a pre-built satellite data warehouse, which includes at least three geostationary orbit satellites and several low-orbit satellites. The data name information represents the data generated by the producers. The data in the satellite data warehouse is updated based on the data name information.

2. The data communication method according to claim 1, characterized in that, Also includes: When the satellite data warehouse receives a request packet from a consumer, it forwards the request packet to the producer. The satellite data warehouse receives the data packets uploaded by the producer based on the request packet and forwards the data packets to the consumer.

3. The data communication method according to claim 2, characterized in that, When the satellite data warehouse receives a request packet from a consumer, it forwards the request packet to the producer, including: The request packet from the consumer is received via the low-Earth orbit satellite; The request packet is marked based on the data name information; Based on the tag, the request packet is routed to the producer.

4. The data communication method according to claim 3, characterized in that, The satellite data warehouse receives data name information uploaded by producers through a target satellite, which is one of the plurality of low-Earth orbit satellites; The step of routing the request packet to the producer based on the tag includes: Based on preset routing rules, the request packet is routed to the target satellite, and the address of the target satellite corresponds to the tag; The target satellite forwards the request packet to the producer based on the producer's data name information.

5. The data communication method according to claim 2, characterized in that, Also includes: When the satellite data warehouse receives a request packet from a consumer, if it determines that the satellite data warehouse has cached the data packet corresponding to the request packet, it forwards the cached data packet to the consumer.

6. The data communication method according to claim 5, characterized in that, The satellite data warehouse caches the data packets using the following method: Determine the number of times the data packet was requested; Determine the number of hops for each of the low-Earth orbit satellites that the data packet passes through each time it is requested; Based on the number of times the data packet was requested and the number of hops, calculate the caching probability of each low-Earth orbit satellite for the data packet; Each of the low-Earth orbit satellites caches the data packets based on the cache probability.

7. The data communication method according to claim 1, characterized in that, The satellite data warehouse contains routing tables, which include satellite-to-ground communication routing tables and inter-satellite communication routing tables. The low-Earth orbit satellites are distributed across several orbits. The method for constructing the inter-satellite communication routing tables includes: For each of the aforementioned low-Earth orbit satellites, a first message is sent to other low-Earth orbit satellites in the same orbit, the first message representing the position of the aforementioned low-Earth orbit satellite; When the low-Earth orbit satellite in the same orbit receives the first information, if the low-Earth orbit satellite in the same orbit does not store the inter-satellite communication routing table corresponding to the low-Earth orbit satellite, then the inter-satellite communication routing table is created and stored in the low-Earth orbit satellite in the same orbit; if it has already been stored, then the inter-satellite communication routing table is updated based on the first information. For each of the aforementioned low-Earth orbit satellites, at set intervals, second information is sent to low-Earth orbit satellites in different orbits, the second information representing the position of the low-Earth orbit satellite; When the low-Earth orbit satellites in different orbits receive the second information, if the inter-satellite communication routing table corresponding to the low-Earth orbit satellite is not stored in the low-Earth orbit satellites in different orbits, then the inter-satellite communication routing table is created and stored in the low-Earth orbit satellites in different orbits; if it has been stored, then the inter-satellite communication routing table is updated based on the second information.

8. The data communication method according to claim 4, characterized in that, The process of updating the data in the satellite data warehouse based on the data name information includes: The data of the target satellite is updated based on the data name information; Update the data of all the low-Earth orbit satellites and geostationary orbit satellites in the satellite data warehouse.

9. A data communication system, characterized in that, include: An information receiving module is used to receive data name information uploaded by producers through a pre-built satellite data warehouse, wherein the satellite data warehouse includes at least three geostationary orbit satellites and several low orbit satellites, and the data name information represents the data generated by the producer; The information update module is used to update the data in the satellite data warehouse based on the data name information.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the data communication method as described in any one of claims 1-8.

Images