WO2000079826A1 - A method and an arrangement relating to groups of communicating users - Google Patents
A method and an arrangement relating to groups of communicating users Download PDFInfo
- Publication number
- WO2000079826A1 WO2000079826A1 PCT/SE2000/001255 SE0001255W WO0079826A1 WO 2000079826 A1 WO2000079826 A1 WO 2000079826A1 SE 0001255 W SE0001255 W SE 0001255W WO 0079826 A1 WO0079826 A1 WO 0079826A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- group
- community
- users
- members
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- 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/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
Definitions
- the present invention relates to a method and a digital telecommunication system where groups of users of communication devices exchange information between each other.
- the system which in the following will be denoted as the mobile community, offers mobile group communication services, enabling groups of people to stay in touch, coordinate events and share information anywhere and anytime via mobile devices such as mobile phones and mobile internet devices. anytime via mobile devices such as mobile phones and mobile internet devices.
- the services offered include group voice messaging which offers private voice mailboxes that can be accessed and used by groups of people.
- group voice messaging offers private voice mailboxes that can be accessed and used by groups of people.
- an SMS is sent to group members to inform them that they should check the group voice mailbox.
- An e-mail is sent to users who do not have a mobile phone.
- group talk Another service offered is group talk which allows users to talk to each other simultaneously on mobile phones and fixed-line phones.
- an SMS is sent to group members to inform them that they should call in to join the group talk.
- Another service offered is group text messaging which allows group messaging via SMS.
- the sender only needs to send a single SMS which is sent to the group members.
- a group web service which includes text chat, group contact lists, calendar and information lists, such as e.g. recommendations regarding restaurants, cinemas etc.
- the group web services are accessible via mobile and stationary internet devices such as WAP-phones and desktop PC's.
- Groups are created and managed via a web site, and users may create and participate in any number of groups with friends, business colleagues, project team members, family members, sports club members etc.
- Privacy is obtained through authorization, where each member is identified through a user ID and an access code.
- user ID typically, for mobile phone users, their mobile phone number acts as user ID.
- Groups of users may be either static or dynamic.
- Static groups are preferably used when a user wants to leave messages to, or communicate with, the same people regularly.
- Dynamic groups are used when recipients are unique for each message or call. Dynamic groups exist for one message or call, and are created by selecting recipients via the WWW or via telephone.
- Broadcast groups are used for one-to-many communication, where one single member, the messenger, is allowed to leave messages in the group mailbox. Other members can read messages and leave responses to the messenger only.
- Mobile Community include access at any time and anywhere, convenience in that a user may communicate with several people simultaneously via a single phone call.
- Figure la shows a schematic view of a system according to the invention.
- Figure lb shows a schematic end-user view of a system according to the invention.
- Figure lc shows a schematic administrator view of a system according to the invention.
- Figure Id shows a schematic view of an application server included in a system according to the invention.
- Figure le shows a schematic view of a SM server included in a system according to the invention.
- Figure If shows a schematic view of a group talk service included in a system according to the invention.
- Figure lg shows a schematic view of a group message service included in a system according to the invention.
- Figure 2a shows a schematic process view of a system according to the invention.
- Figure 2b shows a schematic view of SM server processes in a system according to the invention.
- Figure 3a shows a schematic hardware deployment view of a system according to the invention.
- Figure 3b shows a schematic node configuration view of a system according to the invention.
- Figure 3c shows a schematic multiple node configuration view of a system according to the invention.
- Figure 4 shows a schematic view of service application layers in a system according to the invention.
- Figure 5a shows a schematic view of load balancing in a system according to the invention.
- Figure 5b shows a schematic view of load balancing in a system according to the invention.
- Figure 6 shows a schematic view of system interfaces.
- MS Mobile station i.e. a cellular phone.
- MSC Mobile switching center.
- ORB Object request broker
- SMS Short message services SM Short messages . SMS Short message services.
- the architecture is most easily described using five views, which represent different ways of observing the system: a logical view, a process view, a deployment view, an implementation view and a use-case view.
- the logical view describes the architecturally significant parts of the design model, such as its decomposition into subsystems, service packages, and classes.
- the process view describes the system's decomposition into lightweight processes (single threads of control) and heavyweight processes (groupings of lightweight processes) .
- the deployment view illustrates the configuration and a mapping of processes to each processor.
- the implementation view describes the decomposition of the software into layers and subsystems in the implementation model. Sometimes referred to as component view.
- the use-case view illustrates how the software actually works by giving a few selected use cases or scenarios.
- the view also explains how the various model elements contribute to the functionality.
- the use cases or scenarios given here are chosen because they represent some significant, central functionality of the final system, or for their architectural coverage (they exercise many architectural elements) or to stress or illustrate a specific, delicate point of the architecture .
- the logical view is chosen because they represent some significant, central functionality of the final system, or for their architectural coverage (they exercise many architectural elements) or to stress or illustrate a specific, delicate point of the architecture .
- Figure la illustrates the architecturally significant parts of the design model, such as its decomposition into subsystems and service packages. For each significant package, its decomposition into classes and class utilities is described.
- Figure 1 shows the major components of the system: End User interface components, Administrator interface components, Mobile Community services (with web services for end users and administrators and community services like group talk and group messages) , Network provider for SMS services, and SMPT provider, for sending e-mail.
- End User interface components Administrator interface components
- Mobile Community services with web services for end users and administrators and community services like group talk and group messages
- Network provider for SMS services
- SMPT provider for sending e-mail.
- FIG. lb illustrates, there are four different methods of end user - system interaction: WWW browser, Mail client, Phone, and Mobile phone.
- the user uses the WWW browser to connect to the system to set up and manage his/her profile and communities and the mail client is used for different notifications sent from the system.
- a mobile station may receive notification messages (SM) from the system via the network providers switching center.
- SM notification messages
- a mobile phone is used to manage the community services like group talks and group messages.
- a normal phone can also be used, like the mobile station, to manage the community services .
- FIG. lc illustrates, there are three different methods of administrator - system interaction: WWW browser, Mail client, and Mobile phone.
- the administrator uses the WWW browser to connect to the system to perform system administrative tasks.
- the mail client and the mobile phone are used for different notifications sent from the system.
- Mobile Community Services system will interact with the network provider and the SMSC using a secure protocol.
- the SMTP provider is a mail server that route mail sent from the mail services to users mailboxes on the Internet .
- Mobile Community Services (MC services) :
- the web server handles incoming HTTP requests; retrieves information, and sends it back to the client. If the HTTP-request is targeted at a JSP (Java Server Page) , the request is handed over to the JSP-engine.
- JSP Java Server Page
- the system runs in an application server but no business or data logic is implemented as Enterprise Java Beans.
- the application server is used as execution environment for Java Server Pages and for the Connection Pool only.
- the application server comprises of the following three major components (access layers) : JSP engine (compiler/ - executioner) , Business services, Data services, and Connection Pool.
- the JSP engine is a Java class that creates a Java servlet code out of the jsp-code and then compiles it into a Java servlet class.
- the class code is cached for performance .
- Design packets in the business services layer contain most of the service logic of the system. All access of data services from the user services layer is handled through the business services layer.
- the following design packets are developed within the Mobile Community Services system: crypto, sms, mail, administrator, alarm, broadcast, community, event, grouptalk, invitation, message, news, statistics, trafficdata, user, and util .
- the data services design packets consists mainly of components and classes to access entity objects from the database. This includes creating new, modifying, and removing existing entities as well as searching and listing functionality. The packets are not listed here. For a complete list of available packets, consult the database design. Examples are: User, Event and invitation.
- the mail services include services for sending email (SMTP) .
- SMTP email
- the mail is sent through the SMTP provider.
- SM services include services for sending email (SMTP) .
- the SM server provides functionality to send SM to mobile phones from a client application in a LAN.
- the system consists of an SMS server that acts as an interface to the network operator's SMS gateway and a number of SMS clients that serve applications with the possibility to send SM requests to the SMS server.
- the Group Talk System provides a service for community groups to join specific group calls.
- the service is available from a mobile phone or a normal fixed phone.
- the group talk services does not use any of the application server functions.
- the business and data logic is called directly from the CT run-time environment through a DLL .
- Group talk services Group call capabilities, Recording voice messages, Pre-recorded audio messages for information from the system to the user, Touch-tone input for login to system, setting up and joining a group call, and Dial out enabling the system to make calls to users and play pre-recorded messages.
- the Group Message System provides a service for community groups to record and listen to voice messages located in a message store.
- the service is available from a mobile phone or a normal fixed phone.
- the group message services does not use any of the application server functions.
- the business and data logic is called directly from the CT run-time environment through a DLL.
- All voice messages is stored as flat binary files in the file system of the OS of choice.
- META- information about recorded messages is stored in the RDBMS .
- the realisation and implementation of this message is store is TBD .
- the following functionality will be provided within the
- Group Message services Recording voice messages, Listening to voice messages, Pre-recorded audio messages for information from the system to the user, Touch-tone input for login to system, recording messages and navigation through system functions, and Dial out enabling the system to make calls to users and play prerecorded messages
- IBM DB2 relational database
- All voice messages for the Group Message Services are stored as flat binary files in the file system of the OS of choice.
- META-information about recorded messages is stored in the RDBMS .
- the SM server application consists of one permanent lightweight process running the administration interface. From the GUI thread a server thread is started and stopped. The server thread handles new client connections and administrates the requests.
- the GUI and server threads exchange data mainly by using a common instance of a class containing the server characteristics . Beside these single threads, there are an arbitrary number (upper limit controlled by the server administrator) of session threads that are started and stopped as clients connect and disconnect.
- the server thread creates the session threads, one for each client connection.
- the session threads take over the client connections and execute the requests .
- RDBMS Resource Description
- Any META information about recorded voice messages is also stored in the RDBMS.
- the server (or rather, service) is build on the run-time engine of the selected CT-platform and uses the same business and data logic as the web application.
- Figure 3a shows the system's physical network (hardware) configuration on which the software is deployed and run.
- the configurations indicate the physical nodes (computers, CPUs) that execute the software, and their interconnections (bus, LAN, point-to-point, and so on.) Included is also a mapping of processes from the process view onto physical nodes.
- minimum configuration the system is described with different configurations, called minimum configuration and multiple node configuration.
- Figure 3b illustrates a "minimum" configuration, which is in reality not a single node due to the two parallel systems and the Data server and SMS server. All telephony related services execute in one node and the web services, the application server and the SMS server execute in the other. Depending on the type of toolkit/api used in the phone-related applications, the phone services may be able to use the application server for distributed business objects and access to the RDBMS.
- the telephony server is equipped with several PRI -cards and DCB-cards (for conferencing) . These cards are connected through a SC-bus for internal communication between CT-resources .
- JSP Java Server Pages
- this node is configured with a web server and the application server of choice.
- the SMS service may also execute in this server, but there is a choice to install and execute this application on a separate server.
- the Data server executes the RDBMS. This is also the server where all messages are stored.
- Figure 3c shows a "multiple-node" configuration, where the amount of concurrent and registered users demands multiple web servers and phone servers.
- the servers in the multiple node configuration is explained below.
- Two computers can be connected directly via ATM, but if three or more computers are to be connected, this is best done through an ATM- switch.
- JSP Java Server Pages
- Adding yet another physical web server scales the web servers.
- the incoming requests for web resources are distributed between the web servers through round-robin configuration of the DNS , or by doing a sequentially redirecting of the requests through a front -door web application.
- All web servers have the same host name, but different IP-addresses.
- the DNS-server that resolves a host name to an IP-address does this in "round-robin" order so that the requests are distributed to all available web servers .
- Database server In the Mobile Community system, adding another server does not scale the database.
- the database should run on such hardware that it could be upgraded with more CPU, disks and memory when needed, preferably from the beginning to avoid minimum downtime because of hardware upgrades .
- the MC-system must be aware that more disks have been added for the voice files. Changing the system parameters (configuration) for the MC-system does this.
- SMS server This is the node where the SMS server executes. This server is able to handle thousands of SMS-requests and does not need to be scaled into multiple nodes for the MC-system. The SMS server may very well execute in one of the application server computers, because of the low impact on the system resources.
- Figure 4 shows the decomposition of the software into layers and subsystems in the implementation model.
- the mobile and fixed phone users use an IVR (Interactive Voice Response) system to navigate through the different applications and functions available through the phone interface .
- IVR Interactive Voice Response
- the CT applications are running on top of the selected CT runtime engine.
- GUI Graphic User Interface
- HTML Hypertext Mark-up Language
- the JSP Java Server Pages
- the presentation logic (servmg/buildmg HTML) and is responsible for instantiating and executing the business logic objects.
- Business and data logic The business and data logic is implemented as normal Java classes and not as EJB, because of performance and because the CT application has problems accessing EJB from their run-time environment.
- the Application server should be scalable by hardware. For detailed description of scaling, see "Deployment view" above.
- Load balancing can be configured for three services in the system: Web servers, Phone servers, and Application servers . Load balancing of web servers
- the incoming requests for web resources are distributed between the web servers through round-robin configuration of the DNS, or by doing a sequentially redirecting of the requests through a front -door web application.
- All web servers have the same host name but different IP- addresses.
- the DNS-server that resolves a host name to an IP-address does this in "round-robin" order so that the requests are distributed to all available web servers.
- the incoming phone lines are configured according to the standard "Line hunting" procedure that distributes the incoming calls sequentially to the available PRIs.
- a conference resource handler in the CT-application will allocate the conference resources.
- the conference handler will store status information about all conference resources in RDBMS. Analysing which device that for the moment has most idle conference resources makes the selection of conference device. Load balancing of application server
- Load balancing is built into the application server software. If another application server is installed, this is initially configured to be aware of the other existing application servers. The load balancing is then handled by the software through AS to AS communication.
- SNMP-agents Software and hardware will be monitored by an SNMP fault management system. SNMP-agents will be installed for each server and hardware device. The agents will monitor the devices for errors and report to an SNMP management application if errors occur. Overload and congestion is also to be considered as an error.
- Monitored Hardware includes: PRI- boards , Audio Conference boards, Network controller boards, CPU-boards and ATM-switch.
- Monitored Software includes: CT-application, Webserver, Application server, SM server, RDBMS, and Windows NT. Failure recovery
- the system is not configured with any fail -over functionality.
- install multiple network adapters use double power supply units in the servers, all disks should be RAID- configured for safety (1, 5 or combination) , and CT- servers shall continue to execute Group Talk and Group Message calls even though another CT- server is out of service .
- System interfaces Figure 6 illustrates how the system according to the present invention interfaces other network elements such as an MSC, a local exchange, an SMS-C and the Internet.
- the system connects with the MSC(s) of one GSM operator through a number of EURO-ISDN devices (30B+D.) Telephony interfaces
- the Mobile Community service is accessed via one GSM number. This number is routed to a number of ISDN PRA interfaces (2 Mb, 30 B+D) residing in one or several MSCs.
- the MSC(s) must support line hunting over the full set of PRA lines.
- the normal initial configuration is with 6 PRA.
- both incoming calls to access the Mobile Community service
- outgoing calls to make dial-up notifications for Group Talk from the Mobile Community system
- an alternative is to use ISDN PRA lines to the fixed network.
- time distribution of dial-out notifications is available with the Mobile Community system. This feature distributes dial -out notification calls within a certain group. The time difference between calls within a group is 0.5 seconds. This is done in order to avoid congestion on the GSM paging channel within one cell.
- the specification of the interface includes: Euro- ISDN, CRC4 activation and no ecco cancellation equipment between the MSC and the Mobile Community system.
- This interface is carried between the operators MSC switch site(s) and the Mobile Community operation center via G.703 lines.
- the Mobile Community system interfaces a Short Message service provider via the interface "UCP over TCP/IP" .
- This interface has SSL encryption.
- the Short Message service provider could be the GSM partner, but it is also possible to use other service providers in case cross- network SMS are not available within the country where the system is set up.
- the SMS originates from a specific server located inside the Mobile Community system firewall. A port must be opened in the firewall for this communication. The port number is configurable.
- SMS queuing is used to handle SMS load peaks .
- Internet interface Internet can be used by the Mobile Community system users to configure their groups, invite more members, create new groups etc.
- Hypertext Transfer Protocol as defined in RFC 2616 and RFC 2068 is used.
- RUP Rational Unified Process
- actor instance is someone or something outside the system that interacts with the system.
- An actor type defines a set of actor instances, in which each actor instance plays the same role in relation to the system.
- a use-case instance is a sequence of transactions a system performs that yields an observable result of value to a particular actor.
- a use-case class defines a set of use-case instances.
- An administrator is a registered and authenticated person that has the privilege to administrate the Mobile Community system, or specific parts of the system. Use cases involving administrators almost always require strong authentication.
- the preferred method of administrator - system interaction IS via a WWW browser.
- Guest A guest is a person who accidentally or determined surfs ' the Mobile Community web site or calls the system for registration. Being a guest seldom requires authentication. As a guest registers for member services he is upgraded to user actor. There are three different preferred methods of guest - system interaction: WWW browser, and Mobile or stationary phone User.
- a user is a registered and authenticated person who actively uses the member services provided by the Mobile Community system. Use cases involving users most often requires authentication. There are three different preferred methods of user - system interaction: WWW browser, and Mobile or stationary phone User.
- An Instant user is a person that is invited to a group talk but that is not registered with the system.
- an instant user is a person that is temporarily invited by a user to participate in a group talk.
- Instant users can never initiate their own group talks.
- User description (not mandatory, the user may add a short description of himself that is shown in other users contact lists if the user has chosen to be visible as described above) .
- the guest is not allowed to register an email address or a phone number that already is used in the system by another user.
- the system will verify, using a random generated access code sent to that specific phone as SMS, that he at least actually has access to the mobile phone he registers.
- a notification will also be sent to that address i.e. this is the only possibility for a user with a non-SMS capable phone to get a notification.
- the new user is given a unique member number, which in normal cases is the phone number registered. If he elects not to register phone number, a unique member number is to be generated by the system. This is also the case if the new user registers a non-SMS capable phone.
- a personal user profile is created describing the provided information, privileges, etc of the new user. If he have received invitations for any communities, he is immediately prompted to join them.
- Purpose To gain access to the member services. Description: This is the web site entry point. Here the user may choose to access either register, login, or view any of the public information web pages like service introduction, demo, or company information.
- the anonymity degree can be changed using the radio button that is assigned to each community.
- the "My communities" page contains a string that informs the user when he used the system last time. In this information it is included whether he used the TUI or web interface .
- Purpose To enter missing data if user was registered from TUI . Description: If the user was registered from a phone (fixed or mobile) and it is the first web login after registration, a new web page is opened where he is asked to give additional missing user data. At a minimum he should enter his name or alias. The user is not transferred to his start page until at least his name or alias is given.
- Actors User. Purpose: To enter the name of a community created via TUI.
- a user can only see the interface for the functions and operations that the user is allowed to perform. I.e. the functions and operations that are assigned to the community owner can only bee seen by the community owner.
- Purpose Gives the user a summary of community news and updates . Description: For each community the user can view new messages, new members or members who left the community, new community owner, if any members have updated their contact info, etc. Each new Group Message or Group Talk recording notification is attached with a time stamp.
- Actors User, Guest. Purpose: Create a new community.
- the user creates a new community by naming the community.
- the person may also choose to assign a category to the community and a description of the community.
- the user may invite members by selecting people from his existing contact list (not possible for a guest) or by entering them manually.
- the invitation shall contain the names/alias of other invited persons (users or guests) . This is applicable both to the e-mail invitation sent out and on the "New invitation" page on the WEB.
- Another way of inviting members is to send them an invitation URL.
- an alert might be sent to the community owner.
- An alert might also be sent to the invited person. It is possible to configure these alerts independent of each other, e.g. in one implementation of the system both kinds of alerts might be used, but in another implementation, only the alert directed to the community owner might be used.
- the user If the user invites a person with a forbidden number (i.e. the user states a number stored in the "Dialing Rules File") the user shall be notified and that invitation is cancelled.
- a forbidden number i.e. the user states a number stored in the "Dialing Rules File
- the creating user becomes the "community owner" .
- Actors User. Purpose: Invite others as members of a community.
- the community owner may invite additional members to his community by selecting people from his contact list or by entering them manually.
- the invitation shall contain the names (or alias) of other invited persons (users or guests) and the users that already are members of the group (these are listed as "member” in the invitation) . This is applicable both to the e-mail invitation sent out and on the "New invitation" page on the WEB. Another way of inviting members is to send them an invitation URL.
- an alert might be sent to the community owner.
- An alert might also be sent to the invited person. It is possible to configure these alerts independent of each other, e.g. in one implementation of the system both kinds of alerts might be used, but in another implementation, only the alert directed to the community owner might be used.
- the user If the user invites a person with a forbidden number (i.e. the user states a number stored in the "Dialing Rules File") the user shall be notified and that invitation is cancelled.
- a forbidden number i.e. the user states a number stored in the "Dialing Rules File
- the user selects which persons to invite to the group by specifying their e-mail addresses separated by comma or semicolon (to allow "copy and paste” from e-mail clients) in the in built mail function of the system.
- the user can write a message to the recipients of the invitation that will be displayed first in the invitation e-mail (followed by a standard description of the service) .
- the user submits the invitation to the system and all recipients will receive the e-mail invitation.
- Actors User. Purpose: Allow a user to quickly set up group
- the user can select from his contact list or enter new persons, i.e. instant users, to invite them to the group talk. If the user invites a person with a forbidden number (i.e. the user states a number stored in the "Dialing Rules File") the user shall be notified and that invitation is cancelled.
- a forbidden number i.e. the user states a number stored in the "Dialing Rules File
- the instant group that is created shall be saved in the system and the user can initiate a group talk and group messages with the participants in the instant group without having to enter their numbers again.
- the instant group is replaced the next time the user creates a new instant group.
- a user can only have one instant group.
- Actors User Purpose: Allows a user to join a community.
- the system prompts the user with new invitations. The user can then choose to
- invitation details For each invitation there is a link to further invitation details, see below regarding invitation details.
- Actors User Purpose: Allows a user to view details of an invitation to which he is invited.
- Purpose Allows the user to create and maintain a list of other users .
- a user is given the possibility to store contacts in a contact list.
- the contact list contains other users in the system that manually are added by the user according to the Add contact use case, see below.
- the contact list consists of the following fields:
- the system is able to maintain a list of up to 999 contacts per user.
- the short codes (1-99) can be assigned to any of the 999 entries in the contact list.
- the short codes are used to address other users when setting up instant groups on the TUI .
- the user can also add contacts by selecting other users that are members of the same communities.
- the system informs that an SMS will be sent to the current mobile phone number inviting the receiver of the message to the system.
- the user is further given the possibility to enter an email address in order to additionally send an email invitation.
- the email is sent out (with the user's e-mail address as sender. If the user has not specified an email address in his profile he can not use this function) .
- the invited person need to register using the TUI or WEB interface as in the normal case.
- Actors User. Purpose: To invite a non-registered person to the system. Description: This use case is invoked by the Add contact use case . The user can invite a person to the system without inviting the person to a specific group.
- This use case is similar to the use case Invite Friend To The System Via SMS. The difference is that an SMS will not be sent and that the user is informed that he must specify an email address in order to send the invitation.
- the email invitation is identical to the corresponding part in use case Invite Friend To The System Via SMS. Only users with a registered email address can use this function.
- Actors User. Purpose: To assign a short code for a contact in the contact list.
- the user can generate a short code to any of the contacts in his list by using the function for automatic generation of short codes. Lowest available number is assigned.
- the e-mail should be sent to all members of the community that have registered to the system with an e-mail address, Only users that have chosen to have their profile visible to other users in that community should have their addresses displayed to others.
- the sender's name and e-mail address displayed on the sent e-mail should be the community member performing the action.
- the user must have an email address registered in order to be able to send a mail, otherwise this function can not be used.
- the system supports the use of an adaptable area with text fields to be filled out by the guest (name, e-mail address and mobile number) .
- the adaptable area will be placed on partner sites and integrated with the content shown on that site.
- the guest is forwarded to the login page of the MC system and the user information shall appear in the correct fields.
- the guest has to review the conditions of membership (or accept without reviewing) and submits the registration request to the system.
- Actor User, Guest Purpose: To get access to all Incirco country specific sites .
- Purpose Modify ones own personal data. Description: A user may modify his own personal profile.
- the user may for example elect to change his phone number. If the mobile phone number is changed, the user will be asked to confirm the new number also as his new member number. However, both these changes require an SMS validation using a temporary code in accordance with the registration procedure. If the user is a community owner and chooses to un-register his mobile phone number he must hand over the owner ship to someone else in that community. Otherwise the phone number can not be un- registered. Change Community Owner
- the system searches in the database for a matching entry. If the system finds a corresponding user he is added to the contact list.
- the user may add an own description to each contact in his contact list. This use case addresses how a user can add and modify a description of a contact .
- Actors User. Purpose: Logout from the web site member services.
- Logout is a permanent action; there is no "wastebasket " . The user cannot undo this action and is transferred to the welcome page.
- the user may change the PIN code (four digit PIN code) after successful login.
- the user must first enter the old PIN code, then the new PIN code and finally a confirmation of the new PIN code.
- Purpose Enables the user to quit the member services . Description: Quitting is a permanent action; there is no "wastebasket”. The user cannot undo this action.
- Purpose View list of members in a community. Description: The user can view name, email and mobile phone number of all members in a community. In addition to this information, the user can view all rejected invitations. The user, in the role of community owner, may choose to invite new members or remove members from the community.
- the telephony use cases are use cases related to functions and operations performed from a mobile or stationary phone.
- a guest or instant user has the possibility to join the service without having internet access.
- This use case addresses the case when a guest or instant user wants to register from a phone.
- a guest will get to this use case from the Phone login use case.
- An instant user will get to this use case from the Phone welcome instant user use case. Then follows a telephone dialog helping the person to register. Authentication is performed in the same way as in the web register use case.
- Phone Login Phone Login
- Actors User, instant user, guest.
- the system When the user is logged in, the system will perform a check to see whether there are any ongoing group talks . The system also checks if the user has a recorded spoken name or not. If the system determine that the user do not have a spoken name he should be asked to record one. The name is later used in services using spoken names. If the user has any invitations to communities that he hasn't joined or declined the system informs about this. The first time the community owner logs on via telephony services after having created a new community, he is asked to voice record the community name. This is also the case if the user has changed the name of the community on the web user interface.
- the user is also informed if he has been removed from any communities .
- the use case addresses the case where too many users are trying to access the telephony services at the same time thus consuming all system hardware and software resources .
- Purpose Main menu for an instant user. Description: The system welcomes the instant user to the system. If there is an ongoing instant group talk the instant user will be directed to this. If there are instant group messages the instant user is given the possibility to listen to them. The system will also give the instant user the possibility to register.
- Purpose Accepting community invitations via phone. Description: The system checks whether the user has new community invitations that are unanswered. If there exist such unanswered invitations the user is given the choice to join the communities or to decline the invitations. The name of the user that has sent the invitation and the group name are read out (spoken name) for each invitation. If the user chooses to join the community he is asked to specify whether he shall be visible or invisible to other users of the community
- the time delay for the alert is configurable by the system administrator.
- the user From the TUI, the user enters phone number/member number of other users and/or phone number of instant users to invite them to a group talk, or group message. If the user invites any person from the contact list with a two-digit code assigned the user can enter the code instead of the whole telephone number/member number.
- the system guides the user through a number of prompts and the user interacts with the system using DTMF commands. If the user invites a person with a forbidden number (i.e. the user states a number stored in the "Dialing Rules File") the user shall be notified and that invitation is cancelled.
- the user is given the possibility to review the instant group, i.e. the names of the members of the instant group are read out, using spoken name. If the group contains instant users or if no spoken name is assigned to a user the corresponding phone number will be read out instead.
- the instant group that is created shall be saved in the system and the user can initiate a group talk with the participants in the instant group without having to enter their numbers again.
- the instant group created is saved in the system and replaced the next time the user create a new instant group. A user can only have one instant group defined.
- Users shall be able to set up new static communities via the telephony user interface. This is done in the same way as setting up instant groups via the telephony user interface. If the user invites a person with a forbidden number (i.e. the user states a number stored in the "Dialing Rules File") the user shall be notified and that invitation is cancelled.
- a forbidden number i.e. the user states a number stored in the "Dialing Rules File
- the user will be asked to make a recording of the group name, and the group will be given a temporary name, typically a time stamp, that will be displayed on the web interface until the name is updated by the user, see above .
- a temporary name typically a time stamp
- an alert might be sent to the community owner.
- An alert might also be sent to the invited person. It is possible to configure these alerts independent of each other, e.g. in one implementation if the system both kinds of alerts might be used, but in another implementation, only the alert directed to the community owner might be used.
- Actors User. Purpose: Allow a user to use Group Talk.
- the user selects any community (or the instant group) to invite for Group Talk.
- the system will then initiate an outgoing call to all invited users (or instant users) leaving a short message and an email notification.
- the out dial message will be at least 25 sec long, consisting of a repeated message of an approximate length of 7-10 seconds repeated continuously until the called party hangs up or the time limit (25 sec) is reached.
- the out dial message might contain the name of the user initiating the Group Talk and the name of the community ("spoken name" usage) . What actually is included in the message is configurable. If no spoken name is recorded for the user the system is "silent" instead of reading the user's spoken name. For line busy calls a SMS will be sent .
- the Group Talk continues, and while waiting for the first person to join the call, for example advertisements can be played.
- a Group Talk is automatically recorded by the system during a limited time.
- the Group Talk recording may be accessed as a standard message later on.
- the recorded message is automatically deleted after a system set predefined time.
- the use case addresses the case where too many users are trying to access the Group Talk service at the same time thus consuming all system hardware and software Group Talk resources .
- the use case also addresses the case when the receiving part of the out dial is an answering machine. In this case the out dial shall be aborted. Note! An out dial notification is initiated according to a special sequence. This scheme is given in the UCR.
- Purpose Send a voice message to group members . Description: The user selects which group to address. He then records the message and ends by pressing the # sign. The message is recorded in the Group Message store. An SMS notification and an email notification (if the member has registered the email address) are automatically sent to all group members, urging them to call in and listen to the message. SMS is however not sent to members that still have unchecked messages in that that group. SMS is neither sent to users using a non-SMS capable phone. These users shall receive an email notification if an email address is registered. If no email address is registered the non-SMS capable phone user will not get any notification at all for Group Messages.
- Actors User, Instant user.
- the system will give the user the possibility to listen to the status of the message, i.e. what other users have listened to the message (using spoken name) . Note that this is an option. Further, the user has the choice of appending an own message to the previous one (note that this is not possible to instant group messages and instant group talk recordings) . If so, he records the Group Message. An SMS notification and an email notification (if the member has registered the email address) are automatically sent to all group members, urging them to call m and listen to the message.
- Each user shall start listening to the first recorded message that he hasn't listened to before. The user can skip messages and jump to the next recorded message.
- this is notified in the message log so that the initiator of the message can see on the web, or listen to on the TUI that the message has reached its intended audience.
- Actors User. Purpose: To invite additional members to a community from the TUI.
- the user can invite additional members to an existing community.
- the user must be owner of the community. If a user hasn't replied to an invitation alerts are sent according to above section regarding invitation of members.
- Actors User, Instant user.
- the user may join a Group Talk either directly after he has logged in using a phone of from the main menu.
- the instant user may join an instant user group talk from the Phone welcome instant user use case if there are an instant user group talks for that instant user.
- the system will ask which one he'd like to join, i.e. "For Footballers, press 1 ; for Dart buddies, press 2.” If the user/instant user is invited to one or more instant group talk sessions the system will read the name of the user that set up the current instant group.
- Purpose Get helpful information and tips. Description: It shall be possible to have support and guidance read in the phone by entering a certain phone key from most phone menus .
- Administrative use cases are functions performed by the administrator actor in order to maintain and modify the Mobile Community system.
- Purpose To update the file containing forbidden email addresses . Description: This use case describes how to update the file that contains email addresses that are forbidden to send messages to. The administrator can specify specific addresses, domain or sub domain names.
- This use case describes how to update the file that contains telephone numbers that are forbidden to dial. Such numbers are for example international numbers, premium rate numbers, emergency numbers etc.
- the administrator can specify numbers as well as number series using wildcards: E.g. 112; 90 000; 071*; 00*.
- the search may be performed using some basic search criteria as for example name, email, member number, mobile phone number, registration date and reason for blocking. It is possible to sort the output alphabetically using system-predefined columns.
- Actors Administrator. Purpose: Delete an existing user.
- This use case describes how an existing user may be deleted from the system.
- a user that is deleted is a community owner the community shall be terminated and the other users in the community shall be notified via e-mail.
- Purpose Change the properties and settings of a user account . Description: This use case describes how user details may be modified within the system.
- Any user can be blocked from accessing the member services. Once a user with a certain phone number is blocked, he will need to apply to the administrator by email to be able to register a new membership using the same phone number.
- Reasons for blocking can be:
- Administrators may set and change system parameters. Among those parameters are "Max simultaneous users in Group Talk", "How long time a recorded messages will be saved” .
- the administrator can see key data concerning the usage pattern of the system services, e.g. how many groups different persons initiate, group sizes, number of SMS sent compared to traffic generated etc.
- the system logs all logins at the TUI and WEB. For TUI accesses it is possible to see the length of each session as well as initiated SM and out dials during a session. For WEB the length of each session (until logout) is logged- if the user leave the site without doing a proper log-out it is possible to distinguish that session from other sessions.
- Actors Administrator. Purpose: Billing of operators. Description: Total voice traffic as well as total SMS traffic during a specified period is presented per operator. The administrator is further allowed to access and upload the traffic log file from the system.
- the traffic log file contains MSISDN/member number and start/stop/duration for each call.
- Purpose Specifying rights to other administrators. Description: The "master" administrator can specify what rights the other administrators of the system will have.
- Purpose To exit the administrative services. Description: The actor activates logout function or an automatic logout by a time-out. After logout the actor is redirected to the start page of the administrative web, the Admin welcome.
- the search may be performed using some basic search criteria as for example name, email, member number, mobile phone number, and registration date. It is possible to sort the output alphabetically using system- predefined columns. Delete Administrator
- This use case describes how an administrator may add a new community to the system for an arbitrary user.
- the search may be performed using some basic search criteria as for example name, symbol, and registration date. It is possible to sort the output alphabetically using system-predefined columns.
- Actors Administrator. Purpose: Delete an existing community.
- Actors Administrator. Purpose: Change the properties and settings of a community.
- An administrator can block any community. Once a community is blocked, the community owner will need to apply to the administrator by email to be able to reopen the community.
- the administrator can send email or voice message to all users or to a selected part thereof.
- a function monitors the hardware and software and reports errors to a fault management application.
- the system supports the use of spoken name for all users.
- the spoken name is recorded from the TUI at the first login to the system using the TUI .
- Detect answering machine
- the system is able to detect an answering machine when performing out dials.
- the system accepts users without SMS capable phone. For members that are users of the system using such a phone SM notification is not available as an option. When logging in to the system from such a phone A-number detection should not be used, i.e. the user have to state the member number and the access code . Automatic configuration of notifications
- the system shall be able to configure on a per user basis what notification method that should be used when a Group Talk is initiated.
- the notification schema per user should be set to a default value and can be controlled by the application (i.e. can differ per country) .
- the configuration is determined by what user data are given when registering, and by the country setting.
- the system supports participation of non-registered users in Group Talks .
- the system remembers numbers of instant users that has been invited to an instant group so that they can be given a separate dialogue when entering the system. This feature allows users to invite persons that have never heard about the MC system to join an instant group talk. Out dial notification is performed in the same way as for a regular user, the instant user will get another notification message though.
- the system supports LDAP for access to external directory information. This can be used to synchronize data with other directories and to import data from another user directory via LDAP. It is also possible to export data to another user directory.
- An external system is allowed to query the MC system for certain information via LDAP. In the same way - the MC system is able to query an LDAP directory for user information. The queries are done "online" .
- the system delivers reports on WEB usage. It is possible to detect individual users so that the number of unique users can be determined, not only the total number of hits.
- SMS-C Interface a) The system supports an interface to external SMS-Cs in a modular way so that adaptation can be made to interface new SMS-Cs without having to redesign the service. At least the following interfaces are supported
- the system routes the call to the correct SMS-C by identify which operator that is assigned to the current user (the operator is stored in the user's record) . Hence, several protocols are supported in parallel in one installation.
- the information of operator is determined by the system by analyzing the phone number entered at registration. The system is able to analyze the six first digits in the telephone number. At least 16 operators are able to be determined.
- This feature allows the system to use multiple SMS-Cs for notification
- the system allows out dial to different number series specified in a "Dialing rules" file. If the user with a forbidden out dial number has SM capabilities a SM should be sent to notify that user. The group talk owner shall be notified if all invited users can not be notified.
- the system allows for not sending email to certain addresses or domain/subdomain series which are specified in a "Email rules" file.
- Secure access for system administrators a) The system supports a secure connection for remote login by the administrator. The system requires preferably a certificate from the administrator's terminal. b) In order to keep track of possible unauthorized access to the system administrator account, all logins should be logged with time and IP address of the person logging in as system administrator. Alarm handling and monitoring
- the system supports alarm handling via SNMP to a SNMP manager (not part of the system) . Protection against misuse
- All communication systems can be subject to spam and misuse by users or guests.
- the system supports a function to limit the amount of out dials that are initiated by a certain user (i.e. through set up of group talks) and block users that exceed such value.
- the system supports an alarm function that will be triggered if a user exceeds a certain number of initiated out dials during a 24 hour period.
- the parameters is administered through the system administration interface (web) .
- the system supports a function to limit the amount of SM that are initiated by a certain user (i.e. through leaving group messages and by inviting new users) and block users that exceed such value.
- the system supports an alarm function that will be triggered if a user exceeds a certain number of initiated SM during a 24 -hour period.
- the parameters are administered through the system administration interface (web) .
- Safety aspects a) The system preferably uses a PIN code for authentication on the WEB interface and on the TUI interface . b) The system keeps a log of all accounts temporary blocked due to failed logon, and shall send an alarm upon high volumes of temporary blocked accounts . The system shall also send an alarm if an account is blocked more than 20 times during a period of 1 week. c) When logging out from the system, the webpages should preferably not be allowed to be cached in the browser d) UserlD and password shall preferably not be allowed to be handled as part of an URL. e) All entry fields on the website must have "Boundary checks" to ensure that the indata is of desired type. This checking should be done in the browser.
- Boundary checks must be done on entries between the webserver and the application server in order to prevent unwanted database accesses.
- the password is preferably encrypted in the browser using MD5 or SHA-1.0 before it is sent from the browser to the system. Max Group Size per User Basis.
- the system is prepared for future assignment of a maximum size of community on a user basis.
- Dynamic text usage It is possible to change web texts without service interruption.
- the content of the WEB pages is stored so that the text in the pages can be updated separated from the Java Server Pages (jsp) .
- Access to the text is an attribute in the administrator's access rights, i.e. it is possible to restrict access to changing the texts to certain administrators.
- jsp Java Server Pages
- Access to the text is an attribute in the administrator's access rights, i.e. it is possible to restrict access to changing the texts to certain administrators.
- b) It is possible to change text used in SMs without service interruption.
- c) It is possible to change text used in e-mails without service interruption. Browser compatibility
- the system supports at least America Online' s Netscape Navigator 4.05 and later versions and MS Explorer 4.01 and later versions.
- the scale the system the system is designed to allow configurations with multiple messages stores distributed on several physical servers, and user registers (DB2) distributed on several physical servers.
- Speech Recognition and Text to Speech a) The system is prepared for supporting speech recognition. Preferably, it shall be possible for the user to assign a spoken name for the persons that the user has put in the contact list. b) The system is prepared for Text to Speech translation. It is preferably be possible to e.g. read incoming emails in the TUI .
- the CT-servers shall reject this call.
- Auto-maintenance of log-files, user register and message store a) The database should preferably be cleaned regularly to ensure that all obsolete data is removed. b) Saved data on system usage (e.g. traffic logs etc.) should preferably be automatically archived after e.g. three months storage [system parameter] (and thus removed from the system) . c) It is possible to automatically remove users that have been inactive for more than x months (x is a system parameter - default value 12 months) .
- the system generates SNMP traps if there is any degradation in the capacity of the telephony interface.
- the CT resources (SW processes and HW (Line cards, ATM cards, Conference cards and servers)) should be possible to poll for status information.
- the system monitors activity on the line cards to ensure that they are working properly. If no activity has been detected during a certain time (system parameter) the system generates an alarm. Capacity - typical numbers without restricting the scope of the invention: a.
- the system is capable of meeting a subscriber load of 2 000 000 subscribers.
- the system supports 1000 simultaneous users on the web.
- the system supports 2000 simultaneous users on the TUI .
- the system supports full load on 120 ISDN channels and one DCB960 conference board in one NT server with the following configuration:
- the database isdesigned in a way so that it is possible to update the attributes connected to each user record (i.e. it is be possible to add information such as address and other user-unique data to each user record) .
- the system uses an acoustic profile. This means that different signals will be used to inform the user about different events. The following different sounds may be used:
- Latency As a measurement for the quality of service the system is designed in such a way that the user never need to wait more than 1 second after he has initiate a comment until the system answers back.
- the system is equipped with a time-out prompt that is played in case the 1 second threshold is exceeded during moments of extreme load "The system is retrieving data, please wait” or equivalent.
- GSM uses inband signalling to send DTFM signals. This makes the speech channel sound corrupted during about one second after a key is pressed.
- Audio codec use The system is capable of being configured to use different audio codecs (supported by the dialogic boards) . It shall be possible to use different codecs for recording of group talk and group message (which implies that the system is able to switch audio codec during a call.
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU58612/00A AU5861200A (en) | 1999-06-21 | 2000-06-15 | A method and an arrangement relating to groups of communicating users |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SE9902347-5 | 1999-06-21 | ||
SE9902347A SE9902347L (en) | 1999-06-21 | 1999-06-21 | Mobile community |
SE0001387-0 | 2000-04-13 | ||
SE0001387A SE0001387D0 (en) | 1999-06-21 | 2000-04-13 | A method and an arrangement relating to groups of communicating users |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2000079826A1 true WO2000079826A1 (en) | 2000-12-28 |
WO2000079826A8 WO2000079826A8 (en) | 2001-05-03 |
Family
ID=26655074
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE2000/001255 WO2000079826A1 (en) | 1999-06-21 | 2000-06-15 | A method and an arrangement relating to groups of communicating users |
Country Status (3)
Country | Link |
---|---|
AU (1) | AU5861200A (en) |
SE (1) | SE0001387D0 (en) |
WO (1) | WO2000079826A1 (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002017653A3 (en) * | 2000-08-22 | 2002-06-13 | Ericsson Telefon Ab L M | Mobile radio communication system and method for broadcasting messages to registered groups |
EP1225754A2 (en) * | 2001-01-22 | 2002-07-24 | Sonera Oyj | Voice message system |
WO2002085053A1 (en) * | 2001-04-10 | 2002-10-24 | Etheraction Ab | A system for communicating messages between clients in a radio network |
WO2003039181A1 (en) | 2001-10-30 | 2003-05-08 | Lang Alexander C | Method and apparatus for providing extended call setup and control features using a short message service |
FR2834605A1 (en) * | 2002-01-08 | 2003-07-11 | Freever | Discussion forum mobile telephone message exchange having server subject interest speech box creation phase and user speech message exchange. |
WO2003069946A1 (en) * | 2002-02-14 | 2003-08-21 | Qualcomm Incorporated | A server for joining a user to a group call in a group communication network |
WO2004014089A1 (en) * | 2002-08-01 | 2004-02-12 | Starent Networks Corporation | Providing advanced communications features |
WO2004089012A2 (en) * | 2003-04-03 | 2004-10-14 | Intellprop Limited | Apparatus and method for initiation of conference calls and distribution of text messages in a mobile telephone network |
WO2004109423A2 (en) * | 2003-06-09 | 2004-12-16 | Aasiaonwheels Network Limited | Tele trackers |
WO2006016003A1 (en) * | 2004-08-12 | 2006-02-16 | Nokia Corporation | Transmitting data to a group of receiving devices |
US7466823B2 (en) | 2000-03-03 | 2008-12-16 | Steve Vestergaard | Digital media distribution method and system |
DE102007032616A1 (en) * | 2007-07-11 | 2009-01-15 | Kliqme Gbr (Vertretungsberechtigte Gesellschafter: Jochen Schmidt | Mobile radio communication providing method for inviting group members to meeting place at particular time, involves transferring message sent to distribution lists to communication device of all group members listed in lists over device |
US7529712B2 (en) | 2002-07-16 | 2009-05-05 | Yangaroo Inc. | Content distribution system and method |
EP2526662A1 (en) * | 2010-01-19 | 2012-11-28 | Ringcentral, Inc. | Provisioning interfaces for accessing virtual private branch exchange services through a mobile device |
JP2015191569A (en) * | 2014-03-28 | 2015-11-02 | Kddi株式会社 | Group creation system, server, terminal, and program |
US9350845B2 (en) | 2009-12-01 | 2016-05-24 | Ringcentral, Inc. | Universal call management platform |
US9699637B1 (en) | 2004-12-16 | 2017-07-04 | Groupchatter, Llc | Method and apparatus for efficient and deterministic group alerting |
JP2017138990A (en) * | 2017-02-07 | 2017-08-10 | Kddi株式会社 | Group creation system, management server, and group creation program |
CN112783625A (en) * | 2021-01-18 | 2021-05-11 | 北京思特奇信息技术股份有限公司 | Emergency multi-task short message processing group sending system and method |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4761807A (en) * | 1982-09-29 | 1988-08-02 | Vmx, Inc. | Electronic audio communications system with voice authentication features |
GB2225194A (en) * | 1988-11-15 | 1990-05-23 | Mitel Corp | Group emergency call telephone system |
WO1996002996A1 (en) * | 1994-07-18 | 1996-02-01 | Anderson Howard M | Telephone number storage device |
EP0739115A2 (en) * | 1995-04-20 | 1996-10-23 | AT&T IPM Corp. | Electronic messaging in a wide area network |
WO1996034341A1 (en) * | 1995-04-28 | 1996-10-31 | Charles Ii Bobo | Message storage and delivery system |
US5631904A (en) * | 1994-11-21 | 1997-05-20 | Lucent Technologies Inc. | Method for automatically establishing a conference call |
EP0845894A2 (en) * | 1996-11-05 | 1998-06-03 | Boston Technology Inc. | A system for accessing multimedia mailboxes and messages over the internet and via telephone |
US5915008A (en) * | 1995-10-04 | 1999-06-22 | Bell Atlantic Network Services, Inc. | System and method for changing advanced intelligent network services from customer premises equipment |
WO1999067922A1 (en) * | 1998-06-25 | 1999-12-29 | Mci Worldcom, Inc. | Method and system for multicasting call notifications |
WO2000025536A1 (en) * | 1998-10-28 | 2000-05-04 | Ericsson, Inc. | Method and system for the delivery of telecommunications data from an originating subscriber to multiple subscribers in a telecommunications network |
WO2000030375A2 (en) * | 1998-11-16 | 2000-05-25 | Ericsson Inc. | User group indication and status change in radiocommunication systems |
-
2000
- 2000-04-13 SE SE0001387A patent/SE0001387D0/en unknown
- 2000-06-15 WO PCT/SE2000/001255 patent/WO2000079826A1/en active Application Filing
- 2000-06-15 AU AU58612/00A patent/AU5861200A/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4761807A (en) * | 1982-09-29 | 1988-08-02 | Vmx, Inc. | Electronic audio communications system with voice authentication features |
GB2225194A (en) * | 1988-11-15 | 1990-05-23 | Mitel Corp | Group emergency call telephone system |
WO1996002996A1 (en) * | 1994-07-18 | 1996-02-01 | Anderson Howard M | Telephone number storage device |
US5631904A (en) * | 1994-11-21 | 1997-05-20 | Lucent Technologies Inc. | Method for automatically establishing a conference call |
EP0739115A2 (en) * | 1995-04-20 | 1996-10-23 | AT&T IPM Corp. | Electronic messaging in a wide area network |
WO1996034341A1 (en) * | 1995-04-28 | 1996-10-31 | Charles Ii Bobo | Message storage and delivery system |
US5915008A (en) * | 1995-10-04 | 1999-06-22 | Bell Atlantic Network Services, Inc. | System and method for changing advanced intelligent network services from customer premises equipment |
EP0845894A2 (en) * | 1996-11-05 | 1998-06-03 | Boston Technology Inc. | A system for accessing multimedia mailboxes and messages over the internet and via telephone |
WO1999067922A1 (en) * | 1998-06-25 | 1999-12-29 | Mci Worldcom, Inc. | Method and system for multicasting call notifications |
WO2000025536A1 (en) * | 1998-10-28 | 2000-05-04 | Ericsson, Inc. | Method and system for the delivery of telecommunications data from an originating subscriber to multiple subscribers in a telecommunications network |
WO2000030375A2 (en) * | 1998-11-16 | 2000-05-25 | Ericsson Inc. | User group indication and status change in radiocommunication systems |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7466823B2 (en) | 2000-03-03 | 2008-12-16 | Steve Vestergaard | Digital media distribution method and system |
WO2002017653A3 (en) * | 2000-08-22 | 2002-06-13 | Ericsson Telefon Ab L M | Mobile radio communication system and method for broadcasting messages to registered groups |
US6917806B2 (en) | 2000-08-22 | 2005-07-12 | Telefonaktiebolaget Lm Ericsson | Mobile radio communication system and method for controlling such system |
EP1225754A2 (en) * | 2001-01-22 | 2002-07-24 | Sonera Oyj | Voice message system |
EP1225754A3 (en) * | 2001-01-22 | 2003-07-23 | Sonera Oyj | Voice message system |
WO2002085053A1 (en) * | 2001-04-10 | 2002-10-24 | Etheraction Ab | A system for communicating messages between clients in a radio network |
WO2003039181A1 (en) | 2001-10-30 | 2003-05-08 | Lang Alexander C | Method and apparatus for providing extended call setup and control features using a short message service |
FR2834605A1 (en) * | 2002-01-08 | 2003-07-11 | Freever | Discussion forum mobile telephone message exchange having server subject interest speech box creation phase and user speech message exchange. |
WO2003069946A1 (en) * | 2002-02-14 | 2003-08-21 | Qualcomm Incorporated | A server for joining a user to a group call in a group communication network |
US7529712B2 (en) | 2002-07-16 | 2009-05-05 | Yangaroo Inc. | Content distribution system and method |
US8626138B2 (en) | 2002-08-01 | 2014-01-07 | Cisco Technology, Inc. | Providing advanced communications features |
WO2004014089A1 (en) * | 2002-08-01 | 2004-02-12 | Starent Networks Corporation | Providing advanced communications features |
US7372826B2 (en) | 2002-08-01 | 2008-05-13 | Starent Networks, Corp. | Providing advanced communications features |
AU2004225234B2 (en) * | 2003-04-03 | 2008-12-18 | Intellprop Limited | Apparatus and method for initiation of conference calls and distribution of text messages in a mobile telephone network |
WO2004089012A3 (en) * | 2003-04-03 | 2005-01-20 | Intellprop Ltd | Apparatus and method for initiation of conference calls and distribution of text messages in a mobile telephone network |
WO2004089012A2 (en) * | 2003-04-03 | 2004-10-14 | Intellprop Limited | Apparatus and method for initiation of conference calls and distribution of text messages in a mobile telephone network |
WO2004109423A2 (en) * | 2003-06-09 | 2004-12-16 | Aasiaonwheels Network Limited | Tele trackers |
WO2004109423A3 (en) * | 2003-06-09 | 2006-06-08 | Aasiaonwheels Network Ltd | Tele trackers |
WO2006016003A1 (en) * | 2004-08-12 | 2006-02-16 | Nokia Corporation | Transmitting data to a group of receiving devices |
US7751358B2 (en) | 2004-08-12 | 2010-07-06 | Nokia Corporation | Transmitting data to a group of receiving devices |
US10206088B2 (en) | 2004-12-16 | 2019-02-12 | Groupchatter, Llc | Method and apparatus for efficient and deterministic group alerting |
US10070298B2 (en) | 2004-12-16 | 2018-09-04 | Groupchatter, Llc | Method and apparatus for efficient and deterministic group alerting |
US9699637B1 (en) | 2004-12-16 | 2017-07-04 | Groupchatter, Llc | Method and apparatus for efficient and deterministic group alerting |
DE102007032616A1 (en) * | 2007-07-11 | 2009-01-15 | Kliqme Gbr (Vertretungsberechtigte Gesellschafter: Jochen Schmidt | Mobile radio communication providing method for inviting group members to meeting place at particular time, involves transferring message sent to distribution lists to communication device of all group members listed in lists over device |
US9350845B2 (en) | 2009-12-01 | 2016-05-24 | Ringcentral, Inc. | Universal call management platform |
US9602986B2 (en) | 2009-12-01 | 2017-03-21 | Ringcentral, Inc. | Universal call management platform |
US8971957B2 (en) | 2010-01-19 | 2015-03-03 | Ringcentral, Inc. | Provisioning interfaces for accessing virtual private branch exchange services through a mobile device |
US8838169B2 (en) | 2010-01-19 | 2014-09-16 | Ringcentral, Inc. | Provisioning interfaces for accessing virtual private branch exchange services through a mobile device |
US9749457B2 (en) | 2010-01-19 | 2017-08-29 | Ringcentral, Inc. | Provisioning interfaces for accessing virtual private branch exchange services through a mobile device |
EP2526662A4 (en) * | 2010-01-19 | 2013-08-21 | Ringcentral Inc | Provisioning interfaces for accessing virtual private branch exchange services through a mobile device |
EP2526662A1 (en) * | 2010-01-19 | 2012-11-28 | Ringcentral, Inc. | Provisioning interfaces for accessing virtual private branch exchange services through a mobile device |
JP2015191569A (en) * | 2014-03-28 | 2015-11-02 | Kddi株式会社 | Group creation system, server, terminal, and program |
JP2017138990A (en) * | 2017-02-07 | 2017-08-10 | Kddi株式会社 | Group creation system, management server, and group creation program |
CN112783625A (en) * | 2021-01-18 | 2021-05-11 | 北京思特奇信息技术股份有限公司 | Emergency multi-task short message processing group sending system and method |
CN112783625B (en) * | 2021-01-18 | 2023-10-24 | 北京思特奇信息技术股份有限公司 | Emergency multitasking short message group sending system and method |
Also Published As
Publication number | Publication date |
---|---|
AU5861200A (en) | 2001-01-09 |
SE0001387D0 (en) | 2000-04-13 |
WO2000079826A8 (en) | 2001-05-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9942190B2 (en) | Method and apparatus for group messaging | |
US6418214B1 (en) | Network-based conference system | |
WO2000079826A1 (en) | A method and an arrangement relating to groups of communicating users | |
US9432494B1 (en) | Methods and systems for creating a dynamic call log and contact records | |
EP1122926B1 (en) | Messaging between terminals in different communities | |
US6999478B2 (en) | System controlling use of a communication channel | |
US7970388B2 (en) | Methods and apparatus for providing multiple communications services with unified parental notification and/or control features | |
US7925246B2 (en) | Radio/telephony interoperability system | |
US6564261B1 (en) | Distributed system to intelligently establish sessions between anonymous users over various networks | |
US7411939B1 (en) | Methods and apparatus for providing communications services between connectionless and connection-oriented networks | |
US8798251B2 (en) | Methods and systems for computer enhanced conference calling | |
WO2002075605A9 (en) | Xml based transaction detail records | |
KR20010006455A (en) | A system, method and article of manufacture for switched telephony communication | |
US7400713B2 (en) | IP handset-based voice mail notification | |
JP2001517031A (en) | Information retrieval system | |
Cisco | Before You Begin | |
Cisco | Before You Begin | |
Cisco | Running Quick Config | |
Cisco | Software Applications Feature Summary | |
Cisco | Understanding the uOne Solution Architecture | |
AU2002252424A1 (en) | XML based transaction detail records |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR 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 SK SL TJ TM TR TT TZ UA UG US 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 BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
AK | Designated states |
Kind code of ref document: C1 Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR 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 SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: C1 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 BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
CFP | Corrected version of a pamphlet front page |
Free format text: PUBLISHED FIGURE REPLACED BY CORRECT |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |