US9736296B2

Attaching multiple phone lines to a single mobile or landline phone

Summary by NHIP

Virtual number call routing method

The method connects multiple telephonic devices to a single virtual number by identifying them against stored authorized transmitting numbers in a mapping table. It distinguishes contact devices from operator devices based on whether their transmitting numbers match the stored authorized number, then routes audio communications accordingly.

Claim Score by NHIP

Read claim 1, the broadest

Abstract

Agencies issue multiple devices to personnel for maintaining distinct identities over the course of assigned investigations. To provide flexible capabilities to agencies, a phone is converted for use with multiple attached telephone numbers. Accordingly, a single phone may be used to manage multiple identities over the course of one or more investigations. Using a multiple attached number, a given device can place and receive calls over the network to and from contacts. In addition to providing multiple attached numbers, calls using the multiple attached numbers may be monitored live and recorded to establish evidence.

US9736296B2, drawing sheet 1 — Sheet 1 of 10

Term

5.8 yearsleft in the term

Expires 29 June 2032.

27 claims: 2 independent, 25 dependent

1
Broadest claimClaim Score 36, narrow(NHIP)A computer based method comprising:receiving first number information in response to a request from a first telephonic device to connect to a virtual number, the virtual number associated with an operator device and the first number information including a transmitting number corresponding to the first telephonic device and the virtual number;identifying the first telephonic device as a first contact device based on a lack of a match between the transmitting number of the first telephonic device and an authorized transmitting number stored in association with the virtual number in a mapping table;in response to identifying the first telephonic device as the first contact device, transmitting instructions for connecting the first contact device with the operator device associated with the virtual number;receiving second number information in response to a request from a second telephonic device to connect to the virtual number, the second number information including a transmitting number corresponding to the second telephonic device and the virtual number;identifying the second telephonic device as the operator device based on a match between the transmitting number of the second telephone device and the authorized transmitting number stored in association with the virtual number in the mapping table;andin response to identifying the second telephonic device as the operator device, receiving a transmitting number corresponding to a second contact device and transmitting instructions for connecting the operator device with the second contact device through the virtual number.
15
A system for attaching multiple numbers to an operator device, the system comprising:a server comprising one or more processors and a non-transitory computer-readable storage medium storing computer program code, the computer program code when executed by a processor performing steps comprising: receiving first number information in response to a request from a first telephonic device to communicate with a virtual number, the virtual number associated with an operator device and the first number information including a transmitting number corresponding to the first telephonic device and the virtual number;identifying the first telephonic device as a first contact device based on a lack of a match between the transmitting number of the first telephonic device and an authorized transmitting number stored in association with the virtual number in a mapping table;in response to identifying the first telephonic device as the first contact device, transmitting instructions for connecting the first contact device with the operator device associated with the virtual number or transmitting data received from the first contact device to the operator device from the virtual number;receiving second number information in response to a request from a second telephonic device to communicate with the virtual number, the second number information including a transmitting number corresponding to the second telephonic device and the virtual number;identifying the second telephonic device as the operator device based on a match between the transmitting number of the second telephone device and the authorized transmitting number stored in association with the virtual number in the mapping table;andin response to identifying the second telephonic device as the operator device, receiving a transmitting number corresponding to a second contact device and transmitting instructions for at least one of connecting the operator device with the second contact device through the virtual number or transmitting data received from the operator device to the second contact device from the virtual number.

Independent claims2

159 paragraphs in 6 sections, as filed

This application claims the benefit of U.S. Provisional Application 61/503,586, filed Jun. 30, 2011, which is incorporated by reference herein in its entirety. This application is also related to U.S. patent application Ser. No. 14/086,960, filed Nov. 21, 2013, entitled “Attaching Multiple Phone Lines to a Single Mobile or Landline Phone” which is a co-pending U.S. Continuation Application of this application.

BACKGROUND

1. Field of Art

The present disclosure generally relates to the field of undercover operations and more specifically to managing multiple identities using a single phone.

2. Background of the Invention

Police officers and other agents “operators” oftentimes conduct multiple investigations at the same time during the course of their duties. In many cases, these investigations require the operator to use phones to call, send short message service “SMS” messages (including multimedia messaging service “MMS” messages and proprietary messaging services such as BLACKBERRY messages “BBM”), or otherwise communicate with various contacts under a fake identity. Oftentimes, criminals and other individuals can ascertain information about the operator or the device used by the operator from data associated with the communication. Accordingly, operators frequently use multiple telephonic devices to manage different contacts and protect their identity.

Many operators are issued multiple mobile phones by their agency or department for use with different contacts and for different investigations. For example, the operator may require different phones having different numbers when communicating with different contacts in order to maintain a specific identity or conceal their true identity. Traditionally, the operator would physically require multiple phones or multiple subscriber identity modules (SIM cards) to maintain these different identities.

Use of multiple physical phones present difficulties for the operator in that the operator must carry the correct phone and/or multiple phones at the right time to receive a call or otherwise use the device. Multiple SIM cards are similarly intrusive in that, while they contain all the information required for a given identity, the operator would not receive notifications of calls, etc., incoming to a SIM card unless it was active in a device. Hence, the operator would still require multiple phones to monitor activity on multiple SIM cards. Furthermore, agencies oftentimes lack the ability to issue operators the appropriate devices, SIMs and/or corresponding identities in real time. While these difficulties are discussed with respect to an operator, private individuals (e.g., a business owner) and other entities face similar difficulties when operating multiple devices.

SUMMARY

The above and other issues are address by a method and computer system for configuring one or more virtual numbers for use on a network and attaching the virtual numbers to the operator device. An embodiment of the method comprises receiving connection information in response to requests, such as a phone call or a message, from a telephonic device to communicate with a virtual number. The connection information includes device information about the telephonic device and the virtual number. Based on the connection information, the telephonic device is identified as a contact device or operator device from a mapping table that stores device information associated with virtual number information.

If the mapping table identifies the telephonic device requesting to connect to the virtual number as an operator device, the method further comprises receiving device information corresponding to a contact device the operator would like to communicate with and transmitting instructions for at least one of connecting the operator device with the contact device through the virtual number or transmitting data received from the operator device to the contact device from the virtual number.

If the mapping table identifies the telephonic device requesting to connect to the virtual number as a contact device, the method further comprises transmitting instructions for at least one of connecting the contact device with the operator device associated with the virtual number or transmitting data received from the contact device to the operator device from the virtual number. As the contact device and the operator device communicate through the virtual number, contacts are prevented from ascertaining device and/or number information associated with the operator device.

An embodiment of the system comprises a service having one or more processors and a non0transitory computer-readable storage medium storing computer program code. When executed, the computer program code causes the server to receive information in response to requests, such as a phone call or a message, from a telephonic device to communicate with a virtual number. The information received includes device information about the telephonic device and the virtual number. Based on the connection information, the server identifies the telephonic device as a contact device or operator device in response to matching received information with device information associated with virtual number information stored in a mapping table.

If the mapping table identifies the telephonic device requesting to connect to the virtual number as an operator device, the server receives device information corresponding to a contact device the operator would like to communicate with and, in turn, transmits instructions for at least one of connecting the operator device with the contact device through the virtual number or transmitting data received from the operator device to the contact device from the virtual number.

If the mapping table identifies the telephonic device requesting to connect to the virtual number as a contact device, the server transmits instructions for at least one of connecting the contact device with the operator device associated with the virtual number or transmitting data received from the contact device to the operator device from the virtual number. As the contact device and the operator device communicate through the virtual number, contacts are prevented from ascertaining device and/or number information associated with the operator device

Additionally, multiple virtual numbers may be attached, or associated with, a single operator device to allow an operator to manage a variety of contacts. In turn, embodiments may further comprise receiving a selection of which virtual number to use for communicating with a specified contact device without compromising operator identity.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the embodiments can be readily understood by considering the following detailed description in conjunction with the accompanying drawings.

<figref idref="DRAWINGS">FIG. 1A</figref> is a block diagram illustrating an environment for implementing a multiple attached number “MA number” system according to one example embodiment.

<figref idref="DRAWINGS">FIG. 1B</figref> is a block diagram illustrating an operating environment of an agency service providing MA numbers according to one example embodiment.

<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating a MA module according to one example embodiment.

<figref idref="DRAWINGS">FIG. 3A</figref> is an interaction diagram illustrating a method for provisioning and mapping virtual numbers for operating an operator device with MA numbers according to one example embodiment.

<figref idref="DRAWINGS">FIGS. 3B and 3C</figref> are tables illustrating example embodiments of virtual number mapping for operating and monitoring MA numbers.

<figref idref="DRAWINGS">FIG. 4</figref> is an interaction diagram illustrating a method for connecting an operator device and contact device using a virtual number according to one example embodiment.

<figref idref="DRAWINGS">FIG. 5A</figref> is an interaction diagram illustrating a method for dialing out to a contact device using a MA number, according to one example embodiment.

<figref idref="DRAWINGS">FIG. 5B</figref> is an interaction diagram illustrating a method for dialing out to an operator device using a MA number, according to one example embodiment.

<figref idref="DRAWINGS">FIG. 6</figref> is an interaction diagram illustrating a method for monitoring an operator device according to one example embodiment.

DETAILED DESCRIPTION

The Figures (FIG.) and the following description relate to preferred embodiments by way of illustration only. It should be noted that from the following discussion, alternative embodiments of the structures and methods disclosed herein will be readily recognized as viable alternatives that may be employed without departing from the principles of the embodiments.

Reference will now be made in detail to several embodiments, examples of which are illustrated in the accompanying figures. It is noted that wherever practicable, similar or like reference numbers may be used in the figures and may indicate similar or like functionality. The figures depict embodiments for purposes of illustration only.

Overview

Many operators posses a personal mobile phone or are issued a mobile phone by their agency or department. Oftentimes, operators work multiple cases and the traditional procedure of issuing/carrying additional devices or SIMs is not feasible under the given circumstances or simply cumbersome to the operator or agency. Furthermore, the traditional procedure requires the operator to manually mange the collection of devices, SIMs and their associated identities. In high pressure situations, the operator may inadvertently compromise an identity or lack the appropriately configured device. Accordingly, the agency may coordinate with an agency support service for configuring the operator's mobile phone or landline phone to fulfill the role of multiple telephonic devices. The configuration can take place over-the-air such that a given phone is conveniently converted as needed. Additionally, if the agency desires to provide the capabilities of multiple telephonic devices to additional operators, the agency can specify additional phones for configuration.

Example embodiments described herein relate to implementing a multiple attached “MA” number system over a wired and wireless radio network (e.g., PSTN, Cellular Network and/or WiFi) for network capable devices, such as a mobile phone, or a land-line phone for use with multiple attached numbers “MA numbers”. As mobile phones and similar devices are commonly carried by operators during the course of undercover investigations, mobile phones offer an existing platform for transmitting data wirelessly. Use of such a device with MA numbers allows operators to utilize a single operator device, but maintain numerous, distinct telephonic identities for communicating with various contacts. Operators working from a fixed location with a land-line phone are also provided similar capabilities for using MA numbers.

Additionally, with the popularity of smart phones and feature phones, additional monitoring and safety features may be integrated into the operator's device for enhancing operational viability in the field. For example, the operator device may be configured to collect a wide range of valuable real-time data. Real-time data collected by the operator device may include audio and Global Positioning System (“GPS”) coordinates, etc.

The operator device may subsequently transmit all or a portion of the collected real-time data over existing channels (e.g., a network) back to the agency, agency service or another entity. Embodiments of the agency, agency service and/or other entities within the MA number system receive the collected data for storage and/or live streaming to monitoring devices, operator devices and records. Depending on the embodiment, the monitoring devices are further configured to access and present (e.g., play and/or display) a variety of the real-time and historical data stored on or streamed by the entities on the network. For example, the monitoring devices may access a web interface, API or execute a standalone application for viewing operator device and MA number details and collected information. In some embodiments, the monitoring devices may access portions of the real-time data via a provided monitoring line configured for maintaining the operator's cover. Furthermore, other agencies with appropriate credentials and monitoring devices may similarly access portions of the collected information during inter-agency investigations.

Environment and Implementation of the Operator Device System

<figref idref="DRAWINGS">FIG. 1A</figref> is a block diagram illustrating an environment 100 for implementing a multiple attached number system according to one example embodiment. As shown the environment 100 includes a network 120 connecting an agency support service provider “agency service” 115, an operator device 101 and contact devices 105A through 105E. While only one agency service 115 and one operator device 101 are shown in <figref idref="DRAWINGS">FIG. 1A</figref> for clarity, embodiments can support many operator devices 101 and have multiple agency service providers 115.

Agency service 115 represents a collection of compute devices (e.g., servers) and related storage mediums that are configured for performing various activities such as configuring operator devices 101, exchanging data over the network 120 and storing data in support of one or more agencies (not shown) and operated operator devices 101. For example, the agency service 115 may include one or more modules providing ascribed functionality to an agency via an application programming interface (“API”) or web interface, collectively “the interface”, as described in more detail with reference to <figref idref="DRAWINGS">FIG. 1B</figref>. The agency service 115 may also include infrastructure for providing audio and video communicability (e.g., internally and/or over the network 120) within the monitoring interface using the public switched telephone network (“PSTN”), voice over internet protocol (“VoIP”) and video conferencing services.

The operator devices 101 are oftentimes mobile telephonic devices capable of collecting data and transmitting data (e.g., wirelessly) over the network 120. Some examples of an operator device 101 include a mobile phone, tablet or notebook computer. Example embodiments of the operator device 101 as a mobile phone include feature phones, smart phones or standard mobile phones. Accordingly, a given mobile phone or other device operated as an operator device 101 may not necessarily include or support all of the functionality ascribed herein to the operator device or MA number system due to inherent differences in device capabilities. In some embodiments, other telephonic devices such as land-line phones are used with the MA number system.

In one embodiment, the operator device 101 executes a MA module for automating connections through the network 120 and collecting and transmitting data to entities on the network 120. An example embodiment of a MA module is described in more detail with reference to <figref idref="DRAWINGS">FIG. 2</figref>.

In addition to the operator devices 101, a number of monitoring devices (not shown) may connect to entities on the network 120 to obtain or present data associated with one or more of the operator devices. Depending on the embodiment, a monitoring device is a network 120 capable device that can be operated within an agency or externally in the field. As referred to herein, a monitoring device is a mobile or stationary device capable of connectivity (e.g., wireless or wired) to a network 120 such as an agency network, the internet, PSTN and/or cellular network. Some examples of a monitoring device include a mobile phone, land-line phone, tablet and notebook or desktop computer.

Example embodiments of the monitoring device as a mobile phone can include feature phones, smart phones or standard mobile phones. Accordingly, a given mobile phone or other device operated as a monitoring device does not necessarily include or support all of the functionality ascribed herein to the monitoring device or the MA number system due to inherent differences in device capabilities. In one example embodiment, the monitoring device executes a monitoring module for interfacing with entities on the network 120 to manage operator devices 101 and view collected data.

Also shown are a number of contact devices 105 associated with contacts the operator desires to communicate with using a desired identity. Embodiments of the various contact devices 105 include any network 120 capable device that may send or receive information associated with a transmitting number on the network 120 (however, in some instances, the contact device 105 may use a virtual number itself, or other means, to do so). Accordingly, as referred to herein, a contact device 105 is a mobile or stationary device capable of connectivity (e.g., wireless or wired) to the network 120 for sending or receiving information over the internet, PSTN and/or cellular network. Some examples of a contact device 105 include a mobile phone, land-line phone, tablet and notebook or desktop computer.

<figref idref="DRAWINGS">FIG. 1A</figref> also illustrates a number of virtual numbers 135A through 135D configured for use on the network 120. In one embodiment, the agency service 115 provisions and configures the virtual numbers 135 and handles number information to establish identities for the virtual numbers on the network 120. Additionally, the agency service 115 receives connection information 137 describing operator devices 101 and contact devices 105 requesting to communicate with handled virtual numbers 135. For example, an operator device 101 or contact device 105 may request (and attempt) to communicate with a virtual number (e.g., 135A) by way of a connection request or otherwise transmitting data to the virtual number. Common example communication requests include placing a call to and/or messaging the virtual number from a given device. Based on the device information and configuration of the virtual number, the agency service 115 identifies devices requesting to communicate with a virtual number as either the operator device 101 associated with the virtual number or a contact device 105 (and, in some cases, a monitoring device). For example, the agency service 115 may maintain a mapping table storing transmitting numbers and authentication information for a given operator device 101 and attached virtual numbers 135 for identifying the operator device based on the connection information 127.

After identifying the operator device 101, the agency service 115 enables the operator device 101 to specify a given contact 105A the operator would like to communicate with and, in turn, enables the operator device 101 to communicate with the contact device 105A through (e.g., establishing a connection with or transmitting data from) the virtual number. For example, the operator device 101 specifies device information, such as a transmitting number, for the contact device 105A. The agency service 115 receives the device information for the contact device 105A and transmits instructions that cause the contact device to receive a call from virtual number 135A. If the contact device 105A answers, the parties are connected. In another example, the operator device 101 may transmit data such as an SMS message to the virtual number 135A and specify a contact device 105A for receiving the SMS message from the virtual number 135A. In other words, the agency service 115 transmits instructions (e.g., to a provider) to dial out to the contact device 105A from the virtual number 135A to connect the operator device 101 with the contact device 105 or to send an SMS message from the virtual number to transmit data received from the operator device 101 to intended the contact. As the agency service 115 connects the operator device 101 with entities on the network 120 through the virtual number, the virtual numbers 135 prevent other entities, such as contacts 105, from viewing device and/or number information associated with the operator device.

When the contact device 105A requests to communicate with the virtual number 135A, the agency service 115 determines the operator device (e.g., operator device 101) associated with the virtual number 135A. In turn, the agency service 115 enables the operator device 101 to receive communications from the contact device 105A using the virtual number 135A. For example, the agency service 115 may transmit instructions for connecting the contact device 105 with the operator device 101 (e.g., by dialing out to the operator device 101, optionally from the virtual number) or transmitting data such as SMS messages received at the virtual number from the contact device to the operator device from the virtual number or directly from the agency service 115. As the contact devices 105 send and receive communications to/from the operator device 101 through the virtual number, contacts are typically unable to ascertain device and/or number information associated with the operator device.

The operator device 105, on the other hand, may receive the connection information 137 from the agency service 115 or other entity about contact devices 105 dialing a virtual number 135 and the number identity of the dialed virtual number. Accordingly, the operator may make an informed decision about the caller and the identity expected from the operator. The agency service 115 may further enable the operator or agency to configure multiple virtual numbers to attach to, or associated with, a single operator device 101 for managing a variety of contacts 105. In turn, the operator may use the single operator device 101 to select which virtual number (e.g., 135A) to use for connecting to a specified contact device 105A over the network 120 without compromising operator identity.

The network 120 represents the communication pathway between agencies, agency service 115, the operator devices 101, contact devices 105, monitoring devices and other entities (not shown). In one embodiment, the network 120 includes standard communications technologies and/or protocols and can include the Internet and PSTN. Oftentimes, these communications technologies and/or protocols carry both PSTN and Internet related data. Thus, the network 120 can include links using technologies such as Ethernet, 802.11, worldwide interoperability for microwave access (WiMAX), 2G/3G/4G mobile communications protocols, worldwide interoperability for PSTN communications, digital subscriber line (DSL), asynchronous transfer mode (ATM), InfiniBand, PCI Express Advanced Switching, etc. Similarly, the networking protocols used on the network 120 can include multiprotocol label switching (MPLS), the transmission control protocol/Internet protocol (TCP/IP), the User Datagram Protocol (UDP), the hypertext transport protocol (HTTP), the simple mail transfer protocol (SMTP), the file transfer protocol (FTP), etc. The data exchanged over the network 120 can be represented using technologies and/or formats including analog audio (e.g., for last mile PSTN communications), digital audio and video (e.g., as a file or streaming with Real Time Streaming Protocol), the hypertext markup language (HTML), the extensible markup language (XML), JavaScript, VBScript, FLASH, the portable document format (PDF), etc. In addition, all or some of the data exchanged over the network 120 can be encrypted using conventional encryption technologies such as secure sockets layer (SSL), transport layer security (TLS), virtual private networks (VPNs), Internet Protocol security (IPsec), etc. In another embodiment, the entities on the network 120 can use custom and/or dedicated data communications technologies instead of, or in addition to, the ones described above. For example, some government agencies and the military may operate networks auxiliary to the internet and PSTN.

As used herein, the term “module” refers to computer program instructions and/or other logic used to provide the specified functionality. Thus, a module can be implemented in hardware, firmware, and/or software. In one embodiment, program modules formed of executable computer program instructions are stored on a non-transitory 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)” each comprise the breadth of messaging services and related technologies or standards used for communicating and transmitting data over the network 120. These technologies and services include SMS messages, multimedia messaging service “MMS” messages, proprietary messaging service messages such as BLACKBERRY messages “BBM” and the like.

<figref idref="DRAWINGS">FIG. 1B</figref> is a block diagram illustrating an operating environment of an agency service 115 providing MA numbers according to one example embodiment. As shown, the operating environment includes an agency 110, monitoring devices 107, operator devices 101, contacts 105 and a network 120 with components such as the internet 123, telephony 125 and provider 127. The network 120 may also include GPS satellites (not shown) that relay position data to operator devices 101 and other devices.

Agency 110 represents a collection of servers, desktop, notebook or tablet computers, mobile telephones and related storage mediums used by respective agency personnel for executing applications or modules to communicate with and receive data from the agency service 115 (e.g., via the interface 145) and other entities on the network 120. For example, agency 110 devices may execute a web browser to access a web interface or execute a mobile or desktop application for communicating with an API provided by the agency service 115. An agency 110 may also include telephonic and video infrastructure enabling audio and video communicability (e.g., internally and/or over the network 120) using the public switched telephone network (“PTSN”), voice over internet protocol (“VoIP”) and video conferencing services for monitoring or specifying configurations for operator devices 101.

The telephony network 125 may include servers, switches and other hardware and software for implementing, among other protocols and technologies, worldwide interoperability for PSTN communications including land-lines and 2G/3G/4G wireless protocols. The telephony network 125 also provides mobile devices with the capability to transmit and receive data over the internet 123. The telephony network 125 is managed by one or more communication service providers “CSPs” (not shown) that own telephone numbers for use on the PSTN and the CSPs own network (e.g., a wireless network that communicates with the PSTN).

The provider 127 may include servers, switches and other hardware and software for communicating over the network 120 with CSPs and other entities. The provider 127 buys or leases numbers for use on the telephony network 125 from multiple CSPs. The provider 127, in turn, manages numbers provisioned for use by the agency service 115 and the telephony traffic associated with the numbers. In one embodiment, the provider 127 allows the agency service 115 to provision one or more of the numbers as virtual numbers over the network 120.

Typically, a number used on the telephony 125 network directs to a given mobile device, VoIP device or land-line device having an associated number identity characterized by automatic number identification “ANI” information, or caller identification. Virtual numbers, while still operable with the PSTN and CSP networks, are associated with the provider 127 who handles telephony traffic for the number. Because a virtual number does not direct to an end user device, the provider 127 may establish connections with devices dialing the virtual number, record call information such as call audio and caller history (e.g., on a computer readable medium) and stream/provide call information for download (e.g., over the network 120).

The provider 127 may also pass/bridge audio (bidirectional or unidirectional) in real-time between two or more telephonic devices establishing connections with the same or different virtual numbers (or connected by the provider 127 via a virtual number). Additionally, as the virtual numbers are handled by the provider 127, the agency service 115 may modify ANI information and caller identification associated with the virtual number.

In addition to provisioning virtual numbers for the agency service 115, the provider 127 communicates notifications and data associated with the virtual numbers to the agency service 115 or other entity such as the agency 110. For example, the provider 127 may notify the agency service 115 (and optionally an operator device 101 or monitoring device 107) of an incoming caller or message to the virtual number and receive instructions from the agency service 115 to connect the caller to the virtual number (or another device) or redirect the message. The provider 127 may also receive instructions to stop/start recordings of calls placed to the virtual number and interface with a transcription service to transcribe call audio. In turn, the provider 127 can transmit the recordings and transcripts to the agency service 115 or other entity on the network 120.

Additionally, the provider 127 may enable or disable inbound and/or outbound audio for different parties connected to a virtual number and recordings thereof responsive to instructions received (e.g., via an API) from the agency service 115. The provider 127 can receive instructions for managing a virtual number as part of the provisioning process, prior to an incoming call or in real-time from the agency service 115 when connecting an incoming caller to the virtual number. In some embodiments, the provider 127 communicates directly with the agency 110, operating device 101 and/or monitoring device 107 to provision virtual numbers, transmit notifications and data or receive instructions. Additionally, the provider 127 itself may function as a CSP and vice versa.

The agency service 115 receives requests for provisioning and mapping virtual number from the agency 110, operator device 101, or monitoring device 107. The requests can include number information for provisioning virtual numbers such as an area code (e.g., 555), country code (e.g., +44) and/or associated CSP. In turn, the agency service 115 queries the provider 127 for available virtual numbers matching the request and returns the matching virtual numbers to the requesting entity. The agency service 115 subsequently receives a selection of virtual numbers from the requesting entity and claims the virtual numbers from the provider 127. The agency service 115 may optionally allow the entity to specify number information such as ANI and/or caller identification associated with the virtual number to spoof the number's identity on the network 120. The agency service 115, in turn, transmits instructions to the provider 127 for modifying the number identity. The agency service 115 may optionally verify the spoofed number identity. When a virtual number is no longer needed by the agency 110A, the agency service 115 obtains any audio recordings or call logs associated with the virtual number and releases the number back to the provider 127.

The requests can also include mapping information for configuring claimed virtual number function in a mapping table. Depending on the desired configuration, the mapping information may include the transmitting number of an operator device 101 and/or and monitoring device 107, virtual number for association with the device and/or desired function of the virtual number (e.g., MA number or local number). One example mapping request may specify a claimed virtual number for use as a virtual multiple attached number (MA number) that operator devices 101 connect to in order to transmit collected data (e.g., audio) over the telephony 125 network from the MA number's identity (e.g., to contact devices 105). In one embodiment, the request includes the transmitting number of the operator device 101 and a given claimed virtual number for configuration as the MA number. In response to the request, the agency service 115 associates the transmitting number of the operator device 101 with the MA number and stores the association in a mapping table.

Another example mapping request may specify a claimed virtual number for use as a virtual local number (local number) that monitoring devices 107 connect to in order to monitor a MA number (e.g., listen to audio transmitted between operator device 101 and a contact device 105). The operator device 101 may also utilize the local number to avoid long distances charges for MA numbers in different countries or area codes. In one embodiment, the request includes a given claimed virtual number (e.g., the local number) and the MA number. In response to the request, the agency service 115 associates the MA number with the local number and stores the association in a mapping table.

In some embodiments, a mapping request may optionally include the transmitting number of a monitoring device 107 which the agency service 115 associates with a MA number or local number to identify the monitoring device. As multiple monitoring devices 107A, 107B may monitor call audio, the agency service 115 may store multiple transmitting numbers of monitoring devices in association with a MA number or local number in a mapping table.

In practice, agency service 115 consults the mapping table to automatically identify a device connecting to a virtual number (e.g., the MA number) as the operator device 101, monitoring device 107 or contact device 105 based on the device's transmitting number. Thus, for example, an operator of an operator device 101 may simply dial an MA number mapped to the transmitting number of his phone to place a call using a given MA number.

Personnel with a monitoring device 107 that desire to monitor the operator device 101 with a mobile or land-line phone at the agency 110A or in the field can dial the local number associated with the MA number (and, in some embodiments, the MA number itself). However, in one embodiment (e.g., connecting to a local number), as the agency service 115 does not identify the transmitting number of the device as that of the operator device 101, personnel devices are appropriately identified as monitoring devices 107. In some embodiments (e.g., connecting to a local number and/or MA number), the agency service 115 identifies connecting monitoring device 107 based on a mapping of monitoring devices' 107 transmitting numbers to the receiving number. Alternatively, the agency service 115 identifies the monitoring device 107 or operator device 101 responsive to personal identification number or code “PIN” entered when connecting to a virtual number.

Embodiments of the agency service 115 use the mapping of the operator device 101 to MA numbers for instructing the provider 127 to automatically dial (e.g., from an MA number or via call forwarding) the operator device when calls are received from contact devices 105 on an MA number mapped to the operator device for connecting the parties. Additionally, embodiments of the agency service 115 use the mapping of the operator device 101 to MA numbers for identifying when the operator device desires to use an MA number and instructing the provider 127 to dial (e.g., from an MA number) a contact device 105 specified by the operator and connect the parties. The agency service 115 may also notify operating devices 101 with caller and MA number details through the interface 145, via SMS message or email. Embodiments of the agency service 115 may also use mapping information to direct text messages received on an MA number to an operating device 101 and send text messages (e.g., from the operating device) from the MA number to entities on the network 120 such as contact devices 105.

Additionally, embodiments of the agency service 115 can use the mapping of monitoring devices 107 to MA numbers for instructing the provider 127 to automatically dial (e.g., from a specified local number) or otherwise notify (e.g., a SMS message) monitoring devices when calls are placed or received using a given MA number. The agency service 115 may also notify monitoring devices 107 through the interface 145 or via email.

To prohibit unauthorized access to MA numbers (and local numbers), the agency service 115 may allow personnel and operators to specify key-ins when provisioning and/or mapping virtual numbers. The agency service 115 stores the key-ins in the mapping table or other suitable database structure to identify and authenticate callers attempting connections to the virtual numbers responsive to correct key-ins. Depending on the embodiment, the agency 110, agency service 115 or provider 127 may store the mapping table and/or key-ins for device identification and authentication.

In some embodiments, the agency service 115 provides a MA module 141 to the operator device 101. The MA module 141 interfaces with the native dialer of the operator device 101 to automate the connection process to a given contact device 105. Additionally, the MA module 141 may interface with operator device 101 software and/or hardware to utilize features such as a GPS device to collect real-time position data. The MA module 141 transmits the collected data over the network 120 back to the agency service 115 or other entity. The agency service 115, in turn, may store the collected data for transmission to one or more monitoring devices 107 and the agency 110. Furthermore, the MA module 141 may be configured with a password or otherwise disguised when executed to prevent users other than the operator from accessing the module altogether and/or particular features. The MA module 141 is described in more detail with reference to <figref idref="DRAWINGS">FIG. 2</figref>.

In some embodiments, the agency service 115 includes an interface 145 for providing data received from operator devices 101 and call audio between operators and contacts to various monitoring devices 107 and/or appliances 150 over the network 120. For example, the interface 145 may provide monitoring devices 107 with data corresponding to the status (e.g., connected or disconnected) of one or more operator devices 101 and the corresponding MA number and contact device information. If the operator device 101 is transmitting real-time data or connected to a contact device 105, the interface 145 can stream data such as audio from the active transmission, GPS coordinates with heading, speed and coordinates of last-reported locations for placement on a map, and the internet protocol address and/or telephone numbers of other personnel monitoring or having access to the operator device or MA number. In some embodiments, the interface 145 syncs collected data prior to transmission or includes tags in the transmitted data for synchronization of playback at the monitoring device 107 or operator device 101. The interface 145 can also stream, or provide for download, previously recorded monitoring sessions.

In some embodiments, the agency service 115 provides a monitoring module 140 to monitoring devices 107 for accessing the interface 145. The monitoring module 140 transmits requests associated with configuring an operator device 101 and receiving real-time and historic data. For example, the monitoring module 140 may provide a user interface or status dashboard with options for provisioning virtual numbers, mapping a transmitting number of an operator device 101 or monitoring device 107 to a given virtual number and assigning key-ins for connecting to the virtual number. In one embodiment, the dashboard provides an option to toggle a recording session on or off with the agency service 115. When the recording session is disabled, the monitoring device 107 still receives real-time data, but the agency service 115, appliance 150 and provider 127 do not store copied of the collected data.

The monitoring module 140 may also display real-time status information for the operator device 101 including current GPS location, tracked GPS location, live audio, mapping table information and other information collected from the operator device, operator device 105, or MA number and streamed by the interface 145. Similarly, the monitoring module 140 may be used to access and playback historic activity associated with a given virtual number or operator device 101. For example, the monitoring module 140 may download files for playback or steam them. In addition to interfacing with the agency service 115, the monitoring module 140 may interface with an appliance 150 that stores (or backs up) collected data within the agency 110. Additionally, the monitoring module 140 may include functionality of the MA module 141 and vice versa.

In one embodiment, the agency 110 includes an appliance 150 for storing data collected by operator devices 101 and call audio using MA numbers. The appliance 150 may utilize the monitoring interface 145 provided by the agency service 115 for updating stored data or receive data directly from operator devices 101. Additionally, the appliance 150 may receive audio recorded on a virtual number and associated transcripts from the provider 127 or agency service 115. One example embodiment of the appliance 150 also includes its own interface (not shown) that enables monitoring devices 107 and operator device to access real-time and historic data stored on the appliance for an MA number. Interfaces provided by the agency service 115 or appliance 150 may also be accessible via a web browser for streaming or downloading data and include the same or similar options.

Additionally, the appliance 150 and agency service 115 may communicate to intermittently update collected data and records at defined intervals or in response to notifications to download data. During the intervals or notification periods, the agency service 115 may process the data and perform any necessary actions as desired by operator devices 101 or monitoring device 107 until the data is transferred to the appliance 150. In some embodiments, the agency service 115 maintains a persistent connection with the appliance 150 to facilitate transfer of real-time data collected by operator devices 101 operated in the field.

In one embodiment, the agency service 115 insures that it, and the provider 127, do not possess data collected by operator devices 101 or from a virtual number beyond the time needed to facilitate transfer. However, in mission critical situations, operators and other agency 110 personnel cannot rely only on the availability of the appliance 150 for storing and maintaining collected data. Consequently, if the appliance 150 is unable to take possession of the collected data or go offline during transfer, the agency service 115 and/or the provider 127 may maintain possession of the collected data until the appliance 150 is functioning. Furthermore, the agency service 115 and/or provider 127 may determine whether checksums, hashes or sizes of transferred data match the appliance's 150 version prior to deleting stored data.

In some embodiments, the agency service 115 maintains an appliance instead of, or in addition to, the agency 110. In such cases, the appliance may exist as a dedicated piece of hardware or remote storage. Alternatively, embodiments of the appliance 150 may be implemented in a cloud computing and storage stack available on the network 120.

Operator Device Functionality

<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating a MA module 141 according to one example embodiment. As mentioned above, the MA module 141 may be downloaded from the agency service 115 to the operator device 101 and executed to facilitate communications using MA numbers and collect and transmit data to entities on the network 120. As shown in <figref idref="DRAWINGS">FIG. 2</figref>, the MA module 141 itself includes multiple modules. In the embodiment shown in <figref idref="DRAWINGS">FIG. 2</figref>, the MA module 141 includes a connection module 205, GPS module 210, provisioning module 215, caller ID module 220, case module 225 and SMS module 230. In some embodiments, the functions are distributed among the modules in a different manner than described herein. Other embodiments have additional and/or other modules.

The connection module 205 automates the connection process for dialing out to a given contact. The connection module 205 receives input from the operator including an MA number associated with the operator device 101. In some embodiments, the connection module 205 further receives input indicating a local number associated with the operator device 101 or the MA number. Once a connection with the MA number is established, the connection module 205 transmits the number for a contact device 105 the operator desires to call over the network 120. The connection module 205 may allow the operator to enter the number of the contact device 105 prior to, or after establishing the connection with the MA number. Additionally, the connection module 205 may interface with the agency service 115 to receive information about MA numbers associated with a given local number or the transmitting number of the operator device 105. The connection module 205 may then present an interface to the operator indicating one or more available MA numbers with their number information for selection.

In one embodiment, the connection module 205 detects whether incoming calls were initially placed to a MA number. The connection module 205 subsequently determines MA number and/or contact device 105 information for display to the operator. In one embodiment, the connection module 205 accesses a locally or remotely stored address book to retrieve an address book entry associated with the MA number and/or contact device 105. Alternatively, the connection module 205 may receive and display notifications from the agency service 1115 or provider 127 about incoming calls. Based on the notification or address book information, the operator may review the appropriate identity expected by the contact and/or the contact.

Depending on the operator device's 101 capabilities, the communication module 205 may enable placement/receipt of multiple outgoing and incoming calls to virtual and non-virtual numbers within the native dialer application or similar.

The GPS module 210 communicates with a native GPS receiver on the operator device 101 to receive GPS location data. The GPS module 210 may also communicate with other radio receivers and directional mechanisms (e.g., compass or accelerometers) on the operator device 101 to receive additional location data. The GPS module 210 processes the GPS and radio location data to determine and refine an estimated location measurement for the operator device 101. The location measurement may include, but is not limited to, a latitude, longitude, altitude, heading, speed, associated accuracy measurement and the time and date of recording. The GPS module 210 transmits the determined location measurement over the network 120 the agency service 115 or other entity. In one embodiment, the GPS module 210 streams the location measurement in real-time.

The provisioning module 215 interfaces with the provider 127 or agency services 115 to provision virtual numbers and modify virtual number assignments and function in the field. Alternatively, a web browser on the operator device 101 may be used. For example, the web browser or provisioning module 215 may present the operator with a list of all virtual numbers associated with a given account, transmitting number, or local number. Through the interface, the operator may provision and modify mapping and function of the virtual numbers.

The caller ID module 220 interfaces with the provider 127 or agency services 115 to modify caller ID or other number information associated with provisioned virtual numbers. For example, the caller ID module 220 presents an interface to the operator to specify number information such as location, ownership, carrier and whether or not any of the information should be restricted or blocked when dialing out from a given MA number.

In some embodiments, the case module 225 interfaces with the provider 127, agency services 115 or appliance 150 to retrieve activities associated with a given MA number, local number or transmitting number. For example, the case module 225 presents an interface with MA numbers that the operator may select, for example, to view associated activity and number information. The case module 225 may further provide an interface for the operator to associate contact information or other information (e.g., address book entries) with a given MA number or contact number. The case module 225 may store the address book entries locally and/or remotely with the agency services 115 or appliance 150.

In some embodiments, the MA module 141 includes an SMS module 230 for sending SMS messages with and receiving SMS messages from an MA number. The SMS module 230 may send and receive SMS messages natively (e.g., via the provider 127) and/or send and receive non-native messages (e.g., via the agency services 115) depending on the device capabilities. The SMS module 230 provides an interface to the operator for selecting or otherwise specifying an MA number to use for sending an SMS message and the number of the contact device 105 that should receive the message. The SMS module 230 communicates (e.g., using the SMS itself or via the interface 145) the information for sending the SMS message to the agency service 115 and/or the provider 127. The SMS module 230 may further receive SMS messages sent to a MA number natively or via the interface 145. In one embodiment, the SMS module 230 mimics the look and feel of a native SMS program on the operator device 101.

In some embodiments, the MA module 141 and the modules therein interface and communicate with non-native devices attached to the operator device 101. For example, audio and location data can be determined from accessories coupled (e.g., wired microphone) or wirelessly connected (e.g., Bluetooth headset) to the operator device 101.

Additionally, some or all of the features provided by the MA module 141 may require the operator to enter a specified key-in (e.g., button press combination, password or other personal identification) prior to operation or launch.

Virtual Number Provisioning

<figref idref="DRAWINGS">FIG. 3A</figref> is an interaction diagram illustrating a method for provisioning 300 and mapping virtual numbers for operating an operator device 101 with MA numbers according to one example embodiment. Initially, the agency service 115 receives 310 a request including a calling code for provisioning 300 a virtual number from a monitoring device 107, operator device 101, provided web interface or other entity. The calling code can include an area code and country code where the provisioned virtual number will be operated.

The agency service 115 queries 320 the provider for virtual numbers matching the specified calling code. The provider 127 returns 330 a list of available virtual numbers to the agency service 115 which, in turn, transmits the virtual numbers for display to the requestor. The agency service 115 receives 335 one or more virtual number selections and claims 340 each selected virtual number from the provider 127. The agency service 115 may optionally include corresponding ANI and caller identification information for a virtual number that may be edited on the requesting device 101, 107 or in the web interface. The agency service 115 subsequently stores the modified virtual number information and instructs the provider 127 to update the associated virtual number information.

With one or more virtual numbers claimed, the agency service 115 can receive mapping requests for the virtual numbers and, in turn, map 350 the virtual numbers responsive to information in the mapping request. For example, the requestor may be prompted to enter the transmitting number of an operator device 101 for association with a virtual number to be used as a MA number. The agency service 115 stores the transmitting number of the operator device 101 and the MA number in a mapping table (e.g., at the agency service 115 or on the appliance 150). The requestor may modify the mapping at any time, without any interruption of service at the receiving number.

Oftentimes, MA numbers have a different country code (or area code) than monitoring devices 107 or the operator device 101 connecting to an MA number to monitor or place/receive calls on the MA number. In some cases, the requestor knows the country code or area code where the monitoring devices 107 and/or operator device 101 are located. Accordingly, to avoid costly charges for the agency 110A, the agency service 115 enables the requestor to provision additional virtual numbers with the known country codes and area codes for use as local numbers. The agency service 115 may then receive mapping requests for the local numbers (e.g., to map the transmitting number of the operator device 101) and, in turn map local numbers to specified MA numbers.

When operator device 101 subsequently dials a local number, the agency service 115 identifies the associated MA number from the mapping table. The agency service 115 may further identify the transmitting number or operator PIN associated with the MA/local number and authenticate the operator device 101 (e.g., based on the transmitting number or PIN). In turn, the agency service 115 instructs the provider 127 to connect the operator device 101 to the MA number or pass audio from the MA number to the local number and connect the operator device to the local number.

When a monitoring device 107 dials a local number, the agency service 115 identifies associated MA numbers from the mapping table. The agency service 115 may further identify a monitoring number or monitor pin associated the MA/local number and authenticate the monitoring device 107. In turn, the agency service 115 instructs the 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. Additionally, as the monitoring device 107 should not tip off the contact or otherwise interfere with call status (e.g., ringing, active, etc.), connection/disconnection of the monitoring device 107 (e.g., to/from a virtual number or other device or entity) may be delayed or otherwise modified as not to affect call status or tip off the contact.

In some embodiments, local numbers may be tied to the transmitting number of a operator device 101 for automatic mapping to MA numbers. For example, an operator using the same operator device 101 for multiple investigations in different counties may utilize a different MA number for each investigation (e.g., to keep distinct records or maintain a specific identity). Rather than requiring the operator or personnel monitoring the operator to assign local numbers (or frequently modify mapping) to each MA number on an individual basis, a local number may be tied to the operator device 101. When the operator device 101 is mapped or used with a MA number, the agency service 115 maps the tied 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. As multiple MA numbers may be associated with a single local number, operating devices 101 or monitoring device 107 dialing the local number may be presented with a list of the mapped MA numbers available for placing a call or monitoring. A requestor may re-specify the mapping configuration as needed to change or swap claimed virtual numbers and transmitting numbers between MA numbers and local numbers.

Example embodiments of monitoring device 107 mapping to MA numbers and/or local numbers can be performed in the same or similar fashion as operator device 101 mappings.

<figref idref="DRAWINGS">FIG. 3B</figref> is a table illustrating an example embodiment of virtual number mapping 350 for operating an operator device 101 with MA numbers. As shown, mapping table 360A includes a number of MA numbers 363A mapped to a corresponding transmitting number 361A (e.g., of operator device 101).

When the agency service 115 receives connection requests to MA numbers 363A from the network 120, the agency service identifies the connecting device as the operator device 101 based on the transmitting number 361A stored in the mapping table 360A. In turn, the agency service 115 or provider 127 receives a contact number from the operator device 101 and dials the corresponding contact 105 from the MA number 363A. If the connecting device's number does not match the transmitting number 361A, the agency service 115 identifies the device as a contact device 105 and dials or instructs the provider 127 to dial the specified transmitting number for the operating device 101.

Prior to permitting the operator device 101 to place a call to or receive a call from the MA number or local number, the agency service 115 may wait or instruct the provider 127 to wait for key-in of a specified password. For example, in some instances, the provider 127, telephony 125/PSTN or agency service may fail to correctly identify or pass a transmitting number of a device or a virtual number for forging a connection. If an improper password or no password is received for a local number, the device is disconnected. For a MA number, as contacts 105 dial the number, if an improper password or no password is received (e.g., within a brief time frame of placing the call) the operator device 105 is dialed. In one embodiment, the operator must enter the password or key-in enter a password (e.g., hitting * or # prior to entering the password) within a given time period (e.g., 2-5 seconds) without being prompted to mitigate suspicion when the line is dialed by another party.

Similar precautions may be implemented to authenticate monitoring devices 107 that dial the local number to monitor the call. In some embodiments, the mapping table 360A further includes mappings of monitoring device 107 transmitting numbers to explicitly identify monitoring devices in addition to operating devices 101.

<figref idref="DRAWINGS">FIG. 3C</figref> is a table illustrating an example embodiment of virtual number mapping 350 for operating an operator device 101 with MA numbers. As shown, mapping table 360B includes a number of MA numbers 363B mapped to a corresponding transmitting number 361B (e.g., of operating device 101). Additionally shown are a number of local numbers 365 mapped to the MA numbers 363B.

When the agency service 115 receives connection requests to local numbers 365 from the network 120, the agency service identifies the connecting device as a monitoring device 107 or operator device 101 (e.g., based on mapped transmitting numbers or monitor/operator PIN) and identifies the associated MA numbers 363B from the mapping table 360B. The agency service 115, in turn, instructs the provider 127 to connect the device 101, 107 with a specified MA number 363B (e.g., directly, or through the local number 365).

If the agency service 115 identities the device as the operator device 101, the operator may further enter the number of the contact they desire to dial from the MA number. The agency service 115, in turn, instructs the provider 127 to dial out to the specified contact number from the MA number.

Prior to connecting the monitoring device 107 or operator device 101, key-in of a specified password may be required. In some embodiments, the mapping table 360A further includes mappings of monitoring device 107 transmitting numbers to explicitly identify monitoring devices in addition to operator device 105.

<figref idref="DRAWINGS">FIG. 4</figref> is an interaction diagram illustrating a method for connecting 400 an operator device 101 and contact 105 using a virtual number according to one example embodiment. <figref idref="DRAWINGS">FIG. 4</figref> additionally illustrates a method for connecting 400 a monitoring device to virtual number according to one example embodiment. Once the agency service 115 provisions 300 a virtual number with the provider 127, an operator device 105, monitoring device 107 or contact 105 may connect 400 to the virtual number. However, each entity may be treated differently as explained below.

For any device 101, 105 or 107 dialing 410 the virtual number, the provider 127 receives the connection request via the telephony network 125 and identifies 420 the dialed number as a virtual number provisioned 300 by agency service 115. Accordingly, in embodiments where the agency service 115 stores the mapping table, the provider 127 passes the transmitting number of the device attempting to connect to the virtual number and the virtual number to the agency service 115.

The agency service 115, in turn, identifies 430 the device attempting to connect to the virtual number as either an operator device 101, monitoring device 107 or contact 105 based on the mapping table. The agency service 115, in turn, instructs the provider 127 to connect (or disconnect) 440 the identified device and provide options or perform operations according to the device's classification.

Operator Device

In the case of the operator device 101 dialing an MA number, the agency service 115 determines that the transmitting number stored in the mapping table for the dialed MA number matches the number of the device attempting to connect to the MA number. The agency service 115 then instructs the provider 127 to connect 440 the device to the MA number as the operator device 101.

Alternatively, if the agency service 115 determines that the operator device 101 is attempting to connect to a local number, the agency service determines that the transmitting number stored in the mapping table for the dialed local number (and/or associated MA numbers) matches the number of the device. The agency service 115 then instructs the provider 127 to connect 440 the device to the local number as the operator device 101. If only one MA number exists in the mapping table for the local number, the agency service 115 may automatically instruct the provider to connect the operator device 101 with the MA number (e.g., directly or via the local number). Alternatively, if there are multiple MA numbers assigned to the local number, a menu with details about the MA numbers may be provided for 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” where “John Doe” and “555-111-5555” may be number information for a corresponding MA number and restricted or blocked indicates that an MA number will not display number information when used.

Once the operator device 101 connects to the desired MA number (e.g., via selection or directly), the operator may enter the number of the contact device 105 (e.g., transmitting number of the contact's device) that the operator would like to dial from the MA number. The provider 127, in turn, dials out 500 to the contact number from the MA number (displaying MA number information) and connects the parties. Example embodiments of dialing out to a contact device 105 are explained in more detail with reference to <figref idref="DRAWINGS">FIG. 5A</figref>.

Monitoring Device

In the case of a monitoring device 107 dialing an MA number, the agency service 115 may determine that a transmitting number for a monitoring device stored in the mapping table for the dialed MA number matches the number of the device. The agency service 115 then instructs the provider 127 to connect 440 the device to the MA number as a monitoring device 107 and disable (e.g., mute) audio received from the monitoring device 107.

Alternatively, if the agency service 115 determines that the device is attempting to connect to a local virtual number, the agency service may determine that the number of the device does not match the transmitting number of the operator device stored in the mapping table. For example, the agency service 115 may determine the operator device transmitting stored in the mapping table for the dialed local number (and/or associated MA numbers) and identify devices connecting to the local number that do not match the operator device's transmitting number as monitoring devices. In other embodiments, the agency service 115 may identify the monitoring device 107 based on matching a monitoring device transmitting number stored in the mapping table for the local number or MA numbers with that of the connecting device. The agency service 115 then instructs the provider 127 to connect 440 the device to the local number as the monitoring device 107. If only one MA number exists for the local number, the agency service 115 may automatically instruct the provider 127 to connect the monitoring device to the MA number as described above (e.g., with audio disabled) or, alternatively, pass audio from the MA number (e.g., call audio between the operator and contact) to the local number. Audio from the local number to the MA number may be disabled such that audio received from monitoring devices need not be disabled on the local number. Alternatively, if there are multiple MA numbers assigned to the local number, a menu with details about the MA numbers may be provided for the operator to select a given MA number. The provider 127 and/or the agency service 115 may additionally notify personnel using the monitoring device 107 which MA numbers are active.

In some embodiments, the monitoring devices 107 may communicate with other devices monitoring a given MA number through a local number (e.g., like a conference call) although no audio is transmitted to the operator device. Additionally, the provider 127 or agency service 115 may provide the monitoring devices 107 with key combinations (e.g., *1, 2, etc.) to mute other monitoring devices 107, audio on the MA number or their own device.

Contact Device

In one embodiment, the agency service 115 identifies 430 devices with numbers that do not match a transmitting number stored in the mapping table for a MA number as contact devices 105. The agency service 115 identifies the transmitting numbers associated with the MA number and instructs the provider 127 to connect 440 the contact device 105 to the operator device 101 (e.g., by dialing out 500 to the operator device 101 directly, or through the MA number). Example embodiments of dialing out 500 to the transmitting number of an operator device 101 are explained in greater detail with reference to <figref idref="DRAWINGS">FIG. 5B</figref>.

Additional Considerations

In some embodiments, the PSTN or provider 127 fails to pass the transmitting number associated with an operator device 101 (or monitoring device 107) to the provider or agency service 115. For example, the provider 127 or agency service 115 may receive a number other than the operator device's 101 and incorrectly identify the operator device. Some example PSTN and provider 127 failures are all zeroes numbers (+00 000-000-0000), restricted numbers (737-874-2833) or simply an incorrect number for the operator device 101. In any instance, the agency service 115 may be unable to identify the operator device 101 by the received transmitting number.

The agency service 115 may recognize that some numbers are passed incorrectly (e.g., a restricted number or zeroes number).

In response (e.g., for calls to a local number), the agency service 115 may play a prompt or instruct the provider 127 to play a prompt such as “press 1 for a operator device or press 2 for a monitoring device.” The prompt can also be ambiguous (e.g., please enter the extension of the party you are trying to reach or similar). Operators or personnel may then key-in as using a operator device 101 or monitoring device 107.

Alternatively, as the key-ins of the operator device 101 and monitoring device 107 typically differ, the agency service 115 may instruct the provider 127 to simply play a generic tone or number not available recording to notify users that they need to key-in. The matching of a key-in with stored authentication information 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 the local number to key-in for identification. For example, an agency 110A may want to enable the option to use unmapped devices as operator devices 101 on a specified MA number.

While prompts are effective for identification on a local number (e.g., as only operators and personnel typically have knowledge of the number and it may further require key-in of a PIN), these methods are ineffective for number pass failures to MA numbers as contacts 105, typically, must be tricked into believing they are making a legitimate, confidential call when they (as opposed to the operator device 101 or monitoring device 107) dial the MA number. Accordingly, PSTN or provider 127 failures to pass the transmitting number associated with a device making a call to an MA number may be handled differently.

In one embodiment, the agency service 115 may instruct the provider to begin the dial out 500 process as if the unidentified device were a contact device 105. Once the dial out 500 begins, the operator or personnel will realize that their device was not recognized (e.g., because no menu was presented or prompt was played and the provider 127 is dialing out). The contact, on the other hand, would assume operation as normal. In order to capitalize on this difference, the agency service 115 may instruct the provider 127 to capture a key-in during the dialing process for identifying the requesting device as a monitoring device 107 or operator device 101. The requesting device is then identified and connected according to the provided key-in.

Operating an Operator Device

<figref idref="DRAWINGS">FIG. 5A</figref> is an interaction diagram illustrating a method for dialing out 500A to a contact device 105 using a MA number, according to one example embodiment. Once the connection 400 between the operator device 101 and the MA number is established, the operator may enter the transmitting number of a contact device 105. Alternatively, the number of the contact device 105 may have been previous entered in an application. In either instance, the operator device 101 transmits 510 the dial out number to the provider 127. The provider 127, in turn, dials out 515 to the contact device 105 from the MA number. Thus, when the contact device 105 receives the connection request, the call appears to be coming from the MA number. Accordingly, the contact device 105 will display number information (if any, e.g., for blocked or restricted number) for the MA number rather than the operator device 105. If the contact device 105 picks up, the provider 127 establishes 520 a connection between the operator device 105 and the contact device 105 (e.g., through the MA number or local number, or directly as the contact device will not receive additional number or device information from the operator device). The operator device 101 and/or provider 127 may optionally transmit the number of the contact device 105 to the agency service 115 for records keeping or to open a new record.

Once the connection 520 between the operator device 101 and the contact device 105 is established, the provider 127 begin recording audio on the line. The operator device 101 collects audio data using a microphone coupled to the operator device. The operator device 101, in turn, transmits 525 the collected audio data to the provider 127 and contact device 105 by way of the connection through the MA number. The contact device 105 communicates with the operator device 101 in a similar fashion. The provider 127 may additionally enable monitoring devices 107 to connect to the MA number or local number to monitor the call and/or transmit the audio data received from the operator device 101 and the contact device 105 to the agency service 115 or appliance 150 over the network 120.

Furthermore, the operator device 101 may also collect location data from GPS receivers and other direction mechanisms coupled to the operator device. The operator device 101 may determine a location measurement including the position of the operator device, direction and speed of the operator device and associated accuracy of the measurement. The operator device 101 transmits 525 the location measurement to the agency service 115. In some embodiments, the operator device 101 determines and transmits 525 the location measurements in real-time to the agency service 115.

The provider 127 and/or the agency service 115 may update 530 the appliance 150 with the received audio data. The agency service 115 or provider 127 may also update 530 the appliance with any other data received from the provider 127 and/or operator device 101.

<figref idref="DRAWINGS">FIG. 5B</figref> is an interaction diagram illustrating a method for dialing out 500B to an operator device 101 using a MA number, according to one example embodiment. As described above, the contact device 105 initiates 400 a connection to a MA number and the agency service 115 instructs the provider 127 to connect the contact device 105 to the operator device 101. Accordingly, the agency service 115 transmits 510 the transmitting number of the operator device 101 as stored in the mapping table for the MA number to the provider 127. Depending on the embodiment, the agency service 115 and/or provider 127 may be configured to coordinate connection of the contact device 105 with the MA number and subsequent dialing the operator device 101 or dialing the operator device 101 directly.

Connection through MA Number

The agency service 115 may instruct the provider 127 to connect the contact device 105 to the MA number but play the ring tone (e.g., a specified mp3 file) of the MA number on the line after establishing the connection. In effect, the contact device 105 is connected to the MA number but does not know a connection has already been established because the ring tone is still playing. Temporally proximate to establishing the connection between the contact device 105 and the MA number, the provider 127 dials out 515 to the provided transmitting number of the operator device 101. In response to the operator device 101 answering the call, the provider 127 stops the ring tone played for the contact device 105 and establishes the connection 520 between the parties. If the operator device 101 does not answer, the provider 127 may direct the contact device 105 to a voice mail box associated with the MA number or disconnect the contact device 105.

Direct Connection

The agency service 115 may instruct the provider 127 to connect the contact device 105 to the operator device 101 by forwarding the call to the transmitting number of the operator device 101 to dial out 515. Typically, this process would result in the contact hearing the ring tone of the operator device 101. As ring tones can differ between countries, and for a host of other reasons, the contact may notice that the ring tone being played is different than the ring tone expected for the MA number. Accordingly, the agency service 115 may instruct the provider 127 the play the ring tone of the MA number rather than the operator device 101 being dialed. In some embodiments, the provider 127 plays an mp3 file of the MA number ring tone for the contact device 105. Alternatively, the provider 127 may dial the MA number itself and pass the ring tone audio to the contact device 105. In either instance, the provider 127 suppresses the ring tone of the operator device 101, by disabling audio for example, until the operator device 101 answers the call. Once the operator device 101 answers, the provider 127 establishes the connection 520 between the parties and may pass audio on the line to a local number or MA number for monitoring and/or recording. If the operator device 101 does not answer, the provider may direct the contact device to a voice mail box associated with the MA number or disconnect the contact device.

In some embodiments, the provider 127 and/or agency service 115 may provide notification information 517 to the operator device 101. The notification information 517 includes contact device 105 and/or MA number information describing the caller and identity expected from the operator. In some embodiments, notification information 517 may be injected into, or included with, caller identification information provided for a typical call. In other embodiments, notification information 517 may be provided in a SMS message or otherwise transmitted to the operator device 101 for display using an MA module 141. In one embodiment, rather than immediately establishing 520 the connection between the operator device 101 and the contact device 105 when the operator device 101 answers, the provider 127 transmits audio data including notification information 517 for the operator. The agency service 115 may further instruct the provider 127 to provide options to accept the call, disconnect the call or forward the call to voicemail of the MA number (e.g., by hanging up or selecting a provided option).

Once the connection 520 between the operator device 101 and the contact device 105 is established, the provider 127 records audio on the line. The operator device 101 collects audio data using a microphone coupled to the operator device. The operator device 101, in turn, transmits 525 the collected audio data to the provider 127 and contact device 105 by way of the connection through the MA number. The contact device 105 communicates with the operator device 101 in a similar fashion. The provider 127 may additionally enable monitoring devices 107 to connect to the MA number or local number to monitor the call and/or transmit the audio data received from the operator device 101 and the contact device 105 to the agency service 115 or appliance 150 over the network 120.

Furthermore, the operator device 101 may also collect location data from GPS receivers and other direction mechanisms coupled to the operator device as described above with reference to <figref idref="DRAWINGS">FIG. 5A</figref>. The provider 127 and/or the agency service 115 may update 530 the appliance 150 with the received audio data. The agency service 115 or provider 127 may also update 530 the appliance with any other data received from the provider 127 and/or operator device 101.

SMS Communications

In addition to placing and receiving calls though virtual numbers, the operator device 101 may also send and receive SMS messages through MA numbers. Depending on the embodiment of the operator device 101, SMS messages may be sent/received via native SMS capability or using an application or web browser. Thus, the operator device 101 need not require telephony capability for SMS communications through a MA number.

Sending a SMS Message

In one embodiment, to send an SMS from a MA number to the contact device 105, the operator prepends or appends (e.g., manually or using a MA module 141) a native SMS message (e.g., To: [contact number]|The meeting is at 10 am) sent to the MA number from the operator device 101 to indicate the intended contact device 105. The provider 127 forwards SMS messages received on the virtual numbers to the agency service 115 for processing. The agency service 115 parses the SMS to determine information about the contact device 105, such as a transmitting number preprended or appended to the SMS message. The agency service 115 may also parse the SMS to determine the transmitting number of the source (e.g., for look-up in a mapping table) and/or key-in information for authentication of the source. In turn, the agency service 115 extracts the transmitting number of the contact, any device information associated with the operator device and any formatting or key-in information from the SMS message. The agency service 115 then instruct the provider 127 to transmit the modified SMS message to the extracted contact number from the MA number that originally received the SMS. In some embodiments, the MA module 141 provides an interface for the user to enter an MA number and contact number, which are automatically attached to the SMS.

Alternatively, embodiments of the operator device 101 may communicate data for transmitting via SMS from the MA number to the agency service 115. For example, embodiments of the MA module 141 or a web interface may provide a menu or interface for the user to enter or otherwise select a given MA number and transmitting number of a contact device 105. The interface further provides the operator with the ability to enter message content. The operator may then submit the message and associated information to the agency service 115. The agency service 115 then instructs the provider 127 to transmit an SMS message containing the message to the specified contact number from the specified MA number.

Once the SMS is delivered, the provider 127 and/or agency service 115 may confirm receipt of the SMS at the contact device 105 with operator device 101 or other entity and/or update the appliance 150 with a copy of the SMS and associated information.

Receiving a SMS Message

In one embodiment, to receive an SMS sent to a MA number from the contact device 105, the provider 127 transmits data (e.g., SMS messages) received on the virtual numbers to the agency service 115 for processing. The agency service 115 may then parse the SMS. However, as the SMS message content does not include appended or prepended information (e.g., in the correct format with a transmitting number), the agency service 115 identifies the SMS message as an inbound message on the MA number for delivery to the operator device 101. The agency service 115 may also determine information about the received message, the contact device 105 (e.g., the transmitting number of the device) and/or MA number the message was received on and append or prepend a SMS message with the information. In turn, the agency service 115 determines the transmitting number of the operator device 101 associated with the MA number that received the SMS message and instructs the provider 127 to transmit the SMS message to the operator device 101 with any attached information.

The agency service 115 may instruct the provider to transmit SMS messages to the operator device 101 from the MA number the message was received on to prevent inadvertent, direct communication with the contact device 105. For example, the agency service 115 or provider 127 may prepend a SMS message with the transmitting number of the contact device the original SMS message was received from. In turn, the agency service 115 may and send the prepended SMS, including the original message content (e.g., From: [contact number]|The meeting is at 10 am), from the MA number to the operator device 101.

In some embodiments, the MA module 141 provides an interface for the user to view SMS messages. The MA module 141 may parse the SMS message to determine MA number and/or contact device 105 information attached by the agency service 115 and extract the attached information for presentation in an interface.

Alternatively, the agency service 115 may communicate content from SMS messages received on an MA number and associated contact and MA number information to the operator device 101. For example, embodiments of the MA module 141 may receive and display messages and associated information in an interface for the operator. Alternatively, the agency service 115 may provide a web interface to display the received SMS and associated information.

Once the SMS is delivered, the provider 127 and/or agency service 115 may confirm receipt of the SMS at the operator device 101 or other entity and/or update the appliance 150 with a copy of the SMS and associated information.

Monitoring an Operator Device

<figref idref="DRAWINGS">FIG. 6</figref> is an interaction diagram illustrating a method for monitoring 600 an operator device 101 according to one example embodiment. As described above, the agency service 115 receives 610A collected data from the operator device and/or the provider 127. Additionally, the provider 127 may receive data 610B from the operator device 101. In turn, the agency service 115 and/or provider 127 may update 530 the appliance at the agency 110. A monitoring device 107 may subsequently monitor 600A, 600B the operator device 101 using one or both of the processes outlined below.

In one embodiment, the monitoring device 107 connects 400 to a local number or MA number for monitoring 600A the operator device 101. The monitoring device 107 may be connected 400 by answering an incoming call from the local or MA number initiated by the provider 127 or dialing a virtual number directly as described with reference to <figref idref="DRAWINGS">FIG. 4</figref>.

Once the connection between the monitoring device 107 and the MA number or local number is established, the monitoring device 640 receives the live audio transmitted between the operator device 101 and the contact device 105. To continue monitoring 600A the operator device 101, the monitoring device 107 simply maintains the connection 400 with the virtual number.

In another embodiment, the monitoring device 107 connects 650 to the agency service 115 and/or appliance 150 for monitoring 600B the operator device 101. The monitoring device 107 may establish the connection 650 using a web browser or monitoring module 140 that retrieves or streams collected data via a monitoring interface on the appliance 150 or agency service 115 (e.g., monitoring interface 145).

In one example embodiment, the monitoring device 107 streams 660 audio and/or location measurements in real-time from the agency service 115. In addition, the monitoring device 107 can retrieve 670 historical data stored on the appliance 150 to view previously recorded operator device 101 operating sessions 500. In some embodiments, the appliance 150 also supports real-time monitoring.

In some instances, the monitoring device 107 receives notifications from the monitoring interface 145 for display in the web browser or with the monitoring module 140. Example notifications include audio or visual alerts for notifying personnel if the operator device 101 stops transmitting real-time data (e.g., ends the call). In some embodiments, the monitoring device 107 may also retrieve SMS communications between the operator device 101 and the contact device 105 using the monitoring interface 145 for display in the web browser or with the monitoring module 140.

SUMMARY

The foregoing description of the embodiments has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure.

Some portions of this description describe the embodiments in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combinations thereof

Any of the steps, operations, or processes described herein may be performed or implemented with one or more hardware or software modules, alone or in combination with other devices.

Embodiments may also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, and/or it may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a non-transitory, tangible computer readable storage medium, or any type of media suitable for storing electronic instructions, which may be coupled to a computer system bus. Furthermore, any computing systems referred to in the specification may include a single processor or may be architectures employing multiple processor designs for increased computing capability.

Embodiments may also relate to a product that is produced by a computing process described herein. Such a product may comprise information resulting from a computing process, where the information is stored on a non-transitory, tangible computer readable storage medium and may include any embodiment of a computer program product or other data combination described herein.

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the disclosure be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments is intended to be illustrative, but not limiting, of the scope of the disclosure, which is set forth in the following claims.

Contents6

Every citation, both waysCites: the store holds 147 of 148

Citations
Document	Relation	Office	Cited during
US10944860B2	Cited by	United States of America	Applicant
US10187518B2	Cited by	United States of America	Applicant
US10547737B2	Cited by	United States of America	Applicant
US9998603B2	Cited by	United States of America	Applicant
US10999735B2	Cited by	United States of America	Applicant
US11233891B2	Cited by	United States of America	Applicant
US10375233B2	Cited by	United States of America	Applicant
CN109889544A	Cited by	China	Search report
WO0150682A1	Cites	World Intellectual Property Organization (WIPO)	Applicant
CN101112053A	Cites	China	Applicant
EP1835691A1	Cites	European Patent Office (EPO)	Applicant
CN1852466A	Cites	China	Applicant
CN1917456A	Cites	China	Applicant
US2001016037A1	Cites	United States of America	Applicant
US2001019604A1	Cites	United States of America	Search report
US2001036821A1	Cites	United States of America	Applicant
JP2001237965A	Cites	Japan	Applicant
JP2001268230A	Cites	Japan	Applicant
US2002061100A1	Cites	United States of America	Applicant
US2002132638A1	Cites	United States of America	Search report
US2002181460A1	Cites	United States of America	Search report
US2002198007A1	Cites	United States of America	Applicant
US2003078041A1	Cites	United States of America	Applicant
US2003144024A1	Cites	United States of America	Applicant
US2003215069A1	Cites	United States of America	Applicant
US2004110465A1	Cites	United States of America	Applicant
US2004151288A1	Cites	United States of America	Applicant
US2004152442A1	Cites	United States of America	Applicant
US2004165709A1	Cites	United States of America	Applicant
US2004208307A1	Cites	United States of America	Applicant
US2004240439A1	Cites	United States of America	Applicant
WO2005031544A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
US2005074104A1	Cites	United States of America	Search report
US2005094773A1	Cites	United States of America	Applicant
US2005111629A1	Cites	United States of America	Applicant
US2005175165A1	Cites	United States of America	Applicant
US2005180395A1	Cites	United States of America	Applicant
US2005232253A1	Cites	United States of America	Applicant
US2005277407A1	Cites	United States of America	Applicant
US2006034426A1	Cites	United States of America	Applicant
US2006140200A1	Cites	United States of America	Applicant
US2006147012A1	Cites	United States of America	Applicant
US2006291638A1	Cites	United States of America	Applicant
US2007019618A1	Cites	United States of America	Applicant
US2007036127A1	Cites	United States of America	Applicant
US2007041550A1	Cites	United States of America	Applicant
US2007105531A1	Cites	United States of America	Search report
US2007161412A1	Cites	United States of America	Applicant
JP2007166089A	Cites	Japan	Applicant
US2007183403A1	Cites	United States of America	Applicant
US2007217437A1	Cites	United States of America	Applicant
US2008008105A1	Cites	United States of America	Applicant
US2008045186A1	Cites	United States of America	Search report
US2008198978A1	Cites	United States of America	Applicant
US2008205626A1	Cites	United States of America	Applicant
US2008215725A1	Cites	United States of America	Applicant
US2008242271A1	Cites	United States of America	Applicant
US2009061872A1	Cites	United States of America	Applicant
JP2009071603A	Cites	Japan	Applicant
US2009074156A1	Cites	United States of America	Applicant
US2009141883A1	Cites	United States of America	Applicant
US2009214008A1	Cites	United States of America	Applicant
JP2009260492A	Cites	Japan	Applicant
US2010128857A1	Cites	United States of America	Applicant
US2010161683A1	Cites	United States of America	Applicant
US2010189228A1	Cites	United States of America	Applicant
US2010220843A1	Cites	United States of America	Applicant
CN201039280Y	Cites	China	Applicant
US2011002480A1	Cites	United States of America	Applicant
US2011081009A1	Cites	United States of America	Applicant
WO2011129420A1	Cites	World Intellectual Property Organization (WIPO)	Applicant
US2011164734A1	Cites	United States of America	Applicant
WO2013003779A1	Cites	World Intellectual Property Organization (WIPO)	Applicant
US2013303151A1	Cites	United States of America	Applicant
US2014194101A1	Cites	United States of America	Applicant
US2014302835A1	Cites	United States of America	Applicant
RU2221345C2	Cites	Russian Federation	Applicant
GB2456754A	Cites	United Kingdom	Applicant
US5734659A	Cites	United States of America	Applicant
US5974309A	Cites	United States of America	Applicant
US6301246B1	Cites	United States of America	Applicant
US6356630B1	Cites	United States of America	Applicant
US6449474B1	Cites	United States of America	Applicant
US6553025B1	Cites	United States of America	Applicant
US7181017B1	Cites	United States of America	Applicant
US7626980B1	Cites	United States of America	Applicant
US7839987B1	Cites	United States of America	Search report
US7873349B1	Cites	United States of America	Applicant
US8265597B2	Cites	United States of America	Applicant
US8824652B2	Cites	United States of America	Applicant
EP1835691A1	Cites	European Patent Office (EPO)	Applicant
GB2456754	Cites	United Kingdom	Applicant
JP2001237965	Cites	Japan	Applicant
JP2001268230	Cites	Japan	Applicant
JP2007166089	Cites	Japan	Applicant
JP2009071603	Cites	Japan	Applicant
JP2009260492	Cites	Japan	Applicant
US20010016037A1	Cites	United States of America	Applicant
US20010019604A1	Cites	United States of America	Search report
US20010036821A1	Cites	United States of America	Applicant

Showing 100 of 155

98 members in 10 offices

This recordMember, by publication datePriority claim

Priority claims10

Priority claims
Document	Office	Kind	Date
201161503586	United States of America	P	2011-06-30
201161503586	United States of America	P	2011-06-30
201213539050	United States of America	A	2012-06-29
201314086960	United States of America	A	2013-11-21
201314086960	United States of America	A	2013-11-21
14086960	–	–	–
61503586	–	–	–
US201161503586P	–	–	–
US201213539050	–	–	–
US201314086960	–	–	–

Members98

Family members, oldest first
Document	Office	Kind
CA2837595A1	Canada	A1	2012-12-06
CA2897088A1	Canada	A1	2012-12-06
US2012309379A1	United States of America	A1	2012-12-06
WO2012166729A1	World Intellectual Property Organization (WIPO)	A1	2012-12-06
CA2839952A1	Canada	A1	2013-01-03
US2013003942A1	United States of America	A1	2013-01-03
WO2013003779A1	World Intellectual Property Organization (WIPO)	A1	2013-01-03
CA2850524A1	Canada	A1	2013-04-18
US2013095791A1	United States of America	A1	2013-04-18
WO2013056156A1	World Intellectual Property Organization (WIPO)	A1	2013-04-18
US2013208878A1	United States of America	A1	2013-08-15
AU2012262351A1	Australia	A1	2013-12-19
US8626078B2	United States of America	B2	2014-01-07
AU2012275151A1	Australia	A1	2014-01-16
AU2012262351B2	Australia	B2	2014-02-27
US2014079201A1	United States of America	A1	2014-03-20
US2014080473A1	United States of America	A1	2014-03-20
US2014087692A1	United States of America	A1	2014-03-27
CN103703693A	China	A	2014-04-02
EP2715949A1	European Patent Office (EPO)	A1	2014-04-09
MX2013013965A	Mexico	A	2014-04-14
CN103733601A	China	A	2014-04-16
AU2012323961A1	Australia	A1	2014-04-17
MX2014000151A	Mexico	A	2014-04-25
EP2727323A1	European Patent Office (EPO)	A1	2014-05-07
US8731171B2	United States of America	B2	2014-05-20
MX2014004373A	Mexico	A	2014-05-28
CN103947129A	China	A	2014-07-23
EP2767003A1	European Patent Office (EPO)	A1	2014-08-20
US8824652B2	United States of America	B2	2014-09-02
JP2014524163A	Japan	A	2014-09-18
WO2014151684A2	World Intellectual Property Organization (WIPO)	A2	2014-09-25
JP2014526170A	Japan	A	2014-10-02
JP5624252B2	Japan	B2	2014-11-12
US2014334617A1	United States of America	A1	2014-11-13
RU2533171C1	Russian Federation	C1	2014-11-20
WO2014151684A3	World Intellectual Property Organization (WIPO)	A3	2014-11-20
JP2014533461A	Japan	A	2014-12-11
US8934847B2	United States of America	B2	2015-01-13
EP2715949A4	European Patent Office (EPO)	A4	2015-01-14
JP2015039199A	Japan	A	2015-02-26
US2015065101A1	United States of America	A1	2015-03-05
US2015071425A1	United States of America	A1	2015-03-12
EP2767003A4	European Patent Office (EPO)	A4	2015-03-18
US9031218B2	United States of America	B2	2015-05-12
EP2727323A4	European Patent Office (EPO)	A4	2015-06-10
IN2740CHN2014A	India	A	2015-07-03
RU2014102971A	Russian Federation	A	2015-08-10
CA2837595C	Canada	C	2015-09-29
AU2014236991A1	Australia	A1	2015-10-08
RU2567860C1	Russian Federation	C1	2015-11-10
RU2570899C2	Russian Federation	C2	2015-12-20
AU2012323961B2	Australia	B2	2016-01-07
EP2974251A2	European Patent Office (EPO)	A2	2016-01-20
US9253311B2	United States of America	B2	2016-02-02
US9270814B2	United States of America	B2	2016-02-23
MX2015012023A	Mexico	A	2016-03-09
RU2014135229A	Russian Federation	A	2016-03-27
US9313323B2	United States of America	B2	2016-04-12
US2016119472A1	United States of America	A1	2016-04-28
US2016198041A1	United States of America	A1	2016-07-07
CA2850524C	Canada	C	2016-08-02
JP5965954B2	Japan	B2	2016-08-10
CN103733601B	China	B	2016-09-07
AU2014236991B2	Australia	B2	2016-09-22
JP6016908B2	Japan	B2	2016-10-26
MX343371B	Mexico	B	2016-11-01
EP2974251A4	European Patent Office (EPO)	A4	2016-12-07
AU2012275151B2	Australia	B2	2017-03-30
US9674339B2	United States of America	B2	2017-06-06
JP6141287B2	Japan	B2	2017-06-07
US9736296B2This record	United States of America	B2	2017-08-15
US2017251101A1	United States of America	A1	2017-08-31
US2017264740A1	United States of America	A1	2017-09-14
MX351685B	Mexico	B	2017-10-25
US2017318151A1	United States of America	A1	2017-11-02
CN103947129B	China	B	2018-01-23
CA2839952C	Canada	C	2018-03-27
US9998603B2	United States of America	B2	2018-06-12
EP2767003B1	European Patent Office (EPO)	B1	2018-07-18
EP2715949B1	European Patent Office (EPO)	B1	2018-10-03
EP2974251B1	European Patent Office (EPO)	B1	2018-10-03
EP2727323B1	European Patent Office (EPO)	B1	2018-12-19
US10187518B2	United States of America	B2	2019-01-22
US10218838B2	United States of America	B2	2019-02-26
US2019158656A1	United States of America	A1	2019-05-23
US2019166250A1	United States of America	A1	2019-05-30
CA2897088C	Canada	C	2019-07-09
US10375233B2	United States of America	B2	2019-08-06
US2019306307A1	United States of America	A1	2019-10-03
US10547737B2	United States of America	B2	2020-01-28
US10547740B2	United States of America	B2	2020-01-28
US2020120206A1	United States of America	A1	2020-04-16
US2020128127A1	United States of America	A1	2020-04-23
US10887456B2	United States of America	B2	2021-01-05
US10944860B2	United States of America	B2	2021-03-09
US2021120122A9	United States of America	A9	2021-04-22
US10999735B2	United States of America	B2	2021-05-04

134 transactions on the USPTO file

Allowed after 3 non-final rejections, 2 final rejections and 2 RCEs.

Non-final rejections: 3
Final rejections: 2
RCEs: 2
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2021-02-25	Email NotificationEML_NTR	EML_NTR
2021-02-25	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2021-02-23	Correspondence Address ChangeC.AD	C.AD
2021-01-08	Payment of Maintenance Fee, 4th Year, Large EntityM1551	M1551
2021-01-05	Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG.	BIG.
2017-08-15	Recordation of Patent Grant MailedPGM/	PGM/
2017-08-15	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2017-07-27	Email NotificationEML_NTR	EML_NTR
2017-07-26	Issue Notification MailedAllowedWPIR	WPIR
2017-07-12	Dispatch to FDCD1935	D1935
2017-07-11	Application Is Considered Ready for IssuePILS	PILS
2017-07-10	Issue Fee Payment VerifiedN084	N084
2017-07-10	Issue Fee Payment ReceivedIFEE	IFEE
2017-04-20	Electronic ReviewELC_RVW	ELC_RVW
2017-04-20	Email NotificationEML_NTF	EML_NTF
2017-04-20	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2017-04-17	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2017-04-17	Information Disclosure Statement consideredIDSC	IDSC
2017-04-17	Information Disclosure Statement consideredIDSC	IDSC
2017-03-07	Information Disclosure Statement (IDS) FiledM844	M844
2017-03-07	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2017-01-14	Date Forwarded to ExaminerFWDX	FWDX
2016-12-16	Response after Non-Final ActionA...	A...
2016-12-16	Request for Extension of Time - GrantedXT/G	XT/G
2016-08-09	Reference capture on IDSRCAP	RCAP
2016-08-09	Information Disclosure Statement (IDS) FiledM844	M844
2016-08-09	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2016-06-30	Electronic ReviewELC_RVW	ELC_RVW
2016-06-30	Email NotificationEML_NTF	EML_NTF
2016-06-30	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2016-06-25	Non-Final RejectionNon-final rejectionCTNF	CTNF
2016-06-25	Information Disclosure Statement consideredIDSC	IDSC
2016-06-25	Information Disclosure Statement consideredIDSC	IDSC
2016-06-25	Information Disclosure Statement consideredIDSC	IDSC
2016-06-25	Information Disclosure Statement consideredIDSC	IDSC
2016-06-25	Information Disclosure Statement consideredIDSC	IDSC
2016-06-17	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2016-06-15	Request for Continued Examination (RCE)RCEX	RCEX
2016-06-15	Workflow - Request for RCE - BeginBRCE	BRCE
2016-05-23	Information Disclosure Statement (IDS) FiledM844	M844
2016-05-23	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2016-05-16	Paralegal or electronic terminal disclaimer approvedP574	P574
2016-05-03	Terminal Disclaimer FiledDIST	DIST
2016-04-07	Email NotificationEML_NTR	EML_NTR
2016-04-07	Email NotificationEML_NTR	EML_NTR
2016-04-07	Filing Receipt - ReplacementFLRCPT.R	FLRCPT.R
2016-04-07	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2016-03-22	Email NotificationEML_NTR	EML_NTR
2016-03-22	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2016-03-17	Paralegal TD Not acceptedP575	P575
2016-03-17	Advisory Action (PTOL-303)CTAV	CTAV
2016-03-08	Date Forwarded to ExaminerFWDX	FWDX
2016-03-06	Reference capture on IDSRCAP	RCAP
2016-03-06	Information Disclosure Statement (IDS) FiledM844	M844
2016-03-06	Response after Final ActionA.NE	A.NE
2016-03-06	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2015-12-17	Electronic ReviewELC_RVW	ELC_RVW
2015-12-17	Email NotificationEML_NTF	EML_NTF
2015-12-17	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2015-12-11	Final RejectionFinal rejectionCTFR	CTFR
2015-09-10	Date Forwarded to ExaminerFWDX	FWDX
2015-09-04	Response after Non-Final ActionA...	A...
2015-09-04	Request for Extension of Time - GrantedXT/G	XT/G
2015-08-31	Reference capture on IDSRCAP	RCAP
2015-08-31	Information Disclosure Statement (IDS) FiledM844	M844
2015-08-31	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2015-07-21	Reference capture on IDSRCAP	RCAP
2015-07-21	Information Disclosure Statement (IDS) FiledM844	M844
2015-07-21	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2015-04-22	Information Disclosure Statement (IDS) FiledM844	M844
2015-04-22	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2015-04-10	Electronic ReviewELC_RVW	ELC_RVW
2015-04-10	Email NotificationEML_NTF	EML_NTF
2015-04-10	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2015-04-06	Non-Final RejectionNon-final rejectionCTNF	CTNF
2015-04-06	Information Disclosure Statement consideredIDSC	IDSC
2015-04-06	Information Disclosure Statement consideredIDSC	IDSC
2015-04-06	Information Disclosure Statement consideredIDSC	IDSC
2015-03-06	Reference capture on IDSRCAP	RCAP
2015-03-06	Information Disclosure Statement (IDS) FiledM844	M844
2015-03-06	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2015-02-04	Reference capture on IDSRCAP	RCAP
2015-02-04	Information Disclosure Statement (IDS) FiledM844	M844
2015-02-04	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2014-12-08	Information Disclosure Statement (IDS) FiledM844	M844
2014-12-08	Reference capture on IDSRCAP	RCAP
2014-12-08	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2014-10-28	Date Forwarded to ExaminerFWDX	FWDX
2014-10-28	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2014-10-27	Request for Continued Examination (RCE)RCEX	RCEX
2014-10-27	Workflow - Request for RCE - BeginBRCE	BRCE
2014-09-22	Electronic ReviewELC_RVW	ELC_RVW
2014-09-22	Email NotificationEML_NTF	EML_NTF
2014-09-22	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2014-09-17	Final RejectionFinal rejectionCTFR	CTFR
2014-08-29	Date Forwarded to ExaminerFWDX	FWDX
2014-08-26	Response after Non-Final ActionA...	A...
2014-05-30	Electronic ReviewELC_RVW	ELC_RVW
2014-05-30	Email NotificationEML_NTF	EML_NTF
2014-05-30	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF

Showing 100 of 134

11 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2021-01-20	AssignmentAS	AS
2021-01-20	AssignmentAS	AS
2021-01-08	Maintenance fee paymentMAFP	MAFP
2021-01-08	Maintenance fee paymentMAFP	MAFP
2021-01-05	Fee payment procedureFEPP	FEPP
2021-01-05	Fee payment procedureFEPP	FEPP
2018-06-26	Certificate of correctionCC	CC
2017-07-26	Information on status: patent grantGrantedSTCF	STCF
2017-07-26	Information on status: patent grantGrantedSTCF	STCF
2012-12-20	AssignmentAS	AS
2012-07-02	AssignmentAS	AS

Attaching multiple phone lines to a single mobile or landline phone

Summary by NHIP

Claim Score by NHIP

Abstract