JP2004110276A - Content distribution device, content distribution processing method, content distribution system program and recording medium therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a highly scalable device which can minimize software re-creation even if an application and the system environment of a content distribution system for distributing content by using servers of two or more platform elements are added or changed. <P>SOLUTION: The content distribution system 2 is constituted such that an application (AP) server 21 of the system is divided into an AP scenario part 30 and an AP common function part 31, and the AP common function part 31 is divided into a service system layer 310 and a function system layer 311. The service system layer 310 provides, to the AP scenario part 30, an interface integrating the interface of the function system layer 311 for each service model. The function system layer 311 provides an interface integrating the operation interface of the platform element for each function. <P>COPYRIGHT: (C)2004,JPO

Description

上記利用者登録メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した利用者属性（プロパティ）を登録する。
・手続きが正常に終了した場合，設定した利用者属性をＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【００８５】
上記利用者コマンド「ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，エンドユーザコマンドカプセル，ＰＦ事業者オペレータコマンドカプセル，ＰＦ事業者システムオペレータコマンドカプセル，サービス事業者オペレータコマンドカプセル，サービス事業者コマンドカプセルがある。
【００８６】
ユーザ管理サービスパッケージＰ１５が提供するユーザ属性検索／一覧／詳細参照／変更／削除インタフェースが定義している利用者一覧取得メソッド「ｇｅｔＬｉｓｔ　」，利用者詳細取得メソッド「ｇｅｔＤｅｔａｉｌ　」，利用者属性変更メソッド「ｃｈａｎｇｅ」，利用者削除メソッド「ｄｅｌｅｔｅ」の処理について以下に示す。

上記利用者一覧取得メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した検索条件に合致する利用者属性（プロパティ）を検索する。
・手続きが正常に終了した場合，取得した利用者属性をＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄに格納したものをＬｉｓｔに追加して呼び出し元へ返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。

上記利用者詳細取得メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した検索条件に合致する利用者属性（プロパティ）を検索する。
・手続きが正常に終了した場合，設定した利用者属性をＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。

上記利用者属性変更メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した利用者属性（プロパティ）に，登録済みの利用者属性を変更する。
・手続きが正常に終了した場合，設定した利用者属性をＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。

上記利用者削除メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した利用者属性（プロパティ）を削除（属性無効化）する。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【００８７】
上記各メソッドにおける利用者コマンド「ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，エンドユーザコマンドカプセル，ＰＦ事業者オペレータコマンドカプセル，ＰＦ事業者システムオペレータコマンドカプセル，サービス事業者オペレータコマンドカプセル，サービス事業者コマンドカプセルがある。
【００８８】
ユーザ管理サービスパッケージＰ１５が提供するユーザ属性重複チェックインタフェースが定義しているアカウント重複問い合わせメソッド「ｉｓＥｘｉｓｔ　」の処理について以下に示す。

上記アカウント重複問い合わせメソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した検索条件に合致する利用者属性（プロパティ）のアカウント重複問い合わせをする。
・手続きが正常に終了した場合，処理結果として，アカウントが重複していればｔｒｕｅを，アカウントが重複していなければｆａｌｓｅ　を呼び出し元へ返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【００８９】
上記各メソッドにおける利用者コマンド「ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，エンドユーザコマンドカプセル，ＰＦ事業者オペレータコマンドカプセル，ＰＦ事業者システムオペレータコマンドカプセル，サービス事業者オペレータコマンドカプセル，サービス事業者コマンドカプセルがある。
【００９０】
ユーザ管理サービスパッケージＰ１５が提供するユーザログインインタフェースが定義しているログインメソッド「ｌｏｇｉｎ　」の処理について以下に示す。

上記ログインメソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤを指定して，利用者コマンドに設定した利用者属性（プロパティ）でログインする。
・手続きが正常に終了した場合，取得した認証オブジェクトをＯｂｊｅｃｔに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
【００９１】
上記各メソッドにおける利用者コマンド「ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，エンドユーザコマンドカプセル，ＰＦ事業者オペレータコマンドカプセル，ＰＦ事業者システムオペレータコマンドカプセル，サービス事業者オペレータコマンドカプセル，サービス事業者コマンドカプセルがある。
【００９２】
ユーザ管理サービスパッケージＰ１５が提供するユーザパスワード問い合わせインタフェースが定義しているパスワード問い合わせメソッド「ｐｗｄＱｕｅｒｙ」の処理について以下に示す。

上記パスワード問い合わせメソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した検索条件に合致する利用者属性（プロパティ）のパスワード問い合わせをする。
・手続きが正常に終了した場合，取得したパスワードを　ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓ　Ｃｍｄに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【００９３】
上記パスワード問い合わせメソッドにおける利用者コマンド「ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，エンドユーザコマンドカプセル，ＰＦ事業者オペレータコマンドカプセル，ＰＦ事業者システムオペレータコマンドカプセル，サービス事業者オペレータコマンドカプセル，サービス事業者コマンドカプセルがある。
【００９４】
ユーザ管理サービスパッケージＰ１５が提供するユーザパスワード変更インタフェースが定義しているパスワード変更メソッド「ｐｗｄＣｈａｎｇｅ　」の処理について以下に示す。

上記パスワード変更メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した利用者属性（プロパティ）のパスワードに，登録済みの利用者属性のパスワードを変更する。
・手続きが正常に終了した場合，設定したパスワードを　ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓ　Ｃｍｄに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【００９５】
上記パスワード変更メソッドにおける利用者コマンド「ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，エンドユーザコマンドカプセル，ＰＦ事業者オペレータコマンドカプセル，ＰＦ事業者システムオペレータコマンドカプセル，サービス事業者オペレータコマンドカプセル，サービス事業者コマンドカプセルがある。
【００９６】
ユーザ管理サービスパッケージＰ１５が提供するユーザアカウントの一時停止／再開インタフェースが定義している利用停止／再開メソッド「ｓｔｏｐｐｅｄ　」の処理について以下に示す。

上記利用停止／再開メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，利用者コマンドに設定した利用者属性（プロパティ）の利用状況（停止，または再開）に，登録済みの利用者属性の利用状況を変更する。
・手続きが正常に終了した場合，設定した利用状況を　ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ　に格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【００９７】
上記利用停止／再開メソッドにおける利用者コマンド「ＣＵｓｅｒＩｎｆｏＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，エンドユーザコマンドカプセル，ＰＦ事業者オペレータコマンドカプセル，ＰＦ事業者システムオペレータコマンドカプセル，サービス事業者オペレータコマンドカプセル，サービス事業者コマンドカプセルがある。
【００９８】
次に，サービス系共通コンポーネントパッケージのコンテンツ管理サービスパッケージＰ１１が提供するコンテンツ権利属性登録受付／登録完了通知インタフェースは，以下に示す権利登録予約メソッド「ｒｅｓｉｓｔ」の処理を定義している。

上記権利登録予約メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，権利コマンドに設定した権利属性（プロパティ）の登録予約をする。
・手続きが正常に終了した場合，設定した権利属性をＣＲｉｇｈｔＳｅｒｖｉｃｅｓＣｍｄ　に格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【００９９】
上記権利コマンド「ＣＲｉｇｈｔＳｅｒｖｉｃｅｓＣｍｄ　」を継承したコマンドカプセルの一例として，権利コマンドカプセルがある。
【０１００】
コンテンツ管理サービスパッケージＰ１１が提供するコンテンツ検索／一覧／詳細参照／変更／削除インタフェースは，以下に示す権利一覧取得メソッド「　ｇｅｔＬｉｓｔ」，権利詳細取得メソッド「ｇｅｔＤｅｔａｉｌ　」，権利属性変更メソッド「ｃｈａｎｇｅ」，権利属性削除メソッド「ｄｅｌｅｔｅ」の処理を定義している。

上記権利一覧取得メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，権利コマンドに設定した権利属性（プロパティ）を検索する。
・手続きが正常に終了した場合，取得した権利属性をＣＲｉｇｈｔＳｅｒｖｉｃｅｓＣｍｄ　に格納したものをＬｉｓｔに追加して呼び出し元へ返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。

上記権利詳細取得メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，権利コマンドに設定した検索条件に合致する権利属性（プロパティ）を検索する。
・手続きが正常に終了した場合，取得した権利属性をＣＲｉｇｈｔＳｅｒｖｉｃｅｓＣｍｄ　に格納したものを呼び出し元へ返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。

上記権利属性変更メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，権利コマンドに設定した権利属性（プロパティ）に，登録済みの権利属性を変更する。
・手続きが正常に終了した場合，設定した権利属性をＣＲｉｇｈｔＳｅｒｖｉｃｅｓＣｍｄ　に格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。

上記権利属性削除メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，権利コマンドに設定した権利属性（プロパティ）を削除（属性無効化）する。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【０１０１】
上記各メソッドにおける権利コマンド「ＣＲｉｇｈｔＳｅｒｖｉｃｅｓＣｍｄ　」を継承したコマンドカプセルの一例として，権利コマンドカプセル「ＣＲｉｇｈｔｓＣｍｄ」がある。
【０１０２】
次に，サービス系共通コンポーネントパッケージの商品／コース管理サービスパッケージＰ１２が提供する商品／コース属性登録／登録完了通知インタフェースは，以下に示す商品／コース属性登録メソッド「ｒｅｓｉｓｔ」の処理を定義している。

上記商品／コース属性登録メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，商品／コースコマンドに設定した商品／コース属性属性（プロパティ）を登録する。
・手続きが正常に終了した場合，設定した商品／コース属性を　ＣＣｏｍｍｏｄｉｔｙＳｅｒｖｉｃｅｓＣｍｄに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【０１０３】
上記商品／コースコマンド「　ＣＣｏｍｍｏｄｉｔｙＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，商品コマンドカプセルとコースコマンドカプセルがある。
【０１０４】
商品／コース管理サービスパッケージＰ１２が提供する商品／コース検索／一覧／詳細参照／変更／削除インタフェースは，例えば，以下に示す商品／コース一覧取得メソッド「ｇｅｔＣｏｍｍｏｄｉｔｙＬｉｓｔ」，商品／コース詳細取得メソッド「ｇｅｔＣｏｍｍｏｄｉｔｙＤｅｔａｉｌ」の処理を定義している。

上記商品／コース属性登録メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，商品／コースコマンドに設定した検索条件に合致する商品／コース属性属性（プロパティ）を検索する。・手続きが正常に終了した場合，取得した商品／コース属性を　ＣＣｏｍｍｏｄｉｔｙＳｅｒｖｉｃｅｓＣｍｄに格納したものをＬｉｓｔに追加して呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。

上記商品／コース詳細取得メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，商品／コースコマンドに設定した検索条件に合致する商品／コース属性属性（プロパティ）を検索する。・手続きが正常に終了した場合，取得した商品／コース属性を　ＣＣｏｍｍｏｄｉｔｙＳｅｒｖｉｃｅｓＣｍｄに格納したものを呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【０１０５】
上記各メソッドにおける商品／コースコマンド「　ＣＣｏｍｍｏｄｉｔｙＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，商品コマンドカプセルとコースコマンドカプセルがある。
【０１０６】
商品／コース管理サービスパッケージＰ１２が提供する商品／コースに関連付けられたコンテンツ一覧／詳細インタフェースは，以下に示す関連付けコンテンツ一覧取得メソッド「ｇｅｔＣｏｎｔｅｎｔＬｉｓｔ」の処理を定義している。

上記関連付けコンテンツ一覧取得メソッドの機能概要は，以下の通りである。
・サービス事業者ＩＤと認証オブジェクトを指定して，関連付けコマンドに設定した検索条件に合致する商品／コースに関連付いているコンテンツ属性（プロパティ）を検索する。
・手続きが正常に終了した場合，取得したコンテンツ属性を　ＣＣｏｍｍｏｄｉｔｙＳｅｒｖｉｃｅｓＣｍｄに格納したものをＬｉｓｔに追加して呼び出し元に返す。
・サービス事業者ＩＤは，共通コンポーネント（ストレージサーバ）のスキーマ指定などサービス事業者情報の管理に使用する。
・認証オブジェクトは，各プラットフォームに対して登録依頼を行うときの認証に使用する。
【０１０７】
上記関連付けコンテンツ一覧取得メソッドにおける関連付けコマンド「　ＣＣｏｍｍｏｄｉｔｙＳｅｒｖｉｃｅｓＣｍｄ」を継承したコマンドカプセルの一例として，関連付けコマンドカプセルがある。
【０１０８】
上記インタフェースを使用したサービス系レイヤ３１０および機能系レイヤ３１１の動作例を，サービス系レイヤ３１０が「コンテンツ権利情報登録」の依頼をＡＰシナリオ部３０から受けた場合の例に従って説明する。
【０１０９】
ＡＰシナリオ部３０は，上記コンテンツ管理サービスパッケージＰ１１における権利サービスインタフェースの権利登録予約メソッド（　ＣＲｉｇｈｔｓＳｅｒｖｉｃｅｓＣｍｄ．ｒｅｓｉｓｔ（サービス事業者ＩＤ，認証オブジェクト，権利コマンド））を呼び出し，これをサービス系レイヤ３１０が実行する。
【０１１０】
サービス系レイヤ３１０では，パラメータは正常であるかどうか，また認証されているかどうかを調べ，パラメータが正常でない場合，またはこのサービス事業ＩＤが認証されていない場合には，ＡＰシナリオ部３０へ「不可」の回答を返却する。
【０１１１】
パラメータが正常であり，認証されている場合，コンテンツ権利情報登録を機能系レイヤ３１１に依頼する。このとき，サービス系レイヤ３１０は，コンテンツ管理機能パッケージＰ２２における権利属性操作インタフェースの権利属性登録メソッド（　ＣＡｃｃｅｓｓＣｏｎｔｃｎｔＲｉｇｈｔｓＩｎｆｏ．ｅｎｔｒｙ　（サービス事業者ＩＤ，認証オブジェクト，権利アクセスコマンド））を呼び出し，これを機能系レイヤ３１１が実行する。
【０１１２】
サービス系レイヤ３１０は，呼び出したコンテンツ管理機能パッケージＰ２２における権利属性操作インタフェースの権利属性登録メソッドの戻り値として，コンテンツ権利情報登録の結果を受ける。この戻り値として受け取ったコンテンツ権利情報登録の結果をＡＰシナリオ部３０へ返却する。
【０１１３】
以上は一例である。本発明は，これらのパッケージ，インタフェースの具体的な構成方法自体に特徴があるわけではなく，ＡＰサーバ２１の特にＡＰ共通機能部３１のレイヤ構成と，どのようなパッケージ，インタフェースが存在するかということに特徴があり，以上の説明から他のパッケージのインタフェース，メソッドについても，同様に容易に構成できることは明らかであるので，これ以上の全パッケージおよび全インタフェースを網羅して説明するのを省略する。
【０１１４】
以下では，コンテンツ流通サービスにおける各種の要求処理に対する処理の流れの例について，代表的な例を用いて説明する。
【０１１５】
図２２および図２３は，本発明を用いたサービス事業者オペレータ（ＯＰ）パスワード問合わせ情報チェック処理フローの一例を示す図である。まず，前処理として，ＡＰシナリオ部３０で，ロジック以外の画面遷移，見栄えなどに関する処理が行われる（ステップＳ２１）。例えば，入力画面表示や入力値画面チェックや確認画面表示などの処理を行う。
【０１１６】
そして，ＡＰシナリオ部３０からサービス系レイヤ３１０にサービス事業者ＯＰ検索処理実行を依頼する（ステップＳ２２）。この場合，引数として事業者，認証情報，検索条件などをコマンドカプセルとして渡す。次に，サービス系レイヤ３１０は，機能系レイヤ３１１に処理依頼を出すためのコマンドを作成する（ステップＳ２３）。また，機能系レイヤ３１１に汎用検索処理実行を依頼する（ステップＳ２４）。この場合，サービス事業者ＯＰの検索を汎用検索処理機能に処理実行依頼をする。
【０１１７】
次に，機能系レイヤ３１１は，サービス事業者ＯＰ検索ロジック構築を行う（ステップＳ２５）。また，共通サーバ系レイヤ２２０に検索処理実行を依頼する（ステップＳ２６）。この場合，共通サーバの検索用コマンド発行依頼を行う。次に，共通サーバ系レイヤ２２０は，サービス事業者ＯＰ検索を実行する（ステップＳ２７）。この場合，最適化した検索コマンドを発行する。そして，検索結果を受信し，機能系レイヤ３１１に結果を返却する（ステップＳ２８）。
【０１１８】
次に，機能系レイヤ３１１は，検索結果を受信し，返却用検索結果組み立てを行う（ステップＳ２９）。そして，サービス系レイヤ３１０に結果を返却する（ステップＳ３０）。
【０１１９】
次に，サービス系レイヤ３１０は，検索結果を受信し，返却用検索結果組み立てを行う（ステップＳ３１）。また，次にＡＰシナリオ部３０に結果を返却する（ステップＳ３２）。次に，ＡＰシナリオ部３０でサービス事業者ＯＰ検索処理を受信する（ステップＳ３３）。そして，ＡＰシナリオ部３０で，ロジック以外の画面遷移，見栄えなどに関する処理が行われる（ステップＳ３４）。例えば，確認結果画面表示などを行う。
【０１２０】
図２４乃至図２７は，本発明を用いたサービス事業者ＯＰパスワード問合わせ情報チェックにおけるシーケンス図の一例である。図中，１８はメールサーバである。
【０１２１】
Ａ）まず，クライアントＰＣ８’のサービス事業者トップメニュー画面において，「サービス事業者オペレータパスワード問い合わせ」のリンクをクリックして，ＡＰサーバのＡＰシナリオ部３０に問い合わせると，ＡＰシナリオ部３０は，クライアントＰＣ８’にパスワード問い合わせ情報入力画面を表示させる。当該入力画面において「送信」のリンクをクリックすると，問い合わせ情報がＡＰシナリオ部３０に送信される。
【０１２２】
Ｂ）次に，ＡＰシナリオ部３０は，パスワード問い合わせ情報チェックアクションを行い，問い合わせ情報を基に必須項目をチェックした後，サービス系レイヤ３１０の共通機能部に引数として検索条件をコマンドカプセル１０８として渡してサービス事業者ＯＰ一覧の取得依頼を行う。
【０１２３】
Ｃ−Ｄ）次に，サービス系レイヤ３１０は，機能系レイヤ３１１に処理依頼を出すためのコマンドを作成し，機能系レイヤ３１１に検索条件をコマンドカプセル１０８として渡してサービス事業者ＯＰ検索処理実行を依頼する。
【０１２４】
Ｅ）次に，機能系レイヤ３１１は，サービス事業者ＯＰ検索ロジック構築を行い，コマンドカプセル実行エンジン３１２に検索条件を渡す。
【０１２５】
Ｆ）コマンドカプセル実行エンジン３１２は，共通サーバ系レイヤ２２０に検索実行文を渡してサービス事業者ＯＰ検索実行を依頼する。
【０１２６】
Ｇ−Ｍ）ＡＰ共通ＤＢサーバ２２は，サービス事業者ＯＰ情報を検索し，機能系レイヤ３１１に検索結果を返却する。この検索結果は，コマンドカプセル実行エンジン３１２，機能系レイヤ３１１を経由してサービス系レイヤ３１０に返却される。検索結果を受け取ったサービス系レイヤ３１０は，ＡＰシナリオ部３０に検索結果を返却する。
【０１２７】
Ｎ）ＡＰシナリオ部３０はサービス事業者ＯＰ検索結果を受信すると，サービス事業者存在チェック，サービス事業者オペレータメールアドレス一致チェックを行い，サービス系レイヤ３１０に検索条件を渡してサービス事業者ＯＰパスワードを問い合わせる。
【０１２８】
Ｏ−Ｐ）サービス系レイヤ３１０は，検索条件を機能系レイヤ３１１に渡す。機能系レイヤ３１１は，通知メールをメールサーバ１８に送信するとともに，サービス事業者ＯＰ検索ロジック（ＳＥＬＥＣＴ文等）を構築し，コマンドカプセル実行エンジン３１２に検索条件を渡す。コマンドカプセル実行エンジン３１２は，ＡＰ共通ＤＢサーバ２２に検索実行文を渡して，サービス事業者ＯＰ検索実行を依頼する。
【０１２９】
Ｑ−Ｒ）ＡＰ共通ＤＢサーバ２２は，サービス事業者ＯＰ情報を検索し，検索結果をコマンドカプセル実行エンジン３１２に返却する。この検索結果は，コマンドカプセル実行エンジン３１２，機能系レイヤ３１１を経由してサービス系レイヤ３１０に返却される。
【０１３０】
Ｓ−Ｕ）サービス系レイヤ３１０は，ＡＰシナリオ部３０に検索結果を返却し，検索結果を受け取ったＡＰシナリオ部３０は，確認結果画面表示などに関する処理を行い，問い合わせ結果をクライアントＰＣ８’に送信し，パスワード送信完了画面を表示させる。また，メールサーバ１８からクライアントＰＣ８’には通知メールが送信される。
【０１３１】
図２８および図２９は，本発明を用いた商品・コース検索処理フローの一例を示す図である。まず，前処理として，ＡＰシナリオ部３０で，ロジック以外の画面遷移，見栄えなどに関する処理が行われる（ステップＳ４１）。例えば，入力画面表示や入力値画面チェックや確認画面表示などの処理を行う。そして，ＡＰシナリオ部３０からサービス系レイヤ３１０に商品・コース検索処理実行を依頼する（ステップＳ４２）。
【０１３２】
次に，サービス系レイヤ３１０は，機能系レイヤ３１１に処理依頼を出すためのコマンドを作成する（ステップＳ４３）。また，機能系レイヤ３１１に汎用検索処理実行を依頼する（ステップＳ４４）。次に，機能系レイヤ３１１は，商品・コース検索ロジック構築を行う（ステップＳ４５）。また，共通サーバ系レイヤ２２０に検索処理実行を依頼する（ステップＳ４６）。
【０１３３】
次に，共通サーバ系レイヤ２２０は，商品・コース検索を実行する（ステップＳ４７）。そして，検索結果を受信し，機能系レイヤ３１１に結果を返却する（ステップＳ４８）。次に，機能系レイヤ３１１は，検索結果を受信し，返却用検索結果組み立てを行う（ステップＳ４９）。そして，サービス系レイヤ３１０に結果を返却する（ステップＳ５０）。
【０１３４】
次に，サービス系レイヤ３１０は，検索結果を受信し，返却用検索結果組み立てを行う（ステップＳ５１）。また，次にＡＰシナリオ部３０に結果を返却する（ステップＳ５２）。次に，ＡＰシナリオ部３０で商品・コース検索処理を受信し（ステップＳ５３），ロジック以外の画面遷移，見栄えなどに関する処理が行われる（ステップＳ５４）。例えば，確認結果画面表示などを行う。
【０１３５】
図３０乃至図３２は，本発明を用いたサービス事業者コンテンツ権利情報登録における，処理フローの概要を示す図である。図中１９は，アップロードサーバである。まず，前処理として，ＡＰシナリオ部３０で，ロジック以外の画面遷移，見栄えなどに関する処理が行われる（ステップＳ６１）。例えば入力画面表示や入力画面チェックや確認画面表示などが行われる。そして，ＡＰシナリオ部３０からサービス系レイヤ３１０にコンテンツ権利情報登録処理実行を依頼する（ステップＳ６２）。この場合，引数として事業者，認証情報，登録情報などをコマンドカプセルとして渡す。
【０１３６】
次に，サービス系レイヤ３１０が，機能系レイヤ３１１に処理依頼を出すためのコマンドを作成する（ステップＳ６３）。そして，機能系レイヤ３１１に権利情報登録処理実行を依頼する（ステップＳ６４）。この場合，汎用権利情報登録における，該当コンテンツ登録を処理依頼する。次に，機能系レイヤ３１１において，コンテンツ権利情報登録ロジックを構築する（ステップＳ６５）。例えば，事業者認証，著作権登録，ＩＤ払出し，透かしなど挿入のロジックを構築する。
【０１３７】
機能系レイヤ３１１においては，ＡＰ内で各ロジック処理を行う他，各ＰＦ要素に対して各ロジック処理実行を依頼する（ステップＳ６６）。例えば，ＡＰ内において事業者認証処理や登録情報変換・操作処理，すかし挿入など非同期処理管理処理を実行し，アップロードサーバ１９に対してコンテンツコピー処理の実行を依頼し，著作権管理ＰＦ１３に対してコンテンツＩＤ発行処理の実行を依頼する。また，ＡＰ共通ＤＢサーバ２２に対しては権利情報保存処理の実行を依頼する。
【０１３８】
各ＰＦ要素においては，機能系レイヤ３１１から依頼された処理を実行する（ステップＳ７４）。次に，機能系レイヤ３１１において，非同期処理要求メッセージを構築送信し（ステップＳ６７），ロジック実行結果組み立てを行った上で（ステップＳ６８），サービス系レイヤ３１０に結果を返却する（ステップＳ６９）。次に，サービス系レイヤ３１０において，検索結果を受信し，返却用検索結果の組み立てを行う（ステップＳ７０）。そして，ＡＰシナリオ部３０に結果を返却する（ステップＳ７１）。
【０１３９】
ＡＰシナリオ部３０でサービス事業者コンテンツ権利情報登録受付結果を受信し（ステップＳ７２），ロジック以外の画面遷移，見栄えなどに関する処理が行われる（ステップＳ７３）。例えば確認結果通知画面表示などが行われる。以下，同様に処理が続けられる。
【０１４０】
以上説明したように，本発明は，アプリケーションをＡＰシナリオ部３０とＡＰ共通機能部３１とに分け，さらにＡＰ共通機能部３１をサービス系レイヤ３１０と機能系レイヤ３１１とに階層化することにより，例えば，上位のアプリケーションで修正が必要な場合，一番上のレイヤのインタフェースの修正で吸収して，下位のＰＦ要素に影響を与えないようにすることができる。すなわち，下位のインタフェースおよびプラットフォームはそのままでよい。
【０１４１】
また，逆に，下位のＰＦ要素が変わる場合，下位のインタフェースの修正で吸収し，上のアプリケーションには影響を与えず，そのままとするようなことが可能であり，カスタマイズ，拡張性が広がる。
【０１４２】
【発明の効果】
上述のように，本発明によれば以下の特長を有する。
・様々なビジネスモデルに対応するためのシステム開発が容易になる。
・共通的に利用できる部品の共通利用，及び再利用できる部品を再利用することで，開発リソースの有効利用が図れ，開発効率が高まる。
・システムで利用する各種ＰＦ要素の利用方法を熟知していなくても，それを利用したアプリケーションを開発できるようになる。
【図面の簡単な説明】
【図１】コンテンツ流通ネットワークシステムの全体概念構成図である。
【図２】コンテンツ流通システムの詳細構成図である。
【図３】コンテンツ流通のシナリオモデルを示す図である。
【図４】サービス系レイヤ，機能系レイヤ，共通サーバ系レイヤの概要を示す図である。
【図５】プラットフォームを含めたシステム全体の構成例を示す図である。
【図６】ＡＰサーバに搭載したコンポーネントの関連を示す構成図である。
【図７】インタフェース，メソッド，コマンドカプセル，コマンドカプセル実行エンジンの説明図である。
【図８】共通コンポーネントの動作処理フローを示す図である。
【図９】コンポジット，コマンド，メディエータの説明を示す図である。
【図１０】機能系レイヤとコマンドカプセル実行エンジンの機能ブロック図である。
【図１１】ＡＰ共通機能部おけるパッケージとインタフェースを示す図である。
【図１２】サービス系レイヤインタフェースとパッケージの一覧を示す図である。
【図１３】サービス系レイヤインタフェースとパッケージの一覧を示す図である。
【図１４】機能系レイヤのパッケージの一覧を示す図である。
【図１５】ユーザ管理機能パッケージの機能系レイヤインタフェースの例を示す図である。
【図１６】コンテンツ管理機能パッケージの機能系レイヤインタフェースの例を示す図である。
【図１７】商品管理機能パッケージの機能系レイヤインタフェースの例を示す図である。
【図１８】販売管理機能パッケージの機能系レイヤインタフェースの例を示す図である。
【図１９】課金決済機能パッケージの機能系レイヤインタフェースの例を示す図である。
【図２０】商品配信機能パッケージの機能系レイヤインタフェースの例を示す図である。
【図２１】共通サーバ系レイヤに関する共通コンポーネントパッケージの一覧を示す図である。
【図２２】サービス事業者ＯＰパスワード問合わせ情報チェック処理フローの一例を示す図である。
【図２３】サービス事業者ＯＰパスワード問合わせ情報チェック処理フローの一例を示す図である。
【図２４】本発明を用いたサービス事業者ＯＰパスワード問合わせ情報チェックにおけるシーケンス図の一例を示す図である。
【図２５】本発明を用いたサービス事業者ＯＰパスワード問合わせ情報チェックにおけるシーケンス図の一例を示す図である。
【図２６】本発明を用いたサービス事業者ＯＰパスワード問合わせ情報チェックにおけるシーケンス図の一例を示す図である。
【図２７】本発明を用いたサービス事業者ＯＰパスワード問合わせ情報チェックにおけるシーケンス図の一例を示す図である。
【図２８】本発明を用いた商品・コース検索処理フローの一例を示す図である。
【図２９】本発明を用いた商品・コース検索処理フローの一例を示す図である。
【図３０】本発明を用いたサービス事業者コンテンツ権利情報登録における処理フローの概要を示す図である。
【図３１】本発明を用いたサービス事業者コンテンツ権利情報登録における処理フローの概要を示す図である。
【図３２】本発明を用いたサービス事業者コンテンツ権利情報登録における処理フローの概要を示す図である。
【符号の説明】
１　広義のコンテンツ流通システム
２　狭義のコンテンツ流通システム
３　データセンタ
４　インターネット
５　ＩＳＰ
６　エンドユーザ
７　専用線
８　サービス事業者
９　決済代行業者
１０　ＰＦ事業者
１１　各ＰＦ要素
１２　課金決済ＰＦ
１３　著作権管理ＰＦ
１４　ライセンスサーバ
１５　ＶＯＤ配信サーバ
１６　ダウンロードサーバ
１７　アーカイブサーバ
２１　ＡＰサーバ
２２　ＡＰ共通ＤＢサーバ
２３　ＡＰ共通ＤＢ
２４　ブラウザ
３０　ＡＰシナリオ部
３１　ＡＰ共通機能部
１００　ＨＴＴＰサーバ
１０１　ＰＦ連携システム
１０２，１０３，１０４，１０５，１０６，１０７　プラットフォームインタフェース（ＰＦＩＦ）
１０８　コマンドカプセル
１１０　各ＰＦ要素のサーバ
１３０　サービス系レイヤインタフェース
１３１　機能系レイヤインタフェース
１３２　個別ＰＦのアダプタインタフェース
２２０　共通サーバ系レイヤ
３００　個別ＡＰ
３０１　ＡＰシナリオ部におけるサービス画面
３０２　ＡＰシナリオ部におけるＡＰ制御コンポーネント
３１０　サービス系レイヤ
３１１　機能系レイヤ
３１２　コマンドカプセル実行エンジン[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an application of a content distribution system, and relates to a basic technology of a system for distributing content while protecting copyright by assigning an ID to an image or a video.
[0002]
In particular, the present invention relates to a common component of application software for a video content distribution service in a content distribution system. The common components are a group of general-purpose components that are applied to the construction of a video content distribution service. The common components are introduced into a video content distribution service ASP business, and the individual service construction on the ASP is firstly provided by providing a framework and secondarily. It supports the construction of a content distribution system in terms of providing general-purpose components.
[0003]
[Prior art]
In a conventional content distribution system, individual systems are created depending on service contents and provision targets. In other words, in the conventional technology, the system is not divided into a common part and a part that changes according to the usage scene. Even if it is a common software component, the part depending on the service and the platform (hereinafter, PF) In general, a system configuration in which parts depending on elements are integrated is common. Also, no interface is cut out at the program level suitable for various content distribution services. The interface referred to here is not a hardware or electrical interface but refers to a cutout of a specific unit for exchanging a command statement, a message, and the like on software.
[0004]
As a typical example of the related art, there is an information processing apparatus that attempts to construct a system without porting or recreating an application program developed on a different platform such as an operating system (OS) or hardware (for example, , Patent Document 1). The prior art described in Patent Literature 1 has an open business common base device in an information processing device, and the open business base device has a configuration in which an API matching control device is connected to a plurality of API control devices. . By incorporating various interfaces, it is intended to integrate APs described on different platforms.
[Patent Document 1]
JP-A-10-40080 (page 1-2)
[0005]
[Problems to be solved by the invention]
Here, the interface defined in the above-mentioned conventional technology solves the problem of AP integration by providing a variety of interfaces in order to transparently connect a selected OS or hardware platform to a plurality of application programs. This is not a study as to what kind of specific interface is good, especially assuming an application serviced by a content distributor. Also, there is no description in the above-mentioned Patent Document 1 that the software mounted on the platform server is divided into layers to determine respective interfaces to enhance versatility. For this reason, such a conventional technique cannot realize a content distribution base that can be expected to be expandable from the viewpoint of a network administrator, a user (consumer) who is a final purchaser, and a service provider.
[0006]
That is, the conventional technique has the following problems.
(1) According to various business models in content distribution, the system being used must be completely redesigned each time.
(2) In the case of directly using the interface of the platform (PF) element in system development, the system cannot be constructed unless the mechanism and usage of the used PF element are well understood.
[0007]
The present invention has been made in view of the above points,
A) realizing the operation of integrating related platforms for video content distribution services;
B) Ensuring expandability in the development of video content distribution systems,
C) Developing reusable components (software clusters) in the development of video content distribution systems;
The purpose is to provide a content distribution system platform that satisfies the requirements.
[0008]
[Means for Solving the Problems]
The present invention has the following features to solve the above-mentioned problems.
[0009]
In a content distribution system in content distribution that operates using platform (PF) elements such as commercially available software and packages, application (AP) scenario parts (AP scenario part) corresponding to various content distribution models and change depending on the application A service layer (having an interface with the AP scenario unit) is divided into two layers, a part not to be performed (AP common function unit), and a part that is easily dependent on a service model in order to secure expandability. And a functional layer (having an interface with the PF element) as a part that easily depends on the command of the PF element.
[0010]
That is, the AP scenario part and the AP common function part are divided into layers by a software architecture, and respective interfaces (IF) are provided.
[0011]
In the AP common function part, layers are divided by a software architecture into a part that provides an interface with an AP scenario part and a part that integrates an interface with a PF element, and an interface (IF) is provided for each.
[0012]
In such a layer (layer) of the AP common function unit, the interface for operating each component is configured so as to hide the lower cooperating interface (the configuration in which the upper IF includes the lower IF). For example, a command capsule containing related operations and parameters has been implemented. As a mechanism for linking and independence between the application part and the platform part, for example, an execution engine can be constructed, and the execution part can be operated by a command capsule.
[0013]
The service layer of the AP common function unit has a content management service package, a product / course management service package, a product sales / distribution service package, a product consumption service package, and a user management service package.
[0014]
The functional layer has a user management function package, a content management function package, a product management function package, a sales management function package, a billing and settlement function package, and a product distribution function package.
[0015]
The user management function package in the functional layer provides an interface for user attribute operation and an interface for user authentication. The content management function package provides an interface for right attribute operation and an interface for master content operation. I will provide a.
[0016]
In addition, the product management function package in the functional layer provides an interface for operating product attributes and an interface for operating transaction history attributes, and the billing and settlement package provides an interface for operating billing and payment attributes. The distribution function package provides an interface for operation of distribution content and an interface for license operation.
[0017]
On the other hand, the content management service package in the service layer has an interface for accepting registration of content rights attribute / notifying completion of registration, an interface for searching / listing / detailing / modifying / deleting content, and an interface for inquiring whether content can be deleted. And an interface for searching the content registration procedure status for the content management service package.
[0018]
The product / course management package in the service layer has an interface for product / course attribute registration / registration completion notification, an interface for product / course search / list / detailed reference / modification / deletion, and product / course deletion availability. Provides an interface for inquiries and an interface for listing / detailed contents associated with products / courses.
[0019]
The product sales / distribution service package in the service layer is an interface for content distribution procedure status search, an interface for sales history registration, an interface for sales history search / list / details reference, and a license issuance request. Provides an interface for
[0020]
The product consumption service package in the service layer is an interface for product / course inquiry, an interface for product / course search / list / details reference, an interface for product / course purchase inquiry, product / course purchase It provides an interface for content viewing, content viewing or on-demand / download, and an interface for storing / retrieving usage detail data.
[0021]
The user management service package in the service layer includes an interface for user attribute registration / registration completion notification, an interface for user attribute search / list / detailed reference / change / deletion, an interface for user attribute duplication check, Provides an interface for user login, an interface for changing a user password, an interface for querying a user password, and an interface for suspending / resuming a user account.
[0022]
Using the interface provided by the service layer, the application scenario unit requests the service layer to perform processing related to content management, product / course management, product sales / distribution, product consumption, or user management.
[0023]
The service layer responds to the processing request from the application scenario part by using the user management function, content management function, product management function, sales management function, billing / payment function or product distribution function provided by the functional layer. Request processing to the functional layer.
[0024]
The functional layer issues an operation instruction to a related platform element in response to a processing request from the service layer.
[0025]
The present invention employs the above-described layer configuration to provide a database server, a download server, a license server, and a VDO to an AP scenario unit for realizing a content distribution service model to be developed by an individual service provider. Providing an interface that conceals specific operation methods for related platform elements such as a distribution server, a billing settlement platform, and a copyright management platform, facilitating the development of a content distribution system by creating an AP scenario part, and Scalability and maintainability can be improved.
[0026]
In addition, the AP common function part is configured by dividing into a service layer and a function layer. The function layer provides a related interface in which the operation interface of the related platform element is integrated for each function, while the service layer is provided. , Provides an interface that integrates the functional layer interface from the service point of view for each content distribution service model for the AP scenario part, and responds to changes in the operation interface of related platform elements without affecting the service layer In addition, the addition of a new interface to the AP scenario section in the service layer can be realized with minimal influence on the functional layer.
[0027]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 is an overall conceptual configuration diagram of a content distribution network system including a base data center.
[0028]
In FIG. 1, reference numeral 1 denotes a content distribution system in a broad sense in which each PF element is added to the content distribution system according to the present invention, 3 denotes a data center, 4 denotes the Internet, 5 denotes a provider (ISP) for providing a connection service to the Internet, 6 Is an end user (terminal), 7 is a dedicated line, 8 is a service provider (terminal), 9 is a payment agent (terminal), and 10 is a PF provider (terminal).
[0029]
FIG. 2 is a detailed configuration diagram of the content distribution system 1 shown in FIG. 2, reference numeral 2 denotes a content distribution system in a narrow sense according to the present invention, 21 denotes an AP server, 22 denotes an AP common DB server, 23 denotes an AP common DB, 11 denotes each PF element, 30 denotes an AP scenario part, and 31 denotes an AP common. The function unit 110 is a server for each PF element. Reference numeral 310 denotes a service layer, 311 denotes a function layer, and 220 denotes a common server layer.
[0030]
In the present embodiment, the AP scenario unit 30 and the AP common function unit 31 are implemented using a Java (registered trademark) development environment. The AP scenario unit 30 is a program part prepared for each application of the content distribution service model to be realized. The AP common function unit 31 is a common component prepared in advance in advance for various applications. The common server system layer 220 in the AP common DB server 22 is also a common component prepared in advance for various applications. The common server layer 220 provides an access interface to the AP common DB 23 in which various tables used in the content distribution system 2 are stored for various applications.
[0031]
The AP common function unit 31 is configured to be divided into a service system layer 310 having an interface with the AP scenario unit 30 and a function system layer 311 having an interface with the server 110 of each PF element and the AP common DB server 22. .
[0032]
The service layer 310 provides the AP scenario unit 30 with an interface in which the interface of the functional layer 311 is integrated from a service point of view for each content distribution service model, and the functional layer 311 provides a server for each relevant PF element. It provides a related interface that integrates the operation interface of the application server 110 and the AP common DB server 22 for each function.
[0033]
In realizing the system according to the present invention, the content distribution service model differs depending on the service provider, and even if the application is different, the function commonly required by each application is represented by a video content distribution service as a representative example of the content distribution business. The extraction is performed by taking the case of performing as an example.
[0034]
FIG. 3 shows an example of a content distribution scenario model. In order to extract an AP common function required as the AP common function unit 31, a content distribution scenario model shown in FIG. 3 was set, and what kind of information management and use of information are assumed.
[0035]
As shown in FIG. 3, user attribute management is used when a platform administrator, a user who is a final purchaser, and a service provider register, search, update, and delete user attributes from their respective positions. It is. In product attribute management, a network manager and a service provider operate attributes related to a product.
[0036]
In the content attribute management, platform providers and service providers register, search, update, and delete contents. In the content file management, a platform company and a service company register, search, update, and delete content files. The product sales attribute management is performed by a platform provider, a service provider, and some users. The content distribution management is performed by a platform administrator, a user, and a service provider.
[0037]
Based on such a scenario model, an AP common function is extracted so as to operate on the AP server 21 even if individual applications are different. The extraction of the AP common function was determined based on the following requirements.
(1) It is desired to unify component development / introduction policies of a plurality of individual services by providing a framework for constructing a video content distribution service (for development design support).
(2) We want to make it easier to manage individual service groups by complying with the framework (for development and design support, for PF administrators).
(3) The general-purpose component group is the main operation interface in the video content distribution system, and we would like to hide and provide cooperation of related platforms (to support development design).
(4) We want to concentrate on implementation of our own business model, implementation of our own GUI, and implementation of our own scenario within the scope of the general component group of the distribution service constructed by applying common components (for development design support).
(5) In addition, even if it is out of the applicable range of the general-purpose component group, there is a need for a means for developing a unique component in accordance with the framework (to support development design).
[0038]
The common function part (common component) that satisfies such requirements is determined to have a multilayered layer structure. That is, a service layer 310 having an interface with the AP scenario section 30 and a functional layer 311 having an interface with each PF element 11 are mounted on the AP common function section 31 of the AP server 21, and the AP common DB server 22 is mounted on the AP common DB server 22. The common server system layer 220 is mounted.
[0039]
FIG. 4 shows the outline of each layer. Thereby, even if the service providers are different and the service layer 310 is different, the common functional layer 311 can be used.
[0040]
In order to carry out a content distribution business using the system of FIG. 1, various platform elements are required. FIG. 5 shows an overall system configuration diagram having common components including the platform. 5, reference numeral 12 denotes a charge settlement PF, 13 denotes a copyright management PF, 14 denotes a license server, 15 denotes a VOD distribution server, 16 denotes a download server, 17 denotes an archive server, 300 denotes an individual AP, and 312 denotes a command capsule execution engine. is there.
[0041]
The billing settlement PF 12 is an integrated platform that performs billing and settlement processing for the provided service. The copyright management PF 13 is an integrated platform for managing the copyright of the provided content. The license server 14 is an application server having a content license management function. The VOD distribution server 15 is a server in which streaming contents are arranged and distributed at the time of viewing. The download server 16 is a server in which contents to be downloaded and viewed are arranged. The archive server 17 is a server that stores the original content of the content and stores temporarily generated files. The command capsule execution engine 312 will be described later.
[0042]
FIG. 6 is a configuration diagram showing the relationship between components mounted on the AP server shown in FIG. 6, 24 is a browser, 100 is an HTTP server, 101 is a PF cooperation system, 102 to 107 are platform interfaces (PFIF) of each PF, 108 is a command capsule, 130 is a service layer interface, and 131 is a functional layer. Reference numeral 132 denotes an adapter interface of an individual PF, reference numeral 301 denotes a service screen (JSP) in the AP scenario unit 30, and reference numeral 302 denotes an AP control component (servlet) in the AP scenario unit 30.
[0043]
A service layer 310, a function layer 311, a command capsule execution engine 312, and a common server layer 220 are prepared as components common to the applications. The service screen 301 and the AP control component 302 exist in the AP scenario unit 30.
[0044]
The PF cooperation system 101 is a cooperation mechanism for quickly providing a product that combines services provided by individual platforms. In this system, user management and authentication processing are realized using the PF cooperation system 101. That is, it is provided to perform common user management and user authentication for the charge settlement PF 12 and the copyright management PF 13, and this can be omitted.
[0045]
The items of the architecture described in FIG. 6 are defined as shown in FIG. In order to execute the contents intended by the operator by using the command capsule 108 in which the operation contents are summarized in the upper concept, an interface, a method, the command capsule 108 and the command capsule execution engine 312 are used. The command capsule execution engine 312 is mounted so as to be executed by an instruction from the command capsule 108 from the service layer 310 or the function layer 311 mounted on the AP server 21.
[0046]
The command capsule 108 is a component that encapsulates related data operations, logic, attributes serving as parameters, and the like. The command capsule execution engine 312 operates with the command capsule 108 and distributes the operation to the related platform and the AP common DB server 22.
[0047]
An outline of the operation of the common component in response to the invocation of the common component from the application will be described with reference to FIGS. FIG. 8 is a diagram showing an operation processing flow of the common component.
[0048]
(1) The application of the AP scenario unit 30 passes the command capsule 108 prepared in the service layer 310 to the method of the service layer 310 of the interface of the common component (service layer 310) (step S1).
[0049]
(2) When operating the command capsule execution engine 312 directly from the service layer 310 (step S2), the method of the service layer 310 passes the command capsule 108 of the service layer 310 to the command capsule execution engine 312 (step S2). S4), request execution.
[0050]
(3) When the functional layer 311 is used, the command capsule 108 of the service layer 310 has the method execution logic of the common component (functional layer 311). The command capsule 108 is passed to the method (step S3).
[0051]
(4) The method of the functional layer 311 transfers the passed command capsule 108 to the command capsule execution engine 312 (step S4).
[0052]
(5) The command capsule execution engine 312 executes the command capsule 108 and distributes related processing to each platform (PF) and the AP common DB server 22 (step S5). Here, the execution of the command capsule 108 refers to performing an operation of distributing a command group contained in the command capsule 108 to the PF or the AP common DB server 22 that executes each command.
[0053]
(6) The command capsule execution engine 312 monitors the execution status of the related platform and the AP common DB server 22, and returns a processing result to the caller (step S6).
[0054]
(7) Thereafter, the processing results are sequentially returned to the caller.
[0055]
When the service layer 310, the function layer 311 and the command capsule execution engine 312 are operated, a more general-purpose software structure is obtained by using the pattern (model) shown in FIG.
[0056]
A composite realizes a tree structure and is like a directory. An attribute structure can be created so that the command capsule 108 can be used in various combinations. A command is a template that collects operations for executing an instruction. A command capsule 108 is formed by collecting a plurality of commands to form a command, and collecting and forming a plurality of commands. The command capsule execution engine 312 is activated by the command capsule 108. For example, a plurality of commands are executed by one command capsule 108, and a plurality of operations can be executed by the command. Service can be realized by operation. The mediator (instruction execution / arbitration management unit) mediates and sorts the instructions, and grasps the operation status (start, end, etc.) of the instructions.
[0057]
FIG. 10 is a functional block diagram showing such a functional system layer 311 and the command capsule execution engine 312. 10, reference numeral 400 denotes an instruction execution / arbitration management unit (hereinafter, also referred to as a mediator) of the functional system layer 311; 401, an instruction arbitration unit (hereinafter, also referred to as a concrete mediator); And a command execution unit (hereinafter also referred to as a concrete core league) 403.
[0058]
The operation of the command capsule execution engine 312 located in the lower two layers of the AP server 21 shown in FIG. 10 will be described.
[0059]
An instruction is received by an instruction arbitration unit (concrete mediator) 401 in the functional layer 311 which is a common component via an interface / method. The instruction arbitration unit (concrete mediator) 401 inherits the class of the instruction execution / arbitration management unit (mediator) 400.
[0060]
The instruction arbitration unit (concrete mediator) 401 analyzes the given instruction and distributes the instruction to each instruction execution unit (concrete core league) 403 assigned to each PF element 11. The instruction execution unit (concrete core league) 403 issues an execution instruction to each PF element 11 including the AP common DB server 22 through each PF adapter and AP common DB server adapter. The instruction execution unit (concrete league) 403 inherits the class of the instruction execution supervision unit (core league) 402.
[0061]
The execution state of each is reported as appropriate from the instruction execution unit (concrete core league) 403 to the instruction arbitration unit (concrete mediator) 401 through the mediator report from the core league due to class inheritance. Manages the processing status of
[0062]
According to this pattern, each instruction execution unit (concrete core league) 403 receives the execution instruction from the instruction arbitration unit (concrete mediator) 401 and reports the processing status, thereby reducing the degree of connection between them. I do. Further, since the instruction arbitration unit (concrete mediator) 401 manages the report, the command arbitration unit 401 grasps the overall processing progress.
[0063]
Class inheritance as used here refers to inheritance "with the information of elements necessary to construct an object inside a class". In such a configuration, when a new class is designed, the information possessed by the existing class can be used, so that the development resources can be effectively used.
[0064]
The above-described series of processing is controlled by arithmetic control means such as a CPU, data necessary for the processing and a set thereof are stored in a storage means, and data is read and written in the course of the processing. Further, the above-described series of processing is executed by installing a program from the communication line or the external storage medium into the arithmetic control unit.
[0065]
Next, a package configuration for realizing a common component having a multilayered layer structure will be described.
[0066]
In the present embodiment, the AP scenario unit 30 and the AP common function unit 31 are implemented using the Java (registered trademark) development environment as described above. As is well known, the Java class library is configured by a hierarchical package group. A package is a collection of classes and interfaces that group together multiple classes and avoid namespace conflicts by separating namespaces. A class defines attributes and actions that characterize a thing, and an interface defines a method to be provided, and is like a class with no content.
[0067]
The common component of the service layer 310 and the common component of the functional layer 311 in the AP common function unit 31 are configured by the package shown in FIG. By integrating the interfaces of the common components of the functional layer 311, it is possible to provide an operation interface for application services.
[0068]
FIGS. 12 and 13 are a list of the service layer interface 130 and the packages in FIG. The content management service package P11 is used when performing the content attribute management and the content file management of FIG. The merchandise / course management service package P12 is used when managing the merchandise attributes and merchandise sales attributes shown in FIG. The product sales / distribution service package P13 is used when performing the product attribute management, the product sales attribute management, and the content distribution management of FIG. The product consumption service package P14 is used when performing user attribute management, product sale attribute management, and content distribution management in FIG. The user management service package P15 is used when performing the user attribute management of FIG.
[0069]
From the above, the service layer interface 130 in FIG.
・ Content rights attribute registration reception / registration completion notification interface
・ Content search / list / detailed reference / change / delete interface
・ Content deletion availability interface
・ Content registration procedure status search interface
・ Product / course attribute registration / registration completion notification interface
・ Product / Course Search / List / Detailed Reference / Change / Delete Interface
・ Product / Course Deletion Inquiry Interface
・ Content list / detailed interface related to product / course
・ Content distribution procedure status search interface
・ Sales history registration interface
・ Sales history search / list / detailed reference interface
・ License issuance request interface
・ Product / Course Inquiry Interface
・ Product / Course Search / List / Detailed Reference Interface
・ Product / Course purchased inquiry interface
・ Product / Course purchase interface
・ Content viewing (on-demand / download) interface
・ Usage statement data storage / search interface
・ User attribute registration / registration completion notification interface
・ User attribute search / list / detailed reference / change / delete interface
・ User attribute duplication check interface
・ User login interface
・ User password change interface
・ User password inquiry interface
-User account suspend / resume interface
It is.
[0070]
Next, a common component package related to the functional layer 311 shown in FIG. 11 will be described. FIG. 14 is a diagram showing a list of common component packages related to the functional system layer 311.
[0071]
Each package P21 to P26 of the functional layer 311 is also a package group arranged on the AP server 21. Unify operations on related platforms and local databases in units of functions. This also corresponds to the scenario model shown in FIG.
[0072]
The user management function package P21 is used when performing the user attribute management of FIG. The content management function package P22 is used when performing the content attribute management and the content file management of FIG. The product management function package P23 is used when performing the product attribute management of FIG. The sales management function package P24 is used when the product sales attribute management of FIG. 3 is performed. The billing / payment function package P25 is used when the product sales attribute management of FIG. 3 is performed. The product distribution function package P26 is used when performing the content distribution management of FIG.
[0073]
FIG. 15 shows the functional layer interface 131 of the user management function package P21. The user management function package P21 has a user attribute operation interface which is a general-purpose interface of the user information operation function, and a user authentication interface which authenticates a user and returns an authentication object.
[0074]
FIG. 16 shows the functional layer interface 131 of the content management function package P22. The content management function package P22 has a right attribute operation interface which is a general-purpose interface for the right attribute operation function, and a master content operation interface which is a general-purpose interface for the content file operation function.
[0075]
FIG. 17 shows the functional layer interface 131 of the product management function package P23. The product management function package P23 has a product attribute operation interface that is a general-purpose interface for a product attribute operation function.
[0076]
FIG. 18 shows the functional layer interface 131 of the sales management function package P24. The sales management function package P24 has a transaction history attribute operation interface which is a general-purpose interface for a transaction history operation function.
[0077]
FIG. 19 shows the functional layer interface 131 of the billing and settlement function package P25. The billing / payment function package P25 has a billing / payment attribute operation interface which is a general-purpose interface for a billing / payment attribute operation function.
[0078]
FIG. 20 shows the functional layer interface 131 of the product distribution function package P26. The product distribution function package P26 has a distribution content operation interface that is a general-purpose interface for a distribution content operation function, and a license operation interface that is a general-purpose interface for a license operation function.
[0079]
From the above, the functional layer interface 131
・ User attribute operation interface
・ User authentication interface
・ Right attribute operation interface
・ Master content operation interface
・ Product attribute operation interface
・ Transaction history attribute operation interface
・ Charge settlement attribute operation interface
・ Distributed content operation interface
・ License operation interface
It is.
[0080]
In the present embodiment, a common server system layer 220 is also provided in the AP common DB server 22 as a common component for the application. FIG. 21 shows a list of common component packages related to the common server layer 220. These packages are used in all the scenario models in FIG. It is arranged on the AP common DB server 22 and manages access to the AP common DB 23.
[0081]
The RDBMS Access Package is a bridge to the Oracle (R) DBMS / Stored Procedure / Stored Function. The transaction control package controls requests from a plurality of “common components” without contradiction. The common component management package provides an architecture that works consistently with multi-server deployment of "common components" and addition / deletion for multi-service support. The common server access wrapper provides a receiving point for requests to the common server. The common server access adapter is an interface to a common server access wrapper to be deployed on the AP server 21. Access to the AP common DB server 22 is performed via this adapter.
[0082]
The service system layer 310, the function system layer 311 and the common server system layer 220 each have the interfaces described above, so that the operator registration of the service provider 8, the service provider registration, the content registration, the product / course registration, the product / course registration, and the like. Implements course reference / change, end user list acquisition, end user unsubscribe reservation, platform operator registration, contract list acquisition, product purchase / course contract, etc.
[0083]
As a specific implementation example of the above-described package, the details of the service common component package will be described using an example.
[0084]
The user attribute registration / registration completion notification interface provided by the user management service package P15 of the service common component package defines processing of a user registration method "resist" described below.

The function outline of the above user registration method is as follows.
Register the user attribute (property) set in the user command by specifying the service provider ID and the authentication object.
-When the procedure is completed normally, the set user attribute stored in CUserInfoServicesCmd is returned to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0085]
Examples of command capsules that inherit the above-mentioned user command “CUserInfoServicesCmd” include an end-user command capsule, a PF provider operator command capsule, a PF provider system operator command capsule, a service provider operator command capsule, and a service provider command capsule. .
[0086]
A user list acquisition method “getList” defined by the user attribute search / list / detail reference / change / deletion interface provided by the user management service package P15, a user detail acquisition method “getDetail”, and a user attribute change method “ "change" and the user delete method "delete" are described below.

The function outline of the above user list acquisition method is as follows.
Search for a user attribute (property) that matches the search condition set in the user command by specifying the service provider ID and the authentication object.
-If the procedure is completed normally, add the acquired user attribute stored in the UserInfoServicesCmd to the List and return it to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.

The function outline of the above user details acquisition method is as follows.
Search for a user attribute (property) that matches the search condition set in the user command by specifying the service provider ID and the authentication object.
-When the procedure is completed normally, the set user attribute stored in CUserInfoServicesCmd is returned to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.

The function outline of the above user attribute change method is as follows.
Specify the service provider ID and the authentication object, and change the registered user attribute to the user attribute (property) set in the user command.
-When the procedure is completed normally, the set user attribute stored in CUserInfoServicesCmd is returned to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.

The functional outline of the above user deletion method is as follows.
Specify the service provider ID and the authentication object, and delete (invalidate) the user attribute (property) set in the user command.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0087]
As an example of a command capsule that inherits the user command “CUserInfoServicesCmd” in each of the above methods, an end user command capsule, a PF provider operator command capsule, a PF provider system operator command capsule, a service provider operator command capsule, a service provider command There are capsules.
[0088]
The processing of the account duplication inquiry method "isExist" defined by the user attribute duplication check interface provided by the user management service package P15 is described below.

The function outline of the account duplication inquiry method is as follows.
A service provider ID and an authentication object are specified, and an account duplication inquiry is made for a user attribute (property) that matches a search condition set in a user command.
If the procedure ends normally, true is returned to the caller if the account is duplicated, and false is returned if the account is not duplicated, as the processing result.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0089]
As an example of a command capsule that inherits the user command “CUserInfoServicesCmd” in each of the above methods, an end user command capsule, a PF provider operator command capsule, a PF provider system operator command capsule, a service provider operator command capsule, a service provider command There are capsules.
[0090]
The processing of the login method “login” defined by the user login interface provided by the user management service package P15 is described below.

The function outline of the above login method is as follows.
-Specify the service provider ID and log in with the user attribute (property) set in the user command.
When the procedure ends normally, the acquired authentication object stored in the object is returned to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
[0091]
As an example of a command capsule that inherits the user command “CUserInfoServicesCmd” in each of the above methods, an end user command capsule, a PF provider operator command capsule, a PF provider system operator command capsule, a service provider operator command capsule, a service provider command There are capsules.
[0092]
The processing of the password inquiry method “pwdQuery” defined by the user password inquiry interface provided by the user management service package P15 is described below.

The function outline of the password inquiry method is as follows.
A service provider ID and an authentication object are specified, and a query is made for a password of a user attribute (property) that matches a search condition set in a user command.
-When the procedure is completed normally, the obtained password stored in CUserInfoServices Cmd is returned to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0093]
As an example of a command capsule that inherits the user command “CUserInfoServicesCmd” in the password inquiry method, an end user command capsule, a PF operator operator command capsule, a PF operator system operator command capsule, a service operator operator command capsule, a service operator There is a command capsule.
[0094]
The processing of the password change method “pwdChange” defined by the user password change interface provided by the user management service package P15 will be described below.

The function summary of the password change method is as follows.
-Specify the service provider ID and the authentication object, and change the password of the registered user attribute to the password of the user attribute (property) set in the user command.
-If the procedure is completed normally, return the set password stored in CUserInfoServices Cmd to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0095]
Examples of command capsules that inherit the user command “CUserInfoServicesCmd” in the password change method include end-user command capsules, PF provider operator command capsules, PF provider system operator command capsules, service provider operator command capsules, and service providers. There is a command capsule.
[0096]
The processing of the usage suspension / resumption method “stopped” defined by the user account suspension / resumption interface provided by the user management service package P15 is described below.

The function summary of the above suspend / resume method is as follows.
Specify the service provider ID and the authentication object, and change the usage status of the registered user attribute to the usage status (stop or restart) of the user attribute (property) set in the user command.
-When the procedure is completed normally, the set usage status stored in CUserInfoServicesCmd is returned to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0097]
As an example of a command capsule that inherits the user command “CUserInfoServicesCmd” in the usage suspension / resumption method, an end user command capsule, a PF operator operator command capsule, a PF operator system operator command capsule, a service operator operator command capsule, a service There is a carrier command capsule.
[0098]
Next, the content right attribute registration reception / registration completion notification interface provided by the content management service package P11 of the service common component package defines processing of a right registration reservation method "resist" described below.

The functional outline of the above right registration reservation method is as follows.
Specify the service provider ID and the authentication object, and make a reservation for registration of the right attribute (property) set in the right command.
-If the procedure ends normally, return the rights attribute set in CRrightServicesCmd to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0099]
As an example of a command capsule that inherits the above-mentioned right command “CRlightServicesCmd”, there is a right command capsule.
[0100]
The content search / list / detailed reference / change / deletion interface provided by the content management service package P11 includes a rights list acquisition method “getList”, a right details acquisition method “getDetail”, a right attribute change method “change”, and a right It defines the process of the attribute delete method "delete".

The function summary of the above right list acquisition method is as follows.
Search for the right attribute (property) set in the right command by specifying the service provider ID and the authentication object.
-When the procedure is completed normally, the acquired rights attribute stored in CRlightServicesCmd is added to List and returned to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.

The functional outline of the above right details acquisition method is as follows.
Search for a right attribute (property) that matches the search condition set in the right command by specifying the service provider ID and the authentication object.
-If the procedure ends normally, return the rights attribute obtained in CRrightServicesCmd to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.

The function outline of the right attribute change method is as follows.
Specify the service provider ID and the authentication object, and change the registered right attribute to the right attribute (property) set in the right command.
-If the procedure ends normally, return the rights attribute set in CRrightServicesCmd to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.

The functional outline of the above right attribute deletion method is as follows.
The service provider ID and the authentication object are specified, and the right attribute (property) set in the right command is deleted (attribute invalidation).
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0101]
As an example of a command capsule that inherits the rights command “CRlightServicesCmd” in each of the above methods, there is a rights command capsule “CRlightsCmd”.
[0102]
Next, the product / course attribute registration / registration completion notification interface provided by the product / course management service package P12 of the service common component package defines processing of the following product / course attribute registration method “resist”. .

The function summary of the product / course attribute registration method is as follows.
Register the product / course attribute attribute (property) set in the product / course command by specifying the service provider ID and the authentication object.
-If the procedure ends normally, return the product / course attribute set in CCommodityServicesCmd to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0103]
An example of a command capsule that inherits the product / course command “CCommodityServicesCmd” includes a product command capsule and a course command capsule.
[0104]
The product / course search / list / detailed reference / change / deletion interface provided by the product / course management service package P12 is, for example, a product / course list acquisition method “getCommodityList” and a product / course detail acquisition method “getCommodityDetail” shown below. Is defined.

The function summary of the product / course attribute registration method is as follows.
Search for a product / course attribute attribute (property) that matches the search condition set in the product / course command by specifying the service provider ID and the authentication object. -If the procedure ends normally, add the product / course attribute acquired in CCommodityServicesCmd to the list and return it to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.

The function summary of the above product / course details acquisition method is as follows.
Search for a product / course attribute attribute (property) that matches the search condition set in the product / course command by specifying the service provider ID and the authentication object. -If the procedure is completed normally, return the product / course attribute obtained in the CCommodityServicesCmd stored in the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0105]
As an example of a command capsule that inherits the product / course command “CCommodityServicesCmd” in each of the above methods, there is a product command capsule and a course command capsule.
[0106]
The content list / details interface associated with the product / course provided by the product / course management service package P12 defines the processing of the associated content list acquisition method “getContentList” described below.

The function summary of the above related content list acquisition method is as follows.
A service provider ID and an authentication object are specified, and a content attribute (property) associated with a product / course that matches the search condition set in the association command is searched.
-If the procedure ends normally, add the acquired content attribute stored in CCommodityServicesCmd to List and return it to the caller.
The service provider ID is used for managing service provider information such as specifying a schema of a common component (storage server).
-The authentication object is used for authentication when making a registration request to each platform.
[0107]
An example of a command capsule that inherits the association command “CCommodityServicesCmd” in the association content list acquisition method is an association command capsule.
[0108]
An operation example of the service layer 310 and the function layer 311 using the above interface will be described according to an example in which the service layer 310 receives a request for “contents right information registration” from the AP scenario unit 30.
[0109]
The AP scenario unit 30 calls the right registration reservation method (CRightsServicesCmd.resist (service provider ID, authentication object, right command)) of the right service interface in the content management service package P11, and the service layer 310 executes this. .
[0110]
The service system layer 310 checks whether the parameters are normal and whether they are authenticated. If the parameters are not normal or if the service business ID is not authenticated, the service scenario 310 sends an “impossible” message to the AP scenario unit 30. Is returned.
[0111]
If the parameters are normal and authenticated, the function right layer 311 is requested to register the content right information. At this time, the service layer 310 calls the right attribute registration method (AccessAccessContntRightsInfo.entry (service provider ID, authentication object, right access command)) of the right attribute operation interface in the content management function package P22, and calls this function layer. 311 executes.
[0112]
The service layer 310 receives the result of the content right information registration as the return value of the right attribute registration method of the right attribute operation interface in the called content management function package P22. The result of the content right information registration received as this return value is returned to the AP scenario unit 30.
[0113]
The above is an example. The present invention is not limited to the specific configuration method itself of these packages and interfaces, but includes the layer configuration of the AP server 21, especially the AP common function unit 31, and the types of packages and interfaces that exist. It is clear that it is clear from the above description that the interfaces and methods of other packages can be easily configured in the same way, so that a description of all packages and interfaces beyond this will be omitted. .
[0114]
Hereinafter, an example of a processing flow for various request processing in the content distribution service will be described using a representative example.
[0115]
FIG. 22 and FIG. 23 are diagrams showing an example of a service provider operator (OP) password inquiry information check processing flow using the present invention. First, as pre-processing, processing related to screen transitions and appearance other than logic is performed in the AP scenario unit 30 (step S21). For example, processing such as input screen display, input value screen check, and confirmation screen display is performed.
[0116]
Then, the AP scenario unit 30 requests the service layer 310 to execute a service provider OP search process (step S22). In this case, the business operator, authentication information, search conditions, and the like are passed as arguments as command capsules. Next, the service layer 310 creates a command for issuing a processing request to the functional layer 311 (step S23). Further, it requests the functional system layer 311 to execute a general-purpose search process (step S24). In this case, the search for the service provider OP is requested to the general-purpose search processing function.
[0117]
Next, the functional layer 311 constructs a service provider OP search logic (step S25). Further, it requests the common server system layer 220 to execute a search process (step S26). In this case, a search command issuance request for the common server is made. Next, the common server layer 220 executes a service provider OP search (step S27). In this case, an optimized search command is issued. Then, the search result is received, and the result is returned to the functional layer 311 (step S28).
[0118]
Next, the functional layer 311 receives the search result and assembles the return search result (step S29). Then, the result is returned to the service layer 310 (step S30).
[0119]
Next, the service layer 310 receives the search result and assembles the return search result (step S31). Next, the result is returned to the AP scenario unit 30 (step S32). Next, the service provider OP search process is received by the AP scenario unit 30 (step S33). Then, in the AP scenario unit 30, processing relating to screen transitions, appearance, and the like other than logic is performed (step S34). For example, a confirmation result screen is displayed.
[0120]
FIGS. 24 to 27 are examples of sequence diagrams in the service provider OP password inquiry information check using the present invention. In the figure, reference numeral 18 denotes a mail server.
[0121]
A) First, on the service provider top menu screen of the client PC 8 ′, by clicking the “Service Provider Operator Password Inquiry” link and inquiring of the AP scenario section 30 of the AP server, the AP scenario section 30 returns to the client PC 8 ′. To display the password inquiry information input screen. Clicking the “Send” link on the input screen sends the inquiry information to the AP scenario unit 30.
[0122]
B) Next, the AP scenario unit 30 performs a password inquiry information check action, checks required items based on the inquiry information, and then passes the search condition as an argument to the common function unit of the service layer 310 as a command capsule 108. Request to obtain the service provider OP list.
[0123]
CD) Next, the service layer 310 creates a command for issuing a processing request to the functional layer 311 and passes the search condition to the functional layer 311 as the command capsule 108 to execute the service provider OP search process. Ask for.
[0124]
E) Next, the functional layer 311 constructs a service provider OP search logic and passes the search condition to the command capsule execution engine 312.
[0125]
F) The command capsule execution engine 312 passes the search execution statement to the common server system layer 220 and requests the service provider OP to execute the search.
[0126]
GM) The AP common DB server 22 searches the service provider OP information and returns the search result to the functional layer 311. This search result is returned to the service layer 310 via the command capsule execution engine 312 and the functional layer 311. The service layer 310 that has received the search result returns the search result to the AP scenario unit 30.
[0127]
N) Upon receiving the service provider OP search result, the AP scenario unit 30 performs a service provider existence check and a service provider operator e-mail address match check, passes a search condition to the service layer 310, and changes the service provider OP password. Contact us.
[0128]
(OP) The service layer 310 passes the search condition to the functional layer 311. The functional layer 311 transmits the notification mail to the mail server 18, constructs a service provider OP search logic (SELECT statement or the like), and passes the search condition to the command capsule execution engine 312. The command capsule execution engine 312 passes the search execution statement to the AP common DB server 22 and requests the service provider OP search execution.
[0129]
QR) The AP common DB server 22 searches for service provider OP information, and returns the search result to the command capsule execution engine 312. This search result is returned to the service layer 310 via the command capsule execution engine 312 and the functional layer 311.
[0130]
(SU) The service layer 310 returns the search result to the AP scenario unit 30, and the AP scenario unit 30 receiving the search result performs a process related to display of a confirmation result screen and transmits an inquiry result to the client PC 8 '. And display the password transmission completion screen. Further, a notification mail is transmitted from the mail server 18 to the client PC 8 '.
[0131]
28 and 29 are diagrams showing an example of a product / course search processing flow using the present invention. First, as pre-processing, processing related to screen transitions and appearance other than logic is performed in the AP scenario unit 30 (step S41). For example, processing such as input screen display, input value screen check, and confirmation screen display is performed. Then, the AP scenario unit 30 requests the service layer 310 to execute a product / course search process (step S42).
[0132]
Next, the service layer 310 creates a command for issuing a processing request to the functional layer 311 (step S43). Further, it requests the functional layer 311 to execute a general-purpose search process (step S44). Next, the functional layer 311 constructs a product / course search logic (step S45). Further, it requests the common server system layer 220 to execute a search process (step S46).
[0133]
Next, the common server system layer 220 executes a product / course search (step S47). Then, the search result is received, and the result is returned to the functional layer 311 (step S48). Next, the functional layer 311 receives the search result and assembles the return search result (step S49). Then, the result is returned to the service layer 310 (step S50).
[0134]
Next, the service layer 310 receives the search result and assembles the return search result (step S51). Next, the result is returned to the AP scenario unit 30 (step S52). Next, the product / course search process is received by the AP scenario unit 30 (step S53), and processes related to screen transition and appearance other than logic are performed (step S54). For example, a confirmation result screen is displayed.
[0135]
FIGS. 30 to 32 are diagrams showing an outline of a processing flow in service provider content right information registration using the present invention. 19 is an upload server in the figure. First, as pre-processing, processing related to screen transitions and appearance other than logic is performed in the AP scenario unit 30 (step S61). For example, an input screen display, an input screen check, a confirmation screen display, and the like are performed. Then, the AP scenario unit 30 requests the service layer 310 to execute the content right information registration process (step S62). In this case, the business operator, authentication information, registration information, etc. are passed as arguments as command capsules.
[0136]
Next, the service layer 310 creates a command for issuing a processing request to the functional layer 311 (step S63). Then, it requests the functional layer 311 to execute the right information registration process (step S64). In this case, a processing request is made for the corresponding content registration in the general-purpose right information registration. Next, a content right information registration logic is constructed in the functional layer 311 (step S65). For example, a logic for insertion of a business authentication, a copyright registration, an ID payout, a watermark and the like is constructed.
[0137]
In the functional layer 311, each logic process is performed in the AP, and each PF element is requested to execute each logic process (step S 66). For example, the AP executes asynchronous processing management processing such as business authentication processing, registration information conversion / operation processing, and watermark insertion in the AP, requests the upload server 19 to execute content copy processing, and issues a request to the copyright management PF 13 Request to execute the content ID issuing process. Further, it requests the AP common DB server 22 to execute a right information storage process.
[0138]
In each PF element, the processing requested by the functional layer 311 is executed (step S74). Next, the functional layer 311 constructs and sends an asynchronous processing request message (step S67), assembles the logic execution result (step S68), and returns the result to the service layer 310 (step S69). Next, in the service layer 310, the search result is received and the return search result is assembled (step S70). Then, the result is returned to the AP scenario unit 30 (step S71).
[0139]
The AP scenario unit 30 receives the service provider content right information registration reception result (step S72), and performs processing related to screen transition and appearance other than logic (step S73). For example, a confirmation result notification screen is displayed. Hereinafter, the same processing is continued.
[0140]
As described above, according to the present invention, the application is divided into the AP scenario unit 30 and the AP common function unit 31, and the AP common function unit 31 is hierarchized into the service layer 310 and the function layer 311. For example, if a higher-level application needs to be modified, it can be absorbed by modifying the interface of the uppermost layer so that the lower-level PF element is not affected. That is, the lower interface and platform may be left as they are.
[0141]
Conversely, if the lower-order PF element changes, it can be absorbed by modifying the lower-order interface, leaving the above-mentioned application unaffected and leaving it as it is, thereby expanding customization and expandability.
[0142]
【The invention's effect】
As described above, the present invention has the following features.
・ System development to support various business models becomes easy.
-By using common components that can be used in common and reusing reusable components, effective use of development resources can be achieved and development efficiency can be increased.
-It is possible to develop applications using the PF elements used in the system without having to know how to use them.
[Brief description of the drawings]
FIG. 1 is an overall conceptual configuration diagram of a content distribution network system.
FIG. 2 is a detailed configuration diagram of a content distribution system.
FIG. 3 is a diagram showing a scenario model of content distribution.
FIG. 4 is a diagram showing an outline of a service system layer, a function system layer, and a common server system layer.
FIG. 5 is a diagram illustrating a configuration example of an entire system including a platform.
FIG. 6 is a configuration diagram showing a relationship between components mounted on an AP server.
FIG. 7 is an explanatory diagram of an interface, a method, a command capsule, and a command capsule execution engine.
FIG. 8 is a diagram showing an operation processing flow of a common component.
FIG. 9 is a diagram showing a description of a composite, a command, and a mediator.
FIG. 10 is a functional block diagram of a functional layer and a command capsule execution engine.
FIG. 11 is a diagram showing a package and an interface in an AP common function unit.
FIG. 12 is a diagram showing a list of service system layer interfaces and packages.
FIG. 13 is a diagram showing a list of service system layer interfaces and packages.
FIG. 14 is a diagram showing a list of packages of functional layers.
FIG. 15 is a diagram illustrating an example of a functional layer interface of the user management function package.
FIG. 16 is a diagram showing an example of a functional layer interface of the content management function package.
FIG. 17 is a diagram illustrating an example of a functional layer interface of the product management function package.
FIG. 18 is a diagram illustrating an example of a functional layer interface of the sales management function package.
FIG. 19 is a diagram illustrating an example of a functional layer interface of the billing and settlement function package.
FIG. 20 is a diagram illustrating an example of a functional layer interface of a product distribution function package.
FIG. 21 is a diagram showing a list of common component packages related to a common server system layer.
FIG. 22 is a diagram showing an example of a service provider OP password inquiry information check processing flow.
FIG. 23 is a diagram showing an example of a service provider OP password inquiry information check processing flow.
FIG. 24 is a diagram showing an example of a sequence diagram in a service provider OP password inquiry information check using the present invention.
FIG. 25 is a diagram showing an example of a sequence diagram in a service provider OP password inquiry information check using the present invention.
FIG. 26 is a diagram showing an example of a sequence diagram in a service provider OP password inquiry information check using the present invention.
FIG. 27 is a diagram showing an example of a sequence diagram in a service provider OP password inquiry information check using the present invention.
FIG. 28 is a diagram showing an example of a product / course search processing flow using the present invention.
FIG. 29 is a diagram showing an example of a product / course search processing flow using the present invention.
FIG. 30 is a diagram showing an outline of a processing flow in service provider content right information registration using the present invention.
FIG. 31 is a diagram showing an outline of a processing flow in service provider content right information registration using the present invention.
FIG. 32 is a diagram showing an outline of a processing flow in service provider content right information registration using the present invention.
[Explanation of symbols]
1 Content distribution system in a broad sense
2 Content distribution system in a narrow sense
3 Data Center
4 Internet
5 ISP
6 End user
7 Dedicated line
8 service providers
9 Settlement agency
10 PF operator
11 Each PF element
12 Billing settlement PF
13 Copyright Management PF
14 License server
15 VOD distribution server
16 Download server
17 Archive server
21 AP server
22 AP common DB server
23 AP common DB
24 Browser
30 AP scenario section
31 AP Common Function Unit
100 HTTP server
101 PF cooperation system
102, 103, 104, 105, 106, 107 Platform Interface (PFIF)
108 Command capsule
110 Server of each PF element
130 Service layer interface
131 Functional Layer Interface
132 Individual PF Adapter Interface
220 Common server layer
300 individual AP
301 Service screen in AP scenario section
302 AP control component in AP scenario part
310 Service layer
311 Functional layer
312 Command capsule execution engine

Claims (6)

In a content distribution apparatus having an application server for distributing content using a server of a platform element prepared for content distribution,
The application server,
An application scenario section corresponding to the application of the content distribution service model to be realized,
Includes two layers of application common function parts consisting of parts that do not change depending on the application,
The application common function unit includes:
A service layer having an interface with the application scenario section;
It is divided into a functional layer having an interface with the platform element,
The service layer provides the application scenario section with an interface that integrates the interface of the functional layer from a service viewpoint for each content distribution service model,
The content distribution device, wherein the functional layer provides a related interface in which operation interfaces of the related platform elements are integrated for each function. The content distribution device according to claim 1,
The functional layer is
User management function package for registering, searching, updating and deleting user attributes,
Content management function package for registering, searching and deleting content rights attributes,
Product management function package for registering, searching, updating and deleting product attributes,
Sales management function package for registering, searching, updating and deleting sales history attributes of products,
Billing and payment function package for billing and payment of goods,
Or at least one of a plurality of product distribution function packages for distributing content,
The service layer is
A content management service package for processing related to content right attribute registration, processing related to content search, reference, change, and deletion, processing related to content deletion permission / inquiry, processing related to content registration procedure status search,
Product / course management that performs processing related to product / course attribute registration, processing related to product / course search, reference, change, and deletion, processing related to product / course deletion availability inquiry, and processing related to the list of contents or details related to the product / course Service package,
A product sales / distribution service package that performs processing related to content distribution procedure status search, processing related to sales history registration, processing related to sales history search and reference, processing related to license issuance request,
Merchandise consumption service package that performs merchandise / course inquiry processing, merchandise course search and reference processing, merchandise / course purchase inquiry processing, merchandise / course purchase processing, content viewing / listening, usage details data storage, and search processing ,
And user attribute registration, user attribute search, reference, change, and deletion, user attribute duplication check, user login, user password change, user password inquiry, user account suspension A content distribution apparatus comprising at least one of a plurality of user management service packages for performing a process related to / resumption. The content distribution device according to claim 1,
The functional layer is
Interface for user attribute operation provided by the user management function package,
Interface for user authentication provided by the user management function package,
Interface for rights attribute operation provided by the content management function package,
Interface for master content operation provided by the content management function package,
Interface for product attribute operation provided by the product management function package,
Interface for operating transaction history attributes provided by the sales management function package,
Interface for operating the billing / payment attributes provided by the billing / payment package,
Interface for operating the distribution content provided by the product distribution function package,
And at least one of a plurality of interfaces for license operation provided by the product distribution function package,
The service layer is
Interface for receiving / registering completion of registration of content rights attributes provided by the content management service package,
Interface for content search / list / detailed reference / change / deletion provided by content management service package,
Interface for inquiring whether content can be deleted provided by the content management service package,
Interface for content registration procedure status search provided by content management service package,
Interface for product / course attribute registration / registration completion notification provided by product / course management package,
Interface for product / course search / list / detailed reference / change / deletion provided by product / course management package,
Interface for inquiring whether products / courses can be deleted provided by the product / course management package,
Product / Course Management Package provides interface for content list / detailed reference related to product / course provided by package,
Interface for content distribution procedure status search provided by product sales / distribution service package,
Interface for registering sales history provided by product sales / distribution service package,
Interface for sales history search / list / details reference provided by product sales / distribution service package,
Interface for requesting license issuance provided by product sales / distribution service package,
Interface for product / course inquiry provided by the product consumption service package,
Interface for product / course search / list / detailed reference provided by product consumption service package,
Interface for product / course purchase inquiry provided by the product consumption service package,
An interface for purchasing products / courses provided by the product consumption service package,
An interface for viewing or on-demand / downloading content provided by the product consumption service package,
Interface for storing / retrieving usage details data provided by the product consumption service package,
Interface for user attribute registration / registration completion notification provided by the user management service package,
Interface for user attribute search / list / detailed reference / change / deletion provided by user management service package,
Interface for checking duplicate user attributes provided by the user management service package,
User login interface provided by the user management service package,
Interface for changing user password provided by user management service package,
Interface for querying user password provided by user management service package,
A content distribution apparatus having at least any one of interfaces for suspending / resuming a user account provided by a user management service package. An application server that distributes content using a server of platform elements prepared for content distribution is provided,
The application server includes two layers: an application scenario unit corresponding to the application of the content distribution service model to be realized; and an application common function unit including a part that does not change depending on the application.
The application common function unit is configured to be divided into a service system layer having an interface with the application scenario unit and a function system layer having an interface with the platform element.
A content distribution processing method for distributing content using a content distribution device, comprising:
Requesting processing related to content management, merchandise / course management, merchandise sales / distribution, merchandise consumption or user management using the interface provided by the service layer from the application scenario unit;
In the service layer, in response to a processing request from the application scenario section, an interface related to a user management function, a content management function, a product management function, a sales management function, a charge settlement function, or a product distribution function provided by the functional layer is provided. Requesting the functional layer to perform processing,
A step of issuing an operation command to the related platform element in response to a processing request from the service layer in the functional layer. A content distribution system program for realizing a content distribution device according to claim 1, 2 or 3 by a computer. A computer-readable recording medium storing a content distribution system program for realizing the content distribution apparatus according to claim 1, 2 or 3 by a computer.

Images