Electronic device, system and method for providing cloud service

Abstract

An electronic device according to one embodiment disclosed in the present document may comprise: a communication circuit; a display; a memory for storing a first application and instructions; and at least one processor. When executed individually or collectively by the at least one processor, the instructions can instruct the electronic device to: request a cloud service related to a second application from an external device through the communication circuit; receive, from the external device, cloud service data related to the second application executed by the external device; display, on the display, an execution screen of the second application on the basis of the cloud service data; receive, from the external device, a request, in the second application, for an action related to the first application; perform, by the first application, an action corresponding to the request for the action; and transmit, to the external device, a response to the request for the action on the basis of a result of performing the action. Other various embodiments identified through the specification are possible.

Description

Electronic device, system, and method for providing cloud services

[0001] The embodiments disclosed in this document relate to technology for providing cloud services.

[0002] A cloud service refers to a service that stores applications and / or data on a device providing cloud services connected via a network (e.g., a server device), and allows client devices to access these applications and / or data through external devices when necessary. For instance, some applications may require integration with other applications and / or web services. When attempting to integrate an application with other applications through a cloud service, the integration operations between applications may be performed on the server device providing the cloud service. For instance, when performing integration operations on a server device, it is necessary to store other applications to be integrated with the application currently running on the server device, as well as required user information, in advance. In this case, the client device must provide user information to the server device in advance, or a custom application designed for the server device must be stored on the server device beforehand. In particular, if the server device performs operations related to users' personal information, it may be vulnerable to privacy security risks.

[0003] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art related to the present disclosure.

[0004] An electronic device according to one embodiment disclosed in this document may include a communication circuit, a display, a memory for storing a first application and instructions, and at least one processor. When the instructions are executed individually or collectively by the at least one processor, the electronic device may request a cloud service related to a second application from an external device through the communication circuit, receive cloud service data related to the second application executed by the external device from the external device, display an execution screen of the second application through the display based on the cloud service data, receive a request for an action related to the first application of the second application from the external device, perform an action corresponding to the request for the action through the first application, and transmit a response to the request for the action to the external device based on the result of performing the action.

[0005] In one embodiment disclosed in this document, the system may include a first electronic device comprising a first application and a first delivery module, and a second electronic device comprising a second application and a second delivery module. The first electronic device may request a cloud service related to the second application from the second electronic device, receive cloud service data related to the second application from the second electronic device, display an execution screen of the second application based on the cloud service data, and receive a request for an action related to the first application of the second application from the second electronic device through the first delivery module. The request for the action may have a designated first format. The first electronic device may convert the request for the action into a designated second format and deliver it to the first application, perform an action corresponding to the request for the action through the first application, generate a response to the request for the action based on the result of performing the action, and convert the response into a designated first format and transmit it to the second electronic device through the first delivery module.

[0006] The second electronic device can execute the second application in response to the cloud service request received from the first electronic device, transmit the cloud service data related to the execution of the second application to the first electronic device, and during the execution of the second application, convert a request for an action related to the first application of the second application into the first format and transmit it to the first electronic device through the second transmission module, and convert a response to the request for an action received from the first electronic device into the second format and transmit it to the second application through the second transmission module.

[0007] A method for providing a cloud service of an electronic device including a first application according to an embodiment disclosed in this document may include: requesting a cloud service related to a second application from an external device; receiving cloud service data related to the second application executed by the external device from the external device; displaying an execution screen of the second application based on the cloud service data; receiving a request for an action related to the first application of the second application from the external device; performing an action corresponding to the request for the action through the first application; and transmitting a response to the request for the action to the external device based on the result of performing the action.

[0008] A storage medium according to one embodiment disclosed in this document may store instructions and / or a program that, when executed by at least one processor of an electronic device, causes the electronic device to request a cloud service related to a second application from an external device, receive cloud service data related to the second application executed by the external device from the external device, display an execution screen of the second application based on the cloud service data, receive a request for an action related to the first application of the electronic device of the second application from the external device, perform an action corresponding to the request for the action through the first application, and transmit a response to the request for the action to the external device based on the result of performing the action.

[0009] FIG. 1 is a block diagram of an electronic device according to one embodiment.

[0010] FIG. 2 is a block diagram of an electronic device according to one embodiment.

[0011] FIG. 3 illustrates a system according to one embodiment.

[0012] FIG. 4 is a flowchart of a method for providing a cloud service according to one embodiment.

[0013] FIG. 5 is a flowchart of a method for providing a cloud service according to one embodiment.

[0014] FIGS. 6a to 6c show a cloud service provision screen according to one embodiment.

[0015] FIG. 7 is a block diagram of an exemplary electronic device capable of performing the operations described in this document.

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

[0017] FIG. 1 is a block diagram of an electronic device according to one embodiment.

[0018] According to one embodiment, an electronic device (100) (e.g., the first electronic device (310) of FIG. 3 or the electronic device (700) of FIG. 7) (e.g., a local device (client device)) may include a communication circuit (110) (e.g., the communication circuit (760) of FIG. 7), a display (120) (e.g., the display (740) of FIG. 7), a memory (130) (e.g., the memory (720) of FIG. 7), and at least one processor (150) (e.g., the processor (710) of FIG. 7).

[0019] The communication circuit (110) can transmit and receive information and / or data with at least one external device (e.g., the second electronic device (303) of FIG. 3) (e.g., a cloud server). For example, the communication circuit (110) can receive data related to a cloud service and / or a request for an action related to a designated application (e.g., a first application) from the external electronic device (100). The communication circuit (110) can transmit a response to the request for a cloud service and / or a request for an action related to the designated application (e.g., a second application) to the external device.

[0020] The display (120) can visually display information. For example, the display (120) can display the execution screen of an application. For example, the display (120) can display the execution screen of an application running on the electronic device (100) and / or the execution screen of an application run by an external device (e.g., a cloud server). According to one embodiment, the display (120) may be integrally formed with an input device (e.g., a touch panel). For example, the display (120) may include a touchscreen display (120).

[0021] The memory (130) can store instructions that control the operation of the electronic device (100) when executed individually or collectively by at least one processor (150). For example, the instructions may be stored in one memory (130) or multiple memories (130). The memory (130) may store information and / or data related to the operations of the electronic device (100) at least temporarily. The memory (130) may store at least one application. For example, the memory (130) may store an application related to payment and / or an application related to user authentication. The at least one application may be an application already included in the electronic device (100) (e.g., installed at the time of shipment of the electronic device (100)) and / or a third-party provided application (3 rd It can include a party application.

[0022] At least one processor (150) can control the operations of the electronic device (100) by executing instructions stored in memory (130) individually or collectively. For example, the operations described in this disclosure as being performed by the 'processor (150)' may be understood as being performed individually or collectively by at least one processor (150). For example, at least one processor (150) can control each of the operations of the electronic device (100) described below independently or collectively. According to one embodiment, at least one processor (150) may include circuits such as a CPU (central processing unit), MPU (micro processor unit), AP (application processor), CP (communication processor), SoC (system on chip), and / or IC (integrated circuit).

[0023] The processor (150) may request a cloud service related to the second application from an external device through a communication circuit (110). For example, the second application may be stored in an external electronic device (100) and / or in the electronic device (100). For example, the second application may include at least one application (e.g., a game application) that supports the cloud service.

[0024] According to one embodiment, the processor (150) may receive cloud service data related to a second application executed by an external device from an external device through a communication circuit (110). For example, the cloud service data may include data related to the execution of the application.

[0025] According to one embodiment, the processor (150) may display an execution screen of the second application through the display (120) based on cloud service data. For example, the execution screen of the second application may include an indication indicating that the cloud service is in progress. For example, the processor (150) may transmit user input related to the second application to an external device while the second application is running, and receive execution data of the second application manipulated in real time based on user input from the external device. For example, if the second application is a game application, the processor (150) may provide the same service as when a user runs a game application on an electronic device (100) based on user input.

[0026] According to one embodiment, the processor (150) may receive a request for an action related to the first application of the second application from an external device via a communication circuit (110). For example, the first application may be included in the electronic device (100) and may not be included in the external device. For example, the request for an action received from the external device may correspond to a specified data format (e.g., a first format). For example, the first format may correspond to a specification defined for data transmission between different devices. For example, the received request for an action may have a specified file format (e.g., JSON format) and / or a specified data format (e.g., a stream of bytes). For example, the received request for an action may have the form of continuous data (e.g., bytes). The first processor (150) may convert the received request for an action into a specified data format (e.g., a second format) and transmit it to the first application. For example, the second format may be the same as the format used to transmit requests and / or responses between applications stored on the same device. For example, the second format may correspond to an explicit intent. For example, the processor (150) may transmit a request for an action of the second format to the first application via an explicit intent. For example, the request for an action may include a package name representing the application to perform the action and / or a component name associated with the action (e.g., activity and / or service). For example, an explicit intent may refer to a message object that transmits a request related to a specified function (e.g., a security-sensitive function (e.g., a payment function)) only to the specified caller by explicitly specifying the caller (e.g., the target to whom the request is to be transmitted). For example, the second application may transmit a request for an action to the first application via an explicit intent.For example, the processor (150) can receive a request for an action corresponding to an explicit intent of the second application from an external device and transmit it to the first application.

[0027] According to one embodiment, the processor (150) can perform an action corresponding to a request for an action through the first application. For example, if the request for an action is an in-app payment request through the first application, the processor (150) can perform an in-app payment through the first application. The processor (150) receives user input related to the action and can perform an action corresponding to a request for an action through the first application based at least partially on the received user input.

[0028] According to one embodiment, the processor (150) may transmit a response to a request for an action to an external device based on the result of performing the action through the communication circuit (110). For example, the response may include information related to the result of performing the action (e.g., payment success or payment failure). For example, the processor (150) may obtain a response corresponding to the result of performing the action from a first application. For example, the response obtained from the first application may correspond to a specified data format (e.g., a second format). The processor (150) may convert the response into a specified data format (e.g., a first format) and transmit it to an external device.

[0029] An electronic device (100) according to one embodiment can provide a designated service (e.g., in-app payment) by linking applications together in a manner substantially identical to when a first application and a second application are stored on the same device. A system according to one embodiment can provide a cloud service that provides the same user experience to the user even while providing the cloud service by providing the same service as running an application on a local device, without the need to develop and / or install a separate application for the cloud service for the designated service (e.g., in-app payment). An electronic device (100) according to one embodiment can provide a service requiring security (e.g., payment or authentication) while providing the cloud service without storing personal information (e.g., account information, security information, and / or payment-related information) outside the local device (server). An electronic device (100) according to one embodiment can provide the same service by providing the linkage between applications provided on the local device in the same manner even during the cloud service, thereby storing the same application as the existing one on the server rather than a separately modified application. For example, an electronic device (100) according to one embodiment receives a request for an action through an explicit intent specifying a specific target (e.g., a first application of the electronic device (e.g., a payment application)) from an external device providing a cloud service (e.g., a second application of a cloud server), and transmits the result of performing an action corresponding to the request through the first application to the external device (e.g., a second application), thereby enabling a security-related function (e.g., an in-app payment) that was performed through an explicit intent within a local device (e.g., an electronic device) to be performed in the same or similar manner between different devices providing cloud services (e.g., an electronic device and a cloud server).

[0030] According to various embodiments, the configuration of the electronic device (100) is not limited to that shown in FIG. 2, and at least one configuration may be omitted, or at least one configuration (e.g., at least one of the components of the first electronic device (301) of FIG. 3 or the electronic device (700) of FIG. 7) may be added.

[0031]

[0032] FIG. 2 is a block diagram of an electronic device according to one embodiment.

[0033] According to one embodiment, an electronic device (200) (e.g., the second electronic device (303) of FIG. 3) (e.g., a cloud server) may include a communication circuit (210), a memory (220), and at least one processor (230).

[0034] The communication circuit (210) can transmit and receive information and / or data with at least one external device (e.g., the first electronic device (301) of FIG. 3 or the electronic device (700) of FIG. 7) (e.g., a local device (client device)). For example, the communication circuit (210) can receive a response to a request for execution of a specified application (e.g., a second application) (e.g., a cloud service request related to the specified application) and / or a request for an action from the external device. The communication circuit (210) can transmit cloud service data related to the application running on the external device (e.g., the second application) and / or a request for an action of another application included on the external device requested by the application running on the external device.

[0035] The memory (220) can store instructions that control the operation of the electronic device (200) when executed individually or collectively by at least one processor (230). For example, the instructions may be stored in one memory (220) or multiple memories (220). The memory (220) can store information and / or data related to the operations of the electronic device (200) at least temporarily. The memory (220) can store at least one application. For example, the memory (220) may include, but is not limited to, a game application. The at least one application may be an application already included in the electronic device (200), an application provided from an external device (e.g., a client device), and / or a third-party provided application (3 rd It can include a party application.

[0036] At least one processor (230) can control the operations of the electronic device (200) by executing instructions stored in memory (220) individually or collectively. For example, the operations described in this disclosure as being performed by the 'processor (230)' may be understood as being performed individually or collectively by at least one processor (230). For example, at least one processor (230) can control each of the operations of the electronic device (200) described below independently or collectively. According to one embodiment, at least one processor (230) may include circuits such as a CPU (central processing unit), MPU (micro processor unit), AP (application processor), CP (communication processor), SoC (system on chip), and / or IC (integrated circuit).

[0037] The processor (230) can execute a second application corresponding to a cloud service request based on a cloud service request related to a second application received from an external device.

[0038] According to one embodiment, the processor (230) can transmit cloud service data related to the second application to an external device through a communication circuit (210). For example, the processor (230) can transmit data related to the execution of the second application to an external device. The processor (230) can control the execution of the second application based on user input related to the second application received from an external device during the execution of the second application.

[0039] According to one embodiment, the processor (230) may recognize a request related to the first application of the second application during the execution of the second application. For example, the first application may be an application included in an external device rather than in the electronic device (200). The first application may include a payment-related application, an authentication-related application, and / or an application related to advertising (e.g., in-app advertising). For example, the first application may include at least one of an application, a service provider, or a process (or a process module) that includes logic for performing at least one function of the electronic device (200). For example, the processor (230) may recognize an in-app payment request of the first application during the execution of the second application. A request for an action may correspond to a specified data format (e.g., a second format). For example, the second format may be the same as the format used to transmit requests and / or responses between applications stored on the same device. For example, the second format may correspond to an explicit intent. For example, the processor (230) may recognize a request for an action related to the first application of the second application through an explicit intent. For example, the request for an action may include a package name representing the application to perform the action and / or a component name related to the action (e.g., activity and / or service).

[0040] According to one embodiment, the processor (230) can transmit a request for an action to an external device through a communication circuit (210). The processor (230) can convert the request for an action into a specified data format (e.g., a first format) and transmit it to the external device. The first format may correspond to a specification defined for data transmission between different devices. For example, the processor (230) can convert the request for an action into a specified file format (e.g., JSON format) and / or a specified data format (e.g., a stream of bytes) and transmit it to the external device.

[0041] According to one embodiment, the processor (230) may receive a response to a request for an action from an external device through a communication circuit (210). The response to the request for an action may include information related to the result of an action performed by the external device (e.g., a first application). The response received from the external device may correspond to a specified data format (e.g., a first format).

[0042] According to one embodiment, the processor (230) may transmit a response to a request for an action to a second application. For example, the processor (230) may convert the response received from an external device into a specified data format (e.g., a second format) and transmit it to the second application. The processor (230) may perform an action corresponding to the response through the second application.

[0043] According to various embodiments, the configuration of the electronic device (200) is not limited to that shown in FIG. 2, and at least one configuration may be omitted, or at least one configuration (e.g., at least one of the components of the second electronic device (303) of FIG. 3 or the electronic device (700) of FIG. 7) may be added.

[0044]

[0045] FIG. 3 illustrates a system according to one embodiment.

[0046] According to one embodiment, the system may include a first electronic device (301) (e.g., the electronic device (100) of FIG. 1 or the electronic device (700) of FIG. 7) (e.g., a client device) and a second electronic device (303) (e.g., the electronic device (200) of FIG. 2) (e.g., a cloud server). The operations of the first electronic device (301) described below may be understood as being performed by executing instructions stored in the memory of the first electronic device (301), either individually or collectively, by at least one processor of the first electronic device (301). The operations of the second electronic device (303) described below may be understood as being performed by executing instructions stored in the memory of the second electronic device (303), either individually or collectively, by at least one processor of the second electronic device (303).

[0047] According to one embodiment, the first electronic device (301) may include a first application (313) and a first delivery module (311).

[0048] According to one embodiment, the first application (313) may include an application related to payment (e.g., in-app payment), an application related to user authentication, and / or an application related to advertising (e.g., in-app advertising). For example, the first application (313) may perform the functions and / or roles of a service provider. For example, the first application (313) may perform a function corresponding to the request after receiving a request for an action from the second application (333). For convenience of explanation, the following description assumes that the first application (313) is a payment application, but is not limited thereto. For example, the first application (313) may not be included in the second electronic device (303).

[0049] According to one embodiment, the first electronic device (301) may provide cloud services in conjunction with the second electronic device (303). For example, the first electronic device (301) may request cloud services related to the second application (333) (e.g., a game application) from the second electronic device (303). The first electronic device (301) may receive execution data of the second application (333) executed by the second electronic device (303) from the second electronic device (303). For example, the first electronic device (301) may provide the same service as if the second application (333) were executed directly on the first electronic device (301), without executing the second application (333) directly on the first electronic device (301). For example, from the perspective of the first electronic device (301), the first delivery module (311) and the second electronic device (303) (e.g., the second delivery module (331) and the second application (333)) can operate like a virtual application stored in the first electronic device (301).

[0050] According to one embodiment, the first transmission module (311) can transmit requests and / or responses between an application (e.g., the first application (313)) and an external device (e.g., the second electronic device (303) (e.g., the second application (333))). For example, the first transmission module (311) can convert requests and / or responses between applications into a specified data format supported by the application (e.g., the first format) or a specified data format for data transmission between devices (e.g., the first electronic device (301) and the second electronic device (303)) (e.g., the second format) and transmit them to the first application (313) or the second electronic device (303).

[0051] According to one embodiment, the second electronic device (303) may include a second application (333) and a second delivery module (331).

[0052] According to one embodiment, the second application (333) may include at least one application that supports cloud services. For convenience of explanation, the second application (333) is assumed to be a game application, but is not limited thereto. For example, the second application (333) may be stored only in the second electronic device (303), or it may be stored in both the first electronic device (301) and the second electronic device (303).

[0053] According to one embodiment, the second electronic device (303) can execute the second application (333) in response to a cloud service request related to the second application (333) received from the first electronic device (301). The second electronic device (303) can transmit execution data of the second application (333) to the first electronic device (301). The second electronic device (303) can transmit data related to the execution of the second application (333) to the first electronic device (301) in real time so that the first electronic device (301) can provide the same service as if the second application (333) had been executed locally (on the first electronic device (301)).

[0054] According to one embodiment, the second delivery module (331) can transmit requests and / or responses between an application (e.g., the second application (333)) and an external device (e.g., the first electronic device (301) (e.g., the first application (313))). For example, the first delivery module (311) can convert requests and / or responses between applications into a specified data format supported by the application (e.g., the first format) or a specified data format for data transmission between devices (e.g., the first electronic device (301) and the second electronic device (303)) (e.g., the second format) and transmit them to the first electronic device (301) or the second application (333).

[0055] According to one embodiment, in operation 31, while the second electronic device (303) is running the second application (333), it may receive user input related to the second application (333) from the first electronic device (301). For example, the user input may include an input requesting an in-app payment of the second application (333). The second application (333) (e.g., an in-app payment module) may transmit a request for an action related to the first application (313) (e.g., a payment application) to the second delivery module (331) based on the user input. According to one embodiment, the in-app payment module (335) may include an in-app payment SDK (software development kit). For example, the in-app payment module (335) may be provided in the form of a library (e.g., an in-app purchase (IAP) library). The in-app payment module (335) may include an application programming interface (API) that can request an in-app payment function. The in-app payment module (335) can be configured to manage actions for in-app payments, process payment-related information, and provide the user with a result regarding the success or failure of the payment.

[0056] According to one embodiment, a request for an action may include information specifying an application to perform the action (e.g., a first application (313)) and an action (e.g., an in-app payment). For example, a request for an action may include a package name representing the application to perform the action and / or a component name associated with the action (e.g., an activity and / or a service). A request for an action may include an explicit intent. For example, a second application (333) may call a specific action (e.g., a payment) of the first application (313) through an explicit intent. For example, if the second application (333) is a game application and the request for an action is an in-app payment request, the request for an action may include API (application programming interface) information representing the in-app payment request, a package name representing the target application information (e.g., the second application (333)), a component name representing the action, payment target information (e.g., information on game items to be paid), information for checking payment validity (e.g., information for tracking the payment process including transaction information and / or user-related information), information on a specified operation mode (e.g., API call mode), and / or version information related to the in-app payment module (335) (e.g., SDK (software development kit) version information), and the information included in the request for an action is not limited to those listed above.

[0057] According to one embodiment, a request for an action transmitted by the second application (333) to the second delivery module (331) may correspond to a specified data format (e.g., a second format). For example, the second format may be the same as the format used to transmit requests and / or responses between applications stored on the same device.

[0058] According to one embodiment, in operation 32, the second delivery module (331) can convert the request for an action into a specified data format (e.g., a first format) and transmit it to the first electronic device (301). For example, the first format may correspond to a specification defined for data transmission between different devices. For example, the second delivery module (331) can convert the request for an action into a specified file format (e.g., JSON format) and / or serialize the information contained in the request for an action (e.g., convert it into a stream of bytes) and transmit it to the first electronic device (301).

[0059] According to one embodiment, in operation 33, the first delivery module (311) can convert a request for action received from the second electronic device (303) into a specified format (e.g., a second format) and deliver it to the first application (313). For example, the first delivery module (311) can deliver the request for action of the first application (313) through an explicit intent. The request for action delivered by the first delivery module (311) to the first application (313) may substantially correspond to the request for action delivered by the second application (333) to the first delivery module (311). For example, the first application (313) may receive the request for action in substantially the same manner as receiving the request for action from the second application (333) stored in the same device (e.g., the first electronic device (301)).

[0060] According to one embodiment, in operation 34, the first application (313) may transmit a response generated based on the result of performing a request for an action to the first delivery module (311). The response may correspond to a specified data format (e.g., a second format). For example, the first application (313) may perform an action (e.g., an in-app payment) based at least part of user input related to the execution of an action received by the first electronic device (301) (e.g., payment-related user input).

[0061] According to one embodiment, in operation 35, the first delivery module (311) can deliver the response to the second electronic device (303). For example, the first delivery module (311) can deliver the response to the second electronic device (303) by converting it into a specified data format (e.g., a first format). For example, the first format may correspond to a specification defined for data transmission between different devices. For example, the first delivery module (311) can deliver the request for an action to the second electronic device (303) by converting it into a specified file format (e.g., JSON format) and / or serializing the information contained in the request for an action (e.g., converting it into a stream of bytes).

[0062] According to one embodiment, in operation 36, the second delivery module (331) may convert the received response into a specified data format (e.g., a second format) and deliver it to the second application (333). The response delivered by the second delivery module (331) to the second application (333) may substantially correspond to the response delivered by the first application (313) to the first delivery module (311). For example, the second application (333) may receive the response in substantially the same manner as it received the response from the first application (313) stored in the same device (e.g., a second electronic device (303)). For example, the second application (333) may perform a specified action based on the response.

[0063] A system according to one embodiment can provide a designated service (e.g., in-app payment) by linking the applications together in substantially the same manner as when the first application (313) and the second application (333) are stored on the same device. In providing a cloud service, a system according to one embodiment can provide the same user experience to the user even while providing the cloud service by providing the same service as running the application on a local device, without the need to develop and / or install a separate application for the cloud service for the designated service (e.g., in-app payment). A system according to one embodiment can provide services requiring security (e.g., payment or authentication) while providing the cloud service without storing personal information (e.g., account information, security information, and / or payment-related information) outside the local device (server). A system according to one embodiment can provide the same service by storing the same application as the existing one on the server, rather than a separately modified application, by providing the linkage between applications provided on the local device in the same manner even during the cloud service.

[0064]

[0065] FIG. 4 is a flowchart of a method for providing a cloud service according to one embodiment.

[0066] According to one embodiment, in operation 410, an electronic device (e.g., electronic device (100) of FIG. 1, the first electronic device (301) of FIG. 3, or the electronic device (700) of FIG. 7) may request a cloud service associated with a second application from an external device (e.g., electronic device (200) of FIG. 2 or the second electronic device (303) of FIG. 3). For example, the second application may be stored in the external electronic device and / or the electronic device. For example, the second application may include at least one application (e.g., a game application) that supports the cloud service.

[0067] According to one embodiment, in operation 420, the electronic device may receive cloud service data related to a second application executed by an external device from an external device. For example, the cloud service data may include data related to the execution of the application.

[0068] According to one embodiment, in operation 430, the electronic device may display an execution screen of the second application based on cloud service data. For example, the execution screen of the second application may include an indication indicating that the cloud service is in progress. For example, the electronic device may transmit user input related to the second application to an external device while the second application is running, and receive execution data of the second application manipulated in real time based on user input from the external device. For example, if the second application is a game application, the electronic device may provide the same service as when a user runs a game application on the electronic device based on user input.

[0069] According to one embodiment, in operation 440, the electronic device may receive a request for an action related to the first application of the second application from an external device. For example, the first application may be included in the electronic device and may not be included in the external device. The first application may include a payment-related application, an authentication-related application, and / or an application related to advertising (e.g., in-app advertising). For example, the received request for an action may correspond to a specified data format (e.g., a first format). For example, the first format may correspond to a specification defined for data transmission between different devices. For example, the received request for an action may have a specified file format (e.g., JSON format) and / or a specified data format (e.g., a stream of bytes). The first electronic device may convert the received request for an action into a specified data format (e.g., a second format) and transmit it to the first application. For example, the second format may be the same as the format used to transmit requests and / or responses between applications stored on the same device. For example, the second format may correspond to an explicit intent. For example, an electronic device may transmit a request for an action of the second format to the first application via an explicit intent. For example, the request for an action may include a package name representing the application to perform the action and / or a component name associated with the action (e.g., an activity and / or a service).

[0070] According to one embodiment, in operation 450, the electronic device may perform an action corresponding to a request for an action through a first application. For example, if the request for an action is an in-app payment request through the first application, the electronic device may perform an in-app payment through the first application. The electronic device may receive user input related to the action and perform an action corresponding to a request for an action through the first application based at least partially on the received user input.

[0071] According to one embodiment, in operation 460, the electronic device may transmit a response to a request for an action to an external device based on the result of performing the action. For example, the response may include information related to the result of performing the action (e.g., payment success or payment failure). For example, the electronic device may obtain a response corresponding to the result of performing the action from a first application. For example, the response obtained from the first application may correspond to a specified data format (e.g., a second format). The electronic device may convert the response into a specified data format (e.g., a first format) and transmit it to an external device.

[0072] According to various embodiments, the order of the operations of FIG. 4 may be changed or at least some of the operations may be performed at least simultaneously, and at least some of the operations of FIG. 4 may be omitted or at least one operation may be added.

[0073]

[0074] FIG. 5 is a flowchart of a method for providing a cloud service according to one embodiment. In the following, descriptions that overlap with FIG. 4 are omitted or briefly described.

[0075] According to one embodiment, in operation 510, an electronic device (e.g., the electronic device (200) of FIG. 2 or the second electronic device (303) of FIG. 3) may execute a second application corresponding to a cloud service request based on a cloud service request related to a second application received from an external device (e.g., the electronic device (100) of FIG. 1, the first electronic device (301) of FIG. 3, or the electronic device (700) of FIG. 7). For example, the second application may include at least one application (e.g., a game application) that supports cloud services.

[0076] According to one embodiment, in operation 520, the electronic device may transmit cloud service data related to the second application to an external device. For example, the electronic device may transmit data related to the execution of the second application to the external device. The electronic device may control the execution of the second application based on user input related to the second application received from the external device during the execution of the second application.

[0077] According to one embodiment, in operation 530, the electronic device may recognize a request related to the first application of the second application during the execution of the second application. For example, the first application may not be included in the electronic device but may be an application included in an external device. The first application may include a payment-related application, an authentication-related application, and / or an application related to advertising (e.g., in-app advertising). For example, the electronic device may recognize an in-app payment request of the first application during the execution of the second application. A request for an action may correspond to a specified data format (e.g., a second format). For example, the second format may be the same as the format used to transmit requests and / or responses between applications stored on the same device. For example, the second format may correspond to an explicit intent. For example, the electronic device may recognize a request for an action related to the first application of the second application through an explicit intent. For example, a request for an action may include a package name representing the application to perform the action and / or a component name associated with the action (e.g., an activity and / or a service).

[0078] According to one embodiment, in operation 540, the electronic device may transmit a request for an action to an external device. The electronic device may transmit the request for an action to the external device by converting it into a specified data format (e.g., a first format). The first format may correspond to a specification defined for data transmission between different devices. For example, the electronic device may transmit the request for an action to the external device by converting it into a specified file format (e.g., JSON format) and / or a specified data format (e.g., a stream of bytes).

[0079] According to one embodiment, in operation 550, the electronic device may receive a response to a request for an action from an external device. The response to the request for an action may include information related to the result of an action performed by the external device (e.g., a first application). The response received from the external device may correspond to a specified data format (e.g., a first format).

[0080] According to one embodiment, in operation 560, the electronic device may transmit a response to a request for an action to a second application. For example, the electronic device may convert the response received from an external device into a specified data format (e.g., a second format) and transmit it to the second application. The electronic device may perform an action corresponding to the response through the second application.

[0081] According to various embodiments, the order of the operations of FIG. 5 may be changed, or at least some of the operations may be performed at least simultaneously, and at least some of the operations of FIG. 5 may be omitted or at least one operation may be added.

[0082]

[0083] FIGS. 6a to 6c illustrate a cloud service provision screen according to one embodiment. For example, when a first electronic device (e.g., the electronic device (100) of FIG. 1, the first electronic device (301) of FIG. 3, or the electronic device (700) of FIG. 7) (e.g., a local device (client device)) requests a cloud service for a second application, a second electronic device (e.g., the electronic device (200) of FIG. 2, or the second electronic device (303) of FIG. 3) (e.g., a server) executes the second application and can provide data related to the execution of the second application to the first electronic device in real time. Based on the data related to the execution of the second application received from the second electronic device, the first electronic device may display an execution screen of the second application. FIGS. 6a to 6c describe a case where the second application is a game application and performs in-app payment for convenience of explanation, but the embodiments of the present disclosure are not limited thereto.

[0084] The first screen (601) represents a case where the first electronic device displays an execution screen related to in-app payments while running a game application through a cloud service. The first screen (601) may include an indication (610) indicating that the game application is running through a cloud service. Regarding in-app payments, the first screen (601) may include a first area (620) containing payable item items, payment-related information, and amount information.

[0085] The second screen (603) represents a screen for proceeding with payment for an item selected based on user input. The second screen (603) may include a second area (630) indicating that payment is in progress, a third area (640) containing payment-related information (e.g., payment rules, refund rules, and / or event information), a fourth area (650) indicating a payment method (e.g., payment application information to perform in-app payment), and a fifth area (660) for receiving user input for payment approval.

[0086] The third screen (605) displays a screen indicating the payment result. For example, the third screen (605) may include an indication (670) indicating that the game application is running through a cloud service. The third screen (605) may include a sixth area (680) indicating the payment result. For example, the sixth area (680) of FIG. 6c is illustrated as including information indicating that the payment failed, but may include information indicating that the payment was approved upon payment approval.

[0087] According to various embodiments, the number and contents of the regions illustrated in FIGS. 6a through 6c are not limited to those illustrated and may be changed. According to embodiments of the present disclosure, the first electronic device may display the same execution screen as when the second application (e.g., a game application) is executed via a cloud service, except for an indication (610, 670) indicating that the cloud service is active. The user may obtain the same user experience as when the same application is executed on a local device (the first electronic device), even when the second application is executed via a cloud service and an action (e.g., an in-app payment) is executed via a cloud service.

[0088]

[0089] An electronic device according to one embodiment of the present disclosure may include a communication circuit, a display, a memory for storing a first application and instructions, and at least one processor.

[0090] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may request a cloud service related to a second application from an external device through the communication circuit.

[0091] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may receive cloud service data related to the second application executed by the external device from the external device.

[0092] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may display the execution screen of the second application through the display based on the cloud service data.

[0093] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may receive a request from the external device for an action related to the first application of the second application.

[0094] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may perform an action corresponding to a request for the action through the first application.

[0095] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may transmit a response to a request for the action to the external device based on the result of performing the action.

[0096] The first application may include at least one of a payment-related application or an authentication-related application. The action may include at least one of a payment operation related to the second application or a user authentication operation related to the second application.

[0097] The request for the above action may include information specifying the first application and the action. The received request for the action may have a first format designated for data transmission between the electronic device and the external device.

[0098] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may obtain a response to a request for the action through the first application.

[0099] The above instructions may, when executed individually or collectively by the at least one processor, convert the response to the request for the acquired action into the first format and transmit it to the external device.

[0100] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may convert the request for the received action into a specified second format and transmit it to the first application.

[0101] The above instructions may, when executed individually or collectively by the at least one processor, obtain the result of performing the action corresponding to the request for the action from the first application.

[0102] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may receive user input related to the execution of the action.

[0103] The above instructions can perform the action through the first application based on at least some of the user input when executed individually or collectively by the at least one processor.

[0104] The execution screen of the second application may include an indication that the second application is being executed based on the cloud service.

[0105] A system for providing cloud services according to one embodiment of the present disclosure may include a first electronic device including a first application and a first delivery module and a second electronic device including a second application and a second delivery module.

[0106] The first electronic device may request a cloud service related to the second application from the second electronic device. The first electronic device may receive cloud service data related to the second application from the second electronic device. Based on the cloud service data, the first electronic device may display an execution screen of the second application. The first electronic device may receive a request for an action related to the first application of the second application from the second electronic device through the first delivery module. The request for the action may have a designated first format. The first electronic device may convert the request for the action into a designated second format and deliver it to the first application. The first electronic device may perform an action corresponding to the request for the action through the first application. The first electronic device may generate a response to the request for the action based on the result of performing the action. The first electronic device may convert the response into a designated first format and transmit it to the second electronic device through the first delivery module.

[0107] The second electronic device may execute the second application in response to the cloud service request received from the first electronic device. The second electronic device may transmit the cloud service data related to the execution of the second application to the first electronic device. During the execution of the second application, the second electronic device may, through the second transmission module, convert a request for an action related to the first application of the second application into the first format and transmit it to the first electronic device. The second electronic device may, through the second transmission module, convert a response to the request for an action received from the first electronic device into the second format and transmit it to the second application.

[0108] The first application may include at least one of a payment-related application or an authentication-related application. The action may include at least one of a payment operation related to the second application or a user authentication operation related to the second application. A request for the action may include information specifying the first application and the action.

[0109] The first electronic device may receive user input related to the execution of the action. The first electronic device may perform the action through the first application based at least in part on the user input.

[0110] A method for providing a cloud service of an electronic device including a first application according to one embodiment of the present disclosure may include an operation of requesting a cloud service related to a second application from an external device. The method may include an operation of receiving cloud service data related to the second application executed by the external device from the external device. The method may include an operation of displaying an execution screen of the second application based on the cloud service data. The method may include an operation of receiving a request for an action related to the first application of the second application from the external device. The method may include an operation of performing an action corresponding to the request for the action through the first application. The method may include an operation of transmitting a response to the request for the action to the external device based on the result of performing the action.

[0111] The first application may include at least one of a payment-related application or an authentication-related application. The action may include at least one of a payment operation related to the second application or a user authentication operation related to the second application.

[0112] The request for the above action may include information specifying the first application and the action. The request for the action may have a first format specified for data transmission between the electronic device and the external device.

[0113] The operation of transmitting a response to a request for the above action may include converting the response to the request for the above action into the first format and transmitting it to the external device.

[0114] The operation of performing the above action may include converting the request for the above action into a specified second format and transmitting it to the first application. The operation of performing the above action may include obtaining the result of performing the above action corresponding to the request for the above action from the first application.

[0115] The operation of performing the above action may include receiving user input related to the execution of the above action. The operation of performing the above action may include performing the above action through the first application based at least partially on the user input.

[0116] The execution screen of the second application may include an indication that the second application is being executed based on the cloud service.

[0117] According to embodiments of the present disclosure, functions available in the local device execution environment (e.g., in-app payments) can be provided identically in a virtual environment (e.g., a cloud service provider environment) by using an application installed on a local device without installing a separate dedicated application. According to embodiments of the present disclosure, services and / or functions related to security information (e.g., in-app payments) can be provided by using personal information stored on a local device without storing personal information requiring security in a virtual environment (e.g., a cloud server). According to embodiments of the present disclosure, the same functions and / or services can be provided in a virtual environment using the same application as on a local device without the need to modify an application running on a local device for use in a virtual environment (e.g., a cloud environment).

[0118]

[0119] FIG. 7 is a block diagram of an exemplary electronic device (700) capable of performing the operations described in this document.

[0120] Referring to FIG. 7, the electronic device (700) may be one of various forms of electronic devices, such as a notebook (790), smartphones (791) having various form factors (e.g., a bar-type smartphone (791-1), a foldable-type smartphone (791-2), or a sliderable (or rollable)-type smartphone (791-3)), a tablet (792), a cellular phone (not shown), and other similar computing devices (not shown). The components, their relationships, and their functions illustrated in FIG. 7 are illustrative only and are not intended to limit the implementations described or claimed herein. The electronic device (700) may be referred to as a mobile device, a user device, a multifunction device, a portable device, or a server.

[0121] The electronic device (700) may include components comprising at least one processor (710) (hereinafter referred to as processor (710)), at least one memory (720) (hereinafter referred to as memory (720)), at least one display (740) (hereinafter referred to as display (740)), at least one image sensor (750) (hereinafter referred to as image sensor (750)), at least one communication circuit (760) (hereinafter referred to as communication circuit (760)), and / or at least one sensor (770) (hereinafter referred to as sensor (770)). The components are merely exemplary. For example, the electronic device (700) may include other components (e.g., power management integrated circuitry (PMIC), audio processing circuit, antenna, rechargeable battery, or input / output interface). For example, some components may be omitted from the electronic device (700). For example, some components may be integrated into a single component.

[0122] The processor (710) may be implemented as one or more integrated circuit (or circuitry) chips and may perform various data processing operations. The processor (710) may include at least one electrical circuit and may process instructions (or programs, data, etc.) stored in memory (720) individually or collectively in a distributed manner. The processor (710) may include a processor assembly comprising one or more processing circuits. The processor (710) may include any processing circuit that is operative to control the performance and operations of one or more components of the electronic device (700) (e.g., memory (720), display (740), image sensor (750), communication circuit (760), and / or sensor (770)). For example, the processor (710) (e.g., application processor (AP)) may be implemented as a system on chip (SoC) (e.g., a single chip or chipset). For example, the processor (710) may be implemented with a plurality of cores (or at least one core circuit), a plurality of chips, or a plurality of chipsets. For example, the processor (710) may include one or more processing circuits. For example, the processor (710) may include one or more processing circuits configured to perform the various functions of the present disclosure individually and / or collectively. As an example without limitation, at least a portion of the processor (710) may be included in a first chip of the electronic device (700), and at least another portion of the processor (710) may be included in a second chip of the electronic device (700) different from the first chip of the electronic device (700).

[0123] For example, the processor (710) may include a central processing unit (CPU) (711), a graphics processing unit (GPU) (712), a neural processing unit (NPU) (713), an image signal processor (ISP) (714), a display controller (715), a memory controller (716), a storage controller (717), a communication processor (CP) (718), and / or a sensor interface (719). These components of the processor (710) are merely exemplary. For example, the processor (710) may include other components. For example, some components of the processor (710) may be omitted from the processor (710). For example, some components of the processor (710) may be included as separate components of the electronic device (700) outside of the processor (710). For example, some components of the processor (710) (e.g., memory controller (716)) may be included in other components (e.g., at least part of memory (720), an interface (e.g. available for connection to at least one component of the electronic device (100)), a display (740) and / or an image sensor (750)).

[0124] The processor (710) may cause other components of the electronic device (700) to perform various operations by executing instructions stored in memory (720). The CPU (711) (or central processing circuit) may be configured to control the components of the processor (710) based on the execution of instructions stored in memory (720) (e.g., volatile memory (721) and / or non-volatile memory (722)). The GPU (712) (or graphics processing circuit) may be configured to execute parallel operations (e.g., rendering). The NPU (713) (or neural processing circuit, or AI (artificial intelligence) chip) may be configured to execute operations for an artificial intelligence model (e.g., convolution computation). An ISP (714) (or image signal processing circuit) may be configured to process a raw image acquired through an image sensor (750) into a format suitable for a component within the electronic device (700) or a component of the processor (710). A display controller (715) (or display control circuit, or DPU (display processing unit)) may be configured to process an image acquired from a CPU (711), GPU (712), ISP (714), or memory (720) (e.g., volatile memory (721)) into a format suitable for a display (740). A memory controller (716) (or memory control circuit) may be configured to control reading data from volatile memory (721) and writing data to volatile memory (721). A storage controller (717) (or storage control circuit) may be configured to control reading data from non-volatile memory (722) and writing data to non-volatile memory (722).The CP (718) (communication processing circuit) may be configured to process data obtained from a component of the processor (710) into a format suitable for transmitting to another electronic device via the communication circuit (760), or to process data obtained from another electronic device via the communication circuit (760) into a format suitable for processing by the component of the processor (710). For example, the communication circuit (760) may include one or more communication circuits. The sensor interface (719) (or sensing data processing circuit, sensor hub) may be configured to process data regarding the state of the electronic device (700) and / or the state around the electronic device (700), obtained through the sensor (770), into a format suitable for the component of the processor (710).

[0125] Memory (720) may include one or more storage media (or one or more storage devices). For example, memory (720) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, a permanent memory such as flash memory, read-only memory (ROM) (e.g., non-volatile memory (722)), a semi-permanent memory such as random access memory (RAM) (e.g., volatile memory (721)), any other suitable type of storage (or storage assembly), or any combination thereof. Memory (720) may include a cache memory, which is one or more different types of memory used to temporarily store data for a function or feature of the electronic device (700). As an example not limited to, the cache memory may be included within the processor (710). The memory (720) may be fixedly embedded within the electronic device (700) or incorporated into one or more suitable types of components (e.g., a SIM (subscriber identity module) card and / or an SD (secure digital) card) that can be repeatedly inserted into and removed from the electronic device (700).

[0126] For example, memory (720) may store one or more software applications, such as operating system (or system) software applications, firmware software applications, driver software applications, plugin (e.g., add-in, add-on, and / or applet) software applications, and / or any other suitable software applications. For example, the one or more software applications may include instructions executable by the processor (710). For example, memory (720) may store instructions that can be called by an application programming interface (API). For example, memory (720) may store instructions within a library.

[0127]

[0128] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "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 "at least one of A, B, or C" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as "coupled" or "connected" to another (e.g., 2nd) component, with or without the terms "functionally" or "communicationly," it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0129] As used in the various embodiments of this document, the term “module” may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions.

[0130] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In an electronic device, Communication circuit; display; Memory for storing first applications and instructions; and It includes at least one processor, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Through the above communication circuit, a cloud service related to the second application is requested from an external device, and Receive cloud service data related to the second application executed by the external device from the external device, and Based on the above cloud service data, the execution screen of the above second application is displayed through the above display, and Receiving a request for an action related to the first application of the second application from the external device, and Perform an action corresponding to the request for the action through the first application above, and An electronic device that transmits a response to a request for the action to an external device based on the result of performing the action.

2. In Claim 1, The first application above includes at least one of a payment-related application or an authentication-related application, and The above action is an electronic device comprising at least one of a payment action related to the second application or a user authentication action related to the second application.

3. In Claim 1, An electronic device comprising information specifying the first application and the action, for requesting the action.

4. In Claim 1, The request for the received action is an electronic device having a first format designated for data transmission between the electronic device and the external device.

5. In Claim 4, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Obtain a response to the request for the action through the first application above, and An electronic device that converts a response to a request for the above-mentioned acquired action into the above-mentioned first format and transmits it to the above-mentioned external device.

6. In Claim 4, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Converting the request for the received action into a specified second format and transmitting it to the first application, An electronic device that obtains the result of performing the action corresponding to the request for the action from the first application.

7. In Claim 1, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Receiving user input related to the execution of the above action, and An electronic device that enables the action to be performed through the first application based on at least part of the user input.

8. In Claim 1, The execution screen of the second application described above is an electronic device including an indication that the second application is being executed based on the cloud service.

9. In a system providing cloud services, A first electronic device comprising a first application and a first delivery module; and A second electronic device including a second application and a second delivery module, and The above first electronic device is, Requesting a cloud service related to the second application to the second electronic device, and Receiving cloud service data related to the second application from the second electronic device, and Based on the cloud service data above, display the execution screen of the second application above, and A request for an action related to the first application of the second application is received from the second electronic device through the first transmission module, and the request for the action has a specified first format. Converting the request for the above action into a specified second format and transmitting it to the first application, Perform an action corresponding to the request for the action through the first application above, and Based on the result of performing the above action, generate a response to the request for the above action, and Through the first transmission module, the response is configured to be converted into a specified first format and transmitted to the second electronic device, and The second electronic device above is, Executing the second application in response to the cloud service request received from the first electronic device, and transmitting the cloud service data related to the execution of the second application to the first electronic device, During the execution of the second application, a request for an action related to the first application of the second application is converted into the first format and transmitted to the first electronic device through the second transmission module, and A system configured to convert a response to a request for the action received from the first electronic device into the second format and transmit it to the second application through the second transmission module.

10. A method for providing a cloud service of an electronic device including a first application, An action of requesting a cloud service related to a second application from an external device; The operation of receiving cloud service data related to the second application executed by the external device from the external device; An operation to display the execution screen of the second application based on the cloud service data above; The operation of receiving a request for an action related to the first application of the second application from the external device; An action of performing an action corresponding to a request for the action through the first application; and A method comprising the operation of transmitting a response to a request for the action to an external device based on the result of performing the above action.

11. In Claim 10, A method for requesting the above action that includes information specifying the first application and the action.

12. In Claim 10, A method for requesting the above action having a first format designated for data transmission between the electronic device and the external device.

13. In Claim 10, The operation of transmitting a response to the request for the above action is, A method comprising converting a response to a request for the above action into the above first format and transmitting it to the above external device.

14. In Claim 10, The action of performing the above action is, The operation of converting the request for the above action into a specified second format and transmitting it to the first application; and A method comprising the operation of obtaining the result of performing the action corresponding to the request for the action from the first application.

15. In Claim 10, The action of performing the above action is, An action of receiving user input related to the execution of the above action; and A method comprising an action of performing the action through the first application based on at least part of the user input.

Images