TWM540336U - Corporate mobile banking system - Google Patents

Description

Corporate mobile banking system

This creation involves a mobile banking system, in particular the corporate mobile banking system.

With the development and advancement of technology, the wide application of electronic materials has made enterprises face more severe challenges. In order to cope with the ever-changing living environment, enterprises must process and control all kinds of materials in the shortest time. Therefore, computerized data is gradually realized to enhance the competitiveness of enterprises.

As a general business, "signing" has always been a very important job in daily operations. Almost all the things inside and outside the enterprise can't be related to the "signing". Because of this, the signing of the signing task must cover all the organizational levels of the enterprise, and the task processes and rules implied in it. Content editing, sending and receiving, processing and other issues are quite complicated. Therefore, through electronic operations, the manpower is reduced and the time required for the process is reduced, so that the person who wants to sign the approved documents can directly transfer the electronic documents to the relevant supervisors on the internal network or even through the Internet connection. . Especially for enterprises who want to conduct bank-related electronic transaction business, due to the limited daily business hours of the bank, the signing of electronic transaction related documents has absolute urgency and oppression in terms of time.

However, for high-level executives who often need to go out to perform business, they often go out busy and often cannot stay in the office to review and process each electronic transaction related document to be signed one by one. When the signing of electronic transaction related documents is slightly delayed, The impact is quite large.

In summary, how to improve the timeliness of documents related to signing electronic transactions, and thus effectively improve the efficiency of enterprises, is an urgent problem for the relevant industry.

This work exposes a corporate mobile banking system.

First, the present disclosure discloses a corporate mobile banking system for outputting transaction authentication information to a bank back-office system. The corporate mobile banking system includes: an internal auditing device and a mobile terminal device. The internal auditing device has a built-in first application for receiving the transaction request data and performing an auditing process. When the transaction request data is approved, the internal auditing device outputs the transaction release data, wherein the transaction release data includes the bank public key and the enterprise private Key, payee information and transaction content. The mobile terminal device has a second application built in the network, and is connected to the first application by the network to receive the transaction release data sent by the internal audit device, and after the release program, the transaction authentication data is output to the bank back-end system. The transaction authentication data includes the bank public key, the payee data, the transaction content, the enterprise private key, and the terminal private key.

Next, the present disclosure discloses another corporate mobile banking system for outputting transaction authentication information to the bank back-office system. The corporate mobile banking system includes: an internal auditing device and a plurality of mobile terminal devices. The internal auditing device has a built-in first application for receiving the transaction request data and performing an auditing process. When the transaction request data is approved, the internal auditing device outputs the transaction release data, wherein the transaction release data includes the bank public key and the enterprise private Key, payee information and transaction content. Each mobile terminal device has a second application built in and communicates with the first application through a network. The plurality of mobile terminal devices simultaneously receive the transaction release data sent by the internal auditing device, and when one of the plurality of mobile terminal devices completes the release program, the mobile terminal device that completes the release program uses the network Outputting the transaction authentication data to the bank back-end system and outputting the data to other mobile terminal devices that are not performing the release program or the mobile terminal device that is performing the release program, wherein the transaction authentication data includes the bank public key, the enterprise private key, Payee information, transaction content and terminal private key.

The system disclosed in the present application is as above, and the difference from the prior art is that the creation is to output the transaction release data after reviewing the transaction request data through the internal review device of the built-in first application, and to utilize the mobile terminal with the built-in second application. The device communicates with the first application by the network to receive the transaction release data, and outputs the transaction authentication information including the bank public key, the enterprise private key, the payee data, the transaction content and the terminal private key after the release process. Bank back office system.

Through the above technical means, this creation achieves the technical effect of the remote authority to sign the electronic transaction.

50, 52‧‧‧ network

100, 500‧‧‧Corporate Mobile Banking System

200‧‧‧Bank back office system

110, 510‧‧‧ editing device

120, 520‧‧‧ internal auditing device

122‧‧‧Monitoring unit

124‧‧‧ storage unit

126‧‧‧Message Notification Unit

128‧‧‧Voice dialing unit

129‧‧‧ Instant messaging unit

130, 132‧‧‧ mobile terminal devices

530, 532, 534‧‧‧ mobile terminal devices

Step 210‧‧‧ outputting the transaction request data by using the third application built in the editing device, In the transaction request data, the transaction content and the payee data are included.

Step 220‧‧‧ Receive the transaction request data and perform the review process using the first application built into the internal audit device

Step 230‧‧‧ When the transaction request data is approved, the first application built in the internal auditing device outputs the transaction release data, wherein the transaction release data includes the bank public key, the enterprise private key, the payee data and the transaction content.

Step 240‧‧‧using the second application built in the mobile terminal device to communicate with the first application by the network to receive the transaction release data sent by the internal audit device

Step 250‧‧‧ outputting the transaction authentication data to the bank back-end system by using the second application built in the mobile terminal device, wherein the transaction authentication data includes the bank public key, the payee data, the transaction content, and the enterprise private key And terminal private key

Step 310‧‧‧Using the storage unit to store the phone number of the mobile terminal device

Step 320‧‧‧Using the monitoring unit to receive the read signal

Step 330‧‧‧ When the monitoring unit does not receive the read signal within the first predetermined time, the internal auditing device determines that the mobile terminal device does not receive the transaction release data

Step 340‧‧‧ When the internal auditing device determines that the mobile terminal device does not receive the transaction release data, the message notification unit transmits the notification message to the mobile terminal device by using the telephone number or dials the telephone number by using the voice dialing unit until the mobile terminal device is turned on. And play voice messages when the mobile terminal device is connected

Step 350‧‧‧ After the waiting time, the monitoring unit still does not receive the read signal, and the message notification unit continues to send the notification message to the mobile terminal device by using the telephone number or The voice dialing unit continues to dial the telephone number until the mobile terminal device is turned on, and the voice message is played when the mobile terminal device is turned on.

Step 360‧‧‧ When the internal auditing device determines that the mobile terminal device has not received the transaction release data, the internal auditing device transmits the transaction release data to another mobile terminal device

Step 370‧‧‧ After the waiting time, the monitoring unit has not received the read signal, and the internal auditing device transmits the transaction release data to another mobile terminal device.

Step 410‧‧‧Using the monitoring unit to receive the read signal and the release signal

Step 420‧‧‧ When the monitoring unit receives the read signal within the first predetermined time and does not receive the release signal within the second predetermined time after receiving the read signal, the internal review device determines that the mobile terminal device receives the transaction release data Release procedure not in the second predetermined time

Step 430‧‧‧ When the internal auditing device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data, the message notification unit transmits the notification message to the mobile terminal device by using the telephone number or dials by voice The unit dials the phone number until the mobile terminal device is turned on, and the voice message is played when the mobile terminal device is turned on.

Step 440‧‧‧ After the waiting time, the monitoring unit still does not receive the read signal, and the message notification unit continues to send the notification message to the mobile terminal device by the telephone number or continues to dial the telephone number by using the voice dialing unit until the mobile terminal device is turned on. And play voice messages when the mobile terminal device is connected

Step 450‧‧‧ When the monitoring unit still does not receive the release signal after the waiting time, the internal auditing device transmits the transaction release data to another mobile terminal device

Step 460‧‧‧ When the internal auditing device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data, the instant messaging unit transmits the notification message to the mobile terminal device via the network

Step 470‧‧‧ When the internal auditing device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data, the internal auditing device transmits the transaction release data to another mobile terminal device

Step 610‧‧‧ outputting the transaction request data by using the third application built in the editing device, wherein the transaction request data includes the transaction content and the payee data

Step 620‧‧‧ Receive the transaction request data and perform the review process using the first application built into the internal audit device

Step 630‧‧‧ When the transaction request data is approved, the first application built in the internal auditing device outputs the transaction release data, wherein the transaction release data includes the bank public key, the enterprise private key, the payee data and the transaction content.

Step 640‧‧‧ Using three mobile terminal devices with built-in second application and communicating with the first application to simultaneously receive the transaction release data sent by the first application built in the internal auditing device through the network

Step 650‧‧‧ When one of the three mobile terminal devices uses a second application to complete a release procedure, the mobile terminal device that completes the release program outputs the transaction authentication data to the bank backend system via the network and The road output completion information is sent to other mobile terminal devices that are not performing the release procedure or the mobile terminal device that is performing the release procedure, wherein the transaction authentication data includes the bank public key, the payee data, the transaction content, the enterprise private key, and the terminal private key.

Figure 1 is a block diagram of an embodiment of an authoring corporate mobile banking system.

Figure 2 is a flow chart showing the execution method of the corporate mobile banking system of Figure 1.

Figure 3 is a block diagram of another embodiment of a creative corporate mobile banking system.

Figure 4 is a flow chart showing the execution method of the first embodiment of the corporate mobile banking system of Figure 3.

Figure 5 is a flow chart showing the execution method of the second embodiment of the corporate mobile banking system of Figure 3.

Figure 6 is a flow chart showing the execution method of the second embodiment of the corporate mobile banking system of Figure 3.

Figure 7 is a flow chart showing the execution method of the fourth embodiment of the corporate mobile banking system of Figure 3.

Figure 8 is a flow chart showing the execution method of the fifth embodiment of the corporate mobile banking system of Figure 3.

Figure 9 is a flow chart showing the execution method of the sixth embodiment of the corporate mobile banking system of Figure 3.

Figure 10 is a flow chart showing the execution method of the seventh embodiment of the corporate mobile banking system of Figure 3.

Figure 11 is a system block diagram of still another embodiment of the authoring enterprise mobile banking system.

Figure 12 is a flow chart showing the execution method of the enterprise mobile banking system of Figure 11.

The embodiments of the present invention will be described in detail below with reference to the drawings and the embodiments, so that the implementation process of how to apply the technical means to solve the technical problems and achieve the technical effects can be fully understood and implemented.

Before describing the corporate action banking system and its implementation method disclosed in this creation, the nouns defined by the creation itself are explained. The devices and units included in the enterprise mobile banking system described in this creation can be implemented in various ways. Including software, hardware, firmware or any combination thereof. For example, in some embodiments, the editing device can be implemented using software and/or hardware, and the scope of the present invention is not limited in this respect. The techniques used in the implementation of the software or firmware can be stored on a machine readable storage medium, such as read only memory (ROM), random access memory (RAM), disk storage media, optical storage media, fast. A flash memory device or the like, and can be executed by one or more general purpose or special purpose programmable microprocessors. The editing device, internal auditing device and mobile terminal device included in the enterprise mobile banking system described in the present invention can be connected to each other through a network such as a mobile communication network, an internet, a local area network, a wide area network, and/or a wireless network. . The transmission of signals and data can be performed between the editing device, the internal auditing device, and any of the mobile terminal devices using copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers.

In addition, the editing device disclosed in the present application may be, but not limited to, a desktop computer, a notebook computer, or a tablet computer, and is disposed at a corporate office. The number of the editing devices may be, but not limited to, one, and may be adjusted according to actual needs. The internal auditing device disclosed in this creation can be, but is not limited to, a desktop computer, a notebook computer or a tablet computer, and its configuration location is located in the office of the enterprise. room. The number of internal auditing devices may be, but not limited to, one, and may be adjusted according to actual needs. It should be noted that considering the security of electronic transactions, the number of internal auditing devices should not be too large. The mobile terminal device disclosed in the present application may be, but not limited to, a portable electronic device such as a smart phone, a tablet computer, a palmtop computer or a mobile Internet device (MID), and the location may be located outside the office of the enterprise. The information communication is performed by the network and the editing device located in the office of the enterprise, the internal auditing device and the bank back-office system. The number of the mobile terminal devices may be, but not limited to, one, and may be adjusted according to actual needs. It should be noted that the number of mobile terminal devices should not be too large based on the consideration of transaction security. The storage unit disclosed in the present application can be a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), static random. Access memory (SRAM), portable compact disk read-only memory (CD-ROM), memory stick, floppy disk, mechanical encoding device, for example, a punch card or groove in which a command is stored Structure, and any suitable combination of the above.

The following is a description of the creative corporate mobile banking system and its implementation method. Please refer to "Figure 1" first. "Figure 1" is a system block diagram of an embodiment of the creative corporate mobile banking system. The enterprise mobile banking system 100 is configured to output transaction authentication information to the bank backend system 200. The enterprise mobile banking system 100 includes an editing device 110, an internal auditing device 120, and a mobile terminal device 130.

The editing device 110 has a built-in third application for outputting the transaction request data, wherein the transaction request data includes the transaction content and the payee data, and the transaction content may include the transaction type, the transaction time, and the transaction amount, and the payee data may include The payee's account name and account number, the payee may be a legal or natural person. In more detail, the enterprise grassroots employee can use the third application built in the editing device 110 to input the transaction content and the payee data to establish the transaction request data. After that, the enterprise grassroots employees use the third application to output the transaction request data through the network 50 to the internal review package. Set 120. After the editing device 110 outputs the transaction request data, the third application can send the push message to the internal auditing device 120 to notify the staff responsible for reviewing the transaction request data to perform the subsequent review process, but the embodiment is not used. Limit this creation.

The internal auditing device 120 has a built-in first application, and is connected to the third application by the network 50 to receive the transaction request data and perform an auditing process. When the transaction request data is approved, the internal auditing device 120 outputs the transaction. Release information, wherein the transaction release data includes the bank public key, the enterprise private key, the payee data and the transaction content, the bank public key can be used to encrypt the payee data and the transaction content, and the enterprise private key can be used for the electronic digital signature. In order to provide the bank with the subsequent confirmation of the electronic transaction of the electronic transaction, the enterprise private key may be, but is not limited to, an enterprise private key that the enterprise uses the business certificate to register with the certificate authority (CA), but this embodiment is not used. Limit this creation.

In more detail, after the staff member responsible for reviewing the transaction request information receives the push message through the first application built in the internal audit device 120 (ie, the editing device 110 has output the transaction request data), the internal audit device 120 is built in. The first application receives the transaction request data and performs an audit process. The review procedure may be to confirm the transaction content, the payee data, and the account of the enterprise at a specific bank and the amount thereof, and determine whether the transaction content is feasible, but the embodiment is not intended to limit the creation. When the employee responsible for reviewing the transaction request data confirms that the transaction request information is correct and feasible (ie, the transaction request data is approved), the employee responsible for reviewing the transaction request data utilizes the first application built in the internal auditing device 120 by using the public key. The digital certificate of the Public Key Infrastructure (PKI) and the security bearer of the private key of the enterprise obtain the signature of the transaction request data by the enterprise private key, and encrypt the transaction content and the payee data by using the bank public key of the specific bank. The transaction release data is created, and the transaction release data is output to the mobile terminal device 130 via the network 50. Among them, the specific bank is The bank that conducts the electronic transaction. In this embodiment, the security bearer of the PKI-based digital certificate and the enterprise private key may be, but not limited to, a USB (Universal Serial Bus) Key, but this embodiment is not intended to limit the present creation. For example, the PKI-based digital certificate and the private key of the enterprise private key may be a hard disk storing a digital certificate and an enterprise private key.

In this embodiment, since the CA issues a digital certificate combined with the public key of the enterprise when the enterprise uses the business certificate to register, and the public certificate is stored in the public database, the bank can obtain the enterprise public key through the public database. When the bank obtains the information with the private key of the enterprise for signature encryption, the enterprise public key can be used to decrypt the data and perform the identity authentication of the enterprise.

The mobile terminal device 130 has a second application built in the network, and is connected to the first application by the network 50 for receiving the transaction release data sent from the internal review device 120, and outputting the transaction authentication data to the bank background after the release process. The system 200, wherein the transaction authentication data includes a bank public key, a payee data, a transaction content, an enterprise private key, and a terminal private key, and the terminal private key may be, but is not limited to, an enterprise using the financial extensible markup language (Financial Extensible) Markup Language, FXML) The private key when the electronic signature is registered with the voucher website of a particular bank and is bound to the mobile terminal device 130, and can be used to provide the bank for identity authentication of the enterprise.

In more detail, the supervisor who finally determines whether the electronic transaction is released or not uses the second application built in the mobile terminal device 130 to receive the transaction release data sent from the internal review device 120 via the network 50, and performs the release procedure. The release procedure may be to reconfirm the transaction content, the payee data, and the account of the enterprise at a specific bank and the amount thereof, and determine the feasibility of the transaction content, but this embodiment is not intended to limit the creation. When the supervisor who finally determines whether the electronic transaction is released confirms that the transaction release information is correct and feasible, the supervisor who finally determines whether the electronic transaction is released is signed with the terminal private key bound to the mobile terminal device 130, and is signed by the network. Road 50 outputs transaction authentication information to the bank back office System 200. The transaction authentication data includes a bank public key, a payee data, a transaction content, an enterprise private key, and a terminal private key, and the bank public key can be used to encrypt the payee data and the transaction content, and the enterprise private key and the terminal private key can be used to perform The electronic digital signature is encrypted to provide the bank with the identity of the enterprise for subsequent electronic transactions.

In this embodiment, since the specific bank stores the terminal public key in the database when the enterprise uses the FXML electronic signature for registration, the specific bank can obtain the terminal public key through the database. When a specific bank obtains the information with the terminal private key for signature encryption, the terminal public key can be used to decrypt the data and perform identity authentication of the enterprise. In this embodiment, the specific identity of the enterprise that can use the enterprise private key and the terminal private key to perform the electronic transaction can enhance the security of the electronic transaction.

After the bank backend system 200 receives the transaction authentication data, the bank private key is used to decrypt the payee data and the transaction content, so as to obtain the payee data and the transaction content, and confirm the electronic transaction by the enterprise public key and the terminal public key. Corporate identity certification. Thereafter, the bank backend system 200 processes the electronic transaction based on the payee profile, the identity of the business, and the transaction content.

Next, please refer to "Figure 2", "Figure 2" is the flow chart of the implementation method of the Corporate Mobile Banking System of "Figure 1". The steps include: using the third application built into the editing device to use the network. Corresponding to the first application built in the internal auditing device to output the transaction request data, wherein the transaction request data includes the transaction content and the payee data (step 210); and the first application built in the internal auditing device is used to receive Transmitting the request data and performing the review process (step 220); when the transaction request data is approved, the first application built in the internal auditing device outputs the transaction release data, wherein the transaction release data includes the bank public key, the enterprise private key, The payee data and the transaction content (step 230); the second application built in the mobile terminal device is connected to the first application by the network to receive the transaction release data sent by the internal audit device (step 240) ; and use mobile The second application built in the terminal device outputs the transaction authentication data to the bank back-end system after the release program, wherein the transaction authentication data includes the bank public key, the payee data, the transaction content, the enterprise private key and the terminal private key (step 250) ). Through the above steps, the internal release device of the built-in first application can output the transaction release data after reviewing the transaction request data, and communicate with the first application through the network by using the mobile terminal device with the built-in second application. Connected to receive the transaction release data, and after the release program, output the transaction authentication data including the bank public key, the enterprise private key, the payee data, the transaction content and the terminal private key to the bank back-end system.

Please refer to "Figure 3". "Figure 3" is a system block diagram of another embodiment of the Creative Enterprise Mobile Banking System. In this embodiment, the internal auditing device 120 can include a monitoring unit 122, a storage unit 124, a message notifying unit 126, a voice dialing unit 128, and an instant messaging unit 129. The storage unit 124 is configured to store the phone number of the mobile terminal device 130.

The monitoring unit 122 is configured to receive the read signal and the release signal. The internal auditing device 120 determines whether the mobile terminal device 130 receives the transaction release data by using the monitoring unit 122 to receive the read signal within the first predetermined time; and whether the monitoring unit 122 receives the second predetermined time after receiving the read signal. The release signal is used to determine whether the mobile terminal device 130 performs the release procedure within the second predetermined time after receiving the transaction release data. The first predetermined time may be, but not limited to, three minutes or five minutes, and the second predetermined time may be, but not limited to, five minutes or ten minutes, and the length of the first predetermined time and the second predetermined time may be adjusted according to actual needs. The read signal is the signal returned by the network 50 after the mobile terminal device 130 receives the transaction release data, and the release signal is the signal returned by the network 50 after the mobile terminal device 130 outputs the transaction authentication data.

When the monitoring unit 122 receives the read signal within the first predetermined time, the internal auditing device 120 determines that the mobile terminal device 130 receives the transaction release data; when the monitoring unit 122 is not at the first predetermined time When receiving the read signal in between, the internal auditing device 120 determines that the mobile terminal device 130 has not received the transaction release data. When the monitoring unit 122 receives the release signal within the second predetermined time after receiving the read signal, the internal auditing device 120 determines that the mobile terminal device 130 receives the transaction release data and then performs the release procedure within the second predetermined time; when the monitoring unit 122 receives The release signal is not received within the second predetermined time after the signal is read, and the internal auditing device 120 determines that the mobile terminal device 130 does not perform the release procedure within the second predetermined time after receiving the transaction release data.

The following describes an embodiment of the processing corresponding to the enterprise mobile banking system 100 when the mobile terminal device 130 is in a different state, but the description of the following embodiments is not intended to limit the present creation.

In the first embodiment, when the monitoring unit 122 does not receive the read signal within the first predetermined time (for example, the internal auditing device 120 has output the transaction release data via the network 50, but the mobile terminal device 130 is located at no network. Where the road signal is unable to receive the transaction release data, the mobile terminal device 130 cannot transmit the read signal via the network 50, and the internal review device 120 determines that the mobile terminal device 130 has not received the transaction release data. When the internal auditing device 120 determines that the mobile terminal device 130 does not receive the transaction release data, the internal review device 120 can use the message notification unit 126 to send a notification message to the mobile terminal device 130 or dial the voice using the phone number stored in the storage unit 124. The unit 128 dials the telephone number until the mobile terminal device 130 is turned on (ie, the mobile terminal device 130 picks up the call), and plays a voice message when the mobile terminal device 130 is turned on to remind the holder of the mobile terminal device 130. (ie the supervisor who finally determines whether the electronic transaction is released) There is a release procedure for the release of the transaction data.

In addition, when the internal auditing device 120 uses the message notifying unit 126 or the voice dialing unit 128 to remind the holder of the mobile terminal device 130 (ie, the supervisor who finally determines whether the electronic transaction is released), the transaction release data needs to be released. After the waiting time, the monitoring unit 122 still does not receive the reading. When the signal is received (for example, the supervisor who finally determines whether the electronic transaction is released knows that the transaction release data needs to be released, but cannot receive the transaction release data through the network 50 in time), the internal review device 120 can continue to utilize the message notification unit 126. Or the voice dialing unit 128 reminds the holder of the mobile terminal device 130 (i.e., the supervisor who finally determines whether the electronic transaction is released) that the transaction release data needs to be released. The waiting time can be, but is not limited to, three minutes or five minutes, and the length of the waiting time can be adjusted according to actual needs. The internal auditing device 120 continuously reminds the holder of the mobile terminal device 130 that the transaction release data needs to be released. The amount that can be applied to the electronic transaction is too large. It must be confirmed by the supervisor who finally determines whether the electronic transaction is released. Whether it can be released, or can be applied to the case where the supervisor who finally determines whether the electronic transaction is released does not have a job agent.

Therefore, please refer to "FIG. 4", and "FIG. 4" is a flowchart of the execution method of the first embodiment of the corporate mobile banking system of "FIG. 3". In the present embodiment, the execution method of the corporate mobile banking system 100 In addition to the step 210 to the step 250, the method further includes the steps of: storing the phone number of the mobile terminal device by using the storage unit (step 310); receiving the read signal by using the monitoring unit (step 320); when the monitoring unit does not receive the first predetermined time When the signal is read, the internal auditing device determines that the mobile terminal device does not receive the transaction release data (step 330); and when the internal auditing device determines that the mobile terminal device does not receive the transaction release data, the message notification unit transmits the notification message to the mobile by using the telephone number. The terminal device dials the telephone number by using the voice dialing unit until the mobile terminal device is turned on, and plays a voice message when the mobile terminal device is turned on (step 340); and after the waiting time, the monitoring unit still does not receive the read signal, and utilizes The message notification unit continues to send a notification message to the mobile terminal device by phone number or dials by voice Membered continue dialing a telephone number of the mobile terminal is turned on until the apparatus, and Bofang voice messages (step 350) to the mobile terminal device is turned on. Unavoided graphics are too complicated, "Figure 4" is not drawn Steps 210 through 250 are made, and it is important to note that the above steps can be performed in any order except for causal relationships.

In the second embodiment, when the monitoring unit 122 does not receive the read signal within the first predetermined time (for example, the internal auditing device 120 has output the transaction release data via the network 50, but the mobile terminal device 130 is located just in the network. Where the road signal is unable to receive the transaction release data, the mobile terminal device 130 cannot transmit the read signal via the network 50, and the internal review device 120 determines that the mobile terminal device 130 has not received the transaction release data. When the internal auditing device 120 determines that the mobile terminal device 130 has not received the transaction release data, the internal auditing device 120 may transmit the transaction release data to another mobile terminal device 132. Wherein, the other mobile terminal device 132 is a mobile terminal device of the duty agent of the supervisor who finally determines whether the electronic transaction is released, so that the enterprise mobile banking system 100 can directly determine whether the electronic transaction is released or not. The agent performs a release procedure to speed up the release of the electronic transaction.

Therefore, please refer to "figure 5", and "figure 5" is a flowchart of a second embodiment execution method of the enterprise mobile banking system of "figure 3". In this embodiment, the execution method of the enterprise mobile banking system 100 In addition to the step 210 to the step 250, the method further includes the following steps: receiving the read signal by using the monitoring unit (step 320); when the monitoring unit does not receive the read signal within the first predetermined time, the internal review device determines that the mobile terminal device does not receive the transaction release. Data (step 330); and when the internal auditing device determines that the mobile terminal device has not received the transaction release data, the internal auditing device transmits the transaction release data to another mobile terminal device (step 360). The unavoidable pattern is too complicated, and the "Fig. 5" does not draw the steps 210 to 250, and it is particularly important to note that the above steps can be performed in any order except for the causal relationship.

In the third embodiment, when the internal auditing device 120 uses the message notifying unit 126 or the voice dialing unit 128 to remind the holder of the mobile terminal device 130 (ie, the supervisor who finally determines whether the electronic transaction is released), there is a need to release the transaction data. After the release procedure is performed, and after the waiting time has elapsed, the monitoring unit 122 still does not receive the read signal (for example, the supervisor who finally determines whether the electronic transaction is released or not knows that the release data needs to be released, but cannot pass through the network in time 50 Receiving the transaction release information, the internal review device 120 may transmit the transaction release data to another mobile terminal device 132, so that the enterprise mobile banking system 100 uses the message notification unit 126 to notify the supervisor that the electronic transaction is finally released or not. After the release procedure is required and after the waiting time, the duty agent of the supervisor who finally determines whether the electronic transaction is released may be directly released to speed up the release of the electronic transaction.

Therefore, please refer to "FIG. 6", and "FIG. 6" is a flow chart of the execution method of the third embodiment of the corporate mobile banking system of "FIG. 3". In this embodiment, the execution method of the corporate mobile banking system 100 In addition to the steps 210 to 250, the method further includes the steps of: storing the phone number of the mobile terminal device by using the storage unit (step 310); receiving the read signal by using the monitoring unit (step 320); and not receiving the reading when the monitoring unit fails within the first predetermined time. When the signal is received, the internal auditing device determines that the mobile terminal device does not receive the transaction release data (step 330); and when the internal auditing device determines that the mobile terminal device does not receive the transaction release data, the message notification unit transmits the notification message to the mobile terminal by using the telephone number. The device either dials the telephone number by using the voice dialing unit until the mobile terminal device is turned on, and plays a voice message when the mobile terminal device is turned on (step 340); and after the waiting time, the monitoring unit still does not receive the read signal, and the internal audit The device transmits the transaction release data to another mobile terminal device (step 370). The unavoidable pattern is too complicated, and the "Phase 6" does not draw the steps 210 to 250, and it is particularly important to note that the above steps can be performed in any order except for the causal relationship.

In the fourth embodiment, when the monitoring unit 122 receives the read signal within the first predetermined time and does not receive the release signal within the second predetermined time after receiving the read signal (for example, whether the electronic transaction is finally determined whether The released supervisor knows that there is a release program for the transaction release data, but is too busy to perform the release procedure in time. The internal review device 120 uses the message notification unit 126 to send the notification message to the mobile terminal device 130 by using the telephone number or to use the voice dialing unit. 128 dials the phone number until the mobile terminal device 130 is turned on (ie, the mobile terminal device 130 picks up the call), and plays a voice message when the mobile terminal device 130 is turned on to urge the final determination of whether the electronic transaction is released. The supervisor speeds up the release process.

In addition, when the internal review device 120 uses the message notification unit 126 or the voice dialing unit 128 to urge the holder of the mobile terminal device 130 to perform the release procedure, and after the waiting time has elapsed, the monitoring unit 122 has not received the read signal (for example: The supervisor who determines whether the electronic transaction is released or not knows that the transaction release data needs to be released, but cannot receive the transaction release information through the network 50 in time), and the internal review device 120 can continue to utilize the message notification unit 126 or the voice call unit 128. The holder of the mobile terminal device 130 (i.e., the supervisor who finally determines whether the electronic transaction is released) has a release program for the transaction release data. The waiting time can be, but is not limited to, three minutes or five minutes, and the length of the waiting time can be adjusted according to actual needs. The internal auditing device 120 continuously reminds the holder of the mobile terminal device 130 that the transaction release data needs to be released. The amount that can be applied to the electronic transaction is too large. It must be confirmed by the supervisor who finally determines whether the electronic transaction is released. Whether it can be released, or can be applied to the case where the supervisor who finally determines whether the electronic transaction is released does not have a job agent.

Therefore, please refer to "FIG. 7", and "FIG. 7" is a flowchart of a method for executing the fourth embodiment of the corporate mobile banking system of "FIG. 3". In this embodiment, the corporate mobile banking system 100 The execution method further includes the following steps: storing the phone number of the mobile terminal device by using the storage unit (step 310); receiving the read signal and releasing the signal by using the monitoring unit (step 410); when the monitoring unit is at the first predetermined Receiving the read signal within the time, and not receiving the release signal within the second predetermined time after receiving the read signal, the internal auditing device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data (step 420); when the internal auditing device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data, the message notification unit transmits the notification message to the mobile terminal device by using the telephone number or dials by using the voice dialing unit. The phone number is not connected to the mobile terminal device, and the voice message is played when the mobile terminal device is turned on (step 430); and after the waiting time, the monitoring unit still does not receive the read signal, and the message notification unit continues to send by the phone number. Notifying the SMS to the mobile terminal device or using the voice dialing unit Continued until the call number of the mobile terminal apparatus is turned on, and Bofang voice messages (step 440) to the mobile terminal device is turned on. The unavoidable pattern is too complicated, and the "Fig. 7" does not draw the steps 210 to 250, and it is particularly important to note that the above steps can be performed in any order except for the causal relationship.

In the fifth embodiment, the monitoring unit 122 receives the read signal within the first predetermined time, and does not receive the release signal within the second predetermined time after receiving the read signal, and transmits the message number by using the message notification unit 126. After notifying the short message to the mobile terminal device 130, after the waiting time, the monitoring unit 122 has not received the release signal (for example, the supervisor who has rushed to determine whether the electronic transaction is released is accelerated to release the program, but finally determines whether the electronic transaction is The released supervisor is still too busy to perform the release procedure in time), and the internal auditing device 120 transmits the transaction release data to the other mobile terminal device 132, so that the corporate mobile banking system 100 uses the message notification unit 126 to promptly determine whether the electronic transaction is released. The supervisor accelerates the release procedure and can wait for the final decision. Whether the electronic transaction is released by the supervisor's job agent to perform the release procedure to speed up the release of the electronic transaction.

Therefore, please refer to FIG. 8 and FIG. 8 is a flowchart of a method for executing the fifth embodiment of the corporate mobile banking system of "FIG. 3". In this embodiment, the execution method of the corporate mobile banking system 100 In addition to the steps 210 to 250, the method further includes the steps of: storing the phone number of the mobile terminal device by using the storage unit (step 310); receiving the read signal and the release signal by using the monitoring unit (step 410); when the monitoring unit is within the first predetermined time Receiving the read signal, and not receiving the release signal within the second predetermined time after receiving the read signal, the internal review device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data (step 420) When the internal auditing device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data, the message notification unit transmits the notification message to the mobile terminal device by using the telephone number or dials the telephone number by using the voice dialing unit. Until the mobile terminal device is turned on, and the voice message is played when the mobile terminal device is turned on (step 430) And when the waiting time monitoring unit after the release signal is not received, the transaction release internal audit means transmit the data to another mobile terminal apparatus (step 450). The unavoidable pattern is too complicated, and the "Fig. 8" does not draw the steps 210 to 250, and it is particularly important to note that the above steps can be performed in any order except for the causal relationship.

In the sixth embodiment, when the monitoring unit 122 receives the read signal within the first predetermined time and does not receive the release signal within the second predetermined time after receiving the read signal (for example, whether the electronic transaction is finalized or not) The released supervisor knows that there is a release program for the release data, but is too busy to perform the release procedure in time. The internal review device 120 uses the instant messaging unit 129 to send a notification message to the mobile terminal device 130 via the network 50 to urge the final determination. The supervisor of whether the electronic transaction is released accelerates the release procedure. Wherein, the instant messaging unit 129 can pass through Facebook, A communication software platform such as a twister, a wechat or a line transmits a notification message to the mobile terminal device 130 via the network 50.

Therefore, please refer to FIG. 9 and FIG. 9 is a flowchart of a method for executing the sixth embodiment of the corporate mobile banking system of FIG. 3, and in this embodiment, the execution method of the corporate mobile banking system 100 In addition to the step 210 to the step 250, the method further includes the following steps: receiving, by the monitoring unit, the read signal and the release signal (step 410); when the monitoring unit receives the read signal within the first predetermined time, and after receiving the read signal, the second When the release signal is not received within the predetermined time, the internal auditing device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data (step 420); and when the internal auditing device determines that the mobile terminal device receives the transaction release data When the release procedure is not performed within the second predetermined time, the notification message is sent to the mobile terminal device via the network using the instant messaging unit (step 460). The unavoidable pattern is too complicated, and the "Fig. 9" does not draw the steps 210 to 250, and it is particularly important to note that the above steps can be performed in any order except for the causal relationship.

In the seventh embodiment, when the monitoring unit 122 receives the read signal within the first predetermined time and does not receive the release signal within the second predetermined time after receiving the read signal (for example, whether the electronic transaction is finally determined whether The released supervisor knows that there is a release program for the transaction release data, but is too busy to perform the release procedure in time. The internal review device 120 transmits the transaction release data to another mobile terminal device 132 so that the corporate mobile banking system 100 can directly request the final A duty agent who determines whether the electronic transaction is released or not is released to speed up the release of the electronic transaction.

Therefore, please refer to FIG. 10, and FIG. 10 is a flowchart of a method for executing the seventh embodiment of the corporate mobile banking system of "FIG. 3". In this embodiment, the execution method of the enterprise mobile banking system 100 In addition to the steps 210 to 250, the method further includes the following steps: receiving the read message by using the monitoring unit And the release signal (step 410); when the monitoring unit receives the read signal within the first predetermined time and does not receive the release signal within the second predetermined time after receiving the read signal, the internal review device determines that the mobile terminal device receives After the transaction release data is not released in the second predetermined time (step 420); and when the internal review device determines that the mobile terminal device does not release the program within the second predetermined time after receiving the transaction release data, the internal review device will trade The release data is transmitted to another mobile terminal device (step 470). The unavoidable pattern is too complicated, and the "Phase 10" does not draw the steps 210 to 250, and it is particularly important to note that the above steps can be performed in any order except for the causal relationship.

Please refer to "Figure 11". "Figure 11" is a system block diagram of another embodiment of the Creative Enterprise Mobile Banking System. The corporate mobile banking system 500 includes an editing device 510, an internal auditing device 520, a mobile terminal device 530, a mobile terminal device 532, and a mobile terminal device 534. In this embodiment, the number of mobile terminal devices may be, but not limited to, three. The holder of the mobile terminal device 530 is the supervisor who determines whether the electronic transaction is released, and the mobile terminal device 532 and the mobile terminal device 534. Some of them are job agents who determine the release of the electronic transaction, but this embodiment is not intended to limit the creation, and can be adjusted according to actual needs. The editing device 510 and the internal auditing device 520 are installed in the office of the enterprise, the mobile terminal device 530 is a portable electronic device, and the location thereof can be an area outside the office of the enterprise, and the editing device 510 and the internal auditing device 520 utilize the network 52. Information communication with the mobile terminal device 530.

The editing device 510 has a built-in third application for outputting the transaction request data, and the editing device 510 is configured to output the transaction request data, wherein the transaction request data includes the transaction content and the payee data. In more detail, the enterprise grassroots employee can use the third application built in the editing device 510 to input the transaction content and the payee data to establish the transaction request data. After that, the grassroots employees of the enterprise should use the third The program sends the transaction request data to the internal auditing device 520 via the network 52. After the editing device 510 outputs the transaction request data, the third application can send the push message to the internal auditing device 520 to notify the staff responsible for reviewing the transaction request data to perform the subsequent review process, but the embodiment is not used. Limit this creation.

The internal auditing device 520 has a built-in first application, and is connected to the third application by the network 52 to receive the transaction request data and perform an auditing process. When the transaction request data is approved, the internal auditing device 520 utilizes the An application outputs transaction release data, wherein the transaction release data includes a bank public key, a corporate private key, a payee data, and a transaction content, and the bank public key certificate can be used to encrypt the payee data and the transaction content, and the enterprise private key certificate is available. In order to confirm the identity of the enterprise that conducts the electronic transaction, the enterprise private key may be, but is not limited to, the enterprise private key certificate when the enterprise applies for the registration with the certificate authority (CA) by using the business certificate, but the embodiment is not intended to limit the creation.

In more detail, after the staff member responsible for reviewing the transaction request information receives the push message through the first application built in the internal audit device 520 (ie, the editing device 510 has output the transaction request data), the internal audit device 520 is built in. The first application receives the transaction request data and performs an audit process. When the employee responsible for reviewing the transaction request data confirms that the transaction request information is correct and feasible (ie, the transaction request data is approved), the employee responsible for reviewing the transaction request data utilizes the first application of the internal auditing device 520 by the PKI-based digital certificate and The security bearer of the enterprise private key obtains the enterprise private key to sign the transaction request data, and encrypts the transaction content and the payee data by using the bank public key of the specific bank to establish the transaction release data, and outputs the data through the network 52. The release information is transmitted to the mobile terminal device 530. Among them, the specific bank is the bank that conducts the electronic transaction.

The mobile terminal device 530, the mobile terminal device 532, and the mobile terminal device 534 all have a second application built in, and can be connected to the first application by the network 52, and the mobile terminal device 530, the mobile terminal device 532, and the mobile terminal Devices 534 are also communicatively coupled to each other by network 52.

The mobile terminal device 530, the mobile terminal device 532, and the mobile terminal device 534 can simultaneously receive the transaction release data sent by the first application of the internal audit device 520 through the built-in second application program, when one of the three mobile terminal devices ( For example, after the mobile terminal device 532) completes the release program by the second application, the mobile terminal device 532 that completes the release program outputs the transaction authentication data to the bank backend system 200 via the network 52 and outputs the completed data through the network 52. Other mobile terminal devices 530 and mobile terminal devices 534 that have not performed the release procedure, or mobile terminal devices 530 and mobile terminal devices 534 that are performing the release procedure, wherein the transaction authentication data includes the bank public key, the payee data, the transaction content, and the enterprise. The private key and the terminal private key are used to notify the mobile terminal device 530 that the release data has been released.

After the bank backend system 200 receives the transaction authentication data, the bank private key certificate is used to decrypt the payee data and the transaction content to obtain the payee data and the transaction content, and the enterprise public key certificate and the terminal public key are confirmed. Corporate identity certification for electronic transactions. Thereafter, the bank backend system 200 processes the electronic transaction based on the payee profile, the identity of the business, and the transaction content.

Next, please refer to "12th picture", "12th picture" is the flowchart of the execution method of the enterprise mobile banking system of "11th picture", and the steps include: outputting the transaction request data by using the third application built in the editing device The transaction request data includes the transaction content and the payee data (step 610); the first application built in the internal auditing device receives the transaction request data, and performs an auditing process (step 620); when the transaction request data is approved At the time, the first application built in the internal auditing device outputs the transaction release data, wherein the transaction release data includes the bank public key, the enterprise private key, and the payment Human data and transaction content (step 630); the mobile terminal device using three built-in second applications and communicating with the first application is simultaneously received by the network from the first application built in the internal audit device Transaction release data (step 640); and when one of the three mobile terminal devices uses a second application to complete a release procedure, the mobile terminal device that completes the release program outputs the transaction authentication data to the bank backend system via the network And outputting the data to the other mobile terminal device that is not performing the release program or the mobile terminal device that is performing the release program by using the network, wherein the transaction authentication data includes the bank public key, the payee data, the transaction content, the enterprise private key, and The terminal private key (step 650). Through the above steps, the release program can be accelerated to output the transaction authentication data including the bank public key, the payee data, the transaction content, the enterprise private key and the terminal private key to the bank back-end system.

In summary, it can be seen that the difference between the present creation and the prior art is that the internal release device outputs the transaction release data after reviewing the transaction request data, and the mobile terminal device receives the transaction release data through the network, and outputs the release program. The transaction authentication information including the bank public key, the payee data, the transaction content, the enterprise private key and the terminal private key is sent to the bank back-office system, and the technical problem can be solved by the prior art, thereby achieving the outgoing supervisor. The technical effect of remote signing of electronic transactions. In addition, the creation enterprise mobile banking system can enable the internal auditing device to determine whether the mobile terminal device receives the transaction release data or whether the mobile terminal device receives the transaction release data and performs the release procedure within the second predetermined time period through the setting of the monitoring unit. When the internal auditing device determines that the mobile terminal device does not receive the transaction release data or the mobile terminal device receives the transaction release data and does not perform the release procedure within the second predetermined time, the message notification unit may be used to transmit the notification message, and the voice dialing unit dials the phone number. Until the mobile terminal device is connected or the instant messaging unit sends a notification message via the network, reminding or urging the supervisor who finally determines whether the electronic transaction is released or not, to speed up the release procedure, or The internal auditing device can directly transmit the transaction release data to another mobile terminal device 132, and let the duty agent perform the release procedure to accelerate the release of the electronic transaction.

Although the present invention is disclosed above in the foregoing embodiments, it is not intended to limit the present invention, and any skilled person skilled in the art can make some changes and refinements without departing from the spirit and scope of the present invention. The scope of patent protection shall be subject to the definition of the scope of the patent application attached to this specification.

50‧‧‧Network

100‧‧‧Corporate Mobile Banking System

200‧‧‧Bank back office system

110‧‧‧Editing device

120‧‧‧Internal auditing device

130‧‧‧Mobile terminal devices

Claims (5)

An enterprise mobile banking system for outputting a transaction authentication data to a bank back office system, the enterprise mobile banking system comprising: an internal auditing device, built in a first application for receiving a transaction request data, and performing a An auditing process, when the transaction request data is approved, the internal auditing device outputs a transaction release data, wherein the transaction release data includes a bank public key, an enterprise private key, a payee data, and a transaction content; a mobile terminal device having a second application built in communication with the first application by a network for receiving the transaction release data sent from the internal review device, and outputting the release program after performing a release program Transaction authentication information is provided to the bank back office system, wherein the transaction authentication data includes the bank public key, the transaction content, the payee data, the enterprise private key, and a terminal private key. According to the corporate action banking system of claim 1, wherein the enterprise mobile banking system further includes an editing device, and a third application is built in, and the network is connected to the first application for output. The transaction request data, wherein the transaction request material includes the transaction content and the payee data. According to the corporate action banking system of claim 1, wherein the internal auditing device comprises a monitoring unit, a storage unit and a message notification unit, the storage unit is configured to store a phone number of the mobile terminal device, the monitoring unit Receiving a read signal, when the monitoring unit does not receive the read signal within a first predetermined time, the internal auditing device determines that the mobile terminal device does not receive the transaction release data, and the message notification unit The phone number sends a notification message to the mobile terminal device. According to the corporate action banking system of claim 1, wherein the internal auditing device comprises a monitoring unit, a storage unit and a message notification unit for storing a telephone number of the mobile terminal device, the monitoring device Receiving a read signal and a release signal, when the monitoring unit receives the read signal within a first predetermined time and does not receive the release signal within a second predetermined time after receiving the read signal And the internal review device determines that the mobile terminal device does not perform the release procedure within the second predetermined time after receiving the transaction release data, and the message notification unit sends a notification message to the mobile terminal device by using the telephone number. An enterprise mobile banking system for outputting a transaction authentication data to a bank back office system, the enterprise mobile banking system comprising: an internal auditing device, built in a first application for receiving a transaction request data, and performing a An auditing process, when the transaction request data is approved, the internal auditing device outputs a transaction release data, wherein the transaction release data includes a bank public key, an enterprise private key, a payee data, and a transaction content; a plurality of mobile terminal devices, each of which has a second application built in and communicated with the first application by a network, the mobile terminal devices simultaneously receiving the same from the internal review device Transaction release data, when one of the mobile terminal devices completes a release procedure, the mobile terminal device that completes the release program outputs the transaction authentication data to the bank backend system via the network and outputs the network through the network Once the information is completed to other mobile terminal devices that have not performed the release procedure or the release procedure is in progress The mobile terminal device, wherein the transaction authentication data bank containing the public key of the transaction, the payee information, the company private with a private terminal.