Orchestrating mobile data networks in a network environment

Patent metadata

Field	Value
Publication number	US-9712634-B2
Application number	US-201313841165-A
Country	US
Kind code	B2
Filing date	Mar 15, 2013
Priority date	Mar 15, 2013
Publication date	Jul 18, 2017
Grant date	Jul 18, 2017

Abstract

A method is provided in one example and includes receiving a request for a service from a requestor, an determining at least a first network element and at least a second network element required to satisfy the request from among a plurality of network elements. The method further includes triggering a coordinating of a work flow between the first network element and the second network element responsive to the request. The method still further includes translating communication messages exchanged between the first network element and the second network element from a first communication protocol format and a second communication protocol format.

First claim

What is claimed is:

1. A method, comprising:
receiving a request for a service from a requestor;
determining at least a first network element and at least a second network element required to satisfy the request from among a plurality of network elements;
triggering, by a server in communication with a mobile network, a coordinating of a work flow between the first network element and the second network element responsive to the request, wherein the work flow includes exchanging messages between the first network element and the second network element; and
translating, by the server, the communication messages exchanged between the first network element and the second network element from a first communication protocol format and a second communication protocol format;
wherein translating communication messages between the first network element and the second network element further comprises:
receiving a first communication message from the first network element having the first communication protocol format, wherein the first communication protocol format includes a Hypertext Transfer Protocol (HTTP) format;
translating the first communication message to a second communication message having the second communication protocol format, wherein the second communication protocol format includes a subscriber policy management service protocol format; and
sending the second communication message to the second network element.

2. The method of claim 1 , wherein the request includes a username and network address associated with the requestor.

3. The method of claim 2 , further comprising:
querying a third network element for a subscriber identifier corresponding to the network address;
receiving the subscriber identifier from the third network element;
mapping the username to the subscriber identifier; and
storing the mapping of the username to the subscribe identifier.

4. The method of claim 1 , wherein the requestor is an external network element.

5. The method of claim 1 , wherein the requestor is an internal network element.

6. The method of claim 1 , wherein coordinating the work flow includes determining whether modification of data within at least one of the plurality of network elements is required.

7. The method of claim 6 , further comprising modifying the data within the at least one network element.

8. The method of claim 1 , wherein the network elements include at least one subscriber-aware network element.

9. The method of claim 1 , wherein the network elements include at least one subscriber database.

10. Logic encoded in one or more non-transitory tangible media that includes code for execution and when executed by a processor operable to perform operations comprising:
receiving a request for a service from a requestor;
determining at least a first network element and at least a second network element required to satisfy the request from among a plurality of network elements;
triggering, by a server in communication with a mobile network, a coordinating of a work flow between the first network element and the second network element responsive to the request, wherein the work flow includes exchanging messages between the first network element and the second network element; and
translating, by the server, the communication messages exchanged between the first network element and the second network element from a first communication protocol format and a second communication protocol format;
wherein translating communication messages between the first network element and the second network element further comprises:
receiving a first communication message from the first network element having the first communication protocol format, wherein the first communication protocol format includes a Hypertext Transfer Protocol (HTTP) format;
translating the first communication message to a second communication message having the second communication protocol format, wherein the second communication protocol format includes a subscriber policy management service protocol format; and
sending the second communication message to the second network element.

11. The media of claim 10 , wherein the request includes a username and network address associated with the requestor.

12. The media of claim 11 , wherein the operations further comprise:
querying a third network element for a subscriber identifier corresponding to the network address;
receiving the subscriber identifier from the third network element;
mapping the username to the subscriber identifier; and
storing the mapping of the username to the subscribe identifier.

13. The media of claim 10 , wherein the requestor is an external network element.

14. The media of claim 10 , wherein the requestor is an internal network element.

15. The media of claim 10 , wherein coordinating the work flow includes determining whether modification of data within at least one of the plurality of network elements is required.

16. The media of claim 15 , wherein the operations further comprise modifying the data within the at least one network element.

17. The media of claim 10 , wherein the network elements include at least one subscriber-aware network element.

18. The media of claim 10 , wherein the network elements include at least one subscriber database.

19. An apparatus, comprising:
a memory element configured to store data,
a processor operable to execute instructions associated with the data, and
at least one module, the apparatus being configured to:
receive a request for a service from a requestor;
determine at least a first network element and at least a second network element required to satisfy the request from among a plurality of network elements;
trigger, by a server in communication with a mobile network, a coordinating of a work flow between the first network element and the second network element responsive to the request, wherein the work flow includes exchanging messages between the first network element and the second network element; and
translate, by the server, the communication messages exchanged between the first network element and the second network element from a first communication protocol format and a second communication protocol format;

wherein translating communication messages between the first network element and the second network element further comprises:
receiving a first communication message from the first network element having the first communication protocol format, wherein the first communication protocol format includes a Hypertext Transfer Protocol (HTTP) format;
translating the first communication message to a second communication message having the second communication protocol format, wherein the second communication protocol format includes a subscriber policy management service protocol format; and
sending the second communication message to the second network element.

20. The apparatus of claim 19 , wherein the request includes a username and network address associated with the requestor.

21. The apparatus of claim 20 , wherein the apparatus is further configured to:
query a third network element for a subscriber identifier corresponding to the network address;
receive the subscriber identifier from the third network element;
map the username to the subscriber identifier; and
store the mapping of the username to the subscribe identifier.

22. The apparatus of claim 19 , wherein the requestor is an external network element.

Assignees

• Cisco Tech Inc

Inventors

• Ang Gibson Soon Teck
• Alex Arun C
• Shatzkamer Kevin D
• Mistry Bipin
• Jagadeesan Ramanathan T
• Morgan Jonathan A
• Velandy Rajesh P
• Puthiyandyil Sanil Kumar

Classifications

• H04L61/103

  across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP] · CPC title

• H04W24/00

  Supervisory, monitoring or testing arrangements · CPC title

• H04L61/2503

  Translation of Internet protocol [IP] addresses · CPC title

• H04L12/2876

  Handling of subscriber policies (group policies management H04L41/0893) · CPC title

• H04L29/12613

  Electricity · mapped topic