Question: What role(s) can a UAE Server assume when Common API Framework for 3GPP Northbound APIs (CAPIF) is supported, in relation to service APIs for UAS application-specific servers (e.g., USS/UTM) or other UAE Servers?
Option 1: Solely as a CAPIF's API invoker to consume service APIs from another server.
Option 2: Either as CAPIF's API exposing function to provide service APIs, or as CAPIF's API invoker to consume service APIs from another UAE Server.
Option 3: Exclusively as a CAPIF's API exposing function for its own internal services only.
Option 4: Neither; it delegates all API responsibilities to UAS application-specific servers.
Explanation: When CAPIF is supported, the UAE Server has the flexibility to operate in two capacities: (1) as an **API exposing function**, providing service APIs to external entities like UAS application-specific servers (e.g., USS/UTM) or other UAE Servers, and (2) as an **API invoker**, consuming service APIs provided by another UAE Server. This dual capability allows for a more integrated and efficient management of UAS services within the telecom network.