WO2015147413A1

WO2015147413A1 - Mobile terminal and method for controlling the same

Info

Publication number: WO2015147413A1
Application number: PCT/KR2014/012114
Authority: WO
Inventors: Wongab JEON; Inhui HWANG; Wonjong Lee; Joonhaeng HEO
Original assignee: Lg Electronics Inc.
Priority date: 2014-03-27
Filing date: 2014-12-10
Publication date: 2015-10-01

Abstract

A mobile terminal and method for controlling the same are disclosed. In supporting HCE (host-based card emulation), the present invention includes the steps of downloading a first application related to an NFC (near field communication) card and first application related information related to the first application and based on an NFC processing mode and second information in the application related information, processing the first information in the application related information if a preset condition is met. The preset condition includes at least one of a condition of installing the downloaded first application and a condition of installing the downloaded first application and then detecting a user command for initially running the installed first application. The NFC processing mode includes either an off-host mode on the basis of a route for the NFC controller to route the third information to the SE or an on-host mode on the basis of a route for the NFC controller to route the third information to the host framework.

Description

MOBILE TERMINAL AND METHOD FOR CONTROLLING THE SAME

The present invention relates to a mobile terminal, and more particularly, to a mobile terminal and method for controlling the same. Although the present invention is suitable for a wide scope of applications, it is particularly suitable for implementing a use of a terminal in further consideration of user’s convenience.

Terminals may be generally classified as mobile/portable terminals or stationary terminals according to their mobility. Mobile terminals may also be classified as handheld terminals or vehicle mounted terminals according to whether or not a user can directly carry the terminal.

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.

Efforts are ongoing to support and increase the functionality of mobile terminals. Such efforts include software and hardware improvements, as well as changes and improvements in the structural components.

Recently, the ongoing trend is to release mobile terminals supportive of NFC (near field communication) card emulation. NFC means a communication technology for exchanging wireless data between devices located in a close distance within about 10 seconds. A user of a mobile terminal supportive of NFC card emulation saves credit information related to a credit card or a transportation card in the mobile terminal instead of carrying the credit card or the transportation card separately and is then able to charge a fee on user’s credit or transportation card by simply tapping the mobile terminal on an NFC reader.

FIG. 1 is a schematic block diagram of components of a mobile terminal supportive of NFC card emulation according to a related art. FIG. 1 (a) shows a mobile terminal 10a on which OS of a version previous to Android 4.4 is located. And, FIG. 1 (b) shows a mobile terminal 10a on which OS of Android 4.4 version is located.

Referring to FIG. 1 (a), a mobile terminal 10a according to a related art consists of a host CPU 11, an NFC controller 12 and an SE (secure element) 13. The host CPU 11 stores an application related to an NFC card. The mobile terminal 10a according to the related art can communicate with the NFC reader 14 located externally through the SE 13 only. NFC card emulation is performed through the SE 13. If a user holds the mobile terminal 10a to the NFC reader 14, the NFC controller 12 routes data, which was transmitted from the NFC reader 14, to the SE 13.

Referring to FIG. 1 (b), An OS of Android 4.4 version is loaded on a mobile terminal 10b that is implemented to enable NFC card emulation without including the SE 13. The mobile terminal 10b supports an HCE (host-based card emulation) function. Hence, an application related to the NFC card can be emulated through the host CPU 11. If a user holds the mobile terminal 10b to the NFC reader 14, data transmitted from the NFC reader 14 is routed not to the SE 13 but to the host CPU 11.

In case of the mobile terminal supportive of the HCE function, the NFC controller 12 stores a routing table for managing AID (application ID). Based on the routing table, the controller 12 determines whether the mobile terminal routes the data received from the reader 14 to the host CPU 11 or the SE 13. However, limitation is put on capacity of the routing table due to the limited internal chip capacity of the NFC controller 12. If the storage capacity of the routing table overflows, it causes a problem that it is unclear how to handle the overflowing storage capacity.

Accordingly, an object of the present invention is to address the above-noted and other problems.

Another object of the present invention is to provide a mobile terminal and method for controlling the same, by which a problem of an overflowing storage capacity of a routing table in an NFC controller of a mobile terminal supportive of HCE (host-based card emulation) function can be solved.

Technical tasks obtainable from the present invention are non-limited by the above-mentioned technical tasks. And, other unmentioned technical tasks can be clearly understood from the following description by those having ordinary skill in the technical field to which the present invention pertains.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.

To achieve these and other advantages and in accordance with the purpose of the present invention, as embodied and broadly described, a method of controlling a mobile terminal supportive of HCE (host-based card emulation) according to one embodiment of the present invention includes the steps of downloading a 1st application related to an NFC (near field communication) card and a 1st application related information related to the 1st application, the 1st application related information including a 1st information for identifying the NFC card and a 2nd information indicating whether the NFC card is emulated through an SE (secure element) or a host framework and based on an NFC processing mode for determining a routing route of a 3rd information for identifying a specific NFC card received by an NFC controller from an external NFC reader and the 2nd information, processing the 1st information if a preset condition is met, wherein the preset condition includes at least one of a condition of installing the downloaded 1st application and a condition of installing the downloaded 1st application and then detecting a user command for initially running the installed 1st application and wherein the NFC processing mode includes an off-host mode on the basis of a route for the NFC controller to route the 3rd information to the SE or an on-host mode on the basis of a route for the NFC controller to route the 3rd information to the host framework.

To further achieve these and other advantages and in accordance with the purpose of the present invention, as embodied and broadly described, in controlling a mobile terminal supportive of HCE (host-based card emulation), the mobile terminal according to another embodiment of the present invention includes a host framework, an SE (secure element), an NFC controller configured to route a data communication between an external NFC reader and the host framework and a data communication between the external NFC reader and the SE, and a display unit, wherein the host framework saves applications related to an NFC (near field communication) card and application related information, wherein the application related information includes a 1st information for identifying the NFC card related to each of the applications and a 2nd information indicating whether the NFC card is emulated through an SE (secure element) or a host framework, wherein based on an NFC processing mode for determining a routing route of a 3rd information for identifying a specific NFC card received from the external NFC reader and the 2nd information, the NFC controller saves a routing table in which the 1st information for identifying at least one NFC card is saved, wherein the NFC processing mode includes an off-host mode on the basis of a route for the NFC controller to route the 3rd information to the SE or an on-host mode on the basis of a route for the NFC controller to route the 3rd information to the host framework, wherein the host framework detects an excess of a storage capacity of the routing table within the NFC controller if a preset condition is met, and wherein the host framework controls the display unit to output a notification message indicating that the storage capacity of the routing table is exceeded.

Further scope of applicability of the present invention will become apparent from the detailed description given hereinafter. However, it should be understood that the detailed description and specific examples, while indicating preferred embodiments of the invention, are given by illustration only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description.

A mobile terminal and method for controlling the same according to the present invention provide the following effects and/or features.

According to at least one of embodiments of the present invention, if a storage capacity of a routing table in an NFC controller of a mobile terminal supportive of HCE (host-based card emulation) function is exceeded, a solution for solving this problem can be provided.

The present invention will become more fully understood from the detailed description given herein below and the accompanying drawings, which are given by illustration only, and thus are not limitative of the present invention, and wherein:

FIG. 1 is a schematic block diagram of components of a mobile terminal supportive of NFC card emulation according to a related art;

FIG. 2a is a block diagram of a mobile terminal in accordance with the present disclosure;

FIGS. 2b and 2c are conceptual views of one example of the mobile terminal, viewed from different directions;

FIG. 3 is a conceptual view of a deformable mobile terminal according to an alternative embodiment of the present disclosure;

FIG. 4 is a conceptual view of a wearable mobile terminal according to another alternative embodiment of the present disclosure;

FIG. 5 is a conceptual view of a wearable mobile terminal according to another alternative embodiment of the present disclosure;

FIG. 6 is a schematic block diagram of components of the mobile terminal shown in FIG. 2a to describe one embodiment of the present invention;

FIG. 7 is a flowchart to describe a routing route of data received from an NFC reader if a mobile of a mobile terminal according to one embodiment of the present invention is set to an off-host mode;

FIG. 8 is a flowchart to describe a routing route of data received from an NFC reader if a mobile of a mobile terminal according to one embodiment of the present invention is set to an on-host mode;

FIG. 9 is a diagram for one example of application related information of applications related to an NFC card according to one embodiment of the present invention;

FIG. 10 is a diagram for another example of application related information of applications related to an NFC card according to one embodiment of the present invention.

FIG. 11 is a flowchart to describe one example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention;

FIG. 12 is a flowchart to describe another example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention;

FIG. 13 is a flowchart to describe further example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention;

FIG. 14 is a flowchart to describe another further example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention;

FIG. 15 is a diagram to describe one example of a screen outputted through a display unit of a mobile terminal according to one embodiment of the present invention.

FIG. 16 is a diagram to describe one example of a method of changing an NFC processing mode in a mobile terminal according to one embodiment of the present invention;

FIG. 17 is a flowchart to describe one example of a method of solving a problem of an exceeded storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention;

FIG. 18 is a flowchart to describe one example of a case of outputting a guide message for guiding a user in changing an NFC processing mode if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded;

FIG. 19 is a diagram to describe one example of a guide message for guiding a user in changing an NFC processing mode outputted through a display unit if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded;

FIG. 20 is a diagram to describe one example of a guide message for guiding a user in deleting an application outputted through a display unit if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded;

FIG. 21 is a diagram to describe one example of a screen outputted through a display unit if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded; and

FIG. 22 is a diagram to describe a method of solving a problem, which is caused if a storage capacity of a routing table in an NFC controller is exceeded due to an NFC processing mode changed by a user, according to one embodiment of the present invention.

Description will now be given in detail according to exemplary embodiments disclosed herein, with reference to the accompanying drawings. For the sake of brief description with reference to the drawings, the same or equivalent components may be provided with the same reference numbers, and description thereof will not be repeated. In general, a suffix such as "module" and "unit" may be used to refer to elements or components. Use of such a suffix herein is merely intended to facilitate description of the specification, and the suffix itself is not intended to give any special meaning or function. In the present disclosure, that which is well-known to one of ordinary skill in the relevant art has generally been omitted for the sake of brevity. The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings.

Referring to FIGs. 2a to 2c, FIG. 2a is a block diagram to describe a mobile terminal related to the present invention. FIG. 2b and FIG. 2c are conceptional diagrams of a mobile terminal related to the present invention viewed in different directions, respectively.

It will be understood that although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

It will be understood that when an element is referred to as being “connected with” another element, the element can be connected with the other element or intervening elements may also be present. In contrast, when an element is referred to as being “directly connected with” another element, there are no intervening elements present.

A singular representation may include a plural representation unless it represents a definitely different meaning from the context. Terms such as “include” or “has” are used herein and should be understood that they are intended to indicate an existence of several components, functions or steps, disclosed in the specification, and it is also understood that greater or fewer components, functions, or steps may likewise be utilized.

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 (for example, smart watches, smart glasses, head mounted displays (HMDs)), and the like.

By way of non-limiting example only, further description will be made with reference to particular types of mobile terminals. However, such teachings apply equally to other types of terminals, such as those types noted above. In addition, these teachings may also be applied to stationary terminals such as digital TV, desktop computers, and the like.

Reference is now made to FIGS. 2a-2c, where FIG. 2a is a block diagram of a mobile terminal in accordance with the present disclosure, and FIGS. 2B and 2c are conceptual views of one example of the mobile terminal, viewed from different directions.

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, a power supply unit 190 and a secure element, SE, 195. 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 SE 195 can be configured to encrypt card information of a credit card, a membership card, a transportation card, etc. The SE 195 is in charge of encryption and decryption when communicating between a card terminal such as an NFC reader and the mobile terminal 100. The SE 195 may be embedded in the mobile terminal 100 or may be connected to the mobile terminal 100 as a form of a removable memory. For example, the SE 195 can be embodied as an Embedded SE, a SIM(Subscriber Identity Module) card, an UICC(Universal IC Card), an USIM(Universal Subscriber Identity Module) card, an SD card, an MMC card, etc.

Referring now to FIG. 2a, the mobile terminal 100 is shown having wireless communication unit 110 configured with several commonly implemented components. For instance, 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 (for example, a touch key, a push key, a mechanical key, a soft key, and the like) for allowing a user to input information. Data (for example, audio, video, image, and the like) is obtained by the input unit 120 and may be analyzed and processed by controller 180 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. For example, in FIG. 2a, the sensing unit 140 is shown having a proximity sensor 141 and an illumination sensor 142.

If desired, the sensing unit 140 may alternatively or additionally include other types of sensors or devices, such as a touch sensor, an acceleration sensor, a magnetic sensor, a G-sensor, a gyroscope sensor, a motion sensor, an RGB sensor, an infrared (IR) sensor, a finger scan sensor, a ultrasonic sensor, an optical sensor (for example, camera 121), a microphone 122, a battery gauge, an environment sensor (for example, a barometer, a hygrometer, a thermometer, a radiation detection sensor, a thermal sensor, and a gas sensor, among others), and a chemical sensor (for example, 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 can be coupled to the mobile terminal 100. The interface unit 160, for example, 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. In some cases, 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. For instance, 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 (for example, 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. 2a, or activating application programs stored in the memory 170. As one example, the controller 180 controls some or all of the components illustrated in FIGS. 2a-2c according to the execution of an application program that have been stored in the memory 170.

The power supply unit 190 can 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.

Referring still to FIG. 2a, various components depicted in this figure will now be described in more detail. Regarding the wireless communication unit 110, 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. In some embodiments, 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 broadcast managing entity may be implemented using a server or system which generates and transmits a broadcast signal and/or broadcast associated information, or a server which receives a pre-generated broadcast signal and/or broadcast associated information, and sends such items to the mobile terminal. The broadcast signal may be implemented using any of a TV broadcast signal, a radio broadcast signal, a data broadcast signal, and combinations thereof, among others. The broadcast signal in some cases may further include a data broadcast signal combined with a TV or radio broadcast signal.

The broadcast signal may be encoded according to any of a variety of technical standards or broadcasting methods (for example, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), Digital Video Broadcast (DVB), Advanced Television Systems Committee (ATSC), and the like) for transmission and reception of digital broadcast signals. The broadcast receiving module 111 can receive the digital broadcast signals using a method appropriate for the transmission method utilized.

Examples of broadcast associated information may include information associated with a broadcast channel, a broadcast program, a broadcast event, a broadcast service provider, or the like. The broadcast associated information may also be provided via a mobile communication network, and in this case, received by the mobile communication module 112.

The broadcast associated information may be implemented in various formats. For instance, broadcast associated information may include an Electronic Program Guide (EPG) of Digital Multimedia Broadcasting (DMB), an Electronic Service Guide (ESG) of Digital Video Broadcast-Handheld (DVB-H), and the like. Broadcast signals and/or broadcast associated information received via the broadcast receiving module 111 may be stored in a suitable device, such as a memory 170.

The mobile communication module 112 can transmit and/or receive wireless signals to and from one or more network entities. Typical examples of 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 (for example, 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.

Examples of such wireless Internet access 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.

In some embodiments, 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.

In some embodiments, 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. In addition, 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. Hence, 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 can 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. As an example, 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.

As one example, when the mobile terminal uses a GPS module, a position of the mobile terminal may be acquired using a signal sent from a GPS satellite. As another example, when the mobile terminal uses the Wi-Fi module, a position of the mobile terminal can 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.

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 can 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 can be processed in various manners according to a function being executed in the mobile terminal 100. If desired, 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 (for example, 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. As one example, 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. On the other hand, 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, for example, 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. When the touch screen is implemented as a capacitance type, the proximity sensor 141 can 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. In this case, the touch screen (touch sensor) may also be categorized as a proximity sensor.

The term “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. The term “contact touch” will often be referred to herein to denote the scenario in which a pointer makes physical contact with the touch screen. For the position corresponding to the proximity touch of the pointer relative to the touch screen, such position will correspond to a position where the pointer is perpendicular to the touch screen. The proximity sensor 141 may sense proximity touch, and proximity touch patterns (for example, distance, direction, speed, time, position, moving status, and the like).

In general, 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. In addition, the controller 180 can 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 can 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.

As one example, 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.

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. Accordingly, the controller 180 may sense which region of the display unit 151 has been touched. Here, the touch controller may be a component separate from the controller 180, the controller 180, and combinations thereof.

In some embodiments, 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.

If desired, an ultrasonic sensor may be implemented to recognize position information relating to a touch object using ultrasonic waves. The controller 180, for example, 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.

Implementing the camera 121 with a laser sensor may allow detection of a touch of a physical object with respect to a 3D stereoscopic image. 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. In more detail, 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. For example, 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.

In some embodiments, 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.

In general, a 3D stereoscopic image may include a left image (e.g., a left eye image) and a right image (e.g., a right eye image). According to how left and right images are combined into a 3D stereoscopic image, a 3D stereoscopic imaging method can be divided into a top-down method in which left and right images are located up and down in a frame, an L-to-R (left-to-right or side by side) method in which left and right images are located left and right in a frame, a checker board method in which fragments of left and right images are located in a tile form, an interlaced method in which left and right images are alternately located by columns or rows, and a time sequential (or frame by frame) method in which left and right images are alternately displayed on a time basis.

Also, as for a 3D thumbnail image, a left image thumbnail and a right image thumbnail can be generated from a left image and a right image of an original image frame, respectively, and then combined to generate a single 3D thumbnail image. In general, the term “thumbnail” may be used to refer to a reduced image or a reduced still image. A generated left image thumbnail and right image thumbnail may be displayed with a horizontal distance difference there between by a depth corresponding to the disparity between the left image and the right image on the screen, thereby providing a stereoscopic space sense.

A left image and a right image required for implementing a 3D stereoscopic image may be displayed on the stereoscopic display unit using a stereoscopic processing unit. The stereoscopic processing unit can receive the 3D image and extract the left image and the right image, or can receive the 2D image and change it into a left image and a right image.

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 can 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 can 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 can 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.

Besides vibration, the haptic module 153 can 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 can absorb or generate heat, and the like.

The haptic module 153 can 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 can 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. For example, the interface unit 160 can 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 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. In addition, 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 can be connected with the terminal 100 via the interface unit 160.

When the mobile terminal 100 is connected with an external cradle, the interface unit 160 can 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 can store programs to support operations of the controller 180 and store input/output data (for example, 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 typically control the general operations 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 can also perform the controlling and processing associated with voice calls, data communications, video calls, and the like, or perform pattern recognition processing to recognize a handwriting input or a picture drawing input performed on the touch screen as characters or images, respectively. In addition, the controller 180 can 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 provide internal power and supply the appropriate power required for operating respective elements and components 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.

As another example, the power supply unit 190 may be configured to recharge the battery in a wireless manner without use of the connection port. In this example, the power supply unit 190 can 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.

Referring now to FIGS. 2B and 2C, the mobile terminal 100 is described with reference to a bar-type terminal body. However, the mobile terminal 100 may alternatively be implemented in any of a variety of different configurations. Examples of such configurations include watch-type, clip-type, glasses-type, or as a folder-type, flip-type, slide-type, swing-type, and swivel-type in which two and more bodies are combined with each other in a relatively movable manner, and combinations thereof. Discussion herein will often relate to a particular type of mobile terminal (for example, bar-type, watch-type, glasses-type, and the like). However, such teachings with regard to a particular type of mobile terminal will generally apply to other types of mobile terminals as well.

The mobile terminal 100 will generally include a case (for example, frame, housing, cover, and the like) forming the appearance of the terminal. In this embodiment, the case is formed using a front case 101 and a rear case 102. Various electronic components are incorporated into a space formed between the front case 101 and the rear case 102. At least one middle case may be additionally positioned between the front case 101 and the rear case 102.

The display unit 151 is shown located on the front side of the terminal body to output information. As illustrated, a window 151a of the display unit 151 may be mounted to the front case 101 to form the front surface of the terminal body together with the front case 101.

In some embodiments, electronic components may also be mounted to the rear case 102. Examples of such electronic components include a detachable battery 191, an identification module, a memory card, and the like. Rear cover 103 is shown covering the electronic components, and this cover may be detachably coupled to the rear case 102. Therefore, when the rear cover 103 is detached from the rear case 102, the electronic components mounted to the rear case 102 are externally exposed.

As illustrated, when the rear cover 103 is coupled to the rear case 102, a side surface of the rear case 102 is partially exposed. In some cases, upon the coupling, the rear case 102 may also be completely shielded by the rear cover 103. In some embodiments, the rear cover 103 may include an opening for externally exposing a camera 121b or an audio output module 152b.

The

cases

101, 102, 103 may be formed by injection-molding synthetic resin or may be formed of a metal, for example, stainless steel (STS), aluminum (Al), titanium (Ti), or the like.

As an alternative to the example in which the plurality of cases form an inner space for accommodating components, the mobile terminal 100 may be configured such that one case forms the inner space. In this example, a mobile terminal 100 having a uni-body is formed in such a manner that synthetic resin or metal extends from a side surface to a rear surface.

If desired, the mobile terminal 100 may include a waterproofing unit (not shown) for preventing introduction of water into the terminal body. For example, the waterproofing unit may include a waterproofing member which is located between the window 151a and the front case 101, between the front case 101 and the rear case 102, or between the rear case 102 and the rear cover 103, to hermetically seal an inner space when those cases are coupled.

FIGS. 2B and 2C depict certain components as arranged on the mobile terminal. However, it is to be understood that alternative arrangements are possible and within the teachings of the instant disclosure. Some components may be omitted or rearranged. For example, the first manipulation unit 123a may be located on another surface of the terminal body, and the second audio output module 152b may be located on the side surface of the terminal body.

The display unit 151 outputs information processed in the mobile terminal 100. The display unit 151 may be implemented using one or more suitable display devices. Examples of such suitable display devices include a liquid crystal display (LCD), a thin film transistor-liquid crystal display (TFT-LCD), an organic light emitting diode (OLED), a flexible display, a 3-dimensional (3D) display, an e-ink display, and combinations thereof.

The display unit 151 may be implemented using two display devices, which can implement the same or different display technology. For instance, a plurality of the display units 151 may be arranged on one side, either spaced apart from each other, or these devices may be integrated, or these devices may be arranged on different surfaces.

The display unit 151 may also include a touch sensor which senses a touch input received at the display unit. When a touch is input to the display unit 151, the touch sensor may be configured to sense this touch and the controller 180, for example, may generate a control command or other signal corresponding to the touch. The content which is input in the touching manner may be a text or numerical value, or a menu item which can be indicated or designated in various modes.

The touch sensor may be configured in a form of a film having a touch pattern, disposed between the window 151a and a display on a rear surface of the window 151a, or a metal wire which is patterned directly on the rear surface of the window 151a. Alternatively, the touch sensor may be integrally formed with the display. For example, the touch sensor may be disposed on a substrate of the display or within the display.

The display unit 151 may also form a touch screen together with the touch sensor. Here, the touch screen may serve as the user input unit 123 (see FIG. 1A). Therefore, the touch screen may replace at least some of the functions of the first manipulation unit 123a.

The first audio output module 152a may be implemented in the form of a speaker to output voice audio, alarm sounds, multimedia audio reproduction, and the like.

The window 151a of the display unit 151 will typically include an aperture to permit audio generated by the first audio output module 152a to pass. One alternative is to allow audio to be released along an assembly gap between the structural bodies (for example, a gap between the window 151a and the front case 101). In this case, a hole independently formed to output audio sounds may not be seen or is otherwise hidden in terms of appearance, thereby further simplifying the appearance and manufacturing of the mobile terminal 100.

The optical output module 154 can be configured to output light for indicating an event generation. Examples of such events include a message reception, a call signal reception, a missed call, an alarm, a schedule notice, an email reception, information reception through an application, and the like. When a user has checked a generated event, the controller can control the optical output unit 154 to stop the light output.

The first camera 121a can process image frames such as still or moving images obtained by the image sensor in a capture mode or a video call mode. The processed image frames can then be displayed on the display unit 151 or stored in the memory 170.

The first and

second manipulation units

123a and 123b are examples of the user input unit 123, which may be manipulated by a user to provide input to the mobile terminal 100. The first and

second manipulation units

123a and 123b may also be commonly referred to as a manipulating portion, and may employ any tactile method that allows the user to perform manipulation such as touch, push, scroll, or the like. The first and

second manipulation units

123a and 123b may also employ any non-tactile method that allows the user to perform manipulation such as proximity touch, hovering, or the like.

FIG. 2b illustrates the first manipulation unit 123a as a touch key, but possible alternatives include a mechanical key, a push key, a touch key, and combinations thereof.

Input received at the first and

second manipulation units

123a and 123b may be used in various ways. For example, the first manipulation unit 123a may be used by the user to provide an input to a menu, home key, cancel, search, or the like, and the second manipulation unit 123b may be used by the user to provide an input to control a volume level being output from the first or second

audio output modules

152a or 152b, to switch to a touch recognition mode of the display unit 151, or the like.

As another example of the user input unit 123, a rear input unit (not shown) may be located on the rear surface of the terminal body. The rear input unit can be manipulated by a user to provide input to the mobile terminal 100. The input may be used in a variety of different ways. For example, the rear input unit may be used by the user to provide an input for power on/off, start, end, scroll, control volume level being output from the first or second

audio output modules

152a or 152b, switch to a touch recognition mode of the display unit 151, and the like. The rear input unit may be configured to permit touch input, a push input, or combinations thereof.

The rear input unit may be located to overlap the display unit 151 of the front side in a thickness direction of the terminal body. As one example, the rear input unit may be located on an upper end portion of the rear side of the terminal body such that a user can easily manipulate it using a forefinger when the user grabs the terminal body with one hand. Alternatively, the rear input unit can be positioned at most any location of the rear side of the terminal body.

Embodiments that include the rear input unit may implement some or all of the functionality of the first manipulation unit 123a in the rear input unit. As such, in situations where the first manipulation unit 123a is omitted from the front side, the display unit 151 can have a larger screen.

As a further alternative, the mobile terminal 100 may include a finger scan sensor which scans a user’s fingerprint. The controller 180 can then use fingerprint information sensed by the finger scan sensor as part of an authentication procedure. The finger scan sensor may also be installed in the display unit 151 or implemented in the user input unit 123.

The microphone 122 is shown located at an end of the mobile terminal 100, but other locations are possible. If desired, multiple microphones may be implemented, with such an arrangement permitting the receiving of stereo sounds.

The interface unit 160 may serve as a path allowing the mobile terminal 100 to interface with external devices. For example, the interface unit 160 may include one or more of a connection terminal for connecting to another device (for example, an earphone, an external speaker, or the like), a port for near field communication (for example, an Infrared Data Association (IrDA) port, a Bluetooth port, a wireless LAN port, and the like), or a power supply terminal for supplying power to the mobile terminal 100. The interface unit 160 may be implemented in the form of a socket for accommodating an external card, such as Subscriber Identification Module (SIM), User Identity Module (UIM), or a memory card for information storage.

The second camera 121b is shown located at the rear side of the terminal body and includes an image capturing direction that is substantially opposite to the image capturing direction of the first camera unit 121a. If desired, second camera 121a may alternatively be located at other locations, or made to be moveable, in order to have a different image capturing direction from that which is shown.

The second camera 121b can include a plurality of lenses arranged along at least one line. The plurality of lenses may also be arranged in a matrix configuration. The cameras may be referred to as an “array camera.” When the second camera 121b is implemented as an array camera, images may be captured in various manners using the plurality of lenses and images with better qualities.

As shown in FIG. 2c, a flash 124 is shown adjacent to the second camera 121b. When an image of a subject is captured with the camera 121b, the flash 124 may illuminate the subject.

As shown in FIG. 2b, the second audio output module 152b can be located on the terminal body. The second audio output module 152b may implement stereophonic sound functions in conjunction with the first audio output module 152a, and may be also used for implementing a speaker phone mode for call communication.

At least one antenna for wireless communication may be located on the terminal body. The antenna may be installed in the terminal body or formed by the case. For example, an antenna which configures a part of the broadcast receiving module 111 may be retractable into the terminal body. Alternatively, an antenna may be formed using a film attached to an inner surface of the rear cover 103, or a case that includes a conductive material.

A power supply unit 190 for supplying power to the mobile terminal 100 may include a battery 191, which is mounted in the terminal body or detachably coupled to an outside of the terminal body. The battery 191 may receive power via a power source cable connected to the interface unit 160. Also, the battery 191 can be recharged in a wireless manner using a wireless charger. Wireless charging may be implemented by magnetic induction or electromagnetic resonance.

The rear cover 103 is shown coupled to the rear case 102 for shielding the battery 191, to prevent separation of the battery 191, and to protect the battery 191 from an external impact or from foreign material. When the battery 191 is detachable from the terminal body, the rear case 103 may be detachably coupled to the rear case 102.

An accessory for protecting an appearance or assisting or extending the functions of the mobile terminal 100 can also be provided on the mobile terminal 100. As one example of an accessory, a cover or pouch for covering or accommodating at least one surface of the mobile terminal 100 may be provided. The cover or pouch may cooperate with the display unit 151 to extend the function of the mobile terminal 100. Another example of the accessory is a touch pen for assisting or extending a touch input to a touch screen.

FIG. 3 is a conceptual view of a deformable mobile terminal according to an alternative embodiment of the present invention. In this figure, mobile terminal 200 is shown having display unit 251, which is a type of display that is deformable by an external force. This deformation, which includes display unit 251 and other components of mobile terminal 200, may include any of curving, bending, folding, twisting, rolling, and combinations thereof. The deformable display unit 251 may also be referred to as a “flexible display unit.” In some implementations, the flexible display unit 251 may include a general flexible display, electronic paper (also known as e-paper), and combinations thereof. In general, mobile terminal 200 may be configured to include features that are the same or similar to that of mobile terminal 100 of FIGS. 2A-2C .

The flexible display of mobile terminal 200 is generally formed as a lightweight, non-fragile display, which still exhibits characteristics of a conventional flat panel display, but is instead fabricated on a flexible substrate which can be deformed as noted previously.

The term e-paper may be used to refer to a display technology employing the characteristic of a general ink, and is different from the conventional flat panel display in view of using reflected light. E-paper is generally understood as changing displayed information using a twist ball or via electrophoresis using a capsule.

When in a state that the flexible display unit 251 is not deformed (for example, in a state with an infinite radius of curvature and referred to as a first state), a display region of the flexible display unit 251 includes a generally flat surface. When in a state that the flexible display unit 251 is deformed from the first state by an external force (for example, a state with a finite radius of curvature and referred to as a second state), the display region may become a curved surface or a bent surface. As illustrated, information displayed in the second state may be visual information output on the curved surface. The visual information may be realized in such a manner that a light emission of each unit pixel (sub-pixel) arranged in a matrix configuration is controlled independently. The unit pixel denotes an elementary unit for representing one color.

According to one alternative embodiment, the first state of the flexible display unit 251 may be a curved state (for example, a state of being curved from up to down or from right to left), instead of being in flat state. In this embodiment, when an external force is applied to the flexible display unit 251, the flexible display unit 251 may transition to the second state such that the flexible display unit is deformed into the flat state(or a less curved state) or into a more curved state.

If desired, the flexible display unit 251 may implement a flexible touch screen using a touch sensor in combination with the display. When a touch is received at the flexible touch screen, the controller 180 can execute certain control corresponding to the touch input. In general, the flexible touch screen is configured to sense touch and other input while in both the first and second states.

One option is to configure the mobile terminal 200 to include a deformation sensor which senses the deforming of the flexible display unit 251. The deformation sensor may be included in the sensing unit 140.

The deformation sensor may be located in the flexible display unit 251 or the case 201 to sense information related to the deforming of the flexible display unit 251. Examples of such information related to the deforming of the flexible display unit 251 may be a deformed direction, a deformed degree, a deformed position, a deformed amount of time, an acceleration that the deformed flexible display unit 251 is restored, and the like. Other possibilities include most any type of information which can be sensed in response to the curving of the flexible display unit or sensed while the flexible display unit 251 is transitioning into, or existing in, the first and second states.

In some embodiments, controller 180 or other component can change information displayed on the flexible display unit 251, or generate a control signal for controlling a function of the mobile terminal 200, based on the information related to the deforming of the flexible display unit 251. Such information is typically sensed by the deformation sensor.

The mobile terminal 200 is shown having a case 201 for accommodating the flexible display unit 251. The case 201 can be deformable together with the flexible display unit 251, taking into account the characteristics of the flexible display unit 251.

A battery (not shown in this figure) located in the mobile terminal 200 may also be deformable in cooperation with the flexible display unit 261, taking into account the characteristic of the flexible display unit 251. One technique to implement such a battery is to use a stack and folding method of stacking battery cells.

The deformation of the flexible display unit 251 not limited to perform by an external force. For example, the flexible display unit 251 can be deformed into the second state from the first state by a user command, application command, or the like.

In accordance with still further embodiments, a mobile terminal may be configured as a device which is wearable on a human body. Such devices go beyond the usual technique of a user grasping the mobile terminal using their hand. Examples of the wearable device include a smart watch, a smart glass, a head mounted display (HMD), and the like.

A typical wearable device can exchange data with (or cooperate with) another mobile terminal 100. In such a device, the wearable device generally has functionality that is less than the cooperating mobile terminal. For instance, the short-range communication module 114 of a mobile terminal 100 may sense or recognize a wearable device that is near-enough to communicate with the mobile terminal. In addition, when the sensed wearable device is a device which is authenticated to communicate with the mobile terminal 100, the controller 180 may transmit data processed in the mobile terminal 100 to the wearable device via the short-range communication module 114, for example. Hence, a user of the wearable device can 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 can answer the call using the wearable device. Also, when a message is received in the mobile terminal 100, the user can check the received message using the wearable device.

FIG. 4 is a perspective view illustrating one example of a watch-type mobile terminal 300 in accordance with another exemplary embodiment. As illustrated in FIG. 4, the watch-type mobile terminal 300 includes a main body 301 with a display unit 351 and a band 302 connected to the main body 301 to be wearable on a wrist. In general, mobile terminal 300 may be configured to include features that are the same or similar to that of mobile terminal 100 of FIGS. 2A-2C .

The main body 301 may include a case having a certain appearance. As illustrated, the case may include a first case 301a and a second case 301b cooperatively defining an inner space for accommodating various electronic components. Other configurations are possible. For instance, a single case may alternatively be implemented, with such a case being configured to define the inner space, thereby implementing a mobile terminal 300 with a uni-body.

The watch-type mobile terminal 300 can perform wireless communication, and an antenna for the wireless communication can be installed in the main body 301. The antenna may extend its function using the case. For example, a case including a conductive material may be electrically connected to the antenna to extend a ground area or a radiation area.

The display unit 351 is shown located at the front side of the main body 301 so that displayed information is viewable to a user. In some embodiments, the display unit 351 includes a touch sensor so that the display unit can function as a touch screen. As illustrated, window 351a is positioned on the first case 301a to form a front surface of the terminal body together with the first case 301a.

The illustrated embodiment includes audio output module 352, a camera 321, a microphone 322, and a user input unit 323 positioned on the main body 301. When the display unit 351 is implemented as a touch screen, additional function keys may be minimized or eliminated. For example, when the touch screen is implemented, the user input unit 323 may be omitted.

The band 302 is commonly worn on the user’s wrist and may be made of a flexible material for facilitating wearing of the device. As one example, the band 302 may be made of fur, rubber, silicon, synthetic resin, or the like. The band 302 may also be configured to be detachable from the main body 301. Accordingly, the band 302 may be replaceable with various types of bands according to a user’s preference.

In one configuration, the band 302 may be used for extending the performance of the antenna. For example, the band may include therein a ground extending portion (not shown) electrically connected to the antenna to extend a ground area.

The band 302 may include fastener 302a. The fastener 302a may be implemented into a buckle type, a snap-fit hook structure, a Velcro® type, or the like, and include a flexible section or material. The drawing illustrates an example that the fastener 302a is implemented using a buckle.

FIG. 5 is a perspective view illustrating one example of a glass-type mobile terminal 400 according to another exemplary embodiment. The glass-type mobile terminal 400 can be wearable on a head of a human body and provided with a frame (case, housing, etc.) therefor. The frame may be made of a flexible material to be easily worn. The frame of mobile terminal 400 is shown having a first frame 401 and a second frame 402, which can be made of the same or different materials. In general, mobile terminal 400 may be configured to include features that are the same or similar to that of mobile terminal 100 of FIGS. 2A-2C.

The frame may be supported on the head and defines a space for mounting various components. As illustrated, electronic components, such as a control module 480, an audio output module 452, and the like, may be mounted to the frame part. Also, a lens 403 for covering either or both of the left and right eyes may be detachably coupled to the frame part.

The control module 480 controls various electronic components disposed in the mobile terminal 400. The control module 480 may be understood as a component corresponding to the aforementioned controller 180. FIG. 4 illustrates that the control module 480 is installed in the frame part on one side of the head, but other locations are possible.

The display unit 451 may be implemented as a head mounted display (HMD). The HMD refers to display techniques by which a display is mounted to a head to show an image directly in front of a user’s eyes. In order to provide an image directly in front of the user’s eyes when the user wears the glass-type mobile terminal 400, the display unit 451 may be located to correspond to either or both of the left and right eyes. FIG. 5 illustrates that the display unit 451 is located on a portion corresponding to the right eye to output an image viewable by the user’s right eye.

The display unit 451 may project an image into the user’s eye using a prism. Also, the prism may be formed from optically transparent material such that the user can view both the projected image and a general visual field (a range that the user views through the eyes) in front of the user.

In such a manner, the image output through the display unit 451 may be viewed while overlapping with the general visual field. The mobile terminal 400 may provide an augmented reality (AR) by overlaying a virtual image on a realistic image or background using the display.

The camera 421 may be located adjacent to either or both of the left and right eyes to capture an image. Since the camera 421 is located adjacent to the eye, the camera 421 can acquire a scene that the user is currently viewing. The camera 421 may be positioned at most any location of the mobile terminal. In some embodiments, multiple cameras 421 may be utilized. Such multiple cameras 421 may be used to acquire a stereoscopic image.

The glass-type mobile terminal 400 may include

user input units

423a and 423b, which can each be manipulated by the user to provide an input. The

user input units

423a and 423b may employ techniques which permit input via a tactile input. Typical tactile inputs include a touch, push, or the like. The

user input units

423a and 423b are shown operable in a pushing manner and a touching manner as they are located on the frame part and the control module 480, respectively.

If desired, mobile terminal 400 may include a microphone which processes input sound into electric audio data, and an audio output module 452 for outputting audio. The audio output module 452 may be configured to produce audio in a general audio output manner or an osteoconductive manner. When the audio output module 452 is implemented in the osteoconductive manner, the audio output module 452 may be closely adhered to the head when the user wears the mobile terminal 400 and vibrate the user’s skull to transfer sounds.

A communication system which is operable with the variously described mobile terminals will now be described in more detail. Such a communication system may be configured to utilize any of a variety of different air interfaces and/or physical layers. Examples of such air interfaces utilized by the communication system include Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Universal Mobile Telecommunications System (UMTS) (including, Long Term Evolution (LTE), LTE-A(Long Term Evolution-Advanced)), Global System for Mobile Communications (GSM), and the like.

By way of a non-limiting example only, further description will relate to a CDMA communication system, but such teachings apply equally to other system types including a CDMA wireless communication system as well as OFDM(Orthogonal Frequency Division Multiplexing) wireless communication system. A CDMA wireless communication system generally includes one or more mobile terminals (MT or User Equipment, UE) 100, one or more base stations (BSs, NodeB, or evolved NodeB), one or more base station controllers (BSCs), and a mobile switching center (MSC). The MSC is configured to interface with a conventional Public Switched Telephone Network (PSTN) and the BSCs. The BSCs are coupled to the base stations via backhaul lines. The backhaul lines may be configured in accordance with any of several known interfaces including, for example, E1/T1, ATM, IP, PPP, Frame Relay, HDSL, ADSL, or xDSL. Hence, the plurality of BSCs can be included in the CDMA wireless communication system.

Each base station may include one or more sectors, each sector having an omni-directional antenna or an antenna pointed in a particular direction radially away from the base station. Alternatively, each sector may include two or more different antennas. Each base station may be configured to support a plurality of frequency assignments, with each frequency assignment having a particular spectrum (e.g., 1.25 MHz, 5 MHz, etc.).

The intersection of sector and frequency assignment may be referred to as a CDMA channel. The base stations may also be referred to as Base Station Transceiver Subsystems (BTSs). In some cases, the term "base station" may be used to refer collectively to a BSC, and one or more base stations. The base stations may also be denoted as "cell sites." Alternatively, individual sectors of a given base station may be referred to as cell sites.

A broadcasting transmitter (BT) transmits a broadcast signal to the mobile terminals 100 operating within the system. The broadcast receiving module 111 of FIG. 1A is typically configured inside the mobile terminal 100 to receive broadcast signals transmitted by the BT.

Global Positioning System (GPS) satellites for locating the position of the mobile terminal 100, for example, may cooperate with the CDMA wireless communication system. Useful position information may be obtained with greater or fewer satellites than two satellites. It is to be appreciated that other types of position detection technology, (i.e., location technology that may be used in addition to or instead of GPS location technology) may alternatively be implemented. If desired, at least one of the GPS satellites may alternatively or additionally be configured to provide satellite DMB transmissions.

The location information module 115 is generally configured to detect, calculate, or otherwise identify a position of the mobile terminal. As an example, the location information module 115 may include 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.

A typical GPS module 115 can measure an accurate time and distance from three or more satellites, and accurately calculate a current location of the mobile terminal according to trigonometry based on the measured time and distances. A method of acquiring distance and time information from three satellites and performing error correction with a single satellite may be used. In particular, the GPS module may acquire an accurate time together with three-dimensional speed information as well as the location of the latitude, longitude and altitude values from the location information received from the satellites.

Furthermore, the GPS module can acquire speed information in real time to calculate a current position. Sometimes, accuracy of a measured position may be compromised when the mobile terminal is located in a blind spot of satellite signals, such as being located in an indoor space. In order to minimize the effect of such blind spots, an alternative or supplemental location technique, such as Wi-Fi Positioning System (WPS), may be utilized.

The Wi-Fi positioning system (WPS) refers to a location determination technology based on a wireless local area network (WLAN) using Wi-Fi as a technology for tracking the location of the mobile terminal 100. This technology typically includes the use of a Wi-Fi module in the mobile terminal 100 and a wireless access point for communicating with the Wi-Fi module.

The Wi-Fi positioning system may include a Wi-Fi location determination server, a mobile terminal, a wireless access point (AP) connected to the mobile terminal, and a database stored with wireless AP information.

The mobile terminal connected to the wireless AP may transmit a location information request message to the Wi-Fi location determination server. The Wi-Fi location determination server extracts the information of the wireless AP connected to the mobile terminal 100, based on the location information request message (or signal) of the mobile terminal 100. The information of the wireless AP may be transmitted to the Wi-Fi location determination server through the mobile terminal 100, or may be transmitted to the Wi-Fi location determination server from the wireless AP.

The information of the wireless AP extracted based on the location information request message of the mobile terminal 100 may include one or more of media access control (MAC) address, service set identification (SSID), received signal strength indicator (RSSI), reference signal received Power(RSRP), reference signal received quality(RSRQ), channel information, privacy, network type, signal strength, noise strength, and the like.

The Wi-Fi location determination server may receive the information of the wireless AP connected to the mobile terminal 100 as described above, and may extract wireless AP information corresponding to the wireless AP connected to the mobile terminal from the pre-established database. The information of any wireless APs stored in the database may be information such as MAC address, SSID, RSSI, channel information, privacy, network type, latitude and longitude coordinate, building at which the wireless AP is located, floor number, detailed indoor location information (GPS coordinate available), AP owner's address, phone number, and the like. In order to remove wireless APs provided using a mobile AP or an illegal MAC address during a location determining process, the Wi-Fi location determination server may extract only a predetermined number of wireless AP information in order of high RSSI.

Then, the Wi-Fi location determination server may extract (analyze) location information of the mobile terminal 100 using at least one wireless AP information extracted from the database.

A method for extracting (analyzing) location information of the mobile terminal 100 may include a Cell-ID method, a fingerprint method, a trigonometry method, a landmark method, and the like.

The Cell-ID method is used to determine a position of a wireless AP having the largest signal strength, among peripheral wireless AP information collected by a mobile terminal, as a position of the mobile terminal. The Cell-ID method is an implementation that is minimally complex, does not require additional costs, and location information can be rapidly acquired. However, in the Cell-ID method, the precision of positioning may fall below a desired threshold when the installation density of wireless APs is low.

The fingerprint method is used to collect signal strength information by selecting a reference position from a service area, and to track a position of a mobile terminal using the signal strength information transmitted from the mobile terminal based on the collected information. In order to use the fingerprint method, it is common for the characteristics of radio signals to be pre-stored in the form of a database.

The trigonometry method is used to calculate a position of a mobile terminal based on a distance between coordinates of at least three wireless APs and the mobile terminal. In order to measure the distance between the mobile terminal and the wireless APs, signal strength may be converted into distance information, Time of Arrival (ToA), Time Difference of Arrival (TDoA), Angle of Arrival (AoA), or the like may be taken for transmitted wireless signals.

The landmark method is used to measure a position of a mobile terminal using a known landmark transmitter.

In addition to these position location methods, various algorithms may be used to extract (analyze) location information of a mobile terminal. Such extracted location information may be transmitted to the mobile terminal 100 through the Wi-Fi location determination server, thereby acquiring location information of the mobile terminal 100.

The mobile terminal 100 can acquire location information by being connected to at least one wireless AP. The number of wireless APs required to acquire location information of the mobile terminal 100 may be variously changed according to a wireless communication environment within which the mobile terminal 100 is positioned.

As previously described with regard to FIG. 1A, the mobile terminal may be configured to include short-range communication techniques such as Bluetooth™, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wideband (UWB), ZigBee, Near Field Communication (NFC), Wireless USB(Wireless Universal Serial Bus), and the like.

A typical NFC module provided at the mobile terminal supports short-range wireless communication, which is a non-contactable type of communication between mobile terminals and generally occurs within about 10 cm. The NFC module may operate in one of a card mode, a reader mode, or a P2P mode. The mobile terminal 100 may further include a security module for storing card information, in order to operate the NFC module in a card mode. The security module may be a physical medium such as Universal Integrated Circuit Card (UICC) (e.g., a Subscriber Identification Module (SIM) or Universal SIM (USIM)), a secure micro SD and a sticker, or a logical medium (e.g., embedded Secure Element (SE)) embedded in the mobile terminal. Single Wire Protocol (SWP)-based data exchange may be performed between the NFC module and the security module.

In a case where the NFC module operates in a card mode, the mobile terminal may transmit card information on a general IC card to the outside. More specifically, if a mobile terminal having card information on a payment card (e. g, a credit card or a bus card) approaches a card reader, a short-range mobile payment may be executed. As another example, if a mobile terminal which stores card information on an entrance card approaches an entrance card reader, an entrance approval procedure may start. A card such as a credit card, a traffic card, or an entrance card may be included in the security module in the form of applet, and the security module may store card information on the card mounted therein. Card information for a payment card may include any of a card number, a remaining amount and usage history, and the like. Card information of an entrance card may include any of a user’s name, a user’s number (e.g., undergraduate number or staff number), an entrance history, and the like.

When the NFC module operates in a reader mode, the mobile terminal can read data from an external tag. The data received from the external tag by the mobile terminal may be coded into the NFC Data Exchange Format defined by the NFC Forum. The NFC Forum generally defines four record types. More specifically, the NFC Forum defines four Record Type Definitions (RTDs) such as smart poster, text, Uniform Resource Identifier (URI), and general control. If the data received from the external tag is a smart poster type, the controller may execute a browser (e.g., Internet browser). If the data received from the external tag is a text type, the controller may execute a text viewer. If the data received from the external tag is a URI type, the controller may execute a browser or originate a call. If the data received from the external tag is a general control type, the controller may execute a proper operation according to control content.

In some cases in which the NFC module operates in a P2P(Peer-to-Peer) mode, the mobile terminal can execute P2P communication with another mobile terminal. In this case, Logical Link Control Protocol (LLCP) may be applied to the P2P communication. For P2P communication, connection may be generated between the mobile terminal and another mobile terminal. This connection may be categorized as a connectionless mode which ends after one packet is switched, and a connection-oriented mode in which packets are switched consecutively. For a typical P2P communication, data such as an electronic type name card, address information, a digital photo and a URL, a setup parameter for Bluetooth connection, Wi-Fi connection, etc. may be switched. The P2P mode can be effectively utilized in switching data of a small capacity, because an available distance for NFC communication is relatively short.

Further preferred embodiments will be described in more detail with reference to additional drawing figures. It is understood by those skilled in the art that the present features can be embodied in several forms without departing from the characteristics thereof.

FIG. 6 is a schematic block diagram of components of the mobile terminal shown in FIG. 2a to describe one embodiment of the present invention.

Referring to FIG. 6, a mobile terminal 100 according to one embodiment of the present invention may include a host CPU 185, an NFC controller 114a and an SE 195. At least one portion of the controller 180 of the mobile terminal 100 and the memory 170, which are described with reference to FIG. 2a, shall be integrated to be named a host CPU 185. In particular, the host CPU 185 controls overall operations of the mobile terminal 100 and can include a memory. The NFC controller 114a may belong to the short range communication module 114 of the mobile terminal 100 described with reference to FIG. 2a. The NFC controller 114a is implemented with a chip and may have a storage space inside. According to an embodiment, an operation of the host CPU 185 related with an NFC card mentioned in the following description may be performed by a host framework controlled by the host CPU 185.

The host CPU 185 stores applications related to the NFC card. In particular, the applications may include native applications installed before the mobile terminal 100 is released in the market. And, the applications may include applications downloaded by a user from an external server. In this case, the NFC card may mean a virtual card implemented to perform a payment, an installment or the like by tagging a card emulated in the mobile terminal 100 with the NFC reader 500 through an NFC function.

The mobile terminal 100 supports a host-based card emulation (hereinafter abbreviated HCE). A mobile terminal of the related art can communicate with an external NFC reader 500 through the SE 195 only. The HCE can implement a function of the SE 195 not through the mobile terminal 100 but through a cloud server. And, the HCE provides a method for the mobile terminal 100 to communicate with the NFC reader 500 without the SE 195. The application can emulate the NFC card through the HCE without going through the SE 195.

The mobile terminal 100 may set an NFC processing mode to a 1st mode or a 2nd mode. In this case, when the mobile terminal 100 approaches the NFC reader 500, the NFC processing mode is related to whether the NFC controller 114a routes the data received from the NFC reader 500 to the host CPU 185 or the SE 195. For instance, the 1st mode may include an off-host mode defaulted to a route for routing the data received from the NFC reader 500 to the SE 195, while the 2nd mode may include an on-host mode defaulted to a route for routing the data received from the NFC reader 500 to the host CPU 185. In this case, according to the meaning of ‘defaulted to the route for routing the data received from the NFC reader 500 to the SE 195, if the data received from the NFC reader 500 matches data in a routing table saved in the NFC controller 114a, the data is routed to the host CPU 185. If the data received from the NFC reader 500 fails to match data in a routing table saved in the NFC controller 114a, the data is routed to the SE 195, which is a basic route. Likewise, according to the meaning of ‘defaulted to the route for routing the data received from the NFC reader 500 to the host CPU 185, if the data received from the NFC reader 500 matches data in a routing table saved in the NFC controller 114a, the data is routed to the SE 195. If the data received from the NFC reader 500 fails to match data in a routing table saved in the NFC controller 114a, the data is routed to the host CPU 185, which is a basic route.

The off-host mode shall be described in detail with reference to FIG. 7 and the on-host mode shall be described in detail with reference to FIG. 8, later.

The NFC controller 114a saves a routing table in an internal storage space. AID (application ID) for identifying an application is saved in the routing table. If a user intends to make a payment using an NFC card related to an application installed on the mobile terminal 100, it is necessary for the mobile terminal 100 to be aware that the NFC reader 500 intends to communicate with the mobile terminal 100 using a prescribed HCE service. According to ISE/IEC 7816-4 Specifications, it is defined to select an application, which is to be used for making a payment, using AID.

According to an embodiment, if a plurality of NFC cards related to a single application exist, a plurality of AIDs may exist for the single application. In this case, a plurality of the AIDs may include informations for identifying a plurality of the NFC cards, respectively. In the following description, considering a case that a plurality of NFC cars related to a single application exist, assume that AID is an information for identifying each NFC card. Of course, in case that a single application is related to a single NFC card, AID may be an information for identifying the corresponding application.

The host CPU 185 controls the NFC controller 114a to save at least one portion of AIDs, which are provided to identify NFC cards among application related informations on applications related to the NFC cards saved in the memory 170, in the routing table. The AID saved in the routing table may change depending on whether the NFC processing mode is the off-host mode or the on-host mode. This shall be described in detail with reference to FIGs. 9 to 14 later.

FIG. 7 is a flowchart to describe a routing route of data received from an NFC reader if a mobile of a mobile terminal according to one embodiment of the present invention is set to an off-host mode. The off-host mode is described in detail with reference to FIG. 6 and FIG. 7 as follows.

First of all, if the mobile terminal 100 held by a user approaches the NFC reader 500 located externally, the NFC controller 114a receives AID of an application (or a specific NFC card according to an embodiment) supported by the NFC reader 500 from the NFC reader 500 [S601].

If an AID matching the received AID exists among AIDs saved in a routing table within the NFC controller 114a [‘Yes’, S602], the NFC controller 114a routes the received AID to the host CPU 185 [S603]. An application corresponding to the AID in the routing table, which matches the received AID, can emulate an NFC card through the host CPU 185. And, a payment can be made by a direct communication with the NFC reader 500 through the emulated NFC card.

On the other hand, if an AID matching the received AID fails to exist among the AIDs saved in the routing table within the NFC controller 114a [‘No’, S602], the NFC controller 114a routes the received AID to the SE 195 [S604]. An NFC card of an application corresponding to the AID in the routing table, which matches the received AID, can be emulated through the SE 195. And, a payment can be made in a manner that the SE 195 communicates with the NFC reader 500.

FIG. 8 is a flowchart to describe a routing route of data received from an NFC reader if a mobile of a mobile terminal according to one embodiment of the present invention is set to an on-host mode. The on-host mode is described in detail with reference to FIG. 6 and FIG. 8 as follows.

First of all, if the mobile terminal 100 held by a user approaches the NFC reader 500 located externally, the NFC controller 114a receives AID of an application (or a specific NFC card according to an embodiment) supported by the NFC reader 500 from the NFC reader 500 [S611].

If an AID matching the received AID exists among AIDs saved in a routing table within the NFC controller 114a [‘Yes’, S612], the NFC controller 114a routes the received AID to the SE 195 [S613]. An NFC card of an application corresponding to the AID in the routing table, which matches the received AID, can be emulated through the SE 195. And, a payment can be made in a manner that the SE 195 communicates with the NFC reader 500.

On the other hand, if an AID matching the received AID fails to exist among the AIDs saved in the routing table within the NFC controller 114a [‘No’, S612], the NFC controller 114a routes the received AID to the host CPU 185 [S614]. An application corresponding to the AID in the routing table, which matches the received AID, can emulate an NFC card through the host CPU 185. And, a payment can be made by a direct communication with the NFC reader 500 through the emulated NFC card.

When an NFC function is activated in the mobile terminal 100, an NFC processing mode can be set to one of the off-host mode and the on-host mode. And, the NFC processing mode can be switched to the on-host mode from the off-host mode or to the off-host mode from the on-host mode.

FIG. 9 is a diagram for one example of application related information of applications related to an NFC card according to one embodiment of the present invention.

When a user downloads an application related to an NFC card, the application and an application related information can be downloaded together. In this case, the application related information can include a 1st information for identifying an application and a 2nd information indicating an emulation place of an NFC card related to the application. For instance, the 1st information may include the above-mentioned AID. In case that a plurality of NFC cards related to a single application exist, the AID may include the information for identifying each NFC card. For instance, the 2nd information may include a routing route information indicating whether an NFC card corresponding to the AID will be emulated through the host CPU 185 or the SE 195 using HCE. The application related information may further include an application name information, a category information and the like as well as the AID and the routing route information.

Referring to FIG. 9, 3 applications and application related informations corresponding to the 3 applications are illustrated for example. For instance, an application related information on a 1st application includes ‘PPSE & Mastercard’ as a 1st information (i.e., AID) and ‘Host’ as a 2nd information (i.e., routing route information). If the routing information is ‘Host’, it means that an NFC card related to the 1st application can be emulated through the host CPU 185. For another instance, an application related information on a 2nd application includes ‘PPSE & Visa’ as a 1st information (i.e., AID) and ‘Off Host’ as a 2nd information (i.e., routing route information). If the routing information is ‘Off Host’, it means that an NFC card related to the 2nd application can be emulated not through the host CPU 185 but through the SE 195. For further instance, an application related information on a 3rd application includes ‘T-money’ as a 1st information (i.e., AID) and ‘Host’ as a 2nd information (i.e., routing route information). If the routing information is ‘Host’, it means that an NFC card related to the 3rd application can be emulated through the host CPU 185.

In the following description, the following assumption is made without special description. First of all, if a routing information is ‘Host’, it indicates that an NFC card of a corresponding application can be emulated through the host CPU 185. Secondly, if a routing information is ‘Off Host’, it indicates that an NFC card of a corresponding application can be emulated through the SE 195. Of course, the expression of the ‘Host’ or ‘Off Host’ may vary depending on an application implementing method. Yet, in the present specification, a routing route information is assumed as expressed as ‘Host’ or ‘Off Host’.

According to the example shown in FIG. 10, unlike the former example shown in FIG. 9, there are a plurality of NFC cards related to a single application.

When a user downloads an application related to an NFC card, the application and an application related information can be downloaded together. In this case, the application related information can include a 1st information for identifying an application and a 2nd information indicating an emulation place of an NFC card related to the application. For instance, the 1st information may include an AID and the 2nd information may include a routing route information indicating whether an NFC card corresponding to the AID will be emulated through the host CPU 185 or the SE 195 using HCE. The application related information may further include an application name information, a category information and the like as well as the AID and the routing route information.

Referring to FIG. 10, Mastercard and Visacard exist as NFC cards related to a 1st application, respectively. Hence, AIDs can separately exist for the two NFC cards, respectively. Depending on an embodiment, the same routing route information may exist for all NFC cards related to the 1st application or different routing route informations may exist for at least two of the NFC cards like the example shown in FIG. 10.

FIG. 11 is a flowchart to describe one example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention. The following description with reference to FIG. 11 is made on the assumption that an NFC processing mode is an off-host mode.

Referring to FIG. 11, the host CPU 185 controls the mobile communication module 112 or the wireless internet module 113 to download an application related to an NFC card and an application related information [S701]. As mentioned in the foregoing description, the application related information may include an AID for identifying the NFC card related to the application and a routing information indicating that the NFC card is emulated through a prescribed one of the SE 195 and the host CPU 185.

The host CPU 185 installs the downloaded application [S702]. And, the host CPU 185 checks the routing route information in the application related information [S703].

Based on an NFC processing mode and the routing route information, if the routing route information corresponds to ‘Host’ [Yes, S704], the host CPU 185 controls the NFC controller 114a so that the AID in the application related information can be saved in a routing table [S705].

Depending on an embodiment, if a plurality of NFC cards related to the application exist, the application related information may include AID and routing route information for each of the NFC cards. In the step S704 and S705, the host CPU 185 may control the NFC controller 114a so that the AID of each NFC card corresponding to the routing route information corresponding to ‘Host’ among the routing route informations on a plurality of NFC cards can be saved in the routing table.

FIG. 12 is a flowchart to describe another example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention. The following description with reference to FIG. 12 is made on the assumption that an NFC processing mode is an on-host mode.

Referring to FIG. 12, the host CPU 185 controls the mobile communication module 112 or the wireless internet module 113 to download an application related to an NFC card and an application related information [S711]. As mentioned in the foregoing description, the application related information may include an AID for identifying the NFC card related to the application and a routing information indicating that the NFC card is emulated through a prescribed one of the SE 195 and the host CPU 185.

The host CPU 185 installs the downloaded application [S712]. And, the host CPU 185 checks the routing route information in the application related information [S713].

Based on an NFC processing mode and the routing route information, if the routing route information corresponds to ‘Off Host’ [Yes, S714], the host CPU 185 controls the NFC controller 114a so that the AID in the application related information can be saved in a routing table [S715].

Depending on an embodiment, if a plurality of NFC cards related to the application exist, the application related information may include AID and routing route information for each of the NFC cards. In the step S714 and S715, the host CPU 185 may control the NFC controller 114a so that the AID of each NFC card corresponding to the routing route information corresponding to ‘Off Host’ among the routing route informations on a plurality of NFC cards can be saved in the routing table.

FIG. 13 is a flowchart to describe further example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention. The following description with reference to FIG. 13 is made on the assumption that an NFC processing mode is an off-host mode.

As steps S721 and S722 are identical to the former steps S701 and S702 described with reference to FIG. 11, their details shall be omitted from the following description.

The host CPU 185 detects a user command for running the installed application [S723]. In this case, the user command may include one of a user command for running the application initially and a user command for selecting the application as a default application. And, the default application may mean an application set to run in a background without any user interfaces. For instance, if an application related to an NFC card such as a reserved point car (e.g., a loyalty card), a transit card or the like us set as a default application, it is convenient for a user to make a payment by tapping the mobile terminal 100 to the NFC reader 500 only without separately running the corresponding application in the mobile terminal 100.

In response to the user command, the host CPU 185 checks the routing route information in the application related information [S724].

Steps S725 and S726 following the step S724 are identical to the former steps S704 and S705 described with reference to FIG. 11, their details shall be omitted from the following description.

Depending on an embodiment, if a plurality of NFC cards related to the application exist, the application related information may include AID and routing route information for each of the NFC cards. In the step S725 and S726, the host CPU 185 may control the NFC controller 114a so that the AID of each NFC card corresponding to the routing route information corresponding to ‘Host’ among the routing route informations on a plurality of NFC cards can be saved in the routing table.

Moreover, according to the description with reference to FIG. 13, the case that the NFC processing mode is the off-host mode is taken as an example. Yet, since a case of the NFC processing mode set to the on-host mode is similar to the above case shown in FIG. 13 except that AID in the application related information in case of the routing route information corresponding to ‘Off Host’ is saved in the routing table, details of the case of setting the NFC processing mode to the on-host mode shall be omitted from the following description.

On the other hand, if the application related information of the installed application includes a category information and the category information corresponds to ‘other’, when the application is installed, the steps S724 to S726 can be performed irrespective of a presence or non-presence of a detection of the user command. For instance, an application of which category information corresponds to ‘other’ may mean a coupon use application not related to payment, point saving and the like. Yet, in the step S726, it is determined whether AID overlapping with the AID in the application related information has already exist in the routing table within the NFC controller 114a. Only if the AID overlapping with the AID in the application related information fails to exist in the routing table within the NFC controller 114a, the corresponding AID can be saved in the routing table in the NFC controller 114a.

Meanwhile, depending on an embodiment, if a single application is related to a plurality of NFC cards and NFC cards frequently used in general by people exist among a plurality of the NFC cards related to the single application, such information can be represented by an app developer as additional information of AID in application related information. For instance, an NFC card corresponding to an AID having additional information exist therein may correspond to an NFC card having a high use frequency in general. As the AID corresponding to the NFC card having the high use frequency is preferentially saved in the routing table within the NFC controller 114a, it is intended to efficiently manage the storage capacity of the routing table. This is described in detail with reference to FIG. 14 as follows.

FIG. 14 is a flowchart to describe another further example of a method of saving AID in a routing table within an NFC controller of a mobile terminal according to one embodiment of the present invention. The following description with reference to FIG. 14 is made on the assumption that an NFC processing mode is an off-host mode.

Referring to FIG. 14, steps S731 and S732 can be performed by following the former step ‘Yes’ S704 described with reference to FIG. 11.

The host CPU 185 checks a presence or non-presence of an additional information of each NFC card having a routing route information correspond to ‘Host’ [S731].

Subsequently, the host CPU 185 controls the NFC controller 114a to save the additional information existing AID in a routing table [S732].

According to the present embodiment, when an application is installed, the host CPU 185 can control the additional information existing AID to be saved in the routing table within the NFC controller 114a. When a user command for selecting the application is detected, the host CPU 185 can control the AID having the additional information not exist therein to be saved in the routing table within the NFC controller 114a. In case that a plurality of application related NFC cards exist, as an AID of the NFC card having a relatively high possibility to be used by a user is preferentially saved in the routing table, it is advantageous in that a storage capacity of the routing table can be efficiently managed.

Moreover, according to the description with reference to FIG. 14, the case that the NFC processing mode is the off-host mode is taken as an example. Yet, since a case of the NFC processing mode set to the on-host mode is similar to the above case described with reference to FIG. 14 except that the steps S731 and S732 are performed after the former step [Yes, S714] described with reference to FIG. 12, details of the case of setting the NFC processing mode to the on-host mode shall be omitted from the following description.

Referring to FIG. 15 (a), after a user has installed a configuration application, if the user selects an NFC related menu, a 1st screen 810 can be outputted through a display unit 151.

A 1st menu 811 is included in the 1st screen 810. In this case, the 1st menu 811 corresponds to an NFC payment function for making a payment by tapping the mobile terminal 100 to the NFC reader 500 using an NFC function. Moreover, a menu for selecting whether to activate the NFC function may be included in the 1st screen 810 [not shown in the drawing]. For instance, if the NFC function is in a deactivated state, the 1st menu 811 may be displayed as the deactivated state on the 1st screen 810.

While the NFC function is activated, if the 1st menu 811 is selected, referring to FIG. 15 (b), a 2nd screen 820 can be outputted through the display unit 151.

The 2nd screen 820 can display a list of applications related to an NFC card saved in the memory 170. For instance, the 2nd screen 820 may display a list of applications except an application having a category information set to ‘other’ in an application related information among the applications related to the NFC card saved in the memory 170.

For instance, the application list including a 1st application 821 having a routing route information in the application related information correspond to ‘Host’, a 2nd application 822 having a routing route information in the application related information correspond to ‘Off Host’, and 3rd application 823 having a routing route information in the application related information correspond to ‘On Host’.

A user can set one of the applications listed on the application list displayed on the 2nd screen 820 as a default application. If the mobile terminal 100 approaches the NFC reader 500, the application set as the default application can be automatically run on a background despite that the corresponding application is not separately run in the mobile terminal 1800 by the user.

FIG. 16 is a diagram to describe one example of a method of changing an NFC processing mode in a mobile terminal according to one embodiment of the present invention.

Referring to FIG. 16 (a), a 2nd screen 820 including a list of applications related to an NFC card saved in the memory 170 is outputted through the display unit 151.

If a user selects a setting menu 824 in the 2nd screen 820, referring to FIG. 16 (b), a 3rd screen 830 can be outputted through the display unit 151.

The 3rd screen 830 is provided to set an NFC processing mode and may include a 1st menu 831 for selecting an off-host mode as the NFC processing mode and a 2nd menu 832 for selecting an on-host mode as the NFC processing mode. Currently, assume that the NFC processing mode is set to the off-host mode.

If the user selects the 2nd meu 832 from the 3rd screen 830, referring to FIG. 16 (c), a guide message 840 for confirming that the NFC processing mode will be changed into the on-host mode can be outputted through the display unit 151.

If the user selects a cancel menu 841 included in the guide message 840, the 3rd screen 830 can be outputted through the display unit 151 again. On the other hand, if the user selects a confirm menu 842 included in the guide message 840, the NFC processing mode is changed into the on-host mode from the off-host mode and the 2nd screen 820 can be outputted through the display unit 151.

When the NFC processing mode is changed into the on-host mode from the off-host mode, the host CPU 185 can control the NFC controller 114a so that an AID of each application having a routing route information in an application related information correspond to ‘Off-Host’ among the applications related to the NFC card saved in the memory 170 can be saved in a routing table. The NFC controller 114a deletes AIDs saved in the routing table before changing the NFC processing mode and is then able to save AID of each application having the routing route information in the application related information correspond to ‘Off-Host’ in the routing table.

According to the example described with reference to FIG. 16, the case of changing the NFC processing mode into the on-host mode from the off-host mode is taken as an example. Yet, a case of changing the NFC processing mode into the off-host mode from the on-host mode may be similar to the case taken as the example in the description with reference to FIG. 16. Instead, in case that the NFC processing mode is changed into the off-host mode from the on-host mode, the host CPU 185 can control the NFC controller 114a so that AID of each application having the routing route information in the application related information correspond to ‘Host’ among the applications related to the NFC card saved in the memory 170 can be saved in the routing table.

In the following description, if a storage capacity of a routing table in the NFC controller 114a is exceeded, a method of solving such a problem is described in detail with reference to FIGs. 17 to 22.

FIG. 17 is a flowchart to describe one example of a method of solving a problem of an exceeded storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention. The following description with reference to FIG. 17 is made on the assumption that an NFC processing mode is an off-host mode.

Referring to FIG. 17, the host CPU 185 controls the mobile communication module 112 or the wireless internet module 113 to download an application related to an NFC card and an application related information [S901]. As mentioned in the foregoing description, the application related information may include an AID for identifying the NFC card related to the application and a routing information indicating that the NFC card is emulated through a prescribed one of the SE 195 and the host CPU 185.

The host CPU 185 installs the downloaded application [S902]. And, the host CPU 185 checks the routing route information in the application related information [S903].

Based on an NFC processing mode and the routing route information, if the routing route information corresponds to ‘Host’ [Yes, S904], the host CPU 185 controls the NFC controller 114a so that the AID in the application related information can be saved in a routing table [S905].

Depending on an embodiment, if a plurality of NFC cards related to the application exist, the application related information may include AID and routing route information for each of the NFC cards. In the step S904 and S905, the host CPU 185 may control the NFC controller 114a so that the AID of each NFC card corresponding to the routing route information corresponding to ‘Host’ among the routing route informations on a plurality of NFC cards can be saved in the routing table.

The host CPU 185 detects whether a storage capacity of the routing table in the NFC controller 114a is exceeded [S906]. Depending on an embodiment, the host CPU 185 may detect an excess of the storage capacity of the routing table in the course of saving an AID of the application having the routing route information correspond to ‘Host’ in the routing table within the NFC controller 114a. Since a storage space, which remains in the routing table after completion of saving an AID of the application having the routing route information correspond to ‘Host in the routing table within the NFC controller 114a’, is smaller than a preset extent, if it is difficult to add an AID in the future, the host CPU 185 may detect an excess of the storage capacity of the routing table. When an AID of the application having the routing route information correspond to ‘Host’ starts to be saved in the routing table within the NFC controller 114a, if a size of the AID to be saved is greater than a storage space remaining in the routing table, the host CPU 185 may detect an excess of the storage capacity of the routing table.

If the host CPU 185 detects that the storage capacity of the routing table in the NFC controller 114a is exceeded [Yes, S906], the host CPU 185 controls the display unit 151 to output a notification message for notifying the excess of the storage capacity to a user [S907]. Depending on an embodiment, the notification message may include at least one of a notification message for guiding a user in changing an NFC processing mode, a notification message for guiding a user in deleting the installed application, a notification message for guiding a user in deleting at last one of applications installed ahead of the installed application, and a notification message for guiding a user in deleting at least one of a plurality of NFC cards related to some of applications saved in the memory 170.

Depending on an embodiment, the host CPU 185 can determine whether the storage capacity of the routing table in the NFC controller 114a is exceeded when a new application is downloaded, when a new application is installed, when a user command for running a newly installed application is detected, when an NFC processing mode is changed into an on-host mode from an off-host mode, when an NFC processing mode is changed into an off-host mode from an on-host mode, and/or when a deactivated state of an NFC function is changed into an activated state. In this case, the user command may include one of a user command for initially running a new application, a user command for selecting a new application having a routing route information correspond to ‘Host’ in off-host mode as a default application, and a user command for selecting a new application having a routing route information correspond to ‘Off-Host’ in off-host mode as a default application.

Moreover, according to the description with reference to FIG. 17, the case that the NFC processing mode is the off-host mode is taken as an example. Yet, since a case of the NFC processing mode set to the on-host mode is similar to the above case shown in FIG. 17 except that the AID of the application having the routing route information correspond to ‘Off Host’ is saved in the routing table in the steps S904 and S905, details of the case of setting the NFC processing mode to the on-host mode shall be omitted from the following description.

FIG. 18 is a flowchart to describe one example of a case of outputting a guide message for guiding a user in changing an NFC processing mode if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded. The following description with reference to FIG. 18 is made on the assumption that an NFC processing mode is an off-host mode.

Referring to FIG. 18, if the host CPU 185 detects that a storage capacity of a routing table within the NFC controller 114a is exceeded, the host CPU 185 controls the display unit 151 to output a guide message for guiding a user in changing an NFC processing mode into an on-host mode from an off-host mode [S911].

The host CPU 185 checks an application related information of each of applications related to an NFC card saved in the memory 170 [S913]. And, the host CPU 185 controls the NFC controller 114a so that an AID of each NFC card related to an application having a routing route information in the application related information correspond to ‘Off-Host’ can be saved in the routing table [S914]. In this case, existing AIDs saved in the routing table within the NFC controller 114a in the off-host mode can be deleted.

FIG. 19 is a diagram to describe one example of a guide message for guiding a user in changing an NFC processing mode outputted through a display unit if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded. FIG. 19 (a) shows a case that an NFC processing mode is changed into an on-host mode from an off-host mode. And, FIG. 19 (b) shows a case that an NFC processing mode is changed into an off-host mode from an on-host mode.

Referring to FIG. 19 (a), if a storage capacity of a routing table within the NFC controller 114a is exceeded, a guide message 920 for guiding a user in changing an NFC processing mode into an on-host mode from an off-host mode can be outputted through the display unit 151.

If the user selects a setting menu 921 in the guide message 920, a 1st screen 930 for setting the NFC processing mode can be outputted through the display unit 151. In this case, the 1st screen 930 may include a 1st menu 931 for selecting the off-host mode as the NFC processing mode and a 2nd menu 932 for selecting the on-host mode as the NFC processing mode. Since the NFC processing mode is currently set to the off-host mode, the 1st menu 931 can be activated and displayed.

If the user selects the 2nd menu 932 from the 1st screen 930, the 2nd menu 932 can be activated and displayed.

If the user intends to go back to a previous screen, a 2nd screen 940 including a list 941 of applications related to an NFC card saved in the memory 170 can be outputted through the display unit 151.

Besides, when the guide message 920 is outputted through the display unit 151, if a specific menu included in the guide message 920 is selected, although the user does not make a separate menu selection for changing the NFC processing mode, the NFC processing mode may be directly changed into the on-host mode from the off-host mode [not shown in the drawing].

Referring to FIG. 19 (b), if a storage capacity of a routing table within the NFC controller 114a is exceeded, a guide message 920 for guiding a user in changing an NFC processing mode into an off-host mode from an on-host mode can be outputted through the display unit 151.

If the user selects a setting menu 921 in the guide message 920, a 1st screen 930 for setting the NFC processing mode can be outputted through the display unit 151. In this case, the 1st screen 930 may include a 1st menu 931 for selecting the off-host mode as the NFC processing mode and a 2nd menu 932 for selecting the on-host mode as the NFC processing mode. Since the NFC processing mode is currently set to the on-host mode, the 2nd menu 932 can be activated and displayed.

If the user selects the 1st menu 931 from the 1st screen 930, the 1st menu 931 can be activated and displayed.

Besides, when the guide message 920 is outputted through the display unit 151, if a specific menu included in the guide message 920 is selected, although the user does not make a separate menu selection for changing the NFC processing mode, the NFC processing mode may be directly changed into the off-host mode from the on-host mode [not shown in the drawing].

FIG. 20 is a diagram to describe one example of a guide message for guiding a user in deleting an application outputted through a display unit if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded. The following description with reference to FIG. 20 is made on the assumption that an NFC processing mode is an on-host mode.

Referring to FIG. 20 (a), a storage capacity of a routing table within the NFC controller 114a is exceeded, a guide message 950 for guiding a user in deleting prescribed application(s) can be outputted through the display unit 151.

If the user selects a confirm menu 951 in the guide message 950, referring to FIG. 20 (b), a 1st screen 960 can be outputted through the display unit 151.

A list of deletable applications is displayed on the 1st screen 960. The application included in the list 961 may be an application installed by being downloaded ahead of a newly installed application or an application having a routing route information in an application information correspond to ‘Off-Host’ due to a current NFC processing mode set to an on-host mode. In the on-host processing mode, only if the application having the routing route information in the application information correspond to ‘Off-Host’ is deleted, it is able to secure the storage capacity of the routing table within the NFC controller 114a. The user deletes at least one portion of the applications included in the list 961 and is then able to run the newly installed application. On the contrary, if a current NFC mode is set to the off-host mode, an application included in the list 961 may be an application corresponding to ‘Host’.

Depending on an embodiment, when the storage capacity of the routing table within the NFC controller 114a is exceeded, if it is difficult to solve the problem of the excess of the storage capacity of the routing table despite changing the NFC processing mode, the guide message 950 may be outputted through the display unit 151.

FIG. 21 is a diagram to describe one example of a screen outputted through a display unit if a storage capacity of a routing table in an NFC controller of a mobile terminal according to one embodiment of the present invention is exceeded.

Referring to FIG. 21, if a specific one of applications saved in the memory 170 is related to a plurality of NFC cards, the host CPU 185 can control the display unit 151 to output a guide message for guiding a user in deleting at least one portion of a plurality of the NFC cards. If the user selects a confirm menu in the guide message, a 1st screen 970 shown in FIG. 21 can be outputted through the display unit 151. In this case, the specific application may include an application related to the NFC card having a routing route information in an application related information correspond to ‘Host’ if an NFC processing mode is an off-host mode. And, the specific application may include an application related to the NFC card having a routing route information in an application related information correspond to ‘Off-Host’ if an NFC processing mode is an on-host mode.

If the NFC processing mode is the off-host mode, a list 971 of the NFC cards, each of which routing route information in the application related information correspond to ‘Host’, among the NFC cards related to the specific application may be displayed on the 1st screen 970. If the NFC processing mode is the on-host mode, a list 971 of the NFC cards, each of which routing route information in the application related information correspond to ‘Off-Host’, among the NFC cards related to the specific application may be displayed on the 1st screen 970.

The user cam delete at least one portion of the NFC cards included in the list 971.

Depending on an embodiment, when the storage capacity of the routing table within the NFC controller 114a is exceeded, if it is difficult to solve the problem of the excess of the storage capacity of the routing table despite changing the NFC processing mode, the 1st screen 970 may be outputted through the display unit 151.

FIG. 22 is a diagram to describe a method of solving a problem, which is caused if a storage capacity of a routing table in an NFC controller is exceeded due to an NFC processing mode changed by a user, according to one embodiment of the present invention. According to the example shown in FIG. 22, as an NFC processing mode is changed, it is able to solve a problem of a case of an excess of a storage capacity within the NFC controller instead of changing the NFC processing mode to solve the problem of the excess of the storage capacity within the NFC controller.

Referring to FIG. 22 (a), a 1st screen 1000 for setting an NFC processing mode is outputted through the display unit 151. In this case, the 1st screen 1000 may include a 1st menu 1001 for selecting an off-host mode as the NFC processing mode and a 2nd menu 1002 for selecting an on-host mode as the NFC processing mode. Assume that the NFC processing mode is currently set to the off-host mode.

If a user selects the 2nd menu 1002 from the 1st screen 1000, the host CPU 185 may control the display unit 151 to output a 1st guide message 1010 for checking that the NFC processing mode will be changed into an on-host processing mode.

If the user selects a confirm menu 1011 from the 1st guide message 1010, the host CPU 185 may perform a job for changing the NFC processing mode into the on-host mode from the off-host mode. Since this is similar to the former description of the steps S912 to S914 with reference to FIG. 18, its details shall be omitted from the following description.

While the host CPU 185 performs the job for changing the NFC processing mode into the on-host mode from the off-host mode, if an excess of a storage capacity of a routing table within the NFC controller 114a is detected, referring to FIG. 22 (c), the host CPU 185 may control the display unit 151 to output a 2nd guide message 1020.

If the NFC processing mode is changed into the on-host mode from the off-host mode, since the storage capacity of the routing table within the NFC controller 114a is exceeded, the 2nd guide message 1020 may include a guide message for guiding a user in deleting prescribed application(s). In this case, since the NFC processing mode to be changed is the on-host processing mode, the prescribed application(s) may include an application having a routing route information in an application information correspond to ‘Off-Host’.

If the user selects a confirm menu 1021 from the 2nd guide message 1020, referring to FIG. 22 (d), the host CPU 185 may control the display unit 151 to display a 2nd screen 1030. In this case, the 2nd screen 1030 includes a list 1031 of deletable applications. Since the 2nd screen 1030 is similar to the 1st screen 960 shown in FIG. 20 (b), its details shall be omitted from the following description.

According to at least one of the embodiments mentioned in the foregoing description, if a storage capacity of a routing table within an NFC controller in a mobile terminal supportive of HCE (host-based card emulation) function is exceeded, a solution for solving a problem of the storage capacity excess can be provided.

Various embodiments may be implemented using a machine-readable medium having instructions stored thereon for execution by a processor to perform various methods presented herein. Examples of possible machine-readable mediums include HDD(Hard Disk Drive), SSD(Solid State Disk), SDD(Silicon Disk Drive), ROM, RAM, CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, the other types of storage mediums presented herein, and combinations thereof. If desired, the machine-readable medium may be realized in the form of a carrier wave (for example, a transmission over the Internet). The processor may include the controller 180 of the mobile terminal.

The foregoing embodiments are merely exemplary and are not to be considered as limiting the present disclosure. The present teachings can be readily applied to other types of methods and apparatuses. This description is intended to be illustrative, and not to limit the scope of the claims. Many alternatives, modifications, and variations will be apparent to those skilled in the art. The features, structures, methods, and other characteristics of the exemplary embodiments described herein may be combined in various ways to obtain additional and/or alternative exemplary embodiments.

As the present features may be embodied in several forms without departing from the characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, unless otherwise specified, but rather should be considered broadly within its scope as defined in the appended claims, and therefore all changes and modifications that fall within the metes and bounds of the claims, or equivalents of such metes and bounds, are therefore intended to be embraced by the appended claims.

The present invention relates to a mobile terminal and a method for controlling the same. Therefore, the present invention has industrial applicability.

Claims

A method of controlling a mobile terminal supportive of HCE (host-based card emulation), comprising:

downloading a first application related to an NFC (near field communication) card and a first application related information related to the first application, the first application related information including first information for identifying the NFC card and second information indicating whether the NFC card is emulated through an SE (secure element) or a host framework; and

processing the first information if a preset condition is met, based on an NFC processing mode for determining a routing route of third information for identifying a specific NFC card received by an NFC controller from an external NFC reader and the second information,

wherein the preset condition includes at least one of a condition of installing the downloaded first application and a condition of installing the downloaded first application and then detecting a user command for initially running the installed first application and

wherein the NFC processing mode comprises either an off-host mode on the basis of a route for the NFC controller to route the third information to the SE or an on-host mode on the basis of a route for the NFC controller to route the third information to the host framework.
The method of claim 1, wherein if the NFC processing mode is the off-host mode, the processing the first information comprises saving the first information in a routing table within the NFC controller, if the second information indicates that the NFC card is emulated through the host framework.
The method of claim 1, wherein if the NFC processing mode is the on-host mode, the processing the first information comprises saving the first information in a routing table within the NFC controller, if the second information indicates that the NFC card is emulated through the SE.
The method of claim 2, further comprising:

receiving the third information for identifying the specific NFC card from the external NFC reader by the NFC controller; and

if the received third information matches the first information saved in the routing table within the NFC controller, routing the third information to the host framework from the NFC controller.
The method of claim 3, further comprising:

receiving the third information for identifying the specific NFC card from the external NFC reader by the NFC controller; and

if the received third information matches the first information saved in the routing table within the NFC controller, routing the third information to the SE from the NFC controller.
The method of claim 1, wherein if a plurality of NFC cards related to the first application exist, the first application related information includes the first information on each of a plurality of the NFC cards and the second information on each of a plurality of the NFC cards.
The method of claim 6, wherein when the NFC processing mode is the off-host mode, the processing the first information comprises saving the first information of the NFC card, which corresponds to the second information indicating that the NFC card is emulated through the host framework among the second information on a plurality of the NFC cards, in the routing table within the NFC controller.
The method of claim 6, wherein when the NFC processing mode is the on-host mode, the processing the first information comprises saving the first information of the NFC card, which corresponds to the second information indicating that the NFC card is emulated through the SE among the second information on a plurality of the NFC cards, in the routing table within the NFC controller.
The method of claim 6, wherein when the NFC processing mode is the off-host mode, the processing the first information comprises checking a presence or non-presence of additional information of the first information of the NFC card corresponding to the second information, which indicates that the NFC card is emulated through the host framework, among the information on a plurality of the NFC cards and saving the first information having the additional information in the routing table within the NFC controller based on a result of the check.
The method of claim 6, wherein when the NFC processing mode is the on-host mode, the processing the first information comprises checking a presence or non-presence of additional information of the first information of the NFC card corresponding to the second information, which indicates that the NFC card is emulated through the SE, among the second information on a plurality of the NFC cards and saving the first information having the additional information in the routing table within the NFC controller based on a result of the check.
The method of claim 2, further comprising:

detecting an excess of a storage capacity of the routing table within the NFC controller; and

outputting a notification message indicating that the storage capacity of the routing table is exceeded.
The method of claim 11, wherein the notification message comprises at least one of a notification message for guiding a user in changing the NFC processing mode into the on-host mode from the off-host mode, a notification message for guiding the user in deleting at least one portion of applications installed ahead of the first application and a notification message for guiding the user in deleting at least one of a plurality of NFC cards in case of the first application related to a plurality of the NFC cards.
The method of claim 12, if the notification comprises the notification message for guiding the user in changing the NFC processing mode into the on-host mode from the off-host mode, the method further comprising:

detecting a user command for selecting a change into the on-host mode from the off-host mode;

checking application related information on each of applications related to the NFC card saved in a memory, the application related information including first information for identifying an NFC card related to each of the applications and second information indicating whether the NFC card is emulated through the SE or the host framework; and

saving the first information on each NFC card corresponding to the second information, which indicates the NFC card is emulated through the SE, in the routing table within the NFC controller.
The method of claim 13, the saving the first information on the each NFC card corresponding to the 2nd information, which indicates the NFC card is emulated through the SE, in the routing table within the NFC controller, comprising deleting the first information of the NFC card corresponding to the second information indicating that the NFC card is emulated through the host frame work from the routing table within the NFC controller.
The method of claim 3, further comprising:

detecting an excess of the storage capacity of the routing table within the NFC controller;

outputting a notification message for guiding a user in changing the NFC processing mode into the off-host mode from the on-host mode:

detecting a user command for selecting a change into the off-host mode from the on-host mode;

checking application related information on each of applications related to the NFC card saved in a memory, the application related information including first information for identifying an NFC card related to each of the applications and second information indicating whether the NFC card is emulated through the SE or the host framework; and

saving the first information on each NFC card corresponding to the second information, which indicates the NFC card is emulated through the host framework, in the routing table within the NFC controller.
A mobile terminal supportive of HCE (host-based card emulation), comprising:

a host framework;

an SE (secure element);

an NFC controller to route a data communication between an external NFC reader and the host framework and a data communication between the external NFC reader and the SE; and

a display unit,

wherein the host framework saves applications related to an NFC (near field communication) card and application related information,

wherein the application related information includes first information for identifying the NFC card related to each of the applications and second information indicating whether the NFC card is emulated through an SE (secure element) or a host framework,

wherein based on an NFC processing mode for determining a routing route of third information for identifying a specific NFC card received from the external NFC reader and the second information, the NFC controller saves a routing table in which the first information for identifying at least one NFC card is saved,

wherein the NFC processing mode comprises either an off-host mode on the basis of a route for the NFC controller to route the third information to the SE or an on-host mode on the basis of a route for the NFC controller to route the third information to the host framework,

wherein the host framework detects an excess of a storage capacity of the routing table within the NFC controller if a preset condition is met, and

wherein the host framework controls the display unit to output a notification message indicating that the storage capacity of the routing table is exceeded.
The mobile terminal of claim 16, wherein the preset condition comprises at least one of a condition of downloading an application related to a new NFC card, a condition of downloading the application related to the new NFC card and then installing the downloaded application, a condition of detecting a user command for initially running one of applications related to the NFC card saved in a memory, a condition of changing the NFC processing mode into the on-host mode from the off-host mode, a condition of changing the NFC processing mode into the off-host mode from the on-host mode, and a condition of changing a deactivated state of an NFC function in the mobile terminal into an activated state.
The mobile terminal of claim 16, wherein if the NFC processing mode is the off-host mode, the NFC controller routes the third information to the host framework if the third information for identifying the specific NFC card received from the external NFC reader matches the first information saved in the routing table, wherein if the NFC processing mode comprises the off-host mode, the NFC controller routes the third information to the SE if the third information for identifying the specific NFC card received from the external NFC reader fails to match the first information saved in the routing table, wherein if the NFC processing mode comprises the on-host mode, the NFC controller routes the third information to the SE if the third information for identifying the specific NFC card received from the external NFC reader matches the first information saved in the routing table, wherein if the NFC processing mode comprises the on-host mode, the NFC controller routes the third information to the host framework if the third information for identifying the specific NFC card received from the external NFC reader fails to match the first information saved in the routing table.
The mobile terminal of claim 18, wherein if the NFC processing mode is the off-host mode, the host framework detects the user command for changing the NFC processing mode into the on-host mode from the off-host mode, checks the application related information on each of the applications related to the NFC card saved in the memory, deletes the first information saved in the routing table within the NFC controller, and controls the NFC controller to save the first information on each NFC card corresponding to the second information, which indicates that the NFC card is emulated through the SE, in the routing table.
The mobile terminal of claim 18, wherein if the NFC processing mode is the on-host mode, the host framework detects the user command for changing the NFC processing mode into the on-host mode from the off-host mode, checks the application related information on each of the applications related to the NFC card saved in the memory, deletes the first information saved in the routing table within the NFC controller, and controls the NFC controller to save the first information on each NFC card corresponding to the second information, which indicates that the NFC card is emulated through the host framework, in the routing table.