System and method for allocating multi-access edge computing services

1. A method, comprising:

receiving, by a network device in a core network and from a user device, an application programming interface (API) call including a request to transfer a Multi-access Edge Computing (MEC) service token from a donor user account to a recipient user account,

wherein the MEC service token indicates a service unit of network resources that provide MEC services, and

wherein the transfer request includes a private key and an account identifier of the recipient user account for the MEC service token;

determining, by the network device, that the MEC service token is available for transfer;

sending, by the network device, a notification of the transfer request to a user associated with the account identifier;

verifying, by the network device, that access to the MEC services by the user can be granted; and

transferring, by the network device and after the verifying, the MEC service token to the recipient user account, wherein the transferring includes initiating an update to a block chain ledger, corresponding to the account identifier, to reflect the transferring of the MEC service token from the donor account to the recipient user account.

2. The method of claim 1 , further comprising:

receiving, by the network device and from a user device executing an instance of an application, an access request for the MEC services, wherein the request includes a unique block chain identifier for the application;

debiting, by the network device, the MEC service token from the recipient user account,

wherein the MEC service token indicates parameters limiting use of network resources that provide the MEC services;

extracting, by the network device, parameters from the MEC service token; and

forwarding, by the network device and to a MEC cluster that provides the MEC services to the instance of the application, the parameters indicated in the MEC service token.

3. The method of claim 1 , wherein the MEC service token indicates parameters limiting use of network resources that provide the MEC services to a preconfigured duration of time.

4. The method of claim 1 , wherein the verifying includes conducting a payment transaction.

5. The method of claim 1 , wherein the MEC service token includes parameters for a duration, a bandwidth, a number of compute cycles, or a memory limit for the MEC services.

6. The method of claim 1 , further comprising:

monitoring for usage activity of the MEC service token; and

logging an amount of unused resources, from the MEC service token, that is available for future use.

7. The method of claim 1 , wherein the MEC service token indicates a service including one or more of graphics processing, general processing, or storage.

8. The method of claim 1 further comprising:

creating, by the network device, the recipient user account for storing the MEC service token.

9. The method of claim 1 , wherein receiving the access transfer request includes:

receiving the API call over a radio access network (RAN).

10. The method of claim 1 , wherein sending the notification comprises requesting confirmation from the user.

11. The method of claim 6 , further comprising:

generating, after the logging, a new token for the recipient user's account to credit the unused resources back to the user.

12. A network device, comprising:

a first communications interface for exchanging data with a user device;

a second communications interface for exchanging data with a Multi-access Edge Computing (MEC) cluster; and

one or more processors configured to:

receive, from a user device, an application programming interface (API) call including a request to transfer a Multi-access Edge Computing (MEC) service token from a donor user account to a recipient user account,

wherein the MEC service token indicates a service unit of network resources that provide MEC services, and

wherein the transfer request includes a private key and an account identifier of the recipient user account for the MEC service token,

determine that the MEC service token is available for transfer,

send a notification of the transfer request to a user associated with the account identifier,

verify that access to the MEC services by the user can be granted, and

transfer, after the verifying, the MEC service token to the recipient user account, wherein the transferring includes initiating an update to a block chain ledger, corresponding to the account identifier, to reflect the transferring of the MEC service token from the donor account to the recipient user account.

13. The network device of claim 12 , wherein, when receiving the transfer request, the one or more processors are further configured to:

receive the API call over a radio access network (RAN).

14. The network device of claim 12 , wherein the one or more processors are further configured to:

credit, before receiving the transfer request, the MEC service token to the donor user account.

15. The network device of claim 12 , wherein the MEC service token includes parameters for a duration or memory limit of the MEC services that are available to the instance of the application.

16. The network device of claim 12 , wherein the one or more processors are further configured to:

receive, from a user device executing an instance of an application, an access request for the MEC services, wherein the request includes a private key and a unique block chain identifier for the application,

debit the MEC service token from the recipient user account, wherein the MEC service token indicates parameters limiting use of network resources that provide the MEC services,

extract parameters from MEC service token, and

forward, to the MEC cluster, the parameters indicated in the MEC service token.

17. The network device of claim 12 , wherein, when sending the notification, the one or more processors are further configured to:

request confirmation from the user.

18. A non-transitory computer-readable medium storing instructions executable by a processor to:

receive, from a user device, an access application programming interface (API) call including a request to transfer a Multi-access Edge Computing (MEC) service token from a donor user account to a recipient user account,

wherein the MEC service token indicates a service unit of network resources that provide MEC services, and

wherein the transfer request includes a private key and an account identifier of the recipient user account for the MEC service token,

determine that the MEC service token is available for transfer,

send a notification of the transfer request to a user associated with the account identifier,

verify that access to the MEC services by the user can be granted, and

transfer, after the verifying, the MEC service token to the recipient user account, wherein the transferring includes initiating an update to a block chain ledger, corresponding to the account identifier, to reflect the transferring of the MEC service token from the donor account to the recipient user account.

19. The non-transitory computer-readable medium of claim 18 , further comprising instructions to:

credit, before receiving the transfer request, the MEC service token to the donor user account.

20. The non-transitory computer-readable medium of claim 18 ,

wherein the MEC service token includes parameters for one or more of a duration or an amount of memory.