Skip to content

Commit 5edb098

Browse files
19BMG0019BMG00
authored
Merge pull request #204109 from MicrosoftDocs/release-ga-orbital
Release ga orbital
2 parents 37e22f5 + 6f155e7 commit 5edb098

18 files changed

+816
-100
lines changed

‎articles/orbital/TOC.yml

Lines changed: 28 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -9,33 +9,41 @@ items:
99
href: space-partner-program-overview.md
1010
- name: Quickstart
1111
items:
12-
- name: Earth Observation
13-
items:
14-
- name: Onboard to the Azure Orbital Preview
15-
href: orbital-preview.md
16-
- name: Register a Spacecraft
17-
href: register-spacecraft.md
18-
- name: Configure a Contact Profile
19-
href: contact-profile.md
20-
- name: Schedule a Contact
21-
href: schedule-contact.md
12+
- name: Register a spacecraft
13+
href: register-spacecraft.md
14+
- name: Configure a contact profile
15+
href: contact-profile.md
16+
- name: Schedule a contact
17+
href: schedule-contact.md
2218
- name: Tutorials
2319
items:
24-
- name: Earth Observation
25-
items:
26-
- name: Update the Spacecraft TLE
27-
href: update-tle.md
28-
- name: Cancel a Contact
29-
href: delete-contact.md
20+
- name: Prepare network to send and receive data
21+
href: prepare-network.md
22+
- name: License your spacecraft
23+
href: license-spacecraft.md
24+
- name: Receive real-time telemetry
25+
href: receive-real-time-telemetry.md
26+
- name: Update the spacecraft TLE
27+
href: update-tle.md
28+
- name: Cancel a contact
29+
href: delete-contact.md
3030
- name: How-to guides
3131
items:
3232
- name: Earth Observation
3333
items:
3434
- name: Schedule a contact with NASA's AQUA public satellite
35-
href: howto-downlink-aqua.md
36-
- name: Collect and Process AQUA satellite payload
35+
href: downlink-aqua.md
36+
- name: Collect and process AQUA satellite payload
3737
href: satellite-imagery-with-orbital-ground-station.md
38+
- name: Integrate partner network ground stations
39+
href: partner-network-integration.md
3840
- name: Concepts
3941
items:
40-
- name: Geospatial Reference Architecture
41-
href: geospatial-reference-architecture.md
42+
- name: Contact
43+
href: concepts-contact.md
44+
- name: Contact profile
45+
href: concepts-contact-profile.md
46+
- name: Geospatial reference architecture
47+
href: geospatial-reference-architecture.md
48+
- name: Spacecraft object
49+
href: spacecraft-object.md

‎articles/orbital/concepts-contact-profile.md

Lines changed: 147 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,147 @@
1+
---
2+
title: Ground station contact profile - Azure Orbital GSaaS
3+
description: Learn more about the contact profile object, including how to create, modify, and delete the profile.
4+
author: hrshelar
5+
ms.service: orbital
6+
ms.topic: conceptual
7+
ms.custom: ga
8+
ms.date: 06/21/2022
9+
ms.author: hrshelar
10+
#Customer intent: As a satellite operator or user, I want to understand how to use the contact profile so that I can take passes using the GSaaS service.
11+
---
12+
13+
# Ground station contact profile
14+
15+
The contact profile object stores pass requirements such as links and endpoint details for each link. Use this object with the spacecraft object at time of scheduling to view and schedule available passes.
16+
17+
You can create many contact profiles to represent different types of passes depending on your mission operations. For example, you can create a contact profile for a command and control pass or a contact profile for a downlink only pass.
18+
19+
These objects are mutable and don't undergo an authorization process like the spacecraft objects do. One contact profile can be used with many spacecraft objects.
20+
21+
See [how to configure a contact profile](contact-profile.md) for the full list of parameters.
22+
23+
## Prerequisites
24+
25+
- Subnet that is created in the VNET and resource group you desire. See [Prepare network for Orbital GSaaS integration.](prepare-network.md)
26+
27+
## Creating a contact profile
28+
29+
Follow the steps in [how to create a contact profile.](contact-profile.md).
30+
31+
## Adjusting pass parameters
32+
33+
Specify a minimum pass time to ensure passes of a certain duration. Specify a minimum elevation to ensure passes above a certain elevation.
34+
35+
The two parameters above are used by the service during the contact scheduling. Avoid changing these on a pass-by-pass basis and create multiple contact profiles if you need such flexibility.
36+
37+
At the moment autotrack is disabled and autotracking options are not applied.
38+
39+
## Understanding links and channels
40+
41+
A whole band, unique in direction, and unique in polarity is called a link. Channels, which are children under links, specify center frequency, bandwidth, and endpoints. Typically there's only one channel per link but some applications require multiple channels per link. Refer to the Ground Station manual for a full list of supported bands and antenna capabilities.
42+
43+
You can specify an EIRP and G/T requirement for each link. EIRP applies to uplinks and G/T applies to downlinks. You can give a name to each link and channel to keep track of these properties.
44+
45+
Look at the example below to see how to specify an RHCP channel and an LHCP channel if your mission requires dual-polarization on downlink.
46+
47+
```json
48+
{
49+
"location": "eastus2",
50+
"tags": null,
51+
"id": "/subscriptions/c1be1141-a7c9-4aac-9608-3c2e2f1152c3/resourceGroups/contoso-Rgp/providers/Microsoft.Orbital/contactProfiles/CONTOSO-CP",
52+
"name": "CONTOSO-CP",
53+
"type": "Microsoft.Orbital/contactProfiles",
54+
"properties": {
55+
"provisioningState": "Succeeded",
56+
"minimumViableContactDuration": "PT1M",
57+
"minimumElevationDegrees": 5,
58+
"autoTrackingConfiguration": "disabled",
59+
"eventHubUri": "/subscriptions/c1be1141-a7c9-4aac-9608-3c2e2f1152c3/resourceGroups/contoso-Rgp/providers/Microsoft.EventHub/namespaces/contosoHub/eventhubs/contosoHub",
60+
"networkConfiguration": {
61+
"subnetId": "/subscriptions/c1be1141-a7c9-4aac-9608-3c2e2f1152c3/resourceGroups/contoso-Rgp/providers/Microsoft.Network/virtualNetworks/contoso-vnet/subnets/orbital-delegated-subnet"
62+
},
63+
"links": [
64+
{
65+
"name": "contoso-downlink-rhcp",
66+
"polarization": "RHCP",
67+
"direction": "downlink",
68+
"gainOverTemperature": 25,
69+
"eirpdBW": 0,
70+
"channels": [
71+
{
72+
"name": "contoso-downlink-channel-rhcp",
73+
"centerFrequencyMHz": 8160,
74+
"bandwidthMHz": 15,
75+
"endPoint": {
76+
"ipAddress": "10.1.0.5",
77+
"endPointName": "ContosoTest_Downlink_RHCP",
78+
"port": "51103",
79+
"protocol": "UDP"
80+
},
81+
"modulationConfiguration": null,
82+
"demodulationConfiguration": null,
83+
"encodingConfiguration": null,
84+
"decodingConfiguration": null
85+
}
86+
]
87+
}
88+
{
89+
"name": "contoso-downlink-lhcp",
90+
"polarization": "LHCP",
91+
"direction": "downlink",
92+
"gainOverTemperature": 25,
93+
"eirpdBW": 0,
94+
"channels": [
95+
{
96+
"name": "contoso-downlink-channel-lhcp",
97+
"centerFrequencyMHz": 8160,
98+
"bandwidthMHz": 15,
99+
"endPoint": {
100+
"ipAddress": "10.1.0.5",
101+
"endPointName": "ContosoTest_Downlink_LHCP",
102+
"port": "51104",
103+
"protocol": "UDP"
104+
},
105+
"modulationConfiguration": null,
106+
"demodulationConfiguration": null,
107+
"encodingConfiguration": null,
108+
"decodingConfiguration": null
109+
}
110+
]
111+
}
112+
]
113+
}
114+
}
115+
```
116+
117+
118+
## Applying modems or bring your own
119+
120+
We recommend taking advantage of Orbital's GSaaS software modem functionality if possible. This modem is managed by the service and is inserted between your endpoint and the incoming or outgoing virtual RF stream per channel. We have a library of modems that will be available in the marketplace for you to utilize. If there is no modem that can be used with your application then utilize the virtual RF delivery feature to bring your own modem.
121+
122+
There are 4 parameters related to modem configurations. The table below shows you how to configure these parameters.
123+
124+
| Parameter | Options |
125+
|---------------------------|-----------------------------------------------------------------------------|
126+
| modulationConfiguration | 1. Null for virtual RF<br />2. JSON escaped modem config for software modem |
127+
| demodulationConfiguration | 1. Null for virtual RF<br />2. JSON escaped modem config for software modem |
128+
| encodingConfiguration | Null (not used) |
129+
| decodingConfiguration | Null (not used) |
130+
131+
Use the same modem config file in uplink and downlink channels for full-duplex communications in the same band.
132+
133+
The modem config should be a JSON escaped raw save file from a software modem. Please see the marketplace for modem options.
134+
135+
## Modifying or deleting a contact profile
136+
137+
You can modify or delete the contact profile via the Portal or through the API.
138+
139+
## Configuring contact profile for third party ground stations
140+
141+
When you onboard a third party network, you'll receive a token that identifies your profile. Use this token in the object to link a contact profile to the third party network.
142+
143+
## Next steps
144+
145+
- [Quickstart: Schedule a contact](schedule-contact.md)
146+
- [How to: Update the Spacecraft TLE](update-tle.md)
147+

‎articles/orbital/concepts-contact.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Ground station contact - Azure Orbital GSaSS
3+
description: Learn more about the contact object and how to schedule a contact.
4+
author: hrshelar
5+
ms.service: orbital
6+
ms.topic: conceptual
7+
ms.custom: ga
8+
ms.date: 06/21/2022
9+
ms.author: hrshelar
10+
#Customer intent: As a satellite operator or user, I want to understand how to what the contact object is so I can manage my mission operations.
11+
---
12+
13+
# Ground station contact
14+
15+
A contact occurs when the spacecraft is over a specified ground station. You can find available passes on the system and schedule them for use through Azure Orbital GSaaS. A contact and ground station pass mean the same thing.
16+
17+
When you schedule a contact, a contact object is created under your spacecraft object in your resource group. The contact only associated with this spacecraft and can't be transferred to another spacecraft, resource group, or region.
18+
19+
## Contact object
20+
21+
The contact object contains the start time and end time of the pass and other parameters of interest related to pass operations. The full list is below.
22+
23+
| Parameter | Description |
24+
|---------------------------|--------------------------------------------------------------------------------------------------------------------------------|
25+
| Reservation Start Time | Start time of pass in UTC. |
26+
| Reservation End Time | End time of pass in UTC. |
27+
| Maximum Elevation Degrees | The maximum elevation the spacecraft will be in the sky relative to horizon in degrees, used to gauge the quality of the pass. |
28+
| TX Start Time | Start time of permissible transmission window in UTC. This start time will be equal to or come after Reservation Start Time. |
29+
| TX End Time | End time of permissible transmission window in UTC. This end time will be equal to or come before Reservation End Time. |
30+
| RX Start Time | Start time of permissible reception window in UTC. This start time will be equal to or come after Reservation Start Time. |
31+
| RX End Time | End time of permissible reception window in UTC. This end time will be equal to or come before Reservation End Time. |
32+
| Start Azimuth | Starting azimuth position of the spacecraft measured clockwise from North in degrees. |
33+
| End Azimuth | End azimuth position of the spacecraft measured clockwise from North in degrees. |
34+
| Start Elevation | Starting elevation position of the spacecraft measured from the horizon up in degrees. |
35+
| End Elevation | Starting elevation position of the spacecraft measured from the horizon up in degrees. |
36+
37+
The RX and TX start/end times may differ depending on the individual station masks. Billing meters are engaged between the Reservation Start Time and Reservation End Time.
38+
39+
## Creating a contact
40+
41+
In order to create a contact, you must have the following pre-requisites:
42+
43+
* Authorized spacecraft object
44+
* Contact profile with links in accordance with the spacecraft object above
45+
46+
Contacts are created on a per pass and per ground station basis. If you already know the pass timings for your spacecraft and selected ground station, then you can directly proceed to schedule the pass with these times. The service will succeed in creating the contact object if the window is available and fail if it isn't.
47+
48+
If you don't know the pass timings, or which sites are available, then you can use the portal or API to get those details. Query the available passes and use the results to schedule your passes accordingly.
49+
50+
| Method | List available contacts | Schedule contacts | Notes |
51+
|-|-|-|-|
52+
|Portal| Yes | Yes | Custom pass timings not possible. You have to use the results of the query|
53+
|API | Yes | Yes| Custom pass timings possible. |
54+
55+
See [how-to schedule a contact](schedule-contact.md) for the Portal method. The API can also be used to create a contact. See the API docs (link to API docs) for this method.
56+
57+
## Next steps
58+
59+
- [Quickstart: Schedule a contact](schedule-contact.md)
60+
- [How to: Update the Spacecraft TLE](update-tle.md)

‎articles/orbital/contact-profile.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: 'Configure a contact profile on Azure Orbital Earth Observation service'
33
description: 'Quickstart: Configure a contact profile'
4-
author: wamota
4+
author: apoorvanori
55
ms.service: orbital
66
ms.topic: quickstart
7-
ms.custom: public-preview
8-
ms.date: 11/16/2021
7+
ms.custom: ga
8+
ms.date: 06/01/2022
99
ms.author: wamota
1010
# Customer intent: As a satellite operator, I want to ingest data from my satellite into Azure.
1111
---
@@ -23,7 +23,7 @@ Configure a contact profile with Azure Orbital to save and reuse contact configu
2323

2424
## Sign in to Azure
2525

26-
Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
26+
Sign in to the [Azure portal - Orbital](https://aka.ms/orbital/portal).
2727

2828
## Create a contact profile resource
2929

@@ -36,7 +36,7 @@ Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
3636
| Subscription | Select your subscription |
3737
| Resource group | Select your resource group |
3838
| Name | Enter contact profile name. Specify the antenna provider and mission information here. Like *Microsoft_Aqua_Uplink+Downlink_1* |
39-
| Region | Select **West US 2** |
39+
| Region | Select a region |
4040
| Minimum viable contact duration | Define the minimum duration of the contact as a prerequisite to show you available time slots to communicate with your spacecraft. If an available time window is less than this time, it won't show in the list of available options. Provide minimum contact duration in ISO 8601 format. Like *PT1M* |
4141
| Minimum elevation | Define minimum elevation of the contact, after acquisition of signal (AOS), as a prerequisite to show you available time slots to communicate with your spacecraft. Using higher value can reduce the duration of the contact. Provide minimum viable elevation in decimal degrees. |
4242
| Auto track configuration | Select the frequency band to be used for autotracking during the contact. X band, S band, or Disabled. |
@@ -51,6 +51,7 @@ Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
5151

5252
| **Field** | **Value** |
5353
| --- | --- |
54+
| Direction | Select the link direction |
5455
| Gain/Temperature (Downlink only) | Enter the gain to noise temperature in db/K |
5556
| EIRP in dBW (Uplink only) | Enter the effective isotropic radiated power in dBW |
5657
| Center Frequency | Enter the center frequency in MHz |
@@ -60,6 +61,10 @@ Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
6061
| IP Address | Specify the IP Address for data retrieval/delivery |
6162
| Port | Specify the Port for data retrieval/delivery |
6263
| Protocol | Select TCP or UDP protocol for data retrieval/delivery |
64+
| Demodulation Configuration (Downlink only) | If applicable, paste your modem demodulation configuration |
65+
| Decoding Configuration (Downlink only)| If applicable, paste your decoding configuration |
66+
| Modulation Configuration (Uplink only) | If applicable, paste your modem modulation configuration |
67+
| Encoding Configuration (Uplink only)| If applicable, paste your encoding configuration |
6368

6469
:::image type="content" source="media/orbital-eos-contact-link.png" alt-text="Contact Profile Links Page" lightbox="media/orbital-eos-contact-link.png":::
6570

@@ -69,5 +74,6 @@ Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
6974

7075
## Next steps
7176

77+
- [How-to Receive real-time telemetry](receive-real-time-telemetry.md)
7278
- [Quickstart: Schedule a contact](schedule-contact.md)
73-
- [Tutorial: Cancel a contact](delete-contact.md)
79+
- [Tutorial: Cancel a contact](delete-contact.md)

‎articles/orbital/delete-contact.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
---
2-
title: 'Cancel a scheduled contact on Azure Orbital Earth Observation service'
3-
description: 'Cancel a scheduled contact'
2+
title: Cancel a scheduled contact on Azure Orbital Earth Observation service
3+
description: Learn how to cancel a scheduled contact.
44
author: wamota
55
ms.service: orbital
66
ms.topic: tutorial
7-
ms.custom: public-preview
8-
ms.date: 11/16/2021
7+
ms.custom: ga
8+
ms.date: 06/13/2022
99
ms.author: wamota
1010
# Customer intent: As a satellite operator, I want to ingest data from my satellite into Azure.
1111
---
1212

13-
# Cancel a scheduled contact
13+
# Tutorial: Cancel a scheduled contact
1414

1515
To cancel a scheduled contact, the contact entry must be deleted on the **Contacts** page.
1616

@@ -23,7 +23,7 @@ To cancel a scheduled contact, the contact entry must be deleted on the **Contac
2323

2424
## Sign in to Azure
2525

26-
Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
26+
Sign in to the [Azure portal - Orbital](https://aka.ms/orbital/portal).
2727

2828
## Delete a scheduled contact entry
2929

@@ -39,7 +39,8 @@ Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
3939
:::image type="content" source="media/orbital-eos-contact-config-view.png" alt-text="Delete a scheduled contact" lightbox="media/orbital-eos-contact-config-view.png":::
4040

4141
6. The scheduled contact will be canceled once the contact entry is deleted.
42+
4243
## Next steps
4344

4445
- [Quickstart: Schedule a contact](schedule-contact.md)
45-
- [Tutorial: Update the spacecraft TLE](update-tle.md)
46+
- [Tutorial: Update the spacecraft TLE](update-tle.md)

‎articles/orbital/howto-downlink-aqua.md renamed to ‎articles/orbital/downlink-aqua.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ description: How to schedule a contact with NASA's AQUA public satellite using A
44
author: wamota
55
ms.service: orbital
66
ms.topic: how-to
7-
ms.custom: public-preview
8-
ms.date: 04/14/2022
7+
ms.custom: ga
8+
ms.date: 07/12/2022
99
ms.author: wamota
1010
# Customer intent: As a satellite operator, I want to ingest data from NASA's AQUA public satellite into Azure.
1111
---

0 commit comments

Comments
 (0)