Systems and methods for modifying connectivity and cloud services

1. A computer-implemented method, comprising:

establishing, by a first service provider and via an application programming interface (API), an agreement with a second entity, wherein the agreement identifies services that are permitted to be modified without submission of a new order from either the second entity or the first service provider;

providing, by the first service provider and to the second entity, service topology information associated with components of a first network associated with the first service provider;

receiving, from the second entity, a first message requesting a change associated with a service, wherein the service includes routing data via the first network and a second network associated with the second entity;

determining, by the first service provider and in response to the first message, whether the requested change corresponds to a change that is permitted based on the agreement between the first service provider and the second entity;

determining, by the first service provider, whether resources are available in the first network to implement the requested change;

determining, by the first service provider and based on whether the change is permitted and whether resources are available in the first network to implement the requested change, whether the requested change is accepted;

sending, by the first service provider, a second message to the second entity, wherein the second message indicates whether the change is accepted; and

in response to determining that the change is accepted, automatically implementing the change to the service in the first network.

2. The computer-implemented method of claim 1 , wherein the change comprises a change to a parameter associated with a connectivity service or a change to an application provided by the first service provider.

3. The computer-implemented method of claim 2 , wherein the connectivity service comprises an Ethernet Line (E-Line) service, and wherein the receiving comprises:

receiving the first message via the API.

4. The computer-implemented method of claim 3 , wherein the second entity comprises a second service provider and the E-line service is provided from a location serviced by the second service provider to a destination location serviced by the first service provider, wherein the second service provider is different from the first service provider.

5. The computer-implemented method of claim 1 , wherein establishing the agreement further comprises:

identifying acceptable parameters or parameter ranges for attributes associated with a plurality of connectivity service types or cloud application services.

6. The computer-implemented method of claim 1 , further comprising:

selecting an external network-to-network interface between the first service provider and the second entity.

7. The computer-implemented method of claim 1 , wherein the service includes a connectivity service and the requested change comprises a data rate or bandwidth change for the connectivity service.

8. The computer-implemented method of claim 1 , wherein the second entity comprises a second service provider, the method further comprising:

receiving, from the second service provider, a request for topology information associated with components of the first network; and

providing, by the first service provider and to the second service provider, the service topology information in response to the request for topology information.

9. The computer-implemented method of claim 8 , further comprising:

providing, by the first service provider and to the second service provider, information identifying parameters associated with an Ethernet service that are permitted to be modified based on the agreement.

10. The computer-implemented method of claim 1 , wherein the second entity comprises a second service provider, the method further comprising:

transmitting, by the first service provider and to the second service provider, a third message requesting a second change associated with a connectivity service, wherein the connectivity service includes routing data via the first network and the second network associated with the second service provider; and

receiving, by the first service provider and from the second service provider, a fourth message indicating whether the second change is accepted.

11. A system, comprising:

a memory; and

at least one device associated with a first service provider and configured to:

establish, via an application programming interface (API), an agreement with a second entity, wherein the agreement identifies services that are permitted to be modified without submission of a new order from either the second entity or the first service provider,

provide, by the first service provider and to the second entity, service topology information associated with components of a first network associated with the first service provider;

receive, from the second entity, a first message requesting a change associated with a service, wherein the service includes routing data via the first network and a second network associated with the second entity,

determine, in response to the first message, whether the requested change corresponds to a change that is permitted based on the agreement between the first service provider and the second entity,

determine whether resources are available in the first network to implement the requested change,

determine, based on whether the change is permitted and whether resources are available in the first network to implement the requested change, whether the requested change is accepted,

send a second message to the second entity, wherein the second message indicates whether the change is accepted, and

in response to determining that the change is accepted, automatically implementing the change to the service.

12. The system of claim 11 , wherein the change comprises a change to a parameter associated with a connectivity service.

13. The system of claim 12 , wherein the connectivity service comprises an Ethernet Line (E-Line) service, and when receiving, the at least one device is configured to:

receive the first message via the API.

14. The system of claim 11 , wherein when establishing the agreement, the at least one device is configured to:

identify acceptable parameters or parameter ranges for attributes associated with a plurality of connectivity service types or cloud application services.

15. The system of claim 11 , wherein the second entity comprises a second service provider, wherein the at least one device is further configured to:

receive, from the second service provider, a request for topology information associated with components of the first network, and

provide, to the second service provider, the service topology information in response to the request for topology information.

16. The system of claim 15 , wherein the at least one device is further configured to:

provide, to the second service provider, information identifying parameters associated with an Ethernet service that are permitted to be modified based on the agreement.

17. The system of claim 11 , wherein the second entity comprises a second service provider, and wherein the at least one device is further configured to:

transmit, to the second service provider, a third message requesting a second change associated with a connectivity service, wherein the connectivity service includes routing data via the first network and the second network associated with the second service provider; and

receive, by the first service provider and from the second service provider, a fourth message indicating whether the second change is accepted.

18. The system of claim 11 , wherein the at least one device is further configured to:

charge the second entity for changes to a connectivity service based on the agreement.

19. A non-transitory computer-readable medium having stored thereon sequences of instructions which, when executed by at least one processor associated with a first service provider, cause the at least one processor to:

establish, via an application programming interface (API), an agreement with a second service provider, wherein the agreement identifies services that are permitted to be modified without submission of a new order from either the first service provider or the second service provider;

provide, to the second service provider, service topology information associated with components of a first network associated with the first service provider;

receive, from the second service provider, a first message requesting a change associated with the service, wherein the service includes routing data via the first network and a second network associated with the second service provider;

determine, in response to the first message, whether the requested change corresponds to a change that is permitted based on the agreement between the first and second service providers;

determine whether resources are available in the first network to implement the requested change;

determine, based on whether the change is permitted and whether resources are available in the first network to implement the requested change, whether the requested change is accepted;

send a second message to the second service provider, wherein the second message indicates whether the change is accepted; and

in response to determining that the change is accepted, automatically initiate implementation of the change to the service in the first network.

20. The non-transitory computer-readable medium of claim 19 , wherein the instructions further cause the at least one processor to:

transmit, to the second service provider, a third message requesting a second change associated with a connectivity service, wherein the connectivity service includes routing data via the first and second networks; and

receive, from the second service provider, a fourth message indicating whether the second change is accepted.