# US 2018/0324305 A1 · System and method for setting up a group call

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0324305 A1
- Document ID: US20180324305A1
- Status: Published application
- Kind: A1
- Application number: 15/769,199
- Filed: 2016-10-10
- Published: 2018-11-08
- Earliest claimed: 2015-10-19
- Assignees: Rebtel Networks AB
- Applicants: Rebtel Networks AB
- Inventors: Johan Dahlqvist; Vasco Preto; Andrew Kaminski; Thomas Kyritsis; Pär Lindhe; Thomas Skoglund; Suresh Kumar; Amir Mortazavi; Christopher Connor
- Web page: https://patentgrep.com/patent/US20180324305A1

## CPC

- H04M 3/56: Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities (video conference systems H04N7/15)
- H04M 3/02: Calling substations, e.g. by ringing (selective calling H04Q)
- H04M 7/003: {Click to dial services}
- H04M 7/0057: {Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network}
- H04M 2203/2016: Call initiation by network rather than by subscriber
- H04M 2207/187: combining circuit and packet-switched, e.g. GPRS
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A group call is setup between one originating device (A) and at least two terminating devices (B, C), which each has access to a public land mobile network (131, 132, 133) and a mobile data net-work (121, 122, 123). The originating and terminating devices (A, B, C) include a respective software-implemented call handling tool (SWA, SWB, SWC) configured to assist a user in placing and receiving group calls. Bridge nodes (141, 142, 143) are connected to the mobile data network (121, 122, 123), the public land mobile network (131, 132, 133) and a server node (110), which, in turn, also is connected to the mobile data network (121, 122, 123). In response to a call-setup command from a user of the originating device (A), the software-implemented call handling tool (SWA), on one hand, sends a call-setup request (1) to the server node (110); and on the other hand, makes a first call (2) to a first bridge node (141) over the public land mobile network (131) using a first telephone number (#1) stored in the originating device (A). The call-setup request (1) indicates an identity of the terminating devices (B, C). Based on the call-setup request (1) and the first call (2), the server node (110) sets up a call between the originating and terminating devices (A, B, C) over a conference bridge (146) in the first bridge node (141), plus possibly other bridge nodes (147, 148) depending on where the devices (A, B, C) are located relative to one another.

## Claims

### Claim 1

A system for setting up a group call between one originating device and at least two terminating devices, the originating and terminating devices each having access both to a public land mobile network and a mobile data network, the originating and terminating devices including a respective software-implemented call handling tool configured to assist a user in the process of placing and receiving group calls, the system comprising:
a server node connected to the mobile data network, and
at least one bridge node connected to the server node, the mobile data network and the public land mobile network,
the server node being configured to:
receive a call-setup request from the originating device, the call-setup request being generated by the software-implemented call handling tool in the originating device in response to a call-setup command from a user of the originating device, the call-setup request indicating a respective identity of the at least two terminating devices, and
based on the call-setup request, set up a group call between the originating device and the at least two terminating devices over at least one conference bridge in the at least one bridge node,
wherein in response to the call-setup command, the software-implemented call handling tool in the originating device is further configured to make a first call to a first bridge node of the at least one bridge node over the public land mobile network using a first telephone number stored in the originating device.

### Claim 2 (depends on 1)

The system according to claim 1, wherein the software-implemented call handling tool in the originating device is configured to select the first telephone number based on a location of the originating device.

### Claim 3 (depends on 1)

The system according to claim 1, wherein, in response to the first call, the first bridge node is configured to send a first bridge-acknowledge message to the server node, the first bridge-acknowledge message specifying a first network address of the first bridge node.

### Claim 4 (depends on 1)

The system according to claim 1, wherein, in response to the call-setup request, the server node is configured to send a respective service message to each of the at least two terminating devices, the service messages indicating an identity of the originating device and a petition to establish a voice connection with the at least two terminating devices.

### Claim 5 (depends on 4)

The system according to claim 4, wherein, in response to the service messages, the software-implemented call handling tool in each of the at least two terminating devices is configured to generate a first type of alert signal adapted to notify a user of an incoming group call from the originating device.

### Claim 6 (depends on 5)

The system according to claim 5, wherein, after having initiated the first type of alert signal, the software-implemented call handling tool in each of the at least two terminating devices is configured to make a reply call to at least one second bridge node of the at least one bridge node in response to a respective user's accept command, the reply calls being made over the public land mobile network using a respective reply telephone number.

### Claim 7 (depends on 6)

The system according to claim 6, wherein the software-implemented call handling tool in each of the terminating devices is configured to select the reply telephone number based on a respective location of the terminating device.

### Claim 8 (depends on 6)

The system according to claim 6, wherein the reply telephone number is stored in the terminating device.

### Claim 9 (depends on 6)

The system according to claim 6, wherein, in response to the reply call, the at least one second bridge node is configured to send a second bridge-acknowledge message to the server node, the second bridge-acknowledge message specifying a second network address of the second bridge node; and
in response to the first and second bridge-acknowledge messages, the server node is configured to send a respective bridge-prompting message to the first and second bridge nodes.

### Claim 10 (depends on 9)

The system according to claim 9, wherein, in response to the bridge-prompting messages, the first and second bridge nodes are configured to cause connections between the originating device and the at least two terminating device over the at least one conference bridge.

### Claim 11 (depends on 10)

The system according to claim 10, wherein if:
a connection has been established between the originating device and at least one first device of the at least two terminating devices, and
no user's accept command has been received in at least one non-connected device of the at least two terminating devices within a response interval after having initiated the first type of alert signal,
the server node is configured to send a call-in-progress notification to the at least one non-connected device, and
in response thereto, the software-implemented call handling tool in the at least one non-connected device is configured to generate a second type of alert signal adapted to notify a user of an ongoing call to which the at least one non-connected device can be connected.

### Claim 12 (depends on 10)

The system according to claim 10, wherein a definition of a group of subscribers is stored in a database accessible by the server node, each of the subscribers in the group of subscribers being associated with a particular device, and if a connection has been established between a set of devices associated with a sub-group of subscribers in the group of subscribers,
the server node is configured to send a call-in-progress notification to each non-connected device that is associated with a subscriber of the group however that is not included in the sub-group, and in response thereto
the software-implemented call handling tool in each of the non-connected devices is configured to generate a second type of alert signal adapted to notify a user of an ongoing call to which the non-connected device can be connected.

### Claim 13 (depends on 11)

The system according to claim 11, wherein in response to a received user command designating the ongoing call, the software-implemented call handling tool in the non-connected device is configured to make the reply call to the second bridge node of the at least one bridge node over the public land mobile network using the reply telephone number.

### Claim 14 (depends on 1)

The system according to claim 1, wherein after that a group call has been set up between the originating device and the at least two terminating devices, the software-implemented call handling tool in each of said devices is configured to:
generate the call-setup request in respect of at least one additional terminating device to be included in the group call in response to a call-setup command from a user,
send a call-disconnect request in respect of at least one of said devices to the server node in response to a call-disconnect command from a user, the server node being configured to cause a device specified in the call-disconnect request to be disconnected from the group call, or
send a mute request in respect of at least one of said devices to the server node in response to a muting command from a user, the server node being configured to cause a temporary interruption in an exchange of acoustic data between a device specified in the mute request and the other devices of said devices.

### Claim 15

A method of setting up a group call between one originating device and at least two terminating devices, the originating and terminating devices each having access both to a public land mobile network and a mobile data network, the originating and terminating devices including a respective software-implemented call handling tool configured to assist a user in the process of placing and receiving group calls, the system comprising: a server node connected to the mobile data network, and at least one bridge node connected to the server node, the mobile data network and the public land mobile network, the method comprising:
receiving in the server node a call-setup request from the originating device, the call-setup request being generated by the software-implemented call handling tool in the originating device in response to a call-setup command from a user of the originating device, the call-setup request indicating a respective identity of the at least two terminating devices, and
based on the call-setup request, setting up a group call between the originating device and the at least two terminating devices over at least one conference bridge in the at least one bridge node, wherein
making, via the software-implemented call handling tool in the originating device, a first call to a first bridge node of the at least one bridge node over the public land mobile network using a first telephone number stored in the originating device in response to the call-setup command.

### Claim 16 (depends on 15)

The method according to claim 15, comprising:
selecting, via the software-implemented call handling tool in the originating device, the first telephone number based on a location of the originating device.

### Claim 17 (depends on 15)

The method according to claim 15, comprising:
sending, in response to the first call, a first bridge-acknowledge message from the first bridge node to the server node, the first bridge-acknowledge message specifying a first network address of the first bridge node.

### Claim 18 (depends on 15)

The method according to claim 15, comprising:
sending from the server node, in response to the call-setup request, a respective service message to each of the at least one terminating device, the service messages indicating an identity of the originating device and a petition to establish a voice connection with the at least two terminating devices.

### Claim at position 19

19-29. (canceled)

### Claim 30 (depends on 15)

A computer program product loadable into the memory of at least one processor, comprising software for executing the method of claim 15, when said computer program product is run on the at least one processor.

### Claim 31 (depends on 15)

A processor-readable medium comprising instructions which, when executed by at least one processor, cause the at least one processor to perform a method according to claim 15.
