Uninterrupted transmission of internet protocol transmissions during endpoint changes

Information

  • Patent Grant
  • 10021729
  • Patent Number
    10,021,729
  • Date Filed
    Friday, July 17, 2015
    8 years ago
  • Date Issued
    Tuesday, July 10, 2018
    5 years ago
Abstract
Facilitating uninterrupted transmission of internet protocol (IP) transmissions during endpoint changes is disclosed. When an IP transmission is received at a first relay port or a second relay port, a call record having the first relay port identifier or the second relay port identifier matching a destination port identifier in the IP transmission is located. When the destination port identifier matches the first relay port identifier of the record, a source IP address identifier and a source port identifier from the IP transmission are set as a first entity IP address identifier and first entity port identifier, respectively, of the record when the first entity IP address identifier and first entity port identifier do not match the source IP address identifier and source port identifier respectively and a received IP session identifier in the IP transmission matches the first entity session identifier. A similar procedure is followed to set a second entity IP address identifier and port identifier.
Description
BACKGROUND

Field


This invention relates to Internet protocol (IP) transmissions and, more particularly, to uninterrupted transmission of IP transmissions containing real time transport protocol (RTP) data during endpoint changes.


Description of the Related Technology


Internet Protocol (IP) transmission systems are known to use media relays to relay IP transmissions from one endpoint to another. In a telephone system, the media relay relays IP transmissions between a caller and a callee. An IP session is established by a call controller, which interacts with the media relay, the caller and the callee to convey to each of these entities the IP addresses and ports to which they should send IP transmissions and from which they should expect IP transmissions. The media relay is configured to accept packets conveyed by IP transmissions from specified caller and callee IP addresses and ports. In some systems, such as mobile telephone systems, a mobile telephone may be in communication with a first base station while in a certain geographical area and there may be a handoff of the call to another base station when the mobile telephone is moved to a different geographical location. Communications between the base stations and the mobile telephones are conducted on a Global System from Mobile Communication (GSM) network or other cellular network, for example, and the base stations convert messages to and from the GSM network and the IP network and thus, the base stations establish the caller and callee IP addresses and ports. Each base station will have a unique IP address and UDP port number that it associates or assigns to the mobile telephone with which it has established communication in the conventional manner over the cellular network. Thus, a conventional media relay will reject IP streams from the new base station after handoff of the call because such streams are seen as being transmitted by an unauthorized source. This generally prevents voice over IP telephone calls from being made through systems that employ media relays without further call handling.


The Session Initiation Protocol (SIP) RFC 3261 provided by the Internet Engineering Task Force (IETF) specifies a mechanism for an endpoint to notify another endpoint if its IP address changes. This mechanism employs a signaling message that conveys an identification of new media properties for the endpoint whose IP address has changed. The use of SIP messages for this purpose, however, adds extra overhead and delays to the call as signaling messages must be routed through the call controller and the call controller must communicate with the media relay and endpoints to re-configure the media relay to accept IP transmissions from the endpoint having the new IP address and to cause IP transmission to be relayed thereto each time a handoff occurs.


SUMMARY OF CERTAIN EMBODIMENTS

In accordance with one aspect, there is provided a method for facilitating uninterrupted transmission of Internet Protocol (IP) transmissions, during endpoint changes. The method involves, in response to receiving an IP transmission at a caller port or a callee port of a media relay through which IP transmissions of an IP communication session are relayed, locating a session information record having a caller port identifier or callee port identifier matching a destination port identifier in the IP transmission. The caller port identifier identifies the caller port and the callee port identifier identifies the callee port. When the destination port identifier in the IP transmission matches the caller port identifier of the session information record and when a source IP address identifier or a source port identifier in the IP transmission do not match a caller IP address identifier or the caller port identifier respectively of the session information record, and when a session identifier in the IP transmission matches a caller session identifier in the session information record, the method involves setting the source IP address identifier and the source port identifier in the IP transmission as the caller IP address identifier and caller port identifier respectively of the session information record. When the destination port identifier in the IP transmission matches the callee port identifier of the session information record, and when the source IP address identifier or the source port identifier in the IP transmission do not match a callee IP address identifier or the callee port identifier respectively of the session information record, and when the session identifier in the IP transmission matches a callee session identifier in the session information record, the method involves setting the source IP address identifier and the source port identifier of the IP transmission as the callee IP address identifier and the callee port identifier respectively of the session information record.


The method may involve maintaining the session information records, each record associating session information, caller information and callee information for a respective IP communication session, and the session information including the caller and callee port identifiers identifying a caller port and a callee port respectively of the media relay through which IP transmissions of the IP communication session are relayed. The caller information may include the caller IP address identifier and the caller port identifier to which IP transmissions received at the callee port are transmitted from the media relay, and a caller session identifier. The callee information may include the callee IP address identifier and the callee port identifier to which IP transmissions received at the caller port are transmitted from the media relay, and may further include a callee session identifier.


The method may involve storing the session identifier received in the IP transmission in the caller session identifier field in the session information record, when the pre-determined IP transmission is received from the caller, and storing the session identifier received in the IP transmission in the callee session identifier field in the session information record, when the pre-determined IP transmission is received from the callee.


The method may involve causing the media relay to forward the IP transmission to the callee at the callee IP address and callee port identified by the callee IP address identifier and callee port identifier respectively of the session information record and identifying the source of the IP transmission forwarded to the callee with the callee port identifier, when the IP transmission was received at the caller port.


The method may involve causing the media relay to forward the IP transmission to the caller at the caller IP address and caller port identified by the caller IP address identifier and caller port identifier respectively of the record and identifying the source of the IP transmission forwarded to the caller with the caller port identifier, when the IP transmission was received at the callee port.


The session identifier may include synchronization source (SSRC) identifier, the caller session identifier may include a caller SSRC identifier and the callee session identifier may include a callee SSRC identifier.


The IP transmission may contain real time transport protocol (RTP) data, the caller port may be a caller RTP port and the callee port may be a callee RTP port.


In accordance with another aspect, there is provided a media relay apparatus for facilitating uninterrupted transmission of Internet Protocol (IP) transmissions during endpoint changes. The apparatus includes connection provisions for providing a connection to an IP network, provisions for defining a logical input/output interface defining caller and callee ports in the connection provisions. The apparatus further includes provisions for relaying IP transmissions of an IP communication session between a caller port and a callee port of the connection provisions. The apparatus further includes provisions for receiving an IP transmission at the caller port or the callee port. The apparatus further includes provisions for locating a session information record having a caller port identifier or a callee port identifier matching a destination port identifier included in the IP transmission. The caller port identifier identifies the caller port and the callee port identifier identifies the callee port. The apparatus further includes provisions for setting a source IP address identifier and a source port identifier in the IP transmission as the caller IP address identifier and caller port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the caller port identifier of the session information record, and when the source IP address identifier or the source port identifier in the IP transmission do not match a caller IP address identifier or the caller port identifier respectively of the session information record, and when a session identifier in the IP transmission matches a caller session identifier in the session information record. The apparatus further includes provisions for setting the source IP address identifier and the source port identifier of the IP transmission as the callee IP address identifier and the callee port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the callee port identifier of the session information record, and when the source IP address identifier or the source port identifier in the IP transmission do not match a callee IP address identifier or the callee port identifier respectively of the session information record, and when the session identifier in the IP transmission matches a callee session identifier in the session information record.


The apparatus may include provisions for maintaining the session information records, each record associating session information, caller information and callee information for a respective IP communication session. The session information may include the caller and callee port identifiers identifying a caller port and a callee port respectively of the connection provisions through which IP transmissions of the IP communication session are relayed. The caller information may include the caller IP address identifier and the caller port identifier to which IP transmissions received at the callee port are transmitted from the caller port, and a caller session identifier. The callee information may include the callee IP address identifier and the callee port identifier to which IP transmissions received at the caller port are transmitted from the callee port, and a callee session identifier.


The apparatus may include provisions for storing the session identifier received in the IP transmission in the caller session identifier field in one of the session information records, when the pre-determined IP transmission is received from the caller, and provisions for storing the session identifier received in the IP transmission in the callee session identifier field in one of the session information records, when the pre-determined IP transmission is received from the callee.


The apparatus may include provisions for causing the connection provisions to forward the IP transmission to the callee at the callee IP address and callee port identified by the callee IP address identifier respectively and callee port identifier of the session information record, and provisions for identifying the source of the IP transmission forwarded to the callee with the callee port identifier, when the IP transmission was received at the caller port.


The apparatus may include provisions for causing the connection provisions to forward the IP transmission to the caller at the caller IP address and caller port identified by the caller IP address identifier and caller port identifier respectively of the session information record, and provisions for identifying the source of the IP transmission forwarded to the caller with the caller port identifier, when the IP transmission was received at the callee port.


The session identifier may include synchronization source (SSRC) identifier, the caller session identifier may include a caller SSRC identifier and the callee session identifier may include a callee SSRC identifier.


The IP transmission may contain real time transport protocol (RTP) data, the caller port may be a caller RTP port and the callee port may be a callee RTP port.


In accordance with another aspect, there is provided a media relay apparatus for facilitating uninterrupted transmission of Internet protocol (IP) transmissions during endpoint changes. The apparatus includes a processor circuit operably configured to define caller and callee ports on a network and operably configured to relay IP transmissions of an IP communication session between a defined caller port and a defined callee port. The processor circuit is further configured to locate a session information record having a caller port identifier or a callee port identifier matching a destination port identifier included in the IP transmission. The caller port identifier identifies the caller port and the callee port identifier identifies the callee port. The processor circuit is further configured to set a source IP address identifier and the source port identifier in the IP transmission as the caller IP address identifier and caller port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the caller port identifier of the session information record, and when the source IP address identifier or a source port identifier in the IP transmission do not match a caller IP address identifier or the caller port identifier respectively of the session information record, and when a session identifier in the IP transmission matches a caller session identifier in the session information record. The apparatus further includes setting the source IP address identifier and the source port identifier of the IP transmission as the callee IP address identifier and the callee port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the callee port identifier of the session information record, and when the source IP address identifier or the source port identifier in the IP transmission do not match a callee IP address identifier or the callee port identifier respectively of the session information record, and when the session identifier in the IP transmission matches a callee session identifier in the session information record.


The processor circuit may be further configured to maintain the session information records, each record associating session information, caller information and callee information for a respective IP communication session. The session information may include the caller and callee port identifiers identifying a caller port and a callee port respectively through which IP transmissions of the IP communication session to be relayed. The caller information may include the caller IP address identifier and the caller port identifier to which IP transmissions received at the callee port are transmitted from the caller port, and a caller session identifier. The callee information may include the callee IP address identifier and the callee port identifier to which IP transmissions received at the caller port are transmitted from the callee port, and a callee session identifier.


The processor circuit may be further configured to store the session identifier received in the IP transmission in the caller session identifier field in the one of the session information records, when the pre-determined IP transmission is received from the caller, and to store the session identifier received in the IP transmission in the callee session identifier field in the session information record, when the pre-determined IP transmission is received from the callee.


The processor circuit may be further configured to forward the IP transmission to the callee at the callee IP address and callee port identified by the callee IP address identifier and callee port identifier respectively of the session information record, and identify the source of the IP transmission forwarded to the callee with the callee port identifier, when the IP transmission was received at the caller port.


The processor circuit may be further configured to forward the IP transmission to the caller at the caller IP address and caller port identified by the caller IP address identifier and caller port identifier respectively of the session information record, and identify the source of the IP transmission forwarded to the caller with the caller port identifier, when the IP transmission was received at the callee port.


The session identifier may include a synchronization source (SSRC) identifier, the caller session identifier may include a caller SSRC identifier and the callee session identifier may include a callee SSRC identifier.


The IP transmission may contain real time transport protocol (RTP) data and the caller port may be a caller RTP port and the callee port may be a callee RTP port.


In accordance with another aspect, there is provided a media relay apparatus for facilitating uninterrupted transmission of Internet Protocol (IP) transmissions during endpoint changes. The apparatus includes a network interface providing a connection to a network, and a processor circuit in communication with the network interface, the processor circuit including a processor and a non-transitory computer readable medium in communication with the processor. The non-transitory computer readable medium is encoded with codes for directing the processor to define caller and callee ports on the network, and to relay IP transmissions of an IP communication session between a defined caller port and a defined callee port. The codes further include codes for directing the processor to locate a session information record having a caller port identifier or a callee port identifier matching a destination port identifier included in the IP transmission. The caller port identifier identifies the caller port and the callee port identifier identifies the callee port. The codes further include codes for directing the processor to set the source IP address identifier and the source port identifier in the IP transmission as the caller IP address identifier and caller port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the caller port identifier of the session information record, and when a source IP address identifier or a source port identifier in the IP transmission do not match a caller IP address identifier or the caller port identifier respectively of the session information record, and when a session identifier in the IP transmission matches a caller session identifier in the session information record. The codes further include codes for directing the processor to set the source IP address identifier and the source port identifier of the IP transmission as the callee IP address identifier and the callee port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the callee port identifier of the session information record, and when the source IP address identifier or the source port identifier in the IP transmission do not match a callee IP address identifier or the callee port identifier respectively of the session information record, and when the session identifier in the IP transmission matches a callee session identifier in the session information record.


The non-transitory computer readable medium may be further encoded with codes for directing the processor to maintain the session information records, each record associating session information, caller information and callee information for a respective IP communication session. The session information may include the caller and callee port identifiers identifying a caller port and a callee port respectively of the connection through which IP transmissions of the IP communication session to be relayed. The caller information may include the caller IP address identifier and the caller port identifier to which IP transmissions received at the callee port are transmitted from the caller port, and a caller session identifier. The callee information may include the callee IP address identifier and the callee port identifier to which IP transmissions received at the caller port are transmitted from the callee port, and a callee session identifier.


The non-transitory computer readable medium may be further encoded with codes for directing the processor to store the session identifier received in the IP transmission in the caller session identifier field in the session information record, when the pre-determined IP transmission is received from the caller, and to store the session identifier received in the IP transmission in the callee session identifier field in the one of the session information records, when the pre-determined IP transmission is received from the callee.


The non-transitory computer readable medium may be further encoded with codes for directing the processor to forward the IP transmission to the callee at the callee IP address and callee port identified by the callee IP address identifier and callee port identifier respectively of the session information record, and to identify the source of the IP transmission forwarded to the callee with the callee port identifier, when the IP transmission was received at the caller port.


The non-transitory computer readable medium may be further encoded with codes for directing the processor to forward the IP transmission to the caller at the caller IP address and caller port identified by the caller IP address identifier and caller port identifier respectively of the session information record, and to identify the source of the IP transmission forwarded to the caller with the caller port identifier, when the IP transmission was received at the callee port.


The session identifier may include synchronization source (SSRC) identifier, the caller session identifier may include a caller SSRC identifier and the callee session identifier may include a callee SSRC identifier.


The IP transmission may contain real time transport protocol (RTP) data and the caller port may be a caller RTP port and the callee port may be a callee RTP port.


In accordance with another aspect, there is provided a non-transitory computer readable medium encoded with codes for controlling a processor of a media relay apparatus to facilitate uninterrupted transmission of Internet Protocol (IP) transmissions during endpoint changes. The codes are operable to cause the processor to cause the media relay to act as a network interface providing a connection to a network, define caller and callee ports on the network, and relay IP transmissions of an IP communication session between a defined caller port and a defined callee port. The codes are also operable to cause the processor to locate a session information record having a caller port identifier or a callee port identifier matching a destination port identifier included in the IP transmission. The caller port identifier identifies the caller port and the callee port identifier identifies the callee port. The codes are further operable to cause the processor to further set a source IP address identifier and a source port identifier in the IP transmission as a caller IP address identifier and caller port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the caller port identifier of the session information record, and when a source IP address identifier or a source port identifier in the IP transmission do not match the caller IP address identifier or the caller port identifier respectively of the session information record and when a session identifier in the IP transmission matches a caller session identifier in the session information record. The codes further include codes for directing the processor to set the source IP address identifier and the source port identifier of the IP transmission as the callee IP address identifier and the callee port identifier respectively of the session information record when the destination port identifier in the IP transmission matches the callee port identifier of the session information record and when the source IP address identifier or the source port identifier in the IP transmission do not match a callee IP address identifier or the callee port identifier respectively of the session information record and when the session identifier in the IP transmission matches a callee session identifier in the session information record.


The computer readable medium may be further encoded with codes for directing the processor to maintain the session information records, each record associating session information, caller information and callee information for a respective IP communication session. The session information may include the caller and callee port identifiers identifying a caller port and a callee port respectively of the connection through which IP transmissions of the IP communication session are relayed. The caller information may include the caller IP address identifier and the caller port identifier to which IP transmissions received at the callee port are transmitted from the caller port, and a caller session identifier. The callee information may include the callee IP address identifier and the callee port identifier to which IP transmissions received at the caller port are transmitted from the callee port, and a callee session identifier.


The computer readable medium may be further encoded with codes for directing the processor to store the session identifier received in the IP transmission in the caller session identifier field in the session information record, when the pre-determined IP transmission is received from the caller, and store the session identifier received in the IP transmission in the callee session identifier field in the session information record, when the pre-determined IP transmission is received from the callee.


The computer readable medium may be further encoded with codes for directing the processor to forward the IP transmission to the callee at the callee IP address and callee port identified by the callee IP address identifier and callee port identifier respectively of the session information record, and to identify the source of the IP transmission forwarded to the callee with the callee port identifier, when the IP transmission was received at the caller port.


The computer readable medium may be further encoded with codes for directing the processor to forward the IP transmission to the caller at the caller IP address and caller port identified by the caller IP address identifier and caller port identifier respectively of the session information record, and to identify the source of the IP transmission forwarded to the caller with the caller port identifier, when the IP transmission was received at the callee port.


The session identifier may include synchronization source (SSRC) identifier, the caller session identifier may include a caller SSRC identifier and the callee session identifier may include a callee SSRC identifier.


The IP transmission may contain real time transport protocol (RTP) data and the caller port may be a caller RTP port and the callee port may be a callee RTP port.


Other aspects and features of the present disclosure will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments in conjunction with the accompanying figures.





BRIEF DESCRIPTION OF THE DRAWINGS

In drawings which illustrate embodiments,



FIG. 1 is a schematic diagram illustrating a system for facilitating uninterrupted transmission of internet protocol (IP) transmissions containing real time transport protocol (RTP) data during endpoint changes, according to a first embodiment.



FIG. 2 is a tabular representation of a call record used by the system shown in FIG. 1.



FIG. 3 is a flow chart of an authentication routine executed by a processor of a media relay shown in the system shown in FIG. 1.



FIG. 4 is a schematic representation of an internet protocol (IP) transmission according to the prior art.



FIG. 5 is a tabular representation of the call record shown in FIG. 2 as updated after receipt of an IP transmission at a caller port of the media relay shown in FIG. 1.



FIG. 6 is a flow chart of a continuity routine executed by the processor of the media relay shown in FIG. 1.



FIG. 7 is a tabular representation of the call record as updated after execution of the continuity routine shown in FIG. 6 when a pre-determined packet is received in the IP transmission.



FIG. 8 is a tabular representation of the call record shown in FIG. 7 further updated by the continuity routine after an IP transmission received subsequent to the pre-determined packet is received.



FIG. 9 is a flow chart of a forwarding routine executed by the processor of the media relay shown in FIG. 1 to relay the received IP transmission to a caller or callee with a source identification provided by the call record as updated by the continuity routine shown in FIG. 6.





DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

Referring to FIG. 1, a system for handling voice over internet protocol (IP) transmissions and more generally, IP transmissions, is shown generally at 20. The system 20 includes a routing controller/call controller (RC/CC) system 22 and first, second and third base stations 24, 26 and 50. The base stations 24, 26 and 50 are operable to communicate with the RC/CC 22 via a network or, as shown in this embodiment, separate networks 28 and 30, which in this embodiment depict the internet. The first and second base stations 24 and 26 in this embodiment are operable to communicate with caller and callee mobile telephones 32 and 34 respectively using a cellular wireless network in a conventional manner as is known in the art. The first and second base stations 24 and 26 thus act as “endpoints” for IP transmissions between the caller and callee.


Generally, to establish a call from the caller mobile telephone 32 to the callee mobile telephone 34, the caller mobile telephone transmits to the first base station 24 a session initiation protocol (SIP) message shown generally at 38. The SIP message 38 is transmitted from the caller mobile telephone 32 to the base station 24 and the first base station 24 formats the SIP message 38 into an IP transmission and transmits the IP transmission through the internet 28 to the RC/CC 22. In this embodiment, the first base station 24 is preconfigured with a network IP address 192.168.0.20 and universal datagram protocol (UDP) port 12345.


In response to receipt of the SIP message 38, the RC/CC 22 communicates with a media relay 40 and sends the caller IP address identifier and caller UDP port identifier contained in the SIP message to the media relay 40 to identify the IP address and UDP port to which the media relay 40 should send communications to the first base station 24 for receipt by the caller mobile telephone 32.


The media relay 40 has input/output interfaces 41 in communication with the processor to provide for physical connection to an IP network such as the internet. The media relay 40 is programmed to provide a logical input/output interface that interacts with the input/output interfaces 41 to define caller and callee real time transport protocol (RTP) ports in the conventional manner.


In response, the media relay 40 is configured to send a media relay IP address identifier and media relay RTP port identifier that it associates with the callee identified by the contents of the callee ID field in the SIP message 38. The media relay 40 sends this information to the RC/CC 22 to essentially inform the RC/CC 22 of the media relay IP address identifier and callee RTP port identifier that it should convey to the callee mobile telephone 34 so that the callee telephone can cause IP transmissions to be sent from the second base station 26 to the media relay 40 which can then subsequently forward those transmissions to the caller mobile telephone 32.


In response to receipt of the media relay IP address identifier and the callee RTP port identifier designated by the media relay 40, the RC/CC 22 transmits a SIP invite message 42 through the internet 30 to the callee mobile telephone 34 through the second base station 26. In this embodiment, the second base station 26 has an IP address (192.168.3.10) and a UDP port number (33123). Thus, the RC/CC 22 directs this SIP invite message 42 to the IP address and UDP port associated with the callee mobile telephone 34 by the second base station 26. The second base station 26 then communicates this SIP invite message 42 to the callee mobile telephone 34 over the wireless network and the callee mobile telephone 34 returns a SIP okay message 44 to the second base station 26.


The SIP okay message format is shown at 44 and includes a caller identifier (ID), a callee ID, a call ID, a callee IP address identifier and a callee UDP port identifier. The callee IP address identifier is the IP address of the second base station 26 and the callee UDP port identifier is the UDP port identifier associated with the callee mobile telephone 34 by the second base station 26. The second base station 26 sends the SIP okay message 44 in an IP transmission through the internet 30 to the RC/CC 22 which communicates the call ID, callee IP address identifier, and callee UDP port identifier contained in the SIP okay message 44 to the media relay 40 to identify to the media relay the IP address and UDP port associated with the callee. In response, the media relay 40 sends a reply message to the RC/CC 22 containing a media relay IP address identifier and caller RTP port identifier of a caller RTP port assigned by the media relay, to which the first base station 24 should direct IP transmissions to the media relay for receipt by the callee mobile telephone 34. In this embodiment, this message includes a media relay IP address identifier of 192.168.1.10 and a caller RTP port identifier (R22125).


The RC/CC 22 transmits a SIP okay message 46, having a format as shown, through the internet 28 to the first base station 24 and the first base station communicates the media relay IP address identifier and the caller RTP port identifier associated with the caller to the caller mobile telephone 32.


The above basic communications for establishing a call between the caller and callee mobile telephones 32 and 34 are described in further detail in Applicant's related International Application No. PCT/CA2007/002150. Of interest in connection with the present disclosure is the following way in which the media relay 40 is configured to permit the caller mobile telephone 32 to move to another geographical location in which a handoff occurs between the first base station 24 and the third base station 50 having an IP address identifier and UDP port identifier different from that of the first base station 24.


When a handoff from the first base station 24 to the third base station 50 occurs, the caller mobile telephone 32 ceases communication with the first base station 24 and establishes communication with the third base station 50. However, since the third base station 50 has a different IP address identifier and UDP port identifier than the first base station 24, the media relay 40 will receive IP transmissions from the third base station 50 identifying the source of the transmissions with a different IP address identifier and UDP port identifier than those associated with the first base station. Normally, the media relay 40 would reject such communications as being from an unknown source, however, due to the configuration of the media relay described below, IP transmissions from the third base station 50 are not rejected and the call can continue uninterrupted. To facilitate this, the media relay 40 is configured with additional functionality beyond that which merely relays communications between the caller and callee.


It is known that in general, a media relay 40 includes a processor 52, memory 54 operable to be written to and read by the processor 52, and program memory 56 containing codes readable by the processor 52 that define program instructions for directing the processor 52 to carry out conventional media relay functions for transferring IP transmissions between the caller and the callee. In order to provide the functionality of the present disclosure, in this embodiment, the media relay 40 is further configured with additional codes shown generally at 58 that direct the processor 52 to carry out the functionality described below and include functionality for configuring the memory 54 to include call records 60.


These additional codes 58 may be stored on a computer readable medium such as a CD-ROM, flash drive, or in memory at a remotely located computer and may be downloaded to the program memory 56 or the media relay 40 in a conventional manner, for example.


Referring to FIG. 2, an exemplary call record is shown generally at 60. Each call record associates session information 62, caller information 64 and callee information 66 for an IP communication session (i.e. call) handled by the media relay 40. The session information 62 includes caller and callee RTP port identifier fields 68 and 70 for storing caller and callee RTP port identifiers identifying caller and callee RTP ports respectively of the media relay 40. In this embodiment, the caller RTP port identifier is R22125 and the callee RTP port identifier is E22123. The session information 62 may also include a caller RTCP port identifier field and a callee RTCP port identifier field, however, these are optional.


The caller information 64 includes a caller IP address identifier field 72 and a caller UDP port identifier field 74 that hold a caller IP address identifier and caller UDP port identifier to which IP transmissions received at the callee RTP port are to be transmitted. In this embodiment, the caller IP address identifier is 192.168.0.20 and the caller UDP port identifier is 12345 and correspond to those of the first base station 24, i.e., that associated with the caller. The caller information 64 further includes a caller sync source (SSRC) identifier field 76 for storing a caller sync source identifier associated with the caller side of the IP communication session. In one embodiment, until a pre-determined packet such as a first packet, for example, is received in connection with the call, this caller SSRC identifier is undefined.


In the embodiment shown, the caller information 64 further includes a packets sent field 78 and a packets received field 80 for holding numbers representing the number of packets sent to and received respectively from the caller although these fields are optional and the contents of these fields may be available from other functions on the media relay 40.


Referring to FIG. 2, the callee information 66 includes a callee IP address identifier field 82 and a callee UDP port identifier field 84 that hold a callee IP address identifier and callee UDP port identifier identifying a callee address and UDP port to which IP transmissions received at the caller RTP port are to be transmitted. In this embodiment, the callee IP address identifier is 192.168.3.10 and the callee UDP port identifier is 33123 and correspond to those of the second base station 26, i.e., that is associated with the callee. The callee information 66 also includes a callee sync source (SSRC) identifier field 86 for storing a callee sync source identifier associated with the callee side of the IP communication session. In one embodiment, this callee SSRC identifier field 86 may be unpopulated until a predefined packet such as the first packet, for example, of the IP transmissions associated with the call is received.


In this embodiment, the callee information 66 also includes a packets sent field 88 and a packets received field 90 for storing numbers indicating the number of packets sent to and received from the caller. The call record 60 is populated with the information shown in FIG. 2 during the course of the normal message exchanges between the RC/CC 22, the caller and callee and the media relay 40 described above that communicate to the caller and callee the media relay IP address and respective RTP port identifiers (R22125 and E22123) to which communications are to be sent.


Referring back to FIG. 1, the additional codes 58 for directing the processor 52 of the media relay 40 to carry out the functions that facilitate uninterrupted transmissions of IP transmissions include codes 100 for effecting a low level processing routine, codes 102 for effecting an authentication routine, codes 104 for effecting a continuity routine, codes 106 for effecting a forwarding routine and codes 108 for effecting error handler routines. The functionality of the low level processing routine codes 100 is not shown but generally relates to processing associated with layers 0 to 4 of the 7 layer ISO IP transmission protocol.


Referring to FIG. 3, the functionality of the authentication routine is shown generally at 102. Before describing this routine, however, please refer to FIG. 4 which describes the generic nature of an IP transmission and the important fields of that transmission for effecting the use of the methods described herein.


In FIG. 4, an IP transmission is shown generally at 110 and includes a PSEUDO header 112, a UDP header 114, a RTP header 116, and a payload 118. The PSEUDO header 112 includes various fields, the most important of which, in this embodiment, are source IP address identifier and destination address identifier fields 120 and 122 respectively. The UDP header 114 includes source port and destination port identifier fields 124 and 126 and the RTP header 116 includes a SSRC identifier field 128. The payload 118 includes data representing, in this embodiment, audio and/or video data transmitted between the caller and the callee.


Referring back to FIG. 3, the authentication routine 102 is executed in response to receipt of an IP transmission 110 at either the caller RTP port R22125 of the media relay 40 or at the callee RTP port E22123 of the media relay. In response to receipt of an IP transmission 110 at either of these ports, the processor 52 of the media relay 40 is directed to store the source IP address contained in the source IP address identifier field 120, the source port identifier contained in the source port identifier field 124, the destination IP address contained in the destination IP address identifier field 122 and the destination port identifier contained in the destination port identifier field 126 in fields by the same name in a buffer memory 130 addressable by the processor 52. The low level processing routine codes 100 will perform the necessary functions to cleanly extract this information and in this embodiment, the storing of this information is effected by the authentication routine 102, as shown at 129. Alternatively, the low level processing routine codes 100 may store this information directly in the buffer memory 130. It will be appreciated that the buffer memory 130 may include separately addressable fields storing the respective information.


Referring to FIG. 5, upon completion of the execution of block 129 or the low level processing routine codes 100, the call record 60 is updated with the number of packets received as shown at 136 where it is indicated that one packet has been received from the callee, for example.


Referring back to FIG. 3, the authentication routine 102 further includes a block 132 that directs the processor 52 to find a call record such as shown at 60 in the memory 54 by matching the destination port identifier with at least one of the contents of the caller RTP port identifier field 68 and the contents of the callee RTP port identifier field 70 of any of the call records. To do this, the codes in block 132 may direct the media relay processor 52 to scan through all of the caller RTP port identifier fields and callee RTP port identifier fields of all of the call records 60 to find a match with the destination port identifier stored in the buffer memory 130.


Referring to FIG. 3, block 134 directs the processor 52 to invoke an error handler as shown at 108 if no record is found and to proceed to execute the code 104 associated with the continuity routine if a record is found.


Referring to FIG. 6, the continuity routine 104 begins with a first block 140 which directs the processor 52 to determine whether or not the IP transmission 110 has been received at the caller RTP port or the callee RTP port.


The identification of whether or not the IP transmission 110 is from the caller or callee can occur in a number of ways. One way, for example, is for the processor 52 to be responsive to interrupt signals that may be produced by the input/output interface circuitry 41 that physically implements the interface between the media relay 40 and the internet. Since the caller RTP port and callee RTP port have different port identifiers, the input/output interface circuitry 41 may identify the port which has received an IP transmission 110 and cause an interrupt signal and perhaps an interrupt handler (not shown) to be executed by the processor 52 in order to identify the specific port which has received the IP transmission 110.


Alternatively, when the processor 52 identifies the call record 60 by matching the destination port identifier received from the IP transmission 110 with at least one of the caller RTP port identifier and callee RTP port identifier in a call record, the matching RTP port identifier is inherently identified and this information can be used to identify the specific port that has received the IP transmission 110. A flag (not shown) may be set for example, to identify whether the IP transmission 110 is from the caller or callee, depending on whether there is a match of the destination port identifier with the callee or caller RTP identifier. Thus, if there is a match of the destination port identifier with the callee RTP port identifier, then the source must be the caller and if there is a match of the destination port identifier with the caller RTP port identifier, then the source must be the callee.


Thus, if a flag is used, block 140 can simply cause the processor 52 to read the flag to determine whether or not the IP transmission 110 is received from the caller or callee.


Assuming the IP transmission 110 is received from the caller, optionally, block 142 can direct the processor 52 to determine whether or not a pre-determined packet has been received. In this embodiment, the pre-determined packet is the first packet and thus can be determined by simply reading the contents of the packets received field 80 in the caller information 64 of the call record 60 identified at block 132 of the authentication routine 102. Alternatively, the low level processing codes 100 may have previously stored the number of packets received in some other location readable by the processor 52 for use at this stage.


In this embodiment, the first packet received from the caller is the pre-determined packet and thus, when the first packet is received, block 144 directs the processor 52 to store the SSRC identifier received in the IP transmission 110 in the caller SSRC field 76 associated with the caller information 64 of the call record 60 as shown at 146 in FIG. 7. The processor 52 is then directed to the forwarding routine 106. If at block 142, the IP transmission 110 includes a packet that is not the pre-determined packet, in particular, a packet received subsequent to the pre-determined packet, or where there will be no determination as to whether the received packet is a pre-determined packet, block 147 directs the processor 52 to determine whether the caller IP address identifier and caller port identifier in the caller information 64 of the call record 60 match the source IP address identifier and source port identifier received in the IP transmission 110. If so, the IP transmission 110 has been received from the pre-established source (in this embodiment, the first base station 24) and therefore, the processor 52 is directed to the forwarding routine 106.


If at block 147 the caller IP address identifier and caller port identifier do not match the source IP address identifier and source port identifier, then the IP transmission 110 is deemed to be originating from a different source (i.e. the third base station 50) in which case block 148 directs the processor 52 to determine whether or not the IP transmission is associated with the call represented by the call record 60. To do this, block 148 directs the processor 52 to determine whether the SSRC identifier received in the IP transmission 110 matches the caller SSRC identifier stored in the caller sync source field 76 of the call record 60 shown in FIG. 7. If not, the processor 52 is directed to an error handling routine 108.


If the SSRC received in the IP transmission 110 matches the caller SSRC stored in the caller sync source field 76 of the call record 60, block 150 directs the processor 52 to copy the source IP address identifier and source port identifier respectively to the caller IP address identifier and caller UDP port identifier fields 72 and 74 respectively of the call record 60 to update the call record to identify the IP address and UDP port of the third base station 50 as that of the caller, as shown in FIG. 8. The processor 52 is then directed to the call forwarding routine 106.


Thus, in an IP transmission 110 received subsequent to the pre-determined transmission, or where there is no determination of whether the transmission is a pre-determined one, the source IP address identifier and source port identifier from the IP transmission 110 are set as the caller IP address identifier and caller port identifier respectively of the call record 60 when the caller IP address identifier and caller port identifier of the record do not match the source IP address identifier and source port identifier respectively of the IP transmission 110 and the received SSRC in the IP transmission matches the caller SSRC identifier of the call record.


Similarly, blocks 152, 154, 156, 158, and 160 function to perform similar functionality when the destination port identifier in the IP transmission 110 matches the callee RTP port identifier of the identified call record 60. In this case where there is a determination of whether the transmission is a pre-determined one, if the IP transmission is the pre-determined transmission, the SSRC identifier received in the IP transmission 110 is set as the callee SSRC identifier associated with the callee information 66 of the record 60 and if the IP transmission is received subsequent to the pre-determined transmission, or where there is no determination of whether the transmission is a pre-determined one, the source IP address identifier and source port identifier from the IP transmission are set as the callee IP address identifier and callee port identifier respectively of the record when the callee IP address identifier and callee port identifier do not match the source IP address identifier and source port identifier respectively and the received SSRC identifier in the IP transmission matches the callee SSRC identifier.


Referring to FIG. 9, the forwarding routine is shown generally at 106. The forwarding routine includes a first block 170 that directs the processor 52 to again determine whether or not the IP transmission 110 has been received at the caller RTP port or callee RTP port. Again, this may be determined by reading the flag described above or by simply reading a memory location identifying the RTP port that received the IP transmission 110.


If the IP transmission 110 has been received at the caller RTP port, block 172 directs the processor 52 to transmit the IP transmission from the caller RTP port to the callee IP address and callee UDP port identified by the callee IP address identifier and callee UDP port identifier in the call record 60 and to identify the source IP address and source port of the IP transmission as the media relay IP address and callee RTP port. If on the other hand, the IP transmission 110 was received at the callee RTP port, block 174 directs the processor 52 to transmit the IP transmission from the callee RTP port to the caller IP address identified by the caller IP address identifier and caller UDP port identifier stored in the call record 60 and identify the source IP address and source port of the IP transmission as the media relay IP address and caller RTP port. The IP transmission 110 received at either port is thus relayed by the media relay 40 according to the contents of the call record 60 as previously established by the continuity routine 104 shown in FIG. 6.


It will be appreciated that in this embodiment, the IP transmissions 110 received from the caller and from the callee may have different SSRC identifiers. Alternatively, they may have the same SSRC identifiers.

Claims
  • 1. A method of facilitating an uninterrupted internet protocol (IP) communication session involving internet protocol transmissions between a first entity and a second entity, during endpoint changes, the method comprising: maintaining records, each record associating communication session information, first entity information and second entity information for a respective IP communication session conducted through a media relay, wherein: the communication session information includes first and second relay port identifiers identifying a first relay port and a second relay port respectively of the media relay through which IP transmissions of the IP communication session are relayed;the first entity information includes a first entity IP address identifier and a first entity port identifier to which IP transmissions received at the second relay port are transmitted from the media relay, and a first entity session identifier, andthe second entity information includes a second entity IP address identifier and a second entity port identifier to which IP transmissions received at the first relay port are transmitted from the media relay, and a second entity session identifier; andwhen an IP transmission is received at the first relay port or the second relay port: locating one of the records having the first relay port identifier or the second relay port identifier matching a destination port identifier in the IP transmission; and when the one record is located and when the destination port identifier matches the first relay port identifier of the one record: setting a source IP address identifier and a source port identifier from the IP transmission as the first entity IP address identifier and first entity port identifier respectively of the one record when: the first entity IP address identifier and first entity port identifier do not match the source IP address identifier and the source port identifier respectively; and a received IP session identifier in the IP transmission matches the first entity session identifier; andwhen the one record is located and when the destination port identifier matches the second relay port identifier of the one record: setting the source IP address identifier and the source port identifier from the IP transmission as the second entity IP address identifier and second entity port identifier respectively of the one of the records when: the second entity IP address identifier and second entity port identifier do not match the source IP address identifier and the source port identifier respectively; and the received IP session identifier in the IP transmission matches the second entity session identifier.
  • 2. The method of claim 1, further comprising determining whether the IP transmission is a pre-determined transmission and, if so: when the pre-determined IP transmission is received from the first entity: storing the received IP session identifier as the first entity session identifier in the record; andwhen the pre-determined IP transmission is received from the second entity: storing the received IP session identifier as the second entity session identifier in the record.
  • 3. The method of claim 1, further comprising determining whether the IP transmission is a pre-determined transmission and, if so: where the first entity and second entity use a same entity session identifier, storing the received IP session identifier as the first entity session identifier and as the second entity session identifier in the record.
  • 4. The method of claim 1, further comprising: when the IP transmission is received at the first relay port, causing the media relay to forward the IP transmission to the second entity at a second entity IP address and a second entity port identified by the second entity IP address identifier and the second entity port identifier of the record and identifying a source of the IP transmission forwarded to the second entity with the second relay port identifier; andwhen the IP transmission is received at the second relay port, causing the media relay to forward the IP transmission to the first entity at a first entity IP address and a first entity port identified by the first entity IP address identifier and the first entity port identifier of the record and identifying a source of the IP transmission forwarded to the first entity with the first relay port identifier.
  • 5. A media relay apparatus configured to facilitate uninterrupted transmission of internet protocol (IP) transmissions between a first entity and a second entity during endpoint changes, the apparatus comprising: a processor;a network interface in communication with the processor to provide a connection to an IP network;a program memory and a storage memory, the program memory encoded with computer executable codes for directing the processor to: provide a logical input/output interface interacting with the network interface to define a first relay port and a second relay port;maintain records in the storage memory, each of the records having fields associating session information, first entity information and second entity information for a respective IP communication session between the first and second entities wherein: the fields associating session information includes first and second relay port identifier fields identifying the first relay port and the second relay port respectively, through which IP transmissions of the IP communication session are relayed;the first entity information includes a first entity IP address identifier field and a first entity port identifier field to which IP transmissions received at the second relay port are to be transmitted, and a first entity session identifier field; andthe second entity information includes a second entity IP address identifier field and a second entity port identifier field to which IP transmissions received at the first relay port are to be transmitted, and a second entity session identifier field;locate one of the records having first relay port identifier field contents or second relay port identifier field contents matching a destination port identifier in the IP transmission when an IP transmission is received at the first relay port or the second relay port; andwhen the one record is located and when the destination port identifier in the IP transmission matches the first relay port identifier field contents of the one record: storing a source IP address identifier and source port identifier from the IP transmission in the first entity IP address identifier field and the first entity port identifier field respectively when: contents of the first entity IP address field and contents of the first entity port identifier field do not match the source IP address identifier and the source port identifier respectively; anda received IP session identifier in the IP transmission matches contents of the first entity session identifier field;when the one record is located and when the destination port identifier in the IP transmission matches the contents of the second relay port identifier field of the one record, storing the source IP address identifier and the source port identifier from the IP transmission in the second entity IP address identifier field and the second entity port identifier field respectively when: contents of the second entity IP address identifier field and contents of the second entity port identifier field do not match the source IP address identifier and the source port identifier respectively; andthe received IP session identifier in the IP transmission matches contents of the second entity session identifier field.
  • 6. The apparatus of claim 5, wherein the program memory is further encoded with computer executable codes for directing the processor to: determine whether the IP transmission is a pre-determined transmission and, if so: when the pre-determined IP transmission is received from the first entity: store the received IP session identifier in the first entity session identifier field in the one record; andwhen the pre-determined IP transmission is received from the second entity: store the received IP session identifier in the second entity session identifier field in the one record.
  • 7. The apparatus of claim 5, wherein the program memory is further encoded with computer executable codes for directing the processor to: determine whether the IP transmission is a pre-determined transmission and, if so: where the first entity and second entity are configured to use a same session identifier, store the received IP session identifier in the first entity session identifier field and in the second entity session identifier field in the one record.
  • 8. The apparatus of claim 5, wherein the program memory is further encoded with computer executable codes for directing the processor to: when the IP transmission is received at the first relay port: forward the IP transmission to the second entity identified by the contents of the second entity IP address identifier field and the contents of the second entity port identifier field and identify a source of the IP transmission according to the contents of the second relay port identifier field; andwhen the IP transmission is received at the second relay port, forward the IP transmission to the first entity identified by the contents of the first entity IP address identifier field and the contents of the first entity port identifier field and identify a source of the IP transmission according to the contents of the first relay port identifier field.
  • 9. A media relay apparatus configured to facilitate uninterrupted transmission of internet protocol (IP) transmissions between a first entity and a second entity during endpoint changes, the apparatus comprising: a processor;physical connection means for providing physical connections between the processor and an IP network;means for interacting with the physical connection means and the processor for providing a network interface defining first and second relay ports;means for maintaining records in memory, each of the records having means for associating session information, first entity information and second entity information for a respective IP communication session including: means for storing first and second relay port identifiers identifying a first relay port and a second relay port respectively of the network interface, through which IP transmissions of the IP communication session are relayed;means for storing a first entity IP address identifier and a first entity port identifier identifying a first entity port to which IP transmissions received at the second relay port are to be transmitted from the media relay apparatus;means for storing a first entity session identifier;means for storing a second entity IP address identifier and a second entity port identifier identifying a second entity port to which IP transmissions received at the first relay port are to be transmitted from the media relay apparatus; andmeans for storing a second entity session identifier; andmeans for locating one of the records having a first relay port identifier or a second relay port identifier matching a destination port identifier in an IP transmission when the IP transmission is received at a first relay port or a second relay port;means for determining whether the destination port identifier in the IP transmission matches the first relay port identifier of the one record;means for setting the first entity IP address identifier and the first entity port identifier as a source IP address identifier and a source port identifier respectively from the IP transmission when: the first entity IP address identifier and first entity port identifier do not match the source IP address identifier and the source port identifier respectively; anda received IP session identifier in the IP transmission matches the first entity session identifier;means for determining whether the destination port identifier in the IP transmission matches the second relay port identifier of the one record;means for setting the second entity IP address identifier and the second entity port identifier as the source IP address identifier and the source port identifier respectively from the IP transmission when: the second entity IP address identifier and the second entity port identifier do not match the source IP address identifier and the source port identifier respectively; andthe received IP session identifier in the IP transmission matches the second entity session identifier.
  • 10. The apparatus of claim 9, further comprising: means for determining whether the IP transmission is a pre-determined transmission, and if so: means for storing the received IP session identifier as the first entity session identifier when the pre-determined IP transmission is received from the first entity; andmeans for storing the received IP session identifier as the second entity session identifier when the pre-determined IP transmission is received from the second entity.
  • 11. The apparatus of claim 9, further comprising means for determining whether the IP transmission is a pre-determined transmission and means for storing the received session identifier as the first entity session identifier and as the second entity session identifier, when the first entity and second entity use a same session identifier.
  • 12. The apparatus of claim 9, further comprising: means for forwarding the IP transmission to the second entity identified by the second entity IP address identifier and the second entity port identifier and for identifying a source of the IP transmission with the second relay port identifier when the received IP transmission was received at the first relay port; andmeans for forwarding the IP transmission to the first entity identified by the first entity IP address identifier and first entity port identifier and for identifying a source of the IP transmission with the first relay port identifier when the received IP transmission was received at the second relay port.
  • 13. A non-transitory computer readable medium encoded with computer executable codes for directing a processor of a media relay configured to facilitate uninterrupted transmission of internet protocol (IP) transmissions between first and second entities during endpoint changes, the codes comprising computer executable codes for directing the processor to: maintain records, each record associating session information, first entity information and second entity information for a respective IP communication session, the session information including first and second relay port identifiers identifying a first relay port and a second relay port respectively of the media relay, through which IP transmissions of the IP communication session are relayed,the first entity information including a first entity IP address identifier and a first entity port identifier to which IP transmissions received at the second relay port are transmitted from the media relay, and a first entity session identifier, andthe second entity information including a second entity IP address identifier and a second entity port identifier to which IP transmissions received at the first relay port are transmitted from the media relay, and a second entity session identifier; andwhen an IP transmission is received at the first relay port or the second relay port: locate one of the records having the first relay port identifier or the second relay port identifier matching a destination port identifier in the IP transmission; andwhen the one record is located and when the destination port identifier in the IP transmission matches the first relay port identifier of the one record: set a source IP address identifier and a source port identifier from the IP transmission as the first entity IP address identifier and the first entity port identifier respectively of the one of the records when: the first entity IP address identifier and first entity port identifier do not match the source IP address identifier and the source port identifier respectively; anda received IP session identifier in the IP transmission matches the first entity session identifier, andwhen the one record is located and when the destination port identifier in the IP transmission matches the second relay port identifier of the one record: set the source IP address identifier and the source port identifier from the IP transmission as the second entity IP address identifier and the second entity port identifier respectively of the one record when: the second entity IP address identifier and the second entity port identifier do not match the source IP address identifier and the source port identifier respectively; andthe received IP session identifier in the IP transmission matches the second entity session identifier.
  • 14. The computer readable medium of claim 13, further comprising computer executable codes for directing the processor to: store the received IP session identifier as the first entity session identifier in the one record when the IP transmission is a pre-determined transmission and the pre-determined IP transmission is from the first entity; andstore the received IP session identifier as the second entity session identifier in the one record when the IP transmission is a pre-determined transmission and the pre-determined IP transmission is from the second entity.
  • 15. The computer readable medium of claim 13, further comprising computer executable codes for directing the processor to store the received IP session identifier as the first entity session identifier and as the second entity session identifier in the one record when the IP transmission is a pre-determined transmission and the first entity and second entity are configured to use a same session identifier.
  • 16. The computer readable medium of claim 13, further comprising computer executable codes for directing the processor to: cause the media relay to forward the IP transmission to the second entity at a second entity IP address and a second entity port identified by the second entity IP address identifier and second entity port identifier respectively and identify a source of the IP transmission forwarded to the second entity with the second relay port identifier, when the IP transmission was received at the first relay port; andcause the media relay to forward the IP transmission to the first entity at a first entity IP address and a first entity port identified by the first entity IP address identifier and the first entity port identifier respectively and identify the source of the IP transmission forwarded to the first entity with the first relay port identifier, when the IP transmission was received at the second relay port.
  • 17. A method of facilitating an uninterrupted internet protocol (IP) communication session involving internet protocol transmissions, between a first entity and a second entity, during endpoint changes, the method comprising: conducting IP transmissions, of the IP communication session, to and from the first entity through a first relay port;conducting IP transmissions, of the IP communication session, to and from the second entity, through a second relay port;relaying, between the first and second relay ports, IP transmissions, of the IP communication session, between the first and second entities;when an IP transmission is received at the first relay port or the second relay port: locating at least one communication record associated with the IP communication session with which the IP transmission is associated, by locating at least one communication record having a first relay port identifier or a second relay port identifier matching a destination port identifier in the IP transmission; and when the at least one communication record is located and when the destination port identifier in the IP transmission matches the first relay port identifier of the at least one communication record: changing the at least one communication record such that a first entity IP address identifier and a first entity port identifier of the at least one communication record indicates a source IP address identifier and a source port identifier from the IP transmission respectively when: the first entity IP address identifier and first entity port identifier do not match the source IP address identifier and the source port identifier respectively; and an IP communication session identifier in the IP transmission matches a first entity session identifier associated with the at least one communication record; andwhen the at least one communication record is located and when the destination port identifier in the IP transmission matches the second relay port identifier of the at least one communication record: changing the at least one communication record such that a second entity IP address identifier and a second entity port identifier of the at least one communication record indicates the source IP address identifier and the source port identifier from the IP transmission respectively, when: the second entity IP address identifier and second entity port identifier do not match the source IP address identifier and the source port identifier respectively; and the IP communication session identifier in the IP transmission matches a second entity session identifier associated with the at least one communication record.
  • 18. An apparatus configured to facilitate uninterrupted transmission of internet protocol (IP) transmissions between first and second entities during endpoint changes, the apparatus comprising: means for conducting communications to and from a first entity through a first network port;means for conducting communications to and from a second entity through a second network port;means for relaying, between the first and second network ports, causing communications between the first and second entities;means for locating at least one communication record associated with a communications session with which the IP transmission is associated, the locating means including means for finding at least one communication record having a first network port identifier or a second network port identifier matching a destination port identifier in the IP transmission when an IP transmission is received at the first network port or the second network port;means for changing the at least one communication record such that a first entity IP address identifier and a first entity port identifier respectively of the at least one communication record indicates a source IP address identifier and a source port identifier from the IP transmission when: the at least one communication record is located and when the destination port identifier in the IP transmission matches the first network port identifier of the at least one communication record,the first entity IP address identifier and the first entity port identifier do not match the source IP address identifier and the source port identifier respectively; anda received IP session identifier in the IP transmission matches a first session entity identifier associated with the at least one communication record; andmeans for changing the at least one communication record such that a second entity IP address identifier and a second entity port identifier respectively of the at least one communication record indicates the source IP address identifier and the source port identifier from the IP transmission, when: the at least one communication record is located and when the destination port identifier in the IP transmission matches the second network port identifier of the at least one communication record,the second entity IP address identifier and second entity port identifier do not match the source IP address identifier and the source port identifier respectively; andthe received IP session identifier in the IP transmission matches a second entity session identifier associated with the at least one communication record.
  • 19. An apparatus configured to facilitate uninterrupted transmission of internet protocol (IP) transmissions between first and second entities during endpoint changes, the apparatus comprising: a processor circuit configured to: cause communications to and from the first entity to be conducted through a first network port;cause communications to and from the second entity to be conducted through a second network port;cause communications between the first and second entities to be relayed between the first and second network ports;locate at least one communication record associated with a communications session with which the IP transmission is associated, when an IP transmission is received at the first network port or the second network port, the locating including finding at least one communication record having a first network port identifier or a second network port identifier matching a destination port identifier in the IP transmission; andwhen the at least one communication record is located and when the destination port identifier in the IP transmission matches the first network port identifier of the at least one communication record: change the at least one communication record such that a first entity IP address identifier and first entity port identifier respectively of the at least one communication record indicate a source IP address identifier and a source port identifier from the IP transmission when: the first entity IP address identifier and the first entity port identifier do not match the source IP address identifier and the source port identifier respectively; anda received IP session identifier in the IP transmission matches a first entity session identifier associated with the at least one communication record;when the at least one communication record is located and when the destination port identifier in the IP transmission matches a second network port identifier of the at least one communication record, change the at least one communication record such that a second entity IP address identifier and a second entity port identifier respectively of the at least one communication record indicates the source IP address identifier and the source port identifier from the IP transmission, when: the second entity IP address identifier and the second entity port identifier do not match the source IP address identifier and the source port identifier respectively; andthe received IP session identifier in the IP transmission matches a second entity session identifier associated with the at least one communication record.
  • 20. The apparatus of claim 19, wherein the processor circuit is part of a media relay.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/092,831, filed Nov. 27, 2013, which is a continuation of U.S. application Ser. No. 13/496,864, filed Mar. 16, 2012, now U.S. Pat. No. 8,675,566, entitled “Uninterrupted Transmission of Internet Protocol Transmissions During Endpoint Changes”, which is a national phase entry of PCT/CA2009/001317, filed Sep. 17, 2009, all of which are incorporated by reference in their entireties.

US Referenced Citations (537)
Number Name Date Kind
4747124 Ladd May 1988 A
4916491 Katoh Apr 1990 A
4992971 Hayashi Feb 1991 A
5146491 Silver et al. Sep 1992 A
5247571 Kay et al. Sep 1993 A
5303297 Hillis Apr 1994 A
5325421 Hou et al. Jun 1994 A
5359642 Castro Oct 1994 A
5425085 Weinberger et al. Jun 1995 A
5440621 Castro Aug 1995 A
5454030 de Oliveira et al. Sep 1995 A
5469497 Pierce et al. Nov 1995 A
5506893 Buscher et al. Apr 1996 A
5519769 Weinberger et al. May 1996 A
5559871 Smith Sep 1996 A
5590133 Billstrom et al. Dec 1996 A
5602907 Hata et al. Feb 1997 A
5608786 Gordon Mar 1997 A
5621787 McKoy et al. Apr 1997 A
5633913 Talarmo May 1997 A
5661790 Hsu Aug 1997 A
5677955 Doggett et al. Oct 1997 A
5712907 Wegner et al. Jan 1998 A
5719926 Hill Feb 1998 A
5722067 Fougnies et al. Feb 1998 A
5724355 Bruno et al. Mar 1998 A
5726984 Kubler et al. Mar 1998 A
5737414 Walker et al. Apr 1998 A
5742596 Baratz et al. Apr 1998 A
5751961 Smyk May 1998 A
5768521 Dedrick Jun 1998 A
5793762 Penners et al. Aug 1998 A
5799072 Vulcan et al. Aug 1998 A
5802502 Gell et al. Sep 1998 A
5825863 Walker Oct 1998 A
5828740 Khuc et al. Oct 1998 A
5838682 Dekelbaum et al. Nov 1998 A
5845267 Ronen Dec 1998 A
5850433 Rondeau Dec 1998 A
5864610 Ronen Jan 1999 A
5867495 Elliott et al. Feb 1999 A
5883810 Franklin et al. Mar 1999 A
5883891 Williams et al. Mar 1999 A
5889774 Mirashrafi et al. Mar 1999 A
5905736 Ronen et al. May 1999 A
5907547 Foladare et al. May 1999 A
5910946 Csapo Jun 1999 A
5915005 He Jun 1999 A
5915093 Berlin et al. Jun 1999 A
5917899 Moss et al. Jun 1999 A
5923659 Curry et al. Jul 1999 A
5930343 Vasquez Jul 1999 A
5937045 Yaoya et al. Aug 1999 A
5940598 Strauss et al. Aug 1999 A
5953504 Sokal et al. Sep 1999 A
5956391 Melen et al. Sep 1999 A
5970477 Roden Oct 1999 A
5974043 Solomon Oct 1999 A
5991291 Asai et al. Nov 1999 A
5991378 Apel Nov 1999 A
6005870 Leung et al. Dec 1999 A
6005926 Mashinsky Dec 1999 A
6014379 White et al. Jan 2000 A
6021126 White et al. Feb 2000 A
6029062 Hanson Feb 2000 A
6036090 Rahman et al. Mar 2000 A
6052445 Bashoura et al. Apr 2000 A
6058300 Hanson May 2000 A
6069890 White et al. May 2000 A
6073013 Agre et al. Jun 2000 A
6078647 D'Eletto Jun 2000 A
6104704 Buhler et al. Aug 2000 A
6104711 Voit Aug 2000 A
6115737 Ely et al. Sep 2000 A
6128304 Gardell et al. Oct 2000 A
6137869 Voit et al. Oct 2000 A
6141404 Westerlage et al. Oct 2000 A
6151385 Reich et al. Nov 2000 A
6173272 Thomas et al. Jan 2001 B1
6185414 Brunner et al. Feb 2001 B1
6188752 Lesley Feb 2001 B1
6236851 Fougnies et al. May 2001 B1
6240449 Nadeau May 2001 B1
6243689 Norton Jun 2001 B1
6249573 Hudson Jun 2001 B1
6282574 Voit Aug 2001 B1
6298062 Gardell et al. Oct 2001 B1
6298250 Nilsson Oct 2001 B1
6310859 Morita et al. Oct 2001 B1
6327351 Walker et al. Dec 2001 B1
6351464 Galvin et al. Feb 2002 B1
6359880 Curry et al. Mar 2002 B1
6430275 Voit et al. Aug 2002 B1
6434143 Donovan Aug 2002 B1
6445694 Swartz Sep 2002 B1
6507644 Henderson et al. Jan 2003 B1
6553025 Kung et al. Apr 2003 B1
6560224 Kung et al. May 2003 B1
6574328 Wood et al. Jun 2003 B1
6594254 Kelly Jul 2003 B1
6597686 Smyk Jul 2003 B1
6597783 Tada et al. Jul 2003 B1
6603977 Walsh et al. Aug 2003 B1
6636833 Flitcroft et al. Oct 2003 B1
6650641 Albert et al. Nov 2003 B1
6674745 Schuster et al. Jan 2004 B1
6674850 Vu et al. Jan 2004 B2
6724860 Stumer et al. Apr 2004 B2
6744858 Ryan et al. Jun 2004 B1
6760324 Scott et al. Jul 2004 B1
6766159 Lindholm Jul 2004 B2
6772188 Cloutier Aug 2004 B1
6775534 Lindgren et al. Aug 2004 B2
6785266 Swartz Aug 2004 B2
6798767 Alexander et al. Sep 2004 B1
6819929 Antonucci et al. Nov 2004 B2
6873599 Han Mar 2005 B1
6892184 Komem et al. May 2005 B1
6934279 Sollee et al. Aug 2005 B1
6937713 Kung et al. Aug 2005 B1
6947531 Lewis et al. Sep 2005 B1
6954453 Schindler et al. Oct 2005 B1
6961334 Kaczmarczyk Nov 2005 B1
6963557 Knox Nov 2005 B2
6963739 Dorenbosch et al. Nov 2005 B2
6985440 Albert et al. Jan 2006 B1
6993015 Kobayashi Jan 2006 B2
7006508 Bondy et al. Feb 2006 B2
7010727 Stucker Mar 2006 B1
7027564 James Apr 2006 B2
7042985 Wright May 2006 B1
7046658 Kundaje May 2006 B1
7051072 Stewart et al. May 2006 B2
7055174 Cope et al. May 2006 B1
7068668 Feuer Jun 2006 B2
7068772 Widger et al. Jun 2006 B1
7079526 Wipliez et al. Jul 2006 B1
7120682 Salama Oct 2006 B1
7151772 Kalmanek, Jr. et al. Dec 2006 B1
7174156 Mangal Feb 2007 B1
7177399 Dawson et al. Feb 2007 B2
7203478 Benco et al. Apr 2007 B2
7212522 Shankar et May 2007 B1
7218722 Turner et al. May 2007 B1
7277528 Rao et al. Oct 2007 B2
7330835 Deggendorf Feb 2008 B2
7366157 Valentine et al. Apr 2008 B1
7400881 Kallio Jul 2008 B2
7426492 Bishop et al. Sep 2008 B1
7436835 Castleberry et al. Oct 2008 B2
7437665 Perham Oct 2008 B2
7440441 Lakhani et al. Oct 2008 B2
7440442 Grabelsky et al. Oct 2008 B2
7447707 Gaurav et al. Nov 2008 B2
7454200 Cai et al. Nov 2008 B2
7454510 Kleyman et al. Nov 2008 B2
7457865 Ramakrishnan et al. Nov 2008 B2
7477843 Peeters et al. Jan 2009 B1
7486664 Swartz Feb 2009 B2
7486667 Feuer Feb 2009 B2
7486684 Chu et al. Feb 2009 B2
7512117 Swartz Mar 2009 B2
7545761 Kalbag Jun 2009 B1
7565131 Rollender Jul 2009 B2
7573982 Breen et al. Aug 2009 B2
7580886 Schulz Aug 2009 B1
7587036 Wood et al. Sep 2009 B2
7593390 Lebizay Sep 2009 B2
7593884 Rothman et al. Sep 2009 B2
7599944 Gaurav et al. Oct 2009 B2
7639792 Qiu et al. Dec 2009 B2
7644037 Ostrovsky Jan 2010 B1
7647500 Machiraju et al. Jan 2010 B2
7657011 Zielinski et al. Feb 2010 B1
7664495 Bonner et al. Feb 2010 B1
7676215 Chin et al. Mar 2010 B2
7676431 O'Leary et al. Mar 2010 B2
7680114 Yazaki et al. Mar 2010 B2
7680737 Smith et al. Mar 2010 B2
7702308 Rollender Apr 2010 B2
7715413 Vaziri et al. May 2010 B2
7715821 Rollender May 2010 B2
7734544 Schleicher Jun 2010 B2
7738384 Pelletier Jun 2010 B2
7764777 Wood et al. Jul 2010 B2
7764944 Rollender Jul 2010 B2
7765261 Kropivny Jul 2010 B2
7765266 Kropivny Jul 2010 B2
7774711 Valeski Aug 2010 B2
7797459 Roy et al. Sep 2010 B1
7882011 Sandhu et al. Feb 2011 B2
7894441 Yazaki et al. Feb 2011 B2
7899742 Benkert et al. Mar 2011 B2
7907551 Croy et al. Mar 2011 B2
7907714 Baniak et al. Mar 2011 B2
7929955 Bonner Apr 2011 B1
7944909 James May 2011 B2
7950046 Kropivny May 2011 B2
7958233 Gutierrez Jun 2011 B2
7965645 Pelletier Jun 2011 B2
7979529 Kreusch et al. Jul 2011 B2
7995589 Sollee et al. Aug 2011 B2
8024785 Andress et al. Sep 2011 B2
8027333 Grabelsky et al. Sep 2011 B2
8036366 Chu Oct 2011 B2
8041022 Andreasen et al. Oct 2011 B1
8050273 Gass Nov 2011 B2
8060887 Kropivny Nov 2011 B2
8078164 Ganesan Dec 2011 B2
8111690 Hussain et al. Feb 2012 B2
8116307 Thesayi et al. Feb 2012 B1
8125982 Feuer Feb 2012 B2
8127005 Gutierrez Feb 2012 B2
8145182 Rudolf et al. Mar 2012 B2
8161078 Gaurav et al. Apr 2012 B2
8166533 Yuan Apr 2012 B2
8166547 Bevan et al. Apr 2012 B2
8189568 Qiu et al. May 2012 B2
8190739 Gutierrez May 2012 B2
8200575 Torres et al. Jun 2012 B2
8204044 Lebizay Jun 2012 B2
8219115 Nelissen Jul 2012 B1
8223927 Di Serio et al. Jul 2012 B2
8228837 Sheriff et al. Jul 2012 B2
8228897 Mitchell Jul 2012 B2
8243730 Wong et al. Aug 2012 B1
8244204 Chen et al. Aug 2012 B1
8275404 Berger et al. Sep 2012 B2
8300632 Davis et al. Oct 2012 B2
8306063 Erdal et al. Nov 2012 B2
8315521 Leiden et al. Nov 2012 B2
8363647 Fangman et al. Jan 2013 B2
8364172 Guanfeng et al. Jan 2013 B2
8396445 Crawford et al. Mar 2013 B2
8410907 Twitchell, Jr. Apr 2013 B2
8417791 Peretz et al. Apr 2013 B1
8422507 Björsell et al. Apr 2013 B2
8423791 Yu et al. Apr 2013 B1
8427981 Wyss et al. Apr 2013 B2
8437340 James May 2013 B2
8462915 Breen et al. Jun 2013 B2
8468196 Roskind et al. Jun 2013 B1
8493931 Nix Jul 2013 B1
8509225 Grabelsky et al. Aug 2013 B2
8526306 Jungck et al. Sep 2013 B2
8532075 Rassool et al. Sep 2013 B2
8537805 Björsell et al. Sep 2013 B2
8542815 Perreault et al. Sep 2013 B2
8543477 Love et al. Sep 2013 B2
8594298 Klein et al. Nov 2013 B2
8599747 Saleem et al. Dec 2013 B1
8599837 Kyle Dec 2013 B2
8605714 Lebizay Dec 2013 B2
8605869 Mobarak et al. Dec 2013 B1
8607323 Yuan Dec 2013 B2
8611354 Keränen et al. Dec 2013 B2
8625578 Roy et al. Jan 2014 B2
8627211 Kropivny Jan 2014 B2
8630234 Björsell et al. Jan 2014 B2
8634838 Hellwig et al. Jan 2014 B2
8675566 Huttunen Mar 2014 B2
8682919 Golliher Mar 2014 B1
8702505 Kropivny Apr 2014 B2
8713098 Adya et al. Apr 2014 B1
8724643 Feuer May 2014 B2
8749610 Gossweiler et al. Jun 2014 B1
8750290 Vance et al. Jun 2014 B2
8763081 Bogdanovic et al. Jun 2014 B2
8767717 Siegel et al. Jul 2014 B2
8768951 Crago Jul 2014 B2
8774171 Mitchell Jul 2014 B2
8774378 Björsell et al. Jul 2014 B2
8774721 Hertel et al. Jul 2014 B2
8780703 Eidelson et al. Jul 2014 B1
8792374 Jain et al. Jul 2014 B1
8792905 Li et al. Jul 2014 B1
8804705 Fangman et al. Aug 2014 B2
8805345 Ling et al. Aug 2014 B2
8810392 Teller et al. Aug 2014 B1
8819566 Mehin et al. Aug 2014 B2
8837360 Mishra et al. Sep 2014 B1
8838539 Ashcraft et al. Sep 2014 B1
8848887 Willman Sep 2014 B2
8862701 Havriluk Oct 2014 B2
8885609 Nix Nov 2014 B2
8903051 Li et al. Dec 2014 B2
8903360 Celi, Jr. et al. Dec 2014 B2
8909556 Huxham Dec 2014 B2
8938209 Crawford et al. Jan 2015 B2
8938534 Le et al. Jan 2015 B2
8948061 Sridhar Feb 2015 B2
8972612 Le et al. Mar 2015 B2
8982719 Seetharaman et al. Mar 2015 B2
8995428 Haster Mar 2015 B2
9003306 Mehin et al. Apr 2015 B2
9137385 Björsell et al. Sep 2015 B2
9143608 Björsell et al. Sep 2015 B2
9154417 Huttunen Oct 2015 B2
9179005 Perreault et al. Nov 2015 B2
9432830 Lahtiranta et al. Aug 2016 B2
9537762 Perreault et al. Jan 2017 B2
9549071 Björsell et al. Jan 2017 B2
9565307 Björsell et al. Feb 2017 B2
9813330 Perreault et al. Nov 2017 B2
9826002 Perreault et al. Nov 2017 B2
20010027478 Meier et al. Oct 2001 A1
20010052081 McKibben et al. Dec 2001 A1
20020002041 Lindgren et al. Jan 2002 A1
20020018445 Kobayashi Feb 2002 A1
20020051518 Bondy et al. May 2002 A1
20020057764 Salvucci et al. May 2002 A1
20020068545 Oyama et al. Jun 2002 A1
20020116464 Mak Aug 2002 A1
20020122391 Shalit Sep 2002 A1
20020122547 Hinchey et al. Sep 2002 A1
20020141352 Fangman et al. Oct 2002 A1
20020150080 Bhattacharya et al. Oct 2002 A1
20030008635 Ung et al. Jan 2003 A1
20030012196 Ramakrishnan Jan 2003 A1
20030043974 Emerson, III Mar 2003 A1
20030095539 Feuer May 2003 A1
20030121967 Goldberg et al. Jul 2003 A1
20030179747 Pyke et al. Sep 2003 A1
20030200311 Baum Oct 2003 A1
20030211840 Castrogiovanni et al. Nov 2003 A1
20030219103 Rao et al. Nov 2003 A1
20040009761 Money et al. Jan 2004 A1
20040019539 Raman et al. Jan 2004 A1
20040022237 Elliott et al. Feb 2004 A1
20040034793 Yuan Feb 2004 A1
20040157629 Kallio et al. Aug 2004 A1
20040165709 Pence et al. Aug 2004 A1
20040181599 Kreusch et al. Sep 2004 A1
20040202295 Shen et al. Oct 2004 A1
20040203565 Chin et al. Oct 2004 A1
20040203582 Dorenbosch et al. Oct 2004 A1
20040218748 Fisher Nov 2004 A1
20040240439 Castleberry et al. Dec 2004 A1
20040255126 Reith Dec 2004 A1
20050007999 Becker et al. Jan 2005 A1
20050021939 Le et al. Jan 2005 A1
20050025043 Mussman et al. Feb 2005 A1
20050063519 James Mar 2005 A1
20050069097 Hanson et al. Mar 2005 A1
20050083911 Grabelsky et al. Apr 2005 A1
20050094651 Lutz et al. May 2005 A1
20050131813 Gallagher et al. Jun 2005 A1
20050169248 Truesdale et al. Aug 2005 A1
20050171898 Bishop et al. Aug 2005 A1
20050174937 Scoggins et al. Aug 2005 A1
20050177843 Williams Aug 2005 A1
20050188081 Gibson et al. Aug 2005 A1
20050190892 Dawson et al. Sep 2005 A1
20050192897 Rogers et al. Sep 2005 A1
20050192901 McCoy et al. Sep 2005 A1
20050198499 Salapaka et al. Sep 2005 A1
20050202799 Rollender Sep 2005 A1
20050222952 Garrett et al. Oct 2005 A1
20050267842 Weichert et al. Dec 2005 A1
20050287979 Rollender Dec 2005 A1
20060006224 Modi Jan 2006 A1
20060007940 Sollee et al. Jan 2006 A1
20060013266 Vega-Garcia et al. Jan 2006 A1
20060025122 Harris et al. Feb 2006 A1
20060030290 Rudolf et al. Feb 2006 A1
20060036522 Perham Feb 2006 A1
20060072547 Florkey et al. Apr 2006 A1
20060072550 Davis et al. Apr 2006 A1
20060078094 Breen et al. Apr 2006 A1
20060093135 Fiatal et al. May 2006 A1
20060095320 Jones May 2006 A1
20060109960 D'Evelyn et al. May 2006 A1
20060111116 Palmer et al. May 2006 A1
20060116892 Grimes et al. Jun 2006 A1
20060142011 Kallio Jun 2006 A1
20060146797 Lebizay Jul 2006 A1
20060153342 Sasaki Jul 2006 A1
20060160565 Singh et al. Jul 2006 A1
20060177035 Cope et al. Aug 2006 A1
20060189303 Rollender Aug 2006 A1
20060195398 Dheer et al. Aug 2006 A1
20060195584 Baumann Aug 2006 A1
20060205383 Rollender Sep 2006 A1
20060209768 Yan et al. Sep 2006 A1
20060233317 Coster et al. Oct 2006 A1
20060248186 Smith Nov 2006 A1
20060251056 Feuer Nov 2006 A1
20060258328 Godoy Nov 2006 A1
20060264200 Laiho et al. Nov 2006 A1
20060268921 Ekstrom et al. Nov 2006 A1
20060281437 Cook Dec 2006 A1
20070016524 Diveley et al. Jan 2007 A1
20070036139 Patel et al. Feb 2007 A1
20070036143 Alt et al. Feb 2007 A1
20070047548 Yazaki et al. Mar 2007 A1
20070053382 Bevan et al. Mar 2007 A1
20070064919 Chen et al. Mar 2007 A1
20070092070 Croy et al. Apr 2007 A1
20070112964 Guedalia et al. May 2007 A1
20070115935 Qiu et al. May 2007 A1
20070121590 Turner et al. May 2007 A1
20070121593 Vance et al. May 2007 A1
20070121602 Sin et al. May 2007 A1
20070127676 Khadri Jun 2007 A1
20070174469 Andress et al. Jul 2007 A1
20070217354 Buckley Sep 2007 A1
20070220038 Crago Sep 2007 A1
20070253418 Shiri et al. Nov 2007 A1
20070253429 James Nov 2007 A1
20070263609 Mitchell Nov 2007 A1
20070297376 Gass Dec 2007 A1
20080013523 Nambakkam Jan 2008 A1
20080037715 Prozeniuk et al. Feb 2008 A1
20080043718 Chu Feb 2008 A1
20080056235 Albina et al. Mar 2008 A1
20080056243 Roy et al. Mar 2008 A1
20080056302 Erdal et al. Mar 2008 A1
20080063153 Krivorot et al. Mar 2008 A1
20080160953 Mia et al. Jul 2008 A1
20080166999 Guedalia et al. Jul 2008 A1
20080167019 Guedalia et al. Jul 2008 A1
20080167020 Guedalia et al. Jul 2008 A1
20080167039 Guedalia et al. Jul 2008 A1
20080187122 Baker Aug 2008 A1
20080188198 Patel et al. Aug 2008 A1
20080188227 Guedalia et al. Aug 2008 A1
20080205378 Wyss et al. Aug 2008 A1
20080310599 Purnadi et al. Dec 2008 A1
20090003535 Grabelsky et al. Jan 2009 A1
20090012851 Marc Jan 2009 A1
20090017842 Fukasaku Jan 2009 A1
20090028146 Kleyman et al. Jan 2009 A1
20090129566 Feuer May 2009 A1
20090135724 Zhang et al. May 2009 A1
20090135735 Zhang et al. May 2009 A1
20090141883 Bastien Jun 2009 A1
20090213839 Davis et al. Aug 2009 A1
20090214000 Patel et al. Aug 2009 A1
20090238168 Lavoie et al. Sep 2009 A1
20090268615 Pelletier Oct 2009 A1
20090292539 Jaroker Nov 2009 A1
20090296900 Breen et al. Dec 2009 A1
20090325558 Pridmore et al. Dec 2009 A1
20100002701 Hsieh et al. Jan 2010 A1
20100008345 Lebizay Jan 2010 A1
20100039946 Imbimbo et al. Feb 2010 A1
20100083364 Gutierrez Apr 2010 A1
20100086119 De Luca et al. Apr 2010 A1
20100105379 Bonner et al. Apr 2010 A1
20100114896 Clark et al. May 2010 A1
20100115018 Yoon et al. May 2010 A1
20100128729 Yazaki et al. May 2010 A1
20100142382 Jungck et al. Jun 2010 A1
20100150138 Björsell et al. Jun 2010 A1
20100150328 Perreault et al. Jun 2010 A1
20100172345 Björsell et al. Jul 2010 A1
20100177671 Qiu et al. Jul 2010 A1
20100220852 Willman et al. Sep 2010 A1
20100233991 Crawford et al. Sep 2010 A1
20100246589 Pelletier Sep 2010 A1
20100272242 Croy et al. Oct 2010 A1
20100278534 Leiden et al. Nov 2010 A1
20100316195 Di Serio et al. Dec 2010 A1
20110013541 Croy et al. Jan 2011 A1
20110072095 Havriluk Mar 2011 A1
20110122827 Björsell et al. May 2011 A1
20110153809 Ghanem et al. Jun 2011 A1
20110167164 Gutierrez Jul 2011 A1
20110176541 James Jul 2011 A1
20110201321 Bonner Aug 2011 A1
20110208859 Gutierrez Aug 2011 A1
20110235543 Seetharaman et al. Sep 2011 A1
20110255553 Bobba et al. Oct 2011 A1
20110261717 Akuzuwa et al. Oct 2011 A1
20110267986 Grabelsky et al. Nov 2011 A1
20110273526 Mehin et al. Nov 2011 A1
20110276903 Mehin et al. Nov 2011 A1
20110276904 Mehin et al. Nov 2011 A1
20110292929 Haster Dec 2011 A1
20120014383 Geromel et al. Jan 2012 A1
20120089717 Chen Apr 2012 A1
20120096145 Le et al. Apr 2012 A1
20120099599 Keränen et al. Apr 2012 A1
20120113981 Feuer May 2012 A1
20120155333 Yoon et al. Jun 2012 A1
20120170574 Huttunen et al. Jul 2012 A1
20120195236 Knight Aug 2012 A1
20120195415 Wyss et al. Aug 2012 A1
20120227101 Yuan Sep 2012 A1
20120250624 Lebizay Oct 2012 A1
20120259975 Le et al. Oct 2012 A1
20120270554 Hellwig et al. Oct 2012 A1
20120282881 Mitchell Nov 2012 A1
20120314699 Qiu et al. Dec 2012 A1
20130039226 Sridhar Feb 2013 A1
20130097308 Le et al. Apr 2013 A1
20130114589 Fangman et al. May 2013 A1
20130128879 Kyle May 2013 A1
20130148549 Crawford et al. Jun 2013 A1
20130173534 Nelakonda et al. Jul 2013 A1
20130223276 Padgett Aug 2013 A1
20130229950 Björsell et al. Sep 2013 A1
20130237198 Vashi et al. Sep 2013 A1
20130254301 Lin et al. Sep 2013 A1
20130272297 Breen et al. Oct 2013 A1
20130281147 Denman et al. Oct 2013 A1
20130287006 Nix Oct 2013 A1
20130310002 Celi, Jr. et al. Nov 2013 A1
20130318166 Jungck et al. Nov 2013 A1
20130329722 Perrault et al. Dec 2013 A1
20130329864 Björsell et al. Dec 2013 A1
20140010119 Björsell et al. Jan 2014 A1
20140016764 Björsell et al. Jan 2014 A1
20140024367 Björsell et al. Jan 2014 A1
20140101749 Yuan Apr 2014 A1
20140141884 Kropivny May 2014 A1
20140153477 Huttunen et al. Jun 2014 A1
20140211789 Feuer Jul 2014 A1
20140215642 Huxham Jul 2014 A1
20140220944 Balasubramanian Aug 2014 A1
20140244393 Rimmer et al. Aug 2014 A1
20140247730 Thota et al. Sep 2014 A1
20140269624 Khay-Ibbat et al. Sep 2014 A1
20140307858 Li et al. Oct 2014 A1
20140321333 Björsell et al. Oct 2014 A1
20140324969 Riddle Oct 2014 A1
20140337961 Chien et al. Nov 2014 A1
20140337962 Brandstatter Nov 2014 A1
20140349602 Majumdar et al. Nov 2014 A1
20150327320 Huttunen et al. Nov 2015 A1
20150358470 Björsell et al. Dec 2015 A1
20160006882 Björsell et al. Jan 2016 A1
20160028619 Perreault et al. Jan 2016 A1
20170104868 Björsell et al. Apr 2017 A1
20170111265 Perreault et al. Apr 2017 A1
20170126752 Perreault et al. May 2017 A1
20170142256 Björsell et al. May 2017 A1
Foreign Referenced Citations (135)
Number Date Country
PI 0718312-7 Nov 2013 BR
PI 0719682-2 Jan 2014 BR
2 218 216 Oct 1997 CA
2249668 Apr 1999 CA
2 299 037 Aug 2000 CA
2 437 275 Oct 2002 CA
2598200 Feb 2008 CA
2668025 May 2008 CA
2670510 Jun 2008 CA
2 681 984 Oct 2008 CA
2 690 236 Dec 2008 CA
2 659 007 Sep 2009 CA
2732148 Feb 2010 CA
2 778 905 Aug 2010 CA
2812174 Mar 2011 CA
1498029 May 2004 CN
1498482 May 2004 CN
1668137 Sep 2005 CN
1274114 Sep 2006 CN
101005503 Jul 2007 CN
101069390 Nov 2007 CN
101095329 Dec 2007 CN
101584150 Nov 2009 CN
101584166 Nov 2009 CN
101605342 Nov 2009 CN
1498029 May 2010 CN
101772929 Jul 2010 CN
101069390 Dec 2010 CN
102137024 Jul 2011 CN
102457494 May 2012 CN
102484656 May 2012 CN
102572123 Jul 2012 CN
101095329 Oct 2012 CN
101605342 Dec 2012 CN
102633232 Dec 2012 CN
101005503 Jan 2013 CN
101772929 Jul 2014 CN
102457494 Oct 2014 CN
602 01 827 Nov 2005 DE
11 2005 003 306 Jan 2008 DE
601 33 316 Jul 2008 DE
603 17 751 Nov 2008 DE
0 841 832 May 1998 EP
0 841 832 May 1999 EP
1 032 224 Aug 2000 EP
1 032 224 Aug 2000 EP
1 244 250 Sep 2002 EP
1 266 516 Dec 2002 EP
1 362 456 Nov 2003 EP
1 371 173 Dec 2003 EP
1 389 862 Feb 2004 EP
1 411 743 Apr 2004 EP
1 389 862 Nov 2004 EP
1 526 697 Apr 2005 EP
1 362 456 May 2005 EP
1 575 327 Sep 2005 EP
1 610 583 Dec 2005 EP
1 526 697 Mar 2006 EP
1 721 446 Nov 2006 EP
1 829 300 Sep 2007 EP
1 371 173 Nov 2007 EP
1 411 743 Nov 2007 EP
1 362 456 Mar 2008 EP
1 974 304 Oct 2008 EP
1 974 304 Oct 2008 EP
1 610 583 Aug 2009 EP
2 084 868 Aug 2009 EP
2 090 024 Aug 2009 EP
2 127 232 Dec 2009 EP
2 165 489 Mar 2010 EP
2 215 755 Aug 2010 EP
2 227 048 Sep 2010 EP
2 127 232 Mar 2011 EP
2 165 489 Mar 2011 EP
2 311 292 Apr 2011 EP
1 829 300 May 2012 EP
2 449 749 May 2012 EP
2 478 678 Jul 2012 EP
2 215 755 Oct 2012 EP
1 829 300 Nov 2012 EP
2 449 749 Mar 2014 EP
1 266 516 May 2014 EP
2 332 337 Jun 1999 GB
W00200902627 Sep 2009 ID
242009 Jun 2009 IN
292009 Jul 2009 IN
287412 Sep 2017 IN
2011-199384 Oct 2011 JP
10-2009-0086428 Aug 2009 KR
10-2009-0095621 Sep 2009 KR
2009004811 Aug 2009 MX
2009005751 Aug 2009 MX
151991 Jun 2009 SG
152752 Jun 2009 SG
155474 Oct 2009 SG
WO 0150693 Jul 2001 WO
WO 0169899 Sep 2001 WO
WO 0169899 Sep 2001 WO
WO 0180587 Oct 2001 WO
WO 02082728 Oct 2002 WO
WO 02082782 Oct 2002 WO
WO 02082782 Oct 2002 WO
WO 03027801 Apr 2003 WO
WO 2005084002 Sep 2005 WO
WO 2006067269 Jun 2006 WO
WO 2006072099 Jul 2006 WO
WO 2006078175 Jul 2006 WO
WO 2006078175 Jul 2006 WO
WO 2007044454 Apr 2007 WO
WO 2007056158 May 2007 WO
WO 2007087077 Aug 2007 WO
WO 2007087077 Aug 2007 WO
WO 2008027065 Mar 2008 WO
WO 2008052340 May 2008 WO
WO 2008064481 Jun 2008 WO
WO 2008085614 Jul 2008 WO
WO 2008085614 Jul 2008 WO
WO 2008086350 Jul 2008 WO
WO 2008086350 Jul 2008 WO
WO 2008103652 Aug 2008 WO
WO 2008085614 Oct 2008 WO
WO 2008116296 Oct 2008 WO
WO 2008151406 Dec 2008 WO
WO 2008151406 Dec 2008 WO
WO 2009070202 Jun 2009 WO
WO 2009070278 Jun 2009 WO
WO 2010012090 Feb 2010 WO
WO 2011000405 Jan 2011 WO
WO 2011032256 Mar 2011 WO
WO 0189145 Nov 2011 WO
WO 2013013189 Jan 2013 WO
WO 2013120069 Aug 2013 WO
WO 2014066155 May 2014 WO
WO 2014117599 Aug 2014 WO
WO 2014166258 Oct 2014 WO
Non-Patent Literature Citations (420)
Entry
Abrazhevich, Dennis. “Electronic Payment Systems: a User-Centered Perspective and Interaction Design,” Thesis under the auspices of the J.F. Schouten School for User-System Interaction Research, Technische Universiteit Eindhoven, Netherlands, 2004, pp. Cover page-p. 189.
Baker et al., “Cisco Support for Lawful Intercept in IP Networks,” Internet Draft—working document of the Internet Engineering Task Force (IETF), accessible at http://www.ietf.org/ietf/lid-abstracts.txt, Apr. 2003, expires Sep. 30, 2003, pp. 1-15.
F. Baker et al. “RFC 3924—Cisco Architecture for Lawful Intercept in IP Networks.” Oct. 2004.
Bhushan et al., “Federated Accounting: Service Charging and Billing in a Business-to-Business Environment,” 0-7803-6719-7/01, © 2001 IEEE, pp. 107-121.
Cisco, “Lawful Intercept Requirements Summary,” http://www.faqs.org/rfcs/rfc3924.html. Nov. 8, 2006.
DOTS IP Address Validation, “Overview”, http://www.serviceobjects.com/products/dots_ipgeo.asp; printed Jun. 21, 2012.
DOTS Phone Exchange, “Overview”, http://www.serviceobjects.com/demos/PhoneExchangeDemo.asp (URL no longer valid, current URL is http://www.serviceobjects.com/products/phone/phone-exchange); printed Jun. 21, 2012.
ETSI Technical Specification. “Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia Services.” Apr. 2008, 25 pgs, v.2.3.1, France.
Handley, M. et al. “RFC 2543—SIP: Session Initiation Protocol.” Mar. 1999.
IETF ENUM WG R STASTNY OEFEG Informational Numbering for VOIP and Other IP Communications: “Numbering for VIOP and other IP Communications, draft-stastny-enum-numbering-voip-00.txt”, Oct. 1, 2003, pp. 1-43, XP015035676, ISSN: 0000-0004.
IP2Location, http://www.ip2location.com/; printed Jun. 20, 2012.
ETSI TS 122 173 V12.7,0 (Oct. 2014) Digital cellular telecommunications system (Phase 2+); Technical Specification 8.2,2.3—interoperability with PSTN/ISDN and mobile CS Networks, Contents and Forward, pp. 1-9; Sec. 8, pp. 14-17.
Huitema et al., “Architecture for Internet Telephony Service for Residential Customers,” Academic Paper for Bellcore, Mar. 2, 1999, pp. 1-14.
Jajszczyk et al., “Emergency Calls in Flow-Aware Networks,” IEEE Communications Letters, vol. 11, No. 9, Sep. 2007, pp. 753-755.
Ketchpel et al. “U-PAI: A universal payment application interface” Second USENIX Workshop on Electronic Commerce Proceedings, Aug. 1996, pp. 1-17.
Kim et al., “An Enhanced VoIP Emergency Services Prototype,” Proceedings of the 3rd International ISCRAM Conference (B. Van de Walle and M. Turoff, eds.), Newark, NJ (USA), May 2006, pp. 1-8.
Kornfeld et al,, “DVB-H and IP Datacast—Broadcast to Handheld Devices,” IEEE Transactions on Broadcasting, vol. 53, No. 1, Mar. 2007, pp. 161-170.
Kortebi et al., “SINR-Based Routing in Multi-Hop Wireless Networks to Improve VoIP Applications Support,” 1-4244-0667-6/07, © 2007 IEEE, pp. 491-496.
Lee et al., “VoIP Interoperation with KT-NGN,” in The 6th International Conference on Advanced Communication Technology, Technical Proceedings, 2004, pp. 126-128, accompanied by Title and Contents—4 pages.
Lin et al., “Effective VoIP Coil Routng in WLAN and Celular Integration,” IEEE Communications Letters, vol. 9, No. 10, Oct. 2005, pp. 874-376.
Lind AT&T S: “ENUM Call Flows for VoIP Interworking; draft-lind-enum-callflows-03.txt”, Feb. 1, 2002, No. 3, Feb. 1, 2002, pp. 1-17, XP015004214, ISSN: 0000-0004.
List of North American Numbering Plan area codes, http://en.wikipedia.org/wiki/List_of_NANP_area_codes; printed Jun. 20, 2012.
Ma et al., “Realizing MPEG4 Video Transmission Based on Mobile Station over GPRS,” 0-7803-9335-X/05, © 2005 IEEE, pp. 1241-1244.
Mintz-Habib et al., “A VoIP Emergency Services Architecture and Prototype,” {mm2571,asr,hgs,xiaotaow}@cs.columbia.edu, 0-7803-9428-3/05, © 2005 IEEE, pp. 523-528.
Moberg & Drummond, “MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2),” Network Working Group, Request for Comments: 4130, Category: Standards Track, Copyright © The Internet Society Jul. 2005, pp. 1-47.
Munir, Muhammad Farukh, “Study of an Adaptive Scheme for Voice Transmission on IP in a Wireless Networking Environment 802.11e,” Dept. of Networks and Distributed Computing, Ecole Supérieure En Sciences Informatiques (ESSI), Université De Nice, Jun. 2005, (pp. 1-35),—pp. 1-11.
Rosenberg, et al.; “RFC 3261—SIP: Session Initiation Protocol”, Jun. 2002.
Sippy SIP B2BUA. “About Sippy RTPproxy.” http://www.rtpproxy.org. Jul. 15, 2009.
Sripanidkulchai et al., “Call Routing Mangement in Enterprise VoIP Networks,” Copyright 2007 ACM 978-1-59593-788-9/07/0008, 6 pages.
Stallings, William, “The Session Initiation Protocol,” The Internet Protocol Journal, vol. 6, No. 1, Mar. 2003, pp. 20-30.
Thernelius, Fredrik; “SIP, NAT, and Firewalls,” Master's Thesis; ERICSSON, Department of Teleinformatics, May 2000, pp. 1-69.
Townsley, et al.; “RFC 2661—Layer Two Tunneling Protocol ‘L2TP’”, Aug. 1999.
Trad et al., “Adaptive VoIP Transmission over Heterogeneous Wired/Wireless Networks,” V. Roca and F. Rousseau (Eds.): MIPS 2004, LNCS 3311, pp. 25-36, 2004, © Springer-Verlag Berlin Heidelberg 2004.
Wikipedia, “International mobile subscriber identity (IMSI),” http://en.wikipedia.org/wiki/IMSI, Jul. 16, 2013.
Wikipedia , “Roaming,” http://en.wikipedia.org/wiki//Roaming, Jul. 16, 2013.
Yu et al., “Service-Oriented Issues: Mobility, Security, Charging and Billing Management in Mobile Next Generation Networks,” IEEE BcN2006, 1-4244-0146-1/06, © 2006 IEEE, pp. 1-10.
International Search Report and Written Opinion of the International Searching Authority completed Jun. 6, 2008 for related PCT/CA2008/000545.
Intenational Seach Report and Written Opinion of the International Searching Authority completed Feb. 6, 2008 for corresponding PCT/CA2007/001956.
International Preliminary Report on Patentability mailed May 14, 2009 for corresponding PCT/CA2007/001956.
International Search Report and Written Opinion of the International Searching Authority completed Mar. 3, 2008 for related PCT/CA2007/002150.
International Preliminary Report on Patentability mailed Feb. 13, 2009 for related PCT/CA2007/002150.
International Preliminary Report on Patentability and Written Opinion of the International Searching Authority mailed Feb. 10, 2011 for related PCT Application No. PCT/CA2009/001062, Feb. 1, 2011.
Written Opinion and International Search Report completed on Jun. 18, 2010 for related PCT Application No. PCT/CA2009/001317.
International Search Report and Written Opinion mailed on Mar. 12, 2010 for corresponding PCT Application No. PCT/CA2009/001062.
International Preliminary Report on Patentability issued on Sep. 29, 2009 for PCT/CA2008/000545.
International Preliminary Report on Patentability issued on Mar. 20, 2012 for PCT/CA2009/001317.
Extended European Search Report dated Nov. 2, 2012 for European Application No. EP 07 855 436.7.
Extended European Search Report dated Dec. 20, 2013 for European Application No. EP 09 849 358.8.
Extended European Search Report dated Apr. 16, 2014 for European Patent Application No. EP 09 802 316.1 which shares priority of U.S. Appl. No. 61/129,898, filed Jul. 28, 2008 with U.S. Appl. No. 13/056,277, filed Jan. 27, 2011, which is related to captioned U.S. Appl. No. 13/863,306, and cites above-identified reference Nos. 1 and 2.
Supplementary European Search Report for European Application No. 07 816 106, dated Jun. 18, 2012.
Supplementary European Search Report for European Application No. 07 816 106, dated Nov. 2, 2012.
Canadian Office Action dated Jan. 27, 2015 for Canadian Patent Application No. CA 2,681,984.
Chinese Office Action dated Mar. 24, 2011 for Chinese Patent Application No. CN 200780049791.5.
Chinese Office Action dated Jun. 23, 2011 for Chinese Patent Application No. CN 200780049136.X.
Indonesian Examination Report dated Jul. 5, 2012 for Indonesian Patent Application No. W-00200901414.
Indonesian Examination Report dated Feb. 8, 2013 for Indonesian Patent Application No. W-00200901165.
Mexican Exam Report dated Jul. 11, 2011 for Mexican Patent Application No. MX/a/2009/004811.
Mexican Notice of Allowance dated Sep. 2, 2011 for Mexican Patent Application No. MX/a/2009/005751.
Canadian Office Action dated Nov. 18, 2015 for Canadian Patent Application No. CA 2,681,984.
Canadian Office Action dated Dec. 1, 2015 for Canadian Patent Application No. CA 2,812,174.
Canadian Office Action dated Jan. 22, 2016 for Canadian Patent Application No. CA 2,916,220.
First Examination Report dated Dec. 9, 2015, India Patent Application No. 1047/MUMNP/2009, corresponding to U.S. Appl. No. 14/802,929, which is related to subject U.S. Appl. No. 14/802,872.
European Examination Report dated Nov. 26, 2015 for European Patent Application No. EP 07 816 106.4 which claims priority of U.S. Appl. No. 60/856,212, filed Nov. 2, 2006.
Canadian Office Action dated Mar. 3, 2016 for Canadian Patent Application No. CA 2,670,510.
Document Title: Complaint for Patent Infringement [Jury Demand]; Case Title: VoIP-Pal.com, Inc., a Nevada corporation, Plaintiff, v. Verizon Wireless Services, LLC, a Delaware limited liability corporation; Verizon Communications, Inc., a Delaware corporation; AT&T, Inc., a Delaware corporation; AT&T Corp., a Delaware corporation; and Does I through X, inclusive, Defendants; Case No. 2:16-CV-00271; Court: United States District Court District of Nevada. Attachments: Table of Exhibits; Exhibit A; Exhibit B; Exhibit C; Exhibit D; Exhibit E; Chart 1 to Exhibit E; Chart 2 to Exhibit E; Chart 3 to Exhibit E; Chart 4 to Exhibit E; Chart 5 to Exhibit E; Chart 6 to Exhibit E; Exhibit F; Chart 1 to Exhibit F; Chart 2 to Exhibit F; Chart 3 to Exhibit F; Chart 4 to Exhibit F; Chart 5 to Exhibit F; Chart 6 to Exhibit F; Exhibit G; Exhibit H; and Addendum 1 to Exhibit H.
Document Title: Complaint for Patent Infringement [Jury Demand]; Case Title: VoIP-Pal.com, Inc., a Nevada corporation, Plaintiff, v. Apple, Inc., a California corporation; Defendants; Case No. 2:16-CV-00260; Court: United States District Court District of Nevada. Attachments: Table of Exhibits; Exhibit A; Exhibit B; Exhibit C; Exhibit D; Chart 1 to Exhibit D; Chart 2 to Exhibit D; Chart 3 to Exhibit D; Chart 4 to Exhibit D; Exhibit E; Exhibit F; and Addendum 1 to Exhibit F.
Letter dated Nov. 30, 2015, from VoIP-Pal.com Inc. giving notice and inviting the company listed herein below to contact VoIP-Pal.com about U.S. Pat. Nos. 9,179,005 and 8,542,815 and related patents listed in the accompanying Attachment A. Sent to the following company: Apple Inc. in the U.S.
Letter dated Dec. 1, 2015, from VoIP-Pal.com Inc. giving notice and inviting the company listed herein below to contact VoIP-Pal.com about U.S. Pat. Nos. 9,179,005 and 8,542,815 and related patents listed in the accompanying Attachment A. Sent to the following company: Verizon Communications in the U.S.
Letters dated Dec. 18, 2015, from VoIP-Pal.com Inc. giving notice and inviting the companies listed herein below to contact VoIP-Pal.com about U.S. Pat. No. 9,179,005 and U.S. Pat. No. 8,542,815 and related patents listed in the accompanying Attachment A. (Please Note: Attachment A is attached here only to the first letter.) Sent to the following companies: Airtel in India; Alcatel-Lucent in France; Avaya Inc. in the U.S.; AT&T in the U.S.; Blackberry in Canada; Cable One in the U.S.; CenturyLink in the U.S.; Charter Communications in the U.S.; Cisco Systems in the U.S.; Comcast in the U.S.; Cox Communications in the U.S.; Cricket Wireless in the U.S.; Facebook in the U.S.; Facebook in the U.S.; Freedom Pop in the U.S.; Frontier Communications in the U.S.; Google Inc. in the U.S.; HP in the U.S.; Juniper Networks in the U.S.; LoopPay, Inc. in the U.S.; Magic Jack in the U.S.; MetroPCS in the U.S.; Ooma in the U.S.; PayPal in the U.S.; Republic Wireless in the U.S.; Rok Mobile in the U.S.; Samsung Electronics-America in the U.S.; ShoreTel, Inc. in the U.S.; Siemens in Germany; Skype USA in the U.S.; Sprint in the U.S.; Square Cash in the U.S.; Suddenlink Communications in the U.S.; Talktone in the U.S.; Tango in the U.S.; Time Warner Cable in the U.S.; T-Mobile in the U.S.; Twitter in the U.S.; US Cellular in the U.S.; Venmo in the U.S.; Virgin Mobile USA in the U.S.; Vodafone in the UK; and Vonage in the U.S.
Letters dated Jan. 4, 2016, from VoIP-Pal.com Inc. giving notice and inviting the companies listed herein below to contact VoIP-Pal.com about U.S. Pat. No. 9,179,005 and U.S. Pat. No. 8,542,815 and related patents listed in the accompanying Attachment A. (Please Note: Attachment A is attachment here only the fist letter.) Sent to the following companies: Rogers Communications Inc. in Canada; Shaw Cable in Canada; Walmart in Alaska; and Wind Mobile in Canada.
Letters dated Jan. 21, 2016, from VoIP-Pal.com Inc. giving notice and inviting the companies listed herein below to contact VoIP-Pal.com about U.S. Pat. No. 9,179,005 and U.S. Pat. No. 8,542,815 and related patents listed in the accompanying Attachment A. (Please Note: Attachment A is attachment here only the fist letter.) Sent to the following companies: Alibaba (China) Co., Ltd in China; Comwave Telecommunications in Canada; and Intel in the U.S.
Letters dated Feb. 2, 2016, from VoIP-Pal.com Inc. giving notice and inviting the companies listed herein below to contact VoIP-Pal.com about U.S. Pat. No. 9,179,005 and U.S. Pat. No. 8,542,815 and related patents listed in the accompanying Attachment A. (Please Note: Attachment A is attachment here only the fist letter.) Sent to the following companies: Netflix Inc. in the U.S.; Skype Technologies in the U.S.; and WhatsApp Inc. in the U.S.
Document Title: United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. VoIP-Pal.com Inc., Patent Owner; Case No. TBD, U.S. Pat. No. 9,179,005; Petition for Inter Partes Review of U.S. Pat. No. 9,179,005; dated Jun. 15, 2016. 70 sheets.
Document Title: In the United States Patent and Trademark Office; Petition for Inter Partes Review Pursuant to 37 C.F.R. §42.100 ET SEQ.; In re U.S. Pat. No. 9,179,005; Currently in Litigation Styled: VoIP-Pal.com, Inc. v. Apple Inc., Case No. 2:16-cv-00260-RFB-VCF; Issued: Nov. 3, 2015; Application Filed: Aug. 13, 2013; Applicant: Clay Perreault, et al.; Title: Producing Routing Messages for Voice Over IP Communications; Declaration of Henry H. Houh, PhD; Signed Jun. 14, 2016. 143 sheets.
Document Title: United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. VoIP-Pal.com Inc., Patent Owner; Case No. TBD, U.S. Pat. No. 8,542,815; Petition for Inter Partes Review of U.S. Pat. No. 8,542,815; dated Jun. 15, 2016. 67 sheets.
Document Title: In the United States Patent and Trademark Office; Petition for Inter Partes Review Pursuant to 37 C.F.R. §42.100 ET SEQ.; In re U.S. Pat. No. 8,542,815; Currently in Litigation Styled: VoIP-Pal.com, Inc. v. Apple Inc., Case No. 2:16-cv-00260-RFB-VCF; Issued: Sep. 24, 2013; Application Filed: Nov. 1, 2007; Applicant: Clay Perreault, et al.; Title: Producing Routing Messages for Voice Over IP Communications; Declaration of Henry H. Houh, PhD; Signed Jun. 14, 2016. 143 sheets.
Document Title: Petition for Inter Partes Review of U.S. Pat. No. 8,542,815; United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Unified Patents Inc., Petitioner v. VoIP-Pal.com Inc., Patent Owner; IPR2016-01082; U.S. Pat. No. 8,542,815; Producing Routing Messages for Voice Over IP Communications; dated May 24, 2016. 64 sheets.
Document Title: Declaration of Michael Caloyannides; United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Unified Patents Inc., Petitioner v. VoIP-Pal.com Inc., Patent Owner; IPR2016-01082; U.S. Pat. No. 8,542,815; Producing Routing Messages for Voice Over IP Communications; Signed May 23, 2016; filed May 24, 2016. 84 sheets.
Document Title: Public Switched Telephone Networks: A Network Analysis of Emerging Networks; Daniel Livengood, Jijun Lin and Chintan Vaishnav; Engineering Systems Division; Massachusetts Institute of Technology; Submitted May 16, 2006; to Dan Whitney, Joel Moses and Chris Magee. 27 sheets.
Document Title: A Brief History of VoIP; Document One—The Past; Joe Hallock; joe@sitedifference.com; date on cover page: Nov. 26, 2004; Evolution and Trends in Digital Media Technologies—COM 538; Masters of Communication in Digital Media; University of Washington. 17 sheets.
Document Title: Petitioner's Voluntary Interrogatory Responses; United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Unified Patents Inc., Petitioner v. VoIP-Pal.com Inc., Patent Owner; IPR20161082; U.S. Pat. No. 8,542,815; Producing Routing Messages for Voice Over IP Communications; Signed and Filed not later than May 24, 2016. 8 sheets.
Document Title: VoIP-PAL, The World is Calling!, “Over $7 Billion in Lawsuits File by Voip-Pal.com Inc. vs Apple, Verizon and AT&T for Various Patent Infringements,” Business Wire®, A Berkshire Hathaway Company, Feb. 11, 2016. 2 sheets.
Technical Report, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study into routeing of MT-SMs via the HPLMN (Release 7),” 3GPP TR 23.840 V0.1.0 (Feb. 2006), 13 pages.
Canadian Office Action dated Jun. 8, 2016 for Canadian Patent Application No. CA 2,916,217.
Communication for European Patent Application No. EP 07 816 106.4—Invitation pursuant to Article 94(3) and Rule 71(1) EPC dated Apr. 15, 2016. All pages.
Decision: Denying Institution of Inter Partes Review, 37 C.F.R. § 42.108, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Unified Patents Inc., Petitioner v, VoIP-Pal.com Inc., Patent Owner, Case IPR2016-01082, U.S. Pat. No. 8,542,815 B2, Paper 8, Entered: Nov. 18, 2016.
Decision: Institution of Inter Partes Review, 37 C.F.R. § 42.108, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. VoIP-Pal.com Inc., Patent Owner, Case IPR2016-01201, U.S. Pat. No. 8,542,815 B2, Paper 6, Entered: Nov. 21, 2016.
Decision: Institution of Inter Partes Review, 37 C.F.R. § 42.108, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. VoIP-Pal.com Inc., Patent Owner, Case IPR2016-01198, U.S. Pat. No. 9,179,005 B2, Paper 6, Entered: Nov. 21, 2016.
Scheduling Order: United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. VoIP-pal.com Inc., Patent Owner, Cases IPR2016-01201, IPR2016-01198, U.S. Pat. No. 8,542,815 B2, U.S. Pat. No. 9,179,005 B2, Paper 7, Entered: Nov. 21, 2016.
Canadian Office Action dated Aug. 16, 2016 for Canadian Patent Application No. 2,681,984.
European Examination Report dated Aug. 29, 2016 for European Patent Application No. EP 07 855 436.7.
Communication under Rule 71(3) EPC—Intention to Grant—dated Oct. 14, 2016 for European Patent Application No. EP 07 816 106.4.
Patent Owner's Preliminary Response, Case No. IPR2016-01082, U.S. Pat. No. 8,542,815, Unified Patents Inc., Petitioner, v. Voip-Pal.com Inc., Patent Owner, Filing Date: Aug. 26, 2016, 80 pages.
Voip-Pal.com, Inc. Exhibit 2001, Comparison of portions of Petition with portions of Declaration, IPR2016-01082, Unified Patents v. Voip-Pal, Filing Date: Aug. 26, 2016, 9 pages.
Patent Owner's Preliminary Response to Petition for Inter Partes Review, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, Apple Inc., Petitioner, v. Voip-Pal.com Inc., Patent Owner, Filing Date: Sep. 19, 2016, 74 pages.
Voip-Pal.com, Inc. Exhibit 2001, Comparison of Petition (Ground 1) with Petition (Ground 2), IPR2016-01201, Apple v. Voip-Pal, Filing Date: Sep. 19, 2016, 19 pages.
Patent Owner's Preliminary Response to Petition for Inter Partes Review, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, Apple Inc., Petitioner, v. Voip-Pal.com Inc., Patent Owner, Filing Date: Sep. 21, 2016, 74 pages.
Voip-Pal.com, Inc. Exhibit 2001, Comparison of Petition (Ground 1) with Petition (Ground 2), IPR2016-01198, Apple v. Voip-Pal, Filing Date: Sep. 21, 2016, 21 pages.
Complaint for Patent Infringement, United States District Court, District of Nevada, Case No. 2:16-cv-2338, Voip-Pal.com, Inc., a Nevada corporation, Plaintiff v. Twitter, Inc., a California corporation, Defendant, Filed Oct. 6, 2016, 8 pages.
Civil Docket for Case #: 2:16-cv-02338-RFB-CWH, United States District Court, District of Nevada (Las Vegas), Voip-Pal.com, Inc. v. Twitter, Inc., Date Filed: Oct. 6, 2016, 2 pages.
Table of Exhibits, Case 2:16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, 1 page.
Exhibit A, Case 2:16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, U.S. Pat. No. 8,542,815 B2, Issued Sep. 24, 2013, to Clay Perrault et al., 60 pages.
Exhibit B, Case 2:16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, U.S. Pat. No. 9,179,005 B2, Issued Nov. 3, 2015, to Clay Perrault et al., 63 pages.
Exhibit C, Case 2.16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, Letter dated Dec. 18, 2015 giving notice of U.S. Pat. No. 8,542,815 B2; U.S. Pat. No. 9,179,005 B2; and related Patents listed in Attachment A, 4 pages.
Exhibit D, Case 2:16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, Asserted Claims and Infringement Conditions, United States District Court, District of Nevada, Voip-Pal.com, Inc., a Nevada corporation, Plaintiff v. Twitter, Inc., a California corporation, Defendants, 6 pages.
Chart 1 to Exhibit D, Case 2.16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, Chart 1, Asserted Claims and Infringement Conditions Concerning U.S. Pat. No. 8,542,815, United States District Court, District of Nevada, Voip-Pal.com, Inc., a Nevada corporation, Plaintiff v. Twitter, Inc., a California corporation, Defendants, 20 pages.
Chart 2 to Exhibit D, Case 2:16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, Chart 2, Asserted Claims and Infringement Conditions Concerning U.S. Pat. No. 9,179,005, United States District Court, District of Nevada, Voip-Pal.com, Inc., a Nevada corporation, Plaintiff v. Twitter, Inc., a California corporation, Defendants, 28 pages.
Exhibit E, Case 2:16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, VPLM Active U.S. Patent Matters as of Oct. 1, 2016, 2 pages.
Exhibit F, Case 2:16-cv-02338-RFB-CWH, Filed Oct. 6, 2016, Twitter Royalty Monetization Analysis Overview, 4 pages.
Patent Owner Response to Petition, Apples Inc., Petitioner, v. Voip-Pal.com. Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 5,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Filed: Feb. 10, 2017, 76 pages.
Patent Owner Updated Exhibity List, Apples Inc., Petitioner, v. Voip-Pal.com. Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Filed: Feb. 10, 2017, 6 pages.
Voip-Pal Ex. 2002, IPR2016-01201, “Declaration of Ryan Thomas in Support of Pro HAC Vice Motion, ” Apples Inc., Petitioner, v. Voip-Pal.com. Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 20, 2017, 4 pages.
Voip-Pal Ex. 2003, IPR2016-01201, “Technical Review of Digifornica VoIP System” DIGIFONICA, Global Telephone Solutions, Author: John Rutter, Stuart Gare, Version V0.7 (Draft), Date: May 7, 2005, 35 pages.
Voip-Pal Ex. 2004, IPR2016-01201, Memo—“Subject: Smart 421 Contract signed and Faxed,” From: Clay S. Perreault, Date: Jun. 6. 2005, 8:53 AM, To: Steve Nicholson, et al., 2 pages.
Voip-Pal Ex. 2005, IPR2016-01201, Memo—“Subject: Digifonica TEchnology review,” From: Clay Perreault, Date: Jun. 6, 2005, 5:37 PM; To: John Rutter, et al., 5 pages.
Voip-Pal Ex. 2006, IPR2016-01201, Memo—“Subject: Re: Sample code for review Next document upload complete,” From: Clay Perreault, Date: Jun. 15, 2005, 3:28 PM, To: John Rutter, et al., 3 pages.
Voip-Pal Ex. 2007, IPR2016-01201, DigiFonica International Inc Memo—“[Fwd: Digifonica Technical Review—draft report],” From Clay Perreault, To: Rod Thomson, et al., Tue, Jul. 5, 2005 at 4:45 PM, 2 pages.
Voip-Pal Ex. 2008, IPR2016-01201, John Rutter—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.Com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 31, 2017, 4 pages.
Voip-Pal Ex. 2009, IPR2016-01201, Stuart Gare—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 2, 2017, 4 pages.
Voip-Pal Ex. 2010, IPR2016-01201, Pentti Kalevi Huttunen—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 3, 2017, 4 pages.
Voip-Pal Ex. 2011, IPR2016-01201, Ryan Purita—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 31, 2017, 3 pages.
Voip-Pal Ex. 2012, IPR2016-01201, Johan Emil Viktor Björsell—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 9, 2017, 9 pages.
Voip-Pal Ex. 2013, IPR2016-01201, Clay Perreault—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 8, 2017, 6 pages.
Voip-Pal Ex. 2014, IPR2016-01201, RBR Source Code, Version 361, “call_e164.class.php RBR Version 361, Jun. 6, 2005 09:22:59,” 45 pages.
Voip-Pal Ex. 2015, IPR2016-01201, RBR Source Code Log for Trunk Directory, “r1879 | cdelalande | Oct. 31, 2006 17:07:46-0800 (Tue, Oct. 31, 2006) | 3 lines,” 56 pages.
Voip-Pal Ex. 2016, IPR2016-01201, William Henry Mangione-Smith—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 10, 2017, 82 pages.
Voip-Pal Ex. 2017, IPR2016-01201, DF DigiFonica International Inc Memo—“notes from your presentation, 1 message” From Konstantin Kropivny, To: Emil Björsell, Tue, Jun. 14, 2005 at 7:33PM, 4 pages.
Voip-Pal Ex. 2018, IPR2016-01201, David Terry—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 8, 2017, 5 pages.
Voip-Pal Ex. 2019, IPR2016-01201, DR DigiFonica International Inc Memo—“Software release 10:30 am PST—11:00am PST for Aug. 25, 2005. 1 message” From Samantha Edwards, To: everyone@digifonica.com, Wed., Aug. 24, 2005 at 4:02 PM, 8 pages.
Voip-Pal Ex. 2020, IPR2016-01201, “Next Generation Networks—A Migration Path Digifonica Voice Over IP Technologies. Technology Overview DRAFT Jun. 3, 2005, Not for Distribution,” by Clay S Perreault, CEO/CTO, Digifonica International Ltd, Gibraltar, 45 pages.
Voip-Pal Ex. 2021, IPR2016-01201, DF DigiFonica International Inc Memo—“Software roll out for supermodes. Salm Rev 341, RBR Rev 341 added, 1 message” Fuad A. To: E. Björsell, Tue, May 31, 2005 at 1:13 PM, 1 page.
Voip-Pal Ex. 2022, IPR2016-01201, DF DigiFonica International Inc Memo—“Salm Rev 341, RBR Rev 341, 2 message” Emil Björsell To: Fuad, et al., Tue, May 31, 2005 at 2:38 and 2:44 PM, 1 page.
Voip-Pal Ex. 2023, IPR2016-01201, DF DigiFonica International Inc Memo—“Software roll out of supernodes. RBR Roll out Rev 353 added, 1 message” Fuad A. To: E. Björsell, Thu, Jun. 2, 2005 at 1:12 PM, 1 page.
Voip-Pal Ex. 2024, IPR2016-01201, DF DigiFonica International Inc Memo—“Software roll out for supernodes. RBR Roll out Rev 358 added, 1 message” Fuad A. To: E. Björsell, Sun, Jun. 5, 2005 at 1:18 PM, 1 page.
Voip-Pal Ex. 2025, IPR2016-01201, DF DigiFonica International Inc Memo—“Software roll out for supernodes. RBR Roll out Rev 361 updated, 1 message” Fuad A. To: E. Björsell, Mon., Jun. 6, 2005 at 9:26 AM, 1 page.
Voip-Pal Ex. 2026, IPR2016-01201, DF DigiFonica International Inc Memo—“RBR Roll out Rev 361, 1 message” David Terry To: Fuad, et al., Mon., Jun. 6, 2005 at 9:33 AM, 1 page.
Voip-Pal Ex. 2027, IPR2016-01201, DF DigiFonica International Inc Memo—“RBR Roll out Rev 361, 1 message” Emil Björsell To: Fuad, et al., Mon., Jun. 6, 2005 at 11:33 AM, 1 page.
Voip-Pal Ex. 2030, IPR2016-01201, DF DigiFonica International Inc Memo—“Software roll out for supermodes. RBR Rev 541 updated, 1 message” Fuad A. To: E. Björsell, Thu, Aug. 4, 2005 at 11:57 AM, 1 page.
Voip-Pal Ex. 2031, IPR2016-01201, DF DigiFonica International Inc Memo—“RBR Rev 541, 1 message” David Terry To: Fuad, et al., Thu, Aug. 4, 2005 at 1:58 PM, 1 page.
Voip-Pal Ex. 2032, IPR2016-01201, DF DifiFonica International Inc Memo—“RBR Rev 541, 1 message” Emil Björsell To: Fuad, et al., Thu, Aug. 4, 2005 at 3:59 PM, 1 page.
Voip-Pal Ex. 2033, IPR2016-01201, DR DigiFonica International Inc Memo—“Software roll out for supermodes. RBR Roll out Rev 554 added, 1 message” Fuad A. To: Emil Björsell, Mon, Aug. 8, 2005 at 10:55 AM, 1 page.
Voip-Pal Ex. 2034, IPR2016-01201, DF DigiFonica International Inc Memo—“RBR Roll out Rev 554, 2 messages” David Terry To: Fuad, et al., Mon, Aug. 8, 2005 at 11:48 AM and 12:00 PM, 1 page.
Voip-Pal Ex. 2035, IPR2016-01201, DF DigiFonica International Inc Memo—“RBR Roll out Rev 554, 1 message” Emil Björsell To: Fuad, et al., Mon, Aug. 8, 2005 at 12:09 PM, 1 page.
Voip-Pal Ex. 2036, IPR2016-01201, DF DigiFonica Internatioanl Inc Memo—“Digifonica: RBR and Salma Deployment,” Samanta Edwards To: everyone@digifonica.com, Mon, Aug. 8, 2005 at 4:12 PM, 4 pages.
Voip-Pal Ex. 2042, IPR2016-01201, DF DigiFonica International Inc Memo—“RBR Roll out Rev 693==>694, 1 message” Chris Huff To: Fuad, et al., Tue, Aug. 23, 2005 at 1:33 PM, 1 page.
Voip-Pal Ex. 2043, IPR2016-01201, “Deposition of Henry H. Houh, Ph.D., vol. I, Taken on Behalf of the Patent Owner,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 25, 2017, 128 pages.
Voip-Pal Ex. 2044, IPR2016-01201, “Deposition of Henry H. Houh, Ph.D., vol. II, Taken on Behalf of the Patent Owner,”Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 26, 2017, 158 pages.
Voip-Pal Ex. 2045, IPR2016-01201, Curriculum Vitae of William Henry Mangione-Smith, Ph.D., 23 pages.
Voip-Pal Ex. 2046, IPR2016-01201, U.S. Pat. No. 3,725,596, dated Apr. 3, 1973, Rodney Robert Maxon et al., 18 pages.
Voip-Pal Ex. 2047, IPR2016-01201, “Merlin® Communications System, Centrex/PBS Connection,”Lucent Technologies, Bell Labs Innovations, © 1984 AT&T, 999-500-138 IS, Issue 1, Mar. 1985, 26 pages.
Voip-Pal Ex. 2048, IPR2016-01201, “Telephone Features,” Quick Reference Guide, Definity, Rockefeller Group, Telecommunications Services, Inc., 2000, 2 pages.
Voip-Pal Ex. 2049, IPR2016-01201, Valdar, Andy, Understanding Telecommunications Networks, ©2006 The Institution of Engineering and Technology, London, UK, Title page, copyright page, pp. 38-39.
Voip-Pal Ex. 2050, IPR2016-01201, Horak, Ray, “Webster's New World® Telecom Dictionary,” © 2008 by Wiley Publishing, Inc., Indianapolis, Indiana, Title page, copyright page, p. 133.
Patent Owner Response to Petition, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Filed: Feb. 10, 2017, 78 pages.
Patent Owner Updated Exhibit List, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Filed: Feb. 10, 2017, 6 pages.
Voip-Pal Ex. 2002, IPR2016-011988, “Declaration of Ryan Thomas in Support of Pro HAC Vice Motion,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 20, 2017, 4 pages.
Voip-Pal Ex. 2003, IPR20116-01198, “Technical Review of Digifonica VoIP System,” DIGIFONICA, Global Telelphone Solutions, Author: John Rutter, Stuart Gare, Version V0.7 (Draft), Date: May 7, 2005, 35 pages.
Voip-Pal Ex. 2004, IPR2016-01198, Memo—“Subject: Smart 421 Contract signed and Faxed,” From: Clay S. Perreault, Date: Jun. 6, 2005, 8:53 AM, To: Steve Nicholson, et al., 2 pages.
Voip-Pal Ex. 2005, IPR2016-01198, Memo—“Subject Digifonica TEchnology review,” From: Clay Perreault, Date: Jun. 6, 2005, 5:37 PM; To: John Retter, et al., 5 pages.
Voip-Pal Ex. 2006, IPR2016-01198, Memo—“Subject: Re: Sample Code for review Next document upload complete,” From: Clay Perreault, Date: Jun. 15, 2005, 3:28 PM, To: John Rutter, et al., 3 pages.
Voip-Pal Ex. 2007, IPR2016-01198, DigiFonica International Inc Memo—“[Fwd: Digifonica Technical Review—draft report],” From Clay Perreault, To: Rod Thomson, et al., Tue, Jul. 5, 2005 at 4:45 PM, 2 pages.
Voip-Pal Ex. 2008, IPR2016-01198, John Rutter—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 31, 2017, 4 pages.
Voip-Pal Ex. 2009, IPR2016-01198, Stuart Gare—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.Com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 2, 2017, 4 pages.
Voip-Pal Ex. 2010, IPR2016-01198, Pentti Kalevi Huttunen—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 3, 2017, 4 pages.
Voip-Pal Ex. 2011, IPR2016-01198, Ryan Purita—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 31, 2017, 3 pages.
Voip-Pal Ex. 2012, IPR2016-01198, Johan Emil Viktor Björsell—“Declaration in Support Patent Owner Response to Inter Partes Petition, ” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 9, 2017, 9 pages.
Voip-Pal Ex. 2013, IPR2016-01198, Clay Perreault—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 8, 2017, 6 pages.
Voip-Pal Ex. 2014, IPR2016-01198, RBR Source Code, Version 361, “call_e164.class.php RBR Version 361, Jun. 6, 2005 09:22:59,” 45 pages.
Voip-Pal Ex. 2015, IPR2016-01198, RBR Source Code Log for Trunk Directory, “r1879 | cdelalande | Oct. 31, 2006 17:07:46-0800 (Tue, Oct. 31, 2006) | 3 lines,” 56 pages.
Voip-Pal Ex. 2016, IPR2016-01198, William Henry Mangione-Smith—“Declaration in Support Patent Owner Response to Inter Partes Petition,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 10, 2017, 96 pages.
Voip-Pal Ex. 2017, IPR2016-01198, DF DigiFonica International Inc Memo—“notes from your presentation, 1 message” From Konstantin Kropivny, To: Emil Björsell, Tue, Jun. 14, 2005 at 7:33PM, 4 pages.
Voip-Pal Ex. 2018, IPR2016-01198, Dave Terry—“Declaration in Support Patent Owner Response to Inter Partes Petition, ” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Feb. 8, 2017. 5 pages.
Voip-Pal Ex. 2019, IPR2016-01198, DF DigiFonica International Inc Memo—“Software release 10:30 am PST—11:00am PST for Aug. 25, 2005. 1 message” From Samantha Edwards, To: everyone@digifonica.com, Wed., Aug. 24, 2005 at 4:02 PM, 8 pages.
Voip-Pal Ex. 2020, IPR2016-01198, “Next Generation Networks—A Migration Path Digifonica Voice Over IP Technologies. Technology Overview, DRAFT Jun. 3, 2005, Not for Distribution,” by Clay S Perreault, CEO/CTO, Digifonica International Ltd, Gibraltar, 45 pages.
Voip-Pal Ex. 2021, IPR2016-01198, DF DigiFonica International Inc Memo—“Software roll out for supernods. Salm Rev 341, RBR 341 added, 1 message” Fuad A. To: E. Björsell, Tue, May 31, 2005 at 1:13 PM, 1 page.
Voip-Pal Ex. 2022, IPR2016-01198, DF DigiFonica International Inc Memo—“Salm Rev 341, RBR Rev 341, 2 message” Emil Björsell To: Fuad, et al., Tue, May 31, 2005 at 2:38 and 2:44 PM, 1 page.
Voip-Pal Ex. 2023, IPR2016-01198, DF DigiFonica International Inc Memo—“Software roll out for supernodes. RBR Roll out Rev 353 added, 1 message” Fuad A. To: E. Bjösell, Thu, Jun. 2, 2005 at 1:12 PM, 1 page.
Voip-Pal Ex. 2024, IPR2016-01198, DF DigiFonica International Inc Memo—“Software roll out for supernodes. RBR Roll out Rev 358 added, 1 message” Fuad A. To: E. Björsell, Sun, Jun. 5, 2005 at 1:18 PM, 1 page.
Voip-Pal Ex. 2025, IPR2016-01198, DF DigiFonica International Inc Memo—“Software roll out for supernods. RBR Roll out Rev 361 updated, 1 message” Fuad A. To: E. Björsell, Mon., Jun. 6, 2005 at 9:25 AM, 1 page.
Voip-Pal Ex. 2026, IPR2016-01198, DF DigiFonica International Inc Memo—“RBR Roll Out Rev 361, 1 message” David Terry To: Fuad, et al., Mon., Jun. 6, 2005 at 9:33 AM, 1 page.
Voip-Pal Ex. 2027, IPR2016-01198, DF DigiFonica International Inc Memo—“RBR Roll Out Rev 361, 1 message” Emil Björsell To: Fuad, et al., Mon., Jun. 6, 2005 at 11:33 AM, 1 page.
Voip-Pal Ex. 2030, IPR2016-01198, DF DigiFonica International Inc Memo—“Software roll out for supernodes. RBR Rev 541 updated, 1 message” Fuad A. To: E. Björsell, Thu, Aug. 4, 2005 at 11:57 AM, 1 page.
Voip-Pal Ex. 2031, IPR2016-01198, DF DigiFonica International Inc Memo—“RBR Rev 541, 1 message” David Terry To: Fuad, et al., Thu, Aug. 4, 2005 at 1:58 PM, 1 page.
Voip-Pal Ex. 2032, IPR2016-01198, DF DigiFonica International Inc Memo—“RBR Rev 541, 1 message” Emil Björsell To: Fuad, et al., Thu, Aug. 4, 2005 at 3:59 PM, 1 page.
Voip-Pal Ex. 2033, IPR2016-01198, DF DigiFonica International Inc Memo—“Software roll out for supernodes. RBR Roll out Rev 554 added, 1 message” Fuad A. To: Emil Björsell, Mon, Aug. 8, 2005 at 10:55 AM, 1 page.
Voip-Pal Ex. 2034, IPR2016-01198, DF DigiFonica International Inc Memo—“RBR Roll out Rev 554, 2 messages” David Terry To: Fuad, et al., Mon, Aug. 8, 2005 at 11:48 AM and 12:00 PM, 1 page.
Voip-Pal Ex. 2035, IPR2016-01198, DF DigiFonica International Inc Memo—“RBR Roll out Rev 554, 1 message” Emil Björsell To: Fuad, et al., Mon, Aug. 8, 2005 at 12:09 PM, 1 page.
Voip-Pal Ex. 2036, IPR2016-01198, DF DigiFonica International Inc Memo—“Digifonica: RBR and Salma Deployment,” Samantha Edwards To: everyone@digifonica.com, Mon, Aug. 8, 2005 at 4:12 PM, 4 pages.
Voip-Pal Ex. 2042, IPR2016-01198, DF DigiFonica International Inc Memo—“RBR Roll out Rev 693==>694, 1 message” Chris Huff To: Fuad, et al., Tue, Aug. 23, 2005 at 1:33 PM, 1 page.
Voip-Pal Ex. 2043, IPR2016-01198, “Deposition of Henry H. Houh, Ph.D., vol. I, Taken on Behalf of the Patent Owner,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201 U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 25, 2017, 128 pages.
Voip-Pal Ex. 2044, IPR2016-01198, “Deposition of Henry H. Houh, Ph.D., vol. II, Taken on Behalf of the Patent Owner,” Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201 U.S. Pat. No. 8,542,815, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Dated: Jan. 26, 2017, 158 pages.
Voip-Pal Ex. 2045, IPR2016-01198, Curriculum Vitae of William Henry Mangione-Smith, Ph.D., 23 pages.
Voip-Pal Ex., 2046, IPR2016-01198, U.S. Pat. No. 3,725,596, Issued Apr. 3, 1973, Rodney Robert Maxon et al., 18 pages.
Voip-Pal Ex. 2047, IPR2016-01198, “Merlin® Communications System, Centrex/PBS Connection,” Lucent Technologies, Bell Labs Innovations,© 1984 AT&T, 999-500-138 IS, Issue 1, Mar. 1985, 26 pages.
Voip-Pal Ex. 2048, IPR2016-01198, “Telephone Features,” Quick Reference Guide, Definty, Rockefeller Group, Telecommunications Services, Inc., 2000, 2 pages.
Voip-Pal Ex. 2049, IPR2016-01198, Valdar, Andy, Understanding Telecommunications Networks, © 2006 The Institution of Engineering and Technology, London, UK, Title plage, copyright page, pp. 38-39.
Voip-Pal Ex. 2050, IPR2016-01198, Horak, Ray, “Webster's New World® Telecom Dictionary,”© 2008 by Wiley Publishing, Inc., Indianapolis, Indiana, Title page, copyright page, p. 133.
Canadian Office Action dated Mar. 31, 2017 for Canadian Patent Application No. CN 2,916,220.
Document Title: United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-pal.com Inc., Patent Owner; Case No. IPR2017-01399-815; U.S. Pat. No. 8,542,815; Petition for Inter Partes Review of U.S. Pat. No. 8,542,815; Dated May 9, 2017, 63 pages.
Petitioner Apple Inc. Exhibit 1003, Case No. IPR2017-01399-815; U.S. Pat. No. 8,542,815: U.S. Pat. No. 7,486,684 to Chu, et al., 59 pages.
Petitioner Apple Inc. Exhibit 1004, Case No. IPR2017-01399-815; U.S. Pat. No. 8,542,815: U.S. Pat. No. 6,760,324 to Scott, et al., 65 pages.
Petitioner Apple Inc. Exhibit 1005, Case No. IPR2017-01399-815; U.S. Pat. No. 8,542,815: Declaration of Henry H. Hough, PhD, 45 pages.
Petitioner Apple Inc. Exhibit 1006, Case No. IPR2017-01399-815; U.S. Pat. No. 8,542,815: U.S. Publication No. 2002/0122547 to Hinchey et al., 21 pages.
Document Title: United States Patent and Trademark Office: Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Patent of Voip-Pal.com Inc., Patent Owner; Case No. IPR2017-01398-005; U.S. Pat. No. 9,179,005; Petition for Inter Partes Review of U.S. Pat. 9,179,005; Dated May 9, 2017, 54 pages.
Petitioner Apple Inc. Exhibit 1006, Case No. IPR2017-01398-005; U.S. Pat. No. 9,179,005; U.S. Pat. No. 7,486,684 to Chu, et al., 59 pages.
Petitioner Apple Inc. Exhibit 1007, Case No. IPR2017-01398-005; U.S. Pat. No. 9,179,005: U.S. Pat. No. 6,760,324 to Scott, et al., 65 pages.
Petitioner Apple Inc. Exhibit 1008, Case No. IPR2017-01398-005; U.S. Pat. No. 9,179,005: Declaration of Henry H. Hough, PhD, 41 pages.
Petitioner Apple Inc. Exhibit 1009, Case No. IPR2017-01398-005; U.S. Pat. No. 9,179,005: U.S. Publication No. 200/0122547 to Hinchey et al., 21 pages.
Document Title: In the United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner v. Digifonica (International) Limited Patent Owner, Case No. IPR2017-01382; U.S. Pat. No. 8,542,815; Petition for Inter Partes Review of U.S. Pat. No. 8,542,815; Dated May 8, 2017, 84 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner v. Digifonica (International) Limited Patent Owner, U.S. Pat. No. 8,542,815, Inter Partes Review No. IPR2017-01382; Declaration of James Bress in Support of Petition for Inter Partes Review of U.S. Pat. No. 8,542,815; with Appendices A through II, 2113 pages.
Petitioner AT&T Services, Inc. Exhibit 1004, Case No. IPR2017-01382; Appendix A, James R. Bress, Curriculum Vitae, 26 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix B, Chapter 5, Telecommunications Essentials, Lillian Goleniewski, © 2002, 40 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix C, Chapter 11, Telecommunications Essentials, Lillian Goleniewski, © 2002, 41 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix D, ITU-T Recommendation E.164 (May 1997), 27 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix E, Telcordia Notes on the Networks, SR-2275, Issue 4, Oct. 2000, pp. 3-8-3-14, 9 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix F, Chapter 4, Telecommunications, Essentials, Lillian Goleniewski, © 2002, pp. 99-100, 4 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix G, Telcordia Notes on the Networks, SR-2275, Issue 4, Oct. 2000, pp. 18-1-18-20, 22 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix H, Softswitch, Architecture for VoIP, Franklin D. Ohrtman, Jr., © 2003, Chapter 2, 32 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix I, Telecommunications Act of 1996, 104th Congress of the U.S.A., Jan. 1996, 128 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix J, Perspective on the AIN Architecture, Berman et al., IEEE Communications Magazine, Feb. 1992, 6 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix K, U.S. Pat. No. 7,907,714 B2, to Baniak et al., 21 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix L, The IMS, Polkselkä & Mayer, © 2009, John Wiley & Sons Ltd, Chapter 1 Introduction, 14 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix M, The IMS, Polkselkä & Mayer, © 2009, John Wiley & Sons Ltd, pp. 24-25 and 86-94, 13 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix N, Chapter 9, Telecommunications Esentials, Lillian Goleniewski, © 2002, 42 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix O, Softswitch, Architecture for VoIP, Franklin D. Ohrtman, Jr., © 2003, pp. 238-239, 4 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix P, Softswitch, Architecture for VoIP, Franklin D. Ohrtman, Jr. © 2003, Chapter 4, pp. 67-86, 22 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix Q, Softswitch, Architecture for VoIP, Franklin D. Ohrtman, Jr. © 2003, Chapter 5, pp. 87-112, 28 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix R, Telecommunication Essentials, Lillian Goleniewski, © 2002, pp. 221, 3 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix S, Network Working Group, RFC (Request for Comments): 1122, Internat Engineering Task Force, R. Braden, Ed., Oct. 1989, pp. 18-25, 9 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix T, RFC (Request for Comments): 791, Internet Protocol, DARPA Internet Program, Protocol Specification, Sep. 1981, by Information Sciences Institute, USC, 50 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix U, Network Working Group, RFC (Request for Comments): 1034, P. Mockapetris, ISI, Nov. 1987, pp. 1-55, 55 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix V, Network Working Group, RFC (Request for Comments): 1035, P. Mockapetris, ISI, Nov. 1987, pp. 1-55, 55 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix W, Network Working Group, RFC (Request for Comments): 3761, P. Faltstrom et al., Apr. 2004, pp. 1-18, 18 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix X, U.S. Pat. No. 6,594,254 B1, to Kelly, 18 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix Y, ITU-T Recommendation H.323 (Jul. 2003), 298 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix Z, Telcordia Notes on the Networks, SR-2275, Issue 4, Oct. 2000, pp. 6-306-6-309, 4 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix AA, Telcordia Notes on the Networks, SR-2275, Issue 4, Oct. 2000, pp. 14-10-14-13, 6 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix BB, The Internet Engineering Task Force (IETF®), May 5, 2017, 2 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix CC, Network Working Group, RFC (Request for Comments); 3261, J. Rosenberg et al., Jun. 2002, 269 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix DD, Network Working Group, RFC (Request for Comments): 3666, A. Johnston et al., Dec. 2003, 118 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix EE, Network Working Group, RFC (Request for Comments): 3665, A. Johnston et al., Dec. 2003, 94 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix FF, Network Working Group, RFC (Request for Comments): 2327, M. Handley et al., Apr. 1998, 42 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix GG, ITU-T Recommendation Q.931 (May 1998), 345 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix HH, Telcordia Notes on the Networks, SR-2275, Issue 4, Oct. 2000, pp. 14-76-14-77, 4 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Case No. IPR2017-01382; Appendix II, Telcordia Notes on the Networks, SR-2275, Issue 4, Oct. 2000, pp. 10-17, 3 pages.
Petitioner AT&T Services, Inc. Exhibit 1004, Case No. IPR2017-01382; James R. Bress, Curriculum Vitae, 26 pages.
Petitioner AT&T Services, Inc. Exhibit 1005, Case No. IPR2017-01382; U.S. Pat. No. 6,240,449, Issued May 29, 2001 to Raymond Nadeau, 13 pages.
Petitioner AT&T Services, Inc. Exhibit 1006, Case No. IPR2017-01382; U.S. Pat. No. 6,594,254 B1, Issued Jul. 15, 2003 to Keith C. Kelly, 18 pages.
Petitioner AT&T Services, Inc. Exhibit 1007, Case No. IPR2017-01382; U.S. Pat. No. 7,715,413 B2, Issued May 11, 2010, to Vaziri et al., 53 pages.
Petitioner AT&T Services, Inc. Exhibit 1008, Case No. IPR2017-01382; Decision, Institution of Inter Partes Review, 37 C.F.R. § 42.108, Paper 6, Entered Nov. 21, 2016, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com Inc., Patent Owner, Case IPR2016-01201, U.S. Pat. No. 8,542,815 B2, Before Barbara A. Benoit, Lynne E. Pettigrew, and Stacy B. Margolies, Administrative Patent Judges, 33 pages.
Petitioner AT&T Services, Inc. Exhibit 1009, Case No. IPR2017-01382; p. 221 and Chapter 11, Telecommunications Essentials, Lillian Goleniewski, © 2002, 44 pages.
Petitioner AT&T Services, Inc. Exhibit 1010, Case No. IPR2017-01382; RFC (Request for Comments): 791, Internet Protocol, DARPA Internet Program, Protocol Specification, Sep. 1981, by Information Sciences Institute, USC, 50 pages.
Petitioner AT&T Services, Inc. Exhibit 1011, Case No. IPR2017-01382; ITU-T Recommendation H.323 (Jul. 2003), 298 pages.
Petitioner AT&T Services, Inc. Exhibit 1012, Case No. IPR2017-01382; Telcordia Notes on the Networks, SR-2275, Issue 4, Oct. 2000, pp. 10-17, 3 pages.
Document Title: In the Unted States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner v. Digifonica (International) Limited Patent Owner, Case No. IPR2017-01383; U.S. Pat. No. 9,179,005; Petition for Inter Partes Review of U.S. Pat. No. 9,179,005; Dated May 8, 2017, 92 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Unted States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner v. Digifonica (International) Limited Patent Owner, U.S. Pat. No. 9,179,005, Inter Partes Review No. IPR2017-01383; Declaration of James Bress in Support of Petition for Inter Partes Review of U.S. Pat. No. 9,179,005; with Appendices A through II, 2094 pages.
Petitioner AT&T Services, Inc. Exhibit 1004, Case No. IPR2017-01383; James R. Bress, Curriculum Vitae, 26 pages.
Petitioner AT&T Services, Inc. Exhibit 1005, Case No. IPR2017-01383; U.S. Pat. No. 6,240,449, Issued May 29, 2001 to Raymond Nadeau, 13 pages.
Petitioner AT&T Services, Inc. Exhibit 1006, Case No. IPR2017-01383; U.S. Publication No. 2004/0218748 A1, Published Nov. 4, 2004, by Stephen Fisher, 18 pages.
Petitioner AT&T Services, Inc. Exhibit 1007, Case No. IPR2017-01383; U.S. Pat. No. 6,594,254 B1, Issued Jul. 15, 2003, to Keith C. Kelly, 18 pages.
Petitioner AT&T Services, Inc. Exhibit 1008, Case No. IPR2017-01383; U.S. Pat. No. 6,674,850 B2, Issued Jan. 6, 2004 to Vu et al., 10 pages.
Petitioner AT&T Services, Inc. Exhibit 1009, Case No. IPR2017-01383; Decision, Institution of Inter Partes Review, 37 C.F.R. § 42.108, Paper 6, Entered Nov. 21, 2016, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com Inc., Patent Owner, Case IPR2016-01198, U.S. Pat. No. 9,179,005 B2, Before Barbara A. Benoit, Lynne E. Pettigrew, and Stacy B. Margolies, Administrative Patent Judges, 32 pages.
Petitioner AT&T Services, Inc. Exhibit 1010, Case No. IPR2017-01383; Patent Owner Response to Petition, Filed Feb. 10, 2017, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case IPR2016-01198, U.S. Pat. No. 9,179,005 B2, 78 pages.
Document Title: In the United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner v. Digifonica (International) Limited Patent Owner, Case No. IPR2017-01384; U.S. Pat. No. 9,179,005; Petition for Inter Partes Review of U.S. Pat. No. 9,179,005; Dated May 7, 2017, 70 pages.
Petitioner AT&T Services, Inc. Exhibit 1003, Unted States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner v. Digifonica (International) Limited Patent Owner, U.S. Pat. No. 9,179,005, Inter Partes Review No. IPR2017-01384; Declaration of James Bress in Support of Petition for Inter Partes Review of U.S. Pat. No. 9,179,005; with Appendices A through II, 2085 pages.
Petitioner AT&T Services, Inc. Exhibit 1004, Case No. IPR2017-01384; James R. Bress, Curriculum Vitae, 26 pages.
Petitioner AT&T Services, Inc. Exhibit 1005, Case No. IPR2017-01384; U.S. Pat. No. 6,240,449, Issued May 29, 2001 to Raymond Nadeau, 13 pages.
Petitioner AT&T Services, Inc. Exhibit 1006, Case No. IPR2017-01384; U.S. Pat. No. 6,594,254 B1, Issued Jul. 15, 2003, to Keith C. Kelly, 18 pages.
Petitioner AT&T Services, Inc. Exhibit 1007, Case No. IPR2017-01384; U.S. Pat. No. 7,715,413 B2, Issued May 11, 2010 to Vaziri et al., 53 pages.
Petitioner AT&T Services, Inc. Exhibit 1008, Case No. IPR2017-01384; Decision, Institution of Inter Partes Review, 37 C.F.R. § 42.108, Paper 6, Entered Nov. 21, 2016, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com Inc., Patent Owner, Case IPR2016-01198, U.S. Pat. No. 9,179,005 B2, Before Barbara A. Benoit, Lynne E. Pettigrew, and Stacy B. Margolies, Administrative Patent Judges, 32 pages.
Petitioner AT&T Services, Inc. Exhibit 1009, Case No. IPR2017-01384; p. 221 and Chapter 11, Telecommunications Essentials, Lillian Golenlewski, © 2002, 44 pages.
Petitioner AT&T Services, Inc. Exhibit 1010, Case No. IPR2017-01384; RFC (Request for Comments): 791, Internet Protocol, DARPA Internet Program, Protocol Specification, Sep. 1981, by Information Sciences Institute, USC, 50 pages.
Petitioner AT&T Services, Inc. Exhibit 1011, Case No. IPR2017-01384; ITU-T Recommendation H.323 (Jul. 2003), 298 pages.
Petitioner AT&T Services, Inc. Exhibit 1012, Case No. IPR2017-01384; Telcordia Notes on the Networks, SR-2276, Issue 4, Oct. 2000, p. 10-17, 3 pages.
Document Title: United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Petitioner's Reply to Patent Owner's Response, Dated May 17, 2017, 34 pages.
Petitioner Apple Inc. Exhibit 1007, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Discovery Deposition of William Henry Mangione-Smith, taken on Apr. 19, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 213 pages.
Petitioner Apple Inc. Exhibit 1008, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Discovery Deposition of John Rutter, taken (by phone) on Apr. 5, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 43 pages.
Petitioner Apple Inc. Exhibit 1009, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Discovery Deposition of David Terry, taken on Mar. 24, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 95 pages.
Petitioner Apple Inc. Exhibit 1010, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Discovery Deposition of Clay Perreault, taken on Apr. 12, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 118 pages.
Petitioner Apple Inc. Exhibit 1011, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Complaint for Patent Infringement [Jury Demand], United States District Court, District of Nevada, Case No. 2:16-CV-00260, Voip-pal.com, Inc., a Nevada corporation, Plaintiff, v. Apple, Inc., a California corporation, Defendants, filed Feb. 9, 2016, 8 pages.
Petitioner Apple Inc. Exhibit 1012, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Discovery Deposition of Johan Emil Viktor Bjorsell, taken on Mar. 24, 2017 in Case No. IPR2016-001198; U.S. Pat. No. 9,179,005, 204 pages.
Petitioner Apple Inc. Exhibit 1013, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Letter dated Apr. 21, 2017 to Adam P. Seitz et al., Erise IP, P.A., re: IPR2016-01198 & IPR1026-01201, “Pursuant to the Board Order of Apr. 19, 2017 (Paper 28) . . . ” from Kerry Taylor, Knobbe, Martens, Olson & Bear, LLP, 1 page.
Petitioner Apple Inc. Exhibit 1014, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201; U.S. Pat. No. 8,542,815; Email dated May 1, 2017 to Adam P. Seitz et al., Erise IP, P.A., re: IPR2016-01198 & IPR1026-01201—Fuad Arafa, from Kerry Taylor, Knobbe, Martens, Olson & Bear, LLP, 2 pages.
Document Title: United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Petitioner's Reply to Patent Owner's Response, Paper 34, Dated May 17, 2017, 33 pages.
Petitioner Apple Inc. Exhibit 1010, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Discovery Deposition of William Henry Mangione-Smith, taken on Apr. 19, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 213 pages.
Petitioner Apple Inc. Exhibit 1011, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Discovery Deposition of John Rutter, taken (by phone) on Apr. 5, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 43 pages.
Petitioner Apple Inc. Exhibit 1012, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Discovery Deposition of David Terry, taken on Mar. 24, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 95 pages.
Petitioner Apple Inc. Exhibit 1013, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Discovery Deposition of Clay Perreault, taken on Apr. 12, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 118 pages.
Petitioner Apple Inc. Exhibit 1014, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Complaint for Patent Infringement [Jury Demand], United States District Court, District of Nevada, Case No. 2:16-CV-00260, Voip-Pal.com, Inc. a Nevada corporation, Plaintiff, v. Apple, Inc., a California corporation, Defendants, filed Feb. 9, 2016, 8 pages.
Petitioner Apple Inc. Exhibit 1015, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Discovery Deposition of Johan Emil Viktor Bjorsell, taken on Mar. 24, 2017 in Case No. IPR2016-01198; U.S. Pat. No. 9,179,005, 204 pages.
Petitioner Apple Inc. Exhibit 1016, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Letter dated Apr. 21, 2017 to Adam P. Seitz et al., Erise IP, P.A., re: IPR2016-01198 & IPR1026-01201, “Pursuant to the Board Order of Apr. 19, 2017 (Paper 28) . . . ” from Kerry Taylor, Knobbe, Martens, Olson & Bear, LLP, 1 page.
Petitioner Apple Inc. Exhibit 1017, United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198; U.S. Pat. No. 9,179,005; Email dated May 1, 2017 to Adam P. Seitz et al, Erise IP, P.A., re:IPR2016-01198 & IPR1026-01201—Fuad Arafa, from Kerry Taylor, Knobbe, Martens, Olson & Bear, LLP, 2 pages.
Document Title: United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Patent Owner Objections to Apple Evidence Served with Petitioner's Reply, Filed on behalf of Patent Owner Voip-Pal.com, Inc. Filed: May 24, 2017, 6 pages.
Document Title: United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner v. Voip-Pal.com.Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005; Patent Owner Objections to Apple Evidence Served with Petitioner's Reply, Filed on behalf of Patent Owner Voip-Pal.com Inc., Filed: May 24, 2017, 6 pages.
Canadian Office Action dated May 29, 2017 for Canadian Patent Application No. CA 2,668,025.
Canadian Office Action dated Jun. 9, 2017 for Canadian Patent Application No. CA 2,916,217.
European Examination Report dated May 12, 2017 for European Patent Application No. EP 09-802-316.1.
Petitioner's Reqeust for Oral Argument, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, dated Jun. 14, 2017, 4 pages.
Patent Owner Sur-Reply in Response to Petitioner's Reply, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, dated Jun. 14, 2017, 8 pages.
Patent Owner Request for Oral Argument, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, dated Jun. 14, 2017, 4 pages.
Patent Owner Motion to Exclude, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, dated Jun. 14, 2017, 18 pages.
Voip-Pal Ex. 2052, IPR2016-01201, Apple Inc. vs. Voip-Pal.com, Inc., Reporter's Transcript of Telephoric Hearing, Jun. 7, 2017, 16 pages.
Petitioner's Request for Oral Argument, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, dated Jun. 14, 2017, 4 pages.
Patent Owner Sur-Reply in Response to Petitoner's Reply, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, dated Jun. 14, 2017, 8 pages.
Patent Owner Request for Oral Argument, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, dated Jun. 14, 2017, 4 pages.
Patent Owner Motion to Exclude, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, dated Jun. 14, 2017, 18 pages.
Voip-Pal Ex. 2052, IPR2016-01198, Apple Inc. vs. Voip-Pal.com, Inc., Reporter's Transcript of Telephonic Hearing, Jun. 7, 2017, 16 pages.
Order, Conduct of Proceeding, 37 C.F.R. § 42.5, United States Patent and Trademark Office, Before the Patent Trail and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner. Cases IPR2016-01198 and IPR2016-01201, U.S. Pat. No. 9,179,005 B2 and U.S. Pat. No. 8,542,815 B2, Paper No. 37, Filed: Jun. 13, 2017, 3 pages.
Voip-Pal Ex. 2053, IPR2016-01198, Apple Inc. vs. Voip-Pal.com, Inc., Reporter's Transcript of Telephonic Hearing, Jun. 20, 2017, 25 pages.
Voip-Pal Ex. 2053, IPR2016-01201, Apple Inc. vs. Voip-Pal.com, Inc., Reporter's Transcript of Telephonic Hearing, Jun. 20, 2017, 25 pages.
Order, Conduct of Proceeding, 37 C.F.R. §42.5 United States Patent and Trademark Office, Before the Patent Trail and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner. Cases IPR2016-01198 and IPR2016-01201, U.S. Pat. No. 9,179,005 B2 and U.S. Pat. No. 8,542,815 B2, Paper No. 43, Filed: Jun. 22, 2017, 4 pages.
Order, Trial Hearing, 37 C.F.R. §42.5 United States Patent and Trademark Office, Before the Patent Trail and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner. Cases IPR2016-01198 and IPR2016-01201, U.S. Pat. No. 9,179,005 B2 and U.S. Pat. No. 8,542,815 B2, Paper No. 45, Filed: Jun. 22, 2017, 4 pages.
Petitioner's Opposition to Patent Owner's Motion to Exclude, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01201, U.S. Pat. No. 8,542,815, Date: Jun. 26, 2017, 15 pages.
Petitioner's Opposition to Patent Owner's Motion to Exclude, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2016-01198, U.S. Pat. No. 9,179,005, Date: Jun. 26, 2017, 15 pages.
Patent Owner Reply to Opposition to Motion to Exclude, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR 2016-01198, U.S. Pat. No. 9,179,005, Filed: Jul. 3, 2017, 8 pages.
Patent Owner Reply to Opposition to Motion to Exclude, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR 2016-01201, U.S. Pat. No. 8,542,815, filed Jul. 3, 2017, 8 pages.
Voip-Pal Ex. 2054, IPR2016-01198, Voip-PAL's Demonstratives For Oral Hearing, Apple Inc. v. Voip-Pal.com, Inc., Case IPR2016-01201 (U.S. Pat. No. 8,542,815), Case IPR2016-01198 (U.S. Pat. No. 9,179,005), Jul. 20, 2017, 34 pages.
Petitioner Apple Inc. Ex. 1018, Petitioner's Demonstrative Exhibits, Inter Partes Reviews, U.S. Pat. No. 9,179,005 & U.S. Pat. No. 8,542,815, Oral Argument, Jul. 20, 2017, Apple Inc. v. Voip-Pal.com, Inc., Case IPR2016-01198; U.S. Pat. No. 9,179,005, Case IPR2016-01201; U.S. Pat. No. 8,542,815, 46 pages.
Canadian Office Action dated Aug. 2, 2017 for Candian Patent Application No. CA 2,681,984.
Indian Office Action dated Jun. 21, 2017 for lndian Patent Application No. IN 1227/MUMNP/2009.
Patent Owner's Preliminary Response to Petition for Inter Partes Review, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, AT&T Services, Inc., Petitioner, v. VoIP-PAL.COM, INC., Patent Owner, Case No. IPR2017-01382, U.S. Pat. No. 8,542,815, dated Aug. 24. 2017, 71 pages.
Patent Owner's Preliminary Response to Petition for Inter Partes Review, United States Patent And Trademark Office, Before the Patent Trial and Appeal Board,AT&T Services, Inc., Petitioner, v. VoIP-PAL.COM, INC., Patent Owner. Case No. IPR2017-01383. U.S. Pat. No. 9,179,005, dated Aug. 24, 2017, 74 pages.
Patent Owner's Preliminary Response to Petition for Inter Partes Review, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, AT&T Services, Inc., Petitioner, v. VoIP-PAL.COM, INC., Patent Owner. Case No. IPR2017-01384. U.S. Pat. No. 9,179,005, dated Aug. 24, 2017, 61 pages.
Patent Owner's Preliminary Response to Petition for Inter Partes Review, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner, Case No. IPR2017-01398, U.S. Pat. No. 9,179,005, dated Aug. 25, 2017, 76 pages.
Patent Owner's Preliminary Response to Petition for Inter Partes Review, United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Apple Inc., Petitioner, v. VoIP-PAL.COM, INC., Patent Owner, Case No. IPR2017-01399, U.S. Pat. No. 8,542,815, dated Aug. 25, 2017, 77 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com., Inc. Patent Owner; Cases IPR2016-01198 and IPR2016-01201; U.S. Pat. No. 9,179,005 B2 and U.S. Pat. No. 8,542,815 B2; Record of Oral Hearing, Held: Jul. 20, 2017; Before Josiah C. Cocks, Jennifer Meyer Chagnon, and John A. Hudalla, Administrative Patent Judges, 83 pages.
Intimation of the grant and recordal of India Patent No. 287412 entitled “Producing Routing Messages for Voice Over IP Communications”, dated Sep. 15, 2017, for India Patent Application No. IN 1047/MUMNP/2009 filed Nov. 1, 2007.
Canadian Office Action dated Sep. 18, 2014 for Canadian Patent Application No. CA 2,670,510.
Canadian Office Action dated Aug. 18, 2015 for Canadian Patent Application No. CA 2,732,148.
United States Patent And Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2016-01198, U.S. Pat. No. 9,179,005 B2; Final Written Decision; Paper 53, Entered: Nov. 20, 2017; 29 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2016-01201, U.S. Pat. No. 8,542,815 B2; Final Written Decision; Paper 54, Entered: Nov. 20, 2017; 29 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2017-01399, U.S. Pat. No. 8,542,815 B2; Decision: Denying Institution of Inter Partes Review; Paper No. 6, Entered: Nov. 20, 2017; 23 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2017-01398, U.S. Pat. No. 9,179,005 B2; Decision: Denying Institution of Inter Partes Review; Paper No. 6, Entered: Nov. 20, 2017; 23 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner, v. Voip-Pal.Com, Inc., Patent Owner; Case IPR2017-01382, U.S. Pat. No. 8,542,815 B2; Decision: Denying Institution of Inter Partes Review; Paper No. 8, Entered: Nov. 20, 2017; 28 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2017-01383, U.S. Pat. No. 9,179,005 B2; Decision: Denying Institution of Inter Partes Review; Paper No. 8, Entered: Nov. 20, 2017; 43 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; AT&T Services, Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2017-01384, U.S. Pat. No. 9,179,005 B2; Decision: Denying Institution of Inter Partes Review; Paper No. 8, Entered: Nov. 20, 2017; 31 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Volp-Pal.com, Inc., Patent Owner; Cases IPR2016-01198 and IPR2016-01201, U.S. Pat. No. 9,179,005 B2 and U.S. Pat. No. 8,542,815 B2; Order, Conduct of Proceeding, 37 C.F.R. ξ 42.5; Paper No. 54, Entered: Dec. 20, 2017; 4 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Petitioner's Motion for Entry of Judgment in Favor of Petitioner etc; Paper 55, Date: Dec. 20, 2017; 18 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Petitioner's Updated Exhibit List; Date: Dec. 22, 2017; 4 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Exhibit 1019—Sep. 18, 2017 Voip-Pal Website advertising Dr. Sawyer's Letters; Date: Dec. 20, 2017; 1 page.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IP2016-01201, U.S. Pat. No. 8,542,815; Exhibit 1020—Sep. 2017 Voip-Pal Website posting and linking all of Dr. Sawyer's Letters; Date: Dec. 20, 2017; 2 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, vs. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005 82 and Case No. IPR2016-01201, U.S. Pat. No. 8,542,815 B2; IPR2016-01201 Exhibit 1021—Telephonic Hearing Before the Administrative Patent Judges: Dec. 19, 2017; 25 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Appl. No. 9,179,005; Petitioner's Motion for Entry of Judgment in Favor of Petitioner etc; Date: Dec. 20, 2017; 18 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005; Petitioner's Updated Exhibit List; Date: Dec. 22, 2017; 4 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2016-01198, U.S. Pat. No. 9,179,005 B2; Exhibit 1019—Sep. 18, 2017 Voip-Pal Website advertising Dr. Sawyer's Letters; Date: Dec. 20, 2017; 1 page.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case IPR2016-01198, U.S. Pat. No. 9,179,005 B2; Exhibit 1020—Sep. 2017 Voip-Pal Website posting and linking all of Dr. Sawyer's Letters; Date: Dec. 20, 2017; 2 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, vs. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005 B2 and Case No. IPR2016-01201, U.S. Pat. No. 8,542,815 B2; IPR2016-01198 Exhibit 1021—Telephonic Hearing Before the Administrative Patent Judges: Dec. 19, 2017; 25 pages.
Exhibit 3001 filed Dec. 20, 2017—Letter from Ryan L. Thomas dated Dec. 19, 2017 re Representation of VoIP-Pal.com, Inc. in Conference Call to the Administrative Patent Judges in re IPR2016-01198 and IPR-2016-01201; 1 page.
Exhibit 3002 fied Dec. 20, 2017—Email from Attorney Adam Seitz dated Dec. 15, 2017 to the Administrative Patent Judges in re IPR2016-01198 and IPR-2016-01201 re Authorization to File Motion for Sanctions; 1 page.
Exhibit 3003 filed Dec. 20, 2017—Letter from Dr. Thomas E. Sawyer (Shareholder) dated May 1, 2017 To Ptab Chief Judge David P. Ruschke in re IPR2016-01198 and IPR-2016-01201 re Review of Proceedings, 6 pages.
Exhibit 3004 filed Dec. 20, 2017—Letter from Dr. Thomas E. Sawyer (Shareholder) dated Jun. 21, 2017 to PTAB Chief Judge David P. Ruschke in re IPR2016-01198 and IPR-2016-01201 re Review of Proceedings, 3 pages.
Exhibit 3005 filed Dec. 20, 2017—Letter from Dr. Thomas E. Sawyer (Shareholder) dated Jul. 11, 2017 to PTAB Chief Judge David P. Ruschke in re IPR2016-01198 and IPR-2016-01201 re Review of Proceedings, 5 pages.
Exhibit 3006 filed Dec. 20, 2017—Letter from Dr. Thomas E. Sawyer (Shareholder) dated Jul. 27, 2017 to the Secretary of the Department of Commerce Hon. Wilbur Ross et al. in re IPR2016-01198 and IPR-2016-01201 re Review of Proceedings, 6 pages.
Exhibit 3007 filed Dec. 20, 2017—Letter from Dr. Thomas E. Sawyer (Shareholder) dated Aug. 31 , 2017 to the Secretary of the Department of Commerce Hon. Wilbur Ross in re IPR2016-01198 and IPR-2016-01201 re Review of Proceedings, 8 pages.
Exhibit 3008 filed Dec. 20, 2017—Letter from Dr. Thomas E. Sawyer (Shareholder) dated Oct. 23, 2017 to the PTAB Chief Judge David P. Ruschke et al. in re IPR2016-01198 and IPR-2016-01201 re Review of Proceedings, 10 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005; Patent Owner's Opposition to Apple's Motion for Sanctions Pursuant to Board Order of Dec. 20, 2017; Filed: Jan. 12, 2018; 17 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005; Patent Owner's Updated Exhibit List; Filed: Jan. 12, 2018; 9 pages.
Voip-Pal Exhibit 2056, IPR2016-01198; United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005; Declaration in Support of Patent Owner's Opposition to Motion fr Sanctions; Dated: Jan. 12, 2018; 12 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Patent Owner's Opposition to Apple's Motion for Sanctions Pursuant to Board Order of Dec. 20, 2017; Filed: Jan. 12, 2018; 17 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Patent Owner's Updated Exhibit List; Filed: Jan. 12, 2018; 9 pages.
Voip-Pal Exhibit 2056, IPR2016-01198; United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Declaration in Support of Patent Owner's Opposition to Motion for Sanctions; Dated: Jan. 12, 2018; 12 pages.
Voip-Pal EXHIBIT 2057; IPR2016-01198 and IPR2016-01201; Declaration of Adam R. Knecht, Esq. Regarding Notice of Various Letters from Dr. Thomas Sawyer to the Honorable Judge Richard F. Boulware II (ECF Nos. 28 and 32); including Exhibit A (7 pages), Exhibit B (19 pages) and Exhibit C (12 pages); Executed on Dec. 18, 2017; 40 pages.
Voip-Pal Exhibit 2058; IPR2016-01198 and IPR2016-01201; O'Brien et al., “Revealed: Federal Judges Guilty of Owning Stock in Corporations They Ruled On,” Occupy.com (May 1, 2014) 11 pages.
Voip-Pal Exhibit 2059; IPR2016-01198 and IPR2016-01201; Letter dated Aug. 7, 2013 from Kathryn Siehndel, USPTO FOIA Officer, Re: Freedom of Information Act (FOIA) Request No. F-13-00218 concerning U.S. Pat. No. 7,139,761; 77 pages.
Voip-Pal Exhibit 2060; IPR2016-01198 and IPR2016-01201; Questionnaire for Non-Judicial Nominees; Affidavit executed by Micheile K. Lee Oct. 28, 2014; 40 pages.
Voip-Pal Exhibit 2061; lPR2016-01198 and IPR2016-01201; Davis, R., “PTAB's ‘Death Squad’ Label Not Totally Off-Base, Chief Says,” Law360, New York (Aug. 14, 2014) 4 pages.
Voip-Pal Exhibit 2062; IPR2016-01198 and IPR2016-01201; Graham et al., “The Brainy Bunch,” Intellectual Property: An ALM Supplement, Fall 2015, 7 pages.
Voip-Pal Exhibit 2063; IPR2016-01198 and IPR2016-01201; Patent Trial and Appeal Board Statistics, USPTO, Jan. 31, 2017, 15 pages.
Voip-Pal Exhibit 2064; IPR2016-01198 and IPR2016-01201; Davis, R., “Fed. Circ. Reverses PTAB Nix of Synopsys Circuit Patent,” Law360, New York, Apr. 24, 2017, 5 pages.
Voip-Pal Exhibit 2065; IPR2016-01198 and IPR2016-01201; Scheller et al. “Federal Circuit to PTAB: No Short Cuts Allowed,” The National Law Review; April 25, 2017, 5 pages.
Voip-Pal Exhibit 2066; IPR2016-01198 and IPR2016-01201; Couturier, K. “How Europe is Going After Apple, Google and Other U.S. Tech Giants,” New York Times, Apr. 13, 2015, 1 page.
Voip-Pal Exhibit 2067; IPR2016-01198 and IPR2016-01201; Manjoo, F., “Tech Giants Seem Invincible. That Worries Lawmakers.” New York Times, Jan. 4, 2017, 5 pages.
Voip-Pal Exhibit 2068; IPR2016-01198 and IPR2016-01201; Quinn et al., “Michelle Lee's views on patent quality out of touch with reality facing patent applicants,” IPWatchdog®, Feb. 2, 2017, 5 pages.
Voip-Pal Exhibit 2069; IPR2016-01198 and IPR2016-01201; Quinn, (G., “Michelle Lee launches PTAB initiative to ‘shape and improve’ IPR proceedings,” IPWatohdog®, Apr. 10, 2017, 3 pages.
Voip-Pal Exhibit 2070; IPR2016-01198 and IPR2016-01201; Kampis, J., “Google employees have enjoyed revolving door during Obama administration,” watchdog.org, Aug. 8, 2016, 6 pages.
Voip-Pal Exhibit 2071; IPR2016-01198 and IPR2016-01201; Dayen, D., “The Android Administration,” The lntercept_, Apr. 22, 2016, 16 pages.
Voip-Pal Exhibit 2072; IPR2016-01198 and IPR2016-01201; Editor Charlie, “@scleland: How Google is Anti-employment Anti-property & Pro-regulation,” Artist Rights Watch, News for the Artist Rights Advocacy Community, Nov. 18, 2016, 3 pages.
Voip-Pal Exhibit 2073; IPR2016-01198 and IPR2016-01201; Press Release: “Voip-Pal Issues a Correction to its Press Release of Sep. 18th 2017,” Voip-Pal.Com Inc., Jan. 11, 2018, 1 page.
Voip-Pal Exhibit 2074; IPR2016-01198 and IPR2016-01201; “Former head of Google patent strategy appointed to run U.S. patent agency,” ai (/Profile/12836/AppleInsider), Dec. 12, 2013, 8 pages.
Voip-Pal Exhibit 2075; IPR2016-01198 and IPR2016-01201; Vermont, S. “IPR Statistics Revisited: Yep, It's A Patent Killing Field,” PatentAttorney.com, Feb. 8, 2017, 9 pages.
Voip-Pal Exhibit 2076; IPR2016-01198 and IPR2016-01201; Sterne et al., “PTAB Death Squads: Are All Commercialiy Viable Patents Invalid?” IPWatohdog®, Mar. 24, 2014, 5 pages.
Volp-Pal Exhibit 2077; IPR2016-01198 and IPR2016-01201; Sheafe, B., “Dear Congress: A Small Request on Behalf of the Innovators You (Theoretically) Represent: Part 2,” IPWire, Jan. 12, 2018, 5 pages.
Voip-Pal Exhibit 2078; IPR2016-01198 and IPR2016-01201; Brachmann, S., “Are conflicts of interest at the PTAB leading to preferential decisions for Apple?” IPWatchdog®, Apr. 28, 2017, 5 pages.
Voip-Pal Exhibit 2079; IPR2016-01198 and IPR2016-01201; Quinn et al., “Patent owners do not like IPRs despite what Bloomberg Law, AIPLA study says,” IPWatchdog®, Feb. 6, 2017, 5 pages.
Voip-Pal Exhibit 2080; IPR2016-01198 and IPR2016-01201; “Does Google's Michelle Lee Work for Both Google and the U.S. Patent Office at the Same Time?” The Corruption Times, Your Public New WIKI for Social Updateds, Apr. 6, 2016, 8 pages.
Voip-Pal Exhibit 2081; IPR2016-01198 and IPR2016-01201; Morinville, P., “The Senate Must Vet Vishal Amin,”IPWatchdog®, Apr. 23. 2017, 4 pages.
Voip-Pal Exhibit 2082; IPR2016-01198 and IPR2016-01201; The New York Times “May 15, 1911 | Supreme Court Orders Standard Oil to Be Broken Up,” By the Learning Network, May 15, 2012, 3 pages.
Voip-Pal Exhibit 2083; IPR2016-01198 and IPR2016-01201; Simpson et al., “PTAB Kill Rates: How IPRs are Affecting Patents,” Law360, New York, Sep. 15, 2015, 6 pages.
Voip-Pal Exhibit 2084; IPR2016-01198 and IPR2016-01201; Vermont, S., “IPR Statistics Revisited: Yep, It's a Patent Killing Field,” PatentAttorney.com, Feb. 8, 2017, 9 pages.
Voip-Pal Exhibit 2085; IPR2016-01198 and IPR2016-01201; Robinson, E., “Why the Unified Patents Model Would Not Work in China,” IPWatchdog®, Apr. 26, 2017, 4 pages.
Voip-Pal Exhibit 2086; IPR2016-01198 and IPR2016-01201; Brachmann et al., “US Inventor sets patents on fire as part of PTAB protest at USPTO,” IPWatchdog®, Aug. 11, 2017, 4 pages.
Voip-Pal Exhibit 2087; IPR2016-01198 and IPR2016-01201; “Selection process for assigning judges to expanded PTAB panels,” 717 Madison Place, Aug. 28, 2017, 3 pages.
Voip-Pal Exhibit 2088; IPR2016-01198 and IPR2016-01201; Eden, S., “How the U.S. Patent Office Got So Screwed Up,” Popular Mechanics, Jun. 21, 2016, 21 pages.
Voip-Pal Exhibit 2089; IPR2016-01198 and IPR2016-01201; Quinn, G., “Supreme Court to decide if Inter Partes Review is Unconstitutional,” IPWatchdog®, Jun. 12, 2017, 4 pages.
Voip-Pal Exhibit 2090; IPR2016-01198 and IPR2016-01201; Quinn, G., “Industry reaction to SCOTUS patent venue decision in TC Heartland v. Kraft Food Group,” IPWatchdog®, May 22, 2017, 7 pages.
Voip-Pal Exhibit 2091; IPR2016-01198 and IPR2016-01201; Flibbert et al., “5 Distinctions Between IPRS and District Court Patent Litigation,” Finnegan, Dec. 16, 2015, 6 pages.
Voip-Pal Exhibit 2092; IPR2016-01198 and IPR2016-01201; “2404. Hobbs Act—Under Color of Officiai Right,” USAM, Department of Justice, 5 pages.
Voip-Pal EXHIBIT 2093; IPR2016-01198 and IPR2016-01201; “Selection process for assigning judges to expanded PTAB panels,” 717 Madison Place, Aug. 28, 2017, 3 pages.
Voip-Pal Exhibit 2094; IPR2016-01198 and IPR2016-01201; “2015 Summary of Ethics Rules,” Economic Development Administration, U.S. Department of Commerce. 16 pages.
Voip-Pal Exhibit 2095; IPR2016-01198 and IPR2016-01201; “Patent Trial and Appeal Board Statistics,” United States Patent and Trademark Office, USPTO, Mar. 31, 2017, 15 pages.
Voip-Pal Exhibit 2096; IPR2016-01198 and IPR2016-01201; Madigan etal., “Turning Gold to Lead: How Patent Eligibility Doctrine is Undermining U.S. Leadership in Innovation,” George Mason Law & Economics Research Paper No. 17-16, Mar. 30, 2017, 21 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. VOIP-PAL.COM, INC., Patent Owner; Cases IPR2016-01198 and IPR2016-01201, U.S. Pat. No. 9,179,005 B2 and U.S. Pat. No. 8,542,815 B2; Order, Conduct of Proceeding, 37 C.F.R. ξ 42.5, for both proceedings; Paper No. 62, Entered: Jan. 19, 2018, 4 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. VOLP-PAL.COM, INC., Patent Owner; IPR2016-01198, U.S. Pat. No. 9,179,005; Notice of Appeal, Dated: Jan. 22, 2018, 5 pages.
Apple EXHIBIT 1022, IPR2016-01198, Telephonic Hearing Before the Administrative Patent Judges; Jan. 19th, 2018; 14 pages.
United States Patent and Trademark Office; Before the Patent Trial snd Appeal Board; APPLE INC., Petitioner, v. VOIP-PAL.COM, INC., Patent Owner; IPR2016-01201, U.S. Patent No. 8,542,815; Notice of Appeal, Dated: Jan. 22, 2018, 5 pages.
Apple EXHIBIT 1022, IPR2016-01201, Telephonic Hearing Before the Administrative Patent Judges; Jan. 19th, 2018; 14 pages.
Case: 18-1456; Document: 1-1; Filed: Jan. 23, 2018, 1 page: United States Court of Appeals for the Federal Circuit; Notice of Docketing; 18-1456—Apple Inc. v. Voip-Pal.com, Inc.; Date of Docketing: Jan. 23, 2018, IPR2016-01198; 1 page.
Case: 18-1456; Document: 1-2; Filed: Jan. 23, 2018, 34 pages: United States Court of Appeals for the Federal Circuit; Apple Inc., Petitioner, v. Voip-Pal.Com, Inc., Patent Owner; IPR2016-01198, U.S. Pat. No. 9,179,005; Notice Of Appeal, (Dated: Jan. 22, 2018, 5 pages); with Paper 53; Entered: Nov. 20, 2017; Final Written Decision; 35 U.S.C. ξ 318(a) and 37 C.F.R. ξ 42.73; (29 pages).
Case: 18-1456; Document 6; Filed: Jan. 25, 2018; 14 pages: In the United States Court of Appeals for the Federal Circuit, Apple Inc., Petitioner-Appellant, v. Voip-Pal.com, Inc., Patent Owner-Appellee. On Appeal from the United States Patent and Trademark Office, Patent Trial and Appeal Board, in Case No. IPR2016-01198; Motion of Appellant Apple Inc. to Stay Appeal or for a Limited Remand to Allow Conclusion of Administrative Proceedings.
Case: 18-1457; Document: 1-1; Filed: Jan. 23, 2018, 1 page: United States Court of Appeals for the Federal Circuit; Notice of Docketing; 18-1457—Apple Inc. v. Voip-Pal.com, Inc.; Date of Docketing: Jan. 23, 2018, IPR2016-01201; 1 page.
Case: 18-1457; Document: 1-2; Filed: Jan. 232018, 34 pages: United States Court of Appeals for the Federal Circuit; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; IPR2016-01201, U.S. Pat. No. 8,542,815; Notice of Appeal, (Dated: Jan. 22, 2018, 5 pages); with Paper 54; Entered: Nov. 20, 2017; Final Written Decision; 35 U.S.C. ξ 318(a) and 37 C.F.R. ξ 42.73; (29 pages).
Case: 18-1457; Document 6; Filed: Jan. 25, 2018; 14 pages: In the United States Court of Appeals for the Federal Circuit, Apple Inc., Petitioner-Appellant, v. VOIP-PAL.COM, INC., Patent Owner-Appellee. On Appeal from the United States Patent and Trademark Office, Patent Trial and Appeal Board, in Case No. IPR2016-01201; Motion of Appellant Apple Inc. to Stay Appeal or for a Limited Remand to Allow Conclusion of Administrative Proceedings.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005; Petitioner's Reply in Support of its Motion for Entry of Judgment in Favor of Petitioner as a Sanction for Improper Ex Parte Communications By Patent Owner, or, Alternatively, for New and Constitutionally Correct Proceedings, Date: Jan. 26, 2018, 11 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Volp-Pal.com, Inc., Patent Owner; Case No. IPR2016-01198, U.S. Pat. No. 9,179,005; Petitioner's Updated Exhibit List, Date: Jan. 26, 2018, 4 pages.
Apple EXHIBIT 1023, IPR2016-01198, Voip-Pal Issues a Correction to its Press Release of September 18th 2017; Jan. 12, 2018, 1 page.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Petitioner's Reply in Support of Its Motion for Entry of Judgment in Favor of Petitioner as a Sanction for Improper Ex Parte Communications by Patent Owner, or, Alternatively, for New and Constitutionally Correct Proceedings, Date: Jan. 26, 2018, 11 pages.
United States Patent and Trademark Office; Before the Patent Trial and Appeal Board; Apple Inc., Petitioner, v. Voip-Pal.com, Inc., Patent Owner; Case No. IPR2016-01201, U.S. Pat. No. 8,542,815; Petitioner's Updated Exhibit List, Date: Jan. 26, 2018, 4 pages.
Apple EXHIBIT 1023, IPR2016-01201, Voip-Pal Issues a Correction to its Press Release of Sep. 18th 2017; Jan. 12, 2018, 1 page.
Case: 18-1456; Document 7; Filed: Jan. 29, 2018; 2 pages: United States Court of Appeals for the Federal Circuit, Order; consolidating the appeals.
Case: 18-1457; Document 7; Filed: Jan. 29, 2018; 2 pages: United States Court of Appeals for the Federal Circuit, Order; consolidating the appeals.
Related Publications (1)
Number Date Country
20150327320 A1 Nov 2015 US
Continuations (2)
Number Date Country
Parent 14092831 Nov 2013 US
Child 14802872 US
Parent 13496864 US
Child 14092831 US