SYSTEM FOR BRIDGING, MANAGING, AND PRESENTING SMARTPHONE & OTHER DATA FILES WITH TELEPHONY INTERACTIONS

Abstract

A system for interfacing with mobile carrier networks, mobile application-equipped devices, social media networks, and individual and Enterprise user's databases, contacts, pictures, videos, and text is disclosed. A data link is connected to a mobile carrier network to receive user application and other data. Additional data links are connected to a user's stored smartphone content, including contacts, pictures, videos and other stored information as well as databases and an application-equipped device to obtain and exchange information in determining data selection, routing, presentation, and updating instructions. A user interface is connected to the system to accept configurable conditions for determining selection, routing and sharing instructions. There is a data conversion function for each data source. Synchronization between stored user preferences to automated or semi-automated updates and routes is provided by application driven consumer defined preferences.

Claims

1. A communications system for bridging, managing, and presenting user-selected personal smartphone data and social network stored data with user associated contacts at the onset of a smartphone telephony interaction, the system comprising: a first user data access point link in communication with stored user data for a plurality of users to transmit data therefrom; a second user data access point link in communication with the stored user data for the plurality of users to receive data therefrom; a user data proxy connected to the first user data access link and to the second user data access link; a rules engine in communication with at least one or both of the first user data access point link and the second user data access point link, the rules engine configured to match identified actionable characteristics with a prescribed set of processing rules; an application server in communication with the rules engine and either one or both of the first user data access point links and the second user data access point links, the application server configured to execute the set of processing rules matched with the identified actionable characteristics; and a remote data access point in communication with the application server and in communication with either one or both of the first user data access point and the second user data access point to communicate with users for executing the processing rules.

2. The communications system recited in claim 1, wherein the received and transmitted user data includes a data request, the system further comprising: a component database having stored prioritization levels associated with data request attributes; the application server being configured to assign a prioritization label to the data request in response to a query of a component database; the application server being configured to control the first user data link and second user data link.

3. The communication system recited in claim 1, further comprising a user interface in communication with either one or both of the first user data access point and the second user data access point and configured to display user information in accordance with the user data selected for visual sharing.

4. The communication system recited in claim 3, wherein the user data is formatted into a data stream transmittable to the recipient user based on preferences defined by the user being established thereby.

5. The communication system recited in claim 3, wherein a stored contacts schema of the user includes a sharing selection and association capability and an identifier of the user recipient.

6. A method for bridging and sharing specific user's personal data contained on smartphones, the method comprising the steps of: receiving a selection of personal data to be shared from a first user to a second user; identifying actionable characteristics associated with the personal data to be transmitted based upon an analysis of a user state of the first user; transmitting the personal data from the first user to the second user; identifying actionable characteristics associated with the user data to be received based upon an analysis of the user state of the first user; receiving personal data from the first user; comparing the identified actionable attributes with a database of operational instructions matched with stored actionable attributes to identify operational instructions associated with the identified actionable attributes; executing the identified operational instructions, the operational instructions including sending user data to a specified user; and executing the identified operational instructions, the operational instructions including receiving the user data from the specified user.

7. The method recited in claim 6 further comprising the step of storing the user data received from the user.

8. The method recited in claim 6 wherein the analyzing step includes identifying routing, origination or destination information associated with the user data.

9. The method recited in claim 6 wherein the analyzing step includes processing the user data with a rules engine to identify the actionable characteristics.

10. The method recited in claim 6 wherein identity is determined of consumer, phone unit, phone application, advertisers, and other sources and a memory and repository of each is created.

11. The method recited in claim 9 wherein the rules engine categorizes the identified actionable characteristics into predefined categories, the categories being associated with operational instructions.

12. The method recited in claim 9 wherein the rules engine analyzes the user state to determine the operational instructions.

13. The method recited in claim 6 wherein the comparing step includes determining the routing instructions for the data to be sent to the defined user.

14. The method recited in claim 6 wherein the comparing step includes assigning a prioritization to the operational instructions when the user's state meets a prescribed prioritization threshold.

15. The method recited in claim 6 further comprising the step of matching the received user data with stored user data.

16. The method recited in claim 15 wherein the matching step includes matching the received user data with user data associated with the sender of the user data.

17. The method recited in claim 6 further comprising the step of generating a display, depicting successful user transmission between the sender and receiver.

18. The method recited in claim 6 further comprising the step of generating an interactive user message template to accompany information contained in the user data.

19. The method recited in claim 6 further comprising the step of facilitating an assignment of a user post score associated with the user data.

20. The method recited in claim 19 further comprising the step of publishing user data and user post score associated with the user data to a social network.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] These and other features and advantages of the various embodiments disclosed herein will be better understood with respect to the following description and drawings, in which like numbers refer to like parts throughout, and in which:

[0020] FIG. 1 is a block diagram illustrating one embodiment of a system that connects and displays selected user personal smartphone data posts in conjunction with smartphone telephony interactions for selected smartphone contact records in accordance with one embodiment of the present disclosure;

[0021] FIG. 2 is a flowchart showing the steps of selecting, receiving, labeling, and storing user personal post data for use with selected smartphone contact records in conjunction with smartphone telephony interactions;

[0022] FIG. 3 is a block diagram depicting the system for connecting and displaying selected user personal smartphone data posts across multiple smartphone devices; and

[0023] FIGS. 4A-C are screen shots of a sequence of exemplary user interface displays of a smartphone application for use with the system that connects and displays selected user personal smartphone data posts.

[0024] Common reference numerals are used throughout the drawings and the detailed description to indicate the same elements.

DETAILED DESCRIPTION

[0025] The detailed description set forth below in connection with the appended drawings is intended as a description of the present invention. The description sets forth various functions in connection with the illustrated embodiments, but it is to be understood, however, that the same or equivalent functions may be accomplished by different embodiments that are also intended to be encompassed within the scope of the present disclosure. It is further understood that the use of relational terms such as first and second and the like are used solely to distinguish one entity from another without necessarily requiring or implying any actual such relationship or order between such entities.

[0026] With reference to the block diagram of FIG. 1, there is a system 100 that connects and displays selected user personal smartphone data with smartphone telephony interactions. In accordance with one embodiment, the communications system 100 is contemplated to bridge smartphone or otherwise stored personal data, smartphone telephony interactions and social networks. The system 100 includes smartphone user access point and data proxy 105, which are connected to various smartphone user interfaces and data 200-215. By way of example, there is a user A interface and data 200 that is connected to the user access point and data proxy 105 over a connection 500, a user B interface and data 205 that is connected to the user access point and data proxy 105 over a connection 501, and a user C interface and data 210 that is connected to the user access point and data proxy 105 over a connection 503. These three user interface and data are presented by way of example only, and any additional number of user interfaces and data may be connectible to the user data access point and data proxy 105, e.g., user N interface and data 215. The aforementioned data is understood to be that which is stored on the respective smartphones, or other stored personal data over carrier networks or social networks.

[0027] There may also be an enterprise data access point 160 connected to second data links 700, 720 to access additional system users. These include a smartphone 300 for a user A, which includes a smartphone interface 305 and a smartphone data 310 that is accessed by the interface via a data interlink 710. Furthermore, by way of example, there may be another smartphone 300 for a user B, which includes a smartphone interface 405 and a smartphone data 410 that is accessed via a data interlink 730.

[0028] As shown in FIG. 1, the system 100 includes an application server 110 that is connected to the incoming data access point, i.e., the smartphone user data access point and data proxy 105 as well as the enterprise data access point 160. The post data and routing information requests may be segregated based at least on configurable routing and storage instructions. The system may further include a component database 115 that is utilized by the application server 110 over an interlink 605. Additionally, there may be a rules-based engine 120, as well as integrations to APIs from other sources for automated categorization, routing, and storage. The rules engine 120 may be connected to the application server over an interlink 615. Additionally, the application server 110 is connected to the enterprise data access point 160 over an interlink 610, and the smartphone user data access point and data proxy 105 is connected to the application server 100 over an interlink 600.

[0029] Referring now to the flowchart of FIG. 2, one embodiment of a method 1000 for bridging smartphone users and enterprises to provide users customized visual data, content and offers will be described. In the exemplary embodiment, the user selects a contact in accordance with a step 1010. Furthermore, that user also selects or creates shared data in a step 1020. It is understood that this shared data may originate from various social networking services, specifically, the user content provided thereto and/or may be incorporated back into such social networks schema that allows users to share specific content and specific profile pictures with individual social network contacts, groups and/or desired recipients of any combination of people within their respective social networks.

[0030] The method proceeds to a step 1030 where the data access point 105, 160 processes the selected data. In accordance with a decision branch 1040, the availability of the selected contact is determined. If the contact is available, then the selected shared data is transmitted to the system 100. Otherwise, the shared data is updated when it becomes available in accordance with a step 1050. The shared data is stored in a database 1060 in accordance with a step 1055, then the shared data is associated with the selected contact in a step 1065. Various fields of the record associated with the selected contact on the smartphone are then populated with the shared data at the onset of a telephony interaction in accordance with a step 1070. Thus, data originating from social networking sites and other contemplated sources may be retrieved for this record field population operation.

[0031] If, in a decision branch 1075, it is evaluated that a rate data score option is to be presented, the method proceeds to a step 1080 of scoring the customer data. Then, updates are sent to a designated social networking service in a step 1090, and to the extent the customer data is scored, it is processed in a step 1095. The method also includes a step 1100 of saving the rate data into a database 1105. The method then ends 1110.

[0032] As indicated above, the present disclosure contemplates the sharing of different content for different users or subgroups of users. According to other embodiments of the disclosure, this may be applied in contexts other than mobile devices, such as, for example, the content shared on social networking sites or accessible via smartphone apps. More particularly, person A may see Profile Picture A of an individual, whereas Person B may see Profile Picture B of an individual within their social network and so on rather than everyone seeing Picture A. The dynamically varying content need not be limited to profile pictures, but also to update streams, comments, posts, and so forth, and each grouping of contacts may be designated to receive unique content as defined or segmented by the owner of the account. Continuing with the foregoing example, Person A who sees Profile Picture A, may receive Update Stream A, whereas Person B who sees Profile Picture B, may receive a different Update Stream B. In some cases, a mixture of content in Update Stream A and Update Stream B may be presented.

[0033] The block diagram of FIG. 3 depicts the system 100 on a more generalized level. As indicated above, the system 100 stores the aforementioned images, videos, and other content 1000 that is uploaded from the respective mobile devices and stored thereon for subsequent transmission. The mobile devices each execute a mobile application 1100, with a first mobile device running a mobile application 1100a and a second mobile device running a mobile application 1100b.

[0034] The screen shots of FIG. 4A-4C depict one exemplary user interface 1200 of the mobile application 1100 running on the various mobile devices that connect to the system 100 displaying selected user personal smartphone data with smartphone telephony interactions. Specifically, FIG. 4A is of an interface screen 1200a for contacts stored on the mobile device, and is a listing of names and associated contact information such as phone numbers, e-mail addresses, and the like that are arranged in alphabetical order. In addition to name information shown in a first column 1210a, this listing may also include an inbound visual data column 1210b and an outbound visual data column 1210c.

[0035] As indicated above, it is possible for certain personal data selected by a user of the smartphone initiating the telephony interaction to be presented on the non-initiating or receiving end smartphone at the start of the telephony interaction. In this regard, the user of the smartphone corresponding to the interface screen 1200a, e.g., “John Smith” may either initiate the telephony interaction or receive the telephony interaction initiated by another user. This user may designate an image or other visual data to be displayed, and an interface screen 1200b is the way in which this may be achieved. A main portion 1210 of the interface screen 1200b includes a selected image 1220, though other possible images may be designated via a selection interface 1230 that includes one or more reduced-size representations or icons of other visual data 1240. It will be recognized that selecting these other icons is operative to replace the main portion 1210 with a larger size representation of the selected visual data 1240. In this manner, the user may designate visual data to be presented to users on the receiving end of a telephony interaction, with the outbound visual data column 1210c including a further reduced representation of the selected visual data for that contact. For example, the contacts “Abigail Adams,” “Angel Ravit,” “Ariel Bloom,” “Bachar Eran,” and “Braun Miriam” are assigned the same image 1220.

[0036] When any of these users is on the receiving end of a telephony interaction initiated by the user, e.g., “John Smith,” as shown in an exemplary interface screen 1200c of FIG. 4C, the image 1220 is displayed. Along these lines, the inbound visual data column 1210b include reduced representations of visual data that the users corresponding to that contact have assigned for displaying on the current user's, e.g., “John Smith” smartphone when receiving a telephony interaction therefrom.

[0037] Although the foregoing examples variously refer to images presented to users, it is expressly contemplated that any data, including video data, audio data, text data, and any other data that may be visually represented may be substituted without departing from the scope of the present disclosure.

[0038] The particulars shown herein are by way of example only for purposes of illustrative discussion, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the various embodiments set forth in the present disclosure. In this regard, no attempt is made to show any more detail than is necessary for a fundamental understanding of the different features of the various embodiments, the description taken with the drawings making apparent to those skilled in the art how these may be implemented in practice.