WO2022220859A1

WO2022220859A1 - Satellite network addressing

Info

Publication number: WO2022220859A1
Application number: PCT/US2021/044662
Authority: WO
Inventors: Lin Han
Original assignee: Futurewei Technologies, Inc.
Priority date: 2021-07-02
Filing date: 2021-08-05
Publication date: 2022-10-20

Abstract

A method comprises generating a message comprising addressing, wherein the addressing is for a first satellite and is associated with first orbital information of the first satellite or the addressing is for a second satellite and is associated with second orbital information of the second satellite; and transmitting the message to the second satellite. A method implemented by a GS comprises generating a message comprising first addressing and control instructions, wherein the first addressing is for a first satellite and is associated with first orbital information of the first satellite, wherein the first addressing comprises an orbital plane ID of the first satellite or a satellite ID of the first satellite, and wherein the control instructions are configured to control the first satellite; and transmitting the message to the first satellite.

Description

Satellite Network Addressing

CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This claims priority to U.S. Prov. Patent App. No. 63/218,142 filed on July 2, 2021, which is incorporated by reference.

TECHNICAL FIELD

[0002] The disclosed embodiments relate to satellites in general and satellite network addressing in particular.

BACKGROUND

[0003] Artificial satellites, including GSO, LEO, and VLEO satellites, are becoming ubiquitous for military and commercial purposes. Fixed satellite systems provide audio, video, and other data services. Mobile satellite systems connecting remote entities such as vehicles serve as navigation systems. Scientific satellite systems provide meteorological, land survey, and other data for research purposes. Satellites previously communicated only with GSs, but are now beginning to establish networks and communicate with each other.

SUMMARY

[0004] A first aspect relates to a method comprising: generating a message comprising addressing, wherein the addressing is for a first satellite and is associated with first orbital information of the first satellite or the addressing is for a second satellite and is associated with second orbital information of the second satellite; and transmitting the message to the second satellite.

[0005] The embodiments provide for satellite network addressing. The addressing is IP addressing or MAC addressing and provides an addressing structure associated with orbital information. The addressing comprises an orbital plane ID, a satellite ID, and an interface ID. The addressing further comprises either a network ID or an OUT The orbital plane ID and the satellite ID are sufficient to identify each satellite in a network. The orbital plane ID is associated with orbital information such as parameters e, a, i, W, co, and tO. The satellite ID is associated with orbital information such as parameter v. The addressing is static in order to make routing and forwarding simpler.

[0006] Optionally, in any of the preceding aspects, the first satellite implements the method.

[0007] Optionally, in any of the preceding aspects, a GS implements the method.

[0008] Optionally, in any of the preceding aspects, the addressing is for the second satellite and is associated with the second orbital information, and the method further comprises: determining the second orbital information based on the addressing; calculating a beam direction based on the second orbital information; and further transmitting the message using the beam direction.

[0009] Optionally, in any of the preceding aspects, the second orbital information comprises at least one of e, a, i, W, co, tO, or v.

[0010] Optionally, in any of the preceding aspects, the addressing comprises an orbital plane ID.

[0011] Optionally, in any of the preceding aspects, the orbital plane ID identifies an orbital plane and is sequentially numbered from a reference orbital plane ID identifying a reference orbital plane.

[0012] Optionally, in any of the preceding aspects, the addressing comprises an orbital plane ID, wherein the orbital plane ID comprises an orbital group ID and an orbital plane sub-ID, wherein the orbital group ID identifies an orbital group that an orbit belongs to, and wherein the orbital plane sub-ID identifies an orbital plane in the orbital group.

[0013] Optionally, in any of the preceding aspects, the addressing further comprises a satellite ID.

[0014] Optionally, in any of the preceding aspects, the satellite ID identifies a satellite within an orbital plane and is sequentially numbered from a reference satellite ID identifying a reference satellite.

[0015] Optionally, in any of the preceding aspects, the addressing further comprises an interface ID.

[0016] Optionally, in any of the preceding aspects, the interface ID identifies one of five interfaces of a satellite.

[0017] Optionally, in any of the preceding aspects, the addressing further comprises a network ID. [0018] Optionally, in any of the preceding aspects, the network ID identifies a jurisdiction or a network within that jurisdiction.

[0019] Optionally, in any of the preceding aspects, the addressing further comprises an OUI. [0020] Optionally, in any of the preceding aspects, the OUI uniquely identifies a vendor, a manufacturer, or another organization associated with a satellite.

[0021] Optionally, in any of the preceding aspects, the addressing is 32 bits.

[0022] Optionally, in any of the preceding aspects, the message further comprises an IPv4 header, wherein the IPv4 header comprises the addressing, and wherein part of the addressing replaces a source address and a destination address in the IPv4 header.

[0023] Optionally, in any of the preceding aspects, the message further comprises an IPv6 header, and wherein the IPv4 header is embedded in the IPv6 header.

[0024] Optionally, in any of the preceding aspects, the message further comprises a New IP header, and wherein the IPv4 header is embedded in the New IP header.

[0025] Optionally, in any of the preceding aspects, the message further comprises an Ethernet MAC address, and wherein the Ethernet MAC address comprises the addressing.

[0026] A second aspect relates to a first satellite comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of the preceding aspects.

[0027] A third aspect relates to a computer program product comprising computer-executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a first satellite to perform any of the preceding aspects.

[0028] A fourth aspect relates to a GS comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of the preceding aspects.

[0029] A fifth aspect relates to a computer program product comprising computer-executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a GS to perform any of the preceding aspects.

[0030] A sixth aspect relates to a method implemented by a first satellite and comprising: receiving a message from a second satellite; parsing the message to obtain an actual orbital plane ID of the message and an actual satellite ID of the message; determining a peer position of the second satellite based on a beam direction of the message; determining an expected orbital plane ID of the second satellite and an expected satellite ID of the second satellite; and performing authentication by at least one of comparing the actual orbital plane ID to the expected orbital plane ID or comparing the actual satellite ID to the expected satellite ID.

[0031] Optionally, in any of the preceding aspects, the authentication is of the message and the second satellite.

[0032] Optionally, in any of the preceding aspects, the method further comprises processing the message when the authentication succeeds.

[0033] Optionally, in any of the preceding aspects, the method further comprises communicating with the second satellite when the authentication succeeds.

[0034] Optionally, in any of the preceding aspects, the method further comprises discarding the message when the authentication fails.

[0035] Optionally, in any of the preceding aspects, the method further comprises reporting the second satellite to a GS when the authentication fails.

[0036] A seventh aspect relates to a first satellite comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of the preceding aspects.

[0037] An eighth aspect relates to a computer program product comprising computer- executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a first satellite to perform any of the preceding aspects.

[0038] A ninth aspect relates to a method implemented by a GS and comprising: generating a message comprising first addressing and control instructions, wherein the first addressing is for a first satellite and is associated with first orbital information of the first satellite, wherein the first addressing comprises an orbital plane ID of the first satellite or a satellite ID of the first satellite, and wherein the control instructions are configured to control the first satellite; and transmitting the message to the first satellite.

[0039] Optionally, in any of the preceding aspects, the control instructions comprise second addressing of a second satellite, comprise second orbital information of the second satellite, and instruct the first satellite to update a data structure of the first satellite with the second addressing and the second orbital information.

[0040] Optionally, in any of the preceding aspects, the method further comprises: detecting a phenomenon affecting the first satellite; and updating the first orbital information in response to the phenomenon, wherein the control instructions comprise updated first orbital information of the first satellite and instruct the first satellite to update a data structure of the first satellite with the updated first orbital information.

[0041] A tenth aspect relates to a GS comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of the preceding aspects.

[0042] An eleventh aspect relates to a computer program product comprising computer- executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a GS to perform any of the preceding aspects.

[0043] Any of the above embodiments may be combined with any of the other above embodiments to create a new embodiment. These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS [0044] For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.

[0045] FIG. 1 is a schematic diagram of a satellite network.

[0046] FIG. 2 is a flowchart illustrating a method of satellite network addressing.

[0047] FIG. 3 is a schematic diagram of a first simplified addressing structure.

[0048] FIG. 4 is a schematic diagram of an orbital plane and orbital plane ID scheme.

[0049] FIG. 5 is a schematic diagram of a satellite and satellite ID scheme.

[0050] FIG. 6 is a schematic diagram of a first IP addressing structure.

[0051] FIG. 7 is a schematic diagram of a second IP addressing structure.

[0052] FIG. 8 is a schematic diagram of the orbital plane ID in FIG. 6.

[0053] FIG. 9 is a schematic diagram of an orbital plane, orbital group ID, and orbital plane

ID scheme.

[0054] FIG. 10 is a schematic diagram of the orbital plane ID in FIG. 7.

[0055] FIG. 11 A is a schematic diagram of an extended IPv4 packet.

[0056] FIG. 1 IB is a schematic diagram of the extended header in FIG. 11 A. [0057] FIG. 12 is a schematic diagram of a second simplified addressing structure.

[0058] FIG. 13 is a schematic diagram of a MAC addressing structure.

[0059] FIG. 14 is a flowchart illustrating a method of satellite-to-satellite communication.

[0060] FIG. 15 is a flowchart illustrating a method of satellite authentication.

[0061] FIG. 16 is a flowchart illustrating a method of controlling a satellite.

[0062] FIG. 17 is a schematic diagram of an apparatus.

DETAILED DESCRIPTION

[0063] It should be understood at the outset that, although an illustrative implementation of one or more embodiments are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

[0064] The following abbreviations apply: a: semimajor axis

ASIC: application-specific integrated circuit

CPU: central processing unit

DSP: digital signal processor e: eccentricity

EO: electrical -to-optical

EU: European Union

FPGA: field-programmable gate array

GS: ground station

GSO: geosynchronous orbit i: inclination

IANA: Internet Assigned Numbers Authority ID: identifier

IEEE: Institute of Electrical and Electronics Engineers IHL: internet header length IP: Internet Protocol

IPv4: Internet Protocol version 4

IPv6: Internet Protocol version 6

ITU: International Telecommunication Union km/s: kilometer(s) per second

LEO: low Earth orbit

MAC: medium access control

NIC: network interface controller

OE: optical -to-electrical

OUT organizationally unique identifier

RAM: random-access memory

RF : radio frequency

ROM: read-only memory

RX: receiver unit s: second(s)

SRAM: static RAM

TCAM: ternary content-addressable memory TX: transmitter unit tO: epoch time when other parameters are measured v: position, true anomaly

VLEO: very low Earth orbit

W: longitude of an ascending node co: argument of periapsis.

[0065] Current satellite networks include Starlink and Constellation. Starlink is planned to include 11,943 LEO and VLEO satellites by 2027. However, a new plan would increase that number to 46,000. Constellation is planned to include 12,992 satellites. Other satellite networks, for instance in the EU, are likely to emerge. It is therefore necessary to develop schemes, including addressing schemes, for networking a large number of satellites.

[0066] However, addressing for satellites has challenges due to the velocities of satellites, which exceed 7 km/s; the coverage radii of satellites, which are in the range of 435-1,230 km; the need to flush and recalculate routes due to GS connection changes every 100-400 s; and constant changes in network topology. IP addressing and MAC addressing are two types of addressing used in other contexts. However, in the contexts of satellites, current IP addressing may be unstable due to the need to frequently assign addresses while the network topology quickly changes. In addition, current IP addressing uses virtual addresses, which provide network and device information, but not geographical information needed for a quickly-changing network topology. Current MAC addressing has similar shortcomings and also provides fewer addresses, even though satellite network addressing will need to cover over 10,000 nodes and each node will need multiple addresses. There is therefore a desire to develop an addressing scheme that overcomes those shortcomings.

[0067] Disclosed herein are embodiments for satellite network addressing. The addressing is IP addressing or MAC addressing and provides an addressing structure associated with orbital information. The addressing comprises an orbital plane ID, a satellite ID, and an interface ID. The addressing further comprises either a network ID or an OUT The orbital plane ID and the satellite ID are sufficient to identify each satellite in a network. The orbital plane ID is associated with orbital information such as parameters e, a, i, W, co, and tO. The satellite ID is associated with orbital information such as parameter v. The addressing is static in order to make routing and forwarding simpler. Though static IP addressing, static MAC addressing, specific field orders, and specific field bit lengths are discussed, other suitable embodiments are possible. For instance, the IP addressing and the MAC addressing could be dynamic.

[0068] FIG. 1 is a schematic diagram of a satellite network 100. The satellite network 100 comprises a first satellite 110, a second satellite 120, a service provider 130, and a GS 140. The first satellite 110 and the second satellite 120 may be geosynchronous, LEO, VLEO, or other satellites. Though two satellites and one GS are shown, the satellite network 100 may comprise any suitable number of satellites and GSs (such as a plurality of satellites and/or a plurality of GSs). As an example, the satellite network 100 implements 20 orbits and comprises either 22-23 LEO satellites per orbit or 48-62 VLEO satellites per orbit, totaling 440-1,240 satellites to cover Earth.

[0069] FIG. 2 is a flowchart illustrating a method 200 of satellite network addressing. The service provider 130 performs the method 200. At step 205, the service provider 130 assigns first addressing to the first satellite 110. The first addressing is static. In this context, static means that the addressing for each satellite stays the same for an arbitrary period of time (for example, greater than one hour, one day, one month, or one year), while the satellite is in commission, or based on other criteria. The first addressing comprises the first simplified addressing structure described in FIG. 3.

[0070] FIG. 3 is a schematic diagram of a first simplified addressing structure 300. The first simplified addressing structure 300 comprises a network ID 310, an orbital plane ID 320, a satellite ID 330, and an interface ID 340. The first simplified addressing structure 300 is simplified because it may be incorporated into more complex structures as discussed below. The first satellite 110, the second satellite 120, and the GS 140 may store the network ID 310, the orbital plane ID 320, the satellite ID 330, and the interface ID 340, as well as additional structure and corresponding fields for communication within the satellite network 100.

[0071] The network ID 310 identifies a jurisdiction and/or a network within that jurisdiction. For instance, the network ID 310 identifies the US and Starlink, China and Constellation, or another jurisdiction and the satellite network 100. LANA, ITU, or another organization can allocate the network ID 310.

[0072] The orbital plane ID 320 identifies an orbital plane. The orbital plane ID 320 can be sequentially numbered from a reference orbital plane ID identifying a reference orbital plane. For example, the reference orbital plane may be the first orbital plane with satellites that are launched into space for the satellite network 100. FIG. 4 demonstrates such sequential numbering.

[0073] FIG. 4 is a schematic diagram of an orbital plane and orbital plane ID scheme 400. The orbital plane and orbital plane ID scheme 400 shows orbital plane IDs 410 identifying orbital planes 420. A reference orbital plane ID 410 value of 1 identifies a reference orbital plane 420. Moving laterally to the left, an orbital plane ID 410 value of 2 identifies a next orbital plane 420. That assignment continues until a last orbital plane ID 410 value of 9 identifies a last orbital plane 420. Though nine orbital planes are shown, there may be fewer or more than nine orbital planes. [0074] Returning to FIG. 3, the satellite ID 330 identifies a satellite within an orbital plane. The satellite ID 330 can be sequentially numbered from a reference satellite ID identifying a reference satellite. For example, the reference satellite may be the first satellite, within an orbit, that is launched into space for the satellite network 100. FIG. 5 demonstrates such sequential numbering.

[0075] FIG. 5 is a schematic diagram of a satellite and satellite ID scheme 500. The satellite and satellite ID scheme 500 shows satellite IDs 510 identifying satellites 520. A reference satellite ID 510 value of 1 identifies a reference satellite 520 within an orbital plane. For instance, the orbital plane is the reference orbital plane 420 identified by the reference orbital plane ID 410 value of 1 in FIG. 4. Moving counterclockwise, a satellite ID 510 value of 2 identifies a next satellite 520. That assignment continues until a last satellite ID 510 value of 7 identifies a last satellite 520. Though seven satellites are shown, there may be fewer or more than seven satellites. [0076] Returning to FIG. 3, the interface ID 340 identifies one of five interfaces of a satellite. A first interface ID 340 (for example, a value of 1) identifies interface 1 for communicating with a peer satellite positioned ahead in the same orbital plane. A second interface ID 340 (for example, a value of 2) identifies interface 2 for communicating with a peer satellite positioned behind in the same orbital plane. A third interface ID 340 (for example, a value of 3) identifies interface 3 for communicating with a peer satellite positioned ahead in the subsequent orbital plane. A fourth interface ID 340 (for example, a value of 4) identifies interface 4 for communicating with a peer satellite positioned behind in the previous orbital plane. A fifth interface ID 340 (for example, a value of 5) identifies interface 5 for communicating with a peer satellite crossing paths from a different orbital plane. Though five interfaces are discussed, there may be fewer or more interfaces and corresponding interface IDs 340. When the first simplified addressing structure 300 comprises no interface ID 340 or when the interface ID 340 has a value of 0, the first simplified addressing structure 300 identifies a satellite itself instead of an interface of the satellite.

[0077] As shown, the network ID 310 forms a network prefix. The network prefix represents the satellite network 100. The network ID 310 and the orbital plane ID 320 together form an orbital prefix. The orbital prefix represents an orbit of the first satellite 110. The network ID 310, the orbital plane ID 320, and the satellite ID 330 together form a satellite prefix. The satellite prefix represents the first satellite 110. When the first simplified addressing structure 300 is used for IP addressing, the first satellite 110, the second satellite 120, the service provider 130, and the GS 140 may use the network prefix, the orbital prefix, and the satellite prefix for longest prefix match. The network ID 310, the orbital plane ID 320, the satellite ID 330, and the interface ID 340 are optional and one or more of them can be combined or omitted in any suitable manner. [0078] Returning to FIG. 2, at step 210, the service provider 130 determines first orbital information of the first satellite 110. The first orbital information comprises parameters e, a, i, W, co, tO, and v. The service provider 130 calculates different orbital information for each satellite in the satellite network 100 in order to satisfy the orbital plane and orbital plane ID scheme 400 and the satellite and satellite ID scheme 500.

[0079] At step 215, the service provider 130 creates a first association between the first addressing and the first orbital information. The first association comprises two sub-associations. Specifically, the orbital plane ID 320 is associated with orbital information parameters such as e, a, i, W, co, and tO, which are sufficient to determine an orbit. The satellite ID 330 is associated with orbital information parameter v, which is sufficient to determine a position of a satellite within an orbit at any time t using the law of conservation of angular momentum. The service provider 130 provides the first association to the first satellite 110 and the GS 140. The first satellite 110, the service provider 130, and the GS 140 store the first association, for instance, in a lookup table or other data structure. Table 1 is an example of a lookup table with information for multiple satellites.

Table 1

[0080] At step 220, the service provider 130 launches the first satellite 110. The service provider 130 does so in a manner that satisfies the first orbital information. Thus, the service provider 130 does so in a manner that also satisfies the orbital plane and orbital plane ID scheme 400 and the satellite and satellite ID scheme 500.

[0081] Steps 225-240 are similar to steps 205-220, but for the second satellite 120 instead of the first satellite 110. Specifically, at step 225, the service provider 130 assigns second addressing to a second satellite, the second satellite 120. At step 230, the service provider 130 determines second orbital information of the second satellite 120. At step 235, the service provider 130 creates a second association between the second addressing and the second orbital information. At step 240, the service provider 130 launches the second satellite 120. [0082] At step 245, the service provider 130 provides the first satellite 110 with the second addressing, the second orbital information, and the second association. If the second satellite 120 is a new satellite that was not included in the initial planning of the satellite network 100, then the service provider 130 may perform step 245 after performing step 240. However, if the second satellite 120 was included in the initial planning, then the service provider 130 may perform step 245 before performing step 220.

[0083] At step 250, the service provider 130 updates the first orbital information and the first association. While the orbital information parameters e, a, i, W, co, and tO are very steady, they may change due to air resistance, a solar wind, and other phenomena. When those phenomena occur, a specified time period has elapsed, a new satellite joins the satellite network 100, or another condition occurs, the service provider 130 recalculates those parameters to update the first orbital information, and thus the first association, to obtain updated first orbital information and an updated first association. The service provider 130 causes the GS 140 to transmit an update message to the first satellite 110 and the second satellite 120. The update message comprises the updated first orbital information and the updated first association.

[0084] FIG. 6 is a schematic diagram of a first IP addressing structure 600. The first IP addressing structure 600 is similar to and incorporates the first simplified addressing structure 300. Specifically, the first IP addressing structure 600 comprises a network ID 610, an orbital plane ID 620, a satellite ID 630, and an interface ID 640 similar to the network ID 310, the orbital plane ID 320, the satellite ID 330, and the interface ID 340, respectively, in the first simplified addressing structure 300. However, unlike the first simplified addressing structure 300, the first IP addressing structure 600 further comprises a reserved field 650. As shown, the network ID 610 is 4 bits, the orbital plane ID 620 is 9 bits, the satellite ID 630 is 7 bits, the interface ID 640 is 4 bits, and the reserved field is 8 bits, totaling 32 bits.

[0085] FIG. 7 is a schematic diagram of a second IP addressing structure 700. The second IP addressing structure 700 is similar to and incorporates the first simplified addressing structure 300. Specifically, the second IP addressing structure 700 comprises a network ID 710, an orbital plane ID 720, a satellite ID 730, and an interface ID 740 similar to the network ID 310, the orbital plane ID 320, the satellite ID 330, and the interface ID 340, respectively, in the first simplified addressing structure 300. As shown, the network ID 710 is 5 bits, the orbital plane ID 720 is 12 bits, the satellite ID 730 is 8 bits, and the interface ID 740 is 7 bits, totaling 32 bits. [0086] FIG. 8 is a schematic diagram of the orbital plane ID 620 in FIG. 6. The orbital plane ID 620 in FIG. 8 is 9 bits and comprises an orbital group ID 810 and an orbital plane sub-ID 820. The orbital group ID 810 is 4 bits and identifies an orbital group that an orbit belongs to. All orbits in the same orbital group have the same inclination and the same altitude. The orbital plane sub- ID 820 is 5 bits and identifies an orbital plane in the orbital group. FIG. 9 demonstrates orbital group ID and orbital plane ID numbering.

[0087] FIG. 9 is a schematic diagram of an orbital plane, orbital group ID, and orbital plane ID scheme 900. The orbital plane, orbital group ID, and orbital plane ID scheme 900 shows orbital group IDs 910 and orbital plane IDs 920 identifying orbital planes 930. A first orbital group corresponding to orbital group ID 910 1 is located at the top of the page and comprises 5 orbital planes 930, all of which have the same inclination and the same altitude. Within the first orbital group, a reference orbital plane ID 920 value of 1 identifies a reference orbital plane 930. Moving laterally to the left, an orbital plane ID 920 value of 2 identifies a next orbital plane 930. That assignment continues until a last orbital plane ID 920 value of 5 identifies a last orbital plane 930. [0088] A second orbital group corresponding to orbital group ID 9102 is located at the bottom of the page and comprises 4 orbital planes 930, all of which have the same inclination and the same altitude. Within the second orbital group, a reference orbital plane ID 920 value of 1 identifies a reference orbital plane 930. Moving laterally to the right, an orbital plane ID 920 value of 2 identifies a next orbital plane 930. That assignment continues until a last orbital plane ID 920 value of 4 identifies a last orbital plane 930. Though 9 orbital planes are shown, there may be fewer or more than 9 orbital planes.

[0089] FIG. 10 is a schematic diagram of the orbital plane ID 720 in FIG. 7. The orbital plane ID 720 in FIG. 10 is optional, is 12 bits, and comprises an orbital group ID 1010 and an orbital plane ID 1020. The orbital group ID 1010 and the orbital plane ID 1020 are similar to the orbital group ID 810 and the orbital plane sub-ID 820, respectively, in FIG. 8.

[0090] As mentioned above, the first IP addressing structure 600 and the second IP addressing structure 700 are 32-bit addresses. Such 32-bit addresses may be used for IPv4, IPv6, and New IP. For IPv4, the 32-bit addresses replace the source address and the destination address in an IPv4 header. The header and a payload together form a packet as shown in FIGS. 11 A and 1 IB below. For IPv6, the 32-bit address is embedded in IPv6 the same way IPv4 is embedded in IPv6. For New IP, described for instance in International Patent App. No. PCT/US2020/057962, published as WO/2021/108071 on 3 June 2021, which is incorporated by reference herein in its entirety, the 32-bit address is similarly embedded.

[0091] FIG. 11 A is a schematic diagram of an extended IPv4 packet 1100. The extended IPv4 packet 1100 comprises an extended header 1110 and a payload 1120. The payload 1120 comprises user data. FIG. 1 IB is a schematic diagram of the extended header 1110 in FIG. 11 A. As shown, the extended header 1110 comprises a 32-bit satellite address 1130 as described above.

[0092] FIG. 12 is a schematic diagram of a second simplified addressing structure 1200. The second simplified addressing structure 1200 is an alternative to the first simplified addressing structure 300. Thus, in the method 200, the first addressing and the second addressing may instead comprise the second simplified addressing structure 1200.

[0093] The second simplified addressing structure 1200 is similar to the first simplified addressing structure 300 in FIG. 3. Specifically, the second simplified addressing structure 1200 comprises an orbital plane ID 1220, a satellite ID 1230, and an interface ID 1240, which are similar to the orbital plane ID 320, the satellite ID 330, and the interface ID 340, respectively, in the first simplified addressing structure 300.

[0094] However, instead of the network ID 310, the second simplified addressing structure 1200 comprises an OUI 1210. The OUI 1210 is a number that uniquely identifies a vendor, a manufacturer, or another organization associated with a satellite. Thus, the OUI 1210 provides a similar function as the network ID 310. IEEE or another organization can allocate the OUI 1210. In addition, unlike in the first simplified addressing structure 300, the orbital plane ID 1220, the satellite ID 1230, and the interface ID 1240 in the second simplified addressing structure 1200 together form a satellite address. The satellite address may be embedded as a 24-bit NIC-specific field. In that case, the OUI 1210 is 24 bits, and the OUI 1210 and the NIC-specific field together form an Ethernet MAC address.

[0095] FIG. 13 is a schematic diagram of a MAC addressing structure 1300. The MAC addressing structure 1300 is similar to and incorporates the second simplified addressing structure 1200. Specifically, the MAC addressing structure 1300 comprises an orbital plane ID 1320, a satellite ID 1330, and an interface ID 1340 similar to the orbital plane ID 1220, the satellite ID 1230, and the interface ID 1240, respectively, in the second simplified addressing structure 1200. However, unlike the second simplified addressing structure 1200, the MAC addressing structure 1300 further comprises a reserved field 1310. As shown, the reserved field 1310 is 3 bits, the orbital plane ID 1320 is 9 bits, the satellite ID 1330 is 8 bits, and the interface ID 1340 is 4 bits, totaling 24 bits.

[0096] FIG. 14 is a flowchart illustrating a method 1400 of satellite-to-satellite communication. At step 1410, the first satellite 110 generates a message comprising addressing. The addressing is for the first satellite and is associated with first orbital information of the first satellite or the addressing is for a second satellite and is associated with second orbital information of the second satellite. For instance, the addressing comprises the first simplified addressing structure 300 or the second simplified addressing structure 1200, and the first orbital information or the second orbital information comprises e, a, i, W, co, tO, and v. At step 1420, the first satellite 110 transmits the message to the second satellite 120.

[0097] The method 1400 may implement additional embodiments. Specifically, in a similar embodiment, the addressing is for the second satellite 120 and is associated with the second orbital information, the first satellite 110 determines the second orbital information based on the addressing, the first satellite 110 calculates a beam direction based on the second orbital information, and the first satellite 110 further transmits the message using the beam direction. For instance, the first satellite 110 knows the addressing of the second satellite 120 and looks up the orbital information of the second satellite 120 in Table 1. The second orbital information comprises at least one of e, a, i, W, co, tO, or v. The method 1400 illustrates GS-to-satellite communication, and the GS 140 implements the method 1400.

[0098] The addressing comprises an orbit plane ID. The addressing further comprises a satellite ID. The addressing further comprises an interface ID. The addressing further comprises a network ID. The addressing further comprises an OUT The addressing is 32 bits.

[0099] The message further comprises an IPv4 header, the IPv4 header comprises the addressing, and part of the addressing replaces a source address and a destination address in the IPv4 header. The message further comprises an IPv6 header, and the IPv4 header is embedded in the IPv6 header. The message further comprises a New IP header, and the IPv4 header is embedded in the New IP header.

[0100] FIG. 15 is a flowchart illustrating a method 1500 of satellite authentication. At step 1510, the first satellite 110 receives a message from the second satellite 120. At step 1520, the first satellite 110 parses the message to obtain an actual orbital plane ID of the message and an actual satellite ID of the message. For instance, the actual orbital plane ID is the orbital plane ID 320 or the orbital plane ID 1220, and the actual satellite ID is the satellite ID 330 or the satellite ID 1230.

[0101] At step 1530, the first satellite determines a peer position of the second satellite based on a beam direction of the message. For instance, the beam direction suggests one of four peer positions: peer position 1 of a first peer satellite positioned ahead in the same orbital plane, peer position 2 of a second peer satellite positioned behind in the same orbital plane, peer position 3 of a third peer satellite positioned ahead in the subsequent orbital plane, or peer position 4 of a fourth peer satellite positioned behind in the previous orbital plane.

[0102] At step 1540, the first satellite 110 determines an expected orbital plane ID of the second satellite and an expected satellite ID of the second satellite based on the peer position. For instance, assuming the orbital plane ID of the first satellite 110 is a value OPID, the satellite ID of the first satellite 110 is a value SID, the total number of satellites in the same orbit plane is a value Tl, and the total number of orbital planes in the satellite network 100 is a value T2, the second satellite 120 should have an orbital plane ID and a satellite ID as follows:

Table 2

In Table 2, SID1 is one more than SID if SID is less than Tl; otherwise, SID1 is 1. SID2 is one less than SID if SID is greater than 1; otherwise, SID2 is equal to Tl. OPID3 is one more than OPID if OPID is less than 2; otherwise, OPID3 is 1. OPID4 if one less than OPID if OPID is greater than 1; otherwise, OPID4 is equal to T2. Stated another way:

SID1 = SID + 1 if SID < Tl SID1 = 1 if SID = Tl

SID2 = SID - 1 if SID > 1 SID2 = Tl if SID = 1 OPID3 = OPID + 1 if OPID < T2

OPID3 = 1 if OPID = T2

OPID4 = OPID - 1 if OPID > 1

OPID4 = T2 if OPID = 1.

[0103] At step 1550, the first satellite performs authentication by comparing the actual orbital plane ID to the expected orbital plane ID and by comparing the actual satellite ID to the expected satellite ID. For instance, if the actual orbital plane ID is the same as the expected orbital plane ID and if the actual satellite ID is the same as the expected satellite ID, then the authentication succeeds. If either the actual orbital plane ID is different from the expected orbital plane ID or if the actual satellite ID is different from the expected satellite ID, then the authentication fails. [0104] The method 1500 may implement additional embodiments. Specifically, the first satellite 110 processes the message when the authentication succeeds. The first satellite 110 communicates with the second satellite when the authentication succeeds. The first satellite 110 discards the message when the authentication fails. The first satellite 110 reports the second satellite to a ground station when the authentication fails.

[0105] FIG. 16 is a flowchart illustrating a method 1600 of controlling a satellite. At step 1610, the GS 140 generates a message comprising first addressing and control instructions. The first addressing is for one or more satellites, for example including the first satellite 110, and associated with first orbital information of the first satellite 110. The first addressing comprises an orbital plane ID of the first satellite or comprises a satellite ID of the first satellite and/or one or more other satellites. The control instructions control the first satellite 110. For instance, the first orbital information is e, a, i, W, co, tO, and v; the orbital plane ID is the orbital plane ID 320 or the orbital plane ID 1220; and the satellite ID is the satellite ID 330 or the satellite ID 1230. Generating may comprise receiving, processing, preparing for forwarding, and forwarding. At step 1620, the GS 140 transmits the message to the first satellite 110. The GS 140 may do so either directly to the first satellite 110 or indirectly through the second satellite 120, other satellites, or other ground networks or GSs. Though the method 1600 describes control instructions, the GS 140 may communicate other, non-control messages with the first satellite 110 and the second satellite 120. [0106] The method 1600 may implement additional embodiments. Specifically, the control instructions can comprise second addressing of the second satellite 120, comprise second orbital information of the second satellite 120, and instruct the first satellite 110 to update a data structure of the first satellite 110 with the second addressing and the second orbital information. For instance, the second addressing comprises the first simplified addressing structure 300 or the second simplified addressing structure 1200; the second orbital information is e, a, i, W, co, tO, and v; and the data structure is a lookup table like Table 1. The method 1600 further comprises detecting a phenomenon affecting the first satellite and updating the first orbital information in response to the phenomenon, and the control instructions comprise updated first orbital information of the first satellite and instruct the first satellite to update a data structure of the first satellite with the updated first orbital information. For instance, the phenomenon is air resistance, a solar wind, or another phenomenon; and the data structure is a lookup table like Table 1.

[0107] FIG. 17 is a schematic diagram of an apparatus 1700. The apparatus 1700 may implement the disclosed embodiments. The apparatus 1700 comprises ingress ports 1710 and an RX 1720 or receiving means to receive data; a processor, 1730 or processing means, or logic unit, baseband unit, or CPU, to process the data; a TX 1740 or transmitting means and egress ports 1750 to transmit the data; and a memory 1760 or data storing means to store the data. The apparatus 1700 may also comprise OE components, EO components, or RF components coupled to the ingress ports 1710, the RX 1720, the TX 1740, and the egress ports 1750 to provide ingress or egress of optical signals, electrical signals, or RF signals.

[0108] The processor 1730 is any combination of hardware, middleware, firmware, or software. The processor 1730 comprises any combination of one or more CPU chips, cores, FPGAs, ASICs, or DSPs. The processor 1730 communicates with the ingress ports 1710, the RX 1720, the TX 1740, the egress ports 1750, and the memory 1760. The processor 1730 comprises a satellite network addressing component 1770, which implements the disclosed embodiments. The inclusion of the satellite network addressing component 1770 therefore provides a substantial improvement to the functionality of the apparatus 1700 and effects a transformation of the apparatus 1700 to a different state. Alternatively, the memory 1760 stores the satellite network addressing component 1770 as instructions, and the processor 1730 executes those instructions. [0109] The memory 1760 comprises any combination of disks, tape drives, or solid-state drives. The apparatus 1700 may use the memory 1760 as an over- flow data storage device to store programs when the apparatus 1700 selects those programs for execution and to store instructions and data that the apparatus 1700 reads during execution of those programs. The memory 1760 may be volatile or non-volatile and may be any combination of ROM, RAM, TCAM, or SRAM. [0110] A computer program product may comprise computer-executable instructions for storage on a non-transitory medium and that, when executed by a processor, cause an apparatus to perform any of the embodiments. The non-transitory medium may be the memory 1760, the processor may be the processor 1730, and the apparatus may be the apparatus 1700.

[0111] While several embodiments have been provided in the present disclosure, it may be understood that the disclosed systems and methods might be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.

[0112] In addition, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, components, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled may be directly coupled or may be indirectly coupled or communicating through some interface, device, or intermediate component whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and may be made without departing from the spirit and scope disclosed herein.

Claims

CLAIMS What is claimed is:

1. A method comprising: generating a message comprising addressing, wherein the addressing is for a first satellite and is associated with first orbital information of the first satellite or the addressing is for a second satellite and is associated with second orbital information of the second satellite; and transmitting the message to the second satellite.

2. The method of claim 1, wherein the first satellite implements the method.

3. The method of claim 1, wherein a ground station (GS) implements the method.

4. The method of claims 1-3, wherein the addressing is for the second satellite and is associated with the second orbital information, and wherein the method further comprises: determining the second orbital information based on the addressing; calculating a beam direction based on the second orbital information; and further transmitting the message using the beam direction.

5. The method of any of claims 1-4, wherein the second orbital information comprises at least one of an eccentricity (e), a semimajor axis (a), an inclination (i), a longitude of an ascending node (W), an argument of periapsis (co), an epoch time when other parameters are measured (tO), or a position or a true anomaly (v).

6. The method of any of claims 1-5, wherein the addressing comprises an orbital plane identifier (ID).

7. The method of any of claims 1-6, wherein the orbital plane ID identifies an orbital plane and is sequentially numbered from a reference orbital plane ID identifying a reference orbital plane.

8. The method of any of claims 1-7, wherein the addressing comprises an orbital plane ID, wherein the orbital plane ID comprises an orbital group ID and an orbital plane sub-ID, wherein the orbital group ID identifies an orbital group that an orbit belongs to, and wherein the orbital plane sub-ID identifies an orbital plane in the orbital group.

9. The method of any of claims 1-8, wherein the addressing further comprises a satellite ID.

10. The method of any of claims 1-9, wherein the satellite ID identifies a satellite within an orbital plane and is sequentially numbered from a reference satellite ID identifying a reference satellite.

11. The method of any of claims 1-10, wherein the addressing further comprises an interface ID.

12. The method of any of claims 1-11, wherein the interface ID identifies one of five interfaces of a satellite.

13. The method of any of claims 1-12, wherein the addressing further comprises a network ID.

14. The method of any of claims 1-13, wherein the network ID identifies a jurisdiction or a network within that jurisdiction.

15. The method of any of claims 1-14, wherein the addressing further comprises an organizationally unique identifier (OUI).

16. The method of any of claims 1-15, wherein the OUI uniquely identifies a vendor, a manufacturer, or another organization associated with a satellite.

17. The method of any of claims 1-16, wherein the addressing is 32 bits.

18. The method of any of claims 1-17, wherein the message further comprises an Internet Protocol version 4 (IPv4) header, wherein the IPv4 header comprises the addressing, and wherein part of the addressing replaces a source address and a destination address in the IPv4 header.

19. The method of any of claims 1-18, wherein the message further comprises an Internet Protocol version 6 (IPv6) header, and wherein the IPv4 header is embedded in the IPv6 header.

20. The method of any of claims 1-19, wherein the message further comprises a New Internet Protocol (IP) header, and wherein the IPv4 header is embedded in the New IP header.

21. The method of any of claims 1-20, wherein the message further comprises an Ethernet medium access control (MAC) address, and wherein the Ethernet MAC address comprises the addressing.

22. A first satellite comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of claims 1-21.

23. A computer program product comprising computer-executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a first satellite to perform any of claims 1-21.

24. A ground station (GS) comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of claims 1-21.

25. A computer program product comprising computer-executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a ground station (GS) to perform any of claims 1-21.

26. A method implemented by a first satellite and comprising: receiving a message from a second satellite; parsing the message to obtain an actual orbital plane identifier (ID) of the message and an actual satellite ID of the message; determining a peer position of the second satellite based on a beam direction of the message; determining an expected orbital plane ID of the second satellite and an expected satellite ID of the second satellite; and performing authentication by at least one of comparing the actual orbital plane ID to the expected orbital plane ID or comparing the actual satellite ID to the expected satellite ID.

27. The method of claim 26, wherein the authentication is of the message and the second satellite.

28. The method of claim 27, further comprising processing the message when the authentication succeeds.

29. The method of any of claims 26-28, further comprising communicating with the second satellite when the authentication succeeds.

30. The method of any of claims 26-29, further comprising discarding the message when the authentication fails.

31. The method of any of claims 26-30, further comprising reporting the second satellite to a ground station (GS) when the authentication fails.

32. A first satellite comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of claims 26-31.

33. A computer program product comprising computer-executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a first satellite to perform any of claims 26-31.

34. A method implemented by a ground station (GS) and comprising: generating a message comprising first addressing and control instructions, wherein the first addressing is for a first satellite and is associated with first orbital information of the first satellite, wherein the first addressing comprises an orbital plane ID of the first satellite or a satellite ID of the first satellite, and wherein the control instructions are configured to control the first satellite; and transmitting the message to the first satellite.

35. The method of claim 34, wherein the control instructions comprise second addressing of a second satellite, comprise second orbital information of the second satellite, and instruct the first satellite to update a data structure of the first satellite with the second addressing and the second orbital information.

36. The method of any of claims 34-35, further comprising: detecting a phenomenon affecting the first satellite; and updating the first orbital information in response to the phenomenon, wherein the control instructions comprise updated first orbital information of the first satellite and instruct the first satellite to update a data structure of the first satellite with the updated first orbital information.

37. A ground station (GS) comprising: a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to perform any of claims 34-36.

38. A computer program product comprising computer-executable instructions that are stored on a non-transitory medium and that, when executed by a processor, cause a ground station (GS) to perform any of claims 34-36.