Multi-layered charging system
A method may include receiving, by a computing system of a front-end service provider, a communications request including user data. The method may include determining, by the computing system of the front-end service provider, that one or more back-end service providers can fulfil the communications request. The method may include transmitting, by the computing system of the front-end service provider, data associated with the communications request and/or the one or more back-end service providers to a proxy service. The method may include receiving, by the computing system of the front-end service provider and from the proxy service, information associated with a back-end service provider of the one or more back-end service providers. The method may also include establishing, by the computing system of the front-end service provider, a communications connection with the back-end service provider and transmitting the user data such that the communications request is fulfilled.
1. A method, comprising:
receiving, by a computing system of a front-end service provider, a communications request including user data;
determining, by the computing system of the front-end service provider, that one or more back-end service providers can fulfil the communications request, wherein the one or more back-end service providers are different from the front-end service provider;
transmitting, by the computing system of the front-end service provider, data associated with the communications request and/or the one or more back-end service providers to a charging function (CHF) proxy service, the data indicating requirements of the communications request comprising at least one of a bandwidth requirement, a cost requirement, or a charging function (CHF) registration requirement;
receiving, by the computing system of the front-end service provider and from the CHF proxy service, information associated with a back-end service provider of the one or more back-end service providers, the information comprising at least one of a first CHF associated with the back-end service provider or a second CHF associated with the CHF proxy service;
establishing, by the computing system of the front-end service provider, a communications connection with the back-end service provider; and
transmitting, by the front-end service provider and to the back-end service provider, the user data such that the communications request is fulfilled.
2. The method of claim 1 , wherein determining, by the computing system of the front-end service provider, that one or more back-end service providers can fulfil the communications request further comprises:
accessing, by the computing system of the front-end service provider, one or more policies associated with at least one of the communications request, a sender of the communications request, and policies associated with the front-end service provider; and
accessing, by the computing system of the front-end service provider, one or more provider attributes associated with the back-end service providers.
3. The method of claim 2 , wherein the one or more provider attributes associated with the one or more back-end service providers comprise at least one of a CHF, a service level, and a service capacity.
4. The method of claim 1 , wherein the computing system of the front-end service provider determines the charging function associated with the back-end service provider based at least in part on a charging function registry.
5. The method of claim 1 , wherein the computing system of the front-end service provider provides authentication information associated with a user equipment (UE) of the communications request to the back-end service provider after the communications connection is established.
6. The method of claim 1 , wherein the information associated with a back-end service provider of the one or more back-end service providers comprises information associated with an online marketplace.
7. The method of claim 1 , wherein a charging function associated with the back-end service provider is also associated with a charging-as-a-service entity.
8. The method of claim 1 , wherein communications request is fulfilled by a plurality of back-end service providers.
9. A computing system of a front-end service provider, comprising:
one or more processors;
non-transitory computer-readable memory comprising instructions that, when executed by the one or more processors, cause the computing system to perform operations to:
receive, by the computing system of the front-end service provider, a communications request including user data;
determine, by the computing system of the front-end service provider, that one or more back-end service providers can fulfil the communications request, wherein the one or more back-end service providers are different from the front-end service provider;
transmit, by the computing system of the front-end service provider, data associated with the communications request and/or the one or more back-end service providers to a charging function (CHF) proxy service, the data indicating requirements of the communications request comprising at least one of a bandwidth requirement, a cost requirement, or a charging function (CHF) registration requirement;
receive, by the computing system of the front-end service provider and from the CHF proxy service, information associated with a back-end service provider of the one or more back-end service providers, the information comprising at least one of a first CHF associated with the back-end service provider or a second CHF associated with the CHF proxy service;
establish, by the computing system of the front-end service provider, a communications connection with the back-end service provider; and
transmit, by the front-end service provider and to the back-end service provider, the user data such that the communications request is fulfilled.
10. The computing system of claim 9 , wherein the computing system further comprises a stand-alone 5G network.
11. The computing system of claim 9 , further comprising a session management function, a user plane function, a policy control function and a network repository function.
12. The computing system of claim 11 , wherein the policy control function includes one or more policies associated with at least one of the communications request, a sender of the communications request, and policies associated with a front-end service provider.
13. The computing system of claim 11 , wherein the network repository function includes one or more charging functions, associated with the one or more back-end service providers.
14. The computing system of claim 11 , wherein the network repository function includes a charging function associated with an online marketplace for back-end service providers.
15. The computing system of claim 11 , wherein the session management function comprises one or more provider attributes, the one or more provider attributes comprising a service level and a service capacity.
16. The computing system of claim 11 , wherein the communications request is received from a user equipment.
17. The computing system of claim 11 , wherein the computing system of the front-end service provider provides authentication information associated with a user equipment (UE) to the back-end service provider after the communications connection is established.
18. The computing system of claim 11 , wherein the information associated with the back-end service provider comprises a charging function.
19. The method of claim 1 , wherein determining, by the computing system of the front-end service provider, that one or more back-end service providers can fulfil the communications request further comprises determining one or more back-end service providers associated with geographic locations corresponding to respective endpoints of the one or more endpoints.