Patent Application
20230120471
The present invention relates generally to methods and systems for providing electronic messaging.
Conventional electronic messaging systems deliver a plethora of messages to users on a nearly continuous basis. Messages are of various types including e-mail, event, calendar item, post, task, comment, and document, and are typically stored and presented to users via distinct and separate platforms, e.g., a dedicated web browser page or mobile application provides e-mails, another browser or mobile application provides calendar items, perhaps another platform for comments, and so forth. Disparate messages are often related topically, or by individual, e.g., team members collaborating on a project. For example, team members collaborating on a project may need to access a common set of messages, events, posts, tasks, comments, and documents relating to the project. Conventional electronic messaging systems with their disparate platforms inherently lack integration, and therefore present a formidable challenge for groups of users needing unified access to topically related messages, thereby hampering collaboration and productivity.
The subject matter presented herein is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
A communication stream aggregates electronic messages of arbitrary types and makes them available to stream users. Thus, messages, e.g., events, tasks, posts, comments, and documents, are conveniently accessible to users in a simple, intuitive, and unified way.
By way of example and without limitation, application of a communication stream to a product development project is briefly described. A communication stream corresponding to a product development project is created, and members of a product development team join the stream as users. With certain exceptions, e.g., private messages, members may view and participate, and have access to messages in, the product development communication stream. Team members communicate as the project moves forward, submitting messages to the stream through, e.g., messages, events, tasks, posts, comments, and documents. Over time, a body of product development history grows within the stream. Team membership naturally changes over time as some members leave, and others join. A new team member, once joined to the stream, has access to the body of product development history. The new member may therefore advantageously and expeditiously “onboard” herself to the project simply by reviewing the stream, thereby avoiding a need to resort to unreliable word-of-mouth “folklore” as often occurs. This is especially advantageous when a new team member steps into a supervisory role, e.g., to oversee an existing project. Team members not authorized to view an entire stream are allowed limited access to one or more streams in accordance with one embodiment. For example, a team member may be allowed to participate in a stream by time, e.g., within one or more date ranges, e.g., January-July 2014; September-November 2014, by stream message type, e.g., messages, events, posts, or by any combination of times and types. A plurality of communication streams, e.g., one stream per product development project, enables efficient scaling by capturing a body of information for each project. Similarly, communication streams find useful application in other situations, including, e.g., sales and marketing campaigns, customer relationship matters, election campaigns in a political context, and client matters in a legal, financial, or other professional services settings.
A user interface, e.g., as depicted in
Communication stream server 102 includes accounts for users, also referred to as members. A member is identified by a user I.D., e.g., user001, and is granted access to the member's user account on communication stream server 102 via the user I.D. and a password. Stream service 109, with reference to data structures 300 and 400, creates communication streams, joins users to the communication streams, processes messages, and is involved in managing interrelationships among messages, streams, and users.
Stream service 109 receives an email message in one aspect, the message having commands for creating a communication stream. The message includes a return address, and the commands specify a stream identifier. Responsive to the commands, stream service 109 creates the stream and assigns the stream identifier to the stream. If stream service 109 detects erroneous commands, it transmits a message to the return address identifying the errors. Stream service 109 detects errors in replies it may receive, and repeats (iterates) until it detects an acceptably low number of errors, or receives a termination command.
UI service 107, in communication with stream service 109, provides a representation of one or more communication streams having one or more users or members, e.g., as depicted in
A multicast detection engine 115, a service for identifying multicast messages, analyzes one or more email messages and determines whether the one or more messages may be a bulk transmission, e.g., to a plurality of recipients. A bulk transmission may be formatted as a unicast message to multiple recipients in a single domain (e.g., zoho.com), each message including a personalized greeting, or it may be a multicast message, e.g., a single message directed to a distribution group (mailing list). Bulk transmissions include, e.g., newsletters, ads, and solicitations involving coupon offers. Multicast detection engine 115 identifies bulk transmissions by analyzing incoming email headers for similarities, e.g., source IP address, in accordance with one embodiment. In another aspect, multicast detection engine 115 detects and compares message text, e.g., by pattern detection, and heuristically-based lexicographical analysis. Specific triggering criteria, e.g., a specific source IP address, and message count, e.g., 50 or 100 messages, are employed in accordance with one embodiment. Upon detection of a bulk transmission, multicast detection engine 115 identifies recipients of the bulk transmission as such, maintaining a corresponding list of user I.D.s, and initiating creation of a communication stream. Multicast detection engine 137 in email server 131 (
UI service 107 displays one or more UI-focused and context-sensitive bulk transmission indications to alert a user to the presence of a bulk transmission. In one embodiment, UI service 107 displays a UI-focused indication, e.g., command icon 272 depicted in email interface 250 in
In another embodiment, UI service 107 provides one or more context-sensitive indications to an email viewing window 255, depicted in
In one embodiment, a bulk transmission arrives in a user's email interface before multicast detection 119 has completed detection. In that instance, the one or more bulk transmission indications will not initially appear. For example, an indicator in an email message list would be absent initially, but would automatically appear later after multicast detection engine 119 finishes identifying the bulk transmission, and provides UI service 107 with bulk transmission indications. In another embodiment, an email message corresponding to a bulk transmission arrives in the user's email interface after multicast detection engine 119 finishes identifying a bulk transmission and providing UI service 107 with bulk transmission indications. In this instance, UI service 107 displays the one or more bulk transmission indications contemporaneously when the email message corresponding to the bulk transmission arrives. UI-focused indications, e.g., command icon 272, may be displayed immediately. For example, communication stream menu 271 includes menu item 266 corresponding to a bulk transmission not yet received in email message list 265. Menu item 266 indicates stream “Bulk2@zoho.com” corresponds to a bulk transmission from “deals@discoun . . . ” with subject “Special—Big Deals Today!” Asserting menu item 266 enables a user to join stream “Bulk2@zoho.com” even before the email message corresponding to that bulk transmission appears in email message list 265. Context-sensitive indications are instead displayed in an appropriate context, e.g., “Join Stream” menu item 298 appears in context-sensitive menu 275 when displaying, e.g., email message 278 in viewing pane 270 corresponding to the bulk transmission, and an indicator, e.g., the letter “B” 268 may appear alongside email message 278 in email message list 265, or along with an email message open for viewing. In another aspect, an email message arrives in the users' email interface before multicast detection engine 119 finishes identifying a bulk transmission and providing UI service 107 with bulk transmission indications. In that instance, the view of messages, e.g., message list 265, would not include an indication of a bulk transmission, e.g., the letter “B” 268 depicted in message list 265 would be absent. The absent letter “B” 268 would automatically appear later, however, after bulk transmission detection completes.
Application programming interfaces (“APIs,” “API”) are provided by services, e.g., email service 121, 137, and stream service 109, and enable services to interact with other services, and software components or entities. For example, an API receives a request from a software entity, and appropriately handles, directs, and responds to the request. APIs are depicted within rectangles/blocks in
In another aspect, UI service 107 provides a “message details” link in view 205. If view 205 is configured to view communication stream messages (control 229 asserted), activating the link reveals message details pertaining to, e.g., a stream message. The details revealed include information identifying whether the stream message was sourced, or mapped from, an email. Similarly, activating the message details link when view 205 is configured to view email (control 227 asserted) reveals email message details, including information identifying whether the email was sourced, or mapped from, a stream message.
UI service 107 may communicate with a corresponding UI service in a client, e.g., devices 140 (phone), 150 (laptop), and 160 (tablet). UI service 107 delivers a user interface in a web browser and exchanges data via, e.g., Javascript, in accordance with one embodiment. UI service 107 exchanges data with a UI client via, e.g., JSON for mobile devices, while a mobile device-resident application provides a UI relevant to the mobile device in accordance with another embodiment.
In another embodiment, UI 107 receives a form of email address, e.g., user001@zoho.com, from a communication stream interface on, e.g., a web browser or mobile application, and in response, supports and enables on the web browser or mobile device, an email interface including the form of email address pre-populated in a “To:” email address field. In accordance with another embodiment, UI 107 receives a form of stream I.D. or stream handle from an email interface on, e.g., a web browser or mobile application, and in response, transmits to the web browser or mobile device, a communication stream interface including the form of Stream I.D. pre-populated in a stream address field.
Data tables within data structures 300 and 400 are variable length and expandable. Accordingly, a table such as a message stream table 320, depicted for convenience of illustration with 8 rows, may expand to include an arbitrary number of rows. Likewise, column 2 of table 320, depicted identifying two streams (“1,3”) associated with message 301, may expand to accommodate a larger list of entries, e.g., “1,3,5,7,” as message 301 becomes associated with additional streams, e.g., 5 and 7.
In one aspect, stream service 109 receives a request to create a communication stream. The request arrives from email service 121 or email service 136 in accordance with another embodiment, the email including a return address and commands for creating the communication stream. In another aspect, the request arrives in a non-email message, e.g., via SMS or text message. Command keywords include “create:”, “members:”, and “name:” in one embodiment. A semicolon “;” delimits commands. For example, stream service 109 receives commands “create: str001@zoho.com; members: user001, user002, user003; name: Marketing,” parses the commands, creates str001, joins users001-003 to the stream, and names it “Marketing.” If stream service 109 detects erroneous commands, e.g., a keyword “create:” or “members:” are missing or misspelled, it transmits to the return address, a message identifying errors corresponding to the commands. Stream service 109 detects errors in replies it may receive, and repeats (iterates) until it detects an acceptably low number of errors, or receives a termination command. A keyword “body:” is provided in accordance with another embodiment. Text following this keyword is interpreted as body text to a communication stream message.
The request to create a communication stream arrives from UI service 107, mapping engine 119, or multicast detection engine 115 in another aspect. The request specifies users, including at least a first user. For example, stream service 109 receives a request specifying user001. The request includes a stream name, e.g., “Marketing,” in one embodiment. The request includes a non-private message in accordance with yet another embodiment. Stream service 109 assigns a stream identifier, “1,” enters it in row 1, column 1 of a user stream table 510, enters “Marketing” in stream display name column 2, and enters usr001 in column 3. As depicted in
Messages 301-308, also referred to as stream messages, are of various types in one embodiment, including messages, tasks, events, posts, comments, and documents. A message includes a metadata table, e.g., tables 311, 312, and 316 corresponding to messages 301, 302, and 306. For clarity of depiction, metadata tables relating to other messages are not shown in
Stream service 109 receives a private message, a comment, from the second user, user002, the private message referencing non-private message 301, the third user, user003, and stream identifier 1. Stream service 109 adds metadata table 312 to the private message, assigns and enters message I.D. 302 in row 2, and enters “302” and “1” respectively in row 2, columns 1 and 2 of message stream table 320, thereby associating message 302 with stream 1. Service 109 enters message type “Comment,” timestamp 1409190205, and sender user002 in metadata table 312, and transmits user I.D.s user002, user003, and message I.D. 302, to private message service 111. Service 111 examines private table 340, determines there is no entry for message 302, finds an open row, here, row 2, enters “302” in row 2, column 1, and user I.D.s user002 and user003 in column 2, indicating that only those users may access, e.g., view, message 302. Message 302 is therefore private because access to it is limited, here, to user002 and user003. Private message service 111 returns a reference to row 2 to stream service 109, which enters the reference in row 7 of metadata table 312. Private message service 111 adds message 302 to row 1, column 1 of an anchor table 350 in one embodiment, and adds message 301 to row 1, column 2. By reading anchor table 350, UI service 107 may display message 302 “anchored” to message 301, e.g., by indenting and displaying message 302 below 301. In addition to anchoring private messages, any arbitrary number of messages, whether private or non-private, may be ordered (or “anchored”) according to this scheme. By way of example and without limitation, messages 307 and 308 are “anchored” to message 305 as depicted logically in
To demonstrate anchoring and viewing of private and non-private messages, UI service 107 receives a request from user003 to view stream 1. In turn, stream service 109 receives a request from UI service 107 including user I.D. user003 and stream I.D. stream 1. Service 109 examines message stream table 320, determines messages 301 and 302 are within stream 1, and examines row 7 of metadata tables 311 and 312 for references to rows of message user table 340 relating to messages 301 and 302, here, rows 1 and 2. Stream service 109 determines row 1, column 2 of table 340 is null, and therefore message 301 is non-private. Service 109 determines row 2, column 2 of table 340 contains user I.D.s user002 and user003, indicating only those users may access message 302. Service 109 transmits message I.Ds 301 and 302 to UI service 107, which provides a representation of the communication stream including non-private message 301 and private message 302, to the third user, user003. UI service 107 consults anchor table 350, determines that message 302 is anchored to message 301, and displays message 302 below and indented relative to 301 in accordance with one embodiment. Similarly, a request received by service 107 from user002 to view stream 1 is handled in the same manner and results in UI service 107 providing a representation of the communication stream, including the non-private message (301) and the private message (302) to the second user, user002. UI service 107 next receives a request from user001 to view stream 1. As described above, stream service 109 determines which messages are available in stream 1, and whether any are private. Because message 302 is accessible by user002 and user003, but not by user001, Service 109 transmits only message I.D. 301 to UI service 107, which provides a representation of the communication stream including non-private message 301, sans (without) private message 302, to user001, the first user.
In another embodiment, private message service 111 manages private table 340, and with reference to metadata tables, determines whether messages identified in private table 340 may be viewed by certain users. More specifically, row 7 of a message metadata table may be null, e.g., as depicted in metadata table 316, or may include a reference to private table 340. A null entry in row 7 indicates message 306 is non-private. A non-null entry in row 7, e.g., it references a row in table 340, indicates the row must be examined. If column 2 of the specified row in table 340 is null, then the message is non-private. If column 2 includes a list of user I.D.s, then the message is private, and may be accessed only by users corresponding to the list of user I.D.s. In one embodiment, stream service 109 consults message stream table 320, collects a list of messages, transmits a request including those messages and a user I.D. to private message service 111, and awaits a return transmission from service 111 indicating which messages are accessible to the user corresponding to the user I.D. In another embodiment, stream service 109 directly inspects table 340 without involving private message service 111. In another embodiment, UI service 107 transmits a user I.D. and a stream I.D. to private message service 111, which in turn examines stream table 320, metadata tables, and private table 340, and returns to UI service 107, a list message I.Ds accessible to the user corresponding to the user I.D.
In another aspect, a topic identifier identifies subject matter relating to a message, and is useful for user display, as a search key, and for mapping or transforming a message to an external or non-native format, e.g., e-mail, or a calendaring system. A topic identifier may also include, for user convenience, text relating to a tag, e.g., #ZoholicsMay. A tag is typically inserted by a user to associate a message with other messages, or as a reference to a group of similarly tagged messages. A Topic I.D. field is provided at row 9 of a metadata table in accordance with one embodiment. For example, stream service 109 receives a request to assign a topic identifier to a message, e.g., message 301, and in response, assigns the topic identifier to the message, e.g., 301, by inserting it into row 9 of metadata table 311.
A tag provides associations among communication stream messages, even if the messages are in different communication streams. Message tagging service 113 accesses message tag table 330, and tag type table 420, which include data relating to tagging and searching messages, to manage communication stream message tags. Message table 330 associates a message with one or more tags. For example, table 330, row 1, indicates that message 301 (column 1) is associated with two tags, “#ZoholicsMay,” and “Tag 2.” Tag type table 420 associates a tag with a display name, a tag type, and optional tagging data, e.g., types “TT,” “DR,” “SE,” and “RF” that may be used in searching for messages. Any tag type and related data may appear in any row of table 420. By way of example and without limitation, row 2 indicates “Tag2” (column 1) is of tag type “DR” (column 3) and optional DR (date range) tagging data (“1503052100, 1505190000”) are in column 4. In response to a request for messages relating to “Tag 2,” message tagging service 113 searches tag type table 420, locates “Tag 2” in row 2, determines that Tag2 is of type “DR” and searches messages fitting date range criteria specified in column 4. Message tagging service 113 “searches messages” by examining row 4 of metadata tables (Date/Time), building a list of message I.D.s with timestamps between Mar. 3, 2015, 9:00 pm and May 19, 2015, 12:00 am, as specified in row 2, column 4 of tag type table 420. In another example, row 1 of tag type table 420 indicates tag “#ZoholicsMay” is of tag type “TT.” Accordingly, Message tagging service 113 searches tag table 330 for messages matching the tag itself, here, “#ZoholicsMay.” A search engine expression (type “SE”) is provided in column 4, enabling arbitrarily complex criteria for retrieving messages relating to tag 3. A list of email references (type “RF”) is provided in column 4 to preserve links in a conventional email thread, thereby enhancing mapping and transforming between conventional email and a communication stream.
By way of example and without limitation, messages 301 and 303, associated respectively with streams 1 and 3, and are also associated with a Tag I.D., e.g., “#ZoholicsMay.” A user wishing to retrieve messages relating to #ZoholicsMay sends a request including this term to UI Service 107. Message tag service receives the request, searches message tag table 330 to obtain a list of messages tagged with #ZoholicsMay, here, 301 and 303, and as explained above with respect to messages within a stream, examines whether a user has access to each message, and returns a list of tagged messages, e.g., 301, 303, to UI services 107 to which the user has access. A tag may be added by an automated process, e.g., by multicast detection engine 115 or mapping engine 119, either separately or in cooperation with message tagging service 113, or by a user requesting a tag via UI service 107.
In another aspect, one or more communication stream messages may be “liked” by a user, indicating, e.g., a positive “vote” relating to a comment or message. Row 8 of message metadata tables may include a reference to a “like” table, e.g., table 345. Table 345 associates a message with one or more users who have expressed a “like” relating to the message. For example, row 8 of message metadata table 316 (corresponding to message 306) refers to row 1 of like table 345. Column 2 of this table lists users001-004, indicating these users “like” message 306. When providing a view of a communication stream including message 306, UI service 107 reads like table 345 and displays, e.g., a count of users liking message 306. An exemplary view of a communication stream provided by UI service 107, including a message indicating one (1) “like” 223, is depicted in
In step 625, the method receives a request from the first user to view the first communication stream. The method queries the message stream table in step 630, e.g., message stream table 320, and determines that the non-private and private messages are included in the first communication stream. The private table is next queried in step 635, and the method determines which of the private and non-private messages are accessible to the first user. At step 640, for each message accessible to the first user, the method queries the anchor table, e.g., table 350, to determine whether the message is anchored to another. If “yes” at step 650, the method presents the anchor message (the message to which other messages are “anchored”) at step 655, and presents messages anchored to the anchor message. The anchored messages are presented offset and below the anchor message in one embodiment. If “no” at step 650, then at step 645, the method simply presents the message. At step 660, the method determines whether the last message has been presented. If “no,” the method returns to step 640 and repeats steps 640-660 until the last message has been presented. If “yes,” the method is done at step 695.
In distributed mapping, a plurality of mapping engines serve a plurality of services. One or more mapping engines may be embedded in one or more servers along with other services, may be disposed as standalone entities, or be disposed in any combination. In distributed mapping configuration 830, mapping engine 835 provides mapping services for email app server 833, and mapping engine 837 provides mapping services for (communication) stream app server 840. Mapping engine for streams 837 transforms, e.g., algorithmically or based on rules 1000 communication stream messages in stream app server 840, and exports the transformed messages via path 836, a generalized communication path involving data and control, to mapping engine for email 835 in accordance with one embodiment. Mapping engine for email 835 provides additional transformation, if needed for email app server 833, and forwards the message to server 833. Similarly, a message originating in email server 833 may be transformed by mapping engine for email 835, e.g., algorithmically or based on rules 1000, and transmitted to mapping engine for streams 837 via path 838 (a generalized communication path involving data and control), further transformed if needed, and forwarded to stream app server 840. Communication between mapping engines 835 and 837 is accomplished via APIs, in which each engine polls the other, e.g., periodically to obtain data changes in accordance with one embodiment. Communication between engines 835 and 837 is accomplished via “webhook,” in which each pushes data to the other and vice-versa via, e.g., a callback or interrupt-driven mechanism in accordance with another embodiment. When an update, change, or event occurs in a mapping engine, the engine provides via a webhook to another engine, e.g., delivered at a URL, one or more triggers, data, or changes to data, and information related to events or data changes. Other examples of distributed mapping are depicted in
In one embodiment, mapping and transforming of messages occurs between systems. A conventional email system 910 includes a conventional email client 911 in communication with a conventional email app server 913 and email DB (database) 915. A communication stream system 920 includes a stream client 921 in communication with a stream app server 923 and stream DB (database) 925. A mapping engine 928, in cooperation with webhooks and APIs provided by various services, e.g., services 107, 109, 111, 113, and 115, and data structure 1000 (depicted in
In configuration 930, a combo client 931 and a mapping engine 938 reside in a client device, e.g., wireless handheld device 140, and view messages in combo client 931 originating in email DB 935 and Stream DB 939. Mapping engine 938, in communication with email app server 933 and email DB 935, transforms and maps email messages to a format suitable for storing in communication stream DB 939, and viewing in combo client 931. Mapping engine 938 cooperates with services in a communication stream server, e.g., server 102 via webhooks and APIs, and data structure 1000, to effectuate message mappings and transformations, which may be bi-directional, e.g., email-to-stream DB, and stream-to-email DB. When disposed in a combo client, e.g., 931, mapping engine 938, occurring in many instances of combo client 931, is in a distributed configuration. Although depicted in combo client 931, mapping engine 938 may also be disposed in either server 933 or 937, or may be separately disposed as a standalone service.
In another embodiment, configuration 940 relies on mapping engine 948 to map and transform messages (as described above) residing in a combined stream and email DB 949, to a conventional email client 941 communicating with email app server 945, and to a stream client 943, communicating with stream app server 947. Configuration 950 relies on mapping engine 958 to map and transform messages (as described above) residing in separate email (952) and stream (959) DBs. Conventional email client 951 communicates with email app server 955, and stream client 953, communicates with stream app server 957.
The following description applies to mapping and transforming communication stream messages to email messages. Column 1 of table 1010 includes elements of communication stream message metadata, e.g., metadata table 311. Column 2 of table 1010 includes rules that are executed by a mapping engine, e.g., 119 to effectuate a mapping or transformation. For purposes of illustration, mapping engine 119 processes the rules in table-ascending order. More generally, it may do so in any order. Mapping engine 119 refers to data structures 300 and 400, and relies on other services, e.g., stream service 109, private message service 111, and email services 121 and 137, including their respective referencing of data structures 300 and 400 and operations (as described above) to effectuate rule processing.
To map or transform a communication stream message 302 to an email message, a mapping engine, e.g., mapping engine 119 or 117, or UI service 107, receives a request to forward communication stream message 302 to several email addresses. It transmits the request to mapping engine 119, or another mapping engine, e.g., mapping engine 117, or 138, which executes the rule corresponding to row 1 (Stream I.D.) of table 1010. For clarity of discussion, only mapping engine 119 is described. Any mapping engine, e.g., 117 and 138, may be employed within the scope of the invention. It reads a private table reference in row 7 of metadata table 312 (corresponding to message 302), follows it to row 2 of table 340, and determines that message 302 is private because user002 and user003 are included in row 2 of table 340, indicting they are the only users allowed access to message 302, determines that neither user002 nor user003 is among the several email addresses, and stops. If private table 340 at row 2 (corresponding to message 302) includes an external address, e.g., extuser@notzoho.com (not shown), and if extuser@notzoho.com is among the forwarding email addresses, then mapping engine 119 determines to forward the mapped/transformed message 302 to the external address, further associating message 302 with a “Sent” email folder based on the “Sent” tag it reads from tag table 330, row 2, column 2 (“Folder”). Message 303 is similarly processed, and assuming it too has an external address, is mapped and directed to an external user's “Inbox” folder. Mapping and transforming of messages therefore advantageously retains message relationships. Here, the private message that user002 sent to user003 in the communication stream system is reflected, after mapping, in those users' respective email accounts as “Sent” for user002, and “Inbox” for user003. This is particularly useful when, e.g., mapping and transforming messages in bulk, for example initiated by an administrator, from a legacy email system to a communication stream system.
Mapping engine 119 transforms communication stream message 301 in accordance with another embodiment. A mapping engine, e.g., mapping engine 119, 117, or 138, or UI service 107, receives a request to forward communication stream message 301 to several email addresses. It transmits the request to mapping engine 119, which executes the rule in row 1 of table 1010, reads a private table reference in row 7 of metadata table 311 (corresponding to message 301), follows the reference to row 1 of table 340, and determines the entry is null. The message is therefore non-private. Mapping engine 119 prepares a draft email message and copies the several email address into the “To:” field of the draft email. Rules corresponding to rows 2-4 (Msg. I.D., Type, Date/Time) in table 1010 direct mapping engine 119 to concatenate information from corresponding fields in metadata table 311 and copy the information to a “Msg Source Info” field (analogous to the Msg Source Info field in stream table 320) corresponding to the email. Asserting a “Message Details” link in an email window while viewing the email produced by mapping engine 119 displays this information to a user in accordance with one embodiment. In another aspect, row 5 of table 1010 indicates mapping engine 119 is to enter the Stream I.D. in user@domain.com, format in the “From:” field of the draft email. Row 6 (Tag I.D.) directs mapping engine 119 to copy Folder tags, e.g., Inbox, Sent, Outbox, from table 330 corresponding to the stream message, to a corresponding Tag folder table in the email system database. Emails that have been mapped and transformed from communication stream messages thereby automatically appear in the same relative folders, e.g., Inbox, Sent, as their pre-transformation stream counterparts when displayed by UI service 107 in an email window. Row 7 (Private) relates to user addressing of private messages and was discussed above in connection with user addressing and processing of Row 1. Row 8 of table 1010 includes a rule relating to copying “Likes” from a communication stream message to an email. Mapping engine 119 reads, and if not null follows, a reference in row 8 of metadata table 311 to like table 345. In this example relating to message 301, row 8 of metadata table 311 is blank, so mapping engine 119 takes no action. Had row 8 referred to, e.g., table 345 row 1, mapping engine 119 would have counted four users (users001-004), and would have copied a string to the Subject: field of the draft email, e.g., “4 likes,” or “+1×4.” The destination email server database includes a metadata table (similar to stream metadata tables, e.g., 311) in one embodiment, corresponding to each email message, including a field corresponding to “likes.” Mapping engine 119 copies the user IDs from (stream) table 345 to the email “like” table corresponding to the email being created. An email client, when displaying the converted email, displays the user ID for each like in accordance with one embodiment similar to “likes” displayed in a stream client. Mapping engine 119 reads row 9 (Topic Identifier) of metadata table 301, determines that it is null. Had the field not been null, mapping engine 119 would have copied the Topic Identifier to the Subject: field of the draft email. Because the field is null, mapping engine 119 reads row 1 of table 410 (corresponding to Stream I.D. 1) and enters the display name from column 2 in the Subject: field of the draft email. Finally row 10 instructs mapping engine 119 to copy the body of communication stream message 301 to the body of the draft email. The transformation is complete, and mapping engine 119 submits the draft email to service 121 along with a request for it to transmit the draft email to an email address, here, the one or more email addresses in the “To:” field of the draft email. Responsive to the request, email service 121 transmits the email message. Mapping engine submits the draft email to service 136 in accordance with another embodiment. Mapping engine 938 performs the steps outlined above on a client device in accordance with another embodiment.
The following description applies to mapping and transforming email messages to communication stream messages. Mapping engine 119 receives an email message from mail service 121 in accordance with one embodiment. Table 1030 comprises rules executed by mapping engine 119 for transforming a conventional email message to a communication stream message. To map and transform email to stream messages, mapping engine 119 relies on data structures and services similar to those identified above with respect to mapping stream messages to email. At row 1 of table 1030, mapping engine 119 examines the “To:” field of the email and determines whether it identifies a communication stream, e.g., str001@zoho.com, or a user, e.g., user001@zoho.com. If so, the mapping engine proceeds; if not, it stops. Cc: (carbon copy) and Bcc: (blind carbon copy) fields of the email are ignored. If mapping engine 119 determines the “To:” field of the email does not identify a communication stream, it initiates creating a new communication stream corresponding to the “To:” field. In accordance with another embodiment, if the “To:” field includes a valid stream I.D., e.g., user001@zoho.com, and a corresponding email user, e.g., user001, has opted to view email as stream messages, then a corresponding Stream inbox (and potentially, e.g., other personal folders) will exist. In that case, Cc: and Bcc: will undergo a validity analysis as performed on the “To:” above, and included or ignored according to the validity analysis. Mapping engine 119 initiates communication with the stream server to create user accounts corresponding to addresses it identifies in the “From:,” “Cc:,” and “Bcc:” fields. For an address corresponding to an external user, e.g., external@notzoho.com, the newly created user account facilitates sending and receiving messages to the external user, but the account itself is inaccessible to the external user. Once mapping engine 119 determines the email includes a valid address to a communication stream, it prepares a draft communication stream message, including a draft metadata table, and enters the stream I.D. in row 1 of the draft metadata table. Rules corresponding to rows 2 and 4 (Email I.D., Date/Time) direct mapping engine 119 to concatenate information from corresponding fields a email metadata table corresponding to the email being transformed, and copy the information to the “Msg Source Info” in stream table 320 corresponding to the stream message. Activating a “Message Details” link while viewing a stream message, e.g., in view 205, or a stream-only interface, reveals the “Msg Source Info” in table 320, which includes information identifying the message originated as, i.e., its source is, an email message. Row 3 instructs mapping engine 119 to copy the “In-Reply-To” field of the email to the body of the draft communication stream message. This data is included for user convenience. Row 4 (Date/Time) is null, so mapping engine 119 takes no action. Stream service 109 will automatically timestamp the message after receiving it and the draft metadata table from mapping engine 119. Responsive to the instruction at row 5, mapping engine 119 copies the “From:” field in the email to row 5 (“Sender”) of the draft metadata table. Row 6 relates to processing of a “References:” header in a conventional email message. If this field is present in the email, mapping engine 119 creates a draft tag table in the format of table 420, enter “RF” in column 3 (type), and copies the data from the “References:” header in the email to column 4 of the draft tag table. Mapping engine 119 adds display text to column 2 of the temporary tag table, e.g., “References imported,” in accordance with another embodiment. At row 7 of table 1030, if the Subject field of the email is not null, mapping engine 119 copies it to row 9 (Topic I.D.) of the draft metadata table. Finally, row 8 instructs the mapping engine to copy the body of the email to the body of the draft communication stream message. Row 10 (Tag) directs mapping engine 119 to copy Folder tags, e.g., Inbox, Sent, Outbox, from the tag table corresponding to the email message, to tag table 330 in the communication stream database corresponding to the stream message. Stream messages that have been mapped and transformed from email messages thereby automatically appear in the same relative folders, e.g., Inbox, Sent, as their pre-transformation email counterparts when displayed by UI service 107 in a stream view window, e.g., view 205. The transformation is complete, and mapping engine 119 submits the draft communication message, the draft metadata table, and if one exists, the draft tag table, to stream service 109. Stream service 109 creates a new stream message, including a new metadata table, and respectively copies the contents from draft tables to the new tables. As in creating a new message (explained above with respect to
Computing system 1100 includes a conventional computer 1120, including a processing unit 1121, a system memory 1122, and a system bus 1123 that couples various system components including the system memory to the processing unit 1121. The system bus 1123 may be any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory includes read only memory (ROM) 1124 and random access memory (RAM) 1125. A basic input/output system 1126 (BIOS), containing the basic routines that help to transfer information between elements within the computer 1120, such as during start-up, is stored in ROM 1124. The computer 1120 further includes a hard disk drive 1127 for reading from and writing to a hard disk, not shown, a solid-state drive 1128 (e.g. NAND flash memory), and an optical disk drive 1130 for reading from or writing to an optical disk 1131 (e.g., a CD or DVD). The hard disk drive 1127 and optical disk drive 1130 are connected to the system bus 1123 by a hard disk drive interface 1132 and an optical drive interface 1134, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for computer 1120. Other types of computer-readable media can be used.
A number of program modules may be stored on the hard disk, solid state disk 1128, optical disk 1131, ROM 1124 or RAM 1125, including an operating system 1135, one or more application programs 1136, other program modules 1137, and program data 1138. A user may enter commands and information into the computer 1120 through input devices such as a keyboard 1140 and pointing device 1142. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 1121 through a serial port interface 1146 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A monitor 1147 or other type of display device is also connected to the system bus 1123 via an interface, such as a video adapter 1148. In addition to the monitor, computers can include or be connected to other peripheral devices (not shown), such as speakers and printers.
The computer 1120 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 1149. The remote computer 1149 may be another computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 1120, although only a memory storage device 1150 has been illustrated in
Computer 1120 includes a network interface 1153 to communicate with remote computer 1149 via network connection 1151. In a networked environment, program modules depicted relative to the computer 1120, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
In the foregoing description and in the accompanying drawings, specific terminology and drawing symbols are set forth to provide a thorough understanding of the present invention. In some instances, the terminology and symbols may imply specific details that are not required to practice the invention. For example, the wireless handheld devices discussed above are “smart phones” that support many services in addition to standard voice functions. Portable computing devices other than smart phones, such as tablet computers, e.g., an iPad manufactured by Apple, Inc. of Cupertino, Calif., and palm-top and lap-top computers, can be equipped as detailed herein to serve as wireless handheld devices. Moreover, some components or devices are shown directly connected to one another while others are shown connected via intermediate components, or wirelessly, e.g., Wi-Fi, Bluetooth, a public WAN, e.g., the Internet, or a cellular network. In each instance, the method of interconnection establishes some desired electrical or logical communication between two or more devices, as will be understood by those of skill in the art. More generally, the term “network” may refer to one or more networks of networks; in other words, one or more interconnected networks of various types such that a node, e.g., a client or server device, communicates via the network with another node. A network may include several types of networks, for example, private or public networks, local (LAN) and wide area (WAN) networks, wired, wireless, and cellular networks, and the Internet.
Communication Stream server 102, and email server 131, may be realized as one or more servers, the servers including one or more services shown within servers 102 and 137, e.g., services 107, 109, 111, 113, 115, 119, 121, 136, 137, and 138. Communication Stream server 102, and email server 131, may also be implemented as discrete servers that include one or more processors, memory, storage, and modules, self-contained within a server having discrete physical boundaries. In this embodiment, communications among the processor, memory, storage, and modules, occur internally. A discrete server may also be embodied virtually, e.g., via VMWARE, or VIRTUALBOX. Servers 102, and 137, may also be implemented in a distributed fashion, e.g., via a “hypervisor” implementation such as VMWARE, or as individual “cloud” services, in which processor, memory, and storage are not necessarily physically co-extensive. For example, processor 105 may be distributed across several physical processors communicating over a local area network. In such implementations, memory 103 may be physically separate from processor 105, and storage 129, and communicate over one or more network links. In one embodiment, a network link is potentially insecure. Some embodiments may therefore support secure links and data encryption for the communications into and out of Communication Stream server 102, and email server 131. The components of servers 102, and 131, may be distributed across local and wide-area networks, including the Internet, as will be readily understood by those of ordinary skill in the art.
Systems and methods for enhancing communication in email applications have been described. In the above description, for purposes of explanation, numerous specific details were set forth. It will be apparent, however, that the disclosed technologies can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form. For example, the disclosed technologies are described in some implementations with reference to user interfaces and particular hardware. Moreover, the technologies are disclosed above primarily in the context of communication applications; however, the disclosed technologies apply to other data sources and other data types (e.g., collections of other resources, images, audio, web pages, etc.).
Reference in the specification to “some implementations” or “an implementation” means that a particular feature, structure, or characteristic described in connection with the implementation is included in at least some implementations of the disclosed technologies. The appearances of the phrase “in some implementations” in various places in the specification are not necessarily all referring to the same implementation.
Some portions of the detailed descriptions above were presented in terms of processes and symbolic representations of operations on data bits within a computer memory. A process can generally be considered a self-consistent sequence of steps leading to a result. The steps may involve physical manipulations of physical quantities. These quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. These signals may be referred to as being in the form of bits, values, elements, symbols, characters, terms, numbers, or the like.
These and similar terms can be associated with the appropriate physical quantities and can be considered labels applied to these quantities. Unless specifically stated otherwise as apparent from the prior discussion, it is appreciated that throughout the description, discussions utilizing terms, for example, “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, may refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The disclosed technologies may also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may include a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, for example, any type of disk including floppy disks, optical disks, CD ROMs, and magnetic disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, flash memories including USB keys with non-volatile memory or any type of media suitable for storing electronic instructions, each coupled to a computer system bus.
The disclosed technologies can take the form of an entirely hardware implementation, an entirely software implementation or an implementation containing both hardware and software elements. In some implementations, the technology is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.
Furthermore, the disclosed technologies can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer-readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.
Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems, and Ethernet cards are just a few of the currently available types of network adapters.
Finally, the processes and displays presented herein may not be inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the disclosed technologies were not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the technologies as described herein.
The foregoing description of the implementations of the present techniques and technologies has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present techniques and technologies to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the present techniques and technologies be limited not by this detailed description. The present techniques and technologies may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Likewise, the particular naming and division of the modules, routines, features, attributes, methodologies, and other aspects are not mandatory or significant, and the mechanisms that implement the present techniques and technologies or its features may have different names, divisions, and/or formats. Furthermore, the modules, routines, features, attributes, methodologies, and other aspects of the present disclosure can be implemented as software, hardware, firmware, or any combination of the three. Also, wherever a component, an example of which is a module, is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of ordinary skill in the art of computer programming. Additionally, the present techniques and technologies are in no way limited to implementation in any specific programming language, or for any specific operating system or environment. Accordingly, the disclosure of the present techniques and technologies is intended to be illustrative, and not limiting.
Variations of these embodiments, and variations in usage of these embodiments, including separate or combined embodiments in which features are used separately or in any combination, will be obvious to those of ordinary skill in the art. Therefore, the spirit and scope of the appended claims should not be limited to the foregoing description. In U.S. applications, only those claims specifically reciting “means for” or “step for” should be construed in the manner required under 35 U.S.C. § 112(f).
The present application is a continuation of application Ser. No. 15/288,002, filed Oct. 7, 2016, which is a continuation of application Ser. No. 15/008,818, filed Jan. 28, 2016, which Claims Priority from Provisional Application No. 62/280,307, filed Jan. 19, 2016, is a Continuation-in-part of application Ser. No. 14/961,701, filed Dec. 7, 2015, is a Continuation-in-part of application Ser. No. 14/861,160, filed Sep. 22, 2015, Claims Priority from Provisional Application No. 62/181,960, filed Jun. 19, 2015, Claims Priority from Provisional Application No. 62/120,696, filed Feb. 2, 2015, Claims Priority from Provisional Application No. 62/111,037, filed Feb. 2, 2015, Claims Priority from Provisional Application No. 62/089,034, filed Dec. 8, 2014, and Claims Priority from Provisional Application No. 62/054,683, filed Sep. 24, 2014. All of the above applications are incorporated by reference herein.
| Number | Date | Country | |
|---|---|---|---|
| 62280307 | Jan 2016 | US | |
| 62181960 | Jun 2015 | US | |
| 62120696 | Feb 2015 | US | |
| 62111037 | Feb 2015 | US | |
| 62089034 | Dec 2014 | US | |
| 62054683 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15288002 | Oct 2016 | US |
| Child | 18085927 | US | |
| Parent | 15008818 | Jan 2016 | US |
| Child | 15288002 | US | |
| Parent | 14961701 | Dec 2015 | US |
| Child | 15008818 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14861160 | Sep 2015 | US |
| Child | 14961701 | US |
