Network account linking
Abstract
This record has no abstract on file.
Term
Term ended
Expired 15 July 2024, 2.2 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
59 claims: 10 independent, 49 dependent
- 1ネットワークアカウントを管理するための装置により実行される管理方法であって、 一般アクセスを有する第2のアカウントが当該第2のアカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記第2のアカウントがメンバアクセスを有する第1のアカウントにリンク案内の要求を送信するステップと、 前記 第1のアカウントのアクセスレベルの少なくとも一部を 前記 第2のアカウントと共有することで、前記第1のアカウントに前記第2のアカウントをリンクするステップと、 前記第2のアカウントが前記第1のアカウントにリンクされている間、前記メンバアクセスの少なくとも一部を前記第2のアカウントに付与するステップと、を含み、 前記第1のアカウントは対応するサブスクリプションを有しており、 前記一般アクセスは少なくとも1つの特権を付与し、 前記メンバアクセスは、前記一般アクセスによって提供されない2以上の特権を付与する、 方法。
- 2前記サブスクリプションの費用は、一般アクセスを有するアカウントを得るのに必要な費用よりも高い、 請求項1に記載の方法。
- 3前記メンバアクセスの特権は、オンラインゲームへの参加をアカウントに許可することを含む、 請求項1に記載の方法。
- 4前記メンバアクセスの特権は、オンラインゲームの開始をアカウントに許可することを含む、 請求項1に記載の方法。
- 5前記メンバアクセスの特権は、制限されたオンライン資源へのアクセスをアカウントに許可することを含む、 請求項1に記載の方法。
- 6前記メンバアクセスの特権は、アカウントがメンバアクセスを有することを示すようにして、オンラインゲームへの参加を前記アカウントに許可することを含む、 請求項1に記載の方法。
- 7前記メンバアクセスの特権は、アカウントがメンバアクセスを有することを示す視覚的な合図を付けて、オンラインゲームへの参加を前記アカウントに許可することを含む、 請求項6に記載の方法。
- 8前記メンバアクセスの特権は、当該メンバアクセスの特権を持たないアカウントが参加する方法とは異なる方法で、オンラインゲームへの参加をアカウントに許可することを含む、 請求項1に記載の方法。
- 9前記メンバアクセスの特権は、メンバアクセスを持たないアカウントが利用できない、オンラインゲーム内の1以上の特別な資源へのアクセスをアカウントに許可することを含む、 請求項8に記載の方法。
- 10前記メンバアクセスの特権は、当該メンバアクセスの特権を持たないアカウントが利用できない、オンラインゲーム内の1以上の特別な機能へのアクセスをアカウントに許可することを含む、 請求項8に記載の方法。
- 11前記第1のアカウントはメンバ限定のアクセスも有しており、 前記メンバ限定のアクセスは、前記メンバアクセスによって付与される前記2以上の特権と異なり、且つ前記一般アクセスによって付与される前記少なくとも1つの特権とも異なる1以上の特権を付与する、 請求項1に記載の方法。
- 12前記第2のアカウントが前記第1のアカウントにリンクされている場合に、前記第2のアカウントはメンバ限定のアクセスを有さない、 請求項11に記載の方法。
- 13前記第1のアカウントは前記一般アクセスも有する、 請求項1に記載の方法。
- 14前記サブスクリプションを示すメンバアカウントの作成要求を受け取るステップと、 前記サブスクリプションがメンバアカウントの作成を許可していることを確認するステップと、 前記第1のアカウントを作成するステップと、を更に含む、 請求項1に記載の方法。
- 15メンバアカウントの作成の許可が確認されない場合に、メンバアカウントの作成を許可するために前記サブスクリプションをアップグレードするステップを更に含む、 請求項14に記載の方法。
- 16非メンバアカウントの作成要求を受け取るステップと、 前記第2のアカウントを作成するステップと、を更に含む、 請求項1に記載の方法。
- 17前記第1のアカウント及び前記第2のアカウントを示すリンク要求を受け取るステップと、 前記第1のアカウントがリンクを許可していることを確認するステップと、を更に含む、 請求項1に記載の方法。
- 18前記第2のアカウントがリンクを許可していることを確認するステップを更に含む、 請求項17に記載の方法。
- 19前記第1のアカウント及び前記第2のアカウントを示すリンク解除要求を受け取るステップと、 前記付与された前記メンバアクセスの少なくとも一部を、前記第2のアカウントから破棄するステップと、 前記第1のアカウントから前記第2のアカウントをリンク解除するステップと、を更に含む、 請求項1に記載の方法。
- 20所定のアクセス及びアカウントを有するサービスを示すサービス要求を受け取るステップと、 要求元の前記アカウントが、前記指示されたサービスの前記所定のアクセスを満たすアクセスを現在有していることを確認するステップと、 前記サービスを提供するステップと、を更に含む、 請求項1に記載の方法。
- 21要求元の前記アカウントを、前記指示されたサービスの前記所定のアクセスを満たすアクセスを有するようにアップグレードするステップを更に含む、 請求項20に記載の方法。
- 22前記メンバアクセスの前記少なくとも一部を付与するステップは、前記メンバアクセスの前記2以上の特権の総数よりも少ない数の特権を前記第2のアカウントに付与するステップを含む、 請求項1に記載の方法。
- 23前記メンバアクセスの前記少なくとも一部を付与するステップは、限られた時間、前記メンバアクセスの前記2以上の特権の少なくとも1つを前記第2のアカウントに付与するステップを含む、 請求項1に記載の方法。
- 24前記第2のアカウントが前記第1のアカウントにリンクされている間は、前記第1のアカウントから前記メンバアクセスを削除するステップを更に含む、 請求項1に記載の方法。
- 25前記第2のアカウントは、中間データオブジェクトによって前記第1のアカウントに間接的にリンクされる、 請求項1に記載の方法。
- 26前記中間データオブジェクトはプールである、 請求項25に記載の方法。
- 27ネットワークアカウントを管理するための装置により実行される管理方法であって、 一般アクセスを有するアカウントを作成するステップと、 前記 一般アクセスを有するアカウントが当該アカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記アカウントが他のアカウントにリンク案内の要求を送信するステップと、 アップグレード要求を受け取るステップと、 前記アカウントがメンバアクセスを有するための1以上の要件を満たしている場合に、前記アカウントがアップグレードを許可されることを確認するステップと、 前記アカウントを前記一般アクセスよりも多くのアクセスレベルを提供するメンバアクセスにアップグレードして、前記アカウントに前記メンバアクセスのサービスの少なくとも一部を提供するステップと、を含む、 方法。
- 28ネットワークアカウントを管理するための装置により実行されるリンク方法であって、 一般アクセスを有する第1のアカウントを作成するステップと、 前記 第1のアカウントが当該第1のアカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記第1のアカウントがメンバアクセスを有する第2のアカウントにリンク案内を送信するステップと、 前記第1のアカウントのアクセスレベルを前記第2のアカウントのアクセスレベルの少なくとも一部と共有することで前記第1のアカウントが前記第2のアカウントにリンクされることを示すリンク承諾を受け取るステップと、 メンバアクセスを必要とする所定のアクセスを有するサービスを示すサービス要求を送信するステップと、 前記サービスにアクセスするステップと、を含む、 方法。
- 29ネットワークアカウントを管理するための装置により実行されるリンク方法であって、 メンバアクセスを有する第1のアカウントを作成するステップと、 一般アクセスを有する第2のアカウントが当該第2のアカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記第2のアカウントがメンバアクセスを有する第1のアカウントにリンク案内の要求を送信するステップと、 前記 第2のアカウントを示すリンク案内を受け取るステップと、 前記第1のアカウントのアクセスレベルの少なくとも一部を前記第2のアカウントと共有することで前記第2のアカウントが前記第1のアカウントにリンクされる、ことを示すリンク要求を送信して、前記第2のアカウントへの前記メンバアクセスのサービスの少なくとも一部を提供可能にするステップと、を含む、 方法。
- 30有形の記憶媒体に記憶され、ネットワークアカウントの管理に使用されるコンピュータに、 一般アクセスを有する第2のアカウントが当該第2のアカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記第2のアカウントがメンバアクセスを有する第1のアカウントにリンク案内の要求を送信するための実行可能命令と、 前記 第1のアカウントに 前記 第2のアカウントをリンクするための実行可能命令と、 前記第1のアカウントのアクセスレベルの少なくとも一部を前記第2のアカウントと共有して前記第2のアカウントが前記第1のアカウントにリンクされている間、前記メンバアクセスの少なくとも一部を前記第2のアカウントに付与するための実行可能命令と、を実行させ、 前記第1のアカウントが対応するサブスクリプションを有しており、 前記一般アクセスが少なくとも1つの特権を付与し、 前記メンバアクセスが、前記一般アクセスによって提供されない2以上の特権を付与する、 ことを実行させるためのコンピュータプログラム。
- 31前記サブスクリプションの費用は、一般アクセスを有するアカウントを得るのに必要な費用よりも高い、 請求項30に記載のコンピュータプログラム。
- 32前記メンバアクセスの特権は、オンラインゲームへの参加をアカウントに許可することを含む、 請求項30に記載のコンピュータプログラム。
- 33前記メンバアクセスの特権は、オンラインゲームの開始をアカウントに許可することを含む、 請求項30に記載のコンピュータプログラム。
- 34前記メンバアクセスの特権は、制限されたオンライン資源へのアクセスをアカウントに許可することを含む、 請求項30に記載のコンピュータプログラム。
- 35前記メンバアクセスの特権は、アカウントがメンバアクセスを有することを示すようにして、オンラインゲームへの参加を前記アカウントに許可することを含む、 請求項30に記載のコンピュータプログラム。
- 36前記メンバアクセスの特権は、アカウントがメンバアクセスを有することを示す視覚的な合図を付けて、オンラインゲームへの参加を前記アカウントに許可することを含む、 請求項35に記載のコンピュータプログラム。
- 37前記メンバアクセスの特権は、当該メンバアクセスの特権を持たないアカウントが参加する方法とは異なる方法で、オンラインゲームへの参加をアカウントに許可することを含む、 請求項30に記載のコンピュータプログラム。
- 38前記メンバアクセスの特権は、メンバアクセスを持たないアカウントが利用できない、オンラインゲーム内の1以上の特別な資源へのアクセスをアカウントに許可することを含む、 請求項37に記載のコンピュータプログラム。
- 39前記メンバアクセスの特権は、当該メンバアクセスの特権を持たないアカウントが利用できない、オンラインゲーム内の1以上の特別な機能へのアクセスをアカウントに許可することを含む、 請求項37に記載のコンピュータプログラム。
- 40前記第1のアカウントはメンバ限定のアクセスも有しており、 前記メンバ限定のアクセスは、前記メンバアクセスによって付与される前記2以上の特権と異なり、且つ前記一般アクセスによって付与される前記少なくとも1つの特権とも異なる1以上の特権を付与する、 請求項30に記載のコンピュータプログラム。
- 41前記第2のアカウントが前記第1のアカウントにリンクされている場合に、前記第2のアカウントはメンバ限定のアクセスを有さない、 請求項40に記載のコンピュータプログラム。
- 42前記第1のアカウントは前記一般アクセスも有する、 請求項30に記載のコンピュータプログラム。
- 43コンピュータに、 前記サブスクリプションを示すメンバアカウントの作成要求を処理するための実行可能命令と、 前記サブスクリプションがメンバアカウントの作成を許可していることを確認するための実行可能命令と、 前記第1のアカウントを作成するための実行可能命令と、を更に実行させるための、 請求項30に記載のコンピュータプログラム。
- 44コンピュータに、 メンバアカウントの作成の許可が確認されない場合に、メンバアカウントの作成を許可するために前記サブスクリプションをアップグレードするための実行可能命令を更に実行させるための、 請求項43に記載のコンピュータプログラム。
- 45コンピュータに、 非メンバアカウントの作成要求を処理するための実行可能命令と、 前記第2のアカウントを作成するための実行可能命令と、を更に実行させるための、 請求項30に記載のコンピュータプログラム。
- 46コンピュータに、 前記第1のアカウント及び前記第2のアカウントを示すリンク要求を処理するための実行可能命令と、 前記第1のアカウントがリンクを許可していることを確認するための実行可能命令と、を更に実行させるための、 請求項30に記載のコンピュータプログラム。
- 47コンピュータに、 前記第2のアカウントがリンクを許可していることを確認するための実行可能命令を更に実行させるための、 請求項46に記載のコンピュータプログラム。
- 48コンピュータに、 前記第1のアカウント及び前記第2のアカウントを示すリンク解除要求を処理するための実行可能命令と、 前記付与された前記メンバアクセスの少なくとも一部を、前記第2のアカウントから破棄するための実行可能命令と、 前記第1のアカウントから前記第2のアカウントをリンク解除するための実行可能命令と、を更に実行させるための、 請求項30に記載のコンピュータプログラム。
- 49コンピュータに、 所定のアクセス及びアカウントを有するサービスを示すサービス要求を処理するための実行可能命令と、 要求元の前記アカウントが、前記指示されたサービスの前記所定のアクセスを満たすアクセスを現在有していることを確認するための実行可能命令と、 前記サービスを提供するための実行可能命令と、を更に実行させるための、 請求項30に記載のコンピュータプログラム。
- 50コンピュータに、 要求元の前記アカウントを、前記指示されたサービスの前記所定のアクセスを満たすアクセスを有するようにアップグレードするための実行可能命令を更に実行させるための、 請求項49に記載のコンピュータプログラム。
- 51前記メンバアクセスの前記少なくとも一部の付与は、前記メンバアクセスの前記2以上の特権の総数よりも少ない数の特権の前記第2のアカウントへの付与である、 請求項30に記載のコンピュータプログラム。
- 52前記メンバアクセスの前記少なくとも一部の付与は、限られた時間、前記メンバアクセスの前記2以上の特権の少なくとも1つの前記第2のアカウントへの付与である、 請求項30に記載のコンピュータプログラム。
- 53コンピュータに、 前記第2のアカウントが前記第1のアカウントにリンクされている間は、前記第1のアカウントから前記メンバアクセスを削除するための実行可能命令を更に実行させるための、 請求項30に記載のコンピュータプログラム。
- 54前記第2のアカウントは、中間データオブジェクトによって前記第1のアカウントに間接的にリンクされる、 請求項30に記載のコンピュータプログラム。
- 55前記中間データオブジェクトはプールである、 請求項54に記載のコンピュータプログラム。
- 56有形の記憶媒体に記憶され、ネットワークアカウントの管理に使用されるコンピュータに、 一般アクセスを有するアカウントを作成するための実行可能命令と、 前記 一般アクセスを有するアカウントが当該アカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記アカウントが他のアカウントにリンク案内の要求を送信するための実行可能命令と、 アップグレード要求を処理するための実行可能命令と、 前記アカウントが前記アカウントを前記一般アクセスよりも多くのアクセスレベルを提供するメンバアクセスを有するための1以上の要件を満たしている場合に、前記アカウントが前記メンバアクセスのサービスを有するようにアップグレードを許可されることを確認するための実行可能命令と、 メンバアクセスを有するように前記アカウントをアップグレードするための実行可能命令と、 を実行させるためのコンピュータプログラム。
- 57有形の記憶媒体に記憶され、ネットワークアカウントのリンクに使用されるコンピュータに、 一般アクセスを有する第1のアカウントを作成するための実行可能命令と、 前記 第1のアカウントが当該第1のアカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記第1のアカウントがメンバアクセスを有する第2のアカウントにリンク案内を送信するための実行可能命令と、 前記第1のアカウントのアクセウスレベルを前記第2のアカウントのアクセスレベルの少なくとも一部と共有することで前記第1のアカウントが前記第2のアカウントにリンクされることを示すリンク承諾を処理するための実行可能命令と、 メンバアクセスを必要とする所定のアクセスを有するサービスを示すサービス要求を送信するための実行可能命令と、 前記サービスにアクセスするための実行可能命令と、 を実行させるためのコンピュータプログラム。
- 58有形の記憶媒体に記憶され、ネットワークアカウントのリンクに使用されるコンピュータに、 メンバアクセスを有する第1のアカウントを作成するための実行可能命令と、 一般アクセスを有する第2のアカウントが当該第2のアカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記第2のアカウントがメンバアクセスを有する第1のアカウントにリンク案内の要求を送信するための実行可能命令と、 前記第1のアカウントのアクセスレベルの少なくとも一部を前記第2のアカウントと共有することで前記第2のアカウントが前記第1のアカウントにリンクされる、ことを示すリンク要求を送信して、前記第2のアカウントへの前記メンバアクセスのサービスの少なくとも一部を提供可能にするための実行可能命令と、 を実行させるためのコンピュータプログラム。
- 59ネットワークアカウントを管理するシステムであって、 一般アクセスを有する第2のアカウントが当該第2のアカウントの現在のサブスクリプションレベルより高いアクセスレベルが必要な場合に、前記第2のアカウントがメンバアクセスを有する第1のアカウントにリンク案内の要求を送信する手段と、 前記 第1のアカウントのアクセスレベルの少なくとも一部を 前記 第2のアカウントと共有することで、前記第1のアカウントに前記第2のアカウントをリンクする手段と、 前記第2のアカウントが前記第1のアカウントにリンクされている間、前記メンバアクセスの少なくとも一部を前記第2のアカウントに付与する手段と、を備え、 前記第1のアカウントは対応するサブスクリプションを有しており、 前記一般アクセスは少なくとも1つの特権を付与し、 前記メンバアクセスは、前記一般アクセスによって提供されない2以上の特権を付与する、 システム。
Independent claims59
65 paragraphs, as filed
One or more interconnected computer systems provide an online environment for users to access resources available through computer systems such as web pages, multimedia data, and application software (such as games). Can be done. Users can access the resources of the online environment using a local computer system that is networked to one or more computer systems that provide the online environment.
<p> Online environments often use accounts to identify users and control access to the resources they provide. Each user typically has an account, which indicates the level of access to online resources. Online resource providers also often charge for account subscriptions given to users. In environments with different access levels, providers may charge higher for higher access levels. Therefore, from the provider's point of view, it is desirable to encourage users to purchase high-value subscriptions, which often makes high-access accounts attractive to users.</p>
<p> The present invention provides a method for managing and linking network accounts for sharing access privileges between accounts, and a device thereof. The network account management method of one embodiment includes a step of linking a second account having general access to a first account having member access, and the second account being linked to the first account. In the meantime, the first account has a corresponding subscription and the general access grants at least one privilege, including the step of granting at least a portion of the member access to the second account. However, the member access grants two or more privileges not provided by the general access.</p><p> The network account management method of the other embodiment is based on the account creating an account with general access, receiving an upgrade request, and the account satisfying one or more requirements for having member access. Includes a step of verifying that the upgrade is allowed and a step of upgrading the account to have member access.</p><p> The network account linking method of the other embodiment includes a step of creating a first account having general access, a step of sending a link guide indicating a second account having member access, and the first account. Includes a step of receiving a link consent indicating that it will be linked to the second account, a step of sending a service request indicating a service with minimal access requiring member access, and a step of accessing the service. ..</p><p> The network account linking method of the other embodiment includes a step of creating a first account having member access, a step of receiving a link guide indicating a second account having general access, and the second account said. Includes a step of sending a link request indicating that it is about to be linked to the first account.</p><p> The computer program of the other embodiment is stored in a tangible storage medium and is used for managing network accounts. This computer program provides an executable instruction to link a second account with general access to a first account with member access to the computer, and the second account is linked to the first account. During that time, an executable instruction for granting at least a part of the member access to the second account is executed. The first account has a corresponding subscription, the general access grants at least one privilege, and the member access grants two or more privileges not provided by the general access.</p>
The present invention provides a method for managing and linking network accounts for sharing access privileges between accounts, and a device thereof. In one embodiment, a low privileged account is linked to a high privileged account. While the accounts are linked, the two accounts can take advantage of high privileges. When the link is broken, the access level of each account will be restored.
An embodiment for explanation is described below. After this example, other modified examples will be described.
In one embodiment, the first user purchases a subscription for an online gaming environment. The online gaming environment is supported by a collection (or one system) of server computer systems connected to the Internet. The first user owns a game console that can be connected to the network (such as PlayStation 2 (registered trademark) provided by Sony Computer Entertainment Inc. in Japan), for example, playing online games with other users. To do so, you can access the online gaming environment through this game console. The first user's subscription allows this user to create a member account in the online environment, and the first user is actually doing this. This member account grants member access to the first user. Member access allows a first user to participate in a regular online game in an online environment. Member access also allows the first user to access various resources in the online environment that are restricted to accounts with member access. For example, a first user may access a member chat room to chat with another user who has member access, or may participate in an online game tournament that is restricted to accounts with member access only.
The second user also owns a game console that can be connected to the network, and can access the online game environment through this game console. However, the second user does not have a subscription to the online gaming environment. In an online environment, a non-member account can be created if the user does not have a subscription. Non-member accounts give users general access, but not member access. The second user creates a non-member account in the online environment. The second user has a non-member account but no member access. Therefore, the second user cannot directly participate in a normal online game.
In the online gaming environment, non-member accounts can be linked to member accounts. While the non-member account is linked to the member account, the non-member account is temporarily granted limited member access. Limited member access in this example allows a non-member account to participate in the same game (regular game or tournament) as the member account to which this non-member account is linked. Limited member access does not allow non-member accounts to join member account chat rooms. (In other embodiments, different types of access may be granted to the backlink account, as described below.)
The second user asks the first user to link the account by sending a link invitation to the first user's account. The first user agrees and requests the online environment to link the account. Once the accounts are linked, the two accounts will have the appropriate access to participate in online games. After that, the first user and the second user start an online game and enjoy it. When the game is over, the first user requests the end of the link (or the server automatically ends the link) and each account returns to its original state.
In this example, since the first user has a member account with member access, the first user has an advantage that the second user does not have. The first user can play in the online game without linking to another account. The second user needs to find another user to link this second user to his account. These benefits make member accounts attractive. Further, a user having a member account is required to search for a user having a member account so that a user having a non-member account can play in an online game. As a result, users with member accounts become popular and attract attention in the online environment. Again, member accounts are desirable. Providers of online gaming environments can take advantage of this attraction to increase revenue from subscriptions and profit from increased usage (eg, increased advertising revenue).
FIG. 1 is a block diagram of an embodiment of the network environment 100 for linking network accounts. The network environment 100 includes a server 105, a first user system 110, a second user system 115, and a network 120. The server 105, the first user system 110, and the second user system 120 are interconnected by a network 120.
Server 105 provides services to the user in the connected user system and performs processing and storage for managing the user's network account (including processing and storage). storage) A computer system. Server 105 provides the user with an online environment. Some or all of the resources and services provided by server 105 are limited. Server 105 controls access to these restricted resources or services so that only accounts with the latest appropriate access levels are allowed access to the restricted resources or services. Server 105 creates and manages accounts for users. In one embodiment, the server 105 uses account information (eg, information that identifies a user to the account, account type, current access level for the account, permanent or default access level for the account, and current user system for the account. ) Is connected to and managed by the account database 125. Server 105 creates and manages user subscription information, for example, in local storage or account database 125. In another embodiment, the server 105 accesses the subscription information via the network 120. Subscription information indicates the user's permissions, such as the type of network account the user is allowed to create. Server 105 also manages shared access privileges between the linked account and the linked account.
The first user system 110 and the second user system 115 are also computer systems such as a network-compatible game console. When accessing the online service provided by the server 105, the user systems 110 and 115 interact with each other and perform processing and storage for interacting with the server 105. Further, the user systems 110 and 115 store the user's identification information (for example, the name and password that the user has entered into the user systems 110 and 115). In FIG. 1, the identification information of the first user is indicated by the label ID1 attached to the first user system 110. The identification information of the second user is indicated by the label "ID2" attached to the second user system 115. In another embodiment, the identification information identifies the user system in addition to or on behalf of the user. User systems 110, 115 provide identification information to server 105 so that server 105 uses the correct account for each user system 110, 115.
The network 120 is an intermediate network (such as the Internet) that provides a route for data transmission between the server 105, the first user system 110, and the second user system 115. In another embodiment, the server 105, the first user system 110, and some or all of the second user system 120 are directly connected, so that the intermediate network is not always used or omitted.
In FIG. 1, the first user system 110 has a server account which is a member account. The account of the first user system 110 has the identification information "ID1" corresponding to the account "ACCOUNT1" and the account "ACCOUNT1" has the access level of the member (MEMBER) by the label of the account database 125. ing. The second user system 115 has a server account that is a non-member account. The account of the second user system 115 has the identification information "ID2" corresponding to the account "ACCOUNT2" and the account "ACCOUNT2" has a non-member (NON-MEMBER) access level according to the label of the account database 125. It is shown. As described below, when the account in the second user system 115 is linked to the first user system 110, the server 105 updates the account database 125 to indicate a change in the access level for this link and the account. ..
In one embodiment, the network account is one of two types, a member account and a non-member account. Different account types offer different access levels. Member accounts provide member access, and non-member accounts provide non-member access or general access. In one embodiment, member access includes general access. In other embodiments, the member account provides both member access and general access. Member accounts require the user to have the appropriate subscription. The user obtains a subscription by paying a fee (for example, temporary use or monthly fee) to the provider of the online environment. In other embodiments, the member account has one or more additional requirements, such as achieving a particular goal in an online environment. In other embodiments, such additional requirements are used in place of the requirement to have a subscription. Non-member accounts do not require a subscription. In another embodiment, the non-member account requires a lower subscription than the member account.
The access level of an account defines the privileges available to users of that account. Some of the resources or services provided by the server are restricted to accounts with the appropriate level of access. For example, participation in online games or access to certain websites or web pages can be restricted to accounts with member access. Some of the other resources or services may not be restricted to allow access from any account. For example, member chat rooms are restricted to accounts with member access, but general chat room services may not be restricted.
In each embodiment, various privileges can be granted for high access levels. In each embodiment, the actions that a user is allowed by member access include, but are not limited to (for example, when member access grants one or more of these privileges). Participate in online games. Start an online game. Participate in online games that are restricted to member accounts only. -Use special resources while playing online games. This includes accessing special game areas (eg entering special buildings in the game), accessing special game resources (eg using special tools in the game or special background music). Listen) or use special game features (for example, use special movements or techniques in combat games). Use in-game special indicators that indicate the access level available to your account (for example, your character or team wears a special uniform or mark that is visible in the game). -Store data such as personal web pages, high scores, or saved game data in the online environment. -Read or write messages on online forums or bulletin boards. · Receive or access the newsletter. · Access restricted web resources (eg collections of web page member areas). -Launch an online environment group or clan in which other users can participate. -Join a restricted group or clan in an online environment. -Receive discounts or coupons for goods, services, or subscriptions that can be purchased online or through partners. -Approve the link guide and allow non-member accounts to be linked to member accounts.
In another embodiment, the online environment supports three or more types of accounts and three or more access levels or access types. In this case, privilege pairs can be changed or duplicated for some or all account types and different access levels. Similarly, the requirements for creating different account types, such as different types of subscriptions for different rates, may vary. In another embodiment, the user can add privileges to the account by updating the user's subscription (without changing the account type).
FIG. 2 is a flowchart 200 of an embodiment for creating a network account. In the early stages, the user connects the user system to the server and gives the user system identification information. The user may or may not already have a subscription for the online environment.
At block 205, the user system sends an account creation request to the server. The user causes the user system to send this request. The account creation request indicates the user's identity and the type of account to create. In one embodiment, the account creation request also indicates the user's subscription information.
At block 210, the server checks the user's subscription information to ensure that the user's subscription allows the user to have the requested account type. The server accesses the user's local or remote subscription information. In one embodiment, the server uses the identification information to access the subscription information stored in the server (eg, in the subscription database). The subscription information indicates the user's permissions, including the types of network accounts that the user is allowed to create.
As mentioned earlier, one or more account types are restricted and require a certain level of subscription to create. Similarly, one or more account types are unlimited and do not require a subscription to create. When a user requests a restricted account type, the server compares the subscription information permissions with the requested account type to determine if account creation is allowed. If this account type is not allowed, the server goes to block 215 and proposes to update the user's subscription. If the account type is allowed, the server goes to block 220 and creates an account. If the user does not have any subscriptions and requests a restricted account type, the server proceeds to block 215. If the user requests an unlimited account type, the server can proceed directly to block 220 without having to verify the user's subscription information.
If the user is not allowed to create the requested account type, at block 215, the server proposes to the user to upgrade the subscription. The server proposes to upgrade the user's subscription to the appropriate level that allows the creation of the requested account type. In another embodiment, the server proposes multiple subscription levels to the user. The server presents the user with the cost or requirements for upgrading the subscription. If the user declines the upgrade, the server terminates the account creation process without creating an account. If the user agrees to the upgrade, the server processes the costs required for the upgrade or the transactions required to meet the requirements (for example, processing online credit card payments). After the transaction ends, the server returns to block 210 to check for a new subscription. In another embodiment, the server goes directly to block 220 to ensure that the upgraded subscription allows the requested account type as part of the upgrade transaction.
After verifying that the user's subscription allows the creation of accounts of the requested account type, the server creates a new account for the user in block 220. The server creates a new account and stores this account information in the account database. The account information indicates the user's identity, account type, and current access level.
The user can also upgrade the user's account by sending an account upgrade request to the server indicating the desired account type. The server handles upgrade account requests as well as account creation requests. That is, make sure that the requested account type or privilege is granted by the user's subscription, upgrade the subscription if necessary and approved, and upgrade the account if allowed.
In one embodiment, one or more account types impose requirements related to the online gaming environment in addition to (or instead of) specific subscription levels or fees. The requirements of such an online environment indicate the achievements achieved in the online environment, which may be the minimum play time of the game or the minimum number of games played, the minimum high score, the minimum number of wins, or in-game. There are actions or events achieved (eg, winning a particular opponent in a game, discovering a particular game item, etc.). If the user has achieved one of these achievements, the server will suggest upgrading the user's account if other requirements (such as payments) are met.
FIG. 3 shows a flowchart 300 of an embodiment that provides a service in an online environment to a user. In the early stages, users have created a network account. The user connects the user system to the server and gives the identification information to the user system. The user may or may not already have a subscription for the online environment.
At block 305, the user system sends a service request to the server. The user causes the user system to send this request. In some cases, the user system or server may create multiple service requests from a single request made by the user. The service request indicates the user's identity and the type of service. In one embodiment, the service request also indicates the user's subscription information.
At block 310, the server checks the user's subscription information to ensure that the access level of the user's account allows the requested service. The server accesses the account information stored in the account database. As mentioned earlier, the account information indicates the current access level of the account.
One or more service types are restricted and require a specific level of access. Similarly, one or more service types are unrestricted and do not require a special access level. When a user requests a restricted service, the server compares the access level of the user's account with the access level of the requested service. If the user's access level is inadequate (ie, the user's access level matches or does not exceed the required access level), the server goes to block 315 and proposes to upgrade the user's account. .. If the user's access level is sufficient, the server proceeds to block 320 to provide the service. If the user requests an unrestricted service, the server can proceed directly to block 320 without having to check the user's access level.
If the user's account does not have the required account level for the requested service, at block 315, the server proposes to the user to upgrade the account type. The server proposes to upgrade the user's account to the appropriate account type with the required level of access for the requested service. In another embodiment, the server proposes multiple account types to the user. In another embodiment, it is proposed that the server temporarily raises the access level so that it can be used with a limited number of times (for example, once) without changing the account type. The server presents the user with the cost or requirement to upgrade the account. If the user declines the upgrade, the server terminates service processing without providing the requested service. If the user consents to the upgrade, the server processes the transactions required to meet the costs or requirements required for the upgrade (eg, process online credit card payments). After the transaction ends, the server returns to block 310 and checks for a new account for the requested service. In another embodiment, the server proceeds directly to block 320, making sure that the upgraded account has the required account level for the requested service as part of the upgrade transaction.
Upon verifying that the user's account has the required level of access for the requested service, at block 320 the server provides the requested service. The server either provides services in an online environment or causes a remote system to provide services.
The server handles user system requests to access resources as well.
In another embodiment, instead of suggesting (or as an additional option) to upgrade the user's account if the user does not have the required level of access for the requested service, the server is separate for the link. Suggest to find the user's account. As described below, when an account is linked to another account, the account with the lower access level temporarily receives the higher access level of the other account. A server may provide a matching service that attracts a user requesting a service that exceeds its access level to another user with an appropriate access level. If the user agrees to the server's suggestion, the server will send a link invitation for this user, and if the link is successful, the server will return to block 315 and the access level after the user's account change, as described below. To confirm. If the user declines the server proposal, the server terminates service processing without providing the requested service.
FIG. 4 is a flowchart 400 of an embodiment of a link process for linking a non-member account to a member account. In the early stages, the first user connects the first user system to the server and gives the first identification information to the first user system. The first user has created a member account with member access in the online environment. The second user connects the second user system to the server and gives the second identification information to the second user system. The second user has created a non-member account with non-member access. In the description of FIG. 4, the second user links the account of the second user to the account of the first user. In this case, the account of the first user is the "backlink account" and the account of the second user is the "link account" (users and user systems are also referred to as "backlink ~", "link ~". May).
At block 405, the second user system sends a link guide to the first user system. The second user causes the second user system to send this request. This link guide specifies the first user as the target recipient and the account of the second user as the link account. Link guidance is a request that allows the first user to allow the second user's account to be linked to the first user's account. The second user system sends a link guide to the first user system via the server. In another embodiment, the second user system has the appropriate information to send the link guidance directly to the first user system (without using a server) and does this. In one embodiment, the link guide is transmitted as a challenge to encourage the game to be played.
In another embodiment, the user system sends the user's identification information and a link guide specifying the target user to the server. The server collects the user's account information and adds this account information to the link guide. After that, the server sends the updated link guidance to the user system of the target user.
As described above, the second user system sends the link guidance in response to the request from the second user. In another embodiment, the server sends a link guide on behalf of the user, such as when the user requests a service for which the user's account does not have the appropriate access level. In another embodiment, the server sends a link guide to the second user system on behalf of the first user system, which causes the user of the first user system to participate in the game. For example, when you want to invite users of the system.
At block 410, the first user system sends an invitation consent to the second user system. The first user decides whether or not to accept the link guidance. If the first user decides not to accept the link guidance, the first user system sends a decline message to the server and the link process ends. In another embodiment, the first user system does not respond, ignores the link guidance and declines the guidance. If the first user accepts the link guidance, the first user system sends the guidance consent to the second user system via the server. Guidance acceptance confirms that the first user system requires the server to establish a link between the two accounts. In another embodiment, the first user system has the appropriate information to send the guidance consent directly to the second user system (without using a server) and does this.
At block 415, the first user system sends a link request to the server. The link request indicates the account of the first user and the account of the second user. In another embodiment, the link request indicates the identification information of the first user and the second user, and the server collects the appropriate account information.
At block 420, the server verifies that these accounts allow the second user's account to be linked to the first user's account. The server obtains the appropriate account information (and subscription information or other information as needed) to allow the first user's account to accept links from other accounts, and second. Make sure that your user's account is allowed to link to other accounts. For example, the server may impose restrictions on the creation of links between accounts in order to prevent unauthorized use of accounts or to limit network traffic to a certain state. In one embodiment, the accounts may be linked to only one account at a time, or linked to one account at a time. If the server determines that the link between the accounts is allowed, the server goes to block 425 and creates the link. If the server determines that the link is not allowed, the server terminates the link process without creating the link. In another embodiment, if the link is not allowed but the link is allowed by upgrading one or both of the accounts or subscriptions, the server (as described above, suggests a subscription or account upgrade). Suggest an appropriate upgrade (as well).
After confirming that the account allows the link to be created, at block 425, the server links the second user's account to the first user's account. The server updates the account information of the second user's account to indicate that the second user's account is linked to the first user's account. The server also updates the account information of the first user's account to indicate that the second user's account is linked to the first user's account. In another embodiment, the link is "one way" so that the server does not update the account information of the first user's account.
When the accounts are linked, at block 430, the server grants the access level of the first user's account to the second user's account. The first user's account is a member account and has member access. The second user's account is a non-member account and has non-member access or general access. The server updates the account information of the second user to indicate that the current access level has been changed to member access. When a user requests service from the server as described above, the effect of the link is reflected in determining whether the server should service the user in order for the server to check the current access level of the user's account. To. The server retains the original or default access level of the second user's account. When the link ends, the server updates the account information of the second user's account to indicate that the current access level has returned to the original non-member access level, as described below. At this point, the accounts are linked.
In other embodiments, one account can be linked to multiple accounts. In this case, when one account is linked to another, the server records in the linked account's account information which privilege or access level of which linked account has been granted. When the link is terminated, the server simply revokes the privilege or access level granted by the terminated link.
FIG. 5 is a flowchart of an example of breaking the link between two linked accounts. In the initial stage, the account of the second user is linked to the account of the first user, such as after the link processing described above with reference to FIG. 4 is completed.
At block 505, an event triggers the end of the link. The triggering event is an event that causes the server to decide that a request or link from any of the users of the linked account should be terminated. The server has one or more rules that cause the termination of the link. For example, if one of the users abuses the account, the server may decide to terminate the link. In another example, if any user system disconnects from the server, the server terminates the link.
At block 510, the server removes the access level granted to the second user's account by the link. The server updates the account information of the second user's account to indicate that the current access level has returned to the original access level.
At block 515, the server removes the link from the account. The server updates the account information for the two accounts to indicate that the link has been removed. At this point, the account is no longer linked.
In one embodiment described above, when one account (link account) is linked to another account (backlink account), the linked account receives the access level of the backlink account while the account is linked. This type of link is a direct link. However, in other embodiments, various types of links between accounts can be used in addition to or in place of direct links. In one embodiment, the user of the link account requests a particular type of link in the link guide. In another embodiment, the user of the backlink account accepts or specifies a particular type of link in link acceptance. In other embodiments, the server chooses the type of link depending on the situation (for example, an online game tournament uses a given type of link, and a typical use in an online environment may have another type of link. used).
In one embodiment, the server provides a time-limited link. For time-limited links, the server terminates the link after a certain period of time (such as one day) has passed since the link was established, or when a certain point in time has arrived (for example, the end of the day the link was established). To do.
In another embodiment the server provides a persistent link. Persistent links do not break until one of the users of the linked account or the backlink account requests termination. Persistent links do not end when one or both of the user systems break. When the user returns to the online environment, the persistent link remains valid, even if they use a different user system than the one used when the link was established.
In another embodiment, the server provides a link with a limited number of uses. For links with a limited number of uses, the server terminates the link when the number of services requested by the link account reaches the set number after the link is established. For example, a link that is limited to one use is only allowed to be used once. In one embodiment, the number of consumptions of the limited number of times the service can be used differs depending on the service. For example, some services do not use the number of services available for "free", while others are "expensive" and use multiple available services (for example, it is counted as having used the service twice). There are also things.
In another embodiment, the server provides a link with limited use. For limited-use links, the linked account receives the access level of the backlink account to use one or more specific services. Linked accounts, for example, will have a high level of access just to play one particular online game.
In another embodiment the server provides a partial link. With partial linking, the backlink account has multiple access levels, and the linked account does not receive all of the backlink account's access levels. For example, in one embodiment, suppose an account can have access levels A, B, C, and / or D. Different privileges are given at each level. Suppose the linked account has access levels A and the linked account has access levels A, B, and C. If the user of the backlink account accepts the link guidance, the user of the backlink account designates this link as a partial link that grants only access level B. As a result, for the life of the link, the link account will have access levels A and B, but not access level C. In another example, a member account has a member access level and a member-only access level. Member-only access levels are restricted to accounts with appropriate subscriptions, and member-only access levels are not granted to accounts by links. As a result, the linked account linked to the member account (assuming the linked account does not have the proper subscription) receives a member access level, but not a restricted member-only access level.
In another embodiment, the server provides a rental link. With a rental link, the backlink account transfers the access level of the backlink account to the link account for the life of the link. As a result, the backlink account does not have that access level and is either disabled or reduced in access level. In one embodiment, the accounts exchange access levels with each other.
In another embodiment, the server provides a membership link. With membership linking, the server creates a group for the leader account and automatically links any account that belongs to this group to this leader account. As a result, all accounts belonging to the group will have the access level of the reader account.
In another embodiment the server provides a pool link. In a pool link, the server maintains a pool and groups associated with pool accounts that are allowed access to this pool. Pool accounts can donate links to the pool. Pool accounts can be linked to pools (rather than to a specific account) to receive donated links. For example, the server provides a pool for a clan of accounts. Each clan member has access to the pool. Many high-access clan members provide their access level to the pool, so that the same number of low-access clan members can link to the pool to receive high access levels. Pool links give pool accounts more freedom to share access levels without having to establish a one-to-one relationship between users.
In another embodiment, the server provides one or more types of links that combine the types of links described above. Servers, for example, provide links for limited time and use. Furthermore, the types of links described above are examples, and other types of links are possible as well.
In another embodiment, the server links accounts to privileges rather than linking accounts to each other. In this case, the account will have another privilege (for example, it will be created as a data object independent of the account). The user or account may make the privileges of the account available for sharing or linking. Another user can link his account to the privileges made available to the first user. For example, an account has one or more references to privileges. These references point to privileged objects for privileges owned or donated by the account. The account can allow this privilege to be linked by specifying that the privilege is available for sharing. When a linked account is linked to the sharing privilege of the "provider" account, the linked account remembers a reference to the sharing privilege. As a result, a shared privilege can have multiple references (eg, owning account and one or more linked accounts) that indicate this privilege.
Each embodiment of the present invention is realized by an electronic device, computer software, or a combination of these technologies. Some embodiments have one or more computer programs executed by a programmable processor or computer. For example, referring to FIG. 1, in one embodiment, the server and user system have one or more programmable processors. In general, each computer has one or more processors and one or more data storage devices (eg, volatile or non-volatile memory modules, hard disk drives, floppy disk drives, CD-ROM drives, magnetic tape drives, and other permanent optics. And a magnetic storage device), one or more input devices (eg, mouse, keyboard), and one or more output devices (eg, display console, printer).
Computer programs typically contain executable code that is stored in persistent storage media and copied into memory at run time. The processor executes this code by retrieving executable instructions from memory in a predetermined order. When executing the program code, the computer receives data from the input device and / or the storage device, performs processing on the data, and sends the obtained data to the output device and / or the storage device.
Various examples for explaining the present invention have been described above. However, one of ordinary skill in the art will appreciate that other embodiments are possible and are within the scope of the present invention. For example, the above description focuses on an embodiment that provides an online environment for playing a game, which can be chat or publishing or data (eg, text, image, audio, video, or multimedia). ) May be offered, different services or additional services may be provided.
Therefore, the present invention is not limited to these examples described above.
<figref num="1">It is a block diagram of an Example of a network environment for linking network accounts.</figref><figref num="2">It is a flowchart of one Example which creates a network account.</figref><figref num="3">It is a flowchart of one Example which provides a service in an online environment to a user.</figref><figref num="4">It is a flowchart of an example of the link processing which links a non-member account to a member account.</figref><figref num="5">It is a flowchart of one example which breaks the link of two linked accounts.</figref>
Every citation, both waysCites: the store holds 20 of 21
| Document | Relation | Office | Cited during |
|---|---|---|---|
| JP2001222497A | Cites | Japan | Examiner |
| JP2002092374A | Cites | Japan | Examiner |
| JP2002109394A | Cites | Japan | Search report |
| JP2002268986A | Cites | Japan | Search report |
| JP2002336552A | Cites | Japan | Examiner |
| JP2003024643A | Cites | Japan | Search report |
| JP2003103059A | Cites | Japan | Search report |
| JP2003150735A | Cites | Japan | Search report |
| JP2003210847A | Cites | Japan | Examiner |
| JP2004355458A | Cites | Japan | Search report |
| JP2001222497A | Cites | Japan | – |
| JP2002092374A | Cites | Japan | – |
| JP2002268986A | Cites | Japan | – |
| JP2004355458A | Cites | Japan | – |
| JP2003150735A | Cites | Japan | – |
| JP2002109394A | Cites | Japan | – |
| JP2003024643A | Cites | Japan | – |
| JP2003103059A | Cites | Japan | – |
| JP2003210847A | Cites | Japan | – |
| JP2002336552A | Cites | Japan | – |
| レディマン デビッド David Ladyman,ウルティマオンライン ザ・セカンドエイジ 公式ガイド ルネッサンス・エディション対応版 PRIMA'S OFFICIAL STRATEGY GUIDE:ULTIMA ONLINE THE SECOND AGE,ソフトバンクパブリッシング株式会社 稲葉 俊夫,2002年 4月15日,第7版,第121-124頁 | Non-patent | – | – |
8 members in 4 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 10690000 | United States of America | – | |
| 69000003 | United States of America | A | |
| 69000003 | United States of America | A | |
| 2004023111 | United States of America | W | |
| 2004023111 | United States of America | W | |
| 2003690000 | – | – | – |
| 2004023111 | – | – | – |
| US20030690000 | – | – | – |
| WO2004US23111 | – | – | – |
Members8
| Document | Office | Kind | |
|---|---|---|---|
| US2005086126A1 | United States of America | A1 | |
| WO2005045560A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2005045560A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP1678670A2 | European Patent Office (EPO) | A2 | |
| JP2007516513A | Japan | A | |
| EP1678670A4 | European Patent Office (EPO) | A4 | |
| JP4776540B2This record | Japan | B2 | |
| US8388440B2 | United States of America | B2 |
23 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Transfer to examiner for re-examination before appeal (zenchi)AppealJAPANESE INTERMEDIATE CODE: A911A911 | A911 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Notification of resignation of power of attorneyJAPANESE INTERMEDIATE CODE: A7424RD04 | RD04 | |
| Notification of resignation of power of attorneyJAPANESE INTERMEDIATE CODE: A7424RD04 | RD04 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 |
Numbers
- Publication
- 4776540
- Publication, DOCDB
- 4776540
- Publication, EPODOC
- JP4776540B
- Application
- 2006536559
- Application, DOCDB
- 2006536559
- Application, EPODOC
- JP20060536559
Titles2
- Japanese
- ネットワークアカウントのリンク
- English
- Network account link
Classification
- CPC, 9
- G06Q30/06
- A63F13/12
- A63F2300/5546
- G06Q10/00
- G06Q30/04
- G06Q30/0601
- G06Q30/0633
- A63F13/30
- A63F13/792
- IPC, 7
- G06F21 20
- G06Q30 00
- G06Q50 00
- A63F13 12
- G06F21 31
- G06F21 62
- G06Q10 00