Classifications

• • 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/42195—Arrangements for calling back a calling subscriber
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/80—Rating or billing plans; Tariff determination aspects
  • H04M15/8038—Roaming or handoff
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/83—Notification aspects
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/83—Notification aspects
  • H04M15/835—Time or frequency of notifications, e.g. Advice of Charge [AoC]
  • H04M15/8351—Time or frequency of notifications, e.g. Advice of Charge [AoC] before establishing a communication
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/83—Notification aspects
  • H04M15/84—Types of notifications
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/83—Notification aspects
  • H04M15/84—Types of notifications
  • H04M15/844—Message, e.g. SMS
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/83—Notification aspects
  • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
  • H04M15/852—Low balance or limit reached
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/83—Notification aspects
  • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
  • H04M15/854—Available credit
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/83—Notification aspects
  • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
  • H04M15/856—Unsuccessful event
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/90—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
• • 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/42025—Calling or Called party identification service
  • H04M3/42034—Calling party identification service
  • H04M3/42042—Notifying the called party of information on the calling party
• • 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/42025—Calling or Called party identification service
  • H04M3/42034—Calling party identification service
  • H04M3/42059—Making use of the calling party identifier
• • 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/42365—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
  • H04M3/42374—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity where the information is provided to a monitoring entity such as a potential calling party or a call processing server
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/0016—Arrangements providing connection between exchanges
  • H04Q3/0029—Provisions for intelligent networking
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M2203/00—Aspects of automatic or semi-automatic exchanges
  • H04M2203/10—Aspects of automatic or semi-automatic exchanges related to the purpose or context of the telephonic communication
  • H04M2203/1008—Calls without connection establishment for implicit information transfer or as a service trigger
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M2203/00—Aspects of automatic or semi-automatic exchanges
  • H04M2203/65—Aspects of automatic or semi-automatic exchanges related to applications where calls are combined with other types of communication
  • H04M2203/651—Text message transmission triggered by call
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M2242/00—Special services or facilities
  • H04M2242/04—Special services or facilities for emergency applications
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13345—Intelligent networks, SCP
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13545—Indexing scheme relating to selecting arrangements in general and for multiplex systems monitoring of signaling messages, intelligent network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/345—Intelligent network

Definitions

• the invention relates to systems and methods for intimating a terminating party of a communication failure due to reasons not attributable to terminating party's availability.
• a method for intimating a terminating party of a communication failure comprises the steps of receiving a communication request from an origination party.
• the communication request corresponds to any of voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• the method further comprises of sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced and receiving, by a platform, "request not serviced indication", said "request not serviced indication” being generated only if the request was not serviced for reasons not attributable to terminating party availability and said "request not serviced indication" including data indicative of originating party and terminating party.
• the method further comprises of sending, by the platform, an alert to terminating party, said alert including data indicative of the originating party.
• a system for intimating a terminating parry of a communication failure is also disclosed.
• the system is being selectively in operative communication with an Intelligent Network (IN) via a communication channel.
• the system comprises of a Mobile Switching Centre (MSC) configured for receiving a communication request from an origination party and sending a trigger to the Intelligent Network to validate whether the communication request can be serviced.
• MSC Mobile Switching Centre
• a Platform is provided, in operative communication with the Mobile Switching Centre, configured for receiving a "request not serviced indication" and sending an alert to a terminating party, including data indicative of the originating party.
• a method for intimating a terminating party of a communication failure comprises the steps of receiving a communication request from an origination party.
• the communication request corresponds to any of a voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• the method further comprises of sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced and receiving "a special CONNECT message" including a special digit pattern being added to Terminating party Number by the IN , said "special CONNECT message” being generated only if the communication request cannot be serviced for reasons not attributable to terminating party availability.
• I Intelligent Network
• SCP Service Control Point
• the method further comprises of automatically translating the "special CONNECT message” into a "communication request forwarding command” based on the special digit pattern and redirecting the communication request to a platform, in accordance with the "communication request forwarding command” and sending, by the platform, an alert to the terminating party, said alert including data indicative of the originating party.
• a system for intimating a terminating party of a communication failure is also disclosed.
• the system is being selectively in operative communication with an Intelligent Network (IN) via a communication channel.
• the system comprises of a Mobile Switching Centre (MSC) configured for receiving a communication request from an origination party and sending a trigger to the Intelligent Network to validate whether the communication request can be serviced; the Mobile Switching Centre further configured for receiving " special CONNECT message” including a special digit pattern added to terminating party number and automatically translating the "special CONNECT message” into a "communication request forwarding command” based on the special digit pattern.
• MSC Mobile Switching Centre
• a Platform in operative communication with the Mobile Switching Centre, configured for receiving the "communication request forwarding command" and sending an alert to a terminating party, including data indicative of the originating party.
• a method for intimating a terminating party of a communication failure is disclosed.
• the method comprises the steps of receiving a communication request from an origination parly.
• the communication request corresponds to any of voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• the method further comprises of sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced and generating and transmitting a "request not serviced indication", said "request not serviced indication” being generated only if the request was not serviced for reasons not attributable to terminating party availability.
• I Intelligent Network
• SCP Service Control Point
• the method further comprises of passively monitoring by a platform to receive the trigger and the "request not serviced indication” and in response to passively receiving the "request not serviced indication", sending, by the platform, an alert to the terminating party.
• a system for intimating a terminating party of a communication failure is also disclosed.
• the system is being selectively in operative communication with an Intelligent Network (IN) via a communication channel.
• the system comprises of a Mobile Switching Centre (MSC) configured for receiving a communication request from an origination party and sending a trigger to the Intelligent Network to validate whether the communication request can be serviced.
• MSC Mobile Switching Centre
• a Platform is provided, selectively in operative communication with the Mobile Switching Centre and Intelligent Network, configured for passively monitoring the communication between the Mobile Switching Centre and the Intelligent Network and sending an alert to a terminating party, including data indicative of the originating party.
• a method for intimating a terminating party of a communication failure is disclosed.
• the method comprises the steps of receiving a communication request from an origination parly.
• the communication request corresponds to any of voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• the method further comprises of sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced and generating and transmitting a call detail record (CDR).
• the call detail record including data indicative of originating party and a terminating party, wherein the CDR is generated in response to a failure to service the request, wherein the failure to service the request being attributed to a reason other than terminating parly availability.
• the method further comprises of sending, by the platform, an alert to the terminating party, said alert including data indicative of the originating party.
• a system for intimating a terminating party of a communication failure is also disclosed.
• the system is being selectively in operative communication with an Intelligent Network (IN) via a communication channel.
• the system comprises of a Mobile Switching Centre (MSC) configured for receiving a communication request from an origination party and sending a trigger to the Intelligent Network to validate whether the communication request can be serviced.
• MSC Mobile Switching Centre
• a Platform is provided, selectively in operative communication with the Intelligent Network, configured for receiving a call detail record and sending an alert to a terminating party, including data indicative of the originating party.
• Figure 1 illustrates a schematic diagram of a system for intimating a terminating party of a communication failure in accordance with an embodiment of the invention
• Figure 2 illustrates a flowchart of a method for intimating a terminating party of a communication failure in accordance with an embodiment of the invention
• Figure 3 illustrates a flow diagram of a system for intimating a terminating party of a communication failure in accordance with a first embodiment of the invention
• Figure 4 illustrates a flow diagram of a system for intimating a terminating party of a communication failure in accordance with a third embodiment of the invention
• Figure S illustrates a flow diagram of a system for intimating a terminating party of a communication failure in accordance with a fourth embodiment of the invention
• Figure 6 illustrates a typical hardware con iguration of a computer system, which is representative of a hardware environment for practicing the present invention.
• modules may be implemented as a hardware circuit comprising custom very large scale integration circuits or gate arrays, off-the-shelf semiconductors such as logic, chips, transistors, or the other discrete components.
• a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
• Modules may also be implemented in software for execution by various types of processors.
• An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executable of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined together, comprise the module and achieve the stated purpose for the module.
• a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
• operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data maybe collected as a single data set, or may be distributed over different locations including over different member disks, and may exist, at least partially, merely as electronic signals on a system or network.
• a system and methods for intimating a terminating party of a communication failure is disclosed.
• the intimation to the terminating party may be due to reasons not attributable to terminating party's availability.
• FIG. 1 illustrates a schematic diagram of a system 100 for intimating a terminating party of a communication failure in accordance with an embodiment of the invention.
• the system 100 comprises of a Mobile Switching Centre (MSC) 110 and a Platform 160.
• the system 100 is selectively in operative communication with an Intelligent Network (IN) or a Service Control Point (SCP) via a communication channel (not shown).
• the communication channels may be analog or digital channels, simplex or duplex or half-duplex channel, uplink or downlink channels, or any other communication channels known in the art.
• the Mobile Switching Centre is the core of a Network Switching Subsystem (NSS).
• the MSC is mostly associated with communications switching functions, such as call set-up, release, and routing. However, it also performs a host of other duties, including routing SMS messages, conference calls, facsimile, and billing as well as interfacing with other networks, such as the public switched telephone network (PSTN).
• PSTN public switched telephone network
• the Mobile Switching Centre (MSC) 110 is configured for receiving a communication request from an origination party. According to an embodiment, the communication request corresponding to any of voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• RCS Rich Communications Suite
• the MSC 110 is further configured to generate and send a trigger to an Intelligent Network (IN) 150 to validate whether the communication request can be serviced.
• the MSC 110 may be selectively in operative communication with the IN 150.
• the MSC 110 may be further configured to receive a "request not serviced indication" from the IN 150.
• the "request not serviced indication” may be generated only if the communication request is not serviced for reasons not attributable to terminating party availability.
• the MSc 110 may be further configured to send the "request not serviced indication" to the platform 160.
• the Mobile Switching Centre may comprise of a processor for generating the trigger; and a data repository for being selectively in operative communication with the processor for storing the details communication request such as sender and receiver details, request type, etc.
• the Intelligent Network (IN) is the standard network architecture intended for fixed as well as mobile telecom networks. It allows operators to differentiate themselves by providing value-added services in addition to the standard telecom services such as PSTN, ISDN and GSM services on mobile phones.
• the Intelligent Network (IN) 150 is configured to receive the communication request from the Mobile Switching Centre 110 and generates a "request not serviced indication" only if the request was not serviced for reasons not attributable to a terminating party availability. According to another embodiment, the reasons corresponds to any of insufficient credits in the account of the originating party to comply with the communication request or the originating party not subscribed for the requested communication request. According to an embodiment, the "request not serviced indication" includes data indicative of originating party 140 and terminating party 170. The IN 150 may be configured for checking the credentials/ credit availability of the originating party to proceed with the communication request.
• the Platform 160 is in operative communication with the MSC 110 and configured for receiving a "request not serviced indication".
• the Platform 160 may be further configured to send an alert to a terminating party, including data indicative of the originating party such that the terminating party is aware that the originating party tried to contact via a communication request.
• the alert may be Short Messaging Service (SMS), a Multimedia Messaging Service MMS or a Rich Communications Suite (RCS).
• the platform 160 is a mobile platform or a mobile interface.
• the originating party and the terminating party may be mobile users having a mobile communication device.
• the mobile communication device may be any device used directly by an end-user to communicate such as handheld computers, UMTS mobile phones, GSM mobile phones, etc.
• the mobile communication device is a wireless phone that operates in a wide service area and is supported by a cellular network.
• the term "mobile communication device” includes Internet connectable mobile phones and devices with mobile phone capabilities, such as mobile phone-equipped Personal Digital Assistants (PDAs) e.g. Blackberry and iPhone.
• PDAs Personal Digital Assistants
• the mobile communication device may be associated with a Mobile Subscriber Integrated Services Digital Network-Number (MSISDN).
• MSISDN Mobile Subscriber Integrated Services Digital Network-Number
• the MSISDN is a number uniquely identifying a subscription in a GSM (Global System for Mobile Communication) or UMTS (Universal Mobile Telecommunications System) mobile network.
• GSM Global System for Mobile Communication
• UMTS Universal Mobile Telecommunications System
• the alert may contain the MSISDN of the mobile communication device of the originating party.
• Figure 2 illustrates a flow chart of a method 200 for intimating a terminating party of a communication failure in accordance with an embodiment of the invention.
• the method comprises of steps of initiating a communication request by the originating party as shown in step 202.
• the method further comprise of receiving a communication request from an origination party at the MSC 110 and sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced, as shown in step 204 and 206.
• I Intelligent Network
• SCP Service Control Point
• validate the communication request comprising checking the credentials/ credit availability of the originating party to proceed with the communication request.
• the method further comprises of receiving, by a platform, "request not serviced indication", said “request not serviced indication” being generated only if the request was not serviced for reasons not attributable to terminating party availability and said "request not serviced indication” including data indicative of originating party and terminating party, as shown in step 207.
• the method further comprise of step of sending, by the platform, an alert to terminating party, said alert including data indicative of the originating parry.
• the method further comprises the step of generating a trigger at the MSC from the received communication request and forwarding the trigger to the IN or SCP.
• the method further comprises the step of directing to the MSC the "request not serviced indication".
• the method further comprises the step of forwarding to the platform the "request not serviced indication" from the MSC.
• Figure 3 illustrates a flow diagram of a system 300 for intimating a terminating party of a communication failure in accordance with a first embodiment of the invention.
• the system 300 is configured for intimating a terminating party of a communication failure.
• the system 300 is being selectively in operative communication with an Intelligent Network (IN) 330 via a communication channel.
• the system 300 comprises of a Mobile Switching Centre (MSC) 310 configured for receiving a communication request from an origination party (Party A) and sending a trigger to the Intelligent Network 330 to validate whether the communication request can be serviced.
• the Mobile Switching Centre is further configured for receiving a "special CONNECT message" including a special digit pattern added to the terminating party number and automatically translating the "special CONNECT message" into a "communication request forwarding command" based on the special digit pattern.
• the system 300 further comprises of a Platform 320 in operative communication with the Mobile Switching Centre 310 configured for receiving the "communication request forwarding command" and sending an alert to a terminating party (Party B), including data indicative of the originating party.
• a Platform 320 in operative communication with the Mobile Switching Centre 310 configured for receiving the "communication request forwarding command" and sending an alert to a terminating party (Party B), including data indicative of the originating party.
• the Mobile Switching Centre may comprise of a processor for generating the trigger and automatically translating the "special CONNECT message" into the "communication request forwarding command” and a data repository for being selectively in operative communication with the processor for storing the details of the originating and terminating party and the details of the communication request.
• the Intelligent Network 330 may be configured to generate the "special CONNECT message" including a special digit pattern, only if the communication request cannot be serviced for reasons not attributable to terminating party availability.
• a method for intimating a terminating party of a communication failure comprises the steps of initiating a communication request by the Party A (Originating Party), as shown in step 1 of Figure 3.
• the method further comprises of receiving the communication request at the MSC 310, as shown by step 2.
• the communication request corresponds to any of a voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• the method further comprises the step of sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced, as shown by step 3 wherein the IN validates the communication request by checking the credentials/ credit availability of the originating party to proceed with the communication request, as shown in step 4.
• IN Intelligent Network
• SCP Service Control Point
• the method further comprises of IN generating disconnect by generating a "special CONNECT message” having a special digit pattern added to the terminating party number and sends the "special CONNECT message” to the MSC 310, as shown in step 5.
• the "special CONNECT message” is generated by the IN for routing the communication request to the platform
• the ""special CONNECT message" " is being generated only if the communication request cannot be serviced for reasons not attributable to terminating party availability.
• the reasons corresponds to any of insufficient credits in the account of the originating party to comply with the communication request or the originating party not subscribed for the requested communication request.
• the method further comprises of the step of automatically translating the "a special CONNECT message” into a "communication request forwarding command” based on the special digit pattern and redirecting the communication request to a platform, in accordance with the "communication request forwarding command", as shown in step 6.
• the method further comprises of releasing the communication request at the platform, as shown in step 7 and sending, by the platform, an alert to the terminating party (Party B), said alert including data indicative of the originating party, as shown in step 8.
• the alert to the terminating party (Party B) is in the form of a SMS or MMS or RCS.
• the method further comprises the step of generating at the MSC a trigger from the received communication request and forwarding the trigger to the IN or SCP.
• Figure 4 illustrates a flow diagram of a system for intimating a terminating party of a communication failure in accordance with a third embodiment of the invention.
• the third embodiment of the invention illustrates a tapping based approach for implementing the system 500.
• the system 500 is configured for intimating a terminating party of a communication failure.
• the system 500 is being selectively in operative communication with an Intelligent Network (IN) via a communication channel.
• the system comprises of a Mobile Switching Centre (MSC) 510 configured for receiving a communication request from an origination party (Party A) and sending a trigger to the Intelligent Network 530 to validate whether the communication request can be serviced.
• MSC Mobile Switching Centre
• the Mobile Switching Centre 510 may comprise of a processor for generating the trigger and a data repository for being selectively in operative communication with the processor for storing the details of the originating and terminating party and the details of the communication request.
• the system further comprises of a platform 520 selectively in operative communication with the Mobile Switching Centre 510 and Intelligent Network 530 configured for passively monitoring the communication between the Mobile Switching Centre 510 and the Intelligent Network 530 and sending an alert to a terminating party (Party B), including data indicative of the originating party.
• a platform 520 selectively in operative communication with the Mobile Switching Centre 510 and Intelligent Network 530 configured for passively monitoring the communication between the Mobile Switching Centre 510 and the Intelligent Network 530 and sending an alert to a terminating party (Party B), including data indicative of the originating party.
• the Intelligent Network 530 is configured for generating the "request not serviced indication" only if the request was not serviced for reasons not attributable to terminating party availability and the "request not serviced indication" including data indicative of originating party and terminating party.
• a method for intimating a terminating party of a communication failure comprises the steps of initiating a communication request by the Party A (Originating Party), as shown in step 1 of Figure 4.
• the method further comprises of receiving the communication request at the MSC 510, as shown by step 2.
• the communication request corresponds to any of a voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• the method further comprises the step of sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced, as shown by step 3 wherein the IN validates the communication request by checking the credentials/ credit availability of the originating party to proceed with the communication request, as shown in step 4.
• IN Intelligent Network
• SCP Service Control Point
• the method further comprises of IN generating disconnect by generating a "request not serviced indication” and sends the "request not serviced indication" to the MSC 510, as shown in step 5.
• the "request not serviced indication” being generated only if the communication request cannot be serviced for reasons not attributable to terminating party availability.
• the reasons corresponds to any of insufficient credits in the account of the originating party to comply with the communication request or the originating party not subscribed for the requested communication request.
• the method further comprises of the step of passively monitoring by a platform to receive the trigger and the "request not serviced indication", as shown in step 6.
• the method further comprises the step of, in response to passively receiving the "request not serviced indication", sending by the platform, an alert to the terminating party (Party B), said alert including data indicative of the originating party, as shown in step 7.
• the alert to the terminating party (Party B) is in the form of a SMS or MMS or RCS.
• the method further comprises the step of generating at the MSC a trigger from the received communication request and forwarding the trigger to the IN or SCP.
• FIG. 5 illustrates a flow diagram of a system for intimating a terminating party of a communication failure in accordance with a fourth embodiment of the invention.
• the fourth embodiment of the invention illustrates a file based approach for implementing the system 600.
• the system 600 is configured for intimating a terminating party of a communication failure.
• the system 600 is being selectively in operative communication with an Intelligent Network (IN) 630 via a communication channel.
• the system comprises of a Mobile Switching Centre (MSC) 610 configured for receiving a communication request from an origination party (Party A) and sending a trigger to the Intelligent Network 630 to validate whether the communication request can be serviced.
• MSC Mobile Switching Centre
• the Mobile Switching Centre 610 may comprise of a processor for generating the trigger and a data repository for being selectively in operative communication with the processor for storing the details of the originating and terminating party and the details of the communication request.
• the system 600 further comprises of a platform 620 selectively in operative communication with the Intelligent Network 630 configured for receiving a call detail record and sending an alert to a terminating party (Party B), including data indicative of the originating party.
• a platform 620 selectively in operative communication with the Intelligent Network 630 configured for receiving a call detail record and sending an alert to a terminating party (Party B), including data indicative of the originating party.
• the Intelligent Network 630 is configured for generating a call detail record (CDR), the call detail record including data indicative of originating party and a terminating party, wherein the CDR is generated in response to a failure to service the request, wherein the failure to service the request being attributed to a reason other than terminating parly availability.
• CDR call detail record
• a method for intimating a terminating party of a communication failure comprises the steps of initiating a communication request by the Party A (Originating Party), as shown in step 1 of Figure 5.
• the method further comprises of receiving the communication request at the MSC 610, as shown by step 2.
• the communication request corresponds to any of a voice call request, a video call request, a SMS request, a MMS request, or a Rich Communications Suite (RCS) request.
• the method further comprises the step of sending a trigger to an Intelligent Network (IN) or a Service Control Point (SCP) to validate whether request can be serviced, as shown by step 3 wherein the IN validates the communication request by checking the credentials/ credit availability of the originating party to proceed with the communication request, as shown in step 4.
• IN Intelligent Network
• SCP Service Control Point
• the method further comprises of IN generating disconnect by generating a call detail record (CDR) and sends the call detail record to the MSC 610, as shown in step 5.
• the call detail record includes the data indicative of originating party (Party A) and a terminating party (Party B), wherein the CDR is generated in response to a failure to service the request, wherein the failure to service the request being attributed to a reason other than terminating party availability.
• the reasons corresponds to any of insufficient credits in the account of the originating party to comply with the communication request or the originating party not subscribed for the requested communication request.
• the method further comprises of the step of parsing all the failure CDR in Intelligent Network 630 as shown in step 6.
• the method further comprises the step of sending by the platform, an alert to the terminating party (Party B), said alert including data indicative of the originating party, as shown in step 7.
• the alert to the terminating party (Party B) is in the form of a SMS or MMS or RCS.
• the method further comprises the step of generating at the MSC a trigger from the received communication request and forwarding the trigger to the IN or SCP.
• the steps of the illustrated method described above herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
• a general- purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, micro controller, or state machine.
• a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
• Figure 6 illustrates a typical hardware configuration of a computer system, which is representative of a hardware environment for practicing the present invention.
• Any of the components such as system 100 may include a portion or all of the computer system 1000.
• the computer system 1000 can include a set of instructions that can be executed to cause the computer system 1000 to perform any one or more of the methods disclosed.
• the computer system 1000 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices.
• the computer system 1000 may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment.
• the computer system 1000 can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
• the term "system” shall also be taken to include any collection of
• the computer system 1000 may include a processor 1002, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both.
• the processor 1002 may be a component in a variety of systems.
• the processor 1002 may be part of a standard personal computer or a workstation.
• the processor 1002 may be one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data
• the processor 1002 may implement a software program, such as code generated manually (i.e., programmed).
• module may be defined to include a plurality of executable modules. As described herein, the modules are defined to include software, hardware or some combination thereof executable by a processor, such as processor 1002.
• Software modules may include instructions stored in memory, such as memory 1004, or another memory device, that are executable by the processor 1002 or other processor.
• Hardware modules may include various devices, components, circuits, gates, circuit boards, and the like that are executable, directed, or otherwise controlled for performance by the processor 1002.
• the computer system 1000 may include a memory 1004, such as a memory 1004 that can communicate via a bus 1008.
• the memory 1004 may be a main memory, a static memory, or a dynamic memory.
• the memory 1004 may include, but is not limited to computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like.
• the memory 1004 includes a cache or random access memory for the processor 1002.
• the memory 1004 is separate from the processor 1002, such as a cache memory of a processor, the system memory, or other memory.
• the memory 1004 may be an external storage device or database for storing data. Examples include a hard drive, compact disc (“CD”), digital video disc (“DVD”), memory card, memory stick, floppy disc, universal serial bus (“USB”) memory device, or any other device operative to store data.
• the memory 1004 is operable to store instructions executable by the processor 1002. The functions, acts or tasks illustrated in the figures or described may be performed by the programmed processor 1002 executing the instructions stored in the memory 1004.
• processing strategies may include multiprocessing, multitasking, parallel processing and the like.
• the computer system 1000 may or may not further include a display unit 1010, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information.
• a display unit 1010 such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information.
• the display 1010 may act as an interface for the user to see the functioning of the processor 1002, or specifically as an interface with the software stored in the memory 1004 or in the drive unit 1016.
• the computer system 1000 may include an input device 1012 configured to allow a user to interact with any of the components of system 1000.
• the input device 1012 may be a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device operative to interact with the computer system 1000.
• the computer system 1000 may also include a disk or optical drive unit 1016.
• the disk drive unit 1016 may include a computer-readable medium 1022 in which one or more sets of instructions 1024, e.g. software, can be embedded. Further, the instructions 1024 may embody one or more of the methods or logic as described. In a particular example, the instructions 1024 may reside completely, or at least partially, within the memory 1004 or within the processor 1002 during execution by the computer system 1000.
• the memory 1004 and the processor 1002 also may include computer-readable media as discussed above.
• the present invention contemplates a computer-readable medium that includes instructions 1024 or receives and executes instructions 1024 responsive to a propagated signal so that a device connected to a network 1026 can communicate voice, video, audio, images or any other data over the network 1026. Further, the instructions 1024 may be transmitted or received over the network 1026 via a communication port or interface 1020 or using a bus 1008.
• the communication port or interface 1020 may be a part of the processor 1002 or may be a separate component.
• the communication port 1020 may be created in software or may be a physical connection in hardware.
• the communication port 1020 may be configured to connect with a network 1026, external media, the display 1010, or any other components in system 1000, or combinations thereof.
• connection with the network 1026 may be a physical connection, such as a wired Ethernet connection or may be established wirelessly as discussed later. Likewise, the additional connections with other components of the system 1000 may be physical connections or may be established wirelessly.
• the network 1026 may alternatively be directly connected to the bus 1008.
• the network 1026 may include wired networks, wireless networks, Ethernet AVB networks, or combinations thereof.
• the wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, 802.1Q or WiMax network.
• the network 1026 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols.
• While the computer-readable medium is shown to be a single medium, the term “computer-readable medium” may include a single medium or multiple media, such as a centralized or distributed database, and associated caches and servers that store one or more sets of instructions.
• the term “computer-readable medium” may also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed.
• the "computer-readable medium” may be non-transitory, and may be tangible.
• the computer-readable medium can include a solid-stale memory such as a memory card or other package that houses one or more nonvolatile read-only memories.
• the computer-readable medium can be a random access memory or other volatile rewritable memory.
• the computer-readable medium can include a magneto- optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium.
• a digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
• dedicated hardware implementations such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement various parts of the system 1000.
• Applications that may include the systems can broadly include a variety of electronic and computer systems.
• One or more examples described may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.
• the system described may be implemented by software programs executable by a computer system. Further, in a non-limited example, implementations can include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement various parts of the system.
• the system is not limited to operation with any particular standards and protocols.
• standards for Internet and other packet switched network transmission e.g., TCP/IP, UDP/IP, HTML, HTTP
• Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed are considered equivalents thereof.
• Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

Landscapes

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

Applications Claiming Priority (2)

Publications (1)

Family

ID=51626094

Family Applications (1)

Country Status (3)

Cited By (4)

Families Citing this family (5)

Citations (2)

Family Cites Families (11)

• 2014
  • 2014-07-16 WO PCT/IB2014/063146 patent/WO2015008232A1/en not_active Ceased
• 2015
  • 2015-12-23 US US15/545,439 patent/US10432785B2/en active Active
  • 2015-12-23 IN IN3897DE2014 patent/IN2014DE03897A/en unknown

Patent Citations (2)

Also Published As

Similar Documents

Legal Events