System and Method for Displaying and Notifying Collective Events for a Group

A system and method for displaying collective events for a group is disclosed herein. One method comprises receiving, by a reminder device, a plurality of events from a server. Each of the events can be from a user within a group, and the events can be addressed to the reminder device. The method can also comprise the step of displaying the events in a blog on a screen on the reminder device. The reminder device can be displayable in a location accessible by the group.

BACKGROUND

This disclosure relates to an improved system and method for displaying and notifying collective events for a group

Methods for reminding and notifying individual or family members about special occasions, to-do's, and other important activities, have evolved over the years. A popular method of leaving sticky notes or marking calendars is one of the oldest practices that are still being used today. This method can be effective however it can also be tedious most especially for events and activities that are usually repeated such as birthdays, anniversaries, or grocery shopping. Moreover, such method can require an additional task of organizing the scheduled events at a particular order.

Thus, reminder applications and devices have been developed to be used for this purpose. The method employed by reminder devices and application are usually focused on one individual or the user. As such, only the user would be reminded of a particular task or event. Therefore, having a single device that can remotely receive reminders from a specific group of individual can be an effective reminder tool. As such, any member of a group can send a notification to the device and other group members or individuals who have an access to the device can perform the task or to-do accordingly. Moreover, most reminder applications or devices usually remind user through text-message form. A reminder can be more effective when other medium such as photo, video, and audio file can be used to notify a group or individuals of a certain event or activities.

Furthermore, most reminder devices only functions as a notification tool. Therefore, having a reminder device that can collect and store important memories, thoughts, and events can be a great addition to the function of a reminder device. As such, collection of texts, images, videos, and audio files that can capture important memories or events, can be stored and be revived at any time. As such it would be useful to have an improved system and method for displaying and notifying collective events for a group.

SUMMARY

A system and method for displaying collective events for a group is disclosed herein. One method comprises receiving, by a reminder device, a plurality of events from a server. Each of the events can be from a user within a group, and the events can be addressed to the reminder device. The method can also comprise the step of displaying the events in a blog on a screen on the reminder device. The reminder device can be displayable in a location accessible by the group.

A reminder device can comprise a screen, a processor, and a memory. The memory can comprise a memory that stores an application. The application can be programmed to receive a plurality of events from a server, each of the events from a user within a group. The events can be addressed to the reminder device. The application can also be programmed to display the events in a blog on the screen on the reminder device. The reminder device can be displayable in a location accessible by the group.

DETAILED DESCRIPTION

FIG. 1illustrates a communication network comprising one or more reminder device101and/or electronic device102, one or more (first) server104and/or (second) server105connected via a network103. Reminder device101is electronic equipment programmed essentially for the function of sending, receiving and collecting notification from a user or group of users in a public environment. Moreover, reminder device101can be used to create and store collection of events. Reminder device101can also receive, and store data information from electronic device102through network103. As such, one or more electronic device102can send data information to reminder device101. Electronic device102can include, but is not limited to, a mobile phone, a laptop, a personal digital assistant (PDA), and/or a tablet. In one embodiment, reminder device101can use mobile phone tracking technology that uses radio signals between several radio towers, and/or Global Positioning System (GPS) to determine current time and location of the reminder device101or the electronic device102.

Server104can provide and perform computational tasks across network103. Server104can send and receive data to reminder device101and electronic device102. Network103can be a wide area network (WAN), or a combination of local area network (LAN), and/or piconets. Network103can be hard-wired, wireless, or a combination of both. A LAN can be a network within a single business while WAN can be an Internet.

FIG. 2Aillustrates an embodiment of reminder device101. Reminder device101can comprise a screen201. Input devices can include keypad, buttons, track balls, joysticks, or scroll wheels. Keypad can comprise a plurality of physical buttons comprising alphanumeric characters and/or symbols. However, in an embodiment where screen201is a touch screen, keypad can be represented virtually on screen201. Keypad can be used to add an input data202in reminder device101. In an embodiment wherein reminder device101can be a touch screen, text, pictures, audio and/or videos can be buttons that, upon being pressed, capture such pressing as input data202from screen201.

In one embodiment, reminder device101can also include an optical device203. Optical device203can be a small camera allowing the capture and the storing of still photographs and/or videos. Optical device203can capture still and/or moving images as input data202. As such, reminder device101can create input data202from optical device203, and store it into reminder device101.

An indicator204can be utilized to light up or blink to indicate a notification message, a reminder, and an event entry is received. Indicator can be an LED or any other physical, indicating device. Concurrently, a sound notification alert can also play as indicator204flickers. In one embodiment, audio file can be a defined alert sound stored in reminder device101. In another embodiment, audio file can be input data202recorded, and sent from reminder device101and or electronic device102.

FIG. 2Billustrates internal hardware of a reminder device101comprising a device processor205, a device memory206, and a GPS receiver207. Input data202from screen201of electronic device102can be sent to device processor205. Captured data or inputted data of from screen201, optical device203, keypad, and/or receiver-transmitter captured from reminder device101and electronic device102can be sent to a device processor205. In an embodiment wherein reminder device101can be used, captured data can include still photographs, video files, and audio files. Device processor205can be a device that executes programs stored in device memory206. Device memory206can be a physical device used to store programs and/or data. Processes can include storing input data202to device memory206, verifying input data202is valid and conforms to preset standards, or ensuring all required data. Input data202created from reminder device101and electronic device102can be displayed on screen201of reminder device101. GPS receiver207determines location of reminder device101using methods commonly known in the art.

FIG. 2Cillustrates device memory206comprising a device application208and device data storage209. Device application208can reside and perform logical functions within device memory206. Device data storage209can be a component in device memory206that can be used to retain digital data. Further, device processor205can perform processes on the data according to a device application208stored in device memory206. Processes can include storing input data202in device data storage209.

FIG. 3illustrates a schematic diagram of server104according to an embodiment of the present disclosure. Server104can comprise a server processor301, and a first local interface303. First local interface303can be a program that controls a display for the user, which can allow user to view and/or interact with server104. Server104can be a processing unit that performs a set of instructions stored within server memory302. Server memory302can comprise a server application304, and a server data store305. Server application304can be a program providing logic for server104. Server data store305can be collections of data accessible through server application304. Further, server application304can perform functions such as adding, transferring, and retrieving information on server data store305using first local interface303.

Server104includes at least one processor circuit, for example, having server processor301and server memory302, both of which are coupled to first local interface303. To this end, the server104can comprise, for example, at least one server, computer or like device. First local interface303can comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated.

Both data and several components that are executable by server processor301are stored in server memory302. In particular, server application304and, potentially, other applications are stored in the server memory302and executable by server processor301. Also, server data store305and other data can be stored in server memory302. In addition, an operating system can be stored in server memory302and executable by server processor301.

Other applications can be stored in server memory302and executable by server processor301. Where any component discussed herein is implemented in the form of software, any one of a number of programming languages can be employed such as, for example, C, C++, C#, Objective C, Java, Java Script, Perl, PHP, Visual Basic, Python, Ruby, Delphi, Flash, or other programming languages.

A number of software components can be stored in server memory302and can be executable by server processor301. In this respect, the term “executable” can mean a program file that is in a form that can ultimately be run by server processor301. Examples of executable programs can include a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of server memory302and run by server processor301, source code that can be expressed in proper format such as object code that is capable of being loaded into a random access portion of server memory302and executed by server processor301, or source code that can be interpreted by another executable program to generate instructions in a random access portion of server memory302to be executed by server processor301, etc. An executable program can be stored in any portion or component of server memory302including, for example, random access memory (RAM), read-only memory (ROM), hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (CD) or digital versatile disc (DVD), floppy disk, magnetic tape, or other memory components.

FIG. 4Aillustrates a server data store305comprising one or more device profiles401and one or more events402. In one embodiment, each reminder device101can be related to a unique key such as a serial number. As such, each of device profiles401, comprising the unique key, can be a retrievable unique account related to reminder device101. Events402can be content information such as text messages, images, and audio files that can be received by reminder device101through network103. In an embodiment, wherein events402can be created through reminder device101, content information can include video files. In one embodiment, device profiles401and events402can be stored in server104. In another embodiment, device profile401and events402can be stored locally or within reminder device101.

FIG. 4Billustrates device profile401comprising device information403, and a condition404. Device information403can comprise information on reminder device101and a device owner such as a name, username, password, email address, contact information, members, and a unique key403a. While creating a device profile401, the reminder device101can provide device information403. In one scenario, users other than the device owner can be authorized to create and send event402to reminder device101. In such embodiment, the device owner can add a user as member. The device owner can set up a username and password for each member. As such, an invitation email can be sent to each of the members. The invitation email can contain information that include but are not limited to username, password, and unique key403a. Therefore, the device owner and his member can share the same unique key403a.

To access server application304, the device owner or authorized members can provide account information403, such as a username, password, and/or unique key403a. Correct username, password, and unique key403acan be provided by authorized user to access server application304.

Condition404can be the local time zone applied on reminder device101. As such, GPS receiver207can determine the correct time zone for each reminder device101. Thus, condition404can be populated and updated with date, time, and location every time reminder device101connects with server104.

FIG. 4Cillustrates events402. Events402can be the created tasks, notifications, event entry, and/or reminders from authorized users of reminder device101. Events402can contain text, images, audio, and video files. In one embodiment, events402can be a notification message or a reminder. In another embodiment, events402can be an event entry, wherein any individual from the group can create, post, and store text, images, audio, and video recordings to reminder device101. Moreover, event entry can comprise a blog that can consist of posts containing a personal encounter, opinions, views, and any collection of information. A blog can be used as a personal diary of an individual. As such, reminder device101can be used to collectively store memories, personal views, and special events of a group in a single device.

Each event402can comprise an event message406, and event details407. Event message406can comprise of text, photo, audio, and/or video file. Event details407can be the parameters set for each event402. Event details407can include, but are not limited to, information such as notify flag, date and time of event, date and time of creation, location, and recurrence. In one embodiment, a notify flag can distinguish event402as a notification event or as an event entry. Therefore, when event402is set to notify, event402can comprise a reminder that can be triggered when date and time of event, and/or location of event details407matches condition404. When event402is not flagged to notify then event402can indicate that event402can be an event entry. As such, event message406can be retrieved and displayed on reminder device101according to the date and time of creation. Thus, when event entry's date and time of creation matches with date and time of condition404, a notification for a new event entry can be displayed on reminder device101. As an example scenario, event message406can have a different date and time of event and date and time of creation. Thus in a case wherein event402is an event entry, date and time of event can be used as a reference to the date and time wherein event402can be associated. Therefore the date and time of event of an event entry can be the order wherein events402are arranged to display on reminder device101.

Further, authorized users can set a specific date and time when a created event402can display or retrieve event message406, in one embodiment. In another embodiment wherein event402is flagged to notify, notification can be location based. In such embodiment, event message406can be displayed when reminder device101is at a certain location. Further in another embodiment, notifications can be triggered based on date, time, and location. In such embodiment, all parameters must be met or supplied for notifications to be triggered. Further, event402can be set to recur. As such, event message406can be displayed repeatedly according to a specified recurrence such as daily, weekly, or yearly. Since device information403can be required when accessing server application304, only authorized users can create events402. Therefore, as a user accesses server application304, server application304can associate each events402created with event details407. This can ensure that each event402created by any user is associated to the correct reminder device101.

For the purpose of this disclosure, date, time, and location discussed herein can be stored within a memory based on Greenwich Meridian Time (GMT). Greenwich Meridian Time (GMT) is the basis of every time zone in the world. Thus, ensuring that events402can be triggered at the correct date and time, regardless of the time zones in which events402are created.

FIG. 5illustrates screen201of electronic device102displaying create a reminder page500. In this embodiment, each reminder created can be associated with each event402. Reminder page500can comprise details such as, a device name501, a sender502, an event time503, an event title504, and an event body505. Device name501can be a name set by an owner of device reminder101. Device name501can be a family name, a group name, or any name that can identify a specific reminder device101. Furthermore, device name501can be associated with device information403. Sender502can be the name of an authorized member or user of reminder device101. Sender502can be associated with text or image file that can easily identify a member of reminder device101. Event time503can be the date wherein event has or can take place. In an embodiment wherein event402can be a notification message, event time503can be the date and time of event. As such, event time503can be set to alert or notify on reminder device101once event time503matches the date and time of condition404. In another embodiment, wherein event402can be an event entry, event time503can be used to indicate the date of an occasion, event, or memories. As such, event402can be stored, arranged, and retrieved according to the date and time set on event time503. Therefore in this embodiment, event time503can be equivalent to date and time of event of event details407. Event title504and event body505can be stored as event message406. Event title504can be a brief description of an event entry or notification created. Event body505can comprise a complete description and information of an event. Event body505can comprise of texts, images, and/or audio files. Once, a user is done filling up required information on reminder page500, event402can be created, sent, and stored in server memory302.

FIG. 6illustrates screen201of reminder device101displaying a created event402, as an event notification page600. After event402is stored in server memory302, reminder device101can communicate with server104through network103. Events402associated with reminder device101can be retrieved and stored within device memory206. Thus, when local date and time of reminder device101matches with the date and time of event details407, reminder device101triggers a notification page600that can display event402. Notification page600can display information such as sender502, event time503, event title504, and event body505. In one embodiment, when notification page600is displayed, main page of reminder device101can be disabled at the background.

FIG. 7illustrates screen201of reminder device101displaying a main page700. Closing notification page600can display main page700of reminder device101. Main page700can comprise a first section701and a second section702. In one embodiment, either section can be a blog format. In an embodiment wherein events402can be a notification message, event402can be displayed as thumbnails under first section701. In another embodiment wherein events402can be an event entry, events402can be displayed under second section702. In these embodiments, events402can be collectively displayed at first section701and second section702according to the date and time of event. Events can be a past or future event.

FIG. 8illustrates an exemplary method for displaying an event on a reminder device101. A reminder device101can query a memory for one or more events402. In one embodiment, events402can be stored in a device memory206of reminder device101. As such, reminder device101can query events402locally and does not need to connect via network103to retrieve events402from a server104. In another embodiment, events402can be queried by reminder device101from a server memory302through network103. As such, events402can be created through electronic device102and transferred to server104through network103. Each of said events402can be associated with a unique key403a. Further, unique key403acan be related to reminder device101. As such, events402associated with unique key403acan be filtered and stored within device memory206of reminder device101that matches unique key403a.

During the creation of a reminder or an event, events402can be flagged as a notification message or an event entry. As such, events402can be associated to one or more parameters of event details407. Flags of events402can also be related to a position on screen201of reminder device101. Events402that can be flagged as a notification message can be placed on a first section701of screen201. Furthermore, events402flagged as an event entry can be placed on a second section702of screen201. Moreover events402placed on first section701and second section702can be both arranged according to the date and time of event parameter of event details407. In an embodiment wherein event402can be a notification message, when condition404matches date and time of event, and/or location parameters of event details407, event message406can be displayed as a notification reminder. Further when event402can be an event entry, a notification can be triggered on reminder device101once condition404matches date and time of creation parameter of event details407. As such event message406can be displayed on reminder device101and any member of the group can be informed that a new event entry is received. In these embodiments, when notification is received on reminder device101the display of event message406can also trigger a sound notification alert or a blinking Indicator204. Moreover in these embodiments, event message406displayed on reminder device101can be in text, photo, video, or audio in form.

FIG. 9illustrates a second embodiment of a preferred method. One method comprises receiving, by reminder device101, a plurality of events402from server104. Each of events402can be from a user within a group, and events402can be addressed to reminder device. The method can also comprise the step of displaying events402in a blog on a screen on reminder device101. Reminder device101can be displayable in a location accessible by the group.

Also, server processor301can represent multiple server processors301. Likewise, server memory302can represent multiple server memories302that operate in parallel processing circuits, respectively. In such a case, first local interface303can be an appropriate network, including network103that facilitates communication between any two of the multiple server processors301, between any server processor301and any of the server memory302, or between any two of the server memory302, etc. First local interface303can comprise additional systems designed to coordinate this communication, including, but not limited to, performing load balancing. Server processor301can be of electrical or of some other available construction.

Although server application304, and other various systems described herein can be embodied in software or code executed by general purpose hardware discussed above, server application304can also be embodied in dedicated hardware or a combination of software/general purpose hardware and dedicated hardware. If embodied in dedicated hardware, each server application304can be implemented as a circuit or state machine that employs a number of technologies. These technologies can include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits having appropriate logic gates, or other components, etc. Such technologies are generally well known by those skilled in the art and, consequently, are not described in detail herein.

The flowchart ofFIG. 8shows the functionality and operation of an implementation of portions of server application304. If embodied in software, each block can represent a module, segment, or portion of code that comprises program instructions to implement the specified logical function(s). The program instructions can be embodied in the form of source code that comprises human-readable statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as server processor301in a computer system or other system. The machine code can be converted from the source code, etc. If embodied in hardware, each block can represent a circuit or a number of interconnected circuits to implement the specified logical function(s).

Also, any logic or application described herein that comprises software or code, including server application304, can be embodied in any computer-readable storage medium for use by or in connection with an instruction execution system such as, server processor301in a computer system or other system. The logic can comprise statements including instructions and declarations that can be fetched from the computer-readable storage medium and executed by the instruction execution system.

In the context of the present disclosure, a “computer-readable storage medium” can be any medium that can contain, store, or maintain the logic or application described herein for use by or in connection with the instruction execution system. The computer-readable storage medium can comprise any one of many non-transitory physical media, such as electronic, magnetic, optical, electromagnetic, infrared, or semiconductor media. More specific examples of a suitable computer-readable storage medium can include, but are not limited to, magnetic tapes, magnetic floppy diskettes, magnetic hard drives, memory cards, solid-state drives, USB flash drives, or optical discs. Also, the computer-readable storage medium can be a random access memory (RAM), including static random access memory (SRAM), dynamic random access memory (DRAM) or magnetic random access memory (MRAM). In addition, the computer-readable storage medium can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other type of memory device.