TWI498839B - Device and method for receiving the buying/selling signals of the finance software on a mobile apparatus - Google Patents

Description

Mobile device financial transaction software buying/selling signal receiving device and method

The present invention relates to a mobile device financial transaction software, and more particularly to a device and method for receiving/selling a mobile device software transaction software.

In general, the buy/sell signal provider is a securities dealer or a trader who provides a buy/sell signal for its customers (ie users) to refer to the bid/sale price and time point of a particular financial product. There are two ways to receive the buy/sell signal from the mobile device financial transaction software: 1. Sending a buy/sell signal to the mobile device via SMS (SMS); 2. Directly receiving the server by the financial transaction software. A buy/sell signal sent to a mobile device.

The main shortcoming of the transmission of the buy/sell signal by SMS is that the SMS is opened by the external program of the financial transaction software (usually the built-in program of the mobile device operating system). Users cannot directly click on the financial products or prices in the SMS content. To make an order transaction, and to open the SMS financial transaction software after reading the newsletter, and the user must manually input the financial products and prices in the buy/sell signal (as mentioned in the newsletter content) before proceeding. Single transaction.

As for the purchase/selling signals received by the financial transaction software directly from the server to the mobile device, although the shortcomings of transmitting/selling signals through the SMS are improved, the user can directly receive signals in the financial transaction software. You can click to buy/sell financial products or prices in the signal content to place an order, but this kind of technology still has a major drawback. That is, the financial transaction software must be executed to receive the buy/sell signal, that is, it is closed. After buying the software, you cannot receive the buy/sell signal.

The mobile device financial transaction software relies on the Internet (Data Network, also known as "data transmission connection") to transmit data (Data), and the network protocol of the network connection is divided into HTTP and TCP. HTTP is a type of Connectionless Network Protocol. As the name implies, Connectionless means that the network does not stay connected, that is, the network connection is terminated immediately after the data transmission is completed. Some of the mobile device financial transaction software adopts HTTP as the protocol for network connection because its network has no connection characteristics because its network connection has low power consumption. The automatic update data of the software adopts a fixed time to establish a one-time HTTP network connection to the server. The fixed time can usually be set in the program, for example: 5 seconds/10 seconds/15 seconds/20 seconds/30 seconds/ 1 minute. If the network connection adopts the HTTP protocol and there is no fixed time automatic update, the user needs to manually update the data. TCP is a type of Connection-Oriented Network Protocol (also known as "Connection-Oriented Network Protocol"). The characteristic of TCP is that after the network connection is established, that is, the connection state is maintained until one party terminates the connection. Generally, the program that implements the network connection by TCP Socket is also such a communication protocol, and the TCP connection mode is The power consumption of the power supply is larger than that of the HTTP method (that is, the TCP connection method consumes more power).

Directly receiving buy/sell signals from the mobile device financial trading software can be divided into two ways:

1. Automatically receive by TCP connection;

Second, automatically receive by HTTP connection.

The first method of viewing is shown in Figure 1A: when the server 12 has a buy/sell signal 14, the buy/sell signal 14 is automatically transmitted to the financial transaction software of the mobile device 10. The shortcoming of this method is that when the financial transaction software is closed, the buy/sell signal 14 cannot be automatically received. If the software is always turned on in order to receive the buy/sell signal 14, the power consumption is quite wasted, and the software is occupied by the hardware after being turned on. Resources (CPU and memory) affect the operational effectiveness of the mobile device 10.

The second method of view is as shown in FIG. 1B: the financial transaction software running on the mobile device 10 automatically establishes an HTTP connection for a fixed time (for example, every 30 seconds), and issues an automatic inquiry command 16 to the server 12. By downloading the buy/sell signal 14 from the server 12. The shortcomings of this method are the same as the second method of view, that is, when the financial transaction software is closed, the buy/sell signal 14 cannot be automatically received. If the software is always powered on in order to receive the buy/sell signal 14, the power consumption is quite wasted. And when the software is turned on, the operating efficiency of the mobile device 10 is affected by occupying hardware resources (CPU and memory).

Referring to Figure 2, the system function block diagram of the device is shown. This figure only depicts the modules related to this specification. The remaining unrelated modules are omitted and not depicted. The financial transaction software 18 includes a network connection module 182, a data transmission module 184 and a buy/sell signal module 186. The network connection module 182 is used to establish network connection and close the network connection. The data transfer module 184 is configured to receive data transmitted by the server 12 to the mobile device 10, and to transmit data to the server 12 by the mobile device 10. The information includes financial commodity quote information, query instructions, and buy/sell signals 14. The buy/sell signal module 186 is configured to generate a buy/sell signal view (not depicted) based on the received buy/sell signal 14 for the user to view the buy/sell signal content.

Figure 3A is a flow chart of the user operation of the financial transaction software automatically receiving the buy/sell signal mode. The specific operation flow after opening the financial transaction software 18 is used to explain that the TCP automatically receives the buy/sell signal (such as Figure 1A). For the operation flow shown in the figure, please refer to Figure 1A and Figure 2, which includes the following steps:

Step 101: Execute the financial transaction software; the user executes the transaction financial transaction software 18 on the mobile device 10.

Step 102: Switch to the buy/sell signal view with the menu; when the software is turned on, the user can switch to the buy/sell signal view (not depicted) generated by the buy/sell signal module 186 by the menu (not depicted). Waiting to receive the buy/sell signal 14, or switch to the self-selected quote view (not depicted) while waiting for the buy/sell signal 14 while looking at the quote information.

Step 103: View the buy/sell signal and place an order; after receiving the buy/sell signal 14, the user can view the content of the buy/sell signal 14 (the buy/sell signal 14 shows the contents of the buy/sell signal 14 Not depicted), and the contents of the buy/sell signal 14 can be clicked to place an order transaction. For example, the user clicks on the buy signal of one of the financial products, and then the buy/sell signal module 186 automatically switches to the order transaction view (not depicted), and automatically fills in the code of the financial product, and the user manually Fill in other order trading information including the number of transactions and the price, you can place an order transaction.

Here, please refer to Figure 3B, which is a flow chart of the financial transaction software TCP automatically receiving the buy/sell signal. Between the above steps 102 to 103, the financial transaction software 18 is implemented by the TCP connection method to perform the following steps:

Step 111: Establish a network connection; when switching to the buy/sell signal view, the network connection module 182 establishes a network connection by using a TCP network protocol.

Step 112: Receive the buy/sell signal; after the buy/sell signal 14 is generated, the server 12 automatically transmits the buy/sell signal 14 to the mobile device 10, which is responsible for receiving by the data transfer module 184. As shown in Figure 1A.

Such a TCP connection automatically receives a buy/sell signal. If it waits for a long time to receive a buy/sell signal (steps 111 to 112), it consumes power and consumes power, and the user must not close the financial transaction software 18 while waiting.

Please refer to the 3A and 3C diagrams for the merger. The 3C diagram shows the flow chart of the HTTP transaction automatic receiving/selling signal of the financial transaction software. Between step 102 and step 103 of the above user operation flowchart, the financial transaction software 18 is implemented in the HTTP connection manner to perform the following steps:

Step 211: periodically establish a network connection and query the buy/sell signal; after entering the buy/sell signal view, the buy/sell signal module 186 periodically requests the network connection module 182 to establish a network connection by using an HTTP protocol. The automatic query command 16 is sent to the server 12 via the data transfer module 184 to query the buy/sell signal 14, as shown in the upper half of Figure 1B.

Step 212: Whether there is a buy/sell signal; after the automatic inquiry command 16 is sent to the server 12, if the server 12 has a buy/sell signal 14, then the process jumps to step 213, if the server 12 has no buy/sell signal 14 Then go to step 211.

Step 213: Download the buy/sell signal; when the server 12 has a buy/sell signal 14, the data transfer module 184 can download the buy/sell signal 14 to the mobile device 10, as shown in the lower half of Figure 1B. After downloading, the buy/sell signal module 186 updates the data of the buy/sell signal view.

This kind of HTTP connection automatically receives the buy/sell signal. See the technology. The TCP automatically receives the buy/sell signal to save power consumption. However, this kind of technology has the same shortcomings as the prior art, that is, the financial transaction software 18 cannot automatically receive the buy/sell signal after it is closed.

In summary, the prior art mobile device financial transaction software 18 can still receive the function of buying/selling signals after the transaction software is closed, and the transaction software can not be turned off to waste power consumption of the network connection, and the transaction software opens the cause. Taking up hardware resources to affect the operational performance of mobile devices, such receiving and selling signals is extremely inconvenient for users.

Therefore, it is necessary to propose a device and method for receiving/selling the signal of the mobile device financial transaction software. After the transaction software is closed, the resident program that occupies less hardware resources can continue to receive the buy/sell signal to satisfy the user. The potential need to operate financial trading software.

The invention provides a device and a method for receiving/selling a signal of a mobile device financial transaction software, which mainly opens a resident program that occupies less hardware resources, and is responsible for receiving a buy/sell signal and allowing the financial transaction software to be closed. In the case, you can continue to receive buy/sell signals.

The invention provides a mobile device software transaction software buying/selling signal receiving device, which is applied to a mobile device, comprising: a financial transaction software and a resident program. The financial transaction software includes a first network connection module, a data transmission module, a buy/sell signal module, and a resident program startup module. The first network connection module establishes or closes a network connection between the mobile device and a server. The data transmission module receives the received data transmitted by the server to the mobile device when the network connection is established, and transmits the transmission data generated by the mobile device to the server, wherein the received data includes a buy/sell signal. The buy/sell signal module is configured to generate a buy/sell signal view based on the received buy/sell signal for the user to view the buy/sell signal content. The resident program startup module starts the resident program after the financial transaction software is executed. The resident program includes a second network connection module, an instruction transmission module, a buy/sell signal receiving module, and a resident program termination module. The second network connection module is used to periodically establish an HTTP network connection between the mobile device and the server. The command transfer module transmits an automatic query command to the server during the establishment of the HTTP network connection. The buy/sell signal receiving module downloads the buy/sell signal transmitted by the server during the establishment of the HTTP network connection, and stores the buy/sell signal on the mobile device. The resident program terminates the module and terminates the resident program when a termination condition is triggered.

The invention further provides a mobile device financial transaction software buying/selling signal receiving method, which is applied to a mobile device, comprising the steps of: executing a financial transaction software; and starting a resident program. The resident program performs the following steps: periodically establishing an HTTP network connection between the mobile device and a server; during the establishment of the HTTP network connection, transmitting an automatic query command to the server; establishing the HTTP network connection During the period, a buy/sell signal is downloaded by the server; and a buy/sell signal is stored in the mobile device.

The invention further provides a mobile device software transaction software buying/selling signal receiving method, which is applied to a mobile device, comprising the steps of: executing a financial transaction software; the financial transaction software starts a resident program; and closing the financial transaction software; The resident program receives a buy/sell signal. The resident program performs the following steps: periodically establishing an HTTP network connection between the mobile device and a server; during the establishment of the HTTP network connection, transmitting an automatic query command to the server; establishing the HTTP network connection During the period, a buy/sell signal is downloaded by the server; and a buy/sell signal is stored in the mobile device.

The detailed features and advantages of the present invention are set forth in the Detailed Description of the Detailed Description of the <RTIgt; </ RTI> <RTIgt; </ RTI> </ RTI> </ RTI> <RTIgt; The objects and advantages associated with the present invention can be readily understood by those skilled in the art.

The present invention is applied to a mobile device, such as a mobile phone, a PDA, a stock machine, a smart phone, a tablet PC, or a financial transaction software 20 such as a mobile Internet device (Ultra-Mobile PC).

Referring to Figure 4, there is shown a block diagram of the system function of the apparatus of the embodiment of the present invention. The financial transaction software 20 of the present invention comprises: a first network connection module 22, a data transmission module 24, a buy/sell signal module 26 and a resident program startup module 28. The first network connection module 22 is used to establish a network connection between the mobile device 10 and the server 12; or, the network connection between the mobile device 10 and the server 12 is closed. The data transfer module 24 receives the received data transmitted by the server 12 to the mobile device 10 when the network connection is established, and transmits the transfer data generated by the mobile device 10 to the server 12. The receiving data contains a buy/sell signal 14. The buy/sell signal module 26 generates a buy/sell signal view (not depicted) based on the buy/sell signal 14 stored by the mobile device 10. The resident program launch module 28 activates the resident program (TSR, Terminate-and-Stay-Resident) 30 after the financial transaction software 20 is executed.

The resident program 30 includes a second network connection module 32, an instruction transmission module 34, a buy/sell signal receiving module 36, and a resident program termination module 38. The second network connection module 32 is configured to automatically establish a connection between the HTTP network protocol of the mobile device 10 and the server 12 at a timing. The command delivery module 34 is configured to transmit an automatic query command 16 to the server 12 for querying the buy/sell signal 14. The buy/sell signal receiving module 36 receives the buy/sell signal 14 of the server 12, and stores the received buy/sell signal 14 in a path of a fixed storage buy/sell signal of the mobile device 10 for The buy/sell signal module 26 then generates or updates a buy/sell signal view (not depicted). The resident program termination module 38 is configured to terminate the resident program 30, and the trigger condition is an automatic time switch, for example, the resident program 30 is terminated one hour after the end of the trading day. The resident program termination module 38 can be configured as a selective module.

The present invention will be described with reference to FIG. 1B, which is automatically established by the network connection module 182 by a financial transaction software 18 of the mobile device 10 at a fixed time (for example, every 30 seconds). The HTTP connection is followed by an automatic inquiry command 16 to the server 12 to download the buy/sell signal 14. The present invention is implemented by the resident program 30 of the mobile device 10, and the HTTP connection is automatically established by the second network connection module 32 in the resident program 30 for a fixed time (for example, every 30 seconds). 16 to the server 12 side to download the buy/sell signal 14. The difference between the present invention and the prior art 2 is that the network connection is processed by a separate resident program 30 and the buy/sell signal 14 is downloaded, even if the financial transaction software 20 is closed immediately after execution, via the resident program startup module 28 The activated resident program 30 can continue to receive the buy/sell signal 14.

The second network connection module 32 of the resident program 30, which is responsible for processing the network connection, and the first network connection module 22 of the financial transaction software 20, which are two independent modules, do not mutually coherent. The second network connection module 32 of the resident program 30 establishes a network connection by using an HTTP protocol, and the first network connection module 22 of the financial transaction software 20 does not need to cooperate with the second network of the resident program 30. The road connection module 32 uses the same communication protocol. That is, the first network connection module 22 in the financial transaction software 20 can adopt an HTTP communication protocol or a TCP communication protocol.

Next, the financial transaction software of the embodiment of the present invention automatically receives the buy/sell signal flow. Since the resident program 30 of the present invention is independent of the financial transaction software 20, the financial transaction software automatically receives the buy/sell signal. The process must be cut into two separate sections. Hereinafter, the description will be made on the fifth and fifth views.

FIG. 5A is a flow chart (1) of the financial transaction software automatically receiving the buy/sell signal according to the embodiment of the present invention, which illustrates the operation flow of the financial transaction software 20, please refer to FIG. 4, which includes the following steps:

Step 301: Start (Financial Transaction Software 20 is executed); the user executes the Financial Transaction Software 20 on the mobile device 10 (cf. Step 101 of Figure 3A).

Step 302: Start the resident program; after executing the financial transaction software 20, the resident program launch module 28 activates the resident program 30 to receive the buy/sell signal 14. Please refer to Figure 5B for the procedure of resident program 30.

Step 303: Whether to close the software; after starting the resident program 30, the user does not need to open the financial transaction software 20 all the time to receive the buy/sell signal 14. If the user chooses to close the financial transaction software 20, then the process goes to step 304, and if the user continues to operate the financial transaction software, then the process goes to step 305.

Step 304: End; the financial transaction software 20 terminates operation, releasing the hardware resources (CPU operation and memory occupation capacity) of the mobile device 10 originally occupied by the financial transaction software 20.

Step 305: Whether there is a buy/sell signal; if the buy/sell signal receiving module 36 of the resident program 30 has downloaded the buy/sell signal 14, then skip to step 307, if the resident program 30 buys/sells the signal receiving mode Group 36 has not yet downloaded the buy/sell signal 14 and skips to step 306.

Here, in step 102 of FIG. 3A, the user can switch to the buy/sell signal view (not depicted) by the menu (not depicted) to wait to receive the buy/sell signal 14, or switch to the side of the self-selected quote view (not depicted). Look at the quote information while waiting for the buy/sell signal 14.

Step 306: Waiting for the resident program to download the buy/sell signal; if the resident program 30 has not downloaded the buy/sell signal 14, the user can continue to wait in the buy/sell signal view (not depicted), or close the software (skip to step 304) , or switch to another view (such as a self-selected quote view, not depicted) to view additional information. If the user chooses to switch to another view to view other information, the first network connection module 22 needs to establish a network connection by HTTP or TCP network protocol.

Step 307: Display the buy/sell signal for the order transaction; when the buy/sell signal receiving module 36 of the resident program 30 has downloaded the buy/sell signal 14, the buy/sell signal module 26 updates the buy/sell signal view. (not depicted) information. The user can view the contents of the buy/sell signal 14 (viewed from the buy/sell signal view) and can click on the contents of the buy/sell signal 14 to place an order. For example, the user clicks on the buy signal of one of the financial products, and then the financial transaction software 20 automatically switches to the order transaction view (not depicted), and automatically fills in the code of the financial product, and the user fills in the other The single transaction information includes the quantity and price of the transaction, and the order transaction can be performed (cf. step 103 of Figure 3A).

Next, the operation flow of the resident program 30 will be described. Referring to FIG. 5B, the financial transaction software automatically receives the buy/sell signal flow chart (2) according to the embodiment of the present invention, and the operation flow of the resident program 30 is matched with reference to FIG. 1B and FIG. Figure, which contains the following steps:

Step 401: Start (the resident program is started); after the user executes the financial transaction software 20 in step 301 of the previous process, the financial transaction software 20 starts the resident program 30 to start the process.

Step 402: Establish a network connection and query the buy/sell signal periodically; after the resident program 30 is started, the second network connection module 32 periodically establishes an HTTP network communication protocol between the mobile device 10 and the server 12. Connected. Next, the command delivery module 34 sends an automatic query command 16 to the server 12 to query the buy/sell signal 14. As shown in the upper part of FIG. 1B of the technique (the technology is transmitted by the financial transaction software 18, the automatic inquiry command 16 is transmitted by the resident program 30).

Step 403: Whether there is a buy/sell signal; after sending the automatic inquiry command 16 to the server 12, if the server 12 has a buy/sell signal 14 then skip to step 404, if the server 12 has no buy/sell signal yet 14 Then skip to step 402.

Step 404: Download the buy/sell signal; when the server 12 has the buy/sell signal 14, the buy/sell signal receiving module 36 can download the buy/sell signal 14 (as shown in the lower half of FIG. 1B). And storing to the mobile device 10 a fixed storage buy/sell signal 14 path for the subsequent purchase/sell signal module 26 of the financial transaction software 20 to update the information of the buy/sell signal view.

Step 405: Execute the financial transaction software; after the buy/sell signal receiving module 36 downloads the buy/sell signal 14, the buy/sell signal receiving module 36 preferably generates an icon (not depicted) for notifying The user buy/sell signal 14 has been downloaded and the user can click on the icon to execute the financial transaction software 20. Alternatively, in addition to executing the financial transaction software 20 by the user, the financial transaction software 20 may be automatically activated by the resident program 30 after the download/sell signal 14 is downloaded.

Next, as in the foregoing step 307, after executing the financial transaction software 20, the buy/sell signal module 26 updates the data of the buy/sell signal view (not depicted) and automatically switches to the buy/sell signal view (not depicted). The user can view the contents of the buy/sell signal 14. The user can click the content of the buy/sell signal 14 to place an order transaction, for example, the user clicks on the buy signal of one of the financial products, and then the financial transaction software 20 automatically switches to the order transaction view (not depicted). And the code of the financial product is automatically filled in, and the user fills in the other order transaction information including the transaction quantity and price, and then the order transaction can be performed (cf. step 103 of FIG. 3A).

The above process illustrates the operation of the resident program 30. In addition, the resident program 30 of the embodiment of the present invention can also set the operation of the resident program 30 to be terminated when the specific termination trigger condition is met (cf. step 406 of FIG. 5B). The termination condition of the resident program 30 may be a predetermined termination time length, for example, the resident program 30 is terminated one hour after the end of the current transaction time. Alternatively, a user-terminated option interface (not shown) is provided, and when the user operates the termination option interface, a termination start command is generated and the termination condition is satisfied. The resident program 30 is terminated by the resident program termination module 38 when the termination condition is triggered.

As can be seen from Figures 5A and 5B of the present invention, the resident program 30 of the present invention can continue to receive the buy/sell signal 14 even after the user closes the financial transaction software 20.

In addition, since the resident program 30 of the present invention has a simple function and consumes much less hardware resources (CPU calculation and memory capacity) than the financial transaction software 20, it is suitable for a long time to wait for receiving a buy/sell signal.

The resident service 30 of the present invention has the same meaning and operation mode as the background service provided by the operating system 10 of the mobile device 10. Therefore, the present invention can also replace the resident program 30 with a background service.

In summary, the mobile device financial transaction software buy/sell signal receiving device and method can make the purchase/sell signal receiving work after the order transaction more efficient management of power consumption, when the user performs financial transaction After the software, the financial transaction software can be closed, and the resident program that takes up less hardware resources can be used to process the buying/selling signal receiving operation, so that the user can smoothly operate the mobile device and wait for receiving the buying/selling signal at the same time. Take care of both.

Although the technical content of the present invention has been disclosed in the above preferred embodiments, it is not intended to limit the present invention, and any modifications and refinements made by those skilled in the art without departing from the spirit of the present invention are encompassed by the present invention. The scope of protection of the present invention is therefore defined by the scope of the appended claims.

10. . . Mobile device

12. . . server

14. . . Buy/sell signal

16. . . Automatic query instruction

18. . . See financial trading software

182. . . Network connection module

184. . . Data transfer module

186. . . Buy/sell signal module

20. . . Financial transaction software of the invention

twenty two. . . First network connection module

twenty four. . . Data transfer module

26. . . Buy/sell signal module

28. . . Resident program startup module

30. . . Resident program

32. . . Second network connection module

34. . . Command transmission module

36. . . Buy/sell signal receiving module

38. . . Resident program termination module

Figure 1A shows a schematic diagram of the TCP connection automatic receiving buy/sell signal;

Figure 1B is a schematic diagram of the HTTP connection automatic receiving buy/sell signal;

Figure 2 is a block diagram of the system function of the device;

Figure 3A is a flow chart of the user operation of the financial transaction software automatically receiving the buy/sell signal;

Figure 3B shows the financial transaction software TCP automatic receiving buy/sell signal flow chart;

The 3C figure is a flow chart of the HTTP automatic receiving buy/sell signal of the financial transaction software.

Figure 4 is a block diagram showing the system function of the device of the embodiment of the present invention;

FIG. 5A is a flow chart (1) of automatically receiving a buy/sell signal of a financial transaction software according to an embodiment of the present invention;

FIG. 5B is a flow chart (2) of the financial transaction software automatically receiving the buy/sell signal according to the embodiment of the present invention.

20. . . Financial transaction software of the invention

twenty two. . . First network connection module

twenty four. . . Data transfer module

26. . . Buy/sell signal module

28. . . Resident program startup module

30. . . Resident program

32. . . Second network connection module

34. . . Command transmission module

36. . . Buy/sell signal receiving module

38. . . Resident program termination module

Claims (10)

A mobile device software transaction software buying/selling signal receiving device is applied to a mobile device, the device comprising: a financial transaction software, comprising: a first network connection module, configured to establish or close the mobile device and a network connection between the servers; a data transmission module, when the network connection is established, receiving a data transmitted by the server to the mobile device, and transmitting the mobile device to generate one of the transmissions Data to the server, wherein the received data includes a buy/sell signal; and a resident program launch module; and a resident program that periodically establishes an HTTP network connection between the mobile device and the server, During the establishment of the HTTP network connection, the buy/sell signal is downloaded from the server and stored in the mobile device. The resident program includes: a second network connection module, and the mobile device and the server are periodically established. The HTTP network connection; an instruction transmission module transmits an automatic inquiry command to the server during the establishment of the HTTP network connection; and a buy/sell signal receiving module on the HTTP network Lulian During the establishment, the buy/sell signal transmitted by the server is downloaded, and the buy/sell signal is stored in the mobile device; wherein the resident program startup module starts the resident program after the financial transaction software is executed. The resident program continues to execute after the financial transaction software is closed. The device of claim 1, wherein the financial transaction software further comprises: a buy/sell signal module, and generating a buy/sell signal view according to the buy/sell signal stored by the mobile device. The device of claim 1, wherein the buy/sell signal is selected from the group consisting of: a financial commodity buy signal and a financial commodity sell signal. The device of claim 1, wherein the resident program further comprises: a resident program termination module that terminates the resident program when a termination condition is triggered. The device of claim 4, wherein the termination condition is a predetermined termination time length or a termination initiation command. A mobile device software transaction software buying/selling signal receiving method is applied to a mobile device, comprising the steps of: executing a financial transaction software; the financial transaction software launching a resident program; closing the financial transaction software; and the resident program Receiving a buy/sell signal; wherein the resident program performs the following steps: periodically establishing an HTTP network connection between the mobile device and a server; during the establishment of the HTTP network connection, transmitting an automatic query command to The server downloads a buy/sell signal from the server during the establishment of the HTTP network connection; and stores the buy/sell signal on the mobile device; Among them, the resident program continues to execute after the financial transaction software is closed. The method of claim 6, after receiving the buy/sell signal in the resident program, further comprising the steps of: re-executing the financial transaction software; and the financial transaction software displaying the buy/sell signal. The method of claim 6, wherein the buy/sell signal is selected from the group consisting of: a financial commodity buy signal and a financial commodity sell signal. The method of claim 6, wherein the resident program further performs the step of terminating the resident program when a termination condition is triggered. The method of claim 9, wherein the termination condition trigger is selected from: triggering by a predetermined termination time length or a termination start instruction.