KR20140105677A - Mobile apparatus issuing wallet component managed by ticket server, control method thereof, and ticket server - Google Patents

Abstract

A method for controlling a mobile device issuing a wallet component managed by a ticket server according to an embodiment of the present invention comprises the steps of receiving common information of a wallet component registered in a ticket server from a provider server, displaying the wallet component on a provider application, selecting a request for issuing the wallet component; requesting the ticket server to issue the selected wallet component, transmitting variable information of the selected wallet component to the ticket server, receiving a wallet component issued by the ticket server in response to the requested wallet component and including the common information and the variable information from the ticket server, and displaying the issued wallet component on a wallet application.

Description

TECHNICAL FIELD [0001] The present invention relates to a mobile device that issues a wallet component managed by a ticket server, a control method thereof, and a ticket server,

The present invention belongs to the technology relating to mobile devices and their control methods and servers, and more particularly to a mobile device for issuing Wallet components managed in a ticket server, and a control method thereof and a ticket server.

Various applications are evolving in mobile devices in recent years. In particular, the Wallet application refers to an application that a user of the mobile device can use in the form of an electronic wallet. The Wallet application corresponding to the electronic wallet may store wallet components such as a coupon, a ticket, and a card.

However, the Wallet components such as coupons, tickets, and cards are generated by a provider providing them and are provided to the user. Accordingly, the provider has to construct a separate server and program for managing the coupon, the ticket, and the card.

When the user uses a plurality of mobile devices, the server of the provider has to provide the coupon, ticket, and card directly to the plurality of mobile devices.

In addition, when an update of the coupon, the ticket, and the card occurs, the user information for updating the coupon, the ticket, and the card must be stored in the server. Also, there is a problem that an overload for the update occurs.

Therefore, it is necessary to provide a coupon, a ticket, and a card to a user of the mobile device more easily, and to develop a technique that does not cause an overload to the provider.

One embodiment of the present invention provides a mobile device that issues a Wallet component managed at a ticket server that can receive a Wallet component from a ticket server while removing a processing load associated with issuance of a Wallet component at a provider server, And a ticket server.

In an embodiment of the present invention, a wallet component managed by a ticket server, which can register various wallet components in a ticket server by changing detailed information of a wallet component corresponding to variable information and registering the detailed information in a ticket server, A mobile device to be issued, a control method thereof, and a ticket server.

Yet another embodiment of the present invention is that the provider server is capable of performing update via the ticket server without sending update information directly to the mobile device when an update to the Wallet component occurs, A mobile device for issuing the element, a control method thereof, and a ticket server.

Another embodiment of the present invention is a method for synchronizing updated Wallet components to all of the plurality of mobile devices by searching for a plurality of mobile devices to transmit updates at a ticket server and sending update information to the plurality of mobile devices, And a control method thereof and a ticket server are provided.

A mobile device control method for issuing a wallet component managed by a ticket server according to an embodiment of the present invention includes receiving common information of a wallet component registered in a ticket server from a provider server, The method of claim 1, further comprising: displaying on the application an issuance request for the Wallet component; requesting the ticket server for issuance of the selected Wallet component; Receiving from the ticket server an issued Wallet component issued by the ticket server corresponding to the requested Wallet component and including the common information and the variable information; Lt; RTI ID = 0.0 > Wallet < / RTI > component on the Wallet application.

A ticket server issuing a Wallet component according to an embodiment of the present invention receives common information of a Wallet component from a provider server, receives an issuance request for the Wallet component from a mobile device, A controller configured to issue a Wallet component including the common information and the variable information corresponding to the element and to transmit the issued Wallet component to the mobile device and a communication unit configured to communicate with the mobile device and the provider server, And a storage for storing the Wallet component.

A mobile device issuing a Wallet component managed in a ticket server according to an embodiment of the present invention receives common information of a Wallet component registered in a ticket server from a provider server and displays the Wallet component on a provider application Requesting an issuance request for the Wallet component, requesting the ticket server for issuance of the selected Wallet component, transmitting variable information of the selected Wallet component to the ticket server, A control unit for receiving, from the ticket server, an issued Wallet component issued by the ticket server corresponding to the component and including the common information and the variable information, and displaying the issued Wallet component on the Wallet application; A touch screen for displaying the Wallet component on the provider application and displaying the issued Wallet component on the Wallet application; And a storage for storing the Wallet component.

According to an embodiment of the present invention, there is an advantage that the provider server can request the issuance of the Wallet component to the ticket server while eliminating the processing load due to issuance of the Wallet component.

According to an embodiment of the present invention, there is an advantage that only the detailed information of the wallet component corresponding to the variable information is changed and registered in the ticket server so that various Wallet components can be registered in the ticket server by a simple method.

According to an embodiment of the present invention, there is an advantage in that the provider server can receive the Wallet component from the ticket server while eliminating the processing load due to issuance of the Wallet component.

According to another embodiment of the present invention, the issued Wallet component can be received from the ticket server using the ID of the received Wallet component. That is, there is an advantage that a simple issued Wallet component can be received from the ticket server using an ID that can identify the issued Wallet component.

According to another embodiment of the present invention, there is an advantage that the provider server can perform the update through the ticket server without transmitting the update information directly to the mobile device when an update to the Wallet component occurs.

According to another embodiment of the present invention, the ticket server searches for a plurality of mobile devices to transmit updates and transmits update information to all of the plurality of mobile devices, thereby updating the updated Wallet components in all of the plurality of mobile devices There is an advantage to be able to synchronize.

According to another embodiment of the present invention, the provider server can perform the update through the ticket server when an update to the Wallet component occurs, thereby eliminating the overload due to the update.

1 is a schematic block diagram illustrating a mobile device in accordance with an embodiment of the present invention.
2 is a front perspective view of a mobile device in accordance with an embodiment of the present invention.
3 is a rear perspective view of a mobile device according to one embodiment of the present invention.
4 is a diagram illustrating a configuration of a server according to an embodiment of the present invention.
5 is a flowchart illustrating a method of controlling a mobile device for issuing a Wallet component managed in a ticket server according to an exemplary embodiment of the present invention.
Figure 6 is a diagram showing common information of Wallet components.
7 is a diagram for receiving and displaying the Wallet component registered in the ticket server from the provider server.
Figures 8-11 are diagrams showing Wallet components.
Figures 12-13 show the issued Wallet components as a list view.
14 is a flowchart illustrating a method of controlling a mobile device for issuing a Wallet component managed in a ticket server according to another embodiment of the present invention.
15 is a flowchart illustrating a method of controlling a mobile device for issuing a Wallet component managed in a ticket server according to another embodiment of the present invention.
16 is a diagram showing a notification according to another embodiment of the present invention.

The present invention can be variously modified and may have various embodiments, and specific embodiments will be described in detail with reference to the drawings. It is to be understood, however, that the invention is not to be limited to the specific embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

Terms including ordinals, such as first, second, etc., may be used to describe various elements, but the elements are not limited to these terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

1 is a schematic block diagram illustrating a mobile device in accordance with an embodiment of the present invention.

1, the apparatus 100 may be connected to an external device (not shown) using an external device connection such as a sub communication module 130, a connector 165, and an earphone connection jack 167. An external device includes an earphone, an external speaker, a universal serial bus (USB) memory, a charger, a cradle, a docking station, , A DMB antenna, a mobile payment related device, a health care device (blood glucose meter, etc.), a game machine, a car navigation device, and the like. The "external device" also includes a Bluetooth communication device, a short distance communication device such as a NFC (Near Field Communication) device, and a WiFi direct communication device, a wireless access point (AP) , Access Point). The external device may also include other devices, mobile phones, smart phones, tablet PCs, desktop PCs, and servers.

Referring to FIG. 1, the apparatus 100 includes a display unit 190 and a display controller 195. The apparatus 100 includes a controller 110, a mobile communication module 120, a sub communication module 130, a multimedia module 140, a camera module 150, a GPS module 155, an input / output module 160 A sensor module 170, a storage unit 175, and a power supply unit 180. The sub communication module 130 includes at least one of a wireless LAN module 131 and a local communication module 132. The multimedia module 140 includes a broadcasting communication module 141, an audio reproduction module 142, (143). The camera module 150 includes at least one of a first camera 151 and a second camera 152. The input / output module 160 includes a button 161, a microphone 162, a speaker 163, A motor 164, a connector 165, a keypad 166, and an earphone connection jack 167. Hereinafter, the display unit 190 and the display controller 195 are respectively a touch screen and a touch screen controller.

The control unit 110 stores a ROM or a ROM 112 storing a control program for controlling the apparatus 100 and a signal or data input from the outside of the apparatus 100, And a RAM (RAM) 113 used as a storage area for a work to be performed. The CPU 111 may include a single core, a dual core, a triple core, or a quad core. The CPU 111, the ROM 112, and the RAM 113 may be interconnected via an internal bus.

The control unit 110 includes a mobile communication module 120, a sub communication module 130, a multimedia module 140, a camera module 150, a GPS module 155, an input / output module 160, a sensor module 170, A storage unit 175, a power supply unit 180, a touch screen 190, and a touch screen controller 195, as shown in FIG.

The mobile communication module 120 allows the device 100 to be connected to an external device through mobile communication using at least one or more antennas (not shown) under the control of the controller 110. The mobile communication module 120 may communicate with a mobile phone (not shown), a smartphone (not shown), a tablet PC or other device (not shown) having a phone number input to the device 100, And transmits / receives a radio signal for a text message (SMS) or a multimedia message (MMS).

The sub communication module 130 may include at least one of a wireless LAN module 131 and a local area communication module 132. For example, it may include only the wireless LAN module 131, only the short range communication module 132, or both the wireless LAN module 131 and the short range communication module 132.

The wireless LAN module 131 may be connected to the Internet at a place where an access point (AP) (not shown) is installed under the control of the controller 110. [ The wireless LAN module 131 supports the IEEE 802.11x standard of the Institute of Electrical and Electronics Engineers (IEEE). The short-range communication module 132 may wirelessly perform short-range communication between the apparatus 100 and the image forming apparatus (not shown) under the control of the controller 110. [ The short-distance communication method may include bluetooth, infrared data association (IrDA), WiFi-Direct communication, and Near Field Communication (NFC).

The apparatus 100 may include at least one of a mobile communication module 120, a wireless LAN module 131, and a local communication module 132 according to performance. For example, the device 100 may include a combination of a mobile communication module 120, a wireless LAN module 131, and a short range communication module 132 depending on performance.

The multimedia module 140 may include a broadcasting communication module 141, an audio reproducing module 142, or a moving picture reproducing module 143. The broadcast communication module 141 receives a broadcast signal (e.g., a TV broadcast signal, a radio broadcast signal, or a data broadcast signal) transmitted from a broadcast station through a broadcast communication antenna (not shown) under the control of the controller 110, (E. G., An Electric Program Guide (EPG) or an Electric Service Guide (ESG)). The audio playback module 142 may play back a digital audio file (e.g., a file having a file extension of mp3, wma, ogg, or wav) stored or received under the control of the controller 110. [ The moving picture playback module 143 may play back digital moving picture files (e.g., files having file extensions mpeg, mpg, mp4, avi, mov, or mkv) stored or received under the control of the controller 110. [ The moving picture reproducing module 143 can reproduce the digital audio file.

The multimedia module 140 may include an audio reproduction module 142 and a moving picture reproduction module 143 except for the broadcasting communication module 141. [ The audio reproducing module 142 or the moving picture reproducing module 143 of the multimedia module 140 may be included in the controller 110.

The camera module 150 may include at least one of a first camera 151 and a second camera 152 for capturing still images or moving images under the control of the controller 110. [ Further, the first camera 151 or the second camera 152 may include an auxiliary light source (e.g., a flash (not shown)) for providing the light amount required for photographing. The first camera 151 may be disposed on the front side of the apparatus 100 and the second camera 152 may be disposed on the rear side of the apparatus 100. The distance between the first camera 151 and the second camera 152 is larger than 1 cm and smaller than 8 cm) in a manner different from the first camera 151 and the second camera 152 Dimensional still image or a three-dimensional moving image.

The GPS module 155 receives radio waves from a plurality of GPS satellites (not shown) on the earth orbit, and uses the Time of Arrival from the GPS satellites (not shown) to the device 100 The position of the apparatus 100 can be calculated.

The input / output module 160 may include at least one of a plurality of buttons 161, a microphone 162, a speaker 163, a vibration motor 164, a connector 165, and a keypad 166.

Button 161 may be formed on the front, side, or rear surface of the housing of the apparatus 100 and may include at least one of a power / lock button, a volume button, a menu button, a home button, a back button, One can be included.

The microphone 162 receives a voice or a sound under the control of the controller 110 and generates an electrical signal.

The speaker 163 may transmit various signals (for example, a radio signal, a broadcast signal, a radio signal, a radio signal, a radio signal, a radio signal, and the like) of the mobile communication module 120, the sub communication module 130, the multimedia module 140, or the camera module 150 under the control of the controller 110. [ A digital audio file, a digital moving picture file, a picture photographing, or the like) to the outside of the apparatus 100. The speaker 163 can output sound corresponding to the function performed by the apparatus 100 (e.g., a button operation sound corresponding to a telephone call or a ring back tone). The speaker 163 may be formed at one or a plurality of positions at appropriate positions or positions of the housing of the apparatus 100.

The vibration motor 164 can convert an electrical signal into a mechanical vibration under the control of the control unit 110. [ For example, when the device 100 in the vibration mode receives a voice call from another device (not shown), the vibration motor 164 operates. May be formed in the housing of the apparatus 100 in one or more. The vibration motor 164 may operate in response to the user's touching operation on the touch screen 190 and the continuous movement of the touch on the touch screen 190.

The connector 165 may be used as an interface for connecting the device 100 to an external device (not shown) or a power source (not shown). The device 100 transmits data stored in the storage unit 175 of the device 100 to an external device (not shown) via a wired cable connected to the connector 165 under the control of the control unit 110, May receive data from a device (not shown). The external device may be a docking station, and the data may be an input signal transmitted from an external input device, such as a mouse or a keyboard. The device 100 may also receive power from a power source (not shown) via a wired cable connected to the connector 165, or may charge the battery (not shown) using the power source.

The keypad 166 may receive key input from a user for control of the device 100. The keypad 166 includes a physical keypad (not shown) formed on the device 100 or a virtual keypad (not shown) displayed on the touch screen 190. A physical keypad (not shown) formed in the device 100 may be excluded depending on the performance or structure of the device 100. [

An earphone connecting jack (earphone connecting jack) 167 may be connected to the device 100 by inserting an earphone (not shown).

The sensor module 170 includes at least one sensor for detecting the condition of the device 100. For example, the sensor module 170 may include a proximity sensor that detects whether the user is approaching the device 100, and an illuminance sensor that detects the amount of light around the device 100. Also, the sensor module 170 may include a gyro sensor. The gyro sensor may detect movement of the device 100 (e.g., rotation of the device 100, acceleration or vibration applied to the device 100) and may detect a point of the compass using a geomagnetic field Or may detect the direction of action of gravity. In addition, the sensor module 170 may include an altimeter for measuring the atmospheric pressure and detecting the altitude. The at least one sensor may detect a state, generate a signal corresponding to the detection, and transmit the signal to the controller 110. The at least one sensor of the sensor module 170 may be added or deleted depending on the capabilities of the device 100.

The storage unit 175 is connected to the mobile communication module 120, the sub communication module 130, the multimedia module 140, the camera module 150, the GPS module 155, the input / And may store signals or data input / output corresponding to the operation of the touch panel 160, the sensor module 170, and the touch screen 190. The storage unit 175 may store control programs and applications for controlling the apparatus 100 or the control unit 110. [

The term " storage unit " includes a storage unit 175, a ROM 112 in the control unit 110, a RAM 113, or a memory card (not shown) ). The storage unit may include a nonvolatile memory, a volatile memory, a hard disk drive (HDD), or a solid state drive (SSD).

The power supply unit 180 may supply power to one or a plurality of batteries (not shown) disposed in the housing of the apparatus 100 under the control of the controller 110. One or more batteries (not shown) supply power to the device 100. In addition, the power supply unit 180 can supply power to the apparatus 100 from an external power source (not shown) through a wired cable connected to the connector 165. In addition, the power supply unit 180 may supply power to the apparatus 100 wirelessly input from an external power source through wireless charging technology.

The touch screen 190 may provide a user interface corresponding to various services (e.g., call, data transmission, broadcasting, photographing) to the user. The touch screen 190 may transmit an analog signal corresponding to at least one touch input to the user interface to the touch screen controller 195. The touch screen 190 can receive at least one touch through a user's body (e.g., a finger including a thumb) or a touchable input means (e.g., a stylus pen). Also, the touch screen 190 can receive a continuous movement of one touch among at least one touch. The touch screen 190 may transmit an analog signal corresponding to the continuous movement of the input touch to the touch screen controller 195.

In the present invention, the touch is not limited to the contact between the touch screen 190 and the user's body or touchable input means, and may include non-contact. The distance that can be detected on the touch screen 190 may vary depending on the performance or structure of the device 100.

The touch screen 190 may be implemented by, for example, a resistive method, a capacitive method, an infrared method, or an acoustic wave method.

The touch screen controller 195 converts the received analog signal from the touch screen 190 into a digital signal (e.g., X and Y coordinates) and transmits the converted signal to the controller 110. [ The controller 110 may control the touch screen 190 using the digital signal received from the touch screen controller 195. For example, the control unit 110 may cause a shortcut icon (not shown) displayed on the touch screen 190 to be selected or a shortcut icon (not shown) in response to a touch. Also, the touch screen controller 195 may be included in the control unit 110. [

2 is a front perspective view of a mobile device in accordance with an embodiment of the present invention. 3 is a rear perspective view of a mobile device according to one embodiment of the present invention.

Referring to FIG. 2, a touch screen 190 is disposed at the center of the front surface 100a of the apparatus 100. Referring to FIG. The touch screen 190 is formed to be large enough to occupy most of the front surface 100a of the apparatus 100. [ 2, an example in which the main screen is displayed on the touch screen 190 is shown. The main home screen is the first screen displayed on the touch screen 190 when the apparatus 100 is powered on. Also, if the device 100 has different pages of different home screens, the main home screen may be the first home screen of the plurality of pages. Shortcut icons 191-1, 191-2, and 191-3 for executing frequently used applications, an application switching key 191-4, time, weather, and the like may be displayed on the home screen. The application switching key 191-4 displays application icons representing applications on the touch screen 190 on the screen. A status bar 192 may be provided at the upper portion of the touch screen 190 to indicate the status of the device 100 such as the battery charging status, the intensity of the received signal, and the current time.

A home button 161a, a menu button 161b, and a back button 161c may be formed on the lower portion of the touch screen 190.

The home button 161a displays a main home screen on the touch screen 190. [ For example, if the home button 161a is pressed (or touched) while the home screen or any other home screen or menu screen is displayed on the touch screen 190, the touch screen 190 The main home screen can be displayed. In addition, when the home button 161a is pressed (or touched) while applications are being executed on the touch screen 190, the main home screen shown in Fig. 2 can be displayed on the touch screen 190. [ Home button 161a may also be used to display recently used applications on the touch screen 190 or to display a Task Manager.

The menu button 161b provides a connection menu that can be used on the touch screen 190. The connection menu may include a widget addition menu, a background screen change menu, a search menu, an edit menu, a configuration menu, and the like. And provide a connection menu associated with the application upon execution of the application.

The back button 161c may display a screen that was executed immediately before the currently executed screen, or may terminate the most recently used application.

The first camera 151, the illuminance sensor 170a, and the proximity sensor 170b may be disposed at the edge of the front surface 100a of the apparatus 100. [ A second camera 152, a flash 153, and a speaker 163 may be disposed on the rear surface 100c of the apparatus 100. [

The side 100b of the apparatus 100 may include a power / reset button 161d, a volume control button 161e, a terrestrial DMB antenna 141a for broadcasting reception, one or more microphones 162, . The DMB antenna 141a may be fixed to the apparatus 100 or may be removably formed.

Further, a connector 165 is formed on the lower side surface of the apparatus 100. A plurality of electrodes are formed on the connector 165 and may be connected to an external device by wire. An earphone connection jack 167 may be formed on the upper side of the device 100. An earphone can be inserted into the earphone connection jack 167.

4 is a diagram illustrating a configuration of a server according to an embodiment of the present invention. A typical configuration of such a server 200, 300 is related to a Wallet application, and a typical configuration of such a server 200, 300 is schematic and requires some components shown in a typical configuration of the above-described mobile device 100 . ≪ / RTI >

Referring to FIG. 4, the provider server 200 may include a control unit 210, a communication unit 220, and a storage unit 230. The control unit 210 transmits the Wallet component to the ticket server 300 and the mobile device 100. [ The communication unit 220 performs communication with the mobile device and the ticket server. The storage unit 230 stores the wallet component.

The ticket server 300 may include a control unit 310, a communication unit 320, and a storage unit 330. The control unit 310 receives the Wallet component from the provider server, receives an issuance request for the Wallet component from the mobile device, issues the Wallet component corresponding to the requested Wallet component, ≪ / RTI > to the mobile device. The communication unit 320 communicates with the mobile device and the provider server. The storage unit 330 stores the wallet component.

5 is a flowchart illustrating a method of controlling a mobile device for issuing a Wallet component managed in a ticket server according to an exemplary embodiment of the present invention.

Referring to FIG. 5, first, common information of a wallet component is registered from a provider server to a ticket server (step S110). Common information of the Wallet component may be registered in the ticket server 300 from the provider server 200. [ That is, the common information of the wallet component stored in the provider server 200 may be transmitted to the ticket server 300 and stored in the storage unit 330 of the ticket server 300. At this time, the controller 210 of the provider server 200 may transmit the common information of the wallet component to the ticket server 300. Accordingly, registration with the ticket server 300 may mean that common information of the Wallet component transmitted from the provider server 200 is stored in the storage unit 330 of the ticket server 300. [ Transmission of the common information of the wallet component from the provider server 200 to the ticket server 300 is performed by using the communication unit 210 of the provider server 200 and the communication unit 310 of the ticket server 300 .

The ticket server 300 is a separate server that is different from the provider server 200. That is, the user of the provider server 200 (meaning a provider) can register common information of his / her Wallet component in a separate server 300 that is different from his / her server 200. The manager of the ticket server 300 can register and manage common information of a plurality of Wallet components from a plurality of provider servers 200. [

At this time, the Wallet component may be a coupon, a ticket, or a card. The coupon may be a discount coupon that can be used in a store. For example, the coupon may be a discount coupon for a certain amount that can be used when the shampoo is purchased at Mart. And the ticket can be used for the position of the user. For example, the ticket may be an admission ticket for boarding the airplane, or an admission ticket for entering the theater. And the card may be a membership card or a credit card. For example, the card may be a membership card that can be used in a mart.

Accordingly, the common information of the Wallet component may be registered in the ticket server 300 from the provider server 200. [ At this time, the Wallet component may be a coupon, a ticket, or a card. Therefore, the ticket server 300 may register common information of the Wallet component such as a coupon, a ticket, or a card. For example, common information of an airplane ticket can be registered in the ticket server 300 from the provider server 200. That is, the common information of the airplane ticket stored in the provider server 200 may be stored in the storage unit 330 of the ticket server 300 and registered. For example, a provider such as a K-airline may register common information of an airplane ticket stored in its provider server 200 in the ticket server 300. The manager of the ticket server 300 can store and manage the common information of the airplane ticket received from the provider server 200 to the K airline. Therefore, the ticket server 300 receives and registers common information of a wallet component (which may be referred to as a ticket) such as a coupon, a ticket, or a card from a plurality of provider servers 200, . In addition, the user of the provider server 200 registers common information of a wallet component (ticket) such as a coupon, a ticket or a card thereof in the ticket server 300 and provides it to the ticket server 300 Service can be used.

The wallet component includes common information and variable information received from the provider server 200. The common information means fixed information among the information forming the wallet component. That is, information that is fixed and common among a plurality of Wallet components. In contrast, the variable information means information that can be changed among the information forming the wallet component. That is, information that can be changed among a plurality of Wallet components and is not common. For example, the common information may be a display layout of the Wallet component, and the variable information may be detailed information of the Wallet component. That is, the display layout of the Wallet component corresponding to the common information may be fixed and common information among a plurality of Wallet components. Conversely, the detailed information of the Wallet component corresponding to the variable information may be information that can be changed among the information forming the Wallet component. And, the common information may include an identification key that identifies the display layout of the Wallet component. Accordingly, the control unit 110 of the mobile device 100 can distinguish the display layout of the wallet component through the identification key.

Figure 6 is a diagram showing common information of Wallet components. The common information of the Wallet component may be the display layout of the Wallet component. 6, for example, the display layout of the Wallet component is such that the provider image logo 401 and the provider company name 403 are displayed at the top, and the detailed information 405 of the Wallet component is displayed at the center And a barcode corresponding to the wallet component and a number 407 of the barcode may be displayed at the bottom. At this time, the display layout of the Wallet component corresponding to the common information may be common information that is fixed and unchangeable among a plurality of Wallet components.

The variable information of the Wallet component may be detailed information of the Wallet component. That is, the variable information of the wallet component may be the detailed information of the wallet component displayed in the display layout corresponding to the common information. The detailed information of the Wallet component corresponding to the variable information may be information that can be changed among the information forming the Wallet component. For example, the detailed information of the Wallet component may be the detailed information of the Wallet component shown in FIG. 6, the barcode corresponding to the Wallet component, and the number of the barcode.

Therefore, according to an embodiment of the present invention, the user of the provider server does not change the display layout of the Wallet component corresponding to the common information, but changes only the detailed information of the Wallet component corresponding to the variable information There is an advantage to be able to.

Next, common information of the wallet component registered in the ticket server is received from the provider server (step S120). The mobile device 100 receives common information of the Wallet component registered in the ticket server 300 from the provider server 200. [ That is, the control unit 110 of the mobile device 100 can receive the common information of the wallet component registered in the ticket server 300 from the provider server 200 through the communication unit 120.

Next, the Wallet component is displayed on the provider application (step S130). The controller 110 of the mobile device 100 executes the provider application and displays the Wallet component on the touch screen 190. [ Figure 7 is a diagram showing a Wallet component on a provider application. Referring to FIG. 7, first, the controller 110 may execute a provider application. For example, FIG. 7A shows an example of the application 500 of the provider 'S Coffee' running and displayed on the touch screen 190. And the controller 110 may detect the selection of the Wallet component 502 on the provider application 500. As shown in FIG. 7A, the selection of the wallet component corresponding to the coupon 502 can be detected. For example, a touch to the coupon 502 may be recognized to detect a selection for the coupon 502. [ Next, the controller 110 may request the provider server 200 to transmit the selected coupon 502. Next, the control unit 110 of the mobile device 100 may receive the coupon 502 from the provider server 200 in response to the request. Next, the controller 110 may display the coupon 502 on the provider application as shown in FIG. 7B.

Next, the issuance request for the Wallet component is selected (step S140). The controller 110 of the mobile device 100 may detect a selection of an issuance request for the Wallet component. At this time, the controller 110 may detect a selection of an issuance request for the Wallet component as a selection of an issuance request icon displayed on the provider application. That is, when the controller 110 detects the selection of the issuance request icon displayed on the provider application, it can recognize that the issuance request for the Wallet component is selected. At this time, the selection of the issuance request icon displayed on the provider application may be a touch to the issuance request icon 510. For example, in FIG. 7B, an issuance request icon 510 displayed on the provider application is displayed on the touch screen 190. Accordingly, when a touch on the issue request icon 510 displayed on the provider application is detected, the controller 110 can recognize the selection of the issue request for the Wallet component corresponding to the coupon.

Next, the issuance of the selected Wallet component is requested to the ticket server (step S150). The controller 110 of the mobile device 100 may request the issuance of the selected Wallet component to the ticket server when a touch on the issuance request icon displayed on the provider application is detected. For example, as shown in FIG. 7B, when the issuance request for the wallet component corresponding to the coupon is selected, the controller 110 can request the issuance of the coupon to the ticket server 300. At this time, the controller 110 requests the provider server 200 for issuance of the selected Wallet component and requests the ticket server 300 for issuance of the selected Wallet component by the provider server 200 , And may request the issuance of the selected Wallet component directly to the ticket server 300.

Next, variable information of the selected Wallet component is registered in the ticket server (step S155). The controller 110 of the mobile device 100 may transmit the variable information of the selected Wallet component to the ticket server 300 and register the changed information. At this time, the controller 110 of the mobile device 100 transmits variable information of the selected Wallet component to the provider server 200, and the provider server 200 transmits variable information of the selected Wallet component to the ticket It may be transmitted to the server 300 for registration. As shown in FIG. 7B, for example, the provider server 200 transmits detailed information of a coupon including a discount amount, a discount item, and an expiration date, a barcode corresponding to the coupon, a number of the barcode such as '1234-5678-9012' Can be transmitted to the ticket server 300 as variable information of the selected Wallet component and registered.

Next, in response to the requested Wallet component, the ticket server issues a Wallet component including the common information and the variable information (step S160). The ticket server 300, which has been requested to issue the selected Wallet component, issues the selected Wallet component. At this time, the ticket server 300 may issue the Wallet component by combining the common information of the received Wallet component with the variable information of the Wallet component. That is, the ticket server 300 may issue the Wallet component by combining the common information of the Wallet component received in step 110 and the variable information of the Wallet component received in step S155 described above.

Next, in step S170, the wallet component issued by the ticket server is received from the ticket server in response to the requested wallet component. The mobile device 100 may receive the Wallet component issued from the ticket server 300 in response to the requested Wallet component from the ticket server 300. [ That is, the mobile device 110 may receive the Wallet component issued in step S160 from the ticket server 300, which is requested in step S150 described above. At this time, the mobile device 100 may receive the issued Wallet component from the communication unit 320 of the ticket server 300 using the communication unit 120. Therefore, according to the embodiment of the present invention, there is an advantage that the provider server can receive the Wallet component from the ticket server while removing the processing load due to issuance of the Wallet component.

Next, the issued Wallet component is displayed on the Wallet application (step S180). The control unit 110 of the mobile device 100 displays the issued Wallet component on the Wallet application. That is, the controller 110 of the mobile device 100 may execute the Wallet application and display the issued Wallet component on the touch screen 190 on the Wallet application. At this time, the controller 110 may display the issued Wallet component on the touch screen by combining the common information of the Wallet component and the variable information of the Wallet component.

For example, as shown in FIG. 7C, the control unit 110 of the mobile device 100 executes the Wallet application and displays a Wallet component such as the issued coupon on the Wallet application on the touch screen 190 Can be displayed. The controller 110 of the mobile device 100 may display the variable information of the wallet component in the display layout corresponding to the common information of the wallet component. For example, as shown in FIG. 7C, the provider image logo and provider company name are displayed at the top, detailed information of the Wallet component is displayed at the center, and the barcode corresponding to the Wallet component and the number of the barcode are displayed at the bottom A provider image name 444 such as a coffee image, a provider company name 444 such as 'S Coffee', a coupon detail information 446 including a discount amount, a discount item, and an expiration date, Such as bar code 448, such as bar code 448, such as '1234-5678-9012', may be combined and displayed on the touch screen 190.

FIGS. 8-11 illustrate screens displayed on the Wallet application by the issued Wallet component.

Referring to FIG. 8, an example in which the issued Wallet component is a ticket is shown. That is, the issued Wallet component of FIG. 8 corresponds to a ticket ticket. The issued Wallet component corresponding to the ticket of FIG. 8 includes a provider image logo 402, a provider company name 404, ticket detail information 406, a barcode 408 corresponding to the ticket, Numeral 409 may be included. For example, as shown in FIG. 8, a provider image logo 402 such as an airplane image, a provider company name 404 such as 'K AIRLINE', a departure place corresponding to UA001 San Francisco corresponding to FLIGHT NUMBER, The detailed information 406 of the ticket including the destination, the gate number, the place number and the place of the rank, the bar code 408 corresponding to the ticket, and the number 409 of the bar code such as '1234-5678-9012' May be included in the issued Wallet component.

At this time, the issued Wallet component shown in FIG. 8 may include common information and variable information received from the provider server 200. The common information may be a display layout of the wallet component, and the variable information may be detailed information of the wallet component. Therefore, the provider image logo 402 and the provider company name 404 are displayed at the top, the ticket detail information 406 is displayed at the center, the barcode 408 corresponding to the ticket, the number 409 of the barcode, May be the common information. Thus, the display layout of the Wallet component corresponding to the common information may be common information that is fixed and unalterable among a plurality of Wallet components.

On the contrary, the variable information includes a ticket corresponding to FLIGHT NUMBER corresponding to the detailed information of the issued Wallet component, a ticket including a destination corresponding to UA001 San Francisco, a destination corresponding to Inchon, a gate number, a place number, The bar code 408 corresponding to the ticket, and the number 409 of the bar code such as '1234-5678-9012'. At this time, the detailed information of the wallet component corresponding to the variable information may be information that can be changed among the information forming the wallet component.

Therefore, the user of the provider server 200 does not change the display layout of the Wallet component corresponding to the common information, and the variable information can change only the detailed information of the Wallet component. That is, the user of the provider server 200 does not change the display layout of the Wallet component corresponding to the common information with respect to the plurality of Wallet components, and the detailed information of the Wallet component corresponding to the variable information And registers it in the ticket server 300.

Therefore, according to the embodiment of the present invention, by changing only the detailed information of the ticket corresponding to the variable information and registering the detailed information in the ticket server 300, various tickets can be registered in the ticket server by a simple method.

Referring to FIG. 9, an example in which the issued Wallet component is a ticket is shown. That is, the issued Wallet component of FIG. 9 corresponds to a movie ticket. The issued Wallet component corresponding to the movie ticket of FIG. 9 includes a provider image logo 412, a provider company name 414, detailed information 416 of a ticket, a barcode 418 corresponding to the ticket, Numeral 419 may be included. For example, as shown in FIG. 9, a provider image logo 412 such as a film image, a provider company name 414 such as 'F CINEMA', a screen number corresponding to MOVIE 1, a digit number, a screening date, The details 416 of the ticket including the barcode 418 corresponding to the ticket, and the number 419 of the barcode such as '1234-5678-9012' may be included in the wallet component.

At this time, the issued Wallet component shown in FIG. 9 may include common information and variable information received from the provider server 200. The common information may be a display layout of the wallet component, and the variable information may be detailed information of the wallet component. Therefore, the provider image logo 412 and the provider company name 414 are displayed at the top, the ticket detail information 416 is displayed at the center, the barcode 418 corresponding to the ticket, the number 419 of the barcode, May be the common information. Thus, the display layout of the Wallet component corresponding to the common information may be common information that is fixed and unalterable among a plurality of Wallet components.

In contrast, the variable information includes ticket detail information 416 including a screen number, a digit number, a screening date, and a screening time corresponding to MOVIE 1 corresponding to detailed information of the wallet component, a barcode 418), or a number 419 of the bar code such as '1234-5678-9012'. At this time, the detailed information of the wallet component corresponding to the variable information may be information that can be changed among the information forming the wallet component.

Therefore, according to the embodiment of the present invention, by changing only the detailed information of the ticket corresponding to the variable information and registering the detailed information in the ticket server 300, various tickets can be registered in the ticket server by a simple method.

Referring to FIG. 10, an example in which the issued Wallet component is a card is shown. That is, the issued Wallet component of FIG. 10 corresponds to a membership card. The issued Wallet component corresponding to the membership card of FIG. 10 includes a provider image logo 422, a provider company name 424, detailed information 426 of a card, a barcode 428 corresponding to the card, Numeral 429 may be included. For example, as shown in FIG. 10, a provider image 422 such as a mart bag image, a provider company name 424 such as 'K MART', card details 426 including a card number, a point, , A barcode 428 corresponding to the card, a number 429 of the barcode such as '1234-5678-9012' may be included in the issued Wallet component.

At this time, the issued Wallet component shown in FIG. 10 may include the common information and the variable information received from the provider server 200. The common information may be a display layout of the wallet component, and the variable information may be detailed information of the wallet component. Accordingly, the provider image logo 422 and the provider company name 424 are displayed at the top, the card detailed information 426 is displayed at the center, the bar code 428 corresponding to the card, the number 429 of the bar code, May be the common information. Thus, the display layout of the Wallet component corresponding to the common information may be common information that is fixed and unalterable among a plurality of Wallet components.

Conversely, the variable information may be a card number, a point, and an expiration date corresponding to the detailed information of the wallet component. At this time, the detailed information of the wallet component corresponding to the variable information may be information that can be changed among the information forming the wallet component.

Therefore, according to the embodiment of the present invention, only the detailed information of the card corresponding to the variable information is changed and registered in the ticket server 300, so that various cards can be registered in the ticket server by a simple method.

Referring to FIG. 11, the issued Wallet component is an example of a coupon. That is, the issued Wallet component of FIG. 11 corresponds to a coupon for a mat. The issued Wallet component corresponding to the coupon of FIG. 11 includes a provider image logo 432, a supplier company name 434, detailed information 436 of a coupon for a coupon, a barcode 438 corresponding to the coupon for coupon, The number 439 of bar codes may be included. For example, as shown in FIG. 11, detailed information 436 of a card including a provider image logo 432 such as a mat bag image, a provider company name 434 such as 'K MART', a discount amount, , A barcode 438 corresponding to the card, a number 439 of the barcode such as '1234-5678-9012' may be included in the wallet component.

At this time, the issued Wallet component shown in FIG. 11 may include common information and variable information received from the provider server 200. The common information may be a display layout of the wallet component, and the variable information may be detailed information of the wallet component. Therefore, the provider image logo 432 and the provider company name 434 are displayed at the top, the card detailed information 436 is displayed at the center, the bar code 438 corresponding to the card, the number 439 of the bar code, May be the common information. Thus, the display layout of the Wallet component corresponding to the common information may be common information that is fixed and unalterable among a plurality of Wallet components.

Conversely, the variable information may be a discount amount, a discount item, or an expiration date corresponding to detailed information of the wallet component. At this time, the detailed information of the wallet component corresponding to the variable information may be information that can be changed among the information forming the wallet component.

Therefore, according to the embodiment of the present invention, only the detailed information of the coupon corresponding to the variable information is changed and registered in the ticket server 300, so that various coupons can be registered in the ticket server by a simple method.

Therefore, according to the embodiment of the present invention, it is possible to register various wallet components in the ticket server by simply changing detailed information of the wallet component corresponding to the variable information and registering the detailed information in the ticket server .

The control unit 110 may display an enlarged bar (520) on the touch screen. When the drag on the enlarged bar is detected, the controller 110 may display the additional information 526 related to the issued Wallet component on the touch screen 190 as shown in FIG. 7D. At this time, the controller 110 may display a uniform 524 of additional information on the touch screen 190. The control unit 110 may display the reduced bar on the touch screen 190. At this time, the controller 110 may remove the displayed additional information 526 on the touch screen 190 when a drag on the reduced bar is detected.

And the issued Wallet component may be a plurality of. And the issued Wallet components may be displayed in a list view. That is, the control unit 110 can display the issued Wallet components as a list view, as shown in FIG. At this time, the wallet components may be arranged in columns according to categories. That is, as shown in FIG. 12, the wallet components may be arranged in columns according to categories such as tickets, cards, and coupons. For example, as shown in FIG. 12, tickets 610, 612, 614, 620, 622, and 624 may be displayed in the first and second columns closest to the top of the touch screen 190. As shown in FIG. 12, the airplane tickets 610, 612 and 614 and the movie tickets 620, 622 and 624 may be displayed in the first and second rows closest to the top of the touch screen 190. Next, the cards 630, 632, 634 may be displayed in the third column after the second column. Next, coupons 640, 642, and 644 may be displayed in the fourth column after the third column. Next, cards 650, 652, and 654, such as business cards, may be displayed in the fifth column after the fourth column.

The controller 110 scrolls the Wallet component when a drag or flick is detected for the Wallet component arranged along the column by category. For example, if a drag or flick is detected for the movie ticket 620 arranged in the second column in the category corresponding to the movie ticket, the movie ticket 620 can be scrolled. As shown in FIG. 12, when a drag or flick is detected for the movie ticket 620 arranged in the second column, the movie ticket 620 can be scrolled to display the next movie ticket 624 as shown in FIG.

14 is a flowchart illustrating a method of controlling a mobile device for issuing a Wallet component managed in a ticket server according to another embodiment of the present invention.

Referring to FIG. 14, common information of a wallet component is registered from a provider server to a ticket server (step S210). Common information of the Wallet component may be registered in the ticket server 300 from the provider server 200. [ That is, the common information of the wallet component stored in the provider server 200 may be transmitted to the ticket server 300 and stored in the storage unit 330 of the ticket server 300. At this time, the controller 210 of the provider server 200 may transmit the common information of the wallet component to the ticket server 300. Accordingly, registration with the ticket server 300 may mean that common information of the Wallet component transmitted from the provider server 200 is stored in the storage unit 330 of the ticket server 300. [ Transmission of the common information of the wallet component from the provider server 200 to the ticket server 300 is performed by using the communication unit 210 of the provider server 200 and the communication unit 310 of the ticket server 300 .

The ticket server 300 is a separate server that is different from the provider server 200. That is, the user of the provider server 200 (meaning a provider) can register common information of his / her Wallet component in a separate server 300 that is different from his / her server 200. The manager of the ticket server 300 can register and manage common information of a plurality of Wallet components from a plurality of provider servers 200. [

At this time, the Wallet component may be a coupon, a ticket, or a card. The coupon may be a discount coupon that can be used in a store. For example, the coupon may be a discount coupon for a certain amount that can be used when the shampoo is purchased at Mart. And the ticket can be used for the position of the user. For example, the ticket may be an admission ticket for boarding the airplane, or an admission ticket for entering the theater. And the card may be a membership card or a credit card. For example, the card may be a membership card that can be used in a mart.

Accordingly, the common information of the Wallet component may be registered in the ticket server 300 from the provider server 200. [ At this time, the Wallet component may be a coupon, a ticket, or a card. Therefore, the ticket server 300 may register common information of the Wallet component such as a coupon, a ticket, or a card. For example, common information of an airplane ticket can be registered in the ticket server 300 from the provider server 200. That is, the common information of the airplane ticket stored in the provider server 200 may be stored in the storage unit 330 of the ticket server 300 and registered. For example, a provider such as a K-airline may register common information of an airplane ticket stored in its provider server 200 in the ticket server 300. The manager of the ticket server 300 can store and manage the common information of the airplane ticket received from the provider server 200 to the K airline. Therefore, the ticket server 300 receives and registers common information of a wallet component (which may be referred to as a ticket) such as a coupon, a ticket, or a card from a plurality of provider servers 200, . In addition, the user of the provider server 200 registers common information of a wallet component (ticket) such as a coupon, a ticket or a card thereof in the ticket server 300 and provides it to the ticket server 300 Service can be used.

The wallet component includes common information and variable information received from the provider server 200. The common information means fixed information among the information forming the wallet component. That is, information that is fixed and common among a plurality of Wallet components. In contrast, the variable information means information that can be changed among the information forming the wallet component. That is, information that can be changed among a plurality of Wallet components and is not common. For example, the common information may be a display layout of the Wallet component, and the variable information may be detailed information of the Wallet component. That is, the display layout of the Wallet component corresponding to the common information may be fixed and common information among a plurality of Wallet components. Conversely, the detailed information of the Wallet component corresponding to the variable information may be information that can be changed among the information forming the Wallet component.

Next, common information of the Wallet component registered in the ticket server is received from the provider server (step S220). The mobile device 100 receives common information of the Wallet component registered in the ticket server 300 from the provider server 200. [ That is, the control unit 110 of the mobile device 100 can receive the common information of the wallet component registered in the ticket server 300 from the provider server 200 through the communication unit 120.

Next, the Wallet component is displayed on the provider application (step S230). The controller 110 of the mobile device 100 executes the provider application and displays the Wallet component on the touch screen 190. [

Next, an issuance request for the Wallet component is selected (step S240). The controller 110 of the mobile device 100 may detect a selection of an issuance request for the Wallet component. At this time, the controller 110 may detect a selection of an issuance request for the Wallet component as a selection of an issuance request icon displayed on the provider application. That is, when the controller 110 detects the selection of the issuance request icon displayed on the provider application, it can recognize that the issuance request for the Wallet component is selected. At this time, the selection of the issuance request icon displayed on the provider application may be a touch to the issuance request icon 510.

Next, the issuance of the selected Wallet component is requested to the ticket server (step S250). The controller 110 of the mobile device 100 may request the issuance of the selected Wallet component to the ticket server when a touch on the issuance request icon displayed on the provider application is detected.

Next, variable information of the selected Wallet component is registered in the ticket server (step S255). The controller 110 of the mobile device 100 may transmit the variable information of the selected Wallet component to the ticket server 300 and register the changed information. At this time, the controller 110 of the mobile device 100 transmits variable information of the selected Wallet component to the provider server 200, and the provider server 200 transmits variable information of the selected Wallet component to the ticket It may be transmitted to the server 300 for registration.

Next, in response to the requested Wallet component, the ticket server issues a Wallet component including the common information and the variable information (step S260). The ticket server 300, which has been requested to issue the selected Wallet component, issues the selected Wallet component. At this time, the ticket server 300 may issue the Wallet component by combining the common information of the received Wallet component with the variable information of the Wallet component. That is, the ticket server 300 may issue the Wallet component by combining the common information of the Wallet component received in step 210 and the variable information of the Wallet component received in step S255 described above.

Next, an ID (ID) of a Wallet component corresponding to the Wallet component issued by the ticket server is received from the ticket server (step S272). The mobile device 100 may receive an ID of a Wallet component corresponding to a Wallet component issued from the ticket server 300 from the ticket server 300. [ At this time, the ticket server 300 may generate an ID of a Wallet component corresponding to the issued Wallet component and transmit it to the mobile device 100. In step S210, the mobile terminal 100 may receive the ID of the Wallet component corresponding to the Wallet component issued from the provider server 200 and transmit the ID to the mobile device 100. [

Next, the ID of the received Wallet component is transmitted from the provider application to the Wallet application (step S274). The mobile device 100 may send the identity of the received Wallet component to the Wallet application in the provider application. That is, the mobile device may send the identity of the received Wallet component to the Wallet application if the currently running application is a provider application. Accordingly, the Wallet application can request the issued Wallet component using the ID of the received Wallet component.

Next, the issued Wallet component is requested to the ticket server using the ID of the received Wallet component on the Wallet application (step S276). The mobile device 110 may request the issued Wallet component to the ticket server using the identity of the received Wallet component on the Wallet application.

Next, the issued Wallet component is received from the ticket server on the Wallet application (step S278). That is, the mobile device 100 may receive the Wallet component issued from the ticket server 300 in response to the requested Wallet component from the ticket server 300. At this time, the ticket server 300 can identify the issued Wallet component using the ID of the received Wallet component, and transmit the issued Wallet component to the mobile device 100.

Next, the issued Wallet component is displayed on the Wallet application (step S280). The control unit 110 of the mobile device 100 displays the issued Wallet component on the Wallet application. That is, the controller 110 of the mobile device 100 may execute the Wallet application and display the issued Wallet component on the touch screen 190 on the Wallet application.

Therefore, according to another embodiment of the present invention, the Wallet component issued using the ID of the received Wallet component can be received from the ticket server. That is, there is an advantage that a simple issued Wallet component can be received from the ticket server using an ID that can identify the issued Wallet component.

15 is a flowchart illustrating a method of controlling a mobile device for issuing a Wallet component managed in a ticket server according to another embodiment of the present invention. The flowchart according to another embodiment of the present invention shown in FIG. 15 is a flowchart showing steps after step S180 in step S110 shown in FIG. Therefore, another embodiment of the present invention shown in FIG. 15 includes the step S180 shown in FIG. 5 first in step S110, and the step S180 is followed by the steps S310 and S360. Steps S310 to S360 will be described below.

Referring to FIG. 15, when updating the received Wallet component, the ticket server receives updated Wallet component information from the provider server (S310). The user of the provider server 200 may perform an update for the Wallet component. At this time, the provider server 200 may transmit updated Wallet component information to the ticket server 300. [ For example, if an expiration date for a coupon is modified, the provider server 200 may send updated wallet component information with the updated expiration date to the ticket server 300. [ Therefore, according to another embodiment of the present invention, the provider server can perform the update through the ticket server without transmitting the update information directly to the mobile device when an update to the Wallet component occurs.

Next, the ticket server searches a plurality of mobile devices to be transmitted (step S320). The ticket server 300 has transmitted the Wallet component issued in step S170. Accordingly, the ticket server 300 needs to transmit the updated Wallet component information to the mobile device that has transmitted the issued Wallet component. Accordingly, the ticket server searches for a mobile device that has transmitted the issued Wallet component. A user of the mobile device may use a plurality of mobile devices. For example, a user may use a plurality of mobile devices such as a smart phone, a tab book, and a smart TV. At this time, when an update is made to the issued Wallet component, the user needs to check the updated (updated) Wallet component information in all of the plurality of mobile devices. Accordingly, when the ticket server 300 has transmitted the issued Wallet component to, for example, a smart phone, a tab book, or a smart TV, the ticket server 300 searches the plurality of mobile devices such as a smart phone, can do. At this time, the ticket server 300 may store information on the mobile device, user information, and authentication information in a storage unit. For example, the ticket server 300 may store the information about the AA smartphone, the BB tab book, and the CC smart TV in the storage unit 330 with respect to the user A. Accordingly, the ticket server 300 can search AA smart phones, BB tab books, and CC smart TVs with a plurality of mobile devices to be transmitted.

Thus, according to another embodiment of the present invention, the ticket server searches for a plurality of mobile devices to transmit updates and sends update information to all of the plurality of mobile devices, thereby updating the updated Wallet component Can be synchronized with each other.

Next, the mobile device receives the updated Wallet component information from the ticket server (step S330). The ticket server 300 may transmit the updated Wallet component information to the plurality of mobile devices to be searched. And the retrieved plurality of mobile devices to receive the updated Wallet component information. For example, as shown in FIG. 15, when the first mobile device and the second mobile device are the retrieved plurality of mobile devices to transmit, the ticket server 300 transmits the updated Wallet component information can be transferred.

Next, a notification corresponding to the updated Wallet component information is displayed on the touch screen (step S340). The controller 110 of the mobile device 100 may display a notification corresponding to the updated Wallet component information on the touch screen. For example, as shown in FIG. 16A, the control unit 110 of the mobile device transmits a Wallet component such as a coupon to a provider image logo 442 such as a coffee image, a provider company name 444 such as 'S Coffee' Detailed information 446 of a coupon including a discounted product and an expiration date, a bar code 448 corresponding to the coupon, a number 449 of the bar code such as '1234-5678-9012' Can be displayed. The controller 110 may display the notification 700 corresponding to the updated Wallet component information received in step S330 on the touch screen 190 as shown in FIG. 16B. For example, as shown in FIG. 16B, a notification indicating that the expiration date has been changed can be displayed on the touch screen 190.

Next, a gesture for selecting the notification is detected (step S350). The control unit 110 of the mobile device can detect a gesture for selecting the notification. For example, the gesture may be a gesture that touches the notification. Accordingly, the controller 110 may determine that the gesture for selecting the notification is detected when the touch for the notification is recognized.

Next, when the gesture is detected, the updated wallet component information corresponding to the notification is displayed on the touch screen (step S360). If a gesture for selecting the notification is detected in step S350, the controller 110 may display the updated Wallet component information corresponding to the notification on the touch screen. For example, as shown in FIG. 16C, when the expiration date of the coupon is updated (updated) from 2012.12.24 to 2012.12.10, the updated expiration date 2012.12.10 corresponding to the updated Wallet component information is displayed on the touch screen Can be displayed.

Therefore, according to another embodiment of the present invention, the provider server can perform the update through the ticket server when the update to the Wallet component occurs, thereby eliminating the overload due to the update.

It will be appreciated that embodiments of the present invention may be implemented in hardware, software, or a combination of hardware and software. Such arbitrary software may be stored in a memory such as, for example, a volatile or non-volatile storage device such as a storage device such as ROM or the like, or a memory such as a RAM, a memory chip, a device or an integrated circuit, , Or a storage medium readable by a machine (e.g., a computer), such as a CD, a DVD, a magnetic disk, or a magnetic tape, as well as being optically or magnetically recordable. Embodiments of the present invention may also be implemented by a computer or a mobile terminal including a controller and a memory and the memory may be read by a machine suitable for storing programs or programs containing instructions embodying embodiments of the present invention. It can be seen that this is an example of a storage medium that can be used. Accordingly, the invention includes a program comprising code for implementing the apparatus or method as claimed in any of the claims herein, and a storage medium readable by a machine (such as a computer) for storing such a program. In addition, such a program may be electronically transported through any medium such as a communication signal transmitted via a wired or wireless connection, and the present invention appropriately includes the same.

In addition, the mobile device may receive and store the program from a program providing device connected by wire or wireless. The program providing apparatus includes a memory for storing a program including instructions for performing the embodiments of the present invention, information necessary for embodiments of the present invention, and the like, and a memory for performing wired or wireless communication with the mobile apparatus And a control unit for transmitting the program to the transceiver upon request or automatically by the mobile device.

100: mobile device
200: provider server
300: Ticket server

Claims (19)

Receiving common information of the Wallet component registered in the ticket server from the provider server;
Displaying the Wallet component on a provider application;
Selecting an issuance request for the Wallet component;
Requesting issuance of the selected Wallet component to the ticket server;
Transmitting variable information of the selected Wallet component to the ticket server;
Receiving an issued Wallet component issued from the ticket server corresponding to the requested Wallet component and including the common information and the variable information from the ticket server;
And displaying the issued Wallet component on a Wallet application. ≪ Desc / Clms Page number 19 > The method according to claim 1,
Wherein the Wallet component is a coupon, a ticket, or a card. The method according to claim 1,
Wherein the common information is a display layout of the Wallet component and the variable information is detailed information of the Wallet component. The method according to claim 1,
Wherein the common information comprises an identification key identifying a display layout of the Wallet component. ≪ Desc / Clms Page number 20 > The method according to claim 1,
In the step of selecting an issuance request for the Wallet component,
Further comprising detecting a selection of an issuance request icon displayed on the provider application. ≪ Desc / Clms Page number 21 > The method according to claim 1,
Requesting issuance of the selected Wallet component to the ticket server,
Requesting issuance of the selected Wallet component to the provider server so that the provider server requests the issuance of the selected Wallet component to the ticket server,
And requesting the issuance of the selected Wallet component directly to the ticket server. The method according to claim 1,
Receiving from the ticket server an issued Wallet component issued by the ticket server corresponding to the requested Wallet component and including the common information and the variable information,
Receiving an ID of a Wallet component corresponding to a Wallet component issued from the ticket server from the ticket server;
Transferring the identity of the received Wallet component from the provider application to the Wallet application;
Requesting the issued Wallet component to the ticket server using the ID of the received Wallet component on the Wallet application;
Further comprising receiving from the ticket server the issued Wallet component on the Wallet application. ≪ RTI ID = 0.0 > 31. < / RTI > The method according to claim 1,
Further comprising updating the received Wallet component. ≪ RTI ID = 0.0 > 31. < / RTI > 9. The method of claim 8,
In updating the received Wallet component,
Receiving updated Wallet component information received from the provider server from the ticket server;
Displaying an alert corresponding to the updated Wallet component information on the touch screen;
Detecting a gesture for selecting the notification;
Further comprising displaying the updated Wallet component information corresponding to the notification on the touch screen when the gesture is detected. ≪ RTI ID = 0.0 > 10. < / RTI & . Receiving common information of a Wallet component from a provider server,
Receive an issuance request for the Wallet component from a mobile device,
Issue a Wallet component comprising the common information and the variable information corresponding to the requested Wallet component,
A controller for transmitting the issued Wallet component to the mobile device
A communication unit for communicating with the mobile device and the provider server,
And a store for storing the Wallet component. Receiving common information of the Wallet component registered in the ticket server from the provider server,
Displaying the Wallet component on a provider application,
An issuance request for the Wallet component is selected,
Request an issuance of the selected Wallet component to the ticket server,
Transmitting the variable information of the selected Wallet component to the ticket server,
Receiving from the ticket server an issued Wallet component issued by the ticket server corresponding to the requested Wallet component and including the common information and the variable information,
A control unit for displaying the issued Wallet component on the Wallet application;
A touch screen for displaying the Wallet component on the provider application and displaying the issued Wallet component on the Wallet application;
And a store for storing the Wallet component. ≪ Desc / Clms Page number 19 > 12. The method of claim 11,
Wherein the Wallet component is a coupon, a ticket, or a card. 12. The method of claim 11,
Wherein the common information is a display layout of the Wallet component and the variable information is detailed information of the Wallet component. 12. The method of claim 11,
Wherein the common information comprises an identification key identifying a display layout of the Wallet component. ≪ Desc / Clms Page number 22 > 12. The method of claim 11,
Wherein,
When an issuance request for the Wallet component is selected,
Detecting a selection of an issuance request icon displayed on the provider application. ≪ Desc / Clms Page number 21 > 12. The method of claim 11,
Wherein,
When requesting issuance of the selected Wallet component to the ticket server,
Requesting issuance of the selected Wallet component to the provider server so that the provider server requests the issuance of the selected Wallet component to the ticket server,
And requesting the issuance of the selected Wallet component directly to the ticket server. ≪ RTI ID = 0.0 > 11. < / RTI > 12. The method of claim 11,
Wherein,
Upon receiving from the ticket server an issued Wallet component issued by the ticket server corresponding to the requested Wallet component and including the common information and the variable information,
Receiving an ID of a Wallet component corresponding to a Wallet component issued from the ticket server from the ticket server,
Transferring the identity of the received Wallet component from the provider application to the Wallet application,
Requesting the issued Wallet component to the ticket server using the ID of the received Wallet component on the Wallet application,
And receive the issued Wallet component from the ticket server on the Wallet application. 12. The method of claim 11,
Wherein,
And updates the received Wallet component. ≪ Desc / Clms Page number 24 > 19. The method of claim 18,
Wherein,
Upon updating the received Wallet component,
From the ticket server, updated Wallet component information received from the provider server,
Displaying an alert corresponding to the updated Wallet component information on the touch screen,
Detecting a gesture for selecting the notification,
And when the gesture is detected, displaying the updated Wallet component information corresponding to the notification on the touch screen. ≪ Desc / Clms Page number 19 >

Images