Method and system for confirming a short message of an electronic device

1. Technical Field

Embodiments of the present disclosure relate to message management, and in particular, to a method and system for confirming a short message of an electronic device.

2. Description of Related Art

If an electronic device needs to send a short message, the electronic device may send a data burst message (DBM) including the short message to a Code Division Multiple Access (CDMA) network. The electronic device may know that the DBM has delivered to the CDMA network in response to receiving an acknowledged DBM from the CDMA network. However, if the electronic device does not attempt to access to the CDMA network (e.g. page response or sending a registration message) before sending the DBM, the CDMA network would not return the acknowledged DBM to the electronic device, and the electronic device may not confirm whether the CDMA network has received the DBM.

FIG. 1 is a schematic diagram of one embodiment of an electronic device including a confirmation system.

FIG. 2 is a block diagram of one embodiment of the confirmation system of FIG. 1 .

FIG. 3 is a flowchart of one embodiment of a method for confirming a short message received by a network of the electronic device of FIG. 1 .

The disclosure is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one.

In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, for example, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware, such as an EPROM. It will be appreciated that modules may comprised connected logic units, such as gates and flip-flops, and may comprise programmable units, such as programmable gate arrays or processors. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable medium or other non-transitory computer storage system.

FIG. 1 is a schematic diagram of one embodiment of an electronic device 1 including a confirmation system 13 . The electronic device 1 is in communication with a network 2 , such as a Code Division Multiple Access network (CDMA). The confirmation system 13 may be used to ensure the electronic device 1 to receive an acknowledged data burst message (DBM) when the electronic device 1 does not attempt to access the network 2 before sending the DBM in a system access state. In some embodiments, the electronic device 1 may send a short message, or answer a call in the system access state.

The electronic device 1 also includes a short message service (SMS) unit 12 and a timer 14 . The SMS unit 12 is used to edit short messages of the electronic device 1 . The timer 14 may be a T57m timer. The T57m timer may be used to restrict the electronic device 1 from requesting a power-up registration of the electronic device 1 . The duration of the timer 14 may be 20 seconds, for example. In some embodiments, when the SMS unit 12 needs to send a short message, the electronic device 1 may send a data burst message (DBM) including the short message to the network 2 .

The electronic device 1 further includes a display 11 , a storage system 50 , and at least one processor 60 . The display 11 may output visible data, such as a home page of the electronic device 1 . The storage system 40 may be a memory system of the electronic device 1 , and may be an external storage card, such as a smart media (SM) card, or secure digital (SD) card. The at least one processor 60 executes one or more computerized codes of the electronic device 1 and other applications, to provide the functions of the electronic device 1 .

The electronic device 1 may send a registration message to the network 2 to request the power-up registration after the duration of the timer 14 elapses. The electronic device 1 may register to the network 2 . When there is a call or a short message sent to the electronic device 1 , the network 2 may notify the electronic device 1 . Furthermore, before the electronic device 1 requests the power-up registration, if the electronic device 1 attempts to access the network 2 , such as, attempts of dialing or answering the call, the electronic device 1 may not request the power-up registration. However, the network 2 may also determine that the electronic device 1 is in the network 2 through the attempts of accessing the network 2 of the electronic device 1 .

FIG. 2 is a block diagram of one embodiment of the confirmation system 13 of FIG. 1 . In some embodiments, the confirmation system 13 includes a setting module 131 , an assignment module 132 , an acquisition module 133 , a determination module 134 , and a processing module 135 . The modules 131 - 135 may comprise computerized code in the form of one or more programs that are stored in the storage system 50 . The computerized code includes instructions that are executed by the at least one processor 60 to provide functions for modules 131 - 135 . Details of these operations follow.

The setting module 131 enables the timer 14 when the electronic device 1 is powered on, or disables the timer 14 when the electronic device 1 attempts to access the network 2 and the short message needs to be sent by the SMS unit 12 .

The setting module 131 further sets variables to confirm the short message received by the network 2 (hereinafter referred to as “confirmation variables”). The confirmation variables include a variable “REG_STATUS”, a variable “MO”, a variable “MT”, a variable “SEND_REG”, a variable “GEN_DBM”, a variable “SEND_DBM”, and a variable “QUEUE_DBM”. The variable “REG_STATUS” represents whether the electronic device 1 has registered to the network 2 . The variable “MO” represents whether the electronic device 1 attempts to access the network 2 before sending the DBM. The variable “MT” represents whether the electronic device 1 has received a call from the network 2 before sending the DBM. The variable “SEND_REG” represents whether the electronic device 1 has sent the registration message to the network 2 before sending the DBM. The variable “GEN_DBM” represents whether the electronic device 1 has generated the DBM. The variable “SEND_DBM” represents whether the electronic device 1 may send the DBM. The variable “QUEUE_DBM” represents whether the electronic device 1 queues up the DBM in the electronic device 1 , for example, the electronic device 1 stores the DBM in the storage system 50 to queue up.

In some embodiments, the confirmation variables may be Boolean types, and each of the confirmation variables may have two values including a true value and a false valve. If the values of the confirmation variables are true values, which represent that the electronic device 1 has completed the above-mentioned operations. If the values of the confirmation variables are false values, which represents that the electronic device 1 has not completed the above-mentioned operations. For example, the value of the variable “MO” is the false value, which represents that the electronic device 1 does not attempt to access the network 2 before sending the DBM. The setting module 131 further initializes values of the confirmation variables to be the false values.

The assignment module 132 assigns the true value to the variable “MO” when the electronic device 1 attempts to access the network 2 before sending the DBM. The assignment module 132 assigns the true value to the variable “MT” when the electronic device 1 has received a call from the network 2 before sending the DBM. The assignment module 132 assigns the true value to the variable “SEND_REG” when the electronic device 1 has sent the registration message to the network 2 before sending the DBM. The assignment module 132 assigns the true value to the variable “GEN_DBM” when the SMS unit 12 has finished the short message and the electronic device 1 generates the DBM. When the electronic device 1 has sent the DBM, the assignment module 132 assigns the true value to the variable “SEND_DBM”. If at least one value of the variables “MO”, “MT” and “SEND_REG” is the true value, the assignment module 132 may assign the true value to the variable “REG_STATUS” to represent that the electronic device 1 has registered.

The acquisition module 133 acquires the values of the confirmation variables at a predetermined interval, such as 20 seconds.

When the electronic device 1 displays the home page of the electronic device 1 on the display 11 , the determination module 134 determines whether the electronic device 1 attempts to access the network 2 according to the acquired values of the confirmation variables. In some embodiments, if at least one value of the variables “MT” and “MO” is the true value, the determination module 134 determines that the electronic device 1 attempts to access the network 2 . If both values of the variables “MT” and “MO” are the false values, the determination module 134 determines that the electronic device 1 does not attempt to access to the network 2 .

When the values of the variables “REG_STATUS”, “GEN_DBM” and “SEND_DBM” are the true values, the processing module 135 sends the DBM to the network 2 and waits for the acknowledged DBM from the network 2 .

When the electronic device 1 does not attempt access to the network 2 , the determination module 134 determines whether the duration of the timer 14 elapses.

If the duration of the timer 14 elapses, the processing module 135 further sends the registration message to the network 2 .

If the duration of the timer 14 does not elapse, and both of the values of the variables “GEN_DBM” and “SEND_DBM” are the true values, the assignment module 132 assigns the true value to the variable “QUEUE_DBM”, and the processing module 135 may store the DBM in the electronic device 1 to queue up.

The processing module 135 further receives the acknowledged DBM from the network 2 .

FIG. 3 is a flowchart of one embodiment of a method for confirming a short message received by a network of the electronic device of FIG. 1 . Depending on the embodiment, additional blocks may be added, others removed, and the ordering of the blocks may be changed.

In block S 10 , when the electronic device 1 is powered on, the setting module 131 sets variables to confirming the short message received by the network 2 (confirmation variables for simplification) and enables the timer 14 . The confirmation variables include a variable “REG_STATUS”, a variable “MO”, a variable “MT”, a variable “SEND_REG”, a variable “GEN_DBM”, a variable “SEND_DBM”, a variable “QUEUE_DBM”. The values of the confirmation variables are initialized to be the false values.

In block S 11 , the assignment module 132 assigns the true value to the variable “MO” when the electronic device 1 attempts to access the network 2 before sending the DBM. The assignment module 132 assigns the true value to the variable “MT” when the electronic device 1 has received a call from the network 2 before sending the DBM. The assignment module 132 assigns the true value to the variable “SEND_REG” when the electronic device 1 has sent the registration message to the network 2 before sending the DBM. The assignment module 132 assigns the true value to the variable “GEN_DBM” when the SMS unit 12 has finished the short message and the electronic device 1 generates the DBM. When the electronic device 1 has sent the DBM, the assignment module 132 assigns the true value to the variable “SEND_DBM”. When at least one value of the variables “MO”, “MT” and “SEND_REG” is the true value, the assignment module 132 may assign the true value to the variable “REG_STATUS”.

In block S 12 , the acquisition module 133 acquires the values of the confirmation variables regularly.

In block S 13 , the determination module 134 determines whether the electronic device 1 attempts to access the network 2 according to the acquired confirmation variables, when the electronic device 1 displays the home page of the electronic device 1 on the display 11 . If the electronic device 1 attempts to access to the network 2 , the procedure turns to block S 14 , and if the electronic device 1 does not attempt to access the network 2 , the procedure turns to block S 16 .

In block S 14 , when both values of variables “GEN_DBM” and “SEND_DBM” are the true values, the processing module 135 sends the DBM to the network 2 and waits for the acknowledged DBM from the network 2 , and the setting module 131 disables the timer 14 .

In block S 15 , the processing module 315 receives the acknowledged DBM from the network 2 , and the procedure ends.

In block S 16 , the determination module 134 determines whether a duration of the timer 14 elapses. If the duration of the timer 14 has not elapsed, the procedure turns to block S 17 . If the duration of the timer 14 elapses, the procedure turns to block S 18 .

In block S 17 , when both of the values of variables “GEN_DBM” and “SEND_DBM” are the true values, the assignment module 132 assigns the true value to the variable “QUEUE_DBM”, and the processing module 135 may queue up the DBM in the electronic device 1 to queue up, and the procedure turns back to the block S 16 .

In block S 18 , the processing module 135 further sends the registration message to the network 2 .

In block S 19 , when both values of “GEN_DBM” and “SEND_DBM” are the true values, the processing module 135 sends the DBM to the network 2 and waits for the acknowledged DBM from the network 2 , and the procedure turns back to block S 15 .

It should be emphasized that the described exemplary embodiments are merely possible examples of implementations, and set forth for a clear understanding of the principles of the present disclosure. Many variations and modifications may be made to the-described exemplary embodiments without departing substantially from the spirit and principles of the present disclosure. All such modifications and variations are intended to be comprised herein within the scope of this disclosure and the-described inventive embodiments, and the present disclosure is protected by the following claims.