US8755773B2 - System and method of providing notifications for acknowledgement of missed calls - Google Patents

System and method of providing notifications for acknowledgement of missed calls Download PDF

Info

Publication number
US8755773B2
US8755773B2 US13/201,582 US200913201582A US8755773B2 US 8755773 B2 US8755773 B2 US 8755773B2 US 200913201582 A US200913201582 A US 200913201582A US 8755773 B2 US8755773 B2 US 8755773B2
Authority
US
United States
Prior art keywords
notification
called party
party
calling party
call
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US13/201,582
Other versions
US20120028618A1 (en
Inventor
Mudit Goel
Satish Kanugovi
Sarang Gadgil
Nagendra Bykampadi
Shivani Arora
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alcatel Lucent SAS
Original Assignee
Alcatel Lucent SAS
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 Alcatel Lucent SAS filed Critical Alcatel Lucent SAS
Assigned to ALCATEL LUCENT reassignment ALCATEL LUCENT ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ARORA, SHIVANI, BYKAMPADI, NAGENDRA, GADGIL, SARANG, GOEL, MUDIT, KANUGOVI, SATISH
Publication of US20120028618A1 publication Critical patent/US20120028618A1/en
Assigned to CREDIT SUISSE AG reassignment CREDIT SUISSE AG SECURITY AGREEMENT Assignors: ALCATEL LUCENT
Application granted granted Critical
Publication of US8755773B2 publication Critical patent/US8755773B2/en
Assigned to ALCATEL LUCENT reassignment ALCATEL LUCENT RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: CREDIT SUISSE AG
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H04W36/385—Reselection control by fixed network equipment of the core network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel

Definitions

  • the notification may be in the form of a Short Service Message (SMS), Multimedia Messaging Service (MMS), Wireless Application Protocol (WAP) message or any other suitable means of messaging.
  • SMS Short Service Message
  • MMS Multimedia Messaging Service
  • WAP Wireless Application Protocol
  • the notification may be sent via an application server, with the address of the calling party as the final destination address or directly to the calling party.
  • the application server confirms the subscription of the calling party. On confirmation the notification is sent to the calling party by the application server.
  • the sending of the notification provisioned in the wireless device can be either on confirmation of the called party or automatically once the called party views the missed call record.
  • FIG. 6 is a flow chart depicting a method of sending a notification for acknowledgment of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein.
  • a calling party 101 makes ( 601 ) a call to a called party 104 .
  • the call may result in a missed call as the called party 104 may be busy to address the call or may be out of coverage area of the network.
  • the missed call gets recorded in the list of missed calls on the wireless device of the called party 104 .
  • the wireless device of the called party 104 checks ( 603 ) if the called party 104 has viewed the record of the missed call from the calling party 101 .
  • Both the calling party 101 and the called party 104 subscribe for the notification service.
  • the application 201 on the device of the called party 104 is activated.
  • the application 105 generates ( 1102 ) a notification.
  • the notification is sent ( 1103 ) to the application server 103 , without any confirmation from the called party 104 .
  • Application server on receiving ( 1104 ) the notification confirms the subscription of the calling party 101 for the notification service.
  • the application server 103 forwards ( 1105 ) the notification to the calling party 104 .
  • the notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on.
  • the notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on.
  • the notification may also be defined by the called party 104 .
  • the notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging.
  • the application server 103 checks ( 1206 ) whether the calling party 101 is a subscriber of the missed call notification service. If the calling party 101 is a subscriber of the notification service the application server 103 forwards ( 1207 ) the notification to the calling party 101 via the communication network 102 .
  • Application server 201 is provided with a number that is stored in the wireless device of both calling party 101 and called party 103 . This number can be used for the subscription charges.
  • a missed call may be a call which is not answered by the called party 104 , a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area.
  • the wireless device 104 of the called party 104 When the called party 104 views the record of missed call, the wireless device 104 of the called party 104 generates a notification, which is sent to the network 102 .
  • the wireless device can send the notification to the network 102 on receiving a confirmation from the called party 104 .
  • the wireless device can also send the notification to the network 102 automatically i.e. without any confirmation from the called party 104 .
  • a missed call may be defined as a call which is not answered by the called party 104 , a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area.
  • the missed call gets recorded in the list of missed calls in the wireless communication device of the called party 104 .
  • Both the calling party 101 and the called party 104 subscribe for the notification service.
  • the application 201 on the wireless device of the called party 104 is activated.
  • the application 201 generates ( 1702 ) a notification.
  • the application 201 sends ( 1703 ) the notification to the calling party 101 .
  • the application 201 generates ( 1804 ) a notification on the wireless device of the called party 104 .
  • the application 201 asks ( 1805 ) for confirmation from the called party 104 using a pop up.
  • the application 201 sends ( 1806 ) the notification to the calling party 101 .
  • the notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on.
  • the notification may also be defined by the called party 104 .
  • the notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging.
  • the various actions in method 1800 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 18 may be omitted.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

A system and method for notifying the calling party of acknowledgment of the missed calls by the called party is disclosed. The called party and the calling party can subscribe for the notification service to enable charging for the service. When the calling party initiates a call to the called party it may result in a missed call as the called party may be out of coverage area or busy. When the called party views the record of the missed call a notification is generated on the wireless device by the application on the wireless device of the called party. The notification is then sent to the calling party. The acknowledgement notification may be sent directly to the calling party or via an application server.

Description

BACKGROUND
1. Technical Field
The embodiments herein relate to wireless communication systems and, more particularly, to a system and method of providing notifications for acknowledgement of missed calls in wireless communication systems.
2. Description of the Related Art
Many solutions exist to provide the called party of wireless communication devices with alerts of missed call. A missed call may be a call which is not answered, a call that returns a busy tone, a call that is rejected (either by the called party intentionally or by an application in the called party mobile device) or the case wherein the wireless device is switched off or is out of the coverage area. Existing solutions notify the called party of the missed calls in the form of an SMS when the called party is in the coverage area or returns into the coverage area or mobile device is switched on. Or an alert signal in the form of a reminder may be sent to the called party. However the calling party does not receive a confirmation from the called party if the call has been received. Also there is no assurance as to whether the required action will be taken by the called party. This may leave the calling party in an ambiguous situation, whether the missed call has been viewed by the called party or not.
Wireless communication service providers provide the subscribers with facilities to register for the missed call alerts. When there is a missed call either because the called party is out of coverage area or is unable to attend a call an SMS is sent to the called party once he reaches an area with coverage, disclosing the details of the time of the call, id of the calling party and so on. But there is a time lag between the time when the call is missed and the time when the called party is alerted of the same. Also there are facilities to leave a voice message on the called party's phone. In other known solutions, call forwarding facilities also exist. Where the call is forwarded to a pre-stored number, in case the called party is not able to address the call, where the number is pre-stored by the called party. In addition there are systems for notifying and reminding the called party about the missed calls in a manner specified by the called party.
Another method employs a computer stored program for managing the missed calls. A server keeps track of the information of missed calls, time of call and other details. Later the called party is intimated of the missed calls. The process is cumbersome and also involves time delay.
SUMMARY
In view of the foregoing, an embodiment herein provides a system and method of providing notification of the called party acknowledging the missed call to the calling party. The method comprising of sending a notification to the calling party, when called party views missed call from calling party. Both the called party and the calling party are subscribed to the notification service. An application present on communication device of the called party prompts the called party to send a notification. The notification may be sent either on confirmation from the called party or automatically. The application can also be configured to not send notifications for missed call acknowledgements. The application on the called party device can also provide user defined notification text. The notification is sent to the calling party Further the notification may be the form of a SMS, a MMS or a WAP message, which may be pre defined by the application.
Embodiments further disclose a method of providing notification of acknowledgement of missed calls, wherein, the notification goes via application server that verifies if calling party is subscribed to the notification service. The communication device comprising of a prompting means for the device to prompt user of the communication device to send a notification to the calling party; and a sending means for the communication device to send the notification to calling party.
These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
FIG. 1 is a block diagram illustrating a system for notification for acknowledgement of missed calls, in accordance with the embodiments herein;
FIG. 2 is a block diagram illustrating a system for notification for acknowledgement of missed calls, in accordance with the embodiments herein;
FIG. 3 is a block diagram illustrating a system for notification for acknowledgement of missed calls, in accordance with the embodiments herein;
FIG. 4 is a block diagram illustrating a system for notification for acknowledgement of missed calls, in accordance with the embodiments herein;
FIG. 5 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein;
FIG. 6 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein;
FIG. 7 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein;
FIG. 8 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein;
FIG. 9 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, without any confirmation from the called party, in accordance with the embodiments herein;
FIG. 10 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, without the confirmation of the called party, in accordance with the embodiments herein;
FIG. 11 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, without any confirmation from the called party, in accordance with the embodiments herein; and
FIG. 12 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, without the confirmation of the called party, in accordance with the embodiments herein;
FIG. 13 is a block diagram illustrating a system for notification for acknowledgement of missed calls, in accordance with the embodiments herein;
FIG. 14 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein;
FIG. 15 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein;
FIG. 16 is a block diagram illustrating a system for notification for acknowledgement of missed calls, in accordance with the embodiments herein;
FIG. 17 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein; and
FIG. 18 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein.
 DETAILED DESCRIPTION OF EMBODIMENTS
The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
The embodiments herein achieve a system and a method of providing a notification for acknowledgement of a missed call to the calling party, when the called party views the missed call record. Referring now to the drawings, and more particularly to FIGS. 1 through 18, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
When the calling party initiates a call, the call may result in a missed call if the called party fails to pick up the call. A call may be a missed call if returns a busy tone, or the case wherein the wireless device is out of the coverage area or is switched off. Missed call notifications are used to remind the called party of a particular task such as giving a call back to the called party. Generally missed call alerts to the called party disclose details such as time of the call, identification number of the calling party and so on. Such notifications ensure the required action will be taken by the called party and the purpose of the call being served. When the called party views the record of missed call, a notification will be sent to the calling party. The notification may be in the form of a Short Service Message (SMS), Multimedia Messaging Service (MMS), Wireless Application Protocol (WAP) message or any other suitable means of messaging. The notification may be sent via an application server, with the address of the calling party as the final destination address or directly to the calling party. The application server confirms the subscription of the calling party. On confirmation the notification is sent to the calling party by the application server. The sending of the notification provisioned in the wireless device can be either on confirmation of the called party or automatically once the called party views the missed call record.
FIG. 1 is a block diagram illustrating a system to provide notification for acknowledgment of missed calls by the called party, in accordance with the embodiments herein. A calling party 101 initiates a call to a called party 103 through a network 102. The network 102 comprises of a single network, where the calling party 101 and the called party 104 belong to the same network. The network 102 also comprises of an application server 103. The call may be a missed call if the called party 104 fails to pick up the call. A missed call may be a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. When the called party 104 views the record of missed call, the wireless device 104 of the called party 104 generates a notification, which is sent to the application server 103. The wireless device can send the notification to the application server 103 on receiving a confirmation from the called party 104. The wireless device can also send the notification to the application server 103 automatically i.e. without any confirmation from the called party 104. The notification comprises of information like time the called party 104 viewing the missed call, the time the called party got the notification of the missed call, the address of the calling party 101 as the destination address and so on. The notification text may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The notification is sent to the application server 103 which checks to ensure the calling party 101 is a subscriber of the service. On confirming the subscription of the calling party 101, the application server 103 forwards the notification to the calling party 101, hereby notifying the calling party 101 of the missed call being viewed by the called party 104. For the purpose of charging for the subscription the application server number gets stored in the wireless device of the called party 104. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. Subscription of the service by the called party 104 indicates his acceptance to send missed call acknowledgements. Subscription of the service by the calling party indicates his willingness to be charged for the notification service, if the service provider wants this to be a paid service. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 2 is a block diagram illustrating a system to provide notification for acknowledgment of missed calls by the called party, in accordance with the embodiments herein. A calling party 101 initiates a call to a called party 103 through a network 102. The network 102 comprises of a single network, where the calling party 101 and the called party 104 belong to the same network. The network 102 also comprises of an application server 103. The call may be a missed call if the called party 104 fails to pick up the call. A missed call may be a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. When the called party 104 views the record of missed call, the application 201 on the wireless device is activated. The application 201 will generate a notification the text of which can be user defined. The application 201 can send the notification to the application server 103 on receiving a confirmation from the called party 104. The application 201 can provide option of sending/not sending the notification for the missed call acknowledgement by the called party. The application 201 can also be configured so that the called party 104 is not notified before sending the acknowledgement for the missed call. This is the case where the called party has provisioned the application to send notification unsolicited upon acknowledgment of the missed call. The application 201 can be configured not to send any notification to the calling party 101. The application 201 can also provide the called party with the option of defining the text that goes as part of the notification. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The notification is sent to the application server 103 which checks to ensure the calling party 101 is a subscriber of the service. On confirming the subscription of the calling party 101, the application server 103 forwards the notification to the calling party 101, hereby notifying the calling party 101 of the missed call being viewed by the called party 104. For the purpose of charging for the subscription the application server number gets stored in the wireless device the called party 104. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 3 is a block diagram illustrating a system to provide notification for acknowledgment of missed calls by the called party, in accordance with the embodiments herein. A calling party 101 initiates a call to a called party 104 through networks 301 and 302, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The network 301 also comprises of an application server 103. The call may be a missed call if the called party 104 fails to pick up the call. A missed call may be a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. When the called party 104 views the record of missed call, the wireless device 104 of the called party 104 generates a notification, which is sent to the application server 103 present in network 301 through network 302. The wireless device can send the notification to the application server 103 on receiving a confirmation from the called party 104. The wireless device can also send the notification to the application server 103 automatically i.e. without any confirmation from the called party 104. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The notification is sent to the application server 103 which checks to ensure the calling party 101 is a subscriber of the service. On confirming the subscription of the calling party 101, the application server 103 forwards the notification to the calling party 101, hereby notifying the calling party 101 of the missed call being viewed by the called party 104. For the purpose of charging for the subscription the application server number gets stored in the wireless device of the called party 104. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 4 is a block diagram illustrating a system to provide notification for acknowledgment of missed calls by the called party, in accordance with the embodiments herein. A calling party 101 initiates a call to a called party 104 through networks 301 and 302, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The network 301 also comprises of an application server 103. The call may be a missed call if the called party 104 fails to pick up the call. A missed call may be a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. When the called party 104 views the record of missed call, the application 201 on the wireless device is activated. The application 201 will generate a notification which can be user defined. The application 201 can send the notification to the application server 103 present in network 301 through network 302 on receiving a confirmation from the called party 104. The application 201 can also be configured so that the called party 104 is not notified before sending the acknowledgement for the missed call. This is the case where the called party has provisioned the application to send notification unsolicited upon acknowledgment of the missed call. The application 201 can be configured not to send any notification to the calling party 101. The application 201 can also provide the called party with the option of defining the text that goes as part of the notification. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The notification is sent to the application server 103 which checks to ensure the calling party 101 is a subscriber of the service. On confirming the subscription of the calling party 101, the application server 103 forwards the notification to the calling party 101, hereby notifying the calling party 101 of the missed call being viewed by the called party 104. For the purpose of charging for the subscription the application server number gets stored in the wireless device of the called party 104. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 5 illustrates a flow diagram for sending a notification of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. The calling party 101 initiates (501) a call to the called party 104. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. A call may be a missed call if the called party 104 fails to pick up the call. A missed call may be defined as a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. The missed call gets recorded in the list of missed calls in the wireless communication device of the called party 104. Both the calling party 101 and the called party 104 subscribe for the notification service. When the called party 104 views the record of missed call, the wireless device of the called party 104 generates (502) a notification. A pop up may appear on the wireless device of the called party 104. The pop up asks for a confirmation from the called party 104 for sending the notification. When the called party 104 confirms, the wireless device of the called party 104 sends (503) a notification to the application server 103. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The application server 103 checks (504) the subscription of the calling party 101 to confirm if the calling party 101 is a registered subscriber for the notification service. Further, if the calling party 101 is a registered subscriber for the notification service, the application server 103 forwards (505) the notification to the calling party 101. For the purpose of charging for the subscription number of the application server 103 is stored in the wireless device of the called party 104. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 6 is a flow chart depicting a method of sending a notification for acknowledgment of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. A calling party 101 makes (601) a call to a called party 104. The call may result in a missed call as the called party 104 may be busy to address the call or may be out of coverage area of the network. The missed call gets recorded in the list of missed calls on the wireless device of the called party 104. The wireless device of the called party 104 checks (603) if the called party 104 has viewed the record of the missed call from the calling party 101. Once the called party 104 views the record, the wireless device of the called party 104 generates (604) a notification on the wireless device of the called party 104. The wireless device of the called party 104 asks (605) for confirmation from the called party 104 using a pop up. On receiving a confirmation from the called party 104, the wireless device of the called party 104 sends (606) the notification to the application server 103. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The application server 103 checks (607) whether the calling party 101 is a subscriber of the missed call notification service. If the calling party 101 is a subscriber of the service the application server 103 forwards (608) the notification to the calling party 101. The application server 103 is provided with a number, which gets stored in the wireless device of both the called party 104 and calling party 101. This number can be used for the subscription charges. Subscription ensures the charges of the notification are borne by the calling party 101 who initiated the missed call. The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 may be omitted.
FIG. 7 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. The calling party 101 initiates (701) a call to the called party 104 through the communication network 102. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. A call may be a missed call if the called party 104 fails to pick up the call. A missed call may be defined as a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. The missed call gets recorded in the list of missed calls in the wireless communication device of the called party 104. Both the calling party 101 and the called party 104 subscribe for the notification service. When the called party 104 views the record of missed call, the application 201 on the wireless device of the called party 104 is activated. The application 201 generates (702) a notification. When the called party 104 confirms, the application 201 sends (703) the notification to the application server 103. The application server 103 checks (704) the subscription of the calling party 101 to confirm if the calling party 101 is a registered subscriber for the notification service. Further, if the calling party 101 is a registered subscriber for the notification service, the application server 103 forwards (705) the notification to the calling party 101. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. For the purpose of charging for the subscription number of the application server 103 is stored in the wireless device of the called party 104. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 8 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. A calling party 101 makes (801) a call to a called party 104. The call may result in a missed call as the called party 104 may be busy to address the call or may be out of coverage area of the network. The missed call gets recorded in the list of missed calls on the wireless device of the called party 104. The calling party 101 as well as the called party 104 install the application 201 on their wireless device. The application 201 checks (803) if the called party 104 has viewed the record of the missed call from the calling party 101. Once the called party 104 views the record, the application 201 generates (804) a notification on the wireless device of the called party 104. The application 201 asks (805) for confirmation from the called party 104 using a pop up. On receiving a confirmation from the called party 104, the application 201 sends (806) the notification to the application server 103. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The application server 103 checks (807) whether the calling party 101 is a subscriber of the missed call notification service. If the calling party 101 is a subscriber of the service the application server 103 forwards (808) the notification to the calling party 101 via the communication network 102. The application server 103 is provided with a number, which gets stored in the wireless device of both the called party 104 and calling party 101. This number can be used for the subscription charges. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service. The various actions in method 800 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 8 may be omitted.
FIG. 9 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, without any confirmation required from the called party, in accordance with the embodiments herein. A calling party 101 initiates (901) a call to a called party 103. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The call may result in a missed call as the calling party 101 may be busy or may be out of coverage area of the network. The missed call is recorded in the wireless device of the called party 104. Both the calling party 101 and the called party 104 subscribe for the notification service. When the called party 104 views the record of missed call the wireless device of the called party 104 generates (902) a notification. The notification is sent (903) to the application server 103, without any confirmation from the called party 104. Application server on receiving (904) the notification confirms the subscription of the calling party 101 for the notification service. Further if the calling party 104 is a registered subscriber for the notification service, the application server 103 forwards (905) the notification to the calling party 104. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The number of the application server 103 number is stored in the wireless device of both calling party 101 and called party 104. This number can be used for the subscription charges. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 10 is a flow diagram depicting a method of sending a notification for acknowledgement of missed call to the calling party, without the confirmation of the called party, in accordance with the embodiments herein. A Calling party 101 initiates (1001) a call to a called party 103. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The call may be a missed call as the calling party 101 may be busy or may be out of coverage area of the network. The missed call is recorded in the list of missed calls in the wireless device of the called party 104. The application server 103 checks (1002) if the call is a missed call. If the call is not a missed call the process terminates. The wireless device of the called party 104 checks (1003) if the called party 104 has viewed the record of the missed call by the called party 104. Once the called party 104 views the record, the wireless device of the called party 104 generates (1004) a notification. The notification is sent (1005) to the application server 103 without any confirmation required from the called party 104. The application server 103 checks (1006) whether the calling party 101 is a subscriber of the missed call notification service. If the calling party 101 is a subscriber of the notification service the application server 103 forwards (1007) the notification to the calling party 101 via the communication network 102. Application server 201 is provided with a number that is stored in the wireless device of both calling party 101 and called party 103. This number can be used for the subscription charges. Subscription ensures the charges of the notification are borne by the calling party 101 who initiated the missed call. The various actions in method 1000 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 10 may be omitted.
FIG. 11 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, without any confirmation required from the called party, in accordance with the embodiments herein. A calling party 101 initiates (1101) a call to a called party 103 through the network 102. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The call may result in a missed call as the calling party 101 may be busy or may be out of coverage area of the network. The missed call is recorded in the wireless device of the called party 104. Both the calling party 101 and the called party 104 subscribe for the notification service. When the called party 104 views the record of missed call, the application 201 on the device of the called party 104 is activated. The application 105 generates (1102) a notification. The notification is sent (1103) to the application server 103, without any confirmation from the called party 104. Application server on receiving (1104) the notification confirms the subscription of the calling party 101 for the notification service. Further if the calling party 104 is a registered subscriber for the notification service, the application server 103 forwards (1105) the notification to the calling party 104. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The number of the application server 103 number is stored in the wireless device of both calling party 101 and called party 104. This number can be used for the subscription charges. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service.
FIG. 12 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, without the confirmation of the called party, in accordance with the embodiments herein. A Calling party 101 initiates (1201) a call to a called party 103. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The call may be a missed call as the calling party 101 may be busy or may be out of coverage area of the network. The missed call is recorded in the list of missed calls in the wireless device of the called party 104. The application server 103 checks (1202) if the call is a missed call. If the call is not a missed call the process terminates. The calling party 101 as well as the called party 104 have an application 201 installed on their wireless device. The application 201 may be modified as per the requirements of the user of the wireless device. The application 201 checks (1203) if the called party 104 has viewed the record of the missed call by the called party 104. Once the called party 104 views the record, the application 201 generates (1204) a notification. The application sends (1205) the notification to the application server 103 without any confirmation required from the called party 104. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The application server 103 checks (1206) whether the calling party 101 is a subscriber of the missed call notification service. If the calling party 101 is a subscriber of the notification service the application server 103 forwards (1207) the notification to the calling party 101 via the communication network 102. Application server 201 is provided with a number that is stored in the wireless device of both calling party 101 and called party 103. This number can be used for the subscription charges. As per the subscription model, the charges of the notification are borne by the calling party 101 who initiated the missed call. However, it is also possible for the called party 104 to accept the charges for the notification service. The various actions in method 1200 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 12 may be omitted.
FIG. 13 is a block diagram illustrating a system to provide notification for acknowledgment of missed calls by the called party, in accordance with the embodiments herein. A calling party 101 initiates a call to a called party 103 through a network 102. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The call may be a missed call if the called party 104 fails to pick up the call. A missed call may be a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. When the called party 104 views the record of missed call, the wireless device 104 of the called party 104 generates a notification, which is sent to the network 102. The wireless device can send the notification to the network 102 on receiving a confirmation from the called party 104. The wireless device can also send the notification to the network 102 automatically i.e. without any confirmation from the called party 104. The notification comprises of information like time the called party 104 viewing the missed call, the time the called party got the notification of the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The network 102 forwards the notification to the calling party 101, hereby notifying the calling party 101 of the missed call being viewed by the called party 104.
FIG. 14 illustrates a flow diagram for sending a notification of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. The calling party 101 initiates (1401) a call to the called party 104. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. A call may be a missed call if the called party 104 fails to pick up the call. A missed call may be defined as a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. The missed call gets recorded in the list of missed calls in the wireless communication device of the called party 104. Both the calling party 101 and the called party 104 subscribe for the notification service. When the called party 104 views the record of missed call, the wireless device of the called party 104 generates (1402) a notification. A pop up may appear on the wireless device of the called party 104. The pop up asks for a confirmation from the called party 104 for sending the notification. When the called party 104 confirms, the wireless device of the called party 104 sends (1403) the notification to the calling party 101. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and an on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging.
FIG. 15 is a flow chart depicting a method of sending a notification for acknowledgment of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. A calling party 101 makes (1501) a call to a called party 104. The call may result in a missed call as the called party 104 may be busy to address the call or may be out of coverage area of the network. The missed call gets recorded in the list of missed calls on the wireless device of the called party 104. The wireless device of the called party 104 checks (1503) if the called party 104 has viewed the record of the missed call from the calling party 101. Once the called party 104 views the record, the wireless device of the called party 104 generates (1504) a notification on the wireless device of the called party 104. The wireless device of the called party 104 asks (1505) for confirmation from the called party 104 using a pop up. On receiving a confirmation from the called party 104, the wireless device of the called party 104 sends (1506) the notification to the calling party 101. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The various actions in method 1500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 15 may be omitted.
FIG. 16 is a block diagram illustrating a system to provide notification for acknowledgment of missed calls by the called party, in accordance with the embodiments herein. A calling party 101 initiates a call to a called party 103 through a network 102. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. The call may be a missed call if the called party 104 fails to pick up the call. A missed call may be a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. When the called party 104 views the record of missed call, the application 201 on the wireless device is activated. The application 201 will generate a notification which can be user defined. The application 201 can send the notification to the network 102 on receiving a confirmation from the called party 104. The application 201 can also be configured so that the called party 104 is not notified before sending the acknowledgement for the missed call. This is the case where the called party has provisioned the application to send notification unsolicited upon acknowledgment of the missed call. The application 201 can be configured not to send any notification to the calling party 101. The application 201 can also provide the called party with the option of defining the text that goes as part of the notification. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The network 102 forwards the notification to the calling party 101, hereby notifying the calling party 101 of the missed call being viewed by the called party 104.
FIG. 17 illustrates a flow diagram for sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. The calling party 101 initiates (1701) a call to the called party 104 through the communication network 102. The network 102 may comprise of a single network, where the calling party 101 and the called party 104 belong to the same network 102. The called party 104 and the calling party 101 may belong to different networks, wherein the calling party 101 belongs to network 301 and the called party 104 belongs to network 302. A call may be a missed call if the called party 104 fails to pick up the call. A missed call may be defined as a call which is not answered by the called party 104, a call that returns a busy tone, or the case wherein the wireless device of the called party 104 is switched off or is out of the coverage area. The missed call gets recorded in the list of missed calls in the wireless communication device of the called party 104. Both the calling party 101 and the called party 104 subscribe for the notification service. When the called party 104 views the record of missed call, the application 201 on the wireless device of the called party 104 is activated. The application 201 generates (1702) a notification. When the called party 104 confirms, the application 201 sends (1703) the notification to the calling party 101. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging.
FIG. 18 is a flow chart depicting a method of sending a notification for acknowledgement of missed call to the calling party, on confirmation by the called party, in accordance with the embodiments herein. A calling party 101 makes (1801) a call to a called party 104. The call may result in a missed call as the called party 104 may be busy to address the call or may be out of coverage area of the network. The missed call gets recorded in the list of missed calls on the wireless device of the called party 104. The calling party 101 as well as the called party 104 install the application 201 on their wireless device. The application 201 checks (1803) if the called party 104 has viewed the record of the missed call from the calling party 101. Once the called party 104 views the record, the application 201 generates (1804) a notification on the wireless device of the called party 104. The application 201 asks (1805) for confirmation from the called party 104 using a pop up. On receiving a confirmation from the called party 104, the application 201 sends (1806) the notification to the calling party 101. The notification comprises of information like time the called party 104 viewing the missed call, the address of the calling party 101 as the destination address and so on. The notification may also be defined by the called party 104. The notification may be in the form of a SMS, MMS, WAP message or any other suitable means of messaging. The various actions in method 1800 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 18 may be omitted.
The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing service management functions for the network elements. The network elements shown in FIGS. 1 to 4 and FIGS. 13 and 16 include blocks which can be at least one of a hardware device, a software module or a combination of hardware device and software module
The embodiment disclosed herein specifies a method of providing notification for acknowledgement of missed calls to the calling party. The system is equipped with an application server which confirms the subscription of both the called and calling party to provide the notification facility. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a software program written in e.g. Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof, e.g. one processor and two FPGAs. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means are at least one hardware means and/or at least one software means. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. The device may also include only software means. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.

Claims (20)

The invention claimed is:
1. A method in a wireless communication system of notifying a calling party when a called party acknowledges a missed called notification, where said calling party initiated said missed call to said called party, said method comprising:
sending a notification to said calling party, on said called party viewing and acknowledging said missed call notification for said missed call from said calling party.
2. The method, as claimed in claim 1, wherein said calling party is subscribed to a notification service which regulates permission of calling parties to use said method.
3. The method, as claimed in claim 1, wherein said called party is subscribed to a notification service which regulates permission of called parties to use said method.
4. The method, as claimed in claim 1, wherein an application present on a communication device of said called party prompts said called party to send a notification.
5. The method, as claimed in claim 1, wherein an application present on a communication device of said called party sends said notification automatically.
6. The method, as claimed in claim 1, wherein an application present on a communication device of said called party sends said notification on receiving a confirmation from said called party.
7. The method, as claimed in claim 1, wherein said notification is one of:
a Short Messaging Service (SMS);
a Multimedia Messaging Service (MMS); and
a Wireless Application Protocol (WAP) message.
8. The method, as claimed in claim 1, wherein said notification is pre-defined by an application present on a communication device of said called party.
9. The method, as claimed in claim 1, wherein said notification is defined by said called party.
10. The method, as claimed in claim 1, wherein said notification is sent to said calling party via an application server.
11. The method, as claimed in claim 1, wherein an application server verifies if said calling party is subscribed to a notification service which regulates permission of calling parties to use said method.
12. The method, as claimed in claim 1, wherein said notification is sent to said calling party through networks of said calling party and said called party directly.
13. A communication device, said device comprising:
a prompt that, in response to the device receiving a missed call from a calling party and a user of the device accessing a record of said missed call, prompts the user of said communication device to send a notification to said calling party; and
a sending part operative to send said notification to said calling party.
14. The communication device as claimed in claim 13, wherein said communication device is adapted to send said notification in the form of one of:
a Short Messaging Service (SMS);
a Multimedia Messaging Service (MMS); and
a Wireless Application Protocol (WAP) message.
15. A method in a wireless communication system of notifying a calling party when a called party acknowledges a missed called, said method comprising:
detecting if a call initiated from the calling party to the called party is missed by the called party;
updating a list of missed calls on a device of the called party, wherein said updating includes adding a missed call record to the list indicating a missed called from the calling party in response to detecting said missed called;
detecting if at least one of the missed called list or the missed call record is accessed; and
generating a notification intended for said calling party in response to detecting said access.
16. The method of claim 15, wherein the call initiated from the calling party to the called party is detected as missed if any one of the following occurs: the called party does not answer the call, the calling party is returned a busy signal, the device of the called party is switched off or the device of the called party is outside a coverage area in which service is provided to the device.
17. The method of claim 15, wherein the notification includes an indication of a time of the detected access which resulted in the notification being generated.
18. The method of claim 15, wherein the notification includes an indication of a time that the missed call record was added to the list of missed calls.
19. The method of claim 15, further comprising:
sending the notification directed to the calling party.
20. The method of claim 15, further comprising:
providing a prompt to confirm sending of the notification;
sending said notification directed to the calling party in response to detecting an affirmative response to said prompt; and
not sending said notification directed to the calling party in response to detecting a negative response to said prompt.
US13/201,582 2009-02-16 2009-02-16 System and method of providing notifications for acknowledgement of missed calls Active US8755773B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2009/052311 WO2010092439A1 (en) 2009-02-16 2009-02-16 A system and method of providing notifications for acknowledgement of missed calls

Publications (2)

Publication Number Publication Date
US20120028618A1 US20120028618A1 (en) 2012-02-02
US8755773B2 true US8755773B2 (en) 2014-06-17

Family

ID=41217716

Family Applications (1)

Application Number Title Priority Date Filing Date
US13/201,582 Active US8755773B2 (en) 2009-02-16 2009-02-16 System and method of providing notifications for acknowledgement of missed calls

Country Status (6)

Country Link
US (1) US8755773B2 (en)
EP (1) EP2396981B1 (en)
JP (1) JP2012518310A (en)
KR (1) KR101261260B1 (en)
CN (1) CN102318378B (en)
WO (1) WO2010092439A1 (en)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103164791B (en) * 2011-12-13 2016-04-06 阿里巴巴集团控股有限公司 A kind of method and apparatus being realized secure payment by electric terminal
US9294423B2 (en) * 2013-03-15 2016-03-22 Sorenson Communications, Inc. Communication systems and related methods for notifying devices having a plurality of unique identifiers about missed communications
US9325753B2 (en) 2013-03-15 2016-04-26 Sorenson Communications, Inc. User interface for creating and administering a user group, and methods of operating such
US10082934B2 (en) 2013-03-15 2018-09-25 Sorenson Ip Holdings Llc Systems, methods, and devices for replacing a contact entry corresponding to a communication device with a contact entry corresponding to a user group
US9491205B2 (en) 2013-03-15 2016-11-08 Sorenson Communications, Inc. Communication systems and related methods for communicating with devices having a plurality of unique identifiers
US9204088B2 (en) 2013-03-15 2015-12-01 Sorenson Communications, Inc. Systems including and methods of operating communication devices assigned individual and group identities
US9742711B2 (en) 2013-03-15 2017-08-22 Sorenson Ip Holdings, Llc Communication systems and related methods for notifying devices having a plurality of unique identifiers about missed communications
KR102056485B1 (en) 2013-05-09 2019-12-17 삼성전자 주식회사 Method and apparatus for notification of message reception according to property of received message
WO2016015217A1 (en) * 2014-07-29 2016-02-04 华为技术有限公司 Incoming call forwarding method and user equipment
US9473738B2 (en) 2015-03-17 2016-10-18 Sorenson Communications, Inc. Communication systems, communication endpoints, and related methods for remotely controlling communication endpoints
CN109451793B (en) * 2017-06-30 2021-11-23 北京小米移动软件有限公司 Method and device for realizing network edge calculation
US11275602B1 (en) 2019-08-20 2022-03-15 Intrado Corporation Virtual communication service for mobile devices
US11025773B1 (en) * 2019-08-20 2021-06-01 Intrado Corporation Virtual communication service for mobile devices

Citations (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5629982A (en) * 1995-03-21 1997-05-13 Micali; Silvio Simultaneous electronic transactions with visible trusted parties
FR2768007A1 (en) 1997-09-03 1999-02-26 Motorola Inc METHOD AND APPARATUS FOR PROVIDING MESSAGE RECEIPT VERIFICATION NOTICES IN A MESSAGING SYSTEM
WO2001028171A1 (en) 1999-10-08 2001-04-19 Nokia Corporation Location sensitive multimedia messaging (mms)
US20010031631A1 (en) * 2000-01-12 2001-10-18 Pitts Robert L. Secure area communication arrester
US6323754B1 (en) * 1997-07-02 2001-11-27 U.S. Philips Corporation Two-way telecommunications system
EP1259036A1 (en) 2000-12-04 2002-11-20 NTT DoCoMo, Inc. E-mail distribution control method and mail server
US6529737B1 (en) 1999-03-01 2003-03-04 Nortel Networks Limited Apparatus and method for sending a customized message to a telephony subscriber and establishing a direct operative connection therewith within the same telephone call
WO2003085999A1 (en) 2002-04-09 2003-10-16 Siemens Aktiengesellschaft Method for transmitting data, particularly having multimedia contents, in a mobile radio telephone network
US20030198324A1 (en) * 2002-04-23 2003-10-23 Beno Corporation Method for notifying and reminding phone users of missed calls
US20030206619A1 (en) * 2002-05-01 2003-11-06 David Curbow System and method of using presence information to delay dialing phone calls initiated by a caller to a callee
US6678361B2 (en) * 1999-04-19 2004-01-13 Nokia Corporation Method for delivering messages
US20040090951A1 (en) * 2002-10-10 2004-05-13 Lg Electronics, Inc. System and method for serving short message in high rate packet data system
US20050047561A1 (en) * 2003-08-27 2005-03-03 Frank Seiferth Advanced method and system for handling missed mobile calls
US20050059384A1 (en) * 2003-09-12 2005-03-17 Nokia Corporation Method and device for handling missed calls in a mobile communications environment
US20050124360A1 (en) * 2003-12-08 2005-06-09 Samsung Electronics Co., Ltd. Mobile phone capable of deleting sent short message stored in receiver's mobile phone and method of transmitting and deleting short message using the same
US20060293037A1 (en) * 2005-06-27 2006-12-28 Signore Kenneth W D Method for alerting a mobile unit of a missed call upon movement of the mobile unit
US20070263789A1 (en) * 2006-03-31 2007-11-15 Richard Palazzo Voice message recall
US20070275698A1 (en) * 2006-05-11 2007-11-29 Kuiken David P Method and apparatus for dynamic voice response messages
US20080057926A1 (en) * 2006-09-06 2008-03-06 Scott Forstall Missed Telephone Call Management for a Portable Multifunction Device
US7493110B2 (en) * 2004-11-29 2009-02-17 Roamware Inc. Missed call alerts
US20090245483A1 (en) * 2008-03-25 2009-10-01 Fujitsu Limited Information processing terminal device and method for notifying missed call or unread e-mail
US20090285166A1 (en) * 2008-05-13 2009-11-19 At&T Mobility Ii Llc Interactive white list prompting to share content and services associated with a femtocell
US20100016002A1 (en) * 2008-07-18 2010-01-21 Konicek Jeffrey C End to End Acknowledgment of SMS Messages
US20100111275A1 (en) * 2008-10-31 2010-05-06 Prathap Raj Varma Method for communication information recall in an enterprise network
US20110021182A1 (en) * 2008-03-18 2011-01-27 Hengxi Huan Method and apparatus for automatically handling missed calls in a communication terminal
US7949328B2 (en) * 2005-03-14 2011-05-24 Roamware, Inc. System for delivering user-generated short-text notified multimedia messages between operator networks
US8036643B2 (en) * 2000-12-22 2011-10-11 Telecom Italia S.P.A. Method and device for handling telephone calls directed to non-reachable mobile phones
US20110270935A1 (en) * 2008-09-16 2011-11-03 Pioneer Corporation Communication device, information communication system, method for controlling communication of communication device and program therefor
US8126120B2 (en) * 2005-12-12 2012-02-28 Tellme Networks, Inc. Providing missed call and message information

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005086584A (en) * 2003-09-10 2005-03-31 Nec Corp Portable telephone, schedule management method used for the same, and its program
JP2006229579A (en) * 2005-02-17 2006-08-31 Matsushita Electric Ind Co Ltd Electronic mail system
JP4541295B2 (en) * 2005-12-28 2010-09-08 シャープ株式会社 Communications system
JP4676344B2 (en) * 2006-01-20 2011-04-27 株式会社ナカヨ通信機 Telephone system that notifies you of your presence
CN101064958A (en) * 2006-04-28 2007-10-31 摩托罗拉公司 Method and system for indication to obtain contact with the called mobile equipment
JP2007318642A (en) * 2006-05-29 2007-12-06 Fujitsu Ltd Method for congestion control, and subscriber terminal disaster system, and core network used for the method

Patent Citations (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5629982A (en) * 1995-03-21 1997-05-13 Micali; Silvio Simultaneous electronic transactions with visible trusted parties
US6323754B1 (en) * 1997-07-02 2001-11-27 U.S. Philips Corporation Two-way telecommunications system
FR2768007A1 (en) 1997-09-03 1999-02-26 Motorola Inc METHOD AND APPARATUS FOR PROVIDING MESSAGE RECEIPT VERIFICATION NOTICES IN A MESSAGING SYSTEM
US5956390A (en) 1997-09-03 1999-09-21 Motorola, Inc. Method and apparatus for providing verified message receipt in a messaging system
US6529737B1 (en) 1999-03-01 2003-03-04 Nortel Networks Limited Apparatus and method for sending a customized message to a telephony subscriber and establishing a direct operative connection therewith within the same telephone call
US6678361B2 (en) * 1999-04-19 2004-01-13 Nokia Corporation Method for delivering messages
WO2001028171A1 (en) 1999-10-08 2001-04-19 Nokia Corporation Location sensitive multimedia messaging (mms)
US20010031631A1 (en) * 2000-01-12 2001-10-18 Pitts Robert L. Secure area communication arrester
EP1259036A1 (en) 2000-12-04 2002-11-20 NTT DoCoMo, Inc. E-mail distribution control method and mail server
US8036643B2 (en) * 2000-12-22 2011-10-11 Telecom Italia S.P.A. Method and device for handling telephone calls directed to non-reachable mobile phones
WO2003085999A1 (en) 2002-04-09 2003-10-16 Siemens Aktiengesellschaft Method for transmitting data, particularly having multimedia contents, in a mobile radio telephone network
US20050165897A1 (en) 2002-04-09 2005-07-28 Ralf Prenzel Method for transmitting data, particularly having multimedia contents, in a mobile radio telephone network
US20030198324A1 (en) * 2002-04-23 2003-10-23 Beno Corporation Method for notifying and reminding phone users of missed calls
US20030206619A1 (en) * 2002-05-01 2003-11-06 David Curbow System and method of using presence information to delay dialing phone calls initiated by a caller to a callee
US20040090951A1 (en) * 2002-10-10 2004-05-13 Lg Electronics, Inc. System and method for serving short message in high rate packet data system
US20050047561A1 (en) * 2003-08-27 2005-03-03 Frank Seiferth Advanced method and system for handling missed mobile calls
US20050059384A1 (en) * 2003-09-12 2005-03-17 Nokia Corporation Method and device for handling missed calls in a mobile communications environment
US20050124360A1 (en) * 2003-12-08 2005-06-09 Samsung Electronics Co., Ltd. Mobile phone capable of deleting sent short message stored in receiver's mobile phone and method of transmitting and deleting short message using the same
US7493110B2 (en) * 2004-11-29 2009-02-17 Roamware Inc. Missed call alerts
US7949328B2 (en) * 2005-03-14 2011-05-24 Roamware, Inc. System for delivering user-generated short-text notified multimedia messages between operator networks
US20060293037A1 (en) * 2005-06-27 2006-12-28 Signore Kenneth W D Method for alerting a mobile unit of a missed call upon movement of the mobile unit
US8126120B2 (en) * 2005-12-12 2012-02-28 Tellme Networks, Inc. Providing missed call and message information
US20070263789A1 (en) * 2006-03-31 2007-11-15 Richard Palazzo Voice message recall
US20070275698A1 (en) * 2006-05-11 2007-11-29 Kuiken David P Method and apparatus for dynamic voice response messages
US20080057926A1 (en) * 2006-09-06 2008-03-06 Scott Forstall Missed Telephone Call Management for a Portable Multifunction Device
US20110021182A1 (en) * 2008-03-18 2011-01-27 Hengxi Huan Method and apparatus for automatically handling missed calls in a communication terminal
US20090245483A1 (en) * 2008-03-25 2009-10-01 Fujitsu Limited Information processing terminal device and method for notifying missed call or unread e-mail
US20090285166A1 (en) * 2008-05-13 2009-11-19 At&T Mobility Ii Llc Interactive white list prompting to share content and services associated with a femtocell
US20100016002A1 (en) * 2008-07-18 2010-01-21 Konicek Jeffrey C End to End Acknowledgment of SMS Messages
US20110270935A1 (en) * 2008-09-16 2011-11-03 Pioneer Corporation Communication device, information communication system, method for controlling communication of communication device and program therefor
US20100111275A1 (en) * 2008-10-31 2010-05-06 Prathap Raj Varma Method for communication information recall in an enterprise network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
International Search Report for PCT/IB2009/052311 dated Nov. 27, 2009.

Also Published As

Publication number Publication date
KR101261260B1 (en) 2013-05-07
WO2010092439A1 (en) 2010-08-19
EP2396981A1 (en) 2011-12-21
CN102318378A (en) 2012-01-11
KR20110114628A (en) 2011-10-19
JP2012518310A (en) 2012-08-09
EP2396981B1 (en) 2013-04-03
US20120028618A1 (en) 2012-02-02
CN102318378B (en) 2016-04-13

Similar Documents

Publication Publication Date Title
US8755773B2 (en) System and method of providing notifications for acknowledgement of missed calls
US8364122B2 (en) Delayed delivery messaging
US20090017802A1 (en) Undelivered Call Indicator
US9060253B2 (en) Identifying and blocking mobile messaging service spam
WO2008134944A1 (en) Missed call reminding method, system and mobile service device
EP3069540B1 (en) Missed call notification by notifying contacts of the called party
CN103297941A (en) Communication event processing method and communication event processing device
US10757149B2 (en) Usage authorization control for group communications in a communication network
KR20090073205A (en) Storage of data messages for later retrieval by the recipient
EP2785081A1 (en) Missed call prompting system and method
US20110028133A1 (en) Methods and Apparatus for Providing a Missed Call Alert to a Calling Party
NZ601954A (en) Systems and methods for filtering cellular telephone messages
US8606235B2 (en) Systems and methods for notification of mobile communications device use
US10750014B2 (en) Management of call connection attempt
KR101468431B1 (en) Mobile Communication System for Intercepting Spam-Call and Control Method thereof
WO2016183988A1 (en) Missed call reminder method, device, and core network
WO2008073234A2 (en) Method and system for applying value added services on messages sent to a subscriber without affecting the subscriber's mobile communication
US20180234822A1 (en) Method and control node for handling incoming communication in a vehicle
CN103081451B (en) To the monitoring of Call Forwarding destination
EP2200264A1 (en) Method for notifying availability of called party to calling party
KR101019774B1 (en) Method and aparratus for notifying call in absence of receiver
KR20100082651A (en) System and apparatus for providing message service
CN105812534A (en) Method and system for pushing voice messages
KR20080048225A (en) Method and apparatus for call to limit spam messaging
KR20100026494A (en) Method and apparatus for providing the location information of a called mobile station to a caller mobile station

Legal Events

Date Code Title Description
AS Assignment

Owner name: ALCATEL LUCENT, FRANCE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GOEL, MUDIT;KANUGOVI, SATISH;GADGIL, SARANG;AND OTHERS;REEL/FRAME:027109/0059

Effective date: 20110905

AS Assignment

Owner name: CREDIT SUISSE AG, NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNOR:LUCENT, ALCATEL;REEL/FRAME:029821/0001

Effective date: 20130130

Owner name: CREDIT SUISSE AG, NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:029821/0001

Effective date: 20130130

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: ALCATEL LUCENT, FRANCE

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033868/0555

Effective date: 20140819

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551)

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8