KR101002494B1

KR101002494B1 - Handheld terminal and inquiry method for transaction particulars using the same

Info

Publication number: KR101002494B1
Application number: KR20030075252A
Authority: KR
Inventors: 김용식
Original assignee: 엘지전자 주식회사
Priority date: 2003-10-27
Filing date: 2003-10-27
Publication date: 2010-12-17
Also published as: KR20050040083A

Abstract

The present invention relates to a transaction history inquiry method using a mobile terminal, the method comprising: registering user information with a financial company; Displaying an input window and receiving a transaction history requirement from a user when a transaction history inquiry is requested; Transmitting an inquiry request message to a message server when information input is completed; Receiving, from a message server, transaction history data retrieved by a financial company based on the inquiry request message in the form of a Long Message Service (LMS) message; By sequentially reading the received LMS message to generate a message list linked to the detailed transaction history, it is possible to check the transaction history with the mobile terminal using the long message service (LMS) provided by the mobile communication service .

Description

HANDHELD TERMINAL AND INQUIRY METHOD FOR TRANSACTION PARTICULARS USING THE SAME}

1 is a block diagram of a transaction history inquiry system in an embodiment of the present invention.

2 is an operation flowchart showing a transaction history inquiry process in an embodiment of the present invention.

3 is an exemplary diagram of a transaction history request message structure in FIG.

4 is an exemplary diagram of a transaction history message structure in FIG.

5 is a flowchart illustrating an operation of processing a received message in a mobile terminal according to an embodiment of the present invention.

6 is an exemplary diagram of a received message list in an embodiment of the present invention.

Figure 7 is an illustration of a transaction history display screen in an embodiment of the present invention.

8 is an exemplary view of a detailed transaction history display screen in an embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

110: mobile terminal 120: LMS server

130: Banking Computer System

The present invention relates to a financial transaction service, and more particularly, to a mobile terminal capable of performing transaction history inquiry and a transaction history inquiry method using the same.

Currently, customers who open an account with a financial institution such as a bank want to know when, how and how the deposit and withdrawal of their account was made.

In general, in order to know the details of deposit and withdrawal from one's own account, he / she should visit a financial institution such as a bank with his / her bank account and arrange the account.

This method is inconvenient for the user to visit the financial institution directly.

To improve this, financial institutions such as banks have introduced telebanking services so that customers can check the deposit and withdrawal of their accounts using the ARS method.

However, this method can solve the inconvenience that the user has to visit the financial institution directly, there is a problem that the user can not accurately understand the transaction history when the transaction history is large or complex.

Therefore, in recent years, in order to increase user convenience, a service for providing a transaction history using a mobile communication network has been provided.

That is, in recent years, a method of enabling a user to check his / her transaction history after accessing a financial institution's system on the web by using a mobile communication service is developed by the development of mobile communication technology. In this method, a user subscribes to a service provider and pays a predetermined fee, and the subscriber accesses the financial institution's system on the web and checks the transaction history.

However, in the related art, in order to check the subscriber's account transaction history, the subscriber has to directly access the financial institution's system on the web using the mobile terminal, and the transaction history is large or complicated when the battery capacity is insufficient. When you do not use the service enough disadvantages.

In addition, in the related art, a separate cost must be paid for using the transaction history checking service, which causes a burden on the user.

Therefore, the present invention uses a long message service (LMS) provided in a mobile communication service to improve the disadvantages of the conventional mobile terminal and the invention to be able to receive the transaction details in detail without using the Internet or bank visits The purpose is to provide a transaction history search method.

The present invention provides a transaction history inquiry method using a mobile terminal according to the present invention in order to achieve the above object comprises the steps of: registering user information with a financial company; Displaying an input window and receiving a transaction history requirement from a user when a transaction history inquiry is requested; Transmitting an inquiry request message to a message server when information input is completed; Receiving, from a message server, transaction history data retrieved by a financial company based on the inquiry request message in the form of a Long Message Service (LMS) message; Reading the received LMS message to generate a message list to which detailed transactions are linked;
According to an aspect of the present invention, a portable terminal according to the present invention includes: a display unit which receives an input of transaction details from a user by displaying an input window when a transaction history inquiry is requested; When the input of information is completed, the inquiry request message is transmitted to the message server, and the transaction history data retrieved from the message server based on the inquiry request message is received from the message server in the form of a Long Message Service (LMS) message. It includes a control unit for generating a message list linked to the transaction history based on the LMS message.
In order to achieve the above object, the transaction history inquiry system according to the present invention transmits a transaction history inquiry request requested by the mobile terminal 110 and the mobile terminal 110 to request a transaction history inquiry, A Long Message Service (LMS) server 120 for converting the historical data into an LMS message form and transmitting the LMS message to the portable terminal 110; It includes a bank computer system 130 for transmitting the transaction history data to the LMS server based on the transaction history inquiry request received through the LMS server.

Hereinafter, the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram of a transaction history inquiry system for an embodiment of the present invention. The mobile terminal 110 includes a mobile terminal 110, a long message service (LMS) server 120, and a bank computer system 130.
The bank computer system 130 receives an account number and a password for valid customer authentication from a corresponding customer in order to provide a transaction history inquiry service of an arbitrary user, and registers a password when the transaction inquiry request message is received. When the transaction matches the registered password, the transaction details corresponding to the inquiry period included in the request message are provided.
The mobile terminal 110 displays a window for inputting a bank code, a password, and an inquiry period when a transaction history inquiry is requested by a user, and when a confirmation or transmission button is pressed after the condition item is completed, a tele service ID and a phone number. Transmits an inquiry request message including a message and registers the message list when a message according to the inquiry request is received and displays the transaction details when the message list is selected.
The LMS server 120 reads the inquiry request message from the mobile terminal 110 and transmits the inquiry request message to the computer system 130 of the corresponding bank and converts the transaction history message from the computer system 130 into an LMS type message. To the mobile terminal 110.

The operation and effect of the embodiment of the present invention configured as described above will be described with reference to FIGS.

First, the user must register the user information, that is, the account number to search the transaction details, and the password for validating the inquiry of the legitimate customer in the bank's computer system 130 for the transaction history inquiry service for the account. The password may be the same as the password for deposit and withdrawal, but register a separate number for security.

In this case, the user may request that the computer system 130 automatically transmit the transaction history service to the mobile terminal 110 of the corresponding customer whenever a deposit or withdrawal occurs or at a predetermined period.

In addition, the customer may query the transaction history at any time, rather than automatically receiving the transaction history service. This is described as follows.

When the user wants to inquire a transaction history for a specific account at any time, the user selects a inquiry service menu on the menu screen of the mobile terminal 110. When the inquiry service menu is selected, the controller (not shown) controls the display unit (not shown) so that an input window for requesting transaction details is displayed on the terminal screen. The input window includes an item for inputting a bank code, an account number, a password, and a search period.
In the displayed input window, the user inputs a bank code, an account number, a password, and a search period. Once information input for transaction details is completed, the user sends an inquiry request message by pressing OK or Send button.

In this case, the inquiry request message is configured to include a transaction history request identifier, such as a tele service ID, a mobile phone number, a bank name (or bank code), an account number, a password, and an inquiry period as illustrated in FIG. 3. The transaction service request identifier (Tele service ID) and the mobile phone number are automatically input when the mobile terminal 110 transmits an inquiry request message.

The Long Message Service (LMS) server 120 that receives the inquiry request message reads the inquiry request message. If the transaction service request identifier (Tele service ID) is recognized, the message is regarded as a transaction history inquiry request message, the 'bank code' is checked, and the inquiry request message is transmitted to the bank's computer system ('130' in FIG. 1). To request transaction details.

In this case, the bank computer system 130 checks the 'tele service ID' to determine whether the transaction history inquiry request message, and in the case of the transaction history inquiry request message, checks the 'bank code' and 'account number' for normal transactions. Make sure it's an account. When the check result is confirmed to be a normal trading account, the bank computer system 130 compares the 'password' with a pre-registered password to determine whether it is a legitimate customer inquiry request.

Therefore, if the password is determined to be a legitimate customer, the bank computer system 130 checks the 'inquiry period' and displays the transaction details for the corresponding account within the period, such as the subscriber's telephone number, bank code, and transaction details. The data is converted into data having a predetermined format, and transmitted to the LMS server 120.

The LMS server 120 checks the subscriber's mobile terminal telephone number in the transaction history data, converts the transaction history data into an LMS message, and transmits the transaction history data to the mobile terminal 110.

At this time, the controller of the mobile terminal 110 reads the message transmitted from the LMS server 120, records the message in the message list, and keeps the message in the message inbox.

Accordingly, when the user opens the message inbox on the mobile terminal 110 and selects 'Uri Bank' from the message list displayed as shown in the example of FIG. 6, the controller displays the transaction details as shown in the example of FIG. 7 on the display unit. In addition, when the user selects an arbitrary detail in the displayed transaction details, the control unit displays the corresponding detail in the example of FIG. 8.
In the above process, the transaction history check uses the link function of the LMS message. That is, when the LMS message is received, the user's portable terminal 110 displays transaction history data on the terminal screen in the same process as that of FIG.

As described in detail above, the present invention can check the details in real time when it is necessary to check the bank deposit and withdrawal in real time by checking the transaction history with the mobile terminal without using the Internet or visiting the bank using the long message transmission provided to the mobile terminal. There is an effect that gives convenience and satisfaction to the user.

Claims

Registering user information with a financial company;

Displaying an input window and receiving a transaction history requirement from a user when a transaction history inquiry is requested;

Constructing an inquiry request message including the input transaction history requirement and transmitting the message to a message server;

Receiving a long message service (LMS) message from the message server, the LMS message including transaction history data searched based on the inquiry request message by the financial company;

Reading the LMS message received from the message server to generate a message list linked to detailed transactions;

If the message list is selected, displaying a detailed transaction list linked to the corresponding message on a screen;

Receiving the LMS message

When the message server receives a transaction history request message from the mobile terminal, transmitting the transaction history request message to a financial related company identified by a bank code included in the transaction history request message;

If the transaction history data corresponding to the transaction history request message is received from the financial company system, converting the transaction history data into an LMS type message;

And transmitting the converted LMS message to the mobile terminal.

The method of claim 1, wherein the user information is

Transaction history inquiry method using a mobile terminal, characterized in that it comprises a bank account number and a password for authentication.

The method of claim 1, wherein the transaction requirement is

Transaction history inquiry method using a mobile terminal, comprising a bank name, account number, password and inquiry period.

The method of claim 1, wherein the inquiry request message

Transaction history request method using a mobile terminal, characterized in that it comprises a transaction history request identifier, telephone number, bank code, account number, password and inquiry period.

delete

The method of claim 1, wherein receiving the LMS message is

Checking a transaction history request identifier of the message and determining whether the message is a transaction history request message when a predetermined message is received from the message server;

If the message is a transaction history request message, checking a bank code and an account number to determine whether a normal transaction account;

If the account is confirmed as a normal trading account, comparing the password to determine whether the request of the legitimate customer, and further comprising the step of transmitting the transaction history data including the subscriber's telephone number, bank code and transaction history to the message server Transaction history inquiry method using a mobile terminal.

A display unit which displays an input window when a transaction history inquiry is requested and receives a transaction history requirement from a user;

The inquiry request message including the input transaction history requirement is configured and transmitted to a message server, and the transaction history data retrieved from the message server based on the inquiry request message is a LMS message. It includes a control unit for receiving and displaying in the form,

When the message server receives a transaction history request message from the mobile terminal, the bank server checks a bank code included in the transaction history request message and transmits the transaction history request message to a financial company, and requests the transaction history from the financial company. A mobile terminal comprising receiving transaction history data corresponding to a message and converting the transaction history data into a Long Message Service (LMS) message.

The method of claim 8, wherein the control unit

And a message list in which detailed transaction details are linked by reading the received LMS message.

The method of claim 8, wherein the transaction requirement is

A mobile terminal comprising a bank name, account number, password and inquiry period.

The method of claim 8, wherein the inquiry request message

A mobile terminal comprising a transaction history request identifier, a telephone number, a bank code, an account number, a password, and an inquiry period.

The method of claim 8, wherein the control unit

And when the message list is selected, displaying a detailed transaction list linked to the corresponding message on the screen.

delete

The method of claim 8, wherein the financial company

When a predetermined message is received from the message server, the transaction history request identifier is checked in the message to determine whether the message is a transaction history request message.

If the message is a transaction request message, check the bank code and account number to verify that it is a normal trading account.

When the account is confirmed to be a normal trading account, comparing the password to determine whether a legitimate customer inquiry request, and a mobile terminal, characterized in that for transmitting the transaction data including the subscriber's telephone number, bank code and transaction history to the message server.