[go: up one dir, main page]

WO2002013038A1 - Systeme et procede de messagerie universelle radiodiffusee a des membres d'une communaute - Google Patents

Systeme et procede de messagerie universelle radiodiffusee a des membres d'une communaute Download PDF

Info

Publication number
WO2002013038A1
WO2002013038A1 PCT/US2001/041651 US0141651W WO0213038A1 WO 2002013038 A1 WO2002013038 A1 WO 2002013038A1 US 0141651 W US0141651 W US 0141651W WO 0213038 A1 WO0213038 A1 WO 0213038A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
community
subscriber
recipient
members
Prior art date
Application number
PCT/US2001/041651
Other languages
English (en)
Inventor
Patwinder S. Sidhu
Andrew W. Connors
Lee K. Najjar
John Bell
Original Assignee
Mindsurf Networks, 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
Application filed by Mindsurf Networks, Inc. filed Critical Mindsurf Networks, Inc.
Priority to AU2001281400A priority Critical patent/AU2001281400A1/en
Publication of WO2002013038A1 publication Critical patent/WO2002013038A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • 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/06—Message adaptation to terminal or network requirements
    • H04L51/066—Format adaptation, e.g. format conversion or compression
    • 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/48—Message addressing, e.g. address format or anonymous messages, aliases
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/104—Grouping of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
    • H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
    • 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/23—Reliability checks, e.g. acknowledgments or fault reporting

Definitions

  • the present invention relates to an improved system and method for sending a message to members of a community. More particularly, the system and method relate to an improved technique for the sending of a message, preferably entered using the Internet, via every one of the members' personal communication devices.
  • a messaging system and method collects, records and maintains subscriber profiles for a group of people sharing a particular common attribute or association, such as an association with a particular school, business, town, etc.
  • This subscriber profile is collected during a subscription process, arid includes contact information for all communication devices by which a particular person can be reached, including home, work and mobile phone numbers, pager(s), PDAs, email address(es) and web site(s).
  • Each subscriber is then assigned a unique subscriber ID.
  • the entire group of subscribers is termed a community, and the
  • - - community is commonly _ assigned _a _unique community ID. . .
  • a sub-group of the community is assigned a unique sub-community ID.
  • a subscriber wishing to send a message to another subscriber(s) selects an appropriate unique subscriber ID, community ID or sub- community ID assigned to a particular person or group of persons, and typically prepares the message by entering it via the Internet. Also via an Internet interface, system administrators are presented with a series of custom-tailored admin tools for utilizing the present invention whenever they need it.
  • This interface might include grouping mechanisms reflective of a particular community's needs (for example, in a school setting, grouping may be by whole school, grade, class, club/team, blended/extended family, etc.), a suite of preprogrammed message types and messages specific to a particular community, a mechanism for linking the urgency of the message to the ti eframe for delivery, and a message tracking/feedback system.
  • the message is sent over the Internet to all of the selected recipients, via the communication devices that they specified during subscription.
  • the sender of the message it is not necessary for the sender of the message to individually specify the recipients within a particular community or sub-community, or the types of communication devices, since these parameters are pre-set.
  • messages can be universally broadcast to a desired group in a very fast and efficient manner, and the odds that the selected recipients will actually receive the message in a timely fashion are dramatically increased.
  • the present invention is extremely easy to administer and maintain. This is because subscribers are in charge of creating and maintaining their own profiles (although system administrators have access to subscriber profiles), and can create, join or leave a community as desired. Also, since a subscriber generally need only share his or her unique subscriber ID, a subscriber can be included as a message recipient without having to publicly divulge his or her contact information.
  • Fig. 1 is an example of a browser-based control interface according to an embodiment of the present invention.
  • Fig. 2 is an example of a browser-based compose interface according to an embodiment of the present invention.
  • Fig. 3 is an overview of the high level components in an exemplary architecture overview of an embodiment of the present invention.
  • Fig. 4 demonstrates an exemplary network architecture according to an embodiment of the present invention.
  • Fig. 5 is a flowchart demonstrating a subscription process according to an embodiment of the present invention.
  • Fig. 6 is a flowchart demonstrating a process for managing communities according to an embodiment of the present invention.
  • Fig.7 is a flowchart demonstrating a process for joining a community according to an embodiment of the present invention.
  • Fig. 8 is a flowchart .demonstrating, a process for composing a message according to an embodiment of the present invention.
  • Fig. 9 is a flowchart -illustrating- a process- for sending a message to multiple recipients and communication devices according to an embodiment of the present invention.
  • a preferred embodiment of the present invention begins with subscription by persons wishing to utilize the present invention (typically this subscription occurs online; i.e., via the Internet).
  • this subscription occurs online; i.e., via the Internet.
  • members become subscribers by providing multiple contact numbers and indicating their contact preferences for various messaging situations (e.g., emergency and non-emergency).
  • This contact information is part of a unique subscriber profile, and the subscriber profile is stored in a database, for (password- protected) access by a system administrator(s) only.
  • system administrators can also become subscriber via online subscription.
  • Each subscriber is assigned a unique subscriber ID.
  • the entire community of subscribers is assigned a unique community ID.
  • Groups of subscribers within the community e.g., all parents having students in a particular grade at a particular school) make up various sub-communities, each of which is assigned a unique sub-community ID.
  • Each subscriber is associated with one or more roles that belong to a particular community (or sub-community), and each role assigns one or more permissions to a subscriber. These permissions include, inter alia, the ability to send messages to the community, administer the community, add members to the community, view the community members, or perform corresponding functions within sub-communities.
  • Message senders -access and activate the present invention via a designated portal homepage.
  • Activating a special button (referred to hereinafter as a "Blast" button) on the designated portal homepage launches a browser-based- control interface 100,- hich is shown in Fig. 1. Through this interface, a subscriber can send a message.
  • the subscriber can designate (perhaps from a prepopulated list) message recipients in box 101, a type of message in box 102 and a priority level (for example, urgent, timely, standard) in boxes 103.
  • the priority levels may have preset meanings. For example; "urgent” might mean messages are guaranteed to be sent within a specified period of time, and/or are sent multiple times (perhaps until recipient acknowledges receipt); “timely” might mean messages are sent once via all possible communications devices; and "standard” might mean messages are sent once via email only.
  • the subscriber selects the compose link 104 to launch a browser-based Compose interface.
  • FIG. 2 An example of a Compose interface 200 is shown in Fig. 2.
  • the subscriber can compose a subject in text box 201, and then compose the message in onscreen text box 202 (which also allows a selection of prewritten messages), and then preview the message for accuracy. The subscriber can then select either Save as
  • FIG. 3 demonstrates high-level components for an exemplary architecture 300 contemplated for implementation of the present invention.
  • the core component is Application Server 301, which is, for example, BEA weblogic 4.0.
  • the Application Server 301 is preferably a Java engine used to format dynamic web pages and execute business logic.
  • Content is delivered to a user using a web server 302 (via HTML and other mime types as implemented on web browsers, etc.), such as Netscape Enterprise Server 4.0.
  • the web server can communicate with the Application Server 301 using a Netscape Server Applicati Program ⁇ Interface (NSAPI) plugin and a desired weblogic protocol.
  • NSAPI Netscape Server Applicati Program ⁇ Interface
  • SMTP server 303 for email
  • paging server 304 for paging devices
  • speech server 305 for voice devices
  • fax server 306 for fax messages.
  • speech server 305 may comprise a text-to-speech converter such as the Lucent iSpeechTM Server.
  • WAP gateway can be used; however, note that the preferred use of this gateway is not to push messages out to the subscriber, but to enable a subscriber to use a wireless device to browse the message interfaces (such as those shown in Figs. 1 and 2) and initiate Blast messages.
  • Fig. 4 demonstrates an exemplary network architecture of the present invention.
  • a Blast Node 400 is connected to the Public Internet 401 through firewall 402 and router 403, and contains the various servers described above, such as paging server(s) 404, mail server(s) 405 and text-to-speech server(s) 406, web server(s) 407, application servers(s) 408 and database server 409, connected via Ethernet network 410.
  • paging server(s) 404 paging server(s) 404
  • mail server(s) 405 and text-to-speech server(s) 406 web server(s) 407, application servers(s) 408 and database server 409, connected via Ethernet network 410.
  • text-to-speech server 406 is shown as connected via Primary Rate Interface (PRI), through multiplexer 411 and using PRI.
  • PRI Primary Rate Interface
  • PSTN Public Switched Telephone Network
  • Figs. 1 -4 describe examples of user interfaces and architecture according to the present invention.
  • the flowcharts of Figs. 5-9 describe exemplary methodologies- Tor- practicing . -various features of the invention using the elements described with respect to Figs. 1-4. More particularly, Fig ⁇ 5 ⁇ illustrates ⁇ how ⁇ a ⁇ -user subscribes -to a system implementing the present invention.
  • step 501 a user chooses to subscribe and in step 502 enters one or more sets of profile information, including a subscriber ID suggested by the subscriber.
  • such a subscriber profile may simply contain all of the contact information which the subscriber wishes to divulge to the system, such as the subscriber's mobile phone number, email address, etc.
  • the subscriber profile can also be configured in more detail, according to the wishes of the subscriber. For example, the subscriber may designate different communication devices according to the type, content or level of urgency of a message, or according to the sender of the message.
  • the subscriber profile may include that messages marked "timely" (as described above) should be sent only to his or her home telephone, whereas messages marked "urgent" should be sent to all available communication devices. Similar designations could be made regarding the sender of the message, so that, for example, messages from a school principal are given special status.
  • the subscriber profile could also reserve a special email address or mobile phone number for certain types of messages (e.g., urgent messages).
  • a subscriber could choose to have multiple subscriber profiles, with a corresponding number of subscriber IDs, where each profile is configured to a particular need of the user. It is important to note, however, that all of the information included in the subscriber profile (including, as another example, a language preference of the subscriber, which is discussed in more detail below) is completely transparent to other members of the community. -Thus, only knowledge of a particular subscriber ID is required to send a message in the exact manner desired by that subscriber. Moreover (as described in more detail below)7air of the " profile ⁇ information ⁇ can be completely updated and maintained by the subscriber, making a system implementing the present invention extremely easy to administer and utilize.
  • the profile information is submitted in step 503, and in step 504 the suggested subscriber ID is checked to see if it already exists within the system. If it already exists, then the subscriber must enter another subscriber ID in step 505 and then return to step 503. Otherwise, the subscriber is presented with a confirmation page in step 506, and the information is stored in a Lightweight Directory Access Protocol (LDAP) database in step 507.
  • LDAP Lightweight Directory Access Protocol
  • a subscriber is completely responsible for updating his or her subscriber profile.
  • system administrators may have access to the profiles, it is not necessary for the administrators to update all of the subscribers' various contact information.
  • only the subscriber's unique subscriber ID is visible to the other subscribers. Therefore, as will be seen with regard to Figs. 6-8, messages can be sent and the system can be managed/configured entirely based on these unique subscriber IDs, resulting in a system which is fast, confidential, and easy to administer.
  • Figure 6 is a flowchart that demonstrates an exemplary methodology of how communities are managed in the present invention.
  • a subscriber with proper authorization can, at any time, preview, edit, create, modify or delete a community.
  • the methodology of Fig. 6 can apply to either a community as a whole, or to sub- communities thereof ⁇ therefore, in Fig. 6 (as well as in remaining Figs. 7 and 8), the term community, unless indicated otherwise, is used generically to mean either community or sub-community. - - - - - — — - --- —
  • step 601 a subscriber logins into and is authenticated into a system implementing the present invention.
  • Step 602 presents the subscriber with the choice of three possible steps: step 603 to create a community, step 607 to edit a community and step 618 to delete a community. If the subscriber chooses to create a community in step 603, a new community name is required in step 604 and the subscriber is asked to confirm this in step 605, if not then the flow returns to step 603. Otherwise, the community is created and stored in the LDAP database in step 606. In step 607 the subscriber chooses to edit a community.
  • the subscriber can choose to invite members to the community in step 609, edit a community name in step 612, remove members in step 613, or create a sub-community in step 616. Those who are invited are sent an email invitation in step 610 (using subscriber
  • the email message contains links to enable the invitee to subscribe (if currently a non-subscribed user), join the community (if already subscribed) or decline the invitation.
  • the invitation list is saved to the LDAP database in step 611 (the process for joining a community is illustrated in more detail in Fig.7).
  • a sub-community can be created in step 617 from a list of members of the community.
  • Step 614 asks the subscriber to confirm any edits, if the confirmation is not given the subscriber is returned to step 607, otherwise the updated- community is saved to the LDAP database in step 615.
  • the blastor can assign roles to members to allow them to initiate blasts or view the other members.
  • the community manager is automatically authorized to create sub-communities from the commumty.
  • step 618 If the subscriber chooses to delete a commumty in step 618, he or she is prompted to select a community in step 619 and asked to confirm in steps 620 and 621. If the subscriber does not confirm, the flow returns to step 618, otherwise the community is deleted from the LDAP database in step 622.
  • an administrator external to the community. For example, such an external administrator may maintain the user interfaces and system architecture described with respect to Figs. 1-4. Additionally, the external administrator may undertake any of the methodology regarding the process of managing the communities just described with respect to Fig.
  • the external administrator may also be responsible for maintaining, grouping and listing the subscriber profiles which a community manager accesses in order to, for example, compose an invitation list, create a sub-community, and so forth.
  • the external administrator preferably has access to the subscriber profiles.
  • a subscriber in a school setting wishing to create a community or sub-community made up of all elementary school parents can choose from an invitation list listing all such parents, where the list is made available by the external administrator.
  • the responsibilities and capabilities just described may be divided in any desired manner between the external administrator and one or more members of the community (such as, in a school setting, the school principal), and still be within the scope of the invention.
  • managing communities according to the present invention is extremely fast, easy and convenient.
  • the community manager need not be concerned that the other subscribers' contact information is outdated, since each subscriber can update his or her own contact information as necessary.
  • FIG. 7 shows a flowchart that demonstrates an exemplary methodology of how a subscriber joins a community.
  • the subscriber is authenticated into the system in step 701, and then selects to join a community in step 702, before selecting a community in step
  • Steps 701 to 703 can be performed, for example, by inserting an appropriate URL
  • step 610 a check is made to determine if the subscriber has been invited; if the subscriber has been, then the invitation list is updated to show the subscriber has accepted in step 705, and the subscriber is then added to the community in step 707. Otherwise, another check is made in step 706 to determine if the community will allow anyone to add themselves; if not the subscriber is denied, otherwise the subscriber is added to the community in step 707.
  • the new member can select which aspects of his/her profile, if any besides his/her unique subscriber ID, are visible to the community.
  • FIG. 8 is a flowchart that demonstrates an exemplary methodology of how a subscriber composes a blast message.
  • the subscriber is authenticated into the system in step 801 and then selects to send a message step 802.
  • the subscriber can choose to select a message template in step 804, and then continue to enter or edit a message header in step 805.
  • a message body is entered or edited, and then a recipient list is formed in step 807 comprising a list of zero, one or more communities and zero, one or more individuals.
  • the subscriber is prompted to either send the message immediately in step 808, or send later in step 809. Whether the message is to be sent now or later, the message is previewed in step 810 and sent in step 811.
  • the blastor can initiate a blast in a simple three-step process: select an appropriate community, create a text message, and press a button to blast. Because a single community ID for each community (and/or a single subscriber ID for each subscriber) is all that is required to blast the message, the message can be sent as quickly as possible to all of the blastees' communication devices at once. Additionally, as referred to above, it is not necessary for a blastor to have access to blastees' personal and confidential information (such as unlisted phone numbers, etc.), since the blastor sees only the community/ subscriber ID.
  • the blastor may be updated as to its delivery status. That is, the blastor may be informed as to wfiether the message is completed, pending or undeliverable. The blastor may also be informed as to the percentage completion/incompletion rate, and/or the time the message(s) were delivered.
  • FIG. 9 is a flowchart that demonstrates an exemplary methodology of how a blast message is propagated to the recipients.
  • a blast message is entered into the system (as just explained with respect to Fig. 8) and the community parts of the recipient list are expanded in step 902.
  • all the recipients are expanded into a list of delivery types and delivery addresses in step 903, together with the message to be sent to each delivery address.
  • each recipient is checked to confirm that they agree to accept the message in step 904.
  • the messages are sent, for example, by email in step 909, by paging server in 910 and telephone in step 911.
  • the present invention has been described in conjunction with the above embodiments, it should be noted that these embodiments are designed only to illustrate, and not limit, the present invention.
  • the present invention might also include bilingual universal messaging, in which school messages can be sent in either English or Spanish.
  • the present invention may incorporate automatic translation of English messages to Spanish and vice versa.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Computing Systems (AREA)
  • Strategic Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Marketing (AREA)
  • Game Theory and Decision Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé et un système destiné à contacter de façon rapide et fiable des membres d'une communauté. Les utilisateurs deviennent membres de la communauté en établissant un contact et en fournissant d'autres informations pendant un processus d'abonnement afin d'établir un profil d'abonné (502). On attribue ensuite une identité unique (504) aux abonnés et ces derniers sont responsables de la mise à jour et de la maintenance de leurs profils (502). Les abonnés sont groupés en fonction de leur identité d'abonné afin de former une communauté et/ou diverses sous-communautés possédant également des identités uniques. Des messages basés uniquement sur ces identités sont ensuite envoyés, et le statut de membre de la communauté et des sous-communautés est attribué en utilisant uniquement ces identités uniques. Ainsi, la confidentialité de l'abonné est conservée et l'administration du système est facilitée. En outre, les messages sont généralement entrés via Internet, et envoyés en se basant uniquement sur les identités uniques, de sorte que les messages puissent être envoyés à un individu ou à un groupe en un temps pratiquement aussi court que pour entrer ou sélectionner un message désiré.
PCT/US2001/041651 2000-08-10 2001-08-10 Systeme et procede de messagerie universelle radiodiffusee a des membres d'une communaute WO2002013038A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001281400A AU2001281400A1 (en) 2000-08-10 2001-08-10 System and method for universal broadcast messaging to members of a community

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US63587500A 2000-08-10 2000-08-10
US09/635,875 2000-08-10

Publications (1)

Publication Number Publication Date
WO2002013038A1 true WO2002013038A1 (fr) 2002-02-14

Family

ID=24549478

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/041651 WO2002013038A1 (fr) 2000-08-10 2001-08-10 Systeme et procede de messagerie universelle radiodiffusee a des membres d'une communaute

Country Status (2)

Country Link
AU (1) AU2001281400A1 (fr)
WO (1) WO2002013038A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007062473A1 (fr) * 2005-11-30 2007-06-07 Nicole Shirley Haliday Procede et systeme de publication d’annonces

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5956394A (en) * 1995-11-16 1999-09-21 Lucent Technologies Inc. Common treatment of calls from subscribers served by different types of telecommunication equipment
US6253327B1 (en) * 1998-12-02 2001-06-26 Cisco Technology, Inc. Single step network logon based on point to point protocol

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5956394A (en) * 1995-11-16 1999-09-21 Lucent Technologies Inc. Common treatment of calls from subscribers served by different types of telecommunication equipment
US6253327B1 (en) * 1998-12-02 2001-06-26 Cisco Technology, Inc. Single step network logon based on point to point protocol

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007062473A1 (fr) * 2005-11-30 2007-06-07 Nicole Shirley Haliday Procede et systeme de publication d’annonces

Also Published As

Publication number Publication date
AU2001281400A1 (en) 2002-02-18

Similar Documents

Publication Publication Date Title
US11445033B2 (en) Viral engine for network deployment
US10860784B2 (en) Collaborative email with hierarchical signature authority
US9059955B2 (en) System controlling use of a communication channel
EP1222549B1 (fr) Gestion du flux d'informations en temps reel
US6275575B1 (en) Method and system for coordinating and initiating cross-platform telephone conferences
JP4979193B2 (ja) サーバのプロジェクト・カレンダ上で発行されたイベントを複数のクライアントそれぞれの「パーソナル・カレンダ及びスケジューリング」アプリケーション・データと統合するための方法、システムおよびコンピュータ・プログラム
CA2578632C (fr) Systeme et procede de gestion de l'information et de collaboration
EP1608190B1 (fr) Prestation de services collectifs dans un réseau de télécommunication
US7577711B2 (en) Chat room communication network implementation enabling senders to restrict the display of messages to the chat room chronological displays of only designated recipients
US20060090013A1 (en) Group communication and collaboration method
US20020141560A1 (en) Group establishment system and method
WO2002046957A1 (fr) Procede permettant de distribuer des messages
US9213995B1 (en) System and method for linking networks to one another and sharing resources between members
WO2002013038A1 (fr) Systeme et procede de messagerie universelle radiodiffusee a des membres d'une communaute
KR20020034551A (ko) 협동 작업 지원 시스템
KR101788128B1 (ko) 강사를 위한 다중 사용자 커뮤니케이션에서의 수신자 필터링을 통한 선택적 커뮤니케이션 및 미등록자 메시지 송신 지원 방법
KR100570431B1 (ko) 메신저콜서비스에서 전달 메시지 예약 장치 및 그 방법
KR20020092730A (ko) 그룹 전자메일링 시스템 및 이를 이용한 송수신 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: COMMUNICATION PURSUANT TO RULE 69 EPC (EPO FORM 1205A OF 010803)

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP