Telecommunications – Transmitter and receiver at same station – Radiotelephone equipment detail
Reexamination Certificate
1999-10-05
2003-03-18
Maung, Nay (Department: 2681)
Telecommunications
Transmitter and receiver at same station
Radiotelephone equipment detail
C455S415000
Reexamination Certificate
active
06535751
ABSTRACT:
TECHNICAL FIELD
This invention relates to wireless telephone, and has particular relation to automatically determining the proper origination scheme for a call being placed from a wireless telephone.
BACKGROUND ART
In a landline telephone system, a telephone call is a telephone call. If the call goes through, it goes through. If it doesn't, the user calls again later.
Moreover, the network or service provider of a landline phone makes no attempt to optimize the system to further increase the probability that a call origination will go through.
Some devices have automatic redial. If a sending fax machine calls a receiving fax machine, and the receiving fax machine is busy, the sending fax machine tries again, at progressively longer intervals, until the call goes through or a predetermined maximum number of attempts is reached. A home computer attempting to reach an Internet Service Provider will make similarly repeated attempts if it does not get through the first time. Further flexibility is not possible in a landline telephone system. A telephone call is a telephone call.
BRIEF DISCLOSURE OF THE INVENTION
Applicant has noted that, in a wireless telephone system, not all telephone calls are the same, and not all networks are the same. For example, some networks have Code Division Multiple Access (“CDMA”) and Advanced Mobile Phone System (“AMPS”) systems capabilities while other networks have only CDMA systems. In addition, a network might be more or less likely to return a specific call origination failure indications, such as a REORDER or INTERCEPT, in comparison to a different network. Furthermore, distinct networks will usually also vary in the origination failure indication time period, that is, the time period from the call origination start time to when the mobile receives an origination failure indication from the network.
Another variable that has to be accounted for is the call type. For example, while a regular call might be silently re-dialed a maximum of 4 times within 30 seconds, an emergency 911 call needs to be re-dialed endlessly until call is successfully connected (or battery is empty).
In order to optimize the origination schemes of different call types, a call plan is associated with each such call type. A call type is simply a subset of dial-strings that are grouped together and associated with a particular predefined call type. Example of predefined call types are voice, Emergency, Data, Fax, Packet, OTASP (Over The Air Service Provisioning), Test (Markov, Loopback), and SMS (Short Message Service).
With each such call type there is associated a set of dial strings. For example, the dial-string subset {“911”, “*911”, “#911”} might be associated with the emergency call type. In other words, any dial string that is within this set will be considered of type “emergency” while dial strings that are not within this set are not considered of type “emergency”.
Different wireless service providers are available to the user of a wireless telephone. These providers offer different services, with different prices, to the wireless telephone user, and these services and prices depend on the telephone number being called. The user of a wireless telephone can thus customize a call origination scheme based on the telephone number (or at least the type of telephone number) being called. A “call origination scheme” is a decision as to how many times to attempt to redial, which service provider to use, which (Code Division Multiple Access vs. Frequency Division Multiple Access, for example) of service to use, etc.
Table 1 shows a preferred Origination Plan Table. As shown in Table 1, each entry of the call origination plan table associates a call-type and/or a dial-string with a call origination plan. The call-origination plan holds all the information that is necessary to conduct the origination process for the associated call-type and/or dial-string.
Table 2 is an explanation of the fields shown in Table 1.
Table 3 is an Origination Plan Table Example. Note that the table is being searched from top to bottom. In the case where a particular call-type/dial-string can be matched against more than one table entry, the first entry from the top will dictate the origination plan.
The origination plan can be specified using a table or a set of tables, as illustrated below. In such a table, each entry specifies the origination plan variables that are associated with a particular call type. Alternatively, the origination plan variables can replaced with a script (see FIG.
3
).
TABLE 1
Origination Plan Table
Match
fields
Origination Plan
call_type
mc_ho
pwr_ho
sr_prd_t
sr_max_d
sr_max_t
no_srv
fade
reorder
intercept
release
TABLE 2
Explanation of Fields
Field
Explanation
Match fields
call_type
Indicate the call type corresponding to this
origination plan entry.
Origination
mc_ho
Indication whether we should honor
Plan Fields
hold-origination indication from the
call-processing task during the origination
process.
pwr_ho
The max time we should hold the origination
during power-up, giving service a chance to
appear before starting the call origination
process.
sr_prd_t
The time we should wait after a dial (redial)
attempt failure before we try the next silent
redial attempt.
sr_max_d
The max numbers of dial (redial) attempts,
after which we declare call-origination
failure.
sr_max_t
The max time for silently redialing, after
which we declare call-origination failure.
no_srv
Action to take when dial (redial) attempt
fails due to no-service indication from the
network.
fade
Action to take when dial (redial) attempt
fails due to fade indication from the network.
reorder
Action to take when dial (redial) attempt
fails due to reorder indication from the
network.
intercept
Action to take when dial (redial) attempt
fails due to intercept indication from the
network.
release
Action to take when dial (redial) attempt
fails due to release indication from the
network.
TABLE 3
Origination Plan Example Table
Match fields
Origination Plan
call_type
mc_ho
pwr_ho
sr_prd_t
sr_max_d
sr_max_t
no_srv
fade
reorder
intercept
release
E911
Yes
12 s
4 s
10,000
10,000 s
Redial
Redial
Redial
Redial
Redial
Std-OTASP
No
0 s
0 s
0
10,000 s
None
End-orig
End-orig
End-orig
End-orig
Non-std-OTASP
Yes
12 s
4 s
4
30
Force to
Force to
Force to
End-orig
End-orig
AMPS
AMPS
AMPS
and
and
and
redial
redial
redial
Voice
Yes
12 s
4 s
4
30
Redial
Force to
Force to
End-orig
End-orig
AMPS
AMPS
and
and
redial
redial
REFERENCES:
patent: 5459774 (1995-10-01), Breeden
patent: 5509060 (1996-04-01), Hall et al.
patent: 5602901 (1997-02-01), Redden et al.
patent: 5638433 (1997-06-01), Bubien, Jr. et al.
patent: 5722088 (1998-02-01), Storn et al.
patent: 5754953 (1998-05-01), Briancon et al.
patent: 5905447 (1999-05-01), Eaton et al.
patent: 6125174 (2000-09-01), Watanabe
patent: 6408191 (2002-06-01), Blanchard et al.
patent: 9823108 (1998-05-01), None
patent: 9946911 (1999-09-01), None
Brown Charles
Gelin Jean A
Maung Nay
Qualcomm Incorporated
Seo Howard
LandOfFree
Associating dial numbers with call origination schemes does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Associating dial numbers with call origination schemes, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Associating dial numbers with call origination schemes will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3079349