You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/orbital/about-ground-stations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ In addition, we support public satellites for downlink-only operations that util
32
32
33
33
## Partner ground stations
34
34
35
-
Azure Orbital Ground Station offers a common data plane and API to access all antenna in the global network. An active contract with the partner network(s) you wish to integrate with Azure Orbital Ground Station is required to onboard with a partner. Once you have the proper contract(s) and regulatory approval(s) in place, your subscription is approved to access partner ground station sites by the Azure Orbital Ground Station team. Learn how to [request authorization of a spacecraft](register-spacecraft.md#request-authorization-of-the-new-spacecraft-resource) and [configure a contact profile](concepts-contact-profile.md#configuring-a-contact-profile-for-applicable-partner-ground-stations) for partner ground stations.
35
+
Azure Orbital Ground Station offers a common data plane and API to access all antenna in the global network. An active contract with the partner network(s) you wish to integrate with Azure Orbital Ground Station is required to onboard with a partner. Once you have the proper contract(s) and regulatory approval(s) in place, your subscription is approved to access partner ground station sites by the Azure Orbital Ground Station team. Learn how to [request authorization of a spacecraft](register-spacecraft.md#request-authorization-of-the-new-spacecraft-resource) and [configure a contact profile](concepts-contact-profile.md#configure-a-contact-profile-for-applicable-partner-ground-stations) for partner ground stations.
Copy file name to clipboardExpand all lines: articles/orbital/concepts-contact-profile.md
+41-30Lines changed: 41 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,38 +10,46 @@ ms.author: hrshelar
10
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 Azure Orbital Ground Station.
11
11
---
12
12
13
-
# Ground station contact profile
13
+
# Ground station contact profile resource
14
14
15
15
The contact profile resource stores pass requirements such as links and endpoint details. Use this resource along with the spacecraft resource during contact scheduling to view and schedule available passes.
16
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.
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. These resources are mutable and don't undergo an authorization process like spacecraft resources do. One contact profile can be used with many spacecraft resources.
18
18
19
-
These resources are mutable and don't undergo an authorization process like the spacecraft resources do. One contact profile can be used with many spacecraft resources.
20
-
21
-
See [how to configure a contact profile](contact-profile.md) for a full list of parameters.
22
-
23
-
## Prerequisites
24
-
25
-
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
26
-
- Subnet that is created in the relevant VNET and resource group. See [prepare network for Azure Orbital Ground Station integration](prepare-network.md).
27
-
28
-
## Creating a contact profile
29
-
30
-
Follow these steps to [create a contact profile](contact-profile.md).
31
-
32
-
## Adjusting pass parameters
33
-
34
-
Specify a minimum pass time to ensure passes are a certain duration. Specify a minimum elevation to ensure passes are above a certain elevation.
35
-
36
-
The minimum pass time and minimum elevation parameters are used by Azure Orbital Ground Station during the contact scheduling. Avoid changing these on a pass-by-pass basis and instead create multiple contact profiles if you require flexibility.
37
-
38
-
## Understanding links and channels
19
+
## Understand links and channels
39
20
40
21
A whole band, unique in direction and polarity, is called a link. Channels, which are children under links, specify the center frequency, bandwidth, and endpoints. Typically there's only one channel per link, but some applications require multiple channels per link.
41
22
42
-
You can specify EIRP and G/T requirements for each link. EIRP applies to uplinks and G/T applies to downlinks. You can provide a name for each link and channel to keep track of these properties. Each channel has a modem associated with it. Follow the steps in [how to setup software modem](modem-chain.md) to understand the options.
43
-
44
-
Refer to the example below to understand how to specify an RHCP channel and an LHCP channel if your mission requires dual-polarization on downlink. To find this information about your contact profile, navigate to the contact profile resource overview and click 'JSON view.'
23
+
You can specify EIRP and G/T requirements for each link. EIRP applies to uplinks and G/T applies to downlinks. You can provide a name for each link and channel to keep track of these properties. Each channel has a modem associated with it. Follow the steps in [how to set up a software modem](modem-chain.md) to understand the options.
24
+
25
+
## Contact profile parameters
26
+
27
+
|**Parameter**|**Description**|
28
+
| --- | --- |
29
+
|**Pass parameters**||
30
+
| Minimum viable contact duration | The minimum duration of a contact in ISO 8601 format. Acts as a prerequisite to show available time slots to communicate with your spacecraft. If an available time window is less than this time, it won't be in the list of available options. Avoid changing on a pass-by-pass basis and instead create multiple contact profiles if you require flexibility. |
31
+
| Minimum elevation | The minimum elevation of a contact, after acquisition of signal (AOS), in decimal degrees. Acts as a prerequisite to show available time slots to communicate with your spacecraft. Using a higher value might reduce the duration of the contact. Avoid changing on a pass-by-pass basis and instead create multiple contact profiles if you require flexibility. |
32
+
| Auto track configuration | The frequency band to be used for autotracking during the contact (X band, S band, or Disabled). |
33
+
| Event Hubs Namespace and Instance | The Event Hubs namespace/instance to send telemetry data of your contacts. |
34
+
|**Network Configuration**||
35
+
| Virtual Network | The virtual network used for a contact. This VNET must be in the same region as the contact profile. |
36
+
| Subnet | The subnet used for a contact. This subnet must be within the above VNET, be delegated to the Microsoft.Orbital service, and have a minimum address prefix of size /24. |
37
+
| Third-party configuration | Mission configuration and provider name associated with a partner ground network. |
38
+
|**Links**||
39
+
| Direction | Direction of the link (uplink or downlink). |
40
+
| Gain/Temperature | Required gain to noise temperature in dB/K. |
41
+
| EIRP in dBW | Required effective isotropic radiated power in dBW. |
42
+
| Polarization | Link polarization (RHCP, LHCP, Dual, or Linear Vertical). |
43
+
|**Channels**||
44
+
| Center Frequency | The channel center frequency in MHz. |
45
+
| Bandwidth | The channel bandwidth in MHz. |
46
+
| Endpoint | The name, IP address, port, and protocol of the data delivery endpoint. |
47
+
| Demodulation Configuration | Copy of the modem configuration file such as Kratos QRadio or Kratos QuantumRx. Only valid for downlink directions. If provided, the modem connects to the customer endpoint and sends demodulated data instead of a VITA.49 stream. |
48
+
| Modulation Configuration | Copy of the modem configuration file such as Kratos QRadio. Only valid for uplink directions. If provided, the modem connects to the customer endpoint and accepts commands from the customer instead of a VITA.49 stream. |
49
+
50
+
## Example of dual-polarization downlink contact profile
51
+
52
+
Refer to the example below to understand how to specify an RHCP channel and an LHCP channel if your mission requires dual-polarization on downlink. To find this information about your contact profile, navigate to the contact profile resource overview in Azure portal and click 'JSON view.'
45
53
46
54
```json
47
55
{
@@ -112,20 +120,23 @@ Refer to the example below to understand how to specify an RHCP channel and an L
112
120
}
113
121
}
114
122
```
123
+
## Create a contact profile
115
124
116
-
## Modifying or deleting a contact profile
125
+
Follow these instructions to create a contact profile[via the Azure portal](contact-profile.md) or [use the Azure Orbital Ground Station API](/rest/api/orbital//azureorbitalgroundstation/contact-profiles/create-or-update/).
117
126
118
-
You can modify or delete the contact profile via the [Azure portal](https://aka.ms/orbital/portal) or [Azure Orbital Ground Station API](/rest/api/orbital/).
127
+
## Modify or delete a contact profile
119
128
120
-
In the Azure portal, navigate to the contact profile resource.
129
+
To modify or delete a contact profile via the [Azure portal](https://aka.ms/orbital/portal), navigate to the contact profile resource.
121
130
- To modify minimum viable contact duration, minimum elevation, auto tracking, or events hubs telemetry, click 'Overview' on the left panel then click 'Edit properties.'
122
131
- To edit links and channels, click 'Links' under 'Configurations' on the left panel then click 'Edit link' on the desired link.
123
132
- To edit third-party configurations, click 'Third-Party Configurations' under 'Configurations' on the left panel then click 'Edit' on the desired configuration.
124
133
- To delete a contact profile, click 'Overview' on the left panel then click 'Delete.'
125
134
126
-
## Configuring a contact profile for applicable partner ground stations
135
+
You can also use the Azure Orbital Ground Station API to [modify](/rest/api/orbital/azureorbitalgroundstation/contact-profiles/create-or-update) or [delete](/rest/api/orbital/azureorbitalgroundstation/contact-profiles/delete) a contact profile.
136
+
137
+
## Configure a contact profile for applicable partner ground stations
127
138
128
-
After onboarding with a partner ground station network, you receive a name that identifies your configuration file. When [creating your contact profile](contact-profile.md#create-a-contact-profile-resource), add this configuration name to your link in the 'Third-Party Configuration" parameter. This links your contact profile to the partner network.
139
+
After onboarding with a partner ground station network, you receive a name that identifies your configuration file. When [creating your contact profile](contact-profile.md), add this configuration name to your link in the 'Third-Party Configuration" parameter. This links your contact profile to the partner network.
0 commit comments