Differentiated routing system and method
A differentiated routing system is provided for routing a communication service according to an access point of a subscriber terminal to a first network domain. The system includes a computing system executing a core routing engine (CRE) that receives a request for a communication service from the subscriber terminal. When the communication service is to be routed to a second network domain, the CRE identifies an access point at which the subscriber terminal accesses the first network domain, includes a tag in the request according to the identified access point. The tag includes information to be used by the second network domain for routing the communication service. The CRE then transmits the request to the second network domain.
1. A differentiated routing system comprising:
a computing system comprising at least one processor and in communication with a subscriber terminal and a first network domain; and
a core routing engine (CRE) executable by the at least one processor to:
receive a request for a communication service from the subscriber terminal through an access point at which the subscriber terminal accesses the first network domain; and
when the communication service is to be routed to a second network domain:
identify the access point;
include a tag in the request, the tag selected based on the identified access point, and the tag including information to be used by the second network domain for routing the communication service; and
transmit the request to the second network domain, wherein the second network domain comprises a second CRE to:
receive the request from the first network domain; and
route the communication service through the second network domain according to the tag in the received request.
2. The system as recited in claim 1 , wherein the access point provides a dedicated access line (DAL) for the subscriber terminal.
3. The system as recited in claim 1 , wherein the first network domain and the second network domain both comprise internet protocol (IP) based networks.
4. The system as recited in claim 3 , wherein the request comprises a session initiation protocol-uniform resource identifier (SIP-URI) and the tag is included in the SIP-URI.
5. The system as recited in claim 1 , further comprising a third network domain having a third CRE to:
receive the request from the second network domain; and
route the communication service through the third network domain according to the tag in the received request.
6. The system as recited in claim 1 , wherein the second CRE is further executable to:
route the communication service through the second network domain according to information included in the tag.
7. The system as recited in claim 1 , wherein the second CRE is further executable to:
receive another request from another subscriber terminal, the other request comprising a tag that is different from the tag of the request; and
monitor operating characteristics associated with the communication service provided to the subscriber terminal separately from operating characteristics associated with a communication service provided to the other subscriber terminal.
8. A differentiated routing method comprising:
receiving a request for a communication service from a subscriber terminal by a first core routing engine (CRE) of a first network domain through an access point at which the subscriber terminal accesses the first network domain; and
when the communication service is to be routed to a second network domain:
identifying the access point;
including a tag in the request, the tag selected based on the identified access point, and the tag including information to be used by the second network domain for routing the communication service;
transmitting the request to the second network domain;
receiving the request from the first network domain via a second CRE of the second network domain; and
routing the communication service through the second network domain according to the tag in the received request.
9. The method as recited in claim 8 , further comprising providing a dedicated access line (DAL) for the subscriber terminal using the access point.
10. The method as recited in claim 8 , wherein the first network domain and the second network domain both comprise internet protocol (IP) based networks.
11. The method as recited in claim 10 , further comprising appending the tag in a session initiation protocol-uniform resource identifier (SIP-URI).
12. The method as recited in claim 8 , further comprising:
receiving the request from the second network domain via a third CRE of a third network domain; and
routing the communication service through the third network domain according to the tag in the received request.
13. A communication network comprising:
a first network domain in communication with a subscriber terminal; and
a second network domain in communication with the first network domain;
wherein the first network domain comprises a computing system having at least one processor that executes a core routing engine (CRE) to:
receive a request for a communication service from the subscriber terminal through an access point at which the subscriber terminal accesses the first network domain; and
when the communication service is to be routed to a second network domain:
identify the access point;
include a tag in the request, the tag selected based on the identified access point, and the tag including information to be used by the second network domain for routing the communication service; and
transmit the request to the second network domain;
wherein the CRE is further executed to:
receive, via a second CRE of the second network domain, the request from the first network domain; and
route the communication service through the second network domain according to the tag included in the received request.
14. The communication network as recited in claim 13 , wherein the first network domain and the second network domain both comprise internet protocol (IP) based networks.
15. The communication network as recited in claim 13 , wherein the CRE is further executed to perform appending the tag to a session initiation protocol-uniform resource identifier (SIP-URI), and transmitting the SIP-URI to the second network domain.
16. The communication network as recited in claim 13 , wherein the CRE is further executed to route the communication service through the second network domain according to information included in the tag.
17. The communication network as recited in claim 13 , wherein the CRE is further executed to:
receive another request from another subscriber terminal, the other request comprising a tag that is different from the tag of the request; and
monitor operating characteristics associated with the communication service provided to the subscriber terminal separately from operating characteristics associated with a communication service provided to the other subscriber terminal.