Communicaton system, method and cotroller for routing calls within private networks distributed among geographically distant zones

• US 20040008710A1
• Filed: 12/24/2002
• Published: 01/15/2004
• Est. Priority Date: 02/04/2000
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Arauz-Rosado, Jesus-Javier, Parra-Moyano, Francisco, Perez Fernandez, Javier
• Granted Patent: US 7,356,040 B2
• Time in Patent Office: Days
• US Class Current: 370/422
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 2207/35 virtual private networks
• CPC Class Codes: H04M 3/4228 in networks
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables

Abstract

A controller (GK) of a communication system (SYS) including in each of a plurality of geographically distant zones (ZA, ZB, ZC) a zone-specific controller (GK) and one or more subscriber terminals (EP) comprises a controller characteristics memory (CCM) for storing at least a private network identifier (PNID), a private network configuration memory (PNCM) for storing the private network configuration, a private network configuration determing means (PMDM) for communicating with other controllers (GK) of the communication system to determine the private network configuration and a call router for routing a call setup message received from a subscriber terminal (EP-A₃) in one zone (ZA) to another subscriber terminal (EP-B₂) of another zone (ZB). Before setting-up a call or at repeated time intervals the private network configuration including the controllers and subscriber stations in all zones (ZA, ZB, ZC) which belong to the private network identified by the private network identifier (PNID) can be determined and this private network configuration is used for determining the location of the respective controller which serves the called subscriber station (EP-B₂).

Claims

1. A controller (GK) of a communication system (SYS) including in each of a plurality of geographically distant zones (ZA, ZB, ZC) a zone-specific controller (GK) and one or more subscriber terminals (EP) connected to each other via a zone-specific bus network (BUS-A, BUS-D, BUS-C), said zone-specific bus networks being connected to each other via at least one interconnection network (WAN), wherein said controller (GK) controls the signaling traffic between the subscriber terminals (EP) in each zone and between different zones and comprises:

a) a controller characteristics memory (CCM) for storing at least a private network identifier (PNID) of a private network (PN) to which said zone-specific controller (GK) and its connected subscriber terminals (EP) belong;

b) a private network configuration memory (PNCM) for storing the private network configuration at least of the private network identified by the stored private network identifier (PNID);

c) a private network configuration determining means (PNDM) for communicating (GRQ, GCF, GRJ) with all other controllers (GK) of the communication system (SYS) to determine the private network configuration including those controllers (GK) and subscriber stations (EP) in other zones (B, C) which belong to the private network (PN) identified by the stored private network identifier (PNID) and to store corresponding private network configuration information (TA;

RA;

CNCT) in said private network configuration memory (PNCM).

2. A controller according to claim 1,

characterized in that

said controller characteristics memory (CCM) is further adapted to store the range of calling numbers (RA) of the subscriber terminals (EP) which are connected with the controller (GK) via the bus-network.

3. A controller according to claim 1 or 2,

characterized in that

said controller characteristics memory (CCM) is further adapted to store information about the call routing technique (called number based routing or location based routing) which must be used when setting up a call to a subscriber station (EP) connected to the controller.

4. A controller according to claim 1,

characterized in that

said private network configuration memory (PNCM) is adapted to store as private network configuration information (RASTA;

RA;

CNCT) the RAS transport address (RASTA) of respective other controllers (GK) belonging to the private network identified by the private network identifier, for each RAS transport address (RASTA) the range (RA) of calling numbers and connection information (CNCT) whether a direct connection can be set up to a controller (GK) identified by the RAS transport address (RASTA).

5. A controller according to claim 4,

characterized in that

said private network configuration memory (PNCM) is adapted to store as said private network configuration information (RASTA;

TA;

CNCT) in one table (TB1) the RAS transport address (RASTA) of respective other controllers (GK) belonging to the private network identified by the private network identifier, for each RAS transport address (RASTA) the range of calling numbers and the connection information (CNCT) whether a direct connection can be set up to a controller (GK) identified by the RAS transport address (RASTA).

6. A controller according to claim 4,

characterized in that

said private network configuration memory (PNCM) is adapted to store as private network configuration information (RASTA;

RA;

CNCT) in a first table (TB2) the RAS transport address (RASTA) of respective other controllers (GK) belonging to the private network identified by the private network identifier (PNID) and for each RAS transport address (RASTA) the range (RA) of calling numbers, and in a second table (TB3) the RAS transport addresses (RASTA) of controllers of the same private network (PN) and other private networks to which a direct connection can be set up from the controller.

7. A controller according to claim 1,

characterized by

said private network configuration determining means (PNDM), in order to determine the private network configuration, being adapted to send through the interconnection network (WAN) to all other controllers (GK) in the communication system (SYS) a controller configuration request message (GRQ) including at least the stored private network identifier (PNID);

a controller configuration request response means (GRQRM) for sending, in response to a controller configuration request message (GRQ) from another controller (GK), to said other controller (GK) a controller configuration confirmation message (GCF) including at least the RAS transport address (RASTA) of the controller and the range (RA) of calling numbers (CN) of subscriber terminals (EP) to which the controller (GK) is connected if the private network identifier (PNID) contained in the received controller configuration request message (GRQ) matches the stored private network identifier (PN); and

said private network configuration determining means (PNDM) setting, in response to a receipt of one or more controller configuration confirmation messages (GCF) from one or more other controllers, in its associated private network configuration memory (PNCM) as said private network configuration said RAS transport address (RASTA) and said range (RA) of calling numbers (CN).

8. A controller according to claim 7,

characterized in that

said controller configuration request response means (GRQRM) is adapted for sending, in response to a controller configuration request message (GRQ) from another controller (GK), a controller configuration rejection message (GRJ) if the private network identifier (PNID) contained in the received controller configuration request message (GRQ) does not match the private network identifier (PN) stored in the controller characteristics memory (CCM).

9. A controller according to claim 1,

characterized in that

the controller (GK) further comprises a call router (CR) for receiving from a subscriber terminal (e.g. EP-A₃) connected to said controller (GK) a call setup message (ARQ) indicating a call setup to another subscriber terminal (e.g. EP-B₂), for determining on the basis of the private network configuration information (RASTA, RA, CNCT) in the private network configuration memory (PNCM) the controller (GK) to which said called subscriber terminal (e.g. EP-B₂) is connected, and for routing the call setup message (ARQ) to the determined controller.

21. A controller according to claim 1,

characterized in that

said private network configuration determining means (PNDM) is adapted to determine the private network configuration and to store corresponding private network configuration information (RASTA;

RA;

CNCT) in said private network configuration memory (PNCM) at repeated time intervals to update the configuration information in the private network configuration memory.

22. A communication system (SYS) including in each of a plurality of geographically distant zones (ZA, ZB, ZC) a zone-specific controller (GK) and one or more subscriber terminals (EP) connected to each other via a zone-specific bus network (BUS-A, BUS-D, BUS-C), said zone-specific bus networks being connected to each other via at least one interconnection network (WAN), wherein each zone-specific controller (GK) controls the signaling traffic between the subscriber terminals (EP) in each zones and between different zones and is constituted as defined in one or more claims 1-21.

10. A controller of a communication system (SYS) including in each of a plurality of geographically distant zones (A, B, C) a zone-specific controller (GK) and one or more subscriber terminals (EP) connected to each other via a zone-specific bus network (BUS-A, BUS-D, BUS-C), said zone-specific bus networks being connected to each other via at least one interconnection network (WAN), wherein the controller (GK) controls the signaling traffic between the subscriber terminals (EP) in each zone and between different zones and comprises:

a) a private network configuration memory (PNCM) for storing the private network configuration at least of the private network identified by a private network identifier (PNID); and

b) a call router (CR) for receiving from a subscriber terminal (e.g. EP-A₃) connected to said controller (GK) a call setup message (ARQ) indicating a call setup to-another subscriber terminal (e.g. EP-B₂), for determining on the basis of the private network configuration information (RASTA, RA, CNCT) in the private network configuration memory (PNCM) the controller (GK) to which said called subscriber terminal (e.g. EP-B₂) is connected, and for routing the call setup message (ARQ) to the determined controller.

11. A controller according to claim 10,

characterized in that

said private network configuration memory (PNCM) stores as private network configuration information (RASTA;

RA;

CNCT) at least the RAS transport address (RASTA) of respective other controllers (GK) belonging to the private network identified by the private network identifier, for each RAS transport address (RASTA) the range (RA) of calling numbers (E.164 range) and connection information (CNCT) whether a direct connection can be set up to a controller (GK) identified by the RAS transport address.

12. A controller according to claim 11,

characterized in that

said private network configuration memory (PNCM) stores as said private network configuration information (RASTA;

NR;

CNCT) in one table (TB1) the RAS transport address (RASTA) of respective other controllers (GK) belonging to the private network identified by the private network identifier, for each RAS transport address (RASTA) the range (RA) of calling numbers (E.164 range) and the connection information (CNCT) whether a direct connection can be set up to a controller (GK) identified by the RAS transport address (RASTA).

13. A controller according to claim 11,

characterized in that

said private network configuration memory (PNCM) stores as private network configuration information (RASTA;

RA;

CNCT) in a first table (TB2) the RAS transport address (RASTA) of respective other controllers (GK) belonging to the private network identified by the private network identifier and for each RAS transport address (RASTA) the range of calling numbers, and in a second table (TB3) the RAS transport addresses of controllers of the same private network and other private networks to which a direct connection can be set up from the controller.

14. A controller according to claim 11,

characterized in that

said call router (CR) determines the controller (GK) to which the call setup message (ARQ) is to be routed by carrying out the following steps (FIG. 6) (called number based call routing):

b1) comparing (ST61) the calling number of the called subscriber terminal (EP-B2) in the call setup message (ARQ) with the ranges of calling numbers (CN) in said private network configuration memory (PNCM) and if a match is found;

b2) reading out the RAS transport address associated to a range of calling numbers into which said calling number falls;

b3) removing the transport address part (Ta) of the readout RAS transport address (RASTA) to determine the network address of the controller (GK) to which the called subscriber terminal is connected; and

wherein

b4) said call router (CR) routes (ST66, ST67) the call setup message (ARQ) to the determined network address of the controller (GK).

15. A controller (FIG. 6) according to claim 14 and 13,

characterized in that

said call router (CR) determines the controller (GK) to which the call setup message (ARQ) is to be routed by further carrying out a further step b5) in which the determined network address (NA) is compared with the network part of RAS transport addresses (RASTA) of controllers (GK) stored in the second table (TB3) in which controllers are indicated to which a direct signaling connection can be built up.

16. A controller according to claim 15,

characterized in that

said call router (CR) determines the controller (GK) to which the call setup message (ARQ) is to be routed by further carrying out a further step b6) in which said call router (CR) sends (ST62;

ST82, ST83, ST84) a location enquiry message (LRQ) to the determined RAS transport address (RASTA).

17. A controller (FIG. 7) according to claim 16,

characterized in that

if said call router (CR) in response to sending (ST62) said location enquiry message (LRQ) to said determined RAS transport address (RASTA) receives (ST86, ST87) a location reject message (LRJ), said call router (CR) routes (ST74, ST75) said call setup message to the called subscriber station (EP-B₂) via a first gateway (GW-A) connected to the bus-network (A-BUS) with which the calling subscriber terminal (EP-A₃) is connected, a second interconnection network (VOICE, INET2) connected to the first gateway (GW-A) and a second gateway (GW-B) connected to the second interconnection network (VOICE, INET2) and to the bus network (B-BUS) to which the called subscriber terminal (EP-B2) is connected.

18. A controller according to claim 11,

characterized in that

said call router (CR) determines the controller (GK) to which the call setup message (ARQ) is to be routed by carrying out the following steps (FIG. 8) (location-based call routing):

b7) comparing the calling number of the called subscriber terminal (EP-B₂) in the call setup message (ARQ) with the ranges of calling numbers (CN) in said private network configuration memory (PNCM) and if no match is found;

b8) sending (ST82, ST83, ST84) a location enquiry message (LRQ) including a called subscriber terminal indication (EP-B alias) to each transport address (RASTA) of controllers (GK) which are indicated as belonging to the private network identified by said stored private network identifier (PNID) and to which a direct signaling connection can be setup;

b9) sending (ST810), in response to receiving a location confirmation message (LCF) including a call signaling transport address (CSTA) from one of the controllers (GK) to whose zone (B) the called subscriber terminal (EP-B₂) belongs, the setup message setup to said call signaling transport address (CSTA).

19. A controller according to claim 11,

characterized by

said controller (GK) further comprising a controller characteristics memory (CCM) for storing information about the call routing technique (called number based routing or location based routing) which must be used when setting up a call to a subscriber station connected to the controller (GK).

20. A controller according to claim 18 or claims 14 and 19,

characterized in that

said call router (CR) uses the call routing technique according to steps b1)-b5) (FIG. 6) if said call routing technique indicates a called number based routing and uses the call routing technique according to steps b7)-b9) (FIG. 8) if said call routing technique indicates a location based routing.

23. A method for routing calls in a communication system (SYS) including in each of a plurality of geographically distant zones (ZA, ZB, ZC) a zone-specific controller (GK) and one or more subscriber terminals (EP) connected to each other via a zone-specific bus network (BUS-A, BUS-D, BUS-C), said zone-specific bus networks being connected to each other via at least one interconnection network (WAN), wherein said controller (GK) controls the signaling traffic between the subscriber terminals (EP) in each zone and between different zones and carries out the following steps:

a) storing in a controller characteristics memory (CCM) for storing at least a private network identifier (PNID) of a private network (PN) to which said zone-specific controller (GK) and its connected subscriber terminals (EP) belong;

b) storing in a private network configuration memory (PNCM) for storing the private network configuration at least of the private network identified by the stored private network identifier (PNID); and

c) communicating (GRQ, GCF, GRJ) with all other controllers (GK) of the communication system (SYS) to determine the private network configuration including those controllers (GK) and subscriber stations (EP) in other zones (B, C) which belong to the private network (PN) identified by the stored private network identifier (PNID) and to store corresponding private network configuration information (RASTA;

RA;

CNCT) in said private network configuration memory (PNCM).

24. A method for call routing in a communication system (SYS) including in each of a plurality of geographically distant zones (A, B, C) a zone-specific controller (GK) and one or more subscriber terminals (EP) connected to each other via a zone-specific bus network (BUS-A, BUS-D, BUS-C), said zone-specific bus networks being connected to each other via at least one interconnection network (WAN), wherein the controller (GK) controls the signaling traffic between the subscriber terminals (EP) in each zone and between different zones and carries out the following steps:

a) storing a private network configuration memory (PNCM) for storing the private network configuration at least of the private network identified by a private network identifier (PNID); and

b) receiving from a subscriber terminal (e.g. EP-A₃) connected to said controller (GK) a call setup message (ARQ) indicating a call setup to another subscriber terminal (e.g. EP-B₂);

c) determining on the basis of the private network configuration information (RASTA, RA, CNCT) in the private network configuration memory (PNCM) the controller (GK) to which said called subscriber terminal (e.g. EP-B₂) is connected; and

d) routing the call setup message (ARQ) to the determined controller.