Electronic device and method for managing and displaying avatars of multiple providers

Abstract

This wearable device may comprise: a memory for storing instructions; a display; and at least one processor. The instructions, when executed individually or collectively by the at least one processor, may instruct the wearable device to: display a task bar including an icon of a first software application for integrating avatars provided by source applications; execute a second software application for providing a virtual environment stored in the wearable device on the basis of at least a part of a user input; display the virtual environment including a first avatar in a first state in which the first avatar provided by the second software application is set for the second software application; and display the virtual environment including a second avatar from among the avatars on the basis of the icon for displaying the second avatar in a second state different from the first state.

Description

Electronic device and method for managing and displaying avatars of multiple providers

[0001] The descriptions below relate to electronic devices and methods for managing and displaying avatars of multiple providers.

[0002] To provide an enhanced user experience, electronic devices are being developed that provide extended reality services that display computer-generated information in conjunction with external objects in the real world or virtual objects in the virtual world. The electronic devices may include wearable devices that can be worn by a user. For example, the electronic devices may include user equipment, AR glasses, VR glasses, and / or a head-mounted device (HMD) (e.g., a video see-through (VST) HMD, an optical see-through (OST) HMD).

[0003] A wearable device may include a display. The wearable device may include at least one processor. The at least one processor may be configured to display, through the display, a global menu (task bar) including an icon of a first software application for merging avatars provided by source applications. The icon may include an area for displaying an avatar among the avatars. The at least one processor may be configured to execute a second software application that provides a virtual environment stored in the wearable device based on at least a portion of a user's input. The at least one processor may be configured to display, through the display, the virtual environment including the first avatar in a first state in which the first avatar provided by the second software application is set for the second software application. The at least one processor may be configured to display, through the display, the virtual environment including the second avatar based on the icon displaying the second avatar among the avatars in a second state different from the first state.

[0004] A method performed by a wearable device may include an operation of displaying, through the display, a task bar including an icon of a first software application for merging avatars provided by source applications. The icon may include an area for displaying a set avatar among the avatars. The method may include an operation of executing a second software application that provides a virtual environment stored in the wearable device based on at least a portion of a user's input. The method may include an operation of displaying the virtual environment including the first avatar in a first state in which the first avatar provided by the second software application is set for the second software application. The method may include an operation of displaying the virtual environment including the second avatar in a second state different from the first state, based on the icon displaying the second avatar among the avatars.

[0005] A non-transitory computer-readable storage medium may store one or more programs comprising instructions that, when executed by at least one processor of a wearable device including a display, cause a task bar to be displayed through the display, the task bar including an icon of a first software application for merging avatars provided by source applications. The icon may include an area for displaying a set avatar from among the avatars. The non-transitory computer-readable storage medium may store one or more programs comprising instructions that, when executed by the at least one processor, cause a second software application to be executed for providing a virtual environment stored within the wearable device based on at least a portion of a user's input. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed by the at least one processor, cause the second software application to display, through the display, the virtual environment including the first avatar, in a first state set for the second software application. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed by the at least one processor, cause the second software application to display, through the display, the virtual environment including the second avatar, based on the icon representing the second avatar among the avatars, in a second state different from the first state.

[0006] FIG. 1 is a block diagram of an electronic device within a network environment according to various embodiments.

[0007] FIG. 2A illustrates an example of a perspective view of a wearable device according to various embodiments.

[0008] FIG. 2b illustrates an example of one or more hardware elements arranged within a wearable device according to various embodiments.

[0009] FIGS. 3A and 3B illustrate examples of the appearance of a wearable device according to various embodiments.

[0010] FIG. 4A illustrates an example of how a wearable device manages avatars obtained from multiple providers and displays the avatars in a software application of the wearable device.

[0011] Figure 4b illustrates an example of avatar synchronization performed between multiple providers, wearable devices, and external electronic devices.

[0012] Figure 5 illustrates an exemplary block diagram of a wearable device.

[0013] Figure 6 illustrates an example of an operational flow for managing avatars obtained from multiple providers and displaying the avatars in a software application of a wearable device.

[0014] Figure 7a illustrates an example of a method for obtaining avatar-related information from multiple providers.

[0015] Figures 7b and 7c illustrate examples of a method for performing processing on avatar-related information.

[0016] Figure 8a illustrates examples of a user interface of a first software application for integrating avatars.

[0017] Figure 8b illustrates an example of how to edit an avatar through a first software application.

[0018] Figure 9a illustrates an example of how a virtual environment provided by a second software application may be displayed.

[0019] Figure 9b illustrates an example of how to handle an avatar displayed within a virtual environment provided by a second software application.

[0020] FIG. 10A illustrates an example of how to display an integrated avatar in a first software application based on the state of a second software application.

[0021] Figure 10b illustrates an example of how to set a default avatar for each second software application.

[0022] Figures 11a and 11b illustrate examples of virtual objects displayed within a virtual environment while changing at least a portion of an avatar.

[0023] Figures 12a to 12c illustrate examples of a method of using a second software application through login information associated with an avatar of a first software application.

[0024] Figure 13 illustrates an example of an operational flow for a wearable device to manage avatars obtained from multiple providers and display the avatars in a software application of the wearable device.

[0025] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0026] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0027] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled. However, this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." Conditions described as "more than" may be replaced with "more than," conditions described as "less than," and conditions described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of the elements from A (including A) to B (including B).

[0028] FIG. 1 is a block diagram of an electronic device within a network environment according to various embodiments.

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

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

[0031] The auxiliary processor (123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (160), a sensor module (176), or a communication module (190)) of the electronic device (101), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or can be performed through a separate server (e.g., server (108)). The learning algorithm can 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 can include multiple artificial neural network layers.The artificial neural network may be one of 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, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

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

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

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

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

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

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

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

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

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

[0041] A haptic module (179) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. In one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

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

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

[0044] A battery (189) may power at least one component of the electronic device (101). In one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

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

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

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

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

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

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

[0051] FIG. 2A illustrates an example of a perspective view of a wearable device according to various embodiments. FIG. 2B illustrates an example of one or more hardware components arranged within a wearable device according to various embodiments.

[0052] According to one embodiment, the wearable device (103) may have the form of glasses that are wearable on a body part of the user (e.g., the head). The wearable device (103) of FIGS. 2A and 2B may be an example of the electronic device (101) of FIG. 1. The wearable device (103) may include a head-mounted display (HMD). For example, the housing of the wearable device (103) may include a flexible material, such as rubber and / or silicone, that is configured to fit closely to a portion of the user's head (e.g., a portion of the face surrounding both eyes). For example, the housing of the wearable device (103) may include one or more straps that are capable of being twined around the user's head, and / or one or more temples that are detachably attachable to the ears of the head.

[0053] Referring to FIG. 2A, according to one embodiment, a wearable device (103) may include at least one display (250) and a frame (200) supporting at least one display (250).

[0054] According to one embodiment, the wearable device (103) can be worn on a part of a user's body. The wearable device (103) can provide extended reality (XR) to the user wearing the wearable device (103). For example, the extended reality can provide augmented reality (AR), virtual reality (VR), or mixed reality (MR) that combines augmented reality and virtual reality. For example, the wearable device (103) can display a virtual reality image provided from at least one optical device (282, 284) of FIG. 2B on at least one display (250) in response to a user's designated gesture acquired through the motion recognition cameras (260-2, 263) of FIG. 2B.

[0055] According to one embodiment, at least one display (250) may provide visual information to a user. For example, at least one display (250) may include a transparent or translucent lens. At least one display (250) may include a first display (250-1) and / or a second display (250-2) spaced apart from the first display (250-1). For example, the first display (250-1) and the second display (250-2) may be positioned at positions corresponding to the user's left and right eyes, respectively.

[0056] Referring to FIG. 2B, at least one display (250) can provide the user with visual information transmitted from external light and other visual information distinct from the visual information through a lens included in the at least one display (250). The lens can be formed based on at least one of a Fresnel lens, a pancake lens, or a multi-channel lens. For example, the at least one display (250) can include a first surface (231) and a second surface (232) opposite to the first surface (231). A display area can be formed on the second surface (232) of the at least one display (250). When the user wears the wearable device (103), external light can be transmitted to the user by being incident on the first surface (231) and transmitted through the second surface (232). As another example, at least one display (250) can display an augmented reality image combined with a virtual reality image provided from at least one optical device (282, 284) on a real screen transmitted through external light, in a display area formed on the second surface (232).

[0057] In one embodiment, at least one display (250) may include at least one waveguide (233, 234) that diffracts light emitted from at least one optical device (282, 284) and transmits the diffracted light to a user. The at least one waveguide (233, 234) may be formed based on at least one of glass, plastic, or polymer. A nano-pattern may be formed on at least a portion of the exterior or interior of the at least one waveguide (233, 234). The nano-pattern may be formed based on a grating structure having a polygonal and / or curved shape. Light incident on one end of the at least one waveguide (233, 234) may be propagated to the other end of the at least one waveguide (233, 234) by the nano-pattern. At least one waveguide (233, 234) may include at least one diffractive element (e.g., a diffractive optical element (DOE), a holographic optical element (HOE)) and at least one reflective element (e.g., a reflective mirror). For example, at least one waveguide (233, 234) may be arranged within the wearable device (103) to guide a screen displayed by at least one display (250) to the user's eyes. For example, the screen may be transmitted to the user's eyes based on total internal reflection (TIR) ​​occurring within the at least one waveguide (233, 234).

[0058] The wearable device (103) can analyze an object included in a real image collected through a shooting camera (260-4), combine a virtual object corresponding to an object to be provided with augmented reality among the analyzed objects, and display the virtual object on at least one display (250). The virtual object can include at least one of text and an image regarding various information related to the object included in the real image. The wearable device (103) can analyze the object based on a multi-camera such as a stereo camera. For the object analysis, the wearable device (103) can perform spatial recognition (e.g., simultaneous localization and mapping (SLAM)) using a multi-camera and / or time-of-flight (ToF). A user wearing the wearable device (103) can view an image displayed on at least one display (250).

[0059] According to one embodiment, the frame (200) may be configured as a physical structure that allows the wearable device (103) to be worn on the user's body. According to one embodiment, the frame (200) may be configured so that, when the user wears the wearable device (103), the first display (250-1) and the second display (250-2) can be positioned corresponding to the user's left and right eyes. The frame (200) may support at least one display (250). For example, the frame (200) may support the first display (250-1) and the second display (250-2) to be positioned corresponding to the user's left and right eyes.

[0060] Referring to FIG. 2A, the frame (200) may include a region (220) that is in contact with at least a portion of a user's body when the user wears the wearable device (103). For example, the region (220) of the frame (200) that is in contact with a portion of the user's body may include a region that is in contact with a portion of the user's nose, a portion of the user's ear, and a portion of the side of the user's face that the wearable device (103) makes contact with. According to one embodiment, the frame (200) may include a nose pad (210) that is in contact with a portion of the user's body. When the wearable device (103) is worn by the user, the nose pad (210) may be in contact with a portion of the user's nose. The frame (200) may include a first temple (204) and a second temple (205) that are in contact with another portion of the user's body that is distinct from the portion of the user's body.

[0061] For example, the frame (200) may include a first rim (201) that surrounds at least a portion of the first display (250-1), a second rim (202) that surrounds at least a portion of the second display (250-2), a bridge (203) that is disposed between the first rim (201) and the second rim (202), a first pad (211) that is disposed along a portion of the edge of the first rim (201) from one end of the bridge (203), a second pad (212) that is disposed along a portion of the edge of the second rim (202) from the other end of the bridge (203), a first temple (204) that extends from the first rim (201) and is fixed to a portion of the wearer's ear, and a second temple (205) that extends from the second rim (202) and is fixed to a portion of the ear opposite the ear. The first pad (211) and the second pad (212) may be in contact with a portion of the user's nose, and the first temple (204) and the second temple (205) may be in contact with a portion of the user's face and a portion of the user's ear. The temples (204, 205) may be rotatably connected to the rim through the hinge units (206, 207) of FIG. 2B. The first temple (204) may be rotatably connected to the first rim (201) through the first hinge unit (206) disposed between the first rim (201) and the first temple (204). The second temple (205) may be rotatably connected to the second rim (202) through the second hinge unit (207) disposed between the second rim (202) and the second temple (205). According to one embodiment, the wearable device (103) can identify an external object (e.g., a user's fingertip) touching the frame (200) and / or a gesture performed by the external object by using a touch sensor, a grip sensor, and / or a proximity sensor formed on at least a portion of a surface of the frame (200).

[0062] According to one embodiment, the wearable device (103) may include hardwares that perform various functions (e.g., hardwares to be described later based on the block diagram of FIG. 5). For example, the hardwares may include a battery module (270), an antenna module (275), at least one optical device (282, 284), speakers (e.g., speakers 255-1, 255-2), a microphone (e.g., microphones 265-1, 265-2, 265-3), a light-emitting module (not shown), and / or a printed circuit board (PCB) (290) (e.g., a printed circuit board). The various hardwares may be arranged within the frame (200).

[0063] According to one embodiment, the microphones (e.g., microphones 265-1, 265-2, 265-3) of the wearable device (103) may be disposed on at least a portion of the frame (200) to acquire sound signals. A first microphone (265-1) disposed on the bridge (203), a second microphone (265-2) disposed on the second rim (202), and a third microphone (265-3) disposed on the first rim (201) are illustrated in FIG. 2B , but the number and arrangement of the microphones (265) are not limited to the embodiment of FIG. 2B . When the number of microphones (265) included in the wearable device (103) is two or more, the wearable device (103) may identify the direction of the sound signal by using a plurality of microphones disposed on different portions of the frame (200).

[0064] According to one embodiment, at least one optical device (282, 284) can project a virtual object onto at least one display (250) to provide various image information to a user. For example, at least one optical device (282, 284) can be a projector. At least one optical device (282, 284) can be disposed adjacent to at least one display (250) or can be included within at least one display (250) as a part of at least one display (250). According to one embodiment, the wearable device (103) can include a first optical device (282) corresponding to a first display (250-1) and a second optical device (284) corresponding to a second display (250-2). For example, at least one optical device (282, 284) may include a first optical device (282) disposed at an edge of a first display (250-1) and a second optical device (284) disposed at an edge of a second display (250-2). The first optical device (282) may transmit light to a first waveguide (233) disposed on the first display (250-1), and the second optical device (284) may transmit light to a second waveguide (234) disposed on the second display (250-2).

[0065] In one embodiment, the camera (260) may include a recording camera (260-4), an eye tracking camera (ET CAM) (260-1), and / or a motion recognition camera (260-2, 260-3). The recording camera (260-4), the eye tracking camera (260-1), and the motion recognition cameras (260-2, 260-3) may be positioned at different locations on the frame (200) and may perform different functions. The eye tracking camera (260-1) may output data indicating the position or gaze of the eyes of a user wearing the wearable device (103). For example, the wearable device (103) may detect the gaze from an image including the user's pupils obtained through the eye tracking camera (260-1). The wearable device (103) can perform gaze interaction with at least one object using the user's gaze acquired through the gaze tracking camera (260-1). The wearable device (103) can express a portion corresponding to the eye of an avatar representing the user in a virtual space using the user's gaze acquired through the gaze tracking camera (260-1). The wearable device (103) can render an image (or screen) displayed on at least one display (250) based on the position of the user's eyes. For example, the visual quality (e.g., resolution, brightness, saturation, grayscale, PPI) of a first region related to the gaze and a second region distinguished from the first region within the image may be different from each other. For example, if the wearable device (103) supports an iris recognition function, user authentication can be performed based on iris information acquired using the gaze tracking camera (260-1).An example in which the gaze tracking camera (260-1) is positioned toward the user's right eye is illustrated in FIG. 2B, but the embodiment is not limited thereto, and the gaze tracking camera (260-1) may be positioned solely toward the user's left eye, or may be positioned toward both eyes.

[0066] In one embodiment, the capturing camera (260-4) can capture an actual image or background to be aligned with a virtual image in order to implement augmented reality or mixed reality content. The capturing camera (260-4) can capture an image of a specific object existing at a location viewed by the user and provide the image to at least one display (250). The at least one display (250) can display a single image in which information about an actual image or background including an image of the specific object acquired using the capturing camera (260-4) is superimposed on a virtual image provided through at least one optical device (282, 284). The wearable device (103) can compensate for depth information (e.g., the distance between the wearable device (103) and an external object acquired using a depth sensor) using the image acquired using the capturing camera (260-4). The wearable device (103) can perform object recognition using the image acquired using the capturing camera (260-4). The wearable device (103) may perform a pass-through function to display an image acquired through a photographing camera (260-4) by overlaying it on at least a portion of a screen representing a virtual space on at least one display (250). In one embodiment, the photographing camera (260-4) may be positioned on a bridge (203) positioned between a first rim (201) and a second rim (202).

[0067] The gaze tracking camera (260-1) can implement more realistic augmented reality by tracking the gaze of a user wearing the wearable device (103) and thereby matching the user's gaze with visual information provided to at least one display (250). For example, when the wearable device (103) looks straight ahead, the wearable device (103) can naturally display environmental information related to the user's front at a location where the user is located on at least one display (250). The gaze tracking camera (260-1) can be configured to capture an image of the user's pupil to determine the user's gaze. For example, the gaze tracking camera (260-1) can receive gaze detection light reflected from the user's pupil and track the user's gaze based on the position and movement of the received gaze detection light. In one embodiment, the gaze tracking camera (260-1) can be positioned at positions corresponding to the user's left and right eyes. For example, the gaze tracking camera (260-1) may be positioned within the first rim (201) and / or the second rim (202) to face the direction in which the user wearing the wearable device (103) is positioned.

[0068] The motion recognition camera (260-2, 260-3) can recognize the movement of the user's entire body, such as the user's torso, hand, or face, or a part of the body, and thereby provide a specific event on a screen provided on at least one display (250). The motion recognition camera (260-2, 260-3) can recognize the user's motion (gesture recognition), obtain a signal corresponding to the motion, and provide a display corresponding to the signal on at least one display (250). The wearable device (103) can identify the signal corresponding to the motion and perform a designated function based on the identification. The motion recognition camera (260-2, 260-3) can be used to perform a spatial recognition function using SLAM and / or a depth map for 6 degrees of freedom pose (6 dof pose). The wearable device (103) can perform gesture recognition and / or object tracking functions using motion recognition cameras (260-2, 260-3). In one embodiment, the motion recognition cameras (260-2, 260-3) can be positioned on the first rim (201) and / or the second rim (202).

[0069] The camera (260) included in the wearable device (103) is not limited to the above-described gaze tracking camera (260-1) and motion recognition cameras (260-2, 260-3). For example, the wearable device (103) can identify an external object included in the FoV using a camera positioned toward the user's FoV. The wearable device (103) can identify an external object based on a sensor for identifying the distance between the wearable device (103) and the external object, such as a depth sensor and / or a time of flight (ToF) sensor. The camera (260) positioned toward the FoV can support an autofocus function and / or an optical image stabilization (OIS) function. For example, the wearable device (103) may include a camera (260) (e.g., a face tracking (FT) camera) positioned toward the face to obtain an image including the face of a user wearing the wearable device (103).

[0070] Although not shown, in one embodiment, the wearable device (103) may further include a light source (e.g., an LED) that emits light toward a subject (e.g., a user's eyes, face, and / or an external object within the FoV) being photographed using the camera (260). The light source may include an infrared wavelength LED. The light source may be disposed on at least one of the frame (200) and the hinge units (206, 207).

[0071] According to one embodiment, the battery module (270) may supply power to electronic components of the wearable device (103). In one embodiment, the battery module (270) may be disposed within the first temple (204) and / or the second temple (205). For example, the battery module (270) may be a plurality of battery modules (270). The plurality of battery modules (270) may be disposed within each of the first temple (204) and the second temple (205). In one embodiment, the battery module (270) may be disposed at an end of the first temple (204) and / or the second temple (205).

[0072] The antenna module (275) can transmit signals or power to the outside of the wearable device (103), or receive signals or power from the outside. In one embodiment, the antenna module (275) can be positioned within the first temple (204) and / or the second temple (205). For example, the antenna module (275) can be positioned close to one surface of the first temple (204) and / or the second temple (205).

[0073] The speaker (255) can output an audio signal to the outside of the wearable device (103). The audio output module may be referred to as a speaker. In one embodiment, the speaker (255) may be positioned within the first temple (204) and / or the second temple (205) so as to be positioned adjacent to the ear of a user wearing the wearable device (103). For example, the speaker (255) may include a second speaker (255-2) positioned within the first temple (204) and thus positioned adjacent to the user's left ear, and a first speaker (255-1) positioned within the second temple (205) and thus positioned adjacent to the user's right ear.

[0074] The light-emitting module (not shown) may include at least one light-emitting element. The light-emitting module may emit light of a color corresponding to a specific state or emit light with an action corresponding to a specific state, in order to visually provide information regarding a specific state of the wearable device (103) to the user. For example, when the wearable device (103) requires charging, it may emit red light at a regular cycle. In one embodiment, the light-emitting module may be disposed on the first rim (201) and / or the second rim (202).

[0075] Referring to FIG. 2B, according to one embodiment, a wearable device (103) may include a printed circuit board (PCB) (290). The PCB (290) may be included in at least one of the first temple (204) or the second temple (205). The PCB (290) may include an interposer disposed between at least two sub-PCBs. One or more hardwares included in the wearable device (103) (e.g., hardwares illustrated by different blocks in FIG. 5) may be disposed on the PCB (290). The wearable device (103) may include a flexible PCB (FPCB) for interconnecting the hardwares.

[0076] According to one embodiment, the wearable device (103) may include at least one of a gyro sensor, a gravity sensor, and / or an acceleration sensor for detecting a posture of the wearable device (103) and / or a posture of a body part (e.g., a head) of a user wearing the wearable device (103). Each of the gravity sensor and the acceleration sensor may measure gravitational acceleration and / or acceleration based on mutually perpendicular designated three-dimensional axes (e.g., an x-axis, a y-axis, and a z-axis). The gyro sensor may measure an angular velocity of each of the designated three-dimensional axes (e.g., an x-axis, a y-axis, and a z-axis). At least one of the gravity sensor, the acceleration sensor, and the gyro sensor may be referred to as an inertial measurement unit (IMU). According to one embodiment, the wearable device (103) may identify a user's motion and / or gesture performed to execute or terminate a specific function of the wearable device (103) based on the IMU.

[0077] FIGS. 3A and 3B illustrate examples of the appearance of a wearable device according to various embodiments.

[0078] The wearable device (103) of FIGS. 3A and 3B may be an example of the electronic device (101) of FIG. 1. According to one embodiment, an example of the appearance of a first side (310) of a housing of the wearable device (103) may be illustrated in FIG. 3A, and an example of the appearance of a second side (320) opposite to the first side (310) may be illustrated in FIG. 3B.

[0079] Referring to FIG. 3A, according to one embodiment, a first surface (310) of a wearable device (103) may have a form attachable to a body part of a user (e.g., the face of the user). Although not shown, the wearable device (103) may further include a strap for fixing to a body part of a user, and / or one or more temples (e.g., the first temple (204) and / or the second temple (205) of FIGS. 2A and 2B). A first display (250-1) for outputting an image to a left eye among the user's two eyes, and a second display (250-2) for outputting an image to a right eye among the user's two eyes may be disposed on the first surface (310). The wearable device (103) is formed on the first surface (310) and may further include a rubber or silicone packing to prevent interference by light (e.g., ambient light) different from the light emitted from the first display (250-1) and the second display (250-2).

[0080] According to one embodiment, the wearable device (103) may include cameras (260-1) for photographing and / or tracking both eyes of the user adjacent to each of the first display (250-1) and the second display (250-2). The cameras (260-1) may be referred to as the gaze tracking camera (260-1) of FIG. 2B. According to one embodiment, the wearable device (103) may include cameras (260-5, 260-6) for photographing and / or recognizing the face of the user. The cameras (260-5, 260-6) may be referred to as FT cameras. The wearable device (103) may control an avatar representing the user in a virtual space based on the motion of the user's face identified using the cameras (260-5, 260-6).

[0081] Referring to FIG. 3b, a camera (e.g., cameras (260-7, 260-8, 260-9, 260-10, 260-11, 260-12)) and / or a sensor (e.g., a depth sensor (330)) for obtaining information related to the external environment of the wearable device (103) may be disposed on a second surface (320) opposite to the first surface (310) of FIG. 3a. For example, the cameras (260-7, 260-8, 260-9, 260-10) may be disposed on the second surface (320) to recognize external objects. Cameras (260-7, 260-8, 260-9, 260-10) may be referenced to the motion recognition cameras (260-2, 260-3) of FIG. 2B.

[0082] For example, using cameras (260-11, 260-12), the wearable device (103) can obtain images and / or videos to be transmitted to each of the user's eyes. The camera (260-11) can be placed on the second face (320) of the wearable device (103) to obtain an image to be displayed through the second display (250-2) corresponding to the right eye among the two eyes. The camera (260-12) can be placed on the second face (320) of the wearable device (103) to obtain an image to be displayed through the first display (250-1) corresponding to the left eye among the two eyes. The cameras (260-11, 260-12) can be referred to as the shooting camera (260-4) of FIG. 2B.

[0083] According to one embodiment, the wearable device (103) may include a depth sensor (330) disposed on the second face (320) to identify a distance between the wearable device (103) and an external object. Using the depth sensor (330), the wearable device (103) may obtain spatial information (e.g., a depth map) for at least a portion of the FoV of a user wearing the wearable device (103). Although not shown, a microphone may be disposed on the second face (320) of the wearable device (103) to obtain a sound output from an external object. The number of microphones may be one or more, depending on the embodiment.

[0084] FIG. 4A illustrates an example of how a wearable device manages avatars obtained from multiple providers and displays the avatars in a software application of the wearable device.

[0085] The wearable device (103) of FIG. 4A may represent an example of the wearable device (103) of FIGS. 2A to 3B . For example, the wearable device (103) may include at least a portion of the electronic device (101) of FIG. 1 . Although FIG. 4A illustrates a wearable device (103) that provides an XR environment, the embodiments of the present disclosure are not limited thereto. For example, the wearable device (103) may represent an electronic device such as a smartphone or a tablet PC.

[0086] Referring to FIG. 4A, the wearable device (103) can obtain avatar-related information. For example, the wearable device (103) can obtain the avatar-related information from a source node (410). For example, the avatar-related information can include information for creating an avatar and information about an item worn by the avatar. For example, the item can be referenced as an asset. For example, the information for creating the avatar can be referenced as information about an avatar set. For example, the information about the item can be referenced as information about an item set.

[0087] In one embodiment, the source node (410) may include multiple providers (411, 412, 413, 414). For example, the providers (411, 412, 413, 414) may represent entities that provide avatars. Each of the providers (411, 412, 413, 414) may include at least one of an application or a server. The application may be referred to as a source application. The server may be referred to as a source server. For example, the first provider (411) may include a first source application (411-1) and a first server (411-2). For example, the first server (411-2) may manage the first source application (411-1). For example, a second provider (412) may include a second source application (412-1) and a second server (412-2). For example, the second server (412-2) may manage the second source application (412-1). For example, a third provider (413) may include a third source application (413). For example, a fourth provider (414) may include a third server (414). Since the avatars provided by the providers (411, 412, 413, 414) are integrated through the first software application of the wearable device (103), the providers (411, 412, 413, 414) may also be referenced as integration targets.

[0088] For example, the first software application may be referred to as a software application for integrating avatars of providers (411, 412, 413, 414). For example, the first software application may be referred to as an avatar integration system, an avatar integration app, or an avatar platform. Specific details related thereto are described below in FIG. 4b.

[0089] For example, each of the providers (411, 412, 413, 414) can provide the avatar-related information. For example, a first provider (411) can provide information about a first avatar set and information about a first item set to the wearable device (103). For example, a second provider (412) can provide information about a second avatar set and information about a second item set to the wearable device (103). For example, a third provider (413) can provide information about a third avatar set and information about a third item set to the wearable device (103). For example, a fourth provider (414) can provide information about a fourth avatar set and information about a fourth item set to the wearable device (103).

[0090] Although not illustrated in FIG. 4A, the wearable device (103) may store the avatar-related information obtained from the providers (411, 412, 413, 414). For example, the wearable device (103) may store the avatar-related information in a state linked to the account information of each of the providers (411, 412, 413, 414). In other words, the wearable device (103) may store the avatar-related information for each account information. According to one embodiment, the wearable device (103) may perform normalization on the avatar-related information obtained from the providers (411, 412, 413, 414). The above standardization may refer to converting the ratio of the avatar set by each of the providers (411, 412, 413, 414) into a designated ratio supported by the first software application of the wearable device (103). Specific details related thereto are described below in FIGS. 7A to 7C.

[0091] Referring to FIG. 4A, the wearable device (103) can display a task bar (420), a user interface (UI) (430) of the first software application, and a virtual environment (440). For example, the wearable device (103) can display the task bar (420), the UI (430), and the virtual environment (440) through a display of the wearable device (103) (e.g., the display module (160) of FIG. 1).

[0092] For example, the task bar (420) may represent a virtual object representing a global menu provided by the wearable device (103). For example, the task bar (420) may include a plurality of icons. For example, the plurality of icons may include an icon for a home screen, an icon for providing software applications stored in the wearable device (103), and icons set for quick execution. According to one embodiment, the task bar (420) may include a visual object (421) provided by the first software application. For example, the visual object (421) may be implemented as an icon of the first software application. For example, the visual object (421) may include an area for displaying a set avatar among avatars provided by the source node (410). For example, based on an input to the visual object (421), the first software application may be executed. For example, the visual object (421) may be referred to as the entry point of the first software application. In response to the execution of the first software application, a UI (430) may be displayed. For example, the task bar (420) may be referred to as a device menu, a global menu, or a global settings menu. In other words, the task bar (420) may be used to manage or provide information about the wearable device (103).

[0093] For example, the UI (430) may represent a user interface for displaying and editing avatars provided by providers (411, 412, 413, 414) of the source node (410) through the first software application. For example, the UI (430) may include a first portion (431) including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information. In addition, for example, the UI (430) may include a second portion (432) for providing a preview (or preview image) of a candidate avatar corresponding to a second visual object selected from among the at least one second visual object based on an input to the first portion (431).

[0094] For example, the task bar (420) and the UI (430) may overlap at least partially with the virtual environment (440). For example, the virtual environment (440) may represent an example of a virtual environment provided by the second software applications (441, 442, 443). Alternatively, for example, the virtual environment (440) may be an environment (e.g., a VST environment) generated by reconstructing an image of an actual environment outside the wearable device (103) based on the second software applications (441, 442, 443). However, the embodiments of the present disclosure are not limited thereto. For example, the task bar (420) and the UI (430) may be displayed on the home screen. The home screen may represent a main menu of the wearable device (103). For example, the home screen may represent a screen on which the virtual environment is not displayed. Specific details regarding the task bar (420) and UI (430) are described below in FIG. 8a.

[0095] Referring to FIG. 4A, the wearable device (103) can display an avatar (450) processed based on the first software application in second software applications (441, 442, 443). The second software applications (441, 442, 443) providing a virtual environment may be referred to as an XR application or a target application. For example, the virtual environment provided by each of the second software applications (441, 442, 443) may include a 3D virtual environment. However, the embodiments of the present disclosure are not limited thereto. For example, the virtual environment may also include a 2D virtual environment. For example, the wearable device (103) can process an avatar (450) based on the first software application. For example, the avatar (450) may be included in the avatars provided by the source node (410). For example, processing of an avatar (450) may include integrating the avatars, editing the avatar (450), and storing the edited avatar (450). For example, the wearable device (103) may display the stored avatar (450) within a virtual environment while using the second software applications (441, 442, 443). For example, the wearable device (103) may display the first virtual environment including the avatar (450) while using the second software application (441) providing the first virtual environment. For example, the wearable device (103) may display the second virtual environment including the avatar (450) while using the second software application (442) providing the second virtual environment. For example, the wearable device (103) may display a third virtual environment including an avatar (450) while using a second software application (443) that provides the third virtual environment.In the example of FIG. 4a, each of the second software applications (441, 442, 443) provides a virtual environment and supports the display of an avatar (450). However, the embodiments of the present disclosure are not limited thereto. For example, the wearable device (103) may provide a virtual environment through a third software application different from the second software applications (441, 442, 443). In this case, the third software application may not support the display of an avatar (450). Specific details related to this are described below in FIG. 9a.

[0096] Figure 4b illustrates an example of avatar synchronization performed between multiple providers, wearable devices, and external electronic devices.

[0097] FIG. 4B illustrates an example (460) of a method for synchronizing an avatar between a first provider (411), a second provider (412), a wearable device (103), and an external electronic device (470). For example, the first provider (411) and the second provider (412) may be included in the source node (410) of FIG. 4A. For example, the wearable device (103) of FIG. 4B may represent the wearable device (103) of FIG. 4A.

[0098] Referring to example (460), the wearable device (103) may be connected to an external electronic device (470). For example, the wearable device (103) may be synchronized with the external electronic device (470). For example, the account information of the wearable device (103) may be identical to the account information of the external electronic device (470). In other words, the wearable device (103) may be logged in based on the user's account information, and the external electronic device (470) may also be logged in based on the user's account information. For example, the user's account information may include account information related to the manufacturers of the wearable device (103) and the external electronic device (470).

[0099] Referring to example (460), the wearable device (103) can obtain avatar-related information from the first provider (411) and the second provider (412). For example, the wearable device (103) can obtain information about avatars (A) and (C) through the first source application (411-1) of the first provider (411). The first source application (411-1) of the first provider (411) and the first server (411-1) can be in a state where the wearable device (103) and the avatars (A) and (C) are synchronized. In addition, for example, the wearable device (103) can obtain information about avatars (B) and (C) through the second source application (412-1) of the second provider (412). The second source application (412-1) and the second server (412-2) of the second provider (412) may be synchronized with the wearable device (103) and the avatar (B) and avatar (C). The avatar (D) may be synchronized only within the second source application (412-1) and the second server (412-2). In other words, the avatar (D) may not be uploaded to the first software application provided by the wearable device (103). For example, among the avatars (B), (C), and (D), the avatar (D) that is not uploaded may be selected based on the user.

[0100] Referring to example (460), avatars (A), (B), and (C) can be uploaded to the first software application of the wearable device (103). For example, the wearable device (103) can provide avatars (A), (B), and (C) through the first software application. For example, the wearable device (103) and the external electronic device (470) can be synchronized. In other words, the avatars (e.g., avatars (A), (B), and (C)) uploaded to the first software application of the external electronic device (470) can correspond to the avatars uploaded to the first software application of the wearable device (103).

[0101] Referring to example (460), the wearable device (103) can edit an avatar through the first software application. The first software application can be stored and executed within the wearable device (103). In operation (481), the wearable device (103) can edit an avatar (C) based on at least a portion of the user's input. Accordingly, the wearable device (103) can generate an avatar (C`) modified from the avatar (C). In operation (482), the wearable device (103) can request a synchronized external electronic device (470) to change the avatar. Furthermore, in operation (483), the wearable device (103) can request a change of the avatar from the providers (411, 412). For example, the change of the avatar can include changing the avatar (C) to the avatar (C`). In response to a request for a change of the above avatar, the external electronic device (470) can change the avatar (C) to avatar (C`) and store it. In addition, each of the providers (411, 412) can change the avatar (C) to avatar (C`) and store it.

[0102] Also, referring to example (460), the external electronic device (470) can edit an avatar through the first software application. The first software application can be stored and executed within the external electronic device (470). In operation (491), the external electronic device (470) can edit an avatar (B) based on at least a portion of the user's input. Accordingly, the external electronic device (470) can generate an avatar (B`) modified from the avatar (B). In operation (492), the external electronic device (470) can request a change in the avatar from the synchronized wearable device (103). In response to the request for a change in the avatar, the wearable device (103) can change the avatar (B) to the avatar (B`) and store it. Additionally, in operation (493), the wearable device (103) may request the second provider (412) to change the avatar in response to changing the avatar (B) to the avatar (B`). For example, the change of the avatar may include changing the avatar (B) to the avatar (B`). Additionally, the second provider (412) may change the avatar (B) to the avatar (C`) and save it.

[0103] As described above, the wearable device (103) (or external electronic device (470)) can manage avatars obtained from providers (411, 412). For example, the wearable device (103) can integrate the avatars, perform editing on the integrated avatars, and synchronize the edited avatars with other nodes (e.g., the external electronic device (470) or providers (411, 412)).

[0104] An electronic device and method according to embodiments of the present disclosure can provide, through the first software application, avatars and items (or assets) for avatars provided by different services (e.g., source servers, source applications) in a compatible (or integrated) manner. In addition, an electronic device and method according to embodiments of the present disclosure can provide an editing function for an integrated avatar through the first software application. In addition, an electronic device and method according to embodiments of the present disclosure can use (or display) an avatar obtained from a source server or source application through the first software application within a second software application that provides a virtual environment. In this case, an electronic device and method according to embodiments of the present disclosure can log in to one or more second software applications through login information associated with an avatar provided by the first software application. An electronic device and method according to embodiments of the present disclosure can use an avatar provided by a specific service in another service. Accordingly, an electronic device and method according to embodiments of the present disclosure can provide a user with a continuous user experience when using various services.

[0105] Figure 5 illustrates an exemplary block diagram of a wearable device.

[0106] The wearable device (103) of FIG. 5 may represent an example of the electronic device (101) of FIG. 1, the wearable device (103) of FIGS. 2A to 3B, and the wearable device (103) of FIGS. 4A and 4B.

[0107] Referring to FIG. 5, according to one embodiment, a wearable device (103) may include at least one of a processor (511), a display (513), a communication circuit (515), and a memory (517). The processor (511), the display (513), the communication circuit (515), and the memory (517) may be electrically and / or operably coupled with each other by a communication bus. Hereinafter, operably coupled hardware components may mean that a direct connection or an indirect connection is established between the hardware components, either wired or wireless, such that a second hardware component is controlled by a first hardware component among the hardware components. Although illustrated based on different blocks, the embodiment is not limited thereto, and some of the hardware components illustrated in FIG. 5 (at least a portion of the processor (511), the communication circuit (515), and the memory (517)) may be included in a single integrated circuit such as a system on a chip (SoC). The type and / or number of hardware components included in the wearable device (103) is not limited to those illustrated in FIG. 5. For example, the wearable device (103) may include only some of the hardware components illustrated in FIG. 5.

[0108] According to one embodiment, the processor (511) of the wearable device (103) may include a hardware component for processing data based on one or more instructions. The hardware component for processing data may include, for example, an arithmetic and logic unit (ALU), a floating point unit (FPU), and a field programmable gate array (FPGA). As an example, the hardware component for processing data may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP), and / or a neural processing unit (NPU). The number of processors (511) may be one or more. For example, the processor (511) may have a multi-core processor structure such as a dual core, a quad core, or a hexa core. The processor (511) of FIG. 5 may include at least a part of the processor (120) of FIG. 1.

[0109] For example, the processor (511) may include various processing circuits and / or multiple processors. For example, the term "processor" as used herein, including in the claims, may include various processing circuits including at least one processor, one or more of which may be configured to individually and / or collectively perform the various functions described below in a distributed manner. As used herein, when "processor," "at least one processor," and "one or more processors" are described as being configured to perform various functions, these terms encompass, for example, and without limitation, situations where one processor performs some of the recited functions and other processor(s) perform other parts of the recited functions, and also situations where one processor may perform all of the recited functions. Additionally, the at least one processor may include a combination of processors that perform the various functions enumerated / disclosed, for example, in a distributed manner. At least one processor may execute program instructions to achieve or perform the various functions.

[0110] According to one embodiment, the display (513) of the wearable device (103) can output visualized information to the user (e.g., the visual information of FIGS. 8A, 8B, 9A, 9B, 10A, 10B, 11A, 11B, 12A, 12B, and 12C). The number of displays (513) included in the wearable device (103) may be one or more. For example, the display (513) may be controlled by a processor (511) and / or a graphic processing unit (GPU) (not shown) to output visualized information to the user. The display (513) may include a flat panel display (FPD) and / or electronic paper. The FPD may include a liquid crystal display (LCD), a plasma display panel (PDP), a digital mirror device (DMD), one or more light emitting diodes (LEDs), and / or a micro LED. The LEDs may include organic LEDs (OLEDs). The display (513) of FIG. 5 may include at least a portion of the display module (160) of FIG. 1.

[0111] In one embodiment, light transmission may occur through at least a portion of the display (513). The wearable device (103) may provide a user experience related to augmented reality by providing a combination of light output through the display (513) and light transmitted through the display (513) to the user. As described above with reference to FIGS. 2A and 2B and / or 3A and 3B , the display (513) of the wearable device (103) according to one embodiment may have a structure for covering the entire FoV of the user, or radiating light toward the FoV of the user, while being worn on a body part of the user, such as the head. Although not illustrated, the wearable device (103) may include other output means for outputting information in forms other than visual or auditory forms. For example, the wearable device (103) may include at least one speaker for outputting an audio signal, and / or a motor (or actuator) for providing haptic feedback based on vibration. For example, the wearable device (103) may render an image for providing a user experience related to virtual reality, and display the rendered image through the display (513).

[0112] According to one embodiment, the communication circuit (515) of the wearable device (103) may include hardware for supporting transmission and / or reception of electrical signals between an external electronic device (not shown) (e.g., the external electronic device (470) of FIG. 4B) and the wearable device (103). In addition, the communication circuit (515) of the wearable device (103) may include hardware for supporting transmission and / or reception of electrical signals between the external electronic devices. The communication circuit (515) may include, for example, at least one of a modem (MODEM), an antenna, and an optical / electronic (O / E) converter. The communication circuit (515) may support transmission and / or reception of electrical signals based on various types of communication means, such as Ethernet, Bluetooth (BT), Bluetooth low energy (BLE), ZigBee, long term evolution (LTE), 5G new radio (NR), and wireless-fidelity (Wi-Fi). The communication circuit (515) of FIG. 5 may include at least a portion of the communication module (190) and / or the antenna module (197) of FIG. 1.

[0113] According to one embodiment, the memory (517) of the wearable device (103) may include a hardware component for storing data and / or instructions input to and / or output from the processor (511). The memory (517) may include, for example, a volatile memory such as a random-access memory (RAM), and / or a non-volatile memory such as a read-only memory (ROM). The volatile memory may include, for example, at least one of a dynamic RAM (DRAM), a static RAM (SRAM), a cache RAM, and a pseudo SRAM (PSRAM). The non-volatile memory may include, for example, at least one of a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a flash memory, a hard disk, a compact disc, and an embedded multimedia card (eMMC). The memory (517) of FIG. 5 may include at least a portion of the memory (130) of FIG. 1.

[0114] Although not illustrated in FIG. 5, the wearable device (103) according to one embodiment may include a sensor and a camera. For example, the wearable device (103) may include the sensor for identifying a user's input. For example, the sensor may include an IMU (or IMU sensor), a biometric sensor, an acoustic sensor (or a microphone (or mic)), a gyro sensor, a gravity sensor, and / or an acceleration sensor. For example, the wearable device (103) may include a camera (or image sensor) for recognizing a real environment. The sensor may include at least a portion of the sensor module (176) of FIG. 1. The camera may include at least a portion of the camera module (180) of FIG. 1. In addition, the wearable device (103) according to one embodiment may include an output means for outputting information in a form other than a visualized form. For example, the wearable device (103) may include a speaker for outputting an acoustic signal. For example, the wearable device (103) may include a motor for providing haptic feedback based on vibration.

[0115] Referring to FIG. 5, according to one embodiment, one or more instructions (or commands) representing operations and / or actions to be performed on data by a processor (511) of the wearable device (103) may be stored in the memory (517) of the wearable device (103). A set of one or more instructions may be referred to as a program, firmware, an operating system, a process, a routine, a sub-routine, and / or an application. Hereinafter, when an application is installed in an electronic device (e.g., a wearable device (103)), it may mean that one or more instructions provided in the form of an application are stored in the memory (517), and that the one or more applications are stored in a format executable by the processor of the electronic device (e.g., a file having an extension designated by the operating system of the wearable device (103)). According to one embodiment, the wearable device (103) may perform the operations of FIGS. 6 and 13 by executing one or more instructions stored in the memory (517).

[0116] Referring to FIG. 5, according to one embodiment, the memory (517) of the wearable device (103) may store avatar information (521) and item information (523). For example, the wearable device (103) may store avatar-related information obtained from each of the providers (e.g., the providers (411, 412, 413, and 414) of FIG. 4A). For example, the avatar-related information may include avatar information (521) and item information (523). For example, the wearable device (103) may obtain and store first avatar information and first item information from a first provider among the providers. At this time, the first avatar information and the first item information may be stored in a state linked to the first account information of the first provider. The first avatar information may be included in the avatar information (521), and the first item information may be included in the item information (523). The first avatar information may include information about avatars in a first avatar set provided by the first provider. In addition, for example, the wearable device (103) may obtain and store second avatar information and second item information from a second provider among the providers. At this time, the second avatar information and the second item information may be stored in a state linked to the second account information of the second provider. The second avatar information may be included in avatar information (521), and the second item information may be included in item information (523). The second avatar information may include information about avatars in a second avatar set provided by the second provider.

[0117] Figure 6 illustrates an example of an operational flow for managing avatars obtained from multiple providers and displaying the avatars in a software application of a wearable device.

[0118] At least some of the methods of FIG. 6 may be performed by the wearable device (103) of FIG. 5. For example, at least some of the methods may be controlled by the processor (511) of the wearable device (103). In the embodiments described below, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel.

[0119] In operation (600), the wearable device (103) may obtain avatar-related information from avatar providers. Each of the avatar providers (hereinafter, “providers”) may include at least one of a source application or a source server that provides avatars. For convenience of explanation, it is assumed that the providers include a first source application and a second source application. For example, the wearable device (103) may obtain first avatar-related information from the first source application and second avatar-related information from the second source application. For example, the first avatar-related information may include information for generating a first avatar set provided by the first source application and information for generating a first item set provided by the first source application. In addition, for example, the second avatar-related information may include information for generating a second avatar set provided by the second source application and information for generating a second item set provided by the second source application.

[0120] In operation (610), the wearable device (103) may process the avatar-related information. For example, the wearable device (103) may obtain a scale of the avatar-related information. For example, the wearable device (103) may identify a first scale based on a proportion of the first avatar set provided by the first source application. The first scale may be referred to as a first proportion. For example, the first proportion may include a proportion (or body proportion) of the first avatar set. The first item set may have the first proportion based on the first scale. Alternatively, for example, the wearable device (103) may identify a second scale based on a proportion of the second avatar set provided by the second source application. The second scale may be referred to as a second proportion. For example, the second ratio may include the proportions (or body proportions) of the second avatar set. Additionally, the second item set may have the second ratio based on the second scale.

[0121] In one embodiment, the wearable device (103) may compare the identified ratio with a designated ratio. For example, the wearable device (103) may compare the designated ratio set within a first software application for integrating avatars provided by the providers with the first ratio. Alternatively, for example, the wearable device (103) may compare the designated ratio with the second ratio. If the ratios do not correspond, the wearable device (103) may process the avatar-related information so that the first ratio (or the second ratio) corresponds to the designated ratio. Specific details related thereto are described below in FIGS. 7A to 7C . As described above, the process by which the wearable device (103) adjusts the ratio of the avatar-related information obtained from the providers to correspond to the designated ratio may be referred to as normalization. Based on the above standardization, the wearable device (103) can integrate and manage avatars provided by the providers through the first software application.

[0122] In operation (620), the wearable device (103) may execute the first software application. For example, the wearable device (103) may execute the first software application based on at least a portion of an input to a task bar (e.g., task bar (420) of FIG. 4A) displaying a global menu of the wearable device (103).

[0123] According to one embodiment, the task bar may include a plurality of icons. For example, the plurality of icons may include icons for the home screen, icons for providing software applications stored in the wearable device (103), and icons set for quick execution. According to one embodiment, the plurality of icons may include a visual object of the first software application (e.g., the visual object (421) of FIG. 4A). For example, the icon may include an area for displaying a set avatar among avatars provided by the providers. For example, based on an input to the icon, the first software application may be executed. For example, the task bar may be referred to as a device menu, a global menu, or a global settings menu. In other words, the task bar may be used to manage or provide information of the wearable device (103).

[0124] According to one embodiment, the wearable device (103) may, in response to the execution of the first software application, display a UI (e.g., UI (430) of FIG. 4A) of the first software application. The first software application may display a user interface for displaying and editing avatars provided by the providers. For example, the UI may include a first portion (e.g., first portion (431) of FIG. 4A) including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information. In addition, for example, the UI may include a second portion (e.g., second portion (432) of FIG. 4A) for providing a preview (or preview image) of a candidate avatar corresponding to a second visual object selected from among the at least one second visual object based on an input to the first portion. However, the embodiments of the present disclosure are not limited thereto. For example, the UI may display avatars provided by the providers within a non-split screen. Details regarding the task bar and the UI are described below in FIG. 8a.

[0125] In operation (630), the wearable device (103) may perform editing of an avatar. For example, the avatar may be included in the avatars provided by the providers. For example, the avatar may be provided by the first source application or the second source application.

[0126] For example, the wearable device (103) can change the item worn by the avatar. For example, the wearable device (103) can change the item (or asset) worn by the avatar based on at least a portion of the user's input to the UI. Or, for example, the wearable device (103) can change the avatar to another avatar. For example, the other avatar can be included in the avatars provided by the providers.

[0127] In operation (640), the wearable device (103) may display a virtual environment based on the execution of a second software application. For example, the wearable device (103) may execute the second software application that provides the virtual environment. For example, the second software application may represent a software application stored within the wearable device (103). In other words, unlike the source application of the providers that provide the avatars, the second software application may be stored within the wearable device (103).

[0128] According to one embodiment, the wearable device (103) may identify a state of the second software application in response to the execution of the second software application. For example, the state may include a first state in which an avatar provided by the second software application set for the second software application exists, and a second state different from the first state. For convenience of explanation, the avatar provided by the second software application may be referred to as an app avatar. For example, the second state may include a case in which the app avatar provided by the second software application is not set for the second software application.

[0129] According to one embodiment, the wearable device (103) may, in the first state, display the virtual environment including the app avatar provided by the second software application. Alternatively, the wearable device (103) may, in the second state, display the virtual environment based on the image displayed by the icon of the task bar. For example, if the icon of the task bar displays an image representing the avatar provided by the first source application, the wearable device (103) may, in the second state, display the virtual environment including the avatar. Alternatively, for example, if the icon of the task bar displays a default image different from the avatars provided by the providers or the display of the icon is deactivated, the wearable device (103) may, in the second state, display a screen for selecting the app avatar provided by the second software application. For example, the screen may at least partially overlap with the virtual environment. Specific details related thereto are described below with reference to FIGS. 9A and 10A.

[0130] According to one embodiment, the wearable device (103) may adjust the scale of the avatar when displaying the virtual environment including the avatar. For example, the wearable device (103) may adjust the scale of the avatar to correspond to the scale supported by the second software application. The scale of the avatar may be the designated scale of the first software application. Specific details related thereto are described below in FIG. 9B.

[0131] According to one embodiment, the wearable device (103) may set a default avatar applicable to each second software application based on at least some of the inputs to the UI. For example, the default avatar may be displayed via the icon. Details related to this are described in FIG. 10b below.

[0132] According to one embodiment, the wearable device (103) may perform a login to the second software application after executing the second software application. For example, the wearable device (103) may link the avatar provided by the first source application with the user's login information. For example, the wearable device (103) may display a visual object guiding the linking of the avatar and the login information. If the avatar and the login information are linked based on an input to the visual object, the wearable device (103) may perform the login based on the avatar while executing the second software application in which the avatar is set as the default avatar. For example, the wearable device (103) may request authentication for the second software application based on the avatar to a server managing the second software application. Based on the success of the authentication, the wearable device (103) may display the virtual environment including the avatar. Specific details related to this are described in Fig. 12a below.

[0133] According to one embodiment, the wearable device (103) may display the UI including a visual object representing a candidate avatar among the avatars provided by the providers. At this time, the wearable device (103) may display visual information for indicating a software application to which the candidate avatar corresponding to the visual object is linked, together with the visual object. For example, in an example in which the avatar and the second software application are linked, the wearable device (103) may display the visual information indicating the second software application, together with the visual object for the avatar. Specific details related thereto are described below in FIG. 12b.

[0134] In one embodiment, the wearable device (103) may display another visual object that inquires whether to log in to a third software application different from the second software application using the avatar to which the user's login information is linked. For example, if the avatar is selected as the default avatar and the third software application is executed, the wearable device (103) may display the other visual object. Based on the input to the other visual object, the wearable device (103) may log in to the third software application based on the avatar.

[0135] In one embodiment, the wearable device (103) may perform a change of the avatar while displaying the virtual environment provided by the second software application including the avatar. For example, the wearable device (103) may perform a change of the avatar using the UI of the first software application while displaying the virtual environment. For example, the change of the avatar may include changing the appearance of the avatar from a first appearance to a second appearance, or from the avatar to the other avatar. For example, the other avatar may be provided by the second source application among the providers. In one embodiment, the wearable device (103) may display the virtual environment including a virtual object that notifies the change of the avatar. For example, the virtual object may include an image representing the second appearance to be changed from the first appearance. Alternatively, for example, the virtual object may include a dummy avatar and information about the user. For example, the dummy avatar can be used to notify changes to the avatar. For example, information about the user may include the user's account identifier or the user's name. Specific details related to this are described in FIGS. 11A and 11B below.

[0136] Figure 7a illustrates an example of a method for obtaining avatar-related information from multiple providers.

[0137] FIG. 7A illustrates an example (700) of a method for a wearable device (103) to obtain avatar-related information from a source node (410) including multiple providers. The wearable device (103) of FIG. 7A may represent an example of the wearable device (103) of FIG. 5 . The source node (410) of FIG. 7A may represent an example of the source node (410) of FIG. 4A .

[0138] Referring to example (700), the wearable device (103) can obtain the avatar-related information from the source node (410). For example, the wearable device (103) can obtain the avatar-related information from each of the providers (411, 412, 413, 414). For example, a first provider (411) can provide information about a first avatar set and information about a first item set to the wearable device (103). For example, a second provider (412) can provide information about a second avatar set and information about a second item set to the wearable device (103). For example, a third provider (413) can provide information about a third avatar set and information about a third item set to the wearable device (103). For example, a fourth provider (414) may provide information about a fourth avatar set and information about a fourth item set to the wearable device (103).

[0139] Referring to example (700), the wearable device (103) can store the avatar-related information obtained from the providers (411, 412, 413, 414). For example, the wearable device (103) can store the avatar-related information in a state linked to the account information of each of the providers (411, 412, 413, 414). In other words, the wearable device (103) can store the avatar-related information for each of the account information. For example, the account information can include login information or identification information used by each of the providers (411, 412, 413, 414).

[0140] According to one embodiment, the wearable device (103) may perform normalization on the avatar-related information obtained from the providers (411, 412, 413, 414). The normalization may refer to converting the ratio of the avatar set by each of the providers (411, 412, 413, 414) into a designated ratio supported by the first software application of the wearable device (103). For example, the normalization may be referred to as an override.

[0141] Referring to example (710), the wearable device (103) can perform standardization on the avatar. For example, the wearable device (103) can compare the attributes of the first avatar set provided by the first provider (411) with the specified ratio. For example, the attributes may include the size or ratio of the first avatar set. For example, the wearable device (103) can identify the attributes of the first avatar set through a flat image of the first avatar set. Alternatively, for example, the wearable device (103) can identify the attributes based on data (e.g., a software development kit (SDK)) of information about the first avatar set. The wearable device (103) can divide the avatar (711) of the first avatar set into a plurality of parts (e.g., a head, a body, arms, and legs). The wearable device (103) can adjust the ratio and size of each of the plurality of parts of the avatar (711) to match the specified ratio. In addition, for example, the wearable device (103) can compare the attributes of the second avatar set provided by the second provider (412) with the specified ratio. For example, the attributes may include the size or ratio of the second avatar set. The wearable device (103) can divide the avatar (713) of the second avatar set into a plurality of parts (e.g., head, body, arms, legs). The wearable device (103) can adjust the ratio and size of each of the plurality of parts of the avatar (713) to match the specified ratio.

[0142] Referring to example (710), the wearable device (103) can enlarge an avatar (711) into an avatar (712) having the specified ratio. It can reduce an avatar (713) into an avatar (712) having the specified ratio. Accordingly, the avatar (711) and avatar (713) having the adjusted ratio can be formed to correspond to the specified ratio provided within the first software application and have natural motion.

[0143] Referring to example (720), the wearable device (103) can perform standardization on items. For example, the wearable device (103) can compare the attributes of the first set of items provided by the first provider (411) with the specified ratio. For example, the attributes can include the size or ratio of the first set of items. For example, the wearable device (103) can identify the attributes of the first set of items through a planar image of the first set of items. Alternatively, for example, the wearable device (103) can identify the attributes based on data (e.g., a software development kit (SDK)) of information about the first set of items. The wearable device (103) can divide the items (721) of the first set of items into fixed regions (e.g., sleeves and torso of a top) or deformable regions. The wearable device (103) can adjust the ratio and size of each of the areas of the item (721) to match the specified ratio. In addition, for example, the wearable device (103) can compare the attribute of the second item set provided by the second provider (412) with the specified ratio. For example, the attribute may include the size or ratio of the second item set. The wearable device (103) can divide the item (723) of the second item set into a plurality of areas. The wearable device (103) can adjust the ratio and size of each of the plurality of areas of the item (723) to match the specified ratio.

[0144] Referring to example (720), the wearable device (103) can enlarge an item (721) into an item (722) having the specified ratio. It can also reduce an item (723) into an item (722) having the specified ratio. Accordingly, the item (721) and the item (723) having the adjusted ratio can correspond to the specified ratio provided within the first software application and be applied to an avatar having the specified ratio.

[0145] Figures 7b and 7c illustrate examples of a method for performing processing on avatar-related information.

[0146] Figures 7b and 7c illustrate examples (730, 740) of performing standardization on the avatar-related information.

[0147] Example (730) illustrates an avatar (731) having a specified ratio provided by the first software application and an avatar (732) having a ratio different from the specified ratio. The avatar (732) may have the ratio of an avatar provided by a provider (e.g., a source application) that provides the avatar-related information to the wearable device (103). The wearable device (103) may recognize that the ratio identified based on the avatar-related information for generating the avatar (732) is different from the specified ratio. Accordingly, the wearable device (103) may adjust the avatar (732) having the specified ratio to an avatar (733) having the specified ratio. In this case, the avatar (733) may be generated by adjusting the ratios of a plurality of parts (e.g., head, upper body, lower body) of the avatar (732) and applying a motion (or facial expression) corresponding to each part. Referring to example (730), when adjusting an avatar (732) to an avatar (733), rather than simply enlarging the above ratio of the avatar (732) to the above specified ratio of the avatar (731), the ratios of the plurality of parts constituting the avatar (732) may be adjusted respectively.

[0148] Referring to example (740), as the plurality of joints (741, 742) included in the avatar (732) are adjusted, the avatar (733) can be generated. For example, as the positions of the plurality of joints (741, 742) of the avatar (732) and the number of the plurality of joints (741, 742) are adjusted, the avatar (733) can be generated. The plurality of joints (741, 742) can represent virtual joints. For example, the wearable device (103) can generate a specified ratio (or specified scale) of an avatar that serves as a reference for compatibility with the first software application. The wearable device (103) can generate a skeleton for a plurality of parts based on the specified ratio, and designate the number and positions of the plurality of joints (741, 742) within the skeleton. The wearable device (103) can adjust the avatar (732) into the avatar (733) by adjusting the plurality of joints (741, 742) of the avatar (732) to correspond to the number and positions of the plurality of joints (741, 742) at the specified ratio. In this way, the wearable device (103) can adjust the ratio for the item (750). The specified ratio and the number and positions of the plurality of joints (741, 742) according to the specified ratio can be stored in the first software application.

[0149] Figure 8a illustrates examples of a user interface of a first software application for integrating avatars.

[0150] FIG. 8A illustrates examples (801, 802) of a UI (430) of the first software application. The UI (430) may be displayed through the display (513) of the wearable device (103). For example, the UI (430) may be superimposed on a virtual environment. For example, the virtual environment may be provided by a second software application stored in the wearable device (103). However, the embodiments of the present disclosure are not limited thereto. When the virtual environment is not displayed (e.g., while the home screen is displayed), the UI (430) may be displayed on at least a portion of the display area of ​​the display (513).

[0151] Referring to example (801), the wearable device (103) may display a task bar (420). For example, the task bar (420) may include a plurality of icons. For example, the plurality of icons may include an icon (422) for providing software applications stored in the wearable device (103) and icons set for quick execution. For example, the task bar (420) may include a visual object (421) provided by the first software application. Among the icons set for quick execution, an icon (423) of a currently executing software application may be activated. For example, the software application associated with the icon (423) may provide a virtual environment. The wearable device (103) may display a UI (430) based on an input to the visual object (421).

[0152] Referring to example (801), the UI (430) may include a first portion (431) and a second portion (432). For example, the first portion (431) may include a first visual object (431-1) representing account information and at least one second visual object (431-2) representing a candidate avatar according to the account information. For example, the account information may represent account information used in a source application or for indicating the source application. The second visual object (431-2) may be used to display candidate avatars provided by the source application indicated by the first visual object (431-1). For example, visual information (431-3) at least partially overlapping with the second visual object (431-2) may indicate a second software application that is linked (or interlocked) with the second visual object (431-2). The second software application may represent an application stored within a wearable device (103) that provides a virtual environment. For example, the visual information (431-3) may indicate a second software application (App A).

[0153] For example, the second portion (432) may be used to display an avatar (810) of a selected second visual object (431-2). For example, the second portion (432) may include an area (432-1) for displaying the avatar (810), icons (432-2) for functions for editing the avatar (810), and visual information (432-3). For example, the second portion (432) may provide a preview of the avatar (810) through the area (432-1). The preview may display an avatar adjusted (or reconstructed) to the specified ratio of the first software application. For example, the preview may provide the motion of the avatar to be applied by tracking the motion of the user. For example, the visual information (432-3) may be understood to be substantially the same as the visual information (431-3). For example, icons (432-2) may include icons for functions such as editing, copying, or deleting. For example, the editing function may provide items (or assets) provided by other providers (e.g., a second source application) in addition to the provider providing the avatar (810) (e.g., a first source application). To apply the items of the other providers to the avatar (810), the items of the other providers and the items of the provider may be adjusted according to the specified ratio. The example (801) of FIG. 8A is merely an example for convenience of explanation, and the embodiments of the present disclosure are not limited thereto. The number or shape of icons, visual objects, and visual information included in the example (801) may be changed.

[0154] Referring to example (802), the wearable device (103) can display a UI (430). In example (802), the wearable device (103) omits the task bar (420), but the wearable device (103) may also display the task bar (420). Referring to the UI (430) of example (802), the UI (430) can display a visual object (821) representing account information and at least one visual object (822) providing a preview of a candidate avatar. For example, the visual object (821) can be understood to be substantially the same as the first visual object (431-1) of example (801). For example, the visual object (822) can provide a preview of the candidate avatar according to the account information. The visual object (822) can include visual information (822-1). For example, the visual information (822-1) may indicate a second software application to which the candidate avatar corresponding to the visual object (822) is linked (or connected). Referring to example (802), the UI (430) may display a candidate avatar according to account information selected by the visual object (821) through the visual object (822). However, the embodiments of the present disclosure are not limited thereto. For example, the UI (430) may display avatars provided by all accounts (i.e., source applications) through the visual object (822).

[0155] Figure 8b illustrates an example of how to edit an avatar through a first software application.

[0156] FIG. 8b illustrates an example (850) of a UI (430) of the first software application. The UI (430) can be displayed through a display (513) of a wearable device (103).

[0157] Referring to example (850), the wearable device (103) can display the UI (430). Although the wearable device (103) omits the task bar (420) in example (850), it can be understood that the wearable device (103) displays the task bar (420). For example, the UI (430) can be superimposed on a virtual environment. For example, the virtual environment can be provided by a second software application stored in the wearable device (103). However, the embodiments of the present disclosure are not limited thereto. When the virtual environment is not displayed (e.g., while the home screen is displayed), the UI (430) can be displayed on at least a portion of the display area of ​​the display (513).

[0158] Referring to example (850), the UI (430) may include a second portion (432) and a third portion (433). For example, the second portion (432) may provide a preview of an avatar (860). For example, the avatar (860) may be displayed based on an input to a first portion (not shown) (e.g., the first portion (431) of FIG. 8A) or an input to a visual object (not shown) (e.g., the visual object (822) of FIG. 8A). The third portion (433) may display candidate items to be applied to the avatar (860). For example, the third portion (433) may include a first item (861), a second item (862), and a third item (863). The number and shape of items shown in the example (850) of FIG. 8B are merely exemplary, and the embodiments of the present disclosure are not limited thereto. For example, the third portion (433) may be displayed based on an input for an icon for editing an avatar (860) (e.g., icon (432-2) of FIG. 8A). For example, the third portion (433) may display visual information (861-1, 861-2, 861-3) regarding providers providing items. For example, visual information (861-1) may indicate a first provider (or a first source application) providing a first item (861). Additionally, for example, visual information (861-2) may indicate a second provider (or a second source application) providing a second item (862). Additionally, for example, the visual information (861-3) may indicate a third-party provider (or third-party source application) providing a third item (863). For example, the third portion (433) may include an icon (870) for filtering providers. For example, the icon (870) may be used to classify items by provider. Or, for example, the icon (870) may be used to classify the type (or kind) of an item.For example, the type may include accessories, tops, bottoms, shoes, or looks. For example, the looks may include eye shape, eyebrow shape, skin color, face shape, and mouth shape.

[0159] Figure 9a illustrates an example of how a virtual environment provided by a second software application may be displayed.

[0160] Figure 9a illustrates examples (901, 902) showing a virtual environment provided by the second software application. The second software application may include an application stored in a wearable device (103).

[0161] Referring to example (901), the wearable device (103) may display a task bar (420). For example, the task bar (420) may include a plurality of icons. For example, the plurality of icons may include icons for providing software applications stored in the wearable device (103) and icons set for quick execution. For example, the task bar (420) may include a visual object (421) provided by the first software application. Among the icons set for quick execution, the icon (913) of the currently running second software application (App A) may be activated. For example, the second software application (App A) may provide a virtual environment (915). The wearable device (103) may display the virtual environment (915) based on an input to the icon (913). For example, the virtual environment (915) may include an avatar (917). At this time, the second software application (App A) may be an application that supports the display of an avatar. In example (901), it is assumed that the avatar (917) is an avatar provided by the first software application. For example, the visual object (421) of the task bar (420) may provide a preview (910) of the avatar (917). For example, the visual object (421) may include a preview (910) corresponding to the avatar (917) through the area of ​​the visual object (421). Referring to the above, the wearable device (103) may provide information about the avatar (917) included in the virtual environment (915) provided by the running second software application (App A) through the preview (910) of the task bar (420).

[0162] In contrast, referring to example (902), the wearable device (103) may display a task bar (420). For example, the task bar (420) may include a plurality of icons. For example, the plurality of icons may include icons for providing software applications stored in the wearable device (103) and icons set for quick execution. Among the icons set for quick execution, the icon (923) of the currently running second software application (App B) may be activated. For example, the second software application (App B) may provide a virtual environment (925). The wearable device (103) may display the virtual environment (925) based on an input to the icon (923). In this case, the second software application (App B) may be an application that does not support the display of an avatar. While a second software application (App B) that does not support the display of avatars is running, the task bar (420) may disable the display of the visual object (421) of the first software application. However, the embodiments of the present disclosure are not limited thereto. For example, the task bar (420) may display the visual object (421), but may display a default image (421a) through the area of ​​the visual object (421). For example, the default image (421a) may represent an image different from the avatars provided by the first software application. For example, the default image (421a) may include a simplified image of a human figure.

[0163] Figure 9b illustrates an example of how to handle an avatar displayed within a virtual environment provided by a second software application.

[0164] FIG. 9b illustrates examples (951, 952) of a method for processing an avatar displayed within a virtual environment provided by the second software application. The second software application may include an application stored within a wearable device (103).

[0165] Referring to example (951), the wearable device (103) may display a virtual environment (960). For example, the wearable device (103) may display the virtual environment (960) in response to the execution of the second software application. The virtual environment (960) may include an avatar (970). For example, the avatar (970) may have a specified ratio. For example, the specified ratio may be a ratio set within the first software application of the wearable device (103). Referring to example (951), the avatar (970) having the specified ratio may be different from the ratios of objects in the virtual environment (960). When the virtual environment (960) including the avatar (970) is displayed, the user may experience a sense of incongruity. Therefore, the wearable device (103) needs to adjust the ratio between the specified ratio and the ratio of the virtual environment (960) provided by the second software application.

[0166] Referring to example (952), the wearable device (103) may display a virtual environment (960) including an avatar (980) adjusted to the ratio of the virtual environment (960) from the specified ratio. For example, the wearable device (103) may identify a ratio (990) of an object (e.g., space or object) provided by the second software application, and based on the identified ratio (990), change the scale (or body ratio) of the avatar (980) from the specified ratio to correspond to the ratio (990). Alternatively, for example, the wearable device (103) may identify a ratio (990) requested within the installation information of the second software application, and change the scale of the avatar (980) from the specified ratio to correspond to the ratio (990). For example, the wearable device (103) can adjust the body parts of the avatar (980) that require delicate interaction (e.g., hands, head, feet, etc.) to the ratio (990) of the object or the ratio (990) requested through the installation information. In this case, even if the ratio is adjusted from the specified ratio to the ratio (990), the number and position of virtual joints within the skeleton of the avatar (980) can be applied in the same manner.

[0167] FIG. 10A illustrates an example of how to display an integrated avatar in a first software application based on the state of a second software application.

[0168] FIG. 10A illustrates examples (1001, 1002, 1003) of a method for displaying an avatar provided by a first software application based on a state of a second software application. The second software application may represent an application stored in a wearable device (103). For example, the state of the second software application may include a first state in which an avatar (or app avatar) provided by the second software application is used, and a second state different from the first state. For example, the second state may include a case in which an app avatar provided by the second software application is not present or is not used.

[0169] Referring to example (1001), the wearable device (103) may display a home screen (1010). For example, the home screen (1010) may represent a main screen provided by the wearable device (103). For example, the home screen (1010) may include a task bar (420). For example, the task bar (420) may include a visual object (421) provided by the first software application, an icon (423) of a second software application (App A), and an icon (424) of a second software application (App B). While the home screen (1010) is displayed, the icon (423) and the icon (424) may be deactivated. The visual object (421) may display a basic image (421a).

[0170] In one embodiment, the wearable device (103) may select a preview (1015) for the avatar (1027) based on at least a portion of the input to the visual object (421). For example, the wearable device (103) may change from a base image (421a) to a preview (1015) for the avatar (1027) based on at least a portion of the input to the visual object (421). The visual object (421) displaying the preview (1015) may indicate that the avatar (1027) corresponding to the preview (1015) is used as a default avatar for second software applications. For example, the default avatar may represent an avatar used in a second software application (App A) when the second software application (App A) is executed.

[0171] Referring to example (1002), the wearable device (103) can execute a second software application (App A). ​​For example, the wearable device (103) can execute the second software application (App A) based on an input to an icon (423) of the second software application (App A). ​​As the second software application (App A) executes, the icon (423) can be activated. The activation of the icon (423) can include the display of a visual effect. For example, the wearable device (103) can check the status of the second software application (App A). ​​For example, the wearable device (103) can display a virtual environment (1020) including an app avatar provided by the second software application (App A) based on identifying the first status. Alternatively, the wearable device (103) may identify the image displayed by the visual object (421) based on identifying the second state. For example, if the visual object (421) displays a preview (1015), the wearable device (103) may display a virtual environment (1020) including an avatar (1027) corresponding to the preview (1015). Alternatively, for example, if the visual object (421) displays a basic image (421a), the wearable device (103) may display a screen for selecting an app avatar provided by a second software application (App A). ​​In this case, the second software application (App A) may indicate an application that supports displaying an avatar.

[0172] Referring to example (1003), the wearable device (103) can execute a second software application (App B). For example, the wearable device (103) can execute the second software application (App B) based on an input to the icon (424) of the second software application (App B). As the second software application (App B) executes, the icon (424) can be activated. The activation of the icon (424) can include the display of a visual effect. In this case, the second software application (App B) can indicate an application that does not support the display of an avatar. The wearable device (103) can display a virtual environment (1030) in response to the execution of the second software application (App B). While displaying the virtual environment (1030), the wearable device (103) can deactivate the display of a visual object (421). However, the embodiments of the present disclosure are not limited thereto. For example, the task bar (420) may display a visual object (421), but may also display a default image (421a) through the area of ​​the visual object (421). For example, the default image (421a) may represent an image different from the avatars provided by the first software application. For example, the default image (421a) may include a simplified image of a human figure.

[0173] Figure 10b illustrates an example of how to set a default avatar for each second software application.

[0174] FIG. 10b illustrates examples (1051, 1052) of a method for setting a default avatar for each second software application. The default avatar may represent an avatar used in the second software application (App X) when the second software application (App X) is executed.

[0175] Referring to example (1051), the wearable device (103) may display a UI (430) for the first software application. For example, the UI (430) may include a first portion (431) and a second portion (432). For example, the first portion (431) may display at least one second visual object (431-2) representing a candidate avatar. For example, when the second visual object (431-2) is selected, the second portion (432) may include an area (432-1) for displaying the avatar (1060). For example, the area (432-1) may be used to provide a preview of the avatar (1060).

[0176] Referring to example (1052), based on the input for area (432-1), a UI (430) including a screen for setting the default avatar may be displayed. The UI (430) including the screen of example (1052) may include a preview for the avatar (1060), icons (1071, 1072) representing a second software application, and toggles (1081, 1082) for setting the default avatar. For example, the icons (1071, 1072) and the toggles (1081, 1082) may be used to set the default avatar for the avatar (1060). For example, each of the icons (1071, 1072) may represent an icon of a second software application stored in the wearable device (103). For example, icon (1071) may represent an icon of a second software application (App A), and icon (1072) may represent an icon of a second software application (App B). For example, toggle (1081) may be used to activate or deactivate setting of avatar (1060) as the default avatar for the second software application (App A). ​​For example, toggle (1082) may be used to activate or deactivate setting of avatar (1060) as the default avatar for the second software application (App B). For example, the wearable device (103) may identify an input to toggle (1081) (or toggle (1082)) and activate or deactivate the setting of the default avatar based on the input. The wearable device (103) can display a virtual environment provided by the second software application (App A) including the avatar (1060) when the avatar (1060) runs the second software application (App A) set as the default avatar.

[0177] Figures 11a and 11b illustrate examples of virtual objects displayed within a virtual environment while changing at least a portion of an avatar.

[0178] Figure 11a illustrates an example of a virtual object displayed within a virtual environment (1130) while changing an avatar to another avatar. Figure 11b illustrates an example of a virtual object displayed within a virtual environment (1180) while changing a portion (e.g., appearance) of an avatar.

[0179] Referring to FIG. 11A, the wearable device (103) may change from a second visual object (1110) representing a first avatar (1131) to a second visual object (1120) representing a second avatar (1132) based on an input to the UI (430) of the first software application. For example, the wearable device (103) may identify the input to the UI (430) that displays the second visual object (1110) representing the first avatar (1131), which is a candidate avatar. The input may include an input to the second visual object (1120) representing the second avatar (1132). Based on the above input, while changing from the second visual object (1110) representing the first avatar (1131) to the second visual object (1120) representing the second avatar (1132), the wearable device (103) can display a virtual environment (1130). If the second visual object (1110) representing the first avatar (1131) is selected, the wearable device (103) can display a virtual environment (1130) including the first avatar (1131). If the second visual object (1120) is identified (or selected) based on the above input, the wearable device (103) can display a virtual environment (1130) including a dummy avatar (1140) and information about the user (1145). The dummy avatar (1140) and information about the user (1145) can be referenced as the virtual object. A dummy avatar (1140) may be used to notify a change in the first avatar (1131) within the virtual environment (1130). The user information (1145) may include the user's account information. The account information may include the user's account information or ID of a second software application providing the virtual environment (1130). The wearable device (103) may display a virtual environment (1130) including a second avatar (1132) based on an input for applying the second visual object (1120).The input for applying the second visual object (1120) may include an input for the UI (430).

[0180] Referring to FIG. 11B, the wearable device (103) may change an icon (1160) representing an item to be worn by the avatar to an icon (1170) representing another item based on an input to the UI (430) of the first software application. For example, the wearable device (103) may obtain the input for an icon (1170) representing glasses. Accordingly, the wearable device (103) may deactivate the icon (1160) representing not wearing an accessory and activate the icon (1170). Based on the input, while changing from the icon (1160) to the icon (1170), the wearable device (103) may display a virtual environment (1180). When the icon (1160) is selected, the wearable device (103) can display a virtual environment (1180) including an avatar (1181) not wearing an accessory. The avatar (1181) not wearing an accessory can have a first appearance. Based on the input, when the icon (1170) is identified (or selected), the wearable device (103) can display a virtual environment (1180) including an image (1190) representing a second appearance to be changed together with the avatar (1181). The image (1190) can be referenced as the virtual object. Based on the input for applying an item according to the icon (1170) to the avatar (1181), the wearable device (103) can display a virtual environment (1180) including an avatar (1182) wearing glasses. An avatar (1182) wearing the above glasses may have the second appearance. The input for applying the icon (1170) may include an input for the UI (430).

[0181] Figures 12a to 12c illustrate examples of a method of using a second software application through login information associated with an avatar of a first software application.

[0182] Figures 12a to 12c illustrate examples of a method for using the second software application via login information associated with the avatar of the first software application. The avatar of the first software application may be included in avatars obtained from providers (e.g., source applications).

[0183] Referring to example (1201) of FIG. 12A, the wearable device (103) may display a home screen. For example, the home screen may represent the main screen provided by the wearable device (103). For example, the wearable device (103) may display the home screen including a task bar (420). However, the embodiments of the present disclosure are not limited thereto. For example, the wearable device (103) may activate or deactivate the display of the task bar (420) based on a specified input or a specified gesture.

[0184] Referring to example (1202), the wearable device (103) can display a virtual environment (1210). For example, the wearable device (103) can display the virtual environment (1210) based on the execution of the second software application (App A). ​​For example, the virtual environment (1210) can display a screen (1215) for logging in. For example, the screen (1215) can include a visual object for entering an ID and password for logging in to the second software application (App A) that provides the virtual environment (1210). For example, the screen (1215) can at least partially overlap with the virtual environment (1280).

[0185] Referring to example (1203), the wearable device (103) may display the UI (430) of the first software application while displaying the virtual environment (1210). For example, the wearable device (103) may display the UI (430) based on an input to a visual object (421) of the task bar (420).

[0186] In one embodiment, a user may select an avatar within the UI (430). For example, the wearable device (103) may obtain the selected avatar within the UI (430) based on the user's input. The selected avatar may represent an avatar that the user will use in the second software application (App A).

[0187] Referring to example (1204), the wearable device (103) may display a visual notification (1220) guiding the user to link the selected avatar with the user's login information based on acquiring the selected avatar. For example, the wearable device (103) may display the visual notification (1220) based on an input to an icon (not shown) requesting linking of login information after acquiring the selected avatar. For example, the visual notification (1220) may include a text asking whether to perform login by linking the login information to the selected avatar, a visual object (1221) approving the linking, and a visual object (1223) rejecting the linking.

[0188] For example, the login information may include the ID and password for logging in to the second software application (App A). ​​Alternatively, for example, the login information may include the ID and password for logging in to a plurality of second software applications (e.g., App A, App B). The login information for logging in to the plurality of second software applications may be referred to as SSO (single sign-on) information or integrated login information.

[0189] According to one embodiment, the wearable device (103) may perform a login of the second software application (App A) using the selected avatar based on an input to the visual object (1221). For example, the wearable device (103) may request authentication from a server managing the second software application (App A) in response to the first software application acquiring the selected avatar after the selected avatar is associated with the login information. In one example, the second software application (App A) may be in the second state. In other words, the app avatar provided by the second software application (App A) may not be set (or used). For example, the wearable device (103) may display a virtual environment (1210) including the selected avatar based on the success of the authentication. For example, the wearable device (103) may display a screen (1215) if the authentication fails.

[0190] Referring to example (1231) of FIG. 12B, the wearable device (103) may display a home screen. For example, the home screen may represent the main screen provided by the wearable device (103). For example, the wearable device (103) may display the home screen including a task bar (420). However, the embodiments of the present disclosure are not limited thereto. For example, the wearable device (103) may activate or deactivate the display of the task bar (420) based on a specified input or a specified gesture.

[0191] Referring to example (1232), the wearable device (103) can display a virtual environment (1210). For example, the wearable device (103) can display the virtual environment (1210) based on the execution of the second software application (App A). ​​For example, the virtual environment (1210) can display a screen (1215) for logging in. For example, the screen (1215) can include a visual object for entering an ID and password for logging in to the second software application (App A) that provides the virtual environment (1210). For example, the screen (1215) can at least partially overlap with the virtual environment (1280).

[0192] Referring to example (1233), the wearable device (103) may display the UI (430) of the first software application while displaying the virtual environment (1210). For example, the wearable device (103) may display the UI (430) based on an input to a visual object (421) of the task bar (420).

[0193] In one embodiment, a user may select an avatar within the UI (430). For example, the wearable device (103) may obtain the selected avatar within the UI (430) based on the user's input. The selected avatar may represent an avatar to be used by the user in the second software application (App A). ​​For example, the wearable device (103) may obtain the selected avatar based on the input to the second visual object (431-2) for the selected avatar.

[0194] For example, the wearable device (103) may display visual information (1241, 1242, 1243) together with a second visual object (431-2) for the selected avatar. For example, the visual information (1241, 1242, 1243) may indicate a second software application associated with the selected avatar. For example, the visual information (1241) may include text (e.g., A) indicating the second software application (App A). ​​In addition, for example, the visual information (1242) may include text (e.g., B) indicating the second software application (App B). In addition, for example, the visual information (1243) may include text (e.g., C) indicating the second software application (App C). However, the embodiments of the present disclosure are not limited thereto. For example, if the selected avatar is associated with all second software applications, the visual information may point to all second software applications and may include text indicating that it points to all second software applications (e.g., ALL).

[0195] Referring to example (1261) of FIG. 12C, the wearable device (103) can display a virtual environment (1210). For example, the wearable device (103) can display the virtual environment (1210) based on the execution of the second software application (App A). ​​For example, the virtual environment (1210) can include an avatar (1270). For example, the avatar (1270) can be an avatar of the first software application. In this case, the avatar (1270) can be linked to the login information of the second software application (App A) and the second software application (App B) through the first software application.

[0196] Referring to example (1262), the wearable device (103) may stop displaying the virtual environment (1210) based on the termination of the second software application (App A). ​​In addition, the wearable device (103) may display the virtual environment (1280) based on the execution of the second software application (App B). Referring to example (1263), after displaying the virtual environment (1280), the wearable device (103) may display a screen (1215) for logging in to the second software application (App B). For example, the screen (1215) may at least partially overlap with the virtual environment (1280).

[0197] Referring to example (1264), the wearable device (103) may display a visual notification (1290) based on identifying that the avatar (1270) is associated with the second software application (App B). For example, the visual notification (1290) may at least partially overlap the virtual environment (1280). For example, the visual notification (1290) may be displayed while the virtual environment (1280) is displayed. For example, the visual notification (1290) may include text asking whether to log in to the currently running app (e.g., the second software application (App B)) via the selected avatar (e.g., the avatar (1270)), a visual object (1291) for approval, and a visual object (1293) for rejection. For example, the wearable device (103) may display a virtual environment (1280) including an avatar (1270) based on an input to a visual object (1291). Alternatively, the wearable device (103) may display a virtual environment (1280) based on an input to a visual object (1293) and display a screen for selecting an app avatar provided by the second software application (App B).

[0198] Figure 13 illustrates an example of an operational flow for a wearable device to manage avatars obtained from multiple providers and display the avatars in a software application of the wearable device.

[0199] At least some of the methods of FIG. 13 may be performed by the wearable device (103) of FIG. 5. For example, at least some of the methods may be controlled by the processor (511) of the wearable device (103). In the embodiments described below, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel.

[0200] In operation (1310), the wearable device (103) may display a task bar (e.g., task bar (420) of FIG. 4A) including a visual object provided by a first application for using avatars provided by multiple applications in an application stored in the wearable device (103). The first application may be used to integrate (or be compatible with) avatars provided by the multiple applications. The multiple applications may represent source applications.

[0201] For example, the wearable device (103) may execute the first application. For example, the wearable device (103) may execute the first application based on at least a portion of an input to the task bar that displays the global menu of the wearable device (103).

[0202] According to one embodiment, the task bar may include a plurality of icons. For example, the plurality of icons may include icons for the home screen, icons for providing software applications stored in the wearable device (103), and icons set for quick execution. According to one embodiment, the task bar may include a visual object provided by the first software application (e.g., the visual object (421) of FIG. 4A). For example, the visual object may include an area for displaying a set avatar among avatars provided by the plurality of applications. For example, based on an input to the visual object, the first application may be executed. For example, the task bar may be referred to as a device menu, a global menu, or a global settings menu. In other words, the task bar may be used to manage or provide information of the wearable device (103).

[0203] In one embodiment, the visual object may represent a first avatar among the avatars. For example, the first avatar may be provided by a specific source application (e.g., the first source application) among the plurality of applications.

[0204] According to one embodiment, the wearable device (103) may display a UI (e.g., UI (430) of FIG. 4A) of the first application in response to execution of the first application. The first application may display a user interface for displaying and editing avatars provided by the plurality of applications. For example, the UI may include a first portion (e.g., first portion (431) of FIG. 4A) including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information. In addition, for example, the UI may include a second portion (e.g., second portion (432) of FIG. 4A) for providing a preview (or preview image) of a candidate avatar corresponding to a second visual object selected from among the at least one second visual object based on an input to the first portion. However, the embodiments of the present disclosure are not limited thereto. For example, the UI may display avatars provided by the plurality of applications within a non-split screen.

[0205] According to one embodiment, the wearable device (103) can obtain avatar-related information from the plurality of applications. For example, the plurality of applications may include a first source application and a second source application. For example, the wearable device (103) can obtain first avatar-related information from the first source application and second avatar-related information from the second source application. For example, the first avatar-related information may include information for generating a first avatar set provided by the first source application and information for generating a first item set provided by the first source application. In addition, for example, the second avatar-related information may include information for generating a second avatar set provided by the second source application and information for generating a second item set provided by the second source application.

[0206] According to one embodiment, the wearable device (103) may process the avatar-related information. For example, the wearable device (103) may obtain a scale of the avatar-related information. For example, the wearable device (103) may identify a first scale based on a proportion of the first avatar set provided by the first source application. The first scale may be referred to as a first proportion. For example, the first proportion may include a proportion (or body proportion) of the first avatar set. The first item set may have the first proportion based on the first scale. Alternatively, for example, the wearable device (103) may identify a second scale based on a proportion of the second avatar set provided by the second source application. The second scale may be referred to as a second proportion. For example, the second ratio may include the proportions (or body proportions) of the second avatar set. Additionally, the second item set may have the second ratio based on the second scale.

[0207] In one embodiment, the wearable device (103) may compare the identified ratio with a specified ratio. For example, the wearable device (103) may compare the first ratio with the specified ratio set within a first application for integrating avatars provided by the plurality of applications. Alternatively, for example, the wearable device (103) may compare the specified ratio with the second ratio. If the ratios do not correspond, the wearable device (103) may process the avatar-related information so that the first ratio (or the second ratio) has the specified ratio. As described above, the process of adjusting the ratio of the avatar-related information obtained by the wearable device (103) from the plurality of applications to correspond to the specified ratio may be referred to as normalization. Based on the normalization, the wearable device (103) may integrate and manage the avatars provided by the plurality of applications through the first application.

[0208] According to one embodiment, the wearable device (103) can perform avatar editing. For example, the avatar may be included in avatars provided by the plurality of applications. For example, the avatar may be provided by the first source application or the second source application.

[0209] For example, the wearable device (103) can change the item worn by the avatar. For example, the wearable device (103) can change the item (or asset) worn by the avatar based on at least a portion of the user's input to the UI. Alternatively, for example, the wearable device (103) can change the avatar to another avatar.

[0210] In operation (1320), the wearable device (103) may execute a second application that provides a virtual environment stored in the wearable device (103) based on at least a portion of the user's input. For example, the wearable device (103) may display a virtual environment based on the execution of the second application. For example, the wearable device (103) may execute the second application that provides the virtual environment. For example, the second application may represent a software application stored in the wearable device (103). In other words, unlike the source application of the plurality of applications that provide the avatars, the second application may be stored in the wearable device (103).

[0211] In operation (1330), the wearable device (103) can check whether a second avatar provided by the second application, set for use within the second application, exists. For example, the wearable device (103) can check whether the second avatar exists.

[0212] According to one embodiment, the wearable device (103) may identify a state of the second application in response to the execution of the second application. For example, the state may include a first state in which an avatar (or app avatar) provided by the second application set for the second application exists, and a second state different from the first state. For example, the second state may include a case in which the app avatar provided by the second application is not set for the second application.

[0213] In operation (1330), if the second avatar does not exist (or in the second state), the wearable device (103) can perform operation (1340). Alternatively, in operation (1330), if the second avatar exists (or in the first state), the wearable device (103) can perform operation (1350).

[0214] In operation (1340), the wearable device (103) may display the virtual environment including the first avatar. For example, the wearable device (103) may display the virtual environment including the first avatar based on the visual object displaying the first avatar among the avatars in the second state. The first avatar may be included in the avatars provided by the plurality of applications that are integrated (or compatible) with the first application. For example, the wearable device (103) may display the virtual environment including the first avatar based on an image representing the first avatar displayed by the visual object of the task bar. Alternatively, for example, if the visual object of the task bar displays a default image different from the avatars provided by the plurality of applications or the display of the visual object is deactivated, the wearable device (103) may display a screen for selecting an app avatar (e.g., the second avatar) provided by the second application. For example, the screen may at least partially overlap with the virtual environment.

[0215] According to one embodiment, the wearable device (103) may adjust the scale of the avatar when displaying the virtual environment including the avatar. For example, the wearable device (103) may adjust the scale of the avatar (e.g., the first avatar) to correspond to the scale supported by the second application. The scale of the avatar may be the specified scale of the first application.

[0216] In one embodiment, the wearable device (103) may set a default avatar applicable to each second application based on at least some of the inputs to the UI. For example, the default avatar may be displayed through the visual object.

[0217] According to one embodiment, the wearable device (103) may perform a login for the second application after executing the second application. For example, the wearable device (103) may link the first avatar provided by the first source application with the user's login information. For example, the wearable device (103) may display a visual notification guiding the linking of the first avatar and the login information. If the first avatar and the login information are linked based on an input for the visual notification, the wearable device (103) may perform the login based on the first avatar while executing the second application in which the first avatar is set as the default avatar. For example, the wearable device (103) may request authentication for the second application based on the first avatar to a server managing the second application. Based on the success of the above authentication, the wearable device (103) can display the virtual environment including the first avatar. For specific details related thereto, reference may be made to the contents of FIG. 12a.

[0218] According to one embodiment, the wearable device (103) may display the UI including a visual object that indicates a candidate avatar among the avatars provided by the plurality of applications. At this time, the wearable device (103) may display visual information for notifying a second application to which the candidate avatar is linked, along with the visual notification corresponding to the candidate avatar. For example, in an example in which the first avatar and the second application are linked, the wearable device (103) may display the visual information indicating the second application along with the visual notification for the first avatar. For specific details related thereto, reference may be made to the contents of FIG. 12b.

[0219] In one embodiment, the wearable device (103) may display another visual notification inquiring whether to log in to a third application different from the second application using the first avatar to which the user's login information is linked. For example, if the first avatar is selected as the default avatar and the third application is executed, the wearable device (103) may display the other visual notification. Based on the input for the other visual notification, the wearable device (103) may log in to the third application based on the first avatar.

[0220] According to one embodiment, the wearable device (103) may perform a change of the first avatar while displaying the virtual environment provided by the second application including the first avatar. For example, the wearable device (103) may perform a change of the first avatar using the UI of the first application while displaying the virtual environment. For example, the change of the first avatar may include changing the appearance of the first avatar from the first appearance to the second appearance, or from the first avatar to a third avatar. For example, the third avatar may be provided by the second source application among the plurality of applications. According to one embodiment, the wearable device (103) may display the virtual environment including a virtual object that notifies the change of the first avatar. For example, the virtual object may include an image representing the second appearance to be changed from the first appearance. Alternatively, for example, the virtual object may include a dummy avatar and information about the user. For example, the dummy avatar may be used to notify a change in the first avatar. For example, the information about the user may include the user's account identifier or the user's name. For specific details related thereto, reference may be made to the contents of FIGS. 11A and 11B.

[0221] In operation (1350), the wearable device (103) may display the virtual environment including the second avatar. The second avatar may represent an example of the app avatar provided by the second application. For example, the wearable device (103) may display the virtual environment including the second avatar in the first state set for the second application, provided by the second application.

[0222] As described above, the wearable device (103) may include a memory (517) that stores instructions and includes one or more storage media. The wearable device (103) may include a display (513). The wearable device (103) may include at least one processor (511) that includes a processing circuit. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display, through the display (513), a task bar that includes an icon of a first software application for merging avatars provided by source applications. The icon may include an area for displaying an avatar among the avatars. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to execute a second software application that provides a virtual environment stored within the wearable device (103) based on at least a portion of a user's input. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display, through the display (513), the virtual environment including a first avatar provided by the second software application in a first state set for the second software application.The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display, through the display (513), the virtual environment including the second avatar based on the icon representing the second avatar among the avatars in a second state different from the first state.

[0223] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to identify whether information about the first avatar is acquired based on execution of the second software application. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display the virtual environment including the first avatar in the first state identified based on acquisition of the information about the first avatar. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display the virtual environment including the second avatar in the second state identified based on not acquiring the information about the first avatar.

[0224] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display the virtual environment including the second avatar based on the icon representing the second avatar in the second state. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a screen for selection of an avatar provided by the second software application based on the icon representing an image different from the avatars in the second state. The image may include a default image of the first software application.

[0225] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to execute, after the second software application has terminated, a third software application stored within the wearable device (103) and providing another virtual environment based on at least some of another input from the user. The third software application may not support the display of an avatar. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display the task bar with the display of the icon of the first software application disabled together with the other virtual environment.

[0226] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a user interface of the first software application based on execution of the first software application. The user interface may include a first portion including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information, and a second portion providing a preview of a selected candidate avatar. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display the user interface, based on at least a portion of an input to the user interface, the user interface including an application (app) icon representing the second software application that supports display of an avatar and a toggle for using the second avatar as a default avatar for the second software application. Based on the activated toggle, in the second state, the virtual environment including the second avatar may be displayed.

[0227] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to obtain information about a first avatar set and information about a first item set provided by a first source application among the source applications. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to obtain information about a second avatar set and information about a second item set provided by a second source application different from the first source application among the source applications. The information about the first item set and the information about the second item set may be used for first avatars included in the first avatar set and second avatars included in the second avatar set, respectively.

[0228] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to convert and store body proportions of the first avatars of the first avatar set from a first proportion of the first source application to a specified proportion of the first software application. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to convert and store body proportions of the second avatars of the second avatar set from a second proportion of the second source application to the specified proportion of the first software application.

[0229] According to one embodiment, the specified ratio may be applied to the number of virtual joints constituting the avatar and the positions of the virtual joints.

[0230] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a user interface of the first software application based on execution of the first software application. The user interface may include a first portion including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information, and a second portion providing a preview of a selected candidate avatar. The selected candidate avatar displayed in the second portion may have the specified ratio.

[0231] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a user interface of the first software application based on execution of the first software application while displaying the virtual environment including the second avatar in the second state. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to identify a second appearance of the second avatar to be changed from the first appearance based on at least a portion of the user's input to the user interface. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a virtual object representing the second appearance and the virtual environment including the second avatar.

[0232] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a user interface of the first software application based on execution of the first software application while displaying the virtual environment including the second avatar in the second state. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to identify a third avatar to be changed from the second avatar based on at least a portion of the user's input to the user interface. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display the virtual environment including information about the user of the second software application and a dummy avatar changed from the second avatar. The above dummy avatar can be used to notify changes to the second avatar.

[0233] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a screen for logging in to the second software application for the user in response to the execution of the second software application. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a user interface of the first software application executed based on an input to the icon while the screen is displayed. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display a visual object guiding the user to associate login information with the second avatar based on at least a portion of the input to the user interface.

[0234] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to request authentication based on the second avatar to a server managing the second software application in the second state when the second avatar and the login information are associated based on the input to the visual object. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display the virtual environment including the second avatar based on the successful authentication.

[0235] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to execute a third software application after the second software application associated with the second avatar has been terminated. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to, in response to the execution of the third software application, display another screen for logging in to the third software application for the user. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to, while the other screen is displayed, display another visual object that inquires whether to perform a log-in to the third software application through the second avatar. When a login to the third software application is performed through the second avatar based on an input to the other visual object, another virtual environment provided by the third software application including the second avatar may be displayed.

[0236] According to one embodiment, the user interface may include a first portion including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information, and a second portion providing a preview of a selected candidate avatar. The instructions, when individually or collectively executed by the at least one processor (511), may cause the wearable device (103) to display visual information indicating that the second software application is associated with the second avatar, together with a second visual object corresponding to the second avatar in the user interface, after the second avatar and the login information are associated based on an input to the visual object.

[0237] As described above, a method performed by a wearable device (103) may include an operation of displaying, through the display (513), a task bar including an icon of a first software application for merging avatars provided by source applications. The icon may include an area for displaying a set avatar among the avatars. The method may include an operation of executing a second software application that provides a virtual environment stored in the wearable device (103) based on at least a portion of a user's input. The method may include an operation of displaying the virtual environment including the first avatar in a first state in which the first avatar provided by the second software application is set for the second software application. The method may include an operation of displaying the virtual environment including the second avatar in a second state different from the first state, based on the icon displaying the second avatar among the avatars.

[0238] In one embodiment, the method may include an operation of identifying whether information about the first avatar set for the second software application is acquired based on execution of the second software application. The method may include an operation of displaying the virtual environment including the first avatar in the first state identified based on acquisition of the information about the first avatar. The method may include an operation of displaying the virtual environment including the second avatar in the second state identified based on not acquiring the information about the first avatar.

[0239] In one embodiment, the method may include an operation of displaying the virtual environment including the second avatar based on the icon displaying the second avatar in the second state. The method may include an operation of displaying a screen for selecting an avatar provided by the second software application based on the icon displaying an image different from the avatars in the second state. The image may include a default image of the first software application.

[0240] In one embodiment, the method may include, after the second software application is terminated, executing a third software application stored in the wearable device (103) and providing another virtual environment that does not support the display of an avatar, based on at least a portion of another input from the user. The method may include displaying the task bar with the display of the icon of the first software application disabled together with the other virtual environment.

[0241] As described above, a non-transitory computer-readable storage medium may store one or more programs including instructions that, when individually or collectively executed by at least one processor (511) of a wearable device (103) including a display (513), cause the wearable device (103) to display, through the display (513), a task bar including an icon of a first software application for merging avatars provided by source applications. The icon may include an area for displaying a set avatar among the avatars. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to execute a second software application that provides a virtual environment stored within the wearable device (103) based on at least a portion of a user's input. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to display, through the display (513), the virtual environment including a first avatar provided by the second software application in a first state set for the second software application.The non-transitory computer-readable storage medium may store one or more programs including instructions that, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to display, through the display (513), the virtual environment including the second avatar based on the icon representing the second avatar among the avatars in a second state different from the first state.

[0242] Electronic devices according to the various embodiments disclosed in this document may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to the embodiments of this document are not limited to the aforementioned devices.

[0243] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, 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 the items, unless the context clearly indicates otherwise. In this document, each of the phrases "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" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0244] The term "module" used in 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. A module may be an integral component, or a minimum unit or part of such a component 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).

[0245] Various embodiments of the present document may be implemented as software (e.g., a program (140)) including one or more instructions stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)). For example, a processor (e.g., a processor (120)) of the machine (e.g., an electronic device (101)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate 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 executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0246] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0247] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In a wearable device (103), A memory (517) storing instructions and including one or more storage media; display (513); and At least one processor (511) comprising a processing circuit; The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: A task bar including a visual object provided by a first application for use in an application stored in the wearable device (103) among avatars provided by a plurality of applications is displayed through the display (513), and the visual object represents a first avatar among the avatars; Executing a second application that provides a virtual environment stored within the wearable device (103) based on at least some of the user's input; Checking whether there is a second avatar provided by the second application set for use within the second application; and If the second avatar does not exist, causing the virtual environment including the first avatar to be displayed through the display (513). Wearable device (103).

2. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: If the second avatar exists, causing the virtual environment including the second avatar to be displayed through the display (513). Wearable device (103).

3. In claim 2, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: If the above visual object shows an image different from the above avatars, cause a screen for selecting an avatar provided by the second application to be displayed, The above image includes a default image of the first application. Wearable device (103).

4. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: After the second application is terminated, a third application is executed based on at least some of another input of the user, stored in the wearable device (103), providing another virtual environment, and the third application does not support display of an avatar; and causing said task bar to be displayed with said visual object of said first application disabled together with said other virtual environment; Wearable device (103).

5. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: Based on the execution of the first application, displaying a user interface of the first application, the user interface including a first portion including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information, and a second portion providing a preview for a selected candidate avatar; and Causing said user interface to be displayed, based at least in part on an input to said user interface, an icon representing said second application that supports display of an avatar and a toggle for using said first avatar as a default avatar for said second application; Based on the activated toggle, the virtual environment including the first avatar is displayed. Wearable device (103).

6. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: Obtaining information about a first avatar set and information about a first item set provided by a first source application among the above multiple applications, and To cause a second avatar set and a second item set to be acquired from a second source application different from the first source application among the plurality of applications, Each of the information about the first item set and the information about the second item set is used for the first avatars included in the first avatar set and the second avatars included in the second avatar set. Wearable device (103).

7. In claim 6, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: Converting the body proportions of the first avatars of the first avatar set from the first proportion of the first source application to the specified proportion of the first application and storing them, and Causing the body proportions of the second avatars of the second avatar set to be converted from the second proportion of the second source application to the specified proportion of the first application and stored. Wearable device (103).

8. In claim 7, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: Based on the execution of the first application, the user interface of the first application is configured to be displayed, The user interface comprises a first portion including a first visual object representing account information and at least one second visual object representing a candidate avatar according to the account information, and a second portion providing a preview of a selected candidate avatar, The selected candidate avatar displayed in the second part above has the specified ratio, Wearable device (103).

9. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: While displaying the virtual environment including the first avatar, based on execution of the first application, displaying a user interface of the first application; identifying a second appearance to be changed from the first appearance of the first avatar based on at least a portion of the user's input to the user interface; and Causing to display the virtual environment including the virtual object representing the second appearance and the first avatar; Wearable device (103).

10. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: While displaying the virtual environment including the first avatar, based on execution of the first application, displaying a user interface of the first application; identifying a third avatar to be changed from the first avatar based at least in part on said user input to said user interface; and Causing the virtual environment to be displayed, including information about the user of the second application and a dummy avatar changed from the first avatar, The above dummy avatar is used to notify changes to the first avatar. Wearable device (103).

11. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: In response to the execution of the second application, a screen for logging in to the second application is displayed for the user; While the above screen is displayed, displaying the user interface of the first application executed based on the input to the visual object; and Causing a visual notification to be displayed, based at least in part on input to said user interface, to prompt the user to associate said first avatar with his / her login information; Wearable device (103).

12. In claim 11, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: When the first avatar and the login information are linked based on the input for the above visual notification, requesting authentication based on the first avatar to the server managing the second application; and Based on the success of the above authentication, causing the virtual environment including the first avatar to be displayed, Wearable device (103).

13. In claim 12, The above instructions, when individually or collectively executed by the at least one processor (511), cause the wearable device (103) to: After the second application linked to the first avatar is terminated, the third application is executed; In response to the execution of the third application, displaying another screen for logging in to the third application for the user; and While the above other screen is displayed, cause another visual notification to be displayed asking whether to perform a login of the third application through the first avatar, When a login to the third application is performed through the first avatar based on an input for the other visual notification, another virtual environment provided by the third application including the first avatar is displayed. Wearable device (103).

14. In a method performed by a wearable device (103), An action of displaying a task bar including a visual object provided by a first application for using avatars provided by multiple applications in an application stored in the wearable (103), the visual object representing a first avatar among the avatars; An action of executing a second application providing a virtual environment stored within the wearable device (103) based on at least some of the user's input; An operation for checking whether a second avatar provided by the second application set for use within the second application exists; and Including an action of displaying the virtual environment including the first avatar if the second avatar does not exist. method.

15. A non-transitory computer-readable storage medium, when executed individually or collectively by at least one processor (511) of a wearable device (103) including a display (513), causes the wearable device (103) to: A task bar including a visual object provided by a first application for use in an application stored in the wearable device (103) among avatars provided by a plurality of applications is displayed through the display (513), and the visual object represents a first avatar among the avatars; Executing a second application that provides a virtual environment stored within the wearable device (103) based on at least some of the user's input; Checking whether there is a second avatar provided by the second application set for use within the second application; and storing one or more programs including instructions causing the virtual environment including the first avatar to be displayed through the display (513) if the second avatar does not exist; A non-transitory computer-readable storage medium.

Images