Internet-Draft | Satellite Semantic Addressing | September 2023 |
Han, et al. | Expires 4 March 2024 | [Page] |
This document presents a semantic addressing method for satellites in satellite constellation connecting with Internet. The satellite semantic address can indicate the relative position of satellites in a constellation. The address can be used with traditional IP address or MAC address or used independently for IP routing and switching.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 4 March 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Satellite constellation technologies for Internet are emerging and expected to provide Internet service like the traditional wired network on the ground. A typical satellite constellation will have couple of thousands or over ten thousand of LEO and/or VLEO. Satellites in a constellation will be connected to adjacent satellites by Inter-Satellite-Links (ISL), and/or connected to ground station by microwave or laser links. ISL is still in research stage and will be deployed soon. This memo is for the satellite networking with the use of ISL.¶
The memo proposes to use some indexes to represent a satellite's orbit information. The indexes can form satellite semantic address, the address can then be embedded into IPv6 address or MAC address for IP routing and switching. The address can also be used independently if the shorter than 128-bit length of IP address is accepted. As an internal address for satellite network, it only applies to satellites that will form a constellation to transport Internet traffic between ground stations and will not be populated to Internet by BGP.¶
For IP based satellite networking, the topology is very dynamic and the traditional IGP and BGP based routing technologies will face challenges according to the analysis in [I-D.lhan-problems-requirements-satellite-net]. From the paper, we can easily categorize satellite links as two types, steady and un-steady. For un-steady links, the link status will be flipping every couple of minutes.¶
Section 5.5 has more details about how to identify different links.¶
Some researches have been done to handle such fast changed topologies. one method to overcome the difficulties for routing with un-steady links is to only use the steady links, and get rid of un-steady links unless it is necessary. For example, for real deployment, only links between satellite and ground stations are mandatory to use, other un-steady links can be avoided in routing and switching algorithms. [Routing-for-LEO] proposed to calculate the shortest path by avoiding un-steady links in polar area and links crossing Seam line since satellites will move in the opposite direction crossing the Seam line.¶
Traditionally, to establish an IP network for satellites, each satellite and its interface between satellites and to ground stations have to be assigned IP addresses (IPv4 or IPv6). The IP address can be either private or public. IP address itself does not mean anything except routing prefix and interface identifier [RFC8200].¶
To utilize the satellite relative position for routing, it is desired that there is an easy way to identify the relative positions of different satellites and identify un-steady links quickly. The traditional IP address cannot provide such functionality unless we have the real-time processing for 3D coordinates of satellites to figure out the relative positions of each satellite, and some math calculation and dynamic database are also needed in routing algorithm to check if a link is steady or not. This will introduce extra data exchanged for routing protocols and burden for the computation in every satellite. Considering the ISL link speed (up to 10G for 2000km) and hardware cost (Radiation-hardened semiconductor components are needed) in satellite are more constraint than for network device on ground, it is expected to simplify the routing algorithm, reduce the requirement of ISL, onboard CPU and memory.¶
The document proposes to form a semantic address by satellite orbit information, and then embedded it into a proper IP address. The IP address of IGP neighbors can directly tell the relative position of different satellites and if links between two satellites are stead or not.¶
The document does not describe the details how the semantic address is used to improve routing and switching or new routing protocols, those will be addressed in different documents. Instructive routing [I-D.lhan-satellite-instructive-routing] is a new proposal to use the semantic address for the routing of large-scale LEO satellite network. It is based on source routing mechnism and meshing characteristics of LEO satellite constellation, using semantic address can reduce the overheader of the instruction for the packet forwarding at each satellite. The complete solution combining the semantic address, the instructive routing and modified OSPF [I-D.retana-lsr-ospf-monitor-node] can be found in [Large-Scale-LEO-Network-Routing].¶
This section will introduce some basics for satellite such as orbit parameters.¶
The orbit of a satellite can be either circular or ecliptic, it can be described by following Keplerian elements [KeplerianElement]:¶
The circular orbit is widely used by proposals of satellite constellation from different companies and countries.¶
For a circular orbit, we will have:¶
So, three parameters, Altitude, Inclination and Longitude of the ascending node, will be enough to describe the orbit. The satellite will move in a constant speed and True anomaly (nu) can be easily calculated after the epoch time is defined.¶
One satellite constellation may be composed of many satellites (LEO and VLEO), but normally all satellites are grouped in a certain order that is never changed during the life of satellite constellation. Each satellite constellation's orbits parameters described in Section 4.1 must be approved by regulator and cannot be changed either. Follows are characters of one satellite constellation:¶
When ISL is used for the communication between satellites, each satellite will have a fixed number of links to connect to its neighbor. Due to the cost of ISL and the constraints of power supply on satellite, the number of ISL is normally limited to connect to its closest neighbors. In 3D space, each satellite may have six types of adjacent satellites, each type represents one direction. The number of adjacent neighbors in one direction is dependent on the number of deployment of ISL device on satellites, for example, the laser transmitter and receiver for ISLL. Figure 1 illustrates satellite S0 and its adjacent neighbors.¶
All adjacent satellites of S0 in Figure 1 are listed below:¶
The relative position of adjacent satellites will directly determine the quality of ISL and communication. From the analysis in [I-D.lhan-problems-requirements-satellite-net], The speed of satellite is only related to the altitude of the satellite (on circular orbit), all satellites with a same altitude will move with the same speed. So, in above adjacent satellites, some adjacent satellite's relative positions are steady and the ISL can be alive without interruption caused by movement. Some adjacent satellites relative positions are changing quickly, the ISL may be down since the distance may become out of reach for the laser of ISL, or the quick changed positions of two satellite make the tracking of laser too hard. Below are details:¶
When ISL is deployed in satellite constellation, all satellites in the constellation can form a network like the wired network on ground. Due to the big number of satellites in a constellation, the network could be either L2 or L3. The document proposes to use L3 network for better scalability.¶
When satellites form a L3 network, it is expected that IP address is needed for each satellite and its ISLs.¶
While the traditional IP address can still be used for satellite network, the document proposes an alternative new method for satellite's addressing system. The new addressing system can indicate a satellite's orbit info such as shell group index, orbit plane index and satellite index. This will make the adjacent satellite identification for link status easier and benefit the routing algorithms.¶
As described in Section 4.2, one satellite has three important orbit related information as described below.¶
It should be noted that for all type of indexes, it is up to the owner to assign the index number. There is no rule for which one should be assigned with which number. The only important rule is that all index number should be in sequential to reflect its relative order and position with others. Below is an example of assignment rules:¶
It should also be noted that for all type of indexes assignment, there are no strict requirement for the physical positions of satellite. Due to the launching time difference, the shifing of the satellite orbit after some time, the orbit parameters of satellites always have some difference and do not follow the theoritical values. For example:¶
Figure 3 and Figure 4 illustrate three types of indexes for satellite¶
Shell Group and Orbit Plane Indexes for Satellites¶
Three types of Index for satellites¶
The ranges of different satellite indexes will determine the range the dedicated field for semantic address. The maximum indexes depend on the number of shell group, orbit plane and satellite per orbit plane. The number of orbit plane and satellite per orbit plane have relationship with the coverage of a satellite constellation. There are minimum numbers required to cover earth. [I-D.lhan-problems-requirements-satellite-net] has given the detailed math to estimate the minimal number required to cover the earth. There are two key parameters that determine the minimal number of satellite required. One is the elevation angle, another is the altitude. StarLink has proposed two elevation angles, 25 and 35 degrees [SpaceX-Non-GEO]. The lowest LEO altitude can be 160km according to [Lowest-LEO-ESA]. The Table 1 and Table 2 illustrate the estimation for different altitude (As), the coverage radius (Rc), the minimal required number of orbit planes (No) and satellite per orbit plane (Ns). The elevation angle is 25 degree and 35 degrees respectively.¶
Parameters | VLEO1 | VLEO2 | LEO1 | LEO2 | LEO3 | LEO4 | LEO5 |
---|---|---|---|---|---|---|---|
As(km) | 160 | 300 | 600 | 900 | 1200 | 1500 | 2000 |
Rc(km) | 318 | 562 | 1009 | 1382 | 1702 | 1981 | 2379 |
Ns | 73 | 42 | 23 | 17 | 14 | 12 | 10 |
No | 85 | 48 | 27 | 20 | 16 | 14 | 12 |
Parameters | VLEO1 | VLEO2 | LEO1 | LEO2 | LEO3 | LEO4 | LEO5 |
---|---|---|---|---|---|---|---|
As(km) | 160 | 300 | 600 | 900 | 1200 | 1500 | 2000 |
Rc(km) | 218 | 392 | 726 | 1015 | 1271 | 1498 | 1828 |
Ns | 107 | 59 | 32 | 23 | 19 | 16 | 13 |
No | 123 | 69 | 37 | 27 | 22 | 18 | 15 |
The real deployment may be different as above analysis. Normally, more satellites and orbit planes are used to provide better coverage. So far, there are only two proposals available, one is StarLink, another is from China Constellation. For proposals of [StarLink], there are 7 shell groups, the number of orbit plane and satellites per orbit plane in all shell groups are 72 and 58; For proposals of [China-constellation], there are 7 shell groups, the number of orbit plane and satellites per orbit plane in all shell groups are 60 and 60;¶
It should be noted that some technical parameters, such as the inclination and altitude of orbit planes, in above proposals may be changed during the long-time deployment period, but the total numbers for indexes normally do not change.¶
From the above analysis, to be conservative, it is safe to conclude that the range of all three satellite indexes are less than 256, or 8-bit number.¶
In addition to three satellite indexes described in Section 5.1, other information is also important and can also be embedded into satellite address:¶
The company or country code, or the owner code. In the future, there may have multiple satellite constellations on the sky from different organizations, and the inter-constellation communication may become as normal that is similar to the network on the ground. This code will be useful to distinguish different satellite constellation and make the inter-constellation communication possible. One satellite constellation will have one code assigned by international regulator (IANA or ITU). Considering the following facts:¶
We can predict the total number of satellite constellation is very limited. So, the size of code is limited. In the draft, we propose to use one octet for Owner code.¶
The encoding for satellite semantic address is dependent on what routing and switching (L2 or L3 solution) technologies are used for satellite networking, and finally dependent on the decision of IETF community.¶
Follows are some initial proposals:¶
Using above satellite semantic addressing scheme, to identify steady and un-steady links is as simple as below:¶
Assuming:¶
Two satellites have:¶
Steady links:¶
The links between adjacent satellites on the same orbit plane, or, the satellite indexes satisfy:¶
The links between satellites on adjacent orbit planes on the same altitude. and two satellites are moving to the same direction, or, the satellite indexes satisfy:¶
Un-Steady links:¶
The links between satellites on adjacent orbit planes on different altitude. Or, the satellite indexes satisfy:¶
Figure 8 illustrates the links for adjacent orbit planes (#2 for Steady Link and Un-steady Link above). From the figure, it can be noticed that some links may have shorter distance than steady link, but they are unsteady. For example, the links between S1 and S4; S4 and S2; S2 and S5, etc.¶
Due to the limit of the picture drawing for IETF draft, the pictures in the memo may not be easy to understand. For easier understanding of the method, please refere to the [Large-Scale-LEO-Network-Routing], it provided more vivid pictures obtained by simulation software Savi [Savi].¶
This memo may include request to IANA for owner code, see Section 5.4.¶
The semantic address for satellite only describes the relative positions of satellites, it does not introduce more security issues compared with the normal IP address. Similar to terrestrial network, a satellite network normally will have different protocols at the different layers, form L1 to L7, to provide the security for a satellite network.¶