Cloud Connector Network Connectivity Overview

As gateway devices, Cloud Connectors provide a range of network connectivity options for connecting to Oracle Enterprise Communications Platform (Oracle ECP). Administrators can choose one or more network and media options to support customer business goals such as redundancy, traffic separation, bandwidth control, and security optimization.

Note:

The Cloud Connector’s internet access is intended exclusively for business use to enable Oracle application and service operations.

Oracle ECP displays network connectivity for onboarded Cloud Connectors on the Edge Node Inventory page. Although the Ethernet network interface is the default, cellular and satellite include interfaces and use connectivity services from the Mobile Network Operator (MNO) that manages the SIM card.

After you onboard a Cloud Connector, you can view the network connectivity type on the Edge Node Inventory page. You can view more details by accessing the Network tab on the Edge Node Details page.

The Dashboard page displays information related to different types of network connectivity.

About AT&T Accounts

Oracle Enterprise Communications Platform (Oracle ECP) supports Mobile Network Operator (MNO) account-related settings and functionality designed to accommodate differences in how proprietary MNO accounts and cellular networks work. AT&T MNO accounts operate through the AT&T Control Center for external management of SIM cards.

Oracle ECP connectivity management services support device and Cloud Connector connections directly to ECP Cloud, through an ECP gateway (such as an on-premises Cloud Connector), and through APIs that can interface to device manufacturer clouds and other third-party service provider clouds such as those offered by an MNO. Each Cloud Connector or device in a customer's ECP inventory that is using a SIM Card for connectivity is associated with a MNO account that defines how connectivity services are provided over the cellular network. Some settings and functionality available in Oracle ECP apply for one MNO account type and not others.

AT&T MNO accounts operate through the AT&T Control Center for external management of SIM cards. Devices and Cloud Connector equipped with AT&T SIM cards are automatically assigned during onboarding to a default rate plan configured per GBU guidelines for the customer. AT&T MNO accounts support setting network priority for prioritized handling of associated data traffic in network congestion scenarios and changing rate plans to support optimal connectivity service volumes.

About Vodafone Accounts

Vodafone Mobile Network Operator (MNO) accounts operate through the Vodafone IoT Global Platform for external management of SIM cards. Devices and Cloud Connectors equipped with Vodafone SIM cards are automatically assigned during onboarding to a default Service Profile configured per GBU guidelines for the customer.

The Vodafone Service Profile does not support setting network priority to allow for prioritized handling in network congestion scenarios and has no support for changing rate plans.

Connectivity service rates, services, and terms and conditions of service are defined through the Vodafone Service Profile. Any changes you make to a Service Profile affects the grouped properties of the Vodafone MNO account. If you change the Access Point Name (APN) associated with a Vodafone SIM card, the change could automatically include a change to the associated rate, region, or terms and conditions of service because these properties are interconnected. It is important to understand all MNO account properties and associated contractual agreements before you make a change to a Vodafone Service Profile. Therefore, in the case of an APN change for a Vodafone SIM card, Oracle ECP warns you that additional MNO account-related changes can occur (for instance, because an APN is associated with a region).

Note:

Vodafone SIMs may have a latency of up to 48 hours in showing data usage on the item overview page.

About Starlink Accounts

Oracle Enterprise Communications Platform (Oracle ECP) offers Satellite as a connectivity mode for Cloud Connectors by way of Starlink. With satellite, your Oracle ECP Cloud Connectors can communicate from any location that supports a Starlink account.

To begin, you must establish a Starlink account, choose a service plan, and purchase Starlink terminals (see starlink.com). Provide those details to Oracle to establish operations with Oracle ECP. Then you can associate terminals with Cloud Connectors through the Oracle ECP user interface or APIs.

A Starlink account is a collection of service lines and associated terminals with a corresponding Account ID. An enabled user can configure the service account to provide API access. Access the Starlink portal to add users to your account.

  • You must use a Starlink enterprise account to manage Starlink terminals in a given Country or Region. When you deploy Starlink in a specific country or region, you must deploy to the Starlink account for the specified country.
  • Oracle ECP provides connectivity management for Starlink in multiple countries, so it supports multiple Starlink accounts.
  • Oracle adds Starlink accounts to Oracle ECP by way of the gitlab pipeline, which provides account info, credentials, and system level default service plan.
  • All calls to Starlink APIs use the OAuth client grant for authentication. A service account (distinct from an enterprise account) is used to configure the client ID, secret, and service account name. Creating a service account is a manual procedure performed by a user with access to a Starlink enterprise account. Note: You can use a service account to manage multiple accounts in multiple countries.

Note:

Starlink connectivity is supported only on the official Cloud Connector.