Communication method and system including internal and external application-programming interfaces

• US 20020154755A1
• Filed: 04/23/2001
• Published: 10/24/2002
• Est. Priority Date: 04/23/2001
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Gourraud, Christophe
• Application Number:
  US09/841,319
• Publication Number:
  US 20020154755A1
• Time in Patent Office: Days
• US Class Current: 379/219
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking

Abstract

A multi-level application-programming-interface-based system and method permit applications developed by third-party service providers outside a telecommunications network to access capabilities of the network. The applications access a physical gateway using an external-service application-programming-interface. The physical gateway communicates with the network via an internal-service application-programming interface. Internal-service applications resident on the physical gateway utilize internal-service application-programming interfaces to communicate with network entities of the network. The network entities preferably each comprise a logical gateway that is used to communication via the internal-service application-programming interface with the internal-service applications.

Claims

1. A method of providing telecommunications services comprising the steps of:

an external-service application communicating with a gateway via an external-service application-programming interface (API), wherein the external-service API is adapted to permit the external-service application to communicate with a plurality of entities of the network; and

the gateway invoking at least one internal-service application, the at least one internal-service application communicating with at least one entity of the plurality of entities via an internal-service API, wherein the internal-service API is supported directly by the at least one entity of the plurality of entities.

2. The method of claim 1 wherein the gateway operates as a physical gateway.

3. The method of claim 2 wherein the external-service API permits the external-service application to be agnostic with respect to topology of the network.

4. The method of claim 3 wherein the internal-service API obviates a need for an API or a protocol between the gateway and the at least one entity.

5. The method of claim 1 wherein the external-service API is a subset of the internal-service API.

6. The method of claim 5 wherein the external-service API is more abstract than the internal-service API.

7. The method of claim 1 wherein the at least one entity operates as a logical gateway.

8. The method of claim 1 wherein the gateway provides security against the external-service application to the network.

9. The method of claim 1 wherein the internal-service application is located on the gateway.

10. The method of claim 1 wherein the internal-service application is located on an entity of the plurality of entities.

11. The method of claim 1 wherein the internal-service API operates according to OSA.

12. The method of claim 11 wherein the external-service API operates according to Parlay.

14. The system of claim 13 wherein the gateway comprises a physical gateway.

15. The system of claim 14 wherein the gateway is adapted to provide security against the entities external to the network.

16. The system of claim 14 wherein the external-service API permits the external-service application to be agnostic with respect to topology of the network.

17. The system of claim 13 wherein the external-service API is a subset of the internal-service API.

18. The method of claim 17 wherein the external-service API is more abstract than the internal-service API.

19. The system of claim 13 wherein the at least one entity comprises a logical gateway.

20. The system of claim 13 wherein the internal-service application is located on the gateway.

21. The system of claim 13 wherein the internal-service application is located on an entity of the plurality of entities.

22. The method of claim 13 wherein the internal-service API operates according to OSA.

23. The method of claim 22 wherein the external-service API operates according to Parlay.

25. The gateway of claim 24 wherein the gateway comprises a physical gateway.

26. The gateway of claim 25 wherein the gateway is adapted to provide security against the entity external to the telecommunications network.

27. The gateway of claim 25 wherein the internal-service API obviates a need for a protocol between the gateway and the at least one entity.

28. The gateway of claim 24 wherein the external-service API is a subset of the internal-service API.

29. The method of claim 28 wherein the external-service API is more abstract than the internal-service API.

30. The gateway of claim 24 wherein the at least one entity comprises a logical gateway.

31. The gateway of claim 24 wherein the internal-service application is located on the gateway.

32. The gateway of claim 24 wherein the internal-service application is located on an entity of the plurality of entities.

33. The method of claim 24 wherein the internal-service API operates according to OSA.

34. The method of claim 33 wherein the external-service API operates according to Parlay.

13. A telecommunications system comprising:

a gateway adapted to communicate via an external-service application-programming interface (API) with entities external to a telecommunications network and via an internal-service API with a plurality of entities of the network; and

at least one network entity adapted to communicate with the gateway and on which is directly supported the internal-service API, wherein the direct support obviates a need for a protocol between the gateway and the at least one entity.

24. A telecommunications gateway adapted to:

communicate via an external-service application-programming interface (API) with at least one entity external to a telecommunications network; and

communicate via an internal-service API with a plurality of entities of the network, wherein the at least one entity external to the network is agnostic with respect to topology of the network and the plurality of entities of the network directly support the internal-service API.