Yes. On devices and networks that support 5G network slicing, AMAPI can route traffic for specific applications through dedicated enterprise slices rather than the default carrier data path.
A 5G network slice is a logically separate path through the carrier network with its own quality of service, latency, and bandwidth characteristics. An enterprise can subscribe to one or more slices from a participating carrier and configure managed devices to use them.
In AMAPI, this is controlled through two policy fields:
preferentialNetworkService at the policy level enables preferential network service on the devicepreferentialNetworkServiceSettings defines up to five preferential network configurations, each identified as PREFERENTIAL_NETWORK_ID_ONE through PREFERENTIAL_NETWORK_ID_FIVEpreferentialNetworkId on each application policy assigns that application to one of the configured slices. A defaultPreferentialNetworkId can also be set at the policy level for any application that does not specify onePREFERENTIAL_NETWORK_ID_n values and actual carrier slices