Electronic device and method for sharing accessibility setting

Abstract

This electronic device may comprise a communication circuit, processor(s), and a memory for storing instructions. The instructions may cause, when executed by the processor(s), the electronic device to: log in to a server with a user account; while the electronic device is logged in with the user account, receive, through the communication circuit, an accessibility function list indicating at least one accessibility function being used by a first electronic device, wherein the first electronic device has been logged in to the server with the user account; identify at least one accessibility function usable by the electronic device in the accessibility function list; identify, among the at least one accessibility function usable by the electronic device, a first accessibility function not being used by the electronic device; and apply the first accessibility function to the electronic device.

Description

Electronic device and method for sharing accessibility settings

[0001] Certain exemplary embodiments relate to electronic devices and / or methods that share accessibility settings.

[0002] Various services and additional functions provided through user terminals, such as electronic devices like smartphones, are gradually increasing. To enhance the utility value of these electronic devices and satisfy the needs of diverse users, telecommunications service providers and electronic device manufacturers are competitively developing electronic devices that offer a wide range of functions. Consequently, the various functions provided through these electronic devices are also becoming increasingly sophisticated.

[0003] With the advancement of wireless communication technology, devices utilizing artificial intelligence (AI) are being widely adopted. For example, home appliances connected to a network via the Internet of Things (IoT) technology can utilize artificial intelligence. IoT technology can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated from devices. Through the convergence and integration of existing internet technologies with various industries, IoT technology can be applied to fields such as smart homes, smart buildings, smart cities, smart cars, and smart appliances.

[0004] Homes are equipped with various home appliances for user convenience. Various services utilizing IoT technology are being proposed to make the operation and control of these appliances more convenient. Home network technology can provide diverse services to users within the household through the home network. For example, users can control various controlled devices (e.g., home appliances equipped with IoT technology) that constitute the home network using personal electronic devices (e.g., smartphones). Users may desire to receive a wider range of services to control these controlled devices. Accordingly, there is a demand for the development of various technologies that manage controlled devices by reflecting user intentions.

[0005] 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.

[0006] Certain exemplary embodiments may provide an electronic device and method for sharing accessibility settings.

[0007] Certain exemplary embodiments may provide an electronic device and a method that transmit a list of accessibility features of an electronic device and user account information to a peripheral device so that the peripheral device applies the accessibility settings of the electronic device.

[0008] A second electronic device according to an exemplary embodiment of the present disclosure may include at least one processor comprising a communication circuit and a processing circuit, and a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the second electronic device may: log in to a server with a user account through the communication circuit. When the instructions are executed individually or collectively by the at least one processor, the second electronic device may: receive through the communication circuit an accessibility feature list indicating at least one accessibility feature in use by the first electronic device while the second electronic device is logged in to the user account, wherein the first electronic device is logged in to the server with the user account. When the instructions are executed individually or collectively by the at least one processor, the second electronic device may: identify at least one accessibility feature available to the second electronic device from the accessibility feature list. When the above instructions are executed individually or collectively by the at least one processor, the second electronic device may: identify a first accessibility function that is not in use by the second electronic device among at least one accessibility function available to the second electronic device. When the above instructions are executed individually or collectively by the at least one processor, the second electronic device may: apply the first accessibility function to the second electronic device.

[0009] A server according to an exemplary embodiment may include at least one processor comprising a communication circuit and a processing circuit, and a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the server may identify that a first electronic device is logged in to a user account. When the instructions are executed individually or collectively by the at least one processor, the server may identify that a second electronic device is logged in to the user account. When the instructions are executed individually or collectively by the at least one processor, the server may receive, through the communication circuit, a first accessibility function list indicating at least one accessibility function in use by the first electronic device while the first electronic device and the second electronic device are logged in to the user account. When the above instructions are executed individually or collectively by the at least one processor, the server may receive, through the communication circuit, a second accessibility function list indicating at least one accessibility function in use by the second electronic device while the first electronic device and the second electronic device are logged in with the user account. When the above instructions are executed individually or collectively by the at least one processor, the server may identify at least one accessibility function available to the second electronic device from the first accessibility function list. When the above instructions are executed individually or collectively by the at least one processor, the server may identify, based on the second accessibility function list, a first accessibility function that is not in use by the second electronic device among the identified at least one accessibility function.When the above instructions are executed individually or collectively by the at least one processor, the server may transmit an accessibility setting instruction to the second electronic device through the communication circuit, which instructs the application of the identified first accessibility function.

[0010] A first electronic device according to an exemplary embodiment may include at least one processor comprising a communication circuit and a processing circuit, and a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the first electronic device may identify that the second electronic device is logged in to the user account while the first electronic device is logged in to the server as a user account based on the execution of an application. When the instructions are executed individually or collectively by the at least one processor, the first electronic device may transmit an accessibility function list indicating at least one accessibility function in use by the first electronic device to the server or the second electronic device through the communication circuit, based on identifying that the second electronic device is logged in to the user account. When the above instructions are executed individually or collectively by the at least one processor, the first electronic device may: after transmitting the accessibility function list, receive accessibility setting sharing information representing a first accessibility function among the at least one accessibility function from the server or the second electronic device through the communication circuit. When the above instructions are executed individually or collectively by the at least one processor, the first electronic device may: after displaying a user interface including the accessibility setting sharing information, receive user input accepting to apply the first accessibility function to the second electronic device through the user interface.When the above instructions are executed individually or collectively by the at least one processor, the first electronic device may transmit information accepting the application of the first accessibility function to the second electronic device, either through the server or directly to the second electronic device, based on receiving the user input.

[0011] A method by a second electronic device according to an exemplary embodiment may include the action of logging into a server with a user account; the action of obtaining an accessibility function list representing at least one accessibility function in use by a first electronic device while the second electronic device is logged into the user account, wherein the first electronic device is logged into the server with the user account and the action of identifying at least one accessibility function available to the second electronic device from the accessibility function list; the action of identifying a first accessibility function not in use by the second electronic device among at least one accessibility function available to the second electronic device; and the action of applying the first accessibility function to the second electronic device.

[0012] A method by a server according to an exemplary embodiment may include: identifying that a first electronic device is logged in to a user account; identifying that a second electronic device is logged in to the user account; receiving a first accessibility function list indicating at least one accessibility function in use by the first electronic device while the first electronic device and the second electronic device are logged in to the user account; receiving a second accessibility function list indicating at least one accessibility function in use by the second electronic device while the first electronic device and the second electronic device are logged in to the user account; identifying at least one accessibility function available to the second electronic device from the first accessibility function list; identifying, based on the second accessibility function list, a first accessibility function not in use by the second electronic device among the identified at least one accessibility function; and transmitting an accessibility setting instruction to the second electronic device instructing to apply the identified first accessibility function.

[0013] In a non-transient computer-readable storage medium storing one or more programs according to an exemplary embodiment, the one or more programs may include instructions that, when executed individually or collectively by at least one processor, cause a second electronic device to: log in to a server with a user account, and receive through the communication circuit an accessibility function list indicating at least one accessibility function in use by a first electronic device while the second electronic device is logged in with the user account; wherein the first electronic device is logged in to the server with the user account, identifies at least one accessibility function available to the second electronic device from the accessibility function list, identifies a first accessibility function not in use by the second electronic device among at least one accessibility function available to the second electronic device, and apply the first accessibility function to the second electronic device.

[0014] In a non-transient computer-readable storage medium storing one or more programs according to an exemplary embodiment, the one or more programs may include instructions that, when executed individually or collectively by at least one processor, cause a server to: identify that a first electronic device is logged in to a user account; identify that a second electronic device is logged in to the user account; receive a first accessibility function list indicating at least one accessibility function in use by the first electronic device while the first electronic device and the second electronic device are logged in to the user account; receive a second accessibility function list indicating at least one accessibility function in use by the second electronic device while the first electronic device and the second electronic device are logged in to the user account; identify at least one accessibility function available to the second electronic device from the first accessibility function list; identify, based on the second accessibility function list, a first accessibility function not in use by the second electronic device among the identified at least one accessibility function; and transmit an accessibility setting instruction to the second electronic device instructing to apply the identified first accessibility function.

[0015] In a non-transient computer-readable storage medium storing one or more programs according to an exemplary embodiment, the one or more programs may include instructions that, when executed individually or collectively by at least one processor, cause a first electronic device to: identify that a second electronic device is logged in to the user account while the first electronic device is logged in to the server as a user account based on the execution of an application; based on identifying that the second electronic device is logged in to the user account, transmit an accessibility function list representing at least one accessibility function in use by the first electronic device to the server or the second electronic device; after transmitting the accessibility function list, receive accessibility setting sharing information representing a first accessibility function among the at least one accessibility function from the server or the second electronic device; after displaying a user interface including the accessibility setting sharing information, receive a user input accepting to apply the first accessibility function to the second electronic device through the user interface; and based on receiving the user input, transmit information accepting to apply the first accessibility function to the second electronic device through the server or directly to the second electronic device.

[0016] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by those skilled in the art from the description below.

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

[0018] FIG. 1 illustrates an IoT (internet of things) system according to various exemplary embodiments.

[0019] FIG. 2 is a block diagram of an electronic device in a network environment according to various exemplary embodiments.

[0020] FIG. 3 is a diagram illustrating a network including devices to be controlled according to an exemplary embodiment.

[0021] FIG. 4a is a block diagram illustrating the configuration of a second electronic device according to an exemplary embodiment.

[0022] FIG. 4b is a block diagram illustrating the configuration of a server performing IoT control according to an exemplary embodiment.

[0023] FIG. 5 is a diagram illustrating the execution screen of an IoT client application according to one embodiment.

[0024] FIG. 6 is a diagram showing a configuration for handling accessibility setting sharing according to an exemplary embodiment.

[0025] FIG. 7a is a diagram illustrating a procedure for performing accessibility setting sharing by an IoT device according to an exemplary embodiment.

[0026] FIG. 7b is a diagram illustrating a procedure for sharing accessibility settings by a server according to an exemplary embodiment.

[0027] FIG. 7c shows the matching relationship of accessibility functions according to an exemplary embodiment.

[0028] FIG. 8 is a flowchart illustrating a procedure for sharing accessibility settings by an IoT device according to an exemplary embodiment.

[0029] FIG. 9 is a flowchart illustrating a procedure for sharing accessibility settings by a server according to an exemplary embodiment.

[0030] FIG. 10 is a flowchart illustrating a procedure for analyzing accessibility settings according to an exemplary embodiment.

[0031] FIG. 11 illustrates a procedure for accepting accessibility setting sharing according to an exemplary embodiment.

[0032] FIGS. 12a, FIGS. 12b, FIGS. 12c, and FIGS. 12d are drawings illustrating accessibility function matching according to exemplary embodiments.

[0033] FIG. 13 is a diagram illustrating a procedure for sharing accessibility settings during onboarding according to an exemplary embodiment.

[0034] FIG. 14 shows an accessibility setting sharing user interface according to an exemplary embodiment.

[0035] FIG. 15 is a diagram illustrating a procedure for sharing accessibility settings based on user actions according to an exemplary embodiment.

[0036] FIG. 16 illustrates a procedure for setting accessibility settings sharing when registering a device according to an exemplary embodiment.

[0037] FIG. 17 is a flowchart illustrating a procedure for sharing accessibility settings by an IoT device upon device registration according to an exemplary embodiment.

[0038] FIG. 18 illustrates a procedure for setting accessibility settings sharing through account switching according to an exemplary embodiment.

[0039] FIG. 19 is a flowchart illustrating a procedure for sharing accessibility settings by an IoT device during user interaction according to an exemplary embodiment.

[0040] FIG. 20a illustrates accessibility setting sharing based on voice commands according to an exemplary embodiment.

[0041] FIG. 20b illustrates accessibility setting sharing based on a short-range communication method according to an exemplary embodiment.

[0042] FIG. 21 is a flowchart illustrating a procedure for sharing accessibility settings by voice command according to an exemplary embodiment.

[0043] Exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In describing the embodiments of the present disclosure, specific descriptions of related known functions or configurations are omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Furthermore, terms used below are defined considering their functions in the exemplary embodiments, and these may vary depending on the intent or practice of the user or operator. Therefore, such definitions should be based on the content throughout the present disclosure.

[0044] It should be noted that technical terms used in this disclosure are used merely to describe one embodiment and are not intended to limit this disclosure. Alternatively, unless specifically defined otherwise in this disclosure, technical terms used in this disclosure shall be interpreted in the sense generally understood by those skilled in the art to which this disclosure pertains, and shall not be interpreted in an overly broad or overly narrow sense. Alternatively, technical terms used in this disclosure may be understood as being replaced by other technical terms understood by those skilled in the art. General terms used in the embodiments of this disclosure shall be interpreted according to their prior definitions or according to the context, and shall not be interpreted in an overly narrow sense.

[0045] Singular expressions used in this disclosure may include plural expressions unless the context clearly indicates otherwise. In this disclosure, terms such as “composed” or “comprising” should not be interpreted as necessarily including all of the various components or operations described in the specification, and should be interpreted as some of the components or operations may not be included, or additional components or operations may be included.

[0046] Terms including ordinal numbers, such as first or second as used in this disclosure, may be used to describe various components, but said components should not be limited by said terms. Such terms may be used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the rights of this disclosure, the first component may be named the second component, and similarly, the second component may be named the first component.

[0047] When it is stated that one component is "connected" or "connected" to another component, it may be directly connected or connected to that other component, or there may be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0048] Hereinafter, embodiments according to the present disclosure will be described with reference to the attached drawings. Identical or similar components regardless of drawing symbols are given the same reference numeral, and redundant descriptions thereof will be omitted. In describing exemplary embodiments of the present disclosure, detailed descriptions of related prior art are omitted if it is determined that such detailed descriptions may obscure the essence of the present disclosure. It should be noted that the attached drawings are intended only to facilitate understanding of the embodiments of the present disclosure and should not be interpreted as limiting the present disclosure. The present disclosure should be interpreted as extending to all modifications, equivalents, and substitutions in addition to the attached drawings.

[0049] In certain exemplary embodiments, the embodiments will be described using an electronic device as an example, but the electronic device may be referred to as a terminal, mobile station, mobile equipment (ME), user equipment (UE), user terminal (UT), subscriber station (SS), wireless device, handheld device, or access terminal (AT). In certain exemplary embodiments, the electronic device may be a device with communication capabilities, such as a mobile phone, personal digital assistant (PDA), smartphone, wireless modem, or laptop.

[0050] FIG. 1 illustrates an IoT (internet of things) system (100) according to various embodiments. Meanwhile, at least some of the components of FIG. 1 may be omitted, and the system may be implemented to include additional components not illustrated.

[0051] Referring to FIG. 1, an IoT system (100) according to one embodiment may include a plurality of electronic devices connectable to a data network (116 or 146). For example, the IoT system (100) may include at least one of a first IoT server (110), a first node (120), a voice assistance server (130), a second IoT server (140), a second node (150), or devices (121, 122, 123, 124, 125, 136, 137, 151, 152, 153).

[0052] According to one embodiment, the first IoT server (110) may include at least one of a communication interface (111), a processor (112), or a storage unit (113). The second IoT server (140) may include at least one of a communication interface (141), a processor (142), or a storage unit (143). An “IoT server” in this document may remotely control and / or monitor one or more devices (e.g., devices (121, 122, 123, 124, 125, 151, 152, 153)) based on, for example, a data network (e.g., data network (116) or data network (146)), through a relay device (e.g., first node (120) or second node (150)), or directly without a relay device. The term "device" as used herein may refer to sensors, home appliances, office electronic devices, or devices for performing processes deployed (or located) within a local environment, such as a home, office, factory, building, external branch, or other types of sites, and there are no restrictions on the types thereof. A device that receives a control command and performs an action corresponding to the control command may be referred to as a "target device." An IoT server may also be referred to as a central server in that it selects a target device from among multiple devices and provides control commands.

[0053] According to one embodiment, the first IoT server (110) can communicate with devices (121, 122, 123) through a data network (116). The data network (116) may mean a network for long-distance communication, such as the Internet, or a computer network (e.g., LAN or WAN), or may include a cellular network.

[0054] According to one embodiment, the first IoT server (110) may be connected to a data network (116) through a communication interface (111). The communication interface (111) may include a communication device (or communication module) for supporting communication of the data network (116), and may be integrated into a single component (e.g., a single chip) or implemented as separate components (e.g., multiple chips). The first IoT server (110) may communicate with devices (121, 122, 123) through a first node (120). The first node (120) may receive data from the first IoT server (110) through the data network (116) and transmit the received data to at least some of the devices (121, 122, 123). Alternatively, the first node (120) may receive data from at least some of the devices (121, 122, 123) and transmit the received data to the first IoT server (110) via the data network (116). The first node (120) may function as a bridge between the data network (116) and the devices (121, 122, 123). Meanwhile, although FIG. 1 is illustrated as having only one first node (120), this is merely illustrative and there is no limit to the number.

[0055] In this document, "node" may be an edge computing system or a hub device. According to one embodiment, the first node (120) supports wired and / or wireless communication of the data network (116) and may also support wired and / or wireless communication with devices (121, 122, 123). For example, the first node (120) may be connected to the devices (121, 122, 123) via a short-range communication network such as Bluetooth, Wi-Fi, Wi-Fi Direct, Z-wave, Zig-bee, INSETEON, X10, or IrDA (infrared data association), but there are no restrictions on the type of communication. The first node (120) may be placed (or located) within an environment such as, for example, a home, office, factory, building, external branch, or other types of sites. Accordingly, the devices (121, 122, 123) may be monitored and / or controlled by a service provided by the first IoT server (110), and the devices (121, 122, 123) may not be required to have the capability of full network communication (e.g., Internet communication) for direct connection to the first IoT server (110). The devices (121, 122, 123) are illustrated as being implemented as electronic devices in a home environment, such as light switches, proximity sensors, temperature sensors, etc., but this is exemplary and not limited to this.

[0056] According to one embodiment, the first IoT server (110) may support direct communication with devices (124, 125). Here, "direct communication" means communication without passing through a relay device, such as a first node (120), for example, and may mean communication through a cellular communication network and / or a data network, for example.

[0057] According to one embodiment, the first IoT server (110) may transmit a control command to at least some of the devices (121, 122, 123, 124, 125). Here, "control command" may mean data that causes a controllable device to perform a specific action, and the specific action is an action performed by the device, which may include outputting information, sensing information, reporting information, and managing information (e.g., deletion, or creation), and there is no limitation on the type thereof. For example, the processor (112) may obtain information (or a request) for generating a control command from an external source (e.g., a voice assistant server (130), a second IoT server (140), an external system (160), or at least some of the devices (121, 122, 123, 124, 125), and generate a control command based on the obtained information. Alternatively, the processor (112) may generate a control command based on the fact that the monitoring results of at least some of the devices (121, 122, 123, 124, 125) satisfy a specified condition. The processor (112) may control the communication interface (111) to transmit the control command to the target device.

[0058] According to one embodiment, the processor (112), or the processor (132), or the processor (142) may be implemented as a combination of one or more general-purpose processors such as a CPU (central processing unit), a DSP (digital signal processor), an AP (application processor), or a CP (communication processor), a graphics-dedicated processor such as a GPU (graphical processing unit) or a VPU (vision processing unit), or an artificial intelligence-dedicated processor such as an NPU (neural processing unit). The processing units described above are merely exemplary, and those skilled in the art will understand that the processor (112) is not limited to any means of computation capable of executing instructions stored in memory (113), for example, and outputting the result of the execution.

[0059] According to one embodiment, the processor (112) may configure a web-based interface based on an API (114) or expose a resource managed by the first IoT server (110) to the outside. The web-based interface may support communication, for example, between the first IoT server (110) and an external web service. The processor (112) may allow, for example, an external system (160) to control and / or access the devices (121, 122, 123). The external system (160) may, for example, be an independent system that is not associated with or part of the system (100). The external system (160) may, for example, be an external server or a website. However, security is required for access to the devices (121, 122, 123) or the resources of the first IoT server (110) from the external system (160). According to one embodiment, the processor (112) may expose an API endpoint (e.g., a URL (universal resource locator)) based on the API (114) of the automation application to the outside. As described above, the first IoT server (110) may transmit control commands to a target device among the devices (121, 122, 123). Meanwhile, the description of the communication interface (141), processor (142), API (144) of the storage unit (143), and database (145) of the second IoT server (140) may be substantially the same as the description of the communication interface (111), processor (112), API (114) of the storage unit (113), and database (115) of the first IoT server (110). Additionally, the description of the second node (150) may be substantially the same as the description of the first node (120). The second IoT server (140) can transmit control commands to a target device among the devices (151, 152, 153).The first IoT server (110) and the second IoT server (140) may be operated by the same service provider in one embodiment, but may be operated by different service providers in another embodiment.

[0060] According to one embodiment, the voice assistant server (130) can transmit and receive data with the first IoT server (110) through a data network (116). The voice assistant server (130) according to one embodiment may include at least one of a communication interface (131), a processor (132), or a storage unit (133). The communication interface (131) can communicate with a smartphone (136) or an AI speaker (137) through a data network (not shown) and / or a cellular network (not shown). The smartphone (136) or the AI ​​speaker (137) may include a microphone and can acquire a user voice, convert it into a voice signal, and transmit the voice signal to the voice assistant server (130). The processor (132) can receive a voice signal from the smartphone (136) or the AI ​​speaker (137) through the communication interface (131). The processor (132) can process the received voice signal based on the stored model (134). The processor (132) can generate (or verify) a control command using the processing result based on the information stored in the database (135).According to one embodiment, the storage unit (113, 133, 143) may include at least one type of non-transitory storage medium among a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., SD or XD memory, etc.), RAM (random access memory), SRAM (static random access memory), ROM (read-only memory), EEPROM (electrically erasable programmable read-only memory), PROM (programmable read-only memory), magnetic memory, a magnetic disk, or an optical disk, and there is no limitation on the type.

[0061] Each "processor" herein may include a processing circuit or a plurality of processors. For example, the term "processor" as used in the present disclosure, including in the claims, may include various processing circuits including at least one processor, and at least one of the at least one processor may be configured to perform the various functions described in the present disclosure individually and / or collectively in a distributed manner. When the "processor," "at least one processor," and "one or more processors" as used in the present disclosure are described as being configured to perform a plurality of functions, these terms include, but are not limited to, situations where, for example, one processor performs part of the mentioned functions and other processor(s) perform other parts of the mentioned functions, and situations where a single processor can perform all the mentioned functions. Additionally, at least one processor may include a combination of processors that perform the various mentioned / disclosed functions, for example, in a distributed manner. At least one processor may execute program instructions to achieve or perform the various functions.

[0062] In various embodiments, at least one device (e.g., device (124)) communicating with the first IoT server (110) may be a smartphone in a network environment (e.g., the electronic device (201) of FIG. 2).

[0063] FIG. 2 is a block diagram of an electronic device (201) in a network environment (200) according to various embodiments.

[0064] Referring to FIG. 2, in a network environment (200), an electronic device (201) may communicate with an electronic device (202) through a first network (298) (e.g., a short-range wireless communication network) or with at least one of an electronic device (204) or a server (208) through a second network (299) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (201) may communicate with the electronic device (204) through a server (208). According to one embodiment, the electronic device (201) may include a processor (220), memory (230), input module (250), sound output module (255), display module (260), audio module (270), sensor module (276), interface (277), connection terminal (278), haptic module (279), camera module (280), power management module (288), battery (289), communication module (290), subscriber identification module (296), or antenna module (297). In some embodiments, at least one of these components (e.g., connection terminal (278)) may be omitted from the electronic device (201), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (276), camera module (280), or antenna module (297)) may be integrated into a single component (e.g., display module (260)).

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

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

[0067] The memory (230) can store various data used by at least one component of the electronic device (201) (e.g., processor (220) or sensor module (276)). The data may include, for example, software (e.g., program (240)) and input or output data for related commands. The memory (230) may include volatile memory (232) or non-volatile memory (234).

[0068] The program (240) may be stored as software in memory (230) and may include, for example, an operating system (242), middleware (244), or an application (246).

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

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

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

[0072] The audio module (270) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (270) can acquire sound through the input module (250) or output sound through the sound output module (255) or an external electronic device (e.g., electronic device (202)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (201).

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

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

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

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

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

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

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

[0080] The communication module (290) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (201) and an external electronic device (e.g., electronic device (202), electronic device (204), or server (208)), and the performance of communication through the established communication channel. The communication module (290) may include one or more communication processors that operate independently of the processor (220) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (290) may include a wireless communication module (292) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (294) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (204) via a first network (298) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (299) (e.g., a legacy 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 a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (292) can identify or authenticate the electronic device (201) within a communication network such as the first network (298) or the second network (299) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (296).

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

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

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

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

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

[0086] FIG. 3 is a diagram illustrating a network including devices to be controlled according to an exemplary embodiment.

[0087] Referring to FIG. 3, a network (300) (e.g., an IoT network) may include a server (350) operating as an IoT cloud and / or account server, a first electronic device (310) (e.g., an electronic device (201)), and one or more controlled devices (e.g., IoT devices (320a, 320b, 320c, 320d, and 320e)) within a local network (345).

[0088] In one embodiment, the first electronic device (310) may be configured to communicate with the server (350) via long-range wireless communication (e.g., the second network (299)). In one embodiment, at least one of the IoT devices (320a, 320b, 320c, 320d, and 320e) may be configured to communicate with the first electronic device (310) using short-range wireless communication (e.g., Wi-Fi, Bluetooth legacy, Bluetooth low energy (BLE), ultra-wideband (UWB), and / or near-field communication (NFC)). In one embodiment, at least one of the IoT devices (320a, 320b, 320c, 320d, and 320e) may be configured to support IoT technology and communicate with the server (350) via an access point (AP) (340).

[0089] In one embodiment, any one of the IoT devices (320a, 320b, 320c, 320d, and 320e) (e.g., IoT device (320a)) (e.g., TV, home automation panel, PC (personal computer), smartphone, or tablet) may be configured to have a hub function configured to manage the connection and status of the IoT devices (320a, 320b, 320c, 320d, and 320e). The IoT device (320a) may communicate with the server (350) via the AP (350) and may be registered with the server (350) after being onboarded, similar to the IoT devices (320a, 320b, 320c, 320d, and 320e).

[0090] In one embodiment, the first electronic device (310) can communicate (e.g., control or manage) with IoT devices (320a, 320b, 320c, 320d, and 320e) through a server (350), through long-range wireless communication (e.g., the second network (299)), or through short-range wireless communication (e.g., the first network (298)).

[0091] In one embodiment, the IoT devices (320a, 320b, 320c, 320d, and 320e) may include, for example, at least one of a television, an air conditioner, an air purifier, a refrigerator, a washing machine, a light bulb, a security camera, a sensor, or a window treatment. In one embodiment, the IoT devices (320a, 320b, 320c, 320d, and 320e) may be configured to be controlled (e.g., to report status and / or execute specified actions) by a remote command (e.g., a control command from the first electronic device (310) or the server (350). In one embodiment, IoT devices (320a, 320b, 320c, 320d, and 320e) may communicate with the first electronic device (310) via an AP (340) within a local network (345), communicate with the first electronic device (310) via a server (350), and / or communicate directly with the first electronic device (310) via a point-to-point (P2P) connection (e.g., without going through the server (350), AP (340), or other devices).

[0092] In one embodiment, IoT devices (320a, 320b, 320c, 320d, and 320e) may be configured to communicate with a first electronic device (310) via long-range wireless communication (e.g., a second network (299)) or via short-range wireless communication (e.g., a first network (298)). In one embodiment, IoT devices (320a, 320b, 320c, 320d, and 320e) may be configured to communicate with a server (350) via long-range wireless communication (e.g., a second network (299)) or via short-range wireless communication (e.g., a first network (298)).

[0093] In one embodiment, at least one of the IoT devices (320b, 320c, 320d, and 320e) may be a hub-connected device that establishes a P2P connection (e.g., Bluetooth connection, BLE (Bluetooth low energy) connection, ZigBee connection, ZWave connection, or Wi-Fi connection) with an IoT device (e.g., IoT device (320a)) acting as a hub and receives control commands or reports status from a server (350) through the IoT device (320a). In one embodiment, at least one of the IoT devices (320b, 320c, 320d, and 320e) may be a cloud-connected device configured to receive control commands or report status from a server (350) through an AP (340). In one embodiment, at least one of the IoT devices (320b, 320c, 320d, and 320e) may be a cloud-to-cloud type device registered in a third-party cloud and controlled via an application programmable interface (API) between clouds.

[0094] In one embodiment, the first electronic device (310) may be a personal electronic device such as a smartphone or tablet, for example, or an electronic device having a display and a user interface such as a television or a control console. In one embodiment, the first electronic device (310) may be configured to directly perform at least some of the functions described below of the first electronic device (310), or to perform them through connection (e.g., pairing) with at least one external electronic device (e.g., a wearable device such as a smart watch).

[0095] In one embodiment, the first electronic device (310) can discover at least one of the IoT devices (320a, 320b, 320c, 320d, 320e) and can execute a procedure (e.g., a registration procedure) to register the discovered IoT device to the server (350). The IoT devices (320a, 320b, 320c, 320d, 320e) are registered to the server (350) to be associated with a user account and can log in (e.g., sign in) with said user account. The first electronic device (310) can monitor or / or control the IoT devices (320a, 320b, 320c, 320d, 320e) based on said user account. In one embodiment, the first electronic device (310) can check the status of IoT devices (320a, 320b, 320c, 320d, 320e) that a user can use for an IoT service, or control the IoT devices (320a, 320b, 320c, 320d, 320e) (e.g., transmit a control command instructing to perform a specific action).

[0096] FIG. 4a is a block diagram illustrating the configuration of a second electronic device (330) according to an exemplary embodiment.

[0097] Referring to FIG. 4a, the second electronic device (330) may be an IoT device (e.g., any one of IoT devices (320a, 320b, 320c, 320d, and 320e)) that performs an IoT service (e.g., an event-based IoT service) in an IoT network (e.g., network (300)). For example, the IoT network may be a smart home network, and the IoT service may be an automation service. The second electronic device (330) may include at least one processor (412) including a processing circuit, a communication circuit (414), a memory (416) for storing instructions, and / or a native function unit (418) that performs a native function. In FIG. 4a, each of the components (412, 414, 416, 418) may be functionally connected to one another. In one embodiment, the second electronic device (330) may be a device or TV including a display. In one embodiment, if the second electronic device (330) is a smart TV, the unique function unit (418) may include a TV reception circuit and a display. In one embodiment, if the second electronic device (330) is a smart washing machine, the unique function unit (418) may include a motor and a control circuit. In one embodiment, if the second electronic device (330) is a smart refrigerator, the unique function unit (418) may include a cooling circuit and a control circuit.

[0098] In one embodiment, the communication circuit (414) can transmit and receive wireless signals with an external electronic device (e.g., a first electronic device (310), an AP (340), a server (350), and / or other IoT devices). The second electronic device (330) can support at least one of a specified short-range wireless communication technology (e.g., Zigbee, Z-Wave, UWB (ultra wide-band), or Wi-Fi) through the communication circuit (414). The communication circuit (414) may include one or more communication circuits based on a specified short-range wireless communication technology (e.g., Zigbee, Z-Wave, UWB, and / or Wi-Fi).

[0099] In one embodiment, the processor (412) may be implemented as one or more single-core processors or one or more multi-core processors. In one embodiment, the memory (416) may store instructions and data for the operation of the second electronic device (330).

[0100] In one embodiment, the memory (416) may store relevant information and / or data for controlling accessibility setting sharing according to specific exemplary embodiments. In one embodiment, the memory (416) may store an accessibility function list (e.g., a second accessibility function list) representing accessibility functions in use in the second electronic device (330).

[0101] In one embodiment, the processor (412) may control or manage the state (e.g., accessibility setting state) and actions (e.g., accessibility functions) of the second electronic device (330) associated with the IoT service. In one embodiment, the processor (412) may receive control commands related to the control of the second electronic device (330) from the first electronic device (310) and / or server (350) and may operate according to said control commands. In one embodiment, said control commands may be received via AP (340). In one embodiment, said control commands may include an accessibility setting instruction that indicates at least one accessibility function to be applied to the second electronic device (330).

[0102] FIG. 4b is a block diagram illustrating the configuration of a server (350) that performs IoT control according to an exemplary embodiment.

[0103] Referring to FIG. 4b, a server (350) can control and manage components (e.g., IoT devices (320a, 320b, 320c, 320d, 320e), and a first electronic device (310)) that perform IoT services (e.g., event-based IoT services) in an IoT network (e.g., network (300)). In one embodiment, the server (350) may be configured to communicate with the IoT devices (320a, 320b, 320c, 320d, 320e) and the first electronic device (310) via an external network (e.g., the Internet). In one embodiment, the server (350) may include at least one processor (422) including a processing circuit, a communication circuit (424), and / or a memory (426) for storing instructions. In FIG. 4b, each of the components (422, 424, 426) can be functionally connected to one another.

[0104] In one embodiment, the communication circuit (424) can transmit and receive control messages and data with an external electronic device (e.g., the first electronic device (310) and / or IoT devices (320a, 320b, 320c, 320d, 320e)). In one embodiment, the processor (422) may be implemented with one or more single-core processors or one or more multi-core processors. In one embodiment, the memory (426) may store instructions and data for the operation of the server (350).

[0105] In one embodiment, the memory (426) may store relevant information and / or data for controlling accessibility setting sharing according to specific exemplary embodiments. In one embodiment, the memory (426) may store information about accessibility functions in use in the first electronic device (310) and information about accessibility functions in use in the second electronic device (330).

[0106] In one embodiment, the processor (422) may control or manage the state (e.g., accessibility setting state) and actions (e.g., accessibility functions) of devices (e.g., the first electronic device (310) and the second electronic device (330)) associated with the IoT service. In one embodiment, the processor (422) may receive information (e.g., lists of accessibility functions) related to the control of the first electronic device (310) and the second electronic device (330) from the first electronic device (310) and / or the second electronic device (330), determine accessibility setting sharing based on the received information, and transmit a control command including an accessibility setting instruction according to the determination to the second electronic device (330). The control command may be transmitted to the second electronic device (330) via the AP (340). The accessibility setting instruction may indicate at least one accessibility function to be applied to the second electronic device (330).

[0107] FIG. 5 is a diagram illustrating the execution screen of an IoT client application according to one embodiment.

[0108] Referring to FIG. 5, the first electronic device (310) can execute a client application for an IoT control service and display an execution screen (500) provided by the client application through a display module (e.g., a display module (260)). The execution screen (500) may include a state object (e.g., a state object (510, 520)) representing the states (e.g., at least one of an image, location, name, or connection status) of at least one onboarded external electronic device (e.g., IoT devices (320a, 320b, 320c, 320d, 320e)). The connection status may indicate online or offline.

[0109] In one embodiment, if any one of the IoT devices (320a, 320b, 320c, 320d, 320e) (e.g., a washing machine) is not normally connected to the server (350), the state object (510) corresponding to the washing machine may indicate an offline state. In one embodiment, if any one of the IoT devices (320a, 320b, 320c, 320d, 320e) (e.g., a bedroom TV) is normally connected to the server (350), the state object (520) corresponding to the bedroom TV may indicate an online state. In one embodiment, the IoT devices (320a, 320b, 320c, 320d, 320e) may log in (e.g., sign in) to the server (350) using a user account while online.

[0110] In one embodiment, the first electronic device (310) and / or the second electronic device (330) (e.g., an IoT device) may provide accessibility features designed to make it easier for people with disabilities to use the technology. For example, a text-to-speech feature may read aloud text displayed on the first electronic device (310) for a visually impaired person, and a speech-recognition feature may enable a user with mobility impairments to control the first electronic device (310) by voice.

[0111] In one embodiment, the first electronic device (310) may turn on (e.g., activate or enable) at least one of a plurality of accessibility features according to user settings. In one embodiment, the accessibility features that the first electronic device (310) can provide may include at least one of a talkback feature, a voice access feature, a magnification feature, a high contrast screen feature, a black and white screen feature, a relumino outline feature, an audio description feature, or a live caption feature.

[0112] The above talkback feature can read out text displayed on the screen of the first electronic device (310) (e.g., the display module (260) of FIG. 2) or output voice guidance whenever a user gesture (e.g., touch) is detected.

[0113] The above voice access function can perform tasks such as opening an application, tapping a button, and entering text using voice.

[0114] The above magnification function can adjust the font size, zoom in on the screen, or use the screen of the first electronic device (310) as a magnifying glass.

[0115] The above high contrast screen feature can improve screen readability by making text stand out more against the background.

[0116] The above black and white screen function can switch the color screen to a black and white screen.

[0117] The above relumino outline function can enhance the visibility of text and images on the screen by emphasizing the outlines, colors, and contrast of the screen.

[0118] The above screen description function can read out the user interface, including menus, icons, and / or text.

[0119] The above live caption function can provide captions that explain the content of the screen.

[0120] In one embodiment, the second electronic device (330) (e.g., an IoT device) may be configured to provide at least one accessibility function similar to that provided by the first electronic device (310). In one embodiment, the accessibility functions that the second electronic device (330) can provide may include at least one of the following.

[0121] The voice control function enables the user to control the second electronic device (330) via voice commands. In one embodiment, if the second electronic device (330) is a TV, the user can change the channel or adjust the volume via voice commands.

[0122] A voice guidance function (e.g., a screen reader function) can read out text or menu options displayed on the screen of the second electronic device (330).

[0123] The high contrast screen feature increases screen contrast, allowing users with low vision to navigate menus more easily.

[0124] The color inversion function can invert the colors on the screen.

[0125] The black and white screen function can switch the color screen to a black and white screen.

[0126] The Relumino mode feature can increase screen contrast and brightness and emphasize the outlines of images and shapes.

[0127] The screen description function can provide narration that explains the visual content of the video.

[0128] The closed caption feature can display subtitles on the screen.

[0129] The zoom function can magnify on-screen fonts and interface elements.

[0130] In one embodiment, while a user is applying accessibility settings corresponding to one or more accessibility functions to the first electronic device (310) (e.g., turning on, activating, or enabling), if a second electronic device (330) is newly purchased or onboarded, a new accessibility setting corresponding to accessibility functions similar to the accessibility functions may be created for the second electronic device (330). In the process of setting the accessibility functions of the second electronic device (330), the user may experience inconvenience in finding and applying the desired accessibility function because they are not familiar with the method of entering the accessibility menu.

[0131] Certain exemplary embodiments allow accessibility features applicable in common regardless of the device model to be shared between devices (e.g., a first electronic device (310) and a second electronic device). According to certain exemplary embodiments, through the sharing of accessibility settings between the first electronic device (310) and the second electronic device (330), at least one accessibility feature currently in use in the first electronic device (310) can be conveniently applied to the second electronic device (330) upon login of the second electronic device (330).

[0132] FIG. 6 is a diagram showing a configuration for handling accessibility setting sharing according to an exemplary embodiment.

[0133] Referring to FIG. 6, the accessibility setting analysis module (610) can analyze the accessibility settings of the first electronic device (310) and determine the accessibility functions to be shared with the second electronic device (320). In one embodiment, the accessibility setting analysis module (610) may be included in the server (350), the second electronic device (330), or the first electronic device (310).

[0134] In one embodiment, when detecting a specified user action, or identifying that the second electronic device (330) connects to (e.g., registers) the server (350) and / or is logged in to the server (350) after onboarding the second electronic device (330), the first electronic device (310) may provide an accessibility function list (602) indicating at least one accessibility function in use in the first electronic device (310) to an accessibility setting analysis module (610) (e.g., the server (350) or the second electronic device (330)). In one embodiment, the user action may include at least one of the action of bringing the first electronic device (310) close to the second electronic device (330), the action of physically contacting (e.g., tapping) the first electronic device (310) with the second electronic device (330), a touch on the screen of the first electronic device (310), or user input on the screen or button of the second electronic device (330).

[0135] In one embodiment, the first electronic device (310) may transmit an accessibility function list (602) indicating the accessibility setting status of the first electronic device (310) to an accessibility setting analysis module (610) (e.g., server (350) or the second electronic device (330)) based on identifying that the second electronic device (330) is connected to the server (350) and logged in (e.g., signed in). In one embodiment, the first electronic device (310) may transmit the accessibility function list (602) along with user account information to the accessibility setting analysis module (610).

[0136] In one embodiment, when a specified user action is detected, or when the second electronic device (330) is first connected to and / or logged in to the server (350) after new registration or purchase, the second electronic device (330) may provide an accessibility function list (604) indicating at least one accessibility function in use in the second electronic device (330) to an accessibility setting analysis module (610) (e.g., server (350)).

[0137] In one embodiment, the accessibility setting analysis module (610) can identify at least one accessibility function being used by the first electronic device (310) based on the accessibility function list (602) of the first electronic device (310), and can identify an accessibility function among the at least one accessibility function that is commonly available to the first electronic device (310) and the second electronic device (330). In one embodiment, the accessibility setting analysis module (610) can determine at least one accessibility function (e.g., the first accessibility function) among the commonly available accessibility functions that is not being used by the second electronic device (330) based on the accessibility function list (604) of the second electronic device (330), and can provide an accessibility setting instruction (606) to the second electronic device (330) to instruct the application of the first accessibility function to the second electronic device (330).

[0138] In one embodiment, the accessibility setting analysis module (610) can check for user input that accepts the application of the first accessibility function to the second electronic device (330) before transmitting the accessibility setting instruction (606) to the second electronic device (330).

[0139] In one embodiment, the second electronic device (330) can switch to an accessibility setting similar to the accessibility setting of the first electronic device (310) in accordance with the accessibility setting instruction (606), based on logging in with the same user account as the first electronic device (310). In one embodiment, the second electronic device (330) can immediately apply the accessibility function based on the accessibility setting instruction after onboarding is completed, thereby allowing the user to conveniently use the second electronic device (330) without performing the accessibility setting procedure for the second electronic device (330).

[0140] FIG. 7a is a diagram illustrating a procedure for performing accessibility setting sharing by an IoT device according to an exemplary embodiment.

[0141] Referring to FIG. 7a, in operation 702, the first electronic device (310) can transmit a first accessibility feature list (e.g., accessibility feature list (602)) representing at least one accessibility feature currently in use at the first electronic device (310) (e.g., talkback, high contrast screen, color inversion, black and white screen, relumino contour, screen description, or real-time subtitles) to the second electronic device (330) either directly or through a server (350).

[0142] In one embodiment, the first electronic device (310) may provide the first accessibility function list based on receiving information from the server (350) indicating that the second electronic device (330) is logged in after onboarding, is logged in with the same user account as the first electronic device (310) by account switching, or is logged in for the first time with the same user account as the first electronic device (310). In one embodiment, the first electronic device (310) may provide the first accessibility function list based on detecting a designated user action (e.g., a user action to request the first electronic device (310) to be connected to the second electronic device (330).

[0143] In one embodiment, the first electronic device (310) may transmit the first accessibility function list to the server (350) whenever the accessibility settings in the first electronic device (310) are changed, so that the server (350) can store the first accessibility function list in an up-to-date state. In one embodiment, the server (350) may transmit the first accessibility function list to the second electronic device (330) based on identifying that the second electronic device (330) is logged in with the same user account as the first electronic device (310) and / or receiving information requesting the first accessibility function list from the second electronic device (330).

[0144] In one embodiment, the second electronic device (330) (e.g., any one of the IoT devices (320a, 320b, 320c, 320d, and 320e)) can determine at least one accessibility function (e.g., the first accessibility function) to be applied to the second electronic device (330) based on the list of the first accessibility functions.

[0145] In operation 704, the second electronic device (330) may transmit accessibility setting sharing information to the first electronic device (310) to inquire whether to use the first accessibility function, and the first electronic device (310) may transmit response information to the second electronic device (330) indicating that the user has accepted to use the first accessibility function. In operation 704a, the first electronic device (310) may display an accessibility setting sharing user interface (UI) to inquire whether to accept to apply the first accessibility function to the second electronic device (330), and transmit the response information based on receiving user input accepting to use the first accessibility function through the accessibility setting sharing user interface.

[0146] In operation 706, the second electronic device (330) may apply the first accessibility function (e.g., turn on, activate, or enable) based on receiving the response information.

[0147] FIG. 7b is a diagram illustrating a procedure for sharing accessibility settings by a server according to an exemplary embodiment.

[0148] Referring to FIG. 7b, in operation 712, the first electronic device (310) can transmit to the server (350) a first accessibility feature list (e.g., accessibility feature list (602)) representing at least one accessibility feature in use at the first electronic device (310) (e.g., talkback, high contrast screen, color inversion, black and white screen, relumino contour, screen description, or real-time subtitles).

[0149] In one embodiment, the first electronic device (310) may provide the first accessibility function list based on receiving information from the server (350) indicating that the second electronic device (330) is logged in after onboarding, is logged in with the same user account as the first electronic device (310) by account switching, or is logged in for the first time with the same user account as the first electronic device (310). In one embodiment, the first electronic device (310) may provide the first accessibility function list based on detecting a specified user action. In one embodiment, the first electronic device (310) may provide the first accessibility function list based on a request from the server (350).

[0150] In one embodiment, the first electronic device (310) may transmit the first accessibility function list to the server (350) whenever the accessibility setting in the first electronic device (310) is changed, so that the server (350) may store the first accessibility function list. In one embodiment, the first electronic device (310) may transmit the first accessibility function list to the second electronic device (330) based on receiving information requesting the first accessibility function list from the server (310).

[0151] In operation 714, the second electronic device (330) can transmit to the server (350) a second accessibility feature list (e.g., accessibility feature list (604)) representing at least one accessibility feature currently in use in the second electronic device (330) (e.g., voice guidance, high contrast screen, color inversion, black and white screen, relumino mode, audio description broadcast, or subtitles).

[0152] In one embodiment, the second electronic device (330) may provide the second accessibility feature list based on logging in after the second electronic device (330) is onboarded, logging in with the same user account as the first electronic device (310) by account switching, or logging in for the first time with the same user account as the first electronic device (310). In one embodiment, the second electronic device (330) may provide the second accessibility feature list based on detecting a specified user action. In one embodiment, the second electronic device (330) may provide the second accessibility feature list based on a request from the server (350).

[0153] In one embodiment, the server (350) may determine, based on the first accessibility function list and the second accessibility function list, at least one accessibility function (e.g., the first accessibility function) to be applied to the second electronic device (330) among the accessibility functions currently in use in the first electronic device (310). In one embodiment, when the second electronic device (330) is first onboarded, the server (350) may determine that the second electronic device (330) is not using all accessibility functions and may determine the first accessibility function without the second accessibility function list.

[0154] In operation 716, the server (350) may transmit accessibility setting sharing information to the first electronic device (310) to inquire whether to use the first accessibility function, and the first electronic device (310) may transmit response information to the server (350) indicating that the user has accepted to use the first accessibility function. In operation 716a, the first electronic device (310) may display an accessibility setting sharing user interface (UI) to inquire whether to accept to apply the first accessibility function to the second electronic device (330), and transmit the response information based on receiving user input accepting to use the first accessibility function through the accessibility setting sharing user interface.

[0155] In operation 718, the server (350) may transmit an accessibility setting instruction to the second electronic device (330) instructing it to apply the first accessibility function based on receiving the response information. In operation 720, the second electronic device (330) may apply the first accessibility function (e.g., turn on, activate, or enable) based on receiving the accessibility setting instruction.

[0156] In one embodiment, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) may determine at least one accessibility function available in another electronic device (e.g., the second electronic device (330)) as the target for accessibility setting sharing, excluding the accessibility function specialized for the first electronic device (310) among the available accessibility functions of the first electronic device (310).

[0157] In one embodiment, an accessibility setting analysis module (610) (e.g., a second electronic device (330) or a server (350)) may determine that at least one accessibility function among the available accessibility functions of the first electronic device (310) is determined to be identical or similar to the accessibility function of the second electronic device (330) in terms of user experience is an accessibility function that is commonly available to the first electronic device (310) and the second electronic device (330) (e.g., a common accessibility function).

[0158] In one embodiment, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can match accessibility functions of the second electronic device (330) that are identical or similar to the accessibility functions of the first electronic device (310) to the accessibility functions of the first electronic device (310) on a one-to-one basis. In one embodiment, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can exclude at least one accessibility function that is identical or similar to the accessibility functions of the first electronic device (310) but cannot be applied redundantly.

[0159] FIG. 7c shows the matching relationship of accessibility functions according to an exemplary embodiment.

[0160] Referring to FIG. 7c, the accessibility features (730) supported by the first electronic device (310) may include at least one of a talkback function, a high-contrast screen function, a color inversion function, a black and white screen function, a relumino contour function, an audio description function, or real-time subtitles. In one embodiment, the first electronic device (310) may enable at least one of the above accessibility features.

[0161] In one embodiment, when the second electronic device (330) is a TV, the accessibility functions (732) supported by the TV may include at least one of a voice guidance function, a high-contrast screen function, a color inversion function, a black and white screen function, a relumino function, an audio description broadcast function, or a subtitle function. The voice guidance function, high-contrast screen function, color inversion function, black and white screen function, relumino function, audio description broadcast function, and subtitle function of the TV may each be matched to the talkback function, high-contrast screen function, color inversion function, black and white screen function, relumino outline function, audio description function, and real-time subtitle function of the first electronic device (310).

[0162] In one embodiment, when the second electronic device (330) is a family hub or an LCD (liquid crystal display) appliance, the accessibility functions (734 or 736) supported by the family hub or LCD appliance may include at least one of a voice guidance function, a high-contrast screen function, a color inversion function, or a black and white screen function. The voice guidance function, high-contrast screen function, color inversion function, and black and white screen function of the family hub or LCD appliance may be matched, respectively, to the talkback function, high-contrast screen function, color inversion function, and black and white screen function of the first electronic device (310).

[0163] FIG. 8 is a flowchart illustrating a procedure for performing accessibility setting sharing by an IoT device according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor (e.g., processor (412) of FIG. 4a) of an IoT device (e.g., second electronic device (330)). In one embodiment, a memory of the second electronic device (330) (e.g., memory (416) of FIG. 4a) may store instructions that cause the second electronic device (330) to operate according to at least one of the operations described below.

[0164] Referring to FIG. 8, in operation 802, a second electronic device (330) (e.g., processor (412)) can connect to a server (350) and log in to the server (350) with a user account (e.g., sign-in). In one embodiment, the second electronic device (330) (e.g., processor (412)) can connect to the server (350) based on network information (e.g., the name and password of an access point (AP)) that is stored in advance after onboarding or provided by an external electronic device (e.g., first electronic device (310)), and log in with the user account. In one embodiment, the second electronic device (330) (e.g., processor (412)) can log in with the user account based on the execution of an onboarding and / or registration procedure through the first electronic device (310).

[0165] In one embodiment, the second electronic device (330) (e.g., processor (412)) may log in to the server (350) based on a specified user action (e.g., a user action requesting the first electronic device (310) to be connected to the second electronic device). In one embodiment, the user action may include at least one of an action of detecting that the first electronic device (310) is in proximity to the second electronic device (330), an action of detecting that the first electronic device (310) is physically in contact (e.g., tap) with the second electronic device (330), or receiving user input (e.g., touch) on the screen or button of the second electronic device (330).

[0166] In operation 804, the second electronic device (330) (e.g., processor (412)) may obtain a first accessibility function list (e.g., accessibility function list (602)) representing at least one accessibility function being used by the first electronic device (310). In one embodiment, the second electronic device (330) (e.g., processor (412)) may receive the first accessibility function list directly from the first electronic device (310) via a P2P connection (e.g., Wi-Fi connection or Bluetooth connection) or receive it from the first electronic device (310) via a server (350).

[0167] In operation 806, the second electronic device (330) (e.g., processor (412)) can identify at least one accessibility function (e.g., common accessibility function) available to the second electronic device (330) among at least one accessibility function currently in use by the first electronic device (310) based on the first accessibility function list. In one embodiment, the second electronic device (330) (e.g., processor (412)) can identify the at least one common accessibility function based on a matching between accessibility functions supported by the first electronic device (310) (e.g., accessibility functions (730)) and accessibility functions supported by the second electronic device (330) (e.g., accessibility functions (732, 734, or 736)).

[0168] In operation 808, the second electronic device (330) (e.g., processor (412)) can identify at least one accessibility function (e.g., at least one first accessibility function) that is not in use in the second electronic device (330) among the at least one common accessibility function, based on at least one accessibility function being used in the second electronic device (330). In one embodiment, the second electronic device (330) (e.g., processor (412)) can exclude an accessibility function that is already in use in the second electronic device (330) among the at least one common accessibility function.

[0169] In operation 810, the second electronic device (330) (e.g., processor (412)) can confirm user input accepting to apply the at least one first accessibility function to the second electronic device (330). In one embodiment, the second electronic device (330) (e.g., processor (412)) can confirm, through the first electronic device (310), that the user accepts to apply the at least one first accessibility function to the second electronic device (330).

[0170] In operation 812, the second electronic device (330) (e.g., processor (412)) may apply (e.g., turn on, activate, or enable) the at least one first accessibility function to the second electronic device (330). In one embodiment, the second electronic device (330) (e.g., processor (412)) may display a screen or output sound while the at least one first accessibility function is activated.

[0171] FIG. 9 is a flowchart illustrating a procedure for sharing accessibility settings by a server according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor of the server (350) (e.g., processor (422) of FIG. 4b). In one embodiment, the memory of the server (350) (e.g., memory (426) of FIG. 4b) may store instructions that cause the server (350) to operate according to at least one of the operations described below.

[0172] Referring to FIG. 9, in operation 902, the server (350) (e.g., processor (422)) can identify that the first electronic device (310) has logged in with a user account. In one embodiment, the first electronic device (310) can log in to the server (350) with a specified user account through the execution of a specified application (e.g., an IoT client application).

[0173] In operation 904, the server (350) (e.g., processor (422)) can identify that the second electronic device (330) has logged in with the user account. In one embodiment, the second electronic device (330) can connect to the server (350) based on network information (e.g., the name and password of an access point (AP)) that is stored in advance after onboarding or provided by an external electronic device (e.g., the first electronic device (310)), and can log in to the server (350) with the user account.

[0174] In operation 906, the server (350) (e.g., processor (422)) receives from the first electronic device (310) a first accessibility function list (e.g., accessibility function list (602)) indicating at least one accessibility function being used by the first electronic device (310), and can receive from the second electronic device (330) a second accessibility function list (e.g., accessibility function list (604)) indicating at least one accessibility function being used by the second electronic device (330).

[0175] In one embodiment, the server (350) (e.g., processor (422)) may request the first accessibility feature list and the second accessibility feature list from the first electronic device (310) and the second electronic device (330), respectively, based on identifying that the second electronic device (330) has logged in. In one embodiment, the server (350) (e.g., processor (422)) may obtain the first accessibility feature list, which has been previously received and stored from the first electronic device (310), from memory (426). In one embodiment, the server (350) (e.g., processor (422)) may determine that the second electronic device (330) is not applying all accessibility features without receiving the second accessibility feature list, based on identifying that the second electronic device (330) has been onboarded for the first time.

[0176] In operation 908, the server (350) (e.g., processor (422)) can identify at least one accessibility function (e.g., common accessibility function) available to the second electronic device (330) among at least one accessibility function being used by the first electronic device (310) based on the first accessibility function list. In one embodiment, the server (350) (e.g., processor (422)) can identify the at least one common accessibility function based on a matching between accessibility functions supported by the first electronic device (310) (e.g. accessibility functions (730)) and accessibility functions supported by the second electronic device (330) (e.g. accessibility functions (732, 734, or 736)).

[0177] In operation 910, the server (350) (e.g., processor (422)) can identify at least one accessibility function (e.g., at least one first accessibility function) that is not in use in the second electronic device (330) among the at least one common accessibility function, based on at least one accessibility function (e.g., list of second accessibility functions) that is in use in the second electronic device (330). In one embodiment, the server (350) (e.g., processor (422)) can exclude the accessibility function that is already in use in the second electronic device (330) among the at least one common accessibility function.

[0178] In operation 912, the server (350) (e.g., processor (422)) can verify user input accepting the application of the at least one first accessibility function to the second electronic device (330). In one embodiment, the server (350) (e.g., processor (422)) can verify, through the first electronic device (310), that the user accepts the application of the at least one first accessibility function to the second electronic device (330).

[0179] In operation 914, the server (350) (e.g., processor (422)) may transmit an accessibility setting instruction to the second electronic device (330) instructing it to apply (e.g., turn on, activate, or enable) the at least one first accessibility function to the second electronic device (330). In one embodiment, the accessibility setting instruction may be transmitted to the second electronic device (330) via the Internet or transmitted to the second electronic device (330) via the first electronic device (310). In one embodiment, the second electronic device (330) (e.g., processor (412)) may, upon receiving the accessibility setting instruction, display a screen or output sound while the at least one first accessibility function is activated.

[0180] FIG. 10 is a flowchart illustrating a procedure for analyzing accessibility settings according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by an accessibility setting analysis module (610) (e.g., a processor (412) of the second electronic device (330) or a processor (422) of the server (350)). In one embodiment, the memory of the second electronic device (330) (e.g., the memory (416) of FIG. 4a) or the memory of the server (350) (e.g., the memory (426) of FIG. 4b) may store instructions that cause the second electronic device (330) or the server (350) to operate according to at least one of the operations described below.

[0181] Referring to FIG. 10, in operation 1002, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) can determine whether the first electronic device (310) is using at least one accessibility function based on the first accessibility function list (e.g., accessibility function list (602)) received from the first electronic device (310). If the first electronic device (310) is not using at least one accessibility function, the procedure may be terminated. If the first electronic device (310) is using at least one accessibility function, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) may proceed to operation 1004.

[0182] In operation 1004, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) can identify at least one accessibility function being used by the second electronic device (330). In one embodiment, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) can identify at least one accessibility function being used by the second electronic device (330) or that the second electronic device (330) is not using all accessibility functions based on a second accessibility function list (e.g., accessibility function list (604)) associated with the second electronic device (330). In one embodiment, an accessibility setting analysis module (610) (e.g., a processor (412) of the second electronic device (330) or a processor (422) of the server (350)) may determine that the second electronic device (330) is not using all accessibility functions when the second electronic device (330) is first onboarded.

[0183] In operation 1006, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) can determine whether there is an accessibility function (e.g., a common accessibility function) available to the second electronic device (330) among at least one accessibility function included in the first accessibility function list. If there is no common accessibility function, the procedure may be terminated. If there is a common accessibility function, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) may proceed to operation 1008.

[0184] In operation 1008, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) can determine whether the common accessibility function is already in use (e.g., in use) in the second electronic device (330). If the common accessibility function is already in use, the procedure may be terminated. If the common accessibility function is not in use, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) may proceed to operation 1010.

[0185] In operation 1010, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) may transmit accessibility setting sharing information representing the common accessibility function to the first electronic device (310). The accessibility setting sharing information may cause the first electronic device (310) to display a common accessibility setting sharing user interface to inquire whether to accept applying the common accessibility function to the second electronic device (330).

[0186] In operation 1012, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) can check whether response information is received indicating that user input accepting the application of the common accessibility function to the second electronic device (330) has been received from the first electronic device (310). If the user does not accept the application of the common accessibility function to the second electronic device (330), the procedure may be terminated. If the user accepts the application of the common accessibility function to the second electronic device (330), the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) may proceed to operation 1014.

[0187] In operation 1014, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) can apply the common accessibility function to the second electronic device (330). In one embodiment, the server (350) (e.g., the processor (422)) can transmit an accessibility setting instruction to the second electronic device (330) instructing it to apply the common accessibility function.

[0188] In operation 1016, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) may provide a notification (e.g., visual or auditory information) indicating that the common accessibility function has been applied to the second electronic device (330). In one embodiment, the accessibility setting analysis module (610) (e.g., the processor (412) of the second electronic device (330) or the processor (422) of the server (350)) may cause the first electronic device (310) to output (e.g., display) the notification.

[0189] FIG. 11 illustrates a procedure for accepting accessibility setting sharing according to exemplary embodiments. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor (e.g., processor (220) of FIG. 2) of a first electronic device (310) (e.g., electronic device (201) of FIG. 2). In one embodiment, a memory of the first electronic device (310) (e.g., memory (230) of FIG. 2) may store instructions that cause the first electronic device (310) to operate according to at least one of the operations described below.

[0190] Referring to FIG. 11, in operation 1102, the first electronic device (310) (e.g., processor (220)) can run an IoT client application and log in (e.g., sign in) to the server (350) with a user account through the IoT client application.

[0191] In operation 1104, the first electronic device (310) (e.g., processor (220)) can identify that the second electronic device (330) is logged into the server (350) with the same user account. In one embodiment, the first electronic device (310) (e.g., processor (220)) can recognize the login of the second electronic device (330) based on proceeding with the onboarding and registration procedure of the second electronic device (330) through the IoT client application. In one embodiment, the first electronic device (310) (e.g., processor (220)) can recognize the login of the second electronic device (330) based on receiving information (e.g., user account information) indicating that the second electronic device (330) is logged in from the second electronic device (330) or the server (350).

[0192] In one embodiment, the first electronic device (310) (e.g., processor (220)) may proceed with the onboarding and registration procedure of the second electronic device (330) and recognize the login of the second electronic device (330) based on detecting a designated user action (e.g., a user action requesting the first electronic device (310) to be connected to the second electronic device). In one embodiment, the user action may include at least one of an action of detecting that the first electronic device (310) is in proximity to the second electronic device (330), an action of detecting that the first electronic device (310) physically contacts (e.g., taps) the second electronic device (330), or receiving user input (e.g., touch) on the screen or button of the second electronic device (330).

[0193] In operation 1106, the first electronic device (310) (e.g., processor (220)) may transmit a first accessibility feature list (e.g., accessibility feature list (604)) indicating at least one accessibility feature being used by the first electronic device (310) to a server (350) or a second electronic device (330). In one embodiment, the first electronic device (310) (e.g., processor (220)) may provide the first accessibility feature list based on identifying that the second electronic device (330) is logged in with the same user account. In one embodiment, the first accessibility feature list may be transmitted based on a request from the server (350) or the second electronic device (330). In one embodiment, the first accessibility feature list may be transmitted to the second electronic device (330) directly or through the server (350).

[0194] In operation 1108, the first electronic device (310) (e.g., processor (220)) may receive accessibility setting sharing information from a server (350) or a second electronic device (330) in which the first electronic device (310) represents at least one accessibility function (e.g., the first accessibility function). In one embodiment, the accessibility setting sharing information may be received directly from the second electronic device (330) or through the server (350). The first electronic device (310) (e.g., processor (220)) may display a accessibility setting sharing user interface for inquiring whether to accept applying the first accessibility function to the second electronic device (330) based on the accessibility setting sharing information.

[0195] In operation 1110, the first electronic device (310) (e.g., processor (220)) can receive user input accepting to apply the first accessibility function to the second electronic device (330) through the commonality setting shared user interface.

[0196] In operation 1112, the first electronic device (310) (e.g., processor (220)) may transmit response information to the server (350) or the second electronic device (330) indicating acceptance of applying the first accessibility function to the second electronic device (330).

[0197] FIGS. 12a, FIGS. 12b, FIGS. 12c, FIGS. 12d, and FIGS. 12e are drawings illustrating accessibility function matching according to exemplary embodiments.

[0198] Referring to FIG. 12a, in operation 1202, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the first electronic device (310) is using the talkback function and the screen description function. In operation 1204, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the second electronic device (330) (e.g., the TV) is using the voice guidance function.

[0199] In one embodiment, an accessibility setting analysis module (610) (e.g., a second electronic device (330) or a server (350)) identifies that the talkback function of the first electronic device (310) matches the voice guidance function of the second electronic device (330), and can identify that the screen description function of the second electronic device (330) corresponding to the screen description function of the first electronic device (310) is not in use in the second electronic device (330).

[0200] In operation 1206, the first electronic device (310) may display an accessibility setting sharing user interface that guides the application of a screen description function to the second electronic device (330) based on a request (e.g., accessibility setting sharing information) from an accessibility setting analysis module (610) (e.g., the second electronic device (330) or server (350)). In one embodiment, the accessibility setting sharing user interface may include a phrase guiding the application of an accessibility function (e.g., a screen description function) currently in use on the first electronic device (310) to the second electronic device (330), and an input object (e.g., "Share") for accepting accessibility setting sharing. Based on identifying that user input (e.g., a touch) is received for the input object, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or server (350)) may apply the screen description function to the second electronic device (330).

[0201] In operation 1208, the second electronic device (330) may display a notification screen indicating that a new accessibility feature (e.g., screen narration feature) is applied. In one embodiment, the second electronic device (330) may highlight the new accessibility feature (e.g., screen narration feature) compared to the existing accessibility feature (e.g., voice guidance feature) by displaying (e.g., voice or outline).

[0202] Referring to FIG. 12b, in operation 1212, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the first electronic device (310) is using the high-contrast screen function and the black-and-white screen function. In operation 1214, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the accessibility setting of the second electronic device (330) (e.g., the TV) is turned off. In one embodiment, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) identifies that the high-contrast screen function and the black-and-white screen function of the first electronic device (310) are not being used in the second electronic device (330), but can decide to apply the high-contrast screen function to the second electronic device (330) according to a predetermined priority.

[0203] In operation 1216, the first electronic device (310) may display an accessibility setting sharing user interface that guides the application of a high-contrast screen function to the second electronic device (330) based on a request (e.g., accessibility setting sharing information) from an accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)). In one embodiment, the accessibility setting sharing user interface may include a phrase guiding the application of an accessibility function (e.g., a high-contrast screen function) currently in use on the first electronic device (310) to the second electronic device (330), and an input object (e.g., "Share") for accepting accessibility setting sharing. Based on identifying that user input (e.g., a touch) is received for the input object, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) may apply the high-contrast screen function to the second electronic device (330).

[0204] In operation 1218, the second electronic device (330) may display a notification screen indicating that a new accessibility feature (e.g., a high-contrast screen feature) is applied.

[0205] In one embodiment, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) may determine to select at least one accessibility function among a plurality of accessibility functions currently in use in the first electronic device (310) according to a predefined priority order for each function and apply it to the second electronic device (330).

[0206] In one embodiment, the first electronic device (310) may use four accessibility functions (e.g., functions A, B, C, D) in duplicate, but the second electronic device (330) may use only one of functions A', B', C', D' which are identical or similar to functions A, B, C, D, respectively. In one embodiment, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) may identify the priorities of the functions A / A' > B / B' > C / C' > D / D'. In one embodiment, the priorities may be in the order A / A' > B / B' > C / C' > D / D'. In one embodiment, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) may decide to apply function A' among functions A', B', C', and D' to the second electronic device (330) according to the priorities.

[0207] Referring to FIG. 12c, in operation 1222, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the first electronic device (310) is using a color inversion function. In operation 1224, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the accessibility setting of the second electronic device (330) (e.g., a TV) is turned off.

[0208] In one embodiment, an accessibility setting analysis module (610) (e.g., a second electronic device (330) or a server (350)) can identify that the color inversion function of the second electronic device (330), corresponding to the color inversion function of the first electronic device (310), is not in use in the second electronic device (330).

[0209] In operation 1226, the first electronic device (310) may display an accessibility setting sharing user interface that indicates that a color inversion function is applied to the second electronic device (330) based on a request (e.g., accessibility setting sharing information) from an accessibility setting analysis module (610) (e.g., the second electronic device (330) or server (350)). In one embodiment, the accessibility setting sharing user interface may include a phrase indicating that an accessibility function (e.g., a color inversion function) currently in use on the first electronic device (310) is applied to the second electronic device (330), and an input object (e.g., "Share") for accepting accessibility setting sharing. Based on identifying that user input (e.g., a touch) is received for the input object, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or server (350)) may apply the color inversion function to the second electronic device (330).

[0210] In operation 1228, the second electronic device (330) can display a notification screen indicating that a new accessibility feature (e.g., a color inversion feature) is applied.

[0211] Referring to FIG. 12d, in operation 1232, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the first electronic device (310) is using the high-contrast screen function and the relumino contour function. In operation 1234, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can identify that the accessibility setting of the second electronic device (330) (e.g., the TV) is turned off.

[0212] In one embodiment, an accessibility setting analysis module (610) (e.g., a second electronic device (330) or a server (350)) can identify that the high-contrast screen function and relumino function of the second electronic device (330), corresponding to the high-contrast screen and relumino contour function of the first electronic device (310), are not in use in the second electronic device (330).

[0213] In operation 1236, the first electronic device (310) may display an accessibility setting sharing user interface that guides the application of high contrast screen functions and relumino functions to the second electronic device (330) based on a request (e.g., accessibility setting sharing information) from an accessibility setting analysis module (610) (e.g., the second electronic device (330) or server (350)). In one embodiment, the accessibility setting sharing user interface may include a phrase guiding the application of accessibility functions (e.g., high contrast screen functions and relumino functions) currently in use on the first electronic device (310) to the second electronic device (330), and an input object (e.g., "Share") for accepting accessibility setting sharing. Based on identifying that user input (e.g., touch) is received for the above input object, the accessibility setting analysis module (610) (e.g., the second electronic device (330) or the server (350)) can apply a high-contrast screen function and a relumino function to the second electronic device (330).

[0214] In operation 1238, the second electronic device (330) can display a notification screen indicating that new accessibility features (e.g., high contrast screen feature and relumino feature) are applied.

[0215] FIG. 13 is a diagram illustrating a procedure for sharing accessibility settings during onboarding according to an exemplary embodiment.

[0216] Referring to FIG. 13, in operation 1302, the first electronic device (310) can run an IoT client application and perform a new device addition through the IoT client application. In one embodiment, the first electronic device (310) can log in to the server (350) through the IoT client application. In one embodiment, to perform the new device addition, the first electronic device (310) can identify the presence of the second electronic device (330) via a designated short-range communication method (e.g., Wi-Fi, Bluetooth, and / or UWB). In one embodiment, the second electronic device (330) can display a first start screen for onboarding.

[0217] In operation 1304, the first electronic device (310) may be connected to the second electronic device (330) for onboarding. In one embodiment, the first electronic device (310) may initiate onboarding of the second electronic device (320) based on at least one of the following actions: scanning a QR (quick response) code attached to the housing or product box of the second electronic device (330) through the camera of the first electronic device (310) (e.g., camera module (280) of FIG. 2), receiving a designated PIN (personal identification number) information, or physically contacting (e.g., tapping) the first electronic device (310) with the second electronic device (320). In one embodiment, the second electronic device (330) may be connected to the first electronic device (310) based on receiving a designated user input (e.g., a button push or a touch on the screen).

[0218] In operation 1306, the first electronic device (310) can proceed with device registration (e.g., user input for agreement to terms and conditions) based on being connected to the second electronic device (330). In operation 1308, the first electronic device (310) can perform device configuration (e.g., function configuration of the second electronic device (330)) based on being connected to the second electronic device (330). In one embodiment, the second electronic device (330) can log in to the server (350) with the same user account as the user account of the first electronic device (310).

[0219] In operation 1310, the first electronic device (310) may display an accessibility setting sharing user interface based on accessibility setting sharing information received from the server (350) or the second electronic device (330). The first electronic device (310) may transmit response information to the server (350) or the second electronic device (330) indicating that user input accepting to use a specified accessibility function through the accessibility setting sharing user interface has been received. The second electronic device (330) may turn on at least one accessibility function indicated by the accessibility setting sharing information based on the response information.

[0220] In operation 1312, the first electronic device (310) can remotely control the second electronic device (330), which has completed onboarding and registration, through an IoT client application. While the second electronic device (330) is in use, the second electronic device (330) can display a screen or output sound based on at least one accessibility function indicated by the accessibility setting sharing information.

[0221] FIG. 14 shows an accessibility setting sharing user interface according to an exemplary embodiment.

[0222] Referring to FIG. 14, the first electronic device (310) may display an accessibility setting sharing user interface (1402) that guides at least one accessibility function (e.g., talkback (voice guidance) and high contrast screen) indicated by the accessibility setting sharing information, based on receiving accessibility setting sharing information from a server (350) or a second electronic device (330). When a user input selecting "Share" is received through the accessibility setting sharing user interface (1402), the first electronic device (310) may transmit response information to the server (350) or the second electronic device (330) indicating that at least one accessibility function has been accepted.

[0223] In one embodiment, the second electronic device (330) may turn on the at least one accessibility function (e.g., voice guidance and high contrast screen) based on the response information and output visual or auditory information (1404) (e.g., "Voice guidance, turning on high contrast screen") indicating that the at least one accessibility function (e.g., voice guidance and high contrast screen) is applied.

[0224] FIG. 15 is a diagram illustrating a procedure for sharing accessibility settings based on user actions according to an exemplary embodiment.

[0225] Referring to FIG. 15, in operation 1502, the first electronic device (310) (e.g., processor (220)) may detect a user interaction to recognize the second electronic device (330) while performing any operation (e.g., running an application other than an IoT client application, or in a screen-off state). In one embodiment, the user interaction may include at least one of the following: physically contacting the first electronic device (310) with the second electronic device (330) (e.g., tapping); discovering the second electronic device (330) via a designated near-field communication method (e.g., Wi-Fi, Bluetooth, or UWB); or recognizing a near-field communication (NFC) tag associated with the second electronic device (330). In one embodiment, the second electronic device (330) may detect a user interaction to recognize the first electronic device (310) while performing any operation (e.g., displaying a broadcast screen, or in a screen-off state). In one embodiment, the user interaction may include at least one of the following: identifying that the first electronic device (310) is physically contacted (e.g., tapped) with the second electronic device (330); discovering the first electronic device (310) via a designated short-range communication method (e.g., Wi-Fi, Bluetooth, or UWB); or receiving a designated signal (e.g., a connection request signal) from the first electronic device (310).

[0226] In operation 1504, the first electronic device (310) (e.g., processor (220)) executes an IoT client application based on detecting the user interaction and can be connected to the second electronic device (330) through the IoT client application. In one embodiment, the first electronic device (310) (e.g., processor (220)) logs into the server (350) through the IoT client application and can identify that the second electronic device (330) is logged into the server (350) with the same user account, or can control the second electronic device (330) to log into the server (350) with the same user account. In one embodiment, the first electronic device (310) (e.g., processor (220)) can control the second electronic device (330) to perform an account switch to the same user account as the first electronic device (310) based on identifying that it is not logged in or that the second electronic device (330) is logged in with a different user account.

[0227] In operation 1506, the first electronic device (310) (e.g., processor (220)) may display an accessibility setting sharing user interface based on accessibility setting sharing information received from the server (350) or the second electronic device (330). In one embodiment, the first electronic device (310) (e.g., processor (220)) may transmit response information to the server (350) or the second electronic device (330) indicating that user input accepting to use a specified accessibility function through the accessibility setting sharing user interface has been received. The second electronic device (330) may turn on at least one accessibility function indicated by the accessibility setting sharing information based on the response information.

[0228] In operation 1508, the first electronic device (310) (e.g., processor (220)) can remotely control the second electronic device (330) through an IoT client application. While the second electronic device (330) is in use, it can display a screen or output sound based on at least one accessibility function indicated by the accessibility setting sharing information.

[0229] FIG. 16 illustrates a procedure for setting accessibility settings sharing upon device registration according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor (e.g., processor (220) of FIG. 2) of a first electronic device (310) (e.g., electronic device (201) of FIG. 2). In one embodiment, a memory of the first electronic device (310) (e.g., memory (230) of FIG. 2) may store instructions that cause the first electronic device (310) to operate according to at least one of the operations described below.

[0230] Referring to FIG. 16, in operation 1602, the first electronic device (310) (e.g., processor (220)) can run an IoT client application and log in (e.g., sign in) to the server (350) with a user account through the IoT client application. In operation 1604, the first electronic device (310) (e.g., processor (220)) can identify that the second electronic device (330) is a new device or an unregistered device through the IoT client application. In one embodiment, the first electronic device (310) (e.g., processor (220)) can display a user interface that encourages device registration.

[0231] In operation 1606, the first electronic device (310) (e.g., processor (220)) may receive user input accepting device registration for the second electronic device (330). In operation 1608, the first electronic device (310) (e.g., processor (220)) may perform a registration procedure for the second electronic device (330) based on the user input. The registration procedure may include transmitting network information (e.g., AP name and password) to the second electronic device (330) to connect to, and causing the second electronic device (330) to connect to the server (350) based on the network information. In one embodiment, the registration procedure may include transmitting user account information to the second electronic device (330) to use, and causing the second electronic device (330) to log in to the server (350) based on the user account information.

[0232] In operation 1610, the first electronic device (310) (e.g., processor (220)) may receive information (e.g., user account information) indicating that the second electronic device (330) is logged in from the server (350) or the second electronic device (330). In operation 1612, the first electronic device (310) (e.g., processor (220)) may perform an accessibility setting sharing procedure for the second electronic device (330). In one embodiment, the accessibility setting sharing procedure may include operations 1106, 1108, 1110, and 1112 of FIG. 11. By the accessibility setting sharing procedure, the second electronic device (330) may turn on an accessibility function that is the same or similar to that being used in the first electronic device (310).

[0233] In operation 1614, the first electronic device (310) (e.g., processor (220)) may display a notification indicating that the registration procedure, including sharing accessibility settings, has been completed.

[0234] FIG. 17 is a flowchart illustrating a procedure for sharing accessibility settings by an IoT device upon device registration according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor (e.g., processor (412) of FIG. 4a) of an IoT device (e.g., second electronic device (330)). In one embodiment, a memory of the second electronic device (330) (e.g., memory (416) of FIG. 4a) may store instructions that cause the second electronic device (330) to operate according to at least one of the operations described below.

[0235] Referring to FIG. 17, in operation 1702, a second electronic device (330) (e.g., processor (412)) may begin performing a registration procedure through a connection with a first electronic device (310). In one embodiment, the second electronic device (330) (e.g., processor (412)) may log in to a server (350) with a designated user account (e.g., a pre-stored user account or a user account entered by a user) through the registration procedure. In one embodiment, the second electronic device (330) (e.g., processor (412)) may receive user account information of the first electronic device (310) from the server (350) or the first electronic device (310) during the registration procedure.

[0236] In operation 1704, the second electronic device (330) (e.g., processor (412)) can determine whether the second electronic device (330) is logged in with the same user account as the first electronic device (310). If the second electronic device (330) is logged in with the same user account, the second electronic device (330) (e.g., processor (412)) can proceed to operation 1708. If the second electronic device (330) is not logged in with the same user account, the second electronic device (330) (e.g., processor (412)) can proceed to operation 1706.

[0237] In operation 1706, the second electronic device (330) (e.g., processor (412)) can perform an account switch to log in to the server (350) with the same user account as the user account of the first electronic device (310) based on the user account information of the first electronic device (310).

[0238] In operation 1708, the second electronic device (330) (e.g., processor (412)) may perform an accessibility setting sharing procedure for the second electronic device (330). In one embodiment, the accessibility setting sharing procedure may include operations 804, 806, 808, 810, and 812 of FIG. 8. By the accessibility setting sharing procedure, the second electronic device (330) (e.g., processor (412)) may turn on an accessibility function that is the same or similar to that being used in the first electronic device (310).

[0239] In operation 1710, the second electronic device (330) (e.g., processor (412)) may output visual or auditory information indicating that accessibility setting sharing is complete.

[0240] FIG. 18 illustrates a procedure for setting up accessibility settings sharing through account switching according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor (e.g., processor (220) of FIG. 2) of a first electronic device (310) (e.g., electronic device (201) of FIG. 2). In one embodiment, a memory of the first electronic device (310) (e.g., memory (230) of FIG. 2) may store instructions that cause the first electronic device (310) to operate according to at least one of the operations described below.

[0241] Referring to FIG. 18, in operation 1802, the first electronic device (310) (e.g., processor (220)) can detect a user interaction for recognizing the second electronic device (330). In one embodiment, the user interaction may include at least one of the following: physically contacting the first electronic device (310) with the second electronic device (330) (e.g., tapping); discovering the second electronic device (330) via a designated short-range communication method (e.g., Wi-Fi, Bluetooth, or UWB); or recognizing an NFC tag associated with the second electronic device (330). In one embodiment, the first electronic device (310) (e.g., processor (220)) can identify that the second electronic device (330) is logged in with a user account different from the user account of the first electronic device (310) based on user account information of the second electronic device (330) received from the server (350) or the second electronic device (330).

[0242] In operation 1804, the first electronic device (310) (e.g., processor (220)) may display an account switching confirmation user interface that guides the user to perform an account switching. In operation 1806, the first electronic device (310) (e.g., processor (220)) may receive user input through the account switching confirmation user interface that accepts the user to perform an account switching from the second electronic device (330). In operation 1808, the first electronic device (310) (e.g., processor (220)) may transmit information (e.g., user account information) to the second electronic device (330) that instructs the user to log in with the same user account as the user account of the first electronic device (310), based on the user input.

[0243] In operation 1810, the first electronic device (310) (e.g., processor (220)) can perform an accessibility setting sharing procedure for the second electronic device (330) based on identifying that the second electronic device (330) is logged in with the same user account as the user account of the first electronic device (310) by the account switching.

[0244] FIG. 19 is a flowchart illustrating a procedure for sharing accessibility settings by an IoT device during user interaction according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor (e.g., processor (412) of FIG. 4a) of an IoT device (e.g., second electronic device (330)). In one embodiment, a memory of the second electronic device (330) (e.g., memory (416) of FIG. 4a) may store instructions that cause the second electronic device (330) to operate according to at least one of the operations described below.

[0245] Referring to FIG. 19, in operation 1902, the second electronic device (330) (e.g., processor (412)) can detect a user interaction to recognize the first electronic device (310). In one embodiment, the user interaction may include an action identifying that the first electronic device (310) is physically contacted (e.g., tapped) with the second electronic device (330), or an action of discovering the first electronic device (310) via a designated short-range communication method (e.g., Wi-Fi, Bluetooth, or UWB).

[0246] In operation 1904, the second electronic device (330) (e.g., processor (412)) can determine whether the second electronic device (330) is logged in with the same user account as the first electronic device (310) based on detecting the user interaction. If the second electronic device (330) is logged in with the same user account, the second electronic device (330) (e.g., processor (412)) can proceed to operation 1908. If the second electronic device (330) is not logged in with the same user account, the second electronic device (330) (e.g., processor (412)) can proceed to operation 1906.

[0247] In operation 1906, the second electronic device (330) (e.g., processor (412)) can perform an account switch to log in to the server (350) with the same user account as the user account of the first electronic device (310) based on the user account information of the first electronic device (310).

[0248] In operation 1908, the second electronic device (330) (e.g., processor (412)) may perform an accessibility setting sharing procedure for the second electronic device (330). In one embodiment, the accessibility setting sharing procedure may include operations 804, 806, 808, 810, and 812 of FIG. 8. By the accessibility setting sharing procedure, the second electronic device (330) (e.g., processor (412)) may turn on an accessibility function that is the same or similar to that being used in the first electronic device (310).

[0249] In operation 1910, the second electronic device (330) (e.g., processor (412)) may output visual or auditory information indicating that accessibility settings have been completed (e.g., accessibility features have been applied).

[0250] FIG. 20a illustrates accessibility setting sharing based on voice commands according to an exemplary embodiment.

[0251] Referring to FIG. 20a, the second electronic device (330) may be logged in to User A's user account (e.g., Account A). In one embodiment, the second electronic device (330) may turn on accessibility feature A (e.g., high contrast screen feature (2002)) while logged in to Account A.

[0252] In one embodiment, the second electronic device (330) may receive a command requesting an account switch to User B. In one embodiment, the command may include a voice command (2004) of User B. In one embodiment, the second electronic device (330) may identify that the voice command (2004) includes the voice of User B through voice recognition of the voice command (2004), and may perform an account switch (e.g., re-login to Account B) to a pre-stored user account of User B (e.g., Account B).

[0253] In one embodiment, the second electronic device (330) can, upon receiving the voice command (2004), compare the voice characteristics of the voice command (2004) with the voice characteristics of a previously registered user and, based on the result of the comparison, identify that the voice command was spoken by user B. In one embodiment, the voice characteristics of the previously registered user may be stored in the second electronic device (330) in advance through an input means (e.g., a microphone) of the second electronic device (330), or may be stored in the second electronic device (330) through an external electronic device (e.g., a server (350), the second electronic device (310), or a hub) connected to the second electronic device (330).

[0254] In one embodiment, the second electronic device (330) may automatically perform an account switch to User B's account based on identifying the user of the voice command (e.g., User B), or automatically perform an account switch to the account of the identified user (e.g., User B or User C) based on the meaning of the voice command (e.g., "Change to my account" or "Log in as User C").

[0255] In one embodiment, the second electronic device (330) can identify an accessibility function B (e.g., voice guidance function (2006)) corresponding to Account B based on the account switching to Account B. In one embodiment, the second electronic device (330) can receive information indicating an accessibility function corresponding to Account B (e.g., accessibility function list (602)) from the server (350) or the first electronic device (310) logged in to Account B. In one embodiment, the second electronic device (330) can turn on the accessibility function B (e.g., voice guidance function (2006)) while logged in to Account B.

[0256] FIG. 20b illustrates accessibility setting sharing based on a short-range communication method according to an exemplary embodiment.

[0257] Referring to FIG. 20b, the first electronic device (310) can identify the presence of the second electronic device (330) based on a short-range communication method (2012) (e.g., Wi-Fi, Bluetooth, or UWB). In one embodiment, the first electronic device (310) can display an accessibility setting sharing user interface (2014) indicating an accessibility setting of the first electronic device (310) (e.g., at least one accessibility function) based on identifying the presence of the second electronic device (330). In one embodiment, the first electronic device (310) can receive user input accepting the accessibility setting sharing through the accessibility setting sharing user interface (2014). In one embodiment, the first electronic device (310) can transmit an accessibility setting instruction (2016) to the second electronic device (330) instructing it to apply the at least one accessibility function based on receiving the user input. In one embodiment, the second electronic device (330) may turn on the at least one accessibility function based on the accessibility setting instruction (2016) and output visual or auditory information (2018) indicating that accessibility setting sharing has been performed (e.g., "OO's accessibility setting has been applied" or "Accessibility function OO has been applied").

[0258] FIG. 21 is a flowchart illustrating a procedure for sharing accessibility settings by voice command according to an exemplary embodiment. According to the embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order. In one embodiment, at least one of the operations described below may be executed by a processor (e.g., processor (412) of FIG. 4a) of an IoT device (e.g., second electronic device (330)). In one embodiment, a memory of the second electronic device (330) (e.g., memory (416) of FIG. 4a) may store instructions that cause the second electronic device (330) to operate according to at least one of the operations described below.

[0259] Referring to FIG. 21, in operation 2102, the second electronic device (330) (e.g., processor (412)) receives a voice command and can identify, through voice recognition, that the voice command includes the voice of user A. In one embodiment, the voice command may include a command instructing an account switch (e.g., "Switch to my account") or a command instructing the second electronic device (330) to perform a unique function (e.g., "Turn on the TV").

[0260] In operation 2104, the second electronic device (330) (e.g., processor (412)) can determine whether the second electronic device (330) is logged in to User A's user account (e.g., Account A). If the second electronic device (330) is logged in to Account A, the second electronic device (330) (e.g., processor (412)) can proceed to operation 2114. In operation 2114, the second electronic device (330) (e.g., processor (412)) can perform the function according to the voice command or return to the existing function. If the second electronic device (330) is not logged in to Account A, the second electronic device (330) (e.g., processor (412)) can proceed to operation 2106.

[0261] In operation 2106, the second electronic device (330) (e.g., processor (412)) can determine whether re-login to account A is possible. In one embodiment, if the login information of account A (e.g., account name and password) is not stored, the second electronic device (330) (e.g., processor (412)) can determine that re-login to account A is not possible and proceed to operation 2114. In one embodiment, if the login information of account A (e.g., account name and password) is stored, the second electronic device (330) (e.g., processor (412)) can determine that re-login to account A is possible and proceed to operation 2108.

[0262] In operation 2108, the second electronic device (330) (e.g., processor (412)) can determine whether there is an accessibility setting (e.g., at least one accessibility function) corresponding to account A. If there is no accessibility setting corresponding to account A, the second electronic device (330) (e.g., processor (412)) can proceed to operation 2110. If there is an accessibility setting corresponding to account A, the second electronic device (330) (e.g., processor (412)) can proceed to operation 2112.

[0263] In operation 2110, the second electronic device (330) (e.g., processor (412)) can perform re-login to account A through account switching. After operation 2110, the second electronic device (330) (e.g., processor (412)) can proceed to operation 2114 and return to the existing function.

[0264] In operation 2112, the second electronic device (330) (e.g., processor (412)) can perform an accessibility setting sharing procedure corresponding to account A after re-logging into account A through account switching. In one embodiment, the accessibility setting sharing procedure may include operations 804, 806, 808, 810, and 812 of FIG. 8. After operation 2112, the second electronic device (330) (e.g., processor (412)) can proceed to operation 2114 and return to the existing function.

[0265] According to an exemplary embodiment, when setting synchronization is performed, accessibility information of the first electronic device (310) and the second electronic device (330) is analyzed, and based on this, accessibility settings of the first electronic device (310) can be applied to the second electronic device (330). According to an exemplary embodiment, accessibility settings can be switched according to the user account through account switching, and accessibility settings currently in use on the first electronic device (310) can be synchronized with the second electronic device (330) based on the user account.

[0266] According to an exemplary embodiment, the user's accessibility experience can be improved by sharing commonly available accessibility features among a plurality of devices (e.g., a first electronic device (310) and a second electronic device (330)).

[0267] A second electronic device (330) according to an exemplary embodiment may include a communication circuit (414) configured to support a communication connection, a memory (416) for storing instructions, and at least one processor (412) functionally connected to the communication circuit and the memory. When the instructions are executed individually or collectively by the at least one processor, the second electronic device may be made to: log in to a server with a user account via the communication circuit based on an application, and when the first electronic device is logged in to the server with the user account based on the application, receive an accessibility function list representing at least one accessibility function from the server or the first electronic device via the communication circuit, identify at least one accessibility function that can be used by the second electronic device among the at least one accessibility function corresponding to the accessibility function list, identify a first accessibility function that is not in use by the second electronic device among the identified at least one accessibility function, and apply an accessibility setting corresponding to the identified first accessibility function to the second electronic device.

[0268] A first electronic device (310) according to an exemplary embodiment may include a communication circuit (292) configured to support a communication connection, a memory (230) for storing instructions, and at least one processor (220) functionally connected to the communication circuit and the memory. When the above instructions are executed individually or collectively by the at least one processor, the first electronic device may: receive a user interaction for the first electronic device while the first electronic device is logged into a server with a user account based on an application; control the second electronic device through the communication circuit so that, in response to the user interaction, the second electronic device is logged into the server with the user account; detect an event in which the second electronic device is logged into the server with the user account through the application; identify at least one accessibility function set in the first electronic device based on the detection of the event; and transmit an accessibility function list representing the at least one accessibility function to the server or the second electronic device through the communication circuit, thereby enabling the second electronic device to apply an accessibility setting corresponding to the accessibility function list.

[0269] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the first electronic device may transmit a signal to the server requesting at least one accessibility function to be applied to the second electronic device based on the user interaction.

[0270] In one embodiment, the accessibility function list may include a list of at least one accessibility function applicable to the second electronic device among one or more accessibility functions available in the first electronic device.

[0271] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the first electronic device may share the at least one accessibility function with the second electronic device based on identifying that onboarding of the second electronic device is performed, receiving user input requesting the sharing of accessibility settings for the second electronic device, or identifying that the first electronic device accesses the second electronic device.

[0272] A server according to an exemplary embodiment may include a communication circuit configured to support a communication connection, at least one processor functionally connected to the communication circuit, and a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the server may: identify that a first electronic device is logged into the server with a user account, identify that a second electronic device is logged into the server with the user account, and identify that the second electronic device is logged in while the first electronic device is logged in, based on identifying that the second electronic device is logged in while the first electronic device is logged in, identify at least one accessibility function among one or more accessibility functions set in the first electronic device that can be used by the second electronic device, and transmit an accessibility function list representing the at least one accessibility function to the second electronic device through the communication circuit.

[0273] A second electronic device (330) according to an exemplary embodiment may include a communication circuit (414), at least one processor (412), and a memory (416) for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the second electronic device may: log in to a server (350) with a user account through the communication circuit. When the instructions are executed individually or collectively by the at least one processor, the second electronic device may: receive through the communication circuit an accessibility function list indicating at least one accessibility function in use by the first electronic device (310) while the second electronic device is logged in to the user account, wherein the first electronic device is logged in to the server with the user account. When the instructions are executed individually or collectively by the at least one processor, the second electronic device may: identify at least one accessibility function available to the second electronic device from the accessibility function list. When the above instructions are executed individually or collectively by the at least one processor, the second electronic device may: identify a first accessibility function that is not in use by the second electronic device among at least one accessibility function available to the second electronic device. When the above instructions are executed individually or collectively by the at least one processor, the second electronic device may: apply the first accessibility function to the second electronic device.

[0274] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the second electronic device may transmit a signal requesting the accessibility feature list to the server or the first electronic device based on the fact that the second electronic device is first registered with the server after onboarding.

[0275] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the second electronic device may transmit a signal requesting the accessibility feature list to the server or the first electronic device based on detecting a specified user action while the second electronic device is logged in with the user account.

[0276] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the second electronic device may be made to re-login to the user account through account switching based on identifying that the second electronic device is logged in to a first user account different from the user account.

[0277] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the second electronic device may be enabled to: transmit accessibility setting sharing information for the first accessibility function to the first electronic device, and, after transmitting the accessibility setting sharing information, apply the first accessibility function to the second electronic device based on receiving information from the first electronic device that accepts applying the first accessibility function to the second electronic device.

[0278] In one embodiment, the first accessibility function may include at least one of voice guidance, high contrast screen, color inversion, black and white screen, relumino mode, screen description, or closed caption.

[0279] A server (350) according to an exemplary embodiment may include a communication circuit (424), at least one processor (422), and a memory (426) for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the server may identify that the first electronic device (310) is logged in to the user account. When the instructions are executed individually or collectively by the at least one processor, the server may identify that the second electronic device (330) is logged in to the user account. When the instructions are executed individually or collectively by the at least one processor, the server may receive through the communication circuit a first accessibility function list indicating at least one accessibility function in use by the first electronic device while the first electronic device and the second electronic device are logged in to the user account. When the above instructions are executed individually or collectively by the at least one processor, the server may receive, through the communication circuit, a second accessibility function list indicating at least one accessibility function in use by the second electronic device while the first electronic device and the second electronic device are logged in with the user account. When the above instructions are executed individually or collectively by the at least one processor, the server may identify at least one accessibility function available to the second electronic device from the first accessibility function list. When the above instructions are executed individually or collectively by the at least one processor, the server may identify, based on the second accessibility function list, a first accessibility function that is not in use by the second electronic device among the identified at least one accessibility function.When the above instructions are executed individually or collectively by the at least one processor, the server may: transmit an accessibility setting instruction to the second electronic device through the communication circuit, which instructs the application of the identified first accessibility function.

[0280] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the server may cause the server to transmit a signal to the second electronic device requesting the second accessibility feature list based on the fact that the second electronic device is first registered with the server after onboarding.

[0281] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the server may: transmit a signal requesting the first accessibility feature list to the first electronic device, or / or transmit a signal requesting the second accessibility feature list to the second electronic device, based on receiving a designated request signal from the first electronic device or the second electronic device.

[0282] In one embodiment, when the instructions are executed individually or collectively by the at least one processor, the server may: transmit accessibility setting sharing information for the first accessibility function to the first electronic device, and, after transmitting the accessibility setting sharing information, transmit the accessibility setting instruction to the second electronic device based on receiving information from the first electronic device that accepts applying the first accessibility function to the second electronic device.

[0283] A first electronic device (310) according to an exemplary embodiment may include a communication circuit (292), at least one processor (220), and a memory (230) for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the first electronic device may identify that the second electronic device (330) is logged in to the user account while the first electronic device is logged in to the server (350) as a user account based on the execution of an application. When the instructions are executed individually or collectively by the at least one processor, the first electronic device may transmit an accessibility function list indicating at least one accessibility function in use by the first electronic device to the server or the second electronic device through the communication circuit, based on identifying that the second electronic device is logged in to the user account. When the above instructions are executed individually or collectively by the at least one processor, the first electronic device may: after transmitting the accessibility function list, receive accessibility setting sharing information representing a first accessibility function among the at least one accessibility function from the server or the second electronic device through the communication circuit. When the above instructions are executed individually or collectively by the at least one processor, the first electronic device may: after displaying a user interface including the accessibility setting sharing information, receive user input accepting to apply the first accessibility function to the second electronic device through the user interface.When the above instructions are executed individually or collectively by the at least one processor, the first electronic device may transmit information accepting the application of the first accessibility function to the second electronic device, either through the server or directly to the second electronic device, based on receiving the user input.

[0284] A method by a second electronic device (330) according to an exemplary embodiment may include: an operation (802) of logging into a server (350) with a user account; an operation (804) of obtaining an accessibility function list representing at least one accessibility function in use by a first electronic device (310) while the second electronic device is logged into the server with the user account, wherein the first electronic device is logged into the server with the user account and the operation (806) of identifying at least one accessibility function available to the second electronic device from the accessibility function list; an operation (808) of identifying a first accessibility function not in use by the second electronic device among at least one accessibility function available to the second electronic device; and an operation (812) of applying the first accessibility function to the second electronic device.

[0285] In one embodiment, the method may further include the operation of transmitting a signal requesting the accessibility feature list to the server or the first electronic device based on the fact that the second electronic device is registered with the server for the first time after onboarding.

[0286] In one embodiment, the method may further include the operation of transmitting a signal requesting the accessibility function list to the server or the first electronic device based on detecting a specified user action while the second electronic device is logged in with the user account.

[0287] In one embodiment, the login operation may include re-logging into the user account through account switching based on identifying that the second electronic device is logged in with a first user account different from the user account.

[0288] In one embodiment, the applying operation may include the operation of transmitting accessibility setting sharing information for the first accessibility function to the first electronic device, and the operation of applying the first accessibility function to the second electronic device based on receiving information from the first electronic device that accepts applying the first accessibility function to the second electronic device after transmitting the accessibility setting sharing information.

[0289] A method by a server (350) according to an exemplary embodiment comprises: an action (902) of identifying that a first electronic device (310) is logged in to a user account; an action (904) of identifying that a second electronic device (330) is logged in to the user account; an action (906) of receiving a first accessibility function list indicating at least one accessibility function in use by the first electronic device while the first electronic device and the second electronic device are logged in to the user account; an action (906) of receiving a second accessibility function list indicating at least one accessibility function in use by the second electronic device while the first electronic device and the second electronic device are logged in to the user account; an action (908) of identifying at least one accessibility function available to the second electronic device from the first accessibility function list; an action (910) of identifying a first accessibility function not in use by the second electronic device among the identified at least one accessibility function based on the second accessibility function list; and transmitting an accessibility setting instruction to the second electronic device instructing to apply the identified first accessibility function. It may include operation (914).

[0290] In one embodiment, the method may further include the operation of transmitting a signal to the second electronic device requesting the second accessibility feature list based on the fact that the second electronic device is registered with the server for the first time after onboarding.

[0291] In one embodiment, the method may further include the operation of transmitting a signal requesting the first accessibility function list to the first electronic device or / or transmitting a signal requesting the second accessibility function list to the second electronic device based on receiving a designated request signal from the first electronic device or the second electronic device. The term "based on" as used herein may cover at least "based on".

[0292] In one embodiment, the operation of transmitting the accessibility setting instruction may include the operation of transmitting accessibility setting sharing information for the first accessibility function to the first electronic device, and the operation of transmitting the accessibility setting instruction to the second electronic device based on receiving information from the first electronic device that accepts applying the first accessibility function to the second electronic device after transmitting the accessibility setting sharing information.

[0293] Each embodiment described herein may be used in combination with other embodiments described herein.

[0294] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0295] 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 component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component. Thus, for example, the term “connected” as used in this disclosure covers both direct and indirect connections.

[0296] The term “module” as used in the various embodiments of this document 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. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC). Accordingly, each “module” in this disclosure may include a circuit.

[0297] Various embodiments of the present document may be implemented as software (e.g., program (240)) comprising one or more instructions stored in a storage medium (e.g., internal memory (236) or external memory (238)) readable by a machine (e.g., electronic device (201)). For example, a processor (e.g., processor (220)) of the machine (e.g., electronic device (201)) may call at least one of the one or more instructions stored from the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0298] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or an application store (e.g., Play Store). TM It can be distributed online (e.g., downloaded or uploaded) through ) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0299] 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.

[0300] Although the present disclosure has been illustrated and described with reference to various embodiments, it should be understood that the various embodiments are illustrative and not limiting. Furthermore, those skilled in the art should understand that various modifications to the form and details may be made without departing from the true spirit and full scope of the present disclosure, including the appended claims and their equivalents. Additionally, it should be understood that any embodiment described in the present disclosure may be used in conjunction with any other embodiment described in the present disclosure.

Claims

In the second electronic device (330), Communication circuit (414); At least one processor (412) including a processing circuit; and It includes a memory (416) for storing instructions, and when the instructions are executed individually and / or collectively by the at least one processor, the second electronic device: At least log in to the server (350) with a user account through the communication circuit above, and While the second electronic device is logged in with the user account, it receives an accessibility function list indicating at least one accessibility function in use in the first electronic device (310) logged in to the server with the user account, and Identifying at least one accessibility function available by the second electronic device from the above list of accessibility functions, and Among at least one accessibility function available by the second electronic device, a first accessibility function not in use by the second electronic device is identified, and A second electronic device that enables the application of the first accessibility function to the second electronic device. A second electronic device according to claim 1, wherein when the instructions are executed individually and / or collectively by the at least one processor, the second electronic device transmits a signal requesting the accessibility feature list to the server and / or the first electronic device based on the second electronic device being registered with the server for the first time after onboarding. In claim 1, a second electronic device that, when the instructions are executed individually and / or collectively by the at least one processor, causes the second electronic device to transmit a signal requesting the accessibility feature list to the server and / or the first electronic device based on detecting a specified user action while the second electronic device is logged in with the user account. A second electronic device according to any one of claims 1 to 3, wherein, when the instructions are executed individually and / or collectively by the at least one processor, the second electronic device causes the second electronic device to log in again to the user account through account switching based on identifying that the second electronic device is logged in to a first user account different from the user account. In any one of claims 1 to 4, when the instructions are executed individually and / or collectively by the at least one processor, the second electronic device: Transmitting accessibility setting sharing information for the above-mentioned first accessibility function to the above-mentioned first electronic device, and A second electronic device that applies the first accessibility function to the second electronic device based on receiving information from the first electronic device that accepts applying the first accessibility function to the second electronic device after transmitting the above accessibility setting sharing information. In any one of claims 1 to 5, the first accessibility function is, A second electronic device comprising at least one of voice guidance, high contrast screen, color inversion, black and white screen, relumino mode, screen description, or closed caption. In the server (350), Communication circuit (424); At least one processor (422) including a processing circuit; and It includes a memory (426) for storing instructions, and when the instructions are executed individually and / or collectively by the at least one processor, the server: Identifying that the first electronic device (310) is logged in with a user account, Identifying that the second electronic device (330) is logged in with the user account, While the first electronic device and the second electronic device are logged in with the user account, a first accessibility function list indicating at least one accessibility function in use by the first electronic device is received through at least the communication circuit, and While the first electronic device and the second electronic device are logged in with the user account, a second accessibility function list representing at least one accessibility function in use on the second electronic device is received, and Identifying at least one accessibility function available by the second electronic device in the above first accessibility function list, and Based on the above list of second accessibility functions, among the identified at least one accessibility function, a first accessibility function not in use in the second electronic device is identified, and A server that transmits an accessibility setting instruction to the second electronic device, which instructs the application of the first accessibility function identified above. In claim 7, when the instructions are executed individually and / or collectively by the at least one processor, the server: A server that transmits a signal requesting the second accessibility feature list to the second electronic device based on the fact that the second electronic device is registered with the server for the first time after onboarding. In claim 7, when the instructions are executed individually and / or collectively by the at least one processor, the server: A server that, based on receiving a designated request signal from the first electronic device and / or the second electronic device, transmits a signal requesting the first accessibility function list to the first electronic device, and / or transmits a signal requesting the second accessibility function list to the second electronic device. In claim 7, when the instructions are executed individually and / or collectively by the at least one processor, the server: Transmitting accessibility setting sharing information for the above-mentioned first accessibility function to the above-mentioned first electronic device, and A server that transmits the accessibility setting instruction to the second electronic device based on receiving information from the first electronic device that accepts applying the first accessibility function to the second electronic device after transmitting the accessibility setting sharing information. In the first electronic device (310), Communication circuit (292); At least one processor (220) including a processing circuit; and It includes a memory (230) for storing instructions, and when the instructions are executed individually or collectively by the at least one processor, the first electronic device: Based on the execution of the application, while the first electronic device is logged into the server (350) with a user account, it is identified that the second electronic device (330) is logged into the user account, and Based on identifying that the second electronic device is logged in with the user account, an accessibility function list representing at least one accessibility function in use by the first electronic device is transmitted to the server and / or the second electronic device through at least the communication circuit, and After transmitting the above accessibility function list, accessibility setting sharing information representing a first accessibility function among the at least one accessibility function is received from the server and / or the second electronic device, and After displaying a user interface including the accessibility setting sharing information, receiving user input that accepts applying the first accessibility function to the second electronic device through the user interface, and A first electronic device that transmits information accepting the application of the first accessibility function to the second electronic device, either through the server or directly to the second electronic device, based on receiving the above user input. In the method using the second electronic device (330), The action (802) of logging into the server (350) with a user account; While the second electronic device is logged in with the user account, the operation (804) of obtaining an accessibility function list representing at least one accessibility function in use in the first electronic device (310) logged in with the user account on the server; An operation (806) to identify at least one accessibility function available to the second electronic device in the above list of accessibility functions; Among at least one accessibility function available by the second electronic device, an operation (808) of identifying a first accessibility function that is not in use by the second electronic device; A method including an operation (812) of applying the first accessibility function to the second electronic device. In Article 12, A method further comprising the operation of transmitting a signal requesting the accessibility feature list to the server and / or the first electronic device based on the fact that the second electronic device is registered with the server for the first time after onboarding. In Article 12, A method further comprising the operation of transmitting a signal requesting the accessibility function list to the server and / or the first electronic device based on detecting a specified user action while the second electronic device is logged in with the user account. In the method by the server (350), An action (902) that identifies that the first electronic device (310) is logged in with a user account; An action (904) that identifies that the second electronic device (330) is logged in with the user account; While the first electronic device and the second electronic device are logged in with the user account, the operation (906) of receiving a first accessibility function list indicating at least one accessibility function in use on the first electronic device; While the first electronic device and the second electronic device are logged in with the user account, the operation (906) of receiving a second accessibility function list indicating at least one accessibility function in use on the second electronic device; An operation (908) to identify at least one accessibility function available to the second electronic device in the first accessibility function list above; Based on the second accessibility function list above, an operation (910) of identifying a first accessibility function that is not in use in the second electronic device among at least one identified accessibility function; and A method comprising the operation (914) of transmitting an accessibility setting instruction to the second electronic device that instructs the application of the first accessibility function identified above.

Images