IP Library Granted Patent US 7,366,287
Granted Patent B2
US 7,366,287 · App. 10/669,438 · Granted Apr 29, 2008

DTMF lockout utility epoch time stamp

Assignee: AT&T Knowledge Ventures, L.P.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,366,287
App. No.
10/669,438
Granted
Apr 29, 2008
Kind
B2
Abstract

A current time and a current Gregorian date are converted into an epoch time stamp. A number of seconds that have elapsed since a predetermined date up until the current year is determined. A number of seconds that have elapsed since the beginning of the current year up until the current month is determined based on whether the current year is a leap year. In addition, a number of seconds that have elapsed since the beginning of the current month up until the current day is calculated, as is a number of seconds that have elapsed during the current day. All of these values are summed to obtain a converted time. Finally, it is determined whether Daylight Savings Time is in effect, and when Daylight Savings Time is not in effect, 3600 seconds are added to the converted time.

Claims (80)

1. A method for converting a current time and a Gregorian date comprising a current year, a current month, and a current day into an epoch time stamp, comprising:

receiving the current time and the Gregorian date;

determining a number of seconds that have elapsed since a predetermined date up until, but not including, the current year;

determining whether the current year is a leap year;

determining a number of seconds that have elapsed since the beginning of the current year up until, but not including, the current month, based on whether the current year is a leap year;

calculating a number of seconds that have elapsed since the beginning of the current month up until, but not including, the current day;

calculating a number of seconds that have elapsed during the current day;

summing the determined number of seconds since the predetermined date, the determined number of seconds since the beginning of the current year, the calculated number of seconds since the beginning of the current month, and the calculated number of seconds during the current day to obtain a converted time;

determining whether Daylight Savings Time is in effect; and

when Daylight Savings Time is not in effect, adding 3600 seconds to the converted time;

wherein the converted time is the epoch time stamp, which comprises the number of elapsed seconds since the predetermined time.

2. The method of claim 1 , in which the determining a number of seconds that have elapsed since a predetermined date up until, but not including, the current year further comprises looking up the number of seconds in a table.

3. The method of claim 1 , in which the determining whether the current year is a leap year further comprises comparing the current year with a table of leap years.

4. The method of claim 1 , in which the determining a number of seconds that have elapsed since the beginning of the current year further comprises looking up the number of seconds in a table.

5. The method of claim 4 , in which the table comprises a column for leap year values, and a column for non-leap year values.

6. The method of claim 1 , in which determining whether Daylight Savings Time is in effect further comprises:

storing a current system time including a current system time zone;

changing the current system time zone to a current system time zone non-observing of Daylight Savings Time;

obtaining a new system time using the current system time zone non-observing of Daylight Savings Time;

comparing the new system time with the stored system time; and

when the new system time differs from the stored system time, deciding that Daylight Savings Time is in effect.

7. A computer readable medium storing a program for converting a current time and a Gregorian date comprising a current year, a current month, and a current day into an epoch time stamp, comprising:

a receiving source code segment that receives the current time and the Gregorian date;

a first determining source code segment that determines a number of seconds that have elapsed since a predetermined date up until, but not including, the current year;

a leap year determining source code segment that determines whether the current year is a leap year;

a second determining source code segment that determines a number of seconds that have elapsed since the beginning of the current year up until, but not including, the current month, based on whether the current year is a leap year;

a month calculating source code segment that calculates a number of seconds that have elapsed since the beginning of the current month up until, but not including, the current day;

a day calculating source code segment that calculates a number of seconds that have elapsed during the current day;

a summing source code segment that sums the determined number of seconds since the predetermined date, the determined number of seconds since the beginning of the current year, the calculated number of seconds since the beginning of the current month, and the calculated number of seconds during the current day to obtain a converted time;

a Daylight Savings Time determining source code segment that determines whether Daylight Savings Time is in effect; and

an adding source code segment that, when Daylight Savings Time is not in effect, adds 3600 seconds to the converted time;

wherein the converted time is the epoch time stamp, which comprises the number of elapsed seconds since the predetermined time.

8. The medium of claim 7 , in which the first determining source code segment further comprises a lookup source code segment that looks up the number of seconds in a table.

9. The medium of claim 7 , in which the leap year determining source code segment further comprises a leap year comparing source code segment that compares the current year with a table of leap years.

10. The medium of claim 7 , in which the second determining source code segment further comprises a lookup source code segment that looks up the number of seconds in a table.

11. The medium of claim 10 , in which the table comprises a column for leap year values, and a column for non-leap year values.

12. The medium of claim 7 , in which the Daylight Savings Time determining source code segment further comprises:

a storing source code segment that stores a current system time including a current system time zone;

a time zone source code segment that changes the current system time zone to a current system time zone non-observing of Daylight Savings Time;

a new time source code segment that obtains a new system time using the current system time zone non-observing of Daylight Savings Time;

a comparing source code segment that compares the new system time with the stored system time; and

a decision source code segment that, when the new system time differs from the stored system time, decides that Daylight Savings Time is in effect.

13. A method for determining customer data availability, comprising:

receiving a time stamp of a most recent update, the time stamp comprising a number of elapsed seconds since a predetermined date and a predetermined time;

determining whether the customer data is in use;

receiving a maximum duration of a lockout period; and

analyzing the maximum duration of the lockout period, the time stamp, and whether the customer data is in use to determine whether the customer data is available.

14. The method of claim 13 , in which the analyzing further comprises:

determining whether the sum of the time stamp and the maximum duration of the lockout period is greater than a current time;

when the sum is greater than the current time, deciding that the customer data is not available; and

when the sum is less than or equal to the current time, deciding that the customer data is available.

15. The method of claim 14 , in which the deciding that the customer data is available further comprises replacing the time stamp with a current time stamp and indicating that the customer data is in use.

16. The method of claim 13 , in which the time stamp is derived by receiving a current time and a Gregorian date which comprises a current day, a current month, an a current year;

determining a number of seconds that have elapsed since the predetermined date up until, but not including, the current year;

determining whether the current year is a leap year;

determining a number of seconds that have elapsed since the beginning of the current year up until, but not including, the current month, based on whether the current year is a leap year;

calculating a number of seconds that have elapsed since the beginning of the current month up until, but not including, the current day;

calculating a number of seconds that have elapsed during the current day;

summing the determined number of seconds since the predetermined date, the determined number of seconds since the beginning of the current year, the calculated number of seconds since the beginning of the current month, and the calculated number of seconds during the current day to obtain a converted time;

determining whether Daylight Savings Time is in effect; and

when Daylight Savings Time is not in effect, adding 3600 seconds to the converted time.

17. A computer readable medium storing a program for determining customer data availability, comprising:

a time stamp receiving source code segment that receives a time stamp of a most recent update, the time stamp comprising a number of elapsed seconds since a predetermined date and a predetermined time;

an in use source code segment that determines whether the customer data is in use;

a duration receiving source code segment that receives a maximum duration of a lockout period; and

an analyzing source code segment that analyzes the maximum duration of the lockout period, the time stamp, and whether the customer data is in use to determine whether the customer data is available.

18. The medium of claim 17 , in which the analyzing source code segment further comprises:

a comparison determining source code segment that determines whether a sum of the time stamp and the maximum duration of the lockout period is greater than a current time;

a negative deciding source code segment that, when the sum is greater than the current time, decides that the customer data is not available; and

a positive deciding source code segment that, when the sum is less than or equal to the current time, deciding that the customer data is available.

19. The medium of claim 18 , in which the positive deciding source code segment further comprises a replacement source code segment that replaces the time stamp with a current time stamp and indicates that the customer data is in use.

20. The medium of claim 17 , further comprising a time stamp calculating source code segment that derives the time stamp by receiving a current time and a Gregorian date which comprises a current day, a current month, an a current year;

determining a number of seconds that have elapsed since the predetermined date up until, but not including, the current year;

determining whether the current year is a leap year;

determining a number of seconds that have elapsed since the beginning of the current year up until, but not including, the current month, based on whether the current year is a leap year;

calculating a number of seconds that have elapsed since the beginning of the current month up until, but not including, the current day;

calculating a number of seconds that have elapsed during the current day;

summing the determined number of seconds since the predetermined date, the determined number of seconds since the beginning of the current year, the calculated number of seconds since the beginning of the current month, and the calculated number of seconds during the current day to obtain a converted time;

determining whether Daylight Savings Time is in effect; and

when Daylight Savings Time is not in effect, adding 3600 seconds to the converted time.

Assignments (4)
CORRECTIVE ASSIGNMENT TO CORRECT THE EXECUTION DATE PREVIOUSLY RECORDED ON REEL 020408 FRAME 0975. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME. Recorded Apr 20, 2020
From: SBC KNOWLEDGE VENTURES, L.P.
To: AT&T KNOWLEDGE VENTURES, L.P.
Reel/Frame 052448/0044 →
CHANGE OF NAME Recorded Apr 20, 2020
From: AT&T KNOWLEDGE VENTURES, L.P.
To: AT&T INTELLECTUAL PROPERTY I, L.P.
Reel/Frame 052448/0096 →
CHANGE OF NAME Recorded Jan 24, 2008
From: SBC KNOWLEDGE VENTURES, L.P.
To: AT&T KNOWLEDGE VENTURES, L.P.
Reel/Frame 020408/0975 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 5, 2004
From: STROUD, KENNETH ROBERT; BRANDT, JEFFREY LEWIS; CHERYE, RICK ANTHONY
To: SBC KNOWLEDGE VENTURES, L.P.
Reel/Frame 014954/0371 →
Continuity (1)
Related Publication 20050071396A1 · Mar 31, 2005