Merge changes from topic "presubmit-am-b36d3cf7498841d4a684ea497f8526c1" into tm-dev

import android.os.Looper;

import android.os.Message;

import android.os.RemoteException;

import android.telephony.AccessNetworkConstants;

import android.telephony.AccessNetworkConstants.AccessNetworkType;

import android.telephony.Annotation.ApnType;

import android.util.Log;

         * invoked for certain APN types, then frameworks uses its own logic to determine the

         * transport to setup the data network.

         *

         * For example, QNS can suggest frameworks to setup IMS on IWLAN by specifying

         * {@link ApnSetting#TYPE_IMS} with a list containing single element

         * For example, QNS can suggest frameworks setting up IMS data network on IWLAN by

         * specifying {@link ApnSetting#TYPE_IMS} with a list containing

         * {@link AccessNetworkType#IWLAN}.

         *

         * Or if QNS consider multiple access networks are qualified for certain APN type, it can

         * suggest frameworks by specifying the APN type with multiple elements in the list like

         * {{@link AccessNetworkType#EUTRAN}, {@link AccessNetworkType#IWLAN}}. Frameworks will then

         * first attempt to setup data on LTE network. If the device moves from LTE to UMTS, then

         * frameworks can perform handover the data network to the second preferred access network

         * if available.

         * If QNS considers multiple access networks qualified for certain APN type, it can

         * suggest frameworks by specifying the APN type with multiple access networks in the list,

         * for example {{@link AccessNetworkType#EUTRAN}, {@link AccessNetworkType#IWLAN}}.

         * Frameworks will then first attempt to setup data on LTE network, and If the device moves

         * from LTE to UMTS, then frameworks will perform handover the data network to the second

         * preferred access network if available.

         *

         * If the {@code qualifiedNetworkTypes} list is empty, it means QNS has no suggestion to the

         * frameworks, and frameworks will decide the transport to setup the data network.

         * frameworks, and for that APN type frameworks will route the corresponding network

         * requests to {@link AccessNetworkConstants#TRANSPORT_TYPE_WWAN}.

         *

         * @param apnTypes APN types of the qualified networks. This must be a bitmask combination

         * of {@link ApnType}.

         * @param qualifiedNetworkTypes List of network types which are qualified for data

         * connection setup for {@link @apnType} in the preferred order. Each element in the list

         * is a {@link AccessNetworkType}. Note that {@link AccessNetworkType#UNKNOWN} is not a

         * valid input here.

         * @param apnTypes APN type(s) of the qualified networks. This must be a bitmask combination

         * of {@link ApnType}. The same qualified networks will be applicable to all APN types

         * specified here.

         * @param qualifiedNetworkTypes List of access network types which are qualified for data

         * connection setup for {@code apnTypes} in the preferred order. Empty list means QNS has no

         * suggestion to the frameworks, and for that APN type frameworks will route the

         * corresponding network requests to {@link AccessNetworkConstants#TRANSPORT_TYPE_WWAN}.

         *

         * If one of the element is invalid, for example, {@link AccessNetworkType#UNKNOWN}, then

         * this operation becomes a no-op.

         */

        public final void updateQualifiedNetworkTypes(

                @ApnType int apnTypes, @NonNull List<Integer> qualifiedNetworkTypes) {