WO2024076123A1

WO2024076123A1 - Method for updating application and electronic device therefor

Info

Publication number: WO2024076123A1
Application number: PCT/KR2023/015188
Authority: WO
Inventors: 오명진; 김문경; 박철준; 서동욱; 이세영; 조용기
Original assignee: 삼성전자 주식회사
Priority date: 2022-10-05
Filing date: 2023-10-04
Publication date: 2024-04-11

Abstract

An electronic device according to various embodiments disclosed in the present document comprises a communication module, a memory, and a processor operatively connected to the communication module and the memory, wherein the memory may store instructions that instruct, when executed, the processor to: receive app store source change information for updating a specific application on the basis of application information of the specific application installed on the electronic device; check whether a higher version of the specific application exists in an app store where an update of the specific application is to be performed, which has been identified on the basis of the app store source change information for the specific application; and update the specific application by receiving a higher version application package from the identified app store.

Description

Application update method and its electronic device

Various embodiments disclosed in this document relate to an application update method and an electronic device thereof.

An electronic device may include an operating system (OS) for controlling one or more resources and an application executable on the operating system.

Electronic devices can perform application updates for applications installed in the electronic device through various application stores (hereinafter referred to as ‘App stores’) (e.g. Play StoreTM) operated by servers. You can. The electronic device may download an application package (e.g., an installation file (e.g., *.apk file)) from the App Store to update the application.

When updating an application, the electronic device can perform the update by downloading the application package through the app store where the application is installed. However, in various situations, there may be a need to perform an update by downloading the application package through an app store other than the app store where the application was installed.

Various embodiments disclosed in this document are intended to provide a method and an electronic device for updating an application by changing the app store in an electronic device.

The technical problem to be achieved in the present disclosure is not limited to the technical problem mentioned above, and other technical problems not mentioned can be clearly understood by those skilled in the art from the description below. There will be.

An electronic device according to various embodiments disclosed in this document includes a communication module, a memory, and a processor operatively connected to the communication module and the memory, and when the memory is executed, the processor is connected to the electronic device. Receive app store source change information that performs an update for the specific application based on the application information of the installed specific application, and update the specific application confirmed based on the app store source change information for the specific application. Instructions for checking whether a higher version for the specific application exists in the app store to be performed, receiving the application package for the higher version from the confirmed app store, and performing an update for the specific application. You can save it.

A method of an electronic device according to various embodiments disclosed in this document includes the operation of receiving app store source change information for performing an update for a specific application based on application information of a specific application installed on the electronic device, the specific application An operation of checking whether a higher version for the specific application exists in the app store to perform an update for the specific application, which is confirmed based on the app store source change information, and the higher version from the confirmed app store. It may include an operation of receiving an application package and performing an update for the specific application.

In relation to the description of the drawings, identical or similar reference numerals may be used for identical or similar components .

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

2 is a block diagram of an electronic device according to various embodiments.

FIG. 3 is a diagram illustrating the operation of an electronic device to perform an application update according to an embodiment.

FIG. 4 is a flowchart illustrating the operation of an electronic device to perform an application update according to various embodiments.

Figure 5 is a signal processing flowchart between functional modules of an electronic device and a server for performing an application update according to an embodiment.

FIG. 6 is a diagram illustrating the operation of an electronic device to perform an application update according to an embodiment.

Figure 7 shows an example of a specification file for update app store changes, according to one embodiment.

Figure 8 is a signal processing flowchart between functional modules of an electronic device and a server for performing an application update according to another embodiment.

FIG. 9 is a diagram illustrating an operation of an electronic device to perform an application update according to an embodiment.

Figure 10 is a signal processing flowchart between functional modules of an electronic device and a server for performing an application update according to another embodiment.

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 communicates with the electronic device 102 through a first network 198 (e.g., a short-range wireless communication network) or a second network 199. It is possible to communicate with at least one of the electronic device 104 or the server 108 through (e.g., 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 one 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, and 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 may include an antenna module 197. In some embodiments, at least one of these components (eg, the connection terminal 178) may be omitted or one or more other components may be added to the electronic device 101. In some embodiments, some of these components (e.g., sensor module 176, camera module 180, or antenna module 197) are integrated into one component (e.g., display module 160). It can be.

The processor 120, for example, executes software (e.g., program 140) to operate at least one other component (e.g., hardware or software component) of the electronic device 101 connected to the processor 120. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of data processing or computation, the processor 120 stores commands or data received from another component (e.g., sensor module 176 or communication module 190) in volatile memory 132. The commands or data stored in the volatile memory 132 can be processed, and the resulting data can be stored in the non-volatile memory 134. According to one embodiment, the processor 120 includes a main processor 121 (e.g., a central processing unit or an application processor) or an auxiliary processor 123 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device 101 includes a main processor 121 and a secondary processor 123, the secondary processor 123 may be set to use lower power than the main processor 121 or be specialized for a designated function. You can. The auxiliary processor 123 may be implemented separately from the main processor 121 or as part of it.

The auxiliary processor 123 may, for example, act on behalf of the main processor 121 while the main processor 121 is in an inactive (e.g., sleep) state, or while the main processor 121 is in an active (e.g., application execution) state. ), together with the main processor 121, at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) At least some of the functions or states related to can be controlled. According to one embodiment, co-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). there is. According to one embodiment, the auxiliary processor 123 (eg, neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. For example, such learning may be performed in the electronic device 101 itself on which the artificial intelligence model is performed, or may be performed through a separate server (e.g., server 108). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the examples described above. In addition to hardware structures, artificial intelligence models may additionally or alternatively include software 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. Data may include, for example, input data or output data for software (e.g., program 140) and instructions related thereto. 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 application 146.

The input module 150 may receive commands or data to be used in a component of the electronic device 101 (e.g., the processor 120) from outside the electronic device 101 (e.g., a user). The input module 150 may include, for example, a microphone, mouse, keyboard, keys (eg, buttons), or digital pen (eg, 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. Speakers can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 160 can 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 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 force generated by the touch.

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 acquires sound through the input module 150, the sound output module 155, or an external electronic device (e.g., directly or wirelessly connected to the electronic device 101). Sound may be output through the electronic device 102 (e.g., speaker or headphone).

The sensor module 176 detects the operating state (e.g., power or temperature) of the electronic device 101 or the external environmental state (e.g., 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 includes, 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 IR (infrared) sensor, an optical sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 177 may support one or more designated protocols that can be used to connect the electronic device 101 directly or wirelessly with 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 can 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 can convert electrical signals into mechanical stimulation (e.g., vibration or movement) or electrical stimulation 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 electrical stimulation device.

The camera module 180 can 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 can manage power supplied to the electronic device 101. According to one embodiment, the power management module 188 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

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

Communication module 190 is configured to provide a direct (e.g., wired) communication channel or wireless communication channel between electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108). It can support establishment and communication through established communication channels. Communication module 190 operates independently of processor 120 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 190 is a wireless communication module 192 (e.g., 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 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 198 (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 199 (e.g., legacy It may communicate with an external electronic device 104 through a telecommunication network such as a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 192 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 to communicate within a communication network such as the first network 198 or the second network 199. The electronic device 101 can be confirmed or authenticated.

The wireless communication module 192 may support 5G networks after 4G networks and next-generation communication technologies, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. The wireless communication module 192 may support high frequency bands (eg, mmWave bands), for example, to achieve high data rates. The wireless communication module 192 uses various technologies to secure performance in high frequency bands, for example, beamforming, massive array multiple-input and multiple-output (MIMO), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 192 may support various requirements specified in the electronic device 101, an external electronic device (e.g., electronic device 104), or a network system (e.g., second network 199). According to one embodiment, the wireless communication module 192 supports 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., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 197 may transmit or receive signals or power to or from the outside (eg, an external electronic device). According to one embodiment, the antenna module 197 may include an antenna including a radiator made 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 the communication method used in the communication network, such as the first network 198 or the second network 199, is connected to the plurality of antennas by, for example, the communication module 190. can be selected Signals or power may be transmitted or received between the communication module 190 and an external electronic device through the at least one selected antenna. According to some embodiments, in addition to the radiator, other components (eg, radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 197.

According to various embodiments, the antenna module 197 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., mmWave band); And a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in 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 (e.g., 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 one 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 of the same or different type as the electronic device 101. According to one embodiment, all or part of the operations performed in the electronic device 101 may be executed in one or more of the external

electronic devices

102, 104, or 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 may perform the function or service instead of executing the function or service on its own. Alternatively, or additionally, one or more external electronic devices may be requested to perform at least part of the function or service. One or more external electronic devices that have received the request may execute at least part of the requested function or service, or an 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 process the result as is or additionally and provide it as at least part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology can 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 (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology. .

Electronic devices according to various embodiments disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various changes, equivalents, or replacements of the embodiments. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “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 phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one element from another, and may be used to distinguish such elements in other respects, such as importance or order) is not limited. One (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 any of the components can be connected to the other components directly (e.g. wired), 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 logic, logic block, component, or circuit, for example. It can be used as A module may be an integrated part or a minimum unit of the parts or a part 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 the present document are one or more instructions stored in a storage medium (e.g., built-in memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101). It may be implemented as software (e.g., program 140) including these. For example, a processor (e.g., processor 120) of a device (e.g., electronic device 101) may call at least one command among one or more commands stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and this term refers to cases where data is semi-permanently stored in the storage medium. There is no distinction between temporary storage cases.

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

According to various embodiments, each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components. there is. According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple 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 component of the plurality of components in the same or similar manner as those performed by the corresponding component of the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, or omitted. Alternatively, one or more other operations may be added.

FIG. 2 is a block diagram illustrating an electronic device 200 (eg, the electronic device 101 of FIG. 1 ) for performing an application update according to various embodiments.

Referring to FIG. 2, the electronic device 200 includes a communication module 210 (e.g., the communication module 190 of FIG. 1), a processor 220 (e.g., the processor 120 of FIG. 1), and a memory 230. ) (e.g., memory 130 of FIG. 1). The components shown in FIG. 2 are only examples, and some of them may be omitted or replaced, or may be integrated as a single module, depending on various embodiments. Detailed descriptions of the components shown in FIG. 2 that overlap with those described with reference to FIG. 1 may be omitted here.

According to various embodiments, the communication module 210 connects the electronic device 200 and a plurality of app stores (first app store 301 and second app store 302) (e.g., server 108 of FIG. 1). It can support the establishment of a direct (e.g. wired) or wireless communication channel between devices, and the performance of communication through the established communication channel.

According to one embodiment, the communication module 210 may include a wireless communication module (e.g., the wireless communication module 194 of FIG. 1) and a network (e.g., a second network 199 (e.g., a legacy cellular network, Various signals and/or data for application updates can be transmitted and received by communicating with external app stores through a 5G network, a next-generation communication network, the Internet, or a long-distance communication network such as a computer network (e.g. LAN or WAN). there is.

According to various embodiments, the memory 230 may include function modules that execute (or process) functions related to updating an application of the electronic device 200.

In various embodiments, functional modules may be included as hardware modules or software modules in at least one processor 220 including processing circuitry. The functional modules according to the embodiment shown in FIG. 2 are software (e.g., program 140 in FIG. 1) and are stored in the form of instructions (or instructions) in the memory 230. As such, these instructions may be loaded by at least one processor 220 to execute operations of the functional module.

Various embodiments are not limited to this, and functional modules related to updating an application may be implemented as a separate hardware configuration that runs as part of the processor 220 and/or operates independently of the processor 220.

Referring to FIG. 2, the functional modules included in the memory 230 include a store manager 231, a store database 232, a package parser 233, and a package manager. manager) (234), a setting database (235), and/or store apps (236). Parts of the above-described functional modules may be omitted or replaced, or may be integrated with at least one other module. The setting DB 235 and the store DB 232 are described below as separate DBs, but embodiments are not limited thereto and may use the same physically DB depending on implementation.

According to one embodiment, it operates with a server structure such as the first app store 301 or the second app store 302 for distributing the developer's applications and a client structure such as the store apps 236 installed on the electronic device 200. It can be.

According to one embodiment, the store apps 236 receive an application installation file or application package (e.g. *.apk, Android) from the first app store 301 or the second app store 302 through the communication module 210. package kit file) can be received (or downloaded).

According to one embodiment, an application (e.g., Android application) may be developed in a specific programming language (e.g., Java language), and an application installation file or application package is a file required to install or update the application, and includes code (classes. dex), resources (e.g. Java source code, layout xml files, image files, audio files, animations, menus, styles, and/or colors) and/or signature keys for authentication, and zip. It can be compressed in archive format and created as an application package file (e.g., “apk” extension file). For example, one apk file represents one application (or app) and may be a file installed on the electronic device 200.

According to one embodiment, the package manager 234 can install, delete, and/or update applications.

According to one embodiment, the package manager 234 may perform an application installation operation when an application installation file is downloaded to the electronic device 200. When installation of an application is completed, the package manager 234 can store information about the application in the settings DB 235.

According to one embodiment, the settings DB 235 may store information about applications installed in the electronic device 200. The application information stored in the settings DB 235 may include, for example, the package name of the application, certificate information, and information on the entity that installed the application (app store).

According to one embodiment, when an application package (e.g., an update file related to a target application to be updated) is received by the electronic device 200 for an application update, the package manager 234 stores the received application package (e.g., an update file related to the target application to be updated). Validity check and verification of update files related to the application can be performed.

According to one embodiment, when verification of the application is completed, the package manager 234 extracts an executable file (e.g., dex information) from an application package (e.g., a downloaded application package) related to the application to be updated through the package parser 233. ) can be parsed to create a new profile to use for compilation. According to one embodiment, the package manager 234 performs compilation based on the new profile to generate files such as *.oat files (or native files) and *.art (or initialization images) and builds the application based on these. A data directory can be created. According to one embodiment, when the application installation is completed, the package manager 234 may delete the previous application installation file (eg, .apk file).

According to one embodiment, the process of automatically updating an application installed on the electronic device 200 using a specific app store is carried out by the specific app store, and the app store that performs such application updating can be said to be the source of the application. there is. The source information for the application is set when the application is installed on the electronic device 200, and the app store that installed the application can be the app store that updates the application, that is, the source of the application. there is. For example, when a specific application is installed using the first app store 301, the first app store 301 may be the source of the specific application.

According to one embodiment, the store manager 231 may generally control updates to applications installed in the electronic device 200.

According to one embodiment, the store manager 231 may detect various events in which source information for applications installed on the electronic device 200 changes.

According to one embodiment, the store manager 231 receives source change information of an application for which the source is to be changed from the app store subject to source change (e.g., the second app store 302) through the store apps 236. Source information change events can be detected.

According to one embodiment, the store manager 231 stores the inside of the APK parsed by the package parser 233 during the installation process of the APK received through the app store (e.g., the first app store 301), which is the current source of the specific application. Source change events can be detected by receiving source change information through the development specification file (e.g., Android Manifest) included in the.

According to one embodiment, when the store manager 231 detects the occurrence of a change in the source of the app store that updates the application installed in the electronic device 200 according to the occurrence of various events, the store manager 231 stores the application by the app store changed based on this. update can be performed.

According to one embodiment, when an update performance app store source change situation occurs, the store manager 231 may provide an API to the store apps 236 to inform them that a specific application installed in the electronic device 200 is subject to a source change. .

According to one embodiment, when an app store change occurs for a specific application installed on the electronic device 200, the store manager 231 sends app store change information notifying the app store change along with information about the specific application to the store DB 232. ) can be saved in . Store apps 236 can check the application subject to source change through information stored in the store DB 232.

According to one embodiment, the store DB 232 may store the package name, app store information, version information, and/or certificate information of the application subject to source change. Store apps 236 may receive an application package for an application subject to change of source through the app store subject to change of source based on information stored in the store DB 232. For example, the store apps 236 may check the application to be changed in origin and/or the app store name to be changed in source based on the package name and/or certificate information stored in the store DB 232. For example, the store apps 236 compare the version information stored in the store DB 232 with the actual version information of the application to change the source, and if the saved version of the application to change the source is a version later than the version of the currently installed application, the source is changed. You can proceed with the change.

Table 1 below may show an example of source change information stored in the store DB 232.

출처 변경 대상 (패키지 명칭)Source Change To (package name)	출처 변경 가능 버전Source can be changed version	인증서 (인증서 고유값)certification (certificate unique value)
com.android.samsungpaycom.android.samsungpay	1.2.31.2.3	3b16c6270c973e60d6add360009f049b4f7ddbadf7a60c7f120a906b46ad1cfe3b16c6270c973e60d6add360009f049b4f7ddbadf7a60c7f120a906b46ad1cfe
com.android.sasmungpasscom.android.sasmungpass	12.2412.24	ea37a1c4d03dcb33abdae9f8097 30573c65195a0cd49c9b1e8e2715448adb802ea37a1c4d03dcb33abdae9f8097 30573c65195a0cd49c9b1e8e2715448adb802

In the above example, the package name subject to source change may include information on the application subject to source change and app store information subject to source change. For example, the package name subject to source change may indicate the name of the application subject to source change used in the app store. According to one embodiment, the store apps 236 confirm through the store manager 231 that a specific application installed on the electronic device 200 is subject to source change, and select the source change target app store (e.g., the second app store ( 302)), it can be checked whether a higher version of the application subject to source change exists, and if a higher version exists, the store manager 231 can be notified that the higher version application exists. According to one embodiment, the store manager 231 induces user consent through various notifications such as push notifications or pop-up notifications, and upon user consent, changes the source of the application through the package manager 234. there is.

According to one embodiment, the package manager 234 uses the store apps 236 to receive an application package from the changed source, the app store (e.g., the second app store 302), and stores the received application package as a package. The update can be performed by parsing through the parser 233.

According to one embodiment, when the application update according to the change in the app store source is completed, the package manager 234 may update the setting DB 235 with information about the changed app store for the updated application.

According to one embodiment, when the update due to the change in the App Store source for the application is completed, the store manager 231 sends the app store source change information notifying the change in the App Store source along with information about the updated application to the store DB 232. ) can be deleted from.

FIG. 3 is a diagram illustrating the operation of an electronic device (eg, the electronic device 200 of FIG. 2 ) to perform an application update according to an embodiment.

According to one embodiment, the first application (e.g., Samsung Pay) installed on the electronic device 200 may be an application installed by an installation file received from the first app store 301 through the first store app 201. there is.

According to one embodiment, the second application (e.g., Samsung Note) installed on the electronic device 200 may be an application installed by an installation file received from the second app store 302 through the second store app 202. there is.

According to one embodiment, source information of the first application and the second application may be stored in the settings DB (e.g., the settings DB 235 of FIG. 2). For example, the source information of the first application may be stored in the first application. It may include the first app store 301, which is the installer of the application. For example, the source information of the second application may include the second app store 302, which is the installer of the second application.

According to one embodiment, the store manager of the electronic device 200 (e.g., the store manager 231 in FIG. 2) may detect various events in which source information about an application installed on the electronic device 200 changes.

According to one embodiment, the store manager 231 controls the source change target app store (e.g., the second app store 302) through the second store app 202 (e.g., one of the store apps 236 in FIG. 2). A source information change event can be detected by receiving source change information of an application that wants to change the source from )).

According to one embodiment, the store manager 231 stores the inside of the APK parsed by the package parser 233 during the installation process of the APK received through the app store (e.g., the first app store 301), which is the current source of the specific application. Source change events can be detected by obtaining source change information through the development specification file (e.g., Android Manifest) included in the.

According to one embodiment, when a source app store change event occurs for the first application (e.g., Samsung Pay) installed on the electronic device 200, the store manager 231 notifies the app store change along with information about the first application. App Store change information can be stored in the store DB (e.g., the store DB 232 in FIG. 2).

According to one embodiment, the store DB 232 may store the package name, app store information, version information, and/or certificate information of the application subject to source change. For example, the app store change information stored in the store DB 232 may include the name of the second app store 302 for the first application, which is the application subject to source change.

According to one embodiment, the first store app 201 and the second store app 202 can periodically check the store DB 232 and check the application subject to source change through stored information.

According to one embodiment, the second store app 202 may check the name of the application to be changed and/or the app store name to be changed based on the package name and/or certificate information stored in the store DB 232. For example, the second store app 202 can confirm that the App Store source for the first application (eg, Samsung Pay) is changed to itself based on information stored in the store DB 232.

According to one embodiment, when the second store app confirms that the App Store source of the first application is changed to itself, it checks the current version of the first application and downloads the higher version of the first application through the second app store 301. You can check whether this exists.

According to one embodiment, if a higher version of the first application exists in the second app store 302, the second store app 202 may notify the store manager 231 that the higher version application exists.

According to one embodiment, the store manager 231 induces user consent through various notifications such as push notifications or pop-up notifications, and upon user consent, changes the source of the first application through the package manager 234. You can perform an update.

According to one embodiment, the package manager 234 may receive an application package through the second store app 202 and perform an update based on the received application package.

According to one embodiment, when the update of the first application is completed, the package manager 234 may update the setting DB 235 with information about the second app store, which is a changed source for the first application.

According to various embodiments, an electronic device (e.g., the electronic device 200 of FIG. 2) includes a communication module (e.g., the communication module 210 of FIG. 2), a memory (e.g., the memory 230 of FIG. 2), and a processor (e.g., processor 220 of FIG. 2) operatively connected to the communication module and the memory, wherein the memory, when executed, allows the processor to access application information of a specific application installed on the electronic device. Based on this, receive app store source change information that performs an update for the specific application, and send an update to the app store that is confirmed based on the app store source change information for the specific application. It is possible to check whether a higher version for a specific application exists, receive an application package of the higher version from the confirmed app store, and store instructions for updating the specific application.

According to various embodiments, the memory may store instructions that, when executed, cause the processor to receive the app store source change information through the confirmed app store of the specific application.

According to various embodiments, when the memory is executed, the processor obtains the App Store source change information from a file received from the confirmed App Store and stores the App Store source change information in the store database through the store manager. You can save instructions to save in .

According to various embodiments, when the memory is executed, the processor verifies the current source of the specific application through the store manager, and the App Store where the current source is confirmed based on the App Store source change information. In different cases, instructions for storing the app store source change information in the store database may be stored.

According to various embodiments, when the memory is executed, the processor checks the app store source change information stored in the store database through a store app corresponding to the confirmed app store, and Instructions for receiving the application package of the specific application from the store may be stored.

According to various embodiments, the memory, when executed, may store instructions that cause the processor to delete the App Store source change information from the store database through the store manager when the update of the specific application is completed. .

According to various embodiments, the memory may store instructions that, when executed, cause the processor to receive the app store source change information through the app store, which is the current source of the specific application.

According to various embodiments, when the memory is executed, the processor receives another application package of the specific application from the App Store, which is the current source, and retrieves the App Store source change information from a file included in the other application package. You can store instructions that allow you to obtain .

According to various embodiments, the memory, when executed, causes the processor to store the app store source change information in the store database through a store manager, and store the app store source change information in the store database through a store app corresponding to the confirmed app store. The app store source change information stored in can be confirmed, and instructions for receiving the higher version application package from the confirmed app store based on the app store source change information can be stored.

According to various embodiments, when the memory is executed, when the processor confirms a plurality of store apps based on the app store source change information through the store manager, the memory determines priority among the plurality of store apps. Instructions for confirming the app store corresponding to the store app installed on the electronic device as the app store to perform updates for the specific application may be stored.

According to various embodiments, if the version of the developer application installed in the electronic device is higher than the application version of the file, the processor may confirm the application as an application subject to source change.

FIG. 4 is a flowchart illustrating the operation of an electronic device (e.g., the electronic device 200 of FIG. 2 ) to perform an application update according to various embodiments.

According to one embodiment, the processor of the electronic device 200 (e.g., the processor 220 of FIG. 2) loads instructions (or instructions) stored in a memory (e.g., the memory 230 of FIG. 2) and It may be set to perform operations to change and update the source of various applications installed on the electronic device 200.

According to one embodiment, the processor 220 may receive app store source change information for a specific application installed on the electronic device 200 in operation 401. For example, the processor 220 may receive app store source change information for a specific application through the source change target app store that will perform updates according to the source change, based on the application information of the specific application. For example, the processor 220 may receive app store source change information for a specific application through the current source app store where the specific application is installed or recently updated, based on the application information of the specific application.

According to one embodiment, the processor 220 checks the app store performing an update for a specific application in operation 403, based on the app store source change information for the specific application, and updates the parent app for the specific application through the confirmed app store. You can check whether the version exists.

According to one embodiment, the processor 220 may obtain the package name of a specific application, app store information to be changed as a source, version information, and/or certificate information through app store source change information.

According to one embodiment, if a higher version for a specific application exists in the confirmed app store, the processor 220 may perform an update by receiving the higher version application package through the confirmed app store in operation 405. there is.

FIG. 5 illustrates functional modules of an electronic device (e.g., the electronic device 200 of FIG. 2) and a server (e.g., the app store 201 and/or 202 of FIG. 2) for performing an application update according to an embodiment. This is a signal processing flow chart.

According to one embodiment, the store app (e.g., the second store app 202 in FIG. 3) is stored by the second store app 202 through the settings DB (e.g., the settings DB 235 in FIG. 2) in operation 501. You can check the applications installed on the electronic device 200.

According to one embodiment, the store app 202 may check whether a higher version of the target application exists in the corresponding app store (eg, the second app store 302) in operation 531.

According to one embodiment, if a higher version of the target application exists, the second store app 202 downloads the higher version application package from the second app store 302 and sends it to the package manager 234 in operation 505. You can update by requesting an update to the application.

Meanwhile, in operation 507, the second store app 202 is configured to change the source to the second app store 302 through the app store source change information stored in the store DB (e.g., the store DB 232 in FIG. 2). You can check the target application.

According to one embodiment, if the target application is stored in the electronic device 200, the second store app 202 may check whether a higher version of the target application exists in the second app store 302 in operation 509.

According to one embodiment, the second store app 202 operates when the electronic device 200 is connected to Wifi and/or when the electronic device 200 is likely to be unused (e.g., after midnight) and/or when charging. It may be implemented to search for an update target application in the background, but embodiments are not limited to this. For example, the second store app 202 periodically performs operation 507 to check the store DB 232, and accordingly periodically performs operation 509 to check the existence of a higher version through the second app store 302. It can be implemented to do so.

According to one embodiment, if a higher version of the target application exists in the second app store 302, the second store app 202 is applied to the electronic device 200 (e.g., the store manager 231) in operation 511. The existence of a higher version of the application can be announced by transmitting the version information of the application package.

According to one embodiment, the store manager 231 may request the user's consent to change the app store source in operation 513. For example, the store manager 231 may inform the second app store 302 that a higher version of the target application installed on the electronic device 200 exists and provide a user notification encouraging an update.

According to one embodiment, if there is user consent to change the app store source, the second store app 202 may download the application package of the target application from the second app store 302 in operation 515.

According to one embodiment, the second store app 202 may be implemented to download an application package before requesting user consent. However, even in this case, the user's consent may be required when performing an application update depending on the downloaded application package.

According to one embodiment, based on the downloaded application package, the second store app 202 may update the target application and change the source through the package manager 234 in operation 517. For example, when the target application is updated, the package manager 234 may update the source of the target application stored in the setting DB 235 to the second app store 302 to complete the source change.

FIG. 6 is a diagram illustrating an operation of an electronic device (eg, the electronic device 200 of FIG. 2 ) to perform an application update according to an embodiment.

According to one embodiment, the app store source change information may be processed using the first store app 301 or the second store app 302 (eg, store apps 236 in FIG. 2).

According to one embodiment, the app store source change information is an app store (e.g., the first app store 301 or the second app store 302 in FIG. 2) and the second store app 302 of the electronic device 200. It can be done through.

Hereinafter, an example of changing the source of a specific application (eg, Samsung Pay) installed by the first app store 301 to the second app store 302 will be described.

According to one embodiment, a specific application (e.g., Samsung Pay) is installed through the first app store 301, and referring to the setting DB 235, the source of the specific application (e.g., Samsung Pay) is the first app store ( 301).

According to one embodiment, information (e.g., app store change information) of an application that wishes to change the source to a specific store (e.g., the second app store 302) is changed to a specific app store (e.g., the second app store) that is the change source. It may be delivered to the electronic device 200 from (302)) through a corresponding store app (e.g., the second store app 202).

According to one embodiment, the app store change information for a specific application delivered to the electronic device 200 through a store app (e.g., the second store app 202) is stored in the store manager (e.g., the store manager 231 of FIG. 2). )) can be stored in a store DB (e.g., store DB 232 in FIG. 2).

According to one embodiment, the source change information of a specific application is, for example, in the form of a file (e.g., specification file) in which the intention to change the source is specified, from the second app store 302 to the electronic device (202) through the second store app 202. 200).

Figure 7 shows an example of a specification file for changing the app store source, according to one embodiment.

Referring to Figure 7, the specification file containing App Store change information may include information about the scope of application (e.g. country/operator/OS version) in specific fields (e.g. COUNTRY, CARRIERS, VERSION fields). . For example, a specification file that a developer uploads to the App Store may be classified and/or integrated based on coverage, and may be passed from the App Store to the Store App based on this. Each application may have different functions depending on the country/operator/OS version depending on the circumstances of the developer, and in this case, the size of data transmitted from the App Store to the electronic device 200 can be minimized through the scope of application.

According to one embodiment, the specification file may include the package name (e.g., SOURCE field) of the store app. According to one embodiment, the App Store can store and manage specification files based on the package name of the store app. According to one embodiment, the store manager 231 may register the specification file delivered to the electronic device 200 in the store DB 232 using the package name of the store app as a key value.

According to one embodiment, the specification file may include the package name, version, and/or certificate information (eg, PACKAGE field) of the application. According to one embodiment, the specification file is a file created for the purpose of changing the source of a specific application, and the electronic device 200 may use the package name, version, and/or certificate information of the individual application to specify the application to which it is applied. Among these, the package name is the application's unique information, but since it may be impersonated, certificate information may be required. For example, if the package name is the same and the certificate information included in the actual application package is the same as the certificate information of the application in the specification file, it can be determined that the application was created by the same developer. The version information is information about the version of the application for which the developer wishes to change the source. If the developer application installed on the electronic device 200 is larger than the version of the application in the specification file, the application can be determined to be subject to change of source.

According to one embodiment, the specification file may include a digital signature (eg, SIGNATURE field) for the included application information. In this case, the private key used may be the private key used when creating the application. A digital signature included in the specification file can be used to confirm that the package name, version, and/or certificate information included in the specification file was created by the actual developer. Before storing the source change information of a specific application in the store DB 232 based on the specification file, for example, certificate information can be extracted from the application package of the relevant application to authenticate the digital signature included in the specification file. If the digital signature is properly authenticated, it can be confirmed that the developer's private key used to create the application package was used for the digital signature, so the specification file can be trusted.

In the example of the specification file in Figure 7, the <CONFIG> area can specify the scope of application and prevent unnecessary file transfer. <SOURCE> in the <CONFIG> area can indicate the package name of the store application for which you wish to change the new source of the target application. The <APPLICATION> area may include information on applications for which the source is to be changed, and may include, for example, multiple application package names. When multiple application package names are included, certificate information (e.g., certificate HASH), application version, and/or digital signature information may be included for each application's package name. Authentication and integrity verification can be performed in the app store (e.g., the second app store 302) and the electronic device 200 using this information.

FIG. 8 is a signal processing flowchart between function modules of an electronic device (e.g., the electronic device 200 of FIG. 2) and a server (e.g., the app store 302 of FIG. 2) for performing an application update according to another embodiment. am.

According to one embodiment, the app store source change information of a specific application is received from the app store 302 through the store app (e.g., the second store app 202 in FIG. 2) in the form of a specification file, for example, and is performed in operation 801. It may be transmitted to the store manager of the electronic device 200 (e.g., the store manager 231 in FIG. 2). Accordingly, the store manager 231 can update a specific application in the store DB 232 as a list of applications wishing to change the source through a series of authentication processes.

According to one embodiment, in operation 803, the store manager 231 checks whether a specific application is installed on the electronic device 200 through the setting DB 235 based on the package name included in the specification file and provides the source information. You can check. For example, the intention to change the source for a specific application can be confirmed by comparing the source change information included in the specification file with the source information stored in the settings DB 235.

According to one embodiment, the store manager 231 may check whether a source to be changed for a specific application is registered in the store DB 232 in operation 805 based on the source information of the specific application.

According to one embodiment, when a change target source for a specific application is registered, in operation 807, the store manager 231 stores the certificate information stored by package name from the application setting file in the setting DB 235 into the specification file of the application package. Authentication can be performed by comparing the certificate information entered for each package name included in to check if it matches. The package name is a value created by the developer and may be duplicated, so for example, authentication can be performed by comparing certificate hashes.

According to one embodiment, the store manager 231 refers to the store DB 232 and, if source change information for a specific application is not registered, stores the source change information for the package name of the specific application in the store DB 232. You can register. In this case, the specification file information can be authenticated based on the digital signature included in the specification file, and the package name of the store app included in the specification file can be registered by setting it as the key value of the store DB 232.

According to one embodiment, the store manager 231 may register the application information in the store DB 232 using the name of the store app as the key value after confirming whether the target application and source change are required. Therefore, the store app can use its package name as the key value of the store DB 232 to obtain a list of applications that it wishes to change from the store DB 232.

FIG. 9 is a diagram illustrating an operation of an electronic device (eg, the electronic device 200 of FIG. 2 ) to perform an application update according to an embodiment.

According to one embodiment, the electronic device 200 may check application source change information using a specification file (eg, android manifest) included in the application package.

According to one embodiment, the desired source of change for the application may be specified as source change information in the developer's specification file included in the application package.

According to one embodiment, the application package may be delivered when the application to be changed in origin is installed or updated in the electronic device 200, and after the application to be changed in source is installed or updated, a package manager (e.g., the package manager in FIG. 2) Through (234)), the source change information can be transmitted to the store manager (e.g., the store manager 231 in FIG. 2) so that the store DB (e.g., the store DB 232 in FIG. 2) is updated. If the intention to change the application installation source is confirmed by referring to the specification file included in the application package during the application installation process, the package manager 234 stores the source change information if a store app for which a source change is desired exists in the electronic device 200. It can be registered in DB (232).

In the embodiment of FIG. 6, the source change operation may be performed by checking whether or not the target application is installed on the electronic device 200 according to the source change information included in the received specification file. However, in the embodiment of FIG. 9, the source change operation may be performed by checking whether the target application is installed in the electronic device 200. Based on the specified specification file, the source change operation may be performed by checking whether the store app, which is the desired source for change, is installed on the electronic device 200. If the store app that the developer wants to change does not exist in the electronic device 200, the app store of the application cannot be changed.

According to one embodiment, a plurality of stores desired to be changed may be specified in the specification file of the application package. Accordingly, the electronic device 200 can register the store app installed on the electronic device 200 among the plurality of specified store apps as the source for which the change is desired.

According to one embodiment, store apps (e.g., store apps 236 in FIG. 2) use the store DB 232 to secure a list of applications that wish to change the source from the electronic device 200 to the app store managed by the store app. ) can be referred to periodically. In this case, the store apps 236 can check the package name, version, and/or certificate information of the application they wish to change by referring to the store DB 232 through the standard API using their package name as the key value.

According to one embodiment, when it is desired to change the app store source that provides the latest updated version of a specific application to the electronic device 200, the source change information can be specified in the specification file included in the application package for the specific application. , while the specific application is being installed or updated on the electronic device 200, source change information may be transmitted to the electronic device 200.

According to one embodiment, an application package including a specification file specifying the developer's intention to change the app store source for the application may be installed on the electronic device 200.

According to one embodiment, in the process of registering source change information based on the specification file included in the application package, for example, the process of authenticating a digital signature according to the package name may be omitted. When the application package is created, it is signed with the developer's private key, and during installation on the electronic device 200, a process may be performed to check the integrity and authentication of all files of the application package. Therefore, additional authentication for the specification file included in the application package can be omitted.

As an example of a specification file as described above, the android manifest file is a development specification file defined in an Android application package, and specifies the unique name (package name), permissions, version, and custom format of the application that the developer wishes to use in the application. You can use it.

According to one embodiment, as source change information, a target store tag may be defined in the specification file. For example, the target store tag is an example of a custom format and can specify B, C, and D Store. Accordingly, during the application installation process, the store manager 231 checks whether store apps desired to be changed exist in the electronic device 200 according to priority, and stores the existing store apps in the store DB 232 as a source of desired changes for the installed application. You can save it. In this case, if the store app that actually installs the installation application is the same as the desired change source of the application included in the specification file, it is determined that there is no need to change the source, and the source change information may not be stored in the store DB 232.

FIG. 10 shows signals between function modules of an electronic device (e.g., the electronic device 200 of FIG. 2) and a server (e.g., the first app store 301 of FIG. 2) for performing an application update according to another embodiment. This is a processing flow chart.

Referring to FIG. 10, an application package downloaded from the first app store 301 through a store app (e.g., the first store app 201 in FIG. 2) for installation or update of a specific application is packaged in operation 1001. It can be passed to the parser 233 so that the application can be installed. The package parser 233 may parse an executable file, and may request a package manager (e.g., the package manager 234 in FIG. 2) to install an application in operation 1003 based on the parsed executable file.

According to one embodiment, the package manager 234 may store the installation source (eg, first app store 301) of the parsed application package in the settings DB 235 in operation 1005.

According to one embodiment, the package manager 234 checks source change information (e.g., desired change source included in the source change tag) included in the development specification file (e.g., Android Manifest) included in the application package in operation 1007. , if the installation source and the desired change source are different, the store manager (e.g., the store manager 231 in FIG. 2) may be requested to register the source change information.

According to one embodiment, the store manager 231 may check whether the requested source change information is registered in the store DB 232 in operation 1009.

According to one embodiment, in operation 1011, if the requested source change information is not registered in the store DB 232, the store manager 231 sets the target application to the desired store app to change the source through the setting DB 235. You can check whether it has been installed.

According to one embodiment, in operation 1013, the store manager 231 may register source change information for the target application in the store DB 232 if the target application is not installed through the store app for which a source change is desired. . Source change information for the target application may include, for example, the package name of the target application, version information, authentication information, and/or store app information for which the source is to be changed.

In various embodiments, the store app delivery method described with reference to FIG. 6 can request a change in the source of multiple applications, and can proceed with the change in source without updating the target application. For example, if a specific app store no longer supports application updates, it can be used to change the app store source to another store.

In various embodiments, in the application package delivery method of FIG. 9, the source is changed when the application is installed or updated, so the operation of specifying the application scope of the developer authentication process and the configuration file of the target application may be omitted. In addition, the app store for which you wish to change the source can be specified by priority, so it can be done regardless of whether a specific store app exists on the electronic device.

The embodiments disclosed in this document are merely presented as examples to easily explain the technical content and aid understanding, and are not intended to limit the scope of the technology disclosed in this document. Therefore, the scope of the technology disclosed in this document should be interpreted as including all changes or modified forms derived based on the technical idea of the various embodiments disclosed in this document in addition to the embodiments disclosed herein.

Claims

In electronic devices,

communication module;

Memory; and

Comprising a processor operatively connected to the communication module and the memory,

The memory, when executed, causes the processor to:

Receiving app store source change information that performs an update for the specific application based on application information of the specific application installed on the electronic device,

Confirm whether a higher version for the specific application exists in the App Store to perform an update for the specific application, which is confirmed based on the App Store source change information for the specific application,

Stores instructions for receiving the application package of the higher version from the confirmed app store and performing an update for the specific application.

Electronic devices.
According to paragraph 1,

The memory, when executed, causes the processor to:

An electronic device that stores instructions for receiving the app store source change information through the confirmed app store of the specific application.
According to paragraph 2,

The memory, when executed, causes the processor to:

Obtain the app store source change information from the file received from the confirmed app store,

An electronic device that stores instructions to store the app store source change information in a store database through a store manager.
According to paragraph 3,

The memory, when executed, causes the processor to:

Check the current source of the specific application through the store manager,

An electronic device that stores instructions for storing the App Store source change information in the store database when the current source is different from the App Store confirmed based on the App Store source change information.
According to paragraph 3,

The memory, when executed, causes the processor to:

An electronic device that stores instructions to check the app store source change information stored in the store database through a store app corresponding to the confirmed app store and to receive an application package of the specific application from the confirmed app store. Device.
According to paragraph 3,

The memory, when executed, causes the processor to:

An electronic device that stores instructions for deleting the app store source change information from the store database through the store manager when the update of the specific application is completed.
According to paragraph 1,

The memory, when executed, causes the processor to:

An electronic device that stores instructions for receiving app store source change information through the app store, which is the current source of the specific application.
In clause 7,

The memory, when executed, causes the processor to:

An electronic device that stores instructions for receiving another application package of the specific application from the current source, the App Store, and obtaining the App Store source change information from a file included in the other application package.
According to clause 8,

The memory, when executed, causes the processor to:

Save the above App Store source change information in the store database through the store manager,

Check the app store source change information stored in the store database through the store app corresponding to the confirmed app store, and receive the application package of the higher version from the confirmed app store based on the app store source change information. An electronic device that stores instructions to do something.
According to clause 8,

The memory, when executed, causes the processor to:

When a plurality of store apps are confirmed based on the app store source change information through the store manager, the app store corresponding to the store app installed on the electronic device is selected according to priority among the plurality of store apps to the specific application. An electronic device that stores instructions for checking with the app store to perform updates.
In the method of the electronic device,

An operation of receiving app store source change information for updating a specific application based on application information of the specific application installed on the electronic device;

Checking whether a higher version for the specific application exists in the app store that will perform an update for the specific application, which is confirmed based on the app store source change information for the specific application; and

A method comprising: receiving an application package of the higher version from the confirmed app store and performing an update to the specific application.
According to clause 11,

The receiving operation is a method of receiving the app store source change information through the confirmed app store of the specific application.
According to clause 12,

Obtaining the app store source change information from a file received from the confirmed app store; and,

The method further includes storing the app store source change information in the store database through the store manager.
According to clause 13,

Further comprising an operation of checking the current source of the specific application through the store manager,

The saving operation is a method of storing the App Store source change information in the store database when the current source is different from the App Store confirmed based on the App Store source change information.
According to clause 13,

An operation of checking the app store source change information stored in the store database through a store app corresponding to the confirmed app store; and

The method further includes receiving an application package of the specific application from the confirmed app store.