Telephone status notification system
Claim Score by NHIP
Abstract
A telephone line status notification system including at least one telephone line having a status, a communications network, at least one communications terminal which is connectable to the communications network and which is employable by a seeking user to communicate via the communications network a status request concerning the status of the at least one telephone line, apparatus for processing the status request the apparatus for processing is connectable to the communications network for receiving the status request from the seeking user therethrough and communicating the request, and apparatus for acquiring the status of the at least one telephone line, the apparatus for acquiring is in communication with the apparatus for processing for receiving the status request therefrom, and the apparatus for acquiring is connectable to the communications network for communicating the status via the communications network.
Term
Term ended
Expired 26 June 2018, 8.2 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
89 claims: 5 independent, 84 dependent
- 1Broadest claimClaim Score 71, broad(NHIP)A method for providing telephone line status information for at least one telephone line via a computer communications network, the method comprising:communicating, via said computer communications network, a request concerning the status of said at least one telephone line, said status comprising one or more of a physical in use status and a logical in use status;acquiring information regarding the status of said at least one telephone line without calling said at least one telephone line;and communicating, via said computer communications network, said information regarding said status of said at least one telephone line.
- 8A telephone line status notification system, operative to provide telephone line status information for at least one telephone line via a computer communication network, comprising:at least one communications terminal which is connectable to said computer communications network and which is employable to communicate via said computer communications network a request concerning status of said at least one telephone line, said status comprising one or more of a physical in use status and a logical in use status;apparatus for processing said request wherein said apparatus for processing is connectable to said computer communications network for receiving said request and communicating said request;and apparatus for acquiring information regarding said status of said at least one telephone line without calling said at least one telephone line, wherein said apparatus for acquiring is in communication with said apparatus for processing for receiving said request therefrom, and wherein said apparatus for acquiring is connectable to said computer communications network for communicating said status via said computer communications network.
- 37A method comprising:communicating, by one or more servers via a computer communications network, a request concerning a status of at least one telephone line associated with a first cellular telephone device, wherein the first cellular telephone device is associated with a first user, and wherein the status comprises one or more of a physical in use status or a logical in use status;acquiring, by the one or more servers, information regarding the status of the at least one telephone line associated with the first cellular telephone device without calling the first cellular telephone device;and communicating, by the one or more servers via the computer communications network, the information regarding the status of the at least one telephone line associated with the first cellular telephone device to a device associated with a second user.
- 70A system comprising:one or more servers running software causing the one or more servers to: communicate, via a computer communications network, a request concerning a status of at least one telephone line associated with a first cellular telephone device, wherein the first cellular telephone device is associated with a first user, and wherein the status comprises one or more of a physical in use status or a logical in use status;acquire information regarding the status of the at least one telephone line associated with the first cellular telephone device without calling the first cellular telephone device;and communicate the information regarding the status of the at least one telephone line associated with the first cellular telephone device to a device associated with a second user.
- 86An apparatus comprising:a cellular telephone device associated with a first user, the cellular telephone device configured to: acquire information regarding a status of at least one telephone line associated with the cellular telephone device, wherein the status comprises one or more of a physical in use status or a logical in use status;and communicate, by way of a computer communications network, the information regarding the status of the at least one telephone line associated with the cellular telephone device for delivery to a device associated with a second user, wherein the information regarding the status of the at least one telephone line associated with the cellular telephone device indicates an availability of the first user to communicate with the second user.
Independent claims5
63 paragraphs in 7 sections, as filed
CROSS-REFERENCES TO RELATED APPLICATIONS
0001This application is a continuation application of U.S. application Ser. No. 10/923,789 filed Aug. 24, 2004 now U.S. Pat. No. 7,068,770 which is a division of U.S. application Ser. No. 10/107,202 filed Mar. 28, 2002 (now U.S. Pat. No. 6,798,873) which is a continuation of U.S. application Ser. No. 09/104,970 filed Jun. 26, 1998 (now U.S. Pat. No. 6,389,127).
FIELD OF THE INVENTION
0002The present invention relates to telephone status notification systems in general, and more particularly to the use of computer networks to relay the status of one or more telephones.
BACKGROUND OF THE INVENTION
0003It is known to provide users connected via a computer terminal to a computer network with details of the network connection status of other users similarly connected. Applicant's U.S. patent application Ser. No. 08/791,437, incorporated herein by reference, discloses a system for providing a user with the network address, network connection status, and availability status of one or more users, to enable them, for example, to initiate a point to point connection with each other.
0004Public telephone systems, as presently constituted, generally only provide the status of a telephone at the time one attempts to establish a connection with it. Thus, one gets a busy signal, call waiting signal, or a ringing tone, etc. Some telephone carriers provide a service whereby a person who calls another party and receives a busy signal will be alerted when the telephone number called becomes available, but again status information is provided conditionally on having dialed a number previously. The ability to get an on-line report on the status of one or more telephone numbers automatically, or of receiving the logical status set by a user regarding his availability for a telephone call, as separate from its actual physical status, independent of the need to try to call the desired number, does not exist today among telephone carriers or telephone devices connected to the public telephone system, or the telephone line at home (as opposed to the carrier), or among telephone owners today. However, in general, all the necessary information exists or can be acquired, and can be made available by telephone carriers, by a telephone device which is connected to the system, or the telephone line at home which is connected to the public system, or by the telephone owner. PABXs and other specialized telephony systems such as call centers, telephony help desks, or Automatic Call Distribution Systems do posses the possibility of getting the status of their extensions, but while this information may be available to users connected to such systems by various known methods, it is not available to seeking users of the general public who are not subscribers or extensions of such systems.
SUMMARY OF THE INVENTION
0005The present invention seeks to provide a system for requesting the status of a telephone line, recognizing the status, and passing on the status to one or more requesting computer network addresses. The system additionally provides for automatic call-back and conferencing once a telephone line's status has been determined.
0006There is thus provided in accordance with a preferred embodiment of the present invention a telephone line status notification system including at least one telephone line having a status, a communications network, at least one communications terminal which is connectable to the communications network and which is employable by a seeking user to communicate via the communications network a status request concerning the status of the at least one telephone line, apparatus for processing the status request the apparatus for processing is connectable to the communications network for receiving the status request from the seeking user therethrough and communicating the request, and apparatus for acquiring the status of the at least one telephone line, the apparatus for acquiring is in communication with the apparatus for processing for receiving the status request therefrom, and the apparatus for acquiring is connectable to the communications network for communicating the status via the communications network.
0007Further in accordance with a preferred embodiment of the present invention the status request includes a unique identification of any of the users.
0008Still further in accordance with a preferred embodiment of the present invention apparatus is included for identifying a network address associated with the unique identification.
0009Additionally in accordance with a preferred embodiment of the present invention at least one server is included which is connectable to the communications network.
0010Moreover in accordance with a preferred embodiment of the present invention either of the apparatus for acquiring and the apparatus for processing is resident in the at least one server.
0011Further in accordance with a preferred embodiment of the present invention the apparatus for processing is resident in the communications terminal employable by the seeking user.
0012Still further in accordance with a preferred embodiment of the present invention a communications terminal employable by a sought user and connectable to the communications network is included.
0013Additionally in accordance with a preferred embodiment of the present invention a telephone connectable to the telephone line is included.
0014Moreover in accordance with a preferred embodiment of the present invention the apparatus for acquiring is resident in the telephone.
0015Further in accordance with a preferred embodiment of the present invention the apparatus for acquiring is resident in the communications terminal employable by the sought user.
0016Still further in accordance with a preferred embodiment of the present invention the sought user communicates the status to the apparatus for acquiring via the communications terminal employable by the sought user.
0017Additionally in accordance with a preferred embodiment of the present invention the telephone line is part of a PABX system, and the status is communicated to a user not regularly connected to the PABX system.
0018Further in accordance with a preferred embodiment of the present invention a cellular telephone in communication with the communications terminal employable by the seeking user is included.
0019Still further in accordance with a preferred embodiment of the present invention a cellular telephone in communication with the communications terminal employable by the sought user is included.
0020Additionally in accordance with a preferred embodiment of the present invention e the communications terminal employable by the seeking user is a cellular telephone.
0021Moreover in accordance with a preferred embodiment of the present invention the communications terminal employable by the sought user is a cellular telephone.
0022Further in accordance with a preferred embodiment of the present invention the communications terminal employable by the sought user is adapted to receive a call-back request from the seeking user and initiate a call to the seeking user via the telephone line.
0023Still further in accordance with a preferred embodiment of the present invention the seeking user has a telephone line status, and the communications terminal employable by the sought user is further adapted to initiate the call to the seeking user once the seeking user telephone line status has been determined.
0024Additionally in accordance with a preferred embodiment of the present invention the sought user has a telephone line status, and the communications terminal employable by the sought user is further adapted to initiate the call to the seeking user once the sought user telephone line status has been determined.
0025Moreover in accordance with a preferred embodiment of the present invention the sought user has a telephone line status, the seeking user has a telephone line status, and the communications terminal employable by the sought user is further adapted to initiate the call to the seeking user once either of the sought user telephone line status and the seeking user telephone line status has been determined.
0026Further in accordance with a preferred embodiment of the present invention apparatus is included for conferencing connectable to the communications network and adapted to receive a conferencing request from the seeking user and initiate a conference call between the seeking user and at least one sought user.
0027Still further in accordance with a preferred embodiment of the present invention the apparatus for conferencing is further adapted to first initiate a call to the seeking user and telephonically receive from the seeking user either of a telephone number of the sought user and an identifier associated with a telephone number of the sought user.
0028Additionally in accordance with a preferred embodiment of the present invention the at least one sought user has a telephone line status, and the apparatus for conferencing is further adapted to initiate the conference call once the sought user telephone line status has been determined.
0029Moreover in accordance with a preferred embodiment of the present invention the seeking user has a telephone line status, and the apparatus for conferencing is further adapted to initiate the conference call once the seeking user telephone line status has been determined.
0030Further in accordance with a preferred embodiment of the present invention the at least one seeking user has a telephone line status, the at least one sought user has a telephone line status, and the apparatus for conferencing is further adapted to initiate the conference call once either of the seeking user telephone line status and the sought user telephone line status has been determined.
0031Still further in accordance with a preferred embodiment of the present invention the apparatus for acquiring maintains at least one telephone number associated with at least one sought user.
0032Additionally in accordance with a preferred embodiment of the present invention the either of the apparatus for acquiring and the apparatus for processing includes apparatus for checking the status request from the seeking user for an authorization.
0033Moreover in accordance with a preferred embodiment of the present invention the communications network is the Internet.
0034Further in accordance with a preferred embodiment of the present invention the cellular telephone is adapted to communicate using either of IP protocols and non-IP protocols.
0035There is additionally provided in accordance with a preferred embodiment of the present invention a method for providing telephone line status, the method including providing at least one telephone line having a status, providing a communications network, communicating via the communications network a status request from a seeking user, the status request concerning the status of the at least one telephone line, acquiring the status of the at least one telephone line, and communicating the status via the communications network, thereby providing the telephone line status.
0036Further in accordance with a preferred embodiment of the present invention the communicating via the communications network a status request step includes communicating a unique identification of any of the users.
0037Still further in accordance with a preferred embodiment of the present invention the method includes identifying a network address associated with the unique identification.
0038Additionally in accordance with a preferred embodiment of the present invention the acquiring step includes acquiring the status of the at least one telephone line from a sought user.
0039Moreover in accordance with a preferred embodiment of the present invention the method includes the steps of receiving a call-back request from the seeking user at a sought user, and initiating a call-back to the seeking user from the sought user via the telephone line.
0040Further in accordance with a preferred embodiment of the present invention the method includes the steps of receiving a conferencing request from the seeking user, and initiating a conference call between the seeking user and at least one sought user.
0041Still further in accordance with a preferred embodiment of the present invention the initiating step includes initiating once either of the seeking user's telephone line status and the sought user's telephone line status has been determined.
0042Additionally in accordance with a preferred embodiment of the present invention the acquiring step includes checking the status request from the seeking user for an authorization.
0043Moreover in accordance with a preferred embodiment of the present invention the communicating the status step includes communicating the status to either of the seeking user and a recipient indicated in the status request.
0044It is noted that throughout the specification and claims the phrase “status of a telephone,” “status of a telephone number,” or derivations and permutations thereof refer to whether a telephone line at a given telephone number is physically in use or not, or whether it is logically “in use” or not, that is, whether or not the end-user or owner of a telephone line wishes to be contacted there through specifically by a telephone.
0045It is further noted that throughout the specification and claims the term “PABX” encompasses other specialized telephony systems such as call centers, telephony help desks, or Automatic Call Distribution Systems
0046It is further noted that throughout the specification and claims the term “user” encompasses any entity, preferably human, that operates a computer or other communications terminal, preferably for the purpose of connecting to and communicating via a communications network. It is further noted that the term “seeking user” encompasses any user who requests the status of a telephone line. It is further noted that the term “sought user” encompasses any user whose telephone line status is desired by a seeking user. It is further noted that the term “Internet” encompasses other communications systems using the Internet Protocol such as, but not limited to, “Intranet” and “Extranet” networks.
BRIEF DESCRIPTION OF THE DRAWINGS
0047The present invention will be understood and appreciated from the following detailed description, taken in conjunction with the drawings in which:
0048<figref idref="DRAWINGS">FIG. 1</figref> is a simplified block diagram of a telephone status notification system constructed and operative in accordance with a preferred embodiment of the present invention.
DESCRIPTION OF THE PREFERRED
EMBODIMENTS
0050The present invention will be understood and appreciated more fully from the following detailed description wherein reference is made, purely by way of example, to the following embodiments.
0051Reference is now made to <figref idref="DRAWINGS">FIG. 1</figref> which is a simplified block diagram of a telephone status notification system constructed and operative in accordance with a preferred embodiment of the present invention. A user <b>10</b> wishes to determine the status of a telephone line <b>14</b> associated with a user <b>12</b>. User <b>10</b> typically sends a request for telephone line status information to a request server <b>16</b>. The request typically comprises the telephone number, or other information identifying telephone line <b>14</b> associated with user <b>12</b>. User <b>10</b> typically sends the request via a computer terminal <b>18</b> connectable to a communications network such as the Internet, the request being sent using known Internet protocols. It is appreciated that the request may be sent by user <b>10</b> using any known messaging means, or may be sent via client software running on computer terminal <b>18</b>. User <b>10</b> may provide a list of such telephone numbers that is sent to the request server once for ongoing fulfillment or submitted each time user <b>10</b> connects to the Internet. Additionally or alternatively, user <b>10</b> may send individual telephone number status requests on an ad hoc basis for one-time fulfillment Each request typically comprises information identifying one or more telephones by their number, owner's name, or by any other identification method. Request server <b>16</b> is typically connectable to the Internet and is capable of receiving the request of user <b>10</b>. The request also preferably comprises a unique identification code and/or network address identifying user <b>10</b>, and a unique identification code and/or network address to which the notification of the status of telephone line <b>14</b> is to be sent. The request may also comprise one or more telephone numbers associated with user <b>10</b>. The request may also comprise a unique identification code and/or network address identifying user <b>12</b>. Any of the network addresses described hereinabove may be user <b>10</b>'s or user <b>12</b>'s permanent IP address, should user <b>10</b> or user <b>12</b> possess one. Where user <b>10</b> or user <b>12</b> have a dynamic IP address, the network address may be identified by other identifying information, such as a permanent subscriber code with which the dynamic IP address is related in a given session. Where a unique identification code is used, apparatus may be provided to determine a network address associated therewith. An example of this is described with reference to Applicant's U.S. patent application Ser. No. 08/791,437.
0052Request server <b>16</b> then typically forwards the request to a telephone status acquirer <b>20</b>, typically via the Internet. Telephone status acquirer <b>20</b> may be a server or other apparatus at a telephone company or other entity to which telephone line statuses may become known. It is appreciated that request server <b>16</b> and telephone status acquirer <b>20</b> may be housed within a single server. It is further appreciated that request server <b>16</b> may be embodied within client software running on computer terminal <b>18</b>, being capable of sending a request directly to the telephone status acquirer <b>16</b> as described hereinabove.
0053It is appreciated that telephone status acquirer <b>20</b> may be embodied within client software running on a computer terminal <b>22</b> used by user <b>12</b> that is connectable to the Internet. In this case, the client software typically determines the status of telephone line <b>14</b> by being in communication with a device that determines the on-hook/off-hook status of telephone line <b>14</b>. The device may be attached to the telephone line (a line detector), connected directly to a telephone <b>24</b>, be part of telephone <b>24</b> itself, or contained within computer terminal <b>22</b> to which telephone <b>24</b> or telephone line <b>14</b> may be connected via any one of a number of well-known interface devices. Alternatively, the client software can be integrated with and reside in telephone <b>24</b>. Alternatively, telephone line <b>14</b> may be a PABX extension. In this case, telephone status acquirer acquires the status from a known and integral part of a PABX system configured to determine the status of telephone line <b>14</b>, and then delivers the status, typically via the Internet or other non-PABX connection, to requesting server <b>16</b>, computer terminal <b>18</b>, or whatever destination or destinations specified in user <b>10</b>'s request. User <b>12</b> may additionally or alternatively enter the physical status of telephone line <b>14</b> into the client software to indicate that telephone line <b>14</b> is busy, available, etc., and/or “logical” telephone statuses such as “available/not available for calls,” or more detailed status information such as “available for calls, but only to the following list of users . . . ” and the like.
0054User <b>12</b> may additionally or alternatively enter one or more telephone numbers with which user <b>12</b> is associated into the client software. Should user <b>10</b> not know with which telephone number user <b>12</b> is associated, or otherwise not wish to refer to user <b>12</b> by a telephone number, user <b>10</b> may include information in his request identifying user <b>12</b> by means other than a telephone number. In this case, the status returned typically includes a telephone number or numbers entered by user <b>12</b> into client software as described hereinabove. Alternatively, user <b>10</b> may request the statuses of telephone numbers user <b>12</b> uses regularly, typically with telephone status acquirer <b>20</b> or request server <b>16</b> storing one or more telephone numbers recently used by user <b>12</b>.
0055Requesting server <b>16</b> or telephone status acquirer <b>20</b> may be provided with means for checking the authorization of user <b>10</b> to request the status of telephone line <b>14</b> before divulging such. For example, the status may only be divulged if user <b>10</b> possesses a certain security rating or a certain level of account, or if user <b>10</b> provides a given password.
0056In response to the request forwarded from request server <b>16</b>, telephone status acquirer <b>20</b> preferably sends the requested status information to the destination address or addresses indicated by user <b>10</b>. It is appreciated that user <b>10</b>'s request may specify different destinations depending on the nature of the status determination.
0057User <b>10</b> may alternatively input telephone line status requests into a cellular telephone <b>26</b>. In this case, the cellular telephone company, or the Internet Service Provider with which cellular telephone <b>26</b> is in contact, typically forwards the request to request server <b>16</b> as described hereinabove. Client software may reside in cellular telephone <b>26</b>. Cellular telephone <b>26</b> may additionally be connected to the Internet or other communications network. The client software residing in cellular telephone <b>26</b> typically generally functions as described hereinabove with reference to computer terminal <b>18</b>, with telephone status information preferably being displayed on cellular telephone <b>26</b>'s display. It is appreciated that request server <b>16</b> may be embodied within client software running on cellular telephone <b>26</b> being capable of sending a request directly to the telephone status acquirer <b>16</b> as described hereinabove. It is further appreciated that cellular telephone <b>26</b> may be used alone or in combination with computer terminal <b>18</b>, and that cellular telephone <b>26</b> may communicate using IP or other protocols.
0058User <b>12</b> may additionally or alternatively communicate via a cellular telephone, which may comprise any of the client software and functionality described herein with reference to computer terminal <b>22</b> and telephone <b>24</b>. It is appreciated that the cellular telephone of user <b>12</b> may be used alone or in combination with computer terminal <b>22</b> and telephone <b>24</b>, and that the cellular telephone of user <b>12</b> may communicate using IP or other protocols.
0059It is appreciated that the client software described hereinabove with reference to the cellular telephones of users <b>10</b> and <b>12</b> may reside in a computer located remotely from the cellular telephone. In this case, communication between the cellular telephones of users <b>10</b> and <b>12</b> and the client may use IP or other protocols.
0060It will be appreciated that a notification system as described hereinabove may be used to provide other kinds of status information, for example the statuses of monitors, sensors, or measuring apparatus and/or logical statuses input by the user. It will be further appreciated that a notification system as described hereinabove may be used in conjunction with IP telephones designed for use with the Internet, where the IP telephones comprise computer circuitry and voice processing capability. In addition, a notification and acquisition system as described hereinabove may be used in conjunction with communication devices using CATV as part of the network infrastructure.
0061It is appreciated that once user <b>10</b> receives telephone number and other status information associated with user <b>12</b> as described hereinabove, or once it is stored in his client software, user <b>10</b> may send a request to computer terminal <b>22</b>, typically via the Internet, for a telephone call to be placed from user <b>12</b> to user <b>10</b>. Client software residing in computer terminal <b>22</b> may automatically place a call to user <b>10</b> either immediately, or when the telephone line statuses of user <b>10</b> and/or user <b>12</b> become known to computer terminal <b>22</b>.
0062User <b>10</b> may alternatively send a request, typically via the Internet, to an operator or an automatic telephone switch <b>28</b> to initiate two calls, one to user <b>10</b> and one to user <b>12</b>, and conference the two calls using known conferencing means. User <b>10</b> typically can configure his client software to send the telephone numbers for himself and for user <b>12</b>, or other means of identifying user <b>10</b> and user <b>12</b>, in addition to billing information indicating who should be billed for the call, along with proper authorization. User <b>10</b> may request a conference call with more than one user by sending multiple telephone numbers and/or identifiers in this manner. User <b>10</b> may additionally indicate if a conference call is to be tried immediately, with calls to be conferenced-in as the specified telephone numbers become available, or tried only when all the telephone numbers requested for a conference are known to be available, such as through requesting the status of the telephone numbers as described hereinabove. User <b>10</b> may also initiate a call back, delivering his telephone number and availability to an automated switch, to be conferenced with one of the switch's outgoing dialing lines. User <b>10</b> may additionally indicate if a call back is to be tried immediately or tried only when the telephone number with which the call back is concerned is known to be available, such as through requesting the status of the telephone number as described hereinabove.
0063It is appreciated that various features of the invention which are, for clarity, described in the context of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment may also be provided separately or in any suitable combination.
0064It will be appreciated by persons skilled in the art that the present invention is not limited to what has been particularly shown and described hereinabove. Rather, the scope of the present invention is defined only by the claims that follow:
Contents7
Every citation, both waysCites: the store holds 78 of 79
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP0123456A2 | Cites | European Patent Office (EPO) | Applicant |
| US2002034289A1 | Cites | United States of America | Applicant |
| US2002159577A1 | Cites | United States of America | Search report |
| US2004109551A1 | Cites | United States of America | Applicant |
| US2005025301A1 | Cites | United States of America | Search report |
| US2006233324A1 | Cites | United States of America | Search report |
| US4599493A | Cites | United States of America | Search report |
| US4653090A | Cites | United States of America | Applicant |
| US4812843A | Cites | United States of America | Search report |
| US4817127A | Cites | United States of America | Applicant |
| US4839917A | Cites | United States of America | Search report |
| US4937851A | Cites | United States of America | Search report |
| US4991203A | Cites | United States of America | Search report |
| US5018189A | Cites | United States of America | Search report |
| US5020095A | Cites | United States of America | Applicant |
| US5136501A | Cites | United States of America | Applicant |
| US5214688A | Cites | United States of America | Search report |
| US5245656A | Cites | United States of America | Applicant |
| US5276736A | Cites | United States of America | Applicant |
| US5297195A | Cites | United States of America | Search report |
| US5327486A | Cites | United States of America | Applicant |
| US5418970A | Cites | United States of America | Applicant |
| US5450468A | Cites | United States of America | Search report |
| US5471525A | Cites | United States of America | Applicant |
| US5475737A | Cites | United States of America | Applicant |
| US5483586A | Cites | United States of America | Applicant |
| US5506891A | Cites | United States of America | Applicant |
| US5533110A | Cites | United States of America | Applicant |
| US5535256A | Cites | United States of America | Applicant |
| US5535261A | Cites | United States of America | Applicant |
| US5557659A | Cites | United States of America | Applicant |
| US5568540A | Cites | United States of America | Applicant |
| US5583920A | Cites | United States of America | Applicant |
| US5585858A | Cites | United States of America | Applicant |
| US5588051A | Cites | United States of America | Search report |
| US5592534A | Cites | United States of America | Applicant |
| US5608786A | Cites | United States of America | Applicant |
| US5610910A | Cites | United States of America | Applicant |
| US5625676A | Cites | United States of America | Applicant |
| US5635693A | Cites | United States of America | Applicant |
| US5651054A | Cites | United States of America | Applicant |
| US5652789A | Cites | United States of America | Applicant |
| US5657376A | Cites | United States of America | Applicant |
| US5726948A | Cites | United States of America | Applicant |
| US5726984A | Cites | United States of America | Applicant |
| US5742905A | Cites | United States of America | Applicant |
| US5764756A | Cites | United States of America | Search report |
| US5774668A | Cites | United States of America | Applicant |
| US5790548A | Cites | United States of America | Applicant |
| US5799016A | Cites | United States of America | Search report |
| US5805164A | Cites | United States of America | Applicant |
| US5835566A | Cites | United States of America | Search report |
| US5862203A | Cites | United States of America | Applicant |
| US5884032A | Cites | United States of America | Applicant |
| US5946386A | Cites | United States of America | Applicant |
| US5956485A | Cites | United States of America | Applicant |
| US5978672A | Cites | United States of America | Applicant |
| US5995595A | Cites | United States of America | Applicant |
| US6031895A | Cites | United States of America | Applicant |
| US6078579A | Cites | United States of America | Applicant |
| US6104711A | Cites | United States of America | Applicant |
| US6104909A | Cites | United States of America | Search report |
| US6108704A | Cites | United States of America | Applicant |
| US6144848A | Cites | United States of America | Applicant |
| US6249576B1 | Cites | United States of America | Search report |
| US6252869B1 | Cites | United States of America | Applicant |
| US6263049B1 | Cites | United States of America | Applicant |
| US6343115B1 | Cites | United States of America | Applicant |
| US6389127B1 | Cites | United States of America | Search report |
| US6445733B1 | Cites | United States of America | Search report |
| US6483900B1 | Cites | United States of America | Applicant |
| US6563914B2 | Cites | United States of America | Search report |
| US6661779B2 | Cites | United States of America | Applicant |
| US6798873B2 | Cites | United States of America | Search report |
| US7068770B2 | Cites | United States of America | Search report |
| US7778396B2 | Cites | United States of America | Search report |
| WO9714234A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO9746955A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| http://sunsite.doc.csacsuldpublic/packages/R5contrib/xhtalk-2.9 READDME May 26, 1998. | Non-patent | – | Applicant |
| Muller, "Dial 1-800-Internet With New Software, You Can Talk Business Over the Net and Avoid Long-Distance Charges", Byte, vol. 21, No. 2, Feb. 1, 1996, pp. 83/84, 86, 88. | Non-patent | – | Applicant |
| Wayner, "Hey Baby, Call Me at My IP Address", byte, vol. 21, No. 4, Apr. 1, 1996, pp. 142-144. | Non-patent | – | Applicant |
| Business Week, Sep. 9, 1996, p. 120, No. 3492, Journal Code: BW, Section Heading: Personal Business: Online. | Non-patent | – | Applicant |
| Internet Online Services: Communications, Supplier No. 19254182, Mooradian, Mark: Keane, Patrick, Interactive Content, v2,p. 7(1), Oct. 1996. | Non-patent | – | Applicant |
| Keizer, "Comprehensive Collaboration Comes Cheap", CNET Reviews, NetMeeting 1.0 Beta 1, Jul. 16, 1996, http://www.cnet.com , pp. 1-2. | Non-patent | – | Applicant |
| Murman et al., Perspectives on Project Athena, ACM SIGUCCS XVIII 1990, pp. 287-296. | Non-patent | – | Applicant |
| Fermann, Distributed Consulting in a Distributed Environment, ACM SIGUCCS XVIII 1990, pp. 117-120. | Non-patent | – | Applicant |
| French et al., The Zeohyr Programmer's Manual, Protocol Version ZEPHO.1, Apr. 5, 1989, pp. 1-82. | Non-patent | – | Applicant |
| Zephyr on Athena (AC-34) Draft, [online], [retrieved on Jan. 27, 2003], Retrieved from the Internet: URL:http://web.mitsedu/olh/zephyr/TOC.html. | Non-patent | – | Applicant |
| Zephyr (1) Manual Page, Jul. 1, 1998, [online], [retrieved on Jan. 27, 2003]. Retrieved from the Internet: URL:http://www.tru64unix.compaq.com/demos/ossc-v51a/man-htm/zephyr-man.html. | Non-patent | – | Applicant |
| Zephyr Answers, [online], [retrieved on Jan. 27, 2003]. Retrieved from the Internet: URL:http://web.mit.edu/answers/zephyr. | Non-patent | – | Applicant |
| Sharon Belville et al., Zephyr at CERN, Jul. 15, 1993, [online], [retrieved on Jan. 27, 2003]. Retrieved from the Internet: URL:http://consultscernsch/writeup/zephyr/main.html. | Non-patent | – | Applicant |
| Cohen et al., Inessential Zephyr, [online], [retrieved on Jan. 28, 2003], Retrieved from the Internet: URL:http://www.mit.edu/afs/sipb/project/doc/izephyr/html/izephyr.html. | Non-patent | – | Applicant |
| Finding Several Users, Jul. 14, 1994 [online], [retrieved on Jan. 27, 2003]. Retrieved from the Internet: URL:http://consultscernsch/writeup/zephyr/subsectionstar2 2 3 2.html. | Non-patent | – | Applicant |
| C. Anthony DellaFera, et al., The Zephyr Notification Service, pp. 1-9 (circa 1988). | Non-patent | – | Applicant |
| U.S. Appl. No. 10/107,012, filed May 6, 2003, Office Action. | Non-patent | – | Applicant |
| Profile: AOL Technology:Turning Complicated Things Into Engaging Services, 1996 Annual Report. | Non-patent | – | Applicant |
| U.S. Appl. No. 10/923,789, filed Feb. 6, 2006, Notice of Allowance. | Non-patent | – | Applicant |
| U.S. Appl. No. 10/923,789, filed Oct. 20, 2005, Office Action. | Non-patent | – | Applicant |
| U.S. Appl. No. 10/923,789, filed May 4, 2005, Office Action. | Non-patent | – | Applicant |
| U.S. Appl. No. 11/430,109, filed Jun. 25, 2009, Office Action. | Non-patent | – | Applicant |
25 members in 10 offices
Priority claims23
| Document | Office | Kind | Date |
|---|---|---|---|
| 121501 | Israel | – | |
| 12150197 | Israel | A | |
| 12150197 | Israel | A | |
| 10497098 | United States of America | A | |
| 10497098 | United States of America | A | |
| 10720202 | United States of America | A | |
| 10720202 | United States of America | A | |
| 92378904 | United States of America | A | |
| 92378904 | United States of America | A | |
| 43010906 | United States of America | A | |
| 43010906 | United States of America | A | |
| 201213588982 | United States of America | A | |
| 09104970 | – | – | – |
| 10107202 | – | – | – |
| 10923789 | – | – | – |
| 11430109 | – | – | – |
| 121501 | – | – | – |
| IL19970121501 | – | – | – |
| US19980104970 | – | – | – |
| US20020107202 | – | – | – |
| US20040923789 | – | – | – |
| US20060430109 | – | – | – |
| US201213588982 | – | – | – |
Members25
| Document | Office | Kind | |
|---|---|---|---|
| IL121501D0 | Israel | D0 | |
| CA2299422A1 | Canada | A1 | |
| CA2568095A1 | Canada | A1 | |
| WO9908434A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU8032798A | Australia | A | |
| EP1002417A1 | European Patent Office (EPO) | A1 | |
| BR9813007A | Brazil | A | |
| CN1280737A | China | A | |
| JP2001513603A | Japan | A | |
| US6389127B1 | United States of America | B1 | |
| AU749596B2 | Australia | B2 | |
| US2002159577A1 | United States of America | A1 | |
| IL121501A | Israel | A | |
| US6798873B2 | United States of America | B2 | |
| US2005025301A1 | United States of America | A1 | |
| US7068770B2 | United States of America | B2 | |
| CN1278537C | China | C | |
| US2006233324A1 | United States of America | A1 | |
| CA2299422C | Canada | C | |
| CA2568095C | Canada | C | |
| US7778396B2 | United States of America | B2 | |
| EP1002417B1 | European Patent Office (EPO) | B1 | |
| AT527811T | Austria | T | |
| ATE527811T1 | Austria | T1 | |
| USRE45136EThis record | United States of America | E |
94 transactions on the USPTO file
Allowed after 2 non-final rejections.
- Non-final rejections
- 2
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Printer Rush- No mailingTCPB | TCPB | |
| Printer Rush- No mailingTCPB | TCPB | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Terminal Disclaimer FiledDIST | DIST | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Non-Compliant Preliminary AmendmentMNPRL | MNPRL | |
| Non-Compliant Preliminary AmendmentNPRL | NPRL | |
| Application Is Now CompleteCOMP | COMP | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail-Petition Decision - GrantedMPTGR | MPTGR | |
| Mail-Petition to Revive Application - GrantedMPREV | MPREV | |
| Petition Decision - GrantedPTGR | PTGR | |
| Petition to Revive Application - GrantedPREV | PREV | |
| Petition EnteredPET. | PET. | |
| Payment of additional filing fee/PreexamFLFEE | FLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Petition EnteredPET. | PET. | |
| Mail-Record Petition Decision of Granted to Suspend an ActionMP002 | MP002 | |
| Record Petition Decision of Granted to Suspend an ActionP002 | P002 | |
| Petition EnteredPET. | PET. | |
| Preliminary AmendmentA.PE | A.PE | |
| Notice of Reissue Published in Official GazetteNRE. | NRE. | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Cleared by OIPE CSRL194 | L194 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Preliminary AmendmentA.PE | A.PE | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Claim Preliminary AmendmentCLAIM | CLAIM | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- RE045136
- Publication, DOCDB
- RE45136
- Publication, EPODOC
- USRE45136E
- Application
- 13588982
- Application, DOCDB
- 201213588982
- Application, EPODOC
- US201213588982
Titles
- English
- Telephone status notification system
Classification
- CPC, 11
- H04M3/42374
- H04M1/82
- H04M3/42
- H04M3/42093
- H04M3/42365
- H04M3/48
- H04M3/56
- H04M7/006
- H04M7/12
- Y10S379/913
- Y10S379/90
- IPC, 14
- H04M3 22
- H04M1 64
- H04M11 06
- H04M3 42
- H04M3 48
- H04M3 56
- H04M7 00
- H04M7 12
- H04W4 06
- H04W4 16
- H04W8 24
- H04W8 26
- H04W84 16
- H04W88 14
- USPC, 12
- 379088120
- 348485000
- 370260000
- 370401000
- 375222000
- 375231000
- 379015010
- 379022070
- 379045000
- 379093010
- 379243000
- 455425000