|
Size: 3574
Comment:
|
Size: 11267
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| The first server-sat arrays will be deployed in a "4 hour" orbit, or more precisely a 23.9344696/6 = 3.989078 hour or 14360.7 second orbit (sidereal). This means it passes over the same spot on earth 5 times per day ( = 6-1, the earth is turning underneath once per sidereal1.26E day ). A 4 hour equatorial circular orbit has a radius of 12770 kilometers, and an altitude above the equator of 6399 kilometers. This puts it in a "thinner" part of the Van Allen belt, with an estimated unshielded radiation dose of 1Mrad/year [citation needed]. | {{attachment:elevation.png}} |
| Line 5: | Line 5: |
| At that altitude, the central orbit can be seen at 58 degrees north and south latitude, at a distance of 10500 km. The round trip ping time is 70 milliseconds. The ground ping time through optical fiber across the United States is faster in theory, but ground networks are slowed by switches and indirect routes. Ping times from fat-pipe servers in Dallas Texas to mit.edu are 42 milliseconds , and to orst.edu are 49 milliseconds, so 70msec is not way out of line. However, much of the routing will travel "around the cloud", and without local caching in the "near" links, some pings may need as much as 200 milliseconds to hop from the far side of the orbit. Still, this is better than the 250+ millisecond ping time through a geosynchronous satellite. | [[EarthOrbits|here is a general discussion of orbits]]. |
| Line 7: | Line 7: |
| Server-sats will actually be deployed in very slightly inclined and elliptical orbits, which map onto a nested set of torii ("torus-es") centered on the 4 hour, zero-inclination equatorial orbit. These are 4 hour orbits as well, and the largest torii are have major radii slightly offset inwards. A plane drawn perpendicularly to the center orbit (which intercepts the orbit in two places, and also intersects the center of the earth) will have "territories" marked on it for the regions around the various orbits, and the orbits passing through each "territory" can be treated as a property. This orbital property is further subdivided into angles around the orbit. Server-sats precisely positioned in each orbit will never intersect server-sats in other properties. Arrays in orbits in the same "property" will never intersect the orbits of arrays in different properties. This allows a large region of space to be filled with server-sats, potentially trillions of them. The density is limited by shading - at some point server-sats closer to the sun will reduce the daylight falling on the ones in the "back" of the orbit, and may begin to detectably reduce the sunlight falling on the earth. | The first server-sat arrays will be deployed in a "4 hour" orbit, or more precisely a 23.9344696/6 = 3.989078 hour or 14360.7 second orbit (sidereal). This means it passes over the same spot on earth 5 times per day ( = 6-1, the earth is turning underneath once per sidereal day ), for a repeat time relative to the ground of 288 minutes (which we will call an m288 orbit). A 4 hour equatorial circular orbit has a radius of 12789 kilometers, and an altitude above the equator of 6411 kilometers. This puts it in a "thinner" part of the Van Allen belt, with an estimated unshielded radiation dose of 1Mrad/year [citation needed]. |
| Line 9: | Line 9: |
| Serversats will be spaced perhaps 100 meters apart in an array - an array with 32768 server-sats will be 3.2km on a side. This puts them far enough apart that the shade area behind one 0.3 meter diameter server-sat will never completely block sunlight to the server-sat behind it. If the nested torri extend outwards to 500 km around the central orbit, that is a spatial volume of 3E10 cubic kilometers. Potentially, that is room for 30 trillion server-sats at a 100 meter spacing. This "fuzzy toroidal cloud" of server-sats will block some sunlight, both to the server-sats in the back of the toroidal cloud, and to the surface of the earth. With 30 trillion 300mm diameter server-sats, the blockage would be about 7% at noontime on the equator. However, it is hard to imagine needing that many server-sats, even if they were operating mostly as space solar power satellites, beaming about 5 watts each to the ground, as that far exceeds the projected world demand for electricity. | Relative to a position on the earth, a server-sat will be visible in the same position 5 times per solar day, at intervals of 288 minutes. The constellation of associated orbits will therefore be called the '''m288''' constellation. Of course, higher and lower orbit constellations are possible, though they will get more radiation. The m240 constellation will repeat 6 times per day, and the m360 constellation will repeat 4 times per day. For reasons that will become apparent, it is important that the orbital period is an integer fraction of a day. |
| Line 11: | Line 11: |
| The m288 central orbit can be seen at 58 degrees north and south latitude, at a distance of 10500 km. The round trip ping time is 70 milliseconds. The ground ping time through optical fiber across the United States is faster in theory, but ground networks are slowed by switches and indirect routes. Ping times from fat-pipe servers in Dallas Texas to mit.edu are 42 milliseconds , and to orst.edu are 49 milliseconds, so 70msec is not way out of line. However, much of the routing will travel "around the cloud", and without local caching in the "near" links, some pings may need as much as 200 milliseconds to hop from the far side of the orbit. Still, this is better than the 250+ millisecond ping time through a geosynchronous satellite. | |
| Line 12: | Line 13: |
| Server-sats will actually be deployed in very slightly inclined and elliptical orbits, which map onto a nested set of tori ("torus-es") centered on the 4 hour, zero-inclination equatorial orbit. These are 4 hour orbits as well, and the largest tori are have major radii slightly offset inwards. A plane drawn perpendicularly to the center orbit (which intercepts the orbit in two places, and also intersects the center of the earth) will have "territories" marked on it for the regions around the various orbits, and the orbits passing through each "territory" can be treated as a property. This orbital property is further subdivided into angles around the orbit. Server-sats precisely positioned in each orbit will never intersect server-sats in other properties. Arrays in orbits in the same "property" will never intersect the orbits of arrays in different properties. This allows a large region of space to be filled with server-sats, potentially trillions of them. The density is limited by shading - at some point server-sats closer to the sun will reduce the daylight falling on the ones in the "back" of the orbit, and may begin to detectably reduce the sunlight falling on the earth. {{attachment:eclipse.png}} === Shading === Server-sats will be spaced perhaps 100 meters apart in an array - an array with 32768 server-sats will be 3.2km on a side. This puts them far enough apart that the shade area behind one 0.3 meter diameter server-sat will never completely block sunlight to the server-sat behind it. If the nested tori extend outwards to 500 km around the central orbit, that is a spatial volume of 6E10 cubic kilometers. Potentially, that is room for 60 trillion server-sats at an average 100 meter spacing. This "fuzzy toroidal cloud" of server-sats will block some sunlight, both to the server-sats in the back of the toroidal cloud, and to the surface of the earth. With 60 trillion 300mm diameter server-sats, the light blockage to the ground would be about 14% at noontime near the equator, with the blockage zone following winter as shown above. The blockage of back server-sats near the sides of the orbit would be more severe - at the equinoxes, it could be as much as 95% for portions of a fully populated array. However, it is hard to imagine needing that many server-sats, even if they were operating mostly as space solar power satellites, beaming about 5 watts each to the ground, as that far exceeds the projected world demand for electricity. With a "mere" 10 trillion server-sats, the blockages would be 2% to the ground and 38% to the back of the array. Also, for power production (and one-way information broadcast) ping time is no longer an issue, so m360 and higher orbits can be used. === Elevation above the horizon, interference with geosynchronous satellites === Assume that the first torus to be filled with arrays is at a minor radius of 200km from the central orbit. Refraction will lift the apparent elevation of the central orbit a few degrees above the horizon, so a south-facing antenna at 60 degrees north or south may be able to see the edges of the torus. However, ground sites further north or south of the central band may need to relay through other satellites, or through landlines on the ground. For latitudes between 10 degrees north or south, the torus will have similiar ground antenna elevation angles as geosynchronous satellites. Assuming that the same satellite frequency bands are used for server-sky as for existing geosynchronous services, latitudes between 10 degrees and 60 degrees north and 10 degrees and 60 degrees south should be able to make direct use of server-sky. === Intentional gaps in the constellation === The orbits will not be completely filled - there will be large gaps in them to permit transit of launch vehicles. Establishing these "windows" will involve lots of negotiation, beyond the scope of this document. If it ever proves practical to build space elevators, there will need to be other gaps in time and "property" so that the elevators and the server-sats never interact. A failing space elevator will collide with an undetermined number of server-sats (as well as destroying all the other space elevators), so space elevators and the permanent use of these orbits (or possibly any near-earth orbit) may prove incompatible. In the short term, there will be millions, not trillions, of server-sats. They should still be assigned positions and orbits compatible with a much more crowded sky. It is good to know, going into this, that the region available for well behave server-sky orbits offers much room for growth. === Defining Property Within the m288 toroid === All server sky orbits in the m288 toroid will have the same identical semi-major axis, and hence the same identical 288 minute synoptic period, and the same 14393 second sidereal period. If the orbits are mapped correctly, every item in them will maintain the same approximate spacing to neighbors in three dimensions, even as the whole constellation makes one orbit around the earth and one "short axis rotation" around the central orbit. This allows very large numbers of server-sats to be deployed in the 60 billion cubic kilometers of server sky. Properties can be assigned much like IPV6 address space is assigned by ICANN - indeed, we may map IPV6 addresses onto particular orbital volumes, and know where in the sky a particular server-sat is from its IPV6 address, or vice versa. If we map down to one meter cubes, we will need about 65 bits of address space. The space does not map in a rigidly cartesian way; the "toroids" we are mapping on are slightly distorted from perfectly circular minor cross sections, as shown: || {{attachment:section500.png}} || 500km cross section of nested torii around the m288, 12789km central orbit region. The outer orbits shown have an eccentricity of 0.039 and an inclination of 2.24 degrees. Although these torus cross sections look circular, they are actually distorted by as much as 3 kilometers from perfect circles. The outer torus has a volume of about 60 billion cubic kilometers. The inner torus, with a radius of 100km, has a volume of 2.5 billion cubic kilometers. || || {{attachment:section5000.png}} || 5000km cross section of nested torii around the m288, 12789km central orbit region. The outer orbits shown have an eccentricity of 0.39 and an inclination of 23 degrees. The edge of the earth is to the left. These unusually broad toruses demonstrate the distortion that occurs in outer orbits. The outer torus has a volume of about 6 trillion cubic kilometers (the earth is 1.09 trillion cubic kilometers), a perigee of 1411 kilometers altitude, and intercepts the orbits of many existing satellites and large debris objects, so such large torii should not actually be used. || In addition, objects in the orbits will be advanced or delayed because of increased velocity at perigee and decreased velocity at apogee. This tends to spread objects near perigee (in the line of the orbit) by 1+eccentricity, and near apogee by 1-eccentricity. Thus, the volume elements will lengthen and shorten, and distort trapezoidally (proportional to the eccentricity, or the toroidal minor radius divided by the major radius) as they travel around the orbit. The arrays within those volumes will distort proportionally. The below figure shows 3 orbits with 4 objects in each orbit, spaced at 0.25 times the period. The minor radius of the torus is greatly exaggerated. {{ attachment:orbits_on_torus.png}} To fill a "torus" with a 3x3 square of orbits, add a rotated copy of the figure by 90 degrees, then rotate the pair by 45 degrees and expand the minor radius by sqrt(2). Then subtract the 3 duplicate central orbits. Repeat at larger spacings, add additional objects on each orbit, and the result is a filled torus (or whatever). This is based on a rectangular cartesian grid mapped into a circle at one angle from the equator to the fixed stars - the prime meridian seems like a good candidate. Other grids, such as triangular/hexagonal, can be mapped within the same circle (a cross-section of the largest torus). {{ attachment:orbit_grids.png}} ||{{ attachment:hammer.gif}}|| Assigning orbits within this map can be done many ways - by an organization like ICANN, perhaps working outwards from the center in the order of assignment.<<BR>><<BR>>An intriguing alternative is to map the surface of the globe onto a circle, and then assign orbits to the countries that fall on that mapping. That leaves open spaces in between, in the areas of the globe that are ocean (and on the map) for navigation in space.<<BR>><<BR>>Here is one such mapping, an [[http://en.wikipedia.org/wiki/Hammer_projection| Ernst Hammer equal area projection.]]. It has been modified from an ellipse to a circle. Other possibilities include the [[http://en.wikipedia.org/wiki/Mollweide_projection|Mollweide_projection.]] A more abstract projection that exaggerates continental areas, regularizes passages through the orbit torus, etc. are also possible.|| |
Deployment Orbits
here is a general discussion of orbits.
The first server-sat arrays will be deployed in a "4 hour" orbit, or more precisely a 23.9344696/6 = 3.989078 hour or 14360.7 second orbit (sidereal). This means it passes over the same spot on earth 5 times per day ( = 6-1, the earth is turning underneath once per sidereal day ), for a repeat time relative to the ground of 288 minutes (which we will call an m288 orbit). A 4 hour equatorial circular orbit has a radius of 12789 kilometers, and an altitude above the equator of 6411 kilometers. This puts it in a "thinner" part of the Van Allen belt, with an estimated unshielded radiation dose of 1Mrad/year [citation needed].
Relative to a position on the earth, a server-sat will be visible in the same position 5 times per solar day, at intervals of 288 minutes. The constellation of associated orbits will therefore be called the m288 constellation. Of course, higher and lower orbit constellations are possible, though they will get more radiation. The m240 constellation will repeat 6 times per day, and the m360 constellation will repeat 4 times per day. For reasons that will become apparent, it is important that the orbital period is an integer fraction of a day.
The m288 central orbit can be seen at 58 degrees north and south latitude, at a distance of 10500 km. The round trip ping time is 70 milliseconds. The ground ping time through optical fiber across the United States is faster in theory, but ground networks are slowed by switches and indirect routes. Ping times from fat-pipe servers in Dallas Texas to mit.edu are 42 milliseconds , and to orst.edu are 49 milliseconds, so 70msec is not way out of line. However, much of the routing will travel "around the cloud", and without local caching in the "near" links, some pings may need as much as 200 milliseconds to hop from the far side of the orbit. Still, this is better than the 250+ millisecond ping time through a geosynchronous satellite.
Server-sats will actually be deployed in very slightly inclined and elliptical orbits, which map onto a nested set of tori ("torus-es") centered on the 4 hour, zero-inclination equatorial orbit. These are 4 hour orbits as well, and the largest tori are have major radii slightly offset inwards. A plane drawn perpendicularly to the center orbit (which intercepts the orbit in two places, and also intersects the center of the earth) will have "territories" marked on it for the regions around the various orbits, and the orbits passing through each "territory" can be treated as a property. This orbital property is further subdivided into angles around the orbit. Server-sats precisely positioned in each orbit will never intersect server-sats in other properties. Arrays in orbits in the same "property" will never intersect the orbits of arrays in different properties. This allows a large region of space to be filled with server-sats, potentially trillions of them. The density is limited by shading - at some point server-sats closer to the sun will reduce the daylight falling on the ones in the "back" of the orbit, and may begin to detectably reduce the sunlight falling on the earth.
Shading
Server-sats will be spaced perhaps 100 meters apart in an array - an array with 32768 server-sats will be 3.2km on a side. This puts them far enough apart that the shade area behind one 0.3 meter diameter server-sat will never completely block sunlight to the server-sat behind it. If the nested tori extend outwards to 500 km around the central orbit, that is a spatial volume of 6E10 cubic kilometers. Potentially, that is room for 60 trillion server-sats at an average 100 meter spacing. This "fuzzy toroidal cloud" of server-sats will block some sunlight, both to the server-sats in the back of the toroidal cloud, and to the surface of the earth. With 60 trillion 300mm diameter server-sats, the light blockage to the ground would be about 14% at noontime near the equator, with the blockage zone following winter as shown above. The blockage of back server-sats near the sides of the orbit would be more severe - at the equinoxes, it could be as much as 95% for portions of a fully populated array. However, it is hard to imagine needing that many server-sats, even if they were operating mostly as space solar power satellites, beaming about 5 watts each to the ground, as that far exceeds the projected world demand for electricity. With a "mere" 10 trillion server-sats, the blockages would be 2% to the ground and 38% to the back of the array. Also, for power production (and one-way information broadcast) ping time is no longer an issue, so m360 and higher orbits can be used.
Elevation above the horizon, interference with geosynchronous satellites
Assume that the first torus to be filled with arrays is at a minor radius of 200km from the central orbit. Refraction will lift the apparent elevation of the central orbit a few degrees above the horizon, so a south-facing antenna at 60 degrees north or south may be able to see the edges of the torus. However, ground sites further north or south of the central band may need to relay through other satellites, or through landlines on the ground. For latitudes between 10 degrees north or south, the torus will have similiar ground antenna elevation angles as geosynchronous satellites. Assuming that the same satellite frequency bands are used for server-sky as for existing geosynchronous services, latitudes between 10 degrees and 60 degrees north and 10 degrees and 60 degrees south should be able to make direct use of server-sky.
Intentional gaps in the constellation
The orbits will not be completely filled - there will be large gaps in them to permit transit of launch vehicles. Establishing these "windows" will involve lots of negotiation, beyond the scope of this document.
If it ever proves practical to build space elevators, there will need to be other gaps in time and "property" so that the elevators and the server-sats never interact. A failing space elevator will collide with an undetermined number of server-sats (as well as destroying all the other space elevators), so space elevators and the permanent use of these orbits (or possibly any near-earth orbit) may prove incompatible.
In the short term, there will be millions, not trillions, of server-sats. They should still be assigned positions and orbits compatible with a much more crowded sky. It is good to know, going into this, that the region available for well behave server-sky orbits offers much room for growth.
Defining Property Within the m288 toroid
All server sky orbits in the m288 toroid will have the same identical semi-major axis, and hence the same identical 288 minute synoptic period, and the same 14393 second sidereal period. If the orbits are mapped correctly, every item in them will maintain the same approximate spacing to neighbors in three dimensions, even as the whole constellation makes one orbit around the earth and one "short axis rotation" around the central orbit. This allows very large numbers of server-sats to be deployed in the 60 billion cubic kilometers of server sky. Properties can be assigned much like IPV6 address space is assigned by ICANN - indeed, we may map IPV6 addresses onto particular orbital volumes, and know where in the sky a particular server-sat is from its IPV6 address, or vice versa. If we map down to one meter cubes, we will need about 65 bits of address space.
The space does not map in a rigidly cartesian way; the "toroids" we are mapping on are slightly distorted from perfectly circular minor cross sections, as shown:
|
500km cross section of nested torii around the m288, 12789km central orbit region. The outer orbits shown have an eccentricity of 0.039 and an inclination of 2.24 degrees. Although these torus cross sections look circular, they are actually distorted by as much as 3 kilometers from perfect circles. The outer torus has a volume of about 60 billion cubic kilometers. The inner torus, with a radius of 100km, has a volume of 2.5 billion cubic kilometers. |
|
5000km cross section of nested torii around the m288, 12789km central orbit region. The outer orbits shown have an eccentricity of 0.39 and an inclination of 23 degrees. The edge of the earth is to the left. These unusually broad toruses demonstrate the distortion that occurs in outer orbits. The outer torus has a volume of about 6 trillion cubic kilometers (the earth is 1.09 trillion cubic kilometers), a perigee of 1411 kilometers altitude, and intercepts the orbits of many existing satellites and large debris objects, so such large torii should not actually be used. |
In addition, objects in the orbits will be advanced or delayed because of increased velocity at perigee and decreased velocity at apogee. This tends to spread objects near perigee (in the line of the orbit) by 1+eccentricity, and near apogee by 1-eccentricity. Thus, the volume elements will lengthen and shorten, and distort trapezoidally (proportional to the eccentricity, or the toroidal minor radius divided by the major radius) as they travel around the orbit. The arrays within those volumes will distort proportionally.
The below figure shows 3 orbits with 4 objects in each orbit, spaced at 0.25 times the period. The minor radius of the torus is greatly exaggerated.
To fill a "torus" with a 3x3 square of orbits, add a rotated copy of the figure by 90 degrees, then rotate the pair by 45 degrees and expand the minor radius by sqrt(2). Then subtract the 3 duplicate central orbits. Repeat at larger spacings, add additional objects on each orbit, and the result is a filled torus (or whatever). This is based on a rectangular cartesian grid mapped into a circle at one angle from the equator to the fixed stars - the prime meridian seems like a good candidate. Other grids, such as triangular/hexagonal, can be mapped within the same circle (a cross-section of the largest torus).
|
Assigning orbits within this map can be done many ways - by an organization like ICANN, perhaps working outwards from the center in the order of assignment. |
MORE LATER