Session initiation protocol based advanced intelligent network/intelligent network messaging
View Patent ↗A method and system enables distributed transaction oriented telephony functionality for telephony services in a broadband packet network. Exemplary distributed transaction oriented telephony functionality includes Intelligent Network (IN) and Advanced Intelligent Network (AIN) functionality accessed through the legacy Common Channel Signaling (CCS) network using transaction-based messaging protocols, such as Intelligent Network Application Part (INAP) and/or Transaction Capability Application Part (TCAP) protocols. A functional content of a transaction message, such as a TCAP message, is encapsulated in a Protocol Data Unit (PDU) of the broadband packet network. The PDU is forwarded through the broadband packet network to a second network element. The functionality is then invoked using the encapsulated transaction message functional content. In preferred embodiments the PDU is a Session Initiation Protocol (SIP) envelope, into which TCAP message functional content can be mapped.
1. A method of enabling distributed transaction oriented telephony functionality for telephony services deployed in a broadband packet network, the method comprising steps of:
at a first network element comprising a media gateway controller adapted to enable telephony signal traffic through the broadband packet network, encapsulating a functional content of a transaction message in a Protocol Data Unit (PDU) of the broadband packet network;
forwarding the PDU through the broadband packet network to a second network element; and
at the second network element, invoking the functionality using the encapsulated transaction message functional content.
2. A method as claimed in claim 1 , wherein the distributed transaction oriented telephony functionality comprises intelligent network/advanced intelligent network (IN/AIN) functionality.
3. A method as claimed in claim 1 , wherein the broadband packet network comprises any one or more of: an Asynchronous Transfer Mode (ATM) network; an internet Protocol (IP) network; a Frame Relay (FR) network; and an Integrated Services Digital Network (ISDN).
4. A method as claimed in claim 3 , wherein the broadband packet network comprises an IP Network, and the PDU comprises a Session Initiation Protocol (SIP) message envelope.
5. A method as claimed in claim 1 , wherein the second network element comprises an application server adapted to invoke the functionality using transaction message functional content.
6. A method as claimed in claim 5 , wherein the application server comprises either one of:
a CCS network element adapted to send and receive PDU's of the broadband packet network; and
a network element of the broadband packet network.
7. A method as claimed in claim 1 , wherein the step of encapsulating the functional content of the transaction message comprises the steps of:
formulating a transaction message; and
inserting the formulated transaction message into a payload portion of the PDU.
8. A method as claimed in claim 7 , wherein the transaction message comprises either one of a Transaction Capabilities Application Part (TCAP) message and an Intelligent Network Application Pan (NAP) message.
9. A method as claimed in claim 1 , wherein the step of encapsulating the functional content of the transaction message comprises a step of mapping the transaction message onto the PDU.
10. A method as claimed in claim 9 , wherein the transaction message comprises a Transaction Capabilities Application Part (TCAP) message.
11. A method as claimed in claim 10 , wherein the step of mapping comprises a step of mapping a TCAP message type onto a respective message type of the PDU.
12. A method as claimed in claim 11 , wherein the TCAP message type comprises any one or more of: query; response; conversation; unidirectional; and abort.
13. A method as claimed in claim 9 , wherein the transaction message comprises an Intelligent Network-Application Part (INAP) message.
14. A method as claimed in claim 13 , wherein the step of mapping comprises a step of mapping an INAP message type onto a respective message type of the PDU.
15. A method as claimed in claim 14 , wherein the INAP message type comprises any one or more of: begin; end; continue; unidirectional; and abort.
16. A method as claimed in claim 9 , wherein the step of mapping comprises a step of mapping a transaction message parameter onto a respective PDU message parameter.
17. A method as claimed in claim 16 , wherein the transaction message parameter comprises any one or more of: an origination address and a destination address.
18. A method as claimed in claim 16 , wherein the transaction message parameter is mapped to a respective overhead field of the PDU.
19. A method as claimed in claim 9 , wherein the step of mapping comprises a step of mapping an encoded message payload into a payload of the PDU.
20. A method as claimed in claim 19 , wherein the encoded message payload is mapped into a payload portion of a MIME part of the PDU.
21. A method as claimed in claim 20 , wherein the transaction message comprises two or more encoded payload portions.
22. A method as claimed in claim 21 , wherein each encoded payload portion is mapped to a respective individual MIME payload.
23. A method as claimed in claim 21 , wherein the encoded payload portions are mapped to a common MIME payload.
24. A system enabling distributed transaction oriented telephony functionality for telephony services in a broadband packet network, the system comprising:
a first network element adapted to encapsulate a functional content of a transaction message in a Protocol Data Unit (PDU) of the broadband packet network, wherein the first network element comprises a media gateway controller adapted to enable telephony signal traffic through the broadband packet network; and
a second network element adapted to invoke the functionality using the encapsulated transaction message functional content.
25. A system as claimed in claim 24 , wherein the distributed transaction oriented telephony functionality comprises intelligent network/advanced intelligent network (IN/AIN) functionality.
26. A system as claimed in claim 24 , wherein the broadband packet network comprises any one or more of: an Asynchronous Transfer Mode (ATM) network; an internet Protocol (IP) network; a Frame Relay (FR) network; and an Integrated Services Digital Network (ISDN).
27. A system as claimed in claim 24 , wherein the broadband packet network comprises an IP Network, and the PDU comprises a Session Initiation Protocol (SIP) message envelope.
28. A system as claimed in claim 24 , wherein the second network element comprises an application server adapted to invoke the functionality using transaction message functional content.
29. A system as claimed in claim 28 , wherein the application server comprises either one of:
a CCS network element adapted to send and receive PDU's of the broadband packet network; and
a network element of the broadband packet network.
30. A system as claimed in claim 24 , wherein the first network element comprises:
means for formulating a transaction message; and
means for inserting the formulated transaction message into a payload portion of the PDU.
31. A method as claimed in claim 30 , wherein the transaction message comprises either one of a Transaction Capabilities Application Part (TCAP) message and an Intelligent Network Application Part (INAP) message.
32. A system as claimed in claim 24 , wherein the first network element comprises means for mapping the transaction message onto the PDU.
33. A system as claimed in claim 32 , wherein the transaction message comprises a Transaction Capabilities Application Pan (TCAP) message.
34. A system as claimed in claim 33 , wherein the means for mapping comprises means for mapping the TCAP message type onto a respective message type of the PDU.
35. A system as claimed in claim 34 , wherein the TCAP message type comprises any one or more of: query; response; conversation; unidirectional and abort.
36. A system as claimed in claim 32 , wherein the transaction message comprises an Intelligent Network-Application Part (INAP) message.
37. A system as claimed in claim 36 , wherein the means for mapping comprises means for mapping an INAP message type onto a respective message type of the PDU.
38. A system as claimed in claim 39 , wherein the INAP message type comprises any one or more of: begin; end; continue; unidirectional and abort.
39. A system as claimed in claim 32 , wherein the means for mapping comprises means for mapping a transaction message parameter onto a respective PDU message parameter.
40. A system as claimed in claim 39 , wherein the transaction message parameter comprises any one or more of: an origination address and a destination address.
41. A system as claimed in claim 40 , wherein the transaction message parameter is mapped to a respective overhead field of the PDU.
42. A system as claimed in claim 32 , wherein the means for mapping comprises means for mapping an encoded message payload into a payload of the PDU.
43. A system as claimed in claim 42 , wherein the encoded message payload is mapped into a payload portion of a MIME part of the PDU.
44. A system as claimed in claim 43 , wherein the transaction message comprises two or more encoded payload portions.
45. A system as claimed in claim 44 , wherein each encoded payload portion is mapped to a respective individual MIME payload.
46. A system as claimed in claim 44 , wherein the encoded payload portions are mapped to a common MIME payload.
47. A network node enabling distributed transaction oriented telephony functionality for telephony services in a broadband packet network, the node comprising means for encapsulating at least a functional content of a transaction message in a Protocol Data Unit (PDU) of the broadband packet network, and wherein the node comprises either one of:
a media gateway controller operative to enable telephony signal traffic through the broadband packet network; and
an application server operative to invoke IN/AIN functionality using TCAP functional content.
48. A node as claimed in claim 47 , wherein the distributed transaction oriented telephony functionality comprises intelligent network/advanced intelligent network (IN/AIN) functionality.
49. A node as claimed in claim 47 , wherein the broadband packet network comprises any one or more of: an Asynchronous Transfer Mode (ATM) network; an internet Protocol (IP) network; a Frame Relay (FR) network; and an Integrated Services Digital Network (ISDN).
50. A node as claimed in claim 49 , wherein the broadband packet network comprises an IP Network, and the PDU comprises a Session Initiation Protocol (SIP) message envelope.
51. A node as claimed in claim 47 , wherein the application server comprises either one of:
a CCS network element adapted to send and receive PDU's of the broadband packet network; and
a network element of the broadband packet network.
52. A node as claimed in claim 47 , further comprising:
means for formulating a transaction message; and
means for inserting the formulated transaction message into a payload portion of the PDU.
53. A node as claimed in claim 52 , wherein the transaction message comprises either one of a Transaction Capabilities Application Part (TCAP) message and an Intelligent Network Application Part (INAP) message.
54. A node as claimed in claim 47 , further comprising means for mapping the transaction message onto the PDU.
55. A node as claimed in claim 54 , wherein the transaction message comprises a Transaction Capability Application Part (TCAP) message.
56. A node as claimed in claim 55 , wherein the means for mapping comprises means for mapping a TCAP message type onto a respective message type of the PDU.
57. A node as claimed in claim 56 , wherein the TCAP message type comprises any one or more of: query; response; conversation; unidirectional; and abort.
58. A node as claimed in claim 54 , wherein the transaction message is an Intelligent Network Application Part (INAP) message.
59. A node as claimed in claim 58 , wherein the means for mapping comprises means for mapping the INAP message type onto a respective message type of the PDU.
60. A node as claimed in claim 59 , wherein the NAP message type comprises any one or more of: begin; end; continue; unidirectional; and abort.
61. A node as claimed in claim 54 , wherein the means for mapping comprises means for mapping a transaction message parameter onto a respective PDU message parameter.
62. A node as claimed in claim 61 , wherein the transaction message parameter comprises any one or more of: an origination address and a destination address.
63. A node as claimed in claim 61 , wherein the transaction message parameter is mapped to a respective overhead field of the PDU.
64. A node as claimed in claim 54 , wherein the means for mapping comprises means for mapping an encoded message payload into a payload of the PDU.
65. A node as claimed in claim 64 , wherein the encoded message payload is mapped into a payload portion of a MIME part of the PDU.
66. A node as claimed in claim 65 , wherein the transaction message comprises two or more encoded payload portions.
67. A node as claimed in claim 66 , wherein each encoded payload portion is mapped to a respective individual MIME payload.
68. A node as claimed in claim 66 , wherein the encoded payload portions are mapped to a common MIME payload.