US20140179358A1 - Messages augmented with structured entities - Google Patents

Messages augmented with structured entities Download PDF

Info

Publication number
US20140179358A1
US20140179358A1 US13/723,190 US201213723190A US2014179358A1 US 20140179358 A1 US20140179358 A1 US 20140179358A1 US 201213723190 A US201213723190 A US 201213723190A US 2014179358 A1 US2014179358 A1 US 2014179358A1
Authority
US
United States
Prior art keywords
message
text
server
entity
displaying
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/723,190
Other languages
English (en)
Inventor
Sadi Khan
Kazi Al-Rashid
Jeremy Bong
Arwa Tyebkhan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corp filed Critical Microsoft Corp
Priority to US13/723,190 priority Critical patent/US20140179358A1/en
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BONG, Jeremy, TYEBKHAN, Arwa, AL-RASHID, Kazi, KHAN, SADI
Priority to KR1020157018573A priority patent/KR102059231B1/ko
Priority to JP2015549763A priority patent/JP6324407B2/ja
Priority to PCT/US2013/076823 priority patent/WO2014100544A1/en
Priority to EP13819148.1A priority patent/EP2936846B1/en
Priority to CN201380066921.1A priority patent/CN105027587B/zh
Publication of US20140179358A1 publication Critical patent/US20140179358A1/en
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC reassignment MICROSOFT TECHNOLOGY LICENSING, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC reassignment MICROSOFT TECHNOLOGY LICENSING, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Priority to US15/349,159 priority patent/US10142268B2/en
Priority to US16/169,067 priority patent/US10484318B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/08—Annexed information, e.g. attachments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents
    • G06F40/106—Display of layout of documents; Previewing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/12—Use of codes for handling textual entities
    • G06F40/134—Hyperlinking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/197—Version control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • SMS Short Message Service
  • IM instant messaging
  • SMS and IM While message sent via HTTP are often more convenient, offer richer content, and are more economical to send, SMS and IM continue to have legacy influence. Many phones have Internet service and can communicate by HTTP, but nearly all phones have SMS. When one person wants to send a message to another, the user often does not know what capabilities are available on the recipient's phone, so the sender often sends an SMS message in order to be able to reach the recipient without regard to what type of device the recipient has. But the decision to use SMS subjects the message to SMS's limitations.
  • a message having rich, structured content may be created, and this message may be transmitted to devices that have a wide range of capabilities by leveraging the use of an existing text messaging system, such as SMS or IM.
  • an existing text messaging system such as SMS or IM.
  • the user identifies the phone number of the person to whom the message is to be sent.
  • the full structured message is sent to a server, where it is stored for later retrieval.
  • an SMS representation of the full message is created, and the SMS representation is sent to the recipient via SMS.
  • the SMS representation contains a link to the underlying message that is stored on the server, as well as a textual representation of the content of the message.
  • SMS message When the recipient's device receives the SMS message, software on that device may be configured to check whether the SMS message refers to richer content stored on the server. If such software is installed on the receiving device, that software may retrieve the underlying content from the server, and may render that content in a rich experience for the recipient. In such a case, the SMS message itself might not be displayed, since it is effectively just a legacy representation of the “real” content that the sending is trying to communicate. However, if the recipient's device does not have software installed that can determine whether the SMS message is a stand-in for richer content, then the SMS message may contain enough text to convey the gist of the message. Additionally, as noted above, the SMS message contains a link to the underlying content on the server, and the recipient can retrieve that link manually in order to view the richer content—e.g., by viewing that content on the mobile device's web browser.
  • Creation of richer content may be performed in a variety of ways—e.g., through menus or escape characters. For example, if the hash character (#) is used as the escape character, then including text such as “#John” while the message is being composed may create a structured entity representing “John's” contact information. Similarly, “#6:15pm” may create a calendar entry for the current date at 6:15 p.m. Representations of these entities may be stored, or pointed to, by the rich version of the message, and representations of these entities may be rendered in a variety of ways when the rich content is viewed by the recipient.
  • FIGS. 1-4 are block diagrams of views of an example message composition application.
  • FIG. 5 is a block diagram of example components that may be used in sending a message.
  • FIGS. 6 and 7 are block diagrams of devices that have received a message.
  • FIG. 8 is a flow diagram of an example process of creating a message with entity content.
  • FIG. 9 shows an example process in which a device receives a text message and uses the text message to obtain rich content.
  • FIG. 10 is a block diagram of example components that may be used in connection with implementations of the subject matter described herein.
  • SMS Short Message Service
  • SMS Short Message Service
  • the sender of a message composes a message and directs the message to the recipient's phone number.
  • the message is transmitted to the recipient's phone. SMS software on the recipient's phone notifies the recipient that a message is available and displays the message.
  • SMS Short Message Service
  • Many wireless phones function as full Internet-capable devices.
  • Such devices can receive messages in ways other than SMS.
  • a smart phone may receive e-mail, push notifications, or Internet connection requests.
  • push notifications with the ability to download arbitrary Hypertext Markup Language (HTML) content via Hypertext Transfer Protocol (HTTP)
  • HTTP Hypertext Transfer Protocol
  • SMS is a legacy technology whose use persists mainly because of its ubiquity.
  • the sender often does not know what type of phone the recipient has.
  • Nearly all cell phones can receive SMS messages, but only certain kinds of phones can receive messages in other ways.
  • Apple devices can send messages to each other through a protocol called iMessage.
  • iMessage a protocol that can send messages to each other through a protocol called iMessage.
  • many devices support SMS as part of a high-quality user experience—e.g., providing push notifications and over-the-lock-screen alerts.
  • Other messaging systems could provide a richer experience—e.g., by allowing structured entities to be incorporated into a message—but this sort of experience is difficult to incorporate into an SMS message.
  • the subject matter herein provides a way to leverage the existing SMS system to provide a richer messaging experience, both on the message authoring side and on the messaging rendering side.
  • the messaging experience may include the use of structured entities in messages.
  • the user may include certain types of information that refers to entities. For example, a message might contain the text “John,” but that text actually refers to a person who has specific contact information, specific social relationships, etc.
  • the author might use an escape character such as “#” to write “#John”.
  • An appropriate resolution mechanism may be used to disambiguate entities—e.g., in response to the text “#John” (or incrementally as the user types that text), the authoring system might provide a drop-down menu that allows a user to choose between various people named John. People are only one example of entities that could be added to a message. Other examples include dates and times (e.g., using “#615pm” to refer to 6:15 p.m. on the current day) and places (e.g., using “#bamboo-garden” to refer to a nearby restaurant named “Bamboo Garden”). Any of these “entities” may be represented in an appropriate structured form—e.g., a contact card for a person, a calendar entry for a date and time, a place page for a restaurant, or any other named entity.
  • the author of the message indicates where the message is to be sent.
  • the destination for the message may be a phone number, which may identify a particular phone to which the message is to be sent.
  • the full message—including the entity content— is then transmitted to a server, where it is stored. Transmission of the message to the server may take place by any appropriate mechanism, such as HTTP. Additionally, an SMS message that represents the underlying content of the full message is sent to the destination that the sender identified.
  • the SMS message may contain a text representation of the content that was authored, and may also contain a link to retrieve the full message on the server.
  • the software on that device may query the server to determine whether the SMS message that was received corresponds to a message containing richer content on the server. For example, the software may send the server the phone numbers of the sender and recipient, a digest of the message, and the time of receipt, and the server may use this information to determine whether it has a rich message corresponding to the SMS message. If it is determined that the SMS message corresponds to richer content, then the software obtains that content from the server and renders the content. When the software at the recipient's device is able to determine that the SMS message refers to rich content available on the server, the software may avoid showing the SMS message itself, since the SMS message is effectively just a legacy representation of the content that was obtained from the server.
  • SMS message may be shown to the recipient using the recipient's existing SMS software. That SMS message, as noted above, may contain a link to the content on the server, so that the recipient can manually follow the link and obtain the richer content, if the recipient's device is Internet-capable. (If the recipient's device has no way to download the server content, the recipient can still see the basic text of the sender's message, which is contained in the SMS representation of the message.)
  • SMS Short Message
  • IM Instant Messaging
  • FIGS. 1-4 show example interfaces of a message composition application.
  • device 102 is any type of device that has some communication and computing capability.
  • device 102 may be a smart phone, a tablet, or any other type of device.
  • device 102 is depicted as the non-limiting example of a smart phone.
  • Device 102 may have a touch screen 104 , which serves as an input and output component for device 102 .
  • Device 102 may have other components related to input and output, such as button 106 , which may be used to return to a desktop or home screen on device 102 , or to navigate content on device 102 .
  • Device 102 is capable of running software.
  • One piece of software that may run on device 102 is a message application (“Message App”, in the drawings), which presents a user interface through touch screen 104 .
  • Message App (“Message App”, in the drawings)
  • FIGS. 1-4 (Different views of the message application's interface 108 are shown in FIGS. 1-4 ).
  • the message application's interface contains a box 110 that allows a user to compose a message, a space 112 into which destination of the message may be entered, and a send button 114 that is used to indicate that the message is to be sent.
  • interface 108 is being used on device 102 to compose a message.
  • the user has started to type the message “Let's meet at #bamb . . . ”.
  • the “#” (number sign, or hash mark) character is an escape character 202 , indicating that the text that follows that character refers to an entity.
  • the software that the user is using to author the message may provide various suggestions for entities. In the example shown, these suggestions are provided in the form of a drop-down menu 204 . Drop-down menu 204 offers several choices for the entities that might match the letters that have been typed after escape character 202 . These choices include “Bamboo Garden” and “Bambastic Biz”.
  • Drop-down menu 204 may also include an image for each of the items on the menu—e.g., a fork and knife icon next to a restaurant, the silhouette of a person's head next to a person, etc. Additionally, drop-down menu includes an “ignore” option, which, if selected, allows the sequence “#bamb” to be treated as a literal text string to be included in the message, rather than being treated as the indication of an entity.
  • the choice of entities in a menu may be determined from various contextual information.
  • the choice of entities in a drop-down menu may be determined based on the history of entities that have been chosen by the user at an earlier time (a user is more likely to choose entities that the user has chosen in the past); or by the location of the user (e.g., a user is more likely to choose bamboo Garden if he is presently near bamboo Garden); or based on personalization information such as a social graph (e.g., a person is more likely to write about his or her “friends” in a text message than he or she is to write about people who are very distant from the writer in the social graph).
  • a social graph e.g., a person is more likely to write about his or her “friends” in a text message than he or she is to write about people who are very distant from the writer in the social graph.
  • History, location, and position in the social graph are thus all examples of context that may be used in resolving entities, or in determining what to include in a drop-down menu.
  • the information that is used to determine what to include in the menu, or how to resolve an entity name may come from within the device on which the message is being composed (e.g., the user's smart phone), or from an external source that the device communicates with.
  • FIG. 3 shows further composition of the message.
  • interface 108 is shown on device 102 .
  • the text string “#bamb” has been resolved to the restaurant entity “Bamboo Garden”.
  • the user types “#tonight.”
  • the software may recognize this string as referring to a time entity.
  • the software may present a dialog box 302 that allows the user to specify “tonight” more precisely—e.g., by providing a slider, or other user interface element, that allows the user to specify the time.
  • the user chooses 6:30 p.m. as the time. (As another example, the user might have typed “#this week”, in which case the dialog box might have presented a calendar to allow the user to choose a date.)
  • FIG. 4 shows yet further composition of the message.
  • interface 108 is shown on device 102 .
  • the user has indicated a person entity by writing “#Al”.
  • the software provides a drop-down menu 402 , which provides several choices of names, from which the user can choose to resolve the string “#Al” to a specific entity.
  • the message may be sent to its recipients.
  • the sender chooses a recipient (e.g., by entering a phone number, or a name from a contact list, into space 112 shown in FIG. 1 ).
  • the components involved in sending the message are shown in FIG. 5 .
  • device 102 is the sender's device
  • device 502 is the recipient's device.
  • Software 504 on sender's device 102 (which may be the same software that was used to author the content that the sender wants to send) creates two representation of the content: an SMS message 506 , and a “rich” message that represents the authored text and the entities that are referred to in that text.
  • SMS message contains text 508 and a link 510 .
  • Text 508 is the textual content that was authored by the sender.
  • Link 510 is a link to the rich message that will be stored on server 512 .
  • link 510 is shown as a “short” link (using the Uniform Resource Locator (“URL”) shortening service “bit.ly”, or any other shortening service), although link 510 could take any form.
  • SMS message 506 is sent to recipient's device 502 using the normal SMS delivery mechanisms provided by a text message network 514 (e.g., the cell phone system that is used to deliver SMS messages).
  • a text message network 514 e.g., the cell phone system that is used to deliver SMS messages.
  • Rich message 516 contains text 518 , which is the textual content of the message. Rich message 516 may also contains entities 520 . Entities 520 may be represented in any appropriate manner. For example, a place entity may be represented by its “place page” on a service such as Yelp; or, as another example, a place entity could be represented on a map with its location and the hours that it is open. A date/time entity may be represented as an iCalendar (“.ics”) file, or as a link to an item on a person's calendar. A person entity may be represented as that person's entry in a directory or a contact list.
  • iCalendar iCalendar
  • the representation may include a copy of the information about the entity (e.g., a copy of a person's entry in a directory), or may be a reference to an object that is stored and maintained elsewhere (e.g., a link to a person's listing in an online directory). Any appropriate entity representation may be used.
  • the rich message 516 may be sent to server 512 using any appropriate communication protocol, such as HTTP.
  • Message 516 may be stored in association with various pieces of identifying data. These data may include a sender ID 522 (e.g., the sender's phone number), a recipient ID 524 (e.g., the recipient's phone number), a message digest 526 (e.g., a hash of the SMS message), and a timestamp 528 (indicating the time at which the message was sent and/or received).
  • sender ID 522 e.g., the sender's phone number
  • recipient ID 524 e.g., the recipient's phone number
  • message digest 526 e.g., a hash of the SMS message
  • timestamp 528 indicating the time at which the message was sent and/or received.
  • message 516 may be transmitted to device 502 as part of processes that are described below in connection with FIG. 9 .
  • FIG. 6 shows what may happen when the SMS message is received by a device with ordinary SMS software—i.e., software that is not capable of associating the SMS message with an underlying richer message.
  • Device 602 e.g., a cell phone
  • Software on device 602 treats the SMS message 506 as being an ordinary SMS message, so it simply displays the message.
  • the message contains a link 510 , which points to the underlying message stored on server 512 (shown in FIG. 5 ). If device 602 has the capability to visit a web site (e.g., if device 602 has a web browser), then the user may retrieve link 510 in order to view the underlying content.
  • FIG. 7 shows what may happen when the SMS message is received by a device that has software that is capable of associating the SMS message with an underlying rich message.
  • device 702 may contact server 512 (shown in FIG. 5 ) to determine whether the SMS message is associated with content stored on that server.
  • software on device 702 calculates a digest (e.g., hash) of the message, and then queries the server as to whether the server has a message associated with (a) the calculated hash, (b) the sender of the SMS message, (c) the recipient of the SMS message, and (d) a timestamp that is within some range of when the SMS message was received.
  • a digest e.g., hash
  • the server may associate each message with those items of data (see items 522 - 528 in FIG. 5 ). Thus, the server can make a finding as to whether content corresponding to the SMS message exists on the server. If such content does exist, then the content is transmitted to device 702 (e.g., via HTTP, or some other non-SMS protocol). Device 702 may then display that content, including, for example, text 704 , and any entity information 706 . In the example of FIG. 7 , the entity information is shown in a separate area from said text. The example shows the entities underneath the text, although the entities could be shown above the text, next to the text, on a separate screen from the text—all of which are examples of showing the entities separate from the text. As noted above, when the SMS message is determined to correspond to content stored on server 512 (shown in FIG. 5 ), the SMS message is effectively understood as a legacy representation of that content, so device 702 may avoid actually showing the SMS message itself.
  • FIG. 8 shows an example process of creating a message with entity content.
  • a user authors a message, including entity content as shown in FIGS. 1-4 .
  • the user indicates the recipient of the message—e.g., by specifying the recipient's phone number, or by choosing the recipient from a contacts list.
  • an SMS representation of the message is created, and is sent to the recipient via SMS.
  • a rich representation of the message is created (including representations of the entities in the message), and the rich representation is sent to a server.
  • the server stores the rich representation of the message.
  • the server may associate the message with various identifying indicia—e.g., the sender's and recipient's phone number, a timestamp, and a digest of the SMS message, as mentioned above.
  • FIG. 9 shows an example process in which a device receives an SMS message and uses the SMS message to obtain rich content.
  • the SMS message is received at a device that has enhanced SMS software.
  • the SMS software in this example, is “enhanced” in the sense that the software is able to determine whether an SMS message corresponds to richer content that is stored elsewhere.
  • the software may extract the sender and recipient from the SMS message, calculates a digest of the SMS message, and notes the time of receipt.
  • the identifying indicia are sent to the server where rich messages are stored.
  • the server determines whether there is a message that corresponds to the identifying indicia. For example, if the identifying indicia comprise the sender's and recipient's phone numbers, a digest of the SMS message, and the time of receipt, then the server may examine stored messages to determine which ones have matching phone numbers and SMS message digests, and also have timestamps that are close in time to the time at which the message was received.
  • the server determines that a rich message corresponding to the SMS message exists, then the server sends a representation of the rich message to the recipient's device (at 910 ).
  • the communication of the rich message content may be performed using any communication protocol, such as HTTP.
  • the device renders the content in an appropriate format (at 912 ).
  • the client may display the text of the message, and may also render any entity content such as maps (for place entities), contact cards (for person entities), calendar pages (for date/time entities), etc.
  • FIG. 7 shows an example of rich content being displayed in an appropriate format. If the entity content contains a reference to content that is stored elsewhere, then software on the recipient's device retrieves and/or generates the appropriate content.
  • An example of retrieving content stored elsewhere is when a place entity is represented by a link to the entity's place page, in which case obtaining the content may be performed by requesting the link.
  • An example of creating content is where a place entity is associated with a map, in which case appropriate mapping software may be used to retrieve map data and/or generate the map.
  • FIG. 10 shows an example environment in which aspects of the subject matter described herein may be deployed.
  • Device 1000 includes one or more processors 1002 and one or more data remembrance components 1004 .
  • Device 1000 may be any type of device with some computing power.
  • a smart phone is one example of device 1000 , although device 1000 could be a desktop computer, laptop computer, tablet computer, set top box, or any other appropriate type of device.
  • Processor(s) 1002 are typically microprocessors, such as those found in a personal desktop or laptop computer, a server, a handheld computer, or another kind of computing device.
  • Data remembrance component(s) 1004 are components that are capable of storing data for either the short or long term.
  • Examples of data remembrance component(s) 1004 include hard disks, removable disks (including optical and magnetic disks), volatile and non-volatile random-access memory (RAM), read-only memory (ROM), flash memory, magnetic tape, etc.
  • Data remembrance component(s) are examples of computer-readable (or device-readable) storage media.
  • Device 1000 may comprise, or be associated with, display 1012 , which may be a cathode ray tube (CRT) monitor, a liquid crystal display (LCD) monitor, or any other type of monitor.
  • Display 1012 may be an output-only type of display; however, in another non-limiting example, display 1012 may be (or comprise) a touch screen that is capable of both displaying and receiving information.
  • Software may be stored in the data remembrance component(s) 1004 , and may execute on the one or more processor(s) 1002 .
  • An example of such software is text message augmentation software 1006 , which may implement some or all of the functionality described above in connection with FIGS. 1-9 , although any type of software could be used.
  • Software 1006 may be implemented, for example, through one or more components, which may be components in a distributed system, separate files, separate functions, separate objects, separate lines of code, etc.
  • a device e.g., smart phone, personal computer, server computer, handheld computer, tablet computer, set top box, etc.
  • a program is stored on hard disk, loaded into RAM, and executed on the device's processor(s) typifies the scenario depicted in FIG. 10 , although the subject matter described herein is not limited to this example.
  • the subject matter described herein can be implemented as software that is stored in one or more of the data remembrance component(s) 1004 and that executes on one or more of the processor(s) 1002 .
  • the subject matter can be implemented as instructions that are stored on one or more device-readable media. Such instructions, when executed by a phone, a computer, or another machine, may cause the phone, computer, or other machine to perform one or more acts of a method.
  • the instructions to perform the acts could be stored on one medium, or could be spread out across plural media, so that the instructions might appear collectively on the one or more computer-readable (or device-readable) media, regardless of whether all of the instructions happen to be on the same medium.
  • Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communication media.
  • device-readable media includes, at least, two types of device-readable media, namely device storage media and communication media.
  • Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that may be used to store information for access by a computer or other type of device.
  • communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism.
  • computer storage media does not include communication media.
  • device storage media does not include communication media.
  • any acts described herein may be performed by a processor (e.g., one or more of processors 1002 ) as part of a method.
  • a processor e.g., one or more of processors 1002
  • a method may be performed that comprises the acts of A, B, and C.
  • a method may be performed that comprises using a processor to perform the acts of A, B, and C.
  • device 1000 may be communicatively connected to one or more other devices through network 1008 .
  • device 1010 which may be similar in structure to device 1000 , is an example of a device that can be connected to device 1000 , although other types of devices may also be so connected.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Artificial Intelligence (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Computational Linguistics (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • General Health & Medical Sciences (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Business, Economics & Management (AREA)
  • Operations Research (AREA)
  • Tourism & Hospitality (AREA)
  • Telephone Function (AREA)
US13/723,190 2012-12-20 2012-12-20 Messages augmented with structured entities Abandoned US20140179358A1 (en)

Priority Applications (8)

Application Number Priority Date Filing Date Title
US13/723,190 US20140179358A1 (en) 2012-12-20 2012-12-20 Messages augmented with structured entities
CN201380066921.1A CN105027587B (zh) 2012-12-20 2013-12-20 利用结构化实体扩充的消息
EP13819148.1A EP2936846B1 (en) 2012-12-20 2013-12-20 Messages augmented with structured entities
JP2015549763A JP6324407B2 (ja) 2012-12-20 2013-12-20 構造化エンティティを用いて拡張されたメッセージ
PCT/US2013/076823 WO2014100544A1 (en) 2012-12-20 2013-12-20 Messages augmented with structured entities
KR1020157018573A KR102059231B1 (ko) 2012-12-20 2013-12-20 구조화된 엔티티로 강화된 메시지
US15/349,159 US10142268B2 (en) 2012-12-20 2016-11-11 Messages augmented with structured entities
US16/169,067 US10484318B2 (en) 2012-12-20 2018-10-24 Messages augmented with structured entities

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/723,190 US20140179358A1 (en) 2012-12-20 2012-12-20 Messages augmented with structured entities

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/349,159 Continuation US10142268B2 (en) 2012-12-20 2016-11-11 Messages augmented with structured entities

Publications (1)

Publication Number Publication Date
US20140179358A1 true US20140179358A1 (en) 2014-06-26

Family

ID=49950063

Family Applications (3)

Application Number Title Priority Date Filing Date
US13/723,190 Abandoned US20140179358A1 (en) 2012-12-20 2012-12-20 Messages augmented with structured entities
US15/349,159 Active US10142268B2 (en) 2012-12-20 2016-11-11 Messages augmented with structured entities
US16/169,067 Active US10484318B2 (en) 2012-12-20 2018-10-24 Messages augmented with structured entities

Family Applications After (2)

Application Number Title Priority Date Filing Date
US15/349,159 Active US10142268B2 (en) 2012-12-20 2016-11-11 Messages augmented with structured entities
US16/169,067 Active US10484318B2 (en) 2012-12-20 2018-10-24 Messages augmented with structured entities

Country Status (6)

Country Link
US (3) US20140179358A1 (xx)
EP (1) EP2936846B1 (xx)
JP (1) JP6324407B2 (xx)
KR (1) KR102059231B1 (xx)
CN (1) CN105027587B (xx)
WO (1) WO2014100544A1 (xx)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150347534A1 (en) * 2014-05-30 2015-12-03 Apple Inc. Structured suggestions
US20170011355A1 (en) * 2014-05-30 2017-01-12 Apple Inc. Structured suggestions
US9740740B1 (en) * 2016-02-22 2017-08-22 Pebble Technology Corp. Using metadata to take action on an SMS message on a proprietary system
US9787624B2 (en) 2016-02-22 2017-10-10 Pebble Technology, Corp. Taking actions on notifications using an incomplete data set from a message
US20180213078A1 (en) * 2017-01-23 2018-07-26 Bandwidthx Inc. Application management for a mobile device
US10445425B2 (en) 2015-09-15 2019-10-15 Apple Inc. Emoji and canned responses
US11025565B2 (en) 2015-06-07 2021-06-01 Apple Inc. Personalized prediction of responses for instant messaging
US11528601B1 (en) 2021-06-09 2022-12-13 T-Mobile Usa, Inc. Determining and ameliorating wireless telecommunication network functionalities that are impaired when using end-to-end encryption

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11477139B2 (en) * 2016-02-25 2022-10-18 Meta Platforms, Inc. Techniques for messaging bot rich communication
CN107979700B (zh) * 2017-11-27 2020-03-10 维沃移动通信有限公司 一种发送通知信息的方法及移动终端
CN114390452B (zh) * 2022-01-18 2023-05-26 平安科技（深圳）有限公司 消息发送方法及相关设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5859636A (en) * 1995-12-27 1999-01-12 Intel Corporation Recognition of and operation on text data
US20030097283A1 (en) * 2001-11-22 2003-05-22 Fujitsu Limited Information processing method and system for reservation
US20080109462A1 (en) * 2006-11-06 2008-05-08 Research In Motion Limited System and method of message compression
US20090186634A1 (en) * 2008-01-18 2009-07-23 Verizon Data Services, Inc. Method and System for SMS/MMS Messaging to A Connected Device
US20100159965A1 (en) * 2008-12-23 2010-06-24 At&T Mobility Ii Llc Scalable message fidelity
US20100167766A1 (en) * 2008-12-31 2010-07-01 Matias Duarte Integrated mixed transport messaging system
US20100287241A1 (en) * 2007-03-23 2010-11-11 Scott Swanburg Enhanced Messaging Feature

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070021969A1 (en) * 2005-03-23 2007-01-25 Homeier-Beals Thomas E Mobile electronic transaction system, device and method therefor
US7251680B2 (en) * 2003-10-31 2007-07-31 Veritas Operating Corporation Single instance backup of email message attachments
US7363295B2 (en) 2004-04-19 2008-04-22 Yahoo! Inc. Techniques for inline searching in an instant messenger environment
GB2422519B (en) 2004-04-30 2006-11-08 Yoomedia Plc Improvements relating to telecommunications
US20060218234A1 (en) 2005-03-24 2006-09-28 Li Deng Scheme of sending email to mobile devices
KR100741518B1 (ko) * 2005-08-10 2007-07-20 (주)이스톰 지인간의 광고 메시지 송수신 방법 및 시스템
KR100634335B1 (ko) 2005-09-16 2006-10-16 한영석 정보 질의 입력 창을 이용한 메시지 전송 방법 및 시스템
US9166823B2 (en) * 2005-09-21 2015-10-20 U Owe Me, Inc. Generation of a context-enriched message including a message component and a contextual attribute
US8819034B2 (en) * 2005-12-14 2014-08-26 Blackberry Limited Method and apparatus for generating a new event directly from a document
US7756536B2 (en) 2007-01-31 2010-07-13 Sony Ericsson Mobile Communications Ab Device and method for providing and displaying animated SMS messages
US20080235335A1 (en) 2007-03-20 2008-09-25 International Business Machines Corporation Method, system, and computer program product for changing the status of an existing email in a recipient email client inbox
US8239462B2 (en) * 2007-08-31 2012-08-07 Red Hat, Inc. Method and system for composing electronic messages
US8433797B2 (en) * 2011-04-11 2013-04-30 Ringcentral, Inc. User interface for accessing messages
JP5612002B2 (ja) * 2012-02-29 2014-10-22 ビッグローブ株式会社 プッシュ配信装置、携帯端末、プッシュ配信方法およびプッシュ配信システム

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5859636A (en) * 1995-12-27 1999-01-12 Intel Corporation Recognition of and operation on text data
US20030097283A1 (en) * 2001-11-22 2003-05-22 Fujitsu Limited Information processing method and system for reservation
US20080109462A1 (en) * 2006-11-06 2008-05-08 Research In Motion Limited System and method of message compression
US20100287241A1 (en) * 2007-03-23 2010-11-11 Scott Swanburg Enhanced Messaging Feature
US20090186634A1 (en) * 2008-01-18 2009-07-23 Verizon Data Services, Inc. Method and System for SMS/MMS Messaging to A Connected Device
US20100159965A1 (en) * 2008-12-23 2010-06-24 At&T Mobility Ii Llc Scalable message fidelity
US20100167766A1 (en) * 2008-12-31 2010-07-01 Matias Duarte Integrated mixed transport messaging system

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10747397B2 (en) * 2014-05-30 2020-08-18 Apple Inc. Structured suggestions
US20170011355A1 (en) * 2014-05-30 2017-01-12 Apple Inc. Structured suggestions
US20170010769A1 (en) * 2014-05-30 2017-01-12 Apple Inc. Structured suggestions
US20170011354A1 (en) * 2014-05-30 2017-01-12 Apple Inc. Structured suggestions
US20150347534A1 (en) * 2014-05-30 2015-12-03 Apple Inc. Structured suggestions
US20200363916A1 (en) * 2014-05-30 2020-11-19 Apple Inc. Structured suggestions
US10620787B2 (en) * 2014-05-30 2020-04-14 Apple Inc. Techniques for structuring suggested contacts and calendar events from messages
US10565219B2 (en) * 2014-05-30 2020-02-18 Apple Inc. Techniques for automatically generating a suggested contact based on a received message
US10579212B2 (en) 2014-05-30 2020-03-03 Apple Inc. Structured suggestions
US10585559B2 (en) * 2014-05-30 2020-03-10 Apple Inc. Identifying contact information suggestions from a received message
US11025565B2 (en) 2015-06-07 2021-06-01 Apple Inc. Personalized prediction of responses for instant messaging
US11048873B2 (en) 2015-09-15 2021-06-29 Apple Inc. Emoji and canned responses
US10445425B2 (en) 2015-09-15 2019-10-15 Apple Inc. Emoji and canned responses
US9787624B2 (en) 2016-02-22 2017-10-10 Pebble Technology, Corp. Taking actions on notifications using an incomplete data set from a message
US20200012641A1 (en) * 2016-02-22 2020-01-09 Fitbit, Inc. Using Metadata To Take Action On An SMS Message On A Proprietary System
US10831754B2 (en) * 2016-02-22 2020-11-10 Fitbit, Inc. Using metadata to take action on an SMS message on a proprietary system
US10372710B2 (en) * 2016-02-22 2019-08-06 Fitbit, Inc. Using metadata to take action on an SMS message on a proprietary system
US9740740B1 (en) * 2016-02-22 2017-08-22 Pebble Technology Corp. Using metadata to take action on an SMS message on a proprietary system
US20180213078A1 (en) * 2017-01-23 2018-07-26 Bandwidthx Inc. Application management for a mobile device
US11528601B1 (en) 2021-06-09 2022-12-13 T-Mobile Usa, Inc. Determining and ameliorating wireless telecommunication network functionalities that are impaired when using end-to-end encryption
US11706615B2 (en) 2021-06-09 2023-07-18 T-Mobile Usa, Inc. Determining and ameliorating wireless telecommunication network functionalities that are impaired when using end-to-end encryption
US12015912B2 (en) 2021-06-09 2024-06-18 T-Mobile Usa, Inc. Determining and ameliorating wireless telecommunication network functionalities that are impaired when using end-to-end encryption

Also Published As

Publication number Publication date
KR20150099547A (ko) 2015-08-31
EP2936846B1 (en) 2020-02-26
WO2014100544A1 (en) 2014-06-26
US10142268B2 (en) 2018-11-27
US20190058678A1 (en) 2019-02-21
US10484318B2 (en) 2019-11-19
JP6324407B2 (ja) 2018-05-16
US20170063752A1 (en) 2017-03-02
CN105027587B (zh) 2019-06-04
JP2016509282A (ja) 2016-03-24
EP2936846A1 (en) 2015-10-28
CN105027587A (zh) 2015-11-04
KR102059231B1 (ko) 2019-12-24

Similar Documents

Publication Publication Date Title
US10484318B2 (en) Messages augmented with structured entities
US20230134004A1 (en) Systems and methods for processing and organizing electronic content
US9406048B2 (en) Email system for preventing inadvertant transmission of propriety message or documents to unintended recipient
CN107636641B (zh) 用于处理附加至电子邮件消息的注释的统一消息传送平台
US9047259B1 (en) System and method for renaming hyperlinks
US9485285B1 (en) Assisting the authoring of posts to an asymmetric social network
US8874148B2 (en) Automatic contact recognition from SMS
US10897447B2 (en) Computerized system and method for automatically performing an implicit message search
US9836724B2 (en) Email views
US20230259247A1 (en) Data entry for an application
US20110099464A1 (en) Mechanism for adding content from a search to a document or message
CN109074388B (zh) 基于消息内容划分缩略图预览的优先级
US20240146676A1 (en) Computerized system and method for controlling electronic messages and their responses after delivery
US20200210053A1 (en) Systems, devices and methods for electronic determination and communication of location information
US9542365B1 (en) Methods for generating e-mail message interfaces
US20160219004A1 (en) An apparatus and method for handling metadata of an email message
KR20210122309A (ko) 다수의 메시지들을 참조하는 소셜 미디어 메시지들의 작성
EP3057045A1 (en) Method for generating an electronic message on an electronic mail client system, computer program product for executing the method, computer readable medium having code stored thereon that defines the method, and a communications device
US9385978B2 (en) Generating and/or providing access to a message based on portions of the message indicated by a sending user
US9912622B2 (en) Electronic messaging system involving adaptive content

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KHAN, SADI;AL-RASHID, KAZI;BONG, JEREMY;AND OTHERS;SIGNING DATES FROM 20121214 TO 20121217;REEL/FRAME:029517/0195

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034747/0417

Effective date: 20141014

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:039025/0454

Effective date: 20141014

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION