Interoperable framework for secure dual mode edge application programming interface consumption in hybrid edge computing platforms

1 . At least one non-transitory computer readable medium comprising instructions to cause at least one processor circuit to at least:

access, over a first reference point, information to advertise a first plurality of application programming interfaces (APIs) exposed by a first edge computing platform (ECP), the first ECP to implement a first edge computing technology (ECT) including multi-access edge computing (MEC), the first plurality of APIs including a transport discovery API and a MEC service API;

prepare a common API framework (CAPIF) publish service API including (i) a protocol data type to identify a protocol used by the MEC service API and (ii) a transport data type to identify a first transport protocol used to expose the MEC service API, the transport data type different from the protocol data type;

based on the CAPIF publish service API, expose, to a second ECP over a second reference point, at least the MEC service API and the transport discovery API, the second ECP to implement a second ECT including the CAPIF, the transport discovery API to provide access to a plurality of different transport protocols available to expose a plurality of service APIs, the plurality of different transport protocols including the first transport protocol associated with the MEC service API, the first transport protocol not supported by the second ECT;

obtain a query for a list of exposed APIs from an application implemented by the second ECP;

generate the list of exposed APIs, the list of exposed APIs including the first plurality of APIs exposed by the first ECP and a second plurality of APIs exposed by the second ECP; and

cause the list of exposed APIs to be sent to the application.

2 . The at least one non-transitory computer readable medium of claim 1 , wherein the instructions are to cause one or more of the at least one processor circuit to:

authenticate and verify the first ECP based on an authentication and attestation mechanism; and

authenticate and verify a request from the first ECP based on the authentication and attestation mechanism.

3 . The at least one non-transitory computer readable medium of claim 2 , wherein the authentication and attestation mechanism is based on at least one of an Open Authorization (OAuth) protocol or a Transport Layer Security (TLS) protocol.

4 . The at least one non-transitory computer readable medium of claim 1 , wherein the instructions are to cause one or more of the at least one processor circuit to:

update a list of applications having access to the list of exposed APIs to include the application; and

cause the updated list of applications to be sent to the first ECP.

5 . The at least one non-transitory computer readable medium of claim 1 , wherein the first ECP is a MEC platform in a MEC framework.

6 . The at least one non-transitory computer readable medium of claim 5 , wherein the second ECP is an Edge Enabler Server (EES) in a Third Generation Partnership Project (3GPP) Edge Computing framework, and the application is associated with an Edge Application Server (EAS).

7 . The at least one non-transitory computer readable medium of claim 1 , wherein the first ECP is an EES in a 3GPP Edge Computing framework.

8 . The at least one non-transitory computer readable medium of claim 7 , wherein the second ECP is a MEC platform in a MEC framework, and the application is associated with an application server.

9 . The at least one non-transitory computer readable medium of claim 1 , wherein one or more of the at least one processor circuit is included in or connected with a gateway associated with the CAPIF.

10 . The at least one non-transitory computer readable medium of claim 9 , wherein the first ECP is to act as a CAPIF API Exposure Function (AEF), the first reference point is a first CAPIF reference point, and the second reference point is a second CAPIF reference point.

11 . The at least one non-transitory computer readable medium of claim 10 , wherein the gateway is part of a CAPIF Core Function (CCF) of the CAPIF.

12 . An apparatus comprising:

interface circuitry to communicate over a first reference point and a second reference point;

instructions; and

at least one processor circuit to be programmed by the instructions to:

access, over the first reference point, information to advertise a first plurality of application programming interfaces (APIs) exposed by a first edge computing platform (ECP), the first ECP to implement a first edge computing technology (ECT) including multi-access edge computing (MEC), the first plurality of APIs including a transport discovery API and a MEC service API;

prepare a common API framework (CAPIF) publish service API including (i) a protocol data type to identify a protocol used by the MEC service API and (ii) a transport data type to identify a first transport protocol used to expose the MEC service API, the transport data type different from the protocol data type;

based on the CAPIF publish service API, expose at least the MEC service API and the transport discovery API to a second ECP over the second reference point, the second ECP to implement a second ECT including the CAPIF, the transport discovery API to provide access to a plurality of different transport protocols available to expose a plurality of service APIs, the plurality of different transport protocols including the first transport protocol associated with the service API, the first transport protocol not supported by the second ECT;

obtain a query for a list of exposed APIs from an application implemented by the second ECP;

generate the list of exposed APIs, the list of exposed APIs including the first plurality of APIs exposed by the first ECP and a second plurality of APIs exposed by the second ECP; and

cause the list of exposed APIs to be sent to the application.

13 . A method comprising:

accessing, over a first reference point, information to advertise a first plurality of application programming interfaces (APIs) exposed by a first edge computing platform (ECP), the first ECP implementing a first edge computing technology (ECT) including multi-access edge computing (MEC), the first plurality of APIs including a transport discovery API and a MEC service API;

preparing a common API framework (CAPIF) publish service API including (i) a protocol data type to identify a protocol used by the MEC service API and (ii) a transport data type to identify a first transport protocol used to expose the MEC service API, the transport data type different from the protocol data type;

exposing, based on the CAPIF publish service API, at least the MEC service API and the transport discovery API to a second ECP over a second reference point, the second ECP implementing a second ECT including the CAPIF, the transport discovery API providing access to a plurality of different transport protocols available to expose a plurality of service APIs, the plurality of different transport protocols including the first transport protocol associated with the service API, the first transport protocol not supported by the second ECT;

obtaining a query for a list of exposed APIs from an application implemented by the second ECP;

generating the list of exposed APIs, the list of exposed APIs including the first plurality of APIs exposed by the first ECP and a second plurality of APIs exposed by the second ECP; and

sending the list of exposed APIs to the application.

14 . The at least one non-transitory computer readable medium of claim 10 , wherein the gateway is outside of a CCF of the CAPIF.

15 . The apparatus of claim 12 , wherein one or more of the at least one processor circuit is to:

update a list of applications having access to the list of exposed APIs to include the application; and

cause the updated list of applications to be sent to the first ECP.

16 . The method of claim 13 , including sending a list of applications having access to the list of exposed APIs to the first ECP.