US6097939A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method and apparatus for event data maintenance per MIN/ESN pair in a mobile telephone system
Assignee: Hewlett Packard Enterprise Development LP
•
Filing: 1997-07-11
•
Granted: 2000-08-01
•
Expires: 2017-07-11
Abstract
Abstract A method and apparatus for allowing an Authentication Center (AC) in a cellular telephone system to store and access event a predefined number of maintenance data events on a per-MIN/ESN basis.
Inventors
- 👤 Pamela J. Jacobs
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-08 11:13
CPC Classifications
H; H04; H04Q; H04Q3/00; H04Q3/0016; H04Q3/0029; H04Q3/0045; H04Q3/0025
Claims Analysis
Total Claims: 11
Claim 1
Independent Claim
114 words
A method for storing event data in a wireless communication system, where a first Transaction Capabilities Application Part (TCAP) message has been processed and corresponding event data has been stored in a subrecord of a subscriber database, comprising the steps performed by an Authentication Center (AC), of: processing a second TCAP message for a Mobile Identification Number/Electronic Serial Number (MIN/ESN) pair; extracting a key from the second TCAP message, the key identifying the MIN/ESN pair; and storing event data of the TCAP message as a second subrecord of the subscriber database corresponding to the key, so that event data of multiple TCAP messages is stored in the subscriber database on a per MIN/ESN basis.
Claim 2
Independent Claim
114 words
A method for storing event data in a wireless communication system, where a first Transaction Capabilities Application Part (TCAP) message has been processed and corresponding event data has been stored in a subrecord of a subscriber database, comprising the steps performed by an Authentication Center (AC), of: processing a second TCAP message for a Mobile Identification Number/Electronic Serial Number (MIN/ESN) pair; extracting a key from the second TCAP message, the key identifying the MIN/ESN pair; and storing event data of the TCAP message as a second subrecord of the subscriber database corresponding to the key, so that event data of multiple TCAP messages is stored in the subscriber database on a per MIN/ESN basis.
Claim 3
Dependent Claim
43 words
The method of claim 1, further including the step, performed by the AC, of: processing a response to the second TCAP message; and storing the response to the second TCAP message in the second subrecord of the subscriber database corresponding to the key.
Claim 4
Independent Claim
117 words
An apparatus that stores event data in a wireless communication system, where a first Transaction Capabilities Application Part (TCAP) message has been processed and corresponding event data has been stored in a subrecord of a subscriber database comprising: a portion for processing a second TCAP message for a Mobile Identification Number/Electronic Serial Number (MIN/ESN) pair; a portion configured for extracting a key from the second TCAP message, the key for identifying the MIN/ESN pair; and a portion configured for storing event data of the TCAP message as a second subrecord of the subscriber database corresponding to the key, so that event data of multiple TCAP messages is stored in the subscriber database on a per MIN/ESN basis.
Claim 5
Independent Claim
117 words
An apparatus that stores event data in a wireless communication system, where a first Transaction Capabilities Application Part (TCAP) message has been processed and corresponding event data has been stored in a subrecord of a subscriber database comprising: a portion for processing a second TCAP message for a Mobile Identification Number/Electronic Serial Number (MIN/ESN) pair; a portion configured for extracting a key from the second TCAP message, the key for identifying the MIN/ESN pair; and a portion configured for storing event data of the TCAP message as a second subrecord of the subscriber database corresponding to the key, so that event data of multiple TCAP messages is stored in the subscriber database on a per MIN/ESN basis.
Claim 6
Dependent Claim
44 words
The apparatus of claim 3, further comprising: a portion configured for processing a response to the second TCAP message; and a portion configured for storing the response to the second TCAP message in the second subrecord of the subscriber database corresponding to the key.
Claim 7
Dependent Claim
115 words
A computer-readable medium having stored thereon instructions which, when executed by a processor and where a first Transaction Capabilities Application Part (TCAP) message has been processed and corresponding event data has been stored in a subrecord of a subscriber database, cause the processor to perform the steps of: processing a second TCAP message for a Mobile Identification Number/Electronic Serial Number (MIN/ESN) pair; extracting a key from the second TCAP message, the key identifying the MIN/ESN pair; and storing event data of the TCAP message as a second subrecord of the subscriber database corresponding to the key, so that event data of multiple TCAP messages is stored in the subscriber database on a per MIN/ESN basis.
Claim 8
Dependent Claim
115 words
A computer-readable medium having stored thereon instructions which, when executed by a processor and where a first Transaction Capabilities Application Part (TCAP) message has been processed and corresponding event data has been stored in a subrecord of a subscriber database, cause the processor to perform the steps of: processing a second TCAP message for a Mobile Identification Number/Electronic Serial Number (MIN/ESN) pair; extracting a key from the second TCAP message, the key identifying the MIN/ESN pair; and storing event data of the TCAP message as a second subrecord of the subscriber database corresponding to the key, so that event data of multiple TCAP messages is stored in the subscriber database on a per MIN/ESN basis.
Claim 9
Dependent Claim
40 words
The computer-readable medium of claim 5, further including the steps of: processing a response to the second TCAP message; and storing the response to the second TCAP message in the second subrecord of the subscriber database corresponding to the key.
Claim 10
Independent Claim
171 words
A method for storing event data in a wireless communication system, comprising the steps performed by a data processing system, of: processing an event data transaction; extracting a key from the event data transaction to a subscriber database, the key for storing and retrieving event data on a per key basis; storing at least a part of the event data transaction as a subrecord of a subscriber database corresponding to the key wherein a subrecord for MIN/ESN pair in the subscriber database includes the following information: an MSCID of a TCAP Originator; a PCSSN of TCAP Originator; an invoke Timestamp; an Opcode of the Transaction; an MS COUNT/Call History Count; an Invoke Status Flag; an SSD shared Flag; an SSD Discarded Flag; an SSD Update Flag; an SSD Update Result Flag; a Unique Challenge Sent Flag; Unique Challenge Result Flag; an Access Denied flag; an Error Returned Flag; and storing at least a portion of a response of the transaction in a subrecord of the subscriber database corresponding to the key.
Claim 11
Independent Claim
171 words
A method for storing event data in a wireless communication system, comprising the steps performed by a data processing system, of: processing an event data transaction; extracting a key from the event data transaction to a subscriber database, the key for storing and retrieving event data on a per key basis; storing at least a part of the event data transaction as a subrecord of a subscriber database corresponding to the key wherein a subrecord for MIN/ESN pair in the subscriber database includes the following information: an MSCID of a TCAP Originator; a PCSSN of TCAP Originator; an invoke Timestamp; an Opcode of the Transaction; an MS COUNT/Call History Count; an Invoke Status Flag; an SSD shared Flag; an SSD Discarded Flag; an SSD Update Flag; an SSD Update Result Flag; a Unique Challenge Sent Flag; Unique Challenge Result Flag; an Access Denied flag; an Error Returned Flag; and storing at least a portion of a response of the transaction in a subrecord of the subscriber database corresponding to the key.
References Cited (Backward Citations)
US5128984A
Cited
US5014298A
Cited
US5048075A
Cited
US5553120A
Cited
US4930150A
Cited
US4799061A
Cited
US5282250A
Cited
US5153902A
Cited
US5091942A
Cited
US5077790A
Cited
US5243645A
Cited
US5210787A
Cited
US5237612A
Cited
US5448622A
Cited
US5204902A
Cited
US5309501A
Cited
WO1993011646A1
Cited
US5406619A
Cited
WO1993021715A1
Cited
US5329578A
Cited
US5418835A
Cited
US5551073A
Cited
US5754952A
Cited
US5448760A
Cited
WO1994029992A1
Cited
US5455863A
Cited
US5642401A
Cited
US5594740A
Cited
US5371781A
Cited
US5603081A
Cited
US5504804A
Cited
US5533107A
Cited
US5530736A
Cited
US5668875A
Cited
US5794139A
Cited
US5513245A
Cited
US5600704A
Cited
US5673308A
Cited
US5768358A
Cited
EP0738095A2
Cited
US5793859A
Cited
US5590175A
Cited
US5708710A
Cited
US5719918A
Cited
US5615267A
Cited
US5724417A
Cited
US5754955A
Cited
US5737701A
Cited
US5878126A
Cited
US5937068A
Cited
US5761500A
Cited
US5822691A
Cited
US5943425A
Cited
WO1998005173A2
Cited
US6026293A
Cited
US5887251A
Cited
US5875394A
Cited
US5974252A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-08-01 | 2004-01-31 | 2004-08-01 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-08-01 | 2008-01-31 | 2008-08-01 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-08-01 | 2012-01-31 | 2012-08-01 | $7700.00 | Window Closed / Lapsed |