Systems and methods are known for message display and management. Systems and methods are needed that support images and text and allow users to interface without a requirement for traditional keyboard access.
The preceding description is not to be construed as an admission that any of the description is prior art relative to the present invention.
In one aspect, the embodiments provide a message screen display. The message screen display comprises a static non-scrollable display area for display of at least part of a first message, the first message having an associated first message time. The message screen display further comprises a scrollable display area for display of at least part of a second message, the second message having an associated second message time. The message screen display further comprises a feature applied to at least part of the first message that varies based on time as referenced to the associated first message time.
In other aspects, the feature applied to at least part of the first message is a color. In other aspects the feature indicates whether the first message has been viewed. In other aspects, the feature applied to at least part of the first message is a border. In other aspects, the border feature is a color. In other aspects, the scrollable display area further comprises a time-ordered display area for display of a plurality of messages arranged according to a time associated with each of the plurality of messages. In other aspects, the second message is one of the plurality of messages. In other aspects, the time associated with each of the plurality of messages is before the time associated with the first message. In other aspects, the time associated with the second message is before the time associated with the first message. In other aspects, the associated first message time is a time of message receipt. In other aspects, the associated first message time is a time of message transmission.
In one aspect, the embodiments provide a message template on a message screen display. The message template comprises a message subject fly-out window that includes user configurable and user selectable message subject text templates, and a message recipient fly-out window that includes user configurable and user selectable message recipient text templates. The message template further comprises a message body fly-out window that includes user configurable and user selectable message body text templates and user configurable and user selectable message body graphic templates.
In one aspect, the embodiments provide a system and method for message display on a message screen display. The system and method comprise applying a feature to at least part of a second message that varies based on time as referenced to a time associated with the second message, and displaying at least part of the second message within a static non-scrollable display area. The system and method further comprise receiving a first message, and moving the second message from the static non-scrollable display area to a scrollable display area. The system and method further comprise applying a feature to at least part of the first message that varies based on time as referenced to a time associated with the first message, and displaying at least part of the first message within the static non-scrollable display area.
In other aspects, moving the second message from the static non-scrollable display area to the scrollable display area is responsive to receiving the first message. In other aspects, the system and method further comprise changing the feature applied to at least part of the first message. In other aspects, the system and method further comprise changing the feature applied to at least part of the second message.
The foregoing specific aspects are illustrative of those which can be achieved and are not intended to be exhaustive or limiting of the possible advantages that can be realized. Thus, the objects and advantages will be apparent from the description herein or can be learned from practicing the invention, both as embodied herein or as modified in view of any variations which may be apparent to those skilled in the art. Accordingly the present invention resides in the novel parts, constructions, arrangements, combinations and improvements herein shown and described.
The foregoing features and other aspects of the invention are explained in the following description taken in conjunction with the accompanying figures wherein:
It is understood that the drawings are for illustration only and are not limiting.
Electronic messaging systems and applications have been used for a number of years in many different industries and sectors. Some of those messaging applications rely entirely on text or graphics, and others use a mixture of text and graphics.
Today, the securities and finance industry makes extensive use of electronic messaging, and open outcry trading is one area in that industry where electronic messaging is particularly important. In open outcry trading, individuals gather in a common location to trade financial instruments, such as stocks, bonds, commodity contracts, option contracts, futures contracts, etc. There are a number of open outcry markets, and each generally specializes in particular types of instruments. Some of the most well known open outcry markets in the United States include NYSE, AMEX, CBOT, CME and CBOE.
In a simple example of an open outcry market, a customer order to buy or sell a particular financial instrument (e.g., shares of stock or commodity contracts) is sent to an individual located on the trading floor (e.g., a floor broker or floor trader). The broker or trader goes to a location on the trading floor (e.g., a post or pit) where other brokers or traders gather to trade that instrument and verbally announces terms of the order. If the order terms are acceptable, then another broker or trader in the crowd takes the opposite side of the order and completes the trade. In most open outcry markets floor brokers move freely around the trading floor, trading different instruments for different customers at different locations. Because the floor broker is not always at the same place, getting a customer order to the floor brokers in an open outcry market presents a challenge.
Today, many open outcry markets use wireless electronic communications to send customer orders to the floor brokers. However, before the development of wireless electronic communications, brokers in some markets (e.g., the NYSE) relied heavily on runners to physically take a slip of paper with the order details from a booth on the perimeter of the floor to the broker. At times, the floor broker wanted to tell customers about the market (e.g., market information) and relied on the same runners to take slips of paper with that market information back to the booth where it could be sent to the customers. The floor brokers developed a group of standardized and efficient ways to write and communicate market information on a slip of paper. Although many current electronic communication systems use keyboards for entry of text, in the trading industry, the legacy techniques continue even with electronic devices, and rely on hand-written information contained within images, often referred to as “ink.” This continued use of hand-written information is partly because the broker is standing and holds everything in her hands or pockets. To communicate with her booth on the edge of the trading floor, the broker can write or jot notes on a pad, a slip of paper, or a hand-held device. However, typing on a keyboard with two hands is almost impossible because there is nothing to support the device. The embodiments described have particular application in a trading environment, where at least one of the parties to the communication relies on handwriting or a touch-screen input to communicate, and graphics or images are an integral part of the communication.
An Example System
In
Although not illustrated in
Referring to
Referring to
If the user selects the Message Log button 312, they are presented with a Message Log window. An example Message Log window is illustrated in
There is an indicator 409 at the top of the Message Log to show whether all messages, sent messages, or received messages are being displayed. The example Message Log window in
On the Message Log window, any actions taken for the message are indicated in the action column 410. If there is a reply to the message, a left chevron is emphasized. If the message was forwarded, a right chevron is emphasized, and if the message was both forwarded and replied to, the both the right and left chevrons are emphasized. In the example a message that was received from A2 at 10:44:04 with a subject of PFE has the right chevron emphasized to indicate that the message was forwarded.
The time column 412 shows the time the message was either sent or received. The to/from column 414 shows the destination or origin of the message. The preview column 416 shows a thumbnail of the message. The type column 418 indicates whether the message was received or sent. The subject column 420 indicates the subject of the message, and the post/panel column 422 indicates the post and panel of the stock that is the subject of the message.
In addition, the Message Log window can include a side panel 424, which is opened or closed with a side panel button 426. If open, the side panel shows message details of the selected message. The message details include the subject, post and panel, and who the message is to and from, with associated times. If the message was sent and has been viewed, then the side panel also includes the time the message was viewed (e.g., VW @ 02:58). If the message includes graphics or an image, then a larger view of the graphic is provided, and if the message includes multiple pages, that is indicated at the bottom of the side panel. The user can page forward or backward through the pages using the left and right arrows.
On the Message Log window, the user has buttons to acknowledge a message 428, reply to a message 430, forward a message 432, and print a message 434. The user also has buttons to create a message 436, and select multiple messages 438.
The user can adjust the order of columns on the Message Log window by dragging them, and can adjust the width of each column. If one of the columns is adjusted to a minimum width it is identified by “ . . . ”. The user can view the full column title using a “tooltip” by pressing and holding the column in question. An example tooltip is illustrated at 3602 in
On the Message Log window, messages sent to a broker handheld device or to another agency that are unviewed are indicated by being highlighted in a particular color, such as yellow. Undelivered messages are highlighted with a different color, such as red.
The size of the Message Log window can be adjusted by dragging the lower right corner. There is also a button to minimize the display 446, or close the Message Log window 448.
By selecting a Create Message button (e.g., 314 in
By selecting the Message Ticker button (e.g., 316 in
In
Referring to
The user can also review all replied and forwarded messages associated with a message by using the action indicator buttons in the Message Log window (e.g., 450 in
As illustrated in
When a user presses a message reply button (e.g., 1006 in
When a user presses a message forward button (e.g., 1008 in
A user can forward multiple messages by tapping a select multiple button (e.g., 438 in
Tapping a configure button (e.g., 318 in
To edit an existing address, the user selects the address they want to view or edit and then the view/edit button (e.g., 1710 in
To delete an existing address, the user selects the address they want to delete and then the delete button (e.g., 1712 in
The user can also create and edit groups. To create a group, the user selects the group button 1806 in
To edit a group, the user selects the group button 1904 in
Similar to the way a user can add, edit and view addresses and groups, the user can also add, edit and view subjects, as illustrated in
The user can also use the Configuration List window to add, modify or delete messages, as illustrated in
The user can also configure auto routing using the Auto Routing configuration button 2902. This includes a rule status (active or not), the address, the rule name, the room, post, panel or stock covered, and the date and time of the last modification as well as the user who last modified the rule.
To insert a new rule, the user selects the create rule button (e.g., 2094 in
To configure alerts, the user selects the alerts button (e.g., 3102 in
To configure printing, the user selects the print button (e.g., 3202 in
The toolbar illustrated in
Example Methods
Referring to
At step 3704, system 100 displays message (A) in a non-scrollable area of the display. An example embodiment of such a non-scrollable area is illustrated at 808 in
At step 3706, system 100 begins a timer for the feature, or timers for the features, and at step 3708, system 100 adjusts the feature or features depending on the timer and possibly other factors.
At step 3710, system 100 determines whether a new message has been received, and if not, loops to step 3708.
If at step 3710, system 100 determines that a new message is received, then at step 3712, system 100 receives the new message (B) and applies a feature or features to at least part of message (B). In one example the feature is a colored background and/or colored border.
Then, at step 3714, system 100 displays message (A) in a scrollable area of the display. An example embodiment of such a scrollable area is illustrated at 806 in
At step 3718 system 100 begins a timer or timers for the feature or features of message (B), and at steps 3720 and 3722, system 100 adjusts the features of messages (B) and (A) respectively depending on the timers and possibly other factors.
Some of the steps for adjusting features in
At step 3804, system 100 determines whether the user has viewed the message, and if so, at step 3806 system 100 sets the message background to blue and the message border to blue.
If system 100 determines that the message has not been viewed, then at step 3808, system 100 determines whether the 10 second timer has expired. If the 10 second timer has not expired, system 100 loops to step 3804.
If the 10 second timer has expired, then at step 3810, system 100 sets the message background to light orange and the message border to bright orange.
Then at step 3812, system 100 determines whether the 30 second timer has expired. If the 30 second timer has not expired, system 100 loops to step 3804.
If the 30 second timer has expired, then at step 3814, system 100 sets the message background to blue and the message border to bright orange, and then loops to step 3804.
Although illustrative embodiments have been described herein in detail, it should be noted and will be appreciated by those skilled in the art that numerous variations may be made within the scope of this invention without departing from the principle of this invention and without sacrificing its chief advantages.
Unless otherwise specifically stated, the terms and expressions have been used herein as terms of description and not terms of limitation. There is no intention to use the terms or expressions to exclude any equivalents of features shown and described or portions thereof and this invention should be defined in accordance with the claims that follow.
Number | Name | Date | Kind |
---|---|---|---|
5267327 | Hirayama | Nov 1993 | A |
5715415 | Dazey et al. | Feb 1998 | A |
6727916 | Ballard | Apr 2004 | B1 |
6779178 | Lloyd | Aug 2004 | B1 |
7076730 | Baker | Jul 2006 | B1 |
8073895 | Hamzeh | Dec 2011 | B2 |
20030237043 | Novak et al. | Dec 2003 | A1 |
20040008222 | Hovatter | Jan 2004 | A1 |
20040117831 | Ellis | Jun 2004 | A1 |
20040181586 | Morreale | Sep 2004 | A1 |
20040220829 | Baharav | Nov 2004 | A1 |
20050132298 | Lueckhoff et al. | Jun 2005 | A1 |
20050213174 | Maki | Sep 2005 | A1 |
20060168509 | Boss et al. | Jul 2006 | A1 |
20060184886 | Chung et al. | Aug 2006 | A1 |
20060187477 | Maki et al. | Aug 2006 | A1 |
20060265453 | Kaminsky | Nov 2006 | A1 |
20070106729 | Adams et al. | May 2007 | A1 |
20070156886 | Srivastava | Jul 2007 | A1 |
20070227537 | Bemister | Oct 2007 | A1 |
20070250769 | Bass et al. | Oct 2007 | A1 |
20070250783 | Wu et al. | Oct 2007 | A1 |
20080064363 | Salafia | Mar 2008 | A1 |
20080109472 | Underwood | May 2008 | A1 |
20090265453 | Hirano | Oct 2009 | A1 |
20100115559 | Ellis | May 2010 | A1 |
20100261492 | Salafia | Oct 2010 | A1 |
Entry |
---|
Microsoft Outlook 2003 SP2, Part of Microsoft Office Professional Edition 2013, Copyright 1995-2003 Microsoft Corporation. |
Microsoft Office Outlook 2003 Basic Guide SP2, Part of Microsoft Office Professional Edition 2003, Copyright 1995-2003 Microsoft Corporation, pp. 1-31, Dec. 27, 2005. |
Market Access Subcommittee Interim Report, Nov. 27, 2001. |
Best Practices for Organized Electronic Markets, Apr. 24, 2002. |
A Taxonomy of Automated Trade Execution Systems, Ian Domowitz, Journal of International Money and Finance, (1993), 12, pp. 607-631. |
Number | Date | Country | |
---|---|---|---|
20150253983 A1 | Sep 2015 | US |
Number | Date | Country | |
---|---|---|---|
60675276 | Apr 2005 | US | |
60669485 | Apr 2005 | US | |
60669567 | Apr 2005 | US | |
60669568 | Apr 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11399938 | Apr 2006 | US |
Child | 14718714 | US |