Wearable device, method, and non-transitory computer-readable storage medium for changing scheme for displaying avatar

Abstract

This wearable device may comprise: a memory for storing instructions; one or more first cameras arranged in relation to the face of a user; one or more second cameras arranged in relation to the eyes of the user; one or more microphones; a display assembly including at least one display; and at least one processor. The wearable device may be caused to: display an avatar on the basis of generating first data for expressing a facial expression of the avatar using the one or more first cameras, generating second data for expressing a gaze of the avatar using the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using the one or more microphones; identify an event that causes a change in a scheme for displaying the avatar while the avatar is being displayed on the basis of generating the first data, generating the second data, and generating the third data; and stop at least one of generating the first data, generating the second data, or generating the third data in response to the event.

Description

Wearable device, method, and non-transitory computer-readable storage medium for changing the method for displaying an avatar

[0001] The present disclosure relates to a wearable device, a method, and a non-transitory computer-readable storage medium for changing a method for displaying an avatar.

[0002] A wearable device may include a camera and a display. The wearable device may be utilized as a tool for implementing virtual reality, augmented reality, and mixed reality. The wearable device may display an avatar on the display. The wearable device may provide a portion of the avatar on the display using an image acquired through the camera.

[0003] The above information may be provided as background art to aid in understanding the present disclosure.

[0004] No claim or determination is made as to whether any of the above is applicable as prior art to the present disclosure.

[0005] A wearable device is described. The wearable device may include a memory for storing instructions and including one or more storage media. The wearable device may include one or more first cameras arranged relative to the face of a user wearing the wearable device. The wearable device may include one or more second cameras arranged relative to the eyes of the user wearing the wearable device. The wearable device may include one or more microphones. The wearable device may include a display assembly comprising at least one display. The wearable device may include at least one processor comprising a processing circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data.The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device, in response to the event, to stop one or more of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0006] A method is provided. The method may be executed in a wearable device having one or more first cameras arranged with respect to a face of a user wearing the wearable device, one or more second cameras arranged with respect to an eye of the user wearing the wearable device, one or more microphones, and a display assembly including at least one display. The method may include an operation of displaying the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The method may include an action of identifying an event that causes a change in the manner of displaying the avatar while the avatar is being displayed based on generating the first data, generating the second data, and generating the third data. The method may include an action of stopping, in response to the event, one or more of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0007] A non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a wearable device having one or more first cameras arranged relative to a face of a user wearing the wearable device, one or more second cameras arranged relative to an eye of the user wearing the wearable device, one or more microphones, and a display assembly including at least one display, cause the wearable device to display an avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify an event that causes a change in the manner of displaying the avatar while the avatar is being displayed based on generating the first data, generating the second data, and generating the third data. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to, in response to the event, stop one or more of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0008] A wearable device is described. The wearable device may include a memory that stores instructions. The wearable device may include one or more first cameras arranged in relation to the face of a user wearing the wearable device. The wearable device may include one or more second cameras arranged in relation to the eyes of the user wearing the wearable device. The wearable device may include one or more microphones. The wearable device may include a display assembly including at least one display. The wearable device may include at least one processor. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data.The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify a priority corresponding to the event among generating the first data, generating the second data, and generating the third data. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to determine, based on the identified priority, at least one of the first data, the second data, and the third data as data for displaying the avatar.

[0009] A method is provided. The method may be executed in a wearable device having one or more first cameras arranged with respect to a face of a user wearing the wearable device, one or more second cameras arranged with respect to an eye of the user wearing the wearable device, one or more microphones, and a display assembly including at least one display. The method may include an operation of displaying the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The method may include an operation of identifying an event that causes a change in the manner of displaying the avatar while the avatar is being displayed based on generating the first data, generating the second data, and generating the third data. The method may include an operation of identifying, in response to the event, a priority corresponding to the event among generating the first data, generating the second data, and generating the third data. The method may include an operation of determining, based on the identified priority, at least one of the first data, the second data, and the third data as data for displaying the avatar.

[0010] A non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a wearable device having one or more first cameras arranged with respect to a face of a user wearing the wearable device, one or more second cameras arranged with respect to an eye of the user wearing the wearable device, one or more microphones, and a display assembly including at least one display, cause the wearable device to display an avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify an event that causes a change in the manner of displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify a priority corresponding to the event among generating the first data, generating the second data, and generating the third data.The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to determine, based on the identified priority, at least one of the first data, the second data, and the third data as data for displaying the avatar.

[0011] Figure 1 illustrates an example of an environment for displaying an avatar.

[0012] Figure 2 is a simplified block diagram of an exemplary wearable device.

[0013] Figure 3 is a flowchart illustrating an exemplary method for stopping data generation for displaying an avatar.

[0014] Figure 4 illustrates an example of generating data to display an avatar using a camera.

[0015] Figure 5 illustrates an example of displaying an avatar using pre-saved animation data.

[0016] Figure 6 illustrates an example of a device for displaying an avatar.

[0017] Figure 7 illustrates an example of identifying priorities corresponding to events.

[0018] Figure 8a illustrates an example where generating data for representing the avatar's gaze is stopped.

[0019] Figure 8b illustrates an example in which the generation of data for expressing the avatar's facial expression is stopped.

[0020] Figure 8c illustrates an example where generating data to represent a part of an avatar is stopped.

[0021] Figure 9 is a flowchart illustrating an exemplary method for resuming data generation to display an avatar.

[0022] Figure 10 illustrates another example of an event that obtains a temperature value of a wearable device below a threshold temperature value.

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

[0024] Figure 12a illustrates an example of a perspective view of a wearable device.

[0025] FIG. 12b illustrates an example of one or more hardware devices arranged within a wearable device.

[0026] Figures 13a and 13b illustrate an example of the appearance of a wearable device.

[0027] Figure 14 illustrates an example of a block diagram of a wearable device.

[0028] Fig. 15 shows an example of a block diagram of an electronic device for displaying an image in a virtual space.

[0029] Figure 1 illustrates an example of an environment for displaying an avatar.

[0030] Referring to FIG. 1, a wearable device (100) may represent a device usable for displaying an avatar (e.g., an avatar (420) of FIG. 4). A state (110) may be described as a state in which the wearable device (100) generates data to display the avatar corresponding to a user (130) wearing the wearable device (100). For example, the wearable device (100) may display the avatar through a display assembly (e.g., a display assembly (208) of FIG. 2). For example, the wearable device (100) may include cameras (e.g., one or more first cameras (209), one or more second cameras (210), and one or more third cameras (211) of FIG. 2).

[0031] State (120) can be described as a state in which the wearable device (100) generates fifth data to display an avatar using a control device (e.g., control device (180)). For example, the wearable device (100) can include a communication circuit (e.g., communication circuit (205) of FIG. 2). For example, the wearable device (100) can receive information about the movement of the control device from the control device through the communication circuit to control a part of the avatar. For example, the wearable device (100) can generate fifth data to display a part of the avatar using the information. For example, the wearable device (100) can display a part of the avatar through the display assembly using the fifth data.

[0032] In one embodiment, the wearable device (100) may use the cameras to display the avatar through the display assembly. The temperature value of the wearable device (100) may increase as the wearable device (100) displays the avatar through the display assembly. In one embodiment, the wearable device (100) may need to prevent the temperature value of the wearable device (100) from exceeding a predetermined temperature. For example, if the temperature value of the wearable device (100) exceeds a predetermined temperature, the wearable device (100) may omit displaying the avatar. The wearable device (100) may consume power to display the avatar through the display assembly. The wearable device (100) may need to reduce the amount of power consumed to display the avatar from a rechargeable battery (e.g., the rechargeable battery (215) of FIG. 2). For example, the state of charge (SoC) of a rechargeable battery may be reduced when the wearable device (100) displays the avatar through the display assembly. Depending on the manner in which the avatar (e.g., the avatar (420) of FIG. 4) is displayed, the amount of power consumed from the rechargeable battery (e.g., the rechargeable battery (215) of FIG. 2) may vary. The wearable device (100) may need to stop generating data for displaying the avatar depending on the change in the manner in which the avatar is displayed.

[0033] In one embodiment, the wearable device (100) may identify an event that causes a change in the method for displaying the avatar. For example, the event may include obtaining a temperature value of the wearable device exceeding a threshold temperature value. In response to the event, the wearable device (100) may stop generating data for displaying the avatar. The wearable device (100) may manage the temperature value of the wearable device (100) or the SoC of the wearable device (100) to display the avatar. For example, the wearable device (100) may include hardware components used to perform or execute the above operations. The hardware components are described and exemplified with reference to FIG. 2.

[0034] Figure 2 is a simplified block diagram of an exemplary wearable device.

[0035] Referring to FIG. 2, the wearable device (100) may include at least one processor (207), a communication circuit (205), and a memory (206).

[0036] At least one processor (207) may include a hardware component for processing data using instructions stored in the memory (206). The hardware component for processing data may include a central processing unit (CPU) (e.g., including processing circuitry). The hardware component for processing data may include a graphic processing unit (GPU) (e.g., including processing circuitry). The hardware component for processing data may include a display processing unit (DPU) (e.g., including processing circuitry). The hardware component for processing data may include a neural processing unit (NPU) (e.g., including processing circuitry).

[0037] At least one processor (207) may include one or more cores. For example, at least one processor (207) may have a multi-core processor structure such as a dual core, a quad core, or a hexa core.

[0038] The memory (206) may include hardware components for storing data and / or instructions input to and / or output from at least one processor (207). The memory (206) may include, for example, volatile memory such as random-access memory (RAM), and / or non-volatile memory such as read-only memory (ROM). The volatile memory may include, for example, at least one of dynamic RAM (DRAM), static RAM (SRAM), cache RAM, and pseudo SRAM (PSRAM). The non-volatile memory may include, for example, at least one of programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), flash memory, hard disk, compact disc, and embedded multimedia card (EMMC).

[0039] The communication circuit (205) may include hardware components for supporting transmission and / or reception of signals between the wearable device (100) and an external electronic device. The communication circuit (205) may include, for example, at least one of a modem, an antenna, and an optical / electronic (O / E) converter. The communication circuit (205) may support transmission and / or reception of signals based on various types of protocols, such as Ethernet, a local area network (LAN), a wide area network (WAN), wireless fidelity (WiFi), Bluetooth, Bluetooth low energy (BLE), zigbee, long term evolution (LTE), and 5G new radio (NR).

[0040] The display assembly (208) can output visualized information. For example, the display assembly (208) can output visualized information to the user under the control of at least one processor (207). The display assembly (208) can include hardware components of the wearable device (100) used to display a screen. For example, the display assembly (208) can include light-emitting elements and circuits (e.g., transistors) that control the light-emitting elements to emit light. For example, each of the light-emitting elements can include an organic light emitting diode (OLED) or a micro LED. However, the present invention is not limited thereto. For example, the display assembly (208) can include a liquid crystal display (LCD).

[0041] As a non-limiting example, the display assembly (208) may include a first display positioned in front of the left eye of a user wearing the wearable device (100) and a second display positioned in front of the right eye of the user wearing the wearable device (100). For example, first content provided through a screen displayed through the first display may be (substantially) identical to second content provided through a screen displayed through the second display. While the first content and the second content are identical, the screen displayed through the second display may have a disparity with respect to the screen displayed through the first display. For example, the disparity may cause the display assembly (208) to present content (e.g., corresponding to the first content and the second content) in three dimensions.

[0042] The one or more first cameras (209) may include one or more optical sensors (e.g., a charged coupled device (CCD) sensor, a complementary metal oxide semiconductor (CMOS) sensor) that generate an electrical signal representing the color and / or brightness of light. For example, the one or more first cameras (209) may be described as one or more image sensors. For example, each of the one or more first cameras (209) may be available to acquire an image of the environment surrounding the wearable device (100). For example, at least some of the one or more first cameras (209) may have a field of view (FOV) that corresponds to a field of view (FOV) of a user's eye. For example, the FOV of a part of the one or more first cameras (209) may be different from the FOV of another part of the one or more first cameras (209). For example, one or more first cameras (209) may be used to identify input means positioned around the wearable device (100).

[0043] One or more second cameras (210) may be referred to in the description of one or more first cameras (209).

[0044] One or more third cameras (211) may be referred to in the description of one or more first cameras (209).

[0045] One or more microphones (212) may be configured to capture audio generated by a user (130). For example, the one or more microphones (212) may be used to capture a voice signal. For example, the voice signal may be used to generate a mouth shape of an avatar (e.g., avatar (420) of FIG. 4).

[0046] The temperature detection sensor (213) can obtain temperature data regarding the temperature of the wearable device (100). For example, the temperature detection sensor (213) can be used to identify whether the temperature value of the wearable device (100) reaches a threshold temperature value.

[0047] A power management integrated circuit (214) can manage power supplied to a wearable device (100). The power management integrated circuit (214) can be connected to a rechargeable battery (215). For example, the power management integrated circuit (214) can obtain information about the SoC of the rechargeable battery (215). For example, the power management integrated circuit (214) can be used by at least one processor (207) to identify whether the SoC of the rechargeable battery (215) reaches a threshold SoC.

[0048] A rechargeable battery (215) may power at least one component of the wearable device (100). For example, the rechargeable battery (215) may include a rechargeable secondary battery. For example, the rechargeable battery (215) may be integrally disposed within the wearable device (100). For example, the rechargeable battery (215) may be used by at least one processor (207) to identify whether the state of charge (SoC) of the rechargeable battery (215) reaches a threshold SoC.

[0049] FIG. 3 is a flowchart illustrating an exemplary method for stopping data generation for displaying an avatar. This method may be executed by the wearable device (100) illustrated in FIG. 2 or by at least one processor (207) of the wearable device (100).

[0050] Referring to FIG. 3, in operation 310, at least one processor (207) may generate first data for expressing an expression of an avatar (e.g., an avatar (420) of FIG. 4) corresponding to a user (130) using first images acquired through one or more first cameras (209). At least one processor (207) may generate second data for expressing a gaze of an avatar (e.g., an avatar (420) of FIG. 4) corresponding to a user (130) using second images acquired through one or more second cameras (210). At least one processor (207) may generate third data for expressing a shape of a mouth of the avatar using audio signals acquired through one or more microphones (212). At least one processor (207) may display the avatar through the display assembly (208) based on generating the first data, generating the second data, and generating the third data. For example, the first data may be generated by identifying the facial expression of the user (130) using first images acquired through one or more first cameras (209). For example, the second data may be generated by identifying the direction of the gaze of the user (130) using second images acquired through one or more second cameras (210). For example, the third data may be generated by estimating the shape of the mouth of the user (130) using audio signals acquired through one or more microphones (212). For example, face tracking may be used to generate the first data. For example, face tracking may include detecting the facial expression of the user (130) using one or more first cameras (209). For example, eye tracking may be used to generate the second data.For example, eye tracking may include detecting the gaze of a user (130) using one or more secondary cameras (210). For example, a microphone lip-sync solution may be used to generate third data. For example, the microphone lip-sync solution may include estimating the shape of the user's (130) mouth and estimating the user's (130) gestures using one or more microphones (212).

[0051] According to one embodiment, the wearable device (100) may include one or more microphones (212). At least one processor (207) may generate third data for expressing the shape of the mouth of an avatar (e.g., an avatar (420) of FIG. 4) using the one or more microphones (212). The at least one processor (207) may generate the third data for expressing the shape of the mouth of the avatar using audio signals acquired through the one or more microphones (212). However, the present invention is not limited thereto. For example, the at least one processor (207) may generate sixth data for expressing the movement of the avatar using audio signals acquired through the one or more microphones (212). For example, the at least one processor (207) may identify information within the audio signals. For example, the at least one processor (207) may generate the sixth data for expressing the movement of the avatar in response to the identified information. For example, the sixth data may be generated by estimating a gesture of the user (130) using audio signals acquired through one or more microphones (212).

[0052] According to one embodiment, at least one processor (207) can use the first data, the second data, and the third data to display an avatar (e.g., an avatar (420) of FIG. 4) through a display assembly (208). For example, since the first data is data regarding an expression of the avatar, the at least one processor (207) can use the first data and the second data to display the avatar through the display assembly (208).

[0053] In operation 320, at least one processor (207) may identify an event that causes a change in a manner for displaying the avatar (e.g., the avatar (420) of FIG. 4) while the avatar is being displayed based on generating the first data, generating the second data, and generating the third data. The event may include receiving a user input to stop one or more of expressing a facial expression of the avatar (420), expressing a gaze of the avatar (420), and expressing a shape of a mouth of the avatar (420). The event may include receiving a user input to authorize generating the third data among generating the first data, generating the second data, and generating the third data. The event may include the user (130) not wearing the wearable device (100).

[0054] According to one embodiment, the wearable device (100) may include a temperature detection sensor (213). The event may include obtaining a temperature value of the wearable device (100) exceeding a threshold temperature value from the temperature detection sensor (213). For example, the temperature value may be a temperature value of the wearable device (100). For example, the temperature value of the wearable device (100) may increase by generating data to display an avatar (420). At least one processor (207) may generate data to display the avatar (420) by consuming power. The temperature value of at least one processor (207) may increase by generating data to display the avatar (420).

[0055] In one embodiment, the wearable device (100) may include a power management integrated circuit (214). The wearable device (100) may include a rechargeable battery (215). The event may include obtaining data about the SoC below a threshold SoC from the power management integrated circuit (214). For example, the power management integrated circuit (214) may identify the SoC of the rechargeable battery (215). For example, the SoC of the wearable device (100) may be changed by generating data to display an avatar (420). At least one processor (207) may generate data to display the avatar (420) by consuming power. The SoC of the wearable device (100) may be lowered by generating data to display the avatar (420).

[0056] In one embodiment, at least one processor (207) may include one or more first cameras (209). At least one processor (207) may include one or more second cameras (210). At least one processor (207) may include one or more third cameras (211). For example, at least one processor (207) may fail to generate first data for representing an expression of an avatar (420) using first images acquired through one or more first cameras (209). For example, at least one processor (207) may fail to generate second data for representing a gaze of an avatar (420) using second images acquired through one or more second cameras (210). For example, at least one processor (207) may fail to generate fourth data for representing an arm of an avatar (420) using third images acquired through one or more third cameras (211).

[0057] In one embodiment, at least one processor (207) may fail to detect the gaze of the user (130). For example, at least one processor (207) may fail to detect the facial expression of the user (130). For example, at least one processor (207) may fail to detect the arm of the user (130). For example, the detection failure may be caused by external lighting. For example, the at least one processor (207) may fail to detect a part of the body of the user (130) because the illuminance associated with one or more of the first cameras (209), one or more of the second cameras (210), and one or more of the third cameras (211) exceeds a threshold illuminance. For example, the part of the body of the user (130) may be the eye of the user (130). For example, the part of the body of the user (130) may be the coil of the user (130). For example, a part of the user's (130) body may be the user's (130) mouth. For example, a part of the user's (130) body may be the user's (130) arm. For example, a part of the user's (130) body may be the user's (130) leg. While the above detection failure is described, it is merely exemplary. At least one processor (207) may fail to detect a part of the user's (130) body, thereby failing to generate data for representing the avatar (420). At least one processor (207) may stop generating data for representing the avatar (420) by failing to detect a part of the user's (130) body.

[0058] According to one embodiment, the wearable device (100) may be a device available for generating data for displaying an avatar (420). For example, at least one processor (207) may be used for generating the data. For example, the usage rate of the at least one processor (207) may be the usage rate of a CPU. For example, the usage rate of the at least one processor (207) may be the usage rate of a GPU. The usage rate of the at least one processor (207) may vary depending on the data for displaying the avatar (420). For example, when generating data for expressing the gaze of the avatar (420), the usage rate of the at least one processor (207) may be higher than the usage rate of the at least one processor (207) when not generating data for expressing the gaze of the avatar (420). For example, when generating first data for expressing the facial expression of an avatar (420), the usage rate of at least one processor (207) may be lower than the usage rate of at least one processor (207) when generating first data for expressing the facial expression of an avatar (420) and second data for expressing the gaze of an avatar (420).

[0059] In one embodiment, at least one processor (207) can change the operating state of the cameras. For example, at least one processor (207) can change the operating state of the cameras in response to the event. For example, the cameras can be one or more first cameras (209). For example, the cameras can be one or more second cameras (210). For example, the cameras can be one or more third cameras (211). For example, at least one processor (207) can change the frames per second (fps) of one or more first cameras (209). For example, at least one processor (207) can change the fps of one or more first cameras (209) from 30 to 10. For example, at least one processor (207) can change the fps of one or more second cameras (210) from 30 to 10. For example, at least one processor (207) can change the fps of one or more third cameras (211) from 30 to 10. Although the changing fps of the cameras is described, this is only exemplary. For example, at least one processor (207) can cut off power supplied to one or more first cameras (209). For example, at least one processor (207) can cut off power supplied to one or more second cameras (210). For example, at least one processor (207) can cut off power supplied to one or more third cameras (211). The wearable device (100) can induce a temperature value of the wearable device (100) to be below a threshold temperature value by changing the operating states of the cameras. The wearable device (100) can reduce a rate of decrease of the SoC of the wearable device (100) by changing the operating states of the cameras.The wearable device (100) can reduce the utilization of at least one processor (207) by changing the operating state of the cameras. While power cutoff to the cameras is described, this is merely exemplary. For example, at least one processor (207) can cut power to one or more microphones (212) in response to the event.

[0060] According to one embodiment, at least one processor (207) may further generate fifth data for representing a part of the avatar by using information about the movement of the control device (180) received from the control device (180) through the communication circuit (205) for controlling a part of the avatar (e.g., the avatar (420) of FIG. 4), so as to display the avatar through the display assembly. For example, the wearable device (100) may receive information about the movement of the control device (180) through the communication circuit (205). For example, the wearable device (100) may receive information about the movement of the control device (190) through the communication circuit (205). The information may include information about the position of the control device (180). The information may include information about the rotation of the control device (180). At least one processor (207) may generate fifth data for representing a portion of the avatar using information about the movement of the control device (180). At least one processor (207) may generate fourth data for representing an arm of the avatar using images of the arm of the user (130) acquired through one or more third cameras (211). The generation of the fourth data for representing the arm of the avatar is described and exemplified in more detail with reference to FIG. 4.

[0061] Figure 4 illustrates an example of generating data to display an avatar using a camera.

[0062] Referring to FIG. 4, the wearable device (100) may further include one or more third cameras (211) configured to acquire images of an arm of a user (130) wearing the wearable device (100). At least one processor (207) may further generate fourth data for representing the arm of the avatar using the third images acquired through the one or more third cameras. Based on the further generation of the fourth data, the at least one processor (207) may display the avatar (420) through the display assembly (208).

[0063] State (410) can be described as a state in which the avatar (420) makes the same gesture as the user's (130). For example, when the user (130) makes a gesture of drawing a V with his hand, at least one processor (207) can display the avatar (420) making the gesture of drawing a V with his hand through the display assembly (208).

[0064] According to one embodiment, at least one processor (207) may obtain or be provided with information about a three-dimensional (3D) space in which an avatar (420) is located from a composite layer (e.g., a composite layer (640) of FIG. 6). For example, at least one processor (207) may provide an avatar (420) through a display assembly (208) using the first data and the information about the 3D space provided from the composite layer (e.g., a composite layer (640) of FIG. 6). However, the present invention is not limited thereto. For example, at least one processor (207) may obtain or be provided with information about a background expressed in two dimensions from the composite layer.

[0065] At least one processor (207) may use animation data for pre-stored animation to display an avatar (420) through a display assembly (208). For example, at least one processor (207) may use pre-stored animation data to display an avatar (420) through a display assembly (208). Displaying an avatar (420) using the pre-stored animation data is described and exemplified in more detail with reference to FIG. 5.

[0066] Figure 5 illustrates an example of displaying an avatar using pre-saved animation data.

[0067] Referring to FIG. 5, at least one processor (207) may display an avatar (420) using animation data pre-stored in the memory (206). For example, the animation data pre-stored in the memory (206) may include data on the gaze, facial expression, and movement of the avatar (420). For example, a state (510) may be described as a state in which the gaze of the avatar (420) is expressed using pre-stored animation data. For example, at least one processor (207) may display the gaze of the avatar (420) through the display assembly (208) using animation data pre-stored in the memory (206). For example, a state (520) may be described as a state in which the facial expression of the avatar (420) is expressed using pre-stored animation data. For example, at least one processor (207) may display the facial expression of the avatar (420) through the display assembly (208) using animation data pre-stored in the memory (206). For example, the state (530) can be described as a state in which the movement of the avatar (420) is expressed using pre-stored animation data. For example, at least one processor (207) can display the movement of the avatar (420) through the display assembly (208) using the animation data pre-stored in the memory (206). For example, at least one processor (207) can display the avatar (420) using first data for expressing the facial expression of the avatar (420), second data for expressing the gaze of the avatar (420), third data for expressing the shape of the mouth of the avatar (420), and the animation data pre-stored in the memory (206). Although the animation data pre-stored in the memory (206) is described with reference to FIG. 5, this is merely exemplary.

[0068] At least one processor (207) may generate data to display an avatar (420). At least one processor (207) may stop generating data to display an avatar (420). The generation of data to display an avatar (420) or the stopping of generating data to display an avatar (420) is described and exemplified in more detail with reference to FIG. 6.

[0069] Figure 6 illustrates an example of a device for displaying an avatar.

[0070] Referring to FIG. 6, the wearable device (100) may include a resource manager (610) to display an avatar (420). The wearable device (100) may include a rendering configuration (620). The wearable device (100) may include a provider configuration (630). The wearable device (100) may include a composite layer (640). The wearable device (100) may include a pre-stored animation module (650). The wearable device (100) may include a pre-generated object module (660). The wearable device (100) may include a lip sync module (670). The wearable device (100) may include a tracking module (680). The wearable device (100) may include an interface avatar provider (690). The wearable device (100) may include a rendering thread (692). The wearable device (100) may include an interface stream (694).

[0071] The resource manager (610) may determine data for displaying the avatar (420) in response to identifying an event that causes a change in the method for displaying the avatar (420). For example, the resource manager (610) may identify the event. For example, the resource manager (610) may determine a priority for the data for displaying the avatar (420). For example, the resource manager (610) may change the priority of the data for displaying the avatar (420) based on the occurrence of the event. For example, the priority of the first data for expressing the facial expression of the avatar (420) may be higher than the priority of the animation data pre-stored in the memory (206).

[0072] The rendering configuration (620) can store information for rendering. The rendering configuration (620) can transmit the information to the provider configuration (630). For example, the information can include information about one or more first cameras (209), one or more second cameras (210), and one or more third cameras (211). For example, the information can include information about luminous intensity associated with the cameras. The rendering configuration (620) can provide the resource manager (610) with information for determining the priority. For example, the information can include information about the event. For example, the information can include information about the temperature value of the wearable device (100). For example, the information can include data about the state of charge (SoC) of the wearable device (100). For example, the information can include data about a user input.

[0073] The provider configuration (630) may include a user interface (UI) module that allows the user (130) to select an avatar (420). The provider configuration (630) may include a module that includes information about the avatar (420). For example, the information about the avatar (420) may include information about the personalized wearable device (100). For example, the information about the personalized wearable device (100) may include information about a camera included in the wearable device (100) and information about the shape of the avatar (420). For example, the provider configuration (630) may transmit the information about the avatar (420) to an interface avatar provider (690).

[0074] The composite layer (640) may include layer information about the surroundings of the avatar (420). For example, the composite layer (640) may transmit information about a space in which the avatar (420) is contained in a 3D (three-dimensional) environment to the interface avatar provider (690). The information about the space may be used to provide the avatar (420) through the display assembly (208).

[0075] The pre-stored animation module (650) may include pre-stored animation data in the memory (206). The pre-stored animation module (650) may receive animation data from the server via the communication circuit (205). For example, the pre-stored animation module (650) may be connected to a server (not shown) via a Bluetooth communication technique. For example, the pre-stored animation module (650) may be connected to the server via a Wi-Fi communication technique. The pre-stored animation module (650) may provide animation data to the resource manager (610).

[0076] The pre-created object module (660) may include data about the pre-created object. The pre-created object module (660) may be connected to a server (not shown) via a Bluetooth communication technique. The pre-created object module (660) may be connected to the server via a Wi-Fi communication technique. The pre-created object module (660) may receive data about the object from the server via a communication circuit (205). The pre-created object module (660) may provide data about the object to the resource manager (610).

[0077] According to one embodiment, the lip sync module (670) may generate third data for expressing the shape of the mouth of the avatar (420) using audio signals acquired through one or more microphones (212). The lip sync module (670) may generate sixth data for expressing the movement of the avatar (420) using audio signals acquired through one or more microphones (212). The lip sync module (670) may provide the resource manager (610) with the third data for expressing the shape of the mouth of the avatar (420) and the sixth data for expressing the movement of the avatar (420).

[0078] According to one embodiment, the tracking module (680) may generate first data for expressing an expression of the avatar (420) using first images acquired through one or more first cameras (209). The tracking module (680) may generate second data for expressing a gaze of the avatar (420) using second images acquired through one or more second cameras (210). The tracking module (680) may generate fourth data for expressing an arm of the avatar (420) using third images acquired through one or more third cameras (211). The tracking module (680) may provide the first data for expressing an expression of the avatar (420), the second data for expressing the gaze of the avatar (420), and the fourth data for expressing an arm of the avatar (420) to the resource manager (610).

[0079] The interface avatar provider (690) may provide an interface related to the avatar (420). For example, the interface avatar provider (690) may receive user input by providing the interface. For example, at least one processor (207) may display the interface on the display assembly (208) using the interface avatar provider (690).

[0080] The rendering thread (692) may receive data for displaying the avatar (420) from the resource manager (610). The data may include at least one of the first data, the second data, the third data, the fourth data, the fifth data, the sixth data, and the animation data. The rendering thread (692) may render an image using the data provided from the resource manager (610). For example, the image may include an image of the avatar (420).

[0081] An interface stream (694) can transmit a rendered image to a hardware abstraction layer (HAL) using a surface or buffer. The HAL may include a HAL for a virtual camera.

[0082] Figure 7 illustrates an example of identifying priorities corresponding to events.

[0083] Referring to FIG. 7, at least one processor (207) can determine priorities of first data (710), second data (720), third data (730), fourth data (740), and animation data (750). The resource manager (610) can be provided with the first data (710), second data (720), third data (730), fourth data (740), and animation data (750). For example, at least one processor (207) can include the resource manager (610). The resource manager (610) can determine data having a higher priority among the first data (710), second data (720), third data (730), fourth data (740), and animation data (750). The resource manager (610) can determine data with a lower priority among the first data (710), the second data (720), the third data (730), the fourth data (740), and the animation data (750). For example, the resource manager (610) can identify a priority corresponding to an event that causes a change in the method for displaying the avatar (420). For example, at least one processor (207) can identify priorities differently depending on the type of the event. The resource manager (610) can select at least one of the first data (710), the second data (720), the third data (730), the fourth data (740), and the animation data (750) based on the identified priorities. The resource manager (610) can provide the selected at least one to the rendering thread (692). The rendering thread (692) can render the avatar (420) using the provided at least one. For example, the wearable device (100) can efficiently use resources by identifying priorities. For example, the wearable device (100) can reduce the amount of power required to display an avatar (420) by identifying priorities.For example, in the event that the temperature value of the wearable device (100) exceeds a threshold temperature value, the priority of the animation data (750) may be higher than the priority of the first data (710). For example, if the wearable device (100) receives a user input indicating that it bypasses generating the first data (710), the priority of the animation data (750) may be higher than the priority of the first data (710).

[0084] Referring back to FIG. 3, at operation 330, at least one processor (207) may, in response to the event, stop one or more of generating the first data (710) to display the avatar, generating the second data (720) to display the avatar, and generating the third data (730) to display the avatar. For example, at least one processor (207) may, in response to the event, stop at least one of generating the first data (710) to display the avatar, generating the second data (720) to display the avatar, and generating the third data (730) to display the avatar. However, the present invention is not limited thereto. At least one processor (207) may stop generating the fourth data (740), the fifth data, and / or the sixth data.

[0085] In one embodiment, at least one processor (207) can, in response to the event, stop at least one of generating the first data (710) to display the avatar, generating the second data (720) to display the avatar, and generating the third data (730) to display the avatar. At least one processor (207) can, in response to the event, stop at least one of generating the first data (710) to display the avatar, generating the second data (720) to display the avatar, and generating the third data (730) to display the avatar by identifying a priority corresponding to the event.

[0086] For example, at least one processor (207) may stop generating first data (710) for expressing an expression of the avatar (420) in response to the event. For example, at least one processor (207) may stop generating second data (720) for expressing an eye gaze of the avatar (420) in response to the event. For example, at least one processor (207) may stop generating third data (730) for expressing a shape of a mouth of the avatar (420) in response to the event. For example, at least one processor (207) may stop generating fourth data (740) for expressing an arm of the avatar (420) using third images acquired through one or more third cameras in response to the event. For example, at least one processor (207) may stop generating fifth data for representing a portion of the avatar (420) using information about movement of the control device received from the control device (180) via the communication circuit (205) in response to the event.

[0087] At least one processor (207) may display the avatar (420) using animation data pre-stored in the memory (206) based on stopping at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar (420), and generating the third data (730) to display the avatar (420). For example, at least one processor (207) may display the gaze of the avatar (420) using animation data pre-stored in the memory (206). At least one processor (207) may display the facial expression of the avatar (420) using animation data pre-stored in the memory (206). At least one processor (207) may display the movement of the avatar (420) using animation data pre-stored in the memory (206).

[0088] According to one embodiment, at least one processor (207) may identify a priority corresponding to the event among generating first data (710), generating second data (720), and generating third data (730), in response to the event. Based on the identified priority, the at least one processor (207) may determine at least one of the first data (710), the second data (720), and the third data (730) as data for displaying the avatar (420). For example, the at least one processor (207) may use data with a higher priority to display the avatar (420) based on the determined priority. For example, the at least one processor (207) may identify that the priority of the first data (710) is higher than the priority of the second data (720). For example, at least one processor (207) may refrain from or skip displaying the avatar (420) using the second data (720) while displaying the avatar (420) using the first data (710). However, the present invention is not limited thereto. At least one processor (207) may identify that the priority of the second data (720) is higher than the priority of the first data (710). For example, based on the identified priority, the at least one processor (207) may determine at least one of the first data (710), the second data (720), the third data (730), the fourth data (740), the fifth data, the sixth data, and the animation data (750) as data for displaying the avatar (420). For example, the at least one processor (207) may stop generating data with a lower priority. However, the present invention is not limited thereto.At least one processor (207) can display the avatar (420) using data having a higher priority among the first data (710), the second data (720), the third data (730), the fourth data (740), the fifth data, the sixth data, and the animation data (750). For example, at least one processor (207) can refrain from or skip displaying the avatar (420) using data having a lower priority among the first data (710), the second data (720), the third data (730), the fourth data (740), the fifth data, the sixth data, and the animation data (750). For example, at least one processor (207) can stop generating the data having the lower priority. For example, at least one processor (207) may stop generating the data based on determining which data has a lower priority among the first data (710), the second data (720), the third data (730), the fourth data (740), the fifth data, the sixth data, and the animation data (750). For example, at least one processor (207) may stop generating at least one of the first data (710), the second data (720), the third data (730), the fourth data (740), the fifth data, and the sixth data based on identifying a priority corresponding to an event.

[0089] According to one embodiment, at least one processor (207) can generate data for displaying an avatar (420) by identifying data having a high priority among the first data (710), the second data (720), the third data (730), the fourth data (740), the fifth data, the sixth data, and the animation data (750). For example, when the first data (710) and the animation data (750) are identified as high priority data, the at least one processor (207) can generate data for displaying an avatar (420) using the first data (710) and the animation data (750). The at least one processor (207) can display the avatar (420) on the display assembly (208) using the generated data.

[0090] At least one processor (207) can manage the wearable device (100) by stopping data generation. For example, the at least one processor (207) can manage resources by stopping data generation. For example, the resources may be resources for hardware components of the wearable device (100). For example, the resources may include power. For example, the resources may include usage of the at least one processor (207). For example, the resources may include utilization of the at least one processor (207). For example, the at least one processor (207) can reduce the amount of power consumed for data generation by stopping data generation. For example, the at least one processor (207) can reduce power consumption of hardware components by stopping data generation. For example, the hardware component may be a CPU. For example, the hardware component may be a GPU. For example, the hardware component may be one or more first cameras (209). For example, the hardware component may be one or more second cameras (210). The hardware component is described, but is only exemplary. For example, at least one processor (207) may keep the temperature value of the wearable device (100) below a threshold temperature value by stopping the generation of data. For example, at least one processor (207) may manage the SoC of the wearable device (100) by stopping the generation of data. At least one processor (207) may display an avatar (420) using the resources. At least one processor (207) may display the avatar (420) in various ways. At least one processor (207) may determine a method for displaying the avatar (420) among various ways based on an event.At least one processor (207) can efficiently use the resources by displaying an avatar based on the event.

[0091] At least one processor (207) may display the avatar (420) using animation data stored in the memory (206) based on stopping one or more of generating the first data (710), generating the second data (720), and generating the third data (730). Displaying the avatar (420) using animation data stored in the memory (206) is described and illustrated in more detail with reference to FIGS. 8A to 8C.

[0092] Figure 8a illustrates an example where generating data for representing the avatar's gaze is stopped.

[0093] Referring to FIG. 8A, a state (810) may be described as a state in which an avatar (420) is displayed using second data (720) for expressing the gaze of the avatar (420). An area (815) may be described as an area corresponding to the eyes of the avatar (420). The area (815) may be displayed through the display assembly (208) using second data (720) generated using second images acquired through one or more second cameras (210). For example, one or more second cameras (210) may capture the eyes of the user (130). For example, at least one processor (207) may display the eyes of the avatar (420) through the display assembly (208) using the image of the eyes of the user (130).

[0094] In one embodiment, state (820) may be described as a state in which generating the second data (720) in response to the event is stopped. At least one processor (207) may display the gaze of the avatar (420) using other data as generating the second data (720) is stopped. For example, at least one processor (207) may display the gaze of the avatar (420) using animation data pre-stored in the memory (206) based on the stop in generating the second data (720). Since at least one processor (207) does not display the avatar (420) using the second data (720), the gaze direction of the avatar (420) may be different from the gaze direction of the user (130). For example, while the user (130) is looking to the right, the avatar (420) may be looking straight ahead.

[0095] Figure 8b illustrates an example in which the generation of data for expressing the avatar's facial expression is stopped.

[0096] Referring to FIG. 8B, the state (830) may be described as a state in which the avatar (420) is displayed using the first data (710) for expressing the facial expression of the avatar (420). The region (835) may be described as a region corresponding to the face of the avatar (420). The region (835) may be displayed through the display assembly (208) by using the first data (710) generated using the first images acquired through one or more first cameras (209). For example, one or more first cameras (209) may capture the face of the user (130). For example, at least one processor (207) may display the facial expression of the avatar (420) through the display assembly (208) using the image of the face of the user (130).

[0097] State (840) can be described as a state in which generating the first data (710) in response to the event is stopped. At least one processor (207) may display the facial expression of the avatar (420) using other data as generating the first data (710) is stopped. For example, at least one processor (207) may display the facial expression of the avatar (420) using animation data pre-stored in the memory (206) based on the stopping of generating the first data (710). Since at least one processor (207) does not display the avatar (420) using the first data (710), the facial expression of the avatar (420) may be different from the facial expression of the user (130). For example, while the user (130) is smiling, the avatar (420) may not be smiling.

[0098] At least one processor (207) may display the shape of the mouth of the avatar (420) using audio signals acquired through one or more microphones (212) based on the cessation of generating the first data (710). For example, the at least one processor (207) may identify the audio signals. For example, the at least one processor (207) may determine the shape of the mouth of the user (130) using audio signals acquired through one or more microphones (212). For example, the at least one processor (207) may display the shape of the mouth of the avatar (420) as a shape corresponding to the determined shape of the mouth of the user (130).

[0099] Figure 8c illustrates an example where generating data to represent a part of an avatar is stopped.

[0100] Referring to FIG. 8C, a state (850) can be described as a state in which an avatar (420) is displayed using data for expressing the movement of the avatar (420). For example, at least one processor (207) can display the movement of the avatar (420) through the display assembly (208) using the control device (180). For example, at least one processor (207) can display the movement of the avatar (420) through the display assembly (208) using the control device (190). For example, at least one processor (207) can display the arm of the avatar (420) through the display assembly (208) using third images acquired through one or more third cameras (211).

[0101] State (860) may be described as a state in which generating data about the movement of the avatar (420) in response to the event is stopped. For example, the movement of the avatar (420) may include movement of an arm of the avatar (420). At least one processor (207) may display the movement of the avatar (420) using audio signals acquired through one or more microphones (212) based on the stopping of generating data about the movement of the avatar (420). For example, at least one processor (207) may display the movement of the avatar (420) corresponding to the audio signal through the display assembly (208).

[0102] At least one processor (207) may display the movement of the avatar (420) using other data as the data for the movement of the avatar (420) is stopped. For example, at least one processor (207) may display the movement of the avatar (420) using animation data pre-stored in the memory (206) based on the stop of generating the data for the movement of the avatar (420). For example, since the at least one processor (207) does not display the avatar (420) using third images acquired through one or more third cameras (211), the movement of the avatar (420) may be different from the movement of the user (130). For example, since the at least one processor (207) does not display the avatar (420) using information about the movement of the control device received from the control device (180), the movement of the avatar (420) may be different from the movement of the user (130). For example, while the user (130) assumes a pose with both arms raised to shoulder level, the avatar (420) may assume a basic pose. For example, the basic pose may be the A pose. For example, the basic pose may be a pose with both arms attached to the legs.

[0103] At least one processor (207) may resume generation of data that was interrupted in response to identifying another event that causes a change in the manner in which the avatar (420) is displayed. The resumption of generation is described and exemplified in more detail with reference to FIGS. 9 and 10.

[0104] FIG. 9 is a flowchart illustrating an exemplary method for resuming data generation for displaying an avatar. This method may be executed by the wearable device (100) illustrated in FIG. 9 or by at least one processor (207) of the wearable device (100).

[0105] Referring to FIG. 9, in operation 910, at least one processor (207) may identify another event that causes a change in the manner of displaying the avatar while stopping one or more of generating the first data (710) for displaying the avatar, generating the second data (720) for displaying the avatar, and generating the third data (730) for displaying the avatar. The other event may include receiving a user input to resume one or more of expressing a facial expression of the avatar (420), expressing a gaze of the avatar (420), and expressing a shape of a mouth of the avatar (420). For example, the other event may include obtaining data from the power management integrated circuit (214) regarding the SoC exceeding a threshold SoC. For example, the SoC of a rechargeable battery (215) may be changed by charging the rechargeable battery. For example, the SoC of the rechargeable battery (215) may increase as the rechargeable battery (215) is supplied with power. For example, the other event may include, after the at least one processor (207) fails to generate data to display the avatar (420) using images acquired through the one or more first cameras (209), the at least one processor (207) generates data to display the avatar (420) using images acquired through the one or more first cameras (209).For example, the other event may include generating data for displaying an avatar (420) using images acquired through one or more second cameras (210) after at least one processor (207) fails to generate data for displaying an avatar (420) using images acquired through one or more second cameras (210). For example, the other event may include successfully generating the first data (710) using the first images when generating the first data (710) is interrupted by stopping one or more of generating the first data (710) for displaying the avatar, generating the second data (720) for displaying the avatar, and generating the third data (730) for displaying the avatar. For example, the other event may include successfully generating the second data (720) using the second images when generating the second data (720) is stopped by stopping one or more of generating the first data (710) for displaying the avatar, generating the second data (720) for displaying the avatar, and generating the third data (730) for displaying the avatar. For example, the other event may include a utilization rate of at least one processor (207) being below a threshold utilization rate. Other events that cause a change in the method for displaying the avatar are described, but are by way of example only.

[0106] Figure 10 illustrates another example of an event that obtains a temperature value of a wearable device below a threshold temperature value.

[0107] Referring to FIG. 10, the other event may include obtaining a temperature value of the wearable device below a threshold temperature value from a temperature detection sensor (213). A state (1010) may be described as a state in which a temperature value (1012) of the wearable device (100) exceeds a threshold temperature value (1014). At least one processor (207) may lower the temperature value (1012) of the wearable device (100) by cutting off power supplied to at least one of the one or more first cameras (209), the one or more second cameras (210), and the one or more third cameras (211).

[0108] State (1020) can be described as a state in which the temperature value (1030) of the wearable device (100) is lower than the threshold temperature value (1014). At least one processor (207) can, based on obtaining the temperature value (1030) of the wearable device (100) lower than the threshold temperature value (1014) from the temperature detection sensor (213), supply power again to the cameras that have been cut off from among one or more first cameras (209), one or more second cameras (210), and one or more third cameras (211). At least one processor (207) can, based on the supply of power, resume generating data to display the avatar (420).

[0109] Referring again to FIG. 9, at operation 920, at least one processor (207) may, in response to the other event, resume at least a portion of one or more of generating the first data (710) for displaying the avatar, generating the second data (720) for displaying the avatar, and generating the third data (730) for displaying the avatar. For example, at least one processor (207) may resume at least a portion of at least one of generating the first data (710) for displaying the avatar, generating the second data (720) for displaying the avatar, and generating the third data (730) for displaying the avatar where generation was interrupted. For example, at least one processor (207) may resume generating fourth data (740) for representing an arm of the avatar (420) using third images acquired through one or more third cameras (211). At least one processor (207) may resume generating fifth data for representing a part of the avatar (420) using information about the movement of the control device (180) received from the control device (180) via the communication circuit (205). At least one processor (207) may resume generating data for representing a part of the avatar using audio signals acquired via one or more microphones (212).

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

[0111] Referring to FIG. 11, in a network environment (1100), an electronic device (1101) may communicate with an electronic device (1102) via a first network (1198) (e.g., a short-range wireless communication network), or may communicate with at least one of an electronic device (1104) or a server (1108) via a second network (1199) (e.g., a long-range wireless communication network). In one embodiment, the electronic device (1101) may communicate with the electronic device (1104) via the server (1108). According to one embodiment, the electronic device (1101) may include a processor (1120), a memory (1130), an input module (1150), an audio output module (1155), a display module (1160), an audio module (1170), a sensor module (1176), an interface (1177), a connection terminal (1178), a haptic module (1179), a camera module (1180), a power management module (1188), a battery (1189), a communication module (1190), a subscriber identification module (1196), or an antenna module (1197). In some embodiments, the electronic device (1101) may omit at least one of these components (e.g., the connection terminal (1178)), or may have one or more other components added. In some embodiments, some of these components (e.g., sensor module (1176), camera module (1180), or antenna module (1197)) may be integrated into a single component (e.g., display module (1160)).

[0112] The processor (1120) may, for example, execute software (e.g., a program (1140)) to control at least one other component (e.g., a hardware or software component) of the electronic device (1101) connected to the processor (1120) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (1120) may store commands or data received from other components (e.g., a sensor module (1176) or a communication module (1190)) in a volatile memory (1132), process the commands or data stored in the volatile memory (1132), and store result data in a non-volatile memory (1134). According to one embodiment, the processor (1120) may include a main processor (1121) (e.g., a central processing unit or an application processor) or an auxiliary processor (1123) (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 with the main processor (1121). For example, when the electronic device (1101) includes the main processor (1121) and the auxiliary processor (1123), the auxiliary processor (1123) may be configured to use less power than the main processor (1121) or to be specialized for a given function. The auxiliary processor (1123) may be implemented separately from the main processor (1121) or as a part thereof.

[0113] The auxiliary processor (1123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (1160), a sensor module (1176), or a communication module (1190)) of the electronic device (1101), for example, on behalf of the main processor (1121) while the main processor (1121) is in an inactive (e.g., sleep) state, or together with the main processor (1121) while the main processor (1121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (1123) (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 (1180) or a communication module (1190)). In one embodiment, the auxiliary processor (1123) (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 (1101) itself where the artificial intelligence model is executed, or can be performed through a separate server (e.g., server (1108)). 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.

[0114] The memory (1130) can store various data used by at least one component (e.g., the processor (1120) or the sensor module (1176)) of the electronic device (1101). The data can include, for example, software (e.g., the program (1140)) and input data or output data for commands related thereto. The memory (1130) can include a volatile memory (1132) or a non-volatile memory (1134).

[0115] The program (1140) may be stored as software in memory (1130) and may include, for example, an operating system (1142), middleware (1144), or an application (1146).

[0116] The input module (1150) can receive commands or data to be used in a component of the electronic device (1101) (e.g., a processor (1120)) from an external source (e.g., a user) of the electronic device (1101). The input module (1150) 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).

[0117] The audio output module (1155) can output audio signals to the outside of the electronic device (1101). The audio output module (1155) 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.

[0118] The display module (1160) can visually provide information to an external party (e.g., a user) of the electronic device (1101). The display module (1160) 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 (1160) 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.

[0119] The audio module (1170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (1170) can acquire sound through the input module (1150), output sound through the sound output module (1155), or an external electronic device (e.g., electronic device (1102)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (1101).

[0120] The sensor module (1176) can detect the operating status (e.g., power or temperature) of the electronic device (1101) 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 (1176) 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.

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

[0122] The connection terminal (1178) may include a connector through which the electronic device (1101) may be physically connected to an external electronic device (e.g., the electronic device (1102)). In one embodiment, the connection terminal (1178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0123] The haptic module (1179) 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 (1179) may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

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

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

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

[0127] The communication module (1190) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (1101) and an external electronic device (e.g., electronic device (1102), electronic device (1104), or server (1108)), and the performance of communication through the established communication channel. The communication module (1190) may operate independently from the processor (1120) (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 (1190) may include a wireless communication module (1192) (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 (1194) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, a corresponding communication module can communicate with an external electronic device (1104) via a first network (1198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (1199) (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 (1192) can verify or authenticate the electronic device (1101) within a communication network such as the first network (1198) or the second network (1199) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (1196).

[0128] The wireless communication module (1192) 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 (1192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (1192) may 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 (1192) may support various requirements specified in the electronic device (1101), an external electronic device (e.g., the electronic device (1104)), or a network system (e.g., the second network (1199)). According to one embodiment, the wireless communication module (1192) may support a peak data rate (e.g., 20 Gbps or more) for eMBB implementation, a loss coverage (e.g., 164 dB or less) for mMTC implementation, 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 implementation.

[0129] The antenna module (1197) 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 (1197) 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 (1197) 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 (1198) or the second network (1199), may be selected from the plurality of antennas by, for example, the communication module (1190). A signal or power may be transmitted or received between the communication module (1190) and an external electronic device via 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 (1197).

[0130] According to various embodiments, the antenna module (1197) may form a mmWave antenna module. In 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.

[0131] 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)).

[0132] According to one embodiment, commands or data may be transmitted or received between the electronic device (1101) and an external electronic device (1104) via a server (1108) connected to a second network (1199). Each of the external electronic devices (1102 or 1104) may be the same or a different type of device as the electronic device (1101). According to one embodiment, all or part of the operations executed in the electronic device (1101) may be executed in one or more of the external electronic devices (1102, 1104, or 1108). For example, when the electronic device (1101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (1101) 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 (1101). The electronic device (1101) 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 (1101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (1104) may include an Internet of Things (IoT) device. The server (1108) may be an intelligent server utilizing machine learning and / or a neural network.According to one embodiment, an external electronic device (1104) or server (1108) may be included within the second network (1199). The electronic device (1101) may be applied to intelligent services (e.g., smart homes, smart cities, smart cars, or healthcare) based on 5G communication technology and IoT-related technology.

[0133] FIG. 12a illustrates an example of a perspective view of a wearable device. FIG. 12b illustrates an example of one or more hardware components arranged within the wearable device.

[0134] According to one embodiment, the wearable device (100) may have the form of glasses that are wearable on a body part of the user (e.g., the head). The wearable device (100) of FIGS. 12A and 12B may be an example of the wearable device (100) of FIG. 11. The wearable device (100) may include a head-mounted display (HMD). For example, the housing of the wearable device (100) 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 (100) 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.

[0135] Referring to FIG. 12A, according to one embodiment, a wearable device (100) may include at least one display (1250) and a frame (1200) supporting at least one display (1250).

[0136] According to one embodiment, the wearable device (100) can be worn on a part of a user's body. The wearable device (100) can provide augmented reality (AR), virtual reality (VR), or mixed reality (MR) that combines augmented reality and virtual reality to the user wearing the wearable device (100). For example, the wearable device (100) can display a virtual reality image provided from at least one optical device (1282, 1284) of FIG. 12B on at least one display (1250) in response to a user's designated gesture acquired through the motion recognition cameras (1260-2, 1260-3) of FIG. 12B.

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

[0138] Referring to FIG. 12B, at least one display (1250) 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 (1250). 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 (1250) can include a first surface (1231) and a second surface (1232) opposite to the first surface (1231). A display area can be formed on the second surface (1232) of the at least one display (1250). When the user wears the wearable device (100), external light can be transmitted to the user by being incident on the first surface (1231) and transmitted through the second surface (1232). As another example, at least one display (1250) can display an augmented reality image combined with a virtual reality image provided from at least one optical device (1282, 1284) on a real screen transmitted through external light, in a display area formed on the second surface (1232).

[0139] In one embodiment, at least one display (1250) may include at least one waveguide (1233, 1234) that diffracts light emitted from at least one optical device (1282, 1284) and transmits the diffracted light to a user. The at least one waveguide (1233, 1234) 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 (1233, 1234). 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 (1233, 1234) may be propagated to the other end of the at least one waveguide (1233, 1234) by the nano-pattern. At least one waveguide (1233, 1234) 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 (1233, 1234) may be arranged within the wearable device (100) to guide a screen displayed by at least one display (1250) 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 (1233, 1234).

[0140] The wearable device (100) can analyze an object included in a real image collected through a shooting camera (1260-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 (1250). 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 (100) can analyze the object based on a multi-camera such as a stereo camera. For the object analysis, the wearable device (100) 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 (100) can view an image displayed on at least one display (1250).

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

[0142] Referring to FIG. 12A, the frame (1200) may include a region (1220) that at least partially contacts a portion of the user's body when the user wears the wearable device (100). For example, the region (1220) of the frame (1200) that contacts a portion of the user's body may include a region that contacts 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 (100) makes contact with. According to one embodiment, the frame (1200) may include a nose pad (1210) that contacts a portion of the user's body. When the wearable device (100) is worn by the user, the nose pad (1210) may contact a portion of the user's nose. The frame (1200) may include a first temple (1204) and a second temple (1205) that contact another part of the user's body that is distinct from the part of the user's body.

[0143] For example, the frame (1200) may include a first rim (1201) that surrounds at least a portion of the first display (1250-1), a second rim (1202) that surrounds at least a portion of the second display (1250-2), a bridge (1203) that is disposed between the first rim (1201) and the second rim (1202), a first pad (1211) that is disposed along a portion of the edge of the first rim (1201) from one end of the bridge (1203), a second pad (1212) that is disposed along a portion of the edge of the second rim (1202) from the other end of the bridge (1203), a first temple (1204) that extends from the first rim (1201) and is fixed to a portion of the ear of the wearer, and a second temple (1205) that extends from the second rim (1202) and is fixed to a portion of the ear opposite the ear. There are. The first pad (1211) and the second pad (1212) can be in contact with a part of the user's nose, and the first temple (1204) and the second temple (1205) can be in contact with a part of the user's face and a part of the user's ear. The temples (1204, 1205) can be rotatably connected to the rim through the hinge units (1206, 1207) of FIG. 12B. The first temple (1204) can be rotatably connected to the first rim (1201) through the first hinge unit (1206) disposed between the first rim (1201) and the first temple (1204). The second temple (1205) may be rotatably connected to the second rim (1202) via a second hinge unit (1207) disposed between the second rim (1202) and the second temple (1205). In one embodiment, the wearable device (100) may use a touch sensor, a grip sensor, and / or a proximity sensor formed on at least a portion of a surface of the frame (1200) to identify an external object (e.g., a user's fingertip) touching the frame (1200) and / or a gesture performed by the external object.

[0144] According to one embodiment, the wearable device (100) may include hardwares that perform various functions (e.g., hardwares to be described later based on the block diagram of FIG. 14). For example, the hardwares may include a battery module (1270), an antenna module (1275), at least one optical device (1282, 1284), speakers (e.g., speakers 1255-1, 1255-2), a microphone (e.g., microphones 1265-1, 1265-2, 1265-3), a light-emitting module (not shown), and / or a printed circuit board (PCB) (1290) (e.g., a printed circuit board). The various hardwares may be arranged within the frame (1200).

[0145] According to one embodiment, microphones (e.g., microphones 1265-1, 1265-2, 1265-3) of the wearable device (100) may be disposed on at least a portion of the frame (1200) to acquire sound signals. A first microphone (1265-1) disposed on the bridge (1203), a second microphone (1265-2) disposed on the second rim (1202), and a third microphone (1265-3) disposed on the first rim (1201) are illustrated in FIG. 12B, but the number and arrangement of the microphones (1265) are not limited to the embodiment of FIG. 12B. When the number of microphones (1265) included in the wearable device (100) is two or more, the wearable device (100) can identify the direction of a sound signal by using a plurality of microphones placed on different parts of the frame (1200).

[0146] In one embodiment, at least one optical device (1282, 1284) may project a virtual object onto at least one display (1250) to provide various image information to a user. For example, at least one optical device (1282, 1284) may be a projector. At least one optical device (1282, 1284) may be disposed adjacent to at least one display (1250) or may be included within at least one display (1250) as a part of at least one display (1250). In one embodiment, the wearable device (100) may include a first optical device (1282) corresponding to a first display (1250-1) and a second optical device (1284) corresponding to a second display (1250-2). For example, at least one optical device (1282, 1284) may include a first optical device (1282) disposed at an edge of a first display (1250-1) and a second optical device (1284) disposed at an edge of a second display (1250-2). The first optical device (1282) may transmit light to a first waveguide (1233) disposed on the first display (1250-1), and the second optical device (1284) may transmit light to a second waveguide (1234) disposed on the second display (1250-2).

[0147] In one embodiment, the camera (1260) may include a recording camera (1260-4), an eye tracking camera (ET CAM) (1260-1), and / or a motion recognition camera (1260-2, 1260-3). The recording camera (1260-4), the eye tracking camera (1260-1), and the motion recognition cameras (1260-2, 1260-3) may be positioned at different locations on the frame (1200) and may perform different functions. The eye tracking camera (1260-1) may output data indicating the position or gaze of the eyes of a user wearing the wearable device (100). For example, the wearable device (100) may detect the gaze from an image including the user's pupils obtained through the eye tracking camera (1260-1). The wearable device (100) can identify an object (e.g., a real object and / or a virtual object) focused on by the user using the user's gaze acquired through the gaze tracking camera (1260-1). The wearable device (100) that has identified the focused object can execute a function (e.g., gaze interaction) for interaction between the user and the focused object. The wearable device (100) can express a part 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 (1260-1). The wearable device (100) can render an image (or screen) displayed on at least one display (1250) based on the position of the user's eyes. For example, the visual quality of a first region related to the gaze within the image and the visual quality (e.g., resolution, brightness, saturation, grayscale, PPI) of a second region distinguished from the first region may be different from each other.The wearable device (100) can obtain an image having a visual quality of a first area matching the user's gaze and a visual quality of a second area using foveated rendering. For example, if the wearable device (100) supports an iris recognition function, user authentication can be performed based on iris information obtained using a gaze tracking camera (1260-1). An example in which the gaze tracking camera (1260-1) is positioned toward the user's right eye is illustrated in FIG. 12B, but the embodiment is not limited thereto, and the gaze tracking camera (1260-1) can be positioned solely toward the user's left eye, or toward both eyes.

[0148] In one embodiment, the capturing camera (1260-4) can capture an actual image or background to be aligned with a virtual image to implement augmented reality or mixed reality content. The capturing camera (1260-4) can be used to obtain a high-resolution image based on HR (high resolution) or PV (photo video). The capturing camera (1260-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 (1250). The at least one display (1250) can display a single image in which information about an actual image or background including an image of the specific object obtained using the capturing camera (1260-4) and a virtual image provided through at least one optical device (1282, 1284) are superimposed. The wearable device (100) can compensate for depth information (e.g., the distance between the wearable device (100) and an external object acquired through a depth sensor) using an image acquired through the capture camera (1260-4). The wearable device (100) can perform object recognition using an image acquired using the capture camera (1260-4). The wearable device (100) can perform a function of focusing on an object (or subject) in an image (e.g., auto focus) and / or an optical image stabilization (OIS) function (e.g., anti-shake function) using the capture camera (1260-4). The wearable device (100) can perform a pass-through function to display an image acquired through the capture camera (1260-4) by overlapping at least a portion of a screen representing a virtual space on at least one display (1250) while displaying the screen. In one embodiment, the camera (1260-4) may be positioned on a bridge (1203) positioned between the first rim (1201) and the second rim (1202).

[0149] The gaze tracking camera (1260-1) can implement more realistic augmented reality by tracking the gaze of a user wearing the wearable device (100) and matching the user's gaze with visual information provided to at least one display (1250). For example, when the wearable device (100) looks straight ahead, the wearable device (100) can naturally display environmental information related to the user's front at a location where the user is located on at least one display (1250). The gaze tracking camera (1260-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 (1260-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 (1260-1) can be positioned at positions corresponding to the user's left and right eyes. For example, the gaze tracking camera (1260-1) may be positioned within the first rim (1201) and / or the second rim (1202) to face the direction in which the user wearing the wearable device (100) is positioned.

[0150] The gesture recognition camera (1260-2, 1260-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 (1250). The gesture recognition camera (1260-2, 1260-3) can recognize the user's gesture (gesture recognition), obtain a signal corresponding to the gesture, and provide a display corresponding to the signal on at least one display (1250). The processor can identify the signal corresponding to the gesture, and perform a designated function based on the identification. The gesture recognition camera (1260-2, 1260-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 processor may perform gesture recognition and / or object tracking functions using the motion recognition cameras (1260-2, 1260-3). In one embodiment, the motion recognition cameras (1260-2, 1260-3) may be positioned on the first rim (1201) and / or the second rim (1202).

[0151] The camera (1260) included in the wearable device (100) is not limited to the above-described gaze tracking camera (1260-1) and motion recognition cameras (1260-2, 1260-3). For example, the wearable device (100) can identify an external object included in the FoV using a camera positioned toward the user's FoV. The wearable device (100) can identify an external object based on a sensor for identifying the distance between the wearable device (100) and the external object, such as a depth sensor and / or a time of flight (ToF) sensor. The camera (1260) positioned toward the FoV can support an autofocus function and / or an optical image stabilization (OIS) function. For example, the wearable device (100) may include a camera (1260) (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 (100).

[0152] Although not shown, in one embodiment, the wearable device (100) 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 captured using the camera (1260). The light source may include an LED having an infrared wavelength. The light source may be disposed in at least one of the frame (1200) and the hinge units (1206, 1207).

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

[0154] The antenna module (1275) can transmit signals or power to the outside of the wearable device (100), or receive signals or power from the outside. In one embodiment, the antenna module (1275) can be positioned within the first temple (1204) and / or the second temple (1205). For example, the antenna module (1275) can be positioned close to one surface of the first temple (1204) and / or the second temple (1205).

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

[0156] 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 (100) to the user. For example, when the wearable device (100) 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 (1201) and / or the second rim (1202).

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

[0158] According to one embodiment, a wearable device (100) 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 (100) and / or a posture of a body part (e.g., a head) of a user wearing the wearable device (100). 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 (100) may identify a user's motion and / or gesture performed to execute or terminate a specific function of the wearable device (100) based on the IMU.

[0159] FIGS. 13A and 13B illustrate an example of an exterior appearance of a wearable device (e.g., a wearable device (100)). The wearable device (100) of FIGS. 13A and 13B may be an example of the wearable device (100) of FIG. 11. According to one embodiment, an example of an exterior appearance of a first side (1310) of a housing of a wearable device (100) is illustrated in FIG. 13A, and an example of an exterior appearance of a second side (1320) opposite to the first side (1310) may be illustrated in FIG. 13B.

[0160] Referring to FIG. 13A, a first surface (1310) of a wearable device (100) according to one embodiment 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 (100) 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 (1204) and / or the second temple (1205) of FIGS. 12A and 12B). A first display (1250-1) for outputting an image to a left eye among the user's two eyes, and a second display (1250-2) for outputting an image to a right eye among the two eyes, may be disposed on the first surface (1310). The wearable device (100) is formed on the first surface (1310) 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 (1250-1) and the second display (1250-2).

[0161] According to one embodiment, the wearable device (100) may include cameras (1260-1) for photographing and / or tracking both eyes of the user adjacent to each of the first display (1250-1) and the second display (1250-2). The cameras (1260-1) may be referred to as the gaze tracking camera (1260-1) of FIG. 12B. According to one embodiment, the wearable device (100) may include cameras (1260-5, 1260-6) for photographing and / or recognizing the face of the user. The cameras (1260-5, 1260-6) may be referred to as FT cameras. The wearable device (100) may control an avatar representing the user in a virtual space based on the motion of the user's face identified using the cameras (1260-5, 1260-6). For example, the wearable device (100) may change the texture and / or shape of a portion of an avatar (e.g., a portion of an avatar expressing a human face) using information obtained by cameras (1260-5, 1260-6) (e.g., FT cameras) and representing a facial expression of a user wearing the wearable device (100).

[0162] Referring to FIG. 13b, a camera (e.g., cameras (1260-7, 1260-8, 1260-9, 1260-10, 1260-11, 1260-12)) and / or a sensor (e.g., a depth sensor (1330)) for obtaining information related to the external environment of the wearable device (100) may be disposed on a second surface (1320) opposite to the first surface (1310) of FIG. 13a. For example, the cameras (1260-7, 1260-8, 1260-9, 1260-10) may be disposed on the second surface (1320) for recognizing external objects. Cameras (1260-7, 1260-8, 1260-9, 1260-10) may be referenced to the motion recognition cameras (1260-2, 1260-3) of FIG. 12b.

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

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

[0165] Hereinafter, with reference to FIG. 14, the hardware or software configuration of the wearable device (100) is described.

[0166] Fig. 14 illustrates an example of a block diagram of a wearable device (e.g., a wearable device (100)). The wearable device (100) of Fig. 14 may be an example of the electronic device (1101) of Fig. 11 or the wearable device (100) of Figs. 12a to 13b.

[0167] Referring to FIG. 14, a wearable device (100) according to one embodiment may include a processor (1410), a memory (1415), a display (1250) (e.g., the first display (1250-1) and / or the second display (1250-2) of FIGS. 12A, 12B, 13A, and 13B), and / or a sensor (1420). The processor (1410), the memory (1415), the display (1250), and / or the sensor (1420) may be electrically and / or operatively connected to each other by electronic components such as a communication bus (1402). In the present disclosure, the operative connection of the electronic components may include a direct connection established between the electronic components and / or an indirect connection established between the electronic components such that a first electronic component among the electronic components is controlled by a second electronic component among the electronic components. The type and / or number of electronic components included in the wearable device (100) is not limited to those illustrated in FIG. 14. For example, the wearable device (100) may include only some of the electronic components illustrated in FIG. 14.

[0168] According to one embodiment, a processor (1410) of a wearable device (100) may include a circuit (e.g., a processing circuit) for processing data based on one or more instructions. The circuit for processing data may include, for example, an arithmetic and logic unit (ALU), a field programmable gate array (FPGA), a central processing unit (CPU), and / or an application processor (AP). In one embodiment, the wearable device (100) may include one or more processors. The processor (1410) may have a multi-core processor structure such as a dual core, a quad core, a hexa core, and / or an octa core. The multi-core processor structure of the processor (1410) may include a structure (e.g., a big-little structure) based on a plurality of core circuits that are distinguished by power consumption, clock, and / or calculation amount per unit time. In one embodiment comprising a processor (1410) having a multi-core processor architecture, the operations and / or functions of the present disclosure may be performed individually or collectively by one or more cores included in the processor (1410).

[0169] According to one embodiment, the memory (1415) of the wearable device (100) may include electronic components for storing data and / or instructions input to and / or output from the processor (1410). The memory (1415) may include, for example, volatile memory such as random-access memory (RAM) and / or non-volatile memory such as read-only memory (ROM). The volatile memory may include, for example, at least one of dynamic RAM (DRAM), static RAM (SRAM), cache RAM, and pseudo SRAM (PSRAM). The non-volatile memory may include, for example, at least one of programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), flash memory, hard disk, compact disc, and embedded multi media card (eMMC). In one embodiment, memory (1415) may be referred to as storage.

[0170] In one embodiment, a display (1250) of a wearable device (100) can output visualized information to a user of the wearable device (100). The display (1250), which is arranged in front of the eyes of a user wearing the wearable device (100), can be arranged on at least a portion of a housing of the wearable device (100) (e.g., the first display (1250-1) and / or the second display (1250-2) of FIGS. 12A, 12B, 13A, and 13B). For example, the display (1250) can be controlled by a processor (1410) including circuits such as a CPU, a GPU (graphics processing unit), and / or a DPU (display processing unit), to output visualized information to the user. The display (1250) can include a flexible display, a FPD (flat panel display), and / or electronic paper. The display (1250) may include a liquid crystal display (LCD), a plasma display panel (PDP), and / or one or more light emitting diodes (LEDs). The LEDs may include organic LEDs (OLEDs). The embodiment is not limited thereto, and for example, if the wearable device (100) includes a lens for transmitting external light (or ambient light), the display (1250) may include a projector (or projection assembly) for projecting light onto the lens. In one embodiment, the display (1250) may be referred to as a display panel and / or a display module. The pixels included in the display (1250) may be arranged to face one of the user's eyes when the wearable device (100) is worn by the user.For example, the display (1250) may include display areas (or active areas) corresponding to each of the user's two eyes.

[0171] In one embodiment, the sensor (1420) of the wearable device (100) may generate electrical information that may be processed by the processor (1410) and / or the memory (1415) from non-electronic information related to the wearable device (100). For example, the sensor (1420) may include a global positioning system (GPS) sensor for detecting the geographic location of the wearable device (100). In addition to the GPS method, the sensor (1420) may generate information indicating the geographic location of the wearable device (100) based on a global navigation satellite system (GNSS) such as, for example, Galileo or Beidou (compass). The above information may be stored in memory (1415), processed by processor (1410), and / or transmitted to another electronic device distinct from the wearable device (100) via communication circuitry.

[0172] According to one embodiment, one or more instructions (or commands) representing data to be processed, calculations to be performed, and / or operations to be performed by the processor (1410) of the wearable device (100) may be stored in the memory (1415) of the wearable device (100). 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 a software application (hereinafter, “application”). For example, the wearable device (100) and / or the processor (1410) may perform at least one of the operations of FIGS. 3, 6, and 9 when a set of a plurality of instructions distributed in the form of an operating system, firmware, a driver, a program, and / or a software application is executed. Hereinafter, the fact that a software application is installed in a wearable device (100) may mean that one or more instructions provided in the form of a software application (or package) are stored in a memory (1415), and that the one or more applications are stored in a format executable by the processor (1410) (e.g., a file having an extension specified by the operating system of the wearable device (100)). As an example, the application may include a program and / or a library related to a service provided to a user.

[0173] Referring to FIG. 14, programs installed in the wearable device (100) may be included in any one of different layers, including an application layer (1440), a framework layer (1450), and / or a hardware abstraction layer (HAL) (1480), based on the target. For example, programs (e.g., modules or drivers) designed to target the hardware (e.g., the display (1250), and / or the sensor (1420)) of the wearable device (100) may be included in the hardware abstraction layer (1480). The framework layer (1450) may be referred to as an XR framework layer from the perspective of including one or more programs for providing an XR (extended reality) service. For example, the layers illustrated in FIG. 14 may be logically (or for convenience of explanation) separated, and may not mean that the address space of the memory (1415) is separated by the layers.

[0174] For example, within the framework layer (1450), programs designed to target at least one of the hardware abstraction layer (1480) and / or the application layer (1440) (e.g., a position tracker (1471), a space recognizer (1472), a gesture tracker (1473), an eye-gaze tracker (1474), and / or a face tracker (1475)) may be included. The programs included within the framework layer (1450) may provide an application programming interface (API) that is executable (or callable) based on other programs.

[0175] For example, a program designed to target users of a wearable device (100) may be included within the application layer (1440). As an example of programs included in the application layer (1440), an extended reality (XR) system user interface (UI) (1441) and / or an XR application (1442) are exemplified, but the embodiment is not limited thereto. For example, programs (e.g., software applications) included in the application layer (1440) may call an API to cause execution of functions supported by programs included in the framework layer (1450).

[0176] For example, the wearable device (100) may display one or more visual objects on the display (1250) for performing interaction with the user based on the execution of the XR system UI (1441). A visual object may refer to an object that can be placed within a screen for transmitting and / or interacting with information, such as text, an image, an icon, a video, a button, a checkbox, a radio button, a text box, a slider, and / or a table. A visual object may be referred to as a visual guide, a virtual object, a visual element, a UI element, a view object, and / or a view element. The wearable device (100) may provide the user with functions available within a virtual space based on the execution of the XR system UI (1441).

[0177] Referring to FIG. 14, a lightweight renderer (1443) and / or an XR plug-in (1444) are illustrated to be included within the XR system UI (1441), but are not limited thereto. For example, based on the XR system UI (1441), the processor (1410) may execute a lightweight renderer (1443) and / or an XR plug-in (1444) within the framework layer (1450).

[0178] For example, the wearable device (100) may acquire resources (e.g., APIs, system processes, and / or libraries) used to define, create, and / or execute a rendering pipeline that allows partial changes based on the execution of a lightweight renderer (1443). The lightweight renderer (1443) may be referred to as a lightweight render pipeline in terms of defining a rendering pipeline that allows partial changes. The lightweight renderer (1443) may include a renderer built prior to the execution of a software application (e.g., a prebuilt renderer). For example, the wearable device (100) may acquire resources (e.g., APIs, system processes, and / or libraries) used to define, create, and / or execute an entire rendering pipeline based on the execution of an XR plug-in (1444). The XR plugin (1444) can be referred to as an open XR native client from the perspective of defining (or configuring) the entire rendering pipeline.

[0179] For example, the wearable device (100) may display a screen representing at least a portion of a virtual space on the display (1250) based on the execution of the XR application (1442). The XR plug-in (1444-1) included in the XR application (1442) may include instructions that support functions similar to those of the XR plug-in (1444) of the XR system UI (1441). Descriptions of the XR plug-in (1444-1) that overlap with those of the XR plug-in (1444) may be omitted. The wearable device (100) may cause the execution of the virtual space manager (1451) based on the execution of the XR application (1442).

[0180] For example, the wearable device (100) may display an image on the display (1250) in a virtual space based on the execution of the application (1445). The application (1445) may be configured to output image information for displaying a two-dimensional image. The wearable device (100) may cause the execution of the virtual space manager (1451) based on the execution of the application (1445). The wearable device (100) may generate dual image information to display the two-dimensional image in a three-dimensional virtual space based on the execution of the application (1445). Here, the dual image information may include first image information for the left eye and second image information for the right eye, taking into account binocular parallax. In order to display the two-dimensional image in the three-dimensional virtual space, the wearable device (100) may generate the dual image information based on the image information for displaying the two-dimensional image.

[0181] According to one embodiment, the wearable device (100) may provide a virtual space service based on the execution of the virtual space manager (1451). For example, the virtual space manager (1451) may include a platform for supporting the virtual space service. Based on the execution of the virtual space manager (1451), the wearable device (100) may identify a virtual space formed based on the user's location indicated by data acquired through the sensor (1430), and may display at least a portion of the virtual space on the display (1250). The virtual space manager (1451) may be referred to as a composition presentation manager (CPM).

[0182] For example, the virtual space manager (1451) may include a runtime service (1452). As an example, the runtime service (1452) may be referred to as an OpenXR runtime module (or an OpenXR runtime program). The wearable device (100) may execute at least one of a user's pose prediction function, a frame timing function, and / or a spatial input function based on the execution of the runtime service (1452). As an example, the wearable device (100) may perform rendering for a virtual space service for the user based on the execution of the runtime service (1452). For example, a function related to a virtual space, executable by the application layer (1440), may be supported based on the execution of the runtime service (1452).

[0183] For example, the virtual space manager (1451) may include a pass-through manager (1453). Based on the execution of the pass-through manager (1453), the wearable device (100) may display an image and / or video representing an actual space acquired through an external camera on at least a portion of the screen while displaying a screen representing a virtual space on the display (1250).

[0184] For example, the virtual space manager (1451) may include an input manager (1454). The wearable device (100) may identify data (e.g., sensor data) acquired by executing one or more programs included in the recognition service layer (1470) based on the execution of the input manager (1454). The wearable device (100) may use the acquired data to identify user input related to the wearable device (100). The user input may be related to a motion (e.g., a hand gesture), gaze, and / or speech of the user identified by a sensor (1420) (e.g., an image sensor (1430) such as an external camera). The user input may be identified based on an external electronic device connected (or paired) via a communication circuit.

[0185] For example, the perception abstract layer (1460) can be used for data exchange between the virtual space manager (1451) and the perception service layer (1470). From the perspective of being used for data exchange between the virtual space manager (1451) and the perception service layer (1470), the perception abstract layer (1460) can be referred to as an interface. For example, the perception abstract layer (1460) can be referenced as OpenPX. The perception abstract layer (1460) can be used for a perception client and a perception service.

[0186] According to one embodiment, the recognition service layer (1470) may include one or more programs for processing data acquired from the sensor (1420). The one or more programs may include at least one of a position tracker (1471), a space recognizer (1472), a gesture tracker (1473), and / or an eye tracker (1474). The type and / or number of the one or more programs included in the recognition service layer (1470) are not limited to those illustrated in FIG. 14.

[0187] For example, the wearable device (100) can identify the pose of the wearable device (100) using the sensor (1430) based on the execution of the position tracker (1471). The wearable device (100) can identify the 6 degrees of freedom pose (6 dof pose) of the wearable device (100) using data acquired using an external camera (e.g., an image sensor (1421)) and / or an IMU (e.g., a motion sensor (1422) including a gyro sensor, an acceleration sensor, and / or a geomagnetic sensor) based on the execution of the position tracker (1471). The position tracker (1471) may be referred to as a head tracking (HeT) module (or head tracker, head tracking program).

[0188] For example, the wearable device (100) may obtain information for providing a three-dimensional virtual space corresponding to the surrounding environment (e.g., external space) of the wearable device (100) (or the user of the wearable device (100)) based on the execution of the space recognizer (1472). The wearable device (100) may reproduce the surrounding environment of the wearable device (100) in three dimensions using data obtained using an external camera (e.g., an image sensor (1421)) based on the execution of the space recognizer (1472). The wearable device (100) may identify at least one of a plane, a slope, and stairs based on the surrounding environment of the wearable device (100) reproduced in three dimensions based on the execution of the space recognizer (1472). The space recognizer (1472) may be referred to as a scene understanding (SU) module (or a scene recognition program).

[0189] For example, the wearable device (100) may identify (or recognize) a pose and / or gesture of a hand of a user of the wearable device (100) based on the execution of the gesture tracker (1473). As an example, the wearable device (100) may identify a pose and / or gesture of a hand of a user using data acquired from an external camera (e.g., an image sensor (1421)) based on the execution of the gesture tracker (1473). As an example, the wearable device (100) may identify a pose and / or gesture of a hand of a user based on data (or images) acquired using an external camera based on the execution of the gesture tracker (1473). The gesture tracker (1473) may be referred to as a hand tracking (HaT) module (or hand tracking program) and / or a gesture tracking module.

[0190] For example, the wearable device (100) may identify (or track) eye movements of a user of the wearable device (100) based on the execution of the gaze tracker (1474). As an example, the wearable device (100) may identify eye movements of the user using data acquired from a gaze tracking camera (e.g., an image sensor (1421)) based on the execution of the gaze tracker (1474). The gaze tracker (1474) may be referred to as an eye tracking (ET) module (or eye tracking program) and / or a gaze tracking module.

[0191] For example, the recognition service layer (1470) of the wearable device (100) may further include a face tracker (1475) for tracking the user's face. For example, the wearable device (100) may identify (or track) the movement of the user's face and / or the user's expression based on the execution of the face tracker (1475). The wearable device (100) may estimate the user's expression based on the movement of the user's face based on the execution of the face tracker (1475). As an example, the wearable device (100) may identify the movement of the user's face and / or the user's expression based on data (e.g., images and / or videos) acquired using a camera (1425) (e.g., a camera directed at at least a portion of the user's face) based on the execution of the face tracker (1475).

[0192] Referring to FIG. 14, the renderer (1490) may include instructions for rendering images in a three-dimensional virtual space. The processor (1410) executing the renderer (1490) may obtain at least one image to be at least partially displayed in the display area of ​​the display (1250) in a software application. For example, the processor (1410) executing the renderer (1490) may determine the location of the area in which an application (e.g., XR application (1442), application (1445)) is to be rendered. The processor (1410) executing the renderer (1490) may generate an image of the application to be displayed on the display (1250). The renderer (1490) may synthesize images to generate a composite image to be displayed on the display (1250).

[0193] For example, the processor (1410) executing the renderer (1490) can divide the display area of ​​the display (1250) into a foveated portion (or may be referred to as the foveated area) and a peripheral portion (or may be referred to as the residual area) using the gaze position calculated using the position tracker (1471) and / or the gaze tracker (1474). For example, the processor (1410) detecting the coordinate values ​​of the gaze position can determine the portion of the display area including the coordinate values ​​as the foveated area. The DPU executing the renderer (1490) can obtain at least one image corresponding to each of the foveated area and the residual area, and having a size smaller than the size of the entire display area of ​​the display (1250) or a resolution smaller than the resolution of the display area.

[0194] The processor (1410) executing the renderer (1490) may obtain or generate a composite image to be displayed on the display (1250) by synthesizing an image corresponding to the foveated area and an image corresponding to the surrounding area. For example, the processor (1410) may perform upscaling to enlarge the image corresponding to the surrounding area to the size of the entire display area of ​​the display (1250). On the enlarged image, the processor (1410) may combine the image corresponding to the foveated area to generate a composite image to be displayed on the display (1250). Along the boundary line of the image corresponding to the foveated area, the processor (1410) may apply a visual effect, such as blur, to blend the enlarged image and the image corresponding to the foveated area.

[0195] Fig. 15 shows an example of a block diagram of an electronic device (e.g., electronic device (1101), wearable device (100)) for displaying an image in a virtual space. In Fig. 15, an example of executing multiple programs / instructions for displaying an image in a virtual space is described. The multiple programs / instructions may all be executed in one processor (e.g., AP) or may be executed by multiple processors (e.g., AP, GPU (graphics processing unit), NPU (neural processing unit)). The meaning of being executed by the multiple processors means that some programs / instructions may be executed by a first processor and other some programs / instructions may be executed by a second processor different from the first processor.

[0196] Referring to FIG. 15, the electronic device (1101) may execute a virtual space manager (1550) (e.g., the virtual space manager (1451) of FIG. 14, CPM) to render an image in a virtual space. For the virtual space manager (1550), at least some of the descriptions of the virtual space manager (1451) of FIG. 14 may be referenced. The virtual space manager (1550) may include a platform for supporting a virtual space service. The virtual space manager (1550) may include a runtime service (1551) (e.g., OpenXR Runtime), a panel renderer (1552) (e.g., 2D Panel Render), and an XR compositor (1553). The electronic device (1101) may execute at least one of a user's pose prediction function, a frame timing function, and / or a spatial input function based on the execution of the runtime service (1551). For the runtime service (1551), at least some of the descriptions of the runtime service (1452) of FIG. 14 may be referred to. The electronic device (1101) may display at least one image (video) on a panel (e.g., a 2D panel) to implement a virtual space through the display based on the execution of the panel rendering (1552). For example, the electronic device (1101) may display a rendering image corresponding to RGB information (1566) for the panel from the spatialization manager (1540) described below through the display (e.g., the display (1250)). The electronic device (1101) may synthesize an image of an actual area captured by a camera in the virtual space (hereinafter, a pass-through image) with an image of a virtual area based on the execution of the XR compositor (1553). For example, the electronic device (1101) can generate a composite image by merging the pass-through image and the virtual area image based on the execution of the XR synthesis unit (1553).The electronic device (1101) may transmit the generated composite image to a display buffer so that the composite image is displayed. The electronic device (1101) may identify a virtual space through a virtual space manager (1550) and display at least a portion of the virtual space on the display (1250). The virtual space manager (1550) may be referred to as a CPM. The electronic device (1101) may execute the virtual space manager (1550) to render an image corresponding to at least a portion of the virtual space.

[0197] According to one embodiment, the electronic device (1101) may execute a spatialization manager (1540). The spatialization manager (1540) may perform processes for displaying an image in a three-dimensional virtual space. The electronic device (1101) may perform preprocessing based on the execution of the spatialization manager (1540) so that the image can be rendered in a three-dimensional virtual space through the virtual space manager (1550). For example, the electronic device (1101) may perform at least some of the functions of the renderer (1490) of FIG. 14 based on the execution of the spatialization manager (1540). The electronic device (1101) may process image information provided by an application (e.g., an XR application (1510), an application (1520) that provides a general 2D screen other than XR, and an application that provides a system UI (1530)) based on the execution of the spatialization manager (1540). A spatialization manager (1540) (e.g., Space Flinger) may include a system scene manager (1541) (e.g., System scene), an input manager (1542) (e.g., Input Routing), and a lightweight rendering engine (1543) (e.g., Impress Engine). The system scene manager (1541) may be executed to display a system UI (1530). System UI-related information (1564) may be transmitted to the system scene manager (1541) from a program (e.g., API) that provides the system UI (1530). The system UI-related information (1564) may be obtained through a spatializer API and / or a same-process private API. The spatialization manager (1540) may determine the layout (e.g., location, display order) of the screen of the system UI (1530) in a three-dimensional space through pre-allocated resources.The system screen manager (1541) may transmit image information (1567) for rendering the screen of the system UI (1530) to the virtual space manager (1550) according to the layout. The input manager (1542) may be configured to process user input (e.g., user input on a system screen or an app screen). The impression engine (1543) may be a renderer for image generation (e.g., a lightweight renderer (1443)). For example, the impression engine (1543) may be used to display the system UI (1530). According to one embodiment, the spatialization manager (1540) may include a lightweight rendering engine (1543) for rendering the system UI. According to one embodiment, when the lightweight rendering engine (1543) does not have sufficient resources to render an avatar used in the HMD, at least one external rendering engine may be used. At this time, to resolve compatibility issues with external rendering (e.g., 3rd party engines), an external rendering engine support module may be added within the spatialization manager (1540).

[0198] According to one embodiment, the electronic device can execute an application. For example, in response to the execution of an XR application (1510) (e.g., an XR application (1442), a 3D game, an XR map, or other immersive application), the electronic device can execute a virtual space manager (1550). The electronic device (1101) can provide dual image information (1561) provided from the XR application (1510) to the virtual space manager (1550). In order to display an image in a three-dimensional space, the dual image information (1561) can include two pieces of image information that take binocular parallax into account. For example, the dual image information (1561) can include first image information for the user's left eye and second image information for the user's right eye for rendering in a three-dimensional virtual space. Hereinafter, in the present disclosure, the term dual image information is used to refer to image information for displaying images for both eyes in a three-dimensional space. In addition to the dual image information, the above dual image information may also include binocular image information, dual image information, dual image data, dual images, binocular image data, stereoscopic image information, 3D image information, spatial image information, spatial image data, 12D-3D conversion data, dimensional conversion image data, binocular parallax image data, and / or equivalent technical terms. The electronic device (1101) can generate a composite image by merging image layers through a virtual space manager (1550). The electronic device (1101) can transmit the generated composite image to a display buffer. The composite image can be displayed on the display (1250) of the electronic device (1101).

[0199] According to one embodiment, the electronic device can execute at least one application among an XR application (1510) and other applications (1520) (e.g., a first application (1520-1), a second application (1520-2), ..., an Nth application (1520-N)). According to one embodiment, the application (1520) can be configured to output image information for displaying a two-dimensional image. In other words, the application (1520) can provide a two-dimensional image. For example, the application (1520) can be a video application, a schedule application, or an application (1520) can be an Internet browser application. If it is assumed that in response to the execution of the application (1520), image information (1562) provided from the application (1520) is provided to the virtual space manager (1550). Since the image information (1562) only has x-coordinates and y-coordinates within a two-dimensional plane, it may be difficult to consider the chronological relationship (i.e., the distance from the user) between other applications centered on the user. Even when displaying an application (1520) that provides a general 2D screen, the electronic device (1101) may execute the spatialization manager (1540) to provide dual image information to the virtual space manager (1550). For example, based on the execution of the spatialization manager (1540), the electronic device (1101) may receive application-related information (1563) from the first application (1520-1). For example, the application-related information (1563) may include image information representing a two-dimensional image of the first application (1520-1) (e.g., information including RGB for each pixel) and / or content information in the first application (1520-1) (e.g., characteristics of content executed in the first application, type of content). Application related information (1563) can be obtained through the spatializer API.Based on the execution of the spatialization manager (1540), the electronic device (1101) can identify information about the location of the area to be rendered by the first application (1520-1) and the size of the area to be rendered (hereinafter, location information). Based on the execution of the spatialization manager (1540), the electronic device (1101) can generate dual image information (1565, e.g., RGBx2) that takes into account the user's binocular disparity through the image information and the location information. Based on the execution of the spatialization manager (1540), the electronic device (1101) can provide the dual image information (1565) to the virtual space manager (1550). By converting a simple two-dimensional image into the dual image information (1565), a problem that occurs when the image information (1562) is directly transmitted to the virtual space manager (1550) can be resolved. Additionally, since at least some of the functions for displaying images in a virtual space are performed by the spatialization manager (1540) instead of the virtual space manager (1550), the burden on the virtual space manager (1550) can be reduced.

[0200] The wearable device described above may include a memory for storing instructions. The wearable device may include one or more first cameras arranged in relation to the face of a user wearing the wearable device. The wearable device may include one or more second cameras arranged in relation to the eyes of the user wearing the wearable device. The wearable device may include one or more microphones. The wearable device may include a display assembly including at least one display. The wearable device may include at least one processor. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data.The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device, in response to the event, to stop at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0201] In one embodiment, the wearable device may further include one or more third cameras configured to acquire images of an arm of a user wearing the wearable device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar through the display assembly based on further generating fourth data for representing the arm of the avatar using third images acquired through the one or more third cameras. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on further generating the fourth data. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device, in response to the event, to stop at least one of generating the first data to display the avatar, generating the second data to display the avatar, generating the third data to display the avatar, and generating the fourth data to display the avatar.

[0202] In one embodiment, the wearable device may further include a communication circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar through the display assembly based on further generating fourth data for representing a portion of the avatar using information about movement of the control device received through the communication circuit from a control device for controlling a portion of the avatar. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify an event that causes a change in the manner of displaying the avatar while the avatar is being displayed based on further generating the fourth data. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device, in response to the event, to stop at least one of generating the first data to display the avatar, generating the second data to display the avatar, generating the third data to display the avatar, and generating the fourth data to display the avatar.

[0203] In one embodiment, the event may include failing to generate the first data for expressing an expression of the avatar using the first images acquired through the one or more first cameras. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the first data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0204] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar using data for an animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0205] In one embodiment, the event may include failing to generate second data for representing a gaze of the avatar using the second images acquired through the one or more second cameras. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0206] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar using data for an animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0207] In one embodiment, the wearable device may further include a temperature detection sensor. The event may include obtaining a temperature value of the wearable device exceeding a threshold temperature value from the temperature detection sensor. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on the identification, and stopping generating the second data for displaying the avatar.

[0208] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar using data for an animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0209] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to cut off power supplied to the one or more second cameras in response to the event.

[0210] In one embodiment, the wearable device may further include a rechargeable battery. The wearable device may further include a power management integrated circuit configured to acquire a state of charge (SoC) of the rechargeable battery. The event may include acquiring data about the SoC being below a threshold SoC from the power management integrated circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0211] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar using data for an animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0212] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to cut off power supplied to the one or more second cameras in response to the event.

[0213] In one embodiment, the event may include receiving a user input to stop one or more of: expressing the facial expression of the avatar, expressing the gaze of the avatar, and expressing the shape of the mouth of the avatar.

[0214] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar using data for an animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0215] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar using the first data, the second data, the third data, and data for an animation pre-stored in the memory for displaying the avatar.

[0216] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify another event that causes a change in the manner of displaying the avatar while stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to resume, in response to the another event, at least a portion of one or more of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0217] In one embodiment, the other event may include successfully generating the first data using the first images when generating the first data is stopped by stopping at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0218] In one embodiment, the other event may include successfully generating the second data using the second images when generating the second data is stopped by stopping at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0219] In one embodiment, the wearable device may further include a temperature detection sensor. The other event may include obtaining a temperature value of the wearable device below a threshold temperature value from the temperature detection sensor.

[0220] In one embodiment, the wearable device may further include a rechargeable battery. The wearable device may further include a power management integrated circuit configured to acquire a state of charge (SoC) of the rechargeable battery. The other event may include acquiring data from the power management integrated circuit regarding the SoC exceeding a threshold SoC.

[0221] A method performed by a wearable device having a display assembly including one or more first cameras arranged with respect to a face of a user wearing the wearable device, one or more second cameras arranged with respect to an eye of the user wearing the wearable device, one or more microphones, and at least one display, may include an operation of displaying an avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The method may include an operation of identifying an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data. The method may include, in response to the event, an operation of stopping at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0222] In one embodiment, the wearable device may further include one or more third cameras configured to acquire images of an arm of a user wearing the wearable device. The method may include displaying the avatar through the display assembly based on further generating fourth data for representing the arm of the avatar using third images acquired through the one or more third cameras. The method may include identifying an event that causes a change in a manner of displaying the avatar while the avatar is displayed based on further generating the fourth data. The method may include stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, generating the third data for displaying the avatar, and generating the fourth data for displaying the avatar, in response to the event.

[0223] In one embodiment, the wearable device may further include a communication circuit. The method may include an operation of displaying the avatar through the display assembly based on further generating fourth data for representing a portion of the avatar using information about movement of the control device received through the communication circuit from a control device for controlling a portion of the avatar. The method may include an operation of identifying an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on further generating the fourth data. The method may include an operation of stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, generating the third data for displaying the avatar, and generating the fourth data for displaying the avatar, in response to the event.

[0224] In one embodiment, the event may include a failure to generate the first data for expressing an expression of the avatar using the first images acquired through the one or more first cameras. The method may include an operation of stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the first data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0225] According to one embodiment, the method may include an operation of displaying the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0226] In one embodiment, the event may include a failure to generate second data for representing the gaze of the avatar using the second images acquired through the one or more second cameras. The method may include an operation of stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0227] According to one embodiment, the method may include an operation of displaying the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0228] In one embodiment, the wearable device may further include a temperature detection sensor. The event may include obtaining a temperature value of the wearable device exceeding a threshold temperature value from the temperature detection sensor. The method may include an operation of stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0229] According to one embodiment, the method may include an operation of displaying the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0230] In one embodiment, the method may include, in response to the event, cutting off power supplied to the one or more second cameras.

[0231] In one embodiment, the wearable device may further include a rechargeable battery. The wearable device may further include a power management integrated circuit configured to acquire a state of charge (SoC) of the rechargeable battery. The event may include acquiring data about the SoC being less than a threshold SoC from the power management integrated circuit. The method may include an operation of stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0232] According to one embodiment, the method may include an operation of displaying the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0233] In one embodiment, the method may include, in response to the event, cutting off power supplied to the one or more second cameras.

[0234] In one embodiment, the event may include receiving a user input to stop one or more of: expressing the facial expression of the avatar, expressing the gaze of the avatar, and expressing the shape of the mouth of the avatar.

[0235] According to one embodiment, the method may include an operation of displaying the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0236] According to one embodiment, the method may include an operation of displaying the avatar using the first data, the second data, the third data, and data for an animation pre-stored in the memory for displaying the avatar.

[0237] In one embodiment, the method may include an operation of identifying another event that causes a change in the manner of displaying the avatar while stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar. The method may include an operation of resuming at least a portion of one or more of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar, in response to the another event.

[0238] In one embodiment, the other event may include successfully generating the first data using the first images when generating the first data is stopped by stopping at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0239] In one embodiment, the other event may include successfully generating the second data using the second images when generating the second data is stopped by stopping at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0240] In one embodiment, the wearable device may further include a temperature detection sensor. The other event may include obtaining a temperature value of the wearable device below a threshold temperature value from the temperature detection sensor.

[0241] In one embodiment, the wearable device may further include a rechargeable battery. The wearable device may further include a power management integrated circuit configured to acquire a state of charge (SoC) of the rechargeable battery. The other event may include acquiring data from the power management integrated circuit regarding the SoC exceeding a threshold SoC.

[0242] In a computer-readable storage medium having one or more programs stored thereon, as described above, the one or more programs may include instructions that, when executed by a wearable device having one or more first cameras arranged with respect to a face of a user wearing the wearable device, one or more second cameras arranged with respect to an eye of the user wearing the wearable device, one or more microphones, and a display assembly including at least one display, cause the wearable device to display the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify an event that causes a change in the manner of displaying the avatar while the avatar is being displayed based on generating the first data, generating the second data, and generating the third data. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to, in response to the event, stop at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0243] In one embodiment, the wearable device may further include one or more third cameras configured to acquire images of an arm of a user wearing the wearable device. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar through the display assembly based on further generating fourth data for representing the arm of the avatar using third images acquired through the one or more third cameras. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on further generating the fourth data. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to, in response to the event, stop at least one of generating the first data to display the avatar, generating the second data to display the avatar, generating the third data to display the avatar, and generating the fourth data to display the avatar.

[0244] In one embodiment, the wearable device may further include a communication circuit. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar through the display assembly based on further generating fourth data for representing a portion of the avatar using information about movement of the control device received through the communication circuit from a control device for controlling a portion of the avatar. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify an event that causes a change in the manner of displaying the avatar while the avatar is displayed based on further generating the fourth data. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to, in response to the event, stop at least one of generating the first data to display the avatar, generating the second data to display the avatar, generating the third data to display the avatar, and generating the fourth data to display the avatar.

[0245] In one embodiment, the event may include a failure to generate the first data for expressing an expression of the avatar using the first images acquired through the one or more first cameras. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the first data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0246] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0247] In one embodiment, the event may include a failure to generate second data for representing the gaze of the avatar using the second images acquired through the one or more second cameras. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0248] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0249] In one embodiment, the wearable device may further include a temperature detection sensor. The event may include obtaining a temperature value of the wearable device exceeding a threshold temperature value from the temperature detection sensor. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0250] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0251] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to cut off power supplied to the one or more second cameras in response to the event.

[0252] In one embodiment, the wearable device may further include a rechargeable battery. The wearable device may further include a power management integrated circuit configured to acquire a state of charge (SoC) of the rechargeable battery. The event may include acquiring data about the SoC being below a threshold SoC from the power management integrated circuit. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to stop at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar based on stopping generating the second data for displaying the avatar among generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0253] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0254] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to cut off power supplied to the one or more second cameras in response to the event.

[0255] In one embodiment, the event may include receiving a user input to stop one or more of: expressing the facial expression of the avatar, expressing the gaze of the avatar, and expressing the shape of the mouth of the avatar.

[0256] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar using data for animation pre-stored in the memory based on stopping at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0257] According to one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to display the avatar using the first data, the second data, the third data, and data for an animation pre-stored in the memory for displaying the avatar.

[0258] In one embodiment, the one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify another event that causes a change in the manner of displaying the avatar while suspending at least one of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to resume, in response to the another event, at least a portion of generating the first data for displaying the avatar, generating the second data for displaying the avatar, and generating the third data for displaying the avatar.

[0259] In one embodiment, the other event may include successfully generating the first data using the first images when generating the first data is stopped by stopping at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0260] In one embodiment, the other event may include successfully generating the second data using the second images when generating the second data is stopped by stopping at least one of generating the first data to display the avatar, generating the second data to display the avatar, and generating the third data to display the avatar.

[0261] In one embodiment, the wearable device may further include a temperature detection sensor. The other event may include obtaining a temperature value of the wearable device below a threshold temperature value from the temperature detection sensor.

[0262] In one embodiment, the wearable device may further include a rechargeable battery. The wearable device may further include a power management integrated circuit configured to acquire a state of charge (SoC) of the rechargeable battery. The other event may include acquiring data from the power management integrated circuit regarding the SoC exceeding a threshold SoC.

[0263] The wearable device described above may include a memory for storing instructions. The wearable device may include one or more first cameras arranged in relation to the face of a user wearing the wearable device. The wearable device may include one or more second cameras arranged in relation to the eyes of the user wearing the wearable device. The wearable device may include one or more microphones. The wearable device may include a display assembly including at least one display. The wearable device may include at least one processor. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data.The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify a priority corresponding to the event among generating the first data, generating the second data, and generating the third data. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to determine, based on the identified priority, at least one of the first data, the second data, and the third data as data for displaying the avatar (420).

[0264] A method performed by a wearable device having a display assembly including one or more first cameras arranged with respect to a face of a user wearing the wearable device, one or more second cameras arranged with respect to an eye of the user wearing the wearable device, one or more microphones, and at least one display, may include an operation of displaying an avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The method may include an operation of identifying an event that causes a change in a manner for displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data. The method may include an operation of identifying a priority corresponding to the event among generating the first data, generating the second data, and generating the third data in response to the event. The method may include an operation of determining, based on the identified priority, at least one of the first data, the second data, and the third data as data for displaying the avatar (420).

[0265] In a computer-readable storage medium having one or more programs stored thereon, as described above, the one or more programs may include instructions that, when executed by a wearable device having one or more first cameras arranged with respect to a face of a user wearing the wearable device, one or more second cameras arranged with respect to an eye of the user wearing the wearable device, one or more microphones, and a display assembly including at least one display, cause the wearable device to display the avatar through the display assembly based on generating first data for expressing an expression of an avatar corresponding to the user using first images acquired through the one or more first cameras, generating second data for expressing a gaze of the avatar using second images acquired through the one or more second cameras, and generating third data for expressing a shape of a mouth of the avatar using audio signals acquired through the one or more microphones. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify an event that causes a change in the manner of displaying the avatar while the avatar is displayed based on generating the first data, generating the second data, and generating the third data. The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to identify a priority corresponding to the event among generating the first data, generating the second data, and generating the third data.The one or more programs may include instructions that, when executed by the wearable device, cause the wearable device to determine, based on the identified priority, at least one of the first data, the second data, and the third data as data for displaying the avatar (420).

[0266] The devices described above may be implemented as hardware components, software components, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose computers or special-purpose computers, such as a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used alone; however, one of ordinary skill in the art will recognize that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, a processing unit may include multiple processors, or a processor and a controller. Other processing configurations, such as parallel processors, are also possible.

[0267] Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing device to perform a desired operation or may independently or collectively command the processing device. The software and / or data may be embodied in any type of machine, component, physical device, computer storage medium, or device for interpretation by the processing device or for providing instructions or data to the processing device. The software may also be distributed over networked computer systems and stored or executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media.

[0268] The method according to the embodiment may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium. In this case, the medium may be one that continuously stores a computer-executable program or one that temporarily stores it for execution or download. In addition, the medium may be various recording or storage means in the form of a single or multiple hardware combinations, and is not limited to a medium directly connected to a computer system, but may also be distributed over a network. Examples of the medium may include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and those configured to store program commands, including ROM, RAM, and flash memory. In addition, examples of other media may include recording or storage media managed by app stores that distribute applications, sites that supply or distribute various software, servers, etc.

[0269] Although the embodiments described above have been described by way of limited examples and drawings, those skilled in the art will appreciate that various modifications and variations can be made based on the above teachings. For example, appropriate results can still be achieved even if the described techniques are performed in a different order than described, and / or components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or are replaced or substituted with other components or equivalents.

[0270] Therefore, other implementations, other embodiments, and equivalents of the claims are also within the scope of the claims described below. According to one embodiment, the method according to the various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a commodity 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 at least 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 a relay server.

[0271] 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 wearable devices, A memory (206) storing instructions and including one or more storage media; One or more first cameras (209) arranged with respect to the face of a user wearing the wearable device; One or more second cameras (210) arranged in relation to the eyes of a user wearing the wearable device; One or more microphones (212); A display assembly (208) comprising at least one display; and At least one processor (207) comprising processing circuitry, The above instructions, when individually or collectively executed by the at least one processor, Based on generating first data (710) for expressing the facial expression of an avatar (420) corresponding to the user (130) using first images acquired through the one or more first cameras (209), generating second data (720) for expressing the gaze of the avatar (420) using second images acquired through the one or more second cameras (210), and generating third data (730) for expressing the shape of the mouth of the avatar (420) using audio signals acquired through the one or more microphones (212), the avatar (420) is displayed through the display assembly (208). While the avatar (420) is displayed based on generating the first data (710), generating the second data (720), and generating the third data (730), an event that causes a change in the manner of displaying the avatar (420) is identified, and In response to the above event, stop at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar, and generating the third data (730) to display the avatar. causing the above wearable device, Wearable devices.

2. In claim 1, further comprising one or more third cameras (211) configured to acquire images of an arm of a user wearing the wearable device; The above instructions, when individually or collectively executed by the at least one processor, Based on further generating fourth data for expressing the arm of the avatar (420) using third images acquired through the one or more third cameras (211), the avatar is displayed through the display assembly (208), While the above avatar (420) is displayed based on further generating the fourth data, an event that causes a change in the manner of displaying the above avatar (420) is identified, and In response to the above event, stop at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar, generating the third data (730) to display the avatar, and generating the fourth data to display the avatar. causing the above wearable device, Wearable devices.

3. In claim 1, Further comprising a communication circuit (205), The above instructions, when individually or collectively executed by the at least one processor, Based on further generating fourth data for expressing a part of the avatar (420) by using information about the movement of the control device (180) received through the communication circuit (205) from the control device (180) for controlling a part of the avatar (420), the avatar (420) is displayed through the display assembly (208), While the above avatar (420) is displayed based on further generating the fourth data, an event that causes a change in the manner of displaying the above avatar (420) is identified, and In response to the above event, stop at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar (420), generating the third data (730) to display the avatar (420), and generating the fourth data to display the avatar (420). causing the above wearable device, Wearable devices.

4. In claim 1, the event is: Including failing to generate the first data (710) for expressing the facial expression of the avatar (420) using the first images acquired through the one or more first cameras (209), The above instructions, when individually or collectively executed by the at least one processor, Based on stopping the generation of the first data (710) for displaying the avatar (420), the generation of the second data (720) for displaying the avatar (420), and the generation of the third data (730) for displaying the avatar (420), to stop at least one of the generation of the first data (710) for displaying the avatar (420), the generation of the second data (720) for displaying the avatar (420), and the generation of the third data (730) for displaying the avatar (420). causing the above wearable device, Wearable devices.

5. In claim 4, The above instructions, when individually or collectively executed by the at least one processor, Based on stopping at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar (420), and generating the third data (730) to display the avatar (420), display the avatar (420) using data for animation pre-stored in the memory (206). causing the above wearable device, Wearable devices.

6. In claim 1, the event is: Including failing to generate second data (720) for expressing the gaze of the avatar (420) using the second images acquired through the one or more second cameras (210), The above instructions, when individually or collectively executed by the at least one processor, Based on stopping the generation of the second data (720) for displaying the avatar (420) among generating the first data (710) for displaying the avatar (420), generating the second data (720) for displaying the avatar (420), and generating the third data (730) for displaying the avatar (420), stopping at least one of generating the first data (710) for displaying the avatar (420), generating the second data (720) for displaying the avatar (420), and generating the third data (730) for displaying the avatar (420). causing the above wearable device, Wearable devices.

7. In claim 6, The above instructions, when individually or collectively executed by the at least one processor, Based on stopping at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar (420), and generating the third data (730) to display the avatar (420), display the avatar (420) using data for animation pre-stored in the memory (206). causing the above wearable device, Wearable devices.

8. In claim 1, Further comprising a temperature detection sensor (213), The above event includes obtaining a temperature value of the wearable device exceeding a threshold temperature value from the temperature detection sensor (213), The above instructions, when individually or collectively executed by the at least one processor, Based on stopping the generation of the second data (720) for displaying the avatar (420) among generating the first data (710) for displaying the avatar (420), generating the second data (720) for displaying the avatar (420), and generating the third data (730) for displaying the avatar (420), stopping at least one of generating the first data (710) for displaying the avatar (420), generating the second data (720) for displaying the avatar (420), and generating the third data (730) for displaying the avatar (420). causing the above wearable device, Wearable devices.

9. In claim 8, The above instructions, when individually or collectively executed by the at least one processor, Based on stopping at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar (420), and generating the third data (730) to display the avatar (420), display the avatar (420) using data for animation pre-stored in the memory (206). causing the above wearable device, Wearable devices.

10. In claim 8, The above instructions, when individually or collectively executed by the at least one processor, In response to the above event, to cut off power supplied to the one or more second cameras (210), Further causing the above wearable device, Wearable devices.

11. In claim 1, a rechargeable battery (215); and Further comprising a power management integrated circuit (214) configured to obtain the state of charge (SoC) of the rechargeable battery (215), The above event is, Including obtaining data for the SoC below the critical SoC from the power management integrated circuit (214), The above instructions, when individually or collectively executed by the at least one processor, Based on stopping the generation of the second data (720) for displaying the avatar (420) among generating the first data (710) for displaying the avatar (420), generating the second data (720) for displaying the avatar (420), and generating the third data (730) for displaying the avatar (420), stopping at least one of generating the first data (710) for displaying the avatar (420), generating the second data (720) for displaying the avatar (420), and generating the third data (730) for displaying the avatar (420). causing the above wearable device, Wearable devices.

12. In claim 11, The above instructions, when individually or collectively executed by the at least one processor, Based on stopping at least one of generating the first data (710) to display the avatar (420), generating the second data (720) to display the avatar (420), and generating the third data (730) to display the avatar (420), display the avatar (420) using data for animation pre-stored in the memory (206). causing the above wearable device, Wearable devices.

13. In claim 11, The above instructions, when individually or collectively executed by the at least one processor, In response to the above event, to cut off power supplied to the one or more second cameras (210), Further causing the above wearable device, Wearable devices.

14. A method implemented in an electronic device having one or more first cameras (209) arranged in relation to the face of a user wearing the wearable device, one or more second cameras (210) arranged in relation to the eyes of the user wearing the wearable device, one or more microphones (212), and a display assembly (208) including at least one display, An operation of displaying the avatar (420) through the display assembly (208) based on generating first data (710) for expressing the facial expression of the avatar (420) corresponding to the user (130) using first images acquired through the one or more first cameras (209), generating second data (720) for expressing the gaze of the avatar (420) using second images acquired through the one or more second cameras (210), and generating third data (730) for expressing the shape of the mouth of the avatar (420) using audio signals acquired through the one or more microphones (212), An operation of identifying an event that causes a change in the manner of displaying the avatar (420) while the avatar (420) is displayed based on generating the first data (710), generating the second data (720), and generating the third data (730); In response to the above event, an operation of identifying a priority corresponding to the event among generating the first data (710), generating the second data (720), and generating the third data (730), and An operation including determining at least one of the first data (710), the second data (720), and the third data (730) as data for displaying the avatar (420) based on the identified priority. method.

15. In a non-transitory computer-readable storage medium storing one or more programs, the one or more programs are: When executed by a wearable device comprising one or more first cameras (209) arranged in relation to the face of a user wearing the wearable device, one or more second cameras (210) arranged in relation to the eyes of the user wearing the wearable device, one or more microphones (212), and a display assembly (208) including at least one display, Based on generating first data (710) for expressing the facial expression of an avatar (420) corresponding to the user (130) using first images acquired through the one or more first cameras (209), generating second data (720) for expressing the gaze of the avatar (420) using second images acquired through the one or more second cameras (210), and generating third data (730) for expressing the shape of the mouth of the avatar (420) using audio signals acquired through the one or more microphones (212), the avatar (420) is displayed through the display assembly (208). While the avatar (420) is displayed based on generating the first data (710), generating the second data (720), and generating the third data (730), an event that causes a change in the manner of displaying the avatar (420) is identified, In response to the above event, identify a priority corresponding to the event among generating the first data (710), generating the second data (720), and generating the third data (730), and Based on the identified priority, at least one of the first data (710), the second data (720), and the third data (730) is determined as data for displaying the avatar (420). comprising instructions causing the wearable device to operate; Non-transitory computer-readable storage medium.

Images