Apparatus and methods for transport optimization for widget content delivery
50 claims: 14 independent, 36 dependent
- 1モバイルウィジェットのためのコンテンツを更新する方法であって、 複数の情報階層深度を有するモバイルウィジェットに対応する、更新されたコンテンツを得ることと;前記モバイルウィジェットに対応するユーザナビゲーションパターン履歴データを得ることと、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;第1のコンテンツ更新メッセージへの包含のために、第1の情報階層深度範囲を得ることと、なお、前記第1の情報階層深度範囲は、前記ユーザナビゲーションパターン履歴データに基づいている;前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの第1の部分で、前記第1のコンテンツ更新メッセージを生成することと;を備えている方法。
- 2前記更新されたコンテンツは、第1のサイズを備えており、 圧縮スキームに応じて、前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの前記第1の部分のサイズを縮小し、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記更新されたコンテンツの第1の圧縮された部分を定義すること、をさらに備える請求項1に記載の方法。
- 3前記モバイルウィジェットに対応する無線通信デバイスに対し前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始すること、をさらに備えている請求項2に記載の方法。
- 4前記モバイルウィジェットに対応する前のコンテンツ更新を得ること、をさらに備え、前記圧縮スキームは、前記前のコンテンツ更新と前記更新されたコンテンツに関して動作可能なデルタ圧縮スキームを備える、請求項2に記載の方法。
- 5前記モバイルウィジェットに対応する前のコンテンツ更新を得ることと、 第1のサイズを有するデルタコンテンツを定義するために、前記前のコンテンツ更新に基づいて、前記更新されたコンテンツにデルタ圧縮スキームを適用することと、 データ圧縮スキームに応じて前記第1の情報階層深度範囲に対応する前記デルタコンテンツ更新の第1の部分のサイズを縮小し、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記デルタコンテンツ更新の第1の圧縮されたデルタコンテンツ部分を定義することと、 をさらに備え、前記第1のコンテンツ更新メッセージを生成することは、前記第1の圧縮されたデルタコンテンツ部分を備えるために、前記更新されたコンテンツの前記第1の部分を生成することをさらに備える、請求項1に記載の方法。
- 6前記更新されたコンテンツは、構造スキーマ内で圧縮可能なデータを備え、前記圧縮スキームは、選択されたスキーマ特有圧縮スキームを備え、前記選択されたスキーマ特有圧縮スキームは、前記構造スキーマに対応しており、そして、前記構造スキーマを識別し前記構造スキーマから前記圧縮可能なデータを分離し、前記圧縮可能なデータを圧縮することが動作可能である、請求項2に記載の方法。
- 7前記モバイルウィジェットに対応するモバイルウィジェット識別子を備え、前記更新されたコンテンツに対応するユニバーサルリソース識別子(URI)を除外する、コンテンツ更新リクエストを受信すること、 をさらに備え、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始することは、前記コンテンツ更新リクエストの前記受信に基づいている、請求項3に記載の方法。
- 8前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始することは、一時的なネットワーク使用データあるいは一時的なネットワークキャパシティのいずれかを備えている無線ネットワークオペレータ関連更新考慮すべき事項に応じて決定されるコンテンツ更新スケジュールに基づいている、請求項3に記載の方法。
- 9ユーザ入力に基づいて、あるいは、コンテンツ更新スケジュールに基づいて、コンテンツ更新リクエストを受信すること、 をさらに備え、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始することは、前記コンテンツ更新リクエストの前記受信に基づいている、請求項3に記載の方法。
- 10前記更新されたコンテンツの第2の部分は、前記第1の情報階層深度範囲とは異なる第2の情報階層深度範囲に対応し、前記更新されたコンテンツの前記第2の部分は、第1のサイズを有し、 前記圧縮スキームに応じて前記更新されたコンテンツの前記第2の部分のサイズを縮小し、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記更新されたコンテンツの第2の圧縮された部分を定義することと、 前記モバイルウィジェットに対応する前記無線通信デバイスに、第2のコンテンツ更新メッセージにおける前記更新されたコンテンツの前記第2の圧縮された部分の無線移送を開始することと、 をさらに備えている請求項3に記載の方法。
- 11モバイルウィジェットのためのコンテンツを更新するように構成された少なくとも1つのプロセッサであって、 複数の情報階層深度を有するモバイルウィジェットに対応する更新されたコンテンツを得るための第1のモジュールと、前記更新されたコンテンツは、第1のサイズを有する;前記モバイルウィジェットに対応するユーザナビゲーションパターン履歴データを得るための第2のモジュールと、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;第1のコンテンツ更新メッセージへの包含のために、第1の情報階層深度範囲を得るための第3のモジュールと、なお、前記第1の情報階層深度範囲は、前記ユーザナビゲーションパターン履歴データに基づいている;前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの第1の部分で、前記第1のコンテンツ更新メッセージを生成するための第4のモジュールと;を備えている少なくとも1つのプロセッサ。
- 12圧縮スキームに応じて、前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの前記第1の部分のサイズを縮小し、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記更新されたコンテンツの第1の圧縮された部分を定義するための第5のモジュール、 をさらに備える請求項11に記載の少なくとも1つのプロセッサ。
- 13前記モバイルウィジェットに対応する無線通信デバイスに対し前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始するための第6のモジュール、 をさらに備えている請求項第12に記載の少なくとも1つのプロセッサ。
- 14モバイルウィジェットのためのコンテンツを更新するためのコンピュータプログラムプロダクトであって、コンピュータ可読媒体を備え、前記コンピュータ可読媒体は、 コンピュータに、複数の情報階層深度を有するモバイルウィジェットに対応する更新されたコンテンツを得させるための少なくとも1つの命令と、なお、前記更新されたコンテンツは、第1のサイズを有する;前記コンピュータに、前記モバイルウィジェットに対応するユーザナビゲーションパターン履歴データを得させるための少なくとも1つの命令と、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;前記コンピュータに、第1のコンテンツ更新メッセージへの包含のために、第1の情報階層深度範囲を得させるための少なくとも1つの命令と、なお、前記第1の情報階層深度範囲は、前記ユーザナビゲーションパターン履歴データに基づいている;前記コンピュータに、前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの第1の部分で、前記第1のコンテンツ更新メッセージを生成させるための少なくとも1つの命令と;を備えている、 コンピュータプログラムプロダクト。
- 15前記コンピュータ可読媒体は、 前記コンピュータに、圧縮スキームに応じて、前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの前記第1の部分のサイズを縮小させ、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記更新されたコンテンツの第1の圧縮された部分を定義するための少なくとも1つの命令、 をさらに備える、請求項14に記載のコンピュータプログラムプロダクト。
- 16前記コンピュータ可読媒体は、前記コンピュータに、前記モバイルウィジェットに対応する無線通信デバイスに対し前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始させるための少なくとも1つの命令、をさらに備える、請求項第15に記載のコンピュータプログラムプロダクト。
- 17モバイルウィジェットのためのコンテンツを更新するためのネットワークデバイスであって、 複数の情報階層深度を有するモバイルウィジェットに対応する更新されたコンテンツを得るための手段と、なお、前記更新されたコンテンツは、第1のサイズを備えている;前記モバイルウィジェットに対応するユーザナビゲーションパターン履歴データを得るための手段と、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;第1のコンテンツ更新メッセージへの包含のために、第1の情報階層深度範囲を得るための手段と、なお、前記第1の情報階層深度範囲は、前記ユーザナビゲーションパターン履歴データに基づいている;前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの第1の部分で、前記第1のコンテンツ更新メッセージを生成するための手段と;を備えているネットワークデバイス。
- 18モバイルウィジェットのためのコンテンツを更新するためのネットワークデバイスであって、 コンテンツ更新パッケージバンドラを備えているメモリと、 前記メモリと通信し、そして、前記コンテンツ更新マネージャと前記コンテンツパッケージバンドラを実行することが動作可能であるプロセッサと、 を備え、 前記コンテンツ更新パッケージバンドラは、複数の情報階層深度を有するモバイルウィジェットに対応する更新されたコンテンツを得ることが動作可能であり、前記コンテンツ更新マネージャは、前記モバイルウィジェットに対応するユーザナビゲーションパターン履歴データを得ることがさらに動作可能であり、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応しており、前記コンテンツ更新パッケージバンドラは、第1のコンテンツ更新メッセージへの包含のために、第1の情報階層深度範囲を得ることがさらに動作可能であり、前記第1の情報階層深度範囲は、前記ユーザナビゲーションパターン履歴データに基づいており、前記コンテンツ更新パッケージバンドラは、前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの第1の部分で、前記第1のコンテンツ更新メッセージを生成することがさらに動作可能である、 ネットワークデバイス。
- 19前記更新されたコンテンツは、第1のサイズを備え、前記コンテンツパッケージバンドラは、圧縮スキームに応じて、前記第1の情報階層深度範囲に対応する前記更新されたコンテンツの前記第1の部分のサイズを縮小することが動作可能であり、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記更新されたコンテンツの第1の圧縮された部分を定義する、請求項18に記載のネットワークデバイス。
- 20前記コンテンツ更新パッケージバンドラは、前記モバイルウィジェットに対応する無線通信デバイスに対し前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始することがさらに動作可能である、請求項19に記載のネットワークデバイス。
- 21前記コンテンツ更新パッケージバンドラは、前記モバイルウィジェットに対応する前のコンテンツ更新を得ることがさらに動作可能であり、前記圧縮スキームは、前記前のコンテンツ更新と前記更新されたコンテンツに関して動作可能なデルタ圧縮スキームを備えている、請求項19に記載のネットワークデバイス。
- 22前記コンテンツ更新パッケージバンドラは、 前記モバイルウィジェットに対応する前のコンテンツ更新を得ることと;第1のサイズを有するデルタコンテンツ更新を定義するために前記前のコンテンツ更新に基づいて、前記更新されたコンテンツにデルタ圧縮スキームを適用することと;データ圧縮スキームに応じて前記第1の情報階層深度範囲に対応する前記デルタコンテンツ更新の第1の部分のサイズを縮小し、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記デルタコンテンツ更新の第1の圧縮されたデルタコンテンツ部分を定義することと、なお、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の部分は、前記第1の圧縮されたデルタコンテンツ部分を備えている;が動作可能である、請求項18に記載のネットワークデバイス。
- 23前記更新されたコンテンツは、構造スキーマ内で圧縮可能なデータを備え、前記圧縮スキームは、選択されたスキーマ特有圧縮スキームを備え、前記選択されたスキーマ特有圧縮スキームは、前記構造スキーマに対応しており、そして、前記構造スキーマを識別し前記構造スキーマから前記圧縮可能なデータを分離し、前記圧縮可能なデータを圧縮することが動作可能である、請求項19に記載のネットワークデバイス。
- 24前記コンテンツ更新パッケージバンドラは、前記モバイルウィジェットに対応するモバイルウィジェット識別子を備え前記更新されたコンテンツに対応するユニバーサルリソース識別子(URI)を除外するコンテンツ更新リクエストを受信することがさらに動作可能であり、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の前記無線移送の前記開始は、前記コンテンツ更新リクエストの前記受信に基づいている、請求項20に記載のネットワークデバイス。
- 25前記コンテンツ更新パッケージバンドラは、一時的なネットワーク使用データあるいは一時的なネットワークキャパシティデータのいずれかを備えている無線ネットワークオペレータ関連更新考慮すべき事項に応じて決定されるコンテンツ更新スケジュールに基づいて、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の前記無線移送を開始することがさらに動作可能である、請求項20に記載のネットワークデバイス。
- 26前記コンテンツ更新パッケージバンドラは、ユーザ入力に基づいて、あるいは、コンテンツ更新スケジュールに基づいて、コンテンツ更新リクエストを受信することがさらに動作可能であり、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の圧縮された部分の無線移送を開始することは、前記コンテンツ更新リクエストの前記受信に基づいている、請求項20に記載のネットワークデバイス。
- 27前記更新されたコンテンツの第2の部分は、前記第1の情報階層深度範囲とは異なる第2の情報階層深度範囲に対応し、前記更新されたコンテンツの前記第2の部分は、第1のサイズを有しており、前記コンテンツ更新パッケージバンドラは、圧縮スキームに応じて前記更新されたコンテンツの前記第2の部分のサイズを縮小することがさらに動作可能であり、それによって、前記第1のサイズよりも小さい第2のサイズを有する前記更新されたコンテンツの第2の圧縮された部分を定義し、前記コンテンツ更新パッケージバンドラは、前記モバイルウィジェットに対応する前記無線通信デバイスに対し、第2のコンテンツ更新メッセージにおける前記更新されたコンテンツの前記第2の圧縮された部分の無線移送を開始することがさらに動作可能である、請求項18に記載のネットワークデバイス。
- 28無線通信デバイス上でモバイルウィジェットのためのコンテンツを更新する方法であって、 無線通信デバイス上でモバイルウィジェットを保存することと、なお、前記モバイルウィジェットは、複数の情報階層深度を備えている;ユーザナビゲーションパターン履歴データを定義するために、前記モバイルウィジェットに対応するユーザナビゲーションパターンをトラッキングすることと、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;コンテンツソースと関連づけられたネットワークデバイスに、前記ユーザナビゲーションパターン履歴データを転送することと;前記ネットワークデバイスから、第1のコンテンツ更新メッセージにおいて更新されたコンテンツの第1の部分を無線で受信することと、なお、更新されたコンテンツの前記第1の部分は、前記ユーザナビゲーションパターン履歴データに基づいて、前記モバイルウィジェットの第1の情報階層深度範囲に対応する;を備えている方法。
- 29前記更新されたコンテンツの前記第1の部分は、前記更新されたコンテンツの第1の圧縮された部分を定義するために、圧縮スキームに応じて圧縮され、前記第1の圧縮された部分は、前記更新されたコンテンツの前記対応する第1の部分の第1のサイズよりも小さい第2のサイズを備え、前記第1の圧縮された部分を解凍する、請求項28に記載の方法。
- 30前記圧縮スキームはデルタ圧縮スキームを備えており、前記更新されたコンテンツの前記第1の圧縮された部分は、前記モバイルウィジェットに対応する前のコンテンツ更新を得ることによって圧縮される第1のデルタ圧縮された部分を備え、前記更新されたコンテンツの前記第1のデルタ圧縮された部分を得るために前記更新されたコンテンツの前記第1の部分と、前記前のコンテンツ更新に関して前記デルタ圧縮スキームを実行し、前記方法は、前記更新されたコンテンツの前記第1のデルタ圧縮された部分に基づいて前記モバイルウィジェットを実行することをさらに備えている、請求項29に記載の方法。
- 31前記圧縮スキームは、データ圧縮スキームを備え、前記更新されたコンテンツの前記第1の圧縮された部分は、第1のデータ圧縮された部分を備え、前記更新されたコンテンツの前記第1のデータ圧縮された部分を得るために前記更新されたコンテンツの前記第1の部分に関して前記データ圧縮スキームを実行し、前記方法は、前記更新されたコンテンツの前記第1の解凍された部分で、前記モバイルウィジェットを実行することをさらに備えている、請求項29に記載の方法。
- 32前記更新されたコンテンツは、構造スキーマ内で圧縮可能なデータを備え、前記データ圧縮スキームは、選択されたスキーマ特有圧縮スキームを備え、前記選択されたスキーマ特有圧縮スキームは、前記構造スキーマに対応しており、そして、前記更新されたコンテンツの前記第1の圧縮された部分の前記構造スキーマを識別することが動作可能である、請求項31に記載の方法。
- 33前記モバイルウィジェットに対応するモバイルウィジェット識別子を備え、前記更新されたコンテンツに対応するユニバーサルリソース識別子(URI)を除外するコンテンツ更新リクエストを送信すること、をさらに備え、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の部分を無線で受信することは、前記コンテンツ更新リクエストの前記送信に基づいて開始される、請求項28に記載の方法。
- 34前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の部分を無線で受信することは、一時的なネットワーク使用データあるいは一時的なネットワークキャパシティデータのいずれかを備えている無線ネットワークオペレータ関連更新考慮すべき事項に応じて決定されるコンテンツ更新スケジュールに基づいている、請求項28に記載の方法。
- 35ユーザ入力に基づいて、あるいは、コンテンツ更新スケジュールに基づいて、コンテンツ更新リクエストを送信することと、をさらに備え、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の部分を無線で受信することは、前記コンテンツ更新リクエストの前記送信に基づいて開始される、請求項28に記載の方法。
- 36第2のコンテンツ更新メッセージにおける前記更新されたコンテンツの第2の部分を無線で受信すること、をさらに備え、前記更新されたコンテンツの前記第2の部分は、前記第1の情報階層深度範囲とは異なる第2の情報階層深度範囲を有する前記更新されたコンテンツの第2の部分に対応する、請求項28に記載の方法。
- 37前記更新されたコンテンツの前記第2の部分は、前記更新されたコンテンツの第2の圧縮された部分を定義するために、圧縮スキームに応じて圧縮され、前記第2の圧縮された部分は、前記更新されたコンテンツの前記対応する第2の部分の第1サイズよりも小さい第2のサイズを備えており、 前記第2の圧縮された部分を解凍すること、をさらに備えている請求項36に記載の方法。
- 38無線通信デバイス上でモバイルウィジェットのためのコンテンツを更新することが動作可能な少なくとも1つのプロセッサであって、 無線通信デバイス上でモバイルウィジェットを保存するための第1のモジュールと、なお、前記モバイルウィジェットは、複数の情報階層深度を備えている;ユーザナビゲーションパターン履歴データを定義するために、前記モバイルウィジェットに対応するユーザナビゲーションパターンをトラッキングするための第2のモジュールと、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;コンテンツソースと関連づけられたネットワークデバイスに、前記ユーザナビゲーションパターン履歴データを転送するための第3のモジュールと;前記ネットワークデバイスから、第1のコンテンツ更新メッセージにおいて更新されたコンテンツの第1の部分を無線で受信するための第4のモジュールと、なお、更新されたコンテンツの前記第1の部分は、前記ユーザナビゲーションパターン履歴データに基づいて、前記モバイルウィジェットの第1の情報階層深度範囲に対応する;を備えている少なくとも1つのプロセッサ。
- 39無線通信デバイス上でモバイルウィジェットのためのコンテンツを更新するためのコンピュータプログラムプロダクトであって、コンピュータ可読媒体を備え、前記コンピュータ可読媒体は、 コンピュータに無線通信デバイス上でモバイルウィジェットを保存させることが動作可能な少なくとも1つの命令と、なお、前記モバイルウィジェットは、複数の情報階層深度を備えている;前記コンピュータに、ユーザナビゲーションパターン履歴データを定義するために、前記モバイルウィジェットに対応するユーザナビゲーションパターンをトラッキングさせることが動作可能な少なくとも1つの命令と、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;前記コンピュータに、コンテンツソースと関連づけられたネットワークデバイスに対して前記ユーザナビゲーションパターン履歴データを転送させることが動作可能な少なくとも1つの命令と;前記コンピュータに、前記ネットワークデバイスから第1のコンテンツ更新メッセージにおいて更新されたコンテンツの第1の部分を無線で受信させることが動作可能な少なくとも1つの命令と、更新されたコンテンツの前記第1の部分は、前記ユーザナビゲーションパターン履歴に基づいて、前記モバイルウィジェットの第1の情報階層深度範囲に対応する;を備えている、 コンピュータプログラムプロダクト。
- 40無線通信デバイスであって、 無線通信デバイス上でモバイルウィジェットを保存するための手段と、なお、前記モバイルウィジェットは、複数の情報階層深度を備えている;ユーザナビゲーションパターン履歴データを定義するために、前記モバイルウィジェットに対応するユーザナビゲーションパターンをトラッキングするための手段と、なお、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応する;コンテンツソースと関連づけられたネットワークデバイスに、前記ユーザナビゲーションパターン履歴データを転送するための手段と;前記ネットワークデバイスから第1のコンテンツ更新メッセージにおいて更新されたコンテンツの第1の部分を無線で受信するための手段と、なお、更新されたコンテンツの前記第1の部分は、前記ユーザナビゲーションパターン履歴データに基づいて、前記モバイルウィジェットの第1の情報階層深度範囲に対応する;を備えている無線通信デバイス。
- 41無線デバイスであって、 モバイルウィジェットとウィジェット管理クライアントとを備えているメモリと、なお、前記モバイルウィジェットは、複数の情報階層深度を備えている;前記モバイルウィジェットと前記ウィジェット管理クライアントとを実行することが動作可能であり、前記メモリと通信しているプロセッサと、なお、前記ウィジェット管理クライアントは、ユーザナビゲーションパターン履歴データを定義するために、前記モバイルウィジェットに対応するユーザナビゲーションパターンをトラッキングすることが動作可能であり、前記ユーザナビゲーションパターン履歴データは、前記複数の情報階層深度に対応し、前記ウィジェット管理クライアントは、コンテンツソースと関連づけられたネットワークデバイスに前記ユーザナビゲーションパターン履歴データを転送することがさらに動作可能である;前記ネットワークデバイスから第1のコンテンツ更新メッセージにおいて更新されたコンテンツの第1の部分を無線で受信することが動作可能な通信モジュールと、なお、更新されたコンテンツの前記第1の部分は、前記ユーザナビゲーションパターン履歴データに基づいて前記モバイルウィジェットの第1の情報階層深度範囲に対応する;を備えている無線デバイス。
- 42前記更新されたコンテンツの前記第1の部分は、前記更新されたコンテンツの第1の圧縮された部分を定義するために、圧縮スキームに応じて圧縮され、前記第1の圧縮された部分は、前記更新されたコンテンツの前記対応する第1の部分の第1のサイズよりも小さい第2のサイズを備え、前記ウィジェット管理クライアントは、前記第1の圧縮された部分を解凍することがさらに動作可能である、請求項41に記載の無線デバイス。
- 43前記圧縮スキームは、デルタ圧縮スキームを備えており、前記更新されたコンテンツの前記第1の圧縮された部分は、前記モバイルウィジェットに対応する前のコンテンツ更新を得ることによって圧縮される第1のデルタ圧縮部分を備え、前記更新されたコンテンツの前記第1のデルタ圧縮された部分を得るために前記更新されたコンテンツの前記第1の圧縮された部分と前記前のコンテンツ更新に関して前記デルタ圧縮スキームを実行し、前記モバイルウィジェットは、前記更新されたコンテンツの前記第1のデルタ圧縮された部分に基づいて実行可能である、請求項42に記載の無線デバイス。
- 44前記圧縮スキームは、データ圧縮スキームを備えており、前記更新されたコンテンツの前記第1の圧縮された部分は、第1のデータ圧縮された部分を備え、前記更新されたコンテンツの前記第1のデータ圧縮された部分を得るために前記更新されたコンテンツの前記第1の部分に関してデータ圧縮スキームを実行し、前記ウィジェット管理クライアントは、前記更新されたコンテンツの前記第1の解凍された部分で前記モバイルウィジェットを実行することがさらに動作可能である、請求項42に記載の無線デバイス。
- 45前記更新されたコンテンツは、構造スキーマ内で圧縮可能なデータを備えており、前記データ圧縮スキームは、選択されたスキーマ特有圧縮スキームを備え、前記選択されたスキーマ特有圧縮スキームは、前記構造スキーマに対応しており、そして前記更新されたコンテンツの前記第1の圧縮された部分の前記構造スキーマを識別することが動作可能である、請求項44に記載の無線デバイス。
- 46前記ウィジェット管理クライアントは、前記モバイルウィジェットに対応するモバイルウィジェット識別子を備え、前記更新されたコンテンツに対応するユニバーサルリソース識別子(URI)を除外する、コンテンツ更新リクエストを送信することがさらに動作可能であり、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の部分の前記無線受信は、前記コンテンツ更新リクストの前記送信に基づいて開始される、請求項41に記載の無線デバイス。
- 47前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の部分の前記無線受信は、一時的なネットワーク使用データあるいは一時的なネットワークキャパシティデータのいずれかを備えている無線ネットワークオペレータ関連更新考慮すべき事項に応じて決定されるコンテンツ更新スケジュールに基づいている、請求項41に記載の無線デバイス。
- 48前記ウィジェット管理クライアントは、ユーザ入力に基づいて、あるいは、コンテンツ更新スケジュールに基づいて、コンテンツ更新リクエストを送信することがさらに動作可能であり、前記第1のコンテンツ更新メッセージにおいて前記更新されたコンテンツの前記第1の部分の前記無線受信は、前記コンテンツ更新リクエストの前記送信に基づいて開始される、請求項41に記載の無線デバイス。
- 49前記通信モジュールは、第2のコンテンツ更新メッセージにおける前記更新されたコンテンツの第2の部分を無線で受信することがさらに動作可能であり、前記更新されたコンテンツの前記第2の部分は、前記第1の情報階層深度範囲とは異なる第2の情報階層深度範囲を有する前記更新されたコンテンツの第2の部分に対応する、請求項41に記載の無線デバイス。
- 50前記更新されたコンテンツの前記第2の部分は、前記更新されたコンテンツの第2の圧縮された部分を定義するために、圧縮スキームに応じて圧縮され、前記第2の圧縮された部分は、前記更新されたコンテンツの前記対応する第2の部分の第1のサイズよりも小さい第2のサイズを備えており、前記ウィジェット管理クライアントは、前記第2の圧縮された部分を解凍することがさらに動作可能である、請求項49に記載の無線デバイス。
Independent claims50
157 paragraphs, as filed
Priority claim
(Priority claim under US Patent Law) This patent application, by reference herein, is expressly incorporated herein by "APPARATUS AND METHODS OF MANAGING WIDGETS", filed March 25, 2008. IN A WIRELESS COMMUNICATION ENVIRONMENT) ", claiming the priority of provisional application number 61 / 039,402.
(Refer to the patent application pending at the same time) This patent application is the following co-pending US patent application: "Devices and methods for widget update scheduling" with agent reference number 081068U2, expressly incorporated by reference herein and filed with it. (APPARATUS AND METHODS FOR WIDGET UPDATE SCHEDULING) ";" Devices and methods for widget-related memory management (APPARATUS AND METHODS) with agent reference number 081068U3, explicitly incorporated by reference herein and filed with it. FOR WIDGET-RELATED MEMORY MANAGEMENT) "; A device and method for managing widgets in a wireless communication environment (APPARATUS AND) with agent reference number 081068U4, explicitly incorporated by reference here and filed with it. METHODS FOR MANAGING WIDGETS IN A WIRELESS COMMUNICATION ENVIRONMENT) ; APPPARATUS AND METHODS FOR WIDGET INTER- COMMUNICATION IN A WIRELESS COMMUNICATION ENVIRONMENT) ";
background
The described aspects relate to widgets, and more specifically to devices and methods for transport optimization for widget content delivery in a wireless communication environment.
Wireless networking systems have become a popular means of communicating with others in the world. Wireless communication devices such as mobile or cellular phones, personal digital assistants (PDAs), etc., operate on such networks and are smaller to meet consumer needs and improve portability and convenience. It became higher performance. Consumers have become dependent on these devices, demanding reliable services, expanded areas of service, additional services such as web browsing capabilities, and continued reductions in the size and cost of such devices. There is.
Many of the features and end user experiences of wireless communication devices mimic the features and end user experiences of personal computing (PC) environments without much success (with limited success). , Has developed. For example, mobile web services have seen varying levels of achievement, even in the deployment of relatively fast and high capacity services, such as advanced 3G services (1X-EV-DO Rev. A, UMTS HSPA). .. Much of the challenge lies in the fact that mobile web browsing experience is different from the PC experience that most users are familiar with. In particular, many end users find it difficult to use mobile web browsing applications, for example when it comes to entering search information, for example, it is difficult to enjoy because the presentation that results from the content is not fun. I believe.
In addition, web content delivery for desktop widgets is usually achieved under the assumption that sufficient access layer throughput is available. In contrast, cellular access to such content often results in various and sometimes inadequate throughput for content delivery.
Therefore, it is desirable for devices and methods to improve end-user experience in interacting with web services on wireless communication devices.
The following presents a summary of one or more aspects to provide a basic understanding of such aspects. This overview does not provide a broad overview of all conceived aspects, but may also identify important or decisive elements of all aspects, or detail the scope of any or all aspects. It is also not intended to be portrayed in. Its sole purpose is to present some concepts in one or more aspects in a simplified form as a prelude to a more detailed description, which will be shown later.
One aspect relates to how to update content for a mobile widget. The method can include obtaining updated content for mobile widgets with a plurality of informational hierarchical depths. The method can also include obtaining user navigation pattern historical data corresponding to the mobile widget, where the user navigation pattern historical data corresponds to multiple information hierarchy depths. .. Also, the method is informational hierarchical depth for inclusion in a first content update message. Range) can be included, where the hierarchical depth range of the first piece of information is based on user navigation pattern history data. Further, the method can include generating a first content update message in the first portion of the updated content corresponding to the hierarchical depth range of the first information.
Another aspect relates to at least one processor configured to update content for a mobile widget. The processor can include a first module for obtaining updated content corresponding to mobile widgets with multiple information hierarchy depths. Further, the processor can include a second module for obtaining user navigation pattern history data corresponding to the mobile widget, and the user navigation pattern history data corresponds to a plurality of information hierarchy depths. The processor can also include a third module to obtain a first information hierarchical depth range for inclusion in the first content update message, yet the hierarchical depth of the first information. The range is based on user navigation pattern history data. In addition, the processor can include a fourth module for generating a first content update message in the first part of the updated content corresponding to the hierarchical depth range of the first information.
However, another aspect is a computer program for updating content for mobile widgets, including a computer-readable medium. product). The computer-readable medium can include at least one instruction for causing the computer to obtain updated content corresponding to mobile widgets having multiple information hierarchy depths. Further, the computer-readable medium can include at least one instruction for causing the computer to obtain the user navigation pattern history data corresponding to the mobile widget, and the user navigation pattern history data can be stored in a plurality of information hierarchy depths. Correspond. Also, the computer-readable medium can include at least one instruction to cause the computer to obtain a first information hierarchy depth range for inclusion in the first content update message, which is noted herein. The first information hierarchy depth range is based on user navigation pattern history data. In addition, the computer-readable medium may include at least one instruction to cause the computer to generate a first content update message in the first part of the updated content corresponding to the first information hierarchy depth range. it can.
Another aspect relates to a network device for updating content for a mobile widget. The network device can include means for obtaining updated content corresponding to mobile widgets having a plurality of information hierarchy depths, and the updated content has a first size. Further, the network device can include means for obtaining the user navigation pattern history data corresponding to the mobile widget, and the user navigation pattern history data corresponds to a plurality of information hierarchy depths. The network device can also include means for obtaining a first information hierarchy depth range for inclusion in the first content update message, where the first information hierarchy depth range is the user. Based on navigation pattern history data. Further, the network device can include a means for generating a first content update message, which is the first part of the updated content corresponding to the first information hierarchy depth range.
Yet another aspect relates to network devices for updating content for mobile widgets. Network devices are content update managers and content packages. Can include memory with bundler). The network device can also run a content update manager and a content package bundler, and can include a processor that communicates with memory. The content update manager can act to obtain updated content corresponding to mobile widgets with multiple information hierarchy depths, where the updated content has a first size. The content update manager can further operate to obtain the user navigation pattern history data corresponding to the mobile widget. The user navigation pattern history data corresponds to a plurality of information hierarchy depths. In addition, the content update package bundler can further operate to obtain a first information hierarchy depth range for inclusion in the first content update message. The first information hierarchy depth range is based on user navigation pattern history data. Further, the content update package bundler can further operate to generate a first content update message in the first part of the updated content corresponding to the first information hierarchy depth range.
Another aspect relates to a method of updating content for a mobile widget on a wireless communication device. The method can include storing the mobile widget on a wireless communication device, where the mobile widget has multiple layers of information depth. Further, the method can include tracking the user navigation pattern corresponding to the mobile widget to define the user navigation pattern history data, and the user navigation pattern history data corresponds to a plurality of information hierarchy depths. To do. Further, the method can include transferring user navigation pattern history data to a network device associated with the content source. Further, the method can include wirelessly receiving the first part of the updated content in the first content update message from the network device. The first part of the updated content corresponds to the first information hierarchy depth range of the mobile widget based on the user navigation pattern history data.
Yet another aspect relates to at least one processor capable of updating content for a mobile widget on a wireless communication device. The processor can include a first module for storing mobile widgets on wireless communication devices. Mobile widgets have multiple information hierarchy depths. In addition, the processor can include a second module for tracking user navigation patterns corresponding to mobile widgets to define user navigation pattern history data. The user navigation pattern history data corresponds to a plurality of information hierarchy depths. In addition, the processor can include a third module for transferring user navigation pattern history data to the network device associated with the content source. The processor can also include a fourth module for wirelessly receiving the first part of the updated content in the first content update message from the content source. The first part of the updated content corresponds to the hierarchical depth range of the first information in the mobile widget, based on the user navigation pattern history data.
Another aspect relates to a computer program product for updating content for a mobile widget on a wireless communication device that includes a computer-readable medium. The computer-readable medium can include at least one instruction capable of causing the computer to store the mobile widget on the wireless communication device, and the mobile widget has a plurality of information hierarchy depths. The computer-readable medium can also include at least one instruction capable of causing the computer to track the user navigation pattern corresponding to the mobile widget in order to define the user navigation pattern history data. The user navigation pattern history data corresponds to a plurality of information hierarchy depths. In addition, the computer-readable medium can include at least one instruction capable of causing the computer to transfer user navigation pattern history data to a network device associated with the content source. Further, the computer-readable medium can include at least one instruction capable of causing the computer to wirelessly receive the first part of the updated content in the first content update message from the content source. The first part of the updated content corresponds to the hierarchical depth range of the first information in the mobile widget, based on the user navigation pattern history data.
Yet another aspect relates to wireless communication devices. The wireless communication device can include means for storing the mobile widget on the wireless communication device, and the mobile widget has a plurality of information hierarchy depths. In addition, the wireless communication device can include means for tracking the user navigation pattern corresponding to the mobile widget in order to define the user navigation pattern history data. The user navigation pattern history data corresponds to a plurality of information hierarchy depths. In addition, the wireless communication device can include means for transferring user navigation pattern history data to a network device associated with the content source. Further, the wireless communication device can include a means for wirelessly receiving the first part of the updated content in the first content update message from the content source. The first part of the updated content corresponds to the hierarchical depth range of the first information in the mobile widget, based on the user navigation pattern history data.
Another aspect relates to wireless devices. Wireless devices are mobile widgets and widget management clients Can include memory with client). Mobile widgets have multiple information hierarchy depths. Wireless devices can also include processors that are capable of running mobile widgets and widget management clients and are communicating with memory. The widget management client can operate to track the user navigation pattern corresponding to the mobile widget in order to define the user navigation pattern history data. The user navigation pattern history data corresponds to a plurality of information hierarchy depths. The widget management client can further operate to transfer user navigation pattern history data to the network device associated with the content source. In addition, the wireless device may include a communication module capable of wirelessly receiving a first portion of the updated content in the first content update message from the content source. The first part of the updated content corresponds to the hierarchical depth range of the first information in the mobile widget, based on the user navigation pattern history data.
To achieve the aforementioned and related objectives, one or more aspects may comprise features well described herein and specifically noted in the claims. The description and accompanying drawings below describe in detail the features of the description in one or more embodiments. However, although these features show some different ways in which the principles of different aspects can be utilized, this description includes all such aspects and their equivalents. Is intended to be.
<figref num="1">FIG. 1 is a schematic diagram of an aspect of an end-to-end mobile widget system.</figref><figref num="2">FIG. 2 is a schematic representation of an aspect of a wireless device having a display with a plurality of mobile widgets in the first state.</figref><figref num="3">FIG. 3 is a schematic representation of an aspect of the wireless device of FIG. 2 with one of the mobile widgets in the second state.</figref><figref num="4">FIG. 4 is a schematic diagram of one aspect of the network device of the system of FIG.</figref><figref num="5">FIG. 5 is a schematic view of one aspect of the integrated widget manager (UWM) of FIG.</figref><figref num="6">FIG. 6 is a schematic diagram of one aspect of the auction architecture of the system of FIG.</figref><figref num="7">FIG. 7 is a flow chart of one aspect of the auction method of the system of FIG.</figref><figref num="8">FIG. 8 is a schematic view of one aspect of the widget management system (WMS) of FIG.</figref><figref num="9">FIG. 9 is a schematic view of one aspect of the message router of FIG.</figref><figref num="10">FIG. 10 is a schematic view of one aspect of the wireless device of FIG.</figref><figref num="11">FIG. 11 is a schematic view of one aspect of the widget management client (WMC) of FIG.</figref><figref num="12">FIG. 12 is a schematic view of one aspect of the widget use reporter of the system of FIG.</figref><figref num="13">FIG. 13 is a schematic view of one aspect of the WMC widget wizard of FIG.</figref><figref num="14">FIG. 14 is a schematic view of one aspect of the widget advertisement of the system of FIG.</figref><figref num="15">FIG. 15 is a schematic diagram of one aspect of the advertising architecture of the system of FIG.</figref><figref num="16">FIG. 16 is a schematic diagram of one aspect of the widget configuration architecture of the system of FIG.</figref><figref num="17">FIG. 17 is a schematic view of one aspect of the content access server of the system of FIG.</figref><figref num="18">FIG. 18 is a call flow relating to one aspect of selecting and updating a mobile widget in the system of FIG.</figref><figref num="19">FIG. 19 is a call flow relating to a mode in which a mobile widget is selected and updated in the system of FIG.</figref><figref num="20">FIG. 20 is a call flow relating to one aspect of operator / carrier control of access to the mobile widget in the system of FIG.</figref><figref num="21">FIG. 21 is a call flow related to one aspect of updating a mobile widget in the system of FIG.</figref><figref num="22">FIG. 22 is a call flow relating to an aspect of adjusting a content update schedule for a mobile widget or end user in the system of FIG.</figref><figref num="23">FIG. 23 is a call flow relating to the mode of updating the mobile widget in the system of FIG.</figref><figref num="24">FIG. 24 is a schematic diagram of an aspect of optimizing the transfer of updated content in the system of FIG.</figref><figref num="25">FIG. 25 is a flow diagram of one aspect of a method of optimizing the transfer of updated content in the system of FIG.</figref><figref num="26">FIG. 26 is a flow diagram of one aspect of a method of optimizing the transfer of updated content in the system of FIG.</figref><figref num="27">FIG. 27 is an illustration of an example of a system that facilitates updating content for mobile widgets.</figref><figref num="28">FIG. 28 is an illustration of an example of a system that facilitates updating content for mobile widgets on a wireless communication device.</figref>
Detailed explanation
The disclosed embodiments are described herein, along with the accompanying drawings, and are provided to describe rather than limit the disclosed embodiments, and similar designations refer to similar elements. Shown.
Various aspects are described with reference to the accompanying drawings. In the following description, for purposes of explanation, many specific details are provided to provide a complete understanding of one or more aspects. However, it is clear that such embodiments (s) can be carried out without these particular details.
The aspects described relate to widgets, and more specifically to devices and methods for transport optimization for widget content distribution. For example, the described embodiment can include transporting widget content based on the user's navigation pattern corresponding to each widget.
In the subject description, the term "exemplary" is used to mean acting as an example, instance, or illustration. There is. Any aspect or design described herein is "exemplary" and should not necessarily be construed as preferred or advantageous over other aspects or designs. Absent. Rather, the use of the word "exemplary" is intended to present the concept in a concrete way.
As used herein, the terms "component", "module", "system" and the like are, for example, hardware, firmware, hardware-software combinations, etc. It is intended to include computer-related entities such as software, or running software. For example, components are, but not limited to, processes, processors, objects, executables, and threads of execution that are running on a processor. It may be execution), a program, and / or a computer. As an example, both an application running on a communication device and a computing device can be components. One or more components can reside within a process and / or execution thread, components may be localized on one computer, and / or two or more computers. It may be distributed between. In addition, these components can be run from a variety of computer-readable media with various data structures stored therein. Components can communicate in local and / or remote processes, eg, in local systems, in distributed systems, and / or across networks such as the Internet using other systems in a signaling manner. Follows a signal with one or more data packets, such as data from one component interacting with the component.
In addition, various aspects are described herein in relation to the terminal, which can be a wired terminal, or a wireless terminal. Terminals are also systems, devices, subscriber units, subscriber stations, mobile stations, mobiles, mobile devices, remote stations, remote terminals, access terminals, user terminals, terminals, communication devices, user agents, user devices, or user devices. Can be called (UE). Wireless terminals include cellular phones, satellite phones, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants. It may be an assistant) (PDA), a handheld device with wireless connectivity, a computing device, or other processing device connected to a wireless modem. In addition, various aspects are described herein in connection with the base station. Base stations can be used to communicate with wireless terminals (s) and may also be referred to as access points, node B, or some other term.
Moreover, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified or unclear from the context, the phrase "X utilizes A or B" is intended to mean one of the natural permutations. That is, the phrase "X uses A or B" is one of the following examples: X uses A; X uses B; or X uses both A and B. Is filled with. Moreover, as used in this application and the appended claims, the articles "a" and "an" are not specified or unless apparent from the context as directed to the singular. It should be generally interpreted to mean "one or more."
The techniques described herein can be used in various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA and SC-FDMA, and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems can implement wireless technologies such as Universal Terrestrial Broadcast Access (UTRA) and cdma2000. UTRA includes wideband CDMA (W-CDMA) and other variants of CDMA. In addition, cdma2000 includes IS-2000, IS-95, and IS-856 standards. TDMA systems can implement wireless technologies such as the Global System for Mobile Communications (GSM®). OFDMA system is advanced UTRA (E-UTRA), Ultra Mobile Broadband (Ultra Mobile) Wireless technologies such as Broadband (UMB), IEEE802.20 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802.20, Flash-OFDM®, etc. can be implemented. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which utilizes OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in an organization document called the "3rd Generation Partnership Project" (3GPP). In addition, cdma2000 and UMB have announced that "3rd Generation Partnership Project 2" 2) (3GPP2) is explained in the organization's documentation. In addition, such wireless communication systems include unpaired unlicensed spectrums, 802.xx wifi, BLUETOOTH®, and any other short-range or long-range wireless communication technology. Can additionally include peer-to-peer (eg, mobile-to-mobile) ad hoc network systems that are often used.
Various aspects or features will be demonstrated in terms of systems that can include a large number of devices, components, modules, and the like. The various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. described in connection with the figures. Should be understood and recognized. A combination of these approaches can also be used.
<u style="single">the term</u> To enhance the description of this aspect, the following provides a list of some of the terms discussed.
Mobile widget or widget: A user interface (UI) element on which device end users interact; in some aspects, mobile widgets can have a particular relationship with their respective content sources. For example, a mobile widget or widget is a relatively small, specialized graphical user interface (GUI) application, which, for example, is not limited, such as clocks, calendars, news aggregators, weather information, etc. It can include software modules or combinations of graphical symbols and program code that can provide easy access to various functions or provide visual information.
Widget frame: The static user interface display area for mobile widgets.
Widget management client (WMC): A client application that illustrates and manages one or more mobile widgets.
Widget wall: The device end user sees all or some parts of a mobile widget that resides on each wireless communication device and is determined by the size of each mobile widget and the size of the view. Can be the initial view.
Widget operation modes: (i) Compressed mode: Individual widget frame for display on widget wall, (ii) Extended mode: Individual widget for display when mobile widget is selected Frames, and widget frames in extended mode, may be sized larger than their respective widget frames in compressed mode.
Mobile widget types: (i) Updatable widgets: Widgets that the underlying widget package can be updated after instantiation in the client, (ii) Locked widgets: User Cannot be modified, deleted, or rearranged, widgets; updatable, but user-free and non-updatable; (iii) dynamic Widgets: Mobile widgets with a compressed mode appearance on the UI that can be manipulated by the end user (as opposed to locked widgets), (iv) Floating widgets: Modified by the end user Mobile widgets with a compressed mode appearance that cannot be, (v) Discovery Widgets: Mobile widgets that display widget management capabilities to end users, including widget selection and widget wall management.
Widget security: (i) Trusted widget: Widget that goes through the approval process, (ii) Untrusted widget: Widget that does not go through any approval process, Can be user-defined, public domain, or from a developer.
Standalone ad widget: The optional format of locked widgets displayed on the widget wall may have content about the end user, among other things, based on other widget selections made by WMC. it can.
Widget management system (WMS): An infrastructure element for managing widget subscriptions and downloads.
Widget management portal (WMP): In one aspect, an end user-facing web tool that allows the end user to manage widgets.
Content access server (CAS): It is operational to handle the routing of metering information about end-user interaction with mobile widgets or mobile widget activity from one or more wireless communication devices, and moreover. An infrastructure element that manages to provide content updates to mobile widgets and is even more operational to search / cache the corresponding content updates from one or more content providers.
Widget wizard: A client management engine for mobile widgets.
Unified widget manager (UWM): An infrastructure element that acts as a clearinghouse for mobile widgets.
Message router: A network element to which all communication between the widget system infrastructure element and the WMC is routed.
Schedule record: A data record that provides an update schedule for widget content updates and a timetable for periodic searches of digital locker content; the digital locker is a WMS that contains end-user mobile widget information and configuration. It may be a component, for example, the schedule record may be transmitted from the WMS digital locker to the WMC.
Catalog record: Data records sent from the WMS digital locker to the WMC and WMP that provide widget catalog list mobile widgets available to the end user, such as catalog items; , Can be customized for the end user.
<u style="single">Overview</u> The described aspects relate to widgets, and more specifically, devices and methods relating to end-to-end systems for the generation, storage, distribution, and management of user-defined mobile widgets and widget-related content in a wireless communication environment. Regarding. The described aspects provide devices and methods that allow end users to customize mobile widgets. Further, the described embodiments provide devices and methods that are capable of operating efficiently in a wireless network environment with constraints on network connectivity, communication bandwidth or throughput, and wireless device memory and processing usage.
As such, the described embodiments relate specifically to "mobile" widgets optimized for wireless network environments. To understand mobile widgets, their counterparts, desktop widgets, should also be understood. Desktop widgets are essentially compact, client applications that provide specific functionality to end users through a specialized user interface. However, mobile widgets are a straightforward extension of desktop widgets, especially in some respects. It should be understood that it is not an extension). (a) Desktop widgets can easily write and leverage existing web programming technologies (especially JavaScript® and XML). In some embodiments, the mobile widget contains a compact protocol and can use a limited interpreter (eg JavaScript, etc.) due to device memory and processing power limitations; (b) Desktop widgets generally work in anticipation of consistent connections. Such consistent connections are not always viable in a wireless network environment due to inconsistent available throughput, limited cellular capacity, and specific wireless data plans, and (c) standard JavaScript (eg, standard JavaScript). , ECMAScript version, etc.) The features used by desktop widgets do not interface with those of wireless device specific APIs that can be extended to mobile widget developers. Examples of such APIs include handset power meters, location information, wireless connection status, etc. (d) In some embodiments, mobile widget accessibility can be provided in several forms. , In general, desktop widgets are directly accessible on the PC desktop. In some embodiments, the mobile widget is accessible via the wireless device application manager, while in other embodiments, the mobile widget is accessed via a particular mobile widget management application or via a network portal. It is accessible and (e) mobile widget discovery and instantiation can be controlled by the wireless device application manager, by the mobile widget management application, or by the network portal. In contrast, desktop widget discovery and instantiation is not limited to one client or one portal. Therefore, the described aspects are considered to provide mobile widget services optimized for wireless network environments.
Specifically, the described mobile widgets provide an alternative to mobile browsers for accessing content on wireless devices, custom mobile widgets for individual users to arbitrary wireless devices or web resources. Allows you to easily create.
Therefore, the described aspects provide a true replacement for receiving content via a mobile browser, and with the constraints of wireless access, wireless device capabilities, and web development in mind, the system. Address the above challenges by developing.
<u style="single">End-to-end system architecture</u> With reference to Figure 1-3, in one non-limiting aspect, the Mobile Widget System 100 is an end-to-end architecture for the generation, storage, distribution, operation, and management of mobile widgets in a wireless network environment. I will provide a.
The mobile widget 102 interacts with a content source such as Content Access Server (CAS) 900 to retrieve content for display to the device end user 104 via a user interface 702 such as a display on the device. Includes a compact application or set of code that can be executed by the wireless communication device 700. In one non-limiting aspect, for example, the mobile widget 102 extracts a data feed from a news source and corresponds to a news item or headline to allow the end user 104 to view the latest news. It may be an RSS (Really Simple Syndication) reader capable of displaying (s) (s).
However, it should be noted that the mobile widget 102 is not limited to the previous example and can have any function and include any type of content. For example, the mobile widget 102 can display any content generated by content provider 902, including text, graphics, audio, video, and multimedia content. Further, for example, the content that can be displayed by Mobile Wit 102 can include advertisements, such as from the advertisement serving platform 1000, and the advertisements may be mixed with other content or may be independent content. You may. The Advertising Serving Platform 1000 is a specialized version of Content Provider 902 that supplies advertising content to System 100, manages the placement of advertising in System 100, and relates to the use of advertising on the wireless communication device 700. Track feedback. In addition, the Advertising Serving Platform 1000 provides the Operators and Advertisers 1004 of System 100 with a virtual marketplace that allows placement and management of advertising content within System 100, such as Advertising Bidding Exchange. It is possible to make an interface connection with the negotiation component 1002.
Further, in the system 100, the wireless communication device 700 provides a platform for storing, operating and managing the mobile widget 102 for the end user 104. For example, the wireless communication device 700 can include a widget management client (WMC) 704 that is capable of obtaining one or more mobile widgets 102, such as from the widget management system 300. In addition, the WMC704 supervises mobile widget operations, tracks mobile widget activity on the wireless communication device 700, and reports such activity to the widget tracking component 1100. Can be done.
The Widget Management System (WMS) 300 is capable of communicating with the WMC704, for example via a wireless interface 106 and a message router component 500, and is available for purchase and / or download to the wireless communication device 700. Includes catalog 302 of one or more of the possible widgets 102. The WMS300 is a digital locker capable of storing the corresponding configurations of each widget 102 on each device 700 and a record of each widget 102 downloaded to each device 700. locker) 304 can be included. The widget configuration can include settings related to the operation of widget 102 and the appearance of widget 102, which includes one or more content update settings. In connection with providing access to Widget Catalog 302 and Widget 102, WMS300 provides Widget Recommendations to End User 104 with advice, suggestions, or recommendations for Mobile Widget 102 that may be useful or interesting to End User 104. Vessel 306 can optionally be included.
As described, the message router component 500 is capable of interfacing between the WMC704 and the widget and content supply components of the system 100. Specifically, the message router component 500 downloads the mobile widget 102, configures the mobile widget 102, updates the mobile widget content, schedules content updates, and has end-user interaction with the mobile widget 102. Provides an interface between WMS300 and CAS900 for exchanging messages about, or reporting data that tracks mobile widget activity. Therefore, in some embodiments, the message router component 500 defines a network element that manages and controls all communications with the WMC704.
In addition, in some embodiments, the system 100 may include a widget management portal 800 that allows the end user 104 to access the WMS 300 to inquire about the available mobile widget 102 and widget catalog 302. .. In addition, the widget management portal 800 allows the end user 104 to configure the functionality and appearance of the mobile widget 102 on the wireless communication device 700. As such, the Widget Management Portal 800 provides end users 104 with an alternative interface for mobile widget management.
In System 100, WMS300 can get Mobile Widget 102 and Widget Catalog 302 from Integrated Widget Manager (UWM) 200. The UWM200 is a controlled entry point into system 100 for mobile widget 102. Point-of-entry) is provided. Specifically, the UWM200 can ensure that each mobile widget 102 meets one or more predetermined structural and / or operational widget criteria for functioning within System 100. It may be operational. In addition, the UWM200 provides a common virtual marketplace where one or more mobile widget developers / providers 108 can deploy each mobile widget 102 to operators 110 of system 100, such as wireless network carriers. For example, the widget developer / provider 108 may submit one or more mobile widgets 102 to the UWM200 via the developer interface 202, and the operator / carrier 110 may submit the mobile widget 102 to the UWM200 via the operator interface 204. Can be accessed and reviewed, and the developer interface 202 and operator interface 204 may be network accessible interfaces such as extranets. In addition, for example, through the UWM200, one or more developers / providers 108 and one or more operators / carriers 110 can access widget virtual negotiation component 206, such as the widget bidding exchange, and mobile. Widget pricing, mobile widget operations, mobile widget content updates, mobile widget placement in widget catalogs, mobile widget billing, developer / provider compensation, or operator / carrier mobile widget costs in System 100 An agreement is reached on one or more of them.
Further, in some embodiments, the system 100 may have a back-end system 101 for analyzing data and transactions tracked within the system 100. Specifically, the back-end system 101 receives and reviews the data of the system 100, based on the analysis results of the analysis component 1200 and the analysis component 1200, operator / carrier proprietary information. It can include a reporting component 1300, which produces a report, including 1302. In addition, the backend system 101 accounts accounts for the transactions of system 100 and debits and / or one or more end users 104, developer / provider 108, operator / carrier 110, or advertiser 908. Or debits and / or credits, billing component (billing) component) 1400 can be included. For example, the end user 104 can purchase the mobile widget 102 and download it to each wireless communication device 700. This purchase transaction can be recorded by WMS300 and reported to Analysis Component 1200, which includes the transaction's expense report and the corresponding bill or invoice for that transaction. The reporting component 1300 and / or the billing component 1400 extracts relevant information about the use to generate, respectively. Accounts and billings are paid, for example, for purchases / accounts receivable that can be debited for end-user accounts and credited for operator / carrier accounts. A possible operator / carrier account, a payable developer / provider account that is credited to a developer / provider account, or an advertiser account that can be credited to an advertiser account. Can represent one or more.
It should be noted that the components and features provided by System 100 can be configured in any way. For example, the various functions of any single system component can be performed alternative by the individual system components. Therefore, it should be noted that the aspects of the system 100 may be rearranged in any of a variety of ways and further achieve the functions described above.
In addition, infrastructure components, such as the right component of wireless interface 106 in FIG. 1, can be communicatively coupled by one or a combination of wired or wireless links called the infrastructure communication network 112. .. Therefore, the infrastructure communication network 112 may be a wired network, a wireless network, or a combination of wired / wireless networks, such as LAN, WAN, PSTN, Internet, circuit switching network and / or packet switching network. Including.
Therefore, the system 100 provides an aspect of an end-to-end system for managing mobile widgets in a wireless network environment. Details of the various system components and their aspects are described below.
<u style="single">Infrastructure element / network device</u> In System 100, the network side or infrastructure element may include one or more of any type of computer device capable of performing the functions described herein, eg, network devices. it can. Specifically, network-side or infrastructure elements, including network devices, include, but are not limited to, the following system components: End User 104, Developer / Provider 108, Operator / Carrier 110, Unified Widget Manager (unified widget): manager) (UWM) 200, widget bidding exchange 230, widget management system (widget management) system) (WMS) 300, Digital Locker 304, Recommender 306, Message Router 500, Content Access Server (CAS) 900, Content Provider 902, Ad Serving Platform 1000, Ad Bidding Exchange 1002, Advertiser 1004, Widget Tracking Component 1100, Analysis Includes one or a combination of 1200 components, 1300 reporting components, 1400 billing components, and generally backend system 101.
With reference to FIG. 4, in one aspect, such a computer device or network device is represented by network device 120, which is with any other network side or infrastructure element of system 100 and /. Alternatively, it is operational to communicate with the wireless communication device 700 (Fig. 1) and / or WMC704 (Fig. 1). Network device 120 includes any type of network-based communication device, eg, a network server capable of operating on a communication network that links to components of system 100 (FIG. 1). For example, the communication network underlying system 100 (FIG. 1) may be a wired or wireless communication system, or a combination thereof, and the operator / carrier 110 (FIG. 1) on which the wireless communication device 700 operates. ) Includes a wireless interface 106, such as a wireless access network.
Network device 120 includes processor component 122 for performing processing functions associated with one or more of the components and functions described herein. The processor component 122 can include a single processor, or a multiple set of processors or a multi-core processor. In addition, processor component 122 can be implemented as an integrated processing system and / or a distributed processing system. Specifically, processor component 122, from memory, software to receive and process inputs and generate outputs that correspond to the functionality of each infrastructure element as described herein. It is operational to run a program or application.
Network device 120 stores a local version of a software program or application that contains, for example, scripts, code, algorithms, heuristics, neural networks, rules, fuzzy logic, and executable instructions executed by processor component 122. It also includes a memory 124 to do so. Memory 124 can include one or more types of random access memory (RAM), read-only memory (ROM), and combinations thereof.
In addition, network device 120 provides communication component 126 to establish and maintain communication with one or more components using hardware, software, and services as described herein. Including. The communication component 126 can carry communication between the components on the network device 120 and between the network device 120 and the external device, such as the wireless communication device 700 (Fig. 1), other network side or infrastructure. A structure element, or other device that is continuously or locally connected to network device 120. The communication component 120 includes a receiver that receives the communication and a transmitter that transmits the communication. In addition, the communication component 120 includes a corresponding receive chain component and a transmit chain component to enable exchanging messages, depending on one or more of the respective protocols.
In addition, network device 120 further includes database 128, which can be any suitable combination of hardware and / or software and is utilized in connection with aspects described herein, data. / Provides mass storage of information, data relationships, and software programs / applications.
The network device 120 may further include a user interface component 130 capable of receiving input from the user of the network device 120 and generating output for display to the user. The user interface component 130 is, but is not limited to, a keyboard, number pad, mouse, touch-sensitive display, navigation keys, function keys, microphone, voice recognition component, any other mechanism capable of receiving input from the user. , Or any combination thereof, may include one or more input devices. In addition, user interface component 130 includes, but is not limited to, a display, a speaker, a tactile feedback mechanism, a printer, any other mechanism capable of displaying output to the user, or any combination thereof. Can include one or more output devices.
Thus, the network device 120 is operational in hardware, software, or software capable of enabling it to perform one or more of the functions of the network side or infrastructure elements of system 100 (Figure 1). Includes hardware and software combinations.
<u style="single">Integrated widget manager</u> As explained above, referring to Figures 1 and 5, UWM200 provides a clearinghouse for mobile widget 102, which is system 100 by developer / provider 108 via developer interface 202. And may be managed by the operator / carrier 110 via the operator / carrier interface 204.
Developer Interface 202 provides an extranet-like access point for Developer / Provider 108 to bring Mobile Widget 102 to System 100. In some aspects, the submitted mobile widget 102 follows a trusted widget or trust according to the validation process 210 that can be performed by the widget validation component 212. Untrusted widget Widget), or each submitted widget 102 that has been denied entry to system 100 results. The validation process 210 is an automated, manual process that determines whether the introduced mobile widget 102 conforms to one or more widget system standards 216 and runs on a system designed by the developer / provider 108. , Or a combination of both. If the submitted mobile widget 102 goes through the validation process 210, each mobile widget 102 is classified as a trusted widget. In some aspects, the trusted mobile widget is a trust indicator (trust) such as a digital certificate corresponding to the UWM200 or widget validation component 212 that indicates reliability. Can have an indicator). If the submitted mobile widget 102 fails the validation process 210, or enters system 100 in another way, either through the public domain or defined directly by the user, then each mobile widget 102 Can be thought of as an untrusted widget.
In some embodiments, the developer / provider 108 represents an invalidated widget that represents the type of widget that is not trusted. In the form of package) 216, the mobile widget 102 is introduced to the system 100. Unvalidated widget package 216 can include related components that define each widget, including its operations on system 100 and its pricing. For example, in one aspect, the unvalidated widget package 216 identifies or describes the widget and / or identifies the target demographic or user attitude category to which the widget is directed, widget identifier 218. Can include. In one aspect, the unvalidated widget packet 216, each widget is personalized on a given computer platform, such as a different type of wireless communication device 700, and / or using different technologies. It can further include a widget application or code 220 that contains instructions, objects, etc. to allow it to run on a computer (PC). In one aspect, the unvalidated widget package 216 further includes a recommended update schedule 222 that defines the developer / provider 108's recommendations or recommendations when the content represented by the widget should be updated. For example, the temporary aspects of widgets may differ, and some widgets, such as stock watcher widgets, have frequent updates during market time and less after market time. The frequency widget is preferably updated, whereas the weather widget is preferably updated only a few times a day. In one aspect, the unvalidated widget package 216 includes, for example, the desired end-user price, developer / provider compensation or free or royalties, discounts, carrier-specific pricing, catalog type and slotting position. Proposed values that define one or more pricing-related and / or marketing / sales-related aspects of the widget, such as one or more of the Talog Placement considerations, etc. Attachment 224 can be further included. As each unvalidated widget package 216 goes through the validation process 210 and achieves the widget system standard (s) 214 as defined by the widget validation component 212, It can be enabled to System 100 as validated widget packages 226, which represent a type of trusted widget.
The mobile widget 102 approved by UWM200 is, for example, both developer / provider 108 and operator / carrier via the widget virtual negotiation component 206 entered via developer interface 202 and operator / carrier interface 204, respectively. Can be accessed and modified by 110. Like the developer interface 202, the operator / carrier interface 204 provides an extranet-like access point for the operator / carrier 110 to interact with the UWM200. For example, one or more operators / carriers 110 may want to include each widget in one or more widget catalogs 302 that are available to end users 104 in system 100. The mobile widget 102, or in some embodiments, the validated widget package 226, can be reviewed. Further, for example, the widget virtual negotiation component 206 allows the developer / provider 108 and the operator / carrier 110 to negotiate various aspects of each mobile widget 102 such as widget pricing, developer compensation, operator compensation, update scheduling, etc. Allows you to. In one aspect, for example, the widget virtual negotiation component 206 includes an auction function that controls and reports the results of the auction process used to agree and define the parameters corresponding to each mobile widget 102. Widget bidding exchange (widget bidding) exchange) can be included. In each case, in some embodiments, after an agreement between the developer / provider 108 and the operator / carrier 110 on the widget parameters of the final set, the mobile widget 102 is provided by the negotiated mobile widget package 228. Can be defined. For example, the negotiated mobile widget package 228 can include a widget identifier 230 that identifies or describes the widget and / or identifies the target demographic or user behavior category to which the widget is directed, and It may be the same as identifier 218, or it may be operator / carrier specific. The negotiated mobile widget package 228 can further include a widget application or code 232 with instructions, objects, etc. to allow each widget to run on a given computer platform. , And it may be the same as the widget application or code 220, or it may be operator / carrier specific. Negotiated mobile widget package 228 can further include a negotiated update schedule 234 that defines a negotiated or initially approved content update schedule, which is the same as the recommended update schedule 222. It may be operator / carrier specific. The negotiated mobile widget package 228 may further include a negotiated pricing 236 that defines the price-related and / or marketing / sales-related aspects of one or more widgets agreed during the negotiation. And it may be the same as the proposed pricing 224, or operator / carrier-developer / provider specific
Specifically referring to Figures 6 and 7, one aspect of Architecture 240 and Method 260, corresponding to the widget virtual negotiation component 206, in one unrestricted example, fulfills the auction administration obligation and results in the auction. Includes an online auction server 242 capable of interacting with the UWM200 to send. For example, the online auction server 242 is mobile for operator / carrier 110 (Figure 1), in addition to bidtable parameters associated with each mobile widget, such as pricing and placement (Auction 262 in Figure 7). It may be operational to display the widget inventory. For example, the bidtable parameters for mobile widget placements are, but not limited to, slotting placements for positions on the widget wall. Placement), a "featured" parameter that corresponds to characterizing each mobile widget on the display of the shopping mobile widget, and for each category of widgets or for each widget catalog. Can include parameters such as, slotting placement, and so on. In addition, the mobile widget displayed by the online auction server 242 provides additional targeting metadata, such as targeted demographic data or user behavior category data, to which the widget can be directed. It can have metadata). As a result, the operator / carrier 110 (Figure 1) can access the bidtable item and enter the corresponding bid (Auctions 264 and 266 in Figure 7). Based on the auction results (Action 266 in Figure 7), the UWM200 corrects the records in the corresponding Mobile Widget 102 and / or Mobile Widget Catalog 302 (Action 268 in Figure 7), and they are received by the WMS300 and are digital lockers. Updated in 304 corresponding records (Figure 7, Action 270). Therefore, as a result, such updated records are made available to the WMC 704 and the Widget Management Portal 800 to ensure that the end user 104 (Figure 1) has access to the latest information.
Further, in some embodiments, the UWM200 uses a catalog manager component 240, which is accessible, for example, through the operator / carrier interface 204, so that the operator / carrier 110 has one or more widget catalogs 302. Allows you to organize your mobile widget 102. In one aspect, for example, the operator / carrier 110 selects the widget package 228 negotiated for inclusion in one or more widget catalogs 302, which can be organized in different ways, such as by widget functionality. Further, for example, each widget catalog 302 contains a list of mobile widgets 102 that can be organized in a predetermined manner, eg, based on a given slotting placement payment. The widget catalog 302 contains a catalog record containing mobile widget metadata describing each mobile widget 102 and corresponding parameters that may be of interest to the catalog viewer, such as the name of the widget, a description of the widget function, the graphic or virtual of the widget. It can be defined by one or a combination of display, widget pricing and purchase information, etc. Further, for example, the list of mobile widgets 102 in widget catalog 302 is based on, for example, end-user priority and / or end-user behavior information and / or end-user device capabilities, after generation of widget catalog 302. different. In either case, the catalog manager component 240 further allows the operator / carrier 110 to send the widget catalog 302 to the WMS 300, making the listed mobile widget 102 available to the end user 104. ..
In addition, the UWM200 may further include a widget manager component 242 that allows the operator / carrier 110 to modify one or more parameters or features of the mobile widget 102. For example, widget manager component 242 allows operator / carrier 110 to activate or deactivate each mobile widget 102 for operation on system 100 and to set or change widget identifiers such as identifier 230. And setting or changing a widget application / code like application / code 232, setting or changing a widget update schedule like update schedule 234, and / or pricing like pricing 236 It is possible to set or change information. In one aspect, for example, the widget manager component 242 can further include an update scheduling manager 244 that specifically allows update scheduling and interaction for one or group of mobile widgets 102. For example, the update scheduling manager 244 provides end user considerations, mobile widget characteristics such as temporary aspects of content, and operator / carrier considerations. It can include logic, algorithms, heuristics, fuzzy logic, neural networks, etc. that can provide an automatic update schedule for individuals or groups of mobile widget 102 or end user 104 to take into account and / or balance. ..
Therefore, the UWM200 provides an access point and interfacing function for the developer / provider 108 to bring the mobile widget 102 to the system 100. In addition, the UWM200 provides validation functionality that authorizes mobile widget 102 for operations within System 100. In addition, the UWM200 provides a clearinghouse or marketplace that allows developers / providers 108 and operators / carriers 110 to negotiate and agree on financial and operational parameters for mobile widget 102. In addition, the UWM200 provides access points and interfacing capabilities for the operator / carrier 110 to manage the content and characteristics of the mobile widget 102 and the widget catalog 302 within the system 100.
<u style="single">Widget Management System</u> With reference to Figures 1 and 8, the WMS300 is a mobile widget 102, a widget catalog 302, and an infrastructure element that interacts with the UWM200 to get widget modifications such as changes to widget behavior or configuration information parameters. is there. In addition, the WMS300 allows end users 104 to view, select, purchase / download, and configure the mobile widget 102 via WMC804 on the wireless communication device 700 and / or via the widget management portal 800. Provides an end-user-facing interface that allows you to do this. In addition, the WMS300 is for mobile widget delivery to wireless communication devices to store and implement mobile widget configurations and subscription parameters, and to achieve, record and report on mobile widget transactions. Provides management functions for.
In one aspect, for example, the WMS300 includes a widget database 310 for storing one or more widget catalogs 302 and / or one or more mobile widgets 102. In addition, the WMS300 manages the WMC704 and / or widgets to allow end users access to the widget catalog 302 or individual mobile widgets 102 for purchase and / or download on the wireless communication device 700. It can include a subscription manager component 312 that interacts with Portal 800.
In addition, the subscription management component 312 is capable of controlling one or more subscriber records 314 in a database such as Digital Locker 304. Each subscriber record 314 includes information about each end user and information about each mobile widget 102 corresponding to each end user to allow management and control of mobile widgets for the subscriber. For example, in one aspect, the subscriber record 314 can include one or a combination of the following; used to uniquely identify a given end user 104 and / or wireless communication device 700. Can be a subscriber identifier such as name, subscriber number, phone number, wireless device serial number, etc. 316; subscription identifier, subscription description, subscription key, license, validity time Subscriber profile 326, which includes information describing the end user 104, defines demographic information for the end user 104, and / or defines behavioral information for the end user 104, and such information is the end user. It can be used for market purposes such as to recommend mobile widgets to 104 and / or to serve ads to end users 104. Thus, the WMS300 stores and controls the relationship between each mobile widget 102 and each subscriber or end user 104 in system 100 through the digital locker 302.
Optionally, the WMS300 offers a subscriber manager component 312, digital locker 304, widget database 310, widget slotting information or widget ads to suggest mobile widget 102 that may be of interest to subscriber / end user 104. May include recommender component 306 capable of interacting with other infrastructure elements such as UWM200 or CAS900 to obtain relevant information, and other entities such as marketing and / or sales data providers. it can. For example, in one aspect, the recommender component 306 collects data about available mobile widgets such as mobile widget metadata, such as subscription information 318, transaction history 324, and subscriber profile information 326. Gathering data about subscribers / end users, or collecting other internal or external information about widget popularity, widget profitability, widget sales, widget advertising, widget positioning / slotting, widget marketing, etc. A data collector module 330 can be included that is capable of performing any one or any combination of. In addition, the recommendation component 306 is a potential match (potential) between one or more of the available mobile widgets or catalogs, available subscriber / end user data, and / or external widget related information. It can include an analyzer module 332 that is capable of executing one or more algorithms, heuristics, fuzzy logic, etc. to determine matches). In addition, based on the results of analyzer module 332, the recommender component 306 is of interest to the subscriber / end user 104 and / or of the operator / carrier 110 to facilitate the subscriber / end user 104. It may further include a recommender module 334 capable of generating a message containing the identification or link or reference of one or more mobile widgets 102 or widget catalog 302 of economic interest. Therefore, the recommendation component 306 is capable of dynamically proposing or recommending the mobile widget 102 or the wit catalog 302 to the subscriber / end user 104 based on any number of configurable parameters.
In addition, in some aspects, the WMS300 will continue to track end-user 104 interactions with the WMS300 in the download / purchase of the mobile widget 102, and its back-end system 101 for spending reporting and billing purposes. It can further include a billing reporting component 340 that reports such activities. For example, the billing reporting component 340 is a transaction capable of interacting with the subscription manager component 312 and / or the digital locker 304 to collect transaction data regarding the download or purchase of the mobile widget 102 by the subscriber / end user 104. A collector module 342 can be included. In addition, reporting module 344 includes transaction details that interact with transaction collector module 342 and identify aspects of transaction-specific data such as corresponding subscriber information, mobile widget metadata, and purchase price. Documenting the collected transactions It is operational to generate a message for transmission to the back-end system 101. Therefore, the billing reporting component 340 is operational to update the backend system with billing related information.
<u style="single">Message router</u> With reference to FIGS. 1 and 9, in one aspect, system 100 provides a communication interface between network infrastructures such as WMS300, CAS900, and wireless communication devices 700 and / or WMC704, a message router (MR). ) Includes network elements such as 500. Specifically, in one aspect, the message router 500 communicates directly with the WMC704 by sending and / or receiving over-the-air (OTA) messages over the radio interface 106, and 1 Further relay those messages to the WMS300 and / or CAS900 via one or more infrastructure communication networks.
It should be noted that the wireless interface 106 between the message router 500 and the WTC704 can have a different transport protocol than the one or more infrastructure networks connecting the routers 500, WMS300, and CAS900. Should be. Therefore, in some embodiments, the message router 500 uses the protocol converter component 502 to allow the message router 500 to exchange messages between different protocols and operating devices or transport media. Can include. For example, the protocol converter component 502 can include a transform module 504 that has transform logic capable of accessing the transform database 506 to translate messages from one protocol to another. For example, the converter module 504 may send WMC-MR protocol message 508, eg, a WMC-originated message transmitted according to the protocol of wireless interface 106, to MR-infrastructure message 510, eg, the corresponding infrastructure communication network 112. It is possible to convert it into a message sent according to the protocol. Similarly, for example, the converter component 504 sends an infrastructure-originated message transmitted according to the protocol of the infrastructure-MR protocol message 512, eg, the corresponding infrastructure communication network 112, to the MR-WMC message 514, eg. It is operational to translate into a message transmitted according to the protocol of wireless interface 106. In performing such message conversion, the converter component 504 stores data and relationships corresponding to the originating device / interface 516, destination device / interface 518, and communication protocol 520, local or remote. Converted data Can act to access base 506. For example, using the conversion database 506, the converter component 504 is received from or corresponding to the origination device as defined by the data of the originating device / interface 516. It is possible to identify or determine the corresponding protocol used for the message transported on the ting interface. Similarly, for example, using conversion database 506, converter component 504 is used for messages destined for each destination device, as defined by the data for destination device / interface 518. The corresponding protocol can be determined to be transported to or on the corresponding destination interface. It should be noted that the originating device / interface 516 and the destination device / interface 518 can be combined, for example, to provide a relationship between the device and / or the interface and the corresponding protocol 520. Is. The corresponding protocol can be determined for transport on the destination interface. It should be noted that the originating device / interface 516 and the destination device / interface 518 can be combined, for example, to provide a relationship between the device and / or the interface and the corresponding protocol 520. Is. The corresponding protocol can be determined for transport on the destination interface. It should be noted that the originating device / interface 516 and the destination device / interface 518 can be combined, for example, to provide a relationship between the device and / or the interface and the corresponding protocol 520. Is.
In either case, the message router 500 is operational to transport messages in any desired protocol. For example, such protocols include Hypertext Transfer Protocol (HTTP), Internet Protocol (IP) Socket Protocol, Short Message Service (SMS) Protocol, and any wired and / or wireless network protocol, such as Code Division Multiple Access. (CDMA) -based protocols and Global Systems (GSM) -based protocols for mobile communications can be included.
<u style="single">Wireless interface</u> With reference to FIG. 1, the wireless interface 106 can be any one or a combination of various wireless communication systems. Such systems often use different spectrum bandwidths and / or different radio interface technologies. An exemplary system includes one or a combination of the wireless systems described above.
<u style="single">Infrastructure communication network</u> Referring to FIG. 1, the infrastructure communication network 112 may be any one or a combination of various wired or wireless communication systems, or a combination of both. An exemplary system includes one or a combination of any of the wired or wireless systems described above.
<u style="single">Wireless communication devices and widget-related components</u> FIG. 10 represents a high-level block diagram of a wireless device 700 capable of storing, displaying, and managing mobile widget 102 according to one aspect. As mentioned above, the wireless device can include any device that can operate on the wireless communication system. For example, the wireless device 700 is connected to a cellular telephone, cordless telephone, session initiation protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless connection function, or wireless modem. It can be embodied as another processing device. The wireless communication system may be any of a variety of systems, and it often utilizes different spectrum bandwidths and / or different wireless interface technologies. An exemplary system is CDMA (CDMA2000, EV) FDMA / TDMA (GSM®) systems using DO, WCDMA), OFDM or OFDMA (Flash OFDM, 802.11, WiMAX), FDD or TDD licensed spectrum, unpaired Includes peer-to-peer (eg mobile-to-mobile) ad hoc network systems that often use unlicensed spectrums), and 802.11xx wifi or BLUETOOTH technology.
The wireless device 700 includes a memory 706 and a processor 708 that communicates with the memory 706. Processor 708 is capable of performing processing functions associated with one or more of its components and the functions described herein. Processor 708 can include a single or multiple set of processors or multi-core processors. In addition, the processor 708 can be implemented as an integrated processing system and / or a distributed processing system. Memory 706 is capable of storing applications running on processor 708 such as mobile widget 102. Memory 706 can include random access memory (RAM), read-only memory (ROM), and combinations thereof.
Further, the wireless device 700 includes a user interface 702 capable of receiving input from the user of the wireless device 700 and generating an output for display to the user. Thus, the user interface 702 can include, but is not limited to, keyboards, number pads, mice, touch-sensitive displays, navigation keys, function keys, microphones, voice recognition components, which can include one or more input devices. Includes any other mechanism capable of receiving input from the user, or any combination thereof. In addition, the user interface 702 can include one or more output devices, including but not limited to displays, speakers, tactile feedback mechanisms, printers, and other devices capable of displaying output to the user. Includes mechanisms, or any combination thereof. In aspects disclosed herein, the user interface 702 is a touch-sensitive display capable of providing a visual display of widget 102, providing a visual display and receiving input to widget 102. , And / or a keypad that receives input to widget 102, or the like.
The memory 708 can store one, two, or multiple mobile widgets 102. As mentioned earlier, Mobile Widget 102 is an application that can run on wireless device 700 that provides users with specialized features such as content delivery via a professional user interface 702 such as a visual display. is there. In some instances, mobile widgets 102 to the web / Internet-based content that is delivered over the wireless network can provide the user access. In another example, the mobile widget 102 can provide access to device-based content, such as current battery status, current location, or the like.
In addition, memory 708 stores a widget management client (WMC) 704, including a corresponding widget manager 710, for each mobile widget application 102 stored in memory 708. The WMC704 can wirelessly obtain one or more mobile widgets 102 from a wireless communication network to supervise mobile widget operations. In addition, WMC704, specifically Widget Manager 710, may be feasible to track mobile widget activity on the wireless communication device 700 and report such activity to network components such as widget tracking component 1100. .. The widget manager 710 also provides management of the configuration of content display on the user interface 702 and management of the schedule for updating the content.
FIG. 11 provides a more detailed block diagram display of the Widget Management Client (WMC) 704 stored on the wireless communication device 700. The WMC includes one or more widget managers 710, each corresponding to a mobile widget 102 stored on the wireless device 700. The described embodiment of FIG. 11 illustrates widget managers 710-A, 710-B and 710-N, where N represents the last widget manager 710 of the plurality of widget managers.
Widget Manager 710 includes a Content Update Scheduler 712 that includes logic that can operate to update the schedule for content delivery based on one or more preformed content delivery attributes. Content delivery attributes can include, but are not limited to, widget usage, day / week / month / year time, user / device location, or the like. For example, widget use provides more frequently accessed widgets (eg, clicked widgets or similar) with more frequent content updates, while less accessed widgets provide less frequent content updates. Is provided. In another example, logic can determine at what time of the day a user is likely to access the widget, in other words, schedule more frequent content updates during that time. In addition, logic can associate content updates with locations, so more frequent or less frequent updates occur when the user / device is around the specified location. For example, if the user is in the vicinity of the stadium, the logic can be configured to provide more frequent updates for widgets related to sports information.
The content update scheduler 712 provides logic for determining update schedules based on one or more content delivery attributes, but schedules are also network priorities / factors for content delivery and / or content schedules. It should be noted that it can be based on user configuration. Therefore, content update schedule 712 provides logic to prioritize, weight, or factor content delivery based on content delivery attributes, network priorities / factors, and / or user configurations. Can be further included. In addition, each widget manager 710 allows the user to override the content update scheduler 712, or provides their own content update schedule via options in the widget management module 722 of the widget wizard 718. Can be configured. In addition, widgets can be configured through the widget management module 722 of Widget Wizard 718, with other user interfaces or buttons that allow users to request content updates instantaneously.
Widget Manager 710 also includes Widget Usage Reporter 714, which contains logic that can operate to collect and report widget usage information. FIG. 12 provides a more detailed block diagram of the widget usage reporter 714. Reporter 714 can include a usage data collector 740 capable of collecting widget usage data 742. Widget usage data is not limited, but is, for example, widget access frequency, depth of access (ie, the number of click-throughs the widget has experienced during access), the time of day / week that the widget accesses, and Similar ones can be included. The usage reporter 714 can further use the data storage 744, or optionally, the widget usage data 742 is stored in a separate data storage component external to the widget usage reporter 714 or the widget management client 704. be able to. Usage Reporter 714 is capable of compiling raw usage data into one or more usage data reports based on the reporting criteria of network operators, widget developers, and / or third parties. The reporting compiler 746 can be further included. Alternatively, in another aspect, the widget usage reporter can communicate the raw widget usage data 742 to the network.
The collected widget usage information is raw widget usage data 742 or compiled usage report 748 for network entities. For example, the widget usage data 742 can be communicated to a network entity such as the digital locker 304 of the widget management system (WMS) 300 (FIGS. 1 and 8). WMS can implement usage data 742 that determines the content update schedule of a widget in order to prioritize the widget in the user's personal widget catalog or the like. In addition, the WMS300 may communicate usage information to the back-end system 101 (FIG. 1) for reporting and / or billing purposes.
With reference to FIG. 11 again, the widget manager 710 further includes a widget-specific renderer 716, which contains logic that is capable of displaying widget 102 on the wireless device 700 based on one or more rendering attributes. Rendering attribute to the widget used, time of day / week / month / year, user / device location or similar. For example, widget usage provides more frequently accessed widgets (eg, click-on widgets, or the like) on the initial wall of the user interface or in a prominent position on the user interface. , Instruct that. In another example, the logic can determine that the date is autumn Sunday, so the football score reporting widget is on the initial wall of the user interface or in a prominent position on the user interface. It may be supplied. The widget-specific renderer 716 provides logic to determine where the widget should be rendered on the display, and the renderer 716 can also override or enhance the rendering decisions made by the logic. It should be noted that it is possible to provide a user configuration for.
WMC704 is a widget user like Widget Wizard 718 that can operate to provide users with an interface where widget 102 can be stored and displayed on wireless device 700 and an interface to buy or get widgets from the marketplace. Includes interface. In addition to wireless device-based user interfaces like Widget Wizard 718, System 100 will change to configuration settings and buy / get more widgets, or else it will be displayed on the wireless device. To manage widgets, the network-based user widget management portal 800 (Figure 1) can be included, which allows device users to access the network from another wired or wireless device such as a PC or similar. Provide for.
The Widget Wizard 718 can include a Widget Processing Module 720 that can operate to provide the user with management on the widgets displayed on the user interface 702. In addition, the Widget Wizard 718 can include a Widget Catalog 722 that can operate to provide the user with a current list of widgets currently available from a network operator or some other network source. Figure 13 provides a detailed block diagram of the various components of Widget Wizard 718, including Widget Processing Module 720 and Widget Catalog 722. The widget management module can provide widget list 750, which provides a display of the list of widgets 102 currently stored on the wireless device. Listing 750 provides the user with an instantaneous update of the user interface with the selected widget. In this regard, the user can momentarily deactivate the currently displayed / displayed widget and replace it with another widget stored on the device. In addition, the widget management module 720 provides a widget configuration module 752 that is operational to provide widgets for the user to configure based on individual priorities. The widget configuration module 752 can operate with a content update schedule configuration 754 that allows the user to define how often each widget is provided with content updates, as well as the position on the display, the size of the widget, or the like. It can include a content rendering configuration 756, which can operate to provide the user with the ability to define how widgets are rendered / displayed on the user interface, such as the one. When the user changes the configuration settings in configuration module 752, the widget wizard 718 uploads and is
The Widget Wizard can further include a Widget Catalog 722 that provides a Widget List 758 of widgets currently available from network sources. The list of widgets in the catalog can be updated periodically based on a set schedule or user input to guarantee the currency of the widgets available to the user. Catalog updates or initial reception can be provided by WMS300. In addition, Listing 758 can be customized for the user based on previous widget usage patterns, or other attributes such as time, location, or the like.
In some embodiments, the advertising widget can optionally be displayed to the client via the widget catalog 722. In some aspects, advertising widgets mean of It can be provided to the user as a subsidizing) or as a means of replacing the cost of other widgets. If the widget management client 704 is configured to provide a display of the advertising widget, the advertising widget may be a "locked" widget, which otherwise the user It should be noted that it allows you to manage or configure widgets through the Widget Wizard 718. By locking the ad widget, the network operator and / or advertiser ensures that the ad is displayed / displayed without the user, otherwise he chooses to deselect the ad widget. Further, in those aspects of providing advertising widgets, the widget usage reporter 714 is of interaction-related usage data that allows the user to experience an advertisement, such as the time viewed or the depth of access of the advertisement. It can be configured to supply specific collections and reports.
With reference to FIG. 11 again, the WMC704 further includes an update controller 724 and an update adapter 726. The update controller 724 can operate to control the upstream data delivery to the WMC704 and the downstream data delivery from the WMC704. For example, update controller 724 operates to control the delivery of usage data 742 or usage data report 748 to network entities, widget configuration settings, and / or user requests to purchase / obtain new or updated widgets. be able to. In some embodiments, the update controller 724 can act to collate the data and provide it to an entity such as the Widget Management System (WMS) 300. In addition, the update controller 724 can operate to receive widget content updates, updates to the widget catalog 722, configuration settings for the content update schedule, content reporting requests, or the like.
In addition, update adapter 726 is capable of handling the upstream and downstream transport of data from the WMC704 to the appropriate network entity. In this regard, the update adapter 726 is on a specified type of network connection, such as an Internet Protocol (IP) socket, Hypertext Transfer Protocol (HTTP) socket, Short Messaging Service (SMS) or the like. It is operational to receive / transmit data. In addition, the update adapter 726 works to compare the existing configuration of the widget with the WMS pushed configuration and make changes to the configuration accordingly, eg, instantiate a new widget and / or de. Disable the activated widget.
The WMC704 can further include a throughput sensor 728, which is capable of sensing throughput time and estimating the time to download content for widgets. Throughput sensor 728 can operate to be engaged when opening WMC704, and proper throughput time can be detected by establishing an IP connection and measuring round trip time (RTT). it can. Based on the approximate throughput time and size of previous content updates for the widget of interest, estimates are established when the widget is updated and can be provided to the user when the user requests an update. .. In addition, the throughput sensor 728 can be configured to warn the user if the content update takes longer than a predetermined threshold of time.
The WMC704 can further include a subscriber ID / credit certificate determinant 730 that is capable of determining the subscriber / user identification information associated with the WMC704. In one aspect, the subscriber ID determinant 730 can initiate an HTTP call and the response header can include subscriber identification information. In an alternative embodiment, the subscriber identity determinant can be derived from a wireless device or the like. In addition, the subscriber ID / credit certificate determinant 730 can be configured to determine the subscriber / user credentials by prompting the user to enter an appropriate credential, eg, a user id. Based on the input, the user credentials are compared with the subscriber identification, and if a match is determined, an acknowledge report can be communicated to the WMS300 and the subscriber / user Records are created in Digital Locker 304 associated with. Subsequently, the subscriber ID and subscriber credentials can be included in all messages communicated from the WMC 704 to the message router 500.
As mentioned above, in addition to configuring the widget management client (WMC) 704 and associated mobile widget 102 on the wireless device, the system provides a user widget management portal 800. User Widget Management Portal 800 allows users 104 to access components through another device, such as a wired PC or another wireless device, to manage (WMC) on the wireless device 700. To do. The user widget management portal 800 communicates network with the widget management system (WMS) 300, and the WMS 300 wirelessly communicates with the wireless device 700 via the message router 500. The User Widget Management Portal 800 acts as a complement to the Widget Wizard 718 on the wireless device 700 by providing user 104 with remote access to managing widgets on the wireless device. The User Widget Management Portal 800 is capable of receiving information related to the user's current WMC704 or Widget 102 configuration from the user's profile stored in the WMS300's Digital Locker 304. As such, the User Widget Management Portal 800 can include the WMC Configuration Module 810, which is capable of providing user 104 with the ability to reconfigure settings that generally apply to the entire WMC704. In addition, the User Widget Management Portal 800 may include one or more Widget Configuration Modules 820 capable of providing User 104 with the ability to reconfigure widgets 102 currently stored on the wireless device 700. it can.
In addition to WMC and widget configuration, User Widget Management Portal 800 can provide users to learn and / or acquire new widgets. Therefore, the user widget management portal 800 can include the widget catalog 302 so as to be communicated by the widget management system 300. In addition, the widget catalog 302 can be customized for user 104 so that the widgets of interest to user 104 are listed in the catalog near the beginning or otherwise highlighted. The widget of interest can be identified by the WMS300 based on the widget usage tracking / metering data communicated from the wireless device 700. Once the user selects, acquires, or purchases a new widget, the User Management Portal 800 communicates the selection to the WMS300, which WMS300 retries the widget from the corresponding Content Access Server 900 (Figure 17). Then, the widget is communicated to the wireless device via the message router 500.
<u style="single">Content Access Server / Content Ad Tracking Component</u> With reference to FIG. 17, a detailed block diagram highlighting the Content Access Server 900 is illustrated. The content access server 900 is capable of supplying content to the mobile widget 102 based on a predetermined update schedule for the widget. As mentioned above, the update schedule can be logically determined based on one or more content delivery attributes, network attributes, and / or user configuration settings. The mobile widget 102 will initiate a content request 904 based on an update schedule, which is wirelessly received by the content access server 900 via the message router 500. Content Access Server 900 will work request 904 by searching for current content from content provider 902 or in the case of ad serving platform 1000 communicating with the ad source. Once a content update is searched, the update is communicated to the wireless device for display on the corresponding widget. For example, if the mobile widget is a sports event score reporting widget, the request can be sent to a content access server, such as a web-based sports news site or the like. You can search for content updates in the form of sporting event scores updated by content provider 902. In one aspect, the Content Access Server 900 can include a Content Package Bundler 910 capable of bundling updates with a Content Update Package, such as a file / zip file or other spectrally efficient compression mechanism. .. Bundling content updates in a package provides smaller messages that can be delivered more efficiently to wireless devices. Content update is a wireless device Depending on the connections available in, the wireless device can be communicated over different connections. Examples of connections can include, but are not limited to, HTTP sockets, IP sockets, SMS and the like.
In addition to providing content updates, the Content Access Server 900 serves as a receiving point for metering / tracking data communicated from the WMC704. In some embodiments, the content update request 904 may include metering / tracking data such as widget usage data 742 or widget usage report 748. In such an embodiment, the Content Access Server 900 parses widget usage data 742 or widget usage report 748 from the request and routes metering / tracking data to content provider 902 or reporting serving platform 1000. Includes a metering / tracking component 1100 that can operate. In addition, the content access server can communicate metering / tracking data to the backend system 101, which receives the metering / tracking data and logically determines usage patterns or the like. Includes a workable analysis component 1200 to do. The analytic data is subsequently communicated and used by the reporting component 1300, which produces a pre-determined report, and by the billing component 1400, which generates widget bills such as widget billing based on widget usage rate. Can be done.
As described above, one or more widgets stored and displayed on the wireless device 700 can include advertising widgets that are capable of displaying ads in the form of widgets. In some embodiments, as a selection feature, the advertising widget may be provided by the widget operator, where instead of some form of compensation, such as a reduction in the cost of other non-advertising widgets or the like, advertising widgets. The user is provided with the option to choose to accept. Therefore, the advertising widget can be configured to be the widget provider associated with the advertiser as a "locked" widget, which makes it impossible for the user to reconfigure the widget. Or, it means deactivating the widget on the wireless device. FIG. 14 provides a block diagram of an example of widget ad 1010, and more specifically, ad metadata 1012 contained in such an ad. Metadata 1012 provides an ad identifier 1014, such as an id number that services to identify an ad, and a resource location identifier 1016, which services to identify the source of an ad, such as an IP address or the like. Can include. Metadata 1012 may further include associated interaction 1018, which may include user interaction with the advertisement, such as click-to-browsing capabilities or the like, and / or users other than click-to-browsing. Service to define the landing location 1020, which defines the URL location for the interaction. In another aspect, the metadata 1012 defines a time to live (TTL) for an ad on a wireless device. Live) 1022 can include a display metric time / frequency of 1024, which specifies a particular time and / or frequency at which the advertisement should be displayed on the wireless device. In addition, the metadata 1102 defines the context display metric 1026, which defines other context parameters for the display of the advertisement, and the metric for the display of the advertisement, which is collected by the wireless device and subsequently communicated to the network. For example, the wireless device metric collection instruction 1028, which defines the time / frequency of the display, the frequency of user interaction with the advertisement, the depth of click-through, and the like, can be included. The metadata 1012 may further be the advertisement 1010, any other metadata 1012 relating to the display or reporting capabilities of the advertisement on the widget.
As shown in the block diagram of FIG. 15, the ad 1010 is wirelessly communicated to the ad widget 102-1 on the wireless device 700 via an ad source such as the ad serving component / platform 1000. Since the advertisement serving platform 1000 communicates with the content access server 900, the advertisement 1010 is communicated from the advertisement serving platform 1000 to the wireless device 700 through the content access server 900. In addition, the message router 500 communicates with the content access server 900 and uses an integrated communication protocol to provide advertisements and related information from and to the wireless device over the wireless network 106. Provide services to ensure that they are communicated. The ad serving platform communicates with the ad database 1040, which stores an inventory of ads 1010. Therefore, the ad serving platform operates to search the ad 1010 from the database 1040 and communicate the ad to the ad widget 102-1 on the wireless device.
Further, similar to the content update request as described above, the wireless device can issue an advertisement request 1040 which can act to request the delivery of an advertisement for displaying the advertisement on the wireless device. .. The ad request is received by the ad serving platform 1000 and gets the ad from the ad database 1040. The advertising request can include an identifier issued by the advertising serving platform 1000 that identifies the WMC704. The request also includes a metering / tracking report that identifies the number of recently viewed ads and the number of views between TTLs.
In addition, the ad serving platform 1000 can further include an ad campaign manager 1050 capable of managing ad campaigns for advertisers by communicating ads to ad widgets based on ad campaign standards. .. Advertising campaign criteria can dictate that a particular ad will be pushed to a wireless device that has a display rate frequency and expiration date associated with the advertising campaign. In other aspects, advertising campaigns can target specific demographic information about users, or specific wireless devices, so that specific advertising can be targeted at users and / / within target audience confines. Or target wireless devices. Demographic information includes, but is not limited to, user gender, user interests, user income, user age, user address, location of currently used / wireless devices, and the like. be able to.
The ad serving platform 1000 may further include a tracking / metering component 1060 that tracks and meters information related to the display of the ad on the user ad widget. The tracking / metering component 1100 can parse out those metering and tracking data specifically related to ad 1010 and ad widget 102-1, against the tracking / metering component 1060 of ad serving platform 1000. Can communicate advertising-related metering and tracking information. Tracking / metering data communicated from WMC704 includes ad identifiers, number of displays / displays on ad widgets, depth of user interaction (eg, number of click-throughs), elapsed time of user interaction / viewing of ads and similar. Can include things.
The ad serving platform 1000 also communicates with the ad bidding exchange server 1002, which can act to allow an ad bidding marketplace to occur between the advertiser 1004 and the network / widget operator 110. There is. The Bidding Exchange Marketplace is based on one or more ad criteria, such as ad position / placement on the widget wall, display frequency, display time, target audience demographics, and the like. Widget ads can be provided for Advertiser 1004 to bid on. In addition, the Bidding Exchange Marketplace can provide advertisers to bid based on the broadcast and / or multicast display of ads in the widget. In one aspect, a bidding exchange marketplace is a publicly available marketplace, such as an internet-based marketplace, that allows all advertisers or potential advertisers to bid on widget-based ads.
<u style="single">Backend system</u> With reference back to FIG. 1, in some embodiments, the system 100 may have a back-end system 101 for analyzing tracked data and transactions within the system 100, as described above. The back-end system 101 can include one or a combination of analysis component 1200, reporting component 1300, and billing component 1400.
The analysis component 1200 receives and reviews the data of the system 100.
The reporting component 1300, according to one aspect, generates a report containing the operator / carrier owner information 1302 based on the results of the analysis of the analysis component 1200.
In one example, billing component 1400 reports spending on transactions in system 100 and credits and / or debits to one or more end users 104, developers / providers 108, operators / carriers 110, or advertiser 908. Fill in.
<u style="single">Sample call flow</u> With reference to Figure 18-23, some unrestricted examples of calls or messages are listed for the various scenarios, according to some aspects. Referring to FIG. 18, for example, in one aspect, the high-level call flow relates to the widget management portal (WMP) -originated selection and configuration of new mobile widgets. In particular, the WMP1801 interacts with the WMS300 to select and configure mobile widgets. WMS300 interacts with CAS900 to get content for mobile widgets. In addition, the WMS300 forwards content updates for mobile widgets and / or mobile widgets to the WMC704 via a message router.
Referring to FIG. 19, for example, in one aspect, the high level call flow relates to WMC-originated selection, configuration, and update of mobile widgets. Specifically, the WMC704 interacts with the WMS300 to select and configure mobile widgets. WMS300 interacts with CAS900 to get content for mobile widgets. In addition, WMC704 requests a content update for the mobile widget from CAS900, and CAS900 responds to the updated content, which WMC704 confirms receipt.
Referring to FIG. 20, for example, in one aspect, the high level call flow relates to the WMC704 accessing the webstore front in the WMS300, where the operator / carrier 110 grants access. Specifically, the WMC704 requests access to the storefront from the WMS300, which verifies to the operator / carrier 110 that the WMC704 is authorized for such access. For example, verification receives an identifier or credential associated with the WMC704 or end user to the operator / carrier's content management server or authorization server to determine if the WMC is authorized. Can include passing. Once licensed, the WMS300 can provide the WMC704 with access to the storefront and allow subsequent interaction for mobile widget downloads.
Referring to FIG. 21, for example, in one aspect, the high level call flow relates to content updates requested by the WMC. Specifically, the WMC704 sends a content update request to the CAS900 via the message router 500 based on the occurrence of the content update event. The CAS900 bundles the corresponding content updates and sends them to the WMC704 via the message router 500. In one example, it should be noted that content update requests can be user initiated, rather than event driven. It should also be noted that the WMC704 can package metering / tracking data with content update requests. In this case, the CAS900 is capable of routing metering / tracking data to other infrastructure elements such as the analytics component 1200 and / or the advertising serving platform 1000 of the backend system 101.
Referring to FIG. 22, for example, in one aspect, the high level call flow relates to reporting widget metering / tracking data and corresponding adjustments to the widget update schedule based on the reported metering / tracking data. Specifically, the WMC704 transmits a widget message including metering / tracking data to the CAS900 via the message router 500. The CAS900 is in this case capable of routing metering / tracking data to other infrastructure elements such as the analysis component 1200 and the reporting component 1300. Analysis component 1200 and reporting component 1300 determine usage data based on reported metering / tracking data, and it is against WMS300 and / or UWM200 for use in determining content update schedules. Supplied as an input. Based on its usage data, new update schedules are determined for one or more users and / or one or more mobile widgets. The new update schedule is stored on the WMS300 and / or UWM200 and is further communicated to the WMC704 via the message router 500. Therefore, the new update schedule will be achieved based on the analysis of the reported metering / tracking data provided by WMC704.
Referring to FIG. 23, for example, in one aspect, the high level call flow relates to a CAS that provides content updates to the WMC. Specifically, the CAS900 sends a content request to the content provider 902 that responds with the content document. Content documents can also contain various updated content, as well as references to resources for content updates. The CAS900 parses the content document and requests additional resources from the content provider 902 if needed. Upon receiving the requested resource, the CAS900 transforms the resource and other content from the content document into an update package for delivery to the WMC704. Upon completing the conversion, the CAS900 forwards the content update packet to the WMC704 via the message router 500.
<u style="single">Transport optimization</u> Described embodiments such as CAS900 can be configured to be as efficient as possible in content delivery, as the radio throughput of wireless interface 106 can be limited and variable. Efficient content delivery is even more desirable when several different transport mechanisms (eg SMS, HTTP (web) connections, IP sockets, etc.) are used for the service.
In some embodiments, the compact protocol can be utilized to support widget content delivery. For example, unlike web browsers, where the full URL is usually sent upstream when the user wants to navigate to a particular web source, the mobile widget service is a simple widget when content updates are desired. An identifier can be sent. In addition, the widget package is flattened and encoded, thus allowing efficient transmission of widget scripts over the air.
In one aspect, for example, data compression can be utilized for transfer optimization. Many of the mobile widget content feeds are delivered in the form of XML files, which are ASCII-based and therefore lossless compression algorithms, such as the Lempel-Ziv algorithm and the Lempel-Ziv-Welch algorithm, without limitation. , Lempel-Ziv-Markov algorithm, arithmetic algorithm, and Hoffman algorithm, highly compressed. In addition, the computational efficiency of data compression is improved by using schema-aware compression, which separates the underlying structural schema, such as XML Schema, from the information to be compressed. Can be done.
In addition, delta compression schemes can be used to further improve efficiency in transporting content about updates, especially if updates are provided multiple times a day. For example, consider the RSS feed XML page on the New York Times website. An 8.74kB source file can be compressed to 2.73kB using a data compression scheme. However, if you assume that only one news item has changed from the previous update, for example, resending all the files will be avoided and instead enough to update the previous file. Only metadata can be sent. Therefore, in one aspect, only the delta content update is sent, and the delta content update represents the difference between the previous content update and the current content update. The advantage in this case is decompression in wireless communication devices. Computation) is to be reduced. In another aspect, the data compression scheme can be applied to delta content updates to further reduce its size. In this case, for example, one delta item from an RSS feed may be 633 bytes, which can be further compressed by a data compression scheme such as size 499 bytes.
A hybrid compression scheme refers to any scheme that combines different modes of compression. For example, one hybrid compression technique combines data compression and delta compression. Another hybrid compression scheme, for example, combines schema-aware compression with delta compression. It should be noted that many other possible combinations of compression schemas are possible.
With reference to FIGS. 24-26, in one aspect, the devices and methods for the transfer of mobile widget content are further optimized by considering widget depth, or widget level or layered content interaction. In one aspect, widget depth refers to the number of clicks from the widget wall to the widget that are possible before the user's experience within the widget ends. Increasing the widget depth seen by the end user can result in improved spectral efficiency, such as improved capacity or bandwidth use of wireless interface 106 (FIG. 1). Events that can terminate the user's experience in the widget are (a) no further views within the widget are available, or (b) the browser to view further content. Is that the user is moved to another application such as. Event (b) can be particularly problematic if the user is unable to transition back to the widget experience from another application. For example, different widget depths for popular news site RSS feed widgets are shown in Table 1. In some described embodiments, it is desirable to allow a third click, which is usually required for WAP articles to be displayed within the widget experience. Providing such widget depth within the mobile widget experience can allow greater flexibility in compression, as standardized web compression can be limited.<tables num="1"><img file="JP4976585B2_D0001.tif" /></tables>
In addition, user preferences for widget navigation can be tracked and stored, thus enabling efficient information distribution. For example, if the user is observed interacting with the widget only at depth 2, content updates can be provided without supporting WAP articles.
Thus, in one aspect, the CAS200 is operational to receive user navigation pattern history data 901 tracking one or more widget depths 903 corresponding to user interaction with one or more mobile widgets 102. be able to. For example, user navigation pattern history data 901 can be part of metering / tracking data 905 collected by WTC704 and transferred to CAS900. In addition, the CAS200 may be operational to receive updated content 944 from content provider 902, where the updated content 944 is one or more widget depths 903 of each mobile widget 102. Contains one or more content portions 907 corresponding to.
In addition, the CAS900 content update package Bundler 910 supports access to user navigation pattern history data 901 and one or more of the recorded user interaction distributions with each mobile widget 102. (For example, in the figure, 1 to n, where n is an integer) includes an analyzer module 911 capable of determining data ranges 913, 915. The analyzer module 911 can include one or a combination of logic, fuzzy logic, heuristics, algorithms, neural networks, etc., which is set by the operator / carrier 110 (Figure 1) or another party. It is possible to determine how often the end user 104 (Figure 1) interacts with different widget depths, and to one or more depth ranges 913, 915 in a way that makes efficient use of the wireless interface 106. Separate such interactions.
For example, in one optional aspect, the CAS900 or content update package bundler 910 can utilize the results of analyzer 911 to initiate sending content update message 945 to the wireless device 700, and yet The content update message 945 includes a first portion 907 of the updated content 944 corresponding to the first information hierarchy depth range 913, based on the user navigation pattern history data 901. For example, referring to Table 1, if the user is observed interacting with the widget only at depth 2, the content update message 945 provides the first part of the updated content 944 corresponding to depth 2. The update message, for example, may contain a list of individual articles and articles with signatures, but may not include supporting WAP / HTML / XHTML articles. Similarly, the subsequent content update message can include a second part of the updated content 944 that corresponds to the second information hierarchy depth range based on the user navigation pattern history data 901, eg, the example in Table 1. Subsequent updates can only include supporting WAP / HTML / XHTML articles, thereby supplementing previously sent content update message 945.
In addition, the content update package bundler 910 can include a compression module 919 capable of applying the compression scheme 921 to the updated content 944. The compression scheme 921 may include any one or a combination of compression schemes such as those described above. In particular, based on the results of analyzer module 911, compressor module 919 to generate one or more compressed content parts 923,925 (eg, 1 to n in the figure, where n is an integer). It is operational to apply the compression scheme 921 to one or more content portions 907 corresponding to one or more widget depth ranges 913, 915. For example, each compressed content portion 923 and 925 follows delta compression, data compression, or both delta compression and data compression. Therefore, when the CAS900 updates the content for each mobile widget 102, one or more compressed content portions 923, to optimize transport efficiency, based on the user navigation pattern history data 901, It is operational to send the 925 individually to the WMC704.
For example, in one optional aspect, the CAS900 or content update package bundler 910 can utilize the results of the compressor 919 to initiate sending content update message 947 to the wireless device 700. Note that the content update message 947 includes a first compressed portion 923 of the updated content 944 corresponding to the first information hierarchy depth range 913, based on the user navigation pattern history data 901. For example, referring to Table 1, if the user is observed interacting with the widget only at depth 2, content update message 947 is the first compressed content of updated content 944 corresponding to depth 2. Part 923 can be provided, for example, the update message is a list of articles. Articles), including compressed versions of individual articles with signatures, but will not include supported WAP / HTML / XHTML articles. Similarly, the subsequent content update message can include a second part of the updated content 944 that corresponds to the second information hierarchy depth range based on the user navigation pattern history data 901, eg, the example in Table 1. Subsequent updates can include only supported WAP / HTML / XHTML articles, thereby complementing previously sent content update message 947.
Referring to FIG. 25, in one aspect, a method 610 that can operate on a network device for updating content for a mobile widget has updated content corresponding to a mobile widget with multiple widget depths at 612. Including getting. For example, the updated content can be collected from the content provider, and the updated content can have a large number of content portions, each corresponding to a large number of widget depths of the corresponding mobile widget. In some optional embodiments, the updated content comprises a first size, as shown in parentheses in 612.
The method further comprises obtaining user navigation pattern history data corresponding to the mobile widget, and the user navigation pattern history data corresponds to a plurality of widget depths in 614. For example, user navigation pattern history data can be received from a widget management client on a wireless device running each mobile widget. Further, the user navigation pattern history data can correspond to one user or a plurality of users operating the same mobile widget. Further, the user navigation pattern history data can define user interaction with each widget depth of each mobile widget.
The method also includes obtaining a first widget depth range for inclusion in the first content update message, where the first widget depth range is based on user navigation pattern history data at 616. For example, the first widget depth range analyzes user navigation pattern history data, determines how often each widget depth is accessed, and divides the widget depth into ranges based on the frequency. Can be determined based on.
Optionally, at 618, as shown by the dotted line, the method reduces the size of the first part of the updated content corresponding to the first information hierarchy depth range, depending on the compression scheme. Further includes defining a first compressed portion of updated content having a second size smaller than the first size. For example, the portion of content that corresponds to the first range of widget depth can be identified, and then compression techniques such as delta compression, data compression, or a combination of both are applied to it. ..
In addition, the method involves wirelessly transporting the first (optionally compressed) portion of the updated content in the first content update message to a wireless communication device that supports mobile widgets (block 620). ). For example, to make efficient use of wireless bandwidth when updating one or more mobile widgets, the most frequently reviewed portion of the updated content is sent first, and the rest of the content , Will be sent later, and will only be sent on request.
Referring to FIG. 26, in one aspect, a method 630 that can operate on a wireless device for updating content for a mobile widget comprises storing the mobile widget on a wireless communication device. The mobile widget is 632 and has multiple widget depths. For example, mobile widgets can be downloaded from the wireless network operator's widget management system.
Further, the method includes tracking the user navigation pattern corresponding to the mobile widget to define the user navigation pattern history data, and the user navigation pattern history data is 634, to multiple widget depths. Correspond. For example, a widget management client on a wireless device running each mobile widget can track user interaction with each widget depth for each widget.
The method also includes transferring user navigation pattern history data to the network device associated with the content source in 636. For example, a widget management client on a wireless device can operate to transfer this information to a network device, such as content access or another device interested in such data.
Further, the method comprises wirelessly receiving the first (optionally compressed) portion of the updated content in the first content update message from the content source at 638. In this case, in one aspect, the first portion of the updated content corresponds to the first widget depth range of the mobile widget based on the user navigation pattern history data. Also, in another aspect, the first part of the updated content is compressed according to the compression scheme and is therefore smaller than the first size of the corresponding first decompressed part of the updated content. It has a second size. For example, to make efficient use of wireless bandwidth when updating one or more mobile widgets, the most frequently reviewed portion of the updated content is sent first and the rest of the content. Can be sent later or only on request.
Returning to Figure 27, System 2000, which updates content for mobile widgets, is illustrated. The system 2000 can reside, for example, in a multiplexer, transmitter, mobile device, and the like. As illustrated, the system 2000 includes functional blocks that can represent the functionality implemented by the processor, software, or a combination thereof (firmware). System 2000 includes logical grouping 2002 of electronic components that facilitates updating content for mobile widgets. Logical grouping 2002 can include means 2004 for obtaining updated content corresponding to mobile widgets with multiple information hierarchy depths. Further, the logical grouping 2002 can include means 2006 for obtaining the user navigation pattern history data corresponding to the mobile widget, and the user navigation pattern history data corresponds to a plurality of information hierarchy depths 2006. Further, the logical grouping 2002 can include means 2008 for obtaining a hierarchical depth range of the first information for inclusion in the first content update message, yet the first information is hierarchical. The depth range is based on user navigation pattern history data. Logical grouping 2002 can also include means 2010 for generating a first content update message in the first part of the updated content corresponding to the hierarchical depth range of the first information. In addition, system 2000 can include memory 2011, which holds instructions for performing functions associated with electronic components 2004, 2006, 2008, and 2010. Although shown as being outside of memory 2011, it should be understood that electronic components 2004, 2006, 2008 and 2010 can be inside memory 2011.
See FIG. 28, a system 2012 that updates content for mobile widgets on wireless communication devices. System 2012 can reside, for example, within a multiplexer, transmitter, mobile device, and the like. As illustrated, system 2012 includes functional blocks that can represent functionality implemented by a processor, software, or a combination thereof (eg, firmware, etc.). System 2012 includes Logical Grouping 2013 of electronic components that facilitates updating content for mobile widgets on wireless communication devices. Logical grouping 2013 can include means 2014 for storing mobile widgets on wireless communication devices, where mobile widgets have multiple layers of information depth. In addition, Logical Grouping 2013 can include means 2016 for tracking user navigation patterns corresponding to mobile widgets to define user navigation pattern history data, where the user navigation pattern history data is here. , Corresponds to multiple information hierarchy depths. In addition, Logical Grouping 2013 can include means 2018 for transferring user navigation pattern history data to network devices associated with content sources. In addition, Logical Grouping 2012 can include means 2020 for wirelessly receiving the first part of the updated content in the first content update message from the network device, where it is updated. The first part of the content corresponds to the hierarchical depth range of the first information in the mobile widget, based on the user navigation pattern history data. In addition, the system 2012 can include a memory 2022 that holds instructions to perform the functions associated with the electronic components 2014, 2016, 2018 and 2020. To. Although shown as being external to memory 2022, it should be understood that electronic components 2014, 2016, 2018 and 2020 can exist within memory 2022.
The logic, logic blocks, modules and circuits for various purposes described in connection with the embodiments disclosed herein are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), fields. Implemented in programmable gate arrays (FPGAs), or other programmable logic circuits, discrete gate or transistor logic, discrete hardware components, or any combination of them designed to perform the functions described herein. Or can be executed. The general purpose processor may be a microprocessor, but instead, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor is also a computing device. Devices) combinations, such as DSP and microprocessor combinations, multiple microprocessors, one or more microprocessors in combination with DSP cores, or any other such configuration. You may. In addition, at least one processor may include one or more modules capable of performing one or more of the steps and / or operations described above.
Moreover, the steps and / or operations of the methods or algorithms described in connection with the aspects disclosed herein are embodied directly in hardware, in software modules executed by the processor, or in combination of the two. Can be transformed into. Software modules reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. be able to. The exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. Further, in some embodiments, the processor and storage medium may reside in the ASIC. Further, the ASIC may be resident in the user terminal. Alternatively, the processor and storage medium may reside as discrete components in the user terminal. Moreover, in some embodiments, the steps and / or operations of the method or algorithm are code and / or instructions in one or a combination, or set, on machine-readable and / or computer-readable media. As can exist, and it can be incorporated into computer program products.
In one or more embodiments, the described functionality can be implemented in hardware, software, firmware or any combination thereof. When implemented in software, features may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication, including any medium that facilitates the transfer of computer programs from one location to another. Includes both media). The storage medium may be any available medium that can be accessed by a computer. As an example, and without limitation, such computer-readable media are RAM, ROM, EEPROM, CD-ROM or other optical disc storage, magnetic disc storage or other magnetic storage device, or in the form of instructions or data structures. It can also be provided with any other medium that can be used to store or carry the desired program code in, and that can be accessed by a computer. Also, both connections are properly named computer-readable media. For example, the software may be a website, server, or coaxial cable, fiber optic cable, twisted pair, digital subscriber line. Coaxial cable, fiber optic cable, twisted pair, DSL, or infrared, when transmitted from line) (DSL), or other remote sources using wireless technology such as infrared, wireless, and microwave. Radio and radio technologies such as microwaves are included in the definition of medium. As used herein, discs and discs are compact discs (CDs), laser discs, optical discs, digital general purpose discs. Includes digital versatile discs (DVDs), floppy (registered trademark) discs and blu-ray discs, although discs usually play data magnetically. , Discs are optically regenerated with a laser. Combinations of the above should also be included within the scope of computer readable media.
The above disclosure describes aspects and / or embodiments of the description, but described aspects and / or embodiments as various modifications and amendments are defined by the appended claims. It should be noted that it could be done here without departing from the scope of the embodiment. In addition, the elements of the described embodiments and / or embodiments may be described or claimed in the singular, but the plural is intended unless restrictions to the singular are explicitly stated. ing. Moreover, all or part of any other aspect and / or embodiment may be utilized with all or part of any other aspect and / or embodiment unless otherwise stated.
29 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
Every citation, both waysCites: the store holds 3 of 4
| Document | Relation | Office |
|---|---|---|
| JP2005228228A | Cites | Japan |
| WO01097014A1 | Cites | World Intellectual Property Organization (WIPO) |
| JP2001243161A | Cites | Japan |
| 下屋鋪 太一,モバイル端末用リアルタイムウィンドウシステム「EMiRea」とそのウィジェット管理,ヒューマンインタフェース学会研究報告集,日本,ヒューマンインタフェース学会,2004年11月 5日,Vol.6 No.4・5,p.37~42 | Non-patent | – |
93 members in 9 offices
Priority claims14
| Document | Office | Kind | Date |
|---|---|---|---|
| 3940208 | United States of America | P | |
| 3940208 | United States of America | P | |
| 61039402 | United States of America | – | |
| 12407583 | United States of America | – | |
| 40758309 | United States of America | A | |
| 40758309 | United States of America | A | |
| 2009037790 | United States of America | W | |
| 2009037790 | United States of America | W | |
| 2008039402 | – | – | – |
| 2009407583 | – | – | – |
| 2009037790 | – | – | – |
| US20080039402P | – | – | – |
| US20090407583 | – | – | – |
| WO2009US37790 | – | – | – |
Members93
| Document | Office | Kind | |
|---|---|---|---|
| CA2719073A1 | Canada | A1 | |
| CA2719266A1 | Canada | A1 | |
| CA2806556A1 | Canada | A1 | |
| CA2911113A1 | Canada | A1 | |
| US2009248883A1 | United States of America | A1 | |
| US2009248996A1 | United States of America | A1 | |
| US2009249321A1 | United States of America | A1 | |
| WO2009120597A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009120598A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009120599A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2009271778A1 | United States of America | A1 | |
| WO2009120599A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CA2718898A1 | Canada | A1 | |
| WO2009142808A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009142808A3 | World Intellectual Property Organization (WIPO) | A3 | |
| KR20100124845A | Republic of Korea | A | |
| KR20100124847A | Republic of Korea | A | |
| KR20100127296A | Republic of Korea | A | |
| KR20100127851A | Republic of Korea | A | |
| EP2272035A2 | European Patent Office (EPO) | A2 | |
| EP2277107A1 | European Patent Office (EPO) | A1 | |
| EP2279471A1 | European Patent Office (EPO) | A1 | |
| EP2281235A2 | European Patent Office (EPO) | A2 | |
| CN102016792A | China | A | |
| CN102016793A | China | A | |
| CN102016794A | China | A | |
| CN102016895A | China | A | |
| JP2011515779A | Japan | A | |
| JP2011515780A | Japan | A | |
| JP2011519446A | Japan | A | |
| JP2011523243A | Japan | A | |
| RU2010143395A | Russian Federation | A | |
| RU2010143406A | Russian Federation | A | |
| RU2010143393A | Russian Federation | A | |
| JP4976585B2This record | Japan | B2 | |
| KR20120089748A | Republic of Korea | A | |
| KR20120092138A | Republic of Korea | A | |
| KR101180535B1 | Republic of Korea | B1 | |
| RU2464638C2 | Russian Federation | C2 | |
| KR101200454B1 | Republic of Korea | B1 | |
| KR101204049B1 | Republic of Korea | B1 | |
| RU2468419C2 | Russian Federation | C2 | |
| RU2469383C2 | Russian Federation | C2 | |
| JP5108145B2 | Japan | B2 | |
| KR20120138841A | Republic of Korea | A | |
| KR20130010054A | Republic of Korea | A | |
| JP2013059035A | Japan | A | |
| JP2013102513A | Japan | A | |
| KR101269983B1 | Republic of Korea | B1 | |
| KR101269985B1 | Republic of Korea | B1 | |
| JP5209781B2 | Japan | B2 | |
| KR101285711B1 | Republic of Korea | B1 | |
| KR101335563B1 | Republic of Korea | B1 | |
| KR101335569B1 | Republic of Korea | B1 | |
| CA2718898C | Canada | C | |
| CN102016895B | China | B | |
| CA2719266C | Canada | C | |
| CN102016794B | China | B | |
| JP2014241153A | Japan | A | |
| CN104461511A | China | A | |
| CN102016792B | China | B | |
| US9069575B2 | United States of America | B2 | |
| JP2015130679A | Japan | A | |
| US9110685B2 | United States of America | B2 | |
| US2015248231A1 | United States of America | A1 | |
| CN104932878A | China | A | |
| JP5788311B2 | Japan | B2 | |
| US2015346993A1 | United States of America | A1 | |
| JP5851967B2 | Japan | B2 | |
| JP2016026419A | Japan | A | |
| US9269059B2 | United States of America | B2 | |
| JP2016042709A | Japan | A | |
| BRPI0910408A2 | Brazil | A2 | |
| BRPI0909525A2 | Brazil | A2 | |
| BRPI0910406A2 | Brazil | A2 | |
| JP2016197885A | Japan | A | |
| JP6030097B2 | Japan | B2 | |
| JP2016224966A | Japan | A | |
| CN102016793B | China | B | |
| US9600261B2 | United States of America | B2 | |
| JP2018050304A | Japan | A | |
| JP2018121335A | Japan | A | |
| CA2719073C | Canada | C | |
| US10061500B2 | United States of America | B2 | |
| CA2806556C | Canada | C | |
| CN104461511B | China | B | |
| EP2277107B1 | European Patent Office (EPO) | B1 | |
| BRPI0909525A8 | Brazil | A8 | |
| BRPI0910406A8 | Brazil | A8 | |
| BRPI0910408A8 | Brazil | A8 | |
| EP2279471B1 | European Patent Office (EPO) | B1 | |
| US10481927B2 | United States of America | B2 | |
| BRPI0909525B1 | Brazil | B1 |
13 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 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| 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 | |
| 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 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 4976585
- Publication, DOCDB
- 4976585
- Publication, EPODOC
- JP4976585B
- Application
- 2011501932
- Application, DOCDB
- 2011501932
- Application, EPODOC
- JP20110501932
Titles2
- Japanese
- ウィジェットコンテンツ配信のための移送最適化のための、装置及び方法
- English
- Equipment and methods for transport optimization for widget content delivery
Classification
- CPC, 16
- G06Q10/06
- G06F16/00
- G06F16/14
- G06F16/95
- G06F16/144
- G06F16/148
- G06F16/156
- G06F16/903
- G06F16/907
- G06F16/951
- G06F16/1744
- G06F16/9032
- G06F16/9535
- G06F16/90332
- G06F16/9538
- G06F16/9035
- IPC, 4
- G06F13 00
- G06Q10 00
- G06Q30 02
- G06Q30 06
