Electronic device and operation method of electronic device including touch screen panel

Abstract

In an electronic device according to various embodiments, the electronic device includes a touch screen and a processor, and the processor determines the type of user input entered on the touch screen as either a first touch type or a second touch type, and in response to determining the type of the entered touch as the first touch type, outputs a UI (user interface) corresponding to the first touch type, and in response to determining that there is an error in determining the type of the entered touch as the first touch type, modifies the determined type to the second touch type and outputs a UI corresponding to the second touch type. In a method of operation of an electronic device according to various embodiments, the method of operation of the electronic device may include: an operation of determining the type of user input entered on a touch screen as either a first touch type or a second touch type; an operation of outputting a UI (user experience) corresponding to the first touch type in response to determining the type of the entered touch as the first touch type; an operation of modifying the determined type to the second touch type in response to determining that there is an error in determining the type of the entered touch as the first touch type; and an operation of outputting a UI corresponding to the second touch type. Various other embodiments are possible.

Description

Technology Field

[0001] The various embodiments disclosed in this document relate to an electronic device including a touch screen panel and a method of operating the electronic device, and more specifically, to an electronic device and a method of operating the electronic device for determining the type of touch input to the touch screen panel and determining whether there is an error in determining the touch type. Background Technology

[0003] A touch screen panel refers to a screen that allows users to input commands directly on the screen without using a keyboard, by detecting the location where a touch object (e.g., a part of the user's body) touches characters or specific areas displayed on the screen. Because these touch screen panels integrate display and input devices, they are widely utilized in portable display devices such as smartphones and tablet PCs, as well as in large display devices like smart TVs and public facilities.

[0004] A touch screen is an input means in which a touch object, such as a finger, a stylus pen, or a pointer, contacts an area of ​​the display where the screen is output, and various inputs can be obtained depending on the contact method. For example, a touch screen can receive various touch inputs including force touch, long press, short (or tap) touch, long touch, multi touch, drag touch, flick touch, pinch-in touch, pinch-out touch, swipe touch, and hovering touch. Generally, a force touch input is a touch input that is entered briefly with relatively large pressure compared to a long touch input, and a long touch input may be a touch input that is entered for a long time with relatively small pressure compared to a force touch input.

[0005] However, for some users, there is a concern that the two input types may be confused due to the existence of an area where the pressure condition of Force Touch input and the duration condition of Long Touch input overlap. For example, depending on the user, Force Touch input pressure may be applied for a longer period of time with lower pressure than other users. The problem to be solved

[0007] Various embodiments disclosed in this document can determine the type of touch input to a touch screen panel and, based on the determination of whether there is an error in determining the touch type, update a personalized touch type determination model to the user or correct the touch type to provide user convenience functions.

[0008] Specifically, the electronic device of the various embodiments disclosed in this document can determine whether there is an error in determining the touch type based on user actions after determining the type of touch input to the touch screen panel (e.g., force touch and / or long touch) and update the touch type determination model.

[0009] For example, the electronic device disclosed in this document may determine whether a touch input to a touch screen panel is a force touch or a long touch based on input elements such as coordinates, time, and area. Based on the determined type, the electronic device may output a UI (user experience) corresponding to the determined touch type, such as a 'copy or move selection window for the area selected by touch,' a 'volume control window,' or an 'extension of a rollable display.' After outputting the UI, the electronic device may determine that there is an error in determining the touch type if a specified action occurs, such as 'the user lifting their finger from the touch screen without operating the UI.' The electronic device may classify touch data based on the user's subsequent actions and store it in a database, and update a model that classifies touch types based on the stored touch data.

[0010] In addition, if the electronic device disclosed in this document determines that there is an error in the touch type determined for an input touch, it can correct the touch type and output the UI associated with the corrected touch type again.

[0011] For example, the electronic device disclosed in this document may, after determining that an input touch is a force touch, if it determines that there is an error in determining it as a force touch because the user's intention is determined to be a long touch, display a UI related to a long touch again even without additional user action.

[0012] The technical problems to be solved in this document are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this invention belongs from the description below. means of solving the problem

[0014] An electronic device according to various embodiments disclosed in this document includes a touch screen and a processor, wherein the processor determines the type of user input entered on the touch screen as either a first touch type or a second touch type, outputs a UI (user interface) corresponding to the first touch type in response to determining the type of the input touch as the first touch type, and corrects the determined type to the second touch type in response to determining that there is an error in determining the type of the input touch as the first touch type, and outputs a UI corresponding to the second touch type.

[0015] A method of operation of an electronic device according to various embodiments disclosed in this document may include: determining the type of user input entered on a touch screen as either a first touch type or a second touch type; outputting a UI (user experience) corresponding to the first touch type in response to determining the type of the input touch as the first touch type; modifying the determined type to the second touch type in response to determining that there is an error in determining the type of the input touch as the first touch type; and outputting a UI corresponding to the second touch type. Effects of the invention

[0017] For example, an electronic device can determine whether there is an error in determining the touch type based on user actions after determining the touch type.

[0018] For example, an electronic device can update a touch type determination model by learning data based on individual user characteristics.

[0019] For example, an electronic device can generate a touch type determination model personalized to the user.

[0020] For example, electronic devices can update a touch type determination model based on individual user characteristics to reduce errors in distinguishing between long touch and force touch types.

[0021] For example, electronic devices can accurately recognize the touch type.

[0022] For example, if there is an error in determining the touch type, the electronic device can correct the touch type.

[0023] For example, if there is an error in determining the touch type, the electronic device can output a UI related to the corrected touch type.

[0024] For example, even if a touch type recognition error occurs on an electronic device, the user can be provided with a UI related to the corrected touch type without any additional action. Brief explanation of the drawing

[0026] In relation to the description of the drawings, identical or similar configurations on the element Identical or similar reference numerals may be used for this. FIG. 1 is a block diagram of an electronic device in a network environment according to various embodiments. FIG. 2 is a block diagram of an electronic device according to various embodiments. FIG. 3 is a flowchart illustrating a method for controlling an electronic device so that a processor according to various embodiments determines a touch-type error and updates a recognition model. FIGS. 4a, FIGS. 4b, FIGS. 4c, FIGS. 4d, and FIGS. 4e are drawings illustrating the operation of a processor according to various embodiments determining the touch type of an input touch and determining whether there is an error in the touch type. FIGS. 5A and 5B are drawings illustrating the operation of a processor according to various embodiments to store touch data in a correct answer database and / or an incorrect answer database in response to an error in the touch type. FIG. 6 is a flowchart illustrating a method for a processor according to various embodiments to control an electronic device to update a recognition model. FIG. 7 is a flowchart illustrating a method for controlling an electronic device so that a processor according to various embodiments outputs a UI in response to a touch type determination error. FIGS. 8a and 8b are drawings illustrating the operation of a processor according to various embodiments outputting a UI corresponding to a corrected touch type in response to a touch type determination error. Specific details for implementing the invention

[0027] FIG. 1 is a block diagram of an electronic device (101) in a network environment (100) according to various embodiments. Referring to FIG. 1, in the network environment (100), the electronic device (101) may communicate with an electronic device (102) through a first network (198) (e.g., a short-range wireless communication network) or may communicate with at least one of an electronic device (104) or a server (108) through a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) through a server (108). According to one embodiment, the electronic device (101) may include a processor (120), memory (130), input module (150), sound output module (155), display module (160), audio module (170), sensor module (176), interface (177), connection terminal (178), haptic module (179), camera module (180), power management module (188), battery (189), communication module (190), subscriber identification module (196), or antenna module (197). In some embodiments, at least one of these components (e.g., connection terminal (178)) may be omitted from the electronic device (101), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (176), camera module (180), or antenna module (197)) may be integrated into a single component (e.g., display module (160)).

[0028] The processor (120) can control at least one other component (e.g., hardware or software component) of the electronic device (101) connected to the processor (120) by executing software (e.g., program (140)), for example, and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (120) can store commands or data received from other components (e.g., sensor module (176) or communication module (190)) in volatile memory (132), process the commands or data stored in volatile memory (132), and store the resulting data in non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., central processing unit or application processor) or an auxiliary processor (123) that can operate independently or together with it (e.g., graphics processing unit, neural processing unit (NPU), image signal processor, sensor hub processor, or communication processor). For example, if the electronic device (101) includes a main processor (121) and an auxiliary processor (123), the auxiliary processor (123) may be configured to use lower power than the main processor (121) or to be specialized for a designated function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as part thereof.

[0029] The auxiliary processor (123) may control at least some of the functions or states associated with at least one component of the electronic device (101) (e.g., display module (160), sensor module (176), or communication module (190)) on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor (123) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (180) or communication module (190)). According to one embodiment, the auxiliary processor (123) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or through a separate server (e.g., server (108)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers.An artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

[0030] The memory (130) can store various data used by at least one component of the electronic device (101) (e.g., processor (120) or sensor module (176)). The data may include, for example, input data or output data for software (e.g., program (140)) and related commands. The memory (130) may include volatile memory (132) or non-volatile memory (134).

[0031] The program (140) may be stored as software in memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

[0032] The input module (150) can receive commands or data to be used for a component of the electronic device (101) (e.g., processor (120)) from outside the electronic device (101) (e.g., user). The input module (150) may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0033] The sound output module (155) can output a sound signal to the outside of the electronic device (101). The sound output module (155) may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as multimedia playback or recording playback. The receiver may be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part thereof.

[0034] The display module (160) can visually provide information to an external (e.g., user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling said device. According to one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of the force generated by said touch.

[0035] The audio module (170) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150) or output sound through the sound output module (155) or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (101).

[0036] The sensor module (176) can detect the operating state of the electronic device (101) (e.g., power or temperature) or the external environmental state (e.g., user state) and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module (176) may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0037] The interface (177) may support one or more specified protocols that can be used for the electronic device (101) to be connected directly or wirelessly to an external electronic device (e.g., electronic device (102)). According to one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0038] The connection terminal (178) may include a connector through which the electronic device (101) can be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0039] The haptic module (179) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module (179) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

[0040] The camera module (180) can capture still images and video. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

[0041] The power management module (188) can manage the power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented, for example, as at least part of a power management integrated circuit (PMIC).

[0042] The battery (189) can supply power to at least one component of the electronic device (101). According to one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0043] The communication module (190) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may include one or more communication processors that operate independently of the processor (120) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (104) through a first network (198) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (199) (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (196).

[0044] The wireless communication module (192) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (192) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (192) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), full-dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large-scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), external electronic device (e.g., electronic device (104)), or network system (e.g., second network (199)). According to one embodiment, the wireless communication module (192) can support a Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mMTC, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) for realizing URLLC.

[0045] An antenna module (197) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (197) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as a first network (198) or a second network (199), may be selected from the plurality of antennas, for example, by a communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (197).

[0046] According to various embodiments, the antenna module (197) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.

[0047] At least some of the above components can be connected to each other via a communication method between peripheral devices (e.g., bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)) and exchange signals (e.g., commands or data) with each other.

[0048] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) through a server (108) connected to a second network (199). Each of the external electronic devices (102, or 104) may be the same or different type of device as the electronic device (101). According to one embodiment, all or part of the operations performed on the electronic device (101) may be performed on one or more of the external electronic devices (102, 104, or 108). For example, if the electronic device (101) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (101) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (101) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server using machine learning and / or neural networks. According to one embodiment, the external electronic device (104) or the server (108) may be included within a second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0049] FIG. 2 is a block diagram of an electronic device (200) according to various embodiments.

[0050] Referring to FIG. 2, an electronic device (200) (e.g., electronic device (101) of FIG. 1) may include a processor (220) (e.g., processor (120) of FIG. 1), memory (230) (e.g., memory (130) of FIG. 1) and / or a touch sensor (276) (e.g., sensor module (176) of FIG. 1). The components included in FIG. 2 are only a part of the components included in the electronic device (200), and the electronic device (200) may also include various other components as shown in FIG. 1.

[0051] A touch sensor (276) according to various embodiments may include a touch screen panel (TSP). The touch screen panel may operate in at least one of a capacitive method, a resistive method, an infrared method, an acoustic method, or a pressure method.

[0052] A touch sensor (276) according to one embodiment may be configured to detect at least one of the position coordinates, area, pressure at the time of touch, and capacitance at the time of touch of a touch object applying a touch on a touch screen. The touch object is an object that applies a touch to the touch sensor (276), and may be, for example, an object that can come into contact with the touch sensor (276), such as a finger, a touch pen or stylus pen, or a pointer.

[0053] A touch sensor (276) according to one embodiment can sense various types of touches on a touch screen, such as a short touch, a long touch, a multi touch, a drag touch, a flick touch, a pinch-in touch, a pinch-out touch, a swype touch, a hovering touch, and / or a force touch.

[0054] For example, a force touch may be a touch type in which the position coordinates of the touch are maintained within a specified range of the initial touch position coordinates, and the pressure applied at the time of touch is greater than or equal to the specified pressure.

[0055] For example, a long touch may be a touch type in which the position coordinates of a touch input on a touch screen are maintained within a specified range of the initial touch position coordinates, and the touch holding time is longer than a specified time.

[0056] According to one embodiment, the touch sensor (276) may include a capacitive touch screen panel. For example, the touch sensor (276) may include a substrate having a special conductive metal coated on both sides to form a transparent electrode, and may sense a touch based on location coordinates where a change in capacitance occurs when a touch object contacts the touch screen.

[0057] According to one embodiment, the touch sensor (276) may include a resistive touch screen panel. For example, the touch sensor (276) may include two substrates coated with a transparent electrode layer, and may sense a touch based on the position coordinates of the substrates that come into contact with each other by pressure when a touch object comes into contact with the touch screen.

[0058] According to one embodiment, the touch sensor (276) may include an infrared touch screen panel. For example, the touch sensor (276) may include a plurality of light-emitting elements and light-receiving elements, and may sense a touch based on the position coordinates of a portion where light rays are blocked when a touch object comes into contact with the touch screen.

[0059] According to one embodiment, the touch sensor (276) may include an acoustic touch screen panel. For example, the touch sensor (276) may include an acoustic transducer that generates sound waves on a surface and may sense a touch based on a change in the amplitude of a wave that changes when a touch object comes into contact with the touch screen.

[0060] According to one embodiment, the touch sensor (276) may include a pressure-type touch screen panel. For example, the touch sensor (276) may include a pressure sensor capable of measuring touch pressure and may sense a touch based on the pressure applied by a touch object to the touch screen.

[0061] A touch sensor (276) according to one embodiment may be configured to convert pressure applied to a touch screen, a change in capacitance, a change in the amplitude of a wave, and a change in light into an electrical input signal.

[0062] A processor (220) according to various embodiments may include a touch processing module (221), a touch condition determination module (222), a touch type determination module (223), a touch error determination module (224) and / or a recognition model modification module (225).

[0063] A processor (220) according to one embodiment may be composed of at least one processor unit or may be implemented as a single package. The processor unit may include an application processor, a touch IC, a display control IC, and / or a separate microprocessor. According to one embodiment, at least one of a touch processing module (221), a touch condition determination module (222), a touch type determination module (223), a touch error determination module (224), and a recognition model modification module (225) may be implemented in the touch IC.

[0064] A touch processing module (221) according to one embodiment can process a touch input signal obtained from a touch sensor (276). For example, the touch processing module (221) can obtain touch data corresponding to the touch input signal from the touch sensor (276). For example, the touch data may be a sequence of data processed from continuously collected input signals. For example, the touch data may be image data corresponding to the touch input signal. For example, the touch data may be image data related to touch location coordinates, touch area, and touch holding time as a touch object comes into contact with the touch screen.

[0065] A touch processing module (221) according to one embodiment can generate coordinate data corresponding to an input signal obtained from a touch sensor (276).

[0066] A touch processing module (221) according to one embodiment can transmit coordinate data to some modules included in the processor (220), and the module can convert the coordinate data into display scale data and process it so that it can be used in an OS framework. The touch processing module (221) can determine a touch event corresponding to the input signal (e.g., short touch, multi touch, drag touch, flick touch, pinch-in touch, pinch-out touch, swipe touch and / or hovering touch) based on an input signal obtained from a touch sensor (276), and transmit the determined touch event to an OS framework operating in an Application processor.

[0067] A touch processing module (221) according to one embodiment can store touch data in a touch data temporary storage space (231).

[0068] A touch condition determination module (222) according to one embodiment can determine whether user input satisfies a condition for determining a touch type. For example, the touch condition determination module (222) can obtain touch data and / or coordinate data including touch position coordinates from a touch processing module (221). The touch condition determination module (222) can determine that the touch satisfies a condition for determining a touch type in response to the touch position coordinates being maintained within a specified range of the initial touch position coordinates and the touch holding time exceeding a specified time (e.g., 300 msec). For example, the touch condition determination module (222) can transmit a notification to a touch type determination module (223) in response to the touch data and / or coordinate data satisfying a specified condition.

[0069] A touch type determination module (223) according to one embodiment can determine the touch type of user input. For example, the touch type determination module (223) can determine the touch type as a first touch type and / or a second touch type. For example, the first touch type and / or the second touch type may be a long touch and / or a force touch.

[0070] For example, the touch type determination module (223) may obtain touch data corresponding to the user input from the touch data temporary storage space (231) in response to receiving a notification from the touch condition determination module (222) that the user input satisfies a specified condition. For example, the touch type determination module (223) may determine the touch type of the touch data based on a recognition model stored in the recognition model storage space (232). For example, the touch type determination module (223) may determine the touch type as either a first touch type and / or a second touch type based on a value obtained by inputting the touch data into the recognition model. For example, the touch type determination module (223) may determine the touch type as a first touch type in response to the value obtained by inputting the touch data into the recognition model being greater than or equal to a specified value, and determine the touch type as a second touch type in response to the value being less than a specified value. For example, the touch type determination module (223) can transmit the determined touch type to the main processor (e.g., the main processor (121) of FIG. 1).

[0071] According to one embodiment, the main processor (121) can perform operations based on a determined touch type. For example, the main processor (121) can output a UI corresponding to the touch type. For example, the main processor (121) can output a UI corresponding to the first touch type (e.g., a volume control window UI and / or screen size control). For example, the main processor (121) can output a UI corresponding to the second touch type (e.g., a copy or move selection window UI for a selected area). According to one embodiment, the main processor (121) can output a UI corresponding to a pre-set touch type in the application in response to the running application.

[0072] A touch error determination module (224) according to one embodiment can determine whether there is an error in the touch type determined by the touch type determination module (223).

[0073] According to one embodiment, the touch error determination module (224) can determine that the touch type determination module (223) has an error in determining the touch type in response to satisfying a specified condition.

[0074] For example, the touch error determination module (224) may determine that there is an error in determining the touch type (e.g., the first touch type) in response to the fact that, after the touch type determination module (223) determines the input touch as the first touch type and the main processor (121) outputs the UI related to the first touch type, the user does not receive additional operation input regarding the UI related to the first touch type, and the touch object that was in contact with the touch screen is separated and the touch location coordinates are lost.

[0075] For example, the touch error determination module (224) may determine that there is an error in determining the touch type (e.g., second touch type) in response to the touch target touching another area of ​​the touch screen, after the touch type determination module (223) determines the input touch as a second touch type and the main processor (121) outputs a UI related to the second touch type, and the user does not receive additional operation input regarding the UI related to the second touch type.

[0076] For example, the touch error determination module (224) may determine that there is an error in determining the touch type (e.g., second touch type) in response to the user operating a physical key (e.g., volume control and / or screen size control) after the touch type determination module (223) determines the input touch as a second touch type and the main processor (121) outputs a UI related to the second touch type, and the user does not receive additional operation input from the user regarding the UI related to the second touch type.

[0077] According to one embodiment, the touch error determination module (224) can determine that the touch type determination module (223) has no error in determining the touch type in response to satisfying a specified condition. For example, the touch error determination module (224) can determine that the touch type determination module (223) has no error in determining the touch type in response to receiving input from a user to operate a UI corresponding to the determined touch type. For example, the touch error determination module (224) can determine that there is no error in determining the touch type as the first touch type in response to receiving input from a user to operate a first touch type UI. For example, the touch error determination module (224) can determine that there is no error in determining the touch type as the second touch type in response to receiving input from a user to operate a second touch type UI.

[0078] A touch error determination module (224) according to one embodiment can store touch data in an incorrect answer database (233) in response to the touch type determination module (224) determining that there is an error in determining the touch type.

[0079] For example, the touch error determination module (224) may label the touch data as “first touch type incorrect answer” and store it in the incorrect answer database (233) in response to the touch type determination module (223) determining that there is an error in the touch data determined as a first touch type. For example, the touch error determination module (224) may label the touch data as “second touch type incorrect answer” and store it in the incorrect answer database (233) in response to the touch type determination module (223) determining that there is an error in the touch data determined as a second touch type.

[0080] A touch error determination module (224) according to one embodiment can store touch data in a correct answer database (234) in response to the touch type determination module (224) determining that there is no error in determining the touch type.

[0081] For example, the touch error determination module (224) may label the touch data as “first touch type correct answer” and store it in the correct answer database (234) in response to the touch type determination module (223) determining that there is no error in the touch data determined as the first touch type. For example, the touch error determination module (224) may label the touch data as “second touch type correct answer” and store it in the correct answer database (233) in response to the touch type determination module (223) determining that there is no error in the touch data determined as the second touch type.

[0082] A recognition model modification module (225) according to one embodiment can update a recognition model stored in a recognition model storage space (232) based on touch data stored in an incorrect answer database (233) and a correct answer database (234).

[0083] According to one embodiment, the recognition model modification module (225) may update the recognition model in response to satisfying specified conditions. For example, the recognition model modification module (225) may update the recognition model in response to the amount of touch data stored in the incorrect answer database (233) and / or the correct answer database (234) being greater than or equal to a specified value. For example, the recognition model modification module (225) may update the recognition model in response to the electronic device (200) not being in operation, the remaining battery level of the electronic device (200) being greater than or equal to a specified value, and / or the temperature of the electronic device (200) being less than or equal to a specified value. According to one embodiment, some of the recognition model update operations may be performed on an external server (not shown).

[0084] According to one embodiment, the recognition model modification module (225) can determine the recognition model based on touch data stored in the incorrect answer database (233) and / or the correct answer database (234).

[0085] According to one embodiment, the recognition model modification module (225) may determine a recognition model by learning (or adaptive learning) touch data stored in the incorrect answer database (233) and / or correct answer database (234). For example, the recognition model modification module (225) may determine a recognition model by learning at least one of the touch data labeled as “first touch type incorrect answer” and “second touch type incorrect answer” stored in the incorrect answer database (233), the touch data labeled as “first touch type correct answer” and the touch data labeled as “second touch type correct answer” stored in the correct answer database (234). For example, the recognition model modification module (225) may determine a recognition model that determines the type of the first touch type and / or the second touch type by learning the touch data stored in the incorrect answer database (233) and / or correct answer database (234). For example, the recognition model modification module (225) can learn touch data stored in the incorrect answer database (233) and / or correct answer database (234) to determine a recognition pattern that serves as a criterion for determining the type of the first touch type and / or the second touch type.

[0086] According to one embodiment, the recognition model modification module (225) can determine a recognition model to be used by the touch type determination module (223) among a plurality of recognition models stored in the recognition model storage space (232) based on touch data stored in the incorrect answer database (233) and / or the correct answer database (234). For example, the recognition model modification module (225) inputs touch data stored in the incorrect answer database (233) and / or the correct answer database (234) into a plurality of recognition models, and Recognition performanceThis highest recognition model can be determined as the recognition model to be used in the touch type determination module (223). For example, the recognition model modification module (225) analyzes the touch data stored in the incorrect answer database (233) and / or correct answer database (234), The recognition rate A recognition model based on the highest recognition pattern can be determined as the recognition model to be used in the touch type determination module (223).

[0087] According to one embodiment, the recognition model modification module (225) can update the determined recognition model in the recognition model storage space (232). According to one embodiment, the recognition model modification module (225) can determine the determined recognition model among a plurality of recognition models in the recognition model storage space (232) as the recognition model to be used by the touch type determination module (223).

[0088] A memory (230) according to various embodiments may include a touch data temporary storage space (231), a recognition model storage space (232), an incorrect answer database (233) and / or a correct answer database (234).

[0089] A touch data temporary storage space (231) according to one embodiment can temporarily store touch data obtained from a touch processing module (221). According to one embodiment, a touch type determination module (223) can determine a touch type by obtaining touch data stored in the touch data temporary storage space (231).

[0090] According to one embodiment, the recognition model storage space (232) may temporarily or indefinitely store a recognition model used by the touch type determination module (223) to determine the touch type of touch data. According to one embodiment, the recognition model storage space (232) may temporarily or indefinitely store a plurality of recognition models of different types. According to one embodiment, the recognition model modification module (225) may update the recognition model stored in the recognition model storage space (232).

[0091] According to one embodiment, the incorrect answer database (233) can temporarily or indefinitely store touch data that the touch error judgment module (224) has determined to be an incorrect answer.

[0092] According to one embodiment, the correct answer database (234) can temporarily or indefinitely store touch data determined as the correct answer by the touch error determination module (224).

[0093] According to one embodiment, the incorrect answer database (233) and the correct answer database (234) may be implemented as a single database without physical or logical distinction. In all embodiments disclosed below, the incorrect answer database and the correct answer database used to update the recognition model may be the single database. For example, the single database may be the same storage space that stores touch data labeled as "incorrect answer" or "correct answer".

[0094] According to one embodiment, the recognition model modification module (225) can update the recognition model based on touch data stored in the incorrect answer database (233) and / or the correct answer database (234).

[0095] FIG. 3 is a flowchart illustrating a method for a processor (e.g., processor (220) of FIG. 2) according to various embodiments to determine a touch-type error and update a recognition model by controlling an electronic device (e.g., electronic device (200) of FIG. 2).

[0096] A processor (220) according to various embodiments can determine a condition for determining a touch type in operation 310.

[0097] A processor (220) according to one embodiment can process a touch input signal obtained from a touch sensor (e.g., the touch sensor (276) of FIG. 2). For example, the processor (220) can obtain touch data corresponding to the touch input signal from the touch sensor (276). For example, the touch data may be a series of data processed from continuously collected input signals. For example, the touch data may be image data corresponding to the touch input signal. For example, the touch data may be image data related to touch location coordinates, touch area, and touch holding time as a touch object comes into contact with the touch screen.

[0098] A processor (220) according to one embodiment can generate coordinate data corresponding to an input signal obtained from a touch sensor (276). A processor (220) according to one embodiment can process the coordinate data by converting it into display-scale data so that it can be used in an OS framework. According to one embodiment, a touch IC can perform the generation of the coordinate data, and an application processor in which the OS framework operates can perform up-scaling to match the display resolution and convert it into display-scale data. At this time, the up-scaling process can be implemented by multiplying the coordinate data by a certain constant.

[0099] A processor (220) according to one embodiment can store touch data in a touch data temporary storage space (231).

[0100] A processor (220) according to one embodiment can determine whether user input satisfies conditions for determining a touch type. For example, the processor (220) can determine that the touch satisfies conditions for determining a touch type in response to the touch position coordinates being maintained within a specified range of the initial touch position coordinates and the touch holding time exceeding a specified time (e.g., 300 msec).

[0101] A processor (220) according to various embodiments can determine the touch type of the input touch in operation 320.

[0102] A processor (220) according to one embodiment can determine the touch type of user input. For example, the processor (220) can determine the touch type as a first touch type and / or a second touch type. For example, the first touch type and / or the second touch type may be a long touch and / or a force touch.

[0103] For example, the processor (220) may obtain touch data corresponding to user input from the touch data temporary storage space (231). For example, the processor (220) may determine the touch type of the touch data based on a recognition model stored in the recognition model storage space (232). For example, the processor (220) may determine the touch type as a first touch type and / or a second touch type based on a value obtained by inputting the touch data into the recognition model. For example, the processor (220) may determine the touch type as a first touch type in response to the value obtained by inputting the touch data into the recognition model being greater than or equal to a specified value, and determine the touch type as a second touch type in response to the value being less than a specified value.

[0104] According to one embodiment, the processor (220) can perform operations based on a determined touch type. For example, the processor (220) can output a UI corresponding to the touch type. For example, the processor (220) can output a first touch type UI (e.g., volume control window UI and / or screen size control) in response to the touch type being determined as a first touch type. For example, the processor (220) can output a second touch type UI (e.g., copy or move selection window UI of a selected area) in response to the touch type being determined as a second touch type. According to one embodiment, the processor (220) can output a UI corresponding to a pre-set touch type in the application in response to the running application.

[0105] A processor (220) according to various embodiments can determine whether there is an error in the determined touch type in operation 330.

[0106] According to one embodiment, the processor (220) can determine that there is an error in the touch type determination in response to satisfying a specified condition.

[0107] For example, the processor (220) may determine that there is an error in determining the touch type (e.g., the first touch type) after determining the input touch as the first touch type and outputting the UI associated with the first touch type, and in response to the fact that the user does not input additional operations regarding the UI associated with the first touch type and the touch object that was in contact with the touch screen is separated and the touch position coordinates are lost.

[0108] For example, the processor (220) may determine that there is an error in determining the touch type (e.g., second touch type) after determining the input touch as a second touch type and outputting a UI related to the second touch type, and in response to the touch target touching another area of ​​the touch screen without receiving additional operation input from the user regarding the UI related to the second touch type.

[0109] For example, the processor (220) may determine that there is an error in determining the touch type (e.g., second touch type) after determining the input touch as a second touch type and outputting a UI associated with the second touch type, and in response to the user operating a physical key (e.g., a physical key for volume control and / or screen size control) without receiving additional operation from the user regarding the UI associated with the second touch type.

[0110] According to one embodiment, the processor (220) may determine that there is no error in determining the touch type in response to satisfying a specified condition. For example, the processor (220) may determine that there is no error in determining the touch type in response to receiving input from a user to operate a UI corresponding to the determined touch type. For example, the processor (220) may determine that there is no error in determining the touch type as a first touch type in response to receiving input from a user to operate a first touch type UI. For example, the processor (220) may determine that there is no error in determining the touch type as a second touch type in response to receiving input from a user to operate a second touch type UI.

[0111] A processor (220) according to one embodiment may store touch data in an incorrect answer database (233) in response to determining that there is an error in determining the touch type.

[0112] For example, the processor (220) may, in response to determining that there is an error in determining the first touch type for the touch data, label the corresponding touch data as “first touch type incorrect answer” and store it in the incorrect answer database (233). For example, the processor (220) may, in response to determining that there is an error in determining the second touch type for the touch data, label the corresponding touch data as “second touch type incorrect answer” and store it in the incorrect answer database (233).

[0113] A processor (220) according to one embodiment can store touch data in a correct answer database (234) in response to determining that there is no error in determining the touch type.

[0114] For example, the processor (220) may store the touch data in the answer database (234) by labeling it as “first touch type correct answer” in response to determining that there is no error in determining the touch data as a first touch type. For example, the processor (220) may store the touch data in the answer database (233) by labeling it as “second touch type correct answer” in response to determining that there is no error in determining the touch data as a second touch type.

[0115] A processor (220) according to various embodiments can update a recognition model in operation 340.

[0116] A processor (220) according to one embodiment can update a recognition model stored in a recognition model storage space (232) based on touch data stored in an incorrect answer database (233) and a correct answer database (234).

[0117] According to one embodiment, the processor (220) may update the recognition model in response to satisfying a specified condition. For example, the processor (220) may update the recognition model in response to the amount of touch data stored in the incorrect answer database (233) and / or the correct answer database (234) being greater than or equal to a specified value. For example, the processor (220) may update the recognition model in response to the electronic device (200) not being in operation, the remaining battery level of the electronic device (200) being greater than or equal to a specified value, and / or the temperature of the electronic device (200) being less than or equal to a specified value.

[0118] According to one embodiment, the processor (220) can determine a recognition model based on touch data stored in an incorrect answer database (233) and / or a correct answer database (234).

[0119] According to one embodiment, the processor (220) may determine a recognition model by learning touch data stored in an incorrect answer database (233) and / or a correct answer database (234). For example, the processor (220) may determine a recognition model by learning touch data labeled as a “first touch type incorrect answer” and touch data labeled as a “second touch type incorrect answer” stored in the incorrect answer database (233), touch data labeled as a “first touch type correct answer” and / or touch data labeled as a “second touch type correct answer” stored in the correct answer database (234).

[0120] For example, the processor (220) may determine a recognition model that determines the type of the first touch type and / or the second touch type by learning touch data stored in the incorrect answer database (233) and / or the correct answer database (234). For example, the processor (220) may determine a recognition pattern that serves as a criterion for determining the type of the first touch type and / or the second touch type by learning touch data stored in the incorrect answer database (233) and / or the correct answer database (234).

[0121] According to one embodiment, the processor (220) may determine a recognition model to be used for determining a touch type among a plurality of recognition models stored in a recognition model storage space (232) based on touch data stored in an incorrect answer database (233) and / or a correct answer database (234). For example, the processor (220) inputs touch data stored in the incorrect answer database (233) and / or the correct answer database (234) into a plurality of recognition models, and Recognition performance This highest recognition model can be determined as the recognition model to be used for determining the touch type. For example, the processor (220) analyzes the touch data stored in the incorrect answer database (233) and / or correct answer database (234), Performance and / or suitabilityA recognition model based on the highest recognition pattern can be determined as the recognition model to be used for touch type determination.

[0122] According to one embodiment, the processor (220) can update the determined recognition model in the recognition model storage space (232). According to one embodiment, the processor (220) can determine the determined recognition model among a plurality of recognition models in the recognition model storage space (232) as the recognition model to be used for touch type determination.

[0123] FIGS. 4a, FIGS. 4b, FIGS. 4c and FIGS. 4d are drawings illustrating the operation of a processor (e.g., processor (220) of FIG. 2) according to various embodiments determining the touch type of an input touch and determining whether there is an error in the touch type.

[0124] FIG. 4a is a diagram illustrating the operation in which, when a user inputs a touch on a touch screen with the intention of a long touch, the processor (220) determines the touch type of the input touch and determines whether there is an error in the determined touch type.

[0125] Referring to FIG. 4a (a), a user may input a touch on a touch screen with the intention of a long touch. A touch type determination module (e.g., touch type determination module (223) of FIG. 2) may input the touch data of the touch input by the user into a recognition model and determine the touch type as a force touch.

[0126] Referring to FIG. 4a (b), the main processor (e.g., the main processor of FIG. 1 (121)) can output a force touch UI (e.g., a volume control window UI) in response to the touch type determination module (223) determining that it is a force touch.

[0127] Referring to FIG. 4a (c), the user may remove their hand from the touchscreen without operating the Force Touch UI in response to the Force Touch UI being displayed instead of the intended long touch input. A touch error determination module (e.g., touch error determination module (224) of FIG. 2) may determine that there is an error in determining the touch type as Force Touch in response to the touch coordinates disappearing as the user removes their hand from the touchscreen without receiving additional operation input from the user regarding the Force Touch UI. According to one embodiment, the main processor (121) may stop the output of the Force Touch UI in response to the touch error determination module (224) determining that there is an error in determining the touch type as Force Touch.

[0128] Referring to FIG. 4a (d), the user can re-enter a touch on the touch screen with the intention of a long touch. The touch type determination module (223) can input the touch data of the touch entered by the user into a recognition model and determine the touch type of the touch entered by the user as a long touch.

[0129] Referring to FIG. 4a (e), the main processor (121) can output a long touch UI (e.g., a copy or move selection window for a selected area) in response to the touch type determination module (223) determining that it is a long touch. The user can operate the long touch UI in response to the output of the intended long touch UI. The touch error determination module (224) can determine that there is no error in determining the touch type as a long touch in response to receiving input from the user to operate the long touch UI.

[0130] FIG. 4b is a diagram illustrating the operation in which, when a user inputs a touch on a touch screen with the intent of a force touch, the processor (220) determines the touch type of the input touch and determines whether there is an error in the determined touch type.

[0131] Referring to FIG. 4b (a), the user may input a touch on the touch screen with the intent of a force touch. The touch type determination module (223) may input the touch data of the touch input by the user into a recognition model and determine the touch type as a long touch.

[0132] Referring to FIG. 4b (b), the main processor (121) can output a long touch UI (e.g., a copy or move selection window UI of a selected area) in response to the touch type determination module (223) determining that it is a long touch.

[0133] Referring to FIG. 4b (c), in response to a long touch UI being displayed instead of the intended force touch input, the user may touch another area of ​​the touch screen without operating the long touch UI. The touch error determination module (224) may determine that there is an error in determining the touch type as a long touch because it fails to receive additional operation input from the user regarding the force touch UI and the user touches another area of ​​the touch screen. According to one embodiment, the main processor (121) may stop the output of the long touch UI in response to the touch error determination module (224) determining that there is an error in determining the touch type as a long touch.

[0134] Referring to FIG. 4b (d), the user can re-enter a touch on the touch screen with the intention of a force touch. The touch type determination module (223) can input the touch data of the touch entered by the user into a recognition model and determine the touch type of the touch entered by the user as a force touch.

[0135] Referring to FIG. 4b (e), the main processor (121) can output a Force Touch UI (e.g., volume control window UI) in response to the touch type determination module (223) determining that it is a Force Touch. The user can operate the Force Touch UI in response to the intended Force Touch UI being output. The touch error determination module (224) can determine that there is no error in determining the touch type as a Force Touch in response to receiving input from the user to operate the Force Touch UI.

[0136] FIG. 4c is a drawing illustrating the operation of a processor (220) determining the touch type of the input touch and determining whether there is an error in the determined touch type when a user inputs a touch on a touch screen with the intention of making a long touch in an electronic device (200) including a rollable display.

[0137] Referring to FIG. 4c (a), the user may input a touch on the touch screen with the intention of a long touch. The touch type determination module (223) may input the touch data of the touch input by the user into a recognition model and determine the touch type as a force touch.

[0138] Referring to FIG. 4c (b), the main processor (121) can output a force touch UI (e.g., screen size adjustment UI) in response to the touch type determination module (223) determining that it is a force touch.

[0139] Referring to FIG. 4c (c), the user may remove their hand from the touchscreen without operating the Force Touch UI in response to the Force Touch UI being displayed instead of the intended long touch input. The touch error determination module (224) may determine that there is an error in determining the touch type as Force Touch in response to the touch coordinates disappearing as the user removes their hand from the touchscreen without receiving additional operation input from the user regarding the Force Touch UI. According to one embodiment, the main processor (121) may stop the output of the Force Touch UI in response to the touch error determination module (224) determining that there is an error in determining the touch type as Force Touch.

[0140] Referring to FIG. 4c (d), the user can re-enter a touch on the touch screen with the intention of a long touch. The touch type determination module (223) can input the touch data of the touch entered by the user into a recognition model and determine the touch type of the touch entered by the user as a long touch.

[0141] Referring to FIG. 4c (e), the main processor (121) can output a long touch UI (e.g., a copy or move selection window for a selected area) in response to the touch type determination module (223) determining that it is a long touch. The user can operate the long touch UI in response to the intended long touch UI being output. The touch error determination module (224) can determine that there is no error in determining the touch type as a long touch in response to receiving input from the user to operate the long touch UI.

[0142] FIG. 4d is a drawing illustrating the operation of a processor (220) determining the touch type of the input touch and determining whether there is an error in the determined touch type when a user inputs a touch on a touch screen with the intent of a force touch in an electronic device (200) including a rollable display.

[0143] Referring to FIG. 4d (a), the user may input a touch on the touch screen with the intent of a force touch. The touch type determination module (223) may input the touch data of the touch input by the user into a recognition model and determine the touch type as a long touch.

[0144] Referring to FIG. 4d (b), the main processor (121) can output a long touch UI (e.g., a copy or move selection window UI of a selected area) in response to the touch type determination module (223) determining that it is a long touch.

[0145] Referring to FIG. 4d (c), the user can release their hand from the touchscreen without manipulating the long touch UI in response to the long touch UI being displayed instead of the intended force touch input.

[0146] Referring to FIG. 4d (d), the user can operate a physical key to adjust the intended screen size. The touch error determination module (224) may determine that there is an error in determining the touch type as a long touch when the user does not receive additional input from the user regarding the long touch UI and the user operates a physical key (e.g., a physical key for adjusting the screen size). According to one embodiment, the main processor (121) may stop the output of the long touch UI in response to the touch error determination module (224) determining that there is an error in determining the touch type as a long touch.

[0147] Referring to FIG. 4d (e), the main processor (121) can expand the screen size of the rollable display in response to a user clicking a physical key.

[0148] FIG. 4e is a diagram illustrating the operation in which, when a user intentionally inputs a touch on a touch screen, the processor (220) determines the touch type of the input touch and determines whether there is an error in the determined touch type.

[0149] Referring to FIG. 4e (a), the user may input a touch on the touch screen with the intent of a force touch. The touch type determination module (223) may input the touch data of the touch input by the user into a recognition model and determine the touch type as a long touch.

[0150] Referring to FIG. 4e (b), the main processor (121) can output a long touch UI (e.g., a copy or move selection window UI of a selected area) in response to the touch type determination module (223) determining that it is a long touch.

[0151] Referring to FIG. 4e (c), the user can release their hand from the touchscreen without manipulating the long touch UI in response to the long touch UI being displayed instead of the intended force touch input.

[0152] Referring to FIG. 4e (d), the user can operate a physical key to adjust the intended volume level. The touch error determination module (224) may determine that there is an error in determining the touch type as a long touch when the user does not receive additional input from the user regarding the long touch UI and the user operates a physical key (e.g., a physical key for adjusting the volume level). According to one embodiment, the main processor (121) may stop the output of the long touch UI in response to the touch error determination module (224) determining that there is an error in determining the touch type as a long touch.

[0153] Referring to FIG. 4e (e), the main processor (121) can adjust the volume in response to a user clicking a physical key.

[0154] According to one embodiment, in FIGS. 4a to 4e, the touch error determination module (224) may store the touch data corresponding to the user input of FIG. (a) in the error database (233) by labeling it as “long touch incorrect answer” or “force touch incorrect answer” in response to determining that there is an error in determining the touch type of the touch corresponding to the user input of FIG. (a). According to one embodiment, in FIGS. 4a to 4e, the touch error determination module (224) may store the touch data corresponding to the user input of FIG. (d) in the answer database (234) by labeling it as “long touch correct answer” or “force touch correct answer”. According to another embodiment, the touch error determination module (224) may label touch data corresponding to user input (a) in FIGS. 4a to 4e as “long touch incorrect answer” or “force touch incorrect answer”, and label touch data corresponding to user input (d) in FIGS. 4a to 4c as “long touch correct answer” or “force touch correct answer”, and store them in a database including an incorrect answer database (233) and a correct answer database (234).

[0155] FIGS. 5A and 5B are drawings illustrating the operation of a processor (e.g., processor (220) of FIG. 2) according to various embodiments, which stores touch data in a correct answer database and / or an incorrect answer database in response to an error in the touch type.

[0156] FIG. 5a is a diagram illustrating the operation of, when a user inputs a touch with the intention of a long touch, the processor (220) determines the touch type of the input touch and, in response to an error in determining the touch type, stores the touch data in a correct answer database (e.g., the correct answer database (233) of FIG. 2) and / or an incorrect answer database (e.g., the incorrect answer database (234) of FIG. 2).

[0157] Referring to FIG. 5a (a), the user may input a touch with the intention of a long touch. The touch type determination module (223) may determine the touch type of the touch input by the user as a force touch.

[0158] Referring to FIG. 5a (b), the main processor (e.g., the main processor (121) of FIG. 1) can output a Force Touch UI (e.g., a volume control window UI) in response to the touch type determination module (223) determining that it is a Force Touch. The user can remove their hand from the display without operating the Force Touch UI in response to the Force Touch UI being output, which is not an intended long touch input. The touch error determination module (224) can determine that there is an error in determining the touch type as Force Touch in response to the touch coordinates disappearing as the user removes their hand from the display without receiving additional operation input from the user regarding the Force Touch UI.

[0159] Referring to FIG. 5a (c), the user may re-enter a touch with the intention of a long touch. The touch type determination module (223) can determine the touch type of the touch entered by the user as a long touch.

[0160] Referring to FIG. 5a (d), the main processor (121) can output a long touch UI (e.g., a copy or move selection window UI of a selected area) in response to the touch type determination module (223) determining that it is a long touch. The user can operate the long touch UI in response to the intended long touch UI being output. The touch error determination module (224) can determine that there is no error in determining the touch type as a long touch in response to receiving input from the user to operate the long touch UI.

[0161] Referring to FIG. 5a (e), the touch error determination module (224) may store touch data corresponding to the touch input of FIG. 5a (a) in the incorrect answer database (233) by labeling it as “force touch incorrect answer” and store touch data corresponding to the user input of FIG. 5a (d) in the correct answer database (234) by labeling it as “long touch correct answer”. According to another embodiment, the touch error determination module (224) may store touch data corresponding to the touch input of FIG. 5a (a) in the incorrect answer database (233) and touch data corresponding to the user input of FIG. 5a (d) in the correct answer database (234) by labeling it as “force touch incorrect answer” and labeling it as “long touch correct answer”.

[0162] FIG. 5b is a diagram illustrating the operation in which, when a user inputs a touch with the intent of a force touch, the processor (220) determines the touch type of the input touch and, in response to an error in determining the touch type, stores the touch data in the correct answer database (233) and / or incorrect answer database (234).

[0163] Referring to FIG. 5b (a), the user can input a touch with the intent of a force touch. The touch type determination module (223) can determine the touch type of the touch input by the user as a long touch.

[0164] Referring to FIG. 5b (b), the main processor (121) can output a long touch UI (e.g., a copy or move selection window UI of a selected area) in response to the touch type determination module (223) determining that it is a long touch. In response to the long touch UI being output, which is not the intended force touch input, the user can remove their hand from the display without operating on the long touch UI. The touch error determination module (224) can determine that there is an error in determining the touch type as a long touch in response to the touch coordinates disappearing as the user removes their hand from the display without receiving additional operation input from the user regarding the long touch UI.

[0165] Referring to FIG. 5b (c), the user can re-enter a touch with the intention of a force touch. The touch type determination module (223) can determine the touch type of the touch entered by the user as a force touch.

[0166] Referring to FIG. 5b (d), the main processor (121) can output a Force Touch UI (e.g., a volume control window UI) in response to the touch type determination module (223) determining that it is a Force Touch. The user can operate the Force Touch UI in response to the intended Force Touch UI being output. The touch error determination module (224) can determine that there is no error in determining the touch type as a Force Touch in response to receiving input from the user to operate the Force Touch UI.

[0167] Referring to FIG. 5b (e), the touch error determination module (224) may label the touch data corresponding to the user input of FIG. 5b (a) as “long touch incorrect answer” and store it in the incorrect answer database (233), and label the touch data corresponding to the user input of FIG. 5b (d) as “force touch correct answer” and store it in the correct answer database (234). According to another embodiment, the touch error determination module (224) may label the touch data corresponding to the touch input of FIG. 5b (a) as “long touch incorrect answer” and label the touch data corresponding to the user input of FIG. 5b (d) as “force touch correct answer” and store it in a database including the incorrect answer database (233) and the correct answer database (234).

[0168] FIG. 6 is a flowchart illustrating a method in which a processor (e.g., processor (220) of FIG. 2) according to various embodiments controls an electronic device (e.g., electronic device (200) of FIG. 2) to update a recognition model.

[0169] A processor (220) according to various embodiments can check the amount of data in the database in operation 610.

[0170] According to one embodiment, the processor (220) can check the amount of touch data stored in an incorrect answer database (e.g., incorrect answer database (233) of FIG. 2) and / or a correct answer database (e.g., correct answer database (234) of FIG. 2).

[0171] According to one embodiment, the processor (220) may perform operation 620 in response to the amount of touch data stored in the incorrect answer database (233) and / or correct answer database (234) being greater than or equal to a specified value.

[0172] A processor (220) according to various embodiments can check the state of an electronic device (200) in operation 620.

[0173] According to one embodiment, the processor (220) can check whether the electronic device (200) is in a specified state. For example, the processor (220) can check whether the electronic device (200) is running. For example, the processor (220) can check the remaining battery level of the electronic device (200). For example, the processor (220) can check the temperature of the electronic device (200).

[0174] According to one embodiment, the processor (220) may perform operation 630 in response to the electronic device (200) being in a specified state. For example, the processor (220) may perform operation 630 in response to the electronic device (200) not being in operation, or the remaining battery level of the electronic device (200) being greater than or equal to a specified value and / or the temperature of the electronic device (200) being less than or equal to a specified value.

[0175] A processor (220) according to various embodiments may determine a recognition model based on touch data stored in an incorrect answer database (233) and / or a correct answer database (234) in operation 630.

[0176] According to one embodiment, the processor (220) may determine a recognition model by learning touch data stored in an incorrect answer database (233) and / or a correct answer database (234). For example, the processor (220) may determine a recognition model by learning touch data labeled as a “first touch type incorrect answer” and touch data labeled as a “second touch type incorrect answer” stored in the incorrect answer database (233), touch data labeled as a “first touch type correct answer” and / or touch data labeled as a “second touch type correct answer” stored in the correct answer database (234).

[0177] For example, the processor (220) can determine a recognition model that determines the type of the first touch type and / or the second touch type by learning touch data stored in the incorrect answer database (233) and / or the correct answer database (234). For example, the processor (220) can determine a recognition pattern that serves as a criterion for determining the type of the first touch type and / or the second touch type by learning touch data stored in the incorrect answer database (233) and / or the correct answer database (234).

[0178] According to one embodiment, the processor (220) can determine a recognition model to be used in the touch type determination module (223) among a plurality of recognition models stored in the recognition model storage space (232) based on touch data stored in the incorrect answer database (233) and / or the correct answer database (234). For example, the processor (220) inputs touch data stored in the incorrect answer database (233) and / or the correct answer database (234) into a plurality of recognition models, and Recognition performance This highest recognition model can be determined as the recognition model to be used in the touch type determination module (223). For example, the processor (220) analyzes touch data stored in the incorrect answer database (233) and / or correct answer database (234), Performance and / or suitability A recognition model based on the highest recognition pattern can be determined as the recognition model to be used in the touch type determination module (223).

[0179] Various Examples to The corresponding processor (220) can update the recognition model in operation 640.

[0180] According to one embodiment, the processor (220) can update the recognition model determined in operation 630 in the recognition model storage space (232). According to one embodiment, the processor (220) can determine the recognition model determined in operation 630 among a plurality of recognition models in the recognition model storage space (232) as the recognition model to be used in the touch type determination module (223).

[0181] According to one embodiment, the processor (220) can determine the touch type of the input touch based on an updated recognition model.

[0182] FIG. 7 is a flowchart illustrating a method for controlling an electronic device so that a processor (e.g., the processor (220) of FIG. 2) according to various embodiments outputs a UI in response to a touch type determination error.

[0183] According to various embodiments, the processor (220) can determine the touch type of the input touch in operation 710.

[0184] For example, the processor (220) can determine the touch type of user input input to the touch sensor (e.g., touch sensor (276) of FIG. 2) as a first touch type and / or a second touch type. For example, the first touch type and / or the second touch type may be a long touch and / or a force touch.

[0185] According to one embodiment, the processor (220) can determine the touch type of the user input based on the touch data, which is image data corresponding to the user input, and the recognition model. For example, the processor (220) can determine the touch type as a first touch type and / or a second touch type based on a value obtained by inputting the touch data into the recognition model. For example, the processor (220) can determine the touch type as a first touch type in response to the value obtained by inputting the touch data into the recognition model being greater than or equal to a specified value, and determine the touch type as a second touch type in response to the value being less than the specified value.

[0186] According to one embodiment, the processor (220) can determine the touch type of user input based on touch pressure obtained from the touch sensor (276). For example, the processor (220) can determine the touch type of user input as a first touch type in response to the touch pressure being greater than or equal to a specified value, and determine the touch type as a second touch type in response to the touch pressure being less than the specified value.

[0187] According to various embodiments, the processor (220) can output a UI corresponding to a determined touch type in operation 720.

[0188] According to one embodiment, the processor (220) can perform operations based on a determined touch type. For example, the processor (220) can output a UI corresponding to the touch type. For example, the processor (220) can output a UI corresponding to the first touch type (e.g., a volume control window UI and / or a screen size control window UI) in response to the touch type being determined as a first touch type. For example, the processor (220) can output a UI corresponding to the second touch type (e.g., a copy or move selection window UI for a selected area) in response to the touch type being determined as a second touch type. According to one embodiment, the processor (220) can output a UI corresponding to a pre-set touch type in the application in response to the running application.

[0189] According to various embodiments, the processor (220) can determine whether there is an error in the determined touch type in operation 730.

[0190] According to one embodiment, the processor (220) can determine that there is an error in the touch type determination in response to satisfying a specified condition.

[0191] For example, the processor (220) may determine that there is an error in determining the touch type as the first touch type, after determining the input touch as the first touch type and outputting the UI associated with the first touch type, and in response to the fact that the user does not input additional operations regarding the UI associated with the first touch type and the touch object that was in contact with the touch screen within a specified time is separated and the touch position coordinates are lost.

[0192] For example, the processor (220) may determine that there is an error in determining the touch type (e.g., second touch type) after determining the input touch as a second touch type and outputting a UI related to the second touch type, and in response to the touch target touching another area of ​​the touch screen without receiving additional operation input from the user regarding the UI related to the second touch type.

[0193] For example, the processor (220) may determine that there is an error in determining the touch type (e.g., second touch type) after determining the input touch as a second touch type and outputting a UI related to the second touch type, and in response to the user not receiving additional operation input regarding the UI related to the second touch type and the touch object applying pressure to the same area again.

[0194] According to one embodiment, the processor (220) may determine that there is no error in determining the touch type in response to satisfying a specified condition. For example, the processor (220) may determine that there is no error in determining the touch type in response to receiving input from a user to operate a UI corresponding to the determined touch type. For example, the processor (220) may determine that there is no error in determining the touch type as the first touch type in response to receiving input from a user to operate a first touch type UI. For example, the processor (220) may determine that there is no error in determining the touch type as the second touch type in response to receiving input from a user to operate a second touch UI.

[0195] According to various embodiments, the processor (220) can output a UI corresponding to the corrected touch type in operation 740.

[0196] According to one embodiment, the processor (220) can correct the touch type of the user input in response to an error in determining the touch type. For example, the processor (220) can correct the touch type to a second touch type in response to determining that there is an error in determining the initial touch type as a first touch type. For example, the processor (220) can correct the touch type to a first touch type in response to determining that there is an error in determining the initial touch type as a second touch type.

[0197] According to one embodiment, the processor (220) may perform an operation based on the corrected touch type. For example, the processor (220) may stop the UI output corresponding to the initial touch type and output a UI corresponding to the corrected touch type. For example, the processor (220) may stop the UI output corresponding to the second touch type in response to correcting the touch type to the first touch type and output a UI corresponding to the first touch type (e.g., volume control window UI and / or screen size control window UI). For example, the processor (220) may stop the UI output corresponding to the first touch type in response to correcting the touch type to the second touch type and output a UI corresponding to the second touch type (e.g., copy or move selection window UI of a selected area). According to one embodiment, the processor (220) may output a UI corresponding to a pre-set touch type in the application in response to the running application.

[0198] FIGS. 8a and 8b are drawings illustrating the operation of a processor (e.g., processor (220) of FIG. 2) according to various embodiments outputting a UI corresponding to a corrected touch type in response to a touch type determination error.

[0199] FIG. 8a is a diagram illustrating the operation in which, when a user inputs a touch with the intention of making a long touch, the processor (220) outputs a UI corresponding to the long touch in response to a touch type determination error.

[0200] Referring to FIG. 8a (a), a user may input a touch on a touchscreen with the intention of a long touch. A processor (220) may input touch data of the touch input by the user into a recognition model and determine the touch type as a force touch. A processor (220) may determine the touch type as a force touch based on the pressure of the touch input by the user.

[0201] Referring to FIG. 8a (b), the processor (220) can output a Force Touch UI (e.g., a volume control window UI) in response to determining that the touch type is Force Touch.

[0202] Referring to FIG. 8a (c), the user may remove their hand from the touchscreen without operating the Force Touch UI in response to the Force Touch UI being displayed instead of the intended long touch input. The processor (220) may determine that there is an error in determining the touch type as Force Touch in response to the user removing their hand from the touchscreen and the touch coordinates disappearing as the user does not receive additional operation input from the user regarding the Force Touch UI. The processor (220) may stop the output of the Force Touch UI in response to determining that there is an error in determining the touch type as Force Touch. According to one embodiment, the processor (220) may stop the output of the Force Touch UI and control the display (160) so that the Force Touch UI disappears from the display (e.g., the display module (160) of FIG. 1) in response to determining that there is an error in determining the touch type as Force Touch when a part of the Force Touch UI has been or is being displayed.

[0203] Referring to FIG. 8a (d), the processor (220) can correct the touch type of the user input to a long touch in response to an error in determining the touch type as a force touch. In response to correcting the touch type to a long touch, the processor (220) can output a long touch UI (e.g., a selection window UI for copying or moving a selected area).

[0204] FIG. 8b is a diagram illustrating the operation in which, when a user inputs a touch with the intent of a force touch, the processor (220) outputs a UI corresponding to the force touch in response to a touch type determination error.

[0205] Referring to FIG. 8b (a), a user may input a touch on a touchscreen with the intent of a force touch. A processor (220) may input touch data of the touch input by the user into a recognition model and determine the touch type as a long touch. A processor (220) may determine the touch type as a long touch based on the pressure of the touch input by the user.

[0206] Referring to FIG. 8b (b), the processor (220) can output a long touch UI (e.g., a copy or move selection window UI of a selected area) in response to determining that the touch type is a long touch.

[0207] Referring to FIG. 8b (c), the user may apply pressure to the touchscreen again without manipulating the long touch UI in response to the long touch UI being displayed instead of the intended force touch input. The processor (220) does not receive additional operation input from the user regarding the force touch UI, and the user applies pressure to the touchscreen again. to In response, it can be determined that there is an error in deciding the touch type to be a long touch.

[0208] Referring to FIG. 8b (d), the processor (220) may stop the long touch UI output in response to determining that there is an error in determining the touch type as a long touch. According to one embodiment, the processor (220) may control the display (160) so that the long touch UI disappears from the display (160) by gradually changing the alpha blending value of the long touch UI in response to determining that there is an error in determining the touch type as a long touch.

[0209] Referring to FIG. 8b (d), the processor (220) can correct the touch type of the user input to a force touch in response to an error in determining the touch type as a long touch. In response to correcting the touch type to a force touch, the processor (220) can output a force touch UI (e.g., a volume control window UI).

[0210] An electronic device according to various embodiments of the present invention includes a touch screen and a processor (220), and the processor (220) determines the type of user input entered on the touch screen as either a first touch type or a second touch type, and in response to determining the type of the input touch as the first touch type, outputs a UI (user interface) corresponding to the first touch type, and in response to determining that there is an error in determining the type of the input touch as the first touch type, modifies the determined type to the second touch type and outputs a UI corresponding to the second touch type.

[0211] In an electronic device according to various embodiments of the present invention, the first touch type and the second touch type may be a force touch, which is a type of user input input on the touch screen that contacts the touch screen with a specified pressure or a long touch, which is a type that contacts the touch screen for a specified time or longer.

[0212] In an electronic device according to various embodiments of the present invention, a memory (230) for storing a recognition model is further included, and the processor (220) can determine the type of the user input based on a value obtained by inputting image data corresponding to the user input into the recognition model.

[0213] In an electronic device according to various embodiments of the present invention, the processor (220) inputs the image data into the recognition model in response to user input being input on the touch screen for a specified time or longer, and can determine the type of the user input as a first touch type in response to the value obtained by inputting into the recognition model being greater than or equal to the specified value.

[0214] In an electronic device according to various embodiments of the present invention, the processor (220) may store image data of the user input in the memory (230) in response to determining that there is an error in determining the type of the user input as the first touch type, and may update the recognition model by learning the image data.

[0215] In an electronic device according to various embodiments of the present invention, the touch screen further includes a pressure sensor that detects the pressure of a touch, and the processor (220)

[0216] Acquiring the pressure of user input entered on the above touch screen, and

[0217] In response to the pressure value being greater than or equal to a specified value, the type of the user input can be determined as a first touch type.

[0218] In an electronic device according to various embodiments of the present invention, the processor (220)

[0219] In response to the failure to receive input for operation on the UI for a specified period after outputting the UI corresponding to the first touch type, it can be determined that there is an error in determining the type of user input as the first touch type.

[0220] In an electronic device according to various embodiments of the present invention, the processor (220) may determine that there is an error in determining the type of user input as the first touch type in response to additional user input being input to another area of ​​the touch screen after outputting a UI corresponding to the first touch type.

[0221] In an electronic device according to various embodiments of the present invention, the first touch type is a force touch and the second touch type is a long touch, and the processor (220) outputs a UI corresponding to the force touch in response to determining the type of the user input as a force touch, and in response to not receiving additional user input on the UI corresponding to the force touch for a specified time and the user input being terminated, determines that there is an error in determining the type of the user input as a force touch and outputs a UI corresponding to the long touch.

[0222] In an electronic device according to various embodiments of the present invention, the first touch type is a long touch and the second touch type is a force touch, and the processor (220) outputs a UI corresponding to the long touch in response to determining the type of the user input as a long touch, and does not receive additional user input on the UI corresponding to the long touch for a specified time, and in response to receiving additional user input corresponding to the force touch,

[0223] It is determined that there is an error in determining the type of the above user input as a long touch, and a UI corresponding to the above force touch can be output.

[0224] A method of operation of an electronic device according to various embodiments of the present invention may include: determining the type of user input entered on a touch screen as either a first touch type or a second touch type; outputting a UI (user experience) corresponding to the first touch type in response to determining the type of the input touch as the first touch type; modifying the determined type to the second touch type in response to determining that there is an error in determining the type of the input touch as the first touch type; and outputting a UI corresponding to the second touch type.

[0225] In a method of operation of an electronic device according to various embodiments of the present invention, the first touch type and the second touch type may be a force touch, which is a type of user input input on the touch screen that contacts the touch screen with a pressure greater than a specified amount, or a long touch, which is a type of contact that contacts the touch screen for a time greater than a specified amount.

[0226] In a method of operation of an electronic device according to various embodiments of the present invention, the method may include an operation of determining the type of the user input based on a value obtained by inputting image data corresponding to the user input into a recognition model.

[0227] In a method of operation of an electronic device according to various embodiments of the present invention, the method may include an operation of inputting image data into a recognition model in response to user input being input on the touch screen for a specified time or longer, and an operation of determining the type of user input as a first touch type in response to the value obtained by inputting into the recognition model being greater than or equal to a specified value.

[0228] In a method of operation of an electronic device according to various embodiments of the present invention, in response to determining that there is an error in determining the type of the user input as the first touch type, the method may include the operation of storing image data of the user input in memory (230) and the operation of learning the image data to update the recognition model.

[0229] In a method of operating an electronic device according to various embodiments of the present invention, the method may include acquiring pressure of a user input input on a touch screen and determining the type of the user input as a first touch type in response to the pressure value being greater than or equal to a specified value.

[0230] In a method of operation of an electronic device according to various embodiments of the present invention, in response to not receiving an operation for said UI for a specified period of time after outputting a UI corresponding to said first touch type, an operation of determining that there is an error in determining the type of the user input as said first touch type may be included.

[0231] In a method of operation of an electronic device according to various embodiments of the present invention, after outputting a UI corresponding to the first touch type, the method may include an operation of determining that there is an error in determining the type of the user input as the first touch type in response to additional user input being input in another area of ​​the touch screen.

[0232] In a method of operation of an electronic device according to various embodiments of the present invention, the first touch type is a force touch and the second touch type is a long touch, and in response to determining the type of the user input as a force touch, the method may include an operation of outputting a UI corresponding to the force touch and, in response to the user input ending after failing to receive additional user input on the UI corresponding to the force touch for a specified time, an operation of determining that there is an error in determining the type of the user input as a force touch and an operation of outputting a UI corresponding to the long touch.

[0233] In a method of operation of an electronic device according to various embodiments of the present invention, the first touch type is a long touch and the second touch type is a force touch, and in response to determining the type of the user input as a long touch, the method may include an operation of outputting a UI corresponding to the long touch; an operation of determining that there is an error in determining the type of the user input as a long touch in response to receiving additional user input corresponding to the force touch, and an operation of outputting a UI corresponding to the force touch.

[0234] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments.

[0235] In relation to the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of the noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise.

[0236] In this document, each of the phrases such as “A or B,” “at least one of A and B,” “or at least one of B,” “A, B or C,” “at least one of A, B and C,” and “B, or at least one of C” may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order). Where any (e.g., first) component is referred to as “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicationly,” it means that said component may be connected to said other component directly (e.g., wired), wirelessly, or through a third component.

[0237] Furthermore, the embodiments disclosed in this specification and drawings are merely specific examples presented to facilitate the explanation of the technical content according to the embodiments disclosed in this document and to aid in understanding the embodiments disclosed in this document, and are not intended to limit the scope of the embodiments disclosed in this document. Accordingly, the scope of the various embodiments disclosed in this document should be interpreted to include all modifications or variations derived based on the technical concept of the various embodiments disclosed in this document, in addition to the embodiments disclosed herein.

Claims

Claim 1 An electronic device comprising: a touch screen; a memory having one or more storage media and storing instructions; and at least one processor having a processing circuit, wherein when the instructions are executed individually or collectively by the at least one processor, the electronic device causes: to determine the type of user input entered on the touch screen as either a first touch type or a second touch type; in response to determining the type of the entered touch as the first touch type, output a UI (user interface) corresponding to the first touch type; and in response to additional user input being entered in another area of ​​the touch screen after outputting the UI corresponding to the first touch type, determine that there is an error in determining the type of the user input as the first touch type, modify the type of the user input to the second touch type, and output a UI corresponding to the second touch type. Claim 2 In claim 1, the electronic device wherein the first touch type and the second touch type are a type of user input entered on the touch screen that is a force touch, which is a type of contacting the touch screen with a pressure greater than a specified amount, or a long touch, which is a type of contacting the touch screen for a time greater than a specified amount. Claim 3 An electronic device according to claim 1, wherein, when the instructions are executed individually or collectively by the at least one processor, the electronic device causes the electronic device to determine the type of the user input based on a value obtained by inputting image data corresponding to the user input into a recognition model stored in the memory. Claim 4 In claim 3, the electronic device, when the instructions are executed individually or collectively by the at least one processor, causes the electronic device to: input the image data into the recognition model in response to user input being input on the touch screen for a specified time or longer, and determine the type of the user input as a first touch type in response to the value obtained by inputting into the recognition model being greater than or equal to a specified value. Claim 5 In claim 4, when the instructions are executed individually or collectively by the at least one processor, the electronic device: stores image data of the user input in the memory and learns the image data to update the recognition model in response to determining that there is an error in determining the type of the user input as the first touch type. Claim 6 In claim 1, the touch screen further comprises a pressure sensor for detecting pressure of a touch, and when the instructions are executed individually or collectively by the at least one processor, the electronic device causes: to acquire the pressure of a user input entered on the touch screen, and to determine the type of the user input as a first touch type in correspondence with the pressure value of the acquired pressure being greater than or equal to a specified value. Claim 7 An electronic device according to claim 1, wherein when the instructions are executed individually or collectively by the at least one processor, the electronic device determines that there is an error in determining the type of user input as the first touch type in response to not receiving an operation on the UI for a specified time after outputting the UI corresponding to the first touch type. Claim 8 delete Claim 9 In claim 2, the first touch type is a force touch and the second touch type is a long touch, and when the instructions are executed individually or collectively by the at least one processor, the electronic device causes: in response to determining the type of the user input as a force touch, to output a UI corresponding to the force touch; and in response to failing to receive additional user input on the UI corresponding to the force touch for a specified time and the user input ending, to determine that there is an error in determining the type of the user input as a force touch and to output a UI corresponding to the long touch. Claim 10 delete Claim 11 A method of operating an electronic device comprising: an operation of determining the type of user input entered on a touch screen as either a first touch type or a second touch type; an operation of outputting a UI (user experience) corresponding to the first touch type in response to determining the type of the entered touch as the first touch type; an operation of determining that there is an error in determining the type of the user input as the first touch type in response to additional user input being entered in another area of ​​the touch screen after outputting the UI corresponding to the first touch type; an operation of modifying the type of the user input to the second touch type; and an operation of outputting a UI corresponding to the second touch type. Claim 12 delete Claim 13 delete Claim 14 delete Claim 15 delete Claim 16 delete Claim 17 delete Claim 18 delete Claim 19 delete Claim 20 delete

Images