Generation of information based on event data of a call

• US 10,506,096 B2
• Filed: 05/23/2018
• Issued: 12/10/2019
• Est. Priority Date: 05/24/2017
• Status: Active Grant

• Current Assignee: Telia Company AB
• Original Assignee: Telia Company AB
• Inventors: Seppanen, Juho
• Primary Examiner(s): Bilgrami, Asghar H
• Application Number:
  US15/987,565
• Publication Number:
  US 20180343340A1
• Time in Patent Office: 566 Days
• CPC Class Codes: H04M 2201/14 Delay circuits; Timers
• CPC Class Codes: H04M 2207/12 intelligent networks
• CPC Class Codes: H04M 3/02 Calling substations, e.g. by ringing selective calling H04Q
• CPC Class Codes: H04M 3/42017 Customized ring-back tones
• CPC Class Codes: H04M 3/42093 Notifying the calling party of information on the called or connected party

Abstract

A server, a system, a computer program product, and a method for generating information relating to a subscriber B with respect to a call connection attempt from a subscriber A to the subscriber B by a server. The method including steps of receiving event data; determining when the event data comprises an event representing a busy state; determining when the previous event represents a call ringing state; generating an indication that the call connection attempt is rejected by the subscriber B; and in response to a determination that the previous event does not represent the call ringing state, generating an indication that the call connection attempt did not reach the subscriber B.

Claims

1. A method for generating information, wherein:

the information relates to a subscriber B with respect to a call connection attempt from a subscriber A to the subscriber B by a server, the method comprising;

receiving event data representing the call connection attempt related events,

determining if the event data comprises an event representing a busy state,

in response to a determination that the event data comprises the event representing the busy state determining if the previous event to the event representing the busy state represents a call ringing state,

in response to a determination that the previous event to the event representing the busy state represents the call ringing state generating an indication that the call connection attempt is rejected by the subscriber B,

in response to a determination that the previous event to the event representing the busy state does not represent the call ringing state generating an indication that the call connection attempt did not reach the subscriber B, and

in response to the generation of the indication that the call connection attempt has not reached the subscriber B, generating a notification of a missed connection attempt to the subscriber B.

2. The method of claim 1, the method further comprises, in response to a determination that the previous event to the event representing the busy state represents the call ringing state, that:

duration of the ringing state is determined,

the duration is compared to a timeout value representing a value of time defining a period of time of rejecting the call connection attempt by a communication network implementing the call connection attempt, and

in response to a detection that the duration of the ringing state exceeds or corresponds to the timeout value, generating an indication that the call connection attempt is rejected by the communication network, and

in response to a detection that the duration of the ringing state is below the timeout value, generating the indication that the call connection attempt is rejected by the subscriber B.

3. The method of claim 2, wherein the duration of the ringing state is determined by one of the following:

by determining a period of time between an instant of time when the event representing the busy state is received and an instant of time when the event representing the ringing state is received, by obtaining a timer value triggered in response to a receipt of the ringing state and stopped in response to the receipt of the busy state.

4. The method of claim 1, wherein the event data is received from an intelligent network.

5. The method of claim 1, wherein the event data received is stored in a memory accessible by the server.

6. The method of claim 1, wherein the determination with respect to the event is performed by:

obtaining at least one identifier from the event data, and

comparing it to at least one comparison data value representing at least one state of a subscriber.

14. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein for performing the method of claim 1 when the computer program product is executed on a computer.

15. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein for performing the method of claim 2 when the computer program product is executed on a computer.

16. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein for performing the method of claim 3 when the computer program product is executed on a computer.

17. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein for performing the method of claim 4 when the computer program product is executed on a computer.

18. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein for performing the method of claim 5 when the computer program product is executed on a computer.

7. A server for generating information, wherein:

the information relates to a subscriber B with respect to a call connection attempt from a subscriber A to the subscriber B, the server comprising;

at least one processor;

at least one memory including computer program code;

the at least one memory and the computer program code configured to, with the at least one processor, cause the server to perform;

receive event data representing the call connection attempt related events,

determine if the event data comprises an event representing a busy state,

in response to a determination that the event data comprises the event representing the busy state determine if the previous event to the event representing the busy state represents a call ringing state,

in response to a determination that the previous event to the event representing the busy state represents the call ringing state generate an indication that the call connection attempt is rejected by the subscriber B,

in response to a determination that the previous event to the event representing the busy state does not represent the call ringing state generate an indication that the call connection attempt did not reach the subscriber B, and

in response to the generation of the indication that the call connection attempt has not reached the subscriber B, generate a notification of a missed connection attempt to the subscriber B.

8. The server of claim 7, the server is further configured to, in response to a determination that the previous event to the event representing the busy state represents the call ringing state:

determine duration of the ringing state,

compare the duration to a timeout value representing a value of time defining a period of time of rejecting the call connection attempt by a communication network implementing the call connection attempt, and

generate, in response to a detection that the duration of the ringing state exceeds or corresponds to the timeout value, an indication that the call connection attempt is rejected by the communication network, and

generate, in response to a detection that the duration of the ringing state is below the timeout value, the indication that the call connection attempt is rejected by the subscriber B.

9. The server of claim 8, wherein the server is configured to determine the duration of the ringing state by one of the following:

by determining a period of time between an instant of time when the event representing the busy state is received and an instant of time when the event representing the ringing state is received, by obtaining a timer value triggered in response to a receipt of the ringing state and stopped in response to the receipt of the busy state.

10. The server of claim 7, wherein the server is configured to receive the event data from an intelligent network.

11. The server of claim 7, wherein the server is configured to store the event data in a memory accessible by the server.

12. The server of claim 7, wherein the server is configured to perform the determination with respect to the event by:

obtaining at least one identifier from the event data, and

comparing it to at least one comparison data value representing at least one state of a subscriber.

13. A system for generating information, wherein:

the information relates to a subscriber B with respect to a call connection attempt from a subscriber A to the subscriber B, the system comprising;

a call connection unit,

a server,

in the system the server is configured to;

receive event data representing the call connection attempt related events from the call connection unit,

determine if the event data comprises an event representing a busy state,

in response to a determination that the event data comprises the event representing the busy state determine if the previous event to the event representing the busy state represents a call ringing state,

in response to a determination that the previous event to the event representing the busy state represents the call ringing state generate an indication that the call connection attempt is rejected by the subscriber B,

in response to a determination that the previous event to the event representing the busy state does not represent the call ringing state generate an indication that the call connection attempt did not reach the subscriber B, and

in response to the generation of the indication that the call connection attempt has not reached the subscriber B, generate a notification of a missed connection attempt to the subscriber B.