METHOD FOR CALL FORWARDING ACTIVATION-REMINDER

Abstract: A method for reminding a telephone services subscriber having a subscriber profile linked to an identification number which includes a call-forwarding feature that the call-forwarding feature is active (310) comprises the steps of (assuming that the call-forwarding reminder feature has been activated (310) in the subscriber profile) determining that the call-forwarding feature has been activated and asserting a reminder alert at the telephone associated with the identification number on a timed, periodic basis (450, 452). The method may be implemented as part of the ANSI-41 standard, to include use of the AlertCode and CallingFeaturesIndicator parameters. The method may be implemented as a result of detecting the presence of a mobile station (140) due to autonomous registration, call origination, call termination, or receiving a service order. The method may include specifying a reminder type and frequency interval.

Description: METHOD FOR CALL FORWARDING ACTIVATION - REMINDER BACKGROUND OF THE INVENTION Technical Field This invention relates generally to methods for subscriber service access and modification. More particularly, the invention relates to a method whereby a subscriber is able to receive periodic timed reminders of call forwarding service activation. History of Related Art Various features have been made available to telecommunications subscribers, driven by the needs of a mobile society. Among these features include call forwarding, which operates to automatically redirect a telephone call from the usual destination when certain conditions are present. For example, a telecommunications subscriber may go out of town and desire that all calls, regardless of the circumstances under which they are received, be routed to a different number. The request for this feature, known as "Call Forwarding Unconditional" (CFU), results in all calls being directed from the dialed number, e.g., "111-111-1111" to the forwarded number, e.g., "222-222-2222" whenever the number "111-111-1111" is dialed. The call forwarding feature may also be selected if the subscriber is busy with another call (i.e., Call Forwarding Busy (CFB)), if the dialed number is not answered (i.e., Call Forwarding No Answer (CFNA)), during a specified time period (i.e., Call Forwarding Variable (CFV)), or to a particular default forwarding telephone number (i.e., Call Forwarding Default (CFD)). Figure 1 illustrates how call forwarding may be invoked using a request for CFU by the device operated by the subscriber as an example. Figure 1 also illustrates the provision of an optional CFU alert to the subscriber in the form of a served Mobile Station (MS). The various active components shown in Figure 1 include an Originating Mobile Switching Center (MSC) 100, a Home Location Register (HLR) 110, a Visitor Location Register (VLR) 120, a Serving MSC 130, and a MS 140. At step 150, a call is originated and directed toward the originating MSC 100 using the dialed address digits (i.e., the directory number) for the MS 140. These digits are received at the originating MSC 100. A LOCATIONREQUEST message is sent from the originating MSC 100 to the HLR 110 associated with the MS 140 in step 160. The LOCATIONREQUEST message contains the directory number of the MS 140, which is not necessarily the Mobile Identification Number (MIN). At this point, the HLR 110 determines from the MS 140 service profile that the CFU feature has been activated. Such activation typically occurs after the subscriber enters an activation request using a feature code (not shown). The location request response to the originating MSC 100 in step 170 provides the forwarding number and other routing information in a parameter commonly known as the TerminalList, along with an indication of the type of call forwarding, (i.e., CFU) in the DMH Redirectionlndicator parameter. The originating MSC 100 then establishes a call to the specified forwarding number in step 180. If the subscriber has requested a reminder that CFU has been activated, as determined by the HLR 110, an Information Directive message is sent to the VLR 120 where the MS 140 is registered in step 190. The VLR 120 then directs the serving MSC 130 to alert the MS 140 by sending an Information Directive message to the serving MSC 130 in step 200, which in turn alerts the MS 140, if it is idle, using an alerting method specified in the Alert Code parameter within the received InformationDirective message. For example, the MSC 130 may apply a single, abbreviated alert signal to the MS 140 in step 210 and then wait for a report on the success or failure of the page to the MS 140. Once the result of the page is determined, the serving MSC 130 sends an informationdirective response back to the VLR 120, including the result of the alerting action (e.g., success, not attempted due to a busy condition at the MS 140, etc.) in step 220. The informationdirective response is forwarded from the VLR 120 to the HLR 110 in step 230. The disadvantage of this prior art method is that a forwarding reminder, in the form of an abbreviated alert tone, is only sent to the subscriber at the same time that each call is forwarded. Thus, a subscriber selecting various call forwarding services is only reminded at the time a call forwarding action occurs, and at no other time. This makes it very easy for a subscriber to forget that the call forwarding feature has been activated, such that calls may be forwarded at inappropriate times, or when the subscriber is unavailable at the forwarding number. Thus, what is needed is a call forwarding reminder which can be implemented on a timed, periodic basis. That is, the call forwarding reminder alert at a subscriber telephone would be more useful if it could be activated every ten minutes, fifteen minutes, etc. This would provide a periodic reminder to the subscriber that the call forwarding feature has been activated, and is still active. A useful reminder alert would include the ability to vary the periodicity of the reminder, and the reminder type, for example, the reminder alert might consist of an abbreviated tone, as in the prior art, a vibration signal, or a message on the display of a telecommunications device. SUMMARY OF THE INVENTION The method of the present invention enables a telecommunications subscriber to receive a timed, periodic reminder that a call forwarding feature for a particular telephone has been activated. In the most basic form, the method includes the steps of determining that the call-forwarding feature has been activated and asserting a reminder alert at the subscriber's telephone on a timed periodic basis (assuming that the call-forwarding reminder feature has been activated within the subscriber profile). That is, in contradistinction to the prior art, wherein reminders are asserted at the time that a telephone call is made, the method of the present invention will assert reminders on a timed, periodic basis (e.g., every five minutes, every ten minutes, every half hour, etc.) as selected by the subscriber. The method may further include the step of sending a request to a node (e.g., the Serving MSC) to activate the call-forwarding reminder feature within the subscriber profile. The request made by the subscriber can take the form of an American National Standards Institute-41 (ANSI-41) message, such as a QualifϊcationDirective message, an InformationForward message, or a registration notification response. If such standard messages/responses are used, an AlertCode including a reminder type (e.g., a ring tone, a vibrating signal, or a message displayed on the subscriber telephone) and a reminder frequency interval selected by the subscriber can be inserted as a parameter in the message. If the call-forwarding reminder feature is not presumed to be always active, several different scenarios may result in activation of the feature. These include circumstances wherein the subscriber profile is updated or downloaded, such that sending the request to the node to activate the call-forwarding reminder feature may include the step of detecting the presence of a telephone as a result of autonomous registration, call origination, call termination, or receiving a service order. Also, the subscriber may specifically request activation of the call-forwarding reminder feature by using a key sequence which includes a service code. Similarly, the feature may be deactivated by entry of a key sequence and service code. The step of asserting the reminder alert at the telephone may occur in several different ways. For example, a message may be sent to the telephone, and the reminder signal asserted on a periodic-timed basis as determined within the telephone. Alternatively, the message may be sent to the telephone each time a reminder signal is to be asserted, and the telephone merely acts as a device to assert the signal under control of the message sender. Another method of asserting the reminder signal is to ring the telephone, and announce verbally that the call-forwarding feature is active on a periodic basis. The method of the present invention may operate almost entirely within the node, or entirely within the telephone. For example, if the method operates within the node, the method steps may include one or more of the following: receiving a request at the node to activate the call-forwarding reminder feature in the subscriber profile, determining within the node that the call-forwarding feature has been activated, and asserting a reminder alert from the node to the telephone on the timed, periodic basis. However, if the method is implemented within the telephone, then the steps may include one or more of the following: sending a request from the telephone to the node to activate the call-forwarding reminder feature in the subscriber profile, determining within the telephone that the call-forwarding feature has been activated, and asserting a reminder at the telephone on a timed, periodic basis. Thus, the node or the telephone may be responsible for asserting the reminder alert on a timed, periodic basis. Either implementation is contemplated by the method of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the structure and operation of the present invention may be had by reference to the following detailed description when taken in conjunction with the accompanying drawings, wherein: Fig. 1 is a signal flow diagram illustrating call forwarding reminder alerts as they exist in the prior art (previously described); Fig. 2 is a flow chart diagram illustrating activation and deactivation of the call forwarding reminder feature within the method of the present invention; Fig. 3 is a signal flow diagram illustrating the method of the present invention applied during user profile update activity; Fig. 4 is a signal flow diagram illustrating the method of the present invention applied to a registration notification response scenario; Fig. 5 is a signal flow diagram illustrating the method of the present invention applied to a handoff scenario; Fig. 6 is a signal flow diagram illustrating the method of the present invention applied to a qualifϊcationrequest response operation; and Figs. 7A-7B are flow chart diagrams illustrating activation and deactivation of the call forwarding reminder feature using a key sequence and service code entry by the subscriber. DETAILED DESCRIPTION OF PRESENTLY PREFERRED EXEMPLARY EMBODIMENTS The method of the present invention provides the capability to remind a telecommunications subscriber that call forwarding has been activated, and continues to be activated, on a timed, periodic basis. The subscriber is reminded that the forwarding feature is active on a selectable, periodic basis such that activation of the feature is not easily forgotten, and the feature can be deactivated at an appropriate time. The reminder signal may take many forms, such as an abbreviated ring tone, a vibrating action at the telephone, or a message on the telephone display. Essentially, the invention operates as follows: the telecommunications subscriber enables call-forwarding, using a subscriber service procedure, as is commonly known in the art. If the call forwarding reminder feature is active, then the user is reminded that call-forwarding has been enabled at timed intervals by way of a reminder signal. The reminder signals continue on a timed, periodic basis until the call forwarding reminder feature is deactivated, or until call-forwarding is disabled. Thus, the user will be reminded on a timed, periodic basis, and not just at the times that a calling party chooses to make a call to the telephone that has been forwarded. The method of the present invention may operate in several different ways. Primarily, it is the activation of the Call-Forwarding Reminder Feature (CFRF) where the most variety occurs. Specifically, the CFRF can be activated by command, such as when the profile is updated as requested by the subscriber or the service provider; during registration, as may result from autonomous registration, call origination, call termination, or receipt of a service order; as a result of a handoff operation; or by subscriber procedure, such as when a subscriber enters a particular key sequence, including a service code. Deactivation of the CFRF may also occur under these circumstances. The essential details of CFRF implementation after activating and deactivating the feature can be seen in Fig. 2. The sequence begins at step 300, and continues with activation of the CFRF at step 310. The details of various activation scenarios will be discussed below. Once the CFRF is activated, a flag, such as an AlertFLAG, is turned ON in step 320. A test is made to determine whether the AlertFLAG is ON in step 330. If so, then the CFRF timer will be reset (i.e., set to zero) in step 340, and a reminder type and frequency interval may be sent to a node which communicates with the telephone so that the type of reminder signal (e.g., abbreviated tone, vibration signal, or display message) can be noted by the network, and asserted at the telephone at the appropriate reminder frequency interval. For example, if the method of the present invention is implemented using ANSI-41 standard Mobile Application Part (MAP) signaling messages, then activation of the CFRF can be noted by passing the value of the AlertFLAG (ON) using a reserved portion of the Calling Features Indicator (CFI) MAP parameter. The reminder type can be selected within the Pitch and Cadence fields of the AlertCode MAP parameter, and the reminder frequency can be passed on to the Alert Action field within the AlertCode MAP parameter. To be even more specific, the CFRF AlertFLAG can be embedded within the CFI parameter in one of the reserved fields. The cadence field of the AlertCode can be set to a value of "12" to indicate an abbreviated ring tone of "Pip Pip Pip Pip", the pitch can be set to "0" for a medium pitch alert, and the Alert Action can be set to a (reserved) value of "2" to indicate that the reminder should be asserted every fifteen minutes. Then, in step 360, the CFRF timer is incremented, and in step 370, the newly-incremented time values are compared to the preselected frequency of the reminder interval. If the newly-incremented time value is greater than or equal to the preselected reminder frequency interval, the AlertFLAG can be checked in step 330 to verify that it is ON, the timer is reset in step 340, and the AlertCode is resent to the node so that the reminder will be asserted in step 350 according to the preselected frequency interval selected by the user. If the CFRF is deactivated in step 372, then the AlertFLAG is turned OFF in step 374. After verifying that the AlertFLAG is not ON in step 330, an AlertCode having a cadence value of "0" can be sent to the node to defeat the tone used for reminder alerts and the CFRF feature flag within the CFI MAP parameter can also be reset. The CFRF timer is then reset in step 390, and the process ends at step 400. Not shown in Fig.2 is the process of verifying that the call-forwarding feature is active. It is assumed that the process of Fig. 2 will only occur if the call-forwarding feature has been activated, either by the user, or by the service provider. Otherwise, if call-forwarding is inactive, then the activation of the CFRF will result in a cadence value of "0" being sent along with the AlertFLAG, which indicates that the CFRF is active (however, the reminder signal will not be asserted due to the cadence value being set to "0"). Turning now to Figs. 3 and 4, the method of the present invention is illustrated as applied to QualificationDirective messages and registrationnotification responses, respectively. More particularly, Fig. 3 illustrates the scenario within a QualificationDirective operation occurs because the subscriber has requested a profile update (after the CFRF has been selected for activation by the subscriber). In step 410, the HLR 110 reports the change in the MS 140 service profile by sending a QualificationDirective message to the VLR 120 where the MS 140 is registered. In this case, the QualificationlnformationCode parameter indicates that the type of qualification required is for the user profile only. Within the Profile field, the AlertCode and CFI MAP parameters can be set as described above. Generally, these parameters will be set to indicate that the CFRF is active, and to notify the node that a particular reminder type and preselected frequency interval have been requested. An empty qualifϊcationdirective response is sent from the VLR 120 to the HLR 110 in step 420. In step 430 the VLR 120 reports the change in the MS 140 service profile by sending a QualificationDirective to the serving MSC 130, coded to indicate that the QualificationlnformationCode is set for a profile update only; the AlertCode and CFI parameters are set as noted previously. After receiving the QualificationDirective, the serving MSC 130 sends an empty qualifϊcationdirective response to the VLR 120 and begins implementing the CFRF control algorithm illustrated in Fig. 2. This occurs in step 440, and is followed in step 450 by a timed, periodic assertion of a reminder alert at the MS 140. Multiple periodic reminders may be asserted by the MSC 130 (i.e., the node), as shown in steps 450 and 452. If the MSC 130 is responsible for asserting the reminders on a timed periodic basis, then all of the steps shown in Fig.2 will typically be carried out within the MSC 130, and step 350 in Fig. 2 is equivalent to steps 450 and 452 in Fig. 3. As shown in Fig. 4, the CFRF can also be activated as part of a registration notification scenario. In step 460, the serving MSC 130 determines that a roaming MS 140 has entered the service area. The presence of the MS 140 may be detected by autonomous registration activity, call origination activity, or call termination activity. As a result, the serving MSC 130 will send a Registration Notification message to the VLR 120 in step 470. The serving VLR 120 then determines that the MS 140 is previously registered with an MSC located within the VLR 120 domain, but has been reported inactive; that the MS 140 is unknown to the VLR 120; or that the requested information cannot be made available to the MS 140. In any event, the serving VLR 120 forwards the Registration Notification to the HLR 110 associated with the MS 140 in step 480. If the MS 140 is authorized, the HLR 110 will return the requested information to the serving VLR 120 with a registration notification response. The AlertCode and CFI parameters are set within the registration notification response as described previously. Typically, the CFI will be set to indicate that the CFRF is active and will notify the node that a particular reminder signal should be asserted as qualified by a reminder type and preselected reminder frequency interval. For the purpose of this document, a "reminder type" is typically a parameter value stored in memory which indicates a particular reminder signal selection, while the "reminder signal" is a physical indication, such as a ring tone, vibrating signal, or call-forwarding reminder message display used to remind the telecommunication subscriber that the CFRF is active. This information is returned to the VLR 120 in step 490. The VLR 120 then forwards the registration notification response information to the serving MSC 130 in step 500 and the serving MSC 130 stores the service profile, including a parameter or flag that indicates the CFRF is active, and begins implementing the control algorithm illustrated in Fig.2. The serving MSC 130 then sends a signal to the MS 140 on a timed, periodic basis so as to assert a reminder alert at the MS 140 in steps 510 and 512. Assuming that the MSC 130 is responsible for asserting the reminders on a timed periodic basis, then all of the steps shown in Fig. 2 will typically be carried out within the MSC 130, and step 350 in Fig. 2 is equivalent to steps 510 and 512 in Fig. 4. While only two reminders are shown, it should be noted that any number of reminders, from one up to an indeterminate number, can be sent by the MSC 130 to the MS 140. This is the case for all illustrations of the method, in Figs. 2-5. Fig. 5 illustrates the scenario wherein the CFRF feature is activated as part of a handoff operation. After a call is in progress, as shown in step 520, an intersystem handoff occurs to the serving MSC 130 by the anchor MSC 105. The anchor MSC 105, which has access to the profile of the MS 140, determines that the CFRF is active, and sends an InformationForward message (which contains the CFI and AlertCode information) to the serving MSC 130. This occurs in step 530, and the serving MSC now undertakes implementation of the CFRF control algorithm illustrated in Fig. 2. The serving MSC 130 alerts the MS 140 on a timed, periodic basis in step 540, using the reminder type and reminder frequency intervals selected by the subscriber. As noted above, these parameters were received in the Information Forward message sent in step 530. The serving MSC 130 then sends an informationforward response to the anchor MSC 105, which includes the result of the alerting action undertaken in step 540. Assuming that the MSC 130 is responsible for asserting the reminders on a timed periodic basis, then all of the steps shown in Fig. 2 will typically be carried out within the MSC 130, and step 350 in Fig.2 is equivalent to steps 540 and 552 in Fig. 5. Fig. 6 illustrates activation of the CFRF as a result of a QualificationRequest operation, such as occurs upon initial registration of the mobile station, or any time the Serving MSC requests a download of the MS profile. After determining that a roaming MS 140 is within the local service area, the serving MSC 130 sends a QualificationRequest message to the serving VLR 120 in step 560. This process may result from autonomous registration activity, call origination activity, call termination activity, or receipt of a service order placed by the MS 140. If the MS 140 was previously registered by an MSC located within the domain of the VLR 120, then the VLR 120 may take no further action other than to record the identity of the MSC 130 currently serving the MS 140, and proceed on to step 590. If the MS 140 is unknown to the VLR 120, or if the information requested by the MSC 130 is not available at the VLR 120, then the VLR 120 sends a QualificationRequest message to the HLR 110 associated with the MS 140. This occurs in step 570. If the MS 140 is authorized by the HLR 110, the HLR 110 returns such an indication, along with the profile for the MS 140, to the serving VLR 120 in the qualifϊcationrequest response. As described in detail above, the qualifϊcationrequest response contains the AlertCode parameter, which includes a reminder type and preselected reminder frequency interval for the CFRF. Further, the CFI is configured to show that the CFRF is active. This occurs in step 580. The VLR 120 then forwards the qualification request response message to the serving MSC 130 in step 590 and the serving MSC 130 stores the service profile, including a parameter or flag that indicates the CFRF is active, and begins implementing the control algorithm illustrated in Fig. 2. The serving MSC 130 then sends a signal to the MS 140 in steps 600 and 610. If the MSC 130 is responsible for asserting the reminders on a timed periodic basis, then all of the steps shown in Fig. 2 will typically be carried out within the MSC 130, and step 350 in Fig.2 is equivalent to steps 600 and 610 in Fig. 6. Thus, the method for reminding a telephone services subscriber having a subscriber profile linked to an identification number which includes a call-forwarding feature that the call-forwarding feature is active comprises the general steps of determining that the call-forwarding feature has been activated and asserting a reminder alert at the telephone associated with the identification number on a timed, periodic basis. This sequence assumes that the CFRF within the subscriber profile has be previously activated. The method may also include the step of explicitly sending a request to a node to activate the CFRF in the subscriber profile. While the identification number for the MS 140, or any other telecommunications device, was not explicitly mentioned in the preceding description, it should be understood that the identification number, such as an International Mobile Equipment Identity (IMEI) number, is needed to link the subscriber phone with the subscriber profile throughout a telecommunications network. The request can be a message including a parameter, such as an AlertCode, indicating that the subscriber desires timed, periodic alerts regarding continued activation of the call-forwarding feature. The message may take the form of a QualificationDirective message, a registrationnotifϊcation response, an InformationForward message, or a qualifϊcationrequest response. The message typically includes a preselected reminder type, which specifies that the reminder take the form of a ring tone, a vibration signal, or a display message. The message also typically includes a reminder frequency interval, which specifies the frequency at which the reminder alerts will be asserted at the telephone, such as every five, ten, or thirty minutes. The reminder type and preselected reminder frequency interval may be included in the parameter, or some other part of the message. The node, as has been noted above, can be a serving MSC. The method may include the step of requesting an update of the subscriber profile, or that the subscriber profile is to be downloaded. The method may also include the step of validating the request, so as to ensure that the subscriber is entitled to activation of the CFRF. The message may be sent to the telephone each time that the reminder signal is asserted. The assertion of a reminder alert at the telephone may also occur by ringing the telephone and announcing (e.g. verbally) the active status of the CFRF at the telephone on a timed, periodic basis. As mentioned above, the step of sending a request to the node may occur as a result of detecting the presence of the telephone due to autonomous registration, call origination activity, call termination activity, or receiving a service order. When the method is implemented almost entirely by the node, then the steps may comprise one or more of the following: receiving a request at the node to activate the CFRF in the subscriber profile, determining within the node that the call-forwarding feature has been activated, and then asserting a reminder alert from the node to the telephone on a timed, periodic basis. Whether the method is implemented mostly within the node, the request to activate the CFRF in the subscriber profile may include the step of entering a key sequence into the telephone which includes a service code that operates to activate the CFRF. The CFRF may also be deactivated using a key sequence. Turning now to Figs.7A and 7B, flow chart diagrams to illustrate when the method is implemented almost entirely by the telephone and initiating CFRF activation and deactivation can be seen, respectively. If it is determined that the MS is authorized to implement the CFRF in step 610, then the subscriber may activate the feature by entering a feature code for a particular type of reminder and the time interval for asserting reminder alerts as a key sequence in step 620. The telephone itself may then detect activation of the feature in step 630, by waiting for the feature activation confirmation from the network in step 635, and if the activation is successful as noted in step 640, then the CFRF AlertFLAG can be turned on in step 670, where the telephone starts sending the periodic reminder signal in step 675, and the activation procedure ends in step 660. If the activation is not successful, then the CFRF is turned OFF in step 650 and the procedure ends at step 660. To deactivate the CFRF, the authorization of the MS to use the CFRF is verified in step 680, and the user may send a key sequence, including a service code which indicates that the CFRF features should be deactivated, in step 690. If the telephone detects the desire of the subscriber to deactivate the CFRF in step 700, then the telephone waits for the feature deactivation confirmation from the network in step 705, and the deactivation is confirmed, as noted in step 710, then the CFRF will be turned OFF in step 740. Thus, the telephone stops sending the periodic reminder signal in step 750 and the procedure ends in step 730. However, if deactivation is not successful as detected in step 710, there will be no change to the CFRF in step 720, and the procedure will end at step 730. Thus, the method may include the steps of entering a key sequence into the telephone which includes a service code to deactivate the CFRF and determining that the call-forwarding reminder feature has been deactivated. As mentioned above, the assertion of a reminder signal at the telephone may occur due to timed, periodic activity within the telephone itself. Thus, a single message may be sent from the node to the telephone to indicate that the CFRF is active, and thereafter, the reminder alert signal will be asserted according to reminder signal timing which originates from within the telephone. Although the invention has been described with reference to specific embodiments, this description is not meant to be construed in a limited sense. The various modifications of the disclosed embodiments, as well as alternative embodiments of the invention, will become apparent to persons skilled in the art upon reference to the description of the invention. It is, therefore, contemplated that the appended claims will cover such modifications that fall within the scope of the invention, or their equivalents.

Claims: What is claimed is: 1. A method for reminding a telephone services subscriber having a subscriber profile linked to an identification number which includes a call-forwarding feature that the call-forwarding feature is active, comprising the steps of: determining that the call-forwarding feature has been activated; and asserting a reminder alert at a telephone associated with the identification number on a timed periodic basis. 2. The method of Claim 1, further including the step of sending a request to a node to activate a call-forwarding reminder feature in the subscriber profile. 3. The method of Claim 2, wherein the request is a message including a parameter indicating that the subscriber desires timed periodic alerts regarding continued activation of the call-forwarding feature. 4. The method of Claim 3 , wherein the parameter is an AlertCode. 5. The method of Claim 2, wherein the message includes a reminder type and a preselected reminder frequency interval. 6. The method of Claim 2, wherein the parameter includes a reminder type and a preselected reminder frequency interval. 7. The method of Claim 2, wherein the node is a Serving Mobile Switching Center. 8. The method of Claim 2, wherein the step of sending a request to a node to activate a call-forwarding reminder feature in the subscriber profile includes the step of entering a key sequence into the telephone, wherein the key sequence includes a service code which operates to activate the call-forwarding reminder feature. 9. The method of Claim 1, including the steps of: entering a key sequence into the telephone, wherein the key sequence includes a service code which operates to deactivate the call-forwarding reminder feature; and determining that the call-forwarding reminder feature has been deactivated. 10. The method of Claim 2, including the step of validating the request. 11. The method of Claim 1 , wherein the identification number is an International Mobile Equipment Identity (IMEI). 12. The method ofClaim l, wherein the step of asserting a reminder alert at a telephone associated with the identification number on a timed periodic basis includes the steps of: sending a message to the telephone associated with the identification number; and asserting a reminder signal at the telephone associated with the identification number on a periodic timed basis. 13. The method of Claim 12, wherein the reminder signal is a ring tone. 14. The method of Claim 12, wherein the reminder signal is a vibrating signal. 15. The method of Claim 12, wherein the reminder signal is a call-forwarding reminder display message. 16. The method of Claim 12, wherein the message to the telephone associated with the identification number is sent each time that the reminder signal is asserted at the telephone associated with the identification number. 17. The method of Claim 1 , wherein the step of asserting areminder alert at a telephone associated with the identification number on a timed periodic basis includes the steps of: ringing the telephone associated with the identification number on a timed periodic basis; and announcing an active status of the call-forwarding feature at the telephone associated with the identification number. 18. The method of Claim 1, wherein the step of determining that the call-forwarding feature has been activated includes the step of determining within the telephone that the call-forwarding feature has been activated. 19. The method of Claim 2, wherein the step of determining that the call-forwarding feature has been activated includes the step of determining within the node that the call-forwarding feature has been activated.

Inventors: MARTINEZ JAIME, MARTINEZ, JAIME
Applicants: ERICSSON TELEFON AB L M, TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Application year: 2001
Main classification: H04M3
IPC codes: H04M3