Patent Grant
10541964
With advancements in technology, the amount and different types of information that users can access over wireless networks is growing rapidly. Similarly, mobile devices are becoming ubiquitous due to convenience of use resultant from their lightweight nature. Users are also pushing the envelope on the applications and information that are required to be provided via the devices. Applications related to messaging, contacts, social media, calendaring, digital imaging, audio recording, and the like, can be provided in leading devices. However, an ever present challenge for users is managing the immense types and amount of data to enable convenient and efficient use of the devices. Convention devices provide applications to the user as independent and isolated entities. These devices are application-targeted as the user is required to open a particular application to obtain information provided by the application. In order to enjoy different types of information about those with which the user is in communication, the user is required to repeat the process and open other applications to obtain other types of information provided by the other applications. The process of opening and entering different applications to gain different types of information about individuals and/or groups can be time-consuming and inefficient. Accordingly, systems, apparatus, methods and computer-readable storage media for facilitating integrated messaging, contacts and social media for a selected entity are desirable.
Non-limiting and non-exhaustive embodiments of various aspects detailed herein are described with reference to the following figures, wherein like reference numerals refer to like parts.
Certain illustrative embodiments are described herein in the following description and the annexed drawings. These embodiments are merely exemplary, non-limiting and non-exhaustive. As such, all modifications, alterations, and variations within the spirit of the embodiments is envisaged and intended to be covered herein.
Further, in the following description, for purposes of mere explanation, numerous, specific details are set forth in order to facilitate a more thorough understanding of the embodiments described herein, including the claimed subject matter. However, as is known to those of ordinary skill in the art, the embodiments can be practiced, in many instances, without inclusion of the specific details.
As used in this application, the terms “component,” “module,” “system,” “interface,” and the like, are generally intended to refer to hardware and/or software or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. As another example, an interface can include input/output (I/O) components as well as associated processor, application and/or API components, and can be as simple as a command line or as complex as an Integrated Development Environment (IDE).
Furthermore, the embodiments may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer, apparatus or article of manufacture to implement the functionality disclosed herein. The term “article of manufacture,” as used herein, is intended to encompass a computer program, or computer program product, accessible from any computer-readable device, computer-readable carrier, computer-readable media or computer-readable storage media. Computer-readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strip), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and/or flash memory devices (e.g., card, stick, key drive). Additionally it should be appreciated that a carrier wave can carry computer-readable electronic data (e.g., the data transmitted and received via email and/or to access the Internet or a network such as a local area network (LAN)). As known to those of ordinary skill in the art, modifications can be made to the above embodiments without departing from the spirit of the disclosure.
Moreover, the word “exemplary” is used herein to mean an example, instance or illustration. Any aspect or design described herein as “exemplary” is not to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word “exemplary” is merely intended to present examples of embodiments. Further, as used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the inclusive permutations (e.g., X employs A, X employs B, X employs A and B). In addition, the articles “a” and “an,” as used herein, should be construed to mean “one or more” unless, as specified otherwise, or clear from context, the articles are directed to only a singular form.
As used herein, the terms “infer” or “inference” refer generally to the process of reasoning about or inferring states of the system, apparatus, method, environment, and/or user from a set of observations as captured via events and/or data. By way of examples, but not limitation, inference can be employed to identify a specific context or action, or can generate a probability distribution over states. The inference can be probabilistic (e.g., the computation of a probability distribution over states of interest based on a consideration of data and events). Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference can result in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
It will be appreciated by one of skill in the art that a communication network for systems described herein can include any suitable mobile- and/or wireline-based circuit-switched communication network including a global systems for mobile communication (GSM) network, a time division multiple access (TDMA) network, a code division multiple access (CDMA) network, such as IS-95 and subsequent iterations of CDMA technology, an integrated digital enhanced network (iDEN) network and a public switched telephone network (PSTN). Further examples of a communication network can include any suitable data packet-switched or combination data packet/circuit-switched communication network, wired or wireless internet protocol (IP) network such as a voice over internet protocol (VoIP) network, an IP data network, a universal mobile telecommunication system (UMTS) network, a general packet radio service (GPRS) network, or other communication networks that provide streaming data communication over IP and/or integrated voice and data communication over combination data packet/circuit-switched technologies.
Similarly, one of ordinary skill in the art will appreciate that a communication device for systems disclosed herein can include a mobile device, mobile phone, a PSTN phone, a cellular communication device, a cellular phone, a satellite communication device, a satellite phone, a VoIP phone, a wireless fidelity (WiFi) phone, a dual-mode cellular/WiFi phone, a combination cellular/VoIP/WiFi/Worldwide Interoperability for Microwave Access (WiMAX) phone or any suitable combination thereof. Specific examples of a mobile device can include, but is not limited to, a cellular device, such as a GSM, TDMA, CDMA, IS-95 and/or iDEN phone, a cellular/WiFi device, such as a dual-mode GSM, TDMA, IS-95 and/or iDEN/VoIP phones, UMTS phones UMTS VoIP phones, or like devices or combinations thereof. To provide support for a mobile device, a gateway routing component can include any suitable component that can perform centralized routing within a mobile, satellite, or similar network (but optionally need not include components that route strictly within a PSTN network), routing between communication networks, between networks of varying architecture (e.g., between PSTN, GSM, Universal Mobile Telecommunications System (UMTS), Enterprise VoIP, the Internet, or combinations thereof), and the like. Specific examples of a gateway routing component can include, but are not limited to, a gateway mobile switching center (GMSC), a gateway general packet radio service (GPRS) support node (GGSN), a session border control (SBC) device, or like devices. Additionally, a data storage component of such a system can include any suitable device, process and/or combination device and process that can store digital and/or switched information (e.g., server, database, data store, or the like).
The aspects described herein are systems, apparatus, methods and computer-readable storage media for facilitating integrated messaging, contacts and social media for a selected entity.
In one aspect, a computer-implemented method is provided. The computer-implemented method can include executing, using at least one processor, computer-readable instructions for performing various acts. The acts can include executing at least two applications. At least one of the two applications can be adapted to provide social media information. The acts can also include receiving a signal in response to a detected input gesture indicative of a selection of an entity. The selection can be performed via another one of the two applications. The acts can also include integrating the two applications such that social media information is generated about the entity. The integration can be in response to receiving the signal, and the social media information can include information from one or more social networking websites. The acts can also include displaying the social media information about the entity.
In another aspect, an apparatus is provided. The apparatus can include a processor and an application integration component. The application integration component can be configured to receive a signal in response to a detected input gesture indicative of a selection of an entity. The selection can be performed via at least one application in which the entity can be selected. The application integration component can also be configured to, in response to receiving the signal, integrate the application in which the entity can be selected with at least one application from which social media information can be provided, such that social media information about the entity is generated. The social media information can include information from one or more social networking websites. The apparatus can also include a user interface configured to display the social media information generated about the entity; and a computer-readable storage medium storing computer-executable instructions that, if executed, cause the processor to perform one or more functions of the user interface.
In another aspect, a computer-readable storage medium is provided. The computer-readable storage medium can store computer-executable instructions that, if executed on a processor, cause the processor to display, in a user interface, social media information about an entity. Social media information can be provided via at least one of two applications. Displaying the social media information about the entity can be in response to an application integration component: receiving a signal indicative of a selection of the entity from another one of the two applications; and integrating the two applications such that the social media information about the entity is generated. Integrating the two applications can be performed in response to receiving the signal indicative of the selection of the entity. The social media information can include information from one or more social networking websites.
The I/O component 110 can be configured to receive inputs from a region external to the apparatus 100 and to output information from the apparatus 100. In various embodiments, the inputs can be received in response to input gestures that are finger-based and/or stylus-based. In various embodiments, the outputs can be textual-, graphical-, pictorial-, video- and/or audio-based.
The display component 112 can be, include or be communicatively coupled to a UI (not shown). The UI can be configured to provide textual, graphical, video, pictorial and/or audio displays to the user of the apparatus 100. In some embodiments, the UI can be a triptych UI, and can be as described below with reference to
The display component 112 can be configured to display a selected display region in response to the input gesture. For example, upon displaying the middle display region of the triptych UI and receiving a swipe right gesture, the leftmost display region of the triptych can be displayed. Any number of different types of gestures (e.g., flicks, taps or the like) can be received for displaying a selected display region of the triptych UI. In the embodiments described herein, a triptych UI is generally discussed in connection with displaying information from or related to messaging, contacts and social media applications. However, by way of example, but not limitation, the applications could be email, alarm, camera, telephone, maps, browsers, music, photos, videos, clocks, settings, calendars and/or any other application typically found in a mobile device. Further, the spirit of the embodiments described also applies to a diptych user interface or n-tych user interfaces generally. As used herein, the term “diptych” shall mean “having two display regions virtually coupled to one another.” In some embodiments, the display component 112 can be or include a UI that is a touch-sensitive touch screen.
The apparatus 100 can also include the security component 114. The security component can be a component configured to lock and unlock the UI and/or apparatus 100. In some embodiments, the security component 114 can unlock the UI and/or apparatus 100 in response to a swipe gesture received at the UI.
The apparatus 100 can also include a messaging component 116 configured to control the operation of one or more messaging applications. By way of example, but not limitation, messaging applications can include text-based, voice-based, video-based and/or combination voice and audio-based applications such as text messaging, instant messaging, internet and landline telephony, and/or audio and textual voicemail communications. By way of other examples, but without limitation, messaging applications can include applications utilizing short message service (SMS), multimedia messaging service (MMS), instant messaging (IM) protocols and/or text over internet protocol (ToIP) messaging.
The messaging component 116 can be configured to receive inputs from the I/O component 110 and format, transmit and/or receive messaging content in response to the inputs received. The messaging content can include a threaded list of one or more messages received at or transmitted from the apparatus 100. The messages can be text messages, instant messages, email messages, voicemail messages or any other messages that can be provided to the user. The content of the messages can be provided in bubbles or other shapes or indicia and, in some embodiments, can be associated with or displayed with an identifier of the initiator of the messaging content. In some embodiments, the messaging component 116 can display messaging content as the messaging card discussed below with reference to
In some embodiments, the messaging component 116 can include a quick reply component (not shown) configured to provide a message notification to a user of the apparatus upon receipt of a message. The message notification can be displayed in a manner that superimposes the notification, and/or a text box for responding to the notification, over the content displayed on the UI of the apparatus 100. In various embodiments, the user can enter content for replying to the message notification and/or enter an input causing the message notification to be removed from the UI. Should the user desire to enter content to reply to the message notification, the content can be entered into a displayed text box associated with the message notification. Should the user desire to forego entering content to reply to the message notification, the message prompting the message notification can be closed and the message can nonetheless be provided in a message list generated by the messaging component 116.
The apparatus 100 can also include a contacts component 118 configured to control the operation of one or more contact applications. The contact applications can provide contacts-related information. By way of example, but not limitation, contacts-related information can include voice, email and/or geographical contact information for an individual or group in a contacts repository accessible by the apparatus 100. As such, the contacts-related information can be mobile, home, work and/or fax numbers, email addresses, physical street addresses, social network identification information, a social network identification, or the like. The contacts-related information can also include information about the individual or the group including, but not limited to, biographical information such as the birthday or date of incorporation of the individual and group, respectively, favorite foods of an individual and/or other information specific to the individual or group that the user of the apparatus 100 may want to access. The contacts-related information can include information that the user has stored locally on the apparatus 100 (e.g., in the address book of the apparatus 100) and/or that the user can access from a location that is remote from the physical location of the apparatus 100.
In various embodiments as described herein and with reference to any number of different applications including, but not limited to, a messaging application, a contacts application and/or a social media application, where an entity, person or individual is discussed, the entity, person or individual can be a legal or natural entity, person or individual. Similarly, in various embodiments as described herein and with reference to any number of different applications including, but not limited to, a messaging application, a contacts application and/or a social media application, where an entity or group is discussed herein, the entity or group can include one or more legal or natural entities, persons or individuals. By way of example, but not limitation, an entity or group could be an organization, a business entity, a group of humans, and/or a group including a legal and a natural person or entity.
The apparatus 100 can also include a social media component 120 configured to control the receipt, aggregation, generation, output and/or filtering of social media information at the apparatus 100. By way of example, but not limitation, social media information can include, but is not limited to, information associated with or output from social media feeds, blog information, chat information, instant messaging information, and the like. The social media information can be displayed in any number of arrangements including, but not limited to, the subject matter of the social media feed, the social networking site from which the social media feed is provided and/or the chronological order of the social media feeds. In some embodiments, the social media information can include comments posted (or a number of comments posted) in association with one or more social media feeds for the individual. In some embodiments, one or more comments can be shown on the UI with the one or more feeds. The social media applications can include applications that provide social media feeds, news feeds and wall postings from FACEBOOK®, activity updates (e.g., tweets) from TWITTER® or other information from social networking sites such as MYSPACE®, websites of interest and the like.
The apparatus 100 can also include an application integration component (AIC) 122. In some embodiments, the AIC 122 can include software and/or hardware configured to integrate one or more applications at an individual level or at a group level. Integrating one or more applications at an individual level can include retrieving and/or providing information specific to an individual. Integrating one or more applications at a group-level can include retrieving and/or providing information specific to a group or individuals of, or members of, the group. For example, the AIC 122 can provide messaging, contacts and/or social media information about a specific individual or for a specific group or for specific members of a group.
In these embodiments, the AIC 122 can enable the apparatus 100 to be individual-targeted or group-targeted in provisioning of contact, messaging and/or social media information without requiring a user of the apparatus to enter individual applications for each of the contact, messaging and/or social media information.
As such, while the messaging component 116, contacts component 118 and the social media component 120 can allow the user of the apparatus 100 to view messaging, contacts and social media information about one or more individuals or groups on a single display region of the UI, when the AIC 122 integrates the messaging, contacts and/or social media application, the AIC 122 can do such integration at an individual or group level. As such, upon integration, the messaging, contacts and/or social media information can be targeted towards a single individual and/or a single group. The targeted information can be information that displays details specific to or about the individual and/or group. Such targeted information can be displayed by UI.
The apparatus 100 can also include a processor 124 for performing various operations described herein, and a memory 126 for storing computer-executable instructions and/or information for performing the operations described herein.
Referring again to
The first application component can be configured to execute a first application for providing social media information. The second application component can be configured to execute a second application for accessing information indicative of an entity.
In various embodiments, the entity can be an individual or a group. In some embodiments, the second application can be a messaging application such as that provided by messaging component 116. In these embodiments, the entity can be a group of individuals for which selectable indicia of a group and/or broadcast message is displayed on the UI.
The AIC 122 can be configured to receive a signal in response to a detected input gesture indicative of a selection of the entity from the second application. The AIC 122 can also be configured to, in response to receiving the signal, integrate the first application and the second application such that social media information about the entity is generated.
The social media information can include information from one or more social networking websites. In various embodiments, the social media information can be any type of social media information described herein, including, but not limited to, information from a blog, information from a news feed, information from a post at a social networking website.
In various embodiments, the social media information about the entity can differ in content and/or type from the information indicative of the entity. By way of example, but not limitation, the social media information can include wall postings, news feeds, blogs and/or any social media information related thereto, as described herein. By contrast, in some embodiments, the information indicative of the entity can include contact-related information such as a name or telephone number or email address of a contact. Accordingly, one or more of the embodiments described herein can include generating social media information that includes one or more textual, graphical, pictorial and/or video elements that differ from the textual, graphical, pictorial and/or video elements included in the information indicative of the entity.
In some embodiments, the information from the social networking websites includes first social media information about the entity from a first social networking website, and social media information about the entity from a second social networking website. The social media information about the entity displayed on the user interface can therefore be an aggregate of the first social media information about the entity and the second media information about the entity.
In some embodiments, the UI can be a touch screen. In other embodiments, the UI can be any interface configured to display social media information about an entity. The user interface can be configured to display the social media information about the entity.
In some embodiments, the UI can include a plurality of any number of display regions. For example, in some embodiments, the UI includes a plurality of display regions including a leftmost display region, a rightmost display region and a middle display region between the leftmost display region and the rightmost display region. The UI can be configured to display the leftmost display region, the rightmost display region and the middle display region as non-overlapping regions and/or in non-concurrent time intervals. In some embodiments, the UI and operation thereof can be as shown and described with reference to
In some embodiments, the UI can be configured to display the social media information about the entity on the leftmost display region, the rightmost display region or the middle display region. In some embodiments, the UI can be configured to display the information indicative of the entity on another one of the leftmost display region, the rightmost display region or the middle display region.
The UI can selectively display the leftmost display region, the rightmost display region or the middle display region in response to a selected input gesture. By way of example, but not limitation, the selected input gesture can be a swipe left gesture or a swipe right gesture.
The computer-readable storage medium can store computer-executable instructions that, if executed, cause the processor 124 to implement at least one of the first application component, the second application component, the AIC 122 or the UI.
The middle display region 212 can include indicia 226, 228 of messaging content. The messaging content can be for a specific individual or group, as described with reference to the AIC 122 of
The leftmost display region 210 can include indicia 222 of the individual or group for which contacts-related information is provided, and the contacts-related information 224.
The rightmost display region 214 can include social media information 230, 232, 234, 236 (e.g., social media feeds) from social networking sites. In the embodiment shown, the social media information can be displayed in an aggregated form whereby social media information 230, 232 from a first social networking site can be displayed concurrently on the UI with social media information 234, 236 from a second social networking site.
As shown in the embodiment illustrated, the messaging content can be textual, graphical, video and/or pictorial. Additionally, the messaging content can include audio files and/or links to website or audio files. The individual (or group) with which a conversation is being (or has been) conducted can be selected for integration and individual-targeted information provisioning described with reference to
In embodiments wherein the level two 620 operations are displayed via a triptych UI, the AIC 122 can integrate the level one applications 610 such that first 622, second 626 and third 630 display regions of the triptych UI can display the individual-targeted or the group-targeted contacts-related, messaging or social media information, respectively. In embodiments described herein, inputs for selecting the display of contacts-related, messaging or social media information on the triptych UI can be any number of different types of inputs. The inputs can include, but are not limited to, swipe right or swipe left gestures (or tap gestures on the triptych button 624, 628, 632). The inputs can display the next display region in succession in the order of triptych UI display regions. By way of example, but not limitation, a swipe left gesture from the middle display region, which corresponds to the messaging screen 626 in the illustrated embodiment, can cause the leftmost display region, which corresponds to the contacts screen 622 to be displayed. Similarly, a swipe right gesture from the middle display region can cause the rightmost display region, which corresponds to the social media screen 630 in the illustrated embodiment, to be displayed. Further, a swipe left gesture from the rightmost display region can cause the leftmost display region, which corresponds to the contacts screen 622 in this embodiment, to be displayed. A swipe right gesture from the rightmost display region can cause the messaging screen 626 to be displayed. In various embodiments, in lieu of swiping gestures, a tap gesture on the triptych button 624, 628, 632 can cause the next display region to the right of (or, in some embodiments, the left of) the currently-displayed display to be displayed.
Referring back to
While the apparatus is shown as apparatus 718, principles described herein can also apply to apparatus 100. The UI 720 includes, at least, a locked region 722 and an unlocked region 724. The locked region 722 corresponds to a locking portion while the unlocked region 724 corresponds to an unlocking portion. A lock icon 726 can be displayed in the locked region 722 or the unlocked region 724. An arch 728 can be displayed in the unlocked region 724. At a first time, lock icon 726 can reside in the locked region 722 and the UI 720 can therefore remain in a locked state. At a second time, the lock icon 726 can be moved to the arch 728 of the unlocked region 724. When the lock icon 726 is moved to the arch 728 of the unlocked region 724, a new icon displaying an unlocked lock (not shown) can be displayed. In some embodiments, when the lock icon 726 is moved to the arch 728 of the unlocked region 724, the lock icon 726 continues to be displayed until the UI is unlocked and/or the UI provides a new display.
The lock icon 726 can be moved from the locked region 722 to the arch 728 of the unlocked region 724 via an input gesture on the surface of the UI 720. In various embodiments, the input gesture can include a swipe right gesture from the locked region 722 to the unlocked region 724. In various embodiments, the input gesture can include a swipe in the shape of an arc. The swipe can be provided from the locked region 722 to the unlocked region 724. While the embodiment shown and described discloses a swipe right gesture or a swipe in the form of an arc for unlocking the apparatus 718, in other embodiments wherein the design of the locations of the locking and unlocking portions of the UI is suitable, the apparatus 718 and/or UI can be unlocked upon receiving a swipe left gesture and/or upon receiving a swipe up, a swipe down gesture and/or a swipe along a diagonal.
Referring to
At 818, an input gesture to display social media information can be provided. At 820, individual-targeted social media information can be displayed. In various embodiments, individual-targeted social media information can be social media information about the individual and/or group selected at 810.
Referring to
At 856, the method 850 can include receiving a signal in response to a detected input gesture. The detected input gesture can be indicative of a selection of the entity. The entity can be selected while the user is in the second application.
At 858, the method 850 can include, in response to receiving the signal, integrating the first application and the second application such that social media information about the entity is generated. In some embodiments, the social media information can include information from one or more social networking websites. At 860, the method 850 can include displaying the social media information about the entity.
In various embodiments, the social media information about the entity can differ in content and/or type from the information indicative of the entity. By way of example, but not limitation, the social media information about the entity can include wall postings, news feeds, and/or blogs about the entity, posted on a social networking webpage assigned to the entity and/or any other social media information, as described herein, and about the entity. By contrast, in some embodiments, the information indicative of the entity can include contacts-related information including such as a name or telephone number or email address of a contact. Accordingly, while the contacts-related information can be a first set of characters, the social media information can be a second set of characters. The first set of characters can be different from the second set of characters.
Referring to
Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.
The illustrated aspects of the claimed subject matter can also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.
A computer typically includes a variety of computer-readable storage media. Computer-readable storage media can be any available media that can be accessed by the computer and includes both volatile and non-volatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can comprise computer storage media and communication media. Computer storage media includes both volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital video disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.
Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of communication media derived from computer-readable storage media and capable of subsequently propagating through electrically conductive media, (e.g., such as a system bus, microprocessor, data port, and the like) and/or non-electrically conductive media (e.g., in the form of radio frequency microwave frequency, optical frequency and similar electromagnetic frequency modulated data signals).
With reference to
The AIC 122 can then integrate the first application and the second application in response to receiving the signal. Integrating the first application and the second application can include any steps that result in social media information about the entity being generated.
The social media information can include information from one or more social networking websites. Further, the social media information generated for the entity can differ in content and/or type from the information indicative of the entity. By way of example, but not limitation, the social media information can include wall postings, news feeds, blogs and/or any social media information related thereto, as described herein. By contrast, in some embodiments, the information indicative of the entity can include contact-related information including such as a name or telephone number or email address of a contact. Accordingly, one or more of the embodiments described herein can include generating social media information that includes one or more textual, graphical, pictorial and/or video elements that differ from the textual, graphical, pictorial and/or video elements in the information indicative of the entity.
The computer-readable storage medium can also store computer-executable instructions that, if executed on the processor 124, cause the processor 124 to configure the UI. In some embodiments, the UI can be configured to include a plurality of display regions including a leftmost display region, a rightmost display region and a middle display region between the leftmost display region and the rightmost display region. The UI can be configured to display the leftmost display region, the rightmost display region and the middle display region as non-overlapping regions and/or in non-concurrent time intervals. In some embodiments, the UI and operation thereof can be as shown and described with reference to
In some embodiments, the UI can be configured to display the social media information about the entity on a first one of the leftmost display region, the rightmost display region or the middle display region, and display the information indicative of the entity on a second one of the leftmost display region, the rightmost display region or the middle display region. The first display region can be different from the second display region in some embodiments.
The computer-readable storage medium can also store computer-executable instructions that, if executed on the processor 124, cause the processor 124 to associate a first region of the UI with an unlocked state of the UI; receive a signal indicative of an input gesture in the first region of the UI; and unlock the UI in response to receiving the signal indicative of the input gesture in the first region of the UI. In some embodiments, the UI can be as shown and described with reference to
The computer-readable storage medium can also store computer-executable instructions that, if executed on the processor 124, cause the processor 124 to associate a second region of the UI with a locked state of the UI. Prior to receiving the signal indicative of the input gesture in the first region of the UI, the processor 124 can receive a signal indicative of the input gesture in the second region of the UI. The input gesture can be provided in the second region and in the first region upon a swipe gesture from the second region to the first region being applied to the UI.
The computer-readable storage medium can also store computer-executable instructions that, if executed on the processor 124, cause the processor 124 to display a lock icon in the second region of the UI. In some embodiments, the processor 124 can display an arch in the first region of the UI. The input gesture can be received in the second region and in the first region upon a swipe gesture dragging the lock icon in the second region to the arch in the first region being applied to the UI. In some embodiments, the UI can be touch-sensitive.
Referring back to
The system memory 1112 can retain a number of program modules, such as an operating system, one or more application programs, other program modules, and program data. All or portions of an operating system, applications, modules, and/or data can be, for instance, cached in RAM, retained upon a hard disk drive, or any other suitable location. A user can enter commands and information into the computer 1110 through one or more wired/wireless input devices, such as a keyboard, pointing and clicking mechanism, pressure sensitive screen, microphone, joystick, stylus pen, etc. A monitor or other type of interface can also be connected to the system bus 1116.
The computer 1110 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, phones, or other computing devices, such as workstations, server computers, routers, personal computers, portable computers, microprocessor-based entertainment appliances, peer devices or other common network nodes, etc. The computer 1110 can connect to other devices/networks by way of antenna, port, network interface adaptor, wireless access point, modem, and/or the like.
The computer 1110 is operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This includes at least WiFi and Bluetooth™ wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.
WiFi, or Wireless Fidelity, allows connection to the Internet from a couch at home, a bed in a hotel room, or a conference room at work, without wires. WiFi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out, anywhere within the range of a base station. WiFi networks use radio technologies called IEEE 802.11 (a, b, g, etc.) to provide secure, reliable, fast wireless connectivity. A WiFi network can be used to connect computers to each other, to the Internet, and to wired networks (which use IEEE 802.3 or Ethernet). WiFi networks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10 BaseT wired Ethernet networks used in many offices.
The embedded client 1202a communicates with an application 1202b that provides services and/or information to an end user. One example of the application can be navigation software that provides near real-time traffic information that is received via the embedded client 1202a to the end user. The navigation software can provide road conditions, suggest alternate routes, etc. based on the location of the MS 1202. Those of ordinary skill in the art understand that there are many different methods and systems of locating an MS 1202.
Alternatively, the MS 1202 and a device 1202c can be enabled to communicate via a short-range wireless communication link, such as Bluetooth™ For example, a Bluetooth™ SIM Access Profile can be provided in an automobile (e.g., device 1202c) that communicates with the SIM 1202c in the MS 1202 to enable the automobile's communications system to pull information from the MS 1202. The Bluetooth™ communication system in the vehicle becomes an “embedded phone” that employs an antenna associated with the automobile. The result is improved reception of calls made in the vehicle. As one of ordinary skill in the art would recognize, an automobile is one example of the device 1202c. There can be an endless number of devices 1202c that use the SIM within the MS 1202 to provide services, information, data, audio, video, etc. to end users.
The BTS 1204 is physical equipment, such as a radio tower, that enables a radio interface to communicate with the MS. Each BTS can serve more than one MS. The BSC 1206 manages radio resources, including the BTS. The BSC can be connected to several BTSs. The BSC and BTS components, in combination, are generally referred to as a base station (BSS) or radio access network (RAN) 1203.
The GSM core network 1201 also includes a Mobile Switching Center (MSC) 1208, a Gateway Mobile Switching Center (GMSC) 1210, a Home Location Register (HLR) 1212, Visitor Location Register (VLR) 1214, an Authentication Center (AuC) 1218, and an Equipment Identity Register (EIR) 1216. The MSC 1208 performs a switching function for the network. The MSC also performs other functions, such as registration, authentication, location updating, handovers, and call routing. The GMSC 1210 provides a gateway between the GSM network and other networks, such as an Integrated Services Digital Network (ISDN) or Public Switched Telephone Networks (PSTNs) 1220. In other words, the GMSC 1210 provides interworking functionality with external networks.
The HLR 1212 is a database or component(s) that comprises administrative information regarding each subscriber registered in a corresponding GSM network. The HLR 1212 also includes the current location of each MS. The VLR 1214 is a database or component(s) that contains selected administrative information from the HLR 1212. The VLR contains information necessary for call control and provision of subscribed services for each MS currently located in a geographical area controlled by the VLR. The HLR 1212 and the VLR 1214, together with the MSC 1208, provide the call routing and roaming capabilities of GSM. The AuC 1216 provides the parameters needed for authentication and encryption functions. Such parameters allow verification of a subscriber's identity. The EIR 1218 stores security-sensitive information about the mobile equipment.
A Short Message Service Center (SMSC) 1209 allows one-to-one Short Message Service (SMS) messages to be sent to/from the MS 1202. A Push Proxy Gateway (PPG) 1211 is used to “push” (e.g., send without a synchronous request) content to the MS 1202. The PPG 1211 acts as a proxy between wired and wireless networks to facilitate pushing of data to the MS 1202. A Short Message Peer to Peer (SMPP) protocol router 1213 is provided to convert SMS-based SMPP messages to cell broadcast messages. SMPP is a protocol for exchanging SMS messages between SMS peer entities such as short message service centers. It is often used to allow third parties, e.g., content suppliers such as news organizations, to submit bulk messages.
To gain access to GSM services, such as speech, data, and short message service (SMS), the MS first registers with the network to indicate its current location by performing a location update and IMSI attach procedure. The MS 1202 sends a location update including its current location information to the MSC/VLR, via the BTS 1204 and the BSC 1206. The location information is then sent to the MS's HLR. The HLR is updated with the location information received from the MSC/VLR. The location update also is performed when the MS moves to a new location area. Typically, the location update is periodically performed to update the database as location-updating events occur.
The GPRS network 1230 is logically implemented on the GSM core network architecture by introducing two packet-switching network nodes, a serving GPRS support node (SGSN) 1232, a cell broadcast and a Gateway GPRS support node (GGSN) 1234. The SGSN 1232 is at the same hierarchical level as the MSC 1208 in the GSM network. The SGSN controls the connection between the GPRS network and the MS 1202. The SGSN also keeps track of individual MS's locations and security functions and access controls.
A Cell Broadcast Center (CBC) 1233 communicates cell broadcast messages that are typically delivered to multiple users in a specified area. Cell Broadcast is one-to-many geographically focused service. It enables messages to be communicated to multiple mobile phone customers who are located within a given part of its network coverage area at the time the message is broadcast.
The GGSN 1234 provides a gateway between the GPRS network and a public packet network (PDN) or other IP networks 1236. In embodiments, the GGSN provides interworking functionality with external networks, and sets up a logical link to the MS through the SGSN. When packet-switched data leaves the GPRS network, it is transferred to an external TCP-IP network 1236, such as an X.25 network or the Internet. In order to access GPRS services, the MS first attaches itself to the GPRS network by performing an attach procedure. The MS then activates a packet data protocol (PDP) context, thus activating a packet communication session between the MS, the SGSN, and the GGSN.
In a GSM/GPRS network, GPRS services and GSM services can be used in parallel. The MS can operate in one three classes: class A, class B, and class C. A class A MS can attach to the network for both GPRS services and GSM services simultaneously. A class A MS also supports simultaneous operation of GPRS services and GSM services. For example, class A mobiles can receive GSM voice/data/SMS calls and GPRS data calls at the same time. A class B MS can attach to the network for both GPRS services and GSM services simultaneously. However, a class B MS does not support simultaneous operation of the GPRS services and GSM services. That is, a class B MS can only use one of the two services at a given time. A class C MS can attach for only one of the GPRS services and GSM services at a time. Simultaneous attachment and operation of GPRS services and GSM services is not possible with a class C MS.
A GPRS network 1230 can be designed to operate in three network operation modes (NOM1, NOM2 and NOM3). A network operation mode of a GPRS network is indicated by a parameter in system information messages transmitted within a cell. The system information messages dictates a MS where to listen for paging messages and how signal towards the network. The network operation mode represents the capabilities of the GPRS network. In a NOM1 network, a MS can receive pages from a circuit switched domain (e.g., voice call) when engaged in a data call. The MS can suspend the data call or take both simultaneously, depending on the ability of the MS. In a NOM2 network, a MS cannot receive pages from a circuit switched domain when engaged in a data call, since the MS is receiving data and is not listening to a paging channel. In a NOM3 network, a MS can monitor pages for a circuit switched network while received data and vice versa.
The IP multimedia network 1238 was introduced with 3GPP Release 5, and includes an IP multimedia subsystem (IMS) 1240 to provide rich multimedia services to end users. A representative set of the network entities within the IMS 1240 are a call/session control function (CSCF), a media gateway control function (MGCF) 1246, a media gateway (MGW) 1248, and a master subscriber database, called a home subscriber server (HSS) 1250. The HSS 1250 can be common to the GSM network 1201, the GPRS network 1230 as well as the IP multimedia network 1238.
The IP multimedia system 1240 is built around the call/session control function, of which there are three types: an interrogating CSCF (I-CSCF) 1243, a proxy CSCF (P-CSCF) 1242, and a serving CSCF (S-CSCF) 1244. The P-CSCF 1242 is the MS's first point of contact with the IMS 1240. The P-CSCF 1242 forwards session initiation protocol (SIP) messages received from the MS to an SIP server in a home network (and vice versa) of the MS. The P-CSCF 1242 can also modify an outgoing request according to a set of rules defined by the network operator (e.g., address analysis and potential modification).
The I-CSCF 1243 forms an entrance to a home network and hides the inner topology of the home network from other networks and provides flexibility for selecting an S-CSCF. The I-CSCF 1243 can contact a subscriber location function (SLF) 1245 to determine which HSS 1250 to use for the particular subscriber, if multiple HSS 1250 are present. The S-CSCF 1244 performs the session control services for the MS 1202. This includes routing originating sessions to external networks and routing terminating sessions to visited networks. The S-CSCF 1244 also decides whether an application server (AS) 1252 is required to receive information on an incoming SIP session request to ensure appropriate service handling. This decision is based on information received from the HSS 1250 (or other sources, such as an application server 1252). The AS 1252 also communicates to a location server 1256 (e.g., a Gateway Mobile Location Center (GMLC)) that provides a position (e.g., latitude/longitude coordinates) of the MS 1202.
The HSS 1250 contains a subscriber profile and keeps track of which core network node is currently handling the subscriber. It also supports subscriber authentication and authorization functions (AAA). In networks with more than one HSS 1250, a subscriber location function provides information on the HSS 1250 that contains the profile of a given subscriber.
The MGCF 1246 provides interworking functionality between SIP session control signaling from the IMS 1240 and ISUP/BICC call control signaling from the external GSTN networks (not shown). It also controls the media gateway (MGW) 1248 that provides user-plane interworking functionality (e.g., converting between AMR- and PCM-coded voice). The MGW 1248 also communicates with other IP multimedia networks 1254.
In some embodiments, the IP networks 1236 described herein include networks communicatively coupled to social networking sites. As such, the networks disclosed herein can also include such IP networks 1236 and one or more social networking sites.
What has been described above includes embodiments of claimed subject matter. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the claimed subject matter. However, one of ordinary skill in the art can recognize that many further combinations and permutations of such subject matter are possible. Accordingly, the claimed subject matter is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
This application is a continuation of, and claims priority to each of, U.S. patent application Ser. No. 12/643,726 (now U.S. Pat. No. 9,424,444), filed Dec. 21, 2009, entitled “SYSTEMS, APPARATUS, METHODS AND COMPUTER-READABLE STORAGE MEDIA FOR FACILITATING INTEGRATED MESSAGING, CONTACTS AND SOCIAL MEDIA FOR A SELECTED ENTITY”, which application claims the benefit of priority to U.S. Provisional Application No. 61/251,717, filed Oct. 14, 2009, and entitled “SYSTEMS, METHODS AND APPARATUS FOR NEXT-GENERATION MOBILE MESSAGING,” which applications are hereby incorporated herein by reference in their respective entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5072412 | Henderson, Jr. et al. | Dec 1991 | A |
| 5233687 | Henderson, Jr. et al. | Aug 1993 | A |
| 5394521 | Henderson, Jr. et al. | Feb 1995 | A |
| 5838326 | Card et al. | Nov 1998 | A |
| 5847709 | Card et al. | Dec 1998 | A |
| 6269369 | Robertson | Jul 2001 | B1 |
| 6351764 | Voticky et al. | Feb 2002 | B1 |
| 6367020 | Klein | Apr 2002 | B1 |
| 6401209 | Klein | Jun 2002 | B1 |
| 6633630 | Owens et al. | Oct 2003 | B1 |
| 7269727 | Mukherjee et al. | Sep 2007 | B1 |
| 7286063 | Gauthey et al. | Oct 2007 | B2 |
| 7308926 | Hawkins | Dec 2007 | B1 |
| 7322626 | Thomas | Jan 2008 | B2 |
| 7324333 | Allen | Jan 2008 | B2 |
| 7376669 | Klein | May 2008 | B2 |
| 7443665 | Allen | Oct 2008 | B2 |
| 7453443 | Rytivaara et al. | Nov 2008 | B2 |
| 7478436 | Sheih et al. | Jan 2009 | B1 |
| 7606024 | Boss et al. | Oct 2009 | B2 |
| 7620982 | Ishidera | Nov 2009 | B2 |
| 7628335 | Morimoto et al. | Dec 2009 | B2 |
| 7636033 | Golden | Dec 2009 | B2 |
| 7640293 | Wilson et al. | Dec 2009 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7761814 | Rimas-Ribikauskas et al. | Jul 2010 | B2 |
| 7933609 | Lagerstedt et al. | Apr 2011 | B2 |
| 7953859 | Kiefhaber et al. | May 2011 | B1 |
| 7974414 | Burns | Jul 2011 | B2 |
| 8108781 | Laansoo et al. | Jan 2012 | B2 |
| 8316095 | Wheeler, Jr. et al. | Nov 2012 | B1 |
| 8484564 | Marti et al. | Jul 2013 | B1 |
| 8543927 | McKinley et al. | Sep 2013 | B1 |
| 8676901 | Nicolaou et al. | Mar 2014 | B1 |
| 8881025 | Swink et al. | Nov 2014 | B2 |
| 20010044903 | Yamamoto et al. | Nov 2001 | A1 |
| 20020056046 | Klein | May 2002 | A1 |
| 20020077079 | Ishihara | Jun 2002 | A1 |
| 20020099960 | Klein | Jul 2002 | A1 |
| 20020114654 | Abe | Aug 2002 | A1 |
| 20030023688 | Denenberg et al. | Jan 2003 | A1 |
| 20030025840 | Arling | Feb 2003 | A1 |
| 20030074575 | Hoberock et al. | Apr 2003 | A1 |
| 20030074590 | Fogle et al. | Apr 2003 | A1 |
| 20030120957 | Pathiyal | Jun 2003 | A1 |
| 20030172495 | Pan | Sep 2003 | A1 |
| 20030184592 | Awada et al. | Oct 2003 | A1 |
| 20030191960 | Hung-yi | Oct 2003 | A1 |
| 20030206224 | Sakakibara et al. | Nov 2003 | A1 |
| 20040034561 | Smith | Feb 2004 | A1 |
| 20040046018 | Dobbins | Mar 2004 | A1 |
| 20040082322 | Tani | Apr 2004 | A1 |
| 20040085351 | Tokkonen | May 2004 | A1 |
| 20040092247 | Tani | May 2004 | A1 |
| 20040113491 | Mauser | Jun 2004 | A1 |
| 20040113819 | Gauthey | Jun 2004 | A1 |
| 20040123135 | Goddard | Jun 2004 | A1 |
| 20040137884 | Engstrom et al. | Jul 2004 | A1 |
| 20040189439 | Cansino | Sep 2004 | A1 |
| 20040220913 | Walker | Nov 2004 | A1 |
| 20050085215 | Kokko et al. | Apr 2005 | A1 |
| 20050091272 | Smith et al. | Apr 2005 | A1 |
| 20050117564 | Vieri et al. | Jun 2005 | A1 |
| 20050234910 | Buchheit et al. | Oct 2005 | A1 |
| 20050253817 | Rytivaara et al. | Nov 2005 | A1 |
| 20050282135 | Berman | Dec 2005 | A1 |
| 20060012577 | Kyrola | Jan 2006 | A1 |
| 20060041645 | Zhang | Feb 2006 | A1 |
| 20060052091 | Onyon et al. | Mar 2006 | A1 |
| 20060075250 | Liao | Apr 2006 | A1 |
| 20060101350 | Scott | May 2006 | A1 |
| 20060123347 | Hewitt et al. | Jun 2006 | A1 |
| 20060176661 | Allen | Aug 2006 | A1 |
| 20060184351 | Corston-Oliver et al. | Aug 2006 | A1 |
| 20060195474 | Cadiz et al. | Aug 2006 | A1 |
| 20060253371 | Rutt et al. | Nov 2006 | A1 |
| 20060255907 | Min | Nov 2006 | A1 |
| 20060271526 | Charnock et al. | Nov 2006 | A1 |
| 20060282772 | Chamberlin et al. | Dec 2006 | A1 |
| 20060291157 | Allen | Dec 2006 | A1 |
| 20060291158 | Allen | Dec 2006 | A1 |
| 20070022163 | Wormald et al. | Jan 2007 | A1 |
| 20070085839 | Yang et al. | Apr 2007 | A1 |
| 20070088687 | Bromm et al. | Apr 2007 | A1 |
| 20070119952 | Morimoto et al. | May 2007 | A1 |
| 20070133771 | Stifelman et al. | Jun 2007 | A1 |
| 20070133802 | Yuan | Jun 2007 | A1 |
| 20070135091 | Wassingbo | Jun 2007 | A1 |
| 20070144225 | Tamura | Jun 2007 | A1 |
| 20070150842 | Chaudhri et al. | Jun 2007 | A1 |
| 20070161410 | Huang et al. | Jul 2007 | A1 |
| 20070203982 | Jagoe et al. | Aug 2007 | A1 |
| 20070204064 | Mail et al. | Aug 2007 | A1 |
| 20070220542 | Kim | Sep 2007 | A1 |
| 20070247276 | Murchison et al. | Oct 2007 | A1 |
| 20070274300 | Chu et al. | Nov 2007 | A1 |
| 20070282839 | Walker | Dec 2007 | A1 |
| 20080036743 | Westerman et al. | Feb 2008 | A1 |
| 20080036747 | Hope | Feb 2008 | A1 |
| 20080049135 | Okudaira | Feb 2008 | A1 |
| 20080055269 | Lemay et al. | Mar 2008 | A1 |
| 20080055276 | Chang | Mar 2008 | A1 |
| 20080059880 | Cato et al. | Mar 2008 | A1 |
| 20080064370 | Fukaya et al. | Mar 2008 | A1 |
| 20080082421 | Onyon et al. | Apr 2008 | A1 |
| 20080089587 | Kim et al. | Apr 2008 | A1 |
| 20080122796 | Jobs | May 2008 | A1 |
| 20080153459 | Kansal et al. | Jun 2008 | A1 |
| 20080182563 | Wugofski et al. | Jul 2008 | A1 |
| 20080189122 | Coletrane et al. | Aug 2008 | A1 |
| 20080189623 | Patil | Aug 2008 | A1 |
| 20080207166 | Aerrabotu et al. | Aug 2008 | A1 |
| 20080222636 | Wang et al. | Sep 2008 | A1 |
| 20080229397 | Basner et al. | Sep 2008 | A1 |
| 20080256170 | Hayashi et al. | Oct 2008 | A1 |
| 20080281610 | Yoshida et al. | Nov 2008 | A1 |
| 20090006991 | Lindberg et al. | Jan 2009 | A1 |
| 20090029674 | Brezina et al. | Jan 2009 | A1 |
| 20090034804 | Cho et al. | Feb 2009 | A1 |
| 20090040018 | Lee et al. | Feb 2009 | A1 |
| 20090044578 | Boss et al. | Feb 2009 | A1 |
| 20090061823 | Chu | Mar 2009 | A1 |
| 20090064055 | Chaudhri et al. | Mar 2009 | A1 |
| 20090066489 | Golden | Mar 2009 | A1 |
| 20090102803 | Newman et al. | Apr 2009 | A1 |
| 20090104925 | Aula | Apr 2009 | A1 |
| 20090106247 | Daughtry | Apr 2009 | A1 |
| 20090106415 | Brezina et al. | Apr 2009 | A1 |
| 20090119678 | Shih et al. | May 2009 | A1 |
| 20090128335 | Leung | May 2009 | A1 |
| 20090138562 | Schmulen et al. | May 2009 | A1 |
| 20090157732 | Hao et al. | Jun 2009 | A1 |
| 20090167717 | Wang et al. | Jul 2009 | A1 |
| 20090170553 | Wang et al. | Jul 2009 | A1 |
| 20090177981 | Christie et al. | Jul 2009 | A1 |
| 20090187676 | Griffin et al. | Jul 2009 | A1 |
| 20090209235 | Lawler et al. | Aug 2009 | A1 |
| 20090209243 | Brown et al. | Aug 2009 | A1 |
| 20090215479 | Karmarkar | Aug 2009 | A1 |
| 20090217211 | Hildreth et al. | Aug 2009 | A1 |
| 20090222748 | Lejeune et al. | Sep 2009 | A1 |
| 20090234935 | Watson et al. | Sep 2009 | A1 |
| 20090245484 | Bates | Oct 2009 | A1 |
| 20090248844 | Sommer et al. | Oct 2009 | A1 |
| 20090259968 | Hsieh et al. | Oct 2009 | A1 |
| 20090264117 | Hsieh et al. | Oct 2009 | A1 |
| 20090264157 | Hsieh et al. | Oct 2009 | A1 |
| 20090265666 | Hsieh et al. | Oct 2009 | A1 |
| 20090288032 | Chang et al. | Nov 2009 | A1 |
| 20090296913 | Thomas et al. | Dec 2009 | A1 |
| 20090327263 | Maghoul | Dec 2009 | A1 |
| 20100001967 | Yoo | Jan 2010 | A1 |
| 20100009727 | Presutti | Jan 2010 | A1 |
| 20100011304 | van Os | Jan 2010 | A1 |
| 20100071423 | Dehaan et al. | Mar 2010 | A1 |
| 20100079380 | Nurmi | Apr 2010 | A1 |
| 20100082684 | Churchill et al. | Apr 2010 | A1 |
| 20100094939 | Cheng et al. | Apr 2010 | A1 |
| 20100105440 | Kruzeniski et al. | Apr 2010 | A1 |
| 20100123724 | Moore et al. | May 2010 | A1 |
| 20100127998 | Hyun | May 2010 | A1 |
| 20100145951 | Van Coeverden De Groot et al. | Jun 2010 | A1 |
| 20100156594 | Chaikin et al. | Jun 2010 | A1 |
| 20100159944 | Pascal et al. | Jun 2010 | A1 |
| 20100159995 | Stallings et al. | Jun 2010 | A1 |
| 20100162133 | Pascal et al. | Jun 2010 | A1 |
| 20100164740 | Lo et al. | Jul 2010 | A1 |
| 20100199359 | Cao et al. | Aug 2010 | A1 |
| 20100207723 | Cao et al. | Aug 2010 | A1 |
| 20100214237 | Echeverri et al. | Aug 2010 | A1 |
| 20100223097 | Kramer et al. | Sep 2010 | A1 |
| 20100235733 | Drislane et al. | Sep 2010 | A1 |
| 20100241971 | Zuber | Sep 2010 | A1 |
| 20100251116 | Rimas-Ribikauskas et al. | Sep 2010 | A1 |
| 20100257490 | Lyon et al. | Oct 2010 | A1 |
| 20100309149 | Blumenberg et al. | Dec 2010 | A1 |
| 20100317335 | Borovsky et al. | Dec 2010 | A1 |
| 20100325155 | Skinner et al. | Dec 2010 | A1 |
| 20110010656 | Mokotov | Jan 2011 | A1 |
| 20110035673 | Chou et al. | Feb 2011 | A1 |
| 20110035708 | Damale | Feb 2011 | A1 |
| 20110062143 | Satanek | Mar 2011 | A1 |
| 20110081922 | Chandra et al. | Apr 2011 | A1 |
| 20110169909 | Gu | Jul 2011 | A1 |
| 20110179387 | Shaffer et al. | Jul 2011 | A1 |
| 20120030287 | Leonard | Feb 2012 | A1 |
| 20120303712 | Polis et al. | Nov 2012 | A1 |
| 20120319985 | Moore et al. | Dec 2012 | A1 |
| 20130205243 | Rivera et al. | Aug 2013 | A1 |
| 20140082557 | Warner | Mar 2014 | A1 |
| 20140222577 | Abhyanker | Aug 2014 | A1 |
| 20140258897 | Shiplacoff et al. | Sep 2014 | A1 |
| 20150193132 | Fagans | Jul 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2008107675 | Sep 2008 | WO |
| Entry |
|---|
| “Global Framework—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, 166 Pages, Version 1.10, Last accessed Jun. 16, 2010. |
| “Global Framework—VD Specification,” AT&T Armstrong Project, 2009, Version 1.11, 117 Pages, Last accessed May 16, 2010. |
| “Phone Top—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.18, 104 Pages, Last accessed May 16, 2010. |
| “Phone Top—VD Specification,” AT&T Armstrong Project, 2009, Version 1.12, 52 Pages, Last accessed Jun. 16, 2010. |
| “Phone/Dialer—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.8, 57 Pages, Last accessed May 16, 2010. |
| “Dialer—VD Specification,” AT&T Armstrong Project, 2009, Version 1.7, 19 Pages, Last accessed Jun. 16, 2010. |
| “Contacts—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 2.6, 142 Pages, Last accessed Jun. 16, 2010. |
| “Contacts—VD Specification,” AT&T Armstrong Project, 2009, Version 2.2, 48 Pages, Last accessed Jun. 16, 2010. |
| “Third-Party Pickers—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.1, 23 Pages, Last accessed Jun. 16, 2010. |
| “3rd Party Pickers,” AT&T C@lumbus Project, 2009, Version 1.1, 7 Pages, Last accessed Jun. 16, 2010. |
| “Social—UE Flows and Screen Details,” AT&T C@lumbus Project, 2009, Version 1.5, 107 Pages, Last accessed May 16, 2010. |
| “Social—VD Specification,” AT&T C@lumbus Project, 2009, Version 1.5, 39 Pages, Last accessed Jun. 16, 2010. |
| “Media App—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.6, 118 Pages, Last accessed May 16, 2010. |
| “Media—VD Specification,” AT&T Armstrong Project, 2009, Version 1.3, 29 Pages, Last accessed Jun. 16, 2010. |
| “Mobile Share—Reduced Scope—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.2 RS., 59 pages, Last accessed Jun. 16, 2010. |
| “Mobile Share (Reduced Scope),” AT&T Armstrong Project, 2009, Version 1.2RS, 15 Pages, Last accessed Jun. 16, 2010. |
| “Camera App—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.8, 77 Pages, Last accessed May 16, 2010. |
| “Camera—VD Specification,” AT&T Project, 2009, Version 1.8, 22 Pages, Last accessed Jun. 16, 2010. |
| “Alarm Clock—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.4, 35 Pages, Last accessed May 16, 2010. |
| “Alarm Clock—VD Specification,” AT&T Armstrong Project, 2009, Version 1.4, 18 Pages, Last accessed Jun. 16, 2010. |
| “Settings—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.18, 180 Pages, Last accessed May 16, 2010. |
| “Settings—VD Specification,” AT&T Armstrong Project, 2009, Version 1.8, 40 Pages, Last accessed Jun. 16, 2010. |
| “Conversations—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.3, 148 Pages, Last accessed Jun. 16, 2010. |
| “Conversations,” AT&T Armstrong Project, 2009, Version 1.5, 54 Pages, Last accessed Jun. 16, 2010. |
| “Firmware Over the Air Updates—UE Flows and Screen Details,” AT&T Armstrong Project, 2009, Version 1.9, 39 Pages, Last accessed Jun. 16, 2010. |
| McDougall, “Browser,” AT&T Armstrong Project, 2009, Version 1.3, 6 Pages, Last accessed Jun. 16, 2010. |
| McDougall, “Maps,” AT&T Armstrong Project, 2009, Version 1.3, 8 Pages, Last accessed Jun. 16, 2010. |
| “Reference Guide—Icons,” AT&T Armstrong Project, 2009, Version 1.0, 4 Pages, Last accessed Jun. 16, 2010. |
| Henderson, Jr., et al., “Rooms: The Use of Multiple Virtual Workspaces to Reduce Space Contention in a Window-Based Graphical User Interface,” Jul. 1989, pp. 211-243, vol. 5, Issue 3, ACM Transactions on Graphics, Last accessed Jan. 14, 2015. |
| Foremski, “Panama: Kill Voicemail and Texting With Voice Messaging . . . ,” Silicone Valley Watcher, Apr. 26, 2010, 4 Pages, Last accessed Jan. 14, 2015. |
| Bosco, “Offical Google Blog: Receive and Reply to SMS Messages by Email,” Sep. 9, 2009, 7 Pages, Google, Last accessed Jan. 14, 2015. |
| Tedeschi, “Group Texting Grows Up, With Features That Appeal to Adults,” Oct. 20, 2010, 4 Pages, NYTimes.com, Last accessed Nov. 1, 2010. |
| Miller, “A Teenager's Dream: An iPhone App for Free Texting,” Bits Blog, Aug. 25, 2009, 19 Pages, NYTimes.com, Last accessed Oct. 13, 2009. |
| “Build and Grow With Facebook Connect,” 2009, 2 Pages, Facebook, Last accessed Nov. 2, 2009. |
| “Build and Grow With Facebook Connect,” 2009, 1 Page, Facebook, Last acceseed Nov. 2, 2009. |
| “Move Around on Your Phone”, pp. 44 and 57-58, Section 2B, Last accessed Nov. 6, 2009. |
| “MTN—Meeting the Needs of the South African Market for a New Mobile Messaging Solution—Mobile IM,” 5 Pages, Movius Interactive Corporation, Last accessed Nov. 2, 2009. |
| Kevin, “Social Web Aggregation,” Feb. 11, 2007, 4 Pages, b5media, Last accessed Nov. 6, 2009. |
| “Social Media Aggregation & Lifestreaming—All of Your Web Activity in One Simple, and Potentially Inconvenient Place,” Alexander the Late, Feb. 11, 2008, 3 Pages, Last accessed Nov. 3, 2009. |
| Schroeder, “20 Ways to Aggregate Your Social Networking Profiles,” Jul. 17, 2007, 20 pages, Last accessed Nov. 6, 2009. |
| Hirsch, “iPhone 2.0 Apps: The Social Networking App Comparison,” Jul. 17, 2008, 9 Pages, Last accessed Nov. 6, 2009. |
| “Lifestream: Bebo's New Social Media Aggregation Tool,” PDA The Digital Content Blog, Feb. 23, 2009, 3 Pages, Last Accessed Nov. 6, 2009. |
| “Social Network Aggregation,” Wikipedia, 3 Pages, Last Accessed Nov. 6, 2009. |
| “Your Conversation,” Jaiku, 2009, 3 Pages, Google, Inc., Last accessed Nov. 6, 2009. |
| “Personalized Recommendations to Help You Discover the Best of the . . . ,” 2 Pages, StumbleUpon, Last accessed Nov. 6, 2009. |
| “About Disney Interactive Media Group,” The Walt Disney Internet Group, 1 Page, Last accessed Nov. 6, 2009. |
| “Delicioussocial Bookmarking,” 6 Pages, Last accessed Nov. 6, 2009. |
| “Google Wave,” Wikipedia, 2009, 5 Pages, Last accessed Dec. 18, 2009. |
| “Motorola Backflip (TM)” Wireless From AT&T, 2 Pages, Last Accessed Mar. 29, 2010. |
| “Motoblur,” Motorola USA, 3 Pages, Last accessed Mar. 29, 2010. |
| Office Action dated Dec. 14, 2017 for U.S. Appl. No. 15/277,407, 58 pages. |
| Office Action dated Feb. 7, 2018 for U.S. Appl. No. 14/501,271, 14 pages. |
| Office Action dated Jul. 25, 2017 for U.S. Appl. No. 14/501,271, 60 pages. |
| Office Action dated Nov. 14, 2011 for U.S. Appl. No. 12/643,726, 59 Pages. |
| Spagnuolo, “How to Use Tweetdeck: The Ultimate Twitter Client,” Chris Spagnuolo's EdgeHopper: Tales from the Edge of Technology, Feb. 9, 2009,11 Pages, Last accessed Oct. 26, 2011. |
| Office Action dated Apr. 6, 2012 for U.S. Appl. No. 12/643,726, 43 Pages. |
| Office Action dated Jun. 12, 2012 for U.S. Appl. No. 12/903,618, 41 Pages. |
| Fitz, “AddressBooker & Exporting my Facebook Phonebook,” Brad's Life, Nov. 30, 2008, 9 Pages, Last accessed Jun. 19, 2012. |
| Office Action dated Aug. 1, 2012 for U.S. Appl. No. 12/903,632, 47 Pages. |
| Office Action dated Sep. 7, 2012 for U.S. Appl. No. 12/902,979, 63 Pages. |
| Office Action dated Feb. 11, 2013 for U.S. Appl. No. 12/902,979, 53 Pages. |
| Office Action dated Jan. 30, 2013 for U.S. Appl. No. 12/903,632, 28 Pages. |
| Office Action dated Mar. 13, 2013 for U.S. Appl. No. 12/643,726, 55 Pages. |
| Office Action dated Dec. 20, 2012 for U.S. Appl. No. 12/903,679, 40 Pages. |
| Office Action dated Jun. 13, 2013 for U.S. Appl. No. 12/903,382, 53 Pages. |
| Office Action dated May 14, 2013 for U.S. Appl. No. 12/903,414, 62 Pages. |
| Office Action dated Jun. 18, 2014 for U.S. Appl. No. 12/643,726, 55 Pages. |
| Office Action dated Aug. 23, 2013 for U.S. Appl. No. 12/643,726, 61 Pages. |
| Office Action dated Nov. 1, 2013 for U.S. Appl. No. 12/903,382, 30 Pages. |
| Office Action dated Sep. 26, 2013 for U.S. Appl. No. 12/903,618, 36 Pages. |
| Office Action dated Oct. 11, 2013 for U.S. Appl. No. 12/903,679, 22 Pages. |
| Office Action dated Aug. 26, 2014 for U.S. Appl. No. 12/903,618, 25 Pages. |
| Office Action dated Sep. 23, 2014 for U.S. Appl. No. 12/903,382, 32 Pages. |
| Office Action dated Sep. 30, 2014 for U.S. Appl. No. 12/643,726, 63 Pages. |
| Notice of Allowance dated Jun. 27, 2014 for U.S. Appl. No. 12/903,679, 29 Pages. |
| Office Action dated Jan. 31, 2014 for U.S. Appl. No. 12/903,679, 17 Pages. |
| Sprint, “Palm Pre Phone User Guide, ” 2009, 388 Pages, Palm, Inc., United States. |
| Office Action dated Jan. 28, 2015 for U.S. Appl. No. 12/903,382, 57 Pages. |
| Office Action dated Mar. 10, 2015 for U.S. Appl. No. 12/903,618, 24 Pages. |
| Office Action dated Sep. 14, 2015 for U.S. Appl. No. 12/643,726, 73 Pages. |
| Office Action dated Jul. 29, 2015 for U.S. Appl. No. 12/903,618, 24 Pages. |
| Gross, et al., “Information Revelation and Privacy in Online Social Networks,” Workshop on Privacy in the Electronic Society, Nov. 2005, pp. 71-80, ACM, Alexandria, Virginia, 10 Pages. |
| Office Action dated Dec. 2, 2015 for U.S. Appl. No. 12/903,632, 72 pages. |
| Notice of Allowance dated Jun. 28, 2016 for U.S. Appl. No. 12/903,618, 21 Pages. |
| Office Action dated Jun. 14, 2016 for U.S. Appl. No. 12/903,632, 31 pages. |
| Office Action dated Apr. 14, 2016 for U.S. Appl. No. 14/543,872, 92 pages. |
| Notice of Allowance dated Jun. 15, 2018 for U.S. Appl. No. 15/277,407, 28 pages. |
| Non-Final Office Action dated Jul. 20, 2018 for U.S. Appl. No. 14/501,271, 17 pages. |
| Office Action dated Apr. 8, 2019 for U.S. Appl. No. 15/426,813, 76 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160357374 A1 | Dec 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61251717 | Oct 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12643726 | Dec 2009 | US |
| Child | 15243459 | US |
