User experience enhancements for controlling group communication
Abstract
Problem to be solved.To improve a user experience for conducting a group communication session. The present invention includes displaying visual feedback on a display to indicate the state of a group communication session. In response to user input, the step of establishing a group communication channel with the device in the first mode of operation, the step of detecting the activation of the target-based sliding lock mechanism on the touch screen, and the group communication during the lock mechanism operation. Includes a step of maintaining the channel in the second mode of operation. In response to user input, a step to start a group communication session, a step to detect the user's activation of the locking mechanism on the touch screen, and a step to detect the activation of the locking mechanism in response to the detected activation of the locking mechanism to obtain the priority floor. It may include a step of sending a request to the server and a step of keeping the group communication channel in priority acquisition mode while the locking mechanism is operating. [Selection diagram] Fig. 12

Term
Projected expiry 23 June 2036.
- Priority
- Filed
- Published
- Today
- Projected expiry
115 claims: 33 independent, 82 dependent
- 1ワイヤレス通信デバイス上でグループ通信セッションを行う方法であって、 ユーザインターフェース上でのユーザ入力に応答して、第1の動作モードで1つまたは複数のデバイスとのグループ通信チャネルを確立するステップと、 前記ワイヤレス通信デバイスのタッチスクリーンユーザインターフェースディスプレイ上でのユーザによるターゲットベースのスライディングロック機構の作動を検出するステップと、 前記ロック機構が作動している間、前記グループ通信チャネルを第2の動作モードで維持するステップとを含む、方法。
- 2前記ターゲットベースのスライディングロック機構の解除を検出するステップと、 前記ターゲットベースのスライディングロック機構の解除を検出したことに応答して、前記グループ通信チャネルを前記第1の動作モードで維持するステップとをさらに含む、請求項1に記載の方法。
- 3前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項1に記載の方法。
- 4前記第2の動作モードがハンズフリーモードを含む、請求項1に記載の方法。
- 5ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションのハンズフリーモード状態を示すステップをさらに含む、請求項4に記載の方法。
- 6前記グループ通信チャネルを前記ハンズフリーモードで維持するステップが、前記ロック機構が作動している間、前記ユーザインターフェース上でのさらなる入力を必要とすることなく、1つまたは複数のデバイスとの開放された通信チャネルを維持するステップを含む、請求項4に記載の方法。
- 7前記第2の動作モードが優先権ロックモードを含む、請求項1に記載の方法。
- 8ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションの優先権ロックモード状態を示すステップをさらに含む、請求項7に記載の方法。
- 9前記ロック機構の作動を検出したことに応答して、前記グループ通信セッションにおける優先フロア入手に対する要求をサーバに送信するステップをさらに含む、請求項7に記載の方法。
- 10前記第2の動作モードがメディアロックモードを含む、請求項1に記載の方法。
- 11ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションのメディアロックモード状態を示すステップをさらに含む、請求項10に記載の方法。
- 12前記ロック機構の作動を検出したことに応答して、1つまたは複数のデバイスにメディアファイルを送信するための、優先フロア入手に対する要求をサーバに送信するステップをさらに含む、請求項10に記載の方法。
- 13ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションの状態を示すステップをさらに含む、請求項1に記載の方法。
- 14前記グループ通信セッションにおけるフロアの制御権を要求するステップと、 前記ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションにおける前記フロアの状態を示すステップとをさらに含む、請求項13に記載の方法。
- 15前記グループ通信セッション中のグループの1人または複数のメンバーの視覚的表現を前記ディスプレイに表示するステップと、 前記グループの各メンバーの参加状態を判定するステップと、 前記ディスプレイに視覚的フィードバックを表示して、前記グループの各メンバーの前記参加状態を示すステップとをさらに含む、請求項13に記載の方法。
- 16前記グループ通信セッションにおける、前記グループの参加していないメンバーの参加していない理由を表示するステップをさらに含む、請求項15に記載の方法。
- 17ワイヤレス通信デバイス上でグループ通信を行う方法であって、 ユーザ入力に応答してグループ通信セッションを開始するステップと、 ユーザインターフェース上でのユーザによるロック機構の作動を検出するステップと、 前記ロック機構の作動を検出したことに応答して、優先フロア入手に対する要求をサーバに送信するステップと、 前記ロック機構が作動している間、1つまたは複数のデバイスとのグループ通信セッションを優先権入手モードで維持するステップとを含む、方法。
- 18前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項17に記載の方法。
- 19前記ロック機構が、タッチスクリーンユーザインターフェースディスプレイ上のターゲットベースのスライディングロック機構を含む、請求項17に記載の方法。
- 20ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションの優先権入手モード状態を示すステップをさらに含む、請求項17に記載の方法。
- 21複数のユーザデバイスの間のグループ通信セッションにおいてサーバを動作させる方法であって、 第1のユーザデバイスからメディアロックに対する要求を受信するステップと、 メディアロックに対する前記要求に応答して、前記第1のユーザデバイスへのメディアファイルの送信のためのフロアの制御権をロックするステップとを含む、方法。
- 22前記メディアロックがもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するステップと、 前記受信されたメッセージに応答して、所定の優先規則を使用して前記複数のユーザデバイスの間でメディアファイルの送信のためのフロア制御権を調停するステップとをさらに含む、請求項21に記載の方法。
- 23複数のユーザデバイスの間のグループ通信セッションにおいてサーバを動作させる方法であって、 グループ通信セッションにおいて第1のユーザデバイスから優先フロア入手に対する要求を受信するステップと、 優先フロア入手に対する前記要求を受信したことに応答して、優先入手権が前記第1のユーザデバイスに与えられた状態で、前記グループ通信セッションのフロア制御権を調停するステップとを含む、方法。
- 24優先フロア入手がもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するステップと、 前記受信されたメッセージに応答して、優先入手権を前記第1のユーザデバイスに与えることなく、前記グループ通信セッションのフロア制御権を調停するステップとをさらに含む、請求項23に記載の方法。
- 25ワイヤレス通信デバイス上でグループ通信セッションを行う方法であって、 ワイヤレス通信デバイスディスプレイのホーム画面に、クイック連絡グループ通信ショートカットのアイコンを表示するステップと、 前記ディスプレイの前記ホーム画面に、前記クイック連絡グループ通信ショートカットのアイコンと関連するグループ通信ボタンを表示するステップと、 ユーザインターフェース上でのユーザによる前記グループ通信ボタンの選択を検出するステップと、 連絡先のデバイスとのグループ通信セッションを開始するステップとを含む、方法。
- 26前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項25に記載の方法。
- 27前記デバイスがタッチスクリーンユーザインターフェースディスプレイを含む、請求項25に記載の方法。
- 28前記クイック連絡グループ通信ショートカットと関連するロック機構を表示するステップをさらに含む、請求項27に記載の方法。
- 29前記ロック機構が、タッチスクリーンユーザインターフェースディスプレイ上のターゲットベースのスライディングロック機構を含む、請求項28に記載の方法。
- 30タッチスクリーンユーザインターフェースディスプレイと、 メモリと、 前記タッチスクリーンユーザインターフェースディスプレイおよび前記メモリに結合され、動作を実行するためのプロセッサ実行可能命令によって構成されるプロセッサとを含む、ワイヤレス通信デバイスであって、前記動作が、 前記タッチスクリーンユーザインターフェースディスプレイ上でのユーザ入力に応答して、第1の動作モードで1つまたは複数のデバイスとのグループ通信セッションをサポートするグループ通信チャネルを確立するステップと、 前記タッチスクリーンユーザインターフェースディスプレイ上でのユーザによるターゲットベースのスライディングロック機構の作動を検出するステップと、 前記ロック機構が作動している間、前記グループ通信チャネルを第2の動作モードで維持するステップとを含む、ワイヤレス通信デバイス。
- 31前記プロセッサが、 前記ターゲットベースのスライディングロック機構の解除を検出するステップと、 前記ターゲットベースのスライディングロック機構の解除を検出したことに応答して、前記グループ通信チャネルを前記第1の動作モードで維持するステップとをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項30に記載のワイヤレス通信デバイス。
- 32前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項30に記載のワイヤレス通信デバイス。
- 33前記プロセッサが、前記第2の動作モードがハンズフリーモードを含むように動作を実行するためのプロセッサ実行可能命令によって構成される、請求項30に記載のワイヤレス通信デバイス。
- 34前記グループ通信チャネルを前記ハンズフリーモードで維持するステップが、前記ロック機構が作動している間、前記タッチスクリーンユーザインターフェースディスプレイへのさらなる入力を必要とすることなく、1つまたは複数のデバイスとの開放された通信チャネルを維持するステップを含むように動作を実行するためのプロセッサ実行可能命令によって前記プロセッサが構成される、請求項33に記載のワイヤレス通信デバイス。
- 35前記プロセッサが、前記第2の動作モードが優先権ロックモードを含むように動作を実行するためのプロセッサ実行可能命令によって構成される、請求項30に記載のワイヤレス通信デバイス。
- 36前記プロセッサが、 ディスプレイに視覚的フィードバックを表示して、グループ通信の優先権ロックモード状態を示すステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項35に記載のワイヤレス通信デバイス。
- 37前記プロセッサが、 前記ロック機構の作動を検出したことに応答して、前記グループ通信セッションにおける優先フロア入手に対する要求をサーバに送信するステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項35に記載のワイヤレス通信デバイス。
- 38前記プロセッサが、前記第2の動作モードがメディアロックモードを含むように動作を実行するためのプロセッサ実行可能命令によって構成される、請求項30に記載のワイヤレス通信デバイス。
- 39前記プロセッサが、 ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションのメディアロックモード状態を示すステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項38に記載のワイヤレス通信デバイス。
- 40前記プロセッサが、 前記ロック機構の作動を検出したことに応答して、1つまたは複数のデバイスにメディアファイルを送信するための、優先フロア入手に対する要求をサーバに送信するステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項38に記載のワイヤレス通信デバイス。
- 41前記プロセッサが、 ユーザ入力に応答してグループ通信セッションを開始するステップと、 ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションの状態を示すステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項30に記載のワイヤレス通信デバイス。
- 42前記プロセッサが、 前記グループ通信セッションにおけるフロアの制御権を要求するステップと、 前記ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションにおける前記フロアの状態を示すステップとをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項41に記載のワイヤレス通信デバイス。
- 43前記プロセッサが、 前記グループ通信セッションのグループ中の1人または複数のメンバーの視覚的表現を前記ディスプレイに表示するステップと、 グループの各メンバーの参加状態を判定するステップと、 前記ディスプレイに視覚的フィードバックを表示して、前記グループの各メンバーの前記参加状態を示すステップとをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項41に記載のワイヤレス通信デバイス。
- 44前記プロセッサが、 前記グループ通信セッションにおける、前記グループの参加していないメンバーの参加していない理由を表示するステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項43に記載のワイヤレス通信デバイス。
- 45メモリと、 前記メモリに結合され、動作を実行するためのプロセッサ実行可能命令によって構成されたプロセッサとを含む、ワイヤレス通信デバイスであって、前記動作が、 ユーザ入力に応答してグループ通信セッションを開始するステップと、 ユーザインターフェース上でのユーザによるロック機構の作動を検出するステップと、 前記ロック機構の作動を検出したことに応答して、優先フロア入手に対する要求をサーバに送信するステップと、 前記ロック機構が作動している間、1つまたは複数のデバイスとのグループ通信チャネルを優先権入手モードで維持するステップとを含む、ワイヤレス通信デバイス。
- 46前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項45に記載のワイヤレス通信デバイス。
- 47前記プロセッサに結合されたタッチスクリーンユーザインターフェースディスプレイをさらに含み、前記ロック機構が、前記タッチスクリーンユーザインターフェースディスプレイ上のターゲットベースのスライディングロック機構を含む、請求項45に記載のワイヤレス通信デバイス。
- 48前記プロセッサが、 ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションの優先権入手モード状態を示すステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項45に記載のワイヤレス通信デバイス。
- 49複数のユーザデバイスの間のグループ通信セッションにおいて動作するように構成されるサーバであって、 メモリと、 前記メモリに結合され、動作を実行するためのプロセッサ実行可能命令によって構成されたプロセッサとを含み、前記動作が、 第1のユーザデバイスからメディアロックに対する要求を受信するステップと、 メディアロックに対する前記要求に応答して、前記第1のユーザデバイスへのメディアファイルの送信のためのフロアの制御権をロックするステップとを含む、サーバ。
- 50前記プロセッサが、 前記メディアロックがもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するステップと、 前記メディアロックがもはや要求されていないという前記メッセージを受信したことに応答して、所定の優先規則を使用して前記複数のユーザデバイスの間でメディアファイルの送信のためのフロア制御権を調停するステップとをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項49に記載のサーバ。
- 51複数のユーザデバイスの間のグループ通信セッションにおいて動作するように構成されるサーバであって、 メモリと、 前記メモリに結合され、動作を実行するためのプロセッサ実行可能命令によって構成されたプロセッサとを含み、前記動作が、 グループ通信セッションにおいて第1のユーザデバイスから優先フロア入手に対する要求を受信するステップと、 優先フロア入手に対する前記要求に応答して、優先入手権が前記第1のユーザデバイスに与えられた状態で、前記グループ通信セッションのフロア制御権を調停するステップとを含む、サーバ。
- 52前記プロセッサが、 優先フロア入手がもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するステップと、 優先フロア入手がもはや要求されていないという前記メッセージに応答して、優先入手権を前記第1のユーザデバイスに与えることなく、前記グループ通信セッションのフロア制御権を調停するステップとをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項51に記載のサーバ。
- 53ディスプレイと、 メモリと、 前記ディスプレイおよび前記メモリに結合され、動作を実行するためのプロセッサ実行可能命令によって構成されたプロセッサとを含む、ワイヤレス通信デバイスであって、前記動作が、 前記ディスプレイのホーム画面に、クイック連絡グループ通信ショートカットのアイコンを表示するステップと、 前記ディスプレイの前記ホーム画面に、前記クイック連絡グループ通信ショートカットのアイコンと関連するグループ通信ボタンを表示するステップと、 ユーザインターフェース上でのユーザによる前記グループ通信ボタンの選択を検出するステップと、 連絡先のデバイスとのグループ通信セッションを開始するステップとを含む、ワイヤレス通信デバイス。
- 54前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項53に記載のワイヤレス通信デバイス。
- 55前記ディスプレイがタッチスクリーンユーザインターフェースディスプレイを含む、請求項53に記載のワイヤレス通信デバイス。
- 56前記プロセッサが、 前記クイック連絡グループ通信ショートカットと関連するロック機構を表示するステップをさらに含む動作を実行するためのプロセッサ実行可能命令によって構成される、請求項55に記載のワイヤレス通信デバイス。
- 57前記ロック機構が、タッチスクリーンユーザインターフェースディスプレイ上に実装されるターゲットベースのスライディングロック機構を含む、請求項56に記載のワイヤレス通信デバイス。
- 58ユーザインターフェース上でのユーザ入力に応答して、第1の動作モードで1つまたは複数のデバイスとのグループ通信セッションを可能にするためにグループ通信チャネルを確立するための手段と、 ワイヤレス通信デバイスのタッチスクリーンユーザインターフェースディスプレイ上でのユーザによるターゲットベースのスライディングロック機構の作動を検出するための手段と、 前記ロック機構が作動している間、第2の動作モードで前記グループ通信チャネルを維持するための手段とを含む、ワイヤレス通信デバイス。
- 59前記ターゲットベースのスライディングロック機構の解除を検出するための手段と、 前記ターゲットベースのスライディングロック機構の解除を検出したことに応答して、前記グループ通信チャネルを前記第1の動作モードで維持するための手段とをさらに含む、請求項58に記載のワイヤレス通信デバイス。
- 60前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項58に記載のワイヤレス通信デバイス。
- 61前記グループ通信チャネルを第2の動作モードで維持するための手段が、前記グループ通信チャネルをハンズフリーモードで維持するための手段を含む、請求項58に記載のワイヤレス通信デバイス。
- 62前記グループ通信セッションのハンズフリーモード状態を視覚的に示すものを表示するための手段をさらに含む、請求項58に記載のワイヤレス通信デバイス。
- 63前記グループ通信チャネルを前記ハンズフリーモードで維持するための手段が、前記ロック機構が作動している間、前記ユーザインターフェース上でのさらなる入力を必要とすることなく、1つまたは複数のデバイスとの開放された通信チャネルを維持するための手段を含む、請求項61に記載のワイヤレス通信デバイス。
- 64前記グループ通信チャネルを第2の動作モードで維持するための手段が、前記グループ通信チャネルを優先権ロックモードで維持するための手段を含む、請求項58に記載のワイヤレス通信デバイス。
- 65前記グループ通信セッションの優先権ロックモード状態を視覚的に示すものを表示するための手段をさらに含む、請求項64に記載のワイヤレス通信デバイス。
- 66前記ロック機構の作動を検出したことに応答して、前記グループ通信セッションにおける優先フロア入手に対する要求をサーバに送信するための手段をさらに含む、請求項64に記載のワイヤレス通信デバイス。
- 67前記グループ通信チャネルを第2の動作モードで維持するための手段が、前記グループ通信チャネルをメディアロックモードで維持するための手段を含む、請求項58に記載のワイヤレス通信デバイス。
- 68前記グループ通信セッションのメディアロックモード状態を視覚的に示すものを表示するための手段をさらに含む、請求項58に記載のワイヤレス通信デバイス。
- 69前記ロック機構の作動を検出したことに応答して、1つまたは複数のデバイスにメディアファイルを送信するための、優先フロア入手に対する要求をサーバに送信するための手段をさらに含む、請求項67に記載のワイヤレス通信デバイス。
- 70ユーザ入力に応答してグループ通信セッションを開始するための手段と、 ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションの状態を示すための手段をさらに含む、請求項58に記載のワイヤレス通信デバイス。
- 71前記グループ通信セッションにおけるフロアの制御権を要求するための手段と、 前記ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションにおける前記フロアの状態を示すための手段とをさらに含む、請求項70に記載のワイヤレス通信デバイス。
- 72前記グループ通信セッションのグループの1人または複数のメンバーの視覚的表現を前記ディスプレイに表示するための手段と、 前記グループの各メンバーの参加状態を判定するための手段と、 前記ディスプレイに視覚的フィードバックを表示して、前記グループの各メンバーの前記参加状態を示すための手段とをさらに含む、請求項70に記載のワイヤレス通信デバイス。
- 73前記グループ通信セッションにおける、前記グループの参加していないメンバーの参加していない理由を表示するための手段をさらに含む、請求項72に記載のワイヤレス通信デバイス。
- 74ユーザ入力に応答してグループ通信セッションを開始するための手段と、 ユーザインターフェース上でのユーザによるロック機構の作動を検出するための手段と、 前記ロック機構の作動を検出したことに応答して、優先フロア入手に対する要求をサーバに送信するための手段と、 前記ロック機構が作動している間、1つまたは複数のデバイスとのグループ通信チャネルを優先権入手モードで維持するための手段とを含む、ワイヤレス通信デバイス。
- 75前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項74に記載のワイヤレス通信デバイス。
- 76前記グループ通信セッションの優先権入手モード状態を視覚的に示すものを表示するための手段をさらに含む、請求項74に記載のワイヤレス通信デバイス。
- 77前記ロック機構が、タッチスクリーンユーザインターフェースディスプレイ上のターゲットベースのスライディングロック機構を含む、請求項74に記載のワイヤレス通信デバイス。
- 78複数のユーザデバイスの間のグループ通信セッションにおいて動作するように構成されるサーバであって、 第1のユーザデバイスからメディアロックに対する要求を受信するための手段と、 メディアロックに対する前記要求を受信したことに応答して、前記第1のユーザデバイスへのメディアファイルの送信のためのフロアの制御権をロックするための手段とを含む、サーバ。
- 79前記メディアロックがもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するための手段と、 前記メディアロックがもはや要求されていないという前記メッセージを受信したことに応答して、所定の優先規則を使用して前記複数のユーザデバイスの間でメディアファイルの送信のためのフロア制御権を調停するための手段とをさらに含む、請求項78に記載のサーバ。
- 80複数のユーザデバイスの間のグループ通信セッションにおいて動作するように構成されるサーバであって、 グループ通信セッションにおいて第1のユーザデバイスから優先フロア入手に対する要求を受信するための手段と、 優先フロア入手に対する前記要求に応答して、優先入手権が前記第1のユーザデバイスに与えられた状態で、前記グループ通信セッションのフロア制御権を調停するための手段とを含む、サーバ。
- 81優先フロア入手がもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するための手段と、 優先フロア入手がもはや要求されていないという前記メッセージに応答して、優先入手権を前記第1のユーザデバイスに与えることなく、前記グループ通信セッションのフロア制御権を調停するための手段とをさらに含む、請求項80に記載のサーバ。
- 82ワイヤレス通信デバイスディスプレイのホーム画面に、クイック連絡グループ通信ショートカットのアイコンを表示するための手段と、 前記ディスプレイの前記ホーム画面に、前記クイック連絡グループ通信ショートカットのアイコンと関連するグループ通信ボタンを表示するための手段と、 ユーザインターフェース上でのユーザによる前記グループ通信ボタンの選択を検出するための手段と、 連絡先のデバイスとのグループ通信セッションを開始するための手段とを含む、ワイヤレス通信デバイス。
- 83前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含む、請求項82に記載のワイヤレス通信デバイス。
- 84前記デバイスがタッチスクリーンユーザインターフェースディスプレイを含む、請求項82に記載のワイヤレス通信デバイス。
- 85前記クイック連絡グループ通信ショートカットと関連するロック機構を表示するための手段をさらに含む、請求項82に記載のワイヤレス通信デバイス。
- 86前記ロック機構が、タッチスクリーンユーザインターフェースディスプレイ上のターゲットベースのスライディングロック機構を含む、請求項85に記載のワイヤレス通信デバイス。
- 87ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成されたプロセッサ実行可能命令を記憶したコンピュータ可読記憶媒体であって、前記動作が、 ユーザインターフェース上でのユーザ入力に応答して、第1の動作モードで1つまたは複数のデバイスとのグループ通信セッションを可能にするためにグループ通信チャネルを確立するステップと、 前記ワイヤレス通信デバイスのタッチスクリーンユーザインターフェースディスプレイ上でのユーザによるターゲットベースのスライディングロック機構の作動を検出するステップと、 前記ロック機構が作動している間、前記グループ通信チャネルを第2の動作モードで維持するステップとを含む、コンピュータ可読記憶媒体。
- 88前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記ターゲットベースのスライディングロック機構の解除を検出するステップと、 前記ターゲットベースのスライディングロック機構の解除を検出したことに応答して、前記グループ通信チャネルを前記第1の動作モードで維持するステップとをさらに含む動作を実行させるように構成される、請求項87に記載のコンピュータ可読記憶媒体。
- 89前記記憶されたプロセッサ実行可能命令が、前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項87に記載のコンピュータ可読記憶媒体。
- 90前記記憶されたプロセッサ実行可能命令が、前記第2の動作モードがハンズフリーモードを含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項87に記載のコンピュータ可読記憶媒体。
- 91前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、前記グループ通信セッションのハンズフリーモード状態を視覚的に示すものを表示するステップをさらに含む動作を実行させるように構成される、請求項90に記載のコンピュータ可読記憶媒体。
- 92前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記グループ通信チャネルを前記ハンズフリーモードで維持するステップが、前記ロック機構が作動している間、前記ユーザインターフェース上でのさらなる入力を必要とすることなく、1つまたは複数のデバイスとの開放された通信チャネルを維持するステップを含むように、動作を実行させるように構成される、請求項90に記載のコンピュータ可読記憶媒体。
- 93前記記憶されたプロセッサ実行可能命令が、前記第2の動作モードが優先権ロックモードを含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項87に記載のコンピュータ可読記憶媒体。
- 94前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、前記グループ通信セッションの優先権ロックモード状態を視覚的に示すものを表示するステップをさらに含む動作を実行させるように構成される、請求項93に記載のコンピュータ可読記憶媒体。
- 95前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記ロック機構の作動を検出したことに応答して、前記グループ通信セッションにおける優先フロア入手に対する要求をサーバに送信するステップをさらに含む動作を実行させるように構成される、請求項93に記載のコンピュータ可読記憶媒体。
- 96前記記憶されたプロセッサ実行可能命令が、前記第2の動作モードがメディアロックモードを含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項87に記載のコンピュータ可読記憶媒体。
- 97前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、前記グループ通信セッションのメディアロックモード状態を視覚的に示すものを表示するステップをさらに含む動作を実行させるように構成される、請求項96に記載のコンピュータ可読記憶媒体。
- 98前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記ロック機構の作動を検出したことに応答して、1つまたは複数のデバイスにメディアファイルを送信するための、優先フロア入手に対する要求をサーバに送信するステップをさらに含む動作を実行させるように構成される、請求項96に記載のコンピュータ可読記憶媒体。
- 99前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 ユーザ入力に応答してグループ通信セッションを開始するステップと、 ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションの状態を示すステップとをさらに含む動作を実行させるように構成される、請求項87に記載のコンピュータ可読記憶媒体。
- 100前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記グループ通信セッションにおけるフロアの制御権を要求するステップと、 前記ディスプレイに視覚的フィードバックを表示して、前記グループ通信セッションにおける前記フロアの状態を示すステップとをさらに含む動作を実行させるように構成される、請求項99に記載のコンピュータ可読記憶媒体。
- 101前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記グループ通信セッションのグループ中の1人または複数のメンバーの視覚的表現を前記ディスプレイに表示するステップと、 グループの各メンバーの参加状態を判定するステップと、 前記ディスプレイに視覚的フィードバックを表示して、前記グループの各メンバーの前記参加状態を示すステップとをさらに含む動作を実行させるように構成される、請求項99に記載のコンピュータ可読記憶媒体。
- 102前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記グループ通信セッションにおける、前記グループの参加していないメンバーの参加していない理由を表示するステップをさらに含む動作を実行させるように構成される、請求項101に記載のコンピュータ可読記憶媒体。
- 103ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成されたプロセッサ実行可能命令を記憶したコンピュータ可読記憶媒体であって、前記動作が、 ユーザ入力に応答してグループ通信セッションを開始するステップと、 ユーザインターフェース上でのユーザによるロック機構の作動を検出するステップと、 前記ロック機構の作動を検出したことに応答して、優先フロア入手に対する要求をサーバに送信するステップと、 前記ロック機構が作動している間、1つまたは複数のデバイスとのグループ通信チャネルを優先権入手モードで維持するステップとを含む、コンピュータ可読記憶媒体。
- 104前記記憶されたプロセッサ実行可能命令が、前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項103に記載のコンピュータ可読記憶媒体。
- 105前記記憶されたプロセッサ実行可能命令が、前記ロック機構がタッチスクリーンユーザインターフェースディスプレイ上のターゲットベースのスライディングロック機構を含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項103に記載のコンピュータ可読記憶媒体。
- 106前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、前記グループ通信セッションの優先権入手モード状態を視覚的に示すものを表示するステップをさらに含む動作を実行させるように構成される、請求項103に記載のコンピュータ可読記憶媒体。
- 107サーバプロセッサに動作を実行させるように構成されたプロセッサ実行可能命令を記憶したコンピュータ可読記憶媒体であって、前記動作が、 第1のユーザデバイスからメディアロックに対する要求を受信するステップと、 メディアロックに対する前記要求に応答して、前記第1のユーザデバイスへのメディアファイルの送信のためのフロアの制御権をロックするステップとを含む、コンピュータ可読記憶媒体。
- 108前記記憶されたプロセッサ実行可能命令が、前記サーバプロセッサに、 前記メディアロックがもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するステップと、 前記メディアロックがもはや要求されていないという前記メッセージに応答して、所定の優先規則を使用してグループ通信セッション中の複数のユーザデバイスの間でメディアファイルの送信のためのフロア制御権を調停するステップとをさらに含む動作を実行させるように構成される、請求項107に記載のコンピュータ可読記憶媒体。
- 109サーバプロセッサに動作を実行させるように構成されたプロセッサ実行可能命令を記憶したコンピュータ可読記憶媒体であって、前記動作が、 グループ通信セッションにおいて第1のユーザデバイスから優先フロア入手に対する要求を受信するステップと、 優先フロア入手に対する前記要求に応答して、優先入手権が前記第1のユーザデバイスに与えられた状態で、前記グループ通信セッションのフロア制御権を調停するステップとを含む、コンピュータ可読記憶媒体。
- 110前記記憶されたプロセッサ実行可能命令が、前記サーバプロセッサに、 優先フロア入手がもはや要求されていないというメッセージを前記第1のユーザデバイスから受信するステップと、 優先フロア入手がもはや要求されていないという前記メッセージに応答して、優先入手権を前記第1のユーザデバイスに与えることなく、前記グループ通信セッションのフロア制御権を調停するステップとをさらに含む動作を実行させるように構成される、請求項109に記載のコンピュータ可読記憶媒体。
- 111ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成されたプロセッサ実行可能命令を記憶したコンピュータ可読記憶媒体であって、前記動作が、 ワイヤレス通信デバイスディスプレイのホーム画面に、クイック連絡グループ通信ショートカットのアイコンを表示するステップと、 前記ディスプレイの前記ホーム画面に、前記クイック連絡グループ通信ショートカットのアイコンと関連するグループ通信ボタンを表示するステップと、 ユーザインターフェース上でのユーザによる前記グループ通信ボタンの選択を検出するステップと、 連絡先のデバイスとのグループ通信セッションを開始するステップとを含む、コンピュータ可読記憶媒体。
- 112前記記憶されたプロセッサ実行可能命令が、前記グループ通信セッションが「プッシュツートーク」(PTT)通信を含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項111に記載のコンピュータ可読記憶媒体。
- 113前記記憶されたプロセッサ実行可能命令が、前記デバイスがタッチスクリーンユーザインターフェースディスプレイを含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項111に記載のコンピュータ可読記憶媒体。
- 114前記記憶されたプロセッサ実行可能命令が、前記ワイヤレス通信デバイスのプロセッサに、 前記クイック連絡グループ通信ショートカットと関連するロック機構を表示するステップをさらに含む動作を実行させるように構成される、請求項113に記載のコンピュータ可読記憶媒体。
- 115前記記憶されたプロセッサ実行可能命令が、前記ロック機構がタッチスクリーンユーザインターフェースディスプレイ上のターゲットベースのスライディングロック機構を含むように、前記ワイヤレス通信デバイスのプロセッサに動作を実行させるように構成される、請求項114に記載のコンピュータ可読記憶媒体。
Independent claims115
97 paragraphs, as filed
Related application This application is a US provisional patent application entitled "User Experience Enhancements for Group Communication" filed on November 2, 2011, the entire contents of which are incorporated herein by reference for all purposes. Claim the benefit of the priority of / 554,876.
The application also relates to US Patent Application No. 13 / 611,371 entitled "User Experience Enhancements for Limiting Calls in a Group Communication" filed at the same time as this specification.
The present invention generally relates to wireless remote communication systems. More specifically, the present invention relates to methods and devices that enable group communication, such as "push-to-talk" (PTT) communication, without the need for dedicated push-to-talk (PTT) hardware.
In wireless telecommunications devices such as mobile phones, PDAs, mini laptops, and advanced pagers, the device typically bridges phone calls through existing mobile phone networks and passes data packets over the network over long distances. Communicate over. These wireless communication devices often have data processing and computing capabilities and are therefore capable of transmitting and receiving voice and other types of data over the telephone network.
There is a wireless telecommunications service that enables high-speed one-to-one or one-to-many communications, commonly referred to as the "push-to-talk" (PTT) feature. The specific PTT group of the recipient device for the wireless communication device with which it communicates is usually set by the carrier. A PTT communication connection is typically initiated and released by pressing a single hardware button on a wireless communication device that activates a half-duplex link between the speaker and each member device of the group. The device can then receive the incoming PTT transmission. Existing PTT systems have traditional call setup times that are faster, for example, for cellular voice channels that can take longer than 5 seconds to establish, the setup time is ideally in the range of 1 second. There are advantages over cellular systems. In some configurations, PTT speakers have a "floor" that other group members cannot speak when the speaker is speaking. When the speaker releases the PTT button, any other individual member of the group can operate the PTT button and that member will have a floor. Generally, PTT systems use standard Voice Over Internet Protocol (VoIP) technology. Voice information is transmitted in digital format from an IP-based data network. In the PTT situation, instead of using standard cellular infrastructure, calls are formed by combining separate point-to-point connections between each IP endpoint in the network. By starting the PTT system, a call to the target device is generated. The voice of the caller can be sent to the target handset through the carrier's network.
<p num="0006"> The downside of existing PTT services is that they usually require devices with dedicated PTT hardware components such as hardware PTT buttons, which means that most mobiles these services are used today. It means that it is not generally available on the device.</p>
<p num="0007"> Various embodiments include the step of establishing a group communication channel with one or more devices in the first mode of operation in response to user input in the user interface and on the touch screen user interface display of the wireless communication device. Group communication on a wireless communication device, including the step of detecting the activation of the target-based sliding locking mechanism by the user and the step of maintaining the group communication channel in the second mode of operation while the locking mechanism is active. Includes methods for managing sessions. In various embodiments, the second mode of operation can be hands-free mode, priority lock mode, media lock mode, lockout mode, and / or blockage mode.</p><p num="0008"> The method of the embodiment may further include initiating a group communication session in response to user input and displaying visual feedback on a display to indicate the state of group communication. An embodiment may include a step of requesting control of the floor in a group communication session and a step of displaying visual feedback on a display to indicate the state of the floor in the group communication session. The embodiment further displays a visual representation of one or more members of the group on a display in a group communication session, a step of determining the participation status of each member of the group, and visual feedback on the display. It may include a step indicating the participation status of each member of the group. The embodiment may also include in group communication a step of displaying the reasons why the non-participating members of the group are not participating.</p><p num="0009"> Further embodiments include a step of initiating a group communication session in response to user input, a step of detecting the activation of the locking mechanism by the user on the user interface, and a step of detecting the activation of the locking mechanism in response to the detected activation of the locking mechanism. Wireless communication, including sending a request for priority floor acquisition to the server and maintaining a group communication channel with one or more devices in priority acquisition mode while the locking mechanism is active. Includes methods for managing group communication sessions on the device.</p><p num="0010"> A further embodiment is a step of establishing a group media communication channel with one or more devices in response to user input on the user interface and a step of detecting the activation of the locking mechanism by the user on the user interface. And include methods for managing group communication sessions on wireless communication devices, including the step of maintaining the group media communication channel in media lock mode while the locking mechanism is active.</p><p num="0011"> Further embodiments include displaying a quick contact group communication shortcut icon on the home screen of the display of the wireless communication device, and displaying a group communication button associated with the quick contact group communication shortcut icon on the home screen of the display. Includes methods for managing group communication sessions on wireless communication devices, including detecting the user's selection of a group communication button on the user interface and initiating group communication with the contact's device. .. Further embodiments may include displaying a locking mechanism associated with a quick contact group shortcut.</p><p num="0012"> Further embodiments include a step of receiving a request for preferred floor acquisition from the first user device and a step of arbitrating floor control of a group communication session with preferred acquisition rights granted to the first user device. , Includes methods for running a server in a group communication session between multiple user devices.</p><p num="0013"> A further embodiment gives control of the floor of a group communication session for receiving a request for a media lock from a first user device and in response to the request to send a media file to the first user device. Includes methods for running a server in a group communication session between multiple user devices, including a locking step.</p><p num="0014"> Various embodiments include wireless communication devices and servers, including processors configured to perform the operations of the embodiments disclosed herein. Various embodiments also include wireless communication devices and servers, including means for performing the functions of the methods of the embodiments disclosed herein. Various embodiments also contain processor-readable and server-readable non-temporary storage media that store processor-executable instructions that are configured to cause the processor to perform the operations of the methods of the embodiments disclosed herein. including.</p><p num="0015"> The accompanying drawings, which are incorporated herein and form part of the present specification, illustrate exemplary embodiments of the invention and describe the features of the invention, along with a general description above and a detailed description below. Play a role.</p>
<figref num="1">It is a figure which shows the wireless communication device suitable for use with various embodiments.</figref><figref num="2">It is a figure which shows the software layer of a group application client which may include a "push-to-talk" (PTT) function.</figref><figref num="3">It is a figure which shows an exemplary system for group communication between a plurality of wireless communication devices.</figref><figref num="4">FIG. 5 illustrates an exemplary wireless network suitable for use with various embodiments.</figref><figref num="5">FIG. 5 is a process flow diagram of a method of an embodiment of group communication in which visual feedback on the state of a group communication session is displayed on the display screen of a wireless communication device.</figref><figref num="6A">It is a screenshot of the touch screen user interface of a wireless communication device of an embodiment.</figref><figref num="6B">It is a screenshot of the touch screen user interface of a wireless communication device of an embodiment.</figref><figref num="6C">It is a screenshot of the touch screen user interface of a wireless communication device of an embodiment.</figref><figref num="7">FIG. 3 is a process flow diagram of a method of an embodiment of group communication, including the step of displaying visual feedback to indicate control of the floor in a PTT communication session.</figref><figref num="8A">FIG. 6 is a screenshot of a touch screen display showing a PTT communication session of an embodiment.</figref><figref num="8B">FIG. 6 is a screenshot of a touch screen display showing a PTT communication session of an embodiment.</figref><figref num="8C">FIG. 6 is a screenshot of a touch screen display showing a PTT communication session of an embodiment.</figref><figref num="9A">FIG. 6 is a process flow diagram of a method of an embodiment of group communication, including the step of displaying visual feedback to indicate the state of the floor in a group communication session.</figref><figref num="9B">FIG. 5 is a process flow diagram of a method of an embodiment with group communication using a server capable of transmitting the floor control status.</figref><figref num="10A">FIG. 3 is a process flow diagram of a method of an embodiment of group communication, comprising displaying visual feedback of the participation status of one or more devices in a communication group.</figref><figref num="10B">Process flow of a method of an embodiment of group communication, including displaying visual feedback on the participation status of one or more devices in a communication group and why at least one non-participating device is not participating. It is a figure.</figref><figref num="10C">FIG. 3 is a process flow diagram of a method of an embodiment of group communication using a server that can indicate to devices in a group the participation status and / or the reason for not participating in at least one device in the group.</figref><figref num="11A">FIG. 6 is a screenshot of a touch screen display of an embodiment having a sliding lock mechanism.</figref><figref num="11B">FIG. 6 is a screenshot of a touch screen display of an embodiment having a sliding lock mechanism.</figref><figref num="11C">FIG. 6 is a screenshot of a touch screen display of an embodiment having a sliding lock mechanism.</figref><figref num="11D">FIG. 6 is a screenshot of a touch screen display of an embodiment having a sliding lock mechanism.</figref><figref num="12">FIG. 3 is a process flow diagram of a method of an embodiment with group communication using a "hands-free" mode.</figref><figref num="13A">It is a process flow diagram of the method of an embodiment with group communication using the "priority lock" mode.</figref><figref num="13B">FIG. 5 is a process flow diagram of a method of an embodiment in which a server operates in a group communication session in which a user device requests priority floor acquisition.</figref><figref num="14A">It is a process flow diagram of the method of an embodiment with group communication using a "media lock" mode.</figref><figref num="14B">FIG. 5 is a process flow diagram of a method of an embodiment in which a server operates in a group communication session in which a user device requests a media lock.</figref><figref num="15A">It is a process flow diagram of the method of an embodiment with group communication using the "lock out" mode.</figref><figref num="15B">FIG. 5 is a process flow diagram of a method of an embodiment in which a server operates in a group communication session in which a user device activates a lockout mechanism.</figref><figref num="16A">FIG. 3 is a process flow diagram of a method of an embodiment with group communication using the "block" mode.</figref><figref num="16B">FIG. 5 is a process flow diagram of a method of an embodiment in which a server operates in a group communication session in which a user device activates a blocking mechanism.</figref><figref num="17A">A screenshot of a touch screen display of an embodiment having a "quick contact" group communication shortcut on the home screen.</figref><figref num="17B">A screenshot of a touch screen display of an embodiment having a "quick contact" group communication shortcut on the home screen.</figref><figref num="17C">A screenshot of a touch screen display of an embodiment having a "quick contact" group communication shortcut on the home screen.</figref><figref num="18A">It is a process flow diagram of the method of an embodiment with group communication using a "quick contact" group communication shortcut.</figref><figref num="18B">FIG. 5 is a process flow diagram illustrating a method of an embodiment of group communication using a "quick contact" shortcut and a sliding lock mechanism.</figref><figref num="19">FIG. 5 is a system block diagram of a wireless communication device for use with various embodiments.</figref><figref num="20">FIG. 6 is a system block diagram of a server suitable for use with various embodiments.</figref>
Various embodiments will be described in detail with reference to the accompanying drawings. Whenever possible, the same reference number is used to refer to the same or similar parts throughout the drawing. References made to specific examples and embodiments are for illustration purposes and are not intended to limit the scope of the invention or claims.
The term "exemplary" is used herein to mean "to act as an example, an example, or a concrete example." Any implementation described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other implementations.
The terms "mobile device," "mobile computing device," and "wireless communication device" are used for mobile phones, smartphones, personal or mobile multimedia players, mobile information terminals (PDAs), laptop computers, tablet computers, smart books. , Palmtop computers, wireless email receivers, multimedia internet-enabled mobile phones, wireless game controllers, and software to enable group communications such as push-to-talk (PTT) capabilities, including programmable processors and memory. As used interchangeably herein, to refer to any one or all of similar personal electronic devices, which may include and / or hardware.
In general, various embodiments provide improved group communication, such as "push-to-talk" (PTT) capabilities, in wireless communication devices that use software and native device hardware, such as touch screen displays. .. Various embodiments may be implemented in a wide range of devices, including most internet-enabled mobile phones and other wireless communication devices, and require dedicated hardware such as PTT buttons to provide group communication capabilities. Do not.
Traditionally, push-to-talk services have required dedicated hardware, such as PTT buttons, for users to use the service. The various embodiments combine many of the benefits of traditional hardware-based PTT services with some improved features made possible through the use of group communication services implemented primarily through software, a user experience. I will provide a.
Various embodiments are intended for novel group communication interfaces that can provide improved functionality compared to PTT services implemented by traditional hardware. Since this embodiment is implemented primarily in software, the user no longer has to "press" a physical button to speak. In various embodiments, the user interface allows the user to "lock" control of the floor in hands-free mode, which makes it easier for the user to multitask and the speakerphone mode of the device. And / or the earpiece mode can be used more naturally. The ability to lock floor control for media content, as well as at least temporary criteria for floor control and mediation, which can be useful if the user desires preferential access to the floor for a limited period of time. Additional features may be added, such as the ability to change to. An additional feature is the ability to keep out another device in a communication group from receiving communications originating from the user's device, as well as allowing the user's device to receive group communications from another user. May include the ability to thwart. Some or all of this added functionality may be provided via target-based sliding locks that can be implemented in touch screen user interface displays.
Various embodiments additionally allow the user to create a "quick contact" shortcut on the home screen or as a device widget. When you select this shortcut, a qualified PTT "button" will appear on the screen, which will be software-implemented with the "one-click" PTT experience, which is an advantage of PTT implemented in traditional hardware. It may also include "hands-free" locks, as users have substantially on a wider range of devices that may provide group communication services. The quick contact shortcut avoids the problem that the user has to find, launch, and interact with the group communication application program to talk to that contact.
Various embodiments provide visual feedback to the user that can implement more visual experiences than those previously utilized and can reinforce or replace existing audio instructions for floor control and mediation. Instructions are available. Directed by visual feedback may be provided to the display screen of the wireless device via graphical elements and colors. In various embodiments, the feedback instructions can indicate the state of the group communication session, eg, control of the floor for group communication. In various embodiments, the display screen visually informs the user when the floor is open, when the floor is requested by the user's device, when the floor is controlled by the user's device or a different device. Features can be displayed. In some embodiments, the display screen can also display a visual representation of the members of the group during group communication and can also display the participation status of each member of the group. For example, the device can display members of a group that are currently participating in a group communication session, as well as members of a group that are not participating in a group communication session. In various embodiments, the device can additionally display the reason why a non-participating member is not participating in the communication. These improved features may be implemented in software running on the user's wireless device, or may be partially implemented in the server.
Referring here to FIG. 1, FIG. 1 is to provide a group communication (eg, "push-to-talk" (PTT)) feature that releases direct communication to a target device, eg, an endpoint associated with an IP address. Shown is an exemplary wireless telecommunications device that can be a wireless communication device 100, including software and / or hardware. In various embodiments, the wireless communication device 100 uses only software and existing device hardware (eg, a traditional user interface / display such as a keypad or touch screen interface) to provide group communication capabilities. .. The device 100 of the embodiment of FIG. 1 is shown as having a touch screen interface / display 104. In various embodiments, dedicated PTT hardware, such as a PTT button or a dedicated PTT circuit, is not required to provide PTT functionality.
In various embodiments, the wireless communication device 100 may include a computer platform 106 capable of handling voice and data packets, executing software applications, and transmitting information over wireless networks. The computer platform 106 includes a processor 108, such as an application specific integrated circuit (ASIC) or RISC processor, among other components, such as those that implement the ARM architecture. The processor 108 is usually installed at the time of manufacture of the wireless communication device 100 and is usually not upgradeable. Processor 108 or another processor performs an application programming interface (API) layer 110, which includes a resident application environment and may include an operating system loaded on processor 108. The resident application environment interfaces with any resident program in the memory 112, for example, the computer-readable storage medium of the wireless communication device 100.
As shown herein, the wireless communication device 100 may be a wireless communication telephone with a graphics display 104, but may have a personal digital assistant (PDA), a pager with the graphics display 104, or a wireless communication portal. It may be any wireless device with a computer platform 106 known in the art, such as a separate computer platform 106, which may have a wired connection to a network or the Internet if not. Further, the memory 112 may consist of read-only memory or random access memory (RAM and ROM), EPROM, EEPROM, flash card, or any memory common to computer platforms. Computer platform 106 may also include a local database 114 for storing inactive software applications in memory 112. The local database 114 generally consists of one or more flash memory cells, but is known in the art such as magnetic media, EPROM, EEPROM, optical media, tape, or soft disk or hard disk. It may be any secondary or tertiary storage device. The graphics display 104 can provide information about data packages as well as information about ongoing group calls in order to generate previews as described more fully herein.
The computer platform 106 may also include a direct communication interface 116 configured to open a direct communication channel. The direct communication interface 116 may also be part of a standard communication interface for the wireless communication device 100 that normally carries voice and data transmitted to and from the wireless communication device 100. The direct communication interface 116 usually consists of hardware known in the art.
FIG. 2 is a diagram of an embodiment with a software layer of a group application client that may include, but is not limited to, PTT functionality and data packaging functionality. Although the embodiments presented herein are implemented in a PTT session, the system is used in the setup of any group communication session for transmitting voice and / or data between group members at substantially the same time. Can be done. In one embodiment, the computer platform 106 in a wireless communication device environment is a baseband chipset such as Wireless communication Station Modem (MSM) 218 and Advanced Wireless communication Subscriber Software (AMSS) 220 developed by QUALCOMM®. And may include a set of software "layers" developed on top of system software. In this example, the lower MSM chipsets are CDMA2000 1X and CDMA2000 A software protocol stack for the entire suite of CDMA communication technologies, including 1xEV-DO, can be implemented. In this example, AMSS 220 may be configured to support wireless communication operating system layer 222, which is BREW®, also developed by QUALCOMM® in certain embodiments. The wireless communication operating system layer 222 may provide a separation layer that eliminates direct contact with the AMSS 220 and any OEM software on the computer platform, while at the same time providing an application programming interface for chip or device specific operations. it can. The wireless communication operating system layer 222 may enable application development using the features of the wireless communication device without having to rewrite the application each time a new release of device-specific software is announced.
In this example, the wireless communication operating system 222 may include a PTT client 226 configured to provide access to PTT services through the external interface shown here in the PTT recognition UI 224. The PTT client 226 may include all the features needed to enable applications for the wireless communication operating system 222, such as the media client 228. In one embodiment, the PTT client 226 maintains access to the PTT service, responds to communication requests, processes all PTT-aware wireless communication operating system application requests for the PTT service, and all outgoing PTTs. It can process requests, collect and package vocabulary packets for sending PTT talk spurts, and parse packets of vocoder data for terminated PTT talk spurts.
In various embodiments, the computer platform 106 in a wireless communication device environment may include a media client 228, the media client 228 for access to media types other than traditional half-duplex voice communication (VoIP-PTT media). It can be a wireless communication operating system-based application that extends PTT services for. Media Client 228 provides access to media services through external interfaces such as the Media Recognition API, which is an application that can be developed entirely as a wireless communication operating system based application or used in combination with the AMSS 220 interface. Can be done. Media client 228 can serve requests from users and inform users of the results of media requests for any group. Media client 228 may additionally be configured to handle incoming call notifications, indicating that there is a data package to download from media server 316 in FIG. 3, which is described in more detail below. For example, the media client 228 may be configured to download the data package immediately in one embodiment, or in another embodiment the media client 228 may be configured to download the data package at a predetermined time, eg, every day at 10:00 pm. May be configured to download, or the media client 228 may be configured to prompt the user via PTT UI 224 to decide whether and / or when to download the file. .. Other applications 230, which may be push-to-talk or other applications capable of receiving and transmitting data over a group communication channel, may also reside on the platform.
In some embodiments, software for enabling PTT functionality in the wireless communication device 100 may be pre-installed on the device during device manufacturing. In other embodiments, at least some of the software that provides PTT functionality may be downloaded to device 100 by the end user. In some embodiments, the PTT software can be a downloadable application (eg, a mobile application).
Figure 3 shows another among one or more wireless communication devices in PTT group 302, such as wireless communication device 100, smartphone 301, tablet computer 303, smart pager 304, and personal digital assistant (PDA) 306. An exemplary embodiment of a system 300 for sharing a data package with a wireless communication device of. In system 300, each wireless telecommunications device 100, 301, 303, 304, and 306 selectively communicates directly with a target set of one or more other wireless telecommunications devices across the wireless telecommunications network 308. Can be possible. For example, the target set of wireless communication device 100 may be all devices in communication group 302 or a subset thereof, such as smartphone 301, tablet computer 303, pager 304, and PDA306.
In certain embodiments, the wireless telecommunications device 100 can transmit flags to at least the communication server 310 present on the server-side LAN 312 on the wireless network 308. The flags in this example can be used by the server to determine that a wireless device is present, or accessible, on wireless network 308. The communication server 310 can share this information with the set of target wireless telecommunications devices specified by the first wireless telecommunications device, or resides on server-side LAN 312, or across wireless network 308. You can also share this information with other accessible computer devices. The communication server 310 may have an attached or accessible database 314 for storing group identification data for wireless devices. In various embodiments, the media server 316 may reside on the server-side LAN 312, which may additionally include a circuit for the file management server. It should be understood that the number of computer components present on the server-side LAN 312, or over the wireless network 308, or the Internet in general, is not limited. In addition, some or all of the functionality of some server-side components described herein, such as communication server 310, database 314, and media server 316, may be combined into a single device.
In various embodiments, the communication server 310, which may also be referred to as a group communication server, can establish a point-to-point IP PTT channel between the devices in group 302. PTT channels are half-duplex (true or virtual) between the wireless communication devices 100, 304, and / or 306 communicating with one or more other wireless communication devices in the target set. Can be established through channels. Also, in various embodiments, the communication server 310 performs the requested direct communication if at least one of the wireless communication devices in the target set informs the communication server 310 that it is on the wireless network 308. You can try to bridge to the target set.
The communication server 310 also does not notify the group communication server 310 of its presence on the wireless network 308, and if there is no (or only one) wireless telecommunications device in the target set, direct communication is sent to the target set 302. Wireless communication devices 100, 304, and 306 can be informed that they cannot be bridged. Further, although the communication server 310 is shown herein as having an ancillary database 314 of group identification data, the group communication server 310 device may have group identification data therein, as described herein. Can perform all memory functions.
In various embodiments, the communication server 310 can perform the function of arbitrating the competing demands of the various wireless communication devices 100, 304, 306 for the use of the PTT communication channel through the wireless network 308. For example, in response to a request from the wireless communication device 100 to communicate with one or more other target devices in the PTT group 302, including all other devices in the group 302, the communication server 310 , A PTT channel can be established between the requesting device 100 and all or part of the requested target devices in group 302. Therefore, the communication server 310 can grant the control right of the "floor" to the requesting wireless communication device 100. If there are competing requests among the devices in group 302 for control of the "floor", the communication server 310 can arbitrate the competing requests based on a predetermined priority criterion. Priority criteria may be established by group administrators at the time of formation of PTT group 302 and stored in communication server 310 and / or database 314, for example. In various embodiments, the preference can be the default preference stored in server 301 and / or database 314. In some embodiments, the priority criteria may be ad hoc established by one or more of the wireless communication devices 100, 304, 306 in the PTT group 302.
In general, system 300 may include at least one wireless communication device, such as wireless communication device 100, which may be a member of PTT communication group 302 for wireless communication devices. The wireless communication devices of this example may be configured to communicate with each other or as a group across the wireless communication network 308. In addition, in various embodiments, at least one of the wireless communication devices may be configured to selectively transmit the data package to other members of the communication group 302. At least one communication server 310 may be configured to store information about the communication group 302 on the wireless communication network 308, which information is for a particular member of the wireless communication device of one or more communication groups. Includes identification information. The communication server 310 may also be configured to selectively receive data packages from transmitting wireless communication devices, such as the wireless communication device 100 of communication group 302.
In various embodiments, media server 316 receives a data package from a wireless communication device (such as wireless communication device 100), and members of communication group 302 access the stored data package on wireless communication network 308. It can be configured to allow that to be selectively possible. In certain embodiments, the data package may include, but is not limited to, pictures such as JPEG, TIF, audio files such as MP3, MP4, WAV, documents, and / or presentations. Data packages can additionally include streaming media such as multimedia applications (PowerPoint, MOV files, etc.). The data package may also include half-duplex video conferencing between members of the communications group, where the speaker's picture may be broadcast to other group members, either substantially in real time or with a delay .
The size of the data package file can be very large, and due to the possible delay in transmitting the media, or because the receiving wireless communication device is unable to handle the transmitted media, the system 300 is in communication group 302. The media server 316 can be used to store the data package so that the target member can selectively access the stored media without interfering with other PTT communications. Alternatively, in one embodiment, if the data package is stored on media server 316, media server 316 may be configured to send hypertext links to outgoing or target wireless communication devices in communication group 302. The hypertext link in this example may provide a link to media for a stored group on media server 316. Upon receiving the data package by at least one of the member wireless devices in communication group 302, the communication server 310 tells the wireless communication devices 100, 304, and that at least one member wireless communication device in communication group 302 has received the data package. The acknowledgment shown in 306 can be sent.
Since the wireless communication devices 100, 304, 306 can send the communication group identification data to the communication server 310 at the time of transmitting the data package, for example, the target list, the media server 316 is based on various criteria. It may be configured to send a data package to a member wireless communication device identified in the communication group identification data or to store the data package for that member wireless communication device. Alternatively, the wireless communication devices 100, 304, and 306 can request member data of communication group 302 from the communication server 310 before the wireless communication device sends the data package, and the server 310 may be one or more. Address or communication group address can be sent to wireless communication devices 100, 304, and 306. In certain embodiments, the communication server 310 can filter available potential communication groups based on the ability of member devices to receive data packages.
As further described herein, wireless communication devices 100, 304, and 306 may be involved in group communication with member wireless communication devices of communication group 302, during group communication in the same communication session. The data package can be sent to any of all members and a subset of members. Alternatively, the data package may be transmitted independently of the group communication session.
FIG. 4 shows an exemplary wireless network in a common cellular telecommunications configuration. The wireless network in this example includes a set of communication servers 310 that control communication between configured group member wireless communication devices (devices 100-A to D) in the PTT system. This wireless network is merely an example, and any remote module that communicates wirelessly between each other and / or between components of the wireless network, including, but not limited to, wireless network carriers and / or servers. May include a system. A series of communication servers 310 may be connected to the group communication server LAN312. Wireless devices 100-A to D can request voice (eg, VoIP) and / or packet data sessions from the group communication server 310.
Continuing with FIG. 4, the communication server 310 in this example can be connected to a wireless service provider's PDSN, such as Packet Data Service Node (PDSN) 414, which is shown here to be on carrier network 416. .. When a wireless communication device accesses a wireless data network to obtain service, the PDSN414 interfaces with the authentication, authorization and accounting server "AAA" 428 to authenticate wireless communication devices 100, 304, and / or 306. Can be done. AAA428 may be combined with a database that can operate to store information such as user accounts and privileges. Each PDSN414 can interface with base station controller 418 of base station 320 through packet control function (PCF) 422. PCF422 may be located at base station 420. The wireless network 308 can control the messages sent (generally in the form of data packets) to the messaging service controller (MSC) 424. The carrier network 308 in this example can communicate with the MSC424 via a network, the Internet and / or POTS ("plain ordinary telephone system"). Generally, a network or internet connection between wireless network 308 and MSC424 transfers data, and POTS transfers voice information. The MSC424 may be connected to one or more base stations 420. The MSC424 is typically connected to the branch-to-source (BTS) 426 by both the network and / or the Internet for data transfer and the POTS for voice information in a manner similar to carrier networks. BTS The 426 is ultimately known to wireless devices such as devices 100-A-D, which can be mobile phones, and from wireless devices, by short messaging services (SMS), or others known in the art. Broadcast and receive messages wirelessly by the wireless method of. It should be noted that carrier boundaries and / or PTT administrator network boundaries do not impede or interfere with the sharing of data as described herein.
Wireless communication devices, such as mobile phones or wireless phones, are being manufactured with additional computing power and are becoming comparable to personal computers and handheld PDAs. These "smart" mobile phones allow software developers to create software applications that are downloadable and executable on the processor of wireless devices. Wireless devices like Device 100 are many types of "data packages" that are separate segments of computer code, such as applications, web pages, applets, MIDlets, multimedia, pictures, games, and simple data. Can be downloaded. In a wireless device with communication group 302 (as shown in FIG. 3), the wireless communication device can connect directly with the other members of the set and participate in voice and data communication. However, in various embodiments, such direct group communication may take place through or under the control of the group communication server 310. Not all data packets of the device are necessarily forwarded through the communication server 310 itself, but in various embodiments it is preferred that the communication server 310 can ultimately control communication. It is the only communication server 310 that can typically recognize and / or retrieve the identity of a member of a communication group, or direct the identity of a member of a communication group 302 to another computer device. This is because it is a server-side component.
FIG. 5 is a process flow diagram illustrating Method 500 of an embodiment communicating over a wireless network using a wireless communication device having a group communication function, such as a "push-to-talk" (PTT) function. Although the methods of the various embodiments may be described herein as utilizing the "push-to-talk" feature, it is understood that the methods of the embodiments may be applicable to other types of group communications. Will be. 6A-6C are screenshots of the touch screen user interface 104 of an exemplary wireless communication device 100 suitable for carrying out method 500, according to one embodiment. In various embodiments, the wireless communication device 100 uses software such as the touch screen display 104 and native device hardware, and / or other user interfaces such as the keypad interface, such as PTT communication. Provide group communication. In various embodiments, the PTT methods described herein can be performed on a wide range of devices, including most Internet-enabled mobile phones and other wireless communication devices. In various embodiments, the method can be implemented using wireless communication devices that do not include dedicated PTT hardware such as PTT buttons or PTT-specific circuits.
In block 502 of choice, as shown in method 500, the wireless communication device 100 can download group communication application software such as PTT application software. The group communication application software may include all or part of the group communication client software as described above with respect to FIGS. 1 and 2. In various embodiments, a downloadable version of the group communication application software ensures that a device capable of supporting group communication downloads and runs the group communication application to provide group communication functionality to the wireless device. to enable. In other embodiments, the wireless device 100 may have factory-installed group communication application software, in which case optional block 502 may not be executed.
In block 504 of the option, the wireless communication device 100 can establish a group of one or more other wireless communication devices for group communication (eg, "group communication group"). It will be appreciated that a group communication group can include one other device. Group Communication A group may also include multiple other devices to allow "multicast" or "broadcast" communication with multiple devices over a wireless network using the group communication feature. As shown in FIGS. 6A-6C, a group communication group (university friends) containing six devices has been established, for example, the user's own wireless device 100 and five other devices.
In various embodiments, a group communication group can be established by one or more users of various wireless devices, for example, in an ad hoc process. The establishment of a group communication group can be performed through a server such as the communication group server 310 as described above with respect to FIGS. 3 and 4 or under the control of such a server. Multiple different group communication groups can be established, a single wireless communication device 100 may be included in multiple different group communication groups, and the group communication function can be used to communicate with any one device in the group. You will understand that you can. In some embodiments, one or more group communication groups may be pre-established on the wireless communication device 100, for example by a system administrator, in which case optional block 504 may not be performed.
At block 506, the wireless communication device 100 can initiate the group communication function in response to an input from the user of the device 100. For example, the user can use the appropriate user interface, such as the touch screen display 104 of FIGS. 6A-6C, to select from a menu and launch a group communication application on the wireless device 100. The initiation of the group communication function may also include the selection of the group communication group for which the group communication session is to be established, and the group communication group communication may consist of one or more wireless communication devices.
At block 508, the wireless communication device 100 can use the visual feedback on the display screen 104 of the device 100 to display the status of the group communication session. As described in more detail below, a display screen 104 consisting of a touch screen in various embodiments displays visual feedback instructions, including graphical elements and / or colors, to display a floor condition (ie, floor). It can indicate various states of a group communication session, such as open, floor grant, etc.), the state of other group members, the existence of long connection times, and so on.
Referring to an exemplary embodiment of the touch screen display 104 shown in FIGS. 6A-6B, FIG. 6A shows a touch screen display 104 in which a group communication application, specifically a PTT application, has been initiated. .. The display 104 identifies the group 602 in which the PTT communication session has been established and further displays a plurality of icons 604 representing individual members of the group 602. The virtual PTT button 606 is displayed on screen 104. In various embodiments, the virtual PTT button 606 can function like a traditional hardware PTT button. When the device 100 detects a touch event on the virtual button 606, the device 100 can send a request to the communication server 310 to open the communication channel from the wireless device 100 to other devices in the PTT group. FIG. 6B shows an exemplary embodiment of a display 104 showing a neutral state of a PTT session, in which the PTT session was initiated, for example, by the user's finger 610 touching the virtual PTT button 606. However, the communication channel is not currently established (ie, the "floor" is open). In Figure 6C, the user's finger 610 is touching the virtual button and the communication channel from wireless device 100 to other devices in the group is established and open (ie, the "floor" is the wireless communication device. Shows 104 when (given to 100). In this state, the wireless communication device 100 can transmit voice and / or other data to other devices in the PTT group on the wireless network. As shown in FIG. 6C, this condition (ie, the floor conferred on device 100) can be indicated by a color change that covers part 608 of display 104.
FIG. 7 is a process flow diagram illustrating method 700 of an embodiment of group communication, such as PTT communication, using visual feedback of the state of a group communication session. At block 702, the wireless communication device 100 can initiate a group communication session as described above. At block 704, device 100 can use visual feedback on display screen 104, which can be a touch screen display, to display the status of a group communication session. At block 706, the device 100 can detect the start of group communication by the user on the user interface of the device 100. In various embodiments, this may include the detection of touch events for "virtual" PTT buttons, as described above with respect to FIG. 6A. In other embodiments, such as devices without a touch screen interface, this may include detecting keystrokes to the keypad interface. At block 708, device 100 can send a request for a "floor" of group communication to a server such as the communication server 310 described above. At block 710, device 100 can display a visual feature that indicates the group communication status of the requested but not granted floor. In various embodiments, the visual features for this condition may correspond to the "neutral" condition shown in FIG. 6B. In other embodiments, this condition is a red or yellow screen when the floor is requested but not granted, and when the device 100 is granted the floor, it can change to a different color, such as green, color coded. Can be indicated by. While the floor is requested but not yet granted (ie, determination block 712 = No), device 100 can continue to display visual features indicating this condition. When a floor is granted (ie, decision block 712 = Yes), device 100 is device 100 whose floor is the user. It is possible to display a visual feature indicating that it has been assigned to. As discussed above, these visual features may include color changes of all or part of the display screen 104 (eg, from red or yellow to green), or other graphical feedback. May include display of instructions by. It will be appreciated that in addition to the visual feedback instructions described herein, other feedback instructions, such as voice or tactile instructions, can also be used to indicate the status of group communication. ..
8A-8C are further screenshots of the touch screen display 104 showing a group communication session of an embodiment, specifically a PTT communication session. FIG. 8A shows a screen displaying a visual feature indicating that a floor is assigned to the user's device 100, as discussed above with respect to FIG. 6C. In this embodiment, the device 100 displays a color change that covers a portion 608 of the screen when the floor is granted. The user's thumb 610 is shown to touch the screen. FIG. 8B shows a screen displaying visual features indicating a neutral state in which the floor is open. In this embodiment, the display 104 has an open floor, and a touch event to the display 104 or a portion 804 of the display 104 (eg, "push-to-talk") controls the floor of group communication to device 100. It can be shown to demand rights. FIG. 8C shows a screen displaying a visual feature indicating that another user's device has control of the floor. This condition can be indicated by changes in graphics and / or color on the display screen 104. In this embodiment, this state is indicated by displaying the contact icon 802 (eg, photo) of the user (eg, the person who is speaking) whose device is currently controlling the floor in a group communication session. Is done.
FIG. 9A is a process flow diagram illustrating Method 900 of an embodiment of group communication using visual feedback of the state of a group communication session. At block 902, the user's wireless communication device 100 can receive communications indicating the state of floor control in a group communication session from a server such as the group communication server 310 described above. When a floor is granted to the user's device (ie, decision block 904 = Yes), in block 906, device 100 provides a visual feature indicating the group communication state that the floor is granted to user's device 100. It can be displayed on the display screen. Visual features can include graphical elements and / or color changes as described above. FIG. 8A shows an example of a device screen in a group communication state in which a floor is assigned to a user's device according to one embodiment. When the floor is controlled by another device in the group communication group (ie, decision block 908 = Yes), in block 910, device 100 indicates a group communication state that the floor is assigned to a device of a different user. Visual features can be displayed on the display screen 104. Visual features can include graphical elements and / or color changes as described above. An example of a device screen in this state according to one embodiment is shown in FIG. 8C. In this embodiment, the visual feature may include a contact icon of the user whose device owns controls the floor of group communication, as shown in FIG. 8C. If the floor is not controlled by the user's device (ie decision block 906 = No) and the floor is not controlled by any other device in the group communication group (ie decision block 908 = No). At block 912, device 100 displays a visual feature that indicates a neutral state with the floor open. It can be displayed in 04. Visual features can include graphical elements and / or color changes as described above. An example of a device screen in a neutral state, according to one embodiment, is shown in FIG. 8B.
Until device 100 receives floor state communication from the server in block 902, device 100 can maintain various visual feedback features corresponding to group communication state in blocks 906, 910, and 912, respectively. Process can be repeated.
FIG. 9B is a process flow diagram illustrating method 901 of an embodiment with group communication using a server such as the group communication server 310 shown in FIGS. 3 and 4. At block 914, the server 310 can receive a request for control of the floor in a group communication session from user devices in the group communication group. At block 916, server 310 may determine floor control based on predetermined criteria, as discussed above. At block 918, the server 310 may send a message to the devices in the group indicating which device has control of the floor. At optional block 920, server 310 can also send media content and / or other data to the device. This transmitted data may be available by the device in displaying visual feedback of the status of floor control in a group communication session. For example, server 310 may transmit image files or other information that may be displayed by devices in the group while a particular device has control of the floor. In various embodiments, the device can determine whether or not to use the transmitted data in displaying a visual indication of the state of floor control.
Revisiting FIGS. 8A-8C, in various embodiments, the wireless communication device 100 displays visual feedback of the participation of one or more devices in group communication, such as PTT communication, display 104. May include. In various embodiments, the device 100 can display visual feedback indicating which users in the group can participate in the group communication, as well as which users in the group cannot participate. In various embodiments, the device 100 can also display why one or more users are unable to participate in group communication. As shown in FIG. 8A, the display screen 104 of the device 100 can display the identification information of the group 806 at which the group communication session with it has been started, and the identification information is the name of the group (for example, "University". ), The number of members in the group, and may also include group members currently participating in the group communication session (eg, you + 3/5 ). The display screen 104 can also display icons 810, 812, 814 representing each of the members of the group. The display screen 104 can display only a limited number of icons, allow the user to scroll through additional icons, and / or allow the user to view the icons of additional group members. It may include a separate icon 816 to allow it to be. The icon may include a group member photo 810 if available, and may include a default icon 812 if no photo is available. Icon 814 represents a member of a group who has not participated in a group communication session. In various embodiments, the non-participating group member icon 814 may include different visual characteristics than the participating group member icons 810, 812. In the embodiment shown in FIG. 8A, for example, icon 814 has a darker color than the other icons 810, 812. And also, it is partially faded out. Any suitable graphical feature can be utilized to indicate the participation status of various members. In various embodiments, the display 104 may include visual features to indicate why one or more group members are not participating. In some embodiments, the user clicks on the icon 814 of a non-participating member to see why they are not participating, for example, the member is busy (eg answering another phone call) and is out of touch. Possible (for example, member's device is out of coverage area or group communication is not possible), unresponsive (for example, user's device is turned off), or other You can indicate that you are not participating in the call for the reason (for example, a member has "muted" their device). In various embodiments, the user may be able to set the state of their wireless device (for example, "I can't talk because it's a meeting until 2 pm"), and this reason for not joining is another member of the group. Can be displayed on the device.
FIG. 10A is a process flow diagram illustrating Method 1000 of an embodiment of group communication, including visual feedback of the participation status of one or more devices in a communication group. At block 1002, the wireless communication device 100 can receive a request to initiate and / or join a group communication session with a group of one or more member devices. Requests can be received from users of device 100 on user interfaces such as touch screen displays or keypad interfaces. The request can also be received from another device within the communication group or from a server such as group communication server 310. At block 1004, device 100 can display a visual representation of one or more members of the communication group on the display screen. The visual representation of one or more members may include icons representing each of the members of the group, as shown in FIG. 8A. In various embodiments, different members of the communication group may be accessed from memory on device 100. In some embodiments, members of the communication group are determined via communication with a server such as group communication server 310, or through communication with one or more other devices on the wireless network. obtain. In block 1006, device 100 can determine the participation status of each member of the group. The step of determining the participation status may include a step of determining whether each member device is participating in or not participating in a group communication session. In various embodiments, the participation status of the various members may be determined via communication with a server such as the group communication server 310, or via one or more other devices on the wireless network. At block 1008, device 100 can display visual features that indicate the participation status of each of one or more members of the group. .. In various embodiments, the icons representing non-participating group members may include different visual features than the icons of participating group members, as shown in FIG. 8A. When the participation status of group members changes (ie, decision block 1010 = Yes), device 100 determines the updated participation status in block 1006 and provides a visual feature indicating the updated participation status in block 1008. Can be displayed. This process can continue while the session is active (ie, decision block 1012 = No). The session can end at block 1014 (ie, decision block 1012 = Yes).
Figure 10B provides visual feedback on the participation status of one or more group member devices in a communication group and an additional display of why one or more non-participating group member devices are not participating in a communication session. It is a process flow diagram which shows the method 1001 of an embodiment with group communication including. Blocks 1016 to 1020 are similar to blocks 1002 to 1006 of method 1000 shown in FIG. 10A, in which block 1016 initiates and / or participates in a group communication session with a group of one or more member devices. In block 1018, there is a step of displaying the visual representation of one or more members of the communication group, and in block 1020, there is a step of determining the participation status of each member of the group. Including. At block 1022, wireless communication device 100 can determine why one or more non-participating group members are not participating. In various embodiments, the reason for not participating is, for example, that a particular member is busy, the member's communication device is inaccessible, or the member's device is unavailable for other reasons. Can include being. At block 1024, the user's device 100 can display a visual feature that represents the participation status of each member of the group. In various embodiments, in optional block 1026, the user's device 100 makes a request to display one or more reasons why one or more non-participating group members are not participating. Can be received from the user on the interface. A request to display the reason for not participating can be made, for example, by clicking on the icon of a member who is not participating. At block 1028, in response to the request, device 100 can display the reason for not participating on the display screen 104. Some embodiments The optional block 1026 may be omitted, in which the device 100 can automatically display one or more reasons for not participating. When the participation status of one or more group members changes (ie, decision block 1030 = Yes), device 100 determines the updated participation status in block 1020 and any new participation in block 1022. It is possible to determine the reason why a non-member is not participating, and in blocks 1024 and 1028, the updated participation status and the reason for not participating can be displayed, respectively. Similarly, if the reason why one or more group members are not participating changes (ie, decision block 1032 = Yes), device 100 goes to block 1020 and updates the participation status and the reason for not participating. , Blocks 1024 and 1028 can display updated status and reasons. At block 1036, this can continue until the end of the group communication session (ie, decision block 1034 = Yes) (ie, decision block 1034 = No). You can update the reasons for not adding and display the updated status and reasons in blocks 1024 and 1028. At block 1036, this can continue until the end of the group communication session (ie, decision block 1034 = Yes) (ie, decision block 1034 = No). You can update the reasons for not adding and display the updated status and reasons in blocks 1024 and 1028. At block 1036, this can continue until the end of the group communication session (ie, decision block 1034 = Yes) (ie, decision block 1034 = No).
FIG. 10C is a process flow diagram showing method 1003 of an embodiment in which the server 310 operates in a group communication session. In some embodiments, method 1003 of FIG. 10 can be performed with method 1000 and / or method 1001 of FIGS. 10A and 10B, respectively. At block 1038, the server 310 can receive a request to initiate a group communication session sent by the wireless communication device. At block 1040, server 310 can determine the participation status of each member of the group. In block 1042, for non-participating group members, server 310 can determine why they are not participating. In block 1044, the server 310 communicates with at least one participating group indicating the participation status of at least one other group member and / or why at least one non-participating member is not participating. Can be sent to member devices. If the participation status of one or more group members changes (ie, decision block 1046 = Yes), or if the reason for not participating changes (ie, decision block 1048 = Yes), server 310 proceeds to block 1020. In block 1022, the updated participation status and reason can be determined, and in block 1044, at least one participating group communicates to update the participation status and / or the reason for not participating. Can be sent to members. At block 1052, this can continue until the end of the group communication session (ie, decision block 1050 = Yes) (ie, decision block 1050 = No).
11A-11D show a user-activated locking mechanism that can be used to lock floor control in a group communication (eg, PTT) capable device 100 for "hands-free" operation. It is a screenshot of the screen display 104. In FIG. 11A, display 104 includes a virtual PTT button 1102. In various embodiments, the virtual PTT button 1102 can function like a traditional hardware PTT button. When the device 100 detects a touch event to the virtual button 1102, the device 100 can send a request to the communication server 310 to open the communication channel from the wireless device 100 to other devices in the PTT group. FIG. 11B shows a display screen 104 showing that the user's finger 610 is touching the display screen 104 and a floor is attached to the user's device 100. As described above, the display screen 104 can use visual feedback such as graphical elements or color coding to indicate to the user that the floor has been granted.
In some embodiments, in a conventional mode of operation, device 100 may retain floor control while the device detects a touch event on screen 104 or a portion thereof. Thus, the device can behave like a traditional PTT-enabled device with a dedicated PTT button that the user must hold down the PTT button while communicating with the group. Therefore, in order to communicate with at least one other member of the communication group, the user must maintain continuous touch contact with the screen 104. Even if the user maintains touch contact with the screen, for example, another device in the group that has a higher priority than the original user's device, as determined by server 310, simultaneously requests control of the floor. If so, it will be understood that the user's device can lose control of the floor.
In various embodiments, in addition to the conventional modes described above, the device 100 may additionally include a "hands-free" mode, in which the user maintains continuous contact with the screen. The locking mechanism can be activated to maintain control of the floor without the need (ie, "lock" the floor). The locking mechanism actuated by the user can take various forms, such as a virtual button on a touch screen interface / display, or keystrokes into a traditional keypad interface. As shown in FIG. 11B, the locking mechanism 1104 may be a sliding lock on the touch screen display 104. The sliding lock may be a "target-based" lock, which allows the user to touch a first position on the screen and then slide their finger 610 to a second "target" position on the screen. By doing so, it means that the lock can be activated. The device 100 can detect a touch event to the first position and a sliding motion of the finger 610 to the second "target" position. When the device 100 detects a finger 610 within a predetermined neighborhood of the target position, the device 100 can enter "hands-free" mode, in which the device 100 is in continuous user contact with the user interface. Maintain an open communication channel without the need for. In the example shown in FIGS. 11A-11B, the first position may be the virtual PTT button 1102 of FIG. 11A and the second or "target" position is the "slide and lock" bar of FIG. 11B. It may be 1104. The user can activate the "hands-free" mode by sliding his finger 610 from the virtual PTT button 1102 onto the "slide and lock" bar 1104. This activates the sliding lock mechanism. Device 100 provides visual and / or audio feedback that it has entered "hands-free" mode Can be provided. For example, as shown in FIG. 11C, when entering "hands-free" mode, the "slide and lock" bar 1104 may disappear and the "slide and unlock" bar 1106 may appear in different positions. In various embodiments, the "hands-free" mode may allow the user to maintain an open PTT communication channel without physical contact with the user interface or even holding a device. As shown in FIG. 11C, in "hands-free" mode, the device can retain control of the "floor" of group communications when the user's finger 610 leaves screen 104. Device 100 can take advantage of speakerphone options. In certain embodiments, as shown in FIG. 11D, the hands-free mode can be connected to the device 100 via a suitable link, which can be a wireless link 1108, such as a BLUETOOTH® wireless link, of the headset. Can be used with such earpiece devices 1110.
The device 100 either until the device 100 loses control of the floor (for example, until the server 301 grants control of the floor to another device based on the server floor arbitration priority rule), or the user activates the unlock mechanism. You can stay in hands-free mode until you let it. In various embodiments, the unlocking mechanism may be the same mechanism as the locking mechanism, allowing the user to switch between a locked state and an unlocked state. Thus, to disable the locking mechanism, the user can slide the locking mechanism (eg, a virtual display on the touch screen interface) in the opposite direction of the locking action. The unlocking mechanism may be a virtual button on the touch screen interface / display or a keystroke to a conventional keypad interface. As shown in FIG. 11C, the unlocking mechanism 1106 may be a sliding lock on the touch screen display 104. The sliding lock may be a "target-based" lock, as described above. In the example shown in FIG. 11C, the user touches a possible first position in the central area of display 104 and slides his or her finger to a possible "target" position on the "slide and unlock" bar 1106. can do. When device 100 detects a user's finger within a predetermined neighborhood of the "slide and unlock" bar 1106, the device exits "hands-free" mode, disables the locking mechanism, and returns to the mode of conventional operation. Can be done.
FIG. 12A is a process flow diagram illustrating a method 1200 of an embodiment with group communication, such as PTT communication, with a wireless communication device 100 using a "hands-free" mode. The device 100 can start a group communication session in block 1202 and determine the state of group communication in block 1203. At block 1204, device 100 can use visual feedback to display the status of a group communication session on display screen 104. At block 1206, device 100 can receive user input on the user interface and initiate group communication. As described above with respect to FIGS. 11A-11D, the user input can be a touch event on the touch screen, such as a touch event for a virtual PTT button. In other embodiments, the user input can be a key input to the keypad interface. At block 1208, device 100 can send a request for control of the "floor" in a group communication session to a server such as communication server 310. If floor control is not granted (ie, decision block 1210 = No), the device can proceed to block 1203 to determine the status of group communication. When floor control is granted (ie, decision block 1210 = Yes), in block 1212 device 100 may establish an open group communication channel with one or more devices in the communication group. it can. At block 1214, the device 100 can display visual feedback on the display screen 104 indicating the group communication status of the floor given to the user's device.
At block 1215, the device can display what indicates that the user has the ability to lock the floor. This may include displaying an on-screen locking mechanism, such as the "slide and lock" instruction in FIG. 11B. At block 1216, device 100 can detect the activation of the locking mechanism by the user on the user interface. In various embodiments, the locking mechanism actuated by the user may be, for example, a virtual button on a touch screen interface / display or keystrokes into a conventional keypad interface. In some embodiments, the locking mechanism 1104 may be a sliding lock on the touch screen display 104, as shown in FIGS. 11A-11D. The sliding lock may be a "target-based" lock, which allows the user to touch a first position on the screen and then slide their finger to a second "target" position on the screen. This means that the lock can be activated.
When the locking mechanism is activated, at block 1218, device 100 can maintain an open group communication channel in "hands-free" mode. As explained above, the device 100's "hands-free" mode allows the device to control the floor without the user having to maintain continuous contact with the user interface as with traditional PTT-enabled devices. It may be possible to maintain the rights (ie, "lock" the floor). At block 1220, device 100 can provide an indication of the group communication status of the locked floor to the user's device. For example, device 100 provides audio feedback and / or displays visual feedback on the display screen 104 to indicate that the floor is locked to the user's device in "hands-free" mode. Can be done. The device 100 may remain in "hands-free" mode while the locking mechanism remains active (ie, determination block 1222 = Yes). The user can unlock the device 100 by activating the unlocking mechanism, which in various embodiments may be the same as the locking mechanism, displaying in the opposite direction of locking. It may include disabling the locking mechanism by moving it, and may be a keystroke to a virtual button or keypad interface on the touch screen interface. As shown in FIGS. 11A-11D, the unlocking mechanism 1106 may be a sliding lock on the touch screen display 104. The sliding lock may be a "target-based" lock, which allows the user to touch a first position on the screen and then slide their finger to a second "target" position on the screen. This means that the device can be unlocked.
If the locking mechanism is disabled or no longer activated (ie, decision block 1222 = No), at block 1224, device 100 exits "hands-free" mode and the floor no longer locks to the user's device. It is possible to provide something that indicates that it has not been done. The device 100 may continue group communication (ie, decision block 1227 = Yes) and at block 1229 maintain the communication channel in response to user input (such as the user continuing to touch the touch screen). Alternatively, the device may not continue the communication channel (ie, decision block 1227 = No) and close the communication channel at block 1231. In various embodiments, the locking mechanism as described above with respect to FIGS. 11A-11D and 12 provides other PTT modes in place of or in addition to the "hands-free" mode described above. Can be used to get started. In some embodiments, the device 100 may include a plurality of locking mechanisms activated by the user, the plurality of locking mechanisms being, for example, a touch screen interface / virtual button on a display, and / or a conventional key. It may be a key input to the pad interface. In some embodiments, the device 100 may include a sliding lock on the touch screen display 104, as shown in FIGS. 11A-11D. The sliding lock may be a "target-based" lock having a plurality of different "target" positions on the screen. The user can activate and release different locks by touching a first position on the screen and then sliding his finger to a different "target" position on the screen. According to various embodiments, different target positions may correspond to different PTT modes.
FIG. 13A is a process flow diagram illustrating method 1300 of an embodiment with group communication, such as PTT communication, with wireless communication device 100 using "priority lock" mode. The priority lock mode can be used when the user desires the priority acquisition right of the "floor" in the group communication. In various embodiments, initiating the "priority lock" mode can give the device unobstructed control of the floor in group communication while the priority lock is active. In various embodiments, initiating a priority lock by the user's device can temporarily change the priority rule used by the server 310 in arbitrating the various devices in the group for floor control. In various embodiments, priority lock mode gives device 100 a higher priority than device 100 if the device is not in priority lock mode when arbitrating competing requests for the floor. Can be used in server 310.
In method 1300 of the embodiment shown in FIG. 13A, at block 1302, device 100 can determine the state of a group communication session. At block 1304, the device 100 can use visual feedback to display the state of the group session on the display screen 104. At block 1306, device 100 can receive user input on the user interface and initiate group communication. As described above with respect to FIGS. 11A-11D, the user input can be a touch event on the touch screen, such as a touch event for a virtual PTT button. In other embodiments, the user input can be a key input on the keypad interface. At block 1308, device 100 can send a request for control of the "floor" in a group communication session to a server such as communication server 310. If floor control is not granted (ie, decision block 1310 = No), in block 1302 the device can determine the updated state of group communication and in block 1304 display the updated state. .. Once floor control is granted (ie, decision block 1310 = Yes), in block 1312 device 100 can establish an open group communication channel with one or more devices in the group. .. At block 1314, the device 100 can display visual feedback on the display screen 104 indicating the group communication status of the floor given to the user's device. The device 100 can further provide the user with an indication that the priority lock mode is available.
At block 1316, device 100 can detect the activation of the priority locking mechanism by the user on the user interface. In various embodiments, the locking mechanism actuated by the user may be, for example, a virtual button on a touch screen interface / display or keystrokes into a conventional keypad interface. In some embodiments, the locking mechanism may be a sliding lock on the touch screen display 104, such as the sliding locking mechanism shown in FIGS. 11A-11D. A sliding lock may be a "target-based" lock, which allows the user to touch a first position on the screen and then slide their finger to a second "target" position on the screen. By doing so, it means that the lock can be activated. In various embodiments, the sliding lock may include multiple target positions on the display screen, where each target position initiates a different group communication mode of the device. For example, the first target position may correspond to the "priority lock" mode, and the second target position corresponds to another mode, such as the "hands-free" mode described above with respect to FIG. It's okay.
Upon detecting the user activation of the priority locking mechanism in block 1316, in block 1318 the device 100 can send a request to obtain the priority floor to a server such as the communication server 310. If the request is not granted (ie, decision block 1320 = No), in block 1332, device 100 can then communicate through the group communication channel in priority unlock mode. If the request is granted (ie, decision block 1320 = Yes), device 100 maintains the group communication channel in "priority lock" mode in block 1322 and is locked to user device 100 in block 1324. The status of floor priority can be displayed. In various embodiments, the priority lock mode can give device 100 control of the floor, which generally cannot be disturbed by another device in the group. While the priority lock mechanism is active (ie, decision block 1326 = Yes), in block 1322, the device can maintain the group communication channel in "priority lock" mode. If the priority lock mechanism is no longer activated (ie, decision block 1326 = No), in block 1328 device 100 exits priority lock mode, indicating that the floor priority is no longer locked. Can be provided. At block 1330, device 100 can notify server 310 that priority floor acquisition is no longer required. At block 1332, device 100 can continue to communicate through the group communication channel in priority unlock mode.
In some embodiments, the priority locking mechanism may allow the user to lock the device to one of a plurality of different priority levels. This may be similar to the gear shift of an automobile transmission, in which case the different priority levels are similar to the gears with different gear shifts (eg, 1st, 2nd, 3rd, etc.). The first priority lock level can give the first level priority to the floor control, and the second priority level is the second progressively higher level of priority to the floor control. Rights can be granted and so on. Various priority levels can be activated using the target-based sliding locking mechanism as described above, in which case the user can use the locking mechanism to perform a gradual level of priority locking. Can be activated.
FIG. 13B is a process flow diagram illustrating method 1301 of an embodiment in which the server 310 operates in a group communication session, such as a PTT communication session, where the user device requests priority floor acquisition. In some embodiments, method 1301 of FIG. 13B can be performed with method 1300 of FIG. 13A. At block 1334, the server 310 can receive a request for preferential floor acquisition from the first user device 100. In determination block 1336, the server 310 can determine whether to accept or reject the request. For example, if the priority locking mechanism is not allowed for the requesting user device 100, or is unavailable for other reasons, the server 310 may reject the request (ie, determine). Block 1336 = "No"). Server 310 then sends a message to first user device 100 that the request to obtain the preferred floor was denied in block 1346, and in block 1344 according to the usual priority rules (ie, to first user device 100). Floor control of group communication sessions can be arbitrated (without giving preferential access). If the server 310 accepts the request to obtain the preferred floor (ie, decision block 1336 = "Yes"), in block 1338 the server 310 sends a message to the first user device 100 indicating that the preferred floor has been granted. Can be sent. In block 1340, the server 310 can arbitrate the floor control of the group communication session while the preferred floor acquisition is given to the first user device 100. In various embodiments, the server 310 can grant priority floor acquisition by immediately granting a floor to the first user device 100, regardless of whether another device currently has a floor. Floor obstruction until first user device 100 indicates that is no longer required It is possible to give the first user device 100 a control right that cannot be obtained. At block 1342, the server 310 can receive a message from the first user device 100 that priority floor acquisition is no longer requested. At block 1344, the server 310 can then arbitrate the floor control of the group communication session according to the usual priority rules (ie, without giving preferential access to the first user device 100).
In various embodiments, the server 310 can grant priority floor access to the user device for a predetermined maximum period of time, and if no message is received from the user device 100 within that period, the server 310 will use the user device. You can cancel the priority floor acquisition right for 100. Server 310 can also implement a priority rule to handle floor control if two or more user devices request priority floor acquisition at the same time.
FIG. 14A is a process flow diagram illustrating method 1400 of an embodiment with group communication, such as PTT communication, with a wireless communication device 100 using a "media lock" mode. Media lock mode allows other devices to send audio data to a group while the user wants preferential access to the "floor" for sending media files to one or more members of the group in group communication. Can be used if it is still possible. Media files can include, for example, image files, video files, audio files, documents, and presentations. In some embodiments, initiating a "media lock" mode can give the device unobstructed control of the floor for transmitting media files in group communications while the media lock is active. In various embodiments, when the user's device initiates a media lock, the priority rule used by the server 310 in arbitrating floor control to send media files between different devices in the communication group is temporary. Can be changed.
In method 1400 of the embodiment shown in FIG. 14A, device 100 determines the state of the group communication session in block 1402 and in block 1404 the determined state of the group communication session using visual feedback. It can be displayed on the display screen 104. At block 1406, device 100 can detect the activation of the media locking mechanism by the user on the user interface. In various embodiments, the media locking mechanism actuated by the user may be, for example, a virtual button on a touch screen interface / display or a keystroke into a conventional keypad interface. In some embodiments, the media lock mechanism may be a sliding lock on the touch screen display 104, such as the sliding lock mechanism shown in FIGS. 11A-11D. A sliding lock may be a "target-based" lock, which allows the user to touch a first position on the screen and then slide their finger to a second "target" position on the screen. By doing so, it means that the lock can be activated. In various embodiments, the sliding lock may include multiple target positions on the display screen, where each target position initiates a different group communication mode of the device. For example, the first target position may correspond to the "media lock" mode, and one or more additional target positions may be above for the "hands-free" mode and / or 13A described above with respect to FIG. Other modes may be supported, such as the "priority lock" mode described in.
Upon detecting user activation of the media lock mechanism in block 1406, device 100 can send a request for media lock to a server such as communication server 310 in block 1408. If the request is not granted (ie, decision block 1410 = No), in block 1428, device 100 can transmit media in the usual way through a non- "media lock" channel. If the request is granted (ie, decision block 1410 = Yes), device 100 may establish a group media communication channel at block 1412 and maintain the group media communication channel at block 1414 in "media lock" mode. it can. At block 1416, the device 100 can display on the display screen 104 a visual feature indicating the group communication status of the recognized media lock. While the media lock mechanism is operating (ie, decision block 1418 = Yes), in block 1414, device 100 can maintain the group media communication channel in media lock mode. If the media lock mechanism is no longer active (ie, decision block 1418 = No), in block 1422, device 100 can send a message to server 310 to terminate the media lock. Device 100 can stop media communication (ie, decision block 1424 = No) and close the group media communication channel in block 1426. Alternatively, the device can continue media communication (ie, decision block 1424 = Yes) and transmit media through a non- "media lock" channel in block 1428.
FIG. 14B is a process flow diagram illustrating method 1401 of an embodiment in which Server 310 operates in a group communication session, such as a PTT communication session, in which the user device requires a "media lock" to send media files. .. In some embodiments, method 1401 of FIG. 14B can be performed with method 1400 of FIG. 14A. At block 1430, the server 310 can receive a request for a media lock from the first user device 100. In the determination block 1432, the server 310 can determine whether to accept or reject the request. For example, if the media locking mechanism is not allowed for the requesting user device 100, or is unavailable for other reasons, the server 310 may reject the request (ie, determine block). 1432 = No). Server 310 then sends a message to first user device 100 that the request for media lock has been denied in block 1442, and in block 1440 using normal precedence rules (ie, first user device). Floor control of group communication sessions can be arbitrated for sending media files (without giving 100 media locks). If the server 310 accepts the request to obtain the preferred floor (ie, decision block 1432 = Yes), in block 1434, the server 310 sends a message to the first user device 100 indicating that the preferred floor has been granted. be able to. At block 1336, the server 310 can lock control of the floor for sending media files to the first user's device 100. In various embodiments, the floor is "locked" to the first user's device 100 for the transmission of media files, but the server 310 is still for voice communication between the various user devices in the communication group. Therefore, the control right of the floor can be arbitrated. Block 1 At 438, the server 310 can receive a message from the first user device 100 that the media lock is no longer requested. At block 1440, server 310 can then arbitrate floor control for the transmission of media files according to normal priority rules (ie, without giving media lock to first user device 100).
In various embodiments, the server 310 can grant the user device 100 a media lock for a predetermined maximum period of time, and if no message is received from the user device 100 within that period, the server 310 releases the media lock. can do. Server 310 can also implement a priority rule to handle floor control if two or more user devices request media locks at the same time.
FIG. 15A is a process flow diagram illustrating method 1205 of an embodiment with PTT communication with the wireless communication device 100 using the "lock out" mode. Lockout mode is used to allow a user to temporarily exclude one or more members of a group communication group from receiving communication from the user's device 100 during a group communication session. Can be done.
In method 1500 of the embodiment shown in FIG. 15A, at block 1502, device 100 can initiate a group communication session such as PTT communication. At block 1504, device 100 can use visual feedback to display the status of a group communication session on display screen 104. At block 1506, device 100 can detect the activation of the lockout mechanism by the user on the user interface. In various embodiments, the lockout mechanism actuated by the user may be, for example, a virtual button on a touch screen interface / display or keystrokes into a conventional keypad interface. In some embodiments, the lockout mechanism may be a sliding lock on the touch screen display 104, such as the sliding lock mechanism shown in FIGS. 11A-11D. A sliding lock may be a "target-based" lock, which allows the user to touch a first position on the screen and then slide their finger to a second "target" position on the screen. By doing so, it means that the lock can be activated. In various embodiments, the sliding lock may include multiple target positions on the display screen, where each target position initiates a different group communication mode of the device. For example, the first target position may correspond to the "lock out" mode, and one or more additional target positions are described above for the "hands-free" mode described above with respect to FIG. 12 and above with reference to FIG. 13A. Other group communication modes may be supported, such as the "priority lock" mode and / or the "media lock" mode described above with respect to FIG. 14A.
In various embodiments, the user can select one or more members of the group to be "locked out" from group communications. For example, the user can select a contact icon that represents a particular group member and activate the lockout mechanism to lock out that group member from group communications. In some embodiments, the contact icon of the group member to be locked out may be the "target" in the target-based sliding lock mechanism. Users can slide their fingers to specific contact icons to keep each user out of group communication. In some embodiments, the user can drag the contact icon to an additional target location, such as the "lock" icon, to implement a lock mode for that group member. In other embodiments, the device 100 can display a locking mechanism associated with each contact icon (eg, slide to display a lock bar, "virtual" switch, toggle, button, etc.). The locking mechanism may be displayed, for example, after the user first touches the contact icon. By activating the locking mechanism, the lockout mode for the selected group member can be implemented.
Upon detecting user activation of the lockout mechanism in block 1506, device 100 in block 1508 can establish a group communication channel with one or more devices in the group, excluding devices of group members that are locked out. .. This may involve a temporary reconfiguration of the group communication session, which may be performed by or with the group communication server 310, as discussed below. In block 1510, the user device 100 can exclude the locked group member devices from the outgoing group communication. At block 1512, the device 100 can display on the display screen 104 a visual feature indicating that the lockout is working for the selected group member. If lockout is active (ie, decision block 1514 = Yes), in block 1510 device 100 may continue to exclude the lockout group member devices from group communications originating from the user's device 100. it can. If the lockout mechanism is no longer in operation (ie, decision block 1514 = No), in block 1516, device 100 may include previously locked out group member devices in outgoing group communications. In other words, the group communication session can revert to its original configuration.
FIG. 15B shows a method of an embodiment of server 310 operation in a group communication session, such as a PTT communication session, in which a lockout mechanism for at least one other user device in the communication group is operating on one user device. It is a process flow diagram which shows 1501. In some embodiments, method 1501 of FIG. 15B can be performed with method 1500 of FIG. 15A. At block 1518, the server 310 can configure a group communication session between multiple user devices in the usual way. At block 1520, the server 310 can receive from the first user device 100 that the lockout mechanism is operating for at least one second user device in the communication group. At block 1522, server 310 may (temporarily) reconfigure the group communication session to exclude communication from the first user device 100 from being received by the "locked out" device. it can. At block 1526, the server 310 maintains this reconfigured group communication session until it receives from the first user device 100 that the lockout is no longer working for at least one second user device. Can be (block 1526). At block 1528, server 310 can return to the initial configuration of the group communication session.
FIG. 16A is a process flow diagram illustrating method 1600 of an embodiment with group communication, such as PTT communication, with a wireless communication device 100 using "block" mode. Block mode allows the user to temporarily block the user's device 100 from receiving communication from the devices of one or more selected members of the group communication group during a group communication session. Can be used to do so.
In method 1600 of the embodiment shown in FIG. 16A, at block 1602, device 100 can initiate a group communication session. At block 1604, the device 100 can use visual feedback to display the state of the group session on the display screen 104. At block 1606, device 100 can detect the activation of the blocking mechanism by the user on the user interface. In various embodiments, the blocking mechanism activated by the user may be, for example, a virtual button on a touch screen interface / display, or a keystroke into a conventional keypad interface. In some embodiments, the blocking mechanism may be a sliding lock on the touch screen display 104, such as the sliding lock mechanism shown in FIGS. 11A-11C. A sliding lock may be a "target-based" lock, which allows the user to touch a first position on the screen and then slide their finger to a second "target" position on the screen. By doing so, it means that the lock can be activated. In various embodiments, the sliding lock may include multiple target positions on the display screen, where each target position initiates a different group communication mode of the device. For example, the first target position may correspond to a "block" mode, and one or more additional target positions are described above for the "hands-free" mode described above with respect to FIG. 12 and above with reference to FIG. 13A. Other modes may be supported, such as the "priority lock" mode, the "media lock" mode described above for FIG. 14A, and / or the "lock" mode described above for FIG. 15A.
In various embodiments, the user can select one or more members of the group that should "block" from receiving group communication by the user's device 100. For example, the user can select a contact icon representing a particular group member and activate a blocking mechanism to block communication from the selected group member. In some embodiments, the group member contact icon to be blocked may be the "target" in the target-based sliding lock mechanism. Users can slide their fingers to specific contact icons to block each user. In some embodiments, the user can perform a block by dragging the contact icon of a particular group member into the target area, such as the "block" icon. In other embodiments, the device 100 can display a locking mechanism associated with each contact icon (eg, slide to display a lock bar, "virtual" switch, toggle, or button). The blocking mechanism may be displayed, for example, after the user first touches the contact icon. By activating the blocking mechanism, blocking of selected group members can be performed.
Upon detecting user activation of the blocking mechanism in block 1606, in block 1608, device 100 can block communication from selected blocked group members from being received by user device 100. At block 1610, the device 100 can display on the display screen 104 a visual feature indicating that the blockage is working for the selected group member. While blocking is active (ie, decision block 1612 = Yes), in block 1608, device 100 can continue to block communication from blocked members. If the blocking mechanism is no longer active (ie, decision block 1612 = No), at block 1614, device 100 can receive communications from previously blocked group members.
In some embodiments, blocking mode does not hear or see the communication from the blocked group member, but other users in the group can still receive communication from the blocked member. And may be similar to the "Mute" button. In some embodiments, the blocking feature may be implemented on the user device 100 without server awareness or mediation. In another embodiment, the user device 100 can signal a server such as the group communication server 310 when the blocking mechanism is active, and the server 310 blocks communication from the blocked device. The communication session can be reconfigured so that it is not sent to the device 100. In some embodiments, the blocking mechanism can be activated on a group member device to block the transmission of any communication of the selected device to the group (for example, the blocked device is "floor". Can be prevented from gaining control). In this embodiment, when the blocking mechanism is activated, the device 100 can send a request to block the defined device from communicating with the group to a server such as the group communication server 310. Server 310 can determine whether to block a device based on a predetermined blocking criterion, which may be stored in server 301, for example, the priority state of the user requesting blocking, blocked. It may include the priority status of the requested user, the number of different blocking requests received for a particular user, and so on.
FIG. 16B shows an embodiment of the operation of Server 310 in a group communication session, such as a PTT communication session, in which a blocking mechanism for at least one other user device in the communication group is operating on one user device. It is a process flow diagram which shows 1601. In some embodiments, method 1601 of FIG. 16B can be performed with method 1600 of FIG. 16A. At block 1616, the server 310 can configure a group communication session between multiple user devices in the usual way. At block 1618, the server 310 indicates that the blocking mechanism is operating for at least one second user device (ie, the "blocked" device) in the communication group. It can be received from device 100. At block 1620, the server 310 may (temporarily) reconfigure the group communication session to exclude communication from the "blocked" device from being received by the first user device 100. it can. As discussed above, in various embodiments, the server 310 reconfigures the group communication session so that communication from the "blocked" device is not received by any other device in the communication group. be able to. At block 1624, server 310 continues this reconfigured group communication session until it receives from the first user device 100 that the blocking mechanism is no longer working for at least one second user device. Can be maintained (block 1622). At block 1626, server 310 can return to the initial configuration of the group communication session.
17A-17C are screenshots of the touch screen display 104 of the wireless communication device 100 with a "quick contact" PTT shortcut on the desktop / home screen of the device 100. As shown in FIG. 17A, the device 100 may allow the user to display one or more shortcut icons 1704 on the PTT contacts on the home screen 1702. PTT contacts can be individual PTT users or groups of PTT users. The qualified PTT button 1706 may appear when the shortcut icon 1704 is selected, as shown in Figure 17B. The device 100 can detect a touch event on the PTT button 1706 and, in response, establish a PTT communication channel with the contact device indicated by the icon 1704. As shown in FIG. 17C, in some embodiments, the modified PTT button can also slide to support the locking mechanism 1708. The sliding locking mechanism 1708 can initiate either a "hands-free" mode of operation and / or one of the modes of operation described above with respect to FIGS. 12-16B. This is an improvement over existing non-dedicated hardware methods in that users do not have to find / launch / interact with PTT applications in order to talk to their contacts quickly.
FIG. 18A is a process flow diagram illustrating method 1800 of an embodiment with group communication, such as PTT communication, using the "quick contact" shortcut. At block 1802, the wireless communication device 100 may display at least one quick contact group communication shortcut icon on the home screen of the device display 104. The display 104 may be a touch screen display. The quick contact shortcut icon may be prepared by the user or may be automatically generated by the device 100, for example, based on the contact information stored on the device.
The device 100 can detect the user's selection of the quick contact group communication shortcut icon on the user interface in block 1804 of arbitrary selection, and in step 1806, the group communication button associated with the quick contact group communication shortcut icon (eg, for example). PTT button) can be displayed. In some embodiments, optional step 1804 may be omitted, in which device 100 can automatically display a quick contact shortcut icon and associated group communication button. In some embodiments, the group communication button may include part or all of the quick contact group communication shortcut icon. At block 1808, device 100 can detect the user's selection of group communication buttons on the user interface. In various embodiments using a touch screen display, the device 100 can detect a touch event on a group communication button. At block 1810, device 100 can initiate group communication with the device of the selected contact.
FIG. 18B is a process flow diagram illustrating method 1801 of an embodiment with group communication, such as PTT communication, using a "quick contact" shortcut and a sliding lock mechanism. Blocks 1812 to 1816 are similar to blocks 1802 to 1806 of method 1800 shown in FIG. 18A, in which block 1812 displays at least one quick contact group communication shortcut icon on the home screen of display 100 of the wireless communication device. And, in block 1814 of choice, the step of detecting the user's selection of the quick contact group communication shortcut icon on the user interface, and in block 1816, the group communication button associated with the quick contact group communication shortcut icon (eg, PTT). Includes steps to display the button). At block 1820, device 100 can detect the activation of the locking mechanism by the user on the user interface. The locking mechanism can be a sliding lock that is displayed in response to a user selection of the group communication button, as shown in FIGS. 17A-17C. The sliding lock operation can enter a mode of "hands-free" operation. At block 1822, device 100 can initiate group communication with the device of the contact selected in "hands-free" mode. In an alternative embodiment, the sliding lock mechanism can initiate any of the modes of operation described above with respect to FIGS. 12-16B.
FIG. 19 is a system block diagram of a wireless communication device for use with any of the embodiments. Embodiments can be implemented in various mobile wireless communication devices, especially mobile computing devices. An example of a wireless communication device that can implement various embodiments is the smartphone 2800 shown in FIG. A wireless communication device such as the smartphone 2800 may include a memory 2802 and a processor 2801 coupled to a radio frequency data modem 2805. Modem 2805 may be coupled to antenna 2804 to receive and transmit radio frequency signals. The smartphone 2800 may also include a display 2803, such as a touch screen display. The mobile device 2800 may also include a user input device, such as a button 2806, to receive user input. In various embodiments, the smartphone 2800 can be mounted on the display 2803 of the mobile device 2800 (eg, using E-Sense technology), on the back 2812, or on another side, tactile output. Including the surface. The processor 2801 of a mobile device can be composed of any programmable microprocessor, microprocessor, which can be configured by software instructions (applications) to perform various functions, including the functions of the various embodiments described herein. Or it can be one or more multiprocessor chips. In general, software applications may be stored in internal memory 2802 before being accessed and loaded into processor 2801. For some mobile computing devices, additional memory chips (for example, Secure Data) (SD) card) can be plugged into a mobile device and coupled to processor 2801. The internal memory 2802 can be volatile memory, non-volatile memory such as flash memory, or a mixture of both. As used herein, the general reference to memory refers to all memory accessible by processor 2801, including internal memory 2802, removable memory plugged into a mobile device, and memory within processor 2801.
Various embodiments can be implemented in any of a variety of commercially available server devices, such as the server 2900 shown in FIG. Such a server 2900 typically includes a processor 2901 coupled with volatile memory 2902 and a large amount of non-volatile memory such as disk drive 2903. The server 2900 may also include a flexible disc drive, compact disc (CD) or DVD disc drive 2906 coupled to processor 2901. Server 2900 may also include network access port 2904 coupled to processor 2901 to establish a data connection with network 2905, such as other broadcast system computers and local area networks coupled to servers. Processors 2801, 2901 can be any programmable microprocessor, microcomputer, or one that can be configured with software instructions (applications) to perform various functions, including the functions of the various embodiments described above. Alternatively, it may be a plurality of multiple processor chips. Some devices may provide multiple processors 2801, 2901, such as one processor dedicated to wireless communication and one processor dedicated to running other applications. In general, software applications may be stored in internal memory 2802, 2902, and 2903 before being accessed and loaded into processors 2801, 2901.
Processors 2801, 2901 may include sufficient internal memory to store application software instructions. In many devices, the internal memory can be volatile memory, non-volatile memory such as flash memory, or a mixture of both. For the purposes of this specification, general reference to memory is internal memory, or memory accessible by processors 2801, 2901, including removable memory plugged into the device and memory within processors 2801, 2901 itself. Point to.
The description of the method and the process flow diagram above are provided merely as a helpful example and do not require or imply that the steps of the various embodiments must be performed in the order presented. As those skilled in the art will appreciate, the order of the steps in the above embodiments can be performed in any order. Words such as "after", "next", and "next" do not limit the order of the steps, and these words are used solely to guide the reader to an explanation of the method. Furthermore, for example, references to claim elements in the singular form using the articles "a", "an" or "the" should not be construed as limiting the element to the singular.
The various exemplary logical blocks, modules, circuits, and algorithm steps described with respect to the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To articulate this compatibility of hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general with respect to their functionality. Whether such functionality is implemented as hardware or software depends on specific application examples and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each specific application, but such implementation decisions should not be construed as causing a deviation from the scope of the invention. ..
The hardware used to implement the various exemplary logics, logic blocks, modules, and circuits described with respect to aspects disclosed herein are general purpose processors, digital signal processors (DSPs), and application specific integrated circuits. Designed to perform application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, individual gate or transistor logic, individual hardware components, or the functions described herein. It can be implemented or implemented in any combination of them. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. Processors are also implemented as a combination of computing devices, such as a combination of DSP and microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. obtain. Alternatively, several steps or methods may be performed by a circuit specific to a given function.
In one or more exemplary embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, a function may be stored on a non-temporary computer-readable storage medium as one or more instructions or codes. The steps of the method or algorithm disclosed herein can be embodied in a processor executable software module that can reside or be stored on a non-temporary computer-readable storage medium or processor-readable medium. Non-temporary computer-readable storage media and processor-readable storage media can be any usable medium that can be accessed by the computer or processor. By way of example, but not by limitation, such non-temporary computer-readable media are RAM, ROM, EEPROM, CD-ROM or other optical disc storage, magnetic disk storage or other magnetic storage device, or instruction or data structure. Can be used to store the desired program code in the form of, and may include any other medium that can be accessed by a computer. As used herein, discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), touchable discs, and Blu-ray discs. Including, a disk usually reproduces data magnetically, and a disk reproduces data optically by a laser. The above combinations should also be included within the scope of non-transitory computer-readable media. In addition, the behavior of the method or algorithm may be incorporated into a computer program product, as one or any combination of non-transitory processor-readable media and / or code and / or instructions on the computer-readable medium, or a set thereof. Can exist.
The above description of the disclosed aspects is provided to allow any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the invention. Therefore, the present invention is not intended to be limited to the embodiments presented herein, but is given the maximum scope consistent with the principles and novel features disclosed herein.
100 wireless communication devices 104 Touch screen interface / display, graphics display 106 Computer platform 108 processor 110 Application programming interface 112 memory 114 Local database 116 Direct communication interface 218 MSM 220 AMSS 222 mobile operating system 224 PTT recognition UI 226 PTT client 228 Media Client 230 other applications 300 system 301 smartphone 302 PTT Group 303 tablet computer 304 smart pager 306 Mobile information terminal 308 Wireless network 310 communication server 312 Server-side LAN 314 database 316 Media server 414 PDSN 416 Carrier network 418 Base station controller 420 base station 422 PCF 424 MSC 426 BTS 428 AAA 602 groups 604 icon 606 Virtual PTT Button 608 Part of the display 610 user's finger 802 contact icon 810 icon 812 icon 814 icon 816 icon 1102 virtual PTT button 1104 Lock mechanism 1106 Slide to unlock bar 1108 wireless link 1110 earpiece device 1702 home screen 1704 shortcut icon 1706 PTT button 1708 Sliding and locking mechanism 2800 smartphone 2801 processor 2802 memory 2803 display 2804 antenna 2805 Radio Frequency Data Modem 2806 button 2900 server 2901 processor 2902 Volatile memory 2903 disk drive 2904 Network access port 2905 network 2906 DVD disc drive
38 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31 Sheet 32 Sheet 33 Sheet 34 Sheet 35 Sheet 36 Sheet 37 Sheet 38
Every citation, both ways
| Document | Relation | Office | Category | Cited during |
|---|---|---|---|---|
| US2006008078A1 | Cites | United States of America | – | Search report |
| US2006008078A1 | Cites | United States of America | – | Search report |
| US2006008078A1 | Cites | United States of America | – | Search report |
| WO2006018635A1 | Cites | World Intellectual Property Organization (WIPO) | – | Search report |
| WO2006018635A1 | Cites | World Intellectual Property Organization (WIPO) | – | Search report |
| WO2006018635A1 | Cites | World Intellectual Property Organization (WIPO) | – | Search report |
| JP2006042355A | Cites | Japan | A | Search report |
| JP2006042355A | Cites | Japan | A | Search report |
| JP2008546301A | Cites | Japan | A | Search report |
| JP2008546301A | Cites | Japan | A | Search report |
| JPH056579U | Cites | Japan | – | Search report |
| JPH056579U | Cites | Japan | – | Search report |
| JPH056579U | Cites | Japan | – | Search report |
24 members in 7 offices
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 201161554876 | United States of America | P | |
| 201161554876 | United States of America | P | |
| 61554876 | United States of America | – | |
| 201213661371 | United States of America | A | |
| 201213661371 | United States of America | A | |
| 13661371 | United States of America | – | |
| 13661371 | – | – | – |
| 61554876 | – | – | – |
| US201161554876P | – | – | – |
| US201213661371 | – | – | – |
Members24
| Document | Office | Kind | |
|---|---|---|---|
| US2013109425A1 | United States of America | A1 | |
| US2013109426A1 | United States of America | A1 | |
| WO2013066888A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2013066893A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CN103918288A | China | A | |
| CN103918289A | China | A | |
| KR20140090229A | Republic of Korea | A | |
| KR20140092870A | Republic of Korea | A | |
| EP2774394A1 | European Patent Office (EPO) | A1 | |
| EP2774396A1 | European Patent Office (EPO) | A1 | |
| JP2014533038A | Japan | A | |
| JP2014533039A | Japan | A | |
| IN2342CHN2014A | India | A | |
| US9154925B2 | United States of America | B2 | |
| IN3640CHN2014A | India | A | |
| US9167392B2 | United States of America | B2 | |
| US2015341759A1 | United States of America | A1 | |
| KR20160010653A | Republic of Korea | A | |
| US9288639B2 | United States of America | B2 | |
| KR101617560B1 | Republic of Korea | B1 | |
| JP2016195418AThis record | Japan | A | |
| JP6054982B2 | Japan | B2 | |
| KR101702195B1 | Republic of Korea | B1 | |
| JP6271438B2 | Japan | B2 |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Written measure of dismissal of application [lapsed due to lack of payment]LapsedJAPANESE INTERMEDIATE CODE: A045A045 | A045 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 2016195418
- Publication, DOCDB
- 2016195418
- Publication, EPODOC
- JP2016195418
- Application
- 124193
- Application, DOCDB
- 2016124193
- Application, EPODOC
- JP20160124193
Titles2
- Japanese
- グループ通信を制御するためのユーザ体験の改善
- English
- Improved user experience to control group communication
Classification
- CPC, 8
- H04W4/08
- H04W4/10
- H04L65/4061
- H04L65/1069
- H04M1/724631
- G06F3/04817
- G06F3/04842
- H04M1/72469
- IPC, 4
- H04M1 00
- G06F3 0488
- H04M1 72469
- H04M3 56