WO2018221935A1 - Terminal mobile et son procédé de commande - Google Patents

Terminal mobile et son procédé de commande Download PDF

Info

Publication number
WO2018221935A1
WO2018221935A1 PCT/KR2018/006092 KR2018006092W WO2018221935A1 WO 2018221935 A1 WO2018221935 A1 WO 2018221935A1 KR 2018006092 W KR2018006092 W KR 2018006092W WO 2018221935 A1 WO2018221935 A1 WO 2018221935A1
Authority
WO
WIPO (PCT)
Prior art keywords
screen
payment
app
mobile terminal
membership information
Prior art date
Application number
PCT/KR2018/006092
Other languages
English (en)
Inventor
Sookyeong LEE
Hyehyun Kim
Younhwa Choi
Taekon Lee
Original Assignee
Lg Electronics Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Priority to EP18809746.3A priority Critical patent/EP3632091A4/fr
Publication of WO2018221935A1 publication Critical patent/WO2018221935A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G06Q20/40145—Biometric identity checks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/22—Details of telephonic subscriber devices including a touch pad, a touch sensor or a touch detector

Definitions

  • the present invention relates to a mobile terminal and, more particularly, to a mobile terminal capable of implementing a mobile payment function and a method of controlling the same.
  • Mobile terminals have become increasingly more functional. Examples of such functions include data and voice communications, capturing images and video via a camera, recording audio, playing music files via a speaker system, and displaying images and video on a display. Some mobile terminals include additional functionality which supports game playing, while other terminals are configured as multimedia players. More recently, mobile terminals have been configured to receive broadcast and multicast signals which permit viewing of content such as videos and television programs.
  • a portable terminal has installed user authentication information therein and thus has been used for online/offline payment.
  • the portable terminal can be used as a credit card although a separate credit card is not carried.
  • a mobile payment function using the portable terminal may be performed by executing a payment application (hereinafter referred to as an "app").
  • an app a payment application
  • the user has to inconveniently enter a payment screen instead of an app screen that is now used.
  • a user has to inconveniently perform a process of obtaining one-time coupon information (e.g., a barcode degree) and a separate process of deviating from a payment app screen and applying the payment to the obtained coupon information.
  • one-time coupon information e.g., a barcode degree
  • An embodiment of the present invention is to provide a mobile terminal and a method of controlling the same, wherein a mobile payment task can be performed on a pair with a running app task by supporting a quick payment mode in a running app.
  • an embodiment of the present invention is to provide a mobile terminal and a method of controlling the same, which can improve convenience of mobile payment in such a manner that information provided through a running app can be used for a mobile payment function.
  • an embodiment of the present invention is to provide a mobile terminal and a method of controlling the same, wherein a payment function available for a quick payment mode can be selectively applied based on the attributes of information provided through a running app.
  • a mobile terminal includes a touch screen, memory configured to store payment card information used for mobile payment and first membership information supporting saving or a discount when the mobile payment is performed, and a controller configured to display a payment app screen including the payment card information and first membership information stored in the memory on the touch screen when a first input for activating a payment function is received in the state in which any one app execution screen is displayed on the touch screen while at least one app is executed.
  • the controller is configured to perform control so that the payment app screen additionally includes second membership information when the first input is received in the state in which a first app screen including the second membership information not stored in the memory is displayed on the touch screen.
  • the second membership information is extracted from a screen-captured image after the first app screen is captured.
  • the second membership information may include at least one of membership card information for point saving and discount coupon information associated with a product when the mobile payment is performed.
  • the second membership information may include at least one of a discount ratio, barcode, and a number corresponding to the barcode.
  • the controller may be configured to perform control so that the second membership information is displayed on a payment standby screen when user authentication is completed in the state in which the payment app screen is displayed.
  • the second membership information displayed on the payment app screen may be a temporarily stored state.
  • the temporarily stored state of the second membership information may be terminated when payment may be completed on the payment standby screen.
  • the controller may be configured to store the second membership information in the memory in response to a predetermined input.
  • the controller may be configured to display the first membership information and the second membership information having different display characteristics on the payment app screen in order to distinguish between the first membership information and the second membership information.
  • the controller may be configured to indicate an indicator for activating the payment function in a bottom edge area of the first app screen.
  • the first input may include a swipe input to the indicator.
  • the indicator may be previously configured to be displayed on a screen in which a payment app may be executable.
  • the screen in which the payment app is executable may include at least one of a display-off screen, a lock screen, a home screen and an app execution screen executable in the mobile terminal.
  • the controller may be configured to perform a screen capture on the first app screen when the first input is received.
  • the controller may be configured to perform the screen capture on each of execution screens of all apps in which the at least one app is executed in background before the first input is received when the first input is received and to extract second membership information from each of the execution screens of all the apps and perform control so that the extracted second membership information is additionally included in the payment app screen.
  • the controller may be configured to display a screen-captured image of the first app screen on the touch screen when the first input is received, wherein the payment app screen may overlap at least some of the screen-captured image.
  • the screen-captured image may be blurred and displayed. It may be seen that the first app screen and the payment app operate in conjunction with each other due to the blur-processing.
  • the controller may be configured to display an interface for sharing the second membership information with the payment app on the touch screen when a second input to the second membership information included in the first app screen is received and to add the second membership information to the payment app screen.
  • the controller may be configured to analyze the attributes of an item displayed on a second app screen when the first input is received in the state in which the second app screen is displayed on the touch screen and to provide the touch screen with an interface in which the payment app may be used based on the attributes of an item.
  • the attributes of the item may include remittance counterpart information.
  • the controller may be configured to provide the touch screen with an interface capable of quick remittance based on the remittance counterpart information.
  • the attributes of the item may include multimedia content information.
  • the controller may be configured to search for the multimedia content and to enable the multimedia content to be purchased through the payment app.
  • a method of controlling a mobile terminal includes storing payment card information used for mobile payment and first membership information supporting saving or a discount when the mobile payment is performed, receiving a first input for activating a payment function in the state in which any one app execution screen is displayed on the touch screen while at least one app may be executed, and displaying a payment app screen including the payment card information and first membership information stored in the memory on the touch screen.
  • Displaying the payment app screen on the touch screen includes performing control so that the payment app screen additionally includes second membership information when the first input is received in the state in which a first app screen including the second membership information not stored in memory is displayed on the touch screen.
  • the second membership information is extracted from a screen-captured image after the first app screen is captured.
  • a mobile payment task can be performed on a pair with a running app task by supporting the quick payment mode in a running app.
  • convenience of mobile payment can be improved because information provided through a running app can be used for a mobile payment function.
  • a payment function available for the quick payment mode can be selectively applied based on the attributes of information provided through a running app.
  • FIG. 1 is a block diagram of a mobile terminal related to an embodiment of the present invention.
  • FIG. 2 is a diagram showing the configuration of a mobile payment system using the mobile terminal according to an embodiment of the present invention.
  • FIGS. 3 and 4 are flowcharts illustrating a method of controlling the mobile terminal according to a first embodiment of the present invention.
  • FIG. 5 is an example of the configuration of an interface for activating a payment function in a running app screen.
  • FIG. 6 is an example in which the interface for activating the payment function is provided in a running app screen.
  • FIG. 7 is an example of a screen for configuring an environment in which a quick payment mode can be executed according to an embodiment of the present invention.
  • FIG. 8 is an example of a screen configuration for illustrating S100 to S120 of FIG. 3.
  • FIGS. 9A to 9C are examples of screen configurations for illustrating S130 of FIG. 3.
  • FIG. 9D is an example of a screen configuration for illustrating the embodiment of FIG. 4.
  • FIG. 10 is an example of a screen configuration for illustrating a process of temporarily storing second membership information according to a first embodiment of the present invention.
  • FIGS. 11A and 11B are diagrams for illustrating another example in which second membership information is added to a payment app screen in the quick payment mode according to a first embodiment of the present invention.
  • FIG. 12 is a diagram for illustrating yet another example in which second membership information is added to a payment app screen in the quick payment mode according to a first embodiment of the present invention.
  • FIG. 13 is a flowchart illustrating a method of controlling the mobile terminal according to a second embodiment of the present invention.
  • FIGS. 14A to 15B are diagrams for illustrating a method of controlling the mobile terminal according to the second embodiment of the present invention.
  • FIGS. 16 and 17 are diagrams for illustrating examples of payment app screen configurations provided in the quick payment mode according to an embodiment of the present invention.
  • Mobile terminals presented herein may be implemented using a variety of different types of terminals. Examples of such terminals include cellular phones, smart phones, user equipment, laptop computers, digital broadcast terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigators, portable computers (PCs), slate PCs, tablet PCs, ultra books, wearable devices (e.g., smart watches, smart glasses, head mounted displays (HMDs)), and the like.
  • PDAs personal digital assistants
  • PMPs portable multimedia players
  • PCs portable computers
  • slate PCs slate PCs
  • tablet PCs tablet PCs
  • ultra books ultra books
  • wearable devices e.g., smart watches, smart glasses, head mounted displays (HMDs)
  • FIG. 1 is a block diagram of a mobile terminal in accordance with the present disclosure.
  • the mobile terminal 100 is shown having components such as a wireless communication unit 110, an input unit 120, a sensing unit 140, an output unit 150, an interface unit 160, a memory 170, a controller 180, and a power supply unit 190. It is understood that implementing all of the illustrated components is not a requirement, and that greater or fewer components may alternatively be implemented.
  • the mobile terminal 100 is shown having wireless communication unit 110 configured with several commonly implemented components.
  • the wireless communication unit 110 typically includes one or more components which permit wireless communication between the mobile terminal 100 and a wireless communication system or network within which the mobile terminal is located.
  • the wireless communication unit 110 typically includes one or more modules which permit communications such as wireless communications between the mobile terminal 100 and a wireless communication system, communications between the mobile terminal 100 and another mobile terminal, communications between the mobile terminal 100 and an external server. Further, the wireless communication unit 110 typically includes one or more modules which connect the mobile terminal 100 to one or more networks. To facilitate such communications, the wireless communication unit 110 includes one or more of a broadcast receiving module 111, a mobile communication module 112, a wireless Internet module 113, a short-range communication module 114, and a location information module 115.
  • the input unit 120 includes a camera 121 for obtaining images or video, a microphone 122, which is one type of audio input device for inputting an audio signal, and a user input unit 123 (e.g., a touch key, a push key, a mechanical key, a soft key, and the like) for allowing a user to input information.
  • Data e.g., audio, video, image, and the like
  • controller 180 may analyze and process data (e.g., audio, video, image, and the like) according to device parameters, user commands, and combinations thereof.
  • the sensing unit 140 is typically implemented using one or more sensors configured to sense internal information of the mobile terminal, the surrounding environment of the mobile terminal, user information, and the like.
  • the sensing unit 140 is shown having a proximity sensor 141 and an illumination sensor 142.
  • the sensing unit 140 may alternatively or additionally include other types of sensors or devices, such as proximity sensor 141, illumination sensor 142, a touch sensor, an acceleration sensor 144, a magnetic sensor, a G-sensor, a gyroscope sensor 143, a motion sensor, an RGB sensor, an infrared (IR) sensor, a force sensor 145, a finger scan sensor, a ultrasonic sensor, an optical sensor (e.g., camera 121), a microphone 122, a battery gauge, an environment sensor (e.g., a barometer, a hygrometer, a thermometer, a radiation detection sensor, a thermal sensor, and a gas sensor, among others), and a chemical sensor (e.g., an electronic nose, a health care sensor, a biometric sensor, and the like), to name a few.
  • the mobile terminal 100 may be configured to utilize information obtained from sensing unit 140, and in particular, information obtained from one or more sensors of the sensing unit 140, and combinations thereof.
  • the output unit 150 is typically configured to output various types of information, such as audio, video, tactile output, and the like.
  • the output unit 150 is shown having a display unit 151, an audio output module 152, a haptic module 153, and an optical output module 154.
  • the display unit 151 may have an inter-layered structure or an integrated structure with a touch sensor in order to facilitate a touch screen.
  • the touch screen may provide an output interface between the mobile terminal 100 and a user, as well as function as the user input unit 123 which provides an input interface between the mobile terminal 100 and the user.
  • the interface unit 160 serves as an interface with various types of external devices that may be coupled to the mobile terminal 100.
  • the interface unit 160 may include any of wired or wireless ports, external power supply ports, wired or wireless data ports, memory card ports, ports for connecting a device having an identification module, audio input/output (I/O) ports, video I/O ports, earphone ports, and the like.
  • the mobile terminal 100 may perform assorted control functions associated with a connected external device, in response to the external device being connected to the interface unit 160.
  • the memory 170 is typically implemented to store data to support various functions or features of the mobile terminal 100.
  • the memory 170 may be configured to store application programs executed in the mobile terminal 100, data or instructions for operations of the mobile terminal 100, and the like. Some of these application programs may be downloaded from an external server via wireless communication. Other application programs may be installed within the mobile terminal 100 at time of manufacturing or shipping, which is typically the case for basic functions of the mobile terminal 100 (e.g., receiving a call, placing a call, receiving a message, sending a message, and the like). It is common for application programs to be stored in the memory 170, installed in the mobile terminal 100, and executed by the controller 180 to perform an operation (or function) for the mobile terminal 100.
  • the controller 180 typically functions to control overall operation of the mobile terminal 100, in addition to the operations associated with the application programs.
  • the controller 180 may provide or process information or functions appropriate for a user by processing signals, data, information and the like, which are input or output by the various components depicted in FIG. 1, or activating application programs stored in the memory 170.
  • the controller 180 controls some or all of the components illustrated in FIGS. 1A-1C according to the execution of an application program that have been stored in the memory 170.
  • the power supply unit 190 may be configured to receive external power or provide internal power in order to supply appropriate power required for operating elements and components included in the mobile terminal 100.
  • the power supply unit 190 may include a battery, and the battery may be configured to be embedded in the terminal body, or configured to be detachable from the terminal body.
  • the broadcast receiving module 111 is typically configured to receive a broadcast signal and/or broadcast associated information from an external broadcast managing entity via a broadcast channel.
  • the broadcast channel may include a satellite channel, a terrestrial channel, or both.
  • two or more broadcast receiving modules 111 may be utilized to facilitate simultaneously receiving of two or more broadcast channels, or to support switching among broadcast channels.
  • the mobile communication module 112 may transmit and/or receive wireless signals to and from one or more network entities.
  • a network entity include a base station, an external mobile terminal, a server, and the like.
  • Such network entities form part of a mobile communication network, which is constructed according to technical standards or communication methods for mobile communications (e.g., Global System for Mobile Communication (GSM), Code Division Multi Access (CDMA), CDMA2000(Code Division Multi Access 2000), EV-DO(Enhanced Voice-Data Optimized or Enhanced Voice-Data Only), Wideband CDMA (WCDMA), High Speed Downlink Packet access (HSDPA), HSUPA(High Speed Uplink Packet Access), Long Term Evolution (LTE) , LTE-A(Long Term Evolution-Advanced), and the like).
  • Examples of wireless signals transmitted and/or received via the mobile communication module 112 include audio call signals, video (telephony) call signals, or various formats of data to support communication of text and multimedia messages.
  • the wireless Internet module 113 is configured to facilitate wireless Internet access. This module may be internally or externally coupled to the mobile terminal 100. The wireless Internet module 113 may transmit and/or receive wireless signals via communication networks according to wireless Internet technologies.
  • wireless Internet access examples include Wireless LAN (WLAN), Wireless Fidelity (Wi-Fi), Wi-Fi Direct, Digital Living Network Alliance (DLNA), Wireless Broadband (WiBro), Worldwide Interoperability for Microwave Access (WiMAX), High Speed Downlink Packet Access (HSDPA), HSUPA(High Speed Uplink Packet Access), Long Term Evolution (LTE), LTE-A(Long Term Evolution-Advanced), and the like.
  • the wireless Internet module 113 may transmit/receive data according to one or more of such wireless Internet technologies, and other Internet technologies as well.
  • the wireless Internet module 113 when the wireless Internet access is implemented according to, for example, WiBro, HSDPA,HSUPA, GSM, CDMA, WCDMA, LTE, LTE-A and the like, as part of a mobile communication network, the wireless Internet module 113 performs such wireless Internet access. As such, the Internet module 113 may cooperate with, or function as, the mobile communication module 112.
  • the short-range communication module 114 is configured to facilitate short-range communications. Suitable technologies for implementing such short-range communications include BLUETOOTHTM, Radio Frequency IDentification (RFID), Infrared Data Association (IrDA), Ultra-WideBand (UWB), ZigBee, Near Field Communication (NFC), Wireless-Fidelity (Wi-Fi), Wi-Fi Direct, Wireless USB(Wireless Universal Serial Bus), and the like.
  • the short-range communication module 114 in general supports wireless communications between the mobile terminal 100 and a wireless communication system, communications between the mobile terminal 100 and another mobile terminal 100, or communications between the mobile terminal and a network where another mobile terminal 100 (or an external server) is located, via wireless area networks.
  • One example of the wireless area networks is a wireless personal area networks.
  • another mobile terminal (which may be configured similarly to mobile terminal 100) may be a wearable device, for example, a smart watch, a smart glass or a head mounted display (HMD), which is able to exchange data with the mobile terminal 100 (or otherwise cooperate with the mobile terminal 100).
  • the short-range communication module 114 may sense or recognize the wearable device, and permit communication between the wearable device and the mobile terminal 100.
  • the controller 180 when the sensed wearable device is a device which is authenticated to communicate with the mobile terminal 100, the controller 180, for example, may cause transmission of data processed in the mobile terminal 100 to the wearable device via the short-range communication module 114.
  • a user of the wearable device may use the data processed in the mobile terminal 100 on the wearable device. For example, when a call is received in the mobile terminal 100, the user may answer the call using the wearable device. Also, when a message is received in the mobile terminal 100, the user may check the received message using the wearable device.
  • the location information module 115 is generally configured to detect, calculate, derive or otherwise identify a position of the mobile terminal.
  • the location information module 115 includes a Global Position System (GPS) module, a Wi-Fi module, or both. If desired, the location information module 115 may alternatively or additionally function with any of the other modules of the wireless communication unit 110 to obtain data related to the position of the mobile terminal.
  • GPS Global Position System
  • Wi-Fi Wireless Fidelity
  • a position of the mobile terminal may be acquired using a signal sent from a GPS satellite.
  • a position of the mobile terminal may be acquired based on information related to a wireless access point (AP) which transmits or receives a wireless signal to or from the Wi-Fi module.
  • AP wireless access point
  • the input unit 120 may be configured to permit various types of input to the mobile terminal 120. Examples of such input include audio, image, video, data, and user input.
  • Image and video input is often obtained using one or more cameras 121. Such cameras 121 may process image frames of still pictures or video obtained by image sensors in a video or image capture mode. The processed image frames may be displayed on the display unit 151 or stored in memory 170. In some cases, the cameras 121 may be arranged in a matrix configuration to permit a plurality of images having various angles or focal points to be input to the mobile terminal 100. As another example, the cameras 121 may be located in a stereoscopic arrangement to acquire left and right images for implementing a stereoscopic image.
  • the microphone 122 is generally implemented to permit audio input to the mobile terminal 100.
  • the audio input may be processed in various manners according to a function being executed in the mobile terminal 100.
  • the microphone 122 may include assorted noise removing algorithms to remove unwanted noise generated in the course of receiving the external audio.
  • the user input unit 123 is a component that permits input by a user. Such user input may enable the controller 180 to control operation of the mobile terminal 100.
  • the user input unit 123 may include one or more of a mechanical input element (e.g., a key, a button located on a front and/or rear surface or a side surface of the mobile terminal 100, a dome switch, a jog wheel, a jog switch, and the like), or a touch-sensitive input, among others.
  • the touch-sensitive input may be a virtual key or a soft key, which is displayed on a touch screen through software processing, or a touch key which is located on the mobile terminal at a location that is other than the touch screen.
  • the virtual key or the visual key may be displayed on the touch screen in various shapes, for example, graphic, text, icon, video, or a combination thereof.
  • the sensing unit 140 is generally configured to sense one or more of internal information of the mobile terminal, surrounding environment information of the mobile terminal, user information, or the like.
  • the controller 180 generally cooperates with the sending unit 140 to control operation of the mobile terminal 100 or execute data processing, a function or an operation associated with an application program installed in the mobile terminal based on the sensing provided by the sensing unit 140.
  • the sensing unit 140 may be implemented using any of a variety of sensors, some of which will now be described in more detail.
  • the proximity sensor 141 may include a sensor to sense presence or absence of an object approaching a surface, or an object located near a surface, by using an electromagnetic field, infrared rays, or the like without a mechanical contact.
  • the proximity sensor 141 may be arranged at an inner region of the mobile terminal covered by the touch screen, or near the touch screen.
  • the proximity sensor 141 may include any of a transmissive type photoelectric sensor, a direct reflective type photoelectric sensor, a mirror reflective type photoelectric sensor, a high-frequency oscillation proximity sensor, a capacitance type proximity sensor, a magnetic type proximity sensor, an infrared rays proximity sensor, and the like.
  • the proximity sensor 141 may sense proximity of a pointer relative to the touch screen by changes of an electromagnetic field, which is responsive to an approach of an object with conductivity.
  • the touch screen may also be categorized as a proximity sensor.
  • proximity touch will often be referred to herein to denote the scenario in which a pointer is positioned to be proximate to the touch screen without contacting the touch screen.
  • contact touch will often be referred to herein to denote the scenario in which a pointer makes physical contact with the touch screen.
  • the proximity sensor 141 may sense proximity touch, and proximity touch patterns (e.g., distance, direction, speed, time, position, moving status, and the like).
  • controller 180 processes data corresponding to proximity touches and proximity touch patterns sensed by the proximity sensor 141, and cause output of visual information on the touch screen.
  • the controller 180 may control the mobile terminal 100 to execute different operations or process different data according to whether a touch with respect to a point on the touch screen is either a proximity touch or a contact touch.
  • a touch sensor may sense a touch applied to the touch screen, such as display unit 151, using any of a variety of touch methods. Examples of such touch methods include a resistive type, a capacitive type, an infrared type, and a magnetic field type, among others.
  • the touch sensor may be configured to convert changes of pressure applied to a specific part of the display unit 151, or convert capacitance occurring at a specific part of the display unit 151, into electric input signals.
  • the touch sensor may also be configured to sense not only a touched position and a touched area, but also touch pressure and/or touch capacitance.
  • a touch object is generally used to apply a touch input to the touch sensor. Examples of typical touch objects include a finger, a touch pen, a stylus pen, a pointer, or the like.
  • a touch controller When a touch input is sensed by a touch sensor, corresponding signals may be transmitted to a touch controller.
  • the touch controller may process the received signals, and then transmit corresponding data to the controller 180.
  • the controller 180 may sense which region of the display unit 151 has been touched.
  • the touch controller may be a component separate from the controller 180, the controller 180, and combinations thereof.
  • the controller 180 may execute the same or different controls according to a type of touch object that touches the touch screen or a touch key provided in addition to the touch screen. Whether to execute the same or different control according to the object which provides a touch input may be decided based on a current operating state of the mobile terminal 100 or a currently executed application program, for example.
  • the touch sensor and the proximity sensor may be implemented individually, or in combination, to sense various types of touches.
  • Such touches includes a short (or tap) touch, a long touch, a multi-touch, a drag touch, a flick touch, a pinch-in touch, a pinch-out touch, a swipe touch, a hovering touch, and the like.
  • an ultrasonic sensor may be implemented to recognize position information relating to a touch object using ultrasonic waves.
  • the controller 180 may calculate a position of a wave generation source based on information sensed by an illumination sensor and a plurality of ultrasonic sensors. Since light is much faster than ultrasonic waves, the time for which the light reaches the optical sensor is much shorter than the time for which the ultrasonic wave reaches the ultrasonic sensor. The position of the wave generation source may be calculated using this fact. For instance, the position of the wave generation source may be calculated using the time difference from the time that the ultrasonic wave reaches the sensor based on the light as a reference signal.
  • the camera 121 typically includes at least one a camera sensor (CCD, CMOS etc.), a photo sensor (or image sensors), and a laser sensor.
  • a camera sensor CCD, CMOS etc.
  • a photo sensor or image sensors
  • a laser sensor
  • the photo sensor may be laminated on, or overlapped with, the display device.
  • the photo sensor may be configured to scan movement of the physical object in proximity to the touch screen.
  • the photo sensor may include photo diodes and transistors at rows and columns to scan content received at the photo sensor using an electrical signal which changes according to the quantity of applied light. Namely, the photo sensor may calculate the coordinates of the physical object according to variation of light to thus obtain position information of the physical object.
  • the display unit 151 is generally configured to output information processed in the mobile terminal 100.
  • the display unit 151 may display execution screen information of an application program executing at the mobile terminal 100 or user interface (UI) and graphic user interface (GUI) information in response to the execution screen information.
  • UI user interface
  • GUI graphic user interface
  • the display unit 151 may be implemented as a stereoscopic display unit for displaying stereoscopic images.
  • a typical stereoscopic display unit may employ a stereoscopic display scheme such as a stereoscopic scheme (a glass scheme), an auto-stereoscopic scheme (glassless scheme), a projection scheme (holographic scheme), or the like.
  • the audio output module 152 is generally configured to output audio data. Such audio data may be obtained from any of a number of different sources, such that the audio data may be received from the wireless communication unit 110 or may have been stored in the memory 170. The audio data may be output during modes such as a signal reception mode, a call mode, a record mode, a voice recognition mode, a broadcast reception mode, and the like. The audio output module 152 may provide audible output related to a particular function (e.g., a call signal reception sound, a message reception sound, etc.) performed by the mobile terminal 100. The audio output module 152 may also be implemented as a receiver, a speaker, a buzzer, or the like.
  • a haptic module 153 may be configured to generate various tactile effects that a user feels, perceive, or otherwise experience.
  • a typical example of a tactile effect generated by the haptic module 153 is vibration.
  • the strength, pattern and the like of the vibration generated by the haptic module 153 may be controlled by user selection or setting by the controller. For example, the haptic module 153 may output different vibrations in a combining manner or a sequential manner.
  • the haptic module 153 may generate various other tactile effects, including an effect by stimulation such as a pin arrangement vertically moving to contact skin, a spray force or suction force of air through a jet orifice or a suction opening, a touch to the skin, a contact of an electrode, electrostatic force, an effect by reproducing the sense of cold and warmth using an element that may absorb or generate heat, and the like.
  • an effect by stimulation such as a pin arrangement vertically moving to contact skin, a spray force or suction force of air through a jet orifice or a suction opening, a touch to the skin, a contact of an electrode, electrostatic force, an effect by reproducing the sense of cold and warmth using an element that may absorb or generate heat, and the like.
  • the haptic module 153 may also be implemented to allow the user to feel a tactile effect through a muscle sensation such as the user's fingers or arm, as well as transferring the tactile effect through direct contact. Two or more haptic modules 153 may be provided according to the particular configuration of the mobile terminal 100.
  • An optical output module 154 may output a signal for indicating an event generation using light of a light source. Examples of events generated in the mobile terminal 100 may include message reception, call signal reception, a missed call, an alarm, a schedule notice, an email reception, information reception through an application, and the like.
  • a signal output by the optical output module 154 may be implemented in such a manner that the mobile terminal emits monochromatic light or light with a plurality of colors.
  • the signal output may be terminated as the mobile terminal senses that a user has checked the generated event, for example.
  • the interface unit 160 serves as an interface for external devices to be connected with the mobile terminal 100.
  • the interface unit 160 may receive data transmitted from an external device, receive power to transfer to elements and components within the mobile terminal 100, or transmit internal data of the mobile terminal 100 to such external device.
  • the interface unit 160 may include wired or wireless headset ports, external power supply ports, wired or wireless data ports, memory card ports, ports for connecting a device having an identification module, audio input/output (I/O) ports, video I/O ports, earphone ports, or the like.
  • the identification module may be a chip that stores various types of information for authenticating authority of using the mobile terminal 100 and may include a user identity module (UIM), a subscriber identity module (SIM), a universal subscriber identity module (USIM), and the like.
  • the device having the identification module (also referred to herein as an "identifying device") may take the form of a smart card. Accordingly, the identifying device may be connected with the terminal 100 via the interface unit 160.
  • the interface unit 160 may serve as a passage to allow power from the cradle to be supplied to the mobile terminal 100 or may serve as a passage to allow various command signals input by the user from the cradle to be transferred to the mobile terminal there through.
  • Various command signals or power input from the cradle may operate as signals for recognizing that the mobile terminal is properly mounted on the cradle.
  • the memory 170 may store programs to support operations of the controller 180 and store input/output data (e.g., phonebook, messages, still images, videos, etc.).
  • the memory 170 may store data related to various patterns of vibrations and audio which are output in response to touch inputs on the touch screen.
  • the memory 170 may include one or more types of storage mediums including a Flash memory, a hard disk, a solid state disk, a silicon disk, a multimedia card micro type, a card-type memory (e.g., SD or DX memory, etc), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read-Only Memory (ROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Programmable Read-Only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like.
  • the mobile terminal 100 may also be operated in relation to a network storage device that performs the storage function of the memory 170 over a network, such as the Internet.
  • the controller 180 may basically control an overall operation of the mobile terminal 100. For example, the controller 180 may set or release a lock state for restricting a user from inputting a control command with respect to applications when a status of the mobile terminal meets a preset condition.
  • the controller 180 may also perform control and processing associated with voice calls, data communication, and video calls or may perform pattern recognition processing to recognize a handwriting input or a picture drawing input performed on the touch screen as characters or images, respectively.
  • the controller 180 may control one or a combination of those components in order to implement various exemplary embodiments disclosed herein.
  • the power supply unit 190 receives external power or provides internal power and supplies power necessary for operations of the elements included in the mobile terminal 100.
  • the power supply unit 190 may include a battery, which is typically rechargeable or be detachably coupled to the terminal body for charging.
  • the power supply unit 190 may include a connection port.
  • the connection port may be configured as one example of the interface unit 160 to which an external charger for supplying power to recharge the battery is electrically connected.
  • the power supply unit 190 may be configured to recharge the battery wirelessly without using a connection port.
  • the power supply unit 190 may receive power, transferred from an external wireless power transmitter, using at least one of an inductive coupling method which is based on magnetic induction or a magnetic resonance coupling method which is based on electromagnetic resonance.
  • Various embodiments described herein may be implemented in a computer-readable medium, a machine-readable medium, or similar medium using, for example, software, hardware, or any combination thereof.
  • FIG. 2 is a diagram showing the configuration of a mobile payment system using the mobile terminal according to an embodiment of the present invention.
  • the mobile payment system may include a mobile terminal 100, an authentication server 200, a payment server 300, a financial server 400, and a payment terminal (or POS terminal) 500.
  • the elements of the mobile payment system shown in FIG. 2 may be interconnected over a network.
  • the mobile terminal 100, the authentication server 200, the payment server 300, and the financial server 400 may be interconnected over a mobile communication network or through the Internet.
  • the mobile terminal 100 and the POS terminal 500 may be interconnected over a short distance communication network, for example, near field communication (NFC), wireless-fidelity (Wi-Fi) or magnetic secure transmission (MST).
  • NFC near field communication
  • Wi-Fi wireless-fidelity
  • MST magnetic secure transmission
  • the mobile terminal 100 may perform a user authentication process required for a payment information registration, deletion or payment process using the mobile payment system.
  • the mobile terminal 100 may be a device used by a user when mobile payment according to an embodiment of the present invention is to be performed.
  • the user may perform payment online/offline using the mobile terminal 100.
  • the mobile terminal 100 may provide a payment service using a payment app (e.g., LG Pay Application).
  • the payment app may provide a user interface related to payment.
  • the payment app may provide a user interface related to card registration, payment or transactions.
  • the payment app may provide an authentication interface related to user authentication.
  • the mobile terminal 100 may store card information or payment account information associated with a payment service account (e.g., LG account), a bio authentication service account or a user account.
  • a payment service account e.g., LG account
  • a bio authentication service account e.g., bio authentication service account
  • the mobile terminal 100 may perform user authentication through an authentication process.
  • the authentication process may be a bio authentication method based on a user's bio information or may be a method of entering a preset fin number.
  • the mobile terminal 100 may request a payment token from the payment server 300, and may perform mobile payment using the payment token issued by the financial server 500.
  • the mobile terminal 100 may operate in a payment mode in which mobile payment is performed through a process of transmitting/receiving information necessary for the payment to/from the authentication server 200, the payment server 300, and the financial server 400 connected over a network.
  • the authentication server 200 may perform user authentication in response a request from the mobile terminal 100.
  • the authentication server 300 may provide a fast identity online (FIDO) authentication service for performing user authentication using a user's bio information.
  • FIDO fast identity online
  • the authentication server 200 may perform user authentication using authentication information received from the mobile terminal 100.
  • the payment server 300 may transmit/receive information to/from the mobile terminal 100 and the financial server 400.
  • the payment server 300 may manage card information or account information that operates in conjunction with a payment service account (e.g., LG account), a bio authentication service account and a user account.
  • a payment service account e.g., LG account
  • the payment server 300 may request the payment token from the financial server 400.
  • the payment server 300 may transmit the payment token, received from the financial server 500, to the mobile terminal 100.
  • the financial server 400 may be a server managed by a card company or a bank.
  • the financial server 400 may issue a card and manage card information (or account information). Furthermore, the financial server 40 may generate a payment token.
  • the financial server 40 may request whether user authentication has been performed from the authentication server 200.
  • FIGS. 3 and 4 are flowcharts illustrating a method of controlling the mobile terminal according to a first embodiment of the present invention.
  • FIG. 3 is a diagram for illustrating a process of activating a mobile payment function on the same task as a task of executing a first app and extracting second membership information.
  • FIG. 4 is a diagram for illustrating an example in which second membership information added on a payment app screen is used.
  • the controller 180 provides an interface for directly entering a payment app on the app execution screen. That is, the same effect as that the payment function has been embedded in the execution screen of a specific app may be obtained.
  • the mobile terminal 100 may receive an input for activating a payment function in the state in which any one app execution screen has been displayed on the touch screen 151 while at least one app is executed.
  • an input for activating a payment function on the execution screen of a specific app is hereinafter referred to as a "first input.”
  • payment card information used for mobile payment and membership information capable of supporting saving or discount when mobile payment is performed may be stored in the memory. Accordingly, when a payment app is executed, a previously registered payment card image and membership information may be provided together.
  • the membership information may include information that is provided by a credit card company and that is saved when mobile payment is performed and can be used for saved points and an issued coupon service.
  • the membership information may include a coupon or saving information provided in a one-time manner through a web browser in addition to the credit card company.
  • first membership information membership information that is stored in the memory and available for mobile payment
  • second membership information membership information that is not stored in the memory, but is available for mobile payment
  • membership information may be used through a process of photographing a card number or barcode using a camera and registering the photographed card number or barcode with a payment app.
  • barcode or a barcode number
  • membership information not previously registered with a payment app can be applied to mobile payment more conveniently without performing the aforementioned process.
  • the controller 180 may activate a mobile payment function while executing a first app (S100).
  • a first app execution screen may include second membership information not stored in the memory (or not registered with a payment app).
  • the second membership information may include at least one of membership card information for point saving when mobile payment is performed and discount coupon information associated with a product to be purchased.
  • the second membership information may include at least one of information on a discount ratio, barcode, and a number corresponding to the barcode.
  • the controller 180 may activate the mobile payment function when a predetermined first input is received on the first app execution screen.
  • a payment indicator for activating the payment function may be indicated in the bottom edge area of the first app execution screen.
  • the first input may include an input for swiping the indicator positioned at the bottom of the touch screen 151 in the direction of the center of the touch screen.
  • the payment indicator is described more specifically later with reference to FIGS. 5 and 6.
  • the payment function may be activated in the state in which the first app execution screen has been positioned on the touch screen 151 through the first input.
  • the controller 180 may perform a screen capture function on the first app execution screen displayed on the touch screen 151 in response to the first input (S110).
  • the controller 180 may display a payment app screen without displaying the screen-captured image on the touch screen 151.
  • the controller 180 may extract the second membership information by analyzing the screen-captured image (S120).
  • a method of analyzing the screen-captured image may use a known technology for analyzing text, a symbol, barcode or QR code from an image.
  • the controller 180 may display the second membership information on the payment app screen (S130). Previously registered payment card information and previously registered first membership information may be displayed on the payment app screen along with the second membership information.
  • a first app is not terminated while the first app is executed (or the display of a first app execution screen is maintained), a payment function is activated on a first app screen, and information included in the first app screen can be used to execute the payment function.
  • the controller 180 may display at least one piece of second membership information, provided by at least one app, on a payment app screen (S140) through the method of FIG. 3.
  • the second membership information displayed on the payment app screen through the method of FIG. 3 is only temporary membership information, and may not be information stored in the memory and always available when a payment app is executed. Accordingly, the controller 180 may perform an operation of storing the second membership information displayed on the payment app screen in the memory (C).
  • the controller 180 may perform a mobile payment function using selected second membership information of the at least one piece of second membership information (S150).
  • the controller 180 may remove the second membership information from the payment app screen (S160).
  • the second membership information added to the payment app screen through the method of FIG. 3 is temporarily stored, and may be removed after the mobile payment is performed. Furthermore, the second membership information may be implemented to be automatically deleted if it is not used for mobile payment for a specific time or more.
  • FIGS. 5 and 6 are examples of the configuration of an interface for activating the payment function in a running app screen.
  • the touch screen 151 may include an app area in which the execution screen of an app capable of operating in conjunction with a payment function is displayed, a navigation bar (NB) area, and a payment indicator (VI) area to which a payment activation function has been assigned.
  • NB navigation bar
  • VI payment indicator
  • the navigation bar (NB) area may be implemented in the bottom edge area of the touch screen 151, and the payment indicator VI may be included in the navigation bar (NB) area.
  • the payment indicator (VI) area may have a smaller width than the navigation bar NB.
  • Soft keys capable of performing functions, such as page switching, the display of an app being executed in background, and return to a home screen, may be assigned to the navigation bar NB.
  • the payment indicator VI may be provided on any screen in which a payment function can be activated.
  • the payment indicator VI may include the display of a home payment screen, a lock screen or an always on display (AOD) mode.
  • the navigation bar NB and the payment indicator VI may disappear on a screen according to circumstances. For example, if an app operates in a first mode in which the app is executed on the entire screen of the touch screen 151, the navigation bar NB and the payment indicator VI may be covered on an app execution screen. When an input for swiping the indicator from the bottom of the touch screen 151 toward the center direction in the first mode is sensed, the navigator bar NB and the payment indicator VI may be provided on the touch screen 151 again.
  • the payment indicator VI has been illustrated as being positioned in the navigation bar NB, but the present invention is not limited thereto.
  • the payment indicator VI other than the navigator bar NB may be provided in the bottom edge area of the touch screen.
  • the controller 180 when an app to which a payment function may be applied is sensed based on the characteristics of an app displayed in the app area, the controller 180 automatically displays the payment indicator VI so that a user intuitively notices that payment can be executed.
  • the payment function shown in FIGS. 5 and 6 may mean that a payment app function operates in a quick payment mode. For example, this may mean that the payment function is not executed when a payment app icon is selected, but is executed by swiping the payment indicator.
  • FIG. 7 is an example of a screen for configuring an environment in which a quick payment mode can be executed according to an embodiment of the present invention.
  • an operation of entering the quick payment mode through the payment indicator VI described with reference to FIG. 5 and 6 may be previously set.
  • a configuration may be performed so that the quick payment mode is entered from a display of the AOD mode (11).
  • a configuration may be performed so that the quick payment mode is entered from a lock screen 12 or a home screen 13.
  • a configuration may be performed so that the quick payment mode is entered through any app executed in the mobile terminal 100 (14).
  • a configuration may be performed so that the quick payment mode is entered based on usage contexture of an app used in the mobile terminal 100. That is, for example, a game mode 15, online payment 16, and barcode use 17 may be configured.
  • the controller 180 may provide the payment indicator VI, thus being capable of visualizing that the quick payment mode can be entered.
  • the environment setting menu illustrated in FIG. 7 may include a minimum window menu 21 in which the size of a payment app screen is minimized and provided in the state in which the quick payment mode has been entered. Furthermore, in the quick payment mode, a menu 31 capable of adjusting transparency of the payment app screen (or a payment app window) may be provided.
  • a first embodiment of the present invention is described more specifically below with reference to FIGS. 8 to 11B.
  • FIG. 8 is an example of a screen configuration for illustrating S100 to S120 of FIG. 3.
  • the controller 180 may display a first app execution screen A1 on the touch screen 151.
  • the first app execution screen A1 includes second membership information not stored in the memory.
  • the second membership information stored in the first app execution screen A1 may be a discount coupon.
  • the discount coupon may be provided in a barcode form.
  • the navigation bar NB and the payment indicator VI may be displayed in the bottom edge area of the first app execution screen A1.
  • the controller 180 may enter the quick payment mode while capturing the first app execution screen A1.
  • the controller 180 does not display the captured image CI1 on the touch screen 151, and may extract second membership information from the captured image CI1 through a capture image analysis algorithm.
  • the controller 180 may extract text, a symbol or a specific symbol included in the captured image CI1 through the capture image analysis algorithm, and may classify the extracted results into pieces of information that may be used as membership information.
  • the controller 180 may extract an LG membership, discount ratio information, a barcode image and a barcode number, included in a variety of types of information included in the first app execution screen A1, from the capture image, and may classify them into membership information.
  • FIGS. 9A to 9C are examples of screen configurations for illustrating S130 of FIG. 3.
  • the controller 180 may enter the quick payment mode based on a first input to the payment indicator VI of FIG. 8, and may display a payment app screen PW on the touch screen 151 in the quick payment mode.
  • the payment app screen PW may be provided in a pop-up window form.
  • the controller 180 may display the payment app screen PW so that it overlaps at least some of the first app screen A1 in the quick payment mode.
  • the first app screen A1 is blurred, thereby being capable of enhancing the visibility of the pop-up window PW.
  • Previously registered payment card images C1, C2, and C3 may be displayed in the pop-up window PW in which the payment app screen is provided. If the previously registered payment card is plural, the payment cards are displayed in such a way as to be scrolled.
  • the pop-up window PW may further include user authentication menus A11 and A12.
  • the user authentication menus may include a bio authentication menu A12 and a password entry menu A12.
  • the bio authentication may include a user fingerprint authentication or iris authentication method.
  • the pop-up window PW may further include a membership button M for displaying membership information.
  • the size of the payment app screen PW may be minimized and provided.
  • the membership information may not be displayed in the payment app screen PW.
  • the controller 180 may provide one or more first membership images M11, M12, and M13 that have been previously registered and a second membership image M21 corresponding to the second membership information extracted from the first app screen.
  • the first membership information and the second membership information may be provided in a card image form.
  • the first membership information and the second membership information may be displayed to have different display characteristics so that they are different. For example, the second membership image M21 may be highlighted and displayed so that it is visually different from the first membership images M11, M12, and M13.
  • the controller 180 may provide detailed second membership information M2 along with the second membership image M21.
  • the second membership information M2 may include first app information S1 including the second membership information, a storage menu S2 for storing temporarily extracted second membership information in the memory or normally registering the second membership information with a payment app, a barcode image B21 corresponding to the extracted second membership information, and a barcode number S3 corresponding to the barcode.
  • the controller 180 may perform a payment authentication operation using a user authentication menu in the state in which the second membership information M21 displayed on the payment app screen PW has been selected.
  • the controller 180 may perform a payment operation using a selected payment card C1 and display a payment standby screen on the touch screen 151.
  • the payment standby screen may include the selected second membership information M2.
  • the payment standby screen may further display a payment standby time 40.
  • a user can enter the quick payment mode with respect to a one-time coupon not stored in the memory or not registered with a payment app, and can use the one-time coupon for mobile payment more simply.
  • FIG. 9D is an example of a screen configuration for illustrating the embodiment of FIG. 4.
  • the second membership information when the temporarily provided second membership information is normally used in the mobile payment process of FIG. 9C, the second membership information may be removed from the payment app screen PW, but the present invention is not limited thereto.
  • the second membership information may automatically disappear when a predetermined time (e.g., the validity date of a one-time coupon or time set by a user) elapses in the state in which the second membership information has been added to the payment app screen PW and is not used for a payment process.
  • a predetermined time e.g., the validity date of a one-time coupon or time set by a user
  • second membership information is to be not used right now, it may be registered with a payment app and stored in the memory.
  • FIG. 10 is an example of a screen configuration for illustrating a process of temporarily storing second membership information according to a first embodiment of the present invention.
  • the controller 180 may store temporarily extracted second membership information in the memory or normally register it with a payment app.
  • the controller 180 may automatically receive the name of the second membership information from information extracted from a captured image in response to the first input, and may display the received name (S1').
  • the payment app enters the quick payment mode while the first app is executed has been illustrated and an example in which the number of first apps is one has been assumed, but the present invention is not limited thereto.
  • a plurality of apps being executed in background may be present before a payment app enters the quick payment mode.
  • at least two of the plurality of apps may include pieces of second membership information.
  • FIGS. 11A and 11B are diagrams for illustrating another example in which second membership information is added to a payment app screen in the quick payment mode according to a first embodiment of the present invention.
  • a plurality of apps may be running before the controller enters the quick payment mode according to an embodiment of the present invention. At least two of the plurality of apps may include second membership information.
  • the controller 180 may perform screen capture on each of the execution screens the plurality of first apps.
  • the controller 180 may extract second membership information by analyzing each of screen capture images CI1, CI2, and CI3.
  • the controller 180 may enter the quick payment mode based on the first input and display the payment app screen PW on the touch screen 151.
  • the controller 180 may display a plurality of pieces of second membership information M21, M22, and M23 on the payment app screen PW along with the first membership information previously registered or stored as described above. Accordingly, a user may select any one of the pieces of the added second membership information M21, M22, and M23 and use the selected membership information for mobile payment.
  • second membership information may be added on a payment app screen in various manners.
  • FIG. 12 is a diagram for illustrating yet another example in which second membership information is added to a payment app screen in the quick payment mode according to a first embodiment of the present invention.
  • the controller 180 may control the second membership information 41 or 43 so that it is shared with a payment app 45.
  • the predetermined input may include a long touch input to second membership information (e.g., a barcode image 41, 43).
  • second membership information e.g., a barcode image 41, 43.
  • the controller 180 may provide a sharing app list.
  • the second membership information 41 or 43 may be added on the payment app screen. That is, the second membership information may be added although the payment indicator VI is not used.
  • Second information may be extracted from a screen-captured image and shared with a payment app.
  • a payment app may include a simple remittance function and a product purchase function in addition to a mobile payment function.
  • a simple remittance function may include a simple remittance function and a product purchase function in addition to a mobile payment function.
  • FIG. 13 is a flowchart illustrating a method of controlling the mobile terminal according to a second embodiment of the present invention.
  • the controller 180 may display the execution screen of a second app on the touch screen 151 (S200).
  • the execution screen of a first app disclosed in the first embodiment of the present invention may be an app including second membership information not stored in the memory.
  • a "second app execution screen" according to the second embodiment of the present invention does not need to essentially include second membership information, and may include all of apps including information capable of being associated with any one of various functions of a payment app. Accordingly, the second app is used to distinguish between the first app and the second app.
  • the second app execution screen may include a payment indicator for payment activation.
  • the payment indicator may be positioned in the bottom edge area of the touch screen 151.
  • the controller 180 receives an input that swipes the payment indicator upward (S210).
  • the controller 180 may analyze the second app execution screen in response to the swipe input, and may determine a function that belongs to information included in the execution screen of the second app and that may be applied to a payment app (S220). In an embodiment, the controller 180 may perform a screen capture operation on the second app execution screen in response to the swipe input to the payment indicator, and may determine a function applicable to the payment app using information extracted by extracting a capture image.
  • the controller 180 may analyze the attributes of an item provided on the second app execution screen, and may display an interface in which the payment app may be used on the touch screen based on the attributes of the item (S230).
  • the controller 180 may recommend the remittance function of various functions of a payment app.
  • the controller 180 may display a function execution menu, including a different function other than a payment menu or a payment function, on the touch screen 151 based on the analyzed attributes of the item.
  • the controller 180 may control a function based on a menu selected in response to an input for selecting a specific menu so that the function is executed (S240). If the selected menu is a payment menu, the controller may enter a quick payment mode and provide a payment app screen. If the selected menu is a function execution menu not a payment menu, another additional process may be performed. Another function execution menu other than the payment menu is described more specifically below with reference to FIGS. 14 and 15.
  • FIGS. 14A to 15B are diagrams for illustrating a method of controlling the mobile terminal according to the second embodiment of the present invention.
  • FIGS. 14A and 14B illustrate an example in which a remittance function is performed in the state in which the quick payment mode according to an embodiment of the present invention has been entered.
  • the controller 180 may receive an input for swiping the payment indicator VI upward in the state in which a messenger app has been executed.
  • the controller 180 may analyze information displayed in a chat window. For example, the controller may receive a swipe input to the payment indicator VI in the state in which at least one of a remittance counterpart name 51, an account number, a telephone number 52, and an e-mail address 53 has been posted in the chat window.
  • the controller 180 may perform a screen capture operation on a messenger execution screen based on the swipe input, and may identify a user's intent to perform a remittance function using a payment app based on information extracted from a captured image.
  • the controller 180 may display a simple remittance menu 55 and a payment menu 57 on the touch screen 151 based on the user's intent.
  • the menus may be displayed in the state in which the messenger execution screen has been blurred.
  • the controller 180 may display a simple remittance interface 58 not a payment app execution screen on the touch screen 151.
  • the information e.g., the telephone number of a remittance target
  • extracted on the execution screen of the second app may be automatically input to the simple remittance interface 58.
  • the simple remittance interface 58 may provide a keypad for entering a remittance amount.
  • FIGS. 15A and 15B illustrate an example in which a search function is performed in the state in which the quick payment mode according to an embodiment of the present invention has been entered.
  • the controller 180 may receive an input for swiping the payment indicator VI upward on a second app execution screen that provides multimedia content.
  • the multimedia content may be playing back.
  • the controller 180 may analyze multimedia content information that is being played back.
  • the controller 180 may perform a screen capture operation on the execution screen of a second app in response to the swipe input, and may identify a user's intent to purchase the corresponding multimedia content using a payment app based on information extracted from a captured image.
  • the controller 180 may display a simple shopping menu 58 and a payment menu 57 on the touch screen 151 based on the user's intent.
  • the menus may be provided in the state in which the second app execution screen has been blurred.
  • the controller 180 may search for the extracted multimedia content in the web and display retrieved results on the touch screen 151.
  • the controller 180 may directly enter the simple payment mode and perform mobile payment.
  • FIGS. 16 and 17 are diagrams for illustrating examples of payment app screen configurations provided in the quick payment mode according to an embodiment of the present invention.
  • the controller 180 may provide the payment app screen PW in a reduced screen form as it enters the quick payment mode.
  • the size of the payment app screen PW may be adjusted through size control buttons PW1 and PW2.
  • transparency of the payment app screen PW may be adjusted in the environment setting menu of FIG. 7. Accordingly, a user can perform a mobile payment function while watching more information on an app execution screen.
  • the aforementioned embodiments of the present invention may be implemented in a medium on which a progam has been recorded in the form of code readable by a computer.
  • the computer-readable medium includes all types of recording devices in which data readable by a computer system is stored.
  • the computer-readable medium may include, for example, a hard disk drive (HDD), a solid state disk (SOD), a silicon disk drive (SDD), ROM, RAM, CD-ROM, magnetic tapes, floppy disks, and optical data storages.
  • the aforementioned embodiments may be implemented in the form of carrier waves (e.g., transmission through the Internet).
  • the computer may include the controller 180 of the mobile terminal.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Human Computer Interaction (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

L'invention concerne un terminal mobile et son procédé de commande. Le terminal mobile passe en mode de paiement rapide sur un écran d'exécution d'application en cours et obtient des informations d'adhésion par capture de l'écran d'exécution d'application. Une fonction de paiement mobile peut être utilisée d'une manière plus pratique sur la base des informations d'adhésion obtenues. Les informations d'adhésion obtenues peuvent être des informations d'adhésion uniques non stockées en mémoire ou non enregistrées avec une application de paiement.
PCT/KR2018/006092 2017-05-29 2018-05-29 Terminal mobile et son procédé de commande WO2018221935A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18809746.3A EP3632091A4 (fr) 2017-05-29 2018-05-29 Terminal mobile et son procédé de commande

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762512176P 2017-05-29 2017-05-29
US62/512,176 2017-05-29

Publications (1)

Publication Number Publication Date
WO2018221935A1 true WO2018221935A1 (fr) 2018-12-06

Family

ID=64454779

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/006092 WO2018221935A1 (fr) 2017-05-29 2018-05-29 Terminal mobile et son procédé de commande

Country Status (2)

Country Link
EP (1) EP3632091A4 (fr)
WO (1) WO2018221935A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070075010A (ko) * 2006-01-11 2007-07-18 주식회사 팬택 단문 문자 메시지에서 금융 정보를 추출하여 모바일 금융서비스를 제공하는 방법 및 이동통신 단말기
US20140058897A1 (en) * 2012-08-24 2014-02-27 Samsung Electronics Co., Ltd. Information providing method, mobile terminal and display device for the same
KR20170014606A (ko) * 2015-07-30 2017-02-08 엘지전자 주식회사 이동단말기 및 그 제어방법
KR20170020115A (ko) * 2015-08-13 2017-02-22 엘지전자 주식회사 이동 단말기 및 그 동작 방법
KR20170019782A (ko) * 2015-08-12 2017-02-22 엘지전자 주식회사 와치 타입의 이동 단말기

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11284251B2 (en) * 2012-06-11 2022-03-22 Samsung Electronics Co., Ltd. Mobile device and control method thereof
EP2962262A4 (fr) * 2013-02-26 2016-08-24 Digimarc Corp Procédés et agencements pour des paiements et des transactions par téléphones intelligents

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070075010A (ko) * 2006-01-11 2007-07-18 주식회사 팬택 단문 문자 메시지에서 금융 정보를 추출하여 모바일 금융서비스를 제공하는 방법 및 이동통신 단말기
US20140058897A1 (en) * 2012-08-24 2014-02-27 Samsung Electronics Co., Ltd. Information providing method, mobile terminal and display device for the same
KR20170014606A (ko) * 2015-07-30 2017-02-08 엘지전자 주식회사 이동단말기 및 그 제어방법
KR20170019782A (ko) * 2015-08-12 2017-02-22 엘지전자 주식회사 와치 타입의 이동 단말기
KR20170020115A (ko) * 2015-08-13 2017-02-22 엘지전자 주식회사 이동 단말기 및 그 동작 방법

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3632091A4 *

Also Published As

Publication number Publication date
EP3632091A4 (fr) 2021-03-24
EP3632091A1 (fr) 2020-04-08

Similar Documents

Publication Publication Date Title
WO2018066782A1 (fr) Terminal mobile
WO2017069403A1 (fr) Terminal mobile et procédé de commande associé
WO2015190666A1 (fr) Terminal mobile et son procédé de commande
WO2017065365A1 (fr) Terminal mobile et procédé de commande de celui-ci
WO2017014374A1 (fr) Terminal mobile et son procédé de commande
WO2016186286A1 (fr) Terminal mobile et son procédé de commande
WO2020017706A1 (fr) Dispositif électronique et procédé pour le commander
WO2017039098A1 (fr) Dispositif mobile, dispositif portable et procédé de commande de chaque dispositif
WO2015016524A1 (fr) Terminal mobile, montre intelligente, et procédé de mise en œuvre d'authentification à l'aide du terminal mobile et de la montre intelligente
WO2018026059A1 (fr) Terminal mobile et son procédé de commande
WO2016093459A1 (fr) Terminal mobile et son procédé de commande
WO2017119579A1 (fr) Terminal mobile et son procédé de commande
WO2015064876A1 (fr) Procédé pour générer des informations de recette dans un terminal mobile
WO2017014394A1 (fr) Terminal mobile et son procédé de commande
WO2015041400A1 (fr) Panneau tactile, appareil d'entrée sans fil et terminal mobile comportant le panneau tactile
WO2016056723A1 (fr) Terminal mobile et son procédé de commande
WO2017104941A1 (fr) Terminal mobile et son procédé de commande
WO2017131351A1 (fr) Terminal mobile et procédé de commande associé
WO2018048092A1 (fr) Visiocasque et son procédé de commande
WO2015130040A1 (fr) Terminal mobile et son procédé de commande
WO2016076546A1 (fr) Terminal mobile et son procédé de commande
WO2016039509A1 (fr) Terminal et procédé d'utilisation de celui-ci
WO2014208783A1 (fr) Terminal mobile et procédé pour commander un terminal mobile
WO2018026116A1 (fr) Terminal et son procédé de commande
WO2018093005A1 (fr) Terminal mobile et procédé de commande associé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18809746

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2018809746

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2018809746

Country of ref document: EP

Effective date: 20200102