KR20230028081A - Electronic device for detecting execution error of application and method for operating thereof - Google Patents

Abstract

According to various embodiments, an electronic device includes a processor. The processor is configured to analyze an application to be diagnosed and extract diagnosis-related information about the application to be diagnosed; determine whether a specific diagnosis item corresponding to first specific information included in the diagnosis-related information and version information of an operating system for executing the application to be diagnosed exists in a diagnosis item list, wherein the first specific information includes at least one of application programming interface (API) information or engine information used by the application to be diagnosed; identify information to be diagnosed specified by the specific diagnosis item from the diagnosis item list, based on the specific diagnosis item existing in the diagnosis item list; and provide a guide to the information to be diagnosed based on the information to be diagnosed being not identified from the diagnosis-related information. Other embodiments may also be possible. Accordingly, application execution errors can be easily detected before distributing an application to users.

Description

Electronic device for detecting an execution error of an application and method for operating the same

Various embodiments relate to a method and apparatus for detecting an execution error of an application.

API (application programming interface) means an interface that allows applications to use functions provided by the operating system, and applications are specific APIs in a specific version of the OS (eg, Android R version). To use (eg getDataNetworkType()), a specific permission (eg READ_PHONE_STATE) must be obtained. In addition, in order for an application program using a specific engine to run on a specific version of the OS, the version of the specific engine must be at least a certain version.

When an application wants to use a specific API in a specific version of the OS, an execution error may occur in the application if it does not have the authority related to the specific API. When the first API used in the previous version of the OS is replaced with the second API in the next version of the OS according to the version upgrade of the OS, if the application still uses the first API, an execution error may occur in the application. When an application wants to use a specific engine in a specific version of the OS, an execution error may occur in the application if the version of the specific engine is below a certain version.

Various embodiments may provide an electronic device that extracts application-related information from the application, compares the extracted information with a list of diagnostic items, detects an error in the application, and provides a guide for the detected error.

According to various embodiments, an electronic device may include a processor, wherein the processor analyzes an application to be diagnosed, extracts diagnosis-related information about the application to be diagnosed, and includes a first specific information included in the diagnosis-related information. determining whether a specific diagnosis item corresponding to information and version information of an operating system for executing the diagnosis target application exists in the diagnosis item list, and the first specific information is used by the diagnosis target application Includes at least one of API (application programming interface) information or engine information-, diagnosis target information specified by the specific diagnosis item from the diagnosis item list based on the existence of the specific diagnosis item in the diagnosis item list may be identified, and based on the fact that the diagnosis target information is not identified from the diagnosis related information, a guide for the diagnosis target information may be provided.

According to various embodiments, an operating method of an electronic device may include an operation of analyzing a diagnosis target application and extracting diagnosis-related information about the diagnosis-target application, first specific information included in the diagnosis-related information, and the diagnosis target An operation of determining whether a specific diagnostic item corresponding to version information of an operating system for executing an application exists in the diagnostic item list - the first specific information is an application programming API (API) used by the application to be diagnosed interface) information or engine information, an operation of identifying diagnosis target information specified by the specific diagnosis item from the diagnosis item list based on the presence of the specific diagnosis item in the diagnosis item list. , and an operation of providing a guide for the diagnosis target information based on the fact that the diagnosis target information is not identified from the diagnosis related information.

When an application wants to use a specific API in a specific version of the OS, an execution error may occur in the application if it does not have the authority related to the specific API. When the first API used in the previous version of the OS is replaced with the second API in the next version of the OS according to the version upgrade of the OS, if the application still uses the first API, an execution error may occur in the application. When an application wants to use a specific engine in a specific version of the OS, an execution error may occur in the application if the version of the specific engine is below a certain version.

According to various embodiments, in order to run an application in a specific version of the OS, the electronic device determines whether (1) the application has permission to use a specific API, (2) whether the application is using a replaced API, (3) Execution errors of the application can be easily detected before distributing the application to users by using a diagnosis item list for determining whether a version for using a specific engine is installed in the application.

1 is a block diagram of an electronic device in a network environment, according to various embodiments.
2 is a flowchart illustrating an operation of diagnosing an application to be diagnosed by an electronic device according to various embodiments.
3 is a sequence diagram for explaining an operation of diagnosing an application to be diagnosed by an electronic device according to various embodiments.
4 is a diagram illustrating a format of a diagnostic item, according to various embodiments.
5 is a diagram illustrating a diagnosis item list according to various embodiments.

1 is a block diagram of an electronic device in a network environment according to various embodiments of the present disclosure.

Referring to FIG. 1 , in a network environment 100, an electronic device 101 communicates with an electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or through a second network 199. It is possible to communicate with the electronic device 104 or the server 108 through (eg, a long-distance wireless communication network). According to one embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108 . According to an embodiment, the electronic device 101 includes a processor 120, a memory 130, an input module 150, an audio output module 155, a display module 160, an audio module 170, a 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 the antenna module 197 may be included. In some embodiments, in the electronic device 101, at least one of these components (eg, the connection terminal 178) may be omitted or one or more other components may be added. In some embodiments, some of these components (eg, sensor module 176, camera module 180, or antenna module 197) are integrated into a single component (eg, display module 160). It can be.

The processor 120, for example, executes software (eg, the program 140) to cause at least one other component (eg, hardware or software component) of the electronic device 101 connected to the processor 120. It can control and perform various data processing or calculations. According to one embodiment, as at least part of data processing or operation, processor 120 transfers instructions or data received from other components (e.g., sensor module 176 or communication module 190) to volatile memory 132. , processing commands or data stored in the volatile memory 132 , and storing resultant data in the non-volatile memory 134 . According to an embodiment, the processor 120 may include a main processor 121 (eg, a central processing unit or an application processor), or a secondary processor 123 (eg, a graphic processing unit, a neural network processing unit) that may operate independently of or together with the main processor 121 . (NPU: neural processing unit), image signal processor, sensor hub processor, or communication processor). For example, when the electronic device 101 includes the main processor 121 and the auxiliary processor 123, the auxiliary processor 123 uses less power than the main processor 121 or is set to be specialized for a designated function. It can be. The secondary processor 123 may be implemented separately from or as part of the main processor 121 .

The secondary processor 123 may, for example, take the place of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or the main processor 121 is active (eg, running an application). ) state, together with the main processor 121, at least one of the components of the electronic device 101 (eg, the display module 160, the sensor module 176, or the communication module 190) It is possible to control at least some of the related functions or states. According to one embodiment, the auxiliary processor 123 (eg, image signal processor or communication processor) may be implemented as part of other functionally related components (eg, camera module 180 or communication module 190). there is. According to an embodiment, the auxiliary processor 123 (eg, a neural network processing device) may include a hardware structure specialized for processing an artificial intelligence model. AI models can be created through machine learning. Such learning may be performed, for example, in the electronic device 101 itself where artificial intelligence is performed, or may be performed through a separate server (eg, the server 108). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning or reinforcement learning, but in the above example Not limited. The artificial intelligence model may include a plurality of artificial neural network layers. Artificial neural networks include deep neural networks (DNNs), convolutional neural networks (CNNs), recurrent neural networks (RNNs), restricted boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), It may be one of deep Q-networks or a combination of two or more of the foregoing, but is not limited to the foregoing examples. The artificial intelligence model may include, in addition or alternatively, software structures in addition to hardware structures.

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

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

The input module 150 may receive a command or data to be used by a component (eg, the processor 120) of the electronic device 101 from the outside of the electronic device 101 (eg, a user). The input module 150 may include, for example, a microphone, a mouse, a keyboard, a key (eg, a button), or a digital pen (eg, a stylus pen).

The sound output module 155 may output sound signals to the outside of the electronic device 101 . The sound output module 155 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as multimedia playback or recording playback. A receiver may be used to receive an incoming call. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 160 may visually provide information to the outside of the electronic device 101 (eg, a user). The display module 160 may include, for example, a display, a hologram device, or a projector and a control circuit for controlling the device. According to an 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 force generated by the touch.

The audio module 170 may convert sound into an electrical signal or vice versa. According to an embodiment, the audio module 170 acquires sound through the input module 150, the sound output module 155, or an external electronic device connected directly or wirelessly to the electronic device 101 (eg: Sound may be output through the electronic device 102 (eg, a speaker or a headphone).

The sensor module 176 detects an operating state (eg, power or temperature) of the electronic device 101 or an external environmental state (eg, a user state), and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a bio sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 177 may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device 101 to an external electronic device (eg, the 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.

The connection terminal 178 may include a connector through which the electronic device 101 may be physically connected to an external electronic device (eg, the 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 (eg, a headphone connector).

The haptic module 179 may convert electrical signals into mechanical stimuli (eg, vibration or motion) or electrical stimuli that a user may 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 electrical stimulation device.

The camera module 180 may capture still images and moving images. According to one embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

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

The battery 189 may 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 cell, a rechargeable secondary cell, or a fuel cell.

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

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

The antenna module 197 may transmit or receive signals or power to the outside (eg, an external electronic device). According to an embodiment, the antenna module may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (eg, PCB). According to one embodiment, the antenna module 197 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 198 or the second network 199 is selected from the plurality of antennas by the communication module 190, for example. can be chosen 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, other components (eg, a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module 197 in addition to the radiator.

According to various embodiments, the antenna module 197 may form a mmWave antenna module. According to one embodiment, the mmWave antenna module includes a printed circuit board, an RFIC disposed on or adjacent to a first surface (eg, a lower surface) of the printed circuit board and capable of supporting a designated high frequency band (eg, mmWave band); and a plurality of antennas (eg, array antennas) disposed on or adjacent to a second surface (eg, a top surface or a side surface) of the printed circuit board and capable of transmitting or receiving signals of the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal ( e.g. commands or data) can be exchanged with each other.

According to an embodiment, commands or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199 . Each of the external electronic devices 102 or 104 may be the same as or different from the electronic device 101 . According to an embodiment, all or part of operations executed in the electronic device 101 may be executed in one or more external devices among the external electronic devices 102 , 104 , and 108 . For example, when the electronic device 101 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 101 instead of executing the function or service by itself. Alternatively or additionally, one or more external electronic devices may be requested to perform the function or at least part of the service. One or more external electronic devices receiving the request may execute at least a part of the requested function or service or an additional function or service related to the request, and deliver the execution result to the electronic device 101 . The electronic device 101 may provide the result as at least part of a response to the request as it is or additionally processed. To this end, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device 101 may provide an ultra-low latency service 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. Server 108 may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device 104 or server 108 may be included in the second network 199 . The electronic device 101 may be applied to intelligent services (eg, smart home, smart city, smart car, or health care) based on 5G communication technology and IoT-related technology.

FIG. 2 is a flowchart illustrating an operation of diagnosing an application to be diagnosed by an electronic device (eg, the electronic device 101 of FIG. 1 ) according to various embodiments.

3 is a sequence diagram for explaining an operation of diagnosing an application to be diagnosed by the electronic device 101 according to various embodiments.

4 is a diagram illustrating a format of a diagnostic item, according to various embodiments.

5 is a diagram illustrating a diagnosis item list according to various embodiments.

In operation 201, according to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1) may store a diagnostic item list in a memory (eg, the memory 130 of FIG. 1). According to an embodiment, the electronic device 101 may obtain information about diagnostic items written according to a format determined by the electronic device 101, and generate a diagnostic item list using the information about the diagnostic items. can do. For example, referring to FIG. 3 , the electronic device 101 may generate a diagnosis item list using information about diagnosis items obtained from a manager and store the diagnosis item list in the memory 130 (301). . According to an embodiment, each diagnostic item of the diagnostic item list includes at least one of an operating system (OS) version, a first diagnostic element, a second diagnostic element, a diagnostic test failure condition, or a guide. may be included, and the format of the diagnosis item may be determined according to a predetermined type. For example, referring to FIG. 4 , each diagnostic item includes an OS version 420, a first diagnostic element 430, a second diagnostic element 440, a diagnostic test failure condition 450, or a guide 460. It may include at least one of the following, and the format of each diagnostic item may be determined according to the type 410 of the diagnostic item. According to an embodiment, the first diagnosis element 430 may correspond to one of application programming interface (API) information or engine information, and the second diagnosis element 440 may correspond to permission information and API information. , or engine version information, the failure condition 450 may indicate a case in which the second diagnostic element 440 is not detected, and the guide 460 indicates the use of the second diagnostic element. may contain relevant information. For example, referring to FIG. 4 , a diagnosis item may be classified as one of a first type 411, a second type 412, or a third type 413, and may be written in a format corresponding to each type. can

According to an embodiment, the electronic device 101 may obtain API information usable in the version of the OS and authorization information required to use the API information from a server of an OS manufacturer by using web crawling. A diagnostic item corresponding to the first type 411 may be created using the version information of the OS, the API information, and the authority information, and the generated diagnostic item may be added to a list of diagnostic items. According to an embodiment, the electronic device 101 uses web crawling to provide first API information used in the previous version of the OS and second API information available in the current version of the OS from the server of the OS manufacturer. may be obtained, a diagnosis item corresponding to the second type 412 is created using the version information of the OS, the first API information, and the second API information, and the generated diagnosis item is included in the list of diagnosis items. can be added to According to an embodiment, the electronic device 101 analyzes other applications before performing a diagnostic test on the application to be diagnosed, and as a result, engine information and engine version information used in the version of the OS for executing the other applications. may be obtained, a diagnosis item corresponding to the third type 413 is created using the version information of the OS, the engine information, and the engine version information, and the created diagnosis item is added to a list of diagnosis items. can

In operation 203, according to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1) detects a defect in the application to be diagnosed from an external electronic device (eg, the server 108 of FIG. 1). You may receive a request to do so. For example, referring to FIG. 3 , the electronic device 101 may receive (303) a request for detecting a defect in an application to be diagnosed from an external electronic device 108 (eg, a development server for a diagnosis-related application). there is. According to an embodiment, the request may include version information of an OS for executing a diagnosis target application.

In operation 205, according to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1 ) may analyze the diagnosis target application and extract diagnosis-related information about the diagnosis target application. For example, referring to FIG. 3 , the electronic device 101 may extract (305) diagnosis-related information about a diagnosis target application. According to an embodiment, the diagnosis-related information may include first specific information and second specific information. According to an embodiment, the electronic device 101 may extract, as the first specific information, API information used in a diagnosis target application from a source code of a diagnosis target application or an API list of a diagnosis target application. According to an embodiment, the electronic device 101 determines the application to be diagnosed from information (eg, logo information) of the application to be diagnosed displayed on a display (eg, the display module 160 of FIG. 1 ) when the application to be diagnosed is executed. Engine information used in may be extracted as the first specific information. According to an embodiment, the electronic device 101 may extract, as the second specific information, permission information acquired by the application to be diagnosed from the source code of the application to be diagnosed or a permission list of the application to be diagnosed. According to an embodiment, the electronic device 101 converts version information of an engine used in the application to be diagnosed from information on the application to be diagnosed displayed on the display 160 when the application to be diagnosed is executed, to the second specific application. information can be extracted. For example, referring to [Table 1] below, the electronic device 101 may extract first specific information and second specific information as diagnosis related information for a diagnosis target application.

Diagnosis related information First specific information Second specific information API information engine information Authorization information engine version information getDataNetworkType()
getSerial()
getMeid()
... Unity
... A
B
C
D
... E
F
G
...

According to an embodiment, the electronic device 101 acquires the source code, API list, and/or permission list of the application to be diagnosed from the external electronic device 101 or directly analyzes the application to be diagnosed, and obtains the API list and/or An authority list may be acquired. In operation 207, according to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1 ) determines the first specific information included in the diagnosis-related information and the diagnosis target application. It is possible to determine whether a specific diagnostic item corresponding to the version information of the OS for executing is present in the diagnostic item list. For example, referring to FIG. 3 , the electronic device 101 may determine whether a diagnosis target application is a diagnostic test target based on diagnosis related information and OS version information (307).

According to an embodiment, the electronic device 101 may determine whether a specific diagnosis item including specific OS version information for executing a diagnosis target application and specific API information used in the diagnosis target application exists in the diagnosis item list. . For example, referring to FIG. 5 , when a diagnosis target application (eg, first application) operates in a specific OS version (eg, R OS) and specific API information (eg, getDataNetworkType) is used in the diagnosis target application. , The electronic device 101 may determine whether a specific diagnostic item including the specific OS version and the specific API information exists in the diagnostic item list 500, and the specific diagnostic item in the diagnostic item list 500 ( Example: When the first item 501) is present, it may be determined that the diagnosis target application is a diagnostic test target. The same operation may be performed for the fourth item 504 and the fifth item 505 of the same type as the first item 501 . As another example, referring to FIG. 5 , a diagnosis target application (eg, a second application) operates in a specific OS version (eg, R OS), and specific API information (eg, getNetworkType) is used in the diagnosis target application. In this case, the electronic device 101 may determine whether a specific diagnostic item including the specific OS version and the specific API information exists in the diagnostic item list 500, and the specific diagnostic item in the diagnostic item list 500. If an item (eg, the second item 502) exists, it may be determined that the diagnosis target application is a diagnostic test target.

According to an embodiment, the electronic device 101 may determine whether a specific diagnosis item including specific OS version information for executing a diagnosis target application and specific engine information used in the diagnosis target application exists in the diagnosis item list. . For example, referring to FIG. 5 , a diagnosis target application (eg, a third application) operates in a specific OS version (eg, R OS), and specific engine information (eg, Unity engine) is used in the diagnosis target application. In this case, the electronic device 101 may determine whether a specific diagnostic item including the specific OS version and the specific engine information exists in the diagnostic item list 500, and the specific diagnostic item in the diagnostic item list 500. If (eg, the third item 503) exists, it may be determined that the diagnosis target application is a diagnostic test target.

In operation 209, according to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1 ) selects the diagnosis item list 500 based on the presence of a specific diagnosis item in the diagnosis item list 500. ), diagnosis target information specified by a specific diagnosis item can be identified.

According to an embodiment, when identifying a specific diagnostic item corresponding to a specific OS version and specific API information from the diagnostic item list 500, the electronic device 101 identifies authority information specified by the specific diagnostic item. can For example, referring to FIG. 5 , the electronic device 101 provides a first item 501 corresponding to a specific OS version (eg, R OS) and specific API information (eg, getDataNetworkType) from the diagnosis item list 500. In the case of identifying , permission information (eg, READ_PHONE_STATE) specified by the first item 501 may be identified.

According to an embodiment, when the electronic device 101 identifies a specific diagnostic item corresponding to a specific OS version and first specific API information from the diagnostic item list 500, the second specific diagnostic item specified by the specific diagnostic item API information can be identified. For example, referring to FIG. 5 , the electronic device 101 provides a second item 502 corresponding to a specific OS version (eg, R OS) and specific API information (eg, getNetworkType) from the diagnosis item list 500. In the case of identifying , the second specific API information (eg, getDataNetworkType) specified by the second item 502 may be identified.

According to an embodiment, when identifying a specific diagnostic item corresponding to a specific OS version and specific engine information from the diagnostic item list 500, the electronic device 101 identifies engine version information specified by the specific diagnostic item. can do. For example, referring to FIG. 5 , the electronic device 101 includes a third item 503 corresponding to a specific OS version (eg, R OS) and specific engine information (eg, Unity engine) from the diagnosis item list 500. ), engine version information (eg, 2018.4.30f1, 2019.4.15f1, 2020.1.14f1, 2020.2.0b12) specified by the third item 503 can be identified.

In operation 211, according to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1 ) may determine whether the diagnosis target information is identified from the second specific information included in the diagnosis related information. . For example, referring to FIG. 3 , the electronic device 101 may perform a diagnostic test on an application to be diagnosed using information to be diagnosed (309). According to an embodiment, when authority information specified by a specific diagnosis item is not identified from diagnosis-related information, the electronic device 101 may determine that the diagnosis test for the application to be diagnosed has not passed.

According to an embodiment, the electronic device 101 may determine whether authority information specified by a specific diagnosis item exists in second specific information (eg, authority information) included in diagnosis-related information. For example, referring to FIG. 5 , the electronic device 101 may determine whether permission information (eg, READ_PHONE_STATE) specified by the first item 501 exists in the permission list included in the diagnosis-related information, If authority information (eg, READ_PHONE_STATE) does not exist in the authority list according to the failure condition in the first item 501, it may be determined that the diagnostic test for the application to be diagnosed has not passed.

According to an embodiment, the electronic device 101 may determine whether the second specific API information specified by the specific diagnosis item exists in the first specific information (eg, API information) included in the diagnosis related information. For example, referring to FIG. 5 , the electronic device 101 determines whether the second specific API information (eg, getDataNetworkType) specified by the second item 502 exists in the API list included in the diagnosis-related information. If the second specific API information (eg, getDataNetworkType) does not exist in the API list according to the failure condition in the second item 502, it may be determined that the diagnostic test for the application to be diagnosed has not passed. .

According to an embodiment, the electronic device 101 may determine whether engine version information specified by a specific diagnosis item exists in second specific information (eg, engine version information) included in diagnosis-related information. For example, referring to FIG. 5 , the electronic device 101 determines whether the engine version information (eg, 2020.2.0b12) specified by the third item 503 exists in the engine version list included in the diagnosis-related information. and if the engine version information (eg, 2020.2.0b12) does not exist in the engine version list according to the failure condition in the third item 503, it is determined that the diagnostic test for the application to be diagnosed has not passed. can

According to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1 ) determines that the diagnostic test for the application to be diagnosed has passed, based on the diagnosis target information being identified from the diagnosis related information. and transmits feedback regarding the fact that the diagnostic test has passed to the external electronic device 108 requesting the diagnostic test of the application to be diagnosed.

In operation 213, according to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1 ) provides a guide for diagnosis target information based on the fact that the diagnosis target information is not identified from the diagnosis related information. can provide For example, referring to FIG. 3 , the electronic device 101 may provide a diagnostic test result (eg, a guide for diagnosis target information) to the external electronic device 108 ( 311 ).

According to an embodiment, the electronic device 101, when the authority information specified by the specific diagnosis item does not exist in the second specific information (eg, authority information) included in the diagnosis-related information, is defined in the specific diagnosis item. Guidance on authority information can be provided. For example, referring to FIG. 5 , the electronic device 101, when the authority information specified by the first item 501 (eg, READ_PHONE_STATE) does not exist in the authority list included in the diagnosis-related information, first A guide for the authority information defined in item 501 may be provided.

According to an embodiment, the electronic device 101, when the second specific API information specified by the specific diagnostic item does not exist in the first specific information (eg, API information) included in the diagnosis-related information, the specific diagnostic item A guide for the second specific API information defined in may be provided. For example, referring to FIG. 5 , when the electronic device 101 does not exist in the API list included in the diagnosis-related information, the second specific API information (eg, getDataNetworkType) specified by the second item 502 is not present. , a guide for the second specific API information defined in the second item 502 may be provided.

According to an embodiment, when the engine version information specified by the specific diagnosis item does not exist in the second specific information (eg, engine version information) included in the diagnosis-related information, the electronic device 101 determines the specific diagnosis item. A guide for the defined engine version information can be provided. For example, referring to FIG. 5 , the electronic device 101 determines that the engine version information (eg, 2020.2.0b12) specified by the third item 503 does not exist in the engine version list included in the diagnosis-related information. In this case, a guide for the engine version information defined in the third item 503 may be provided.

According to various embodiments, the electronic device 101 (eg, the processor 120 of FIG. 1 ), based on acquiring additional diagnostic items for a diagnosis target application, lists the obtained additional diagnostic items in the diagnostic item list 500. ), the diagnosis item list 500 can be updated. For example, referring to FIG. 3 , the electronic device 101 may update (313) the diagnosis item list 500 to include additional diagnosis items. According to an embodiment, the electronic device 101 may determine whether the additional diagnosis item includes first specific information included in diagnosis-related information in operation 207 and OS version information for executing a diagnosis target application, When the additional diagnostic items include the first specific information and the OS version information, operations 209 to 213 may be performed using the additional diagnostic items. At this time, the electronic device 101 provides the guide defined in the additional diagnosis item to the external electronic device 108 when diagnosis target information specified by the additional diagnosis item is identified from the second specific information included in the diagnosis-related information. can do. According to an embodiment, the electronic device 101 may provide a guide to the external electronic device 108 through an open service for diagnosing an arbitrary application.

Electronic devices according to various embodiments disclosed in this document may be devices of various types. The electronic device may include, for example, a portable communication device (eg, a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. An electronic device according to an embodiment of the present document is not limited to the aforementioned devices.

Various embodiments of this document and terms used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, like reference numbers may be used for like or related elements. The singular form of a noun corresponding to an item may include one item or a plurality of items, unless the relevant context clearly dictates otherwise. In this document, "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "A Each of the phrases such as "at least one of , B, or C" may include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first", "second", or "first" or "secondary" may simply be used to distinguish a given component from other corresponding components, and may be used to refer to a given component in another aspect (eg, importance or order) is not limited. A (e.g., first) component is said to be "coupled" or "connected" to another (e.g., second) component, with or without the terms "functionally" or "communicatively." When mentioned, it means that the certain component may be connected to the other component directly (eg by wire), wirelessly, or through a third component.

The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as, for example, logic, logical blocks, parts, or circuits. can be used as A module may be an integrally constructed component or a minimal unit of components or a portion thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of this document provide one or more instructions stored in a storage medium (eg, internal memory 136 or external memory 138) readable by a machine (eg, electronic device 101). It may be implemented as software (eg, the program 140) including them. For example, a processor (eg, the processor 120 ) of a device (eg, the electronic device 101 ) may call at least one command among one or more instructions stored from a storage medium and execute it. This enables the device to be operated to perform at least one function according to the at least one command invoked. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' only means that the storage medium is a tangible device and does not contain a signal (e.g. electromagnetic wave), and this term refers to the case where data is stored semi-permanently in the storage medium. It does not discriminate when it is temporarily stored.

According to one embodiment, the method according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. A computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or through an application store (eg Play Store ^TM ) or on two user devices ( It can be distributed (eg downloaded or uploaded) online, directly between smart phones. In the case of online distribution, at least part of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium such as a manufacturer's server, an application store server, or a relay server's memory.

According to various embodiments, each component (eg, module or program) of the above-described components may include a single object or a plurality of entities, and some of the plurality of entities may be separately disposed in other components. there is. According to various embodiments, one or more components or operations among the aforementioned corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by a corresponding component of the plurality of components prior to the integration. . According to various embodiments, the actions performed by a module, program, or other component are executed sequentially, in parallel, iteratively, or heuristically, or one or more of the actions are executed in a different order, or omitted. or one or more other actions may be added.

According to various embodiments, an electronic device (eg, the electronic device 101 of FIG. 1 ) includes a processor (eg, the processor 120 of FIG. 1 ), and the processor analyzes an application to be diagnosed, Diagnosis-related information about the application to be diagnosed is extracted, and a specific diagnosis item corresponding to first specific information included in the diagnosis-related information and version information of an operating system for executing the application to be diagnosed is provided. It is determined whether or not it exists in the diagnosis item list (eg, the diagnosis item list 500 of FIG. 5), and the first specific information includes at least one of application programming interface (API) information or engine information used by the application to be diagnosed. Including-, based on the fact that the specific diagnosis item exists in the diagnosis item list, diagnosis target information specified by the specific diagnosis item is identified from the diagnosis item list, and the diagnosis target information is the diagnosis related information Based on what is not identified from, it may be set to provide a guide for the diagnosis target information.

According to various embodiments, each diagnostic item of the diagnostic item list includes at least one of an OS version, a first diagnostic element, a second diagnostic element, a diagnostic test failure condition, and a guide, and the first diagnostic element corresponds to one of application programming interface (API) information or engine information, the second diagnostic element corresponds to one of permission information, API information, or engine version information, and The diagnostic test failure condition indicates a case in which the second diagnostic component is not detected, and the guide may include information related to use of the second diagnostic component.

According to various embodiments, the processor may be configured to extract authority information acquired by the diagnosis target application as second specific information of the diagnosis related information as a result of analyzing the diagnosis target application.

According to various embodiments, the processor may, when the specific diagnostic item including the OS version information and the API information exists in the diagnostic item list, permission information specified by the specific diagnostic item. It can be set to identify.

According to various embodiments, the processor, when the authority information specified by the specific diagnosis item does not exist in the authority information extracted as the second specific information of the diagnosis-related information, in the specific diagnosis item It can be set to provide a guide for the defined authority information.

According to various embodiments, the processor identifies other API information specified by the specific diagnostic item when the specific diagnostic item including version information of the OS and the API information exists in the diagnostic item list. can be set to

According to various embodiments, the processor may, when the other API information specified by the specific diagnosis item does not exist in the API information included in the first specific information of the diagnosis-related information, the specific diagnostic item It can be set to provide a guide for the other API information defined in

According to various embodiments, the processor may be configured to extract engine version information used in the diagnosis target application as second specific information of the diagnosis related information as a result of analyzing the diagnosis target application.

According to various embodiments, the processor identifies the engine version information specified by the specific diagnosis item, when the specific diagnosis item including version information of the OS and the engine information exists in the diagnosis item list. can be set to

According to various embodiments, the processor may, when the engine version information specified by the specific diagnosis item does not exist in the engine version information extracted as the second specific information of the diagnosis-related information, the specific diagnosis It can be set to provide a guide for the engine version information defined in the item.

According to various embodiments, an operating method of an electronic device may include an operation of analyzing a diagnosis target application and extracting diagnosis-related information about the diagnosis-target application, first specific information included in the diagnosis-related information, and the diagnosis target An operation of determining whether a specific diagnostic item corresponding to version information of an operating system for executing an application exists in the diagnostic item list - the first specific information is an application programming API (API) used by the application to be diagnosed interface) information or engine information, an operation of identifying diagnosis target information specified by the specific diagnosis item from the diagnosis item list based on the presence of the specific diagnosis item in the diagnosis item list. , and an operation of providing a guide for the diagnosis target information based on the fact that the diagnosis target information is not identified from the diagnosis related information.

According to various embodiments, the operation of extracting the diagnosis-related information may include an operation of extracting authority information acquired by the diagnosis-target application as second specific information of the diagnosis-related information as a result of analyzing the diagnosis-target application. can include

According to various embodiments, the operation of identifying the diagnosis target information specified by the specific diagnosis item may be performed when the specific diagnosis item including version information of the OS and the API information exists in the diagnosis item list. , It may include an operation of identifying permission information specified by the specific diagnosis item.

According to various embodiments, in the operation of providing a guide for the diagnosis target information, the authority information specified by the specific diagnosis item is present in the authority information extracted as the second specific information of the diagnosis-related information. If not, an operation of providing a guide for the authority information defined in the specific diagnosis item may be included.

According to various embodiments, the operation of identifying the diagnosis target information specified by the specific diagnosis item may be performed when the specific diagnosis item including version information of the OS and the API information exists in the diagnosis item list. , It may include an operation of identifying other API information specified by the specific diagnosis item.

According to various embodiments, the operation of providing a guide for the diagnosis target information may include the API information included in the first specific information of the diagnosis related information, in which the other API information specified by the specific diagnosis item If it does not exist, an operation of providing a guide for the other API information defined in the specific diagnosis item may be included.

According to various embodiments, the operation of extracting the diagnosis-related information may include extracting engine version information used in the diagnosis-target application as second specific information of the diagnosis-related information as a result of analyzing the diagnosis-target application. can include

According to various embodiments, the operation of identifying the diagnosis target information specified by the specific diagnosis item may be performed when the specific diagnosis item including version information of the OS and the engine information exists in the diagnosis item list. , an operation of identifying engine version information specified by the specific diagnosis item.

According to various embodiments, the operation of providing a guide for the diagnosis target information may include the engine version information in which the engine version information specified by the specific diagnosis item is extracted as the second specific information of the diagnosis related information. If it does not exist in , an operation of providing a guide for the engine version information defined in the specific diagnosis item may be included.

Claims (20)

In electronic devices,
contains a processor;
the processor,
Analyzing a diagnosis target application and extracting diagnosis-related information about the diagnosis target application;
determining whether a specific diagnosis item corresponding to the first specific information included in the diagnosis-related information and version information of an operating system (OS) for executing the diagnosis target application exists in the diagnosis item list; 1 specific information includes at least one of application programming interface (API) information or engine information used by the application to be diagnosed;
Based on the fact that the specific diagnostic item exists in the diagnosis item list, diagnosis target information specified by the specific diagnostic item is identified from the diagnosis item list, and
The electronic device configured to provide a guide for the diagnosis target information based on the fact that the diagnosis target information is not identified from the diagnosis related information.
According to claim 1,
Each diagnosis item in the diagnosis item list,
at least one of a version of the OS, a first diagnostic component, a second diagnostic component, a diagnostic test failure condition, or a guide;
The first diagnostic element corresponds to one of application programming interface (API) information and engine information;
The second diagnostic element corresponds to one of permission information, API information, or engine version information,
The diagnostic test failure condition indicates a case in which the second diagnostic component is not detected,
The electronic device of claim 1 , wherein the guide includes information related to use of the second diagnostic element.
According to claim 1,
the processor,
As a result of analyzing the diagnosis target application, the electronic device is configured to extract authority information acquired by the diagnosis target application as second specific information of the diagnosis related information.
According to claim 3,
the processor,
The electronic device, configured to identify permission information specified by the specific diagnostic item when the specific diagnostic item including version information of the OS and the API information exists in the diagnostic item list.
According to claim 4,
the processor,
When the authority information specified by the specific diagnosis item does not exist in the authority information extracted as the second specific information of the diagnosis-related information, to provide a guide to the authority information defined in the specific diagnosis item. Set, electronic device.
According to claim 1,
the processor,
The electronic device, configured to identify other API information specified by the specific diagnosis item when the specific diagnosis item including version information of the OS and the API information exists in the diagnosis item list.
According to claim 6,
the processor,
If the other API information specified by the specific diagnosis item does not exist in the API information included in the first specific information of the diagnosis-related information, a guide for the other API information defined in the specific diagnosis item is provided. An electronic device, set up to provide.
According to claim 1,
the processor,
The electronic device is set to extract engine version information used in the diagnosis target application as second specific information of the diagnosis related information as a result of analyzing the diagnosis target application.
According to claim 8,
the processor,
The electronic device, configured to identify engine version information specified by the specific diagnosis item when the specific diagnosis item including version information of the OS and the engine information exists in the diagnosis item list.
According to claim 9,
the processor,
When the engine version information specified by the specific diagnosis item does not exist in the engine version information extracted as the second specific information of the diagnosis-related information, a guide to the engine version information defined in the specific diagnosis item An electronic device set up to provide
In the method of operating an electronic device,
Analyzing a diagnosis target application and extracting diagnosis-related information about the diagnosis target application;
An operation of determining whether a specific diagnosis item corresponding to the first specific information included in the diagnosis related information and version information of an operating system (OS) for executing the diagnosis target application exists in the diagnosis item list - the above The first specific information includes at least one of application programming interface (API) information or engine information used by the application to be diagnosed;
an operation of identifying diagnosis target information specified by the specific diagnostic item from the diagnosis item list based on the existence of the specific diagnostic item in the diagnosis item list; and
and providing a guide for the diagnosis target information based on the fact that the diagnosis target information is not identified from the diagnosis related information.
According to claim 11,
Each diagnosis item in the diagnosis item list,
at least one of a version of the OS, a first diagnostic component, a second diagnostic component, a diagnostic test failure condition, or a guide;
The first diagnostic element corresponds to one of application programming interface (API) information and engine information;
The second diagnostic element corresponds to one of permission information, API information, or engine version information,
The diagnostic test failure condition indicates a case in which the second diagnostic component is not detected,
The method of claim 1 , wherein the guide includes information related to use of the second diagnostic element.
According to claim 11,
The operation of extracting the diagnosis-related information,
and extracting authority information acquired by the diagnosis target application as second specific information of the diagnosis related information as a result of analyzing the diagnosis target application.
According to claim 13,
The operation of identifying the diagnosis target information specified by the specific diagnosis item,
When the specific diagnosis item including the version information of the OS and the API information exists in the diagnosis item list, identifying permission information specified by the specific diagnosis item. how it works.
According to claim 14,
The operation of providing a guide for the diagnosis target information,
When the authority information specified by the specific diagnosis item does not exist in the authority information extracted as the second specific information of the diagnosis-related information, providing a guide for the authority information defined in the specific diagnosis item A method of operating an electronic device, including an operation.
According to claim 11,
The operation of identifying the diagnosis target information specified by the specific diagnosis item,
and identifying other API information specified by the specific diagnosis item when the specific diagnosis item including version information of the OS and the API information exists in the diagnosis item list. .
According to claim 16,
The operation of providing a guide for the diagnosis target information,
If the other API information specified by the specific diagnosis item does not exist in the API information included in the first specific information of the diagnosis-related information, a guide for the other API information defined in the specific diagnosis item is provided. A method of operating an electronic device, including providing an operation.
According to claim 11,
The operation of extracting the diagnosis-related information,
and extracting, as a result of analyzing the diagnosis target application, engine version information used in the diagnosis target application as second specific information of the diagnosis related information.
According to claim 18,
The operation of identifying the diagnosis target information specified by the specific diagnosis item,
and identifying engine version information specified by the specific diagnosis item when the specific diagnosis item including the version information of the OS and the engine information exists in the diagnosis item list. .
According to claim 19,
The operation of providing a guide for the diagnosis target information,
When the engine version information specified by the specific diagnosis item does not exist in the engine version information extracted as the second specific information of the diagnosis-related information, a guide to the engine version information defined in the specific diagnosis item A method of operating an electronic device comprising an operation of providing a.

Images