Maintaining a message thread with opt-in permanence for entries

Information

  • Patent Grant
  • 12212536
  • Patent Number
    12,212,536
  • Date Filed
    Friday, May 24, 2024
    8 months ago
  • Date Issued
    Tuesday, January 28, 2025
    11 days ago
  • CPC
    • H04L51/216
  • Field of Search
    • US
    • NON E00000
  • International Classifications
    • H04L51/216
    • Disclaimer
      This patent is subject to a terminal disclaimer.
      Term Extension
      0
Abstract
A server has a processor and a memory storing a message thread module with instructions executed by the processor to maintain a message thread between users of client devices. The message thread module serves a message thread with a new text entry to a client device in response to a request for the message thread from a user. Message thread state change is collected from the client device, where the message thread state change represents an indication to automatically delete the new text entry of the message thread after the duration of a transitory display period on the client device unless an indication of a gesture applied to a display screen presenting the new text entry of the message thread is received from the client device during the transitory display period. The message thread state change is queued at the server along with additional message thread state changes associated with the collecting operation performed for additional users associated with the message thread. The message thread is revised based upon the message thread state change and the additional message thread state changes to form shared message thread state. The shared message thread state is stored. The shared message thread state is supplied in response to a request for the message thread from a user.
Description
FIELD OF INVENTION

This invention relates generally to communications in a networked environment. More particularly, this invention relates to maintaining a message thread with opt-in permanence for entries.


BACKGROUND OF THE INVENTION

Communications between individuals are increasingly digitized and transmitted via the Internet. Individuals are communicating through text messages, email messages, voice mail messages and the like. In the case of a text message between two individuals a conversation thread is maintained. Each individual contributes text to a chronologically listed record of the communications between the two individuals. With each new communication, a new entry is added to the communication thread. Either individual can review the conversation thread at any time and edit it locally in the messaging client.


Maintaining a complete and precise record of a sequence of communication may inhibit the spontaneity of an interaction. For example, when one has a conversation with an individual, it is typically not recorded and therefore the exchange may be more candid.


A live conversation between two individuals may be memorialized with notes, but in this case there is visual feedback indicating when one individual is recording information, which allows the other individual to clarify a point or otherwise alter the direction of the conversation.


Storing the entire contents of a digital conversation may also make it difficult to surface the most important information. It is a case of information overload. Selectively saving certain communications in an ephemeral conversation thread allows the user to quickly recall or reference important aspects of the thread.


In view of the foregoing, it would be desirable to have a digital communication mechanism that more naturally mimics the types of interactions to which individuals are accustomed.


SUMMARY OF THE INVENTION

A server has a processor and a memory storing a message thread module with instructions executed by the processor to maintain a message thread between users of client devices. The message thread module serves a message thread with a new text entry to a client device in response to a request for the message thread from a user. Message thread state change is collected from the client device, where the message thread state change represents an indication to automatically delete the new text entry of the message thread after the duration of a transitory display period on the client device unless an indication of a gesture applied to a display screen presenting the new text entry of the message thread is received from the client device during the transitory display period. The message thread state change is queued at the server along with additional message thread state changes associated with the collecting operation performed for additional users associated with the message thread. The message thread is revised based upon the message thread state change and the additional message thread state changes to form a single shared message thread state. The shared message thread state is stored. The single shared message thread state is supplied in response to a request for the message thread from a user.





BRIEF DESCRIPTION OF THE FIGURES

The invention is more fully appreciated in connection with the following detailed description taken in conjunction with the accompanying drawings, in which:



FIG. 1 illustrates a system configured in accordance with an embodiment of the invention.



FIG. 2 illustrates message generation processing utilized in accordance with an embodiment of the invention.



FIG. 3 illustrates message consumption processing utilized in accordance with an embodiment of the invention.



FIG. 4 illustrates message thread review processing utilized in accordance with an embodiment of the invention.



FIG. 5 illustrates a first message thread displayed in accordance with an embodiment of the invention.



FIG. 6 illustrates the message thread of FIG. 5 with altered parameters associated with entries of the message thread.



FIG. 7 illustrates asynchronous batch mode processing performed in accordance with an embodiment of the invention.





Like reference numerals refer to corresponding parts throughout the several views of the drawings.


DETAILED DESCRIPTION OF THE INVENTION


FIG. 1 illustrates a system 100 configured in accordance with an embodiment of the invention. The system 100 includes a set of client devices 102_1 through 102_N and at least one server 104 connected via a network 106, which may be any wired or wireless network.


Each client device 102 may be a computer, tablet, Smartphone and the like with standard components, such as a central processing unit 110 connected to input/output devices 112 via a bus 114. The input/output devices 112 may include a touch display, keyboard, mouse and the like. A network interface circuit 116 is also connected to the bus 114 to provide connectivity with network 106.


A memory 120 is also connected to the bus 114. The memory 120 stores standard components, such as a communication module 122. The communication module 122 may be a text message module that supports ShortMessage Service (SMS) texting. Alternately, the communication module 122 may be a browser, which supports access to an email server. Alternately, the communication-module 122 may be a telephony interface that supports telephone interactions, such as voice messages.


Server 104 also includes standard components, such as a central processing unit 160 connected to input/output devices 164 via a bus 162. A network interface circuit 166 is also connected to the bus 162. Further, a memory 170 is connected to the bus 162. The memory 170 stores modules of executable instructions to implement disclosed operations. For example, the memory 170 may store a message thread module 172, which maintains a thread of communications between at least two individuals. The thread of communications may be a text message thread, an email with a sequence of returned communications or a voice mail file with a sequence of returned communications.


The configuration of system 100 is exemplary. The system 100 may include multiple servers 104 and a variety of communication devices to support various forms of digital communication.



FIG. 2 illustrates processing operations associated with an embodiment of the message thread module 172. In particular, the figure illustrates message generation processing utilized in accordance with an embodiment of the invention. By way of example, operations will be discussed in the context of text messaging.


Initially, a transitory display parameter is set 200. The transitory display parameter may be set as a default value (e.g., a 3 second viewing period) or it may be set through user input. The notion associated with the transitory display parameter is that all message entries will be deleted after the transitory display parameter time expires and therefore message entries are transitory, unless an individual opts-in for message entry permanence.


The next operation of FIG. 2 is to collect a text entry 202. The text entry collection process is terminated when an individual indicts that the text entry should be sent. At this point it is determined if there was an indication to save the text entry 204. The indication may be in the form of a gesture applied to the screen where the text is entered. Alternately, the indication may be based upon a specified key or combination of keys on a keyboard used to enter the text.


If there is no indication to save the entry (204—No), then the text is displayed in the thread associated with the sender and the recipient. When the recipient reads or otherwise consumes the entry, the entry is deleted from the thread associated with the sender 206.


If there is an indication to save the entry (204—Yes), then the entry is displayed in its original form in the thread associated with the sender and the recipient. A check is periodically made to determine if the entry has been read by the recipient 210. If not (210—No), the entry continues to be displayed in its original form. If so (210—Yes), indicia associated with the thread is altered 212. That is, after the recipient reads the entry the nature of the entry will be altered on the sending side and the receiving side. If the recipient does not provide an indication to save the entry, then the indicia of the entry on the sending side thread will be altered to indicate that only one of the two parties (the sender) has saved the entry. If the recipient provides an indication to save the entry, then the indicia of the entry on the sending side and the receiving side is altered to indicate that both of the parties have saved the entry. In an alternate embodiment, the message may be restored in the sender side thread if the recipient provides an indication to save the message. This restoration in the sender side thread includes indicia that the recipient saved the message, although the sender originally declined to do so.


The operations of FIG. 2 are performed by the message thread module 172 operating in conjunction with a client device 102. That is, operations such as collecting a text entry 202 and identifying an indication to save 204 are performed at the client device 102, with the results of the operations passed and processed to the message thread module 172. Similarly, the display until consumed operation 206, display operation 208 and altering of thread indicia 212 are manifested at the client device 102 in response to information supplied by the message thread module 172.



FIG. 3 illustrates message consumption processing operations performed in accordance with an embodiment of the invention. The message thread module 127 coordinates the delivery of the text to the recipient 300. The text is displayed for the duration of the transitory display parameter 302. That is, the message thread module 127 directs the client device 102 to display the text for the duration of the transitory display parameter. Alternately, the text may be displayed until it is actively deleted or the user scrolls past it without saving it.


It is determined whether there is an indication to save the entry 304 during the duration of the transitory display parameter. If not (304—No), the message is deleted 306 from the recipient's thread. Thread indicia of the sender is altered, if necessary 308. That is, if the sender elected to preserve the entry, then indicia associated with the entry would be altered to indicate that the sender preserved the entry, but the recipient did not.


If there is an indication to save the entry (304—Yes), the entry is saved in the recipient's thread 310. The thread indicia are altered 312 to at least indicate that the recipient has saved the entry. If the sender also saved the entry, then the sender's indicia and the recipient's indicia reflect that both entities have saved the message.



FIG. 4 illustrates thread review processing that may be performed in accordance with an embodiment of the invention. Initially, a text thread is displayed to a user 400. The text thread is between the user and one or more other users. As the user scrolls through the text thread, individual entries may be deleted. If so (402—Yes), the individual entry is deleted 404. If necessary, indicia associated with the entry on another device is altered 406. For example, if another user had saved the entry and the present user had saved the entry initially, then the indicia associated with the entry on the two client devices would indicate that both parties saved the entry. After one party deletes the entry, the indicia associated with the entry for the other party indicates that only a single party has saved the entry.



FIG. 5 illustrates a client device 102 with a display screen 500 and a keyboard 502. The display screen 500 displays a thread including a first entry 504 from a first user and a second entry 506 from a second user. The first entry 504 is persisted in response to a gesture applied to the display screen 500. The second entry 506 is also persisted in response to a gesture applied to the display screen 500.



FIG. 6 illustrates updated indicia indicating different states of entry preservation. Entry 504′ is in bold to reflect that both the sender and the recipient persisted the entry. Entry 506′ is italicized to indicate that the reply was preserved by the recipient, but not the sender.


Thus, in this example, a parameter in the form of varying fonts is altered to reflect the persistence of an entry. Other parameters may be used, such as a separate graphic indicative of the preservation states. Alternately, the parameter may be in the form of a number where a 1 indicates that only the user of the client device has saved the entry and where the number 2 indicates that two parties have saved the entry. Larger numbers may be used in the event of a group message. A text color scheme may also be used to indicate preservation states.


In one embodiment, the message thread module 172 is configured to eliminate the ability to copy/paste a conversation? This prevents aspects of the conversation from being taken out of context. In addition, this feature keeps the record of the “saved” communications consistent.


Thus, it will be appreciated that the disclosed techniques allow for a digital communication mechanism that more naturally mimics the types of interactions to which individuals are accustomed. That is, individual utterances (entries) are transitory in nature, unless a user opts-in to preserve an utterance. Opting-in to preserve an utterance may result in feedback that allows a counter-party to know that another has preserved the entry.


In addition to providing a more natural communication flow, the invention may provide a more condensed communication thread where only perceived important entries are preserved. This can be advantageous in connection with the use of a mobile device, which has a small screen and therefore a limited ability to display information. This may also be advantageous as it reduces the amount of information that needs to be communicated across a network.


The invention has been disclosed in the context of text communications. However, the same techniques may be applied to email communications or threaded voicemail or multimedia communications.


This disclosure has discussed real time updates to a message thread. An embodiment of the invention reduces computation demand by utilizing batch mode asynchronous processing. The message thread module 172 may be configured to implement such operations, as shown in FIG. 7. Initially, a request for a message thread is received 700. The message thread is associated with two or more users, any of which may request the message thread. The request is typically in response to an indication of a new text entry in the message thread. The message thread is served 702. Message thread state change, if any, is collected 704. The message thread state change represents an indication to automatically delete the new text entry of the message thread after the duration of a transitory display period on the client device unless an indication of a gesture applied to a display screen presenting the new text entry is received from the client device during the transitory display period. The state change may be queued at the server instantaneously or when the user exits the message thread (706—Yes). State changes, if any, are queued by the server 708. It should be appreciated that the queued messages may include message thread state change from the recently served message thread and/or additional message thread state changes from previously and subsequently served message threads to other users associated with the message thread.


A synchronization condition may then be applied 710. The synchronization condition may be a specified time of day. For example, batch mode asynchronous processing may be performed in the middle of the night when there is typically low demand on computational resources. If the synchronization condition is satisfied (710—Yes), the shared thread state is revised based on queued thread state changes 712. That is, the message thread is revised based upon all message thread state change associated with the message thread to produce new shared message thread state, which may be persistently stored until the next synchronization event. The new shared message thread state is supplied 702 in response to a request for the message thread from a user (700—Yes).


Techniques of the invention may be used in connection with non-textual communications, such as a thread of exchanged photographs. Further, the techniques of the invention may be used in connection with a variety of user inputs, such as a mouse click associated with a desktop computer, a gesture applied to a controller associated with a game console, a shaking motion applied to a mobile device and the like.


An embodiment of the present invention relates to a computer storage product with a non-transitory computer readable storage medium having computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media, optical media, magneto-optical media and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (“ASICs”), programmable logic devices (“PLDs”) and ROM and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter. For example, an embodiment of the invention may be implemented using JAVA®, C++, or other object-oriented programming language and development tools. Another embodiment of the invention may be implemented in hardwired circuitry in place of, or in combination with, machine-executable software instructions.


The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that specific details are not required in order to practice the invention. Thus, the foregoing descriptions of specific embodiments of the invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed; obviously, many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, they thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the following claims and their equivalents define the scope of the invention.

Claims
  • 1. A method comprising: responsive to determining that a request to preserve one or more content items has been received, modifying, by one or more processors, a display attribute of textual content based on a quantity of users in a set of users from which the request to preserve was received; andincrementing a displayed value each time a request to preserve the one or more content items is received from the set of users.
  • 2. The method of claim 1, further comprising: receiving, from a first device, the one or more content items exchanged in a communication session, the textual content being displayed by the first device according to a given display attribute, wherein as a result of modifying the display attribute, the textual content being displayed by the first device changes from being displayed according to the given display attribute to being displayed according to a different display attribute.
  • 3. The method of claim 2, wherein the one or more content items are directed to a second device, further comprising: displaying the one or more content items by the second device;determining that the request to preserve the one or more content items was received from (1) either the first device or the second device or (2) from both the first and second devices;modifying the given display attribute according to which of the one or more content items are being displayed by the second device in a first manner, in response to determining that the request to preserve the one or more content items is received from either the first device or the second device; andmodifying the given display attribute according to which of the one or more content items are being displayed by the second device in a second manner, in response to determining that the request to preserve the one or more content items is received from both the first and second devices.
  • 4. The method of claim 2, further comprising: receiving from the first device the request to preserve the one or more content items, wherein the request to preserve the one or more content items is received from the first device in response to a first gesture applied to a first display screen of the first device.
  • 5. The method of claim 1, further comprising automatically deleting the one or more content items displayed by a second device after duration of a display period unless the request to preserve the one or more content items is received from the second device during the display period.
  • 6. The method of claim 5, further comprising: receiving the request to preserve the one or more content items from the second device during the display period; andin response to receiving the request to preserve the one or more content items:generating an altered text indicia;maintaining the one or more content items displayed on the second device with the altered text indicia; andproviding feedback to a first device indicating that the request to preserve the one or more content items was received from the second device.
  • 7. The method of claim 1, wherein the textual content includes a first textual entry and a second textual entry, further comprising: causing a first device to display simultaneously the first and second textual entries with different display attributes, wherein the first textual entry is displayed with a given display attribute modified in a first manner to indicate that the request to preserve the one or more content items was received from either the first device or a second device, and wherein the second textual entry is displayed with the given display attribute modified in a second manner to indicate that the request to preserve the one or more content items was received from both the first and second devices.
  • 8. The method of claim 7, wherein the first textual entry was received from the first device and the second textual entry was received from the second device.
  • 9. The method of claim 1, further comprising providing first indicia indicating that only a first device requested to preserve the one or more content items and that there was no request to preserve the one or more content items received from a second device.
  • 10. The method of claim 9, further comprising providing a second indicia to indicate that both the first device and the second device requested to preserve the one or more content items.
  • 11. The method of claim 1, wherein modifying the display attribute comprises italicizing text included in the one or more content items.
  • 12. The method of claim 1, wherein modifying the display attribute comprises displaying text included in the one or more content items in bold.
  • 13. The method of claim 1, wherein modifying the display attribute comprises presenting text included in the one or more content items in a first color or with a first number.
  • 14. The method of claim 1, further comprising preventing a portion of the set of users from performing a copy/paste operation in relation to the one or more content items.
  • 15. The method of claim 1, wherein the one or more content items are presented at a same time on both a first device and a second device.
  • 16. The method of claim 1, wherein the one or more content items comprise a text communication, email communication, voicemail communication, or multimedia communication.
  • 17. The method of claim 1, wherein the one or more content items are part of a content item thread among a plurality of users.
  • 18. The method of claim 1, further comprising automatically deleting the one or more content items when a user scrolls past the one or more content items without requesting to preserve the one or more content items.
  • 19. A system comprising: one or more processors configured to perform operations comprising:responsive to determining that a request to preserve one or more content items has been received, modifying a display attribute of textual content based on a quantity of users in a set of users from which the request to preserve was received; andincrementing a displayed value each time a request to preserve the one or more content items is received from the set of users.
  • 20. A non-transitory computer readable medium comprising non-transitory computer readable instructions that, when executed by one or more processors, perform operations comprising: responsive to determining that a request to preserve one or more content items has been received, modifying a display attribute of textual content based on a quantity of users in a set of users from which the request to preserve was received; andincrementing a displayed value each time a request to preserve the one or more content items is received from the set of users.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/970,003, filed Oct. 20, 2022, which is a continuation of U.S. patent application Ser. No. 17/402,316, filed Aug. 13, 2021, which is a continuation U.S. patent application Ser. No. 16/552,018, filed Aug. 27, 2019, which is a continuation of U.S. patent application Ser. No. 15/682,404, filed Aug. 21, 2017, which is a continuation of U.S. patent application Ser. No. 14/274,610, filed May 9, 2014, which is a continuation-in-part of U.S. patent application Ser. No. 13/906,261, filed May 30, 2013, each of which are incorporated herein by reference in their entireties.

US Referenced Citations (397)
Number Name Date Kind
5754939 Herz et al. May 1998 A
5999932 Paul Dec 1999 A
6038295 Mattes Mar 2000 A
6154764 Nitta et al. Nov 2000 A
6158044 Tibbetts Dec 2000 A
6167435 Druckenmiller et al. Dec 2000 A
6204840 Petelycky et al. Mar 2001 B1
6205432 Gabbard et al. Mar 2001 B1
6216141 Straub et al. Apr 2001 B1
6310694 Okimoto et al. Oct 2001 B1
6442590 Inala et al. Aug 2002 B1
6484196 Maurille Nov 2002 B1
6487586 Ogilvie et al. Nov 2002 B2
6665531 Soderbacka et al. Dec 2003 B1
6701347 Ogilvie Mar 2004 B1
6711608 Ogilvie Mar 2004 B1
6724403 Santoro et al. Apr 2004 B1
6757713 Ogilvie et al. Jun 2004 B1
6898626 Ohashi May 2005 B2
6980909 Root et al. Dec 2005 B2
7004394 Kim Feb 2006 B2
7124164 Chemtob Oct 2006 B1
7149893 Leonard et al. Dec 2006 B1
7162512 Amit et al. Jan 2007 B1
7173651 Knowles Feb 2007 B1
7203380 Chiu et al. Apr 2007 B2
7243163 Friend et al. Jul 2007 B1
7278168 Chaudhury et al. Oct 2007 B1
7356564 Hartselle et al. Apr 2008 B2
7376715 Cunningham et al. May 2008 B2
7411493 Smith Aug 2008 B2
7478402 Christensen et al. Jan 2009 B2
7496347 Puranik Feb 2009 B2
7519670 Hagale et al. Apr 2009 B2
7535890 Rojas May 2009 B2
7607096 Oreizy et al. Oct 2009 B2
7703140 Nath et al. Apr 2010 B2
7856449 Martino et al. Dec 2010 B1
7912896 Wolovitz et al. Mar 2011 B2
7971156 Albertson et al. Jun 2011 B2
7996793 Latta et al. Aug 2011 B2
8001204 Burtner et al. Aug 2011 B2
8098904 Ioffe et al. Jan 2012 B2
8112716 Kobayashi Feb 2012 B2
8131597 Hudetz Mar 2012 B2
8170957 Richard May 2012 B2
8199747 Rojas et al. Jun 2012 B2
8214443 Hamburg Jul 2012 B2
8238947 Lottin et al. Aug 2012 B2
8244593 Klinger et al. Aug 2012 B2
8276092 Narayanan et al. Sep 2012 B1
8279319 Date Oct 2012 B2
8312086 Velusamy et al. Nov 2012 B2
8312097 Siegel et al. Nov 2012 B1
8332475 Rosen et al. Dec 2012 B2
8379130 Forutanpour et al. Feb 2013 B2
8405773 Hayashi et al. Mar 2013 B2
8418067 Cheng et al. Apr 2013 B2
8428453 Spiegel et al. Apr 2013 B1
8471914 Sakiyama et al. Jun 2013 B2
8487938 Latta et al. Jul 2013 B2
8560612 Kilmer et al. Oct 2013 B2
8570907 Garcia, Jr. et al. Oct 2013 B2
8687021 Bathiche et al. Apr 2014 B2
8718333 Wolf et al. May 2014 B2
8724622 Rojas May 2014 B2
8744523 Fan et al. Jun 2014 B2
8745132 Obradovich Jun 2014 B2
8775407 Huang Jul 2014 B1
8775972 Spiegel Jul 2014 B2
8788680 Naik Jul 2014 B1
8797415 Arnold Aug 2014 B2
8856349 Jain et al. Oct 2014 B2
8856691 Geisner et al. Oct 2014 B2
8874677 Rosen et al. Oct 2014 B2
8909679 Root et al. Dec 2014 B2
8909714 Agarwal et al. Dec 2014 B2
8909725 Sehn Dec 2014 B1
8914752 Spiegel Dec 2014 B1
8995433 Rojas Mar 2015 B2
9026943 Spiegel May 2015 B1
9037577 Saylor et al. May 2015 B1
9040574 Wang et al. May 2015 B2
9055416 Rosen et al. Jun 2015 B2
9083770 Drose et al. Jul 2015 B1
9094137 Sehn et al. Jul 2015 B1
9098832 Scardino Aug 2015 B1
9100806 Rosen et al. Aug 2015 B2
9100807 Rosen et al. Aug 2015 B2
9113301 Spiegel et al. Aug 2015 B1
9148424 Yang Sep 2015 B1
9191776 Root et al. Nov 2015 B2
9204252 Root Dec 2015 B2
9225805 Kujawa et al. Dec 2015 B2
9225897 Sehn et al. Dec 2015 B1
9230160 Kanter Jan 2016 B1
9237202 Sehn Jan 2016 B1
9264463 Rubinstein et al. Feb 2016 B2
9276886 Samaranayake Mar 2016 B1
9294425 Son Mar 2016 B1
9385983 Sehn Jul 2016 B1
9396354 Murphy et al. Jul 2016 B1
9407712 Sehn Aug 2016 B1
9407816 Sehn Aug 2016 B1
9430783 Sehn Aug 2016 B1
9443227 Evans et al. Sep 2016 B2
9482882 Hanover et al. Nov 2016 B1
9482883 Meisenholder Nov 2016 B1
9489661 Evans et al. Nov 2016 B2
9491134 Rosen et al. Nov 2016 B2
9532171 Allen et al. Dec 2016 B2
9537811 Allen et al. Jan 2017 B2
9560006 Prado et al. Jan 2017 B2
9628950 Noeth et al. Apr 2017 B1
9652896 Jurgenson et al. May 2017 B1
9659244 Anderton et al. May 2017 B2
9693191 Sehn Jun 2017 B2
9705831 Spiegel Jul 2017 B2
9742713 Spiegel et al. Aug 2017 B2
9785796 Murphy et al. Oct 2017 B1
9825898 Sehn Nov 2017 B2
9854219 Sehn Dec 2017 B2
9961520 Brooks et al. May 2018 B2
10102423 Shaburov et al. Oct 2018 B2
10284508 Allen et al. May 2019 B1
10439972 Spiegel et al. Oct 2019 B1
10509466 Miller et al. Dec 2019 B1
10514876 Sehn Dec 2019 B2
10579869 Xiong et al. Mar 2020 B1
10587552 Spiegel Mar 2020 B1
10614855 Huang Apr 2020 B2
10616162 Zhao Apr 2020 B1
10748347 Li et al. Aug 2020 B1
10958608 Allen et al. Mar 2021 B1
10962809 Castañeda Mar 2021 B1
10996846 Robertson et al. May 2021 B2
10997787 Ge et al. May 2021 B2
11012390 Al Majid et al. May 2021 B1
11030454 Xiong et al. Jun 2021 B1
11036368 Al Majid et al. Jun 2021 B1
11062498 Voss et al. Jul 2021 B1
11087728 Canberk et al. Aug 2021 B1
11092998 Castañeda et al. Aug 2021 B1
11106342 Al Majid et al. Aug 2021 B1
11115361 Spiegel Sep 2021 B2
11115363 Pina Ros et al. Sep 2021 B1
11126206 Meisenholder et al. Sep 2021 B2
11134046 Spiegel et al. Sep 2021 B2
11143867 Rodriguez, II Oct 2021 B2
11169600 Canberk et al. Nov 2021 B1
11227626 Krishnan Gorumkonda et al. Jan 2022 B1
11307747 Dancie et al. Apr 2022 B2
11509618 Spiegel et al. Nov 2022 B2
11531402 Stolzenberg Dec 2022 B1
11546505 Canberk Jan 2023 B2
20020026487 Ogilvie et al. Feb 2002 A1
20020047868 Miyazawa Apr 2002 A1
20020087884 Shacham et al. Jul 2002 A1
20020122659 Mcgrath et al. Sep 2002 A1
20020144154 Tomkow Oct 2002 A1
20030016247 Lai et al. Jan 2003 A1
20030052925 Daimon et al. Mar 2003 A1
20030126215 Udell Jul 2003 A1
20030164856 Prager et al. Sep 2003 A1
20030217106 Adar et al. Nov 2003 A1
20040027371 Jaeger Feb 2004 A1
20040111467 Willis Jun 2004 A1
20040203959 Coombes Oct 2004 A1
20040243531 Dean Dec 2004 A1
20050078804 Yomoda Apr 2005 A1
20050097176 Schatz et al. May 2005 A1
20050104976 Currans May 2005 A1
20050114783 Szeto May 2005 A1
20050122405 Voss et al. Jun 2005 A1
20050193340 Amburgey et al. Sep 2005 A1
20050193345 Klassen et al. Sep 2005 A1
20050198128 Anderson Sep 2005 A1
20050223066 Buchheit et al. Oct 2005 A1
20060114338 Rothschild Jun 2006 A1
20060242239 Morishima et al. Oct 2006 A1
20060270419 Crowley et al. Nov 2006 A1
20070038715 Collins et al. Feb 2007 A1
20070040931 Nishizawa Feb 2007 A1
20070064899 Boss et al. Mar 2007 A1
20070073823 Cohen et al. Mar 2007 A1
20070082707 Flynt et al. Apr 2007 A1
20070192128 Celestini Aug 2007 A1
20070214216 Carrer et al. Sep 2007 A1
20070233801 Eren et al. Oct 2007 A1
20070243887 Bandhole et al. Oct 2007 A1
20070255456 Funayama Nov 2007 A1
20080025701 Ikeda Jan 2008 A1
20080033930 Warren Feb 2008 A1
20080055269 Lemay et al. Mar 2008 A1
20080104503 Beall et al. May 2008 A1
20080120409 Sun et al. May 2008 A1
20080207176 Brackbill et al. Aug 2008 A1
20080222545 Lemay Sep 2008 A1
20080256446 Yamamoto Oct 2008 A1
20080266421 Takahata et al. Oct 2008 A1
20080270938 Carlson Oct 2008 A1
20080306826 Kramer et al. Dec 2008 A1
20080313346 Kujawa et al. Dec 2008 A1
20090006565 Velusamy et al. Jan 2009 A1
20090012788 Gilbert et al. Jan 2009 A1
20090015703 Kim et al. Jan 2009 A1
20090024956 Kobayashi Jan 2009 A1
20090040324 Nonaka Feb 2009 A1
20090042588 Lottin et al. Feb 2009 A1
20090058822 Chaudhri Mar 2009 A1
20090079846 Chou Mar 2009 A1
20090132453 Hangartner et al. May 2009 A1
20090132665 Thomsen et al. May 2009 A1
20090160970 Fredlund et al. Jun 2009 A1
20090183082 Osullivan et al. Jul 2009 A1
20090265647 Martin et al. Oct 2009 A1
20100082427 Burgener et al. Apr 2010 A1
20100082693 Hugg et al. Apr 2010 A1
20100131880 Lee et al. May 2010 A1
20100131895 Wohlert May 2010 A1
20100156933 Jones et al. Jun 2010 A1
20100159944 Pascal et al. Jun 2010 A1
20100161831 Haas et al. Jun 2010 A1
20100185665 Horn et al. Jul 2010 A1
20100214436 Kim et al. Aug 2010 A1
20100223128 Dukellis et al. Sep 2010 A1
20100223343 Bosan et al. Sep 2010 A1
20100257196 Waters et al. Oct 2010 A1
20100281045 Dean Nov 2010 A1
20100306669 Della Pasqua Dec 2010 A1
20110004071 Faiola et al. Jan 2011 A1
20110040783 Uemichi et al. Feb 2011 A1
20110040804 Peirce et al. Feb 2011 A1
20110050909 Ellenby et al. Mar 2011 A1
20110050915 Wang et al. Mar 2011 A1
20110099507 Nesladek et al. Apr 2011 A1
20110102605 Hannaford May 2011 A1
20110102630 Rukes May 2011 A1
20110126126 Blair May 2011 A1
20110141025 Tsai Jun 2011 A1
20110145564 Moshir et al. Jun 2011 A1
20110184980 Jeong et al. Jul 2011 A1
20110197194 D'Angelo et al. Aug 2011 A1
20110202598 Evans et al. Aug 2011 A1
20110202968 Nurmi Aug 2011 A1
20110211534 Schmidt et al. Sep 2011 A1
20110213845 Logan et al. Sep 2011 A1
20110273575 Lee Nov 2011 A1
20110283188 Farrenkopf Nov 2011 A1
20110286586 Saylor et al. Nov 2011 A1
20110301934 Tardif Dec 2011 A1
20110320373 Lee et al. Dec 2011 A1
20120028659 Whitney et al. Feb 2012 A1
20120062805 Candelore Mar 2012 A1
20120108293 Law et al. May 2012 A1
20120110096 Smarr et al. May 2012 A1
20120113143 Adhikari et al. May 2012 A1
20120113272 Hata May 2012 A1
20120131507 Sparandara et al. May 2012 A1
20120131512 Takeuchi et al. May 2012 A1
20120143760 Abulafia et al. Jun 2012 A1
20120150978 Monaco Jun 2012 A1
20120163664 Zhu Jun 2012 A1
20120166971 Sachson et al. Jun 2012 A1
20120169855 Oh Jul 2012 A1
20120173991 Roberts et al. Jul 2012 A1
20120176401 Hayward et al. Jul 2012 A1
20120184248 Speede Jul 2012 A1
20120200743 Blanchflower et al. Aug 2012 A1
20120209921 Adafin et al. Aug 2012 A1
20120209924 Evans et al. Aug 2012 A1
20120210244 De Francisco et al. Aug 2012 A1
20120212632 Mate et al. Aug 2012 A1
20120220264 Kawabata Aug 2012 A1
20120233000 Fisher et al. Sep 2012 A1
20120236162 Imamura Sep 2012 A1
20120239761 Linner et al. Sep 2012 A1
20120250951 Chen Oct 2012 A1
20120254325 Majeti et al. Oct 2012 A1
20120278387 Garcia et al. Nov 2012 A1
20120278692 Shi Nov 2012 A1
20120281129 Wang et al. Nov 2012 A1
20120299954 Wada et al. Nov 2012 A1
20120304080 Wormald et al. Nov 2012 A1
20120307096 Ford et al. Dec 2012 A1
20120307112 Kunishige et al. Dec 2012 A1
20120323933 He et al. Dec 2012 A1
20130050260 Reitan Feb 2013 A1
20130057587 Leonard et al. Mar 2013 A1
20130059607 Herz et al. Mar 2013 A1
20130060690 Oskolkov et al. Mar 2013 A1
20130063369 Malhotra et al. Mar 2013 A1
20130067027 Song et al. Mar 2013 A1
20130071093 Hanks et al. Mar 2013 A1
20130085790 Palmer et al. Apr 2013 A1
20130128059 Kristensson May 2013 A1
20130145286 Feng et al. Jun 2013 A1
20130169822 Zhu et al. Jul 2013 A1
20130173729 Starenky et al. Jul 2013 A1
20130182133 Tanabe Jul 2013 A1
20130185131 Sinha et al. Jul 2013 A1
20130194301 Robbins et al. Aug 2013 A1
20130198176 Kim Aug 2013 A1
20130222323 Mckenzie Aug 2013 A1
20130227476 Frey Aug 2013 A1
20130232194 Knapp et al. Sep 2013 A1
20130263031 Oshiro et al. Oct 2013 A1
20130265450 Barnes, Jr. Oct 2013 A1
20130290443 Collins et al. Oct 2013 A1
20130344896 Kirmse et al. Dec 2013 A1
20130346877 Borovoy et al. Dec 2013 A1
20140011538 Mulcahy et al. Jan 2014 A1
20140032682 Prado et al. Jan 2014 A1
20140047045 Baldwin et al. Feb 2014 A1
20140047335 Lewis et al. Feb 2014 A1
20140049652 Moon et al. Feb 2014 A1
20140052485 Shidfar Feb 2014 A1
20140052633 Gandhi Feb 2014 A1
20140057660 Wager Feb 2014 A1
20140085334 Payne Mar 2014 A1
20140089314 Iizuka et al. Mar 2014 A1
20140100997 Mayerle et al. Apr 2014 A1
20140122658 Haeger et al. May 2014 A1
20140122787 Shalvi et al. May 2014 A1
20140129953 Spiegel May 2014 A1
20140143143 Fasoli et al. May 2014 A1
20140149519 Redfern et al. May 2014 A1
20140155102 Cooper et al. Jun 2014 A1
20140171036 Simmons Jun 2014 A1
20140173457 Wang et al. Jun 2014 A1
20140189592 Benchenaa et al. Jul 2014 A1
20140201527 Krivorot Jul 2014 A1
20140207679 Cho Jul 2014 A1
20140214471 Schreiner, III Jul 2014 A1
20140279436 Dorsey et al. Sep 2014 A1
20140280537 Pridmore et al. Sep 2014 A1
20140282096 Rubinstein et al. Sep 2014 A1
20140298210 Park et al. Oct 2014 A1
20140317302 Naik Oct 2014 A1
20140325383 Brown et al. Oct 2014 A1
20140359024 Spiegel Dec 2014 A1
20140359032 Spiegel et al. Dec 2014 A1
20150046278 Pei et al. Feb 2015 A1
20150094106 Grossman et al. Apr 2015 A1
20150116529 Wu et al. Apr 2015 A1
20150120293 Wohlert et al. Apr 2015 A1
20150172534 Miyakawa et al. Jun 2015 A1
20150199082 Scholler et al. Jul 2015 A1
20150222814 Li et al. Aug 2015 A1
20150227602 Ramu et al. Aug 2015 A1
20150350251 Brander et al. Dec 2015 A1
20150370320 Connor Dec 2015 A1
20160006927 Sehn Jan 2016 A1
20160085773 Chang et al. Mar 2016 A1
20160085863 Allen et al. Mar 2016 A1
20160086670 Gross et al. Mar 2016 A1
20160099901 Allen et al. Apr 2016 A1
20160180887 Sehn Jun 2016 A1
20160277419 Allen et al. Sep 2016 A1
20160321708 Sehn Nov 2016 A1
20160359957 Laliberte Dec 2016 A1
20160359987 Laliberte Dec 2016 A1
20170123487 Hazra et al. May 2017 A1
20170161382 Ouimet et al. Jun 2017 A1
20170171131 Steiner et al. Jun 2017 A1
20170263029 Yan et al. Sep 2017 A1
20170277684 Dharmarajan Mary Sep 2017 A1
20170277685 Takumi Sep 2017 A1
20170287006 Azmoodeh et al. Oct 2017 A1
20170295250 Samaranayake et al. Oct 2017 A1
20170351910 Elwazer et al. Dec 2017 A1
20170374003 Allen et al. Dec 2017 A1
20170374508 Davis et al. Dec 2017 A1
20180158370 Pryor Jun 2018 A1
20180351903 Allen et al. Dec 2018 A1
20190386943 Spiegel et al. Dec 2019 A1
20200252360 Spiegel Aug 2020 A1
20200403951 Kapoor et al. Dec 2020 A1
20210011612 Dancie et al. Jan 2021 A1
20210074016 Li et al. Mar 2021 A1
20210166732 Shaburova et al. Jun 2021 A1
20210174034 Retek et al. Jun 2021 A1
20210241529 Cowburn et al. Aug 2021 A1
20210303075 Cowburn et al. Sep 2021 A1
20210303077 Anvaripour et al. Sep 2021 A1
20210303140 Mourkogiannis Sep 2021 A1
20210377199 Spiegel et al. Dec 2021 A1
20210382564 Blachly et al. Dec 2021 A1
20210397000 Rodriguez, II Dec 2021 A1
20210405761 Canberk Dec 2021 A1
20220188539 Chan et al. Jun 2022 A1
20220206588 Canberk et al. Jun 2022 A1
20220300730 Eirinberg et al. Sep 2022 A1
20220300731 Eirinberg et al. Sep 2022 A1
20220326781 Hwang et al. Oct 2022 A1
20220334649 Hwang et al. Oct 2022 A1
20230039505 Spiegel et al. Feb 2023 A1
Foreign Referenced Citations (42)
Number Date Country
2912651 Dec 2014 CA
2887596 Jul 2015 CA
103049761 Aug 2016 CN
2418606 Feb 2012 EP
2482537 Aug 2012 EP
3005652 Nov 2018 EP
3707693 Sep 2020 EP
3454509 Dec 2022 EP
20120003323 Jan 2012 KR
102030226 Oct 2019 KR
102193489 Dec 2020 KR
102238205 Apr 2021 KR
102355839 Feb 2022 KR
102450303 Sep 2022 KR
20220158824 Dec 2022 KR
WO-2012000107 Jan 2012 WO
WO-2013008238 Jan 2013 WO
WO-2013008251 Jan 2013 WO
WO-2013010187 Jan 2013 WO
WO-2014194262 Dec 2014 WO
WO-2015192026 Dec 2015 WO
WO-2016007285 Jan 2016 WO
WO-2016054562 Apr 2016 WO
WO-2016065131 Apr 2016 WO
WO-2016112299 Jul 2016 WO
WO-2016168591 Oct 2016 WO
WO-2016179166 Nov 2016 WO
WO-2016179235 Nov 2016 WO
WO-2017176739 Oct 2017 WO
WO-2017176992 Oct 2017 WO
WO-2018005644 Jan 2018 WO
WO-2019094618 May 2019 WO
WO-2022005687 Jan 2022 WO
WO-2022005693 Jan 2022 WO
WO-2022060549 Mar 2022 WO
WO-2022066578 Mar 2022 WO
WO-2022132381 Jun 2022 WO
WO-2022146678 Jul 2022 WO
WO-2022198182 Sep 2022 WO
WO-2022216784 Oct 2022 WO
WO-2022225761 Oct 2022 WO
WO-2022245765 Nov 2022 WO
Non-Patent Literature Citations (132)
Entry
“Android Getting Started Guide”, Voxer Business, [Online] Retrieved from the Internet: <URL: https://voxer.com/assets/AndroidGuide.pdf>, (Feb. 1, 2014), 18 pgs.
“U.S. Appl. No. 13/906,261, Advisory Action mailed Nov. 21, 2014”, 3 pgs.
“U.S. Appl. No. 13/906,261, Advisory Action mailed Dec. 14, 2015”, 3 pgs.
“U.S. Appl. No. 13/906,261, Examiner Interview Summary mailed Jan. 23, 2017”, 3 pgs.
“U.S. Appl. No. 13/906,261, Examiner Interview Summary mailed Jan. 31, 2017”, 2 pgs.
“U.S. Appl. No. 13/906,261, Examiner Interview Summary mailed Feb. 7, 2014”, 3 pgs.
“U.S. Appl. No. 13/906,261, Examiner Interview Summary mailed Feb. 14, 2014”, 3 pgs.
“U.S. Appl. No. 13/906,261, Examiner Interview Summary mailed Feb. 23, 2015”, 4 pgs.
“U.S. Appl. No. 13/906,261, Examiner Interview Summary mailed Aug. 2, 2016”, 3 pgs.
“U.S. Appl. No. 13/906,261, Final Office Action mailed Jan. 28, 2014”, 20 pgs.
“U.S. Appl. No. 13/906,261, Final Office Action mailed Feb. 15, 2017”, 6 pgs.
“U.S. Appl. No. 13/906,261, Final Office Action mailed Sep. 16, 2014”, 19 pgs.
“U.S. Appl. No. 13/906,261, Final Office Action mailed Sep. 22, 2016”, 20 pgs.
“U.S. Appl. No. 13/906,261, Final Office Action mailed Nov. 19, 2015”, 31 pgs.
“U.S. Appl. No. 13/906,261, Non Final Office Action mailed Mar. 6, 2014”, 17 pgs.
“U.S. Appl. No. 13/906,261, Non Final Office Action mailed Jul. 24, 2015”, 20 pgs.
“U.S. Appl. No. 13/906,261, Non Final Office Action mailed Jul. 25, 2016”, 19 pgs.
“U.S. Appl. No. 13/906,261, Non Final Office Action mailed Sep. 23, 2013”, 17 pgs.
“U.S. Appl. No. 13/906,261, Non Final Office Action mailed Dec. 30, 2016”, 6 pgs.
“U.S. Appl. No. 13/906,261, Notice of Allowance mailed Mar. 7, 2017”, 7 pgs.
“U.S. Appl. No. 13/906,261, Response filed Jan. 31, 2017 to Non Final Office Action mailed Dec. 30, 2016”, 5 pgs.
“U.S. Appl. No. 13/906,261, Response filed Feb. 10, 2014 to Final Office Action mailed Jan. 28, 2014”, 5 pgs.
“U.S. Appl. No. 13/906,261, Response filed Feb. 13, 2015 to Advisory Action mailed Nov. 21, 2014”, 7 pgs.
“U.S. Appl. No. 13/906,261, Response filed Feb. 28, 2017 to Final Office Action mailed Feb. 15, 2017”, 4 pgs.
“U.S. Appl. No. 13/906,261, Response filed Jun. 6, 2014 to Non Final Office Action mailed Mar. 6, 2014”, 9 pgs.
“U.S. Appl. No. 13/906,261, Response filed Aug. 13, 2015 to Non Final Office Action mailed Jul. 24, 2015”, 9 pgs.
“U.S. Appl. No. 13/906,261, Response filed Aug. 26, 2016 to Non Final Office Action mailed Jul. 25, 2016”, 7 pgs.
“U.S. Appl. No. 13/906,261, Response filed Oct. 21, 2016 to Final Office Action mailed Sep. 22, 2016”, 4 pgs.
“U.S. Appl. No. 13/906,261, Response filed Nov. 5, 2013 to Non Final Office Action mailed Sep. 23, 2013”, 8 pgs.
“U.S. Appl. No. 13/906,261, Response filed Nov. 7, 2014 to Final Office Action mailed Sep. 16, 2014”, 10 pgs.
“U.S. Appl. No. 13/906,261, Response filed Nov. 23, 2015 to Final Office Action mailed Nov. 19, 2015”, 6 pgs.
“U.S. Appl. No. 13/906,261, Response filed Dec. 18, 2015 to Advisory Action mailed Dec. 14, 2015”, 5 pgs.
“U.S. Appl. No. 13/906,261, Supplemental Notice of Allowability mailed Jun. 14, 2017”, 2 pgs.
“U.S. Appl. No. 14/274,610, Advisory Action mailed Feb. 27, 2015”, 3 pgs.
“U.S. Appl. No. 14/274,610, Examiner Interview Summary mailed Feb. 23, 2015”, 3 pgs.
“U.S. Appl. No. 14/274,610, Final Office Action mailed Feb. 5, 2015”, 14 pgs.
“U.S. Appl. No. 14/274,610, Final Office Action mailed Feb. 18, 2016”, 13 pgs.
“U.S. Appl. No. 14/274,610, Final Office Action mailed Sep. 22, 2016”, 20 pgs.
“U.S. Appl. No. 14/274,610, Non Final Office Action mailed Feb. 17, 2017”, 18 pgs.
“U.S. Appl. No. 14/274,610, Non Final Office Action mailed Jul. 24, 2015”, 15 pgs.
“U.S. Appl. No. 14/274,610, Non Final Office Action mailed Jul. 26, 2016”, 10 pgs.
“U.S. Appl. No. 14/274,610, Non Final Office Action mailed Sep. 17, 2014”, 11 pgs.
“U.S. Appl. No. 14/274,610, Notice of Allowance mailed Apr. 18, 2017”, 8 pgs.
“U.S. Appl. No. 14/274,610, Notice of Allowance mailed Jul. 20, 2017”, 2 pgs.
“U.S. Appl. No. 14/274,610, Preliminary Amendment filed May 20, 2014”, 3 pgs.
“U.S. Appl. No. 14/274,610, Response filed Feb. 13, 2015 to Final Office Action mailed Feb. 5, 2015”, 4 pgs.
“U.S. Appl. No. 14/274,610, Response filed Feb. 28, 2016 to Non Final Office Action mailed Feb. 17, 2017”, 6 pgs.
“U.S. Appl. No. 14/274,610, Response filed Mar. 1, 2016 to Final Office Action mailed Feb. 18, 2016”, 7 pgs.
“U.S. Appl. No. 14/274,610, Response filed Mar. 11, 2015 to Advisory Action mailed Feb. 27, 2015”, 8 pgs.
“U.S. Appl. No. 14/274,610, Response filed Aug. 26, 2016 to Non Final Office Action mailed Jul. 26, 2016”, 5 pgs.
“U.S. Appl. No. 14/274,610, Response filed Oct. 21, 2016 to Final Office Action mailed Sep. 22, 2016”, 9 pgs.
“U.S. Appl. No. 14/274,610, Response filed Nov. 7, 2014 to Non Final Office Action mailed Sep. 17, 2014”, 5 pgs.
“U.S. Appl. No. 14/274,610, Response filed Nov. 23, 2015 to Non Final Office Action mailed Jul. 24, 2015”, 4 pgs.
“U.S. Appl. No. 15/646,014, Final Office Action mailed Jun. 26, 2019”, 7 pgs.
“U.S. Appl. No. 15/646,014, Non Final Office Action mailed Oct. 1, 2018”, 12 pgs.
“U.S. Appl. No. 15/646,014, Notice of Allowance mailed Oct. 28, 2019”, 5 pgs.
“U.S. Appl. No. 15/646,014, Response filed Apr. 1, 2019 to Non Final Office Action mailed Oct. 1, 2018”, 7 pgs.
“U.S. Appl. No. 15/646,014, Response filed Sep. 26, 2019 to Final Office Action mailed Jun. 26, 2019”, 7 pgs.
“U.S. Appl. No. 15/682,404, Examiner Interview Summary mailed Jan. 23, 2019”, 9 pgs.
“U.S. Appl. No. 15/682,404, Non Final Office Action mailed Oct. 1, 2018”, 13 pgs.
“U.S. Appl. No. 15/682,404, Notice of Allowance mailed Jun. 27, 2019”, 7 pgs.
“U.S. Appl. No. 15/682,404, Notice of Non-Compliant Amendment mailed Feb. 19, 2019”, 2 pgs.
“U.S. Appl. No. 15/682,404, Notice of Non-Compliant Amendment mailed Nov. 6, 2017”, 2 pgs.
“U.S. Appl. No. 15/682,404, Preliminary Amendment filed Aug. 21, 2017”, 5 pgs.
“U.S. Appl. No. 15/682,404, Response filed Nov. 16, 2017 to Notice of Non-Compliant Amendment mailed Nov. 6, 2017”, 5 pgs.
“U.S. Appl. No. 15/682,404, Response filed Apr. 3, 2019 to Notice of Non-Compliant Amendment mailed Feb. 29, 2019”, 7 pgs.
“U.S. Appl. No. 15/682,404, Respponse filed Jan. 21, 2019 to Non Final Office Action mailed Oct. 1, 2018”, 12 pgs.
“U.S. Appl. No. 16/552,018, Non Final Office Action mailed Feb. 1, 2021”, 32 pgs.
“U.S. Appl. No. 16/552,018, Notice of Allowance mailed May 7, 2021”, 8 pgs.
“U.S. Appl. No. 16/552,018, Response filed Mar. 30, 2021 to Non Final Office Action mailed Feb. 1, 2021”, 10 pgs.
“U.S. Appl. No. 16/552,018, Supplemental Notice of Allowability mailed Aug. 27, 2021”, 2 pgs.
“U.S. Appl. No. 16/781,727, Examiner Interview Summary mailed Mar. 17, 2021”, 2 pgs.
“U.S. Appl. No. 16/781,727, Non Final Office Action mailed Feb. 3, 2021”, 32 pgs.
“U.S. Appl. No. 16/781,727, Notice of Allowance mailed May 7, 2021”, 7 pgs.
“U.S. Appl. No. 16/781,727, Preliminary Amendment filed Apr. 30, 2020”, 6 pgs.
“U.S. Appl. No. 16/781,727, Response filed Apr. 12, 2021 to Non Final Office Action mailed Feb. 3, 2021”, 9 pgs.
“U.S. Appl. No. 17/402,316, Final Office Action mailed May 13, 2022”, 22 pgs.
“U.S. Appl. No. 17/402,316, Non Final Office Action mailed Jan. 6, 2022”, 27 pgs.
“U.S. Appl. No. 17/402,316, Notice of Allowance mailed Jul. 21, 2022”, 8 pgs.
“U.S. Appl. No. 17/402,316, Response filed Mar. 8, 2022 to Non Final Office Action mailed Jan. 6, 2022”, 10 pgs.
“U.S. Appl. No. 17/402,316, Response filed Jun. 30, 2022 to Final Office Action mailed May 13, 2022”, 9 pgs.
“U.S. Appl. No. 17/970,003, Corrected Notice of Allowability mailed Mar. 6, 2024”, 3 pgs.
“U.S. Appl. No. 17/970,003, Non Final Office Action mailed Oct. 12, 2023”, 27 pgs.
“U.S. Appl. No. 17/970,003, Notice of Allowance mailed Feb. 27, 2024”, 7 pgs.
“U.S. Appl. No. 17/970,003, Response filed Dec. 18, 2023 to Non Final Office Action mailed Oct. 12, 2023”, 8 pgs.
“Canadian Application Serial No. 2,912,651, Examiners Rule 86(2) Report mailed Sep. 11, 2023”, 4 pgs.
“Canadian Application Serial No. 2,912,651, Examiners Rule 86(2) Report mailed Dec. 1, 2022”, 4 pgs.
“Canadian Application Serial No. 2,912,651, Office Action mailed Oct. 29, 2021”, 3 pgs.
“Canadian Application Serial No. 2,912,651, Response filed Jan. 8, 2024 to Examiners Rule 86(2) Report mailed Sep. 11, 2023”, 7 pgs.
“European Application Serial No. 14804343.3, Communication Pursuant to Article 94(3) EPC mailed Nov. 24, 2017”, 7 pgs.
“European Application Serial No. 14804343.3, Extended European Search Report mailed Sep. 29, 2016”, 12 pgs.
“European Application Serial No. 14804343.3, Response filed Jan. 16, 2018 to Communication Pursuant to Article 94(3) EPC mailed Nov. 24, 2017”, w/ Amended Claims, 20 pgs.
“European Application Serial No. 14804343.3, Response filed Feb. 10, 2016 to Communication pursuant to Rules 161(2) and 162 EPC mailed Jan. 19, 2016”, 4 pgs.
“European Application Serial No. 14804343.3, Response filed Apr. 24, 2017 to Extended European Search Report mailed Sep. 29, 2016”, 3 pgs.
“European Application Serial No. 15819676.6, Extended European Search Report mailed Oct. 12, 2017”, 9 pgs.
“European Application Serial No. 18202667.4, Communication Pursuant to Article 94(3) EPC mailed Mar. 31, 2021”, 11 pgs.
“European Application Serial No. 18202667.4, Communication Pursuant to Article 94(3) EPC mailed May 18, 2020”, 12 pgs.
“European Application Serial No. 18202667.4, Communication Pursuant to Article 94(3) EPC mailed Aug. 30, 2019”, 10 pgs.
“European Application Serial No. 18202667.4, Extended European Search Report mailed Feb. 11, 2019”, 11 pgs.
“European Application Serial No. 18202667.4, Response filed Sep. 24, 2020 to Communication Pursuant to Article 94(3) EPC mailed May 18, 2020”, 10 pgs.
“European Application Serial No. 18202667.4, Response filed Dec. 16, 2019 to Communication Pursuant to Article 94(3) EPC mailed Aug. 30, 2019”, 17 pgs.
“European Application Serial No. 18202667.4, Response filed May 26, 2021 to Communication Pursuant to Article 94(3) EPC mailed Mar. 31, 2021”, 8 pgs.
“European Application Serial No. 22209781.8, Extended European Search Report mailed Apr. 26, 2023”, 17 pgs.
“How Snaps Are Stored And Deleted”, Snapchat, [Online] Retrieved from the Internet: <URL: https://www.snap.com/en-US/news/post/how-snaps-are-stored-and-deleted/>, (May 9, 2013), 2 pgs.
“International Application Serial No. PCT/US2014/040346, International Preliminary Report on Patentability mailed Dec. 10, 2015”, 8 pgs.
“International Application Serial No. PCT/US2014/040346, International Search Report mailed Mar. 23, 2015”, 2 pgs.
“International Application Serial No. PCT/US2014/040346, Written Opinion mailed Mar. 23, 2015”, 6 pgs.
“International Application Serial No. PCT/US2015/037251, International Search Report mailed Sep. 29, 2015”, 2 pgs.
“International Application Serial No. PCT/US2015/037251, Written Opinion mailed Sep. 29, 2015”, 4 pgs.
“IVisit Mobile: Getting Started”, iVisit, [Online] Retrieved from the Internet: <URL: http://web.archive.org/web/20140830174355/http://ivisit.com/support_mobile>, (Dec. 4, 2013), 16 pgs.
“Korean Application Serial No. 10-2015-7037022, Notice of Preliminary Rejection mailed Mar. 19, 2019”, w/ English Translation, 6 pgs.
“Korean Application Serial No. 10-2015-7037022, Response filed May 17, 2019 to Notice of Preliminary Rejection mailed Mar. 19, 2019”, w/ English Claims, 38 pgs.
“Korean Application Serial No. 10-2019-7028277, Notice of Preliminary Rejection mailed May 25, 2020”, w/ English Translation, 14 pgs.
“Korean Application Serial No. 10-2019-7028277, Response filed Jul. 15, 2020 to Notice of Preliminary Rejection mailed May 25, 2020”, w/ English Claims, 47 pgs.
“Korean Application Serial No. 10-2021-7010091, Notice of Preliminary Rejection mailed May 27, 2021”, w/ English Translation, 6 pgs.
“Korean Application Serial No. 10-2021-7010091, Response filed Jul. 1, 2021 to Notice of Preliminary Rejection mailed May 27, 2021”, w/ English Machine Translation, 47 pgs.
“Korean Application Serial No. 10-2022-7002196, Notice of Preliminary Rejection mailed Apr. 2, 2022”, w/ English Translation, 6 pgs.
Castelluccia, Claude, et al., “EphPub: Toward robust Ephemeral Publishing”, 19th IEEE International Conference on Network Protocols (ICNP), (Oct. 17, 2011), 18 pgs.
Fajman, “An Extensible Message Format for Message Disposition Notifications”, Request for Comments: 2298, National Institutes of Health, (Mar. 1998), 28 pgs.
Leyden, John, “This SMS will self-destruct in 40 seconds”, [Online] Retrieved from the Internet: <URL: http://www.theregister.co.uk/2005/12/12/stealthtext/>, (Dec. 12, 2005), 1 pg.
Melanson, Mike, “This text message will self destruct in 60 seconds”, [Online] Retrieved from the Internet: <URL: http://readwrite.com/2011/02/11/this_text_message_will_self_destruct_in_60_seconds>, (Feb. 18, 2015), 4 pgs.
Sawers, Paul, “Snapchat for IOS Lets You Send Photos to Friends and Set How long They're Visible For”, [Online] Retrieved from the Internet: <URL: https://thenextweb.com/news/snapchat-for-ios-lets-you-send-photos-to-friends-and-set-how-long-theyre-visible-for>, (May 7, 2012), 5 pgs.
Shein, Esther, “Ephemeral Data”, Communications of the ACM, vol. 56, No. 9, (Sep. 2013), 3 pgs.
Vaas, Lisa, “StealthText, Should You Choose to Accept It”, [Online] Retrieved from the Internet: <URL: https://www.eweek.com/enterprise-apps/stealthtext-should-you-choose-to-accept-it/>, (Dec. 13, 2005), 3 pgs.
U.S. Appl. No. 13/906,261 U.S. Pat. No. 9,705,831, filed May 30, 2013, Apparatus and Method for Maintaining a Message Thread with Opt-In Permanence for Entries.
U.S. Appl. No. 15/646,014 U.S. Pat. No. 10,587,552, filed Jul. 10, 2017, Apparatus and Method for Maintaining a Message Thread with Opt-In Permanence for Entries.
U.S. Appl. No. 16/781,727 U.S. Pat. No. 11,115,361, filed Feb. 4, 2020, Apparatus and Method for Maintaining a Message Thread with Opt-In Permanence for Entries.
U.S. Appl. No. 14/274,610 U.S. Pat. No. 9,742,713, filed May 9, 2014, Apparatus and Method for Maintaining a Message Thread with Opt-In Permanence for Entries.
U.S. Appl. No. 15/682,404 U.S. Pat. No. 10,439,972, filed Aug. 21, 2017, Apparatus and Method for Maintaining a Message Thread with Opt-In Permanence for Entries.
U.S. Appl. No. 16/552,018 U.S. Pat. No. 11,134,046, filed Aug. 27, 2019, Apparatus and Method for Maintaining a Message Thread with Opt-In Permanence for Entries.
U.S. Appl. No. 17/402,316 U.S. Pat. No. 11,509,618, filed Aug. 13, 2021, Maintaining a Message Thread with Opt-In Permanence for Entries.
U.S. Appl. No. 17/970,003, filed Oct. 20, 2022, Maintaining a Message Thread with Opt-In Permanence for Entries.
Related Publications (1)
Number Date Country
20240314098 A1 Sep 2024 US
Continuations (5)
Number Date Country
Parent 17970003 Oct 2022 US
Child 18674419 US
Parent 17402316 Aug 2021 US
Child 17970003 US
Parent 16552018 Aug 2019 US
Child 17402316 US
Parent 15682404 Aug 2017 US
Child 16552018 US
Parent 14274610 May 2014 US
Child 15682404 US
Continuation in Parts (1)
Number Date Country
Parent 13906261 May 2013 US
Child 14274610 US