JP6349328B2 - Access controlled interaction system and method - Google Patents

Access controlled interaction system and method Download PDF

Info

Publication number
JP6349328B2
JP6349328B2 JP2015552778A JP2015552778A JP6349328B2 JP 6349328 B2 JP6349328 B2 JP 6349328B2 JP 2015552778 A JP2015552778 A JP 2015552778A JP 2015552778 A JP2015552778 A JP 2015552778A JP 6349328 B2 JP6349328 B2 JP 6349328B2
Authority
JP
Japan
Prior art keywords
interaction
user
sender
message
messages
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2015552778A
Other languages
Japanese (ja)
Other versions
JP2016510459A (en
Inventor
ラフ ティモシー
ラフ ティモシー
ロウ ジェイソン
ロウ ジェイソン
Original Assignee
エバーニム インコーポレイテッドEvernym, Inc.
エバーニム インコーポレイテッドEvernym, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201361750634P priority Critical
Priority to US61/750,634 priority
Application filed by エバーニム インコーポレイテッドEvernym, Inc., エバーニム インコーポレイテッドEvernym, Inc. filed Critical エバーニム インコーポレイテッドEvernym, Inc.
Priority to PCT/US2014/010905 priority patent/WO2014110279A1/en
Publication of JP2016510459A publication Critical patent/JP2016510459A/en
Application granted granted Critical
Publication of JP6349328B2 publication Critical patent/JP6349328B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08User group management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • H04L1/1621Group acknowledgement, i.e. the acknowledgement message defining a range of identifiers, e.g. of sequence numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/70Admission control or resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/08Messages including annexed information, e.g. attachments
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/12Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages with filtering and selective blocking capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to network resources
    • H04L63/104Grouping of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/08Access security
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • H04W4/14Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/005Resource management for broadcast services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/30Network-specific arrangements or communication protocols supporting networked applications involving profiles
    • H04L67/306User profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • H04W4/029Location-based management or tracking services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Description

  The present disclosure relates to systems and methods for managing access to and interaction with user resources.

  The present disclosure provides, among other things, new communication and interaction methods that can solve many problems of interaction and / or mass communication among individuals, businesses and groups. Currently, individuals and other private information including personal IDs must be disclosed to one person when interacting with others or entities. For this reason, management of the person and other private information is lost, and management of access to the person and other private and resources is lost. For example, personal contacts such as email addresses and phone numbers must be disclosed to one person in order to contact others. However, if an individual's contact information is widely known or available, annoying contacts such as spam and telephone invitations may be received. The only way to get rid of annoying contacts is to change your personal contacts, which can be inconvenient, cumbersome, or impossible. Users are often hesitant to give personal contact information to merchants and the like because of annoying solicitations and other communication fears. When the merchant receives a “withdrawal” request from the user (for example, a request from the owner of the email address to not use the email address in the future), the merchant falls into the position of “protecting the henhouse” Often there is.

  Increasingly, children are increasingly involved in and relying on electronic communication with school teachers and others. In addition, children are particularly vulnerable to inappropriate or undesirable electronic communication, and a safe method of electronic communication is needed. Also, whether communication is done from home or from the office using a company phone or a personal phone, and the method (e.g. email, short message service (SMS), pager message, via smartphone) Employees, notifications, in-app messages on mobile, web or desktop applications, calls or APIs to external web services, client chat messages of various protocols, instant messaging (IM), voice, etc.) There is no cross-platform way to manage, monitor and / or record all electronic communications and use it in all situations.

In addition, especially in emergency communications, there are some limitations on the current method of communication between individuals. Automatic emergency or emergency communication to multiple disparate communication methods, from email messages to SMS messages and phone calls and / or repeated at regular intervals, etc. until the intended recipient confirms receipt There is no way to escalate (expand in stages). This leaves the sender of the emergency message with the option of manual escalation, that is, the option of trying different phone numbers, email addresses, other devices, other people one by one, but this It is only effective if the subscriber is subscribed to the same system as the required contact information and / or recipient (eg, subscribes to the same IM provider). Similarly, to receive emergency communications, their personal contact information must be made available to all potential senders, which is accompanied by the privacy issues described above.
Privately public interactions

“Privately public” interactions allow the user to use one interaction address, such as a communication address that does not need to change whatever the public address is, and others can use the user's other contact information (phone number) Without having an e-mail address, etc., the user can interact with the user in multiple ways: e-mail, SMS, MSS, IM, voice, video, personal computer, etc. In addition, the user can prevent an unauthorized person from interacting with the user and / or accessing user resources, even if the user has the user's interaction address. The ability of a person to interact with a user at any time without having to exchange interaction addresses can be disabled. This provides the user with privacy and management and others with a simple, convenient and effective means of interacting with the user. Furthermore, an interaction directed to one interaction address can be routed to the user via a phone number, IM address, email address, social media address, and the like. Only the interaction address, and possibly the access code, needs to be published for any method of interaction to be performed.
Interaction server

  Private and public interaction can be easily performed by the interaction server. The interaction server can manage interactions such as electronic or other communications between users, non-users and / or devices. Interaction server is application-to-application, email, SMS / MMS messaging, phone, fax, audio / video conferencing, webinar / screen sharing, instant messaging, mail, social media messaging and posted messages, data validation, data transfer, validation , Authentication, and / or any other method of interaction can be used for various methods of interaction. The interaction server can receive an interaction, such as an interaction request for the user, from a user or a non-user sender. The interaction request may be implicit. For example, the sender may simply attempt to send a message using a conventional paradigm without knowing that the user is interacting with the interaction server. The interaction request can be received at the interaction server via one or more of several methods such as application interface, email, SMS, phone, IM, web service, API, postal processing request. The interaction server is the user / recipient targeted for interaction requests, billing notifications, physical emails, etc. by one or more of several methods such as application, email, SMS, phone, IM, mail, etc. Can be routed to. The recipient can respond to the sender via the interaction server using the same or different methods. The recipient can respond to the sender in another way that does not use an interaction server. The history of all messages and / or interaction requests can be recorded or stored at that location or at a remote location.

In some embodiments, the message center may store transmission records and / or received interaction requests and / or messages. The message center can store these requests and / or messages even if a copy of the messages or interaction requests or links to them are routed elsewhere. The message center can include one or more data structures such as a database, list, stack, queue, etc. for storing messages. The user can log in to the message center and view the message. The message center may be displayed to the user in one or more mailboxes, folders, directories, lists, etc. Users can interact with messages accessed through the message center, including forwarding, responses, and so on.
Public and private addresses-single, unique public identifier

  The user can register a public address in the interaction server. This address can be in various forms, such as a string containing numbers, letters and / or other symbols or signs. The user can use the public address as a single, unique public identifier that is addressed to multiple types of interactions such as email, SMS, IM phone, mail, and the like. The interaction server can receive interaction requests such as communication requests and route them to user resources such as client devices or physical addresses specified by the user (the case of physical mail is described below). Client devices / locations can be identified by private addresses and / or user-running proprietary applications. Private addresses include information that is not visible to the sender of the interaction, such as email addresses, phone numbers, screen names, postal addresses, and social media addresses.

The public address can be modified and / or bypassed to successfully deliver the interaction request to the interaction server via different methods. For example, in the case of a user having a public address of SUPERMAN123, an interaction request may be sent to SUPERMAN123@example.com and sent to the interaction server via email. The interaction request sent to SUPERMAN123@example.com via SMS can also be received by the interaction server. The phone corresponds to dialing SUPERMAN123 directly by dialing a general number that the caller is instructed to provide SUPERMAN123, such as by dialing a specific number associated with SUPERMAN123, etc. Can be sent by calling application. This process can be automated using a smartphone app, which makes the process easier. For example, the user can simply select SUPERMAN 123 to indicate that he wants voice interaction. The IM may be redirected to an interaction server, redirected to a service compatible with the interaction server, or a proprietary IM service may be utilized.
rule

  The user can specify interaction rules that determine how to route incoming interactions. Interaction rules can be general or customized to a specific sender or group, category, or type of sender, such as a non-user, a new user, a user in a directory or group in a directory, etc. Good. The rules may be general or customized according to the type of interaction request received, such as speech, text, request. Rules include voice, text or physical mail communication or how and where to go; preference setting for confirmation notation; user location; allowed or preferred private address (phone number, e-mail address, etc.); access permitted, blocked or preferred senders; emergency and emergency message handling and / or escalation rules; block or hold all or some interaction requests until power outage Power outage period; time period during which access is permitted; when each method of interaction is permitted (eg, time, day of the week, etc.); whether personal contacts or other data are visible to other users and / or non-users Or how to display the sender in the contact's directory Or Shimesuru, and the like. The user can freely change the interaction rule.

  The interaction request can specify the type of interaction requested. The type of interaction requested includes common communication methods such as written messages, voice messages, live voices; desired specific communication methods such as email or telephone. The interaction server may evaluate a rule that sends an interaction request to one or more client devices specified by the user. For example, the interaction server can send a written message to an email address, route a telephone or fax to the appropriate telephone number, and so on. The interaction server can evaluate the interaction rules to determine if and / or how the client device has received the interaction request. Examples of client devices include telephones, pagers, computers, servers, smartphones, tablets, and portable information terminal devices. Therefore, the message by document can be transmitted as IM when the user is working, and as a text message when the user is not working. The user's location can be determined by GPS data, login status, time, cascading by device, and the like. The client device can execute an application for sending and receiving interactions.

  Instead of placing a traditional phone call, the “caller” need only use the app to request voice interaction with the interaction server. If the recipient is ready, he can accept the interaction and make a voice chat or phone call reliably. If the recipient is not available, the recipient may respond with a response time or duration, or may not respond at all. When the recipient becomes available, it can simply respond to the original interaction request and can reliably make a voice chat or phone call. If the original requester cannot respond by the time the recipient can respond, the original requester can similarly respond by displaying when it can respond. In this way, the interaction server facilitates efficient interaction and solves the problems related to the conventional “telephone tag (a state in which they are not in contact with each other)”.

  Using the interaction server, users can display their level of response, which is used for escalation and / or routing communication to or by various communication mechanisms or devices Can do. The user also chooses to publish the level of availability to all users and / or other trusted users to help individuals who want to interact with the user make predictions. be able to. Interaction escalation and routing are affected by the receiver's availability level, the recipient's confidence in the sender, and / or the sender's indicated urgency.

The person 1 can try to interact with the person 2 using a normal private address such as a normal telephone number or an e-mail address regardless of whether the person 1 is a user or a non-user. If person 2 prefers interaction using an interaction server, such service interaction can be automatically routed to the interaction server by the service provider, and this can be done again by restricting interaction rules such as restriction, routing, escalation, and approval. Can be applied. The interaction rules can be based on the original phone number, the original email address, time, etc.
access code

  The interaction server can restrict annoying interaction requests including annoying communications from being sent to the user. The interaction server can only allow certain interaction requests and not others. One way to manage access may be using access codes. The interaction request includes an access code, and the interaction server can determine whether the interaction request is authorized for the received access code. The interaction server may request registration of the access code with the interaction server before the access code is used by the sender. When the interaction server receives an interaction request with a new access code, it can dynamically assign the access code. An unlimited number of messages and / or an unlimited number of senders can use the access code. If the access code is functionally valid and the interaction request arrives without an access code, the sender can be prompted for input and / or the request can be ignored. The ignored request can be saved so that the recipient can select and view the blocked or ignored interaction request. The interaction server can reject and / or bounce the interaction request without a valid access code before the interaction server downloads the entire interaction request to save bandwidth.

  In one embodiment, when sending and receiving a documented message, the access code is added as a suffix or prefix to the local part of the email address and separated by special characters such as tilde (eg, “user1~56aQ1nE3@example.com”), The email message itself can be substituted for the interaction request.

  The user issues a valid new access code and is free to disable the access code if the interaction is no longer needed or if an annoying interaction request begins to arrive with a particular access code. If the interaction request does not have a valid access code, a bounce message and / or an instruction to enter the correct access code can be returned, and the user can not receive notification of the interaction request or attempt. If the access code is not functionally enabled by the user, an interaction request directed to the user's public address, including the access code or not including the access code, can be received by the user.

  Interaction rules can be specified for each access code. For example, a message with a specific access code can be treated as an unconfirmed interaction request, while specific rights can be granted to other access codes. For example, “4428” is the access code for an important new contact, and when this access code is used, that contact automatically becomes a trusted sender; “7726” is treated as spam and spam Or an access code that is routed to an unconfirmed inbox and / or tagged as spam; tag “soccer” as a new contact to the sender under the heading “soccer team” It can be an access code. For a particular access code, the interaction through all interaction methods may be authorized and / or only certain interaction types and / or methods may be used. Some access codes allow messages to be sent to a verified mailbox and / or allow live communication, while allowing one of these rights Some or none allow. In some embodiments, the interaction server includes an access code that is used to access the forwarded message, so that the user can filter the received message (eg, “soccer” into the soccer folder, “7726” Can be filtered to bulk folder). Alternatively or additionally, interaction requests can be sent to various inboxes based on the access code used. Based on the access code used, interaction requests can be stored, displayed, tagged, grouped, etc. in the message center and / or mailbox. The interaction request and / or message received with the access code may display or encode the access code used with the interaction request and / or message for user reference.

The interaction rules for access codes include the allowed interaction methods, how to handle emergency and emergency messages, whether such messages are allowed to be escalated, the frequency and sequence of interactions used during escalation. And the type, duration of access, when each method of interaction is allowed (eg, time of day, day of the week, etc.), can see personal contacts or other data, send the sender to the contact directory And how to display, how to display, how to format and / or how to handle responses to the sender, and so forth. The user is allowed to freely change the access code interaction rules, such as disabling the access code. Access code interaction rules can set default interaction rules for a particular sender, which can be changed, customized or maintained at a later time. For example, the sender can inherit the default interaction rule from the first access code used by the sender. Interaction rules can also be used to aggregate or consolidate messages from specific senders or groups of senders so that recipients can provide something like a “summary”. Instead of multiple similar messages that appear as separate messages, they can be combined into a single message so that the recipient can view a single message that combines multiple interactions.
Trusted sender

  Another way to use an interaction server to restrict access is to specify a trusted sender ("trusting"). “Trusting” can be used as such or in combination with other methods of restricting access, such as access codes (eg, an interaction server can selectively enable or disable trusting and / or access codes) Can be made). By using both trusting and access codes, there are two important benefits of "privately public" interactions: interaction addresses that are not afraid of unsolicited unsolicited interaction requests and do not disclose private addresses Can be used for public use. For example, if an annoying interaction request is received from a trusted sender, the sender can be put on an untrusted list and / or a blacklist to prevent further interaction. The interaction server can reject and / or bounce interaction requests from blacklisted senders prior to download by the interaction server to save bandwidth. If an unsolicited interaction request is received from a sender using a valid but untrusted access code, the access code does not affect future interactions with the trusted sender and changes the public address Can be disabled without need. In one embodiment, the trusted sender is required to use a valid access code for the user's received interaction request.

  The user can designate certain other users and / or non-users as trusted senders and automatically allow some or all of the communication and / or interaction requests from these users. Other users, email addresses, telephone numbers, email addresses, IM addresses, etc., and / or entities or accounts that own one or more of these addresses can be designated as trusted senders. Messages from new senders and / or new addresses may be flagged, grouped, identified or marked until the user establishes a trust level. The sender can be designated as trusted before or after sending the interaction request to the user. The interaction and / or communication address can be designated as trusted before or after the user receives an interaction request and / or communication from them. Senders and / or addresses can be specified individually or as a group from a list, directory, file, folder, database, etc. as trusted. All domains, subdomains, zones, area codes, zip codes, ranges, etc. may or may not be trusted (eg blacklisted). The user may define rules to trust the sender based on, for example, automatically trust any recipient that the user has previously sent a message, and / or perform steps Also good.

  A communication and / or interaction request from a trusted sender does not contain an access code in the interaction request or contains an incorrect access code and / or the access code is fully functionally disabled You can even allow it. Authenticate trusted senders via login process, digital signature, prove IP and / or email address is not spoofed, Sender Policy Framework (SPF) records, prove third party verification can do. An interaction rule can be specified for each trusted sender and / or a default interaction rule can be used for multiple trusted senders. Interaction rules for trusted senders include: allowed interaction methods, how to handle emergency and emergency messages, whether such message escalation is allowed, how long as a trusted sender, When each method is allowed (for example, time of day, day of week, etc.), whether the trusted sender can see the user's personal contacts or other data, or whether the trusted sender is included in the contact's directory , Or how to include, how to format the response to the sender, and / or how to handle it, etc. The user can also blacklist other users, non-users and / or any kind of interaction address, block all communications and / or interactions, and revoke previously granted permissions. Blacklist users can remain blocked even if they try to interact with a new private address and / or valid access code. The user is free to change the trusted sender's interaction rules, including invalidating the status of the trusted sender or modifying the trust and / or permissions.

  Automatically trust third parties trusted by the first user's trusted senders ("Senders trusted by my trusted senders") by the interaction rules, trust on a case-by-case basis, Only certain types of interactions can be trusted. When this rule is disabled, a common acquaintance is needed for referrals. A user can send a request for trust to another user without a valid access code, but may only allow a limited number of trust denials before the ability to send a request for trust status is disabled. Can not. The sender's trust can be cloud-sourced based on the trust decisions made by other users. When a user decides whether to trust the sender, the trust statistics of decisions made by other users can be shared with the user and / or the user is based on other users' trust decisions Rules on whether to automatically trust the sender can be established.

  Use different mailboxes, folders, labels, tags, flags, groupings, etc. to identify messages from trusted and untrusted senders among various trusted senders it can. For example, a verification or trusted inbox holds messages from trusted senders, while another inbox holds messages from untrusted senders. Alternatively or additionally, messages can be stored, displayed, tagged, grouped, etc. based on the sender's trust level and / or access code usage. If an untrusted sender is designated as trustworthy, the type, display, tag, etc. of the message sent by that sender can be changed. For requests for live voice or video, trusted callers are allowed to call the user, while untrusted callers are automatically routed to voice email or other messaging systems, or they An alert is sent to the user instructing his / her identity and / or instructing to provide an access code and / or attempting to make a call.

Create temporary and / or temporary accounts for interaction requests received from non-users, thereby enabling the trusting process with or without user or non-user side actions receiving the requests can do. This method allows the user to interact with non-users using trusting, communication integration, confirmation delivery, and other features of the interaction server. Some features and capabilities enjoyed by users include instructions to acknowledge receipt by including links or buttons in non-user email messages, non-users receiving and / or confirming their messages Available to the non-user when the non-user interacts with the user and / or escalation until the confirmation is received between the non-user's known interaction address and / or device and / or Be available. Users and non-users can mark messages with hashtags and / or other symbols to take advantage of Interaction Server features (eg, task assignment #task (described below), emergency message # urgent (described below). Non-users with provisional accounts are provided with a means to switch their provisional account to a permanent account and consolidate multiple provisional accounts into one regular account.
emergency

  Prior to this disclosure, Person 1 who interacts electronically with Person 2 is Person 2's known interaction address (phone number, Skype (or similar service), user name, email address, SMS number, IM name. Etc.) and had to try the interaction. If the interaction attempt was unsuccessful, Person 1 had to try another address (if it was known). When interacting via an interaction server, the person 1 is a user, whether it is a voice or a character, whether it is a voice or a character, a user, a non-user, to interact via most types of interactions. Need only one public address (if the user activates an access code and / or trusting, a valid access code or prior authorization as a trusted sender is also required). Person 1 does not have to own the phone number, email or other address of the user who is trying to interact, and further, the user's multiple addresses and / or types of communications (such as voice or document) You can try until you are successfully connected to the user.

In one embodiment, person 1 can select the user's public address, the type of interaction desired (such as voice or text) and the emergency level. If no urgent is displayed in the interaction, it can be defaulted to normal or low. The interaction from the person 1 can be processed according to the interaction rule for the urgent user set in the interaction server. For example, when person 1 designates a message in a document as a normal emergency message, the user rule can designate e-mail as a suitable delivery means for text / document messages in a normal emergency. A message from person 1 indicated as high urgency can trigger high emergency delivery to the user, such as repeated SMS messages, simultaneous or sequential dialing of multiple phone numbers.
escalation

  A user can give other users, non-users, and / or zones (as defined below) the right to send an emergency or other emergency message to him. The user can establish a specific access code as an emergency or emergency access code. The access code, sender, zone and / or another field of the interaction request indicates that the message is an emergency message and / or the message has a specific emergency level (low, normal, emergency and emergency) An emergency indicator can be included.

  When a user receives a message with an emergency indicator, the interaction server repeats it sequentially or simultaneously to a plurality of addresses and / or devices by a plurality of interaction methods (for example, voice, text, etc.) at a predetermined interval. To escalate the emergency message. The interaction server can continue to escalate until the message is confirmed. The urgent message can be sent sequentially by a plurality of interaction methods, with a predetermined interval between transmissions by each interaction method, and / or the urgent message can be sent through each set of simultaneous transmissions through the selected interaction method. Can be sent with a predetermined interval between them. When users look at their message center and / or inbox, the message may be illuminated, such as red, to indicate that it is currently escalated. The interaction server can be configured to change the volume of the alert device (e.g., change the volume of the smartphone from static to maximum), vibrate, flash, etc. to alert the user. The emergency message can be escalated to the user's spouse, family, co-workers, etc., or even a red person nearby. The user may snooze the emergency message and escalation may be delayed at a predetermined and / or user indicated snooze interval. The user can send a confirmation or confirmation message to the interaction server to end the escalation. The interaction server can provide confirmation or confirmation, or a report of the absence to the sender of the message.

  The interaction server can help contact the target user using GPS or other location-aware technologies. The interaction server can escalate emergency messages to other users who are physically close to the user. For example, if a user receiving a notification does not notice the notification because their mobile phone call is turned off or the battery is dead, other users nearby receive an alert and receive the alert. You can look for and tell your message. Location data may be used to dynamically change the order of escalations. For example, if the user is at the office, the office phone number and IM account are alerted first, and if the user is at home, the order of escalations is dynamically changed to provide a fixed phone number and personal IM account. Can be alerted first.

The user can define escalation rules and settings that determine which interaction methods to use, the order in which these interaction methods are used, the interval between issuing emergency messages, and the like. The user can select escalation settings for each sender, zone and / or access code, and / or the user can use default settings for multiple senders, zones, access codes, etc. If the sender abuses the emergency right, the second user can invalidate or modify the emergency right. All messages from the sender can be handled as non-emergency messages. Alternatively, the user can allow escalation only during certain times of the day, some days of the week, or weeks of the year. Conversely, if the sender is considered by the recipient to be a very important person (VIP), such as the recipient's child or the recipient's boss, certain or all types of interactions may Regardless of the emergency indicator included with it, it can be automatically escalated or the identified emergency level can be automatically updated to a higher next emergency level or the like.
Relationship

The interaction server can authorize relationships between parents and children, employers and employees, colleagues and colleagues. The parent account can manage the interaction rules and access to the child account. In this way, the guardian can specify a trusted sender, issue and disable access codes, establish and modify interaction rules, use other accounts and manage access, and the like. The guardian can choose to hold all interaction requests destined for the child or all unverified interaction requests and hide them from the child. The parent can then approve the interaction request before sending them to the child. The guardian may choose that an interaction request from a specific trusted sender and / or including a specific access code is sent to the child without requiring approval. In this way, parents can provide their children with a safe and controlled way and enjoy the benefits of electronic interaction.
zone

  Users can use zones to associate their accounts with companies or organizations. Zones allow zone owners or administrators to manage the look and feel (look and feel) of their member interactions and to monitor content. Organizations can register zones on interaction servers. An organization can associate specific users with a zone and generate these user-specific addresses that can be used with the zone. A unique address used with a zone (eg "Sam.Jones {company1}" containing the zone in curly braces) works like the public address described above and can be exchanged with this address, limiting interaction requests And a trusted sender is identified. For example, user Sam Jones may use “Sam.Jones {company1}” and “1234” when providing his zone's provided public address with a valid access code. Similar to the previously described "private public" system, once the sender is identified as a trusted sender, the access code is no longer needed and the trusted sender can successfully interact with Sam using "Sam. "Jones {company1}" is enough.

  The unique address with the zone may be part of a new user account or may be associated with the user's existing account. A unique address with a zone can be associated with an existing account only if permission is granted by the account owner. When the user's organization is no longer relevant, the user may be removed from the associated zone. A user can be associated with multiple zones. For example, user Sam Jones can use “SamJones123” as his personal public address while associating it with “Sam.Jones {company1}” and “CoachJones {soccerteam1}”.

  An email message can be addressed to “Sam.Jones{company1}@example.com”, for example, including the zone in curly braces. The email address with the zone and access code is like Sam.Jones{company1}~1234@example.com. When an organization's email communication is forwarded to an interaction server for processing, email messages from trusted senders should be sent to sam.jones@company1.com, for example, without requiring a zone in curly braces It becomes a “private public” interaction that is transparently provided to the organization's interaction within the email format.

  Users are allowed by the zone administrator to manage certain aspects of their zone-related interactions, but not others. For example, the user is allowed to manage some or all of the rules for receiving interactions or identifying trusted senders, but for other things such as interaction look and feel, editing specific contacts in the zone directory, etc. Rules or configuration modifications are not allowed. Users can sign in to the zone's associated personal account or access the zone through a separate sign-in process established by the zone. Even if a zone is associated with a personal account and a user can access the zone with that personal account, the zone administrator cannot have access to the user's personal account.

  The interaction server can separate interactions according to each zone and by non-zone interactions. The user ensures that only work calls and work emails will receive calls and messages addressed to the zone associated with that work, and / or the user sets default interaction rules for both zoned and non-zoned interactions Alternative interaction rules for each zone can be specified, such as Contacts can also be divided by zone. In this way, interaction requests sent to contacts associated with a zone can be automatically branded with a predetermined signature, look / feel, return address, and the like. For contacts associated with multiple zones, the user can select which zone and / or brand to apply. The interaction server may also determine phone usage associated with zones and phone usage associated with non-zones, allowing organizations and users to accurately calculate usage, costs, and the like.

  One or more users with zone administrator and / or owner privileges can specify zone settings and / or view and manage all interactions and data associated with the zone. Zone administrators and / or privileged users include adding associated users to groups and / or subgroups within the zone; sending interaction requests based on groups, subgroups, physical locations, departments, etc. , Interaction with associated users; removal of users from the zone; global changes that affect all associated users; designation and removal of trusted senders; management of access codes; Forced channel subscription; withdrawal of a user from a channel and / or permission to join a channel; sharing of a directory among associated users, groups, subgroups, etc .; any interaction method for alignment, etc. A record of all interaction requests sent by Allow and disallow features within the zone, such as subscribing to and storing files; creating standardized web and / or social media pages for each associated user; assigning and monitoring tasks and projects; Requests can be submitted.

Zones are unconstrained interactions between some or all of the zone members; directory sharing with contacts; file sharing and data repositories; application sharing and collaboration; virtual bulletin boards; shared calendaring, etc. Can be used to link interactions with features and functions.
Requests, assignments, tasks, projects

  Emails, SMS messages and handwritten letters are typically constructed without any special original structure. Users can configure new interaction requests as unstructured or create them using formats, templates and / or tools such as requests, assignments, solicitations, notifications, forms, multiple selections, blank padding, Or can be used. The recipient of the interaction request responds according to the received structure, such as “Yes” or “No”, approval or rejection with or without additional conditions, multiple selections, blank filling, filling in forms, responses with unstructured messages, etc. can do. If multiple answers are requested from the user, multiple interaction requests and / or messages can be delivered in separate responses required for each. The received interaction request can be saved based on whether a response is required.

Interaction requests formed as assignments, tasks, etc. can be integrated with a task or project management system. Recipients can accept, reject, or respond to requests for assignments or task requests. The requester can look at the answers and track the progress of the task and / or project. Tasks and / or projects can involve multiple parties such as requesters, actors, sponsors, contactees, helpers, and the like. Approved and / or invited parties can be notified of or allowed to interact with task and / or project data and / or other parties. Communication, notifications, other workflows, and other actions are specific events or thresholds such as task completion, new comments, answers to queries, attachments or other data, imminent or overdue, external data Can be triggered by the occurrence of Tasks, projects, conversations, actions, etc. can be stored in the interaction server and / or provide local copies for offline access and other purposes, and these copies are later synchronized when online access is restored Can be made.
Work flow

Interaction servers can facilitate simple or complex workflows. Users can create electronic forms and processes for workflows using built-in custom or external tools, templates, and the like. A workflow process can include a series of steps performed by an interaction server. For each step, it is necessary to satisfy certain conditions before performing the step. For example, the accounting department can create an expense clearing form and embed a workflow process in the interaction server. The first user can fill out the form, which can trigger an alert for approval to the manager. The manager's approval triggers an alert to the accounting department and issues a refund to the first user. A payment notification is sent to the first user, who can receive the payment. All parties can retain access to permanent records of all aspects of the workflow process, including requests, responses, dates, names, approvals, rejections, comments, attachments, notifications, etc.
Assign incoming messages

The interaction server can be configured such that, for example, when a customer interacts with a customer service department, the interaction can be easily performed on a one-to-many basis or a multi-to-many basis. Multiple individuals can be received and given corresponding rights to interaction requests received by one or more user accounts, such as, for example, staff within a customer service department. Interaction requests can be automatic and / or manual and can be broken down by priority, urgency, VIP sender, etc. Interaction requests can be automatically or manually assigned to one or more approved individuals. Once assigned, the interaction request cannot be serviced by others, the request is moved to a queue, marked with a specific status, and / or classified as another interaction request. Interaction requests can be forwarded and / or escalated in several ways: increased priority, sent to and / or assigned to various individuals, departments or services. Escalation occurs due to various reasons such as response time delays, emergency indicators, VIP senders, and so on. The interaction between two parties begins in one form, such as text, and can be moved or changed to another form, for example, when a party wants to initiate a phone call, video conference, etc. The means of interaction for the interaction request need not be the same for each party performing the interaction. For example, the sender wants to talk by email, while the receiver chooses to display video to the sender, or vice versa. Senders or recipients may wish to keep their personal contact information, real ID, or other information. The sender or receiver can request that specific information be disclosed or shared as a condition of interaction. The interaction server can be used for file transfer, screen sharing, participation in real-time messaging, and / or collaboration in other ways. Access to a permanent record of each interaction can be retained for each party.
Simultaneous notification / group interaction

The simultaneous notification system can be configured to send communications to addresses contained in a contact database. The simultaneous notification system can be used mainly for emergency and / or emergency notification, but it can also be used without emergency communication. There are some major limitations to the simultaneous notification system. The bulk notification system needs to collect and maintain a database of contacts and “push” notifications to the group, but the target recipients may have a potential privacy breach, a sense of security from self-satisfaction and / or Due to the inconvenience of having to manage the same information in multiple separate systems, such as in towns and schools, people are increasingly reluctant to provide personal contacts. In addition, maintaining accurate contact information quickly falls into a never-ending and frustrating battle due to group member movement, disconnection or number changes, email address changes, withdrawal from groups, and the like. Furthermore, using the simultaneous notification system for emergency evacuation is convenient for adding the landline telephone number obtained from the telecommunications carrier to the contact database, but using the landline telephone is a voice over IP ( As VoIP) and mobile phones are becoming more and more popular, there is a big gap that the resident's phone number that needs to be notified cannot be found. The bulk notification system is expensive and may be limited by small groups such as small schools, small towns, small organizations, teams and clubs, and families. Social media tools allow free communication by multiple users. Social media tools do not have the headaches of collecting and maintaining databases in a batch notification system, but social media tools are used effectively by escalation, confirmation (verification of receipt), dynamic segmentation and batch notification systems. Does not provide other features necessary for emergency notifications.
channel

A user can establish one or more “channels” that facilitate interaction between groups, including broadcast notifications. Users can subscribe to the channel and receive broadcast messages without revealing their private addresses, personal contacts, their real names, etc. Therefore, a user who can broadcast on the channel can interact with the viewer without restriction without knowing the subscriber's private address, personal contact information, telephone number, e-mail address, real name, and the like. Interaction data sent or posted to a channel may be transferred or “broadcasted” to one or more subscribers of that channel in multiple ways, including application, email, SMS, IM, telephone, mail, etc. Can do. Broadcast messages can take the form of multiple formats including recorded audio, live audio, text, video, announcements, requests, questions, prompts, and the like. Subscribers can automatically receive channel interactions without an access code. The subscriber can choose how to receive the channel message and respond to the message using the same or different methods. Channel managers and / or subscribers can personally send interaction requests to other subscribers of the channel or access information about other subscribers.
Join the channel

  The channel can be hosted by an interaction server and / or the channel can be hosted by another server and / or entity. A user with an interaction server account can subscribe to channels hosted by the interaction server and / or channels remotely hosted. The interaction server may comprise an API that allows a remote channel hosted by another server to broadcast a message to users with an interaction server account and users subscribed to the remote channel. In some embodiments, the interaction server may use an API to authenticate another server and route the received message to the user's message center. When a user subscribes to a channel, the user's personal data and / or the user's trust list can be updated to reflect the subscription. The interaction server may inform that the user is not subscribed to the channel, such as by rejecting an interaction request from a channel the user is not subscribed to, and / or sending a bounce message.

  If the user wants to subscribe to that channel, the channel can request access to a specific private address or other data (for example, mail if attempting to join a marriage channel set up by a married couple) Request access to the destination). The requested information is made available to channel managers and / or other subscribers, such as by creating a directory from the requested information, and who has access to who wants to subscribe has access Can tell you. Admission rules determine other required criteria such as required information, location, family relationships, team lineage, age restrictions, parental permissions, number of subscribers, answering security questions, holding passwords, etc. can do. For example, parents seeking to join a channel for a child's school classroom are required to submit verification data such as their name, child's name, password, and child's birthday. The channel can be configured to automatically approve all subscribers that satisfy the enrollment rules and / or require the channel manager's permission before accepting the subscription. The channel manager can also delete a subscriber.

  Each subscriber can set their own interaction rules, for example, similar to the interaction rules for receiving non-channel interaction requests. For example, these interaction rules include the device receiving the message, whether the channel has emergency rights, the handling of emergency messages, including the frequency and order in which additional devices or users must receive the message, and power outages This includes the period for which the message is blocked or retained. The subscriber can set custom rules for the channel or can use default rules. The interaction server may request confirmation of receipt of the message and / or confirm whether delivery has been achieved. Interaction rules can determine how to handle unconfirmed messages. For example, some users may not allow messages to be escalated even though they have never confirmed. Users are free to cancel their subscription or change their rules.

  Some channels allow users to join a channel only by email address, SMS number, telephone number, etc. without explicitly creating an account with the interaction server. The channel manager can add and / or invite subscribers to the channel individually or from lists or directories. Applications can provide access to electronic directories and other applications to facilitate the subscriber recruitment process. Users can be notified that they have been invited to join the channel. Subscribe to non-users, for example, by sending them a button or link in an email message, or by providing a non-user with a channel name and prompting them to search for it online or by application Can be recommended. Non-users can subscribe to the channel without creating temporary and / or temporary accounts, thereby taking action on the non-user side. This method allows all subscribers to receive broadcasts by their account, email address, SMS, phone, etc. Provisional subscribers can respond to broadcasts or be counted as part of a channel statistics report. Provisional subscribers can switch their provisional account to a permanent account and may be provided with a means to consolidate multiple provisional accounts into one permanent account.

For example, when a user enters a predetermined area, the user can automatically subscribe to the local Amber Alert channel. The user can automatically cease to subscribe to channels that are no longer interested or subscribed, or can suspend some or all future automatic subscriptions. A user can create multiple channels. Each channel can have a web page and / or web presence, which can be used by subscribers and / or the public so that visitors know about the channel, subscribe to the channel and receive broadcasts In response to broadcasts, the user can view past broadcasts, view statistical data and other information about channels, view related files, and view related videos. Channels can be found by direct link, search, browsing, etc.
broadcast

  Broadcasting can be initiated by authorized users in a number of ways, such as using applications or APIs, text messages, email or phone calls, or other interactions. A channel can have a specified email or other address, in which case messages received at that address are automatically broadcast on that channel. Subscribers can respond to the broadcast, and their response is or is not broadcast on that channel. Some channels broadcast important emergency and / or emergency messages to subscribers. Messages displayed as urgent trigger the subscriber rules for urgent message delivery and are thereby enabled / disabled and / or customized for each channel they subscribe to. For example, an emergency message can be escalated until confirmation or confirmation is received. Like one-on-one emergency interactions, emergency channel messages are close in several ways, eg, try multiple devices, try the same device repeatedly, use multiple means, sequentially or simultaneously It can be escalated by alerting other users, alerting multiple recipients until confirmed, etc. Subscribers can also snooze messages to delay escalation. The subscriber can end the escalation by sending a confirmation or confirmation message to the interaction server. The interaction server can provide confirmation or confirmation to the broadcast sender, channel manager, etc., or can indicate that there is no confirmation / confirmation.

  Some channels allow all subscribers to broadcast messages to some or all other subscribers, and only certain subscribers and / or channel managers can broadcast messages on those channels. Some channels are available. Some or all subscribers can escalate messages to channel managers and / or other channel subscribers. Messages from subscribers received by the channel can be assigned for handling as described above. Channels can be permanent, such as clubs, families, associations, companies, departments, schools, local governments, or temporary, such as teams, classes, weddings, etc. . The channel can be used to initiate a voice or video conference call, including dial out / dial in to the subscriber. The channel can also be used as a chat room or to receive immediate queries and answers from a large group of people, such as receiving polls or answers in a live broadcast on television or stadium. The channel supports question and answer formats such as “yes” or “no”, multiple choice, blank filling, free answer, etc., and can provide statistical data to the channel manager and / or broadcaster in real time. Channels can facilitate two-way interaction between broadcasters and recipients through multiple interaction methods including text, audio, video, etc., which can be used for family, team, club, class Useful for small groups such as. Channel interactions can be recorded or monitored. Some channels are charged and you can check the subscription status before sending a message to the subscriber.

  Channels can be used to broadcast news feeds, newsletters, blogs, podcasts, and more. The broadcasted message may include an attachment that the subscriber can open. The subscriber has a reader and / or multimedia player, which can receive and interact with messages sent by the channel. Subscribers can retrieve data from channels such as private channels, private data from other subscribers, private data from channel managers, and the like. The purpose of the channel is to allow subscribers access to private data.

  Channels can be used to create subscriber directories. For example, any directory channel subscriber can interact with other subscribers. Directory channels can be set up by school, town, state, country, etc. for students. A directory channel may, for example, allow only non-urgent document messages and / or require subscribers to publish certain contacts and / or allow certain types of interactions from other subscribers, etc. , You can limit the types of interactions allowed. Directory channels can be annoying, such as identifying the number of trust denials that are allowed before a subscriber can no longer interact with other subscribers, and identifying trusted crowdsourcing parameters. Subscribers can be protected from communication.

  Subscribers can also specify rules that interact with other subscribers in the directory channel, including the type of interaction allowed; the restriction of the subscriber's geographic area allowed to interact; from the directory channel Includes filtering of all interactions to a particular folder, labels and / or mailboxes, etc. Subscriber rules for directory channels can blacklist or whitelist specific users, groups of users, user categories such as merchants' profile / interesting merchants, user geography, etc. . The subscriber can leave the directory channel and / or block all interactions from the subscriber to the directory channel. The subscriber can choose to include the trust status in the personal user override rule for the user group that contains the personal user, and / or the subscriber chooses to prompt for instructions if a conflict occurs. be able to.

Channels also allow subscribers to interact with shared data. For example, a potluck style channel can include a list of items that a subscriber selects or signs up on a first-come, first-serve basis (eg, a list of dishes for a potluck dinner). ). Channels can have calendaring capabilities including calendars linked from integrated calendars and / or other channels or calendaring systems. The broadcast message can have a calendaring element that includes the ability for the subscriber to automatically insert events into the calendaring system. Notifications can be automatically triggered when an administrator adds a new event. Administrators can trigger broadcasts by tapping or editing calendar events. Linked channel events have scheduled reminders that can be escalated, snoozed, rejected, and confirmed.
Dynamic split

The channel may also allow for dynamic partitioning of subscribers so that messages can be broadcast to only a subset of subscribers. For example, when sending a message, a broadcaster can select a criteria and automatically send the message only to subscribers that meet the criteria. The criteria can include private information, which the interaction server knows but the broadcaster does not know. For example, the channel manager cannot determine which subscribers meet the criteria, but the criteria can specify that messages be sent only to recipients over the age of 50. Criteria include location (eg, evacuation orders for people currently in a specific area or persons with a permanent residence in a specific area), zones, groups, and / or subgroups, age, gender, new / recent membership Subscribers (eg, users who have started subscribing to a channel within a certain period of time), subscribers with special profiles or products of interest. Broadcasters do not need to group subscribers in advance before specifying criteria. If broadcasters send messages based on conditions where some subscribers have not identified the relevant data, these subscribers will not have channel message information because they lack information about their subscriber profiles or preferences. You can be notified that it may not have arrived. Once the appropriate information is entered, the original communication is delivered to the subscriber.
Mail merge

The channel can provide a mail merge type function to the broadcaster. Broadcasters can integrate data into messages from databases, lists, and so on. For example, the broadcaster can enter “Dear {$ NAME}” to reference the name field and add the name of the intended recipient to each message. The data can include subscriber private data stored in the interaction server. In one embodiment, broadcasters can integrate data that they do not have access to, and broadcasters cannot see messages generated by the integration process. Alternatively, if the broadcaster needs the right to integrate private data into the message, the broadcaster can be instructed to determine whether to request data from subscribers who do not allow broadcaster access. Information that requires more protection (eg payment information, etc.) may be prohibited from integration by the interaction server and / or the subscriber and / or may require permission from the subscriber before being integrated, Information that does not require much protection (such as last names) can be integrated and / or does not require permission. The application used to compose the message can display available fields and / or can display fields that are prohibited from integration or need permission.
Automatic message

Automatic messages can be sent to individual users by channel. For example, an automatic message can be sent as a reminder at a predetermined time or as an alert for a scheduled event (eg, a birthday or anniversary, a reminder to vote, an air filter replacement reminder, etc.) When certain conditions occur (eg, server crash, reaching stock price, approaching pedophile, sale of desired goods on website, reaching certain threshold for monitoring temperature, by certain user Message receipt, alarm or alert trigger, etc.). The interaction server can receive, retrieve and / or calculate data and use it to determine whether a predetermined condition has occurred. Condition data can be retrieved from emails, calendars, data providers / servers, file servers, databases, websites, web services, APIs, message centers, other channels, and the like. For example, an aggregator promo channel can forward promotions from individual retailer channels. Automatic channel messages can also be combined with dynamic segmentation to send smart messages to subscribers that meet certain criteria. For example, a car service chain can send a message to a user within the radius of the service center that an oil change is required. The date of the most recent oil change can be stored on the interaction server and / or the car service chain can determine which users need an oil change. It is also possible to broadcast communications on a channel using an automatic mechanism. The automatic server can directly interact with the interaction server using a web service or API, and can eliminate the need for direct human interaction in message transmission.
Location-aware message

  The interaction server can use the location data to process channel messages and / or one-to-one interaction requests. For example, the interaction server may receive from the user location data determined by a global positioning system (GPS) receiver of the client device. The interaction request may indicate that the delivery of the message is delayed until the intended recipient enters a specific area, eg, within a specific distance of the delivery location. Channel messages can be filtered by location and / or delivered automatically upon entering a predetermined area (eg, emergency blame orders, advertisements from local businesses, etc.). For example, if a chain store opens a new store, customers may be able to subscribe to the chain store on the channel, but may not want to give their address to the chain store. The interaction server allows the chain store to open a new store, all subscribers with an address near the new store, and / or the GPS location of the subscriber is constant from the store within a certain period of time. If it falls within the distance, the subscriber can be notified. The interaction server can utilize user defined rules or other criteria to select which client device receives the interaction request based on the received location data. When deciding when to send a message, the location and / or orientation of the subscriber and / or the speed of travel can be considered. For example, a local coffee shop may want to broadcast a promotion for a new product when a subscriber approaches and arrives in about 60 seconds.

A user may be required to sign in to an interaction server when entering a WiFi network (eg, a coffee shop or hotel WiFi network). And even if users have disabled location-aware capabilities such as GPS, they can receive emergency notifications at their location, and / or user interaction rules can provide location-based intelligent interaction request routing Can be done. Temporary and / or temporary accounts can be created for those who do not have an account.
Blind mailing service

  The user's private address may include one or more postal addresses. The user may wish to receive the mail without leaking the mail address and / or the broadcaster may wish to send the mail without collecting or maintaining a database of addresses. The sender can send the electronic message to the target interaction server as mail to one or more recipients without owning the recipient's postal address. The interaction server can determine the mail address of the intended recipient. If the interaction request identifies the recipient and / or sender's zone, the interaction server may use the appropriate “to” and / or “from” address to send the item, etc. Branding, labeling, etc. can be determined (eg selection of work address or home address). The interaction server may comprise one or more devices configured to print messages, print the correct zip code on an addressed envelope, and pack the envelope. The interaction server can allow the sender to select first class postage, priority mail, next day delivery mail, and the like. The one or more devices may be configured to perform labeling and stuffing operations on envelopes or boxes for physical items received by blind mailing services. In one embodiment, the interaction server can send blind mail without using the device by sending or providing access to all necessary information to the third party for fulfillment.

In order for the user to receive a physical “blind” mail or “blind” package (in this case, the sender does not know the recipient's postal address) that is not an electronic message, the item is addressed to the user's public address. Can be sent to a central processing place. Bar codes, QR codes, etc. can be used to facilitate routing. When the goods are received at the central processing location, the sender is authenticated, the recipient's rules allow the goods to be received from the sender, and the interaction server can query the recipient's postal address. , You can mail or ship the item to its final destination. In this way, a “blind” mailing of the physical item is achieved, in which case the sender does not need to know the recipient's actual postal address and the recipient does not need to leak it. Alternatively, a mailing or delivery provider, such as the US Postal Service, may provide tools to authenticate the sender and retrieve recipient address information and / or access to an interaction server. In this way, the delivery provider provides a seamless blind mailing service that eliminates the need to mail and deliver the item twice (first to the central processing location and to the final destination).
Dashboard

Channel managers and / or message broadcasters can view and receive channel-related data through searches, dashboards, summary reports, real-time reports, tickers or banners, alerts, notifications, and the like. Channel-related data includes real-time statistical data, historical statistical data, the percentage of users who have confirmed message reception, the number of subscribers, new subscribers, past subscribers, past notifications, responses, and attachments. Channel-related data includes predefined statistical fittings or custom criteria, such as subscribers of a certain gender of a specific age, married subscribers, subscribers in a specific region, subscribers with a specific product preference Some subscribers make specific responses. Each user's interaction rules can specify how much of the user information is published in the channel related data.
Reverse search shopping

  Prior to this disclosure, the online shopping model was not very useful for local shopping, optimizing search engines to launch websites, initiate pay-per-clicks, and / or attract more people to the site Given the cost of campaigns, blogging, video creation, and maintaining website updates, it was costly and time consuming for local merchants. As a result, instead of using online shopping, shoppers drive their cars to go to the store, call the store, and / or find the goods they purchase in local advertisements. It is advantageous for local sellers to communicate directly with interested local shoppers at low cost, without having to create a website. With the interaction server, shoppers do not need to visit the seller's website, drive anywhere, leak contact information, and / or do not need to know the seller's phone number or web address , You can interact anonymously directly with the seller. Furthermore, the merchant only has to pay a service fee when interacting directly with the shopper. Furthermore, the interaction server allows the contract to be concluded and / or paid safely.

  In some embodiments, when a shopper initiates an interaction, the merchant can bid on the bid words by displaying the amount they are willing to pay. The merchant can also create a list of bids by uploading or providing real-time access to product inventory and / or other data. Shoppers can post what they want to buy on the interaction server. The shopper can request a match at a particular location, such as within a particular radius from the shopper's location. The interaction server may return a list of matching products by comparing the bid document with the post and / or comparing the seller's location with the location specified by the shopper. The highest bidder can be listed first. Shoppers can search and categorize results based on third-party website ratings. The shopper clicks on the list and can use the interaction server and / or another site for additional information including images, videos, descriptions, advertisements, useful information, etc. (eg merchant information, third party products) Evaluation). Shoppers can anonymously initiate an interaction with the merchant via text, chat, voice, video, and the like. There is no charge for the merchant until the interaction begins. If the shopper's posts do not match, the interaction server can save the posts until the seller bids on the matching bid document. The shopper is alerted of the match. The shopper can also choose to save the post. Saved posts allow more results to be accumulated and more sellers to find shoppers. Alternatively or additionally, merchants can manually search for posts and advertise to shoppers. Merchants can also be alerted when a shopper's post matches their bid, but they can't initiate an interaction with the shopper.

An interaction request from a shopper can be answered by a seller and / or others such as a salesperson. The shopper can specify a general method of interaction, and the merchant can select a specific method of interaction and / or a device for performing the interaction. For example, a shopper can identify a voice communication and the merchant can choose to escalate the communication from an office phone to a mobile phone or the like until the communication is answered. Shoppers and / or merchants can publish both their public and private addresses, or neither. Shoppers may always want to interact with sellers anonymously, while sellers may always want to be as open as possible. For example, in communications, the shopper wants to talk to the seller over the phone, and the seller can be contacted by text from the shopper without exposing the private or public address, while the seller Are viewed by shoppers via video conferencing. Merchants don't need a website to interact with shoppers and don't publish phone numbers. Instead, the merchant need only have a telephone and / or computer. In some embodiments, a phone or computer app can be used. If the merchant has a website, the app allows the merchant to interact with the website visitors. With respect to video conferencing, merchants can show stores, themselves, products / models of interest to shoppers, etc., while shoppers may choose not to display video or identify themselves it can. The interaction server can manage payments such as down payment or full payment, including payment escrow and maintenance of paper trails (detailed below). The interaction server can also store a copy of the contract between the seller and the shopper. The shopper and seller can submit each other's evaluation to the interaction server when the transaction ends.
payment

  The interaction server can also be used to facilitate payments between users and non-users. Payers and / or payees may not share payment and / or private information (username, email address, phone number, credit card number, bank account number, etc.) with each other. Trading capabilities do not require commercial capabilities such as point-of-sale (POS) capabilities. As a result, users can make payments instantly and easily and / or receive payments to other users or non-users, or even payments from them, and are unreliable It is possible to prevent the user from receiving unauthorized payment. For example, a potential payee can send the requested amount, desired payer, desired payment type (eg, credit, check, etc.), etc. to the interaction server. The payment request can be sent via an application by e-mail to a specific address, an automated teller machine, a push phone, or the like. The payee can use a location-aware app that automatically makes a proposal to the payer for the transaction in the domain. Once a payment request is made, the payer can receive a payment request notification, decide whether to approve the transaction, and / or specify a payment source, amount, category, payment details, and the like. Similarly, a transaction can be initiated by a payer attempting to send payment to the payee. For payer-initiated transactions, the payer specifies the payment amount, payment source, category, details, etc. and specifies the desired payee (for example, a location near the payee, such as a store where the payer is lined up at the checkout) You can specify and initiate a payment (by selecting from the aware generation list). Recipient receives payment, can apply it to contracts, invoices, purchase orders, etc., deposit it to a specific account, forward to another recipient, refuse payment, etc. It can be performed.

  The payee can include a general indication of the desired or required payment source (eg, the payee prefers funds over a checking account or prefers credit card payments). A payer can select a specific payment source when responding to a payment request. Personal payments and account information from various sources can be stored on the interaction server. Personal payment information includes credit card numbers, electronic check information (eg, bank fulcrum code and account number), online payment service access and / or address. If the payer approves the charge, the interaction server may submit a specific amount of the charge to a payment processing system associated with the payment source specified by the payer, such as an automatic clearing house (ACH), credit card processing system, etc. it can. Alternatively or additionally, the account balance display of the account managed by the interaction server can be updated based on the transaction and provided to the user. Upon completion of payment, a summary of receipts or other interaction history can be saved to a storage device or other storage medium within the interaction server and made available to one or more parties and / or other desired parties of the transaction. Can be.

  The parties to the transaction can select the required user authentication level. For example, before releasing a payment, the payer can re-login the recipient to their user account, answer one or more security questions, pass biometric security, receive third party verification, etc. Can be requested. Before the user is allowed to use the payment and / or contract function, an extended validation can be performed to confirm the user's ID and prevent personal information thieves. Extended verification includes voucher matching, credit check, notary letter receipt, etc. by a trusted user. Users may not be allowed to store their passwords and / or if they use payment and / or contract features, they must choose a longer and / or more secure password than usual There is.

  Payment requests can be sent as phone calls, text messages, emails, and notifications via applications that can run on smartphones, tablets, personal computers (PCs), and the like. The authorization response can be made by touching a key during a call, sending a response text message or email, responding via a smartphone app, submitting an answer via a website, voice recognition or other biometric authentication. Pins and / or passwords and / or other authentication information and / or processes may be required for authorization of the interaction. The payer can automatically designate approved recipients and / or individually approve or reject payment requests to unauthorized recipients. The payer can pre-authorize a specific or maximum amount to be paid to a specific payee during a specific time period or within a specific area. For example, to save waiting time at the cash register, the payer can pre-authorize the store where the payer is shopping to charge up to $ 50 and the authorization lasts only one hour.

  The payer's ability to pay can be similarly limited by the parent's linked account or related zone. For example, a child is pre-authorized by a parent to use up to $ 20 for a specific recipient or category of recipients within a specific range from the house, only from a specific account, for a specific time window, etc. be able to. Similarly, employees may use a specific amount to entertain a client, to a specific recipient or recipient category, from a specific account, for a specific time window, etc., depending on their associated zone. Can be pre-authorized.

  The user can attempt to pay or charge the user or non-user for payment. Non-users can receive an email or other message informing them of the charge. A non-user may be asked to respond to a transaction and / or complete a transaction with or without creating a user account. Non-users can complete a transaction by making payments by any means, such as cash, check, credit or debit card, setting up a user account, authorizing transactions with their financial institutions by any number of means . The user can be notified electronically of whether the transaction has been completed or rejected, or the user can manually record how the transaction has been terminated. Records of transactions and payments for all related events can be stored in the interaction server, making copies, receipts and / or other information available to related parties.

  In some embodiments, the interaction server can optionally serve as an escrow agent for transactions. Depending on the payment settings specified by the payer and / or the payment request, the interaction server can determine whether to act as an intermediary. If the interaction server functions as an intermediary, the payers can keep their payment information secret and only provide the public address. Payers can also make anonymous payments, keeping their personal contacts secret. With respect to escrow payments, a specific amount request sent to the payment processing system may designate the interaction server as the recipient of the funds. The interaction server may initiate and / or approve a second transaction to transfer funds from a source associated with the interaction server to the recipient.

  Alternatively or additionally, the payer can provide payment information to the payee and the interaction server can manage the transaction that is about to be performed with the payment information. For example, a merchant may attempt to charge a credit card and the charge is automatically rejected by the payer's bank. The payer's bank can inform the payer via the interaction server that the charge attempt has been attempted and / or has been rejected. The payer sends a reply approving the request. The merchant then tries again and is successfully processed. Alternatively, the merchant may attempt to charge for the first time and the request may not be approved or rejected until an answer is received from the payer. In one embodiment, the payer can preauthorize the merchant for a specific or maximum amount. Pre-authorization has limitations such as time, location, and specific vendor. Billing that requires a PIN, such as billing to a debit card, as a backup can be granted without a response from the payer. The interaction server can store a copy of all payment requests, authorization responses, billing approvals, etc. and provide a paper trail.

The interaction server allows users to use their smartphones, tablets, and / or other similar devices as point-of-sale devices. Users can use their smartphone application to scan the bar code, QR code, etc. of the desired item, add it to the electronic shopping cart, and / or immediately cease the purchase, and then discontinue the purchase. You don't have to line up. Electronic or printed evidence of purchases, receipts, etc. can be printed, displayed, stored by the interaction server, or made available to both buyers and sellers. Near field communication (NFC), GPS and / or other location-aware and wireless technologies allow users who carry their smartphones or other devices for transactions and have proof of purchase to trigger crime detection devices You will be able to leave the store without losing time, without the intervention of store clerk, and waiting for cash register.
Agreement

  The interaction server can also be used for contract negotiation and execution. The user may want to accept a contract in which a permanent record is stored, and / or one or more users may want approval of the action before the action is performed. The storage device can store an indication of the contract and / or approval. The first user can send a contract request to the interaction server, including a contract or description of the action that requires approval. The contract request is forwarded to the second user by the interaction server for authorization. When the contract request is approved by the second user or by both users, the interaction server stores the contract request and the date and time of each approval in a storage device as a temporary or permanent record of the contract. Can do. The interaction server may make the contract and / or receipt available to both users. The same process is useful when two or more parties contract or multiple approvals are required before an action is performed.

  The user can make changes to the contract before agreeing, and the change history with the recorded time can be stored in the storage device. An example use of a contract is when an automobile mechanic requires approval when performing additional work on a vehicle, or when two parties sell a used car privately. Credit providers and / or agencies may also require approval before opening a new account to prevent identity thieves. Credit provider and / or trusted agency credit may require authorization to open an account. The interaction server can create a template that can be used by the parties to create a contract, such as a voucher template for vehicle sales, a written letter, a borrowed certificate (IOU). For parties that do not have an account on the interaction server, a provisional account can be created automatically. Provisional account owners can be sent a link so they can manipulate the contract and interact with the other party without signing up for a full account. Once the parties have made the edits, the contract can be printed and signed.

Contracting parties can select the required user authentication level prior to completion and / or conclusion of the contract. For example, one party may re-login to their user account, answer one or more security questions, go through a security biometric form, receive a third-party verification form, meet, There may be a case where it is required to confirm the identity.
Web presence

  The interaction server can store personal data and other data in a storage device, and the data can be used as web presence. Data can be used by public means, but access to the data can be restricted. The entity can submit an interaction request specifying the data the user desires. The user allows certain trusted senders and / or access codes to automatically access the data. Users can request their authorization / approval before data is shared. If the requested data is not stored in the storage device, the interaction server can instruct the user to provide information. The data includes shipping and / or billing addresses, health records, demographic information, personal contacts, advertising preferences, browsing preferences, authentication data, answers to questions, and the like. The user can authorize the entity to attach and / or add new data to the user's web presence.

  For example, address and health records can be accessed from entities that require such information. Magazine or newspaper publishers can verify a subscriber's address before sending a new publication. A health-related provider can download a patient's health record, ask the patient for new information, and / or attach the new information to the record. In addition, the user can select an entity to receive automatic updates of information. Once the address is updated on the storage device, the update will be immediately available and / or accessible to the newspaper and magazine publishers booked for purchase, the bank with the account, friends and family .

The interaction server can manage the sharing of other information shared by the user with a directory of contacts or other users. Changes to the shared private contacts can be immediately viewed by other source and / or trusted users and / or new changes can be automatically communicated to the shared directory. With regard to the personal health record, the user can update it with new symptoms, and the updated personal health record is immediately available to the doctor. The doctor also submits an interaction request, such as an interview, to the user, which can be attached to the personal health record along with the answers to the questions. Some entities have access to modify private data and / or can submit private data update requests. In this way, a hospital with access rights can update an individual's health record and can send such updates to other hospitals and health providers selected by the user.
Profile, interest and safety browsing

Users can maintain profiles in an interaction server available to advertisers. Profiles include advertising preferences, products of interest, demographic information, location information, user-selected interests, browsing preferences, and the like. When a user browses the Internet, a browser, cookie, browser plug-in, etc. on the user's client device displays the user's public address, which causes a web page and / or advertiser to request profile information from the interaction server, and Information can be obtained from the interaction server. Information can be transferred as a highly compressed preference map. Alternatively or additionally, the user can log in to an account that is managed by the interaction server or has access to the interaction server at the start of browsing, and the browser is requesting a web page or during other services, Public address can be sent. In this way, an advertisement of interest can be shown to the user, blocking unwanted content such as pornography or violence, or browsing the entire undesired website. However, there is no need to publish other private data due to the preference being performed. The advertisement can include one or more management buttons so that the user can update preferences or cancel unwanted advertisements. The parent account can manage the child account's advertising and browsing preferences so that only sites that are age appropriate and / or authorized by the parent can be visited. Profile information can be shared with authorized merchants, websites and other organizations at the request of the user. The shared information may be general information applicable to multiple websites and / or such information may be site specific. The user can also allow direct interaction requests from the website / organization, set restrictions on the interaction, and / or block the interaction freely. Users can allow an organization to ask new questions or receive answers to their profile and / or interests and attach new fields and / or information to their profile.
Authentication and account integration

  As an additional functionality, the interaction server can store usernames and passwords for multiple websites, online accounts, etc. When a user visits a web page, the form filler can automatically fill in the login name for that web page with a username and password. Alternatively or additionally, the website executes an application programming interface (API), which allows the interaction server to authenticate the user. In an exemplary embodiment, the user can log into the interaction server and the website can communicate with the interaction server to verify the user's identity. Websites and interaction servers can communicate according to OpenID standards, OAuth standards, proprietary standards, and the like. The website may direct the user to the interaction server for login and / or the user may first log in and be automatically authenticated upon reaching the website. Once authenticated, users can use the website just as they normally use it.

The authentication and access of profile information works synergistically to benefit both users and websites. For example, a website called “Runner's World” would give users an account on the website in order to access the content they want and sell their profile, interests and interaction preferences. Request to create. A user may be a passionate runner who does not want to create another online account. Also, when visiting runnersworld.com, a user logs in with an interaction server account and is immediately authenticated and identified by doing so. The interaction server also provides Runner's World with access to the user's profile and product preferences, as well as ways to interact directly with the user, and the user is free to disable it. The interaction server account allows this user to instruct Runner's World to enter additional running preferences from time to time, and these preferences and responses are not stored within the runnersworld.com website, but within the interaction server. Can be reviewed and maintained. In this way, Runner's World gains access to valuable information about the runner and a way to reliably interact with the user. Users don't need to create a separate online account, they can protect their privacy, manage what private data Runner's World has accessed, and whether Runner's World interacted with the user Final management can be retained. Users can then share the same information with additional distributors in the running industry, rather than maintaining accounts in multiple locations.
utility

The interaction server can also provide cloud, collaborative services and tools. The interaction server can provide users with calendars, word processing, spreadsheets, presentation capabilities, flowchart creation, and the like. Users can share and edit calendars and documents, collaborate, and plan events. The storage device can store calendars, documents, images, notes, backup files and other files. The interaction server allows storage for sharing files that are too large for email and / or forwarding between users. The interaction server can provide translation capabilities for interaction requests while composing messages during transmission, after reception, and the like.
Definition

  “Interaction” is defined broadly herein, including communication, interaction with another person's information or file, interaction with a shared file or workflow, interaction through any method described in this application, etc. included. An “interaction request” includes any initiation of an interaction with or without a message, either synchronous or asynchronous, by any mechanism or means. As used herein, the term “communication” refers to voice communication, text communication, physical mail, electronic request for interaction, response to request, all records of conversation or interaction, attachment, notification, broadcast, response, Shows answers, choices, etc. “Messages” include documents, audio messages, video messages, data, etc., necessary to achieve an interaction request, and can be structured or unstructured.

  The interaction server and / or client may comprise a processor. Alternatively or additionally, the interaction server and / or client can be executed by a computer system. Embodiments can include various steps, which can be embodied in machine executable instructions executed by a computer system. The computer system includes one or more general purpose or special purpose computers (or other electronic devices). Alternatively, the computer system can comprise hardware components that include specific logic circuitry for performing the steps, or can comprise a combination of hardware, software, and / or firmware. Computer systems include workstations, laptop computers, removable mobile computers, servers, mainframes, clusters, so-called “network computers” or “thin clients”, tablets, smartphones, personal digital assistants or other portable computing devices, “ A “smart” consumer device or device, or a combination thereof, can be provided without limitation. Servers include physical servers, server clusters, distributed servers, virtual servers, cloud servers, computer-provided resources for one or more clients, and one or more combinations of the above. Some or all of the functions, steps and / or operations described herein may be performed by one or more clients rather than an interaction server. One skilled in the art will be able to divide operations between the interaction server and one or more clients.

  Each computer system includes at least one processor and memory, and the computer system can include various input devices and / or output devices. The processor may include one or more general purpose central processing units (CPUs), image processing units (GPUs) or digital signal processors (DSPs) such as Intel®, AMD®, Nvidia®, ATI. (Registered trademark), TI (registered trademark), or other "commercially available" microprocessors. Processors include ASICs, PALs, PLAs, PLDs, field programmable gate arrays (FPGAs) or other specialized processing devices such as customized or programmable devices. The memory may be static RAM, dynamic RAM, flash memory, ROM, CD-ROM, disk, tape or magnetic, optical or other computer storage means. Input devices include keyboards, mice, touch screens, light pens, tablets, microphones, sensors or hardware with firmware and / or software. Output devices include monitors or other displays, printers, voice or character synthesizers, switches, signal lines or other hardware with firmware and / or software.

  The computer can use floppy drives, tape drives, optical drives, magneto-optical drives, memory card readers, or other media that read storage media. Suitable storage media include magnetic, optical or other computer readable storage devices having a specific physical configuration. Suitable storage devices include floppy disks, hard disks, tapes, CD-ROMs, DVDs, PROMs, random access memory, flash memory and other computer system storage devices. The physical structure represents data and instructions that cause a computer system to operate in a specific and predetermined manner, as described herein.

  Embodiments can also be provided as a computer program product, which includes a non-transitory machine-readable storage medium, which is a computer (or other electronic device) for performing the processes described herein. Instructions that can be used for programming are stored. Non-transitory machine-readable storage media for storing hard drives, floppy diskettes, optical disks, CD-ROMs, DVD-ROMs, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, tapes, solid state memory devices or electronic instructions There are other types of suitable / machine-readable media, but are not limited to these.

  Suitable networks for the configurations and / or uses described herein include one or more local area networks, wide area networks, metropolitan area networks, and / or “Internet” or IP networks, such as world wide networks. There are web, private internet, secure internet, value added network, virtual private network, extranet, intranet, or a standalone machine (so-called “sneaker net”) that communicates with other machines by physical transport of media. In particular, a suitable network can be formed from part or all of two or more other networks, including networks that use different hardware and network communication technologies. One suitable network includes one server and several clients, other suitable networks include servers, clients, and / or other combinations of peer-to-peer nodes, and a given computer can be both a client and a server Can function. Each network includes at least two computer systems, such as servers and / or clients.

  The network includes communication or networking software such as software available from Novell, Microsoft, Artifot and other vendors, using TCP / IP, SPX, IPX and other protocols, twisted pair, coaxial or fiber optic cable, telephone It can operate on lines, satellites, microwave repeaters, modulated AC power lines, physical media transfers, and / or other data transmission “wires” known to those skilled in the art. The network can include smaller networks and / or can be connected to other networks by gateways or similar mechanisms.

  Suitable software to assist in the practice of the present invention includes the teachings described herein and, for example, Java, Pascal, C ++, C, PHP, JavaScript, Python, C #, Perl, SQL, Ruby, Shell, Visual Using programming languages and tools such as Basic, Assembly, Action Script, Objective C, Lisp, Scala, Tcl Haskell, Scheme, database language, API, SDK, assembly, firmware, microcode, and / or other languages and tools Readily provided by those skilled in the relevant art. Appropriate signal formats are in analog or digital form, using error detection and / or correction bits, packet headers, network addresses in a particular format and / or other basic material readily provided by one skilled in the relevant arts. Can be implemented with or without use.

  Some aspects of the embodiments are described as software modules or components. As used herein, a software module or component can include any type of computer instructions or computer-executable code residing in a memory device. A software module is one of the computer instructions that can be organized as, for example, a routine, program, script, object, component, data structure, etc. that performs one or more tasks or executes a particular abstract data type. Or it can comprise a plurality of physical or logical blocks.

  In certain embodiments, a particular software module includes different instructions stored in different locations of a memory device, different memory devices, or different computers, which together perform the functionality of the modules described. Certainly, a module contains one or more instructions and is distributed over several different code segments, various programs, and several memory devices. Some embodiments may be performed in a distributed computing environment where tasks are performed by remote processing devices that are linked by a communications network. In a distributed computing environment, software modules can be located in local and / or remote memory storage devices. In addition, data related to or rendered in a database record may be in the same memory device or across several memory devices and linked together through a network to a record field in the database. Can do.

  Most of the infrastructure that can be used in accordance with the present invention is available, such as general purpose computers, computer programming tools and technologies, computer networking and networking technologies, and digital storage media.

FIG. 6 is a schematic diagram of an interaction server configured to allow controlled interaction with access from a sender; Fig. 4 is a flow chart of a method for processing an interaction received by an interaction server; FIG. 6 is a flowchart of a method for processing an interaction for a child public identifier linked to a parent account; FIG. 6 is a flowchart of a method for sending an interaction to a recipient user resource using a location-based interaction rule; 1 is a schematic diagram of a system configured to broadcast a message to multiple channel subscribers; Fig. 4 is a flowchart of a method for joining a new subscriber to a channel; 1 is a schematic diagram of a system configured to send a message to a channel subscriber; FIG. 4 is a schematic diagram representing an escalation rule to a user; FIG. 2 is a schematic diagram of a system configured to send a message to a plurality of dynamically partitioned channel subscribers; 1 is a schematic diagram of a system configured to send automatic messages to interested channel subscribers; 1 is a schematic diagram of a system for interaction between multiple channel subscribers.

  FIG. 1 is a schematic diagram of an interaction server configured to allow private public communication of recipient 160. The senders 151 and 152 transmit an interaction such as an interaction request to the interaction server 100. The user 152 having an account of the interaction server 100 may be one of the senders 151 and 152. The senders 151 and 152 include a person, a computer that operates autonomously, and a computer operated by the person. The interaction request includes an address and / or a public identifier (eg, a public address), an access code, a payload (eg, a message), and the like. The interaction request is first processed by the authentication / identification module 102. Authentication / identification module 102 requires login authentication information from user 152 and verifies that non-user sender 151 has not spoofed their ID. If the senders 151, 152 are authenticated and / or identified, their interaction request is communicated to the authorization module 110. Otherwise, the interaction request can be rejected, deleted, and flagged.

  The authorization module 110 can determine whether an interaction request from the sender 151, 152 is authorized for delivery to one or more user resources associated with the recipient 160. If interaction requests are not authorized, they can be deleted (drawn in trash bin 130). The authorization module 110 can also be configured to classify interaction requests between one or more user resources, such as one or more inboxes 121, 122. If the senders 151, 152 are on the trust list 112, an interaction request can be sent to the trust inbox 121. If the interaction request is authorized (eg, with a valid access code or interaction rule that specifies that all interaction requests must be sent to the recipient 160), the interaction request can be sent to the unconfirmed inbox 122. . In the illustrated embodiment, the inboxes 121 and 122 are separate mailboxes. In other embodiments, all authorized interaction requests can be stored in the message center with tags, fields, etc. that indicate whether the interaction request is from a trusted sender. In one embodiment, the unconfirmed inbox 122 is a holding area that is not visible to the recipient 160, and a request to the recipient 160 to trust the senders 151, 152 can be sent to the trusted inbox 121. For a sender 151 who does not have an account on the interaction server, the provisional account module 116 can create a provisional account before the interaction request is delivered to one of the inboxes 121, 122.

  The interaction server 100 can include an interaction notification engine 120. The interaction notification engine 120 is configured to periodically check the trusted and / or unconfirmed inbox 121, 122 and / or message center to see if new interaction requests and / or messages have arrived. be able to. The interaction notification engine 120 can store or access an interaction rule that is used to determine how to handle a new message. When a new message is detected in inbox 121, 122, interaction notification engine 120 notifies recipient 160 that a new message has arrived; escalates the message until recipient 160 confirms them; If you can not. When notifying recipient 160, interaction notification engine 120 may include a message, a copy of the message, a preview of the message (eg, a predetermined number of characters at the beginning of the message), a link to the message, and the like.

  Recipient 160 can access inboxes 121, 122 and / or an integrated message center (not shown) to view messages therein. When viewing an unconfirmed message, the recipient 160 can be instructed to determine whether the senders 151, 152 are trusted. Until a trust decision is made, the recipient 160 may or may not be allowed to respond to the message. Recipient 160 can respond with “yes”, “no” or “probably” when deciding whether to trust senders 151, 152. The recipient indicates that the sender 151, 152 is trusted, adds the sender 151, 152 to the trust list 112, moves any message from the sender 151, 152 to the trusted inbox 121, and / or Can be tagged, grouped, or identified as trusted. The “probably” response makes the sender 151, 152 partially trusted and / or gives the sender 151, 152 limited trust privileges. If the recipient 160 indicates that the senders 151, 152 are not trusted, the interaction request can be discarded. If the recipient 160 is receiving an undesirable message sent with a particular access code, the recipient 160 can use the access code module 114 to invalidate or modify the rules for the access code. If the recipient 160 receives an undesirable message and the access code is revoked, the recipient 160 can use the access code module 114 to validate the access code.

  Some interaction requests require confirmation or response. Accordingly, the recipient 160 indicates to the confirmation module 140 that the message has been received, and / or the recipient provides an answer to the request such as a multiple choice question, “yes” or “no”, detailed answer, etc. be able to. The confirmation module 140 can indicate to the senders 151, 152 that the interaction request has been confirmed, and / or the module can communicate the answer.

  FIG. 2 is a flowchart of a method 200 for processing an interaction request received by the interaction server 100. Method 200 begins when interaction server 100 receives an interaction request (202). The interaction server 100 determines whether the receiver 160 has enabled the sender's trust (204). If the sender's trust is not enabled, the interaction server 100 proceeds to step 208. Otherwise, the interaction server 100 determines whether the senders 151, 152 are trusted (eg, determines whether the senders 151, 152 are on the trust list 112) (206). If the sender 151, 152 is trusted, the interaction request is designated as trusted and / or delivered to the trusted inbox 121 (220). Otherwise, the interaction server goes to step 208

  In step 208, the interaction server 100 determines whether the access code is valid. In the illustrated configuration, if the access code is not valid, the interaction request is delivered to the inbox 121 (220) or otherwise available for review. Alternatively or additionally, the interaction request can be deleted if the access code is not valid. When the access code becomes valid, the interaction server 100 can determine whether the received access code is valid (210). If the received access code is not valid, the interaction request can be deleted (218). If the access code is valid, the interaction request can be designated as unconfirmed and / or moved to the unconfirmed inbox 122.

  When the recipient 160 reviews the unconfirmed interaction request and / or the unconfirmed inbox 122, the recipient 160 can be instructed to identify whether the senders 151, 152 are trusted. The interaction server 100 may receive an answer indicating whether the senders 151, 152 are trusted (212). If the receiver 160 indicates that the senders 151, 152 are untrustworthy, the interaction server blocks the senders 151, 152 from sending future interaction requests (214) and deletes the interaction requests (218). If the recipient 160 indicates that the sender 151, 152 is trustworthy, the sender 151, 152 is added to the trusted sender list 112 (216), and the interaction request is designated as trusted, and / or It can be delivered to the trusted inbox 121 (220). Method 200 ends with delete interaction request 218 or delivery 220 until the next interaction request is received.

  FIG. 3 is a flowchart of a method 300 for processing an interaction request addressed to a child's public address linked to a parent account. The method 300 begins when the interaction server 100 receives (302) an interaction request addressed to a child's public address. The interaction server 100 can determine whether the senders 151, 152 are trusted and / or have a valid access code (304). If the sender 151, 152 is not trusted and / or does not have a valid access code, the interaction request can be deleted (314). Alternatively, the interaction server 100 can proceed to step 306.

  In step 306, interaction server 100 may determine whether parental approval is required. The guardian may allow a specific sender 151, 152 and / or access code to send an interaction request to the child without the guardian's approval. If parental approval is not required, an interaction request is made available and / or sent to the child (316). If parental approval is required, an interaction request is made available and / or sent to the parent for approval (308). The guardian reviews the interaction request and the interaction server 100 can receive an answer indicating whether the guardian trusts the sender and / or approves the interaction request (310). If the guardian does not trust the sender, the sender is blocked (312) and the interaction request can be deleted (314). Otherwise, the interaction request becomes available and / or sent to the child (316). If the parent trusts the sender, the parent may indicate to the interaction server 100 that no approval is required for future messages, or all future messages will be reviewed by the parent before delivery. it can.

  FIG. 4 is a flowchart of a method 400 for delivering an interaction request to a recipient 160 using location-based interaction rules. The method 400 may begin when the interaction server 100 receives (402) an interaction request. The interaction server 100 can determine whether the location of the target recipient 160 (for example, a location by GPS) is available. Additionally or alternatively, the interaction server 100 can determine whether the intended recipient has logged into the computer or has performed other activities that can leverage the location data therefrom.

  If the location is available, the interaction server 100 can use the location to select the final destination of the interaction request (206). If the location is not available, interaction server 100 may use the current time, day of the week, and / or interaction rules to predict the final destination that is most likely to reach recipient 160 (408). The interaction rule can be obtained from the past behavior of the recipient 160. The interaction server 100 may deliver the interaction request to the selected and / or expected final destination (410).

  For an interaction request that requires confirmation, the interaction server 100 may determine whether an interaction request confirmation has been received (412). If no confirmation has been received, the interaction server can return to step 404. The interaction server 100 can expand the number of final destinations selected and / or predicted in each interaction. Upon receipt of the confirmation, the method ends (414).

  FIG. 5 is a schematic diagram of a system 500 configured to broadcast a message to a plurality of channel subscribers 540, 550, 560. System 500 includes a plurality of channels 511, 512, 513. Channel subscribers 540, 550, 560 can subscribe to one or more of channels 511, 512, 513, and / or channels 511, 512, 513 can be an interaction request and / or message sent to channel subscriber 540. 550, 560 can be made available to one or more of them. Broadcasters 531, 532, 533 send interaction requests and / or messages to channels 511, 512, 513, which make the received interaction requests and / or messages available to channel subscribers 540, 550, 560. be able to.

  Channel subscribers 540, 550, 560 maintain databases 545, 555, 565, respectively. Databases 545, 555, 565 may include various information such as interaction data maintained by subscribers 540, 550, 560 and / or private data including personal contacts. Channels 511, 512, 513 can retrieve private data from databases 545, 555, 565. Based on the retrieved information, the channels 511, 512, 513 can determine how to deliver messages and / or interaction requests. Private data can only be shared with channels 511, 512, 513 and / or interaction notification engines (not shown), and not with broadcasters 531, 532, 533. Subscribers 540, 550, 560 can share certain private data with broadcasters 531, 532, 533 so that one or more broadcasters can use the private data to personally contact the subscriber. Can be. The same user account and private data can be used by subscribers 540, 550, 560 to subscribe to multiple channels 511, 512, 513.

  FIG. 6 is a flowchart of a method 600 for allowing a new subscriber to join a channel. Method 600 begins when a channel receives a request to join a channel from a user (602). The channel can search the enrollment rules to determine which criteria a user must meet to join the channel (604). Admission rules can specify that the user must provide access to private user data. For example, the running channel may require the user to allow access to the user's location and / or to specify the distance the user is running. The user's location and / or answers to questions can be added to their private data, which can be maintained by the user and shared with other channels and / or trusted contacts (not shown).

  The channel and / or system containing the user database can determine whether the user's database contains the required private user data (606). If the user's database does not contain the required data, the user can be prompted to enter the data. Alternatively, the channel can request access to private user data in the user's database (610). The channel may receive an answer indicating whether private user data has been entered into the user's database and / or whether the user has allowed access to the private user data (612). If directed, if the user does not enter data (608) and / or does not allow access to the data, the method 600 ends without enrolling the user (618). Otherwise, the user is authorized as a channel subscriber (614) or waits for final approval from the administrator. In some configurations, recent messages can be forwarded to the user (616) and / or the user can be given access to the history of previous channel messages. Method 600 may end 618 until the next request for channel subscription.

  FIG. 7 is a schematic diagram of a system 700 configured to broadcast messages to channel subscribers, including subscribers 760. Broadcaster 730 has a broadcast right to channel 710. Broadcaster 730 can send an interaction request and / or message to channel 710 for delivery to the subscriber. Channel 710 may be configured to process interaction requests and / or messages received from broadcaster 730. Channel 710 may determine that channel subscriber 760 subscribes to channel 710 and receives interaction requests and / or messages.

  The interaction notification engine 720 can be configured to notify the channel subscriber 760 of new interaction requests and / or messages sent to the channel 710. Channel 710 can notify interaction notification engine 720 that an interaction request and / or message is available to subscriber 760. Alternatively, the channel 710 can deliver the interaction request and / or message to the channel subscriber 760's message center, and the interaction notification engine 720 can check the message center for new interaction requests and / or messages. When the interaction notification engine 720 notices a new interaction request and / or message for the channel subscriber 760, it may attempt to notify the channel subscriber 760.

  The interaction notification engine 720 can retrieve from the database 765 the channel subscriber's private data, including personal contacts, interaction rules, and / or escalation rules, and the channel subscriber 760 can store such information in the database. Is maintained. Private data can be shared with the interaction notification engine 720 and not with the channel 710 and / or the broadcaster 730. Based on the retrieved data, broadcaster 730, channel 710 and / or interaction request and / or data in the message, the interaction notification engine 720 how to deliver the interaction request and / or message to the channel subscriber 760 and the interaction request. And / or whether to escalate the message can be determined. For example, based on interaction rules, text messages can be sent to a feature phone (cell phone) 764 and / or voice messages, text messages, chat messages, and / or application messages can be sent to computer 761, smartphone 762, and / or landline phone. 763. Broadcaster 730 and / or channel 710 may not have visibility into this escalation process.

  The interaction request and / or message can request confirmation and / or reply. If channel subscriber 760 does not confirm or reply to escalated interaction request and / or message, send message repeatedly, send to various devices 761, 762, 763, 764, or to third party 770 You can send it. Third party 770 may be a relative or friend of channel subscriber 760 and / or third party 770 may be a stranger near channel subscriber 760. Broadcasters 730 may make available how many subscribers have acknowledged the message, what answers have been received, and / or other useful statistical data and information. Broadcaster 730 and channel 710 cannot access the channel subscriber's private data, and that information can be shared with broadcaster 730 only if channel subscriber 760 explicitly allows its sharing. Channel subscriber 760 can send an interaction request and / or message back to broadcaster 730 only if allowed by broadcaster 730 and / or channel settings. Whether the response of the interaction request to the broadcaster 730 is always possible depending on the channel setting, the response of the interaction request to the broadcaster 730 is impossible, or the interaction request responding to the broadcast is enabled. Can be determined by the broadcaster 730.

  FIG. 8 is a schematic diagram of an escalation rule 800 for the user 810. User 810 may be a channel subscriber (eg, channel subscriber 760) and / or a recipient of an interaction request (eg, recipient 160). Escalation rule 800 may be the default rule for all channel messages and / or interaction requests received by user 810. At the first escalation level 802, the user 810 can receive a message to his computer 811 and a call to his landline 812. After the first predetermined period, if the user 810 has not confirmed the notification, the interaction can be escalated to the second escalation level 804. At the second escalation level, the user 810 can again receive a message to his computer 811 and a call to his landline 812. The user 810 can also receive a message on the smartphone 813 via the application, and can also receive a text message on the feature phone 814.

  After the second predetermined period, the notification can be escalated to a third escalation level 806. The second predetermined period may or may not be the same as the first predetermined period. The third escalation level 806 may be the same as the other escalation levels, and the interaction can be attempted using the same device. The fourth and maximum escalation level 808 can be achieved after a third predetermined period. Notification can be retried by the user's devices 811, 812, 813, 814 during the fourth escalation level 808. Furthermore, a message can be sent to the computer 821, home phone 822, and smartphone 823 of the second user 820. Notification may be repeated at a fourth escalation level 808, with a delay of a fourth predetermined time interval separating each additional attempt. The attempt to iterate at the fourth escalation level 808 can continue until confirmation is received. Alternatively, the escalation can be terminated after a predetermined number of deliveries. In other embodiments, the escalation levels may be different numbers and / or other methods may be used to notify the user 810 at each escalation level.

  FIG. 9 is a schematic diagram of a system 900 configured to broadcast a message to a plurality of dynamically partitioned channel subscribers 940, 950, 960, 980. Broadcaster 930 wants to send a message only to subscribers that meet certain criteria. For example, broadcaster 930 wants to broadcast a question on a dedicated runner-only channel. The broadcaster's question is about marathon training, so we want to send a message only to subscribers interested in the marathon. Channel subscribers 940, 950, 960, 970, 980 may provide preferences and / or data to the subscriber databases 945, 955, 965, 975, 985, such as identifying the type of race they have participated and / or are interested in. Can be saved. Each channel subscriber 940, 950, 960, 970, 980 can have its own database 945, 955, 965, 975, 985, and / or one database can have multiple channel subscribers 940, 950, Information about 960, 970, 980 can be stored. Channel subscribers 940, 950, 960, 970, 980 can indicate that they only want to receive notifications of messages that meet their stated interests.

  When broadcaster 930 sends a message to the interaction server with a question about marathon training, the broadcaster can request dynamic splitting so that only subscribers interested in the marathon receive the message. Channel 910 can send a message to interaction notification engine 920 to determine which channel subscribers 940, 950, 960, 970, 980 will receive the message. In another embodiment, channel 910 determines which channel subscribers 940, 950, 960, 970, 980 will receive messages, and interaction notification engine 920 causes channel 910 to send messages to each channel subscriber's message center. After delivery, channel subscribers 940, 950, 960, 970, 980 can be notified. The interaction notification engine 920 can automatically access the databases 945, 955, 965, 975, 985 to determine subscribers 940, 950, 960, 980 who are interested in the marathon. Dynamic segmentation can be done without access to private data used to determine to whom broadcaster 930 will broadcast the message. The interaction notification engine 920 can determine dynamic partitioning without sharing private data with the broadcaster 930.

  The interaction notification engine 920 can send a notification to the subscribers 940, 950, 960, 980, which includes a message, a copy of the message, a predetermined number of characters in the message, a link to the message, and the like. If the first subscriber 940 and the second subscriber 950 indicate in their information that they have previously run a marathon, a message can be delivered to them. Based on the interaction rules in their database 945, 955, the interaction notification engine 920 can determine that a message is sent to the first subscriber computer 942 and the second subscriber landline 952.

  It is assumed that the third subscriber 960 has displayed that he is interested in the marathon. Third subscriber 960 owns a small athletics store and wants to immediately send a message to the channel. Third subscriber 960 may specify in his escalation rules that any message for that channel is first sent to his smartphone 962 and no answer is received, causing his computer 964 to escalate. it can. Because the fourth subscriber 970 has written that she will not run more than 10 kilometers, no message will be delivered to her. The fifth subscriber 980 has a marathon training and is interested in the marathon. Since the fifth subscriber 980 wants to ensure that all messages from the channel are received, the interaction rule for this fifth subscriber 980 is that all messages are the fifth subscriber's landline 982, smartphone 984. And can be specified to be delivered to the computer 986. Confirmation, response, and / or dynamic segmentation statistics such as the number of subscribers that meet the submitted criteria may be made available to the broadcaster 930.

  FIG. 10 is a schematic diagram of a system 1000 configured to broadcast automatic messages to interested channel subscribers 1040, 1080. Channel 1010 periodically receives and / or retrieves information from information server 1030 and / or channel 1010 computes information. In the illustrated embodiment, there is one information server 1030. In other embodiments, there may be more than one information server with aggregated content.

  In one embodiment, channel 1010 may request information about the next race from information server 1030 and determine that the San Francisco half marathon has been added to the list of races stored in information server 1030. Channel 1010 can send that information to interaction notification engine 1020 to determine which subscribers will receive notification of that information. Suppose that the first and fifth subscribers 1040, 1080 live in San Francisco and specify in their databases 1045, 1085 that they want to receive messages about the next race of interest. The interaction notification engine 1020 can broadcast automatic messages about the race to the first and fifth subscribers 1040, 1080. The second subscriber 1050 lives in San Francisco but does not want to receive an automated message about the next race. The third subscriber 1060 is only interested in the race on the east coast, and the fourth subscriber 1070 runs only a race of 10 kilometers or less. The interaction notification engine 1020 does not want the second subscriber 1050 to receive messages from these subscribers' databases 1055, 1065, 1075, and the location and distance for the third and fourth subscribers 1060, 1070, respectively. It is determined that it is not applicable, so the message is not sent to them and / or is not available.

  FIG. 11 is a schematic diagram of a communication system 1100 between a plurality of channel subscribers 1130, 1140, 1150, 1160, 1170. Channel 1110 can be configured to allow multiple channel subscribers 1130, 1150, 1160, 1170 to broadcast interaction requests and / or messages to each other and / or view each other's private data. For example, channel 1110 can be a family channel. Channel 1110 allows family members to take advantage of many of the features described herein. Messages are dynamically split among channel subscribers 1130, 1140, 1150, 1160, 1170 so that only messages associated with some family members are delivered to these channel subscribers 1130, 1140, 1150, 1170. Can be. Channel 1110 also allows one-to-one communication between any two of channel subscribers 1130, 1140, 1150, 1160, 1170. The message can be escalated to multiple devices 1172, 1174, 1176 of the channel subscriber 1170 to ensure that critical and / or emergency messages are received. Channel subscribers 1130, 1140, 1150, 1160, 1170 each maintain a database 1135, 1145, 1155, 1165, 1175, which may include private data such as personal contacts, interaction rules, escalation rules. Information in the databases 1135, 1145, 1155, 1165, 1175 can be used by the channel 1110 and / or interaction notification engine (not shown) to determine how to deliver the message, and / or It can be shared among channel subscribers 1130, 1140, 1150, 1160, 1170, such as family members who share mailing addresses and other personal contacts.

  The administrator 1130 can manage the rules of the channel 1110. The administrator 1130 allows some channel subscribers 1130, 1150, 1160, 1170 to broadcast messages and prevents other channel subscribers 1140 such as children in the family from broadcasting messages. Can do. The administrator 1130 can also determine to whom each channel subscriber 1130, 1140, 1150, 1160, 1170 can broadcast. Channel subscribers 1130, 1140, 1150, 1160, 1170 are all other channel subscribers 1130, 1140, 1150, 1160, 1170, a specific individual channel subscriber 1130, 1140, 1150 in a dynamically partitioned subset. 1160, 1170, etc. can be broadcast. The administrator 1130 can freely change the rules of the channel 1110.

  In another example, a channel 1110 can be operated by a school, and channel subscribers 1130, 1140, 1150, 1160, 1170 include parents, students, teachers, staff, and the like. Schools can send emergency messages to parents and students, such as school closures due to weather emergencies. Parents can also send messages back to school, including emergency messages. The school can assign messages received from parents to teachers and / or staff for response. Students and / or parents may or may not be allowed to send messages to other students and parents. Channel subscribers 1130, 1140, 1150, 1160, 1170 can interact with shared data. Therefore, teachers can create parent-teacher conference sign-up requests and share them only with their students' parents using dynamic segmentation. The guardian can reserve a time frame by looking at which time frame is available, and when the reservation is made, a mark indicating that the time frame cannot be used is immediately attached.

  Those skilled in the art will appreciate that many changes can be made to the details of the above-described embodiments without departing from the fundamental principles of the disclosure. The scope of the present disclosure is therefore determined solely by the following claims.

Claims (30)

  1. A computer implemented method for managing access to and interaction with a user resource, the method comprising:
    Associating a user with a single, unique public identifier that can be used to receive multiple types of interactions in a storage device;
    Receiving a first interaction from the sender, including an access code, addressed to the single, unique public identifier;
    Determining, based at least on the access code, whether to provide the first interaction to one or more user resources associated with the single, unique public identifier;
    Providing the first interaction;
    Select at least a first user resource,
    Providing the first interaction to at least the first user resource;
    Receiving from the user an indication of whether the sender is trusted among the steps determined by the processor ;
    Method comprising the additional interaction from a trusted the sender, without evaluating the access code, and providing one or at least one of the plurality of users resources.
  2.   2. The computer-based method of claim 1, wherein selecting at least the first user resource includes at least one of the one or more user resources associated with the single, unique public identifier. Selecting the first user resource, the step of providing the first interaction to at least the first user resource includes the first interaction, the notification of the first interaction, and the first Routing at least one of the payloads associated with the interaction to at least the first user resource.
  3.   3. The computer-based method of claim 2, wherein the routing step includes transmitting the first interaction without disclosing the address associated with the first user resource. Including routing to a person.
  4.   2. The computer-based method of claim 1, wherein selecting at least the first user resource comprises: telephone, voice mailbox, instant message client, email client, short message service (SMS) client, multimedia Message service (MMS) client, social media account, application, device specified by device identifier, device specified by internet protocol (IP) address, processing module, sensor, file system, database, web server, web service, service Select at least one user resource from the group consisting of locations specified by bus, store-and-forward device and postal address The method comprising that step.
  5.   The method using a computer according to claim 1, wherein selecting at least the first user resource includes selecting the first user resource based on an interaction rule received from the user.
  6.   6. The computer-based method according to claim 5, wherein, prior to providing the first interaction to at least the first user resource, the first interaction is determined from a first type based on the interaction rule. The method further comprising converting to at least a second type.
  7.   2. The computer-based method according to claim 1, wherein selecting at least the first user resource includes evaluating an interaction rule, and evaluating the interaction rule includes the location of the user, the access Code, the sender's ID, the sender's address, the sender's trust level, the sender's location, the user resource requested by the sender, the type of the first interaction, an emergency indication, important A method comprising the step of reviewing at least one of sex display, parental control, zone, current date, current time.
  8.   8. The computer-based method according to claim 7, wherein the step of providing the first interaction includes the first interaction, a notification of the first interaction, and a payload associated with the first interaction. And repeatedly routing at least one of the methods.
  9.   8. The computer-based method according to claim 7, wherein the step of providing the first interaction includes a plurality of user resources, the first interaction, the notification of the first interaction, and the first interaction. Routing at least one of the payloads associated with the.
  10.   The computer-based method of claim 1, further comprising receiving confirmation of the first interaction from the user.
  11.   11. The computer-based method of claim 10, further comprising making the confirmation available to the sender of the first interaction.
  12.   11. The computer-based method of claim 10, further comprising terminating an escalation process in response to receiving the confirmation.
  13.   The computer-based method of claim 1, further comprising the step of verifying that delivery of the first interaction to the user has been achieved.
  14.   14. The computer-based method of claim 13, further comprising making a delivery notification available to the sender of the first interaction.
  15.   2. The computer-based method of claim 1, wherein the first interaction includes a request for information, and determining whether to provide the first interaction comprises: Determining the amount to make available to the sender.
  16.   2. The computer-based method according to claim 1, wherein the plurality of types of interactions are e-mail message, short message service (SMS), multimedia message service (MMS), instant message, application message, device notification, social From media messages, voice messages, phone calls, video messages, video calls, multimedia data, user data requests, integrated public alert systems (IPAWS), chat messages, verification codes, authorization codes, wireless application protocol (WAP) messages and mail How to choose from a group.
  17.   2. The computer-based method of claim 1, receiving a second interaction including the access code before receiving the indication that the sender is trusted from the user, and the second Providing a first user resource to the first user resource.
  18. A system for managing access to and interaction with a user resource, the system comprising:
    A registration module configured to associate a user with a single, unique public identifier that can be used to receive multiple types of interactions;
    An access module,
    Receiving a first interaction from the sender, including an access code, addressed to the single, unique public identifier;
    An access module configured to determine whether to provide the first interaction to one or more user resources associated with the single, unique public identifier based at least on the access code; ,
    In response to the decision to provide the first interaction,
    Select at least a first user resource,
    A fulfillment module configured to provide the first interaction to at least the first user resource;
    The access module is further configured to receive an indication from the user whether the sender is trusted during the determining process, and the fulfillment module receives additional interaction from the sender. A system further configured to provide at least one of one or more user resources without evaluating an access code in response to receiving the indication that the sender is trusted.
  19.   19. The system of claim 18, wherein the fulfillment module selects at least the first user resource from among the one or more user resources associated with the single, unique public identifier. Configured to select at least the first user resource, wherein the fulfillment module is configured to select at least one of the first interaction, the notification of the first interaction, and a payload associated with the first interaction. A system configured to provide the first interaction to at least the first user resource by routing one to at least the first user resource.
  20.   20. The system of claim 19, wherein the fulfillment module routes the first interaction to the sender of the first interaction without disclosing the address associated with the first user resource. Configured system.
  21.   19. The system of claim 18, wherein the fulfillment module is a telephone, voice mailbox, instant message client, email client, short message service (SMS) client, multimedia message service (MMS) client, social media account, application. Specified by device identifier, device specified by Internet Protocol (IP) address, processing module, sensor, file system, database, web server, web service, service bus, store and forward device, and postal address Selecting at least one user resource from a group of defined locations, at least the first user resource A system configured to select.
  22.   19. The system of claim 18, wherein the fulfillment module is configured to select at least the first user resource based on an interaction rule received from the user.
  23.   23. The system of claim 22, wherein the fulfillment module changes the at least second type from a first type based on the interaction rules before providing the first interaction to at least the first resource. A system further configured to convert the first interaction.
  24.   19. The system of claim 18, wherein the fulfillment module is configured to select at least the first user resource by evaluating an interaction rule, the fulfillment module comprising the user location, the access code, the transmission. The sender's ID, the sender's address, the sender's trust level, the sender's location, the user resource requested by the sender, the type of the first interaction, the urgency display, the importance display A system configured to evaluate the interaction rule by reviewing at least one of: parental control, zone, current date and current time.
  25.   25. The system of claim 24, wherein the fulfillment module repeatedly routes at least one of the first interaction, a notification of the first interaction, and a payload associated with the first interaction. A system configured to provide the first interaction.
  26.   25. The system of claim 24, wherein the fulfillment module includes at least one of a plurality of user resources, the first interaction, a notification of the first interaction, and a payload associated with the first interaction. A system configured to provide the first interaction by routing the.
  27.   The system of claim 18, wherein the fulfillment module is further configured to receive a confirmation of the first interaction from a user.
  28.   28. The system of claim 27, wherein the access module is further configured so that the confirmation is available to the sender of the first interaction.
  29.   19. The system of claim 18, wherein the plurality of types of interactions are email messages, short message service (SMS) messages, multimedia message service (MMS) messages, instant messages, application messages, device notifications, social media messages. Voice message, telephone, video message, video call, multimedia data, user data request, integrated public alarm system (IPAWS) alert, chat message, verification code, authorization code, wireless application protocol (WAP) message and postal A system selected from a group.
  30. Computer readable storage means comprising program code for performing a method for managing access to and interaction with a user resource, the method comprising:
    Associating a user with a single, unique public identifier available to receive multiple types of interactions at a storage device;
    Receiving, from a sender, a first interaction including an access code addressed to the single, unique public identifier;
    Determining whether to provide the first interaction to one or more user resources associated with the single, unique public identifier based at least on the access code, If you provide interactions for
    Select at least a first user resource,
    Providing the first interaction to at least the first user resource;
    Among the said determining step comprises the steps of receiving an indication of whether the sender is trusted by the user,
    Additional interactions from a trusted the sender, without evaluating the access code, means and providing at least one of the one or more user resource.

JP2015552778A 2013-01-09 2014-01-09 Access controlled interaction system and method Active JP6349328B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US201361750634P true 2013-01-09 2013-01-09
US61/750,634 2013-01-09
PCT/US2014/010905 WO2014110279A1 (en) 2013-01-09 2014-01-09 Systems and methods for access-controlled interactions

Publications (2)

Publication Number Publication Date
JP2016510459A JP2016510459A (en) 2016-04-07
JP6349328B2 true JP6349328B2 (en) 2018-06-27

Family

ID=51061857

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2015552778A Active JP6349328B2 (en) 2013-01-09 2014-01-09 Access controlled interaction system and method

Country Status (11)

Country Link
US (3) US8874770B2 (en)
EP (1) EP2943889B1 (en)
JP (1) JP6349328B2 (en)
KR (1) KR20150105359A (en)
CN (1) CN105164663B (en)
AU (1) AU2014205387B2 (en)
BR (1) BR112015016568A2 (en)
CA (1) CA2897042A1 (en)
SG (1) SG11201505362WA (en)
WO (1) WO2014110279A1 (en)
ZA (1) ZA201504903B (en)

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9762685B2 (en) * 2005-04-27 2017-09-12 Live Nation Entertainment, Inc. Location-based task execution for enhanced data access
US20150003595A1 (en) * 2011-04-25 2015-01-01 Transparency Sciences, Llc System, Method and Computer Program Product for a Universal Call Capture Device
US9547862B2 (en) * 2012-08-01 2017-01-17 Paypal, Inc. Electronic payment restriction
US8844050B1 (en) 2013-03-15 2014-09-23 Athoc, Inc. Personnel crisis communications management and personnel status tracking system
US20140379390A1 (en) 2013-06-20 2014-12-25 Live Nation Entertainment, Inc. Location-based presentations of ticket opportunities
US10142277B2 (en) * 2013-06-28 2018-11-27 Orange Posting and consultation of messages by users of social networks
US9710808B2 (en) * 2013-09-16 2017-07-18 Igor V. SLEPININ Direct digital cash system and method
US20150163189A1 (en) * 2013-12-10 2015-06-11 Sweigh, Inc. Social messaging system and method
US20150256679A1 (en) * 2014-03-08 2015-09-10 J. Stephen Burnett Electronic Message Aggregation and Sharing System and Apparatus
US20150269700A1 (en) 2014-03-24 2015-09-24 Athoc, Inc. Exchange of crisis-related information amongst multiple individuals and multiple organizations
US20150310381A1 (en) * 2014-04-29 2015-10-29 Vivint, Inc. Systems and methods for secure package delivery
US10169776B2 (en) * 2014-05-12 2019-01-01 Adobe Systems Incorporated Obtaining profile information for future visitors
US20160007171A1 (en) * 2014-07-01 2016-01-07 Time Warmer Cable Enterprises LLC Message management and conditional delivery of available messages
GB2529721A (en) * 2014-09-01 2016-03-02 Ibm Temporary authorizations to access a computing system based on user skills
CN105530640B (en) * 2014-09-30 2019-02-22 国际商业机器公司 Method and apparatus for communication control
US20160119785A1 (en) * 2014-10-23 2016-04-28 Hyunil Choi System and method for managing posts
JP6354857B2 (en) * 2014-12-08 2018-07-11 日本電気株式会社 Wireless terminal and method for messaging
US20160275301A1 (en) * 2015-03-17 2016-09-22 Dots Communication, Inc. Information sharing control
US9830591B2 (en) 2015-05-27 2017-11-28 Bank Of America Corporation Providing access to account information using authentication tokens
US9824351B2 (en) 2015-05-27 2017-11-21 Bank Of America Corporation Providing access to account information using authentication tokens
US10298617B2 (en) * 2015-07-08 2019-05-21 T-Mobile Usa, Inc. Trust policy for telecommunications device
US20170068827A1 (en) * 2015-09-04 2017-03-09 Swim.IT Inc. Live privacy policy method and apparatus
CN105516259B (en) * 2015-11-27 2019-06-04 北京奇虎科技有限公司 A kind of method for sending information and device
CN105491121A (en) * 2015-11-27 2016-04-13 常作廷 Method and device for sending key signal to APP (Application)
CN106973322A (en) * 2015-12-09 2017-07-21 财团法人工业技术研究院 Across the screen synch apparatus and method of content of multimedia and playing device and servomechanism
CN105898066A (en) * 2016-05-19 2016-08-24 努比亚技术有限公司 Method and device for automatically distributing to specific contact based on specific information
CN106162306B (en) * 2016-07-05 2019-01-15 北京真真科技有限公司 A kind of merchandise display for net cast shopping and lower single system for prompting
CN106488294A (en) * 2016-09-28 2017-03-08 乐视控股(北京)有限公司 Barrage information transfer, display packing and device
CN106341313A (en) * 2016-09-29 2017-01-18 北京小米移动软件有限公司 Method and apparatus for obtaining billing information
CN108809799A (en) * 2017-04-28 2018-11-13 腾讯科技(深圳)有限公司 Method for sending information, method for information display, apparatus and system
WO2019010362A1 (en) * 2017-07-07 2019-01-10 Samchat, Inc. Systems, methods and computer program products for providing enhanced chat services

Family Cites Families (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5287498A (en) 1991-04-02 1994-02-15 Rolm Company Message transmitting system wherein recipient site is determined using information concerning the relationship between the sender and recipient sites
US5724521A (en) 1994-11-03 1998-03-03 Intel Corporation Method and apparatus for providing electronic advertisements to end users in a consumer best-fit pricing manner
FR2741465B1 (en) * 1995-11-20 1997-12-19 Bull Sa a User Authentication Method working in a distributed environment in client / server
US6055510A (en) 1997-10-24 2000-04-25 At&T Corp. Method for performing targeted marketing over a large computer network
US6161185A (en) * 1998-03-06 2000-12-12 Mci Communications Corporation Personal authentication system and method for multiple computer platform
WO2001059660A1 (en) 2000-02-11 2001-08-16 Marcio Marc Abreu System and method for communicating product recall information, product warnings or other product-related information to users of products
US20020072996A1 (en) 2000-03-28 2002-06-13 Paiz Richard S. Method of and apparatus for practicing religious faith through the world wide web via purchase of copies of proprietary religious audio and visual works and merchandise
US8073565B2 (en) 2000-06-07 2011-12-06 Apple Inc. System and method for alerting a first mobile data processing system nearby a second mobile data processing system
CA2425243A1 (en) * 2000-10-10 2002-04-18 Upoc, Inc. A personal message delivery system
AU1285702A (en) 2000-10-27 2002-05-06 Fulcit New Zealand Ltd Method and apparatus for generating an alert message
US7536351B2 (en) 2000-10-30 2009-05-19 Amazon.Com, Inc. User-to-user payment service with payee-specific pay pages
US7272662B2 (en) * 2000-11-30 2007-09-18 Nms Communications Corporation Systems and methods for routing messages to communications devices over a communications network
WO2002059773A1 (en) 2000-12-04 2002-08-01 Thinkshare Corp. Modular distributed mobile data applications
US20020138622A1 (en) 2001-03-21 2002-09-26 Motorola, Inc. Apparatus and method of using long lived addresses in a private network for push messaging to mobile devices
US7228438B2 (en) * 2001-04-30 2007-06-05 Matsushita Electric Industrial Co., Ltd. Computer network security system employing portable storage device
FR2827465B1 (en) 2001-07-13 2004-01-02 Cegetel Method for addressing a mobile terminal
GB0125201D0 (en) * 2001-10-19 2001-12-12 Nokia Corp A messaging system
US20030130857A1 (en) 2002-01-04 2003-07-10 Masanobu Matsuo Systems, methods and computer program products for utilizing an information exchange framework
US20030225590A1 (en) * 2002-06-04 2003-12-04 Baby Croesus Sa Web card system
US7010565B2 (en) 2002-09-30 2006-03-07 Sampson Scott E Communication management using a token action log
US20040111480A1 (en) 2002-12-09 2004-06-10 Yue Jonathan Zhanjun Message screening system and method
US7895263B1 (en) 2003-06-25 2011-02-22 Everbridge, Inc. Emergency and non-emergency telecommunications geo-notification system
US8102974B2 (en) 2003-07-01 2012-01-24 Avaya Inc. Method and apparatus for event notification based on the identity of a calling party
US8316128B2 (en) 2004-01-26 2012-11-20 Forte Internet Software, Inc. Methods and system for creating and managing identity oriented networked communication
US7827234B2 (en) 2005-01-10 2010-11-02 International Business Machines Corporation Privacy entitlement protocols for secure data exchange, collection, monitoring and/or alerting
US7672440B2 (en) 2005-01-20 2010-03-02 International Business Machines Corporation Single point of contact personal communication system
US7130389B1 (en) 2005-04-28 2006-10-31 Tech Radium, Inc. Digital notification and response system
US20070043608A1 (en) * 2005-08-22 2007-02-22 Recordant, Inc. Recorded customer interactions and training system, method and computer program product
US7706253B1 (en) 2005-12-02 2010-04-27 Network Equipment Technologies, Inc. Gateway to route communications during a fault
EP1984889A2 (en) 2006-02-08 2008-10-29 Imagineer Software, Inc. Secure digital content management using mutating identifiers
US7301450B2 (en) 2006-03-14 2007-11-27 John Carrino Citizen communication center
CN100466783C (en) * 2006-04-06 2009-03-04 华为技术有限公司 Right discriminating method between mobile terminal and network equipment
US20080013712A1 (en) * 2006-07-11 2008-01-17 Karsten Gopinath Unified Communication Directory Service
US7927214B2 (en) * 2006-12-08 2011-04-19 Microsoft Corporation Transfer of content to closed systems
CN101335622B (en) * 2007-06-27 2012-08-29 日电(中国)有限公司 Method and apparatus for distributed authorization using anonymous flexible certificate
US9838365B2 (en) 2007-07-10 2017-12-05 Qualcomm Incorporated Peer to peer identifiers
CA2707536C (en) 2007-12-06 2015-05-12 Suhayya Abu-Hakima Processing of network content and services for mobile or fixed devices
JP5045417B2 (en) * 2007-12-19 2012-10-10 ソニー株式会社 Network system and direct access method
US8424057B2 (en) * 2007-12-28 2013-04-16 Ebay, Inc. Mobile anti-phishing
US8224284B2 (en) 2008-01-04 2012-07-17 At&T Intellectual Property I, L.P. Emergency communication system and method
US20090271873A1 (en) * 2008-04-24 2009-10-29 Alon Ram Method and system for displaying a sequence of media files
CN102037749B (en) 2008-05-23 2014-02-19 艾利森电话股份有限公司 Method and system for message routing in IMS and circuit switched networks
US8416933B2 (en) * 2008-10-30 2013-04-09 International Business Machines Corporation Trusted environment for communication between parties
US9473419B2 (en) * 2008-12-22 2016-10-18 Ctera Networks, Ltd. Multi-tenant cloud storage system
US20130254314A1 (en) * 2009-06-09 2013-09-26 Edmond K. Chow Digital content delivery
US8315595B2 (en) 2009-06-10 2012-11-20 International Business Machines Corporation Providing trusted communication
IE20110012A1 (en) * 2010-01-13 2011-07-20 Sotxtme Ltd User-defined access controls for accessing user via an electronic communication device
US8219542B2 (en) * 2010-03-25 2012-07-10 Boku, Inc. Systems and methods to provide access control via mobile phones
US9319390B2 (en) 2010-03-26 2016-04-19 Nokia Technologies Oy Method and apparatus for providing a trust level to access a resource
US8468584B1 (en) * 2010-04-02 2013-06-18 Wells Fargo Bank, N.A. Authentication code with associated confirmation words
US8914523B2 (en) 2010-05-17 2014-12-16 Verizon Patent And Licensing Inc. Dynamic internet protocol registry for mobile internet protocol based communications
CN102567115B (en) * 2010-12-23 2016-04-06 伊姆西公司 Distribute for information technology resources in cloud system and utilize the apparatus and method of following the tracks of
WO2012094235A2 (en) 2011-01-03 2012-07-12 MONTOYA, David Geo-location systems and methods
US9037724B2 (en) 2011-02-08 2015-05-19 Sierra Wireless, Inc. Method and system for forwarding data between network devices
US20120215620A1 (en) 2011-02-18 2012-08-23 Ryan Scott Rodkey Message Center Application and System
US8769422B2 (en) 2011-05-10 2014-07-01 Echostar Technologies L.L.C. Apparatus, systems and methods for facilitating social networking via a media device
US8751317B2 (en) 2011-05-12 2014-06-10 Koin, Inc. Enabling a merchant's storefront POS (point of sale) system to accept a payment transaction verified by SMS messaging with buyer's mobile phone
WO2011157142A2 (en) 2011-05-31 2011-12-22 华为技术有限公司 Method and apparatus for message transmission
KR101748732B1 (en) * 2011-06-27 2017-06-19 삼성전자주식회사 Method for sharing contents using temporary keys and Electric device
US8589481B2 (en) * 2011-09-14 2013-11-19 Microsoft Corporation Multi tenant access to applications
US8584259B2 (en) * 2011-12-29 2013-11-12 Chegg, Inc. Digital content distribution and protection
US9276869B2 (en) * 2013-01-02 2016-03-01 International Business Machines Corporation Dynamically selecting an identity provider for a single sign-on request

Also Published As

Publication number Publication date
CN105164663A (en) 2015-12-16
WO2014110279A1 (en) 2014-07-17
BR112015016568A2 (en) 2017-07-11
US20160105776A1 (en) 2016-04-14
AU2014205387B2 (en) 2019-02-21
US20140195626A1 (en) 2014-07-10
US9763064B2 (en) 2017-09-12
US20150019666A1 (en) 2015-01-15
CN105164663B (en) 2018-05-01
JP2016510459A (en) 2016-04-07
ZA201504903B (en) 2016-06-29
SG11201505362WA (en) 2015-08-28
EP2943889B1 (en) 2018-10-24
US8874770B2 (en) 2014-10-28
CA2897042A1 (en) 2014-07-17
EP2943889A1 (en) 2015-11-18
KR20150105359A (en) 2015-09-16
AU2014205387A1 (en) 2015-08-20
EP2943889A4 (en) 2016-09-28

Similar Documents

Publication Publication Date Title
US9264462B2 (en) System and method for confirming attendance for in-person meetings or events
US8904295B2 (en) Web-based interactive meeting facility with recommendations to users
US8464315B2 (en) Network invitation arrangement and method
US8965409B2 (en) User-generated community publication in an online neighborhood social network
US20070156824A1 (en) Community messaging system
US8929857B2 (en) Policy management of electronic devices
US8880620B2 (en) Social graphing for data handling and delivery
US20080098313A1 (en) System and method for developing and managing group social networks
US7761566B2 (en) System for tracking domain name related reputation
JP2010503072A (en) Computer-based meeting preparation method and execution system
US20040133440A1 (en) System and method for objectively managing complex familial interactions and responsibilities
TWI396112B (en) A system, method, service method, and program product for managing entitlement with identity and privacy applications for electronic commerce
US7970832B2 (en) Electronic message delivery with estimation approaches and complaint, bond, and statistics panels
US20040172279A1 (en) System and method for objectively managing complex familial interactions and responsibilities
US20130262168A1 (en) Systems and methods for customer relationship management
US9654425B2 (en) System and method for communicating among members of meeting groups
US8375097B2 (en) Communication systems and methods with social network filtering
US8886817B2 (en) Federation and interoperability between social networks
US20100082652A1 (en) Method and system for managing user interaction
US20070136178A1 (en) Trust based architecture for listing service
US10117074B2 (en) Systems and methods for establishing communications between mobile device users
US8751575B2 (en) System and method for generating a ghost profile for a social network
US20070127693A1 (en) Consumer feedback method and apparatus
US9680803B2 (en) Systems and methods for secure short messaging service and multimedia messaging service
US7822821B2 (en) Access point object depositable on a web page and useful for initiating communication between depositing user and buddy

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20170105

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20180227

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20180517

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20180522

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20180604

R150 Certificate of patent or registration of utility model

Ref document number: 6349328

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150