System and method for generating call records based on account codes
First Claim
1. A method for tracking calls from a subscriber number to called party numbers in the same local access and transport network (LATA) as the subscriber number, according to an intraLATA call tracking service, the method comprising:
- receiving call data relating to an intraLATA call from the subscriber number;
when the intraLATA call tracking service is active, receiving a code entered from a terminal associated with the subscriber number;
comparing the received code with a previously stored subscriber account code;
when the received code matches the subscriber account code, storing data in association with the subscriber account code and continuing processing of the call, the data comprising at least the call data; and
when the received code does not match the subscriber account code, discontinuing processing of the call.
0 Assignments
0 Petitions
Accused Products
Abstract
A telecommunications service implements an account code reporting feature by storing an account code associated with a subscriber at a service control point (SCP) in the public switched telephone network (PSTN). When a call is initiated from the subscriber'"'"'s terminal, the SCP receives outgoing call data, including the subscriber'"'"'s telephone number, a called party number and an account code entered from the subscriber'"'"'s terminal. The SCP determines whether the call is subject to the account code reporting service and, if so, stores the call data. The SCP transmits the call data to a service management system accessible by the subscriber via a graphical user interface through a packet switched data network and an interactive voice response through the PSTN. The call is subject to the account code reporting service when the called party number is in the same local access and transport area as the subscriber'"'"'s telephone number.
-
Citations
20 Claims
-
1. A method for tracking calls from a subscriber number to called party numbers in the same local access and transport network (LATA) as the subscriber number, according to an intraLATA call tracking service, the method comprising:
-
receiving call data relating to an intraLATA call from the subscriber number; when the intraLATA call tracking service is active, receiving a code entered from a terminal associated with the subscriber number; comparing the received code with a previously stored subscriber account code; when the received code matches the subscriber account code, storing data in association with the subscriber account code and continuing processing of the call, the data comprising at least the call data; and when the received code does not match the subscriber account code, discontinuing processing of the call. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A computer readable medium for storing a computer program that enables collection of data relating to outgoing calls, placed from a terminal of an account code service subscriber, based on at least one predetermined account code associated with the subscriber, the computer readable medium comprising:
-
a first receiving source code segment that receives signaling data relating to an outgoing call from the subscriber terminal, the signaling data indicating at least a calling party number and a called party number; a first determining source code segment that determines whether the calling party number is in the same local access and transport area (LATA) as the called party number, based on the signaling data; a second receiving source code segment that receives a code entered at the subscriber terminal, when the calling party number and the called party number are in the same LATA; a second determining source code segment that determines whether the received code matches the at least one predetermined account code associated with the subscriber; a storing source code segment that stores at least a portion of the signaling data in association with the at least one predetermined account code when the received code matches the at least one predetermined account code; and a terminating source code segment that initiates termination of the outgoing call when the second receiving source code segment does not receive the code entered by the subscriber or the second determining source code segment determines that the code entered by the subscriber does not match the at least one predetermined account code. - View Dependent Claims (8, 9, 10, 11, 12, 13, 14)
-
-
15. A method for tracking and controlling calls by a calling party from at least one subscriber directory number, in a local access and transport area (LATA) of a telecommunications network, to called party directory numbers in the same LATA, the at least one subscriber directory number having an associated account code, comprising one of a verified account code for tracking and completing the calls and an unverified account code for tracking the calls, the method comprising:
-
receiving data relating to an outgoing call from the at least one subscriber directory number, the data indicating the at least one subscriber directory number and a called party number; determining whether the at least one subscriber directory number and the called party number are in the same LATA based on the received data; when the at least one subscriber directory number and the called party number are in the same LATA, requesting entry of the account code associated with the at least one subscriber directory number and receiving a code entered by the calling party; determining whether the entered code matches the account code; when the entered code matches the account code, storing the data in association with the account code and processing the call; when the entered code does not match the associated account code, determining whether the account code is a verified account code or an unverified account code; when the account code is a verified code, terminating the call without storing the data; and when the account code is an unverified account code, storing the data in association with the account code and processing the call. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification