Connection control module

• US 20010028646A1
• Filed: 04/10/2001
• Published: 10/11/2001
• Est. Priority Date: 04/11/2000
• Status: Active Grant

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Alcatel SA (Nokia Corporation)
• Inventors: Arts, Francis, Coenen, Maria, De Vleeschouwer, Hans
• Granted Patent: US 7,420,966 B2
• Time in Patent Office: Days
• US Class Current: 370/386
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04Q 11/04 for time-division multiplexing H04Q11/0001 takes precedence

Abstract

A connection control module of a switching node in a telecommunications network, and adapted to communicate to a service control module of said switching node is further adapted to communicate to at least one other connection control module of said switching node. This approach enables to establish connections at the physiccal level by linking half-call connections at this level.

Claims

1. Connection control module (CCM1;

CCM2) of a switching node in a telecommunications network, said connection control module (CCM1;

CCM2) being adapted to communicate to a service control module (SC1a;

SC2a) of said switching node

characterised in that

said connection control module (CCM1;

CCM2) is further adapted to communicate via a connection control interface to at least one other connection control module (CCM2;

CCM1) of said switching node.

2. Connection control module (CCM1;

CCM2) according to

claim 1

characterised in that

said connection control module (CCM1;

CCM2) is further adapted to communicate with at least one other service control module (SC1b;

SC2b) of said switching node.

3. Connection control module (CCM1;

CCM2) according to

claim 1

characterised in that

said connection control module (CCM1;

CCM2) further includes a service interface handler (SIH1;

SIH2), said service interface handler (SIH1;

SIH2) is adapted to receive from said service control module (SCM1a;

SCM2a) a service request message (SRM1;

SRM2,LRQM2), to analyse said service request message and to perform an action, dependent on the result of the analysis of said service request message.

4. Connection control module (CCM1;

CCM2) according to

claim 3

characterised in that

in case said result of said analysis of said service request message indicates that at least one of a predetermined type of physical device drivers is needed for establishing a connection pertaining to a call, said action consists of generating a physical device interface handler module (PDIH1;

PDIH2), associated to said predetermined type of said physical device drivers, for inclusion in said connection control module (CCM1;

CCM2).

5. Connection control module (CCM1;

CCM2) according to

claim 4

characterised in that

said physical device interface handler module (PDIH1;

PDIH2) is further adapted to transmit to an associated resource manager module (RM) included in said switching node, a resource request message (RRM1;

RRM2), said associated resource manager module (RM) being adapted to select from a plurality of said physical device drivers of said predetermined type and included in or coupled to said switching node, and based upon said resource request message (RRM1;

RRM2), an associated physical device driver (DD1;

DD2) of said plurality.

6. Connection control module (CCM1;

CCM2) according to

claim 5

characterised in that

said physical device interface handler module (PDIH1;

PDIH2) is further adapted to activate said associated physical device driver (DD1;

DD2), and to confirm said operation to said service interface handler (SIH1;

SIH2).

7. Connection control module (CCM1;

CCM2) according to

claim 6

characterised in that

said service interface handler (SIH1;

SIH2) is further adapted to confirm said operation to said service control module (SC1a;

SC2a).

8. Connection control module (CCM1;

CCM2) according to

claim 3

characterised in that

in case said result of said analysis of said service request message indicates that a physical device driver of said switching node is to be removed from an existing call connection,

said action consists of deleting an existing physical device interface handler module (PDIH1;

PDIH2) associated to said physical device driver and included within said connection control module.

9. Connection control module (CCM1;

CCM2) according to

claim 3

characterised in that

in case said result of said analysis of said service request message indicates that the operation of a physical device driver of said switching node is to be modified

said action consists of initiating a state change within an existing physical device interface handler (PDIH1;

PDIH2) associated to said physical device driver and included within said connection control module (CCM1;

CCM2).

10. Connection control module (CCM1) according to

claim 3

characterised in that

in case said result of said analysis of said service request message indicates that said at least one other connection control module is involved,

said service interface handler (SIH1) is further adapted to communicate to a service interface handler (SIH2) of said at least one other connection control module.

11. Connection control module (CCM1) according to

claim 10

characterised in that

upon communication with said service interface handler of said at least one other connection control module, said service interface handler (SIH1) is further adapted to communicate to a physical device interface handler referred to in said service request message and included in said connection control module

12. Connection control module (CCM1) according to

claim 11

characterised in that

said physical device interface handler referred to in said service request message is further adapted to communicate with a second physical device interface handler referred to in said service request message and included in said at least one other connection control module (CCM2).