Attaching multiple phone lines to a single mobile or landline phone
29 claims: 5 independent, 24 dependent
- 1オペレータデバイスをサポートするサービスエージェンシーにおける、コンピュータベースの方法であって、 仮想番号と通信する、第1の電話デバイスからの要求に応答して、前記仮想番号のプロバイダからの第1の情報を受信するステップであって、前記仮想番号は前記オペレータデバイスと関連付けられ、前記受信した第1の情報は、前記第1の電話デバイスに対応するデバイス情報および前記仮想番号を含む、ステップと、 前記第1の電話デバイスの前記デバイス情報と、マッピングテーブル内に前記仮想番号と関連付けて格納された前記オペレータデバイスのデバイス情報と、の比較に基づいて、前記第1の電話デバイスを第1のコンタクトデバイスとして識別するステップと、 前記第1の電話デバイスを前記第1のコンタクトデバイスとして識別したことに応答して、 前記第1のコンタクトデバイスを前記仮想番号と関連付けられた前記オペレータデバイスと接続する命令、または前記第1のコンタクトデバイスから受信されたデータを、前記仮想番号から前記オペレータデバイスに送信する命令、のうちの少なくとも1つを、前記プロバイダに送信するステップと、 前記第1のコンタクトデバイスを前記オペレータデバイスと接続する接続要求、または前記第1のコンタクトデバイスから受信されたデータを前記仮想番号から前記オペレータデバイスに送信するために送信されたデータ、のうちの少なくとも1つにおける前記仮想番号に対して指定された番号情報および/または前記第1のコンタクトデバイスに対する前記デバイス情報を、前記オペレータデバイスに識別させるステップと、 前記仮想番号と通信する、第2の電話デバイスからの要求に応答するための、前記プロバイダからの第2の情報を受信するステップであって、前記受信した第2の情報は、前記第2の電話デバイスに対応するデバイス情報および前記仮想番号を含む、ステップと、 前記第2の電話デバイスの前記デバイス情報と、前記マッピングテーブル内に前記仮想番号と関連付けて格納された前記オペレータデバイスの前記デバイス情報と、の比較に基づいて、前記第2の電話デバイスを前記オペレータデバイスとして識別するステップと、 前記第2の電話デバイスを前記オペレータデバイスとして識別したことに応答して、 前記オペレータデバイスから受信された第2のコンタクトデバイスに対応する前記デバイス情報に基づいて、前記仮想番号を通じて前記オペレータデバイスを前記第2のコンタクトデバイスと接続する命令、または前記オペレータデバイスから受信された前記第2のコンタクトデバイスに対応する前記デバイス情報に基づいて、前記オペレータデバイスから受信されたデータを前記仮想番号から前記第2のコンタクトデバイスに送信する命令、のうちの少なくとも1つを前記プロバイダに送信するステップと、 前記オペレータデバイスを前記第2のコンタクトデバイスと接続する接続要求、または前記オペレータデバイスから受信されたデータを前記仮想番号から前記第2のコンタクトデバイスに送信するために送信されたデータ、のうちの少なくとも1つにおける前記仮想番号に対して指定された番号情報を、前記第2のコンタクトデバイスに識別させるステップと、 前記仮想番号を通じて前記オペレータデバイスを前記第2のコンタクトデバイスと接続する接続要求、または前記オペレータデバイスから受信されたデータを前記仮想番号から前記第2のコンタクトデバイスに送信するために送信されたデータ、のうちの少なくとも1つにおいて、前記オペレータデバイスのデバイス情報を、前記第2のコンタクトデバイスに送信することを防止するステップと を備えたことを特徴とする方法。
- 2デバイス情報は、送信番号を含んでいることを特徴とする請求項1に記載の方法。
- 3前記第2の電話デバイスは、前記第2の電話デバイスの送信番号と、前記仮想番号と関連付けて前記マッピングテーブルに格納された前記オペレータデバイスの送信番号との間で一致したことに応答して、前記オペレータデバイスとして識別されることを特徴とする請求項2に記載の方法。
- 4前記第1の電話デバイスは、前記第1の電話デバイスの送信番号と、前記仮想番号と関連付けて前記マッピングテーブルに格納された前記オペレータデバイスの送信番号との間で一致しなかったことに応答して、前記第1のコンタクトデバイスとして識別されることを特徴とする請求項2に記載の方法。
- 5前記仮想番号と関連付けられた音声通信が記録されていることの通知を、モニタリングデバイスに送信するステップをさらに備えたことを特徴とする請求項1に記載の方法。
- 6前記第2の電話デバイスから受信されたキー入力情報と、前記仮想番号と関連付けて前記マッピングテーブルに格納されたキー入力情報との比較に基づいて、前記第2の電話デバイスを前記オペレータデバイスとして認証するステップをさらに備えたことを特徴とする請求項1に記載の方法。
- 7前記第2の電話デバイスからの、前記仮想番号と通信する前記要求に対応するキー入力情報の認証に応答して、前記第2の電話デバイスを前記オペレータデバイスとして前記仮想番号に接続する命令を送信するステップをさらに備えたことを特徴とする請求項6に記載の方法。
- 8前記オペレータデバイスの機能とインターフェースするモジュールを、前記オペレータデバイスに提供するステップをさらに備え、前記モジュールは、 前記第2のコンタクトデバイスに対応する前記デバイス情報、および前記オペレータデバイスにマッピングされた前記仮想番号を取得するステップと、 前記仮想番号を通じて前記オペレータデバイスを前記第2のコンタクトデバイスに接続すること、または前記オペレータデバイスから受信されたデータを、前記仮想番号から前記第2のコンタクトデバイスに送信すること、のうちの少なくとも1つのために、前記取得されたデバイス情報から前記第2のコンタクトデバイスに対する送信番号を提供するステップと のうちの少なくとも1つを実行することを特徴とする請求項1に記載の方法。
- 9前記仮想番号に対して受信された番号情報に基づいて、前記仮想番号をプロビジョニングするステップと、 前記仮想番号に対するマッピング情報を受信するステップであって、前記マッピング情報は、前記オペレータデバイスに対応する前記デバイス情報を含み、前記デバイス情報は、前記オペレータデバイスの送信番号を含む、ステップと、 前記オペレータデバイスに対応する前記送信番号と関連付けて、前記仮想番号を複数のアタッチされた番号として前記マッピングテーブルに格納するステップと をさらに備えたことを特徴とする請求項1に記載の方法。
- 10前記仮想番号を通じて前記オペレータデバイスを前記第2のコンタクトデバイスに接続することは、前記仮想番号を通じた前記第2のコンタクトデバイスとの接続を要求して、 前記接続要求において、 前記仮想番号に対して指定された前記番号情報を前記第2のコンタクトデバイス に識 別 される ことを備え、前記接続要求は、前記オペレータデバイスとは異なる第3の電話デバイスから前記接続要求が来ているように見えるように、前記仮想番号に対して指定された前記番号情報を備えることを特徴とする請求項1に記載の方法。
- 11前記第1のコンタクトデバイスから前記仮想番号で受信された前記データ、または、前記仮想番号から前記第2のコンタクトデバイスに送信された前記データのうちの少なくとも1つは、ショートメッセージサービス(SMS)、マルチメディアメッセージサービス(MMS)、または、プロプライエタリサービス上のメッセージであることを特徴とする請求項1に記載の方法。
- 12前記第1のコンタクトデバイスに関連付けられたデバイス情報を、前記仮想番号から前記オペレータデバイスに送信する前記メッセージにアタッチする命令、ならびに、前記第1のコンタクトデバイスの前記デバイス情報を有する前記メッセージを前記仮想番号から送信して、前記仮想番号に対して指定された番号情報および前記第1のコンタクトデバイスに対する前記デバイス情報を、前記オペレータデバイスに識別させる命令、をさらに備えていることを特徴とする請求項11に記載の方法。
- 13前記仮想番号から前記第2のコンタクトデバイスに送信する前記メッセージから、前記オペレータデバイスに関連付けられたデバイス情報、または前記第2のコンタクトデバイスに関連付けられたデバイス情報のうちの少なくとも1つを抽出する命令、ならびに、前記抽出した情報なしで、前記メッセージを前記仮想番号から前記第2のコンタクトデバイスに送信して、前記オペレータデバイスに対する識別デバイス情報の送信を防止する命令、をさらに備えていることを特徴とする請求項11に記載の方法。
- 14第3の電話デバイスから第2の仮想番号への接続要求に応答して、第3の情報を受信するステップであって、前記第3の情報は、前記第3の電話デバイスに対応するデバイス情報および前記第2の仮想番号を含む、ステップと、 前記第3の電話デバイスを、前記仮想番号を通じて前記オペレータデバイスの通信を監視することが許可されたモニタリングデバイスとして識別するステップと、 前記モニタリングデバイスが、前記オペレータデバイスと、前記第1のコンタクトデバイスまたは前記第2のコンタクトデバイスの1つとの間の音声通信を受信することを許可する命令を送信するステップと をさらに備えたことを特徴とする請求項1に記載の方法。
- 15前記モニタリングデバイスが、前記オペレータデバイスと、前記第1のコンタクトデバイスまたは前記第2のコンタクトデバイスの1つとの間の前記音声通信を受信することを許可する命令は、前記モニタリングデバイスを、前記第2の仮想番号に接続し、および、前記仮想番号を通じて確立された接続に関連付けられた音声を前記第2の仮想番号に渡す命令を含んでいることを特徴とする請求項14に記載の方法。
- 16前記第1のコンタクトデバイスおよび前記第2のコンタクトデバイスは、同一の電話デバイスであり、前記第1のコンタクトデバイスの前記デバイス情報は、前記第2のコンタクトデバイスに対して受信された前記デバイス情報と一致することを特徴とする請求項1に記載の方法。
- 17前記オペレータデバイスを前記第2のコンタクトデバイスと接続することは、前記第2のコンタクトデバイスと前記オペレータデバイスとの間の音声通信を確立し、前記方法は 、前 記第2のコンタクトデバイスと前記オペレータデバイスとの間で送信された音声を記録する命令を送信するステップをさらに備えたことを特徴とする請求項1に記載の方法。
- 18オペレータデバイスをサポートするサービスエージェンシーにおいて、複数の番号を前記オペレータデバイスにアタッチするシステムであって、 1または複数のプロセッサと、コンピュータプログラムコードを記憶した非一時的コンピュータ可読記憶媒体とを備えたサーバを備え、前記コンピュータプログラムコードは、実行されると、 仮想番号と通信する、第1の電話デバイスからの要求に応答して、仮想番号のプロバイダからの第1の情報を受信することであって、前記仮想番号は前記オペレータデバイスと関連付けられ、前記受信した第1の情報は、前記第1の電話デバイスに対応するデバイス情報および前記仮想番号を含む、ことと、 前記第1の電話デバイスの前記デバイス情報と、マッピングテーブル内に前記仮想番号と関連付けて格納された前記オペレータデバイスのデバイス情報と、の比較に基づいて、前記第1の電話デバイスを第1のコンタクトデバイスとして識別することと、 前記第1の電話デバイスを前記第1のコンタクトデバイスとして識別したことに応答して、 前記第1のコンタクトデバイスを、前記仮想番号と関連付けられた前記オペレータデバイスと接続する命令、または、前記第1のコンタクトデバイスから受信されたデータを、前記仮想番号から前記オペレータデバイスに送信する命令、のうちの少なくとも1つを前記プロバイダに送信することと、 前記第1のコンタクトデバイスを前記オペレータデバイスと接続する接続要求、または前記第1のコンタクトデバイスから受信されたデータを前記仮想番号から前記オペレータデバイスに送信するために送信されたデータ、のうちの少なくとも1つにおける前記仮想番号に対して指定された番号情報、および/または、前記第1のコンタクトデバイスに対する前記デバイス情報を前記オペレータデバイスに識別させることと、 前記仮想番号と通信する、第2の電話デバイスからの要求に応答するための、前記プロバイダからの第2の情報を受信することであって、前記受信した第2の情報は、前記第2の電話デバイスに対応するデバイス情報および前記仮想番号を含む、ことと、 前記第2の電話デバイスの前記デバイス情報と、前記マッピングテーブル中に前記仮想番号と関連付けて格納された前記オペレータデバイスの前記デバイス情報と、の比較に基づいて、前記第2の電話デバイスを前記オペレータデバイスとして識別することと、 前記第2の電話デバイスを前記オペレータデバイスとして識別したことに応答して、 前記オペレータデバイスから受信された第2のコンタクトデバイスに対応する前記デバイス情報に基づいて、前記仮想番号を通じて前記オペレータデバイスを前記第2のコンタクトデバイスと接続する命令、または前記オペレータデバイスから受信された第2のコンタクトデバイスに対応する前記デバイス情報に基づいて、前記オペレータデバイスから受信されたデータを前記仮想番号から前記第2のコンタクトデバイスに送信する命令、のうちの少なくとも1つを前記プロバイダに送信することと、 前記オペレータデバイスを前記第2のコンタクトデバイスと接続する接続要求、または前記オペレータデバイスから受信されたデータを前記仮想番号から前記第2のコンタクトデバイスに送信するために送信されたデータ、のうちの少なくとも1つにおける前記仮想番号に対して指定された番号情報を、前記第2のコンタクトデバイスに識別させることと、 前記仮想番号を通じて前記オペレータデバイスを前記第2のコンタクトデバイスと接続する接続要求、または前記オペレータデバイスから受信されたデータを前記仮想番号から前記第2のコンタクトデバイスに送信するために送信されたデータ、のうちの少なくとも1つにおいて、前記オペレータデバイスのデバイス情報を前記第2のコンタクトデバイスに送信することを防止することと を備えたステップを実行することを特徴とするシステム。
- 19デバイス情報は送信番号を含み、前記第2の電話デバイスは、前記第2の電話デバイスの送信番号と、前記仮想番号と関連付けて前記マッピングテーブルに格納された前記オペレータデバイスの送信番号との間で一致したことに応答して、前記オペレータデバイスとして識別されることを特徴とする請求項18に記載のシステム。
- 20デバイス情報は送信番号を含み、前記第1の電話デバイスは、前記第1の電話デバイスの送信番号と、前記仮想番号と関連付けて前記マッピングテーブルに格納された前記オペレータデバイスの送信番号との間で一致しなかったことに応答して、前記第1のコンタクトデバイスとして識別されることを特徴とする請求項18に記載のシステム。
- 21前記ステップは、 前記仮想番号に対して受信された番号情報に基づいて、前記仮想番号をプロビジョニングすることと、 前記仮想番号に対するマッピング情報を受信することであって、前記マッピング情報は、前記オペレータデバイスに対応する前記デバイス情報を含み、前記デバイス情報は、前記オペレータデバイスの送信番号を含む、ことと、 前記オペレータデバイスに対応する前記送信番号と関連付けて、前記仮想番号を複数のアタッチされた番号として前記マッピングテーブルに格納することと をさらに備えたことを特徴とする請求項18に記載のシステム。
- 22前記仮想番号に対して受信された前記マッピング情報は、前記オペレータデバイスが前記仮想番号に接続することを認証するキー入力をさらに含み、前記ステップは、前記第2の電話デバイスから受信されたキー入力情報に応答して、前記第2の電話デバイスを前記オペレータデバイスとして認証することをさらに備えていることを特徴とする請求項21に記載のシステム。
- 231または複数のプロセッサと、コンピュータプログラムを記憶したコンピュータ可読記憶媒体とを備えた第2のサーバをさらに備え、前記コンピュータプログラムは実行されると、 所与の電話デバイスから前記仮想番号への接続要求を識別することと、 ターゲット電話デバイスにダイヤルアウトする命令を受信することと、 前記仮想番号を通じて、前記所与の電話デバイスと前記ターゲット電話デバイスとの間の接続を確立することと 前記所与の電話デバイスと前記ターゲット電話デバイスとの間の音声通信を記録することと を備えたステップを実行することを特徴とする請求項18に記載のシステム。
- 24前記仮想番号を通じて前記オペレータデバイスを前記第2のコンタクトデバイスに接続することは、前記仮想番号を通じた前記第2のコンタクトデバイスとの接続を要求して、 前記接続要求において、 前記仮想番号に対して指定された前記番号情報を前記第2のコンタクトデバイス に識 別 される ことを備え、前記接続要求は、前記オペレータデバイスとは異なる第3の電話デバイスから前記接続要求が来ているように見えるように、前記仮想番号に対して指定された前記番号情報を備えていることを特徴とする請求項18に記載のシステム。
- 25前記第1のコンタクトデバイスから前記仮想番号で受信された前記データ、または、前記仮想番号から前記第2のコンタクトデバイスに送信された前記データのうちの少なくとも1つは、ショートメッセージサービス(SMS)、マルチメディアメッセージサービス(MMS)、または、プロプライエタリサービス上のメッセージであることを特徴とする請求項18に記載のシステム。
- 26前記第1のコンタクトデバイスに関連付けられたデバイス情報を、前記仮想番号から前記オペレータデバイスに送信する前記メッセージにアタッチする命令、ならびに、前記第1のコンタクトデバイスの前記デバイス情報を有する前記メッセージを、前記仮想番号から送信して、前記仮想番号に対して指定された番号情報および前記第1のコンタクトデバイスに対する前記デバイス情報を、前記オペレータデバイスに識別させる命令、をさらに備えていることを特徴とする請求項25に記載のシステム。
- 27前記仮想番号から前記第2のコンタクトデバイスに送信する前記メッセージから、前記オペレータデバイスに関連付けられたデバイス情報、または前記第2のコンタクトデバイスに関連付けられたデバイス情報のうちの少なくとも1つを抽出する命令、ならびに、前記抽出した情報なしで、前記メッセージを前記仮想番号から前記第2のコンタクトデバイスに送信して、前記オペレータデバイスに対する識別デバイス情報の送信を防止する命令、をさらに備えていることを特徴とする請求項25に記載のシステム。
- 28前記第1のコンタクトデバイスおよび前記第2のコンタクトデバイスは、同一の電話デバイスであり、前記第1のコンタクトデバイスの送信番号は、前記第2のコンタクトデバイスに対して受信された送信番号と一致することを特徴とする請求項18に記載のシステム。
- 29前記オペレータデバイスを前記第2のコンタクトデバイスと接続することは、前記第2のコンタクトデバイスと前記オペレータデバイスとの間の音声通信を確立し、前記システムは、前記第2のコンタクトデバイスと前記オペレータデバイスとの間で送信された音声を記録する命令を送信することをさらに備えたことを特徴とする請求項18に記載のシステム。
Independent claims29
132 paragraphs, as filed
The disclosure relates generally to the field of undercover operations, and more specifically to managing multiple identities using a single phone.
Police officers and other agent "operators" often conduct multiple investigations at the same time during their duties. In many cases, these surveys show that operators use their phones to make calls and short message service "SMS" messages (proprietary messaging such as multimedia messaging service "MMS" messages and BLACKBERRY messages "BBM"". It is required to send (including services) or otherwise communicate with various contacts under a fake identity. Criminals and other individuals are often able to uncover information about the operator or information about the devices used by the operator from the data associated with the communication. Therefore, operators often use multiple phone devices to manage different contacts and protect their identities.
Many operators are provided with multiple mobile phones by their agency or department for use with different contacts and for different investigations. For example, an operator may need different phones with different numbers when communicating with different contacts in order to maintain a particular identity or hide its true identity. Traditionally, operators physically require multiple phones or multiple subscriber identification modules (SIM cards) to maintain their different identities.
The use of multiple physical phones in that the operator must carry the correct phone and / or multiple phones at the appropriate time in order to receive the call or use the device in other ways. , Presents difficulties for operators. Multiple SIM cards contain all the information they need for a given identity, but the operator does not receive notifications such as incoming calls to it unless the SIM card is active in the device. And it's also intrusive. Therefore, the operator needs multiple phones to monitor activity on multiple SIM cards. In addition, agencies lack the ability to issue the appropriate device, SIM, and / or corresponding identities to operators in real time. These challenges are discussed with respect to operators, but private individuals (eg, business owners) and other entities face similar challenges when operating multiple devices.
The above and other issues are addressed by methods and computer systems for configuring one or more virtual numbers for use on the network and attaching virtual numbers to operator devices. To. An embodiment of the method comprises a step of receiving connection information and communicating with a virtual number in response to a request from a telephone device, such as a telephone call or message. The connection information includes device information and a virtual number about the telephone device. Based on the connection information, the phone device is identified as a contact device or operator device from a mapping table that stores the device information associated with the virtual number information.
If the mapping table identifies the telephone device requesting a connection to the virtual number as the operator device, the method is to receive the device information corresponding to the contact device that the operator wants to communicate with, and the operator device through the virtual number. It further comprises a step of transmitting at least one of an instruction to connect to the contact device or an instruction to transmit the data received from the operator device to the contact device from the virtual number.
If the mapping table identifies a telephone device that requests a connection to a virtual number as a contact device, the method is to connect the contact device to the operator device associated with the virtual number, or from the virtual number, the contact device. It further comprises a step of transmitting at least one of the instructions to transmit the data received from the operator device. Since the contact device and the operator device communicate through the virtual number, the contact is prevented from ascertaining the device information and / or the number information associated with the operator device.
Embodiments of the system include a server having one or more processors and a non-temporary computer-readable storage medium containing computer program code. When executed, the computer program code causes the server to receive information and communicate with the virtual number in response to requests such as telephone calls or messages from telephone devices. The received information includes device information and virtual numbers related to the telephone device. Based on the connection information, the server identifies the phone device as a contact device or operator device in response to matching the received information with the device information associated with the virtual number information stored in the mapping table.
When the mapping table identifies the telephone device requesting a connection to the virtual number as the operator device, the server receives the device information corresponding to the contact device with which the operator wants to communicate, and the operator device is referred to through the virtual number. Send at least one of the commands to connect to the contact device, or from the virtual number, to send the data received from the operator device to the contact device.
When the mapping table identifies a telephone device that requests a connection to a virtual number as a contact device, the server uses an instruction to connect the contact device to the operator device associated with the virtual number, or from the virtual number, the contact device. Sends at least one of the instructions to send the data received from the operator device. Since the contact device and the operator device communicate through the virtual number, the contact is prevented from verifying the device information and / or the number information associated with the operator device.
In addition, multiple virtual numbers are attached or associated with a single operator device, allowing the operator to manage different contacts. The embodiment may then further comprise the step of receiving a choice of which virtual number to use for communication with the designated contact device without jeopardizing the operator identity.
The teachings of the embodiments can be easily understood by examining the following detailed description in connection with the accompanying drawings.<figref num="1A">FIG. 6 is a block diagram illustrating an environment for implementing multiple attached number "MA number: multiple attached number" systems according to one exemplary embodiment.</figref><figref num="1B">It is a block diagram which shows the operating environment of the agency service which provides the MA number according to one exemplary embodiment.</figref><figref num="2">FIG. 6 is a block diagram showing an MA module according to one exemplary embodiment.</figref><figref num="3A">It is a dialogue diagram showing a method for provisioning and mapping a virtual number for operating an operator device having an MA number according to one exemplary embodiment.</figref><figref num="3B">It is a table showing an exemplary embodiment of virtual number mapping for manipulating and monitoring MA numbers.</figref><figref num="3C">It is a table showing an exemplary embodiment of virtual number mapping for manipulating and monitoring MA numbers.</figref><figref num="4">It is a dialogue diagram which shows the method for connecting an operator device and a contact device using a virtual number according to one exemplary embodiment.</figref><figref num="5A">It is a dialogue diagram showing a method for dialing out to a contact device using an MA number according to one exemplary embodiment.</figref><figref num="5B">It is a dialogue diagram showing a method for dialing out to an operator device using an MA number according to one exemplary embodiment.</figref><figref num="6">It is a dialogue diagram which shows the method for monitoring an operator device according to one exemplary embodiment.</figref>
The drawings and the following detailed description relate to preferred embodiments by way of illustration only. It should be noted from the discussion below that alternative embodiments of the structures and methods disclosed herein are readily recognized as feasible alternatives that may be adopted without departing from the principles of the embodiments. I want to be.
The details of the plurality of embodiments are then referred to, examples of which are shown in the accompanying drawings. Note that whenever feasible, similar or reference numbers are used in the drawings and exhibit similar or similar functionality. The drawings show embodiments for illustration purposes only.
<Overview> Many operators own or are provided with mobile phones by their agency or department. Often, the traditional procedure for an operator to handle multiple cases and to supply / carry an additional device or SIM is not feasible under certain circumstances, or is simply cumbersome for the operator or agency. In addition, conventional procedures require the operator to manually manage the device, SIM, and the set of identities associated with them. In tense situations, operators may unknowingly endanger their identities or lack properly configured devices. Therefore, the agency may coordinate with the agency support service to configure the operator's mobile or landline telephone to satisfy the role of multiple telephone devices. This configuration is done over-the-air, which allows a given phone to be conveniently converted as needed. In addition, if the agency wishes to provide additional operators with the capabilities of multiple telephone devices, the agency can specify additional telephones for the configuration.
The exemplary embodiments described herein are wired and wired to network-enabled devices such as mobile phones or land-line telephones used with multiple attached numbers "MA numbers". Concerning implementing multiple attached "MA" numbers on wireless networks (eg PSTN, cellular networks, and / or WiFi). Since mobile phones and similar devices are generally carried by operators during undercover operations, mobile phones provide an existing platform for transmitting data wirelessly. Using such a device with an MA number allows the operator to utilize a single operator device. Operators working from a fixed position by landline telephone are also provided with similar capabilities for using MA numbers.
In addition, with the demand for smart phones and feature phones, additional monitoring and safety features may be integrated into the operator's device to increase on-site operational feasibility. For example, the operator device may be configured to collect a wide range of useful real-time data. Real-time data collected by the operator device may include voice and Global Positioning System (GPS) coordinates and the like.
The operator device may subsequently send all or part of the collected real-time data back to an agency, agency service, or another entity on an existing channel (eg, a network). An embodiment of an agency, agency service, and / or other entity within the MA number system receives the collected data for live streaming to storage and / or monitoring devices, operator devices, and records. Depending on the embodiment, the monitoring device accesses and presents (eg, plays and / or displays) various real-time and historical data stored or streamed by entities on the network. Further configured. For example, the monitoring device may access a web interface, API, or run a stand-alone application to view the details of the operator device and MA number as well as the collected information. In some embodiments, the monitoring device may access a portion of real-time data via a provided monitoring line configured to maintain operator cover. In addition, other agencies and monitoring devices with the appropriate credentials may likewise access some of the information collected during inter-agency interrogation.
<Environment and embodiment of operator device system> FIG. 1A is a block diagram showing an environment 100 that implements a plurality of attached numbering systems according to one exemplary embodiment. As shown, the environment 100 includes the agency support service provider "agency service" 115, the operator device 101, and the network 120 connecting the contact devices 105A-105E. Although only one agency service 115 and one operator device 101 are shown in FIG. 1A for clarity, embodiments can support a large number of operator devices 101 and multiple agency services. You may have provider 115.
Agency service 115 configures operator device 101, exchanges data over network 120, and stores data that supports one or more agencies (not shown) and operated operator device 101, and so on. Represents a collection of computing devices (eg, servers) and associated storage media that are configured to perform various activities. For example, Agency Service 115 is a functionality that is attributed to an agency through an application programming interface (API) or web interface, collectively interface, as described in more detail with reference to Figure 1B. May include one or more modules that provide. Agency Service 115 provides voice and video transmissibility (eg, internally and / /) within a monitoring interface using the Public Switched Telephone Network (PSTN), Voice over Internet Protocol (VoIP), and video conferencing services. Alternatively, it may also include an infrastructure that provides (on network 120).
The operator device 101 is often a mobile phone device capable of collecting data and transmitting data over the network 120 (eg, wirelessly). Some examples of operator device 101 include mobile phones, tablets, or notebook computers. An exemplary embodiment of the operator device 101 as a mobile phone includes a feature phone, a smart phone, and a standard mobile phone. Thus, a given mobile phone or other device operated as operator device 101 will not necessarily have all of the functionality attributed to the operator device or MA numbering system herein due to the inherent differences in device capabilities. It may not be included or may not be supported. In some embodiments, other telephone devices, such as landline telephones, are used by the MA numbering system.
In one embodiment, the operator device 101 executes an MA module that automates connections through network 120, collects data on network 120, and sends it to entities. An exemplary embodiment of the MA module will be described in more detail with reference to FIG.
In addition to the operator device 101, a number of monitoring devices (not shown) may connect entities on network 120 to acquire or present data associated with one or more operator devices. .. Depending on the embodiment, the monitoring device is a network 120 capable device that can be operated within the agency or outside the field. As referred to herein, the monitoring device is a mobile device or stationary that can connect (eg, wireless or wired) to network 120 such as agency networks, the Internet, the PSTN, and / or cellular networks. ) The device. Some examples of monitoring devices include mobile phones, landline phones, tablets and notebooks or desktop computers.
An exemplary embodiment of a monitoring device as a mobile phone can include a feature phone, a smart phone, or a standard mobile phone. Thus, a given mobile phone or other device operated as a monitoring device will necessarily include all of the functionality attributable to the monitoring device or MA numbering system herein due to the inherent differences in device capabilities. It may or may not be supported. In one exemplary embodiment, the monitoring device runs a monitoring module that interacts with entities on the network 120 to manage the operator device 101 and reference the collected data.
A plurality of contact devices 105 associated with contacts that the operator wishes to communicate with using the desired identity are also shown. Various contact device 105 embodiments include any network 120 capable device capable of transmitting or receiving information associated with a transmission number on network 120 (but in some examples, contacts). Device 105 may use the virtual number itself or other means to do so). Thus, as referred to herein, the contact device 105 has a connection (eg, wireless or wired) to network 120 to send or receive information over the Internet, PSTN, and / or cellular networks. A possible mobile device or fixed device. Some examples of the contact device 105 include mobile phones, landline phones, tablets, and notebooks or desktop computers.
Figure 1A also shows multiple virtual numbers 135A-135D configured for use on network 120. In one embodiment, the agency service 115 provisions and configures the virtual number 135 and processes the number information to establish an identity for the virtual number on the network 120. In addition, the agency service 115 receives connection information 137 that describes the operator device 101 and the contact device 105 that require communication with the virtual number 135 being processed. For example, operator device 101 or contact device 105 may request (and attempt) to communicate with a virtual number (eg, 135A) by means of a connection request or a method of sending data to another virtual number. Typical exemplary communication requests include calling a virtual number from a given device and / or messaging. Based on the device information and virtual number configuration, Agency Service 115 communicates with the virtual number as either an operator device 101 or a contact device 105 (and, in some cases, a monitoring device) associated with the virtual number. Identify the device that you want to do. For example, the agency service 115 may maintain a mapping table that stores the transmit number and credentials for a given operator device 101 and the attached virtual number 135 that identifies the operator device based on connection information 137. ..
After identifying the operator device 101, the agency service 115 allows the operator device 101 to identify a given contact 105A that the operator wants to communicate with, and the operator device 101 can identify the given contact 105A through a virtual number ( For example, it enables communication with the contact device 105A (which establishes a connection with or sends data from the virtual number). For example, the operator device 101 identifies device information such as a transmission number for the contact device 105A. The agency service 115 receives the device information for the contact device 105A and sends an instruction to make the contact device receive the call from the virtual number 135A. If the contact device 105A responds, the parties are connected. In another example, the operator device 101 may send data, such as an SMS message, to virtual number 135A, and may identify contact device 105A to receive SMS messages from virtual number 135A. In other words, the agency service 115 sends an instruction (for example, to the provider) to dial out the contact device 105A from the virtual number 135A, connect the operator device 101 to the contact device 105, or send an SMS message from the virtual number. To send the data received from the operator device 101 to the intended contact device. When agency service 115 connects operator device 101 to an entity on network 120 through a virtual number, virtual number 135 refers to the device and / or number information associated with the operator device by other entities, such as contact device 105. Prevent from doing.
When contact device 105A requests communication with virtual number 135A, agency service 115 determines the operator device associated with virtual number 135A (eg, operator device 101). The agency service 115 then allows the operator device 101 to use the virtual number 135A to receive communications from the contact device 105A. For example, the agency service 115 may send an instruction to connect the contact device 105 to the operator device 101 (for example, by optionally dialing out from the virtual number to the operator device 101), or virtual from the contact device. You may send an instruction to send data such as an SMS message received by number from the virtual number or directly from the agency service 115 to the operator device. Since the contact device 105 sends communication to / from the operator device 101 through the virtual number, the contact is usually unable to ascertain the device information and / or number information associated with the operator device.
On the other hand, the operator device 101 may receive connection information 137 and the number identity of the dialed virtual number from the agency service 115 or another entity regarding the contact device 105 dialing out the virtual number 135. Thus, the operator can make informed decisions regarding the caller and the identity expected of the operator. Agency service 115 also allows an operator or agency to configure multiple working numbers to attach to or associate with a single operator device 101 in order to manage various contact devices 105. To. The operator then uses a single operator device 101 to use which virtual number (eg, 135A) to connect to the identified contact device 105A on network 120 without compromising the operator identity. You may choose whether to use it.
Network 120 represents a communication path between an agency, an agency service 115, an operator device 101, a contact device 105, a monitoring device, and other entities (not shown). In one embodiment, the network 120 includes standard communication techniques and / or protocols and may include the Internet and PSTN. These communication technologies and / or protocols often carry both PSTN and Internet-related data. Therefore, network 120 includes Ethernet®, 802.11, worldwide interoperability for microwave access (WiMAX), 2G / 3G / 4G mobile communication protocols, worldwide interoperability for PSTN communications, digital subscriber lines (DSL), asynchronous transfer mode ( ATM), InfiniBand, and PCI Express Advanced It can include links that use techniques such as Switching. Similarly, the networking protocols used on Network 120 are Multiprotocol Label Switching (MPLS), Transmission Control Protocol / Internet Protocol (TCP / IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), It can include Simple Mail Transfer Protocol (SMTP), File Transfer Protocol (FTP), and so on. Data exchanged over network 120 can be analog audio (for example, for last mile PSTN communication), digital audio and video (for example, as a file or streaming via a real-time streaming protocol), hypertext markup language (HTML), and extendable. It can be represented using technologies and / or formats including markup language (XML), JavaScript®, VBScript, FLASH, and portable document formats (PDF). In addition, all or part of the data exchanged over network 120 can be transferred to the usual secure socket layer (SSL), transport layer security (TLS), virtual private network (VPN), and Internet protocol security (IPsec). It can be encrypted using encryption technology. In another embodiment, the entities on the network 120 may use customized and / or specialized data communication techniques in place of or in addition to those described above. For example, some government agencies and the military may operate ancillary networks to the Internet and the PSTN.
As used herein, the term "module" refers to program instructions and / or other logic used to provide the specified functionality. Therefore, the module can be implemented in hardware, firmware, and / or software. In one embodiment, a program module formed from executable computer program instructions is stored on a non-temporary storage device, loaded into memory, and executed by a computer processor as one or more processes.
As used herein, the terms "message", "messaging", and "short messaging service (SMS)" are used to communicate and transmit data over network 120, respectively. , Messaging services, as well as a range of related technologies or standards. These technologies and services include SMS messages, multimedia messaging service "MMS" messages, and proprietary messaging service messages such as the BLACKBERRY message "BBM".
FIG. 1B is a block diagram showing the operating environment of the agency service 115 that provides the MA number according to one exemplary embodiment. As shown, the operating environment includes an agency 110, a monitoring device 107, an operator device 101, a contact device 105, and a network 120 with components such as the Internet 123, telephony 125, and provider 127. Network 120 may also include GPS satellites (not shown) that relay position data to operator device 101 and other devices.
Agency 110 is used by each agency employee running an application or module to communicate with and receive data from agency services 115 and other entities on network 120 (eg, through interface 145). Represents a set of servers, desktops, notebook or tablet computers, mobile phones, and related storage media. For example, the Agency 110 device may run a web browser to access a web interface or run a mobile or desktop application to communicate with the API provided by Agency Service 115. Agency 110 also uses the public switched telephone network (PSTN), voice over Internet Protocol (VoIP), and video conferencing services to monitor or identify the configuration for operator device 101. It may include a telephone and video infrastructure that enables communication (eg, internally and / or on network 120).
The telecommunications network 125 implements worldwide interoperability for PSTN communications, including land-based and 2G / 3G / 4G radio protocols, among other protocols and technologies, servers, switches, and other hardware and software. It may be included. The telephone communication network 125 also provides mobile devices with the ability to transmit and receive data over the Internet 123. The telephone communication network 125 is one or more CSPs (not shown) that own a telephone number for use on the PSTN and the network of the communications service provider "CSP" itself (eg, a wireless network that communicates with the PSTN). Managed by.
Provider 127 may include servers, switches, and other hardware and software that communicate with CSPs and other entities on network 120. Provider 127 purchases or rents numbers from multiple CSPs for use on the telecommunications network 125. Provider 127 then manages the number provisioned for use by Agency Service 115 and the telephone communication traffic associated with that number. In one embodiment, provider 127 allows agency service 115 to provision one or more numbers as virtual numbers on network 120.
Generally, the numbers used on the telephone communications network 125 have an associated number identity, characterized by automatic number identification "ANI" information or caller identification, a given mobile device, VoIP device, or land. Regarding land-line devices. The virtual number, which can be operated by the PSTN and CSP networks, is associated with provider 127, which handles telephone communication traffic for the number. Since the virtual number is not about the end-user device, the provider 127 establishes a connection with the device that dials the virtual number and records call information such as call voice and caller history (eg, a computer-readable medium). (Above), as well as streaming / providing call information for download (eg, on network 120).
Provider 127 also passes / bridges audio in real time between one or more phone devices that establish a connection with the same or different virtual number (or connected to provider 127 through the virtual number). May be bidirectional or unidirectional. In addition, since the virtual number is processed by provider 127, agency service 115 may change the ANI information and caller identification associated with the virtual number.
In addition to provisioning a virtual number to Agency Service 115, Provider 127 communicates notifications and data associated with the Virtual Number with other entities such as Agency Service 115 or Agency 110. For example, provider 127 notifies agency service 115 (and optionally operator device 101 or monitoring device 107) of an incoming caller or message to a virtual number, and the caller (or another) to the virtual number. You may receive instructions from the agency service 115 to connect to the device) or redirect the message. Provider 127 may also receive instructions to stop / start recording the call to the virtual number and interface with the transcription service to transcribing the call voice. Provider 127 may then send records and postings to Agency Service 115 or other entities on Network 120.
In addition, provider 127 can use inbound and / or outbound audio and its recording to different parties connected to the virtual number in response to instructions received from agency service 115 (eg, via API). Or it may be disabled. Provider 127 may receive instructions from Agency Service 115 to manage the virtual number as part of the provisioning process when connecting the incoming caller to the virtual number, either before the incoming call or in real time. .. In some embodiments, provider 127 communicates directly with agency 110, operator device 101, and / or monitoring device 107 to provision virtual numbers, send notifications and data, or receive instructions. .. In addition, provider 127 itself may act as a CSP and vice versa.
Agency service 115 receives a virtual number provisioning and mapping request from agency 110, operator device 101, or monitoring device 107. These requests may include number information for provisioning virtual numbers, such as area code (eg, 555), country code (eg, +44), and / or associated CSP. Agency service 115 then queries provider 127 for an available virtual number that matches the request and returns the matching virtual number to the requesting entity. Agency service 115 then receives a selection of virtual numbers from the requesting entity and claims the virtual number from provider 127. Agency service 115 optionally identifies number information, such as ANI and / or caller identification, associated with a virtual number, allowing an entity to impersonate a number's identity on network 120. The agency service 115 then sends an instruction to change the number identity to the provider 127. Agency service 115 may optionally verify spoofed number identities. When the virtual number is no longer needed by Agency 110A, Agency Service 115 acquires any voice recording or call log associated with the virtual number and releases the number to Provider 127.
The request can also include mapping information for configuring the solicited virtual number function in the mapping table. Depending on the desired configuration, the mapping information can be the transmission number of the operator device 101 and / or the monitoring device 107, the virtual number for associating with the device, and / or the desired function of the virtual number (eg, MA number or local). Number) may be included. One exemplary mapping request is a virtual connection to which the operator device 101 connects to transmit the collected data (eg, voice) from the identity of the MA number on the telephone communication network 125 (eg, to the contact device 105). The virtual number billed for use as multiple attached numbers (MA numbers) in may be specified. In one embodiment, the request includes a transmission number of operator device 101 and a given solicited virtual number for configuration as an MA number. In response to the request, Agency Service 115 associates the transmit number of operator device 101 with the MA number and stores this association in the mapping table.
Another exemplary mapping request is the virtual local number (local) to which the monitoring device 107 connects to monitor the MA number (eg, listen for audio sent between the operator device 101 and the contact device 105). The virtual number charged for use as a number) may be specified. Operator device 101 may also utilize local numbers to avoid long-distance charges for MA numbers in different country or area codes. In one embodiment, the request comprises a given solicited virtual number (eg, local number) and MA number. In response to the request, Agency Service 115 associates the MA number with the local number and stores this association in the mapping table.
In some embodiments, the mapping request may optionally include a transmission number of monitoring device 107, which agency service 115 associates with an MA number or local number to identify the monitoring device. Since the plurality of monitoring devices 107A and 107B may monitor the call voice, the agency service 115 may store a plurality of transmission numbers of the monitoring devices in the mapping table in relation to the MA number or the local number.
In practice, the agency service 115 queries the mapping table to automatically connect devices to virtual numbers (eg, MA numbers) as operator device 101, monitoring device 107, or contact device 105 based on the device's transmit number. Identify. Thus, for example, the operator of operator device 101 can simply dial the MA number mapped to the outgoing number of the telephone and make a call using the given MA number.
Personnel with a monitoring device 107 who wish to monitor the operator device 101 on an agency 110A or on-site with a mobile phone or landline telephone have a local number associated with the MA number (and, in some embodiments, the MA number itself. ) Can be dialed. However, in one embodiment (eg, connecting to a local number), the agency service 115 does not identify the transmission number of the device as the transmission number of the operator device 101, so that the staff device is properly identified as the monitoring device 107. Will be done. In some embodiments (eg, connecting to a local number and / or MA number), the agency service 115 identifies the monitoring device 107 to connect to based on the mapping of the sending number of the monitoring device 107 to the receiving number. To do. Alternatively, the agency service 115 identifies the monitoring device 107 or the operator device 101 in response to the personal identification number or code "PIN" entered when connecting to the virtual number.
An embodiment of agency service 115 automatically dials the operator device when a call is received from the contact device 105 on the MA number mapped to the operator device for connecting the parties (eg, MA number). Use the mapping of operator device 101 to the MA number to instruct provider 127 to (from or via automatic transfer). In addition, an embodiment of Agency Service 115 identifies when the operator device wishes to use the MA number, and dials the contact device 105 identified by the operator (eg, from the MA number), and Use the mapping of operator device 101 to the MA number to instruct provider 127 to connect the parties. Agency service 115 may also notify operator device 101 of caller and MA number details via SMS message or email through interface 145. An embodiment of agency service 115 also uses the mapping information to send a text message received on the MA number to the operator device 101, as well as contact a text message from the MA number (eg, from the operator device). It may be sent to an entity on network 120 such as device 105.
In addition, an embodiment of agency service 115 maps the monitoring device 107 to an MA number to instruct provider 127 when a call is made or received using a given MA number. You can use it to automatically dial your monitoring device (for example, from a local number identified) or notify you (for example, an SMS message). Agency service 115 may also notify monitoring device 107 through interface 145 or via email.
To prevent unauthorized access to MA numbers (and local numbers), Agency Service 115 ensures that personnel and operators identify keystrokes when provisioning and / or mapping virtual numbers. to enable. Agency service 115 stores keystrokes in a mapping table or other suitable database structure to identify and authenticate callers attempting to connect to virtual numbers in response to accurate keystrokes. Depending on the embodiment, agency 110, agency service 115, or provider 127 may store mapping tables and / or keystrokes for device identification and authentication.
In some embodiments, the agency service 115 provides the MA module 141 to the operator device 101. The MA module 141 is the native dialer of the operator device 101. Interface with dialer) to automate the process of connecting to a given contact device 105. In addition, the MA module 141 may interface with the software and / or hardware of the operator device 101 to take advantage of features such as GPS devices to collect real-time position data. MA module 141 sends the collected data back to agency service 115 or other entity on network 120. Agency service 115 may then store the collected data for transmission to one or more monitoring devices 107 and agency 110. In addition, MA module 141 may be configured to be password protected or hidden when executed to prevent non-operator users from accessing the entire module and / or certain functions. MA module 141 is described in more detail with reference to FIG.
In some embodiments, the agency service 115 transfers the data received from the operator device 101 and the call voice between the operator and the contact to various monitoring devices 107 and / or device 150 on the network 120. Includes interface 145 to provide. For example, interface 145 may provide monitoring device 107 with data corresponding to the status of one or more operator devices 101 (eg, connected or disconnected) and the corresponding MA number and contact device information. When operator device 101 is transmitting real-time data or is connected to contact device 105, interface 145 provides audio from active transmission, GPS coordinates with headers, speed and Even if you stream data such as the coordinates of the last reported position to the location on the map and the internet protocol address and / or phone number of another employee who monitors or accesses the operator device or MA number. Good. In some embodiments, interface 145 synchronizes the data collected prior to transmission or includes a tag in the transmission data for synchronization of playback on monitoring device 107 or operator device 101. Interface 145 can also stream or provide a previously recorded monitoring session for download.
In some embodiments, agency service 115 provides monitoring module 140 to monitoring device 107 to access interface 145. Monitoring module 140 sends requests associated with configuring operator device 101 and receiving real-time and historical data. For example, monitoring module 140 provisions a virtual number, maps the transmission number of operator device 101 or monitoring device 107 to a given virtual number, and assigns keystrokes to connect to the virtual number. You may provide a user interface or status dashboard with. In one embodiment, the dashboard provides the option to toggle the recording session on and off by agency service 115. When the recording session is unavailable, the monitoring device 107 still receives real-time data, but agency service 115, equipment 150, and provider 127 do not store a copy of the collected data.
The monitoring module 140 is also provided by the current GPS position, tracked GPS position, live audio, mapping table information, and other information collected from the operator device 101, contact device 105, or MA number, or interface 145. Real-time status information for the operator device 101, including other streamed information, may be displayed. Similarly, monitoring module 140 may be used to access and replay historical activity associated with a given virtual number or operator device 101. For example, the monitoring module 140 may download the file for playback or stream the file. In addition to interfacing with Agency Services 115, Monitoring Module 140 may also interface with Equipment 150 for storing (or backing up) data collected within Agency 110. Further, the monitoring module 140 may include the functionality of the MA module 141 and vice versa.
In one embodiment, the agency 110 includes a device 150 that stores the data collected by the operator device 101 using the MA number and the call voice. The device 150 may utilize the monitoring interface 145 provided by the agency service 115 to update the stored data, or may receive the data directly from the operator device 101. In addition, device 150 may receive audio and associated transcripts recorded on the virtual number from provider 127 or agency service 115. One exemplary embodiment of device 150 also has its own interface (not shown) that allows the monitoring device 107 and operator device to access real-time and historical data stored in the device for MA numbers. )including. The interface provided by Agency Services 115 or Device 150 may also be accessible via a web browser for streaming or downloading data, and may include the same or similar options. ..
In addition, device 150 and agency service 115 may communicate at defined intervals or in response to notifications to download data to intermittently update the collected data and records. During the interval or notification period, agency service 115 processes the data and takes any necessary action as required by operator device 101 or monitoring device 107 until the data is transferred to device 150. You may do it. In some embodiments, the agency service 115 maintains a permanent connection with the device 150, facilitating the transfer of real-time data collected by the operator device 101 operated in the field.
In one embodiment, the agency service 115 is data collected by the operator device 101 beyond the time required for the agency service 115 and provider 127 to facilitate transfer, or data collected from a virtual number. Guarantee that you do not own. However, in mission-critical situations, operators and other agency 110 personnel cannot rely on the availability of equipment 150 to store and maintain the collected data. As a result, if device 150 cannot take ownership of the data collected during the transfer, or goes offline, agency service 115 and / or provider 127 will continue until device 150 is functioning. , You may maintain ownership of the collected data. In addition, agency service 115 and / or provider 127 may determine if the checksum, hash, or size of the transferred data matches the version of device 150 before deleting the stored data.
In some embodiments, the agency service 115 maintains the device on behalf of, or in addition to, the agency 110. In that case, the device may exist as a dedicated part of the hardware or remote storage. Alternatively, the embodiment of device 150 may be implemented in a cloud computing and storage stack available on network 120.
<Operator device functionality> FIG. 2 is a block diagram showing the MA module 141 according to one exemplary embodiment. As mentioned above, the MA module 141 may be downloaded from the agency service 115 to the operator device 101 to perform, facilitate communication using the MA number, and collect data and network 120. You may send it to the entity above. As shown in FIG. 2, the MA module 141 itself contains a plurality of modules. In the embodiment shown in FIG. 2, MA module 141 includes connection module 205, GPS module 210, provisioning module 215, caller ID module 220, case module 225, and SMS module 230. In some embodiments, the functionality is distributed among the modules in a format different from that described herein. Other embodiments have additional and / or other modules.
Connection module 205 automates the connection process of dialing out to a given contact. Connection module 205 receives input from the operator including the MA number associated with operator device 101. In some embodiments, the connection module 205 further receives an input indicating a local number or MA number associated with the operator device 101. Once the connection with the MA number is established, the connection module 205 sends the number of the contact device 105 that the operator wants to call on the network 120. The connection module 205 allows the operator to enter the number of the contact device 105 before or after establishing a connection with the MA number. In addition, the connection module 205 may interface with the agency service 115 to receive information about a given local number or the MA number associated with the transmission number of the operator device 101. The connection module 205 may then provide the operator with an interface indicating one or more available MA numbers, along with their number information for selection.
In one embodiment, the connection module 205 detects whether the incoming call was initially dialed to the MA number. The connection module 205 then determines the MA number and / or information on the operator device 105 for display to the operator. In one embodiment, the connection module 205 accesses a locally or remotely stored address book to retrieve the MA number and / or the address book entry associated with the operator device 105. Alternatively, connection module 205 may receive and display notifications regarding incoming calls from agency service 115 or provider 127. Based on the notification or address book information, the operator may inspect the appropriate entity and / or contact expected by the contact.
Depending on the capabilities of the operator device 101, the connection module 205 can make and receive multiple calls and calls to and from virtual and non-virtual numbers in a native dialer application or the like. To do.
The GPS module 210 communicates with the native GPS receiver on the operator device 101 to receive GPS position data. The GPS module 210 may also communicate with other radio receivers and directional mechanisms (eg, compass or accelerometer) on the operator device 101 to receive additional position data. The GPS module 210 processes GPS and radio position data to determine and improve estimated position measurements for the operator device 101. Positional measurements may include, but are not limited to, latitude, longitude, altitude, heading, speed, associated accuracy measurements, and the date and time of recording. The GPS module 210 transmits the determined position measurement to the agency service 115 or other entity on the network 120. In one embodiment, the GPS module 210 streams position measurements in real time.
The provisioning module 215 interfaces with provider 127 or agency service 115 to provision virtual numbers and change virtual number assignments and capabilities in the field. Alternatively, a web browser on the operator device 101 may be used. For example, a web browser or provisioning module 215 may present the operator with a list of all virtual numbers associated with a given account, transmission number, or local number. Through this interface, operators may provision and modify virtual number mappings and features.
The caller ID module 220 interfaces with provider 127 or agency service 115 to change the caller ID or other number information associated with the provisioned virtual number. For example, the caller ID module 220 identifies number information such as location, ownership, carrier, and when dialing out from a given MA number, any of the information is restricted or blocked. Present the operator with an interface to identify whether or not it should be.
In some embodiments, case module 225 interfaces with provider 127, agency service 115, or device 150 to retrieve activity associated with a given MA number, local number, or transmit number. For example, Case Module 225 presents an interface with an MA number that the operator can choose to refer to, for example, associated activity and number information. Case Module 225 may further provide an interface for the operator to associate contact information or other information (eg, an address book entry) with a given MA number or contact number. Case module 225 may store address book entries locally and / or remotely on agency service 115 or device 150.
In some embodiments, the MA module 141 includes an SMS module 230 that sends an SMS message with an MA number and receives an SMS message from the MA number. The SMS module 230 sends and receives SMS messages natively (natively) and / or sends and / or receives non-native messages, depending on the device's capabilities. May (eg, via Agency Service 115). The SMS module 230 provides the operator with an interface to select or identify the MA number used to send the SMS message and the number of the contact device 105 to receive the message. SMS module 230 communicates information for sending SMS messages to agency service 115 and / or provider 127 (for example, using SMS itself or through interface 145). The SMS module 230 may also receive SMS messages sent to the MA number natively or via interface 145. In one embodiment, the SMS module 230 reproduces the look and feel of a native SMS program on the operator device 101.
In some embodiments, the MA module 141 and modules within it interface and communicate with a non-native device attached to the operator device 101. For example, voice and location data can be determined from accessories coupled to operator device 101 (eg, wired microphones) or wirelessly connected (eg, Bluetooth® headsets).
In addition, some or all of the features provided by MA Module 141 require an operator-specified keystroke (eg, button press combination, password, or other personal identification) prior to operation or activation. You may.
<Virtual number provisioning> FIG. 3A is a dialogue diagram showing a method 300 of provisioning and mapping virtual numbers for operating an operator device 101 having an MA number according to one exemplary embodiment. First, the agency service 115 receives a request from a monitoring device 107, an operator device 101, a web interface provided, or another entity that includes a (300) calling code to provision a virtual number (310). ). The calling code may include an area code and a country code on which the provisioned virtual number is manipulated.
Agency service 115 queries the provider for a virtual number that matches the identified calling code (320). Provider 127 returns a list of available virtual numbers to Agency Service 115 (330), which sends the Virtual Numbers for display to the requester. Agency service 115 receives one or more virtual number selections (335) and charges provider 127 for each selected virtual number (340). Agency service 115 may optionally include the corresponding ANI and caller identification information for the virtual number, which can be edited on the requested devices 101, 107 or in the web interface. Agency service 115 then instructs provider 127 to store the changed virtual number information and update the associated virtual number information.
When one or more virtual numbers are requested, the agency service 115 can receive a mapping request for the virtual number and map the virtual number in response to the information in the mapping request (350). For example, the requester may be prompted to enter the transmission number of operator device 101 for association with a virtual number used as the MA number. The agency service 115 stores the transmission number and the MA number of the operator device 101 in a mapping table (for example, in the agency service 115 or on the device 150). The requester may change the mapping at any time without any interruption of service at the receiving number.
Often, the MA number has a different country code (or area code) than the monitoring device 107 or operator device 101 that connects to the MA number to monitor or receive calls on the MA number. Often. In some cases, the requester is aware of the country code or area code where the monitoring device 107 and / or the operator device 101 is located. Therefore, to avoid high cost charges for Agency 110A, Agency Service 115 should provision an additional virtual number for which the requester has a known country code and area code for use as a local number. To enable. Agency service 115 may receive a mapping request for a local number (for example, to map the transmission number of operator device 101) and map the local number to the identified MA number.
When the operator device 101 then dials the local number, the agency service 115 identifies the associated MA number from the mapping table. Agency service 115 may further identify the transmit number or operator PIN associated with the MA / local number and authenticate the operator device 101 (for example, based on the transmit number or PIN). The agency service 115 then instructs provider 127 to connect the operator device 101 to the MA number, or pass voice from the MA number to the local number, and connect the operator device to the local number.
When monitoring device 107 dials a local number, agency service 115 identifies the associated MA number from the mapping table. Agency service 115 may further identify the monitoring number or monitor the pin associated with the MA / local number and authenticate the monitoring device 107. The agency service 115 then instructs provider 127 to connect the monitoring device 107 to the MA number, or pass audio from the MA number to the local number, and connect the monitoring device to the local number. In addition, the monitoring device 107 should not inform the contact or interfere with the call status (eg, ringing, active, etc.), so the monitoring device 107 connects / disconnects (eg, virtual number). , To or from other devices, or entities) may be delayed or modified in order not to affect call status or inform contacts. ..
In some embodiments, the local number may be tied to the transmission number of operator device 101 for automatic mapping to the MA number. For example, for multiple surveys in different countries, operators using the same operator device 101 may use different MA numbers for each survey (eg, keep separate records or identify). To maintain your identity). The local number may be tied to the operator device 101, rather than requiring the operator or staff monitoring the operator to assign a local number to each MA number individually (or change the mapping frequently). When the operator device 101 is mapped to or used in the MA number, the agency service 115 maps the associated local number to the MA number. In such a way, a given local number may be dedicated to monitoring / supporting a particular operator device 101. Because multiple MA numbers are associated with a single local number, the operator device 101 or monitoring device 107 that dials the local number is on the list of mapped MA numbers that can be used to make or monitor calls. May be presented. The requester may respecify the mapping configuration as needed to change or switch between the MA number and the local number for the billed virtual and transmit numbers.
An exemplary embodiment of the monitoring device 107 that maps to the MA number and / or the local number can be performed in the same or similar format as the operator device 101 mapping.
FIG. 3B is a table showing an exemplary embodiment of a virtual number mapping 350 that operates the operator device 101 with MA numbers. As shown, the mapping table 360A contains multiple MA numbers 363A mapped to the corresponding transmission number 361A (eg, of operator device 101).
When agency service 115 receives a connection request from network 120 to MA number 363A, agency service identifies the device to connect as operator device 101 based on transmission number 361A stored in mapping table 360A. Agency service 115 or provider 127 then receives the contact number from operator device 101 and dials the corresponding contact number 105 from MA number 363A. If the number of the connecting device does not match transmission number 361A, Agency Service 115 identifies the device as contact device 105 and dials or dials the transmission number identified for operator device 101. Instruct provider 127 to dial this.
Before the operator device 101 is allowed to make or receive a call from the MA number or local number, the agency service 115 waits for or waits for the key input of the identified password, provider 127. You may instruct. For example, in some examples, provider 127, telephone communications 125 / PSTN, or agency service 115 correctly identifies or passes the device's outgoing or virtual number to establish a connection. May fail. If an invalid password is received for the local number, or if no password is received, the device will be disconnected. Contact 105 dials the number for the MA number, so if an incorrect password is received, or if the password is not received (for example, within a short time frame to make a call), the operator device 101 is dialed. To. In one embodiment, within a given time period (eg, 2-5 seconds), the operator must enter the password without being prompted to reduce suspicion when the line is dialed by another party. You must, or key in, enter the password (for example, press * or # before entering the password).
Similar precautions may be taken to authenticate the monitoring device 107 dialing the local number to monitor the call. In some embodiments, the mapping table 360A further includes mapping the transmission number of the monitoring device 107 to explicitly identify the monitoring device, in addition to the operator device 101.
FIG. 3C is a table showing an exemplary embodiment of a virtual number mapping 350 that operates the operator device 101 with MA numbers. As shown, the mapping table 360B contains multiple MA numbers 363B mapped to the corresponding transmission number 361B (eg, of operator device 101). In addition, multiple local numbers 365 mapped to MA number 363B are also shown.
When agency service 115 receives a connection request from network 120 to local number 365, agency service 115 identifies the connecting device as monitoring device 107 or operator device 101 (for example, a mapped transmission number or monitor). / Identifies the associated MA number 363B from the mapping table 360B) (based on the operator PIN). Agency service 115 then instructs provider 127 to connect to devices 101, 107 with the identified MA number 363B (eg, directly or via local number 365).
If Agency Service 115 identifies the device as Operator Device 101, the operator may also enter the contact number they wish to dial from the MA number. Agency service 115 then instructs provider 127 to dial the contact number identified from the MA number.
You may be required to enter the specified password key before connecting the monitoring device 107 or the operator device 101. In some embodiments, the mapping table 360B further includes mapping the transmission number of the monitoring device 107 to explicitly identify the monitoring device in addition to the operator device 101.
FIG. 4 is a dialogue diagram showing a method (400) of connecting an operator device 101 and a contact device 105 using a virtual number according to one exemplary embodiment. FIG. 4 further shows (400) a method of connecting a monitoring device to a virtual number according to one exemplary embodiment. When agency service 115 provisions a virtual number to provider 127, operator device 101, monitoring device 107, or contact device 105 may connect to the virtual number (400). However, each entity may be treated differently as described below.
Dial a virtual number (410) For any device 101, 105, or 107, provider 127 receives a connection request over the telecommunications network 125 and dials the number by agency service 115. Identifies as a provisioned (300) virtual number (420). Therefore, in the embodiment in which the agency service 115 stores the mapping table, the provider 127 passes the transmission number of the device attempting to connect to the virtual number and the virtual number to the agency service 115.
The agency service 115 then identifies the device attempting to connect to the virtual number as either an operator device 101, a monitoring device 107, or a contact device 105, based on the mapping table (430). Agency service 115 connects (or disconnects) the identified device (440) and also provides options or instructs provider 127 to perform operations according to the device classification.
<Operator device> When the operator device 101 dials the MA number, the agency service 115 determines that the transmission number stored in the mapping table for the dialed MA number matches the number of the device attempting to connect to the MA number. judge. Agency service 115 instructs provider 127 to connect the device to the MA number as operator device 101 (440).
Alternatively, if the agency service 115 determines that the operator device 101 is trying to connect to the local number, the agency service will send the transmit number (and / /) stored in the mapping table to the dialed local number. Or determine that the associated MA number) matches the device number. Agency service 115 instructs provider 127 to connect the device to the local number as operator device 101 (440). If only one MA number is present in the mapping table for the local number, then the agency service 115 will connect the operator device 101 with the MA number (for example, directly or through the local number) to the provider. May be automatically instructed. Alternatively, if there are multiple MA numbers assigned to local numbers, a menu with details about the MA numbers may be provided to the operator to select a given MA number. For example, "press 1 for John Doe", "press 1 for" "Restricted / Blocked" or "press 1 for 555-111-5555", and "John Doe" and "555-111-5555" may be number information for the corresponding MA number and used It may be a restricted or blocked number that indicates that the MA number does not display number information when it is done.
When the operator device 101 connects to the desired MA number (eg, through selection or directly), the operator may enter the number of the contact device 105 that the operator wants to dial from the MA number (eg, contact). Device transmission number). Provider 127 then dials out (500) (displays MA number information) from the MA number to the contact number and connects the parties. An exemplary embodiment of dialing out to the contact device 105 is described in more detail with reference to FIG. 5A.
<Monitoring device> When the monitoring device 107 dials the MA number, the agency service 115 determines that the transmission number of the monitoring device stored in the mapping table for the dialed MA number matches the device number. Agency service 115 then instructs provider 127 to connect the device to the MA number as monitoring device 107 (440) and disables (eg, mutes) the audio received from monitoring device 107. ..
Alternatively, if the Agency Service 115 determines that the device is trying to connect to a local virtual number, the Agency Service determines that the device number does not match the sending number of the operator device stored in the mapping table. You may. For example, Agency Service 115 determines the operator device transmission number stored in the mapping table for the dialed local number (and / or associated MA number) and does not match the operator device transmission number. A device that connects to a local number may be identified as a monitoring device. In another embodiment, the agency service 115 bases the monitoring device transmission number or MA number stored in the mapping table relative to the local number on the monitoring device 107 based on matching those numbers on the connecting device. May be identified. Agency service 115 then instructs provider 127 to connect the device to the local number as monitoring device 107 (440). If only one MA number exists for the local number, the agency service 115 may connect the monitoring device to the MA number (for example, disable voice) as described above, or instead. May automatically instruct provider 127 to pass the voice from the MA number (eg, the call voice between the operator and the contact) to the local number. The audio from the local number to the MA number may be disabled so that the audio received from the monitoring device does not need to be disabled on the local number. Alternatively, if there are multiple MA numbers assigned to local numbers, a menu with details about the MA numbers may be provided to the operator to select a given MA number. Provider 127 and / or Agency Service 115 also informs personnel using monitoring device 107 which MA number.
In some embodiments, no voice is transmitted to the operator device, but the monitoring device 107 may communicate with other devices that monitor a given MA number through a local number (eg, as in a conference call). ). In addition, the provider 127 or agency service 115 provides the monitoring device 107 with another monitoring device 107, audio on the MA number, or a key combination (for example, * 1, 2, etc.) to mute its own device. May be provided.
<Contact device> In one embodiment, the agency service 115 identifies as the contact device 105 a device that has a number that does not match the transmit number stored in the mapping table for the MA number (430). Agency service 115 identifies the transmit number associated with the MA number and instructs provider 127 to connect (440) the contact device 105 to operator device 101 (for example, dial out directly to operator device 101). By (500), or through the MA number). An exemplary embodiment of dialing out the operator device 101 to a transmission number (500) is described in more detail with reference to FIG. 5B.
<Additional considerations> In some embodiments, the PSTN or provider 127 fails to pass the transmission number associated with the operator device 101 (or monitoring device 107) to the provider or agency service 115. For example, provider 127 or agency service 115 may receive a number other than operator device 101 and may misidentify the operator device. Some exemplary PSTN failures and provider 127 failures are all 0 numbers (+00 000-000-0000), restricted numbers (737-874-2833), or simply inaccurate for operator device 101. Number. In any case, the agency service 115 may not be able to identify the operator device 101 by the received transmission number.
Agency service 115 can recognize that some numbers have been passed incorrectly (eg, restricted numbers or zero numbers).
In response (for example, to a call to a local number), the agency service 115 should play a prompt or play a prompt such as "press 1 for a operator device or press 2 for a monitoring device". May instruct provider 127. You can also obscure the prompt (for example, enter the extension number of the party you are trying to contact). The operator or staff may key in using the operator device 101 or the monitoring device 107.
Instead, the keystrokes on the operator device 101 and the monitoring device 107 are usually different, so the agency service 115 tells the provider 127 to simply play the recording of the unavailability of common tones or numbers, and the user. May notify the user that a key must be entered. A keystroke match with the stored credentials identifies the operator device 101 (or monitoring device 107) on the local number.
In some embodiments, the agency service 115 may prompt all devices connecting to the local number and key in for identification. For example, Agency 110A may want to enable the option to use an unmapped device as an operator device 101 on a particular MA number.
Prompts are valid for identification on local numbers (for example, because only operators and staff usually have number recognition, and it can further require PIN keying), but these Method is not effective for failure to pass the number to the MA number. This is because contact devices 105 usually have to be fooled into assuming that they are making a legitimate, secret call when dialing an MA number (rather than operator device 101 or monitoring device 107). Because it doesn't become. Therefore, the failure of the PSTN or provider 127 to pass the transmission number associated with the device calling the MA number may be treated differently.
In one embodiment, the agency service 115 may instruct the provider to initiate the dial-out process (500) as if the unidentified device was the contact device 105. When dial-out (500) is initiated, the operator or staff member does not recognize their device (for example, no menu is presented, or a prompt is played, and provider 127 is dialed out. (Because there is). On the other hand, the contact assumes the behavior to be normal. To capitalize this difference, agency service 115 instructs provider 127 to capture keystrokes during the dialing process to identify the requesting device as monitoring device 107 or operator device 101. May be good. The requesting device is then identified and connected according to the keystrokes provided.
<Operation of operator device> FIG. 5A is a dialogue diagram showing a method 500A of dialing out to the contact device 105 using the MA number according to one exemplary embodiment. Once the connection 400 between the operator device 101 and the MA number is established, the operator may enter the transmission number of the contact device 105. Alternatively, the contact device 105 number may have been previously entered into the application. In both examples, operator device 101 sends a number to dial out to provider 127 (510). Provider 127 then dials out the contact device 105 from the MA number (515). Therefore, when the contact device 105 receives the connection request, the call appears to come from the MA number. Therefore, the contact device 105 displays number information for MA numbers other than the operator device 101 (eg, for blocked or restricted numbers, if present). Contact device 105 picks up In the case of up), the provider 127 establishes a connection between the operator device 101 and the contact device 105 (520) (eg, through the MA number or local number, or the contact device operates additional numbers or device information. Directly when not receiving from the device). Operator device 101 and / or provider 127 may optionally send the number of contact device 105 to agency service 115 to keep a record or open a new record.
Once the connection 520 between the operator device 101 and the contact device 105 is established, provider 127 begins recording audio online. The operator device 101 collects voice data using a microphone coupled to the operator device. The operator device 101 then transmits the collected voice data to the provider 127 and the contact device 105 via a connection through the MA number (525). The contact device 105 communicates with the operator device 101 in a similar manner. The provider 127 also causes the monitoring device 107 to connect to the MA number or local number to monitor the call and / or to agency the voice data received from the operator device 101 and the contact device 105 on the network 120. Allows transmission to service 115 or device 150.
In addition, the operator device 101 may also collect position data from the GPS receiver and other directional mechanisms coupled to the operator device. The operator device 101 may determine the position measurement including the position of the operator device, the direction and speed of the operator device, and the associated accuracy of the measurement. The operator device 101 sends the position measurement to the agency service 115 (525). In some embodiments, the operator device 101 determines the position measurement in real time and sends it to the agency service 115 (525).
Provider 127 and / or Agency Service 115 may update device 150 with the received voice data (530). Agency service 115 or provider 127 may also update the device with any other data received from provider 127 and / or operator device 101 (530).
FIG. 5B is a dialogue diagram showing a method 500B of dialing out to the operator device 101 using the MA number according to one exemplary embodiment. As described above, the contact device 105 initiates a connection to the MA number (400), and the agency service 115 instructs provider 127 to connect the contact device 105 to the operator device 101. Therefore, the agency service 115 sends the transmission number of the operator device 101 stored in the mapping table to the MA number to the provider 127 (510). Depending on the embodiment, the agency service 115 and / or provider 127 coordinates the connection of the contact device 105 with the MA number and subsequent dialing to the operator device 101 or direct dialing to the operator device 101. It may be configured as follows.
<Connection through MA number> Agency service 115 connects the contact device 105 to the MA number after establishing a connection, but instructs provider 127 to play the ringtone for the MA number on the line (for example, the specified mp3 file). May be good. Effectively, the contact device 105 is connected to the MA number but does not recognize that the connection has already been established because the ringtone is still playing. In close time to establishing a connection between the contact device 105 and the MA number, provider 127 dials out to the provided transmission number of operator device 101 (515). In response to the operator device 101 answering the call, the provider 127 stops the ringtone being played to the contact device 105 and establishes a connection between the parties (520). If the operator device 101 does not respond, the provider 127 may direct the contact device 105 to the voice mailbox associated with the MA number, or disconnect the contact device 105.
<Direct connection> Agency service 115 may instruct provider 127 to connect contact device 105 to operator device 101 by forwarding a call to the calling number of operator device 101 to dial out (515). This process usually results in the contact listening to the ringtone on operator device 101. Ringtones can vary from country to country, and for a number of other reasons, contacts will find that the ringtone being played is different from the ringtone expected for a MA number. You may notice it. Therefore, the agency service 115 may instruct provider 127 to play a ringtone for an MA number other than the operator device 101 being dialed. In some embodiments, provider 127 plays an mp3 file of MA number ringtones for contact device 105. Alternatively, provider 127 may dial the MA number itself and pass the ringtone voice to contact device 105. In both examples, provider 127 suppresses the ringtone of operator device 101, for example by disabling voice, until operator device 101 answers the call. When the operator device 101 responds, the provider 127 may establish a connection 520 between the parties and pass audio over the line to a local number or MA number for monitoring and / or recording. If the operator device 101 does not respond, the provider may direct the contact device to the voice mailbox associated with the MA number or disconnect the contact device.
In some embodiments, provider 127 and / or agency service 115 may provide notification information 517 to operator device 101. Notification information 517 includes contact device 105 and / or MA number information that describes the identity expected from the caller and operator. In some embodiments, the notification information 517 may be injected into, or may be included with, the caller identification information provided for a normal call. In other embodiments, the notification information 517 may be provided in an SMS message or may be sent to the operator device 101 for display using the MA module 141. In one embodiment, in addition to immediately establishing a connection between the operator device 101 and the contact device 105 (520) when the operator device 101 responds, the provider 127 includes notification information 517 to the operator. Send voice data. Agency service 115 also offers the option of accepting the call, disconnecting the call, or forwarding the call to voicemail with the MA number (for example, by picking up the handset or selecting the option provided). ) May be instructed to provider 127.
When the connection 520 between the operator device 101 and the contact device 105 is established, the provider 127 records the voice on the line. The operator device 101 collects voice data using a microphone coupled to the operator device. The operator device 101 then transmits the collected voice data to the provider 127 and the contact device 105 via a connection through the MA number (525). The contact device 105 communicates with the operator device 101 in a similar manner. Provider 127 also provides an agency service on network 120 with the monitoring device 107 connecting to the MA number or local number to monitor the call and / or the voice data received from the operator device 101 and the contact device 105. Allows transmission to 115 or device 150.
In addition, the operator device 101 may also collect position data from GPS receivers and other directional mechanisms coupled to the operator device, as described above with reference to FIG. 5A. Provider 127 and / or Agency Service 115 may update device 150 with the received voice data (530). Agency service 115 or provider 127 may also update device 150 with any other data received from provider 127 and / or operator device 101 (530).
<SMS communication> In addition to making and receiving calls through virtual numbers, operator device 101 may also send and receive SMS messages through MA numbers. Depending on the embodiment of operator device 101, SMS messages may be sent / received via native SMS functionality or using an application or web browser. Therefore, the operator device 101 does not need to request a telephone communication function for SMS communication through the MA number.
<Send SMS message> In one embodiment, in order to send an SMS from the MA number to the contact device 105, the operator prepends or appends to the native SMS message sent from the operator device 101 to the MA number. (Append) (for example, manually or using MA module 141) (for example, To: [contact number] | The meeting is at 10 am), the desired contact device 105 may be shown. Provider 127 forwards the SMS message received on the virtual number to agency service 115 for processing. The agency service 115 may parse the SMS to determine information about the contact device 105, such as a transmission number added to the beginning or end of the SMS message. Agency service 115 can also parse SMS to determine the source send number (for example, for lookups in the mapping table) and / or keystroke information for source authentication. Good. The agency service 115 then extracts the contact transmission number, any device information associated with the operator device, and any format or keystroke information from the SMS message. Agency service 115 then instructs provider 127 to send the modified SMS message to the contact number extracted from the MA number that first received the SMS. In some embodiments, the MA module 141 provides an interface for the user to enter the MA number and contact number, which is automatically attached to the SMS.
Alternatively, embodiments of operator device 101 may communicate data for transmission via SMS from the MA number to agency service 115. For example, an embodiment of MA module 141 or web interface may provide a menu or interface for the user to enter or select a given MA number and transmission number of contact device 105. The interface also provides the operator with the ability to enter message content. The operator may then submit the message and associated information to Agency Service 115. Agency service 115 then instructs provider 127 to send an SMS message containing the message from the identified MA number to the identified contact number.
When the SMS is delivered, Provider 127 and / or Agency Service 115 confirms receipt of the SMS on the contact device 105 on the operator device 101 or other entity and / or in a copy of the SMS and associated information. Device 150 may be updated.
<Receive SMS message> In one embodiment, in order to receive the SMS sent from the contact device 105 to the MA number, the provider 127 sends the data received on the virtual number (eg, SMS message) to the agency service 115 for processing. To do. The agency service 115 may then analyze the SMS. However, since the SMS message content does not contain the information added at the end or at the beginning (for example, in the correct format with the transmission number), the agency service 115 is for delivery to the operator device 101. Identifies the SMS message as an inbound message on the MA number. Agency service 115 also determines information about the received message, contact device 105 (eg, device transmission number), and / or the MA number at which the message was received, and finally puts that information in the SMS message. It may be added or added at the beginning. The agency service 115 then determines the transmission number of the operator device 101 associated with the MA number that received the SMS message and sends the SMS message to the operator device 101 along with any attached information. Instruct.
Agency service 115 may instruct the provider to send an SMS message from the MA number on which the message was received to the operator device 101 to prevent inadvertent direct communication with the contact device 105. For example, Agency Service 115 or Provider 127 may prefix the SMS message with the calling number of the contact device from which the original SMS message was received. The agency service 115 may then send a prefixed SMS (eg, From: [contact number] | The meeting is at 10 am) from the MA number to the operator device 101, including the content of the original message. ..
In some embodiments, MA module 141 provides an interface for the user to view SMS messages. MA module 141 may parse SMS messages to determine MA number and / or contact device 105 information attached by agency service 115 and extract information attached for presentation on the interface. ..
Alternatively, the agency service 115 may communicate the content from the SMS message received on the MA number with the associated contact information and MA number information to the operator device 101. For example, embodiments of MA module 141 may receive messages and associated information and display them in an interface to the operator. Alternatively, Agency Service 115 may provide a web interface for displaying received SMS and associated information.
When the SMS is delivered, the provider 127 and / or the agency service 115 confirms receipt of the SMS on the operator device 101 or other entity and / or updates the device 150 with a copy of the SMS and associated information. You may.
<Monitoring operator device> FIG. 6 is a dialogue diagram showing a method 600 for monitoring the operator device 101 according to one exemplary embodiment. As described above, Agency Service 115 receives the collected data from the operator device and / or provider 127 (610A). In addition, provider 127 may receive data from operator device 101 (610B). Agency service 115 and / or provider 127 may then update the equipment at agency 110 (530). The monitoring device 107 may then monitor the operator device 101 using one or both of the processes outlined above (600A, 600B).
In one embodiment, the monitoring device 107 may connect to a local number or MA number (400) to monitor the operator device 101 (600A). Monitoring device 107 may be connected by answering an incoming call from a local or MA number initiated by provider 127, or by dialing the virtual number directly as described with reference to FIG. (400).
Once the connection between the monitoring device 107 and the MA number or local number is established, the monitoring device receives live audio transmitted between the operator device 101 and the contact device 105 (640). To continue monitoring operator device 101 (600A), monitoring device 107 simply maintains connection 400 with a virtual number.
In another embodiment, the monitoring device 107 connects to the agency service 115 and / or device 150 (650) to monitor the operator device 101 (600B). Monitoring device 107 makes a connection using a web browser or monitoring module 140 that retrieves or streams the collected data through a monitoring interface (eg, monitoring interface 145) on device 150 or agency service 115. May be established (650).
In one exemplary embodiment, monitoring device 107 streams voice and / or position measurements from agency service 115 in real time (660). Further, the monitoring device 107 may retrieve the historical data stored on the device 150 and refer to the previously recorded operation session 500 of the operator device 101 (670). In some embodiments, the device 150 also supports real-time monitoring.
In some examples, the monitoring device 107 receives a notification from the monitoring interface 145 for display in a web browser or display in the monitoring module 140. The exemplary notification includes a voice or visual alert to notify the employee when the operator device 101 stops transmitting real-time data (eg, ends the call). In some embodiments, the monitoring device 107 also uses the monitoring interface 145 for display in a web browser or display in the monitoring module 140 for SMS communication between the operator device 101 and the contact device 105. May be taken out.
<Overview> The above description of the embodiments are provided for illustration purposes only and are not intended to be inclusive or intended to be limited to disclosure to the exact form disclosed. is not it. Those skilled in the art can understand that a number of modified and modified forms are possible in view of the above disclosure.
A portion of the disclosure describes embodiments with respect to algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the art of data processing techniques to efficiently convey substantial work to other skilled in the art. These operations are described functionally, computationally, or logically, but are understood to be implemented by computer programs or equivalent electronic circuits, microcode, and the like. Moreover, it has often proved convenient to refer to these arrangements of operations as modules, without loss of generality. The operations described and their associated modules may be performed in software, firmware, hardware, or any combination thereof.
Any step, operation, or process described herein may be performed alone or in combination with other devices on one or more hardware or software modules, or may be implemented. Good.
Embodiments may also relate to devices that perform the operations herein. This device may be specifically configured for the required purpose and / or a general purpose computing device in which it is selectively activated or reconfigured by a computer program stored in the computer. May include. Such computer programs may be stored on non-temporary, non-tangible computer-readable storage media, or any type of medium suitable for storing electronic instructions that can be coupled to the computer system bus. Further, any computing system referred to herein may include a single processor or may be an architecture that employs a multi-processor design for increased computing power.
Embodiments may also relate to products produced by the computing processes described herein. Such products may include information arising from the computing process, which is stored in non-temporary, non-tangible computer-readable storage media and computer program products or as described herein. Any embodiment of other data combinations may be included.
Finally, the terms used herein have been selected primarily for readability and instructional purposes, as well as to delineate or define the subject of the invention in detail. It's not a thing. Therefore, the scope of the present disclosure is not limited by this detailed description, but rather is intended to be limited by the claims issued against the application under this specification. Therefore, the disclosure of embodiments is not intended to limit the scope of the present disclosure set forth in the appended claims, but is intended to be exemplary.
10 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2001268230A | Cites | Japan |
| JP2001237965A | Cites | Japan |
| US20080008105A1 | Cites | United States of America |
| US20070105531A1 | Cites | United States of America |
100 members in 10 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 201161503586 | United States of America | P | |
| 201161503586 | United States of America | P | |
| 61503586 | United States of America | – | |
| 2012045052 | United States of America | W | |
| 2012045052 | United States of America | W | |
| 61503586 | – | – | – |
| US201161503586P | – | – | – |
| US2012045052 | – | – | – |
| WO2012US45052 | – | – | – |
Members100
| Document | Office | Kind | |
|---|---|---|---|
| CA2837595A1 | Canada | A1 | |
| CA2897088A1 | Canada | A1 | |
| US2012309379A1 | United States of America | A1 | |
| WO2012166729A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CA2839952A1 | Canada | A1 | |
| US2013003942A1 | United States of America | A1 | |
| WO2013003779A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CA2850524A1 | Canada | A1 | |
| US2013095791A1 | United States of America | A1 | |
| WO2013056156A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US2013208878A1 | United States of America | A1 | |
| AU2012262351A1 | Australia | A1 | |
| US8626078B2 | United States of America | B2 | |
| AU2012275151A1 | Australia | A1 | |
| AU2012262351B2 | Australia | B2 | |
| US2014079201A1 | United States of America | A1 | |
| US2014080473A1 | United States of America | A1 | |
| US2014087692A1 | United States of America | A1 | |
| CN103703693A | China | A | |
| EP2715949A1 | European Patent Office (EPO) | A1 | |
| MX2013013965A | Mexico | A | |
| CN103733601A | China | A | |
| AU2012323961A1 | Australia | A1 | |
| AU2014201981A1 | Australia | A1 | |
| MX2014000151A | Mexico | A | |
| EP2727323A1 | European Patent Office (EPO) | A1 | |
| US8731171B2 | United States of America | B2 | |
| MX2014004373A | Mexico | A | |
| CN103947129A | China | A | |
| EP2767003A1 | European Patent Office (EPO) | A1 | |
| US8824652B2 | United States of America | B2 | |
| JP2014524163A | Japan | A | |
| WO2014151684A2 | World Intellectual Property Organization (WIPO) | A2 | |
| JP2014526170A | Japan | A | |
| JP5624252B2 | Japan | B2 | |
| US2014334617A1 | United States of America | A1 | |
| RU2533171C1 | Russian Federation | C1 | |
| WO2014151684A3 | World Intellectual Property Organization (WIPO) | A3 | |
| JP2014533461A | Japan | A | |
| US8934847B2 | United States of America | B2 | |
| EP2715949A4 | European Patent Office (EPO) | A4 | |
| JP2015039199A | Japan | A | |
| US2015065101A1 | United States of America | A1 | |
| US2015071425A1 | United States of America | A1 | |
| EP2767003A4 | European Patent Office (EPO) | A4 | |
| US9031218B2 | United States of America | B2 | |
| EP2727323A4 | European Patent Office (EPO) | A4 | |
| IN2740CHN2014A | India | A | |
| AU2014201981B2 | Australia | B2 | |
| RU2014102971A | Russian Federation | A | |
| CA2837595C | Canada | C | |
| AU2014236991A1 | Australia | A1 | |
| RU2567860C1 | Russian Federation | C1 | |
| RU2570899C2 | Russian Federation | C2 | |
| AU2012323961B2 | Australia | B2 | |
| EP2974251A2 | European Patent Office (EPO) | A2 | |
| US9253311B2 | United States of America | B2 | |
| US9270814B2 | United States of America | B2 | |
| MX2015012023A | Mexico | A | |
| RU2014135229A | Russian Federation | A | |
| US9313323B2 | United States of America | B2 | |
| US2016119472A1 | United States of America | A1 | |
| US2016198041A1 | United States of America | A1 | |
| CA2850524C | Canada | C | |
| JP5965954B2 | Japan | B2 | |
| CN103733601B | China | B | |
| AU2014236991B2 | Australia | B2 | |
| JP6016908B2This record | Japan | B2 | |
| MX343371B | Mexico | B | |
| EP2974251A4 | European Patent Office (EPO) | A4 | |
| AU2012275151B2 | Australia | B2 | |
| US9674339B2 | United States of America | B2 | |
| JP6141287B2 | Japan | B2 | |
| US9736296B2 | United States of America | B2 | |
| US2017251101A1 | United States of America | A1 | |
| US2017264740A1 | United States of America | A1 | |
| MX351685B | Mexico | B | |
| US2017318151A1 | United States of America | A1 | |
| CN103947129B | China | B | |
| CA2839952C | Canada | C | |
| US9998603B2 | United States of America | B2 | |
| EP2767003B1 | European Patent Office (EPO) | B1 | |
| EP2715949B1 | European Patent Office (EPO) | B1 | |
| EP2974251B1 | European Patent Office (EPO) | B1 | |
| EP2727323B1 | European Patent Office (EPO) | B1 | |
| US10187518B2 | United States of America | B2 | |
| US10218838B2 | United States of America | B2 | |
| US2019158656A1 | United States of America | A1 | |
| US2019166250A1 | United States of America | A1 | |
| CA2897088C | Canada | C | |
| US10375233B2 | United States of America | B2 | |
| US2019306307A1 | United States of America | A1 | |
| US10547737B2 | United States of America | B2 | |
| US10547740B2 | United States of America | B2 | |
| US2020120206A1 | United States of America | A1 | |
| US2020128127A1 | United States of America | A1 | |
| US10887456B2 | United States of America | B2 | |
| US10944860B2 | United States of America | B2 | |
| US2021120122A9 | United States of America | A9 | |
| US10999735B2 | United States of America | B2 |
21 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| 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 | |
| Notification of acceptance of power of attorneyJAPANESE INTERMEDIATE CODE: R3D02RD02 | RD02 | |
| Written notification of registration of transferJAPANESE INTERMEDIATE CODE: R350R350 | R350 | |
| Request for change of ownership or part of ownershipJAPANESE INTERMEDIATE CODE: R313111S111 | S111 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on accelerated examinationJAPANESE INTERMEDIATE CODE: A971005A975 | A975 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 | |
| Explanation of circumstances concerning accelerated examinationJAPANESE INTERMEDIATE CODE: A871A871 | A871 |
Numbers
- Publication
- 6016908
- Publication, DOCDB
- 6016908
- Publication, EPODOC
- JP6016908B
- Application
- 2014519176
- Application, DOCDB
- 2014519176
- Application, EPODOC
- JP20140519176
Titles2
- Japanese
- 単一の携帯電話または陸線電話への複数の電話回線のアタッチ
- English
- Attaching multiple phone lines to a single mobile phone or landline phone
Classification
- CPC, 15
- H04M3/42059
- H04M2250/66
- H04M3/42153
- H04M3/42306
- H04M3/2281
- H04M3/42008
- H04M3/42068
- H04M3/4211
- H04M3/42136
- H04M3/42221
- H04M3/42229
- H04M3/382
- H04M1/724
- H04M3/42042
- H04M3/02
- IPC, 3
- H04M3 42
- H04M1 724
- H04W8 26
