WO2011155996A2 - Système, procédé et appareil d'intégration de messagerie de groupe - Google Patents

Système, procédé et appareil d'intégration de messagerie de groupe Download PDF

Info

Publication number
WO2011155996A2
WO2011155996A2 PCT/US2011/001044 US2011001044W WO2011155996A2 WO 2011155996 A2 WO2011155996 A2 WO 2011155996A2 US 2011001044 W US2011001044 W US 2011001044W WO 2011155996 A2 WO2011155996 A2 WO 2011155996A2
Authority
WO
WIPO (PCT)
Prior art keywords
message
group
rules
messaging
delivery
Prior art date
Application number
PCT/US2011/001044
Other languages
English (en)
Other versions
WO2011155996A3 (fr
Inventor
Brian Szady
Jeremy Keehn
Original Assignee
Maxx Wireless, Incorporated
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
Application filed by Maxx Wireless, Incorporated filed Critical Maxx Wireless, Incorporated
Publication of WO2011155996A2 publication Critical patent/WO2011155996A2/fr
Publication of WO2011155996A3 publication Critical patent/WO2011155996A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding

Definitions

  • the present invention generally relates to transmission of information over an electronic network, and more specifically, to a group messaging integration service.
  • SMS Short Message Service
  • SMS text messaging is the most widely used data application in the world.
  • the term SMS is used as a synonym for all types of short text messaging as well as the user activity itself in many parts of the world.
  • MMS multimedia messaging service
  • a mobile operator providing MMS services to a subscriber will have an MMS - compatible infrastructure in place.
  • a sender wishing to send a multimedia message intended for a recipient, sends the multimedia message to a multimedia message service center (MMSC) of the sender's mobile operator.
  • the multimedia message may include a recipient address.
  • the MMSC of the sender's mobile operator delivers the multimedia message to the MMSC of the recipient's mobile operator either directly or via a MMS hub or MMS gateway.
  • the MMSC of the recipient's MMS operator sends the multimedia message to the recipient.
  • the recipient then views the multimedia message on a MMS - compatible handset.
  • FIG. 1 illustrates an ecosystem for providing a seamless group messaging integration system, in accordance with an embodiment of the present invention
  • FIG. 2 is a flow chart illustrating initiation steps included in one embodiment of the present invention
  • FIG. 3 is a flow chart illustrating creation of a new user steps included in one embodiment of the present invention.
  • FIG. 4 is a flow chart illustrating steps used to invite friends to one embodiment of the present invention.
  • FIG. 5 is a flow chart illustrating joining a group generated by one embodiment of the present invention.
  • FIG. 6 is a flow chart illustrating sending a message according to one embodiment of the present invention.
  • FIG. 7 is a flow chart illustrating general use steps included in one embodiment of the present invention.
  • FIG. 8 is a flow chart illustrating creating a group generated by one embodiment of the present invention.
  • FIG. 9 is a flow chart illustrating listing a users groups generated by one embodiment of the present invention.
  • FIG. 10 is a flow chart illustrating member listing steps included in one embodiment of the present invention.
  • FIG. 1 1 is a flow chart illustrating stop steps included in one embodiment of the present invention
  • FIG. 12 is a flow chart illustrating help steps included in one embodiment of the present invention.
  • FIG. 13 is a block diagram of an example computing system in which the present invention may operate.
  • the GMI of the present invention uses either a CSC or Long Code.
  • Long Code, or Virtual MISDN is a randomly generated regular phone number (for example, 555-555-5555 or 053-72-42-1234).
  • GMI employs API, which allows the entire platform to be integrated into third party IP environments, SMSC, and MM7.
  • One embodiment of the GMI allows groups to be created, joined, and posted in the following manner: Any person with a wireless cell device can create a group, join a group, post to a group, as well as have access to other controls. The system will intelligently walk the user through creation, joining, posting, and other processes - while including "state" information.
  • a user sends a message.
  • the system provides additional information to the user that clarifies the initial task.
  • the GMI has cached that initial action as a specific "state" - with that information held in a pending state within the GMI.
  • the information that is held is all cumulative messages and metadata for each step until the whole function is deemed complete.
  • a user sends an invite message command.
  • the GMI stores the command [invite], user ID, device [mobile], and access method [text].
  • the GMI responds by asking the user which number to invite.
  • the user sends the message containing the number, and the GMI stores the command [invite], the number, the user ID, the device [mobile], and the access method [text].
  • the GMI then includes the initial message into the subsequent action.
  • the GMI enables spontaneously created groups. For example, a user in San
  • the user decides to create a group at the spur of the moment called 'sanfrancisco'.
  • the user can create the group in real-time - without needing anything but their wireless device.
  • the group is instantly created upon the user sending in the create commands. If a group name is taken, then the system recommends similar names that are available.
  • Posts from anyone in the group can be delivered across to any delivery mechanism, for example, instant messaging (IM), email, web or Internet sites, widgets, wireless applications, short messaging system (SMS), and multimedia messaging service (MMS).
  • IM instant messaging
  • SMS short messaging system
  • MMS multimedia messaging service
  • the GMI uniquely identifies the process required for the creation, joining, inviting, sending, and posting an IP, SMS, and MMS based group message.
  • Each message is received by each member of the group.
  • Each reply to an individual message also routes to each member of the group.
  • Each message is dynamically routed to every individual group members through the pre-determined delivery mechanism: SMS, MMS, and IP-based (i.e., email, IM, API post, XML).
  • the GMI specifically relates to delivery over wireless and IP -based networks and devices.
  • One module is the Message Engine Routing module that comprises the core rules, or algorithms that manage the delivery of messaging, when messaging is delivered, where messaging is delivered, and how messaging is delivered.
  • This routing engine includes decisions such as where to send messages for existing and new users.
  • the Message Engine Routing module performs such tasks as: send message to SMS; send message to social networks; send message to any IP environment including: binary applications, websites, mobile websites, email and IM.
  • the Message Engine Routing module can convert messages from one format to another. For example, a SMS formatted message is received and reformatted to a mobile website format. Thus, when messages are received, they are processed so that the components of each message are extracted from the source format and stored for future use. Messages are comprised two basic components - content and metadata. Each is stored so that stored information includes the content of the message (text and/or binary information), the details of the delivery platform, the ID of the GROUP (see below), and the ID of the sender.
  • Processing is based on sets of rules relating to the destination address of each recipient. Some of these rules include the access methods the recipient has registered, the delivery settings of each recipient (where and when the recipient has selected to receive messages), and the platform status of each recipient (the recipient's account and security status).
  • processing rules include access method rules, delivery method rules, account status rules and security mechanism rules.
  • the access method rules are selected from a group consisting of: send message to web, send message to mobile web, send message to binary application, send message to SMS, send APN notification, send message to email, send message to Instant Messenger, send message to 3 rd party integration through API, send message to other IP based delivery locations.
  • Receive message rules are through: SMS, web, mobile web, binary application, email, instant messenger, API, APN Notification, and other IP based delivery mechanisms.
  • the delivery method rules are selected by the user/administrator/group creator and may be one, many, or all of the below: SMS, binary application, web, mobile web, APN notification, email, instant messenger, API only, and other IP based delivery methods.
  • the account status rules include: existing member, new member, specific time-based delivery of messaging, mute (i.e., do not send message when mute is enabled). Also, the administrator/user/group creator can be selected to send to specific access locations.
  • the security mechanism rules can be selected through: SMS, web, mobile web, binary application, API, and other IP based locations where API integration occurs.
  • the Message Engine Routing module can convert messages from one format to another. This novel process results in the GMI transforming and transcoding messages, metadata, and binary information from SMS/MMS formats to IP-based formats, and vice- versa.
  • the Business Rules module includes specific functions and features that define what end-users will be able to use.
  • Business rules allow developers to select specific functions and features to expose to end users. For example, geolocation features can either be included or not included in an application or website based on the 'business rules' selected.
  • Each business rule can be selected by the 'owner' of the application, website, or communication system that is integrating the GMI. For example, a GMI customer can choose to implement all GMI functions or a select subset of core components.
  • the GMI platform then delivers those decisions through the GMI application programming interface (API).
  • API application programming interface
  • MMA sets standards that must be followed by companies delivering services, platforms, or applications over wireless networks (SMS or IP). Examples include requiring users to opt-in to join a service, minimum billing requirements, legal copy, etc.
  • the GMI platform includes all required standards built deep within the GMI platform. For example, MMA requirements mandate all users must opt-in when joining any service. GMI sends a message to the user that she has been invited to join a group. The invitee must accept the invite to join the group. GMI never automatically joins users into a communication chain or group.
  • Transcoding is a system that dynamically transforms media, applications, websites, and messaging to specific formats that will work on specific devices. Transcoding allows information to be viewed, in an optimized format, on multiple device types. For example, a video must be transcoded into different formats to work over certain mobile phones, websites, or applications.
  • the GMI platform includes unique extensions and also extensions from a software system developed by Mobixell, a provider of transcoding systems.
  • the Device Database module houses information on hundreds of mobile devices, applications, and websites. This information includes file support, media support, technical specifications, and other information. The Device Database then informs the transcoding engine as to what formats each different device supports. The device database is integrated into the GMI platform and has been developed specifically for the GMI platform.
  • the Data Warehouse module is where core information is housed and stored within the GMI server farm and network. Examples of core information include: all user information, messages, media, user profiles, and authentication records.
  • the Commerce engine module is a system that allows for billing integration into wireless carrier networks and credit card networks. The Commerce Engine manages any billing transaction. This commerce solution leverages the wireless carrier billing systems with API/Secure VPN integration through: individual wireless carriers (such as AT&T, Verizon, etc), wireless aggregators (such as mblox, OpenMarket, etc). The wireless aggregator has integrations into multiple wireless carriers and includes billing capabilities.
  • the Analytics module comprises a mechanism for studying usage information, statistics, and other system-wide data.
  • Sample analytics include: user click information, where and how users access different parts of the GMI platform, average message length, most frequent words within messages, message keywords, average message usage per user, average total users per group, and average access time within each group, among others.
  • the GMI platform enables a group of users, each using a different platform (such as website or email) to seamless send and receive messages.
  • the GMI includes an Application Programming Interface (API), which allows the GMI platform to be exposed to other developers, applications, websites, etc.
  • APIs enable other developers to easily integrate and build the GMI platform into external offerings (websites, applications, SMS/MMS).
  • the GMI platform can communicate and be hosted on a Website, and can_provide IP based delivery of content and application code that is visible through an Internet based browser, whether accessed through a PC, mobile device, or other Internet connected machines.
  • the GMI platform can integrate into any ⁇ - based environment including a website.
  • a customer integrating GMI into their website would use the GMI API.
  • the API provides access to every GMI function, feature, and messaging capability. The customer would then select which features to expose to their website users, provide a desired user interface, and the GMI platform would be active.
  • SMS/MMS (or SMS OEM) can communicate with the GMI platform, and GMI enables the SMS/MMS quick messaging format to delivered through wireless carrier networks and IP based networks, which are typically limited to 160 characters in length.
  • an iphone (iOS) application can integrate with the GMI API. This integration would enable all the GMI functions within the iphone application including authentication, group creation, inviting, media posting, message posting, profile updates, social network integration, and all other GMI platform functions.
  • FIGS. 2- 12 flow charts illustrating one embodiment of the GMI, entitled “GROUP” is illustrated.
  • GROUP initiation is illustrated.
  • step Al a user creates a GROUP by initiating a create GROUP action through IP or by sending the create/new group command/keyword(s).
  • An example of this process may include, the user sending 'New' or 'Create' to GMI.
  • the user may send 'new groupname nickname' "GROUP” ( 'New' or 'Create', which then initiates the GMI wizard-based process) through SMS, and either a CSC or Long Code.
  • step A3 a user process is performed, which is illustrated in FIG. 3, by the "B" sequence steps.
  • GROUP name Check for valid GROUP name, if GROUP name is valid, check if GROUP name in use. If GROUP name in use, ask user to try again. If GROUP name valid and not in use, check for first time account. If first time account, ask for nickname, then check for valid nickname. If nickname is valid, check if nickname is in use. If nickname is in use, ask user to try again. If nickname valid and not in use, create account and associate new nickname with GROUP. If account exists, associate current nickname with GROUP. Create GROUP using specified GROUP name and assign associated nickname to GROUP. Check if GROUP created from SMS. If GROUP created from SMS, send SMS confirmation notification.
  • the GROUP properties are set, which includes one or more of the following processes: (1 ) Originating application: The application the GROUP was created from. This can be the GROUP system or a third party application (mobile app, website, mobile website, SMS, email, IM). (2) Public/private: whether or not the GROUP can be searched and viewed from people other than the members of the GROUP. (3) Gated/ungated: relates to invitations. A gated GROUP is a GROUP where the creator of the GROUP has to approve all joins. (4) Avatar: The picture for the GROUP. (5) Description: The description of the GROUP (i. e. , 'This GROUP is about cooking.').
  • External/internal Internal GROUP would be a local group within only a private organization (i.e., a corporation). External GROUP would be the normal public/private group accessible by any user.
  • Default users joined In an internal GROUP, the administrator could automatically join specific users into a group.
  • Category the topic for the GROUP (i.e. , sports).
  • Timeline to be live a private GROUP could expire after a specified period of time as denoted by the creator.
  • Geolocation on/off Allowing or not allowing geolocation to be included for that particular GROUP.
  • Blocked users Any specific users that cannot join into the GROUP.
  • step Fl - a user invites friends to GROUP by initiating an invite friend action through IP, or by sending an invite keyword through SMS.
  • step F2 check if user is new to GROUP platform.
  • Step F3 if user is new, go to Create User process.
  • Step F4 prompt user for GROUP name.
  • step F5 check for valid GROUP name.
  • Step F6 if GROUP name not valid, ask user for new GROUP name.
  • Step F7 - ask user for invitation routing information (example: email, buddy name, mobile number).
  • Step F9 if routing information is not valid, ask user to try inviting a different friend.
  • step F10 send invite using specified routing information.
  • a user may invite friends to GROUP by initiating an invite friend action through IP, or by sending the Invite command keyword(s), for example, 'invite' or "Invite [ mobile number
  • the user could simply send 'Invite', which would initiate the GMI wizard-based process for inviting through SMS.
  • invite to social network Facebook, Twitter, etc. Then, if invite not to social network, check for valid mobile number
  • a user sends a message by initiating a send message action through IP, or by sending just the message, which will initiate the GMI wizard-based algorithms or "[GROUP name] [message]" through SMS.
  • a user sends a message by sending [message] through SMS.
  • Check for valid GROUP name if GROUP name not valid, return error. If GROUP name valid, check if user belongs to GROUP, if user does not belong to GROUP, return error.
  • GROUP If user belongs to GROUP, check for valid message, if message not valid, return error. If message is valid, store the message. View messages on IP properties ⁇ i. e. , on websites, or applications). Check for SMS enabled delivery. Check for application notifications.
  • FIGS. 7-12 Illustrated in FIGS. 7-12 are flow charts illustrating other GROUP processes. It will be appreciated that the specific steps may vary, or other changes may occur within the GMI platform.
  • another embodiment of the GMI system may be "wizard" based.
  • This embodiment includes very powerful, scalable, and simple to use algorithms which power the wizard- based structure of the SMS interaction.
  • This embodiment allows for users to have no prior knowledge of key commands or keywords to initiate actions.
  • Actions may include, but not limited to, create new group, invite to a group, join and group, post to a group, list members of a group, list groups a user belongs, and help.
  • a user may belong to multiple groups.
  • the inviter can simply text 'Invite' to the GMI.
  • the response to the inviter from GMI will ask the inviter which group the person wants to invite the other person.
  • the inviter will respond with the desired group name.
  • GMI will then send a message requesting the mobile#, nickname, or unique identifier.
  • the inviter replies with the invitee mobile#, nickname, or unique identifier.
  • GMI then sends the invite to the invitee and sends a confirmation message to the inviter.
  • the inviter could alternatively send a message containing all the relevant information such as: invite keyword, mobile#/nickname/unique identifier, group name.
  • GMI will then deliver the invite to the invitee and a confirmation message to the inviter.
  • Another example includes a user whom is a member of multiple groups. If the user sends a message without the group name included, GMI will store the original message content. GMI will send a message to the sender asking which group the sender desires to send that message - GMI also includes a listing of recent group names with which the person has interacted. The sender can reply with a specific command for the appropriate group (a number, a letter, an abbreviation, etc) or with the actual group name itself. GMI will then send the original message to the stated group and send a confirmation of send message to the sender.
  • the alternative manner for sending a message to a group is to include the group name in the message itself.
  • One additional example of use interaction includes a new group user, whom does not have an existing account.
  • the person sends any SMS message to GMI.
  • GMI responds with a request for the user to create a nickname/unique identifier. Once the unique identifier is created, GMI then responds with a listing of the function options that user can engage, examples include: create a group, join a group, invite to a group, post to a group, and more.
  • the user would then reply with the command word(s) associated with the particular desired function. That process would then be initiated. This similar process exists for each and every command function within the alternative embodiment GMI.
  • Command functions include, but are not limited to, create new group, invite to group, join group, post to group, list members of a group, list the groups a user is a member, help.
  • These algorithms comprise the major components of the GMI platform and ensure the use of SMS messaging is a simple process, whereby the complexity is entirely hidden within the GMI platform.
  • One method employed by the GMI comprises sending and receiving electronic communication between a plurality of users operating within a plurality of different network architectures. Provisioning a server with a messaging software, where the server is in communication with each of the users. Causing a processor to broadcast from one of the users a message identified by a number generated by the messaging software. Causing a processor to receive the message, and processing the message using the number. Searching a plurality of groups using the number and sending a plurality of response messages using the number, the plurality of response messages sent to the plurality of users located within each of the different network architectures. The number generated by the server, the number used to process the message, the number used to search the plurality of groups, and the number used to send the plurality of messages is the same number. Also, the messaging software is selected from a group consisting of a common short code, a long code, a virtual MISDN, and a combination of two or more thereof.
  • the processing includes separating the message into a message content and a message metadata, where the processing includes a plurality of administrative controls specific to a specific user or group, or both, and where the administrative controls are selected from a group consisting of: a geolocation function, a social network integration, a message delivery schedule, a type of message delivery, a muted messaging function, and an authentication function.
  • the processing includes a plurality of user controls selected from a group consisting of: a message muting function, a message delivery schedule, a geolocation function, and a social network message delivery function.
  • the message includes a media and an attachment, and where the media is selected from a group consisting of: a video, an image, a document, a .pdf, and a combination of two or more thereof. Also, the step of sending the plurality of response messages is provided through an application programming interface that integrates with a third party.
  • the groups are comprised of a plurality of common interest subjects generated by the users, and where the different network architectures are selected from a group consisting of: a mobile web network, a web network a short message service network, an email network, an instant messenger network, an Internet protocol-based network, and a combination of two or more thereof.
  • Another method employed by the GMI comprises sending electronic communication between a plurality of users operating within a network architecture, the method comprising the steps of: provisioning a server with a messaging software, wherein the server is in communication with each of the users; causing a processor to broadcast from one of the users a message that includes an address of a recipient user; causing a processor to receive the message, where the message is comprised of a message content and a message metadata; causing the processor to extract from the message the message content and the message metadata; causing the processor to queue the message content for delivery to the recipient user; reformatting the message from a received format to a format used by a communication device employed by the recipient, where the step of reformatting comprises the steps of: causing a processor to process the message content by applying a plurality of rules including access method rules, delivery method rules, account status rules and security status rules; and causing the processor to send the reformatted message to the recipient user.
  • the access method rules are selected from a group consisting of: a plurality of send message rules, a plurality of receive message rules, and a combination and a combination of two or more thereof
  • the plurality of send message rules are selected from a group consisting of: send message to an Internet, send message to a mobile web, send message to a binary application, send message to a short message service, send an access point name notification, send a message to an email, send a message to an instant messenger, send a message to a third party integration through an application programming interface, send a message to a plurality of other Internet protocol-based delivery locations, and a combination of two or more thereof.
  • the plurality of receive message rules are selected from a group consisting of: short message service rules, Internet rules, mobile Internet rules, binary application rules, email rules, instant messenger rules, application programming interface rules, access point name notification rules, and a plurality of other Internet protocol-based delivery rules, and a combination of two or more thereof.
  • the delivery method rules are selected from a group consisting of: short message service delivery rules, binary application delivery rules, email delivery rules, mobile web delivery rules, web delivery rules, access point name notification delivery rules, and instant messenger delivery rules.
  • the account status rules are selected from a group consisting of: existing member rules, new member rules, and specific time-based delivery of messaging rules.
  • Yet another method employed by the GMI comprises a computing system, comprising: a processor; a data storage module; and a memory module that comprises a plurality of components that are executable by the processor, the components comprising: a receiver component that receives a request to create a messaging group for a messaging application, wherein the request includes an indication of one or more entities that are desired to be members of the messaging group; a group creator component that creates the messaging group based at least in part upon the received group creation request, where the messaging group continues over multiple messaging sessions, and where the receiver component receives a group message and recognizes that the group message is to be disseminated to all entities of the messaging group, and where the entities of the messaging group are located within a plurality of different network architectures; and a message transmitter component that transmits the group message to each entity of the messaging group, and where the transmitted group message is delivered to each entity of the messaging group, where each entity is located in one of the plurality of different network architectures.
  • the receiver component, group creator component, and message transmitter component are selected from a group consisting of a common short code, a long code, a virtual MISDN, and a combination of two or more thereof, and the receiver component separates the message into a message content and a message metadata.
  • the different network architectures are selected from a group consisting of: a mobile web network, a web network a short message service network, an email network, an instant messenger network, an Internet protocol-based network, and a combination of two or more thereof.
  • the computing device may be used in a system that can be used to receive and transmit messages pertaining to a group messaging integration system and/or used to retain data pertaining to a group messaging integration system.
  • the computing device includes at least one processor that executes instructions that are stored in a memory.
  • the instructions may be, for instance, instructions for implementing functionality described as being carried out by one or more components discussed above or instructions for implementing one or more of the methods described above.
  • the processor may access the memory by way of a system bus illustrated as the dark line connecting the individual elements in FIG. 13.
  • the memory may also store data pertaining to a group messaging integration system, identities, etc.
  • the computing device additionally includes a data store that is accessible by the processor by way of the system bus.
  • the data store may include executable instructions, data pertaining to a group messaging integration system, et cetera.
  • the computing device also includes an input interface that allows external devices to communicate with the computing device. For instance, the input interface may be used to receive instructions from an external computer device, receive instant messages to be transmitted, et cetera.
  • the computing device also includes an output interface that interfaces the computing device with one or more external devices. For example, the computing device may transmit data to a personal computer by way of the output interface.
  • the computing device may be a distributed system. Thus, for instance, several devices may be in communication by way of a network connection and may collectively perform tasks described as being performed by the computing device.
  • platform As used herein, the terms "platform,” “component” and “system” are intended to encompass hardware, software, or a combination of hardware and software. Thus, for example, a platform, system or component may be a process, a process executing on a processor, or a processor. Additionally, a component or system may be localized on a single device or may be distributed across several devices.
  • the GMI platform may include computer-executable instructions, such as program modules, being executed by a personal computer.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • program modules may be located on both local and remote memory storage devices.
  • embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product which is embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, and so forth
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart and/or block diagram block or blocks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention porte sur un système d'intégration de messagerie de groupe. Un procédé de communication employé par le système d'intégration de messagerie de groupe comprend l'envoi et la réception d'une communication électronique entre une pluralité d'utilisateurs opérant dans une pluralité d'architectures de réseau différentes, un serveur étant en communication avec chacun des utilisateurs ; une diffusion à partir de l'un des utilisateurs d'un message identifié par un numéro généré par le logiciel de messagerie, la réception du message, puis le traitement du message à l'aide du numéro, enfin la recherche d'une pluralité de groupes à l'aide du numéro et l'envoi d'une pluralité de messages de réponse à l'aide du même numéro, la pluralité de messages de réponse étant envoyés à la pluralité d'utilisateurs localisés dans chacune des architectures de réseau différentes.
PCT/US2011/001044 2010-06-09 2011-06-08 Système, procédé et appareil d'intégration de messagerie de groupe WO2011155996A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US35306910P 2010-06-09 2010-06-09
US61/353,069 2010-06-09

Publications (2)

Publication Number Publication Date
WO2011155996A2 true WO2011155996A2 (fr) 2011-12-15
WO2011155996A3 WO2011155996A3 (fr) 2012-02-16

Family

ID=45097139

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/001044 WO2011155996A2 (fr) 2010-06-09 2011-06-08 Système, procédé et appareil d'intégration de messagerie de groupe

Country Status (2)

Country Link
US (1) US20110307565A1 (fr)
WO (1) WO2011155996A2 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9727924B2 (en) * 2011-10-10 2017-08-08 Salesforce.Com, Inc. Computer implemented methods and apparatus for informing a user of social network data when the data is relevant to the user
WO2013112940A2 (fr) * 2012-01-25 2013-08-01 Socialparent, Inc. Plate-forme de mise en réseau de familles sociales
WO2013131979A2 (fr) * 2012-03-06 2013-09-12 Kernan Colm Système de communication pour des messages textes
US20150312193A1 (en) * 2012-11-30 2015-10-29 Conversepoint Llc Systems and methods for accumulating messages in a messaging conversation
US10126927B1 (en) 2013-03-15 2018-11-13 Study Social, Inc. Collaborative, social online education and whiteboard techniques
CN104732331B (zh) * 2015-02-13 2017-04-12 腾讯科技（深圳）有限公司 分组管理方法、装置和系统
US9935906B2 (en) 2015-06-08 2018-04-03 International Business Machines Corporation Selectively unmuting electronic messaging conversations
US11107020B2 (en) * 2019-03-15 2021-08-31 Microsoft Technology Licensing, Llc Intelligent task suggestions based on automated learning and contextual analysis of user activity
US10999231B1 (en) * 2019-03-29 2021-05-04 Amazon Technologies, Inc. User defined application code for electronic mail

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1220501A2 (fr) * 2000-12-27 2002-07-03 Nokia Corporation Création de groupes pour terminals de communication sans fils
EP1253770A2 (fr) * 2001-04-27 2002-10-30 Nokia Corporation Système de transmission d'annonces de groupe
EP2096837A1 (fr) * 2004-06-15 2009-09-02 Orange Personal Communications Services Ltd. Fourniture de services groupés dans un réseau de télécommunications
EP2117164A1 (fr) * 2001-12-13 2009-11-11 Telefonaktiebolaget L M Ericsson (Publ) Procédé et dispositif de diffusion dans un réseau point à point

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006086939A1 (fr) * 2005-02-17 2006-08-24 Infineon Technologies Ag Gestion de groupes dynamiques dans un systeme de communication cellulaire a poussoir de conversation
US20080040437A1 (en) * 2006-08-10 2008-02-14 Mayank Agarwal Mobile Social Networking Platform
US9544180B2 (en) * 2007-08-31 2017-01-10 Qualcomm Incorporated Techniques for group messaging on a mobile computing device
US7729366B2 (en) * 2007-10-03 2010-06-01 General Instrument Corporation Method, apparatus and system for network mobility of a mobile communication device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1220501A2 (fr) * 2000-12-27 2002-07-03 Nokia Corporation Création de groupes pour terminals de communication sans fils
EP1253770A2 (fr) * 2001-04-27 2002-10-30 Nokia Corporation Système de transmission d'annonces de groupe
EP2117164A1 (fr) * 2001-12-13 2009-11-11 Telefonaktiebolaget L M Ericsson (Publ) Procédé et dispositif de diffusion dans un réseau point à point
EP2096837A1 (fr) * 2004-06-15 2009-09-02 Orange Personal Communications Services Ltd. Fourniture de services groupés dans un réseau de télécommunications

Also Published As

Publication number Publication date
WO2011155996A3 (fr) 2012-02-16
US20110307565A1 (en) 2011-12-15

Similar Documents

Publication Publication Date Title
US20110307565A1 (en) Group messaging integration system, method and apparatus
US20170302780A1 (en) Calling for Instant Messaging and Recording Instant Messaging Call Specific Conversation
US11677878B2 (en) Methods and systems for notifications in communications networks
US8769418B2 (en) Enhanced message handling
US8990329B1 (en) Access control list for a multi-user communication session
US20120240062A1 (en) Text-based messaging application cloud
US20160142889A1 (en) Methods and systems relating to visual communications
US8849322B2 (en) Systems and methods for sharing threaded conversations on mobile communications devices
US20170318443A1 (en) Data assistance application for mobile devices
US11146519B1 (en) Techniques for multi-agent messaging
CN103581111B (zh) 一种通信方法及系统
US10592865B2 (en) Methods, systems, and computer readable media for managing social interaction histories
WO2017214212A1 (fr) Modification dynamique de message sortant
US20120166561A1 (en) Multi-Channel Dynamic Response Communication Engine
US20070112927A1 (en) Apparatus and method for transmitting a message
US20150066641A1 (en) Enhanced consumer engagement using advanced communication exchange services
WO2012034539A1 (fr) Procédé et dispositif permettant d'inviter des amis sur un site de réseautage social par le biais d'un terminal de communication mobile
US9559995B1 (en) System and method for broadcasting contents from web-based browser to a recipient device using extensible messaging and presence protocol (XMPP)
CN105704001A (zh) 一种微信服务器消息分发方法及系统
US9439049B2 (en) System and method for message service gateway
WO2015167703A1 (fr) Exécution d'instructions intégrées dans des messages
US9444775B2 (en) Multipurpose internet mail extensions (“MIME”) metadata for group messaging
KR20110079235A (ko) 그룹 메시지 서비스 방법
WO2023095164A1 (fr) Informations d'état d'un message de groupe envoyé ou reçu avec lien de communication dans une plateforme de communication numérique
KR101111228B1 (ko) 그룹 메시지 서비스 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11792782

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11792782

Country of ref document: EP

Kind code of ref document: A2