System and method for push-to-share file distribution with previews
60 claims: 8 independent, 52 dependent
- 1通信リンクを介してメディアオブジェクトのプレビューを送信するように構成されたワイヤレス通信デバイスであって、ワイヤレス通信デバイスは: メモリと; メモリに接続されたプロセッサと;を含み、プロセッサは: 送信のためのメディアオブジェクトの選択を受信し; メディアサーバがターゲットデバイスにメディアオブジェクトを配信できるようにするフォーマットでメディアサーバにメディアオブジェクトを送信し; ユーザ選択に従って複数のプレビューを選択し、プレビューは、メディアオブジェクトから導き出された生成されたオブジェクトとメディアオブジェクトから導き出されなかった独立したオブジェクトとから構成されるグループから選択されるアイテムを含み;メディアオブジェクトのファイルフォーマット変換オプションを識別する情報をメディアサーバから受信し; グループ通信チャネルを介して複数のターゲットデバイスの各々に複数のプレビューの1つとメディアサーバからメディアオブジェクトをダウンロードするためのリンクとを送信すること; を含む動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とするワイヤレス通信デバイス。
- 2プロセッサは、メディアオブジェクトのユーザ定義メタデータを受信することをさらに含む動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 3プロセッサは、メディアオブジェクトの複数のプレビューを選択することが: 第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択し; 第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択し; グループ通信チャネルを介して第1のターゲットデバイスに第1のプレビューと、第2のターゲットデバイスに第2のプレビューとを送信すること; をさらに含むようにプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 4プロセッサは、第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択することが: エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択すること; をさらに含むように動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項3に記載のワイヤレス通信デバイス。
- 5プロセッサは、第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択することが: メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成すること; をさらに含むように動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項4に記載のワイヤレス通信デバイス。
- 6プロセッサは、ユーザ選択に従って複数のプレビューを選択することが: エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択すること; をさらに含むようにプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 7プロセッサは、ユーザ選択に従って複数のプレビューを選択することが: メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成すること; をさらに含むようにプロセッサ実行可能な命令で構成されることを特徴とする請求項6に記載のワイヤレス通信デバイス。
- 8プロセッサは、メディアオブジェクトのプレビューを生成することが: プレビューのファイルサイズを計算し; ワイヤレス通信デバイスのディスプレイ上にプレビューのファイルサイズを表示すること; をさらに含むようにプロセッサ実行可能な命令で構成されることを特徴とする請求項7に記載のワイヤレス通信デバイス。
- 9プロセッサは、プレビューの最大伝送単位を識別する情報を表示することをさらに含む動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項8に記載のワイヤレス通信デバイス。
- 10プロセッサは、メディアサーバにメディアオブジェクトのメタデータを送信することをさらに含む動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 11プロセッサは: メディアオブジェクトのメタデータをメディアサーバから受信し; グループ通信チャネルを介してターゲットデバイスの各々にメタデータを送信すること; をさらに含む動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 12プロセッサは: ターゲットデバイスの各々がメディアサーバからメディアオブジェクトをダウンロードする時、メディアオブジェクトをダウンロードすることに関連するコストが課金されるユーザアカウントを識別する情報を送信すること; をさらに含む動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 13プロセッサは:ターゲットデバイスの各々にファイルフォーマット変換オプションを識別する情報を送信すること; をさらに含む動作を実行するためのプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 14グループ通信チャネルがそのフロアを含み、プロセッサは、フロアを有する時にのみ複数のプレビューを送信するようにプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 15グループ通信チャネルがそのフロアを含み、プロセッサは、デバイスがフロアを有することにかかわらず複数のプレビューを送信するようにプロセッサ実行可能な命令で構成されることを特徴とする請求項1に記載のワイヤレス通信デバイス。
- 16通信リンクを介してメディアオブジェクトのプレビューを送信するように構成されたワイヤレス通信デバイスであって、ワイヤレス通信デバイスは: 送信のためのメディアオブジェクトの選択を受信するための手段と; メディアサーバがターゲットデバイスにメディアオブジェクトを配信できるようにするフォーマットでメディアサーバにメディアオブジェクトを送信するための手段と; ユーザ選択に従って複数のプレビューを選択するための手段であって、プレビューは、メディアオブジェクトから導き出された生成されたオブジェクトとメディアオブジェクトから導き出されなかった独立したオブジェクトとから構成されるグループから選択されるアイテムを含む、選択するための手段と;メディアオブジェクトのファイルフォーマット変換オプションを識別する情報をメディアサーバから受信するための手段と; グループ通信チャネルを介して複数のターゲットデバイスの各々に複数のプレビューの1つとメディアサーバからメディアオブジェクトをダウンロードするためのリンクとを送信するための手段と; を含むことを特徴とするワイヤレス通信デバイス。
- 17メディアオブジェクトのユーザ定義メタデータを受信するための手段をさらに含むことを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 18メディアオブジェクトの複数のプレビューを選択するための手段は: 第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択するための手段と; 第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択するための手段と; グループ通信チャネルを介して第1のターゲットデバイスに第1のプレビューと、第2のターゲットデバイスに第2のプレビューとを送信するための手段と; をさらに含むことを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 19第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択するための手段は: エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択するための手段; をさらに含むことを特徴とする請求項18に記載のワイヤレス通信デバイス。
- 20第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択するための手段は: メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成するための手段; をさらに含むことを特徴とする請求項19に記載のワイヤレス通信デバイス。
- 21ユーザ選択に従って複数のプレビューを選択するための手段は: エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択するための手段; をさらに含むことを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 22ユーザ選択に従って複数のプレビューを選択するための手段は: メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成するための手段; をさらに含むことを特徴とする請求項21に記載のワイヤレス通信デバイス。
- 23メディアオブジェクトのプレビューを生成するための手段は: プレビューのファイルサイズを計算するための手段と; ワイヤレス通信デバイスのディスプレイ上にプレビューのファイルサイズを表示するための手段と; をさらに含むことを特徴とする請求項22に記載のワイヤレス通信デバイス。
- 24プレビューの最大伝送単位を識別する情報を表示するための手段をさらに含むことを特徴とする請求項23に記載のワイヤレス通信デバイス。
- 25メディアサーバにメディアオブジェクトのメタデータを送信するための手段をさらに含むことを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 26メディアオブジェクトのメタデータをメディアサーバから受信するための手段と; グループ通信チャネルを介してターゲットデバイスの各々にメタデータを送信するための手段と; をさらに含むことを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 27ターゲットデバイスの各々がメディアサーバからメディアオブジェクトをダウンロードする時、メディアオブジェクトをダウンロードすることに関連するコストが課金されるユーザアカウントを識別する情報を送信するための手段をさらに含むことを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 28ターゲットデバイスの各々にファイルフォーマット変換オプションを識別する情報を送信するための手段; をさらに含むことを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 29グループ通信チャネルがそのフロアを含み、複数のプレビューを送信するための手段は、フロアを有する時にのみプレビューを送信することを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 30グループ通信チャネルがそのフロアを含み、複数のプレビューを送信するための手段は、デバイスがフロアを有することにかかわらずプレビューを送信することを特徴とする請求項16に記載のワイヤレス通信デバイス。
- 31グループ通信チャネルを介して複数のターゲットデバイスにメディアオブジェクトのプレビューを送信するためのワイヤレス通信デバイス上で実行される方法であって: 送信のためのメディアオブジェクトの選択を受信するステップと; メディアサーバがターゲットデバイスにメディアオブジェクトを配信できるようにするフォーマットでメディアサーバにメディアオブジェクトを送信するステップと; ユーザ選択に従って複数のプレビューを選択するステップであって、プレビューは、メディアオブジェクトから導き出された生成されたオブジェクトとメディアオブジェクトから導き出されなかった独立したオブジェクトとから構成されるグループから選択されるアイテムを含む、選択するステップと;メディアオブジェクトのファイルフォーマット変換オプションを識別する情報をメディアサーバから受信するステップと; グループ通信チャネルを介して複数のターゲットデバイスの各々に複数のプレビューの1つとメディアサーバからメディアオブジェクトをダウンロードするためのリンクとを送信するステップと; を含むことを特徴とする方法。
- 32メディアオブジェクトのユーザ定義メタデータを受信するステップをさらに含むことを特徴とする請求項31に記載の方法。
- 33メディアオブジェクトの複数のプレビューを選択するステップは: 第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択するステップと; 第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択するステップと; グループ通信チャネルを介して第1のターゲットデバイスに第1のプレビューと、第2のターゲットデバイスに第2のプレビューとを送信するステップと; をさらに含むことを特徴とする請求項31に記載の方法。
- 34第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択するステップは、エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択するステップをさらに含むことを特徴とする請求項33に記載の方法。
- 35第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択するステップは、メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成するステップをさらに含むことを特徴とする請求項34に記載の方法。
- 36ユーザ選択に従って複数のプレビューを選択するステップは、エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択するステップをさらに含むことを特徴とする請求項31に記載の方法。
- 37ユーザ選択に従って複数のプレビューを選択するステップは: メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成するステップ; をさらに含むことを特徴とする請求項36に記載の方法。
- 38メディアオブジェクトのプレビューを生成するステップは: プレビューのファイルサイズを計算するステップと; ワイヤレス通信デバイスのディスプレイ上にプレビューのファイルサイズを表示するステップと; をさらに含むことを特徴とする請求項37に記載の方法。
- 39プレビューの最大伝送単位を識別する情報を表示するステップをさらに含むことを特徴とする請求項38に記載の方法。
- 40メディアサーバにメディアオブジェクトのメタデータを送信するステップをさらに含むことを特徴とする請求項31に記載の方法。
- 41メディアオブジェクトのメタデータをメディアサーバから受信するステップと; グループ通信チャネルを介してターゲットデバイスの各々にメタデータを送信するステップと; をさらに含むことを特徴とする請求項31に記載の方法。
- 42ターゲットデバイスの各々がメディアサーバからメディアオブジェクトをダウンロードする時、メディアオブジェクトをダウンロードすることに関連するコストが課金されるユーザアカウントを識別する情報を送信するステップをさらに含むことを特徴とする請求項31に記載の方法。
- 43ターゲットデバイスの各々にファイルフォーマット変換オプションを識別する情報を送信するステップ; をさらに含むことを特徴とする請求項31に記載の方法。
- 44フロアを有する時にのみ複数のプレビューを送信することを特徴とする請求項31に記載の方法。
- 45デバイスがフロアを有することにかかわらず複数のプレビューを送信することを特徴とする請求項31に記載の方法。
- 46送信のためのメディアオブジェクトの選択を受信し; メディアサーバがターゲットデバイスにメディアオブジェクトを配信できるようにするフォーマットでメディアサーバにメディアオブジェクトを送信し; ユーザ選択に従って複数のプレビューを選択し、プレビューは、メディアオブジェクトから導き出された生成されたオブジェクトとメディアオブジェクトから導き出されなかった独立したオブジェクトとから構成されるグループから選択されるアイテムを含み;メディアオブジェクトのファイルフォーマット変換オプションを識別する情報をメディアサーバから受信し; グループ通信チャネルを介して複数のターゲットデバイスの各々に複数のプレビューの1つとメディアサーバからメディアオブジェクトをダウンロードするためのリンクとを送信するステップと; を含む動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されるプロセッサ実行可能な命令を格納して有する非一時的なコンピュータ読取可能な媒体。
- 47プロセッサ実行可能な命令は、メディアオブジェクトのユーザ定義メタデータを受信するステップをさらに含む動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 48プロセッサ実行可能な命令は、メディアオブジェクトの複数のプレビューを選択することが: 第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択し; 第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択し; グループ通信チャネルを介して第1のターゲットデバイスに第1のプレビューと第2のターゲットデバイスに第2のプレビューとを送信すること; をさらに含むように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 49プロセッサ実行可能な命令は、第1のターゲットデバイスのユーザ選択に従って第1のプレビューを選択することが: エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択すること; をさらに含むように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項48に記載の非一時的なコンピュータ読取可能な媒体。
- 50プロセッサ実行可能な命令は、第2のターゲットデバイスのユーザ選択に従って第2のプレビューを選択することが: メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成すること; をさらに含むように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項49に記載の非一時的なコンピュータ読取可能な媒体。
- 51プロセッサ実行可能な命令は、ユーザ選択に従って複数のプレビューを選択することが: エモーティコン、一般的な画像、商標登録画像、オーディオファイル、およびムービーファイルから構成されるグループから選択されるメディアオブジェクトから導き出されなかった独立したオブジェクトを含むプレビューを選択すること; をさらに含むように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 52プロセッサ実行可能な命令は、ユーザ選択に従って複数のプレビューを選択することが: メディアオブジェクトの圧縮形式、メディアオブジェクトの低減されたサイズ形式、メディアオブジェクトのクリップ形式、メディアオブジェクトのクロップ形式、メディアオブジェクトの変換形式、メディアオブジェクトのダウンサンプル形式、およびメディアオブジェクトの修正形式から構成されるグループから選択されるメディアオブジェクトから導き出されたオブジェクトを含むプレビューを生成すること; をさらに含むように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項51に記載の非一時的なコンピュータ読取可能な媒体。
- 53プロセッサ実行可能な命令は: メディアオブジェクトのプレビューを生成することが: プレビューのファイルサイズを計算し; ワイヤレス通信デバイスのディスプレイ上にプレビューのファイルサイズを表示すること; をさらに含むように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項52に記載の非一時的なコンピュータ読取可能な媒体。
- 54プロセッサ実行可能な命令は、プレビューの最大伝送単位を識別する情報を表示することをさらに含む動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項53に記載の非一時的なコンピュータ読取可能な媒体。
- 55プロセッサ実行可能な命令は、メディアサーバにメディアオブジェクトのメタデータを送信することをさらに含む動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 56プロセッサ実行可能な命令は: メディアオブジェクトのメタデータをメディアサーバから受信し; グループ通信チャネルを介してターゲットデバイスの各々にメタデータを送信すること; をさらに含む動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 57プロセッサ実行可能な命令は: ターゲットデバイスの各々がメディアサーバからメディアオブジェクトをダウンロードする時、メディアオブジェクトをダウンロードすることに関連するコストが課金されるユーザアカウントを識別する情報を送信すること;をさらに含む動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 58プロセッサ実行可能な命令は:ターゲットデバイスの各々にファイルフォーマット変換オプションを識別する情報を送信すること; をさらに含む動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 59グループ通信チャネルがそのフロアを含み、プロセッサ実行可能な命令は、フロアを有する時にのみ複数のプレビューを送信するように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
- 60グループ通信チャネルがそのフロアを含み、プロセッサ実行可能な命令は、デバイスがフロアを有することにかかわらず複数のプレビューを送信するように動作をワイヤレス通信デバイスのプロセッサに実行させるように構成されることを特徴とする請求項46に記載の非一時的なコンピュータ読取可能な媒体。
Independent claims60
60 paragraphs, as filed
The present invention relates to a point-to-point or point-to-multipoint wireless communication system. More specifically, the present invention relates to systems and methods for sharing various forms of media between wireless communication devices.
In wireless communication devices such as cellular phones, PDAs, mini laptops, and advanced pagers, the device is generally long by bridging phone calls over the existing cellular telephone network and passing data packets over the network. Communicate over a distance. These wireless devices often have limited or significant data processing and computing power, and are therefore capable of transmitting and receiving software programs over the telephone network in addition to voice.
There are wireless communication services that provide one-to-one or one-to-many high-speed communication, commonly referred to as the "push-to-talk" (PTT) feature. A particular PTT group of recipient devices for a communication wireless device is usually set up by the carrier. A PTT communication connection is typically initiated by pressing a button once on a wireless device to activate a half-duplex link between the speaker and each member device of the group, and when the button is released, the device receives an incoming call. Can receive PTT transmissions. Because existing PTT systems have faster call setup times, for example, ideally in the range of 1 second, as opposed to cellular voice channels, which can take more than 5 seconds to establish. It has advantages over conventional cellular systems. In some configurations, the PTT speaker will have a "floor" that other group members cannot speak while the speaker is speaking. When the speaker releases the PTT button, other individual members of the group will be able to use their PTT button and have a floor. Generally, PTT systems use standard Voice Over Internet Protocol (VoIP) technology. Voice information is transmitted in digital form over an IP-based data network. In the PTT scenario, instead of using the standard cellular infrastructure, the call is formed by combining separate point-to-point connections between each IP endpoint on the server. When you start the PTT system, a call to the target device is generated. The caller's voice can be sent to the target handset through the carrier's network.
In existing PTT systems, member devices only communicate voice data between devices during a communication session. Due to the size of the data and the device resources needed to process the non-voice data, it is difficult to include other data in the group communication. Therefore, mobile devices that want to send non-voice data, such as media objects, should generally send non-voice data through a specific data channel established between the device and the wireless communication network, rather than the PTT channel. Must be.
Therefore, it would be advantageous to provide a system and method for a mobile device to send a preview of a media object to another mobile device during a PTT communication session. Therefore, the main subject of the present invention is such systems and methods.
<p num="0006"> Briefly, the present invention relates to a system and method for transmitting a preview of a shared media object in a group communication such as a push-to-talk or push-to-share communication session. Media objects can be stored on media servers and / or outbound communication devices. A preview of the media object can be generated by the outgoing device and sent during the PTT session. The preview can include metadata, which can be used by the recipient on the target mobile device to determine if the user wants to download the media object.</p>
<p num="0007"> Therefore, the present invention is advantageous because it provides a system and method that can be employed on a mobile device to send a preview of a media object to another device during a PTT session or other group communication session. This may allow a potential receiving wireless device to choose to stop receiving media or, in detail, prepare to receive media objects.</p><p num="0008"> The above is an overview and, of course, includes simplifications, generalizations and omissions of the details. Those skilled in the art will appreciate that the outline is merely exemplary and not limiting in any way.</p>
<figref num="1">It is a figure which shows the exemplary operational environment for carrying out the aspect of this disclosure.</figref><figref num="2">It is a figure which shows an exemplary wireless network in a common cellular communication configuration.</figref><figref num="3A">FIG. 5 illustrates an exemplary mobile computer platform and components that can be mobile devices.</figref><figref num="3B">FIG. 3A illustrates an exemplary software layer residing on the computer platform.</figref><figref num="4">It is a figure which shows an exemplary operation procedure for generating a preview of a media object and sending it to a target device.</figref><figref num="5">It is a figure which shows the exemplary operation procedure for receiving the preview of a media object.</figref><figref num="6">FIG. 5 illustrates an exemplary operating procedure for enabling the transfer of a preview of a media object between a transmitting mobile device and a receiving mobile device.</figref><figref num="7">It is a figure which shows an exemplary call flow for establishing a push-to-talk session.</figref><figref num="8">FIG. 6 is an exemplary call flow diagram for an embodiment of a method of transmitting a preview of a media object during a floor shared between making a call and transmitting a preview of the media object.</figref><figref num="9">It is a figure which shows the exemplary call flow diagram of one Embodiment of the method of transmitting the preview of the media object on the floor different from the PTT client.</figref>
In this disclosure, the terms "communication device," "wireless device," "wireless communication device," "PTT communication device," "handheld device," "mobile device," and "handset" are used interchangeably. .. The terms "call" and "communication" are also used interchangeably. The term "exemplary" means that the disclosed element or embodiment is merely an example and does not indicate any user preference. The term "group communication" includes one-to-one or one-to-many, half-duplex communication, or full-duplex communication operating in half-duplex mode. The term "floor" is as understood in the field of PTT or half-duplex group communication technology, i.e. voice on a forward link while other devices in the group can only receive voice / data. / A device capable of transmitting data. Moreover, similar numbers throughout the drawings refer to similar elements, and unless otherwise specified herein, the articles "a" and "the" include multiple references.
As used throughout this disclosure, the term "circuit" can include dedicated computer circuits that implement logic that can operate to perform a function. In another example, the term "circuit" can include a general purpose processing unit that can be configured by software instructions that perform logic that can operate to perform a function. In this example, the implementer can write source code that implements logic that can be compiled into machine-readable code. The compiled code can then be processed by the general purpose processing unit, thereby converting the general purpose processing unit into a special purpose processor. Current technology has evolved to the extent that there is little difference between hardware, software, and combinations of hardware and software, and that hardware-to-software choice is a design choice left to the implementer. Those skilled in the art will understand. More specifically, one of ordinary skill in the art will appreciate that a software process can be converted into an equivalent hardware circuit, and a hardware circuit can be converted into an equivalent software process in its own right.
Figure 1 shows a preview of media objects and media objects on wireless network 20 among one or more wireless communication devices in PTT group 12, such as wireless phone 14, smart pager 16, and personal digital assistant (PDA) 18. An exemplary embodiment of the system 10 for sharing with other wireless communication devices is shown. In system 10, each wireless communication device 14, 16 and 18 can selectively communicate directly with the target set of one or more of the other wireless communication devices on the wireless communication network 20. Is. For example, the target set of mobile phone 14 can be all devices in communication group 12, or a subset thereof, such as pagers 16 and PDA18.
In this embodiment, the wireless communication device (such as mobile phone 14) may send the flag to at least the group communication computer device located on the server-side LAN 30 on the wireless network 20 and here indicated as server 32. it can. The flag can be used by the server in this example to determine that the wireless device is on the wireless network 20, i.e. accessible. The group communication computer device 32 can share this information with the set of target wireless communication devices specified by the first wireless communication device, or it resides on the server-side LAN 30 or wirelessly. It can also be shared with other computer devices accessible on network 20. The group communication computer device 32 can have an attached or accessible database 34 that stores the group identification data of the wireless device. The media server 36 further includes a circuit for a file management server that may exist on the server-side LAN 30. Please understand that the number of computer components resident on the server-side LAN30, wireless network 20, or the entire Internet is not limited.
Group communication, such as PTT communication, can be established via a half-duplex channel between the wireless communication devices 14, 16, 18 communicating and one or more other wireless communication devices in the target set. Also, if at least one of the wireless communication devices in the target set notifies the group communication server 32 of their presence on the wireless network 20, the group communication server 32 attempts to bridge the requested direct communication with the target set. You can try.
The group communication server 32 also communicates directly to the target set 12 when all (or at least one) wireless communication devices in the target set have not notified the group communication server 32 of their presence on the wireless network 20. Can notify wireless communication devices 14, 16 and 18 that they cannot bridge. Further, although the group communication server 32 is shown here as having an ancillary media server 34 of group identification data, the group communication computer device 32 can have group identification information data resident on it. All storage functions described herein can be performed.
In overview, the system 10 can include at least one wireless communication device, such as a mobile phone 14, which can be a member of the communication group 12 of the wireless communication device. The wireless communication devices, in this example, can be configured to communicate with each other or as a group on the wireless communication network 20. In addition, at least one of the wireless communication devices can be configured to selectively send a preview of the media object to other members of communication group 12. At least one group communication server 32 is configured to store information about the communication group 12 on the wireless communication network 20, which information includes identification information of a particular member wireless communication device of one or more communication groups. .. The group communication server 32 is further configured to selectively receive a preview of the media object from the transmitting wireless communication device of the communication group 12, such as the mobile phone 14, and later download the media object.
The system 10 may further include a media server 36 communicating with the group communication server 32, so that the group communication server 32 sends media objects to the media server 36, as further described herein. It is composed. The media server 36 receives a media object from a wireless communication device (such as a mobile phone 14), and a member of the communication group 12 to which the preview is sent accesses the media object stored on the wireless communication network 20. Can be configured to selectively enable
For example, in embodiments of the present disclosure, media objects are, but are not limited to, images in JPEG, TIF, etc., audio files such as MP3, MP4, WAV, documents, schedules, calendar events, emails, spreadsheets, ( It can include drawings (such as Visio drawings or other CAD / CAM drawings) and / or presentations. Media objects can further include streaming media such as multimedia applications (Powerpoint, MOV files, etc.). The media object can also be a half-duplex video conference between members of a communications group, where the speaker's image is broadcast to other group members in real time or with a delay.
The size of the media object file can be very large, and the system 10 is in communication group 12 because the transmission of the media is potentially delayed or the receiving wireless communication device is unable to handle the transmitted media. Media objects can be stored using Media Server 36 (or File Management Server) so that target members can selectively access stored media without interrupting other PTT communications. it can. The media server 36 can be configured to send a preview of the media object to each of the member wireless devices when establishing a communication link with each of the member wireless devices of communication group 12. Alternatively, in one embodiment, if the media object is stored on the media server 36, the media server 36 can be configured to send hyperlinks to the outgoing device or other member wireless communication device of the communication group 12. The hyperlink can, in this example, provide a link to the group media stored on the media server 36. When the preview of the media object is received by at least one of the member wireless devices in communication group 12, the group communication server 32 means that at least one member wireless communication device in communication group 12 has received the media object. An acknowledgment can be sent to wireless communication devices 14, 16 and 18.
When the wireless communication devices 14, 16 and 18 request the transmission of the media object, the communication group identification data, for example, the target list can be transmitted to the group communication server 32, and thus the media server 36 is described herein. As further discussed in the book, media objects can be configured to send or store media objects to member wireless communication devices identified in the communication group identification data based on various criteria. Alternatively, the wireless communication devices 14, 16 and 18 can request the group communication computer device 32 for member data of the communication group 12 before transmitting the media object, and the group communication server 32 may request one or more member data. Addresses or communication group addresses can be sent to wireless communication devices 14, 16 and 18. In one embodiment, the communication group computer device 32 can filter available potential communication groups based on the capabilities of the communication group member devices for the received media object.
As further described herein, wireless communication devices 14, 16 and 18 are involved in group communication with member wireless communication devices of communication group 12 and during group communication in the same communication session or independently. You can send media objects. Alternatively, the media object can be transmitted independently of the group communication session, with or without alerting the target device to indicate that the media has been transmitted.
Next, with reference to FIG. 2, an exemplary wireless network in a common cellular communication configuration is shown. The wireless network can include, in this example, a set of group communication servers 32 that control communication between the wireless communication devices of the configured group members (devices 70, 72, 74, 76) in the PTT system. This wireless network is exemplary only, with remote modules between and within each other and / or, but not limited to, between and / or between the components of the wireless network 20 including the wireless network carrier and / or server. It can include any system for wireless communication. A series of group communication servers 32 are connected to the group communication server LAN50. The wireless telephone can request a packet data session from the group communication server 32 using the data service option.
Continuing with FIG. 2, the group communication server 32 can connect to a packet data service node (PDSN) of a wireless service provider, such as the PDSN 52, which is shown here to reside on the carrier network 54. Each PDSN 52 can interface with the base station controller 64 of the base station 60 via the packet control function (PCF) 62. PCF62 can be located at base station 60. The carrier network 54 can control the messages sent (generally in the form of data packets) to the messaging service controller ("MSC") 58. Carrier network 30 is, in this example, network, internet and / or POTS ("plain ordinary telephone". It can communicate with MSC32 by system) "). Generally, the network or internet connection between carrier network 54 and MSC58 transfers data, and POTS transfers voice information. The MSC58 can connect to one or more base stations 60. In a manner similar to carrier networks, MSC58s are generally connected to branch-to-source (BTS) 66 by networks for data transfer and / or both the Internet and POTS for voice information. .. The BTS66 will eventually broadcast messages wirelessly to wireless devices such as cellular phones 70, 72, 74, 76 by short message service ("SMS"), or other wireless methods known in the art. And receive messages from wireless devices. It should also be noted that carrier boundaries and / or PTT operator network boundaries do not deter or prohibit data sharing, as described herein.
Cellular phones and mobile communication devices, such as wireless phones 14, are being manufactured with increased computing power and are becoming similar to personal computers and handheld PDAs. These "smart" cellular phones allow software developers to create software applications that are downloadable and runnable on the processor of wireless devices. Wireless devices such as the Cellular Phone 14 can download many types of applications such as web pages, applets, MIDlets, games and data. In a wireless device with communication group 12 specified (as shown in FIG. 1 and the like), the wireless communication device can connect directly with other members of the set and can participate in voice and data communication. However, such direct communication takes place through or under the control of the group communication computer device 32. Although not all data packets on the device necessarily travel through the communication server 32 itself, the communication server 32 generally recognizes and / or can retrieve the identity of the members of the communication group. Or, because it is the only server-side 30 component that can direct the identity of a member of communication group 12 to another computer device, it must ultimately be able to control communication.
Next, referring to FIG. 3, an exemplary wireless communication device, which can be a mobile phone 14 with a PTT button 78 that opens direct communication to the target device, is shown. The wireless device 14 is also shown as having a graphics display 80. The wireless device 14 may include a computer platform 82 capable of processing voice and data packets and receiving and executing software applications transmitted over the wireless network 20. Computer platform 82 includes application specific integrated circuits ("ASIC") 84, or other processors, microprocessors, logic circuits, programmable gate arrays, or other data processing devices among its components. The ASIC84 is installed at the time of manufacture of the wireless device and is usually not upgradeable. The ASIC84 or other processor runs the application programming interface ("API") layer 86, which contains the resident application environment and can contain the operating system loaded on the ASIC84. The resident application environment interfaces with any resident program in memory 88 of the wireless device. An example of a resident application environment is the "Binary Runtime Environment for Wireless" (BREW) software for wireless device platforms developed by QUALCOMM®.
As shown here, the wireless device 17 can be a mobile phone 14 with a graphic display 80, but with a personal digital assistant (PDA), a pager with a graphic display 80, and even a wireless communication portal. It can also be any wireless device with a computer platform 82 known in the art, such as a separate computer platform 82 that may have a wired connection to a network or the Internet. In addition, memory 88 can 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 82 may also include a local database 90 for storing software applications that are not actively used in memory 88. The local database 90 generally consists of one or more flash memory cells, but any secondary known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or soft or hard disk. Or it can be a tertiary storage device. The graphic display 80 is to present information about media objects as well as information about ongoing group calls to include file previews to generate previews, as more fully described herein. Can be done.
In this embodiment, the computer platform 82 can also include a direct communication interface 92 capable of opening a direct communication channel. The direct communication interface 92 can also be part of a standard communication interface for wireless devices that normally carry voice and data transmitted between wireless devices. The direct communication interface 92 is generally composed of hardware known in the art.
Continuing the description of FIGS. 3A-3B, further illustrated is an embodiment of a software layer of a group application client that can include, but is not limited to, PTT functionality and media object functionality. In this embodiment, the computer platform 82 in a mobile device environment is a series of mobile modems (MSM) 100 developed by QUALCOMM® and deployed on Advanced Mobile Subscriber Software (AMSS) 102. Software "layers" can be included. In this example, the underlying MSM chipsets are CDMA2000 1X and CDMA2000. A software protocol stack can be implemented for the entire suite of CDMA communication technologies, including 1xEV-DO. In this example, this embodiment can be configured to support mobile operating system layer 104, which is also BREW®, also developed by QUALCOMM®. Mobile operating system layer 104 can provide an application programming interface for chip or device-specific operation while providing an isolation layer that eliminates direct contact between AMSS 102 and OEM software on computer platforms. Mobile operating system layer 104 can enable application development that uses the capabilities of mobile devices without the need to rewrite applications each time a new release of device-specific software is released.
In this example, the mobile operating system 104 can include a PTT client 108 configured to provide access to PTT services through the external interface shown here in the PTT-aware UI 106. The PTT client 108 can include all the features needed to enable applications for the mobile operating system 104, such as the media client 110. In this embodiment, the PTT client 108 maintains access to the PTT service, responds to communication requests, processes all PTT-aware mobile operating system application requests for the PTT service, and makes all outgoing PTT requests. It can process, collect and package vocoder packets for outgoing PTT talk spurts, and parse packets for vocoder data for finished PTT talk spurts.
In this example, Media Client 110 can be a mobile operating system-based application that extends PTT services for access to media types other than traditional half-duplex voice communication (VoIP-PTT media). Media Client 110 can provide access to media services through external interfaces such as the Media Recognition API, which is an application that can be fully deployed as a mobile operating system based application or used in combination with the AMSS102 interface. it can. The group media recognition UI can respond to user requests to media services by calling the appropriate APIs, such as APIs from other resident PTTs and group media applications 112. The media client 110 can process the request from the user and notify the user of the result of the media request for the group. The media client 110 can be further configured to handle incoming call notifications indicating that there are media objects to be downloaded from the file management server (data store 36). For example, the media client 110 can be configured to download media objects immediately in one embodiment, or the media client 110 in another embodiment can be configured for a predetermined time period, eg, every day at 10:00 pm. Can be configured to download media objects in minutes, or can be configured to prompt the user via PTT UI 106 to determine if and / or when to download the file. ..
Next, with reference to FIG. 4, an exemplary operating procedure for generating a preview of a media object during a push-to-talk chat session and sending it to the target mobile device 20 is shown. In this exemplary embodiment, operation 400 initiates an operating procedure, indicating that operation 402 selects an option to send a preview of the media object from user interface 80 on device 14. The circuitry of device 14 can be configured by the software of media client 110 so that the user can generate a preview of the media object when the user selects such an option. The preview, in the exemplary embodiments of the disclosure, generally provides sufficient information to allow the recipient to make an informed decision as to whether the recipient wishes to download the media object. Anything you give to the recipient is possible. When the device circuitry is configured by the media client 110, the user can select media objects to share with one or more target devices that can be members of group 12, for example device 20.
Media objects can include, but are not limited to, documents, audio files, digital images, video clips, or any other type of digital media in the exemplary embodiments of the present disclosure. In an exemplary embodiment, the media object can be stored, for example, in the local database 90 and / or media server 36 of FIG. For example, in embodiments of the present disclosure, a user can obtain an account with a service provider that provides access to online storage, such as a media server 36. The user can create an account and upload media objects to the media server 36 on an hourly basis. The media server 36 can generate a link to a media object, eg, a hyperlink, in this example and send the link back to the mobile device 14. The circuit of device 14 in this exemplary embodiment allows the user to scroll through media objects to see which media objects have been uploaded to the media server 36 and which media objects are stored in the local database 90. Can be configured to allow
Continuing with the description of FIG. 4, in operation 404, a preview of the media object is generated. For example, the circuit of device 14 can be configured, for example, by the media client 110 to launch a preview generation option. In an exemplary embodiment, the menu compresses the media object that should form the preview, clips the media object that should form the preview, changes the media object that should form the preview, and / or acts as a preview. It can include an option to select the icon to be. This list of preview generation options is not exhaustive and options that allow the user to generate previews of media objects are contemplated by the present disclosure.
In embodiments of the present disclosure, options for compressing media objects to form a preview can be rendered on the display of device 14 and selected by the user. In this example, a compressed copy of the media object can act as a preview of the media object. For example, the media object can, in one embodiment, be a digital photo having a set of pixels. The user can select compression options and also reduce the resolution of the digital image, for example, changing the resolution to include fewer pixels, thereby in the push-to-talk communication channel. You can create a preview of the picture that can fit within the available bandwidth requirements.
In another exemplary embodiment, the menu may include an option to select a portion of the media object as a preview. In this exemplary embodiment, the media object can include documents, presentations, spreadsheets, images, and the like. The media client 110 can be configured to allow the user to draw a bounding box on a portion of a media object and / or select a paragraph, page, or slide and use that selected portion as a preview. In other exemplary embodiments, such as video or audio media objects, the media client 110 can be configured to allow the user to select a time range in which the preview should work, eg, the user is in the preview. You can choose 30 seconds for the song to work on or 10 seconds for the video.
The media client 110, in this example and other exemplary embodiments, may include a menu option for selecting an icon to represent a media object. For example, in one embodiment an emoticon such as a smiley face can be used to represent a media object, or in another embodiment a small general image such as a flower, or an image of a sporting event, on the device 14. Can be stored in memory. When the user selects a media object, he can scroll through the list of images that can be used as a preview and select one. For example, if the media object is a movie, the user can select the image of the person watching the movie that should represent the media object.
For example, a trademarked icon that can be used as a preview in an exemplary embodiment may be provided by the company. These trademarked icons can be used as a preview of the media object and can also act as a source identifier for the media object. For example, a user may wish to submit a preview of a patent application drafted by a patent attorney from a particular law firm. The user can select a trademarked icon placed on the letterhead of the office by the law firm, which should act as a preview of the patent application. In this example, the preview can indicate that the media object came from a law firm. Another example could include a video of a baseball player hitting a home run. In this example, the user can select an icon such as a player's team logo.
With reference to operation 406, the user can select a preview option after scrolling through the options and a preview can be generated, but in other exemplary embodiments, multiple previews of different types can be generated. , The user can select a preview that is considered to carry the "correct" amount of information. The mobile device 14 allows the user to select a number of different preview options and view and / or listen to them in order to determine which preview option the user wants to select as the preview. It can be configured to display the get menu. In certain examples, the user decides to send a digital image to a friend and chooses options to compress the image, such as deleting pixels, cropping the image, converting the image to black and white, and so on. can do. The user can scroll through all three selections to determine which one the user wants to use as a preview and select the desired selection.
Continuing with the description of FIG. 4, the exemplary operation 408, in one exemplary embodiment, is in the preview, eg, in the header of the preview, and / or in the body of the message containing the preview. Indicates that metadata can be added. In one embodiment, metadata can be used to provide additional information to the user of target device 20. Metadata, in this example, can include information that describes the media object, or other information that describes information related to the media object. Metadata can be obtained and generated by various metadata sources such as user, device 14, media server 36 and target device 20. Each metadata source can add metadata to the preview to give the target 20 users enough information to determine if the user wants to download the media object. For example, the user can generate metadata for a preview of a media object. The device 14 can include, in this example, a keypad and / or a keyboard that can operate to receive text. The user can access the menu from the media client 110 and, for example, add text to the media object that can describe the media object. In another embodiment, the menu can include predefined text options that can be selected by the user and added to the preview.
In another exemplary embodiment, the user may choose the option that users of the target device 20 will be charged for their accounts if they download the media objects. For example, a service provider can charge a fee for downloading a media object, but can allow users to receive a preview for free. In this example, a user who wishes to share a media object with the target mobile device 20 can select an option on the media client that indicates that the user pays for the download. In this example, selection information can be stored along with other metadata in the preview header and / or in the body of the message containing the media object.
The circuit of device 14 can be configured by the media client 110 to inform the user, for example, to help the user generate a preview. For example, in one embodiment, the PTT client 108 can identify a size limit for the preview, eg, the maximum transmission unit, and information that identifies the current size of the preview while the user selects the preview. Can be overlaid on the display 80. For example, the user may wish to crop the image as a preview. In this example, the media client 110 can be configured to receive information from the PTT client 108 that identifies the maximum size limit for transmitting data over the push-to-talk link. This information can be overlaid on the preview generation screen along with the current size of the preview. The user interface can generate a bounding box on an image that can be reduced in size by the user. When the user reduces the size of the bounding box, the media client 110 can be configured to calculate the current size of the information in the bounding box. In this example, the user can use that information to determine how much the user must crop the image. Similar techniques can be applied to music, video, and documents. More specifically, the media client 110 can be configured to allow the user to select a portion of a video clip, which may display information on the screen indicating whether the clip is too large. In the example document, the user can generate a bounding box on a part of the document, the user can select a range of text, and the information on the display is that part of the document too large? Information can be given to indicate whether or not.
In another exemplary embodiment, the mobile device 14 may include a circuit configured to generate metadata and add it to the preview. For example, in one exemplary embodiment, device 14 is a device identifier, such as a media object's file extension, a link to a media object, eg, a file path to an object on the device, and an identifier used by the network. Information such as the file size of the media object, the date the media object was modified and / or created, the identity of the entity that created the media object, such as the name of the company or user who created the media object, and the copyright information of the media object. And / or can be obtained. In one exemplary embodiment, this information is from the media server 36, such as a hyperlink to the media object, the file size of the media object stored on the media server 36, the price associated with downloading the media object from the server, and so on. Can be merged with the information obtained. For example, in one embodiment, the media server 36 can store a media object and determine the price for downloading the media object based on the size of the object. This information may be sent to device 14 and added to the preview. The preview may be sent to the target device 20 and its information may be displayed. In this example, the target device 20 can obtain pricing information before attempting to download the media object from the media server 36.
In the same embodiment, as well as in other embodiments, the media server 36 sends additional metadata that can be sent to device 14 and sent to target 20 with a preview, or to target 20 in response to a request from target 20. Additional metadata that can be generated can be generated. In this exemplary embodiment, the metadata can include information that identifies file format conversion options for media objects. The media server 36 can include a database management program and a circuit for discovering the file extension of the stored media object, for example, a processor configured by the program. For example, in one embodiment, the media object can have specific file types such as .mov, .jpeg, .tiff, .pdf, .ppt, .doc, .mp3, .mpeg. In an exemplary embodiment of the present disclosure, when a media object is stored by the communication server 32, is it possible to determine that the file extension is for the media object and convert the media object from one file type to another? The circuit of the media server 36 can be configured to determine whether or not. In one embodiment, this information may be returned to the mobile device 14, for example, in a message confirming the success of the storage operation. That information may be stored in the header of the media object along with other metadata. In certain examples, the media object can be a video with the .mov file extension. In this example, when a video is uploaded to the media server 36, the server's circuitry can be configured to determine if the file can be converted to another format. The table stored in memory is accessible and the circuit can search for .mov. In this example, the media server 36 puts .mov files in .mpeg, .divx, .. It can contain circuits for converting to mpg, or another movie file type. The conversion circuit can be configured in this example to determine that the conversion circuit can convert the video to various formats and send a list of conversion options to the mobile device 14, where the information is , Can be stored in the header of a media object, or in the body of a message containing a media object. This information is then sent to Target 20 during the preview, and if the user wishes to copy the media object, the preview user may be presented with information indicating that the copy can be downloaded in .mpg format instead of .mov format.
Next, referring to operation 410, when a preview of the media object is generated, the preview is sent to the target device 20 or a plurality of target devices via the push-to-talk communication channel. For example, if the user decides to send a preview of the media object to the target device 20, the user can establish a push-to-talk session with the target device 20 and send the preview. If the user is already involved in a push-to-talk session, the user can send a preview of the media object to the target device 20 during the session when the user has a floor.
Next, referring to FIG. 5, the operation procedure related to receiving the media object from the device 14 is shown. Operation 500 initiates the operating procedure, and operation 502 indicates that the target device 20 can enter a push-to-talk communication session with device 14. For example, the user of target device 20 can receive a signal from device 14 (via one or more servers in the data network) indicating that the user wants to start a PTT session with them. .. In one embodiment, the user of target device 20 accepts the communication and initiates a conversation with the user of device 14 (depending on whether the user of device 14 sent a preview before initiating the conversation). And / or you can receive a preview of the media object. As indicated by operation 504, the target device 20 provides sufficient information to allow the user of the target device 20 to make an informed decision as to whether or not the user of the target device 20 wishes to download the media object. You can receive a preview that you can give. As described above, the preview can include, but is not limited to, a compressed version of the media object, a portion of the media object, and / or an icon.
When the preview is received on the target device 20, in one embodiment, the metadata can be generated from any metadata associated with the preview. For example, the media client 110-T of target 20 can generate metadata from the metadata received from the outgoing device 14, the media server 36, and the user of device 14. For example, the target device 20 can include information that identifies the data plan that the user has subscribed to. The data plan, in this example, can include information indicating whether the user has subscribed to a plan that allows unlimited PTT media object downloads. When the target device 20 receives the preview and the preview is displayed, the user may be presented with information indicating how much it will cost to download. Further, in one embodiment, the target device 20 can include information indicating how much storage is available to store the media objects. The information that defines the size of the media object and the available storage can be used to calculate how much remaining storage is available for the target device 20 if the media object is downloaded. In the same embodiment, or in other embodiments, the target device 20 takes information indicating how large the media object is and the available bandwidth to allow the target device 20 to download the object. It is possible to generate an estimated amount of time that will be. For example, when a preview is received, the target device 20 can use the information that identifies the location of the media server 36 to ping the location of the media server 36 to determine the latency. You can then use the latency to determine how long it will take to download the media object, and use this information with other metadata.
Upon receiving the preview and metadata, the preview and metadata are displayed on the screen of the target device 20 as indicated by operation 506. A preview can be displayed on the user interface 80 of the target device 20, and metadata can be organized and displayed. For example, the metadata can be organized into various tabs that can be selected by the user, such as "conversion information", "download information", and / or "media object information". Each tab can contain metadata from various sources in this exemplary embodiment, for example, media object information gives context to size, author name, information about modified data, and preview. It can include information generated by the device 14, such as text generated by the user of the device 14, such as the subject.
If the user on target device 20 decides to download the media object, select the link during preview or embedded in the body of the message containing the preview to download the media object, as indicated by operation 508. be able to. For example, in one embodiment, the link can be a hyperlink to a media object stored on the media server 36, or in another example, the link can be a link to a media object stored on device 14. can do. In one example, the media server 36 can store a copy of the media object and send a hyperlink to device 14. When device 14 sends a preview to target device 20, the preview can contain hyperlinks. In this example, the user of target device 20 can "click" (or "select") the hyperlink and the download process can be initiated. In another embodiment, the link may be associated with device 14. For example, media objects may not be stored on the media server 36 when the preview is sent to the target. In this example, the link can include information such as the device identifier and the filename of the media object. The user of the target device 20 can click on the link to connect to the media server 36. The media server 36 can be configured to determine that the link contains the device 14 identifier and file path. The media server 36 can locate the device 14 and request a media object. When the media object is uploaded to the media server 36, the media server can download the media object to the target device.
Next, referring to FIG. 6, an exemplary operating procedure related to sending a preview to the target mobile device 20 is shown. For example, a service provider system can include a media server 36 and a dispatch call handler (DCH) that can allow the transfer of media objects from the source to the target. For example, operation 600 initiates the procedure and operation 602 indicates that the DCH can receive a call setup request message indicating that the user of device 14 wants to establish a push-to-talk session. Operation 604 indicates that network resources can be allocated to handle the request. In one exemplary embodiment, the DCH can receive a preview by querying either the media client 110 on target device 20 or a database of information that identifies the functionality of target device 20. It can be configured to determine that. In the same embodiment, or in other embodiments, the DCH comprises a circuit for retrieving an address in the database of accounts, where target 20 receives a preview and / or receives a media object via a PTT link. It can be configured to determine if you are eligible. For example, in one embodiment, target 20 may not pay the monthly fee associated with receiving a media object over a PTT link. For example, if target 20 is not qualified, for example, the user does not subscribe to a service that supports media objects, or device 20 is not able to receive such media objects, it signals the SMS server. Is sent, and a text message indicating that the user is unable to receive a preview of the media object is generated and can be sent to target 20.
Continuing with the description of FIG. 6, operation 606 indicates that the DCH can receive the preview from the source device 14 and transfer the preview to the target device 20. In this example, the data over the PTT channel can be routed through the DCH, and the DCH computer system may include a circuit that parses the preview and adds metadata to the preview as shown by operation 608. it can. For example, you can add metadata to the preview, such as information about the location of media objects on the media server 36 and / or information in the business rules established by the service provider. For example, there may be a business rule that states that all media objects downloaded on a given date are free. In this example, you can add information to the preview to indicate that the media object will be free to download if that date matches the date in the business rule. In another example, the ad can be added to the preview, for example, in the body of the message containing the preview, or the ad can be sent in a separate package prior to the preview. In this example, the circuit of target 20 can be configured to display an ad before giving the user access to the preview. In this example, the target 20 user may not have paid for receiving the media object, but may have agreed to get a free media object to view the ad. Continuing the description, as indicated by operation 610, when metadata is added to the preview, the preview is sent to the target via the transmit and receive base stations.
Next, with reference to FIG. 7, an exemplary call flow diagram for establishing a push-to-talk session is shown. For example, the user of device 14 can determine that the user wants to be involved in a PTT conversation with the user of target device 20 and requests a push-to-talk session. A PTT session can be established by the PTT client 108 selecting a contact from the address book and pressing the PTT button 78 in FIG. In one embodiment, the PTT client 108 can receive selection instructions and send a call setup request message to DCH134. The call setup request can include, for example, the address of the target device, instructions that the media object should be shared, and information that identifies the media server 36 that stores the media for the mobile device 14. Call setup requests can also be sent with DataOverSignaling access channel messages. In one exemplary embodiment, the DCH134 locates a target, applies call restrictions, selects a vocoder and location, and / or stores media objects uploaded during a PTT session. Can be configured to perform PTT call setup functions, including allocating a media server 36 to handle. The media PTT session can then be notified to the media server 36 that the media PTT session has been created and that the identification information of both the calling device and the target device has been created. In this example, the DCH 134 determines if the mobile device 14 is capable of sending / receiving media objects and / or if the target device 20 is allowed to send / receive media objects. It can include circuits that can operate as such. For example, both devices can send / receive media objects and the target is a PTT session.
Next, with reference to FIG. 8, an exemplary call flow diagram for sending a preview of a media object during the floor shared between making a call and sending a preview of the media object is shown. As shown in FIG. 8, in the embodiments of the present disclosure, a PTT session can be established and media objects can be uploaded to the media server 36. However, in this exemplary flow diagram, media objects may be stored by the media server 36 after the call is initiated or terminated. For example, during a conversation, the caller may want to take a picture of something or think about and share a media object stored on device 14 that is relevant to the discussion. In one exemplary embodiment, the media object can then be uploaded to the media server 36 via the data channel, which can generate a hyperlink to the media object.
Continuing with the description of FIG. 8, the user of the calling device 14 can then request the PTT call to send a preview of the media object using the same floor mechanism as the PTT call. That is, in this example, a preview of the media object can be transmitted with the voice during the PTT talk spurt. In this exemplary embodiment, the media client 110 can transmit data at the same time as requesting permission to make a call. In this scenario, the user may be participating in a PTT call, and the user can perform the function of sharing data to the media client 110 during subsequent talk bursts from the user. That is, in this example, there is only a single floor control mechanism used for both PTT calls and sharing of media previews. The media client 110 can request the PTT client 108 to add a preview of the media object to the existing PTT call in this example. The media addition request can include an instruction that the data should be shared using the same floor control mechanism as the PTT client 110. The PTT client 110 can request that the media server 36 add a new media type to an existing call in this example. The media server 36 verifies that the target mobile device 20 can support the new media type by contacting the media client 110-T, for example, and tells the mobile device 14 that the new media type has been added to the PTT call. You can notify. After the new media type is successfully added to the PTT call, the user can send a preview of the media object at the same time as requesting permission to make a call.
In one exemplary embodiment, the media client 110 can send a preview to the target device 20 via a push-to-talk channel. In this example, the media server 36 can be configured to receive the preview, add additional metadata to the preview, and send the preview to the target device. For example, in embodiments of the present disclosure, device 14 cannot upload media objects to a media server until after a preview has been generated and sent to the target. In this example, when the media server 36 receives the preview, it can store information that identifies the media object to which the preview is associated and the device identifier of the outgoing device 14. The media server 36 can then request the outgoing device 14 to make a copy of the media object for storage and upload the media object over the data channel. In an alternative embodiment, the user of the outgoing device 14 can upload a copy of the media object over the data channel after or during the PTT.
Next, with reference to FIG. 9, an exemplary call flow diagram for sending a preview of the media object on a different floor than the PTT client on the target mobile device 402 is shown. In this exemplary embodiment, the media client 110 can be configured to request that a preview be sent to the target 20 using a floor control mechanism that is different from the PTT call. In this example, the preview of the media object is transmitted over the media PTT channel independently of the voice data. For example, in one embodiment, the user may request permission to transmit data whenever there is data ready to be shared with the target mobile device 20. In this scenario, the user of mobile device 14 can perform a function on media client 110 to participate in a PTT call and instruct media client 110 to share a preview with target mobile device 20. In this example, the media client 110 should share its data using a floor control mechanism that is separate from the PTT call, that is, a floor control mechanism that is independent of the floor control mechanism used for the PTT call. It can be configured to determine that it is a kimono and send a request to the PTT client 108 to add a new media type to an existing PTT call. The media addition request can include an instruction that the data should be shared using a floor control mechanism different from the PTT call. The PTT client 108 can send a request to the media server 36 to add a new media type to an existing call in this example. The media server 36 can be configured to verify that one or more of the call participants can support the new media type, and then the media server 140 gives a notification that the new media type has been added to the call. Can be sent to call participants. In this embodiment, the notification to the call participant is a preview of the media object. In addition to the new destination port number on the media server 36 for communication, it can include a floor identifier for a separate media floor. PTT client 108-R on target device 20 assigns a new media port for sending or receiving media for groups, sends the new port identifier to media server 36 during acknowledgment, and finally media client 110-R. Media can be received at.
After the new media type is successfully added to the PTT call, the user can request permission to send a preview of the media object. The media client 110 can be configured to notify the PTT client 108 that a media transmission request for a group has been received. The PTT client 108 can be configured to request the media server 36 for permission to send media for groups. The PTT request from the PTT client 108 can include a floor identifier assigned to the group media floor. The media server 36 can verify that the data floor is available before granting the floor request. The PTT client 108 can then notify the media client 110 that the floor request has been granted.
The embodiments for carrying out the above invention have described various embodiments of the system and / or process through examples and / or operating diagrams. As long as such a block diagram and / or example contains one or more functions and / or operations, each function and / or operation within such a block diagram or example contains a wide range of hardware, software, etc. Those skilled in the art will appreciate that they can be implemented individually and / or collectively, with firmware, or almost any combination thereof.
In view of the methods that can be performed on mobile devices and other computer platforms, this method can be performed by a program residing on computer readable media accordingly, and the program will perform the steps of this method on the computer platform. Instruct a mobile device or other computer device that has. The computer-readable medium can be the memory of the server or may be in a connectable database. In addition, computer readable media can be found in secondary storage media that can be loaded onto the computer platform of communication devices, such as magnetic disks or tapes, optical discs, hard disks, flash memory, or other storage media known in the art. There may be.
In one or more exemplary embodiments, the functionality described herein can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, a function can be stored on a computer-readable medium as one or more instructions or codes, or transmitted via a computer-readable medium. Computer-readable media include both computer storage media and computer communication media, including any medium that allows the transfer of computer programs from one location to another. The storage medium can be any available medium accessible by the computer. By way of example, but not by limitation, such computer-readable media are RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or desired programs in the form of instructions or data structures. It can include any other medium that can be used to carry or store the code and is accessible by a computer. Also, any connection is properly referred to as a computer-readable medium. For example, the software uses coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, wireless, and microwave from a website, server, or other remote source. When transmitted, coaxial cables, fiber optic cables, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the definition of medium. The discs and discs used herein are compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks. (Registered Trademarks) Including discs and Blu-ray discs, "disks" typically reproduce data magnetically and "discs". ) "Reproduces the data optically with a laser. The above combinations should also be included within the scope of computer-readable media.
Although the particular aspects of the subject matter described herein have been illustrated and described, making changes and modifications based on the teachings herein without departing from the subject matter described herein and its broader aspects. And therefore, the appended claims should include all such changes and modifications within the true meaning and scope of the subject matter described herein. Will be obvious to those skilled in the art.
10 system 12 PTT group 14 wireless phone 16 smart pager 17 wireless device 18 Personal Digital Assistant (PDA) 20 wireless network 30 Server-side LAN 32 Group communication computer device 34 database 36 media server 52 PDSN 54 Carrier Network 58 Messaging service controller 60 base station 62 Packet control function (PCF) 64 base station controller 66 Branch to Source (BTS) 70 Cellular Phone 72 Cellular phone 74 Cellular phone 76 Cellular Phone 78 PTT button 80 graphics display 82 Computer platform 84 ASIC 86 Application Programming Interface (API) Layer 88 memory 90 local database 92 Direct communication interface 102 Advanced Mobile Subscriber Software (AMSS) 104 Mobile Operating System Layer 106 PTT recognition UI 108 PTT client 110 media client 112 Group Media Application 20 Target mobile devices 134 Dispatch Call Handler (DCH) 108 PTT client 108-R PTT client 110 media client 110-R Media Client
10 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| WO2008157809A2 | Cites | World Intellectual Property Organization (WIPO) |
| JP2006514359A | Cites | Japan |
| WO2008087742A1 | Cites | World Intellectual Property Organization (WIPO) |
| WO2007048793A2 | Cites | World Intellectual Property Organization (WIPO) |
| JP2004348268A | Cites | Japan |
| JP2007258851A | Cites | Japan |
| JP2007148659A | Cites | Japan |
| JP2010531122A | Cites | Japan |
| JP2009514290A | Cites | Japan |
61 members in 7 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 12358979 | United States of America | – | |
| 35897909 | United States of America | A |
Members61
| Document | Office | Kind | |
|---|---|---|---|
| WO2008157809A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2008318610A1 | United States of America | A1 | |
| WO2008157809A3 | World Intellectual Property Organization (WIPO) | A3 | |
| KR20100028110A | Republic of Korea | A | |
| CN101682583A | China | A | |
| EP2171945A2 | European Patent Office (EPO) | A2 | |
| US2010190478A1 | United States of America | A1 | |
| WO2010085677A1 | World Intellectual Property Organization (WIPO) | A1 | |
| JP2010531122A | Japan | A | |
| KR20110115154A | Republic of Korea | A | |
| EP2382759A1 | European Patent Office (EPO) | A1 | |
| KR101086976B1 | Republic of Korea | B1 | |
| EP2391074A1 | European Patent Office (EPO) | A1 | |
| CN102282823A | China | A | |
| KR20110138211A | Republic of Korea | A | |
| KR20110138211A | Republic of Korea | A | |
| KR101129740B1 | Republic of Korea | B1 | |
| JP2012516116A | Japan | A | |
| US2013040686A1 | United States of America | A1 | |
| US2013040687A1 | United States of America | A1 | |
| US2013084912A1 | United States of America | A1 | |
| KR20130042650A | Republic of Korea | A | |
| KR20130042650A | Republic of Korea | A | |
| US2013122872A1 | United States of America | A1 | |
| US2013122955A1 | United States of America | A1 | |
| KR101289945B1 | Republic of Korea | B1 | |
| KR101289945B1 | Republic of Korea | B1 | |
| KR101289977B1 | Republic of Korea | B1 | |
| KR101289977B1 | Republic of Korea | B1 | |
| JP2013150351A | Japan | A | |
| JP5255130B2 | Japan | B2 | |
| CN101682583B | China | B | |
| JP2013168987A | Japan | A | |
| CN103369470A | China | A | |
| CN103402183A | China | A | |
| JP2013243723A | Japan | A | |
| EP2683209A1 | European Patent Office (EPO) | A1 | |
| EP2683210A1 | European Patent Office (EPO) | A1 | |
| WO2014085443A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2014107392A1 | World Intellectual Property Organization (WIPO) | A1 | |
| EP2171945B1 | European Patent Office (EPO) | B1 | |
| JP5591694B2 | Japan | B2 | |
| JP5601734B2This record | Japan | B2 | |
| TW201440474A | Taiwan Province of China | A | |
| JP2014207692A | Japan | A | |
| US8892147B2 | United States of America | B2 | |
| US8892148B2 | United States of America | B2 | |
| JP5635153B2 | Japan | B2 | |
| CN104885429A | China | A | |
| KR20150104139A | Republic of Korea | A | |
| JP2015188238A | Japan | A | |
| EP2941856A1 | European Patent Office (EPO) | A1 | |
| US9210202B2 | United States of America | B2 | |
| TWI520546B | Taiwan Province of China | B | |
| JP2016512659A | Japan | A | |
| CN103402183B | China | B | |
| EP2391074B1 | European Patent Office (EPO) | B1 | |
| US9674675B2 | United States of America | B2 | |
| JP6147805B2 | Japan | B2 | |
| US2017201552A1 | United States of America | A1 | |
| CN103369470B | China | B |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 5601734
- Application
- 84646
Titles2
- Japanese
- プレビューを用いたプッシュツーシェアファイル配信のためのシステムおよび方法
- English
- A system and a method for the push two share file distribution using a preview
Classification
- CPC, 5
- H04L65/4061
- H04W4/18
- H04W4/10
- H04W76/45
- H04W88/02
- IPC, 3
- H04M11 00
- H04M1 00
- H04W4 10
