Apparatus method and system for roamer originated automatic telecommunication conferencing and broadcasting

• US 6,421,324 B1
• Filed: 11/25/1998
• Issued: 07/16/2002
• Est. Priority Date: 11/25/1998
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Hotze, Karen, Thompson, Robin Jeffrey, McCormick, Mark Alan, Gafrick, John Matthew, Perkins, Kathleen Anne, FitzPatrick, Catherine Mary, Boyle, Patrick Joseph
• Primary Examiner(s): Olms, Douglas
• Assistant Examiner(s): VANDERPUYE, KENNETH N
• Application Number:
  US09/199,843
• Time in Patent Office: 1,329 Days
• Field of Search: 370/259, 370/260, 370/261, 370/263, 370/265, 370/266, 370/270, 370/401, 370/432, 370/328, 455/518, 455/414, 455/416, 455/422, 455/432, 455/433, 455/519, 379/201, 379/202, 379/204, 379/205, 709/204
• US Class Current: 370/261
• CPC Class Codes: H04M 2207/18 wireless networks
• CPC Class Codes: H04M 3/56 Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities video conference systems H04N7/15
• CPC Class Codes: H04W 76/40 for selective distribution or broadcast

Abstract

An apparatus, method and system are provided for roamer originated automatic telecommunication conferencing and broadcasting. The system embodiment includes a first switch for reception of a first incoming call leg from a roaming mobile unit or from another telecommunication device outside its assigned serving area. The first incoming call leg preferably designates a multiple leg service, such as a telecommunication conference, and also designates a subscriber group. Each particular subscriber group is predefined, and consists of a list of directory numbers to be included within the conference or broadcast session. In the various embodiments, the first switch communicates with a second switch or a database, and obtains a routing directory number to reroute the first incoming call leg, to form a second incoming call leg to the second switch. The system embodiment also includes a conference bridge coupled to the second switch, in which the conference bridge includes instructions to receive the second incoming call leg routed from the second switch, to determine the plurality of directory numbers associated with the subscriber group, and to return to the second switch a plurality of intermediate incoming call legs corresponding to the plurality of directory numbers for routing by the second switch to form a plurality of outgoing call legs. The conference bridge also includes further instructions to monitor answering of the plurality of outgoing call legs, and to connect an outgoing call leg indicating joinder, of the plurality of outgoing call legs, to the conference bridge for a multiple leg telecommunication session, such as a conference or broadcast session.

Claims

1. A method for roamer originated telecommunication conferencing and broadcasting, the method comprising:

(a) receiving at a first switch a first incoming call leg designating a multiple leg service and a subscriber group;

(b) routing the first incoming call leg as a second incoming call leg to a second switch;

(c) routing the second incoming call leg to a conference bridge;

(d) determining a plurality of directory numbers associated with the subscriber group;

(e) returning to the second switch a plurality of independent intermediate incoming call legs corresponding to the plurality of directory numbers for routing to form a plurality of independent outgoing call legs;

(f) monitoring answering of the plurality of outgoing call legs; and

(g) when an outgoing call leg, of the plurality of outgoing call legs, indicates joinder, connecting the outgoing call leg to the conference bridge for a multiple leg telecommunication session with the second incoming call leg.

2. The method of claim 1, wherein step (b) further comprises:

transmitting a message to the second switch;

transmitting a response to the first switch, wherein the response includes a routing directory number designating a multiple leg telecommunication session.

3. The method of claim 2, wherein the response further includes a first parameter identifying the subscriber group.

4. The method of claim 3, wherein the first parameter is encoded as destination digits.

5. The method of claim 2, wherein the response further includes a second parameter indicating a multiple leg telecommunication session.

6. The method of claim 5, wherein the second parameter is encoded as a DMH redirection indicator.

7. The method of claim 2, wherein step (c) further comprises:

releasing the routing directory number.

8. The method of claim 2, wherein the message is a feature request and wherein the response is a feature request return result.

9. The method of claim 2, wherein the message is an origination request and wherein the response is an origination request return result.

10. The method of claim 1, wherein step (b) further comprises:

transmitting a first message to a database;

transmitting a first response to the first switch, wherein the first response includes a routing directory number designating a multiple leg telecommunication session.

11. The method of claim 10, wherein the routing directory number is selected from a plurality of routing directory numbers predesignated to indicate a multiple leg telecommunication session.

12. The method of claim 10, wherein the first response further includes a first parameter identifying the subscriber group.

13. The method of claim 12, wherein the first parameter is encoded as destination digits.

14. The method of claim 10, wherein the first response further includes a second parameter indicating a multiple leg telecommunication session.

15. The method of claim 14, wherein the second parameter is encoded as a DMH redirection indicator.

16. The method of claim 10, further comprising:

transmitting a second message to the second switch; and

transmitting a second response to the database, wherein the second response includes the routing directory number designating a multiple leg telecommunication session.

17. The method of claim 16, wherein the second message is a routing request, and wherein the second response is a routing request return result.

18. The method of claim 10, wherein the first message is a feature request and wherein the first response is a feature request return result.

19. The method of claim 10, wherein the first message is an origination request and wherein the first response is an origination request return result.

20. The method of claim 1, wherein the second incoming call leg includes a routing directory number as a called party, a mobile directory number as a calling party, and a subscriber group identification.

21. The method of claim 20, wherein the subscriber group identification is encoded as a generic digits parameter.

22. The method of claim 1, further comprising:

terminating the multiple leg telecommunication session upon reception of an on hook message from the first incoming call leg.

23. The method of claim 1, further comprising:

terminating the multiple leg telecommunication session upon reception of an on hook message from a penultimate call leg remaining from a plurality of call legs forming the multiple leg telecommunication session.

24. The method of claim 1, further comprising:

connecting all outgoing call legs indicating joinder, of the plurality of outgoing call legs, to the conference bridge for the multiple leg telecommunication session.

25. The method of claim 1 wherein joinder is indicated by an answering of the outgoing call leg.

26. The method of claim 1 wherein joinder is indicated by an answering of the outgoing call leg followed by reception of a predesignated code.

27. The method of claim 1, wherein the plurality of directory numbers corresponding to a subscriber group are predefined and stored in a database.

28. The method of claim 27, wherein determining the plurality of directory numbers is performed by a database query designating the subscriber group.

29. The method of claim 27, wherein determining the plurality of directory numbers is performed by a first database query designating the subscriber group to obtain a predefined pseudo-random number, followed by a second database query designating the predefined pseudo-random number to obtain the plurality of directory numbers corresponding to the subscriber group.

30. The method of claim 1, wherein step (d) further comprises transmitting an ISUP initial address message, for each intermediate incoming call leg of the plurality of intermediate incoming call legs, wherein the ISUP initial address message includes a called party directory number, a calling party directory number, an identification of the subscriber group, and an indication of the multiple leg service.

31. The method of claim 1, wherein step (c) further comprises transmitting an ISUP initial address message, wherein the ISUP initial address message includes a calling party directory number, an identification of the subscriber group, and an indicator of a type of multiple leg service.

32. The method of claim 1, further comprising:

releasing an outgoing call leg, of the plurality of outgoing call legs, which has remained unanswered for a predetermined period of time.

33. The method of claim 1, wherein step (f) further comprises:

transmitting a message on the first incoming call leg indicating a number of outgoing call legs which have joined the multiple leg telecommunication session.

34. A system for roamer originated telecommunication conferencing and broadcasting, the system comprising:

a first switch, the first switch for reception of a first incoming call leg designating a multiple leg service and a subscriber group and for routing the first incoming call leg to form a second incoming call leg;

a second switch coupled to the first switch, the second switch for reception of the second incoming call leg; and

a conference bridge coupled to the second switch, the conference bridge including instructions to receive the second incoming call leg routed from the second switch, to determine a plurality of directory numbers associated with the subscriber group, and to return to the second switch a plurality of independent intermediate incoming call legs corresponding to the plurality of directory numbers for routing by the second switch to form a plurality of independent outgoing call legs;

the conference bridge including further instructions to monitor answering of the plurality of outgoing call legs, and when an outgoing call leg, of the plurality of outgoing call legs, indicates joinder, the conference bridge including further instructions to connect the outgoing call leg to the conference bridge for a multiple leg telecommunication session with the second incoming call leg.

35. The system of claim 34, wherein the second switch includes a database.

36. The system of claim 35, wherein the database is an integrated home location register.

37. The system of claim 35, wherein the first switch includes instructions to transmit a message to the second switch, and wherein the second switch includes instructions to transmit a response to the first switch, wherein the response includes a routing directory number designating a multiple leg telecommunication session.

38. The system of claim 37, wherein the response further includes a first parameter identifying the subscriber group.

39. The system of claim 38, wherein the first parameter is encoded as destination digits.

40. The system of claim 37, wherein the response further includes a second parameter indicating a multiple leg telecommunication session.

41. The system of claim 40, wherein the second parameter is encoded as a DMH redirection indicator.

42. The system of claim 37, wherein the second switch includes further instructions to release the routing directory number upon routing the second incoming call leg to the conference bridge.

43. The system of claim 37, wherein the message is a feature request and wherein the response is a feature request return result.

44. The system of claim 37, wherein the message is an origination request and wherein the response is an origination request return result.

45. The system of claim 34, further comprising a database coupled to the first switch.

46. The system of claim 45, wherein the database is a home location register.

47. The system of claim 45, wherein the first switch includes instructions to transmit a first message to the database, and wherein the database includes instructions to transmit a first response to the first switch, wherein the first response includes a routing directory number designating a multiple leg telecommunication session.

48. The system of claim 47, wherein the routing directory number is selected from a plurality of routing directory numbers predesignated to indicate a multiple leg telecommunication session.

49. The system of claim 47, wherein the first response further includes a first parameter identifying the subscriber group.

50. The system of claim 49, wherein the first parameter is encoded as destination digits.

51. The system of claim 47, wherein the first response further includes a second parameter indicating a multiple leg telecommunication session.

52. The system of claim 51, wherein the second parameter is encoded as a DMH redirection indicator.

53. The system of claim 47, wherein the database is further coupled to the second switch.

54. The system of claim 53, wherein the database includes further instructions to transmit a second message to the second switch, and wherein the second switch includes further instructions to transmit a second response to the database, wherein the second response includes the routing directory number designating a multiple leg telecommunication session.

55. The system of claim 54, wherein the second message is a routing request, and wherein the second response is a routing request return result.

56. The system of claim 47, wherein the first message is a feature request and wherein the first response is a feature request return result.

57. The system of claim 47, wherein the first message is an origination request and wherein the first response is an origination request return result.

58. The system of claim 34, wherein the second incoming call leg includes a routing directory number as a called party, a mobile directory number as a calling party, and a subscriber group identification.

59. The system of claim 34, wherein the conference bridge includes further instructions to terminate the multiple leg telecommunication session upon reception of an on hook message from the first incoming call leg.

60. The system of claim 34, wherein the conference bridge includes further instructions to terminate the multiple leg telecommunication session upon reception of an on hook message from a penultimate call leg remaining from a plurality of call legs forming the multiple leg telecommunication session.

61. The system of claim 34, wherein the conference bridge includes further instructions to connect all outgoing call legs indicating joinder, of the plurality of outgoing call legs, to the conference bridge for the multiple leg telecommunication session.

62. The system of claim 34 wherein the conference bridge includes further instructions to determine joinder by an answering of the outgoing call leg.

63. The system of claim 34 wherein the conference bridge includes further instructions to determine joinder by an answering of the outgoing call leg followed by reception of a predesignated code.

64. The system of claim 34, further comprising a database coupled to the conference bridge, and wherein the database stores the plurality of directory numbers corresponding to the subscriber group.

65. The system of claim 64, wherein the conference bridge includes further instructions to determine the plurality of directory numbers by a database query designating the subscriber group.

66. The system of claim 64, wherein the database is further coupled to the second switch, and wherein the second switch includes instructions to perform a first database query designating the subscriber group to obtain a predefined pseudo-random number, and wherein the conference bridge includes further instructions to perform a second database query designating the predefined pseudo-random number to obtain the plurality of directory numbers corresponding to the subscriber group.

67. The system of claim 34, wherein the conference bridge includes further instructions to transmit an ISUP initial address message to the second switch, for each intermediate incoming call leg of the plurality of intermediate incoming call legs, wherein the ISUP initial address message includes a called party directory number, a calling party directory number, an identification of the subscriber group, and an indication of the multiple leg service.

68. The system of claim 34, wherein the second switch includes instructions to transmit an ISUP initial address message to the conference bridge, wherein the ISUP initial address message includes a calling party directory number, an identification of the subscriber group, and an indicator of a type of multiple leg service.

69. The system of claim 34, wherein the conference bridge includes further instructions to release an outgoing call leg, of the plurality of outgoing call legs, which has remained unanswered for a predetermined period of time.

70. The system of claim 34, wherein the conference bridge includes further instructions to transmit a message on the first incoming call leg indicating a number of outgoing call legs which have joined the multiple leg telecommunication session.

71. An apparatus for roamer originated telecommunication conferencing and broadcasting, the apparatus couplable to a conference bridge, the apparatus comprising:

a memory, the memory storing a plurality of routing directory numbers designating a multiple leg telecommunication session;

a network interface, the network interface for reception of an incoming call leg having a routing directory number of the plurality of routing directory numbers, the incoming call leg further having a designation of a subscriber group, the network interface further for reception and subsequent routing of a plurality of intermediate call legs to form a plurality of outgoing call legs to a corresponding plurality of directory numbers associated with the subscriber group for the multiple leg telecommunication session; and

a processor coupled to the network interface and to the memory, the processor including instructions to recognize the routing directory number of the incoming call leg as designating a multiple leg telecommunication session, and to direct the network interface to transfer the incoming call leg having the routing directory number to the conference bridge to obtain the plurality of intermediate call legs.

72. The apparatus of claim 71, further comprising a database coupled to the processor.

73. The apparatus of claim 72, wherein the database is an integrated home location register.

74. The apparatus of claim 72, the apparatus further couplable to a first switch, wherein the processor includes instructions to, upon reception of a message from the first switch, transmit a response via the network interface to the first switch, wherein the response includes the routing directory number designating a multiple leg telecommunication session.

75. The apparatus of claim 74, wherein the processor includes further instructions to include in the response a first parameter identifying the subscriber group.

76. The apparatus of claim 75, wherein the processor includes further instructions to encode the first parameter as destination digits.

77. The apparatus of claim 74, wherein the processor includes further instructions to include in the response a second parameter indicating a multiple leg telecommunication session.

78. The apparatus of claim 77, wherein the processor includes further instructions to encode the second parameter as a DMH redirection indicator.

79. The apparatus of claim 74, wherein the processor includes further instructions to release the routing directory number upon directing the transfer of the incoming call leg to the conference bridge.

80. The apparatus of claim 74, wherein the message is a feature request and wherein the response is a feature request return result.

81. The apparatus of claim 74, wherein the message is an origination request and wherein the response is an origination request return result.

82. The apparatus of claim 71, wherein the plurality of routing directory numbers are predesignated to indicate a multiple leg telecommunication session.

83. The apparatus of claim 71, the apparatus further couplable to a database, wherein the processor includes instructions to, upon reception of a message from the database, transmit a response via the network interface to the database, wherein the response includes the routing directory number designating a multiple leg telecommunication session.

84. The apparatus of claim 83, wherein the processor includes further instructions to release the routing directory number upon directing the transfer of the incoming call leg to the conference bridge.

85. The apparatus of claim 83, wherein the message is a routing request and wherein the response is a routing request return result.

86. The apparatus of claim 71, wherein the incoming call leg includes the routing directory number as a called party, a mobile directory number as a calling party, and a subscriber group identification.

87. The apparatus of claim 86, wherein the subscriber group identification is encoded as a generic digits parameter.

88. The apparatus of claim 71, wherein the processor includes further instructions, in directing the incoming call leg to be transferred to the conference bridge, to utilize a generic digits parameter encoding the subscriber group as a called party number, and to forward a calling party directory number.