Source: http://www.google.com/patents/US5912954?dq=3657699
Timestamp: 2016-09-27 23:29:09
Document Index: 773560687

Matched Legal Cases: ['Application No. 60', 'art 138', 'arts 140', 'arts 142', 'arts 142', 'arts 172', 'art 172', 'art 172', 'art 172', 'art 172', 'art 180', 'art 172']

Patent US5912954 - Method and system for providing billing information in a telecommunications ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA method for generating billing information for a call in a telecommunications network is disclosed. In one embodiment, a call initiation stimulus is received at a service switching system (112). The service switching system (112) notifies a service control system (104) of the call initiation stimulus....http://www.google.com/patents/US5912954?utm_source=gb-gplus-sharePatent US5912954 - Method and system for providing billing information in a telecommunications networkAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS5912954 APublication typeGrantApplication numberUS 09/001,622Publication dateJun 15, 1999Filing dateDec 31, 1997Priority dateFeb 28, 1997Fee statusPaidAlso published asWO1998038790A1Publication number001622, 09001622, US 5912954 A, US 5912954A, US-A-5912954, US5912954 A, US5912954AInventorsJohn L. Whited, Hung V. Le, Charles C. Lee, Jr.Original AssigneeAlcatel Usa Sourcing, L.P.Export CitationBiBTeX, EndNote, RefManPatent Citations (7), Non-Patent Citations (4), Referenced by (85), Classifications (15), Legal Events (7) External Links: USPTO, USPTO Assignment, EspacenetMethod and system for providing billing information in a telecommunications network
US 5912954 AAbstract
A method for generating billing information for a call in a telecommunications network is disclosed. In one embodiment, a call initiation stimulus is received at a service switching system (112). The service switching system (112) notifies a service control system (104) of the call initiation stimulus. The service control system (104) generates a first TCAP connect message with a destination routing address portion having a billing information tag and customer billing information. The first TCAP connect message is transmitted to the service switching system (112), which transmits a response message to the service control system (104). The service control system (104) transmits a second TCAP connect message to the service switching system (112) in response to the response message. The service switching system (112) generates a billing record in response to the first TCAP connect message. The method provides for the generation and storing of billing information using standard SS7 signaling, message protocols and call detail record formats, and using any proprietary switch.
1. A method for generating billing information for a call in a telecommunications network, comprising the steps of:receiving a call initiation stimulus at a service switching system; notifying a service control system of the call initiation stimulus by the service switching system; generating a first TCAP connect message by the service control system, the TCAP connect message having a destination routing address portion including a billing information tag and customer billing information; transmitting the first TCAP connect message to the service switching system; transmitting a response message from the service switching system to the service control system in response to the first TCAP message; transmitting a second TCAP connect message from the service control system to the service switching system in response to the response message; and generating a billing record by the service switching system in response to the first TCAP connect message. 2. The method of claim 1, wherein the step of generating the billing record comprises the steps of:passing the customer billing information from the service switching system to a billing system; and generating and storing a call detail record by the billing system. 3. The method of claim 2, wherein the step of generating and storing the call detail record comprises the steps of generating the call detail record including the customer billing information.
4. The method of claim 1, further comprising the step of generating a customer bill by the billing system based upon the billing record.
5. A telecommunications network, comprising:a service switching system; a service control system; and a billing system; the service switching system being operable to receive a call initiation stimulus and to notify the service control system of the call initiation stimulus; the service control system being operable to generate and transmit to the service switching system a first TCAP connect message having a destination routing address portion including a billing information tag and customer billing information; the service switching system being further operable to pass the customer billing information to the billing system; and the billing system being operable to generate a billing record in response to the customer billing information. 6. The telecommunications network of claim 5, wherein the billing system is further operable to generate a bill for a customer based upon the billing record.
7. The telecommunications network of claim 5, wherein the billing system further comprises a storage system operable to store the billing record.
This application claims the benefit of U.S. Provisional Application No. 60/039,676 filed on Feb. 28, 1997, which is incorporated herein by reference.
This invention relates generally to the field of telecommunications and more particularly to a method and system for providing billing information in a telecommunications network.
In intelligent networks, various techniques may be used to track billing information and generate bills for customers. These techniques are typically unique to the type of switch employed in the network. Moreover, known methods typically employ non-standard, switch-dependent messaging to transmit billing information. These switch-dependent methods require significant and costly modification to the network to accommodate the particular billing solution implemented for the switch deployed in the network. In addition, these switch-dependent solutions are not portable across networks.
Therefore, a need has arisen for a method and system for providing billing information in a telecommunications network that address the disadvantages and deficiencies of the prior art.
A method for generating billing information for a call in a telecommunications network is disclosed. In one embodiment of the present invention, a call initiation stimulus is received at a service switching system. The service switching system notifies a service control system of the call initiation stimulus. The service control system generates a first TCAP connect message with a destination routing address portion having a billing information tag and customer billing information. The first TCAP connect message is transmitted to the service switching system, which transmits a response message to the service control system. The service control system transmits a second TCAP connect message to the service switching system in response to the response message. The service switching system generates a billing record in response to the first TCAP connect message.
A technical advantage of the present invention is that the method provides for the generation and storing of billing information using standard SS7 signaling, message protocols and call detail record formats. Another technical advantage is that minimal changes to a telecommunications network are required to accommodate this billing method. Yet another technical advantage is that any proprietary switch may be used in a telecommunications network that implements the billing method.
FIG. 1 is a block diagram of a telecommunications network constructed in accordance with one embodiment of the present invention;
FIG. 2 is a block diagram illustrating an exemplary SS7 message format;
FIG. 3 is a block diagram illustrating an exemplary TCAP message format;
FIG. 4 is a flowchart illustrating a method for generating billing information in accordance with one embodiment of the present invention;
FIG. 5 is a block diagram illustrating a TCAP message formatted in accordance with one aspect of the present invention; and
FIG. 6 is an illustration of an exemplary billing information field of the TCAP message.
FIG. 1 is a block diagram of a telecommunications network 100, such as an advanced intelligent network (AIN). Telecommunications network 100 includes a service management system 102 that interfaces with a plurality of service control points (SCP) 104 and a plurality of signal transfer points (STP) 106 via an industry standard protocol, such as X.25. Service management system 102 provides network information, database management, and administrative support for telecommunications network 100. Service management system 102 generally interfaces with service control points 104 for provisioning, database management, service control point application program management, and collecting traffic metering measurement data.
Service control points 104 may also be directly linked to signal transfer points 106 via a signaling system number 7 (SS7) link set 108. Signal transfer points 106 are further coupled through a signaling system number 7 link set to one or more service switching points 112 and 114, which perform switching and call handling functions in the network. Service control points 104 are transaction based processing systems whose primary responsibility is to respond to queries from service switching points 112 and 114 for data needed to complete routing of a call. Service switching points 112 and 114 are part of the public switched telephone network and are coupled to the customer premises equipment (CPE) of telephone service subscribers or customers 121, which include wire-based telephones and wireless telephones 122 and intelligent peripherals 123.
It will be understood that service control points 104, signal transfer points 106 and service switching points 112 may be functions combined and implemented on one or more platforms rather than discrete points in telecommunications network 100. For example, in one alternative configuration of telecommunications network 100, a plurality of service nodes each contains a service control function and a service switching function. Within a node, the service control function and the service switching function may communicate directly by means of TCAP (transaction capabilities application part) messages without the use of a signal transfer point 106.
Service management system 102 and service switching points 112 and 114 are connected to a billing system 124. Billing system 124 receives information regarding calls, stores the information as call detail records (CDR) in a mass storage device 125, and later uses the information to generate billing information for the customers of network 100. The interaction of billing system 124 with service switching points 112 and 114 will be described more fully below.
Service independent building blocks (SIBs) are building blocks sometimes used to construct service logic programs to implement network services. These service independent building blocks, as defined in the International Telecommunication Union ITU-T Q.1213, are primarily used in a service creation environment (SCE) 126 through a user interface 130 to produce the service logic programs that are then downloaded to network elements such as service management system 102, service control point 104, and/or signal transfer point 106, where they are executed.
Referring to FIG. 2, an exemplary SS7 message format is illustrated. The message 130 includes a message transfer part (MTP) 132, a signaling connection and control part (SCCP) 134 and a transaction capabilities application part (TCAP) 136.
Referring to FIG. 3, an exemplary TCAP message format is illustrated. The TCAP message 136 includes a transaction part 138, one or more component parts 140 and one or more application parts 142. Application parts 142 follow the well known intelligent network application protocol (INAP).
Referring to FIG. 4, a flowchart illustrating a method for generating billing information for a call in accordance with the present invention is shown. The method begins at step 150 and proceeds to wait state 152, where service switching point 112 waits to receive a stimulus, such as an attempt by a customer 121 to initiate a call. When such a stimulus is received, service switching point 112 sends a TCAP initial detection point (IDP) message to a service control point 104 at step 154.
Based on the IDP message, service control point 104 executes a selected service logic program. The service logic program may provide for routing of the call according to the number dialed by the customer 121. The service logic program may also provide various services for which the customer being called has subscribed.
However, before the call is routed and/or services are provided, the service logic program, in accordance with the present invention, determines that a billing record should be created for the call. The service logic program therefore causes a specially formatted TCAP message to be a sent to service switching point 112.
Referring to FIG. 5, a TCAP message 170 formatted in accordance with one aspect of the present invention is shown. TCAP message 170 includes first and second INAP application parts 172 and 180, respectively. Application part 172 is a specially formatted INAP connect message. Following standard INAP connect message format, application part 172 has a 10-digit destination routing address field 174, normally used to provide information regarding the destination of the call. In accordance with one aspect of the present invention, destination routing address field 174 does not contain a destination routing address, but rather contains a billing flag 176 and a billing information field 178.
Billing flag 176 is a unique identifier, not normally found in a destination routing address, that denotes application part 172 as a non-standard INAP connect message. For example, billing flag 176 may be a two-digit string such as "##" that does not normally occur at the beginning of a destination routing address. This flag serves to notify service switching point 112 that application part 172 contains billing information rather than the standard routing information found in an INAP connect message.
Billing information field 178 includes billing information regarding the call awaiting connection. For example, billing information field 178 may include a separate one-bit flag for every service available at service control point 104. Each flag thus denotes whether the service in question is invoked by the call awaiting connection. Examples of such services are toll-free 800-number service, premium-rate 900-number service and calling card service. Billing information field 178 may also contain a flag denoting whether the customer being called is to be billed for the services invoked by the call.
In this example, billing information field 178 may be up to 8 digits in length. Depending on the amount and format of the information included in the field, billing information field 178 may be shorter than the maximum available length.
According to one aspect of the present invention, the billing information may be preferably stored in an unused portion of a call detail record, as will be explained more fully below. Thus, the amount of unused space available in call detail record, which depends on the format used for the call detail record, may also limit the usable length of billing information field 178.
An exemplary billing information field 178 is shown in FIG. 6. Billing information field 178 is shown as a 20-bit translation of the eight numeric digits stored in billing information field 178. The information in billing information field 178 will be stored in this more useful 20-bit format within a call detail record, as will be described more fully below.
In this example, bit 1 is a customer billing flag, with a value of "1" indicating that the customer being called should be charged for the services invoked during the call. Bit 2 is a flag for Service A, which may be one of the services previously mentioned, or any other telecommunications service. Bit 2 has a value of "1," indicating that Service A is invoked for this call. Bit 3, the flag for Service B, has a value of "0," indicating the Service B is not invoked for this call.
Bits 19 and 20 contain a two-bit version code. This code indicates the meaning of the other bits in billing information field 178. In this case, "Version 01" indicates that bit 1 is the customer billing flag, bit 2 is the Service A flag, and bit 3 is the Service B flag. Other versions may correspond to other service groupings commonly employed in telecommunications network 100. For example, "Version 10" may contain a customer billing flag and flags for Services A, C, D and E. The version code may be occupy any number of bits in billing information field 178, as necessary.
Returning to FIG. 5, INAP application part 180 is a request report basic call state model event (RRB) message. This type of message may be used to request that service switching point 112 monitor the call for an event. In this example, the RRB is a request to monitor the call for a connection failure. Returning to FIG. 4, after sending TCAP message 170, the service logic program causes service control point 104 to wait for service switching point 112 to respond to the RRB request to monitor for connection failure.
Upon receiving the RRB contained in TCAP message 170, service switching system sets an internal timer and waits to see whether the call is connected. However, because service switching point 112 recognized application part 172 as a non-standard connect message that did not contain routing information, no attempt was made to connect the call. Thus, a connection failure event is detected when the internal timer expires.
At step 160, service switching point 112 sends a TCAP event report basic call state model (ERB) message to service control point 104, notifying service control point 104 that the connection failure event occurred. In response to this message, service control point 104 sends a standard TCAP connect message to service switching point 112 at step 162. Proceeding to step 164, the call is routed, connected and terminated normally. Service switching point 112 may monitor the call to gather further billing information, such as the length of the call and any additional services invoked during the call.
After the call terminates, service switching point 112 generates a call detail record reflecting the billing information for the call at step 166. Alternatively, the call detail record may be generated when the billing information is first received at service switching point 112. The call detail record may then be updated as necessary during the call or after the call is completed.
The billing information is preferably included in a previously unused portion of the call detail record, so that no change to the call detail record format is required. The call detail record is sent to billing system 124 for further processing and/or storage in mass storage system 125. For example, billing system 124 may periodically generate a bill for each customer reflecting the billing information contained in the call detail records stored in mass storage system 125. This ends the method illustrated in FIG. 4.
It will be appreciated that this above-described method for generating and storing billing information uses standard SS7 signaling, message protocols and call detail record formats. Thus, the changes that must be made to a telecommunications network to enable this billing method are minimal. The service logic programs at service control points 104 are modified to generate the specially formatted TCAP connect message before generating the standard TCAP connect message. Service switching point 112 is modified to recognize the specially formatted TCAP connect message and respond accordingly. No further modification to telecommunications network 100 is necessary. Thus, any proprietary switch may implement the above-described billing functions at service switching point 112 with only minor modifications.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5008929 *Jan 18, 1990Apr 16, 1991U.S. Intelco Networks, Inc.Billing system for telephone signaling networkUS5163087 *Dec 31, 1990Nov 10, 1992At&T Bell LaboratoriesDelivery of customer data base key using automatic number identificationUS5313463 *Mar 25, 1993May 17, 1994At&T Bell LaboratoriesISDN credit checkingUS5640446 *May 1, 1995Jun 17, 1997Mci CorporationSystem and method of validating special service calls having different signaling protocolsJPH0345068A * Title not availableWO1996031973A1 *Apr 4, 1996Oct 10, 1996Bell Communications Research, Inc.A system and method for providing portable telephone number serviceWO1997023100A2 *Dec 20, 1996Jun 26, 1997Ericsson Inc.Transport mechanism for accounting messages within a telecommunications system* Cited by examinerNon-Patent CitationsReference1Abdi R. Modarressi, et al., "An Overview of Signaling System No. 7", Proceedings of the IEEE, vol. 80, No. 4, Apr. 1, 1992, pp. 590-606.2 *Abdi R. Modarressi, et al., An Overview of Signaling System No. 7 , Proceedings of the IEEE, vol. 80, No. 4, Apr. 1, 1992, pp. 590 606.3 *Patent Abstracts of Japan, vol. 015, No. 185 (E 1066), May 13, 1991 & JP 03 045068 A (NEC Corp), Feb. 26, 1991.4Patent Abstracts of Japan, vol. 015, No. 185 (E-1066), May 13, 1991 & JP 03 045068 A (NEC Corp), Feb. 26, 1991.* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6185285 *Oct 14, 1997Feb 6, 2001At&T Corp.Method for providing network users with improved management of a communications service featureUS6249572 *Jun 8, 1998Jun 19, 2001Inet Technologies, Inc.Transaction control application part (TCAP) call detail record generation in a communications networkUS6327352 *Feb 24, 1997Dec 4, 2001Ameritech CorporationSystem and method for real-time fraud detection within a telecommunications systemUS6359976Sep 14, 1999Mar 19, 2002Inet Technologies, Inc.System and method for monitoring service quality in a communications networkUS6381306Jun 8, 1998Apr 30, 2002Inet Technologies, Inc.System and method for monitoring service quality in a communications networkUS6411604Jun 5, 1998Jun 25, 2002Inet Technologies, Inc.System and method for correlating transaction messages in a communications networkUS6453158 *Oct 26, 1999Sep 17, 2002Mci Communications CorporationWireless prepaid platform integration with standard signalingUS6459779 *Sep 4, 1998Oct 1, 2002Ameritech CorporationSystem and method for creating a billing record with a called party's nameUS6529594Jun 5, 1998Mar 4, 2003Inet Technologies, Inc.System and method for generating quality of service statistics for an international communications networkUS6567511 *Sep 6, 2001May 20, 2003Ameritech CorporationSystem and method for real-time fraud detection within a telecommunications systemUS6614894Jun 5, 1998Sep 2, 2003Inet Technologies, Inc.System and method for mass call onset detection in a communications networkUS6636589Jun 5, 2001Oct 21, 2003Telefonaktiebolaget Lm Ericsson (Publ)Cascade accounting of connection-oriented communication sessions in a telecommunication systemUS6741927May 12, 2003May 25, 2004Arrivalstar, Inc.User-definable communications methods and systemsUS6748318May 6, 1997Jun 8, 2004Arrivalstar, Inc.Advanced notification systems and methods utilizing a computer networkUS6748320Dec 20, 2002Jun 8, 2004Arrivalstar, Inc.Advance notification systems and methods utilizing a computer networkUS6763299May 12, 2003Jul 13, 2004Arrivalstar, Inc.Notification systems and methods with notifications based upon prior stop locationsUS6763300May 12, 2003Jul 13, 2004Arrivalstar, Inc.Notification systems and methods with purpose message in notificationsUS6804606May 12, 2003Oct 12, 2004Arrivalstar, Inc.Notification systems and methods with user-definable notifications based upon vehicle proximitiesUS6868147Aug 15, 2002Mar 15, 2005Sbc Properties, L.P.System and method for creating a billing record with a called party's nameUS6954631Feb 13, 2003Oct 11, 2005Hewlett-Packard Development Company, L.P.Apparatus and method for telecommunications servicesUS6980791May 22, 2002Dec 27, 2005Nokia CorporationCharging control of telecommunication network subscriberUS7058166Mar 26, 2003Jun 6, 2006Sbc Properties, L.P.System and method for real-time fraud detection within a telecommunications systemUS7069446Apr 17, 2001Jun 27, 2006Mci, LlcStateless mechanism for data retrievalUS7072953 *Feb 8, 2000Jul 4, 2006Siemens AktiengesellschaftMethod for setting up and/or processing a service of an intelligent networkUS7127617Apr 17, 2001Oct 24, 2006Mci, LlcOn-line directory assistance systemUS7136467Jan 4, 2002Nov 14, 2006Symphony Service CorpCustomer-oriented telecommunications data aggregation and analysis method and object oriented systemUS7149292Jun 29, 2004Dec 12, 2006Sbc Holdings Properties, L.P.System and method for creating a billing record with a called party's nameUS7248681 *May 31, 2006Jul 24, 2007Sbc Properties, L.P.System and method for real-time fraud detection within a telecommunication networkUS7275162Feb 22, 2006Sep 25, 2007Verizon Business Global LlcOn-line directory assistance systemUS7304984Feb 9, 2001Dec 4, 2007Convergent Networks, Inc.Methods and systems for creating, distributing and executing multimedia telecommunications applications over circuit and packet switched networksUS7406161Jun 11, 2007Jul 29, 2008Sbc Properties, L.P.System and method for real-time fraud detection within a telecommunication networkUS7508926Oct 19, 2006Mar 24, 2009At&T Intellectual Property 1, L.P.Method and system for creating a billing record with a called party's nameUS7546113Mar 1, 2001Jun 9, 2009Telefonaktiebolaget L M Ericsson (Publ)Transmission of call detail records in a telecommunications systemUS7570751Jun 23, 2008Aug 4, 2009At&T Intellectual Property I, L.P.System and method for real-time fraud detection within a telecommunication networkUS7640166Apr 17, 2001Dec 29, 2009Verizon Business Global LlcMethod for charging on-line directory assistance servicesUS7668534Jul 5, 2005Feb 23, 2010Agilent Technologies, Inc.Method and system for transportation of derived call records to a central repositoryUS7876239Jan 25, 2011Horstemeyer Scott ASecure notification messaging systems and methods using authentication indiciaUS7924992 *Apr 12, 2011Huawei Technologies Co., Ltd.Method of ensuring call processing for intelligent userUS7934206Feb 9, 2001Apr 26, 2011Convergent Networks, Inc.Service level executable environment for integrated PSTN and IP networks and call processing language thereforUS8068037Nov 29, 2011Eclipse Ip, LlcAdvertisement systems and methods for notification systemsUS8232899Jul 31, 2012Eclipse Ip, LlcNotification systems and methods enabling selection of arrival or departure times of tracked mobile things in relation to locationsUS8242935Aug 14, 2012Eclipse Ip, LlcNotification systems and methods where a notified PCD causes implementation of a task(s) based upon failure to receive a notificationUS8284076May 23, 2012Oct 9, 2012Eclipse Ip, LlcSystems and methods for a notification system that enable user changes to quantity of goods and/or services for delivery and/or pickupUS8362927Jan 29, 2013Eclipse Ip, LlcAdvertisement systems and methods for notification systemsUS8368562May 23, 2012Feb 5, 2013Eclipse Ip, LlcSystems and methods for a notification system that enable user changes to stop location for delivery and/or pickup of good and/or serviceUS8531317Jan 2, 2013Sep 10, 2013Eclipse Ip, LlcNotification systems and methods enabling selection of arrival or departure times of tracked mobile things in relation to locationsUS8564459Jan 2, 2013Oct 22, 2013Eclipse Ip, LlcSystems and methods for a notification system that enable user changes to purchase order information for delivery and/or pickup of goods and/or servicesUS8711010Jan 2, 2013Apr 29, 2014Eclipse Ip, LlcNotification systems and methods that consider traffic flow predicament dataUS8712450 *Aug 27, 2007Apr 29, 2014International Business Machines CorporationSystem and method of creating and providing SMS http taggingUS9013334Mar 5, 2014Apr 21, 2015Eclipse, LLCNotification systems and methods that permit change of quantity for delivery and/or pickup of goods and/or servicesUS9019130Mar 5, 2014Apr 28, 2015Eclipse Ip, LlcNotification systems and methods that permit change of time information for delivery and/or pickup of goods and/or servicesUS9253612Mar 25, 2014Feb 2, 2016International Business Machines CorporationSystem and method of creating and providing SMS http taggingUS9373261Mar 2, 2015Jun 21, 2016Electronic Communication Technologies LlcSecure notification messaging with user option to communicate with delivery or pickup representativeUS20020007455 *Apr 17, 2001Jan 17, 2002Wiederin Shawn E.Stateless mechanism for data retrievalUS20020026579 *Apr 17, 2001Feb 28, 2002Wiederin Shawn E.On-line directory assistance systemUS20020183041 *May 22, 2002Dec 5, 2002Jukka WalleniusCharging control of telecommunication network subscriberUS20030012183 *Feb 9, 2001Jan 16, 2003David ButlerMethods and systems for creating, distributing and executing multimedia telecommunications applications over circuit and packet switched networksUS20030098802 *Nov 20, 2002May 29, 2003Jones Martin KellyBase station apparatus and method for monitoring travel of a mobile vehicleUS20030228008 *Mar 26, 2003Dec 11, 2003Betts Judy LynnSystem and method for real-time fraud detection within a telecommunications systemUS20030233188 *May 12, 2003Dec 18, 2003Jones M. KellyNotification systems and methods with user-definable notifications based upon occurance of eventsUS20030233190 *May 12, 2003Dec 18, 2003Jones M. KellyNotification systems and methods with user-definable notifications based upon vehicle proximitiesUS20040044467 *Sep 5, 2003Mar 4, 2004David LairdNotification systems and methods enabling user entry of notification trigger information based upon monitored mobile vehicle locationUS20040162054 *Feb 13, 2003Aug 19, 2004Christophe ThiebotApparatus and method for telecommunications servicesUS20040254985 *Nov 12, 2003Dec 16, 2004Horstemeyer Scott A.Response systems and methods for notification systems for modifying future notificationsUS20040255297 *Jun 2, 2004Dec 16, 2004Horstemeyer Scott A.Secure notification messaging systems and methods using authentication indiciaUS20050013422 *Jun 29, 2004Jan 20, 2005Wardin William KonradSystem and method for creating a billing record with a called party's nameUS20060026047 *Sep 27, 2005Feb 2, 2006Jones Martin KPackage delivery notification system and methodUS20060156037 *Feb 22, 2006Jul 13, 2006Wiederin Shawn EOn-line directory assistance systemUS20060206257 *May 9, 2006Sep 14, 2006Jones Martin KSystem and method for an advance notification system for monitoring and reporting proximity of a vehicleUS20060233337 *May 31, 2006Oct 19, 2006Sbc Properties, L.P.System and method for real-time fraud detection within a telecommunication networkUS20060290533 *Aug 29, 2006Dec 28, 2006Horstemeyer Scott AResponse systems and methods for notification systems for modifying future notificationsUS20070010239 *Jul 5, 2005Jan 11, 2007Connelly Stephen PMethod and system for transportation of derived call records to a central repositoryUS20070030175 *Sep 13, 2006Feb 8, 2007Horstemeyer Scott ANotification systems and methods that consider traffic flow predicament dataUS20070127648 *Oct 19, 2006Jun 7, 2007Wardin William KMethod and system for creating a billing record with a called party's nameUS20070242818 *Jun 11, 2007Oct 18, 2007Sbc Properties, L.P.System and method for real-time fraud detection within a telecommunication networkUS20080042882 *Oct 26, 2007Feb 21, 2008Horstemeyer Scott AMobile thing determination systems and methods based upon user-device locationUS20080043979 *Oct 4, 2007Feb 21, 2008Huawei Technologies Co., Ltd.Method of ensuring call processing for intelligent userUS20080046326 *Oct 26, 2007Feb 21, 2008Horstemeyer Scott AMobile thing determination systems and methods based upon user-device locationUS20080100475 *Oct 29, 2007May 1, 2008Horstemeyer Scott AResponse systems and methods for notification systems for modifying future notificationsUS20080267375 *Jun 23, 2008Oct 30, 2008Ameritech CorporationSystem and method for real-time fraud detection within a telecommunication networkUS20090061909 *Aug 27, 2007Mar 5, 2009International Business Machines CorporationSystem and method of creating and providing sms http taggingUS20110194556 *Aug 11, 2011David ButlerService Level Executable Environment for Integrated PSTN and IP Networks and Call Processing Language ThereforEP1168805A1 *Jun 20, 2000Jan 2, 2002Alcatel Alsthom Compagnie Generale D'electriciteCall charging method, a related device, object and object-oriented development systemWO2001079968A2 *Apr 17, 2001Oct 25, 2001Clabaugh Lonnie SStateless mechanism for data retrievalWO2001079968A3 *Apr 17, 2001Feb 21, 2002Jonathan AbelStateless mechanism for data retrieval* Cited by examinerClassifications U.S. Classification379/114.29, 379/127.01, 379/91.02, 379/116, 379/230, 379/119International ClassificationH04Q3/00, H04M15/00Cooperative ClassificationH04Q3/0029, H04M2215/016, H04M15/90, H04M15/00European ClassificationH04M15/90, H04Q3/00D3, H04M15/00Legal EventsDateCodeEventDescriptionApr 27, 1998ASAssignmentOwner name: DSC TELECOM L.P., TEXASFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WHITED, JOHN L.;LE, HUNG V.;LEE, CHARLES C. JR.;REEL/FRAME:009193/0028;SIGNING DATES FROM 19980224 TO 19980226Nov 27, 1998ASAssignmentOwner name: ALCATEL USA SOURCING, L.P., TEXASFree format text: CHANGE OF NAME;ASSIGNOR:DSC TELECOM L.P.;REEL/FRAME:009596/0527Effective date: 19980909Nov 21, 2002FPAYFee paymentYear of fee payment: 4Dec 8, 2006FPAYFee paymentYear of fee payment: 8Dec 8, 2010FPAYFee paymentYear of fee payment: 12Mar 7, 2013ASAssignmentFree format text: SECURITY INTEREST;ASSIGNOR:ALCATEL-LUCENT USA INC.;REEL/FRAME:030510/0627Effective date: 20130130Owner name: CREDIT SUISSE AG, NEW YORKOct 9, 2014ASAssignmentOwner name: ALCATEL-LUCENT USA INC., NEW JERSEYFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033949/0531Effective date: 20140819RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services