diff options
| author | Benedict Wong <benedictwong@google.com> | 2020-12-22 08:11:02 +0000 |
|---|---|---|
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2020-12-22 08:11:02 +0000 |
| commit | ba3f1179a8ac84a04212fbb3cbc48669ae3b850a (patch) | |
| tree | 8d6a7881524ae147ae4ba675411c9a06d810a302 | |
| parent | 7a7308b53d69ab85ce58c864dbde587c6c02f65b (diff) | |
| parent | 7fb0db69b4081e70088ca05601f82bfca5be8bc9 (diff) | |
Merge "Add additional javadoc for VcnManager"
| -rw-r--r-- | core/java/android/net/vcn/VcnManager.java | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/core/java/android/net/vcn/VcnManager.java b/core/java/android/net/vcn/VcnManager.java index 46d1c1c7a23a..19c183f9fe9c 100644 --- a/core/java/android/net/vcn/VcnManager.java +++ b/core/java/android/net/vcn/VcnManager.java @@ -30,6 +30,30 @@ import java.io.IOException; /** * VcnManager publishes APIs for applications to configure and manage Virtual Carrier Networks. * + * <p>A VCN creates a virtualization layer to allow MVNOs to aggregate heterogeneous physical + * networks, unifying them as a single carrier network. This enables infrastructure flexibility on + * the part of MVNOs without impacting user connectivity, abstracting the physical network + * technologies as an implementation detail of their public network. + * + * <p>Each VCN virtualizes an Carrier's network by building tunnels to a carrier's core network over + * carrier-managed physical links and supports a IP mobility layer to ensure seamless transitions + * between the underlying networks. Each VCN is configured based on a Subscription Group (see {@link + * android.telephony.SubscriptionManager}) and aggregates all networks that are brought up based on + * a profile or suggestion in the specified Subscription Group. + * + * <p>The VCN can be configured to expose one or more {@link android.net.Network}(s), each with + * different capabilities, allowing for APN virtualization. + * + * <p>If a tunnel fails to connect, or otherwise encounters a fatal error, the VCN will attempt to + * reestablish the connection. If the tunnel still has not reconnected after a system-determined + * timeout, the VCN Safe Mode (see below) will be entered. + * + * <p>The VCN Safe Mode ensures that users (and carriers) have a fallback to restore system + * connectivity to update profiles, diagnose issues, contact support, or perform other remediation + * tasks. In Safe Mode, the system will allow underlying cellular networks to be used as default. + * Additionally, during Safe Mode, the VCN will continue to retry the connections, and will + * automatically exit Safe Mode if all active tunnels connect successfully. + * * @hide */ @SystemService(Context.VCN_MANAGEMENT_SERVICE) |