Patent Application
20120317162
The present invention relates generally to computer hardware, mobile devices, televisions, and software. More specifically, it relates to managing and exchanging information shared by a defined group in a distributed network.
The sharing and management of information is becoming increasingly important in people's day-to-day lives. Individuals, whether they are members of a family, classmates, or co-workers, want to know more about what other individuals with whom they have a relationship or association are doing, where they are, what plans they are making, and so on. In many cases, people would like such notifications and information feeds to be non-intrusive and have a light touch or footprint to present being overwhelmed or constantly interrupted with such information.
Currently, information is shared among individuals using numerous communication channels, networks, and devices. The most significant trend in devices has been the proliferation of mobile devices, namely “smartphones” and tablet computing devices. These hand-held devices are what many people now use to get onto the Internet, play media, communicate, and run software (“apps” or software applications that execute on mobile devices and TVs), play media, and communicate. The use of these mobile devices is converging with other widely used devices, such as desktop and laptop computers, TVs, GPS devices, e-book readers, and the like. Out of all these devices, the TV is currently going through some major changes in how users interact with them. They are now used for more than simply watching network and cable TV content or DVDs. They are being used to run apps, get online, display photos and videos, and display content different from traditional broadcast media (e.g., TV shows, movies, or music). They are now being used to display personalized content. As such, it is increasingly being used with or integrated with other devices, especially with smart phones and tablet computers.
This convergence of mobile devices, TVs, and other components has given rise to opportunities for sharing and managing group-related information in ways that were previously impractical or technologically infeasible. Generally, it would be desirable for a group of registered users, utilizing various devices—some mobile and other traditionally stationary—to be able to exchange information and communicate in ways that are not intrusive and that integrate well with existing devices. It would be desirable to leverage existing devices, such as TVs, that are conventionally used for displaying content and expand their use to display group-related information to users, again, in an unobtrusive and well-integrated way.
The present invention provides a service for sharing, managing, and storing group-related information using existing technology relating to mobile devices, TVs, server computers, and distributed networks. Users in a defined group, such a family or a group of co-workers, can use devices, such as smart phones or tablets, to get updates from other users or to send information about themselves. The information can be displayed on authorized devices, some of which are generally used to display information, such as TVs.
One aspect of the present invention is a method of managing group information stored on a central server. A header of a communication received from a device is examined at a central server. It is then determined whether the type of the communication is a broadcast message, an event message, a query message, or an update message. The communication is stored in a database on the central server if the communication is a broadcast message or an event message. If the communication is a query message, the central sever responds to the message. If it is an update message, the database in the central server is updated. The group information is displayed in real-time on one or more devices and is combined in one place.
Another aspect of the present invention is a method of managing group information on a device. A header of a communication received from a server is examined. It is then determined whether the type of the communication is a broadcast message or a response to a query, the response being sent by the central server or hub. A query response may be a calendaring event, location information, or a bulletin board item. The communication is then stored in the device database. In one embodiment, it may be determined that the user of the device is making an update to the group information. This update to the group information is stored in a local database and is transmitted to the server.
Another aspect of the present invention is a system for facilitating group information communication and management. The system includes a central server or hub having a database and a group information server or hub application set, wherein combined group information is stored in the database. It also includes one or more devices, where the devices display a group-information in various formats, such as a group information ticker on a TV and has a group information client application set. The system enables interactions among group members are simplified and integrated.
The invention and the advantages thereof may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:
In the drawings, like reference numerals are sometimes used to designate like structural elements. It should also be appreciated that the depictions in the figures are diagrammatic and not to scale.
Methods and systems for sharing, managing, and storing information related to a group of individuals are described in the various figures. The invention enables these individuals (“users”) and their devices, to send messages, receive messages and updates, such as calendar or scheduling changes, provide location information, status, and the like, to other users, through a central server or hub. These communications may be displayed in various formats on a device that is predominantly used for display, such as a TV or a digital photo frame or on other devices, such as smartphones or tablets. The marketplace has many Internet-based services that offer messaging, calendar services, e-mail, chat, and other features to groups and businesses. The present invention combines key information relevant to a close group, such as a family, and integrates a set of features for that group. The group-information ticker is an example such a feature. The ticker, one embodiment of a broader concept is akin to an emergency alert that can be found on many TVs, but is applied to and displays group-related information. Details are provided in the description below.
In any of these existing and future server technology implementations, server 102, whether in the cloud, in a living room, or even on a mobile device, functions as a central hub for the group-related information. It has a network-accessible database which is used as a central repository for data relevant to the group. As described below, central server or hub 102 executes applications related to the present invention and stores group-related information in addition to performing other server-related activities and storing various other types of data. It may also be noted that central hub 102 may have multiple APIs for implementing different physical transport or message passing infrastructures, allowing it to communicate with various types of devices. Central hub 102 is described in greater detail in
Hub 102 is able to communicate with at least one device, such as device 104a, and will typically communicates with two or more devices, shown as devices 104a to 104g. The lines between devices 104a-g and hub 102 indicate bi-directional communication which can be wired or wireless (there may also be communication channels directly between certain devices, but they are not relevant to the present invention). The devices primarily fall in the category of consumer electronic devices that are capable of Internet connectivity and can run applications. They include mobile phones, including smartphones (sometimes called “app phones”), TVs, tablet computing devices, digital picture frames, mobile gaming devices, e-book readers, IP-enabled media players, such as MP3 players, navigational devices, desktop, laptop, or netbook PCs, large-surface computing devices, IP-enabled digital cameras and camcorders, among others devices.
The present invention utilizes existing and emerging capabilities available in these and other electronic devices. For example, presently mobile phones have location information, WAN access, Web browsers, and app execution capabilities. An increasing number of TVs have the ability to run apps, receive notifications, display Web content, and accept user input, for example, via a keyboard, a mobile device, or a remote control. Other devices (provided as examples above) have some or all of these capabilities. Some may have calendaring functions, mapping information, presence information, real-time notification ability, and a display. As is known in the art, these functions, or building blocks, are used in numerous electronic devices and services.
It may also be noted that the number of applications needed for implementing the present invention on devices 104a-g may vary depending on what type of device is running the invention. It may also be noted that the devices are not technically divided into categories or classes. From a technical standpoint, the devices are treated the same and their functionality will depend on their hardware specifications and software/firmware capabilities. However, some devices will generally be suitable for displaying as well as transmitting information, such as a PC, a tablet computing device, or a smartphone. These may be seen as both producers and consumers of information. Others may be more adaptable or suitable for displaying information (information consumers), such as TVs and digital photo frames, and may not be used as often for producing information. That is, users, for example, may not be accustomed to entering or typing in information onto a touch screen of a digital photo frame or using a keyboard for a TV (although this is a trend that may change as TVs become more advanced). Some devices may be predominantly information producers, such as navigational (GPS) devices and more conventional (previous generation) cell phones, which may be used mostly for providing (producing) location information of its user to other users in the group network.
The capabilities of the various devices and the functionality of hub 102 enable a convergence or integration of, for example, mobile devices, TVs, and tablet PCs (to name a few of the more the more widely-used devices) over the Internet. These capabilities and functionality allow users, who may be traveling with their smartphones or at home watching TV, to exchange and display information relevant to a close group of user in a manner that is not intrusive and does not require activity awareness on every device, such as on the TV. That is, the TV or other device does not have to explicitly participate in the activity. The information is collected and interwoven into the network and displayed where it needs to be. The user does not have to tell the device how to execute or what to do next.
As noted,
One aspect of the family ticker concept is that the mobile phone does not have to be the only device that users can use to get information. The information provided is richer, more timely, and informative than notifications that simply appear in a scroll at the bottom of the TV screen or any other display. In other embodiments, there may be a notification icon or symbol on the screen that there is information that the TV viewer may want to see. Ticker 208 is displayed on the TV screen regardless of what content is being shown on TV 206 or where the content is coming from (e.g., cable, satellite, DVD player, PC, camcorder and the like). The ticker information is always made available to TV 206 from calendar 204 as long as the TV is powered on. Calendar 204 is only one example of a source of family information that can be displayed on TV 206. As described below, various types of information and updates from family hub server 102 may be shown on TV 206 in the form of a scroll or ticker 208. Ticker 208 is one example of a light-touch or minimally intrusive interaction that characterizes the viewing experience when displaying family hub information. By having a scroll or ticker, for example, the viewer's experience of watching TV is kept intact; the intrusion is minimal yet the family hub information conveyed is rich, timely, and relevant. Family ticker 208 is one example of how group information can be displayed to users in a manner that is integrated with the TV viewing experience. If a user wants more in-depth information, she can obtain such information from the family hub database by interacting further with the family hub. What is shown in ticker 208 is an initial display of information and more detailed and related information may be obtained by interacting with TV 206 using any suitable means, such as a keyboard or remote control.
If the communication is determined to be a broadcast message from a registered device in the network, control goes to step 306 where the message is stored in a central hub database. The database, for example, a relational database, may have one or more tables used specifically for storing messages from devices. At step 308 the central hub transmits or broadcasts the same message that it received to other authorized devices in the network. Which devices are authorized to receive the particular message is determined by settings and filters. The server can be configured, using such settings and filters, to selectively send broadcast information. This allows certain devices to send and view information, but keep their users from being overly interrupted with broadcast messages, many of which may not of high relevance or interest to all users. This may be described as a centrally-administered device model.
[Broadcasting msg selection, p. 7 process for selective broadcasting] A process of selective broadcast (or how central hub transmissions are decided) begins with the central hub server receiving a broadcast message that is to be sent to all devices. The server may then load a list of devices on its network (e.g., network 100 in
Returning to step 304, if the central hub determines that the communication is an event/item, control goes to step 310 where the central hub stores the event or item. Examples include a calendaring (scheduling) event, a user or device location update, or a “bulletin board” (“BB”) item, such as a task, assignment, or chore. A location update may be in response to a “server notice,” explained below. Other types of events and items may also be implemented.
If the communication is determined to be a message query from a device at step 304, control goes to step 312. The message query may be related to location, calendaring, or bulletin board messages of another device. For example, a query may comprise requesting the location of another user in the network, such as a parent requesting the location of a child or wanting to know when a certain event (e.g., a birthday party) is taking place. At step 312 the server responds to the query with a location, calendaring information, or a bulletin board message. The server retrieves the data needed for responding to the query from the database using techniques known in the art.
Returning to step 304 for the fourth option, if the server determines that the communication received from a device is a message update relating to location, calendaring, or the bulletin board, at step 314 the update or change relating to one of these items is made to the specific entry in the database.
With respect to the operations described in
An important aspect of the present invention is the device to server connection and communication. A device will generally connect to a server using secure communication means, such as SSL. The user of the device provides login information and a password and the server verifies this information by checking for an account and validating the password. If valid the device is authorized for communication with the server. The device may disconnect from the server and in the case of mobile devices using cellular networks, the device can still receive server notices using the network. When they are connected, they can use the cellular network or TCP/IP connections.
On the subject of device authentication, as mentioned above, note that devices may or may not be authenticated. This is an implementation decision. One possible implementation is using out of band signaling to verify ownership, such as sending a text message or e-mail to a registered user. There are various ways to implement device authentication. Similarly, users may or may not be authenticated. For example, a user may be authorized by a moderator, a password or passcode may be used, or an e-mail invitation may be sent to the registered account holder. Once authenticated, a user can access the system with the username and passcode.
With respect to user authentication, an example using the family hub embodiment may be helpful. A family hub server is configured to accept or allow registration applications, which are used by individual family members (or non-family members) to apply to be in the family or network. Server registrations can be allowed or disallowed. A user accesses the family hub Web site and registers using a top-level system name. The user may then create a username and passcode and enter account information. The request may then be logged and awaiting approval by an administrator (e.g., a parent). An administrator authorizes the account and then the account is marked active and the user is activated. This process may be favored, for example, by Internet service providers.
In another embodiment, the family hub server has an “activation code” set by an administrator. The user is given the code, for example, in the form of a card from a cellular network carrier. The user may then go to the family hub Web site and register using the activation code. The user then creates a username, passcode and enters account information, after which the user is activated. The process may be favored by cellular network carriers.
If at step 501 the device receives a message (MSG), control goes to step 504. At step 504 the device examines the content of the message, for example, the header or other component of the message, to determine the communication type. This may be done, for example, by a family hub application running on the device. Depending on the communication type, in one embodiment, one of three operations may occur as indicated by the three arrows from step 504.
If the communication is a message update, the message is stored on a local database on the device at step 506. One requirement of a device, besides being able to run apps, is that it has data storage or memory. The message is pushed to the device from the server (which follows policies and settings with respect to which devices receive the message update) and may reflect an update on the overall state of the system. The message update may be a server notice. The device may be configured to enable or disable the ability to receive broadcast messages from the server. In one embodiment, this may only be done using an administrative setting on the server. This may prevent, for example, a child from disabling her mobile device from receiving such messages. In another embodiment, the user of a device can also enable or disable broadcast messages while they are using the device. It is also possible to have both these capabilities.
At step 507 the update is displayed to the user. As noted, this may be done in one of a number of ways depending on the device. If it is a TV, it may be displayed using a ticker at the bottom of the screen. If it is a tablet computer, it may be displayed using a notification (similar to a text message or e-mail message notification).
If the communication is a response from the server to a query made by the device, control goes to step 508. This is a continuation of the process described at step 312 of
If the communication is the result of the user of the device adding an event, message, or item to the system, control goes to step 510. This may happen if the user types in a message, enters something on the calendar, or moves to another location (in which case the location item may be added automatically to the device). For example, if a user moves from a school to a friend's house, this location information will be added to the device database automatically and eventually forwarded to the server, as described in step 512. The event, message, or item is stored in a local database on the device at step 510. At step 512 the event/message/item is transmitted to the server. In one embodiment, these communications may be queued on the device for transmission to the server at a later time (a ‘store-and-forward’ implementation). The content of an event may vary from something very basic to a detailed communication. For example, it may contain pictures, video, music, and the like. However, in one embodiment, only a portion of the event (depending on how much data is used to convey the event) may be transmitted to the server. After steps 502, 507, 508, and 512, the processes are done and control goes back to step 501 where the device waits for a response or communication from the central hub.
As noted above, many mobile devices have built-in location determination capabilities. They know where they are with varying degrees of specificity. Location information can also be entered manually by a user. A location transmission policy may be included in the application set for implementing the present invention (e.g., family hub application set). This location transmission policy may be changed by a designated administrator, such as a parent in the family hub environment. This administrator may be one, multiple, or all users of the network.
In one embodiment, a family hub calendar may accept calendar invitations and notifications from other calendar systems. This facilitates the incorporation of events from other sources into the family hub network. The family hub may leverage existing calendaring technology, however, in one embodiment, the feature or application set of the present invention may focus on calendaring display and access. Family hub members may use other applications for managing their personal and work calendars. Events from personal and work calendars may be easily integrated with the family hub.
Another feature of the family hub network is the family map. Many family members use location capabilities that presently exist on many mobile phones. There are numerous existing services that use location information from the phone to facilitate searching and other applications. There are services that offer a feature that shows the location of friends on a map. The family hub performs a similar function for family members. The Family Hub map display may show the name of each family member on a map. Additional location tags can be added to the map so that important locations can be displayed along with the location of the family members. Examples are school, dad's work, mom's work, pool, friend's house, and the like. This makes it easy to see when family members are at known locations.
A family hub mobile application provides mobile access to the same information that is shown on an in-home device, such as a TV or a digital picture frame. The mobile application set may also activate the location reporting feature, so a family member's location is displayed to other family members. In one embodiment, the mobile version also includes a version of the family ticker, but the text messaging feature of the phone may be utilized for real-time updates.
An example of how the family hub network may be used to send a broadcast message is helpful in understanding the present invention. This example is provided simply for illustration and is not intended to limit the invention or any embodiments to the family environment or to solely sending broadcast messages. In this example, a system configuration may be comprised of the following:
One (1) Family Hub Server—Svr1
Family Hub server is active at all times
Two (2) Family hub mobile devices—Dev1, Dev2 (devices are active in this example)
Family Hub mobile device automatically share LOC information on periodic basis.
Family Hub broadcast messages “pop up” when received on the mobile device.
Family Hub mobile application is active only when the user activates it.
One (1) Family Hub TV—TV1
Family Hub TV1 is active only when powered on, and in use.
Family Hub TV1 is active in this example, and User3 is watching TV1.
Three (3) Family Hub users: User1, User2, User3.
A use case may be as follows. User1 of Dev1 activates the Family Hub application on her mobile phone (Dev1). The same user touches/activates the “send message” option of the family hub application. The family hub application then displays a dialog box on Dev1 that allows User1 to type a message. User1 types a message “Going to Sara's house after school” and presses the “send” button on the family hub mobile application. The family hub mobile application on Dev1 stores the message locally and transmits the message to Svr1. Svr1 acknowledges receipt of the message from Dev1 and stores the message in the Svr1 database. Svr1 then transmits the message “Going to Sara's house after school” to Dev2 and TV1. User2 receives a beep tone and “pop up” message on his mobile phone showing the username/friendly name of User1. The message “Going to Sara's house after school” is sent to User3 who sees a ticker or scrolling banner message on TV1 showing the username/friendly name of User1, and the message “Going to Sara's house after school” in the ticker.
In one embodiment, a user can program a setting such that only text messages are sent as an alternative delivery system. In another embodiment, the system may support communication between devices. For example, a user 1 may send a message from device 1 to a server, where the message is tagged for a user 2. User 2 connects to the server and queries for messages tagged for user 2. The server may respond with messages tagged for user 2.
Processor 922 is also coupled to a variety of input/output devices such as display 904 and network interface 940. In general, an input/output device may be any of: video displays, keyboards, microphones, touch-sensitive displays, tablets, styluses, voice or handwriting recognizers, biometrics readers, or other devices. Processor 922 optionally may be coupled to another computer or telecommunications network using network interface 940. With such a network interface, it is contemplated that the CPU might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Furthermore, method embodiments of the present invention may execute solely upon processor 922 or may execute over a network such as the Internet in conjunction with a remote processor that shares a portion of the processing.
In addition, embodiments of the present invention further relate to computer storage products with a computer-readable medium that have computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and holographic devices; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs) and ROM and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter.
Although illustrative embodiments and applications of this invention are shown and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those of ordinary skill in the art after perusal of this application. Accordingly, the embodiments described are illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
