WO2025198401A1 - Electronic device, method, and non-transitory computer-readable recording medium for sharing hardware resources - Google Patents

Abstract

An electronic device is disclosed. The electronic device may comprise a communication circuit for Bluetooth low energy (BLE). The electronic device may comprise at least one processor including a processing circuit. The electronic device may comprise a memory which stores instructions and includes one or more storage media. The electronic device may receive, from another electronic device through the communication circuit, an advertisement packet for sharing a hardware component of the other electronic device. The electronic device may enable a driver for accessing the hardware component indicated by the advertisement packet, on the basis of the advertisement packet being received while the sharing of the hardware component of the electronic device is enabled. The electronic device may maintain the driver in a disabled state on the basis of the advertisement packet being received while the sharing is disabled.

Description

Electronic device, method, and non-transitory computer-readable recording medium for sharing hardware resources

The following descriptions relate to electronic devices, methods, and non-transitory computer-readable recording media for sharing hardware resources.

As IT technology advances, the use of small electronic devices is increasing. These devices can include smartphones, tablet PCs, portable multimedia players (PMPs), laptop personal computers (PCs), and wearable devices. As the use of small electronic devices increases, situations where multiple small electronic devices are used in the same space are also occurring, and the demand for a continuous and unified user experience across multiple small electronic devices within the same space is also increasing.

An electronic device is disclosed. The electronic device may include a communication circuit for BLE (Bluetooth low energy). The electronic device may include at least one processor including a processing circuit. The electronic device may include a memory storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to receive, from another electronic device via the communication circuit, an advertisement packet for sharing a hardware component of the other electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to activate a driver for accessing the hardware component indicated by the advertisement packet based on the advertisement packet being received while the sharing of the hardware component of the electronic device is enabled. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to keep the driver in a disabled state based on the advertisement packet being received while the sharing was disabled.

An electronic device is disclosed. The electronic device may include a communication circuit for Bluetooth Low Energy (BLE). The electronic device may include at least one processor including a processing circuit. The electronic device may include a memory storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to broadcast an advertisement packet for sharing a hardware component of the electronic device to another electronic device via the communication circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to obtain, from the other electronic device via the communication circuit, an access request for the hardware component indicated by the advertisement packet. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to connect a server process associated with the hardware component to a client process associated with the hardware component running on the other electronic device, based on obtaining the access request. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to transmit, via the communication circuit, a signal to the other electronic device indicating that the server process is connected to the client process running on the other electronic device.

A method is disclosed. The method can be performed in an electronic device including a communication circuit for BLE. The method can include receiving, through the communication circuit, an advertisement packet for sharing a hardware component of another electronic device from the other electronic device. The method can include activating a driver for accessing the hardware component indicated by the advertisement packet based on whether the advertisement packet is received while the sharing of the hardware component of the electronic device is activated. The method can include maintaining the driver in a deactivated state based on whether the advertisement packet is received while the sharing is deactivated.

A method is disclosed. The method can be performed in an electronic device including a communication circuit for BLE. The method can include broadcasting an advertisement packet for sharing a hardware component of the electronic device to another electronic device through the communication circuit. The method can include obtaining, from the other electronic device through the communication circuit, an access request for the hardware component indicated by the advertisement packet. The method can include connecting a server process associated with the hardware component to a client process associated with the hardware component running on the other electronic device based on obtaining the access request. The method can include transmitting, to the other electronic device through the communication circuit, a signal indicating that the server process is connected to the client process running on the other electronic device.

A non-transitory computer-readable storage medium is disclosed. The non-transitory computer-readable storage medium may store a program including instructions. The instructions, when individually or collectively executed by at least one processor of an electronic device including a communication circuit for BLE, may cause the electronic device to receive, through the communication circuit, an advertisement packet for sharing a hardware component of the other electronic device from another electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to activate a driver for accessing the hardware component indicated by the advertisement packet based on the advertisement packet being received while the sharing of the hardware component of the electronic device is activated. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to maintain the driver in a deactivated state based on the advertisement packet being received while the sharing is deactivated.

A non-transitory computer-readable recording medium is disclosed. The non-transitory computer-readable recording medium can store a program including instructions. The instructions, when individually or collectively executed by at least one processor of an electronic device including a communication circuit for BLE, can cause the electronic device to broadcast an advertisement packet for sharing a hardware component of the electronic device to another electronic device via the communication circuit. The instructions, when individually or collectively executed by the at least one processor, can cause the electronic device to obtain, from the other electronic device via the communication circuit, an access request for the hardware component indicated by the advertisement packet. The instructions, when individually or collectively executed by the at least one processor, can cause the electronic device to connect a server process associated with the hardware component to a client process associated with the hardware component running on the other electronic device, based on obtaining the access request. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to transmit, via the communication circuit, a signal to the other electronic device indicating that the server process is connected to the client process running on the other electronic device.

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

FIG. 2 is a block diagram illustrating a program according to various embodiments.

FIG. 3 illustrates an example of a wireless environment including an electronic device, according to one embodiment.

FIG. 4A is a diagram illustrating an example of a screen displayed on another electronic device according to one embodiment.

FIG. 4b is a diagram illustrating an example of a screen displayed on another electronic device according to one embodiment.

FIG. 5A is a diagram illustrating an example of a screen displayed on an electronic device according to one embodiment.

FIG. 5b is a diagram illustrating an example of a screen displayed on an electronic device according to one embodiment.

FIG. 6A is a diagram illustrating operations for advertising and scanning between electronic devices according to one embodiment.

FIG. 6b is a diagram illustrating operations of broadcasting an advertising packet in electronic devices according to one embodiment.

FIG. 6c is a diagram illustrating operations of scanning an advertising packet in an electronic device according to one embodiment.

FIG. 7A is a diagram illustrating operations for sharing hardware resources between electronic devices according to one embodiment.

FIG. 7b is a diagram illustrating operations for setting performance information of hardware components between electronic devices according to one embodiment.

FIG. 8A is a diagram illustrating an example of a screen displayed during sharing of hardware resources in another electronic device, according to one embodiment.

FIG. 8b is a diagram illustrating an example of a screen displayed during sharing of hardware resources in an electronic device according to one embodiment.

FIG. 9 is a diagram illustrating an example of a program architecture of electronic devices according to one embodiment.

FIG. 10A is a diagram illustrating operations by which another electronic device requests initialization of a resource context, according to one embodiment.

FIG. 10b is a diagram illustrating operations by which another electronic device requests an update of a resource context, according to one embodiment.

FIG. 10c is a diagram illustrating operations of an electronic device to update a resource context according to one embodiment.

FIG. 10d is a diagram illustrating operations of an electronic device requesting resources for updating a resource context, according to one embodiment.

FIG. 10e is a diagram illustrating operations of an electronic device requesting resources for updating a resource context, according to one embodiment.

FIG. 11 is a diagram illustrating an example of a relationship between processes of electronic devices according to one embodiment.

FIG. 12 is a flowchart illustrating the operation of an electronic device according to one embodiment.

FIG. 13 is a diagram illustrating an example of different orientations and/or aspect ratios of electronic devices according to one embodiment.

FIG. 14a is a flowchart illustrating the operation of an electronic device according to one embodiment.

FIG. 14b is a flowchart illustrating the operation of an electronic device according to one embodiment.

FIG. 15A is a diagram illustrating operations of an electronic device for processing an image, according to one embodiment.

FIG. 15b is a diagram illustrating operations of an electronic device for processing an image, according to one embodiment.

FIG. 1 is a block diagram of an electronic device (101) within a network environment (100) according to various embodiments.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

According to various embodiments, the antenna module (197) 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.

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)).

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

FIG. 2 is a block diagram (200) illustrating a program (140) according to various embodiments. According to one embodiment, the program (140) may include an operating system (142), middleware (144), or an application (146) executable in the operating system (142) for controlling one or more resources of the electronic device (101). The operating system (142) may include, for example, Android ^™ , iOS ^™ , Windows ^™ , Symbian ^™ , Tizen ^™ , or Bada ^™ . At least some of the programs (140) may be preloaded in the electronic device (101), for example, at the time of manufacturing, or may be downloaded or updated from an external electronic device (e.g., the electronic device (102 or 104), or a server (108)) when used by a user.

The operating system (142) may control the management (e.g., allocation or retrieval) of one or more system resources (e.g., processes, memory, or power) of the electronic device (101). The operating system (142) may additionally or alternatively include one or more driver programs for driving other hardware devices of the electronic device (101), for example, an input module (150), an audio output module (155), a display module (160), an audio module (170), a sensor module (176), an interface (177), a haptic module (179), a camera module (180), a power management module (188), a battery (189), a communication module (190), a subscriber identification module (196), or an antenna module (197).

Middleware (144) can provide various functions to the application (146) so that functions or information provided from one or more resources of the electronic device (101) can be used by the application (146). Middleware (144) can include, for example, an application manager (201), a window manager (203), a multimedia manager (205), a resource manager (207), a power manager (209), a database manager (211), a package manager (213), a connectivity manager (215), a notification manager (217), a location manager (219), a graphics manager (221), a security manager (223), a call manager (225), or a voice recognition manager (227).

The application manager (201) can manage, for example, the life cycle of the application (146). The window manager (203) can manage, for example, one or more GUI resources used on the screen. The multimedia manager (205) can, for example, identify one or more formats required for playing media files, and perform encoding or decoding of a corresponding media file among the media files using a codec suitable for the corresponding format selected among the formats. The resource manager (207) can manage, for example, the source code of the application (146) or the memory space of the memory (130). The power manager (209) can manage, for example, the capacity, temperature, or power of the battery (189), and determine or provide related information necessary for the operation of the electronic device (101) using the corresponding information. According to one embodiment, the power manager (209) can be linked with the basic input/output system (BIOS) (not shown) of the electronic device (101).

The database manager (211) can, for example, create, search, or modify a database to be used by the application (146). The package manager (213) can, for example, manage the installation or update of an application distributed in the form of a package file. The connectivity manager (215) can, for example, manage a wireless connection or direct connection between the electronic device (101) and an external electronic device. The notification manager (217) can, for example, provide a function for notifying a user of the occurrence of a specified event (e.g., an incoming call, a message, or an alarm). The location manager (219) can, for example, manage location information of the electronic device (101). The graphics manager (221) can, for example, manage one or more graphic effects to be provided to the user or a user interface related thereto.

The security manager (223) may provide, for example, system security or user authentication. The telephony manager (225) may manage, for example, a voice call function or a video call function provided by the electronic device (101). The voice recognition manager (227) may, for example, transmit the user's voice data to the server (108) and receive, from the server (108), a command corresponding to a function to be performed in the electronic device (101) based at least in part on the voice data, or text data converted based at least in part on the voice data. In one embodiment, the middleware (144) may dynamically delete some of the existing components or add new components. In one embodiment, at least a portion of the middleware (144) may be included as a part of the operating system (142) or implemented as separate software different from the operating system (142).

The application (146) may include, for example, a home (251), a dialer (253), an SMS/MMS (255), an instant message (IM) (257), a browser (259), a camera (261), an alarm (263), a contact (265), a voice recognition (267), an email (269), a calendar (271), a media player (273), an album (275), a watch (277), a health (279) (e.g., measuring biometric information such as the amount of exercise or blood sugar), or an environmental information (281) (e.g., measuring barometric pressure, humidity, or temperature information) application. According to one embodiment, the application (146) may further include an information exchange application (not shown) that can support information exchange between the electronic device (101) and an external electronic device. The information exchange application may include, for example, a notification relay application configured to transmit designated information (e.g., a call, a message, or an alarm) to an external electronic device, or a device management application configured to manage an external electronic device. The notification relay application may, for example, transmit notification information corresponding to a designated event (e.g., receipt of an email) that occurred in another application (e.g., an email application (269)) of the electronic device (101) to the external electronic device. Additionally or alternatively, the notification relay application may receive notification information from the external electronic device and provide the information to the user of the electronic device (101).

A device management application may, for example, control the power (e.g., turning on or off) or the function (e.g., brightness, resolution, or focus) of an external electronic device or a component thereof (e.g., a display module or a camera module of the external electronic device) that communicates with the electronic device (101). The device management application may additionally or alternatively support the installation, deletion, or update of an application running on the external electronic device.

FIG. 3 illustrates an example of a wireless environment including an electronic device, according to one embodiment.

In one embodiment, the electronic device (101) of FIG. 3 may correspond to the electronic device (101) of FIG. 1. Referring to FIG. 3, the electronic device (101) may include a processor (120), a memory (130), a first communication circuit (391), and a second communication circuit (392).

In one embodiment, the processor (120) may be used to execute operations of the electronic device (101) exemplified in the descriptions of FIGS. 6A to 7B, 10A to 10E, 12, and 14A to 15B. For example, the processor (120) may include at least a portion of the processor (120) of FIG. 1 or may correspond to at least a portion of the processor (120) of FIG. 1. For example, the processor (120) may include one or more processors, including an application processor (AP) and/or a communication processor (CP). For example, the processor (120) may be implemented as a single chip, such as a system on chip (SoC), or may be implemented as multiple chips. For example, the processor (120) may be implemented as a single integrated circuit or may be implemented as multiple integrated circuits. For example, the processor (120) may be distributedly arranged within the electronic device (101).

In one embodiment, the memory (130) may (at least temporarily) store instructions for executing operations of the electronic device (101) exemplified in the descriptions of FIGS. 6A to 7B, 10A to 10E, 12, and 14A to 15B. The instructions may be executed by the processor (120). The instructions may be included in one or more programs (140) stored in the memory (130) (e.g., the program (140) of FIG. 2). For example, the memory (130) may include at least a portion of the memory (130) of FIG. 1 (or at least a portion of the non-volatile memory (134)) or may correspond to at least a portion of the memory (130) of FIG. 1 (or at least a portion of the non-volatile memory (134)). For example, the memory (130) may include a main memory (e.g., a random access memory (RAM)) within the electronic device (101), a register for the processor (120), a cache for the processor (120), a register for the communication circuits (391, 392), a buffer (or soft buffer) for the communication circuits (391, 392), and/or an auxiliary memory (e.g., a hard disk drive (HDD), a solid state drive (SSD)) of the electronic device (101). For example, the memory (130) may be implemented as a single chip or may be implemented as multiple chips. For example, the memory (130) may be implemented as a single integrated circuit or may be implemented as multiple integrated circuits. For example, the memory (130) may be distributedly arranged within the electronic device (101).

In one embodiment, the first communication circuit (391) may be used to support Bluetooth communication (e.g., legacy Bluetooth communication (or classic Bluetooth communication and/or Bluetooth low energy (BLE)) between the electronic device (101) and other electronic devices (e.g., electronic devices (303, 305, 307)). However, the communication technique of the first communication circuit (391) is not limited to the Bluetooth communication technique. The first communication circuit (391) may be used to support communication between the electronic device (101) and other electronic devices (e.g., electronic devices (303, 305, 307)) based on various short-range wireless communication techniques (e.g., wireless fidelity (Wi-Fi), Wi-Fi Direct, Wi-Fi aware, Wi-Fi mobile hotspot, Wi-Fi legacy communication technique, and/or ultra wide band (UWB)).

For example, the first communication circuit (391) may include at least a portion of the communication module (190) (or the wireless communication module (192)) of FIG. 1, or may correspond to at least a portion of the communication module (190) (or the wireless communication module (192)) of FIG. 1. For example, the first communication circuit (391) may include a communication circuit for Bluetooth. For example, the first communication circuit (391) may be used to establish a communication link. For example, the first communication circuit (391) may be used to transmit packets to external electronic devices (201, 202) via the communication link. For example, the first communication circuit (391) may be used to receive packets from electronic devices (303, 305, 307) via the communication link. For example, the first communication circuit (391) may be implemented as a single chip or may be implemented as multiple chips. For example, the first communication circuit (391) may be implemented as a single integrated circuit or as multiple integrated circuits. For example, the first communication circuit (391) may be distributedly arranged within the electronic device (101).

In one embodiment, the second communication circuit (392) may be used to further support a communication technique different from the communication technique of the first communication circuit (391). For example, the second communication circuit (392) may be used to further support a communication technique different from the Bluetooth communication technique (e.g., Wi-Fi, Wi-Fi Direct, Wi-Fi aware, Wi-Fi mobile hotspot, and/or Wi-Fi legacy communication technique). However, the communication technique of the second communication circuit (392) is not limited to Wi-Fi, Wi-Fi Direct, Wi-Fi aware, Wi-Fi mobile hotspot, and Wi-Fi legacy communication techniques. The second communication circuit (39) may be used to support communication between the electronic device (101) and other electronic devices (e.g., electronic devices (303, 305, 307)) based on various short-range wireless communication techniques (e.g., classic Bluetooth communication, BLE, and/or UWB).

For example, the second communication circuit (392) may be implemented as a single chip or as multiple chips. For example, the second communication circuit (392) may be implemented as a single integrated circuit or as multiple integrated circuits. For example, the second communication circuit (392) may be distributedly arranged within the electronic device (101).

In one embodiment, the electronic device (101) may include additional hardware components in addition to the hardware components illustrated in FIG. 3. For example, the electronic device (101) may include hardware components exemplified through the electronic device (101) of FIG. 1 (e.g., a camera module (180), a display module (160), and/or an audio output module (155)).

In one embodiment, the electronic device (303) may include a processor (311), a memory (315), a first communication circuit (393), and a second communication circuit (394). In one embodiment, each of the processor (311), the memory (315), the first communication circuit (393), and the second communication circuit (394) of the electronic device (303) may correspond to each of the processor (120), the memory (130), the first communication circuit (391), and the second communication circuit (392) of the electronic device (101). For example, the hardware configuration and/or the provideable functions of the processor (311) may correspond to the hardware configuration and/or the provideable functions of the processor (120). For example, the hardware configuration and/or the provideable functions of the memory (315) may correspond to the hardware configuration and/or the provideable functions of the memory (130). For example, the hardware configuration and/or the available functions of the first communication circuit (393) may correspond to the hardware configuration and/or the available functions of the first communication circuit (391). For example, the hardware configuration and/or the available functions of the second communication circuit (394) may correspond to the hardware configuration and/or the available functions of the second communication circuit (392).

In one embodiment, the electronic device (303) may include a shareable hardware component (320). For example, the shareable hardware component (320) may include a camera (321), a keyboard (322), and a speaker (323). In one embodiment, the camera (321) may correspond to the camera module (180) of FIG. 1. In one embodiment, the keyboard (322) may correspond to the input module (150) of FIG. 1. In one embodiment, the speaker (323) may correspond to the audio output module (155) and/or the audio module (170) of FIG. 1.

In one embodiment, the electronic device (303) may include additional hardware components in addition to the hardware components illustrated in FIG. 3. For example, the electronic device (303) may include the hardware components illustrated through the electronic device (101) of FIG. 1.

In one embodiment, the electronic device (305) may include a processor (331), a memory (335), a first communication circuit (395), and a second communication circuit (396). In one embodiment, each of the processor (331), the memory (335), the first communication circuit (395), and the second communication circuit (396) of the electronic device (305) may correspond to each of the processor (120), the memory (130), the first communication circuit (391), and the second communication circuit (392) of the electronic device (101).

In one embodiment, the electronic device (305) may include a shareable hardware component (340). For example, the shareable hardware component (340) may include a speaker (343) and a display (344). In one embodiment, the speaker (343) may correspond to the audio output module (155) and/or the audio module (170) of FIG. 1. In one embodiment, the display (344) may correspond to the display module (160) of FIG. 1.

In one embodiment, the electronic device (305) may include additional hardware components in addition to the hardware components illustrated in FIG. 3. For example, the electronic device (305) may include the hardware components illustrated through the electronic device (101) of FIG. 1.

In one embodiment, the electronic device (307) may include a processor (351), a memory (355), a first communication circuit (397), and a second communication circuit (398). In one embodiment, each of the processor (351), the memory (355), the first communication circuit (397), and the second communication circuit (398) of the electronic device (307) may correspond to each of the processor (120), the memory (130), the first communication circuit (391), and the second communication circuit (392) of the electronic device (101).

In one embodiment, the electronic device (307) may include a shareable hardware component (360). For example, the shareable hardware component (360) may include a camera (361) and storage (365). In one embodiment, the camera (361) may correspond to the camera module (180) of FIG. 1. In one embodiment, the storage (365) may correspond to the non-volatile memory (134) of FIG. 1.

In one embodiment, the electronic device (307) may include additional hardware components in addition to the hardware components illustrated in FIG. 3. For example, the electronic device (307) may include the hardware components illustrated through the electronic device (101) of FIG. 1.

In one embodiment, the electronic device (101) and the electronic devices (303, 305, 307) may be a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device.

Hereinafter, operations of an electronic device (101) advertising that sharing of hardware components is activated to electronic devices (303, 305, 307) may be described. Herein, sharing of hardware components of the electronic device (101) may be a function that allows resources related to hardware components of the electronic device (101) to be occupied by shared electronic devices (303, 305, 307). Hereinafter, an electronic device sharing hardware components may be referred to as a sharer (or sharer device), and an electronic device sharing hardware components may be referred to as a receiver (or receiver device).

In one embodiment, the electronic device (101) can activate a shared function of a hardware component. In one embodiment, the electronic device (101) can activate a shared function of a hardware component that is in a disabled state based on an input.

For example, the electronic device (101) may activate the sharing function of a hardware component based on an input to a user interface (UI) for setting the sharing function (e.g., screens (400, 405) of FIG. 4A and/or FIG. 4B). However, the present invention is not limited thereto. For example, the electronic device (101) may maintain the sharing function in an activated state according to a default setting.

For example, the electronic device (101) may activate a sharing function to operate as a sharer of hardware components. For example, the electronic device (101) may activate a sharing function to share at least one hardware component among the shareable hardware components of the electronic device (101).

For example, the electronic device (101) can set sharing conditions for hardware components. For example, the electronic device (101) can set sharing conditions that limit the range of recipients who can share the hardware components. For example, the electronic device (101) can limit the range of recipients to electronic devices logged in with the same account. For example, the electronic device (101) can limit the range of recipients to electronic devices logged in with the account of a user with the same designated relationship (e.g., a colleague, friend, or family member). However, the present invention is not limited thereto.

In one embodiment, the electronic device (101) may broadcast an advertisement packet (e.g., ADV_IND) indicating that sharing is enabled through the first communication circuit (391) based on activating a sharing function to share at least one hardware component. In one embodiment, the electronic device (101) may periodically broadcast an advertisement packet indicating that sharing is enabled through the first communication circuit (391). An operation of broadcasting an advertisement packet indicating that sharing is enabled may be described below with reference to FIG. 6B.

In one embodiment, an advertising packet may include LTV (length, type, value) structures arranged sequentially. Each of the LTV structures arranged sequentially within the advertising packet may include a length field and a data field. The length field may indicate the length of the data field of the LTV structure. The data field of each LTV structure may include a type field and a value field. The type field may have a length of 1 byte. The value field may have a length that is 1 byte less than the length indicated by the length field.

In one embodiment, an advertising packet may include an LTV structure for a flag (hereinafter, a first LTV structure) and an LTV structure for broadcasting manufacturer specific data (hereinafter, a second LTV structure).

In one embodiment, a field (e.g., a continuity LTV field) related to a shared function (or a multi-device continuity framework (MCF)) among the fields included in the second LTV structure may include user information (or account information) (or account ID (identification)) of the electronic device (101). In one embodiment, the MCF may be a framework for providing a continuous user experience between multiple electronic devices registered with the same account. For example, the MCF may generate a command for controlling the search for a nearby electronic device registered with the same account, a command for instructing the exchange of status information of electronic devices registered with the same account, or a command for instructing a connection with an electronic device registered with the same account. However, the present invention is not limited thereto.

In one embodiment, another field (e.g., another continuity LTV field (e.g., a ClientHandlerContext field)) related to the shared function (or MCF) among the fields included in the second LTV structure may include information indicating that the shared function is activated. For example, the electronic device (101) may indicate that the shared function is activated by entering a specified value (e.g., 6) into a specified item (e.g., AppID) of another field related to the shared function of the advertisement packet.

Below, operations by which an electronic device (101) provides performance information (or resources) of hardware components for sharing to a recipient device (e.g., electronic device (303)) may be described.

In one embodiment, the electronic device (101) may broadcast a packet including capability information (or resource) of at least one hardware component based on activating a sharing function to share at least one hardware component. For example, the packet including the capability information (or resource) may include identification information (e.g., AppID, sequence, or presence or absence of app data), the length of the app data, or the app data. Here, the presence or absence of the app data may indicate the presence or absence of the performance information (or resource). The app data may indicate the performance information (or resource). When the sequence is changed, an update of the performance information (or resource) of the hardware component may be triggered.

For example, the electronic device (101) may receive a scan request (e.g., SCAN_REQ) from a recipient device (e.g., electronic device (303)) via the first communication circuit (391). For example, the electronic device (101) may broadcast a packet (e.g., SCAN_RSP) including performance information in response to a scan request for an advertising packet indicating that sharing is enabled. However, the present invention is not limited thereto. For example, the electronic device (101) may include performance information in an advertising packet indicating that sharing is enabled. In this case, the scan request (e.g., SCAN_REQ) and/or the scan response (e.g., SCAN_RSP) may not be transmitted and/or received. In one embodiment, the scan response (e.g., SCAN_RSP) including performance information may be referred to as a media configuration specification message (e.g., MediaConfigSpec). The operation of transmitting and/or setting performance information can be described below with reference to FIG. 7b and FIGS. 10a to 10e.

In one embodiment, the performance information may include information of the electronic device (101) (e.g., name, version of a user interface (UI) program (e.g., OneUI)), information of a program for supporting a sharing function (e.g., version and/or version code), and/or information of a hardware component (e.g., type, supportable functions (or properties)). For example, if the hardware component is a camera, the supportable functions (or properties) may include location (e.g., front or rear), resolution (e.g., 720P, 1080P, 1440P, 2K, 4K), bitrate (e.g., 5, 17), frame rate (frames per seconds, FPS) (e.g., 15, 30), default settings (e.g., default settings for resolution, bitrate, and/or frame rate), and/or image effects (e.g., blur, face touch, auto frame, HDR (high dynamic range)). However, the present invention is not limited thereto. For example, if the hardware component is a speaker, the supported features may include sample rate, bit rate, bit depth, and/or number of channels.

Below, operations for setting the performance of hardware components for sharing by an electronic device (101) can be described.

In one embodiment, the electronic device (101) may receive a scan request (e.g., SCAN_REQ) requesting configuration of a hardware component from a receiver device. In one embodiment, the scan request (e.g., SCAN_REQ) requesting configuration of a hardware component may be referred to as a media configuration message (e.g., MediaConfig). In one embodiment, the media configuration message included in the scan request (e.g., SCAN_REQ) may include a parameter indicating a media type of the hardware component and a parameter indicating an attribute of the hardware component. For example, if the hardware component is a camera, the media configuration message included in the scan request (e.g., SCAN_REQ) may include a parameter indicating a media type of the camera (e.g., "mediaType": "video") and a parameter indicating an attribute of the camera (e.g., "cameraLens": "rear", "resolution": "1080P", "bitrate": 15, "fps": 30). For example, if the hardware component is a speaker, the media setup message included in the scan request (e.g., SCAN_REQ) may include, but is not limited to, parameters indicating the media type of the speaker (e.g., "mediaType": "audio") and parameters indicating the properties of the speaker (e.g., "samplerate": 8, "bitrate": 16, "bitdepth": 16, "channel": "mono").

In one embodiment, the electronic device (101) may change the configuration of a hardware component in response to a scan request (e.g., SCAN_REQ) from a recipient device requesting the configuration of a hardware component. In one embodiment, the electronic device (101) may broadcast a scan response (e.g., SCAN_RSP) indicating that the configuration of the hardware component has been changed.

In one embodiment, a scan response (e.g., SCAN_RSP) indicating a change in the configuration of a hardware component may be referred to as a media configuration message (e.g., MediaConfig). In one embodiment, a scan response (e.g., SCAN_RSP) indicating a change in the configuration of a hardware component may indicate the result of the change in the configuration of the hardware component (e.g., whether an error occurred).

According to an embodiment, the electronic device (101) may receive a scan request (e.g., SCAN_REQ) requesting a change in the settings of a hardware component from a receiver device. In one embodiment, the scan request (e.g., SCAN_REQ) requesting a change in settings may be referred to as a media settings change message (e.g., ChangeMedia). In one embodiment, the media settings change message may include a parameter indicating the media type of the hardware component and a parameter for an attribute to be changed among the attributes of the hardware component. For example, if the hardware component is a camera, the media settings change message included in the scan request (e.g., SCAN_REQ) may include a parameter indicating the media type of the camera (e.g., "mediaType": "video") and a parameter indicating some of the attributes of the camera (e.g., "bitrate": 3). In one embodiment, the electronic device (101) may change some of the settings of the hardware component (e.g., change the bitrate from 15 to 3) in response to a scan request (e.g., SCAN_REQ) from the recipient device requesting a change in the settings of the hardware component. In one embodiment, the electronic device (101) may broadcast a scan response (e.g., SCAN_RSP) indicating that the settings of the hardware component have been changed.

In some embodiments, the electronic device (101) may not receive a scan request (e.g., SCAN_REQ) requesting configuration of a hardware component from the recipient device. In this case, the electronic device (101) may maintain the configuration of the hardware component as the default setting.

Below, shared operations for access by a recipient device (e.g., electronic device (303)) of a hardware component of an electronic device (101) may be described.

In one embodiment, the electronic device (101) may receive a request to execute a server program related to a hardware component from a receiver device. In one embodiment, after the configuration of the hardware component is completed, the electronic device (101) may receive a request to execute a server program related to the hardware component from the receiver device. In one embodiment, the electronic device (101) may receive a request to execute a server program to connect to a client program related to the hardware component running on the receiver device. According to an embodiment, the request to execute the server program may include a binding request between the server program and the client program.

In one embodiment, the client program can communicate with the server program (e.g., inter-process communication (e.g., socket communication)). For example, the client program can provide a request for execution (or control) (or access) of a hardware component to the server program with which it is connected to the communication. For example, the client program can provide the execution result (or control result) (or access result) of the hardware component according to the request obtained from the server program with which it is connected to the communication to the application (146). For example, the client program can be a set of one or more programs for providing one or more functions related to the hardware component to the application. In one embodiment, when the client program is executed, the client program can be referred to as a client process.

In one embodiment, the server program can communicate with the client program (e.g., inter-process communication (e.g., socket communication)). For example, the server program can transmit a request for execution (or control) (or access) of a hardware component from the client program to a device driver associated with the hardware component. For example, the server program can provide the execution result (or control result) (or access result) of the hardware component according to the request obtained from the device driver to the client program with which it is connected to the communication. For example, the server program can be a set of one or more programs for providing one or more functions related to the hardware component to the client program. In one embodiment, when the server program is executed, the server program can be referred to as a server process.

In one embodiment, the electronic device (101) may execute a server program associated with a hardware component in response to an execution request. In one embodiment, the electronic device (101) may establish a communication connection between the running server program and a client program running on a recipient device in response to the execution request. The operation of establishing a communication connection between the server program and the client program may be described below with reference to FIG. 7A.

In one embodiment, the electronic device (101) may obtain a request from a client program running on the recipient device. In one embodiment, the request may include execution (or control) (or access) of a hardware component.

For example, if the hardware component is a camera, the request may include taking a picture using the camera. For example, if the hardware component is a camera, the request may include controlling the camera (e.g., switching cameras, applying basic functions provided by the camera). For example, switching cameras may include switching a camera for taking a picture among multiple cameras included in the electronic device (101). For example, basic functions provided by the camera may include blur, face touch, auto frame, and/or HDR (high dynamic range), but are not limited thereto.

For example, if the hardware component is a speaker, the request may include outputting media (e.g., an audio file) through the speaker (e.g., outputting through the speaker). For example, if the hardware component is a speaker, the request may include controlling the speaker (e.g., changing the volume or applying a basic function provided by the speaker), but is not limited thereto.

For example, if the hardware component is a display, the request may include outputting media (e.g., still images and/or video) through the display (e.g., outputting through the display). For example, if the hardware component is a display, the request may include controlling the display (e.g., changing brightness and/or changing frame rate), but is not limited thereto.

For example, if the hardware component is storage, the request may include, but is not limited to, reading and/or writing data through the storage.

In one embodiment, the electronic device (101) may perform execution (or control) (or access) of a hardware component based on a request from a client program running on the recipient device. In one embodiment, the electronic device (101) may perform execution (or control) (or access) of a hardware component through a server program and/or a device driver.

In one embodiment, the electronic device (101) may transmit a response indicating an execution result (or control result) (or access result) of a hardware component to a client program through a server program.

In one embodiment, communication between the server program and the client program may be performed via the first communication circuit (391) and/or the second communication circuit (392). For example, in the case of data having a relatively large size, data transfer between the server program and the client program may be performed via the second communication circuit (392). For example, in the case of data having a relatively small size, data transfer between the server program and the client program may be performed via the first communication circuit (391) and/or the second communication circuit (392).

For example, if the hardware component is a camera, a request from a client program can be transmitted to a server program via a first communication circuit (391) and/or a second communication circuit (392). For example, if the hardware component is a camera, an image acquired by the camera can be transmitted from the server program to the client program via a second communication circuit (392).

For example, if the hardware component is a speaker, a request for controlling the speaker (e.g., changing the volume or applying a basic function provided by the speaker) may be transmitted to the server program via the first communication circuit (391) and/or the second communication circuit (392). For example, if the hardware component is a speaker, media (e.g., an audio file) may be transmitted from the client program to the server program via the second communication circuit (392).

For example, if the hardware component is a display, a request for controlling the display (e.g., changing the brightness and/or changing the frame rate) may be transmitted to the server program via the first communication circuit (391) and/or the second communication circuit (392). For example, if the hardware component is a display, media (e.g., still images and/or videos) may be transmitted from the client program to the server program via the second communication circuit (392).

For example, if the hardware component is storage, a data read request may be transmitted to the server program through the first communication circuit (391) and/or the second communication circuit (392). For example, if the hardware component is storage, data read from the storage in response to the data read request may be transmitted from the server program to the client program through the second communication circuit (392). For example, if the hardware component is storage, a data write request may be transmitted to the server program through the second communication circuit (392). For example, if the hardware component is storage, a response in response to the data write request may be transmitted from the server program to the client program through the first communication circuit (391) and/or the second communication circuit (392).

In one embodiment, the electronic device (101) may perform execution (or control) (or access) of a hardware component based on a request from a client program running on the recipient device. In one embodiment, the electronic device (101) may perform execution (or control) (or access) of a hardware component through a server program and/or a device driver.

In one embodiment, the electronic device (101) may transmit a response indicating an execution result (or control result) (or access result) of a hardware component to a client program through a server program.

In one embodiment, the electronic device (101) may output a UI (e.g., screens (800, 803) of FIG. 8A) indicating that the hardware component is shared with the recipient device while performing execution (or control) (or access) of the hardware component based on a request from a client program running on the recipient device.

Below, operations for setting the performance of hardware components for sharing based on the loss rate of the electronic device (101) can be described.

In one embodiment, the electronic device (101) may identify a communication environment associated with a hardware component. For example, the communication environment may be associated with transmission and/or reception of data associated with the hardware component.

In one embodiment, the electronic device (101) can identify a loss rate of data associated with a hardware component as an indicator representing a communication environment. In one embodiment, the data may be data transmitted between a server program and a client program. For example, the data may be data acquired by a hardware component transmitted from the server program to the client program. For example, the data may be data to be output to a hardware component transmitted from the client program to the server program. However, the present invention is not limited thereto.

In one embodiment, the electronic device (101) can identify a data loss rate based on a reception report obtained from the receiver device. In one embodiment, the reception report can include information about the number of data received by the receiver device (hereinafter, “the number of reception data”) and/or the number of data not received by the receiver device (hereinafter, “the number of reception failure data”) during a specified period of time. In one embodiment, the receiver device can identify the number of reception data and/or the number of reception failure data based on a sequence number of the data. For example, the receiver device can transmit a reception report including information about the number of reception data and/or reception failure data during a specified period of time to the electronic device (101).

In one embodiment, the electronic device (101) can identify the ratio between the number of received data and/or the number of failed reception data as a loss rate.

In one embodiment, the electronic device (101) can change the throughput of the communication connection through which the electronic device (101) transmits data to the receiver device based on the communication environment. In one embodiment, the electronic device (101) can change the throughput of the communication connection through which the electronic device (101) transmits data to the receiver device based on a loss rate.

For example, the electronic device (101) may increase the throughput based on an improvement in the communication environment. For example, the electronic device (101) may decrease the throughput based on a deterioration in the communication environment. For example, the electronic device (101) may change the throughput by a first value when the loss rate is within a first range. For example, the electronic device (101) may change the throughput by a second value when the loss rate is within a second range. For example, the electronic device (101) may change the throughput by a third value when the loss rate is within a third range. Here, the lower limit of the second range may have a value higher than the upper limit of the first range. The lower limit of the third range may have a value higher than the upper limit of the second range. The third value may be greater than the second value. In one embodiment, the electronic device (101) can increase the throughput when there is no loss rate (or when the throughput is low). In one embodiment, the electronic device (101) can decrease the throughput when there is a loss rate. In one embodiment, the electronic device (101) can decrease the throughput more as the loss rate increases. For example, the first range can include a loss rate of 0%. For example, the second range can include a loss rate of 1 to 4%. For example, the third range can include a loss rate of 5 to 10%. For example, when a loss rate of 0% is identified, the electronic device (101) can increase the throughput by a first value. For example, when a loss rate between 1 and 4% is identified, the electronic device (101) can decrease the throughput by a second value. For example, if a loss rate of between 5 and 10% is identified, the electronic device (101) may reduce the throughput by a third value.

In one embodiment, the electronic device (101) can change the settings of the shared hardware components to change the throughput. In one embodiment, the electronic device (101) can change the parameters specified for each of the hardware components. For example, if the hardware component is a camera, the electronic device (101) can change at least one of the resolution, bit rate, and/or frame rate (e.g., bit rate) to change the throughput. However, the present invention is not limited thereto.

Below, operations of the electronic device (101) scanning advertising packets of the electronic devices (303, 305, 307) can be described.

In one embodiment, the electronic device (101) can activate a shared function of a hardware component. In one embodiment, the electronic device (101) can activate a shared function of a hardware component that is in a disabled state based on an input.

For example, the electronic device (101) may activate the sharing function of a hardware component based on an input to a UI (e.g., screens (500, 505) of FIG. 5A and/or FIG. 5B) for setting the sharing function. However, the present invention is not limited thereto. For example, the electronic device (101) may maintain the sharing function in an activated state according to a default setting.

For example, the electronic device (101) may activate a sharing function to act as a recipient of a hardware component. For example, the electronic device (101) may activate a sharing function to share at least one hardware component among hardware components that can be shared by the electronic device (101).

For example, the electronic device (101) can set sharing conditions for hardware components. For example, the electronic device (101) can set sharing conditions that limit the range of users sharing the hardware components. For example, the electronic device (101) can limit the range of users to electronic devices logged in with the same account. For example, the electronic device (101) can limit the range of users to electronic devices logged in with the account of a user with the same specified relationship (e.g., a colleague, friend, or family member). However, the present invention is not limited thereto.

In one embodiment, the electronic device (101) may scan for an advertisement packet (e.g., ADV_IND) indicating that sharing is enabled, via the first communication circuit (391), based on activating a sharing function to share at least one hardware component. In one embodiment, the electronic device (101) may periodically scan for an advertisement packet indicating that sharing is enabled, via the first communication circuit (391). The operation of scanning for an advertisement packet indicating that sharing is enabled may be described below with reference to FIG. 6C.

In one embodiment, the electronic device (101) may periodically scan, via the first communication circuit (391), an advertising packet including a field (e.g., a continuity LTV field) related to a shared function (or MCF). In one embodiment, the electronic device (101) may periodically scan an advertising packet including user information (or, designated account information) (or, designated account ID) specified in the continuity LTV field. In one embodiment, the electronic device (101) may periodically scan an advertising packet having user information that satisfies a sharing condition.

In one embodiment, the electronic device (101) may periodically scan for advertisement packets that include information indicating that the sharing function is activated in another field (e.g., another continuity LTV field (e.g., a ClientHandlerContext field)) related to the sharing function (or MCF) among the continuity LTV fields. For example, the electronic device (101) may periodically scan for advertisement packets in which a specified value (e.g., 6) is entered in a specified item (e.g., AppID) of another field related to the sharing function of the advertisement packet.

Below, operations by which an electronic device (101) obtains performance information (or resources) of a hardware component of a sharer can be described.

In one embodiment, the electronic device (101) may transmit a scan request (e.g., SCAN_REQ) to a sharer device (e.g., electronic device (303)) via the first communication circuit (391) based on receiving a designated advertising packet. In one embodiment, the electronic device (101) may transmit the scan request requesting performance information of at least one hardware component.

In one embodiment, the electronic device (101) may receive a packet (e.g., SCAN_RSP) containing performance information in response to a scan request from the sharer device. In one embodiment, the scan response (e.g., SCAN_RSP) containing performance information may be referred to as a media configuration specification message (e.g., MediaConfigSpec), but is not limited thereto. For example, the electronic device (101) may obtain the performance information from an advertising packet indicating that sharing is enabled. In this case, the scan request (e.g., SCAN_REQ) and/or the scan response (e.g., SCAN_RSP) may not be transmitted and/or received.

In one embodiment, the electronic device (101) can identify a hardware component shared by the sharer device based on a packet (e.g., SCAN_RSP). In one embodiment, the electronic device (101) can display a visual object representing the found sharer on a UI (e.g., screen (500) of FIG. 5A) for setting the sharing function based on whether the hardware component shared by the sharer device corresponds to a hardware component for which the electronic device (101) has enabled the sharing function.

Below, operations for setting the performance of hardware components for sharing by an electronic device (101) can be described.

In one embodiment, the electronic device (101) can set the performance of the hardware components of the sharer device. For example, when multiple sharer devices are searched, the electronic device (101) can set the performance of the hardware components of the selected sharer device. For example, the electronic device (101) can select the most recently connected (or shared) (or shared) sharer device among the multiple sharer devices. For example, the electronic device (101) can select the sharer device based on a user's selection among the multiple sharer devices.

In one embodiment, the electronic device (101) may determine configuration information of a hardware component based on a packet (e.g., SCAN_RSP) containing performance information. In one embodiment, the electronic device (101) may determine configuration information of a hardware component based on a packet (e.g., SCAN_RSP) containing performance information received from a selected sharer device.

In one embodiment, the electronic device (101) may transmit a scan request (e.g., SCAN_REQ) requesting configuration of a hardware component, including determined configuration information, to the sharer device. In one embodiment, the scan request (e.g., SCAN_REQ) requesting configuration of a hardware component may be referred to as a media configuration message (e.g., MediaConfig). The operation of transmitting and/or setting performance information may be described below with reference to FIG. 7B and FIGS. 10A to 10E.

In one embodiment, the electronic device (101) may receive a scan response (e.g., SCAN_RSP) from the sharer device indicating that a configuration of a hardware component has changed. In one embodiment, the scan response (e.g., SCAN_RSP) indicating that a configuration of a hardware component has changed may be referred to as a media configuration message (e.g., MediaConfig).

According to an embodiment, the electronic device (101) may transmit a scan request (e.g., SCAN_REQ) requesting a change in the settings of a hardware component to the sharer device. In one embodiment, the scan request (e.g., SCAN_REQ) requesting a change in settings may be referred to as a media settings change message (e.g., ChangeMedia). In one embodiment, the media settings change message may include a parameter indicating the media type of the hardware component and a parameter for an attribute to be changed among the attributes of the hardware component.

According to an embodiment, the electronic device (101) may not change the configuration information of the hardware components from the default settings. In this case, the electronic device (101) may not transmit a scan request (e.g., SCAN_REQ) requesting the shared device to configure the hardware components. In this case, the configuration of the hardware components of the shared device may be maintained at the default settings.

Below, sharing operations for accessing hardware components of a sharer device (e.g., electronic device (303)) of an electronic device (101) may be described.

In one embodiment, the electronic device (101) may execute a client program related to a hardware component of the sharer device. In one embodiment, the electronic device (101) may execute a client program related to a hardware component of the sharer device after the configuration of the hardware component is completed.

In one embodiment, the electronic device (101) may transmit a request to the sharer device to execute a server program related to a hardware component. In one embodiment, after execution of the client program (or configuration of the hardware component) is completed, the electronic device (101) may transmit a request to the sharer device to execute a server program related to the hardware component. In one embodiment, the electronic device (101) may transmit a request to execute a server program to connect the sharer device to a client program. According to an embodiment, the request to execute the server program may include a binding request between the server program and the client program.

In one embodiment, the electronic device (101) may receive a response to an execution request from the sharer device. For example, the response to the execution request may include communication connection information between the client program and the server program. The operation of establishing a communication connection between the server program and the client program may be described below with reference to FIG. 7A.

In one embodiment, the electronic device (101) may activate (or load (e.g., INSMOD)) a (virtual) device driver associated with a hardware component. For example, activating (or loading (e.g., INSMOD)) a (virtual) device driver associated with a hardware component may include creating a (kernel) object representing the hardware component in the kernel layer.

In one embodiment, the electronic device (101) may activate (or load (e.g., INSMOD)) a single (virtual) device driver associated with a hardware component when the electronic device (303) shares multiple hardware components of the same type (e.g., one or more front cameras, and/or one or more rear cameras).

In one embodiment, the electronic device (101) may register a hardware component with the device manager based on the execution of a client program and the activation (or loading) of a (virtual) device driver. For example, as the hardware component is registered with the device manager, a device list of hardware components actually included in the electronic device (101) and hardware components shared from a sharer device may be provided to the application (146) through the device manager. Here, the device manager may be a program for managing the hardware component. For example, if the hardware component is a camera, the device manager may be a camera manager. For example, if the hardware component is a display, the device manager may be a display manager. However, the present invention is not limited thereto.

In one embodiment, when the electronic device (101) shares multiple hardware components of the same type (e.g., shares one or more front cameras and/or one or more rear cameras), a list of devices including multiple hardware components may be provided to the application (146) as the hardware components are registered with the device manager.

In one embodiment, the electronic device (101) may obtain a request for a hardware component shared from an application (146). In one embodiment, the electronic device (101) may obtain the request from a client program running on a recipient device. In one embodiment, the request may include execution (or control) (or access) of the hardware component. For example, if the hardware component is a camera, the request may include taking a picture through the camera. For example, if the hardware component is a speaker and/or a display, the request may include outputting media through the speaker and/or the display (e.g., outputting through the speaker and/or outputting through the display). For example, if the hardware component is a storage, the request may include reading and/or writing data through the storage, but is not limited thereto.

In one embodiment, the electronic device (101) can transmit a request from an application (146) to a client program through a device manager. In one embodiment, the electronic device (101) can transmit the request transmitted to the client program to a server program running on a sharer device.

In one embodiment, the electronic device (101) can obtain a response from the server program indicating an execution result (or control result) (or access result) of a hardware component.

In one embodiment, the electronic device (101) may transmit a response indicating an execution result (or control result) (or access result) of a hardware component to the application (146) through a client program and/or a device manager.

In one embodiment, the electronic device (101) may, while executing (or controlling) (or accessing) the hardware components of the sharer device through a client program, display data obtained from the hardware components of the sharer device and/or a UI for controlling the hardware components (e.g., screen (805) of FIG. 8b).

As described above, the electronic device (101) and the electronic devices (303, 305, 307) can utilize hardware components provided by other electronic devices as their own hardware components. For example, the electronic device (101) that has shared a hardware component can register the hardware component in the framework of the electronic device (101) so that the application (146) of the electronic device (101) can recognize the hardware component. Accordingly, the electronic device (101) and the electronic devices (303, 305, 307) can reduce the limitations of the hardware components of the electronic device (101) used by the user by enabling the sharing of hardware components without installing a dedicated application for communication.

FIG. 4A is a diagram illustrating an example of a screen displayed on another electronic device according to one embodiment.

Fig. 4a can be explained with reference to Figs. 1 and 3.

Referring to FIG. 4A, in the settings screen (400), the electronic device (303) can set up sharing of the camera to act as a camera sharer. For example, based on an input to a visual object (415) located in an area (411) for setting up sharing of the camera, the electronic device (303) can activate or deactivate sharing of the camera. In one embodiment, the visual object (415) can be a toggle switch for selecting one of two options (e.g., activating sharing and deactivating sharing).

In one embodiment, the electronic device (303) may broadcast an advertising packet indicating that sharing is enabled via the first communication circuit (393) based on sharing being enabled.

FIG. 4b is a diagram illustrating an example of a screen displayed on another electronic device according to one embodiment.

Fig. 4b can be explained with reference to Figs. 1 and 3.

Referring to FIG. 4B, in the setting screen (405), the electronic device (303) may set sharing of at least one of a plurality of hardware components in order to operate as a sharer of the hardware components. In one embodiment, the setting screen (405) may include a text object (421) indicating that it is a screen for setting sharing of a hardware component, an area (425) for guiding sharing settings, and areas (431, 441, 451, 461, and 471) for setting a plurality of sharable hardware components. However, the present invention is not limited thereto.

For example, the electronic device (303) may identify a plurality of shareable hardware components through hardware resource initialization. For example, the electronic device (303) may display the identified plurality of hardware components in areas (431, 441, 451, 461, and 471).

For example, the electronic device (303) can determine whether to share each of the plurality of hardware components based on user input for visual objects (435, 445, 455, 465, and 475) located in areas (431, 441, 451, 461, and 471). For example, based on input for visual object (435) located in area (431) for setting sharing of storage, the electronic device (303) can activate or deactivate sharing of storage. For example, based on input for visual object (445) located in area (441) for setting sharing of speaker, the electronic device (303) can activate or deactivate sharing of speaker. For example, based on an input to a visual object (455) located in an area (451) for setting up sharing of a camera, the electronic device (303) can activate or deactivate sharing of the camera. For example, based on an input to a visual object (465) located in an area (461) for setting up sharing of a keyboard, the electronic device (303) can activate or deactivate sharing of the keyboard. For example, based on an input to a visual object (475) located in an area (471) for setting up sharing of a display, the electronic device (303) can activate or deactivate sharing of the display.

In one embodiment, the electronic device (303) may broadcast an advertising packet indicating that sharing is enabled via the first communication circuit (393) based on sharing being enabled.

FIG. 5A is a diagram illustrating an example of a screen displayed on an electronic device according to one embodiment.

Fig. 5a can be explained with reference to Figs. 1 and 3.

Referring to FIG. 5A, in the setting screen (500), the electronic device (101) can set up sharing of the camera in order to act as a camera receiver. For example, in the setting screen (500), the electronic device (101) can display a screen for setting up sharing of the camera based on the selection of an item (510) for device-to-device connection. The screen for setting up sharing of the camera may include a text object (521) indicating that it is camera sharing, a visual object (525) for setting up or disabling camera sharing, an area (531) for displaying an image acquired from a sharer during camera sharing, an area (535) for guiding the sharing settings of the camera, a list of scanned sharers (541), and an object (545) for requesting additional scans of the sharer.

For example, based on an input to a visual object (525) to set up sharing of a camera, the electronic device (101) may enable or disable sharing of the camera. In one embodiment, the visual object (525) may be a toggle switch for selecting one of two options (e.g., enabling sharing and disabling sharing).

In one embodiment, the electronic device (101) may scan, via the first communication circuit (391), for an advertising packet indicating that sharing is enabled based on the sharing being enabled. In one embodiment, the electronic device (101) may display one or more electronic devices sharing the camera in a list (541) while sharing is enabled.

FIG. 5b is a diagram illustrating an example of a screen displayed on an electronic device according to one embodiment.

Fig. 5b can be explained with reference to Figs. 1 and 3.

Referring to FIG. 5B, in the setting screen (505), the electronic device (101) may set sharing of at least one of a plurality of hardware components in order to operate as a recipient of the hardware components. In one embodiment, the setting screen (505) may include a text object (551) indicating that it is a screen for setting sharing of a hardware component, an area (555) for guiding sharing settings, and areas (561, 571, 581) for setting a plurality of sharable hardware components. However, the present invention is not limited thereto.

For example, the electronic device (101) can identify a plurality of hardware components that can be shared through hardware resource initialization. For example, the electronic device (101) can display the identified plurality of hardware components in areas (561, 571, 581). Here, the plurality of hardware components that can be shared may be hardware components in which a client program and/or a device driver for each of the plurality of hardware components exists. In one embodiment, as the electronic device (101) additionally acquires (or downloads) a client program and/or a device driver, the plurality of hardware components that can be shared may be further added.

For example, the electronic device (101) can determine whether to share each of a plurality of hardware components based on user input to visual objects (565, 575, and 585) located in areas (561, 571, and 581). For example, based on an input to a visual object (565) located in an area (561) for setting sharing of storage, the electronic device (101) can activate or deactivate sharing of storage. For example, based on an input to a visual object (575) located in an area (571) for setting sharing of a speaker, the electronic device (101) can activate or deactivate sharing of the speaker. For example, based on an input to a visual object (585) located in an area (581) for setting sharing of a camera, the electronic device (101) can activate or deactivate sharing of a camera.

In one embodiment, the electronic device (101) may scan, via the first communication circuit (391), an advertising packet indicating that sharing is enabled based on sharing being enabled.

FIG. 6A is a diagram illustrating operations for advertising and scanning between electronic devices according to one embodiment.

Figure 6a can be explained with reference to Figures 1 to 5b.

Referring to FIG. 6A, in operation 611, the electronic device (101) may activate a sharing function. The electronic device (101) may activate the sharing function to share at least one hardware component. For example, the electronic device (101) may activate the sharing function to share at least one hardware component selected from among a plurality of hardware components that may be shared.

In operation 613, the electronic device (303) may activate a sharing function. The electronic device (303) may activate the sharing function to share at least one hardware component. For example, the electronic device (303) may activate the sharing function to share at least one hardware component selected from among a plurality of shareable hardware components.

In operation 615, the electronic device (305) may activate a sharing function. The electronic device (305) may activate the sharing function to share at least one hardware component. For example, the electronic device (305) may activate the sharing function to share at least one hardware component selected from among a plurality of shareable hardware components.

In operation 617, the electronic device (307) may activate a sharing function. The electronic device (307) may activate the sharing function to share at least one hardware component. For example, the electronic device (307) may activate the sharing function to share at least one hardware component selected from among a plurality of shareable hardware components.

In operation 621, the electronic device (101) may scan an advertising packet. In one embodiment, the electronic device (101) may scan an advertising packet indicating that sharing is enabled through the first communication circuit (391) based on the sharing being enabled.

In one embodiment, the electronic device (101) may periodically scan, via the first communication circuit (391), an advertising packet including a field (e.g., a continuity LTV field) related to a shared function (or MCF). In one embodiment, the electronic device (101) may periodically scan an advertising packet including user information (or, designated account information) (or, designated account ID) specified in the continuity LTV field. In one embodiment, the electronic device (101) may periodically scan an advertising packet having user information that satisfies a sharing condition.

In one embodiment, the electronic device (101) may periodically scan for advertisement packets that include information indicating that the sharing function is activated in another field (e.g., another continuity LTV field (e.g., a ClientHandlerContext field)) related to the sharing function (or MCF) among the continuity LTV fields. For example, the electronic device (101) may periodically scan for advertisement packets in which a specified value (e.g., 6) is entered in a specified item (e.g., AppID) of another field related to the sharing function of the advertisement packet.

In operation 623, the electronic device (303) may broadcast an advertising packet. In one embodiment, the electronic device (303) may broadcast an advertising packet indicating that sharing is activated through the first communication circuit (393) based on the sharing being activated.

In operation 625, the electronic device (305) may broadcast an advertising packet. In one embodiment, the electronic device (305) may broadcast an advertising packet indicating that sharing is enabled through the first communication circuit (395) based on sharing being enabled.

In operation 627, the electronic device (307) may broadcast an advertising packet. In one embodiment, the electronic device (307) may broadcast an advertising packet indicating that sharing is enabled through the first communication circuit (397) based on sharing being enabled.

Advertising packets broadcast via operations 623, 625, and/or 627 may include an LTV structure for flags and an LTV structure for broadcasting manufacturer-specific data. Advertising packets broadcast via operations 623, 625, and/or 627 may include user information (or account information) (or account ID). Advertising packets broadcast via operations 623, 625, and/or 627 may include information indicating that a sharing function is enabled.

In operation 631, the electronic device (101) can identify a hardware component.

In one embodiment, the electronic device (101) may transmit a scan request (e.g., SCAN_REQ) to the sharer devices (e.g., electronic devices (303, 305, 307)) through the first communication circuit (391) based on receiving a designated advertisement packet. In one embodiment, the electronic device (101) may transmit a scan request requesting performance information of at least one hardware component. In one embodiment, the electronic device (101) may receive a packet (e.g., SCAN_RSP) including performance information in response to the scan request from the sharer devices (e.g., electronic devices (303, 305, 307)). In one embodiment, the electronic device (101) may identify a hardware component shared by each of the sharer devices (e.g., electronic devices (303, 305, 307)) based on the packet (e.g., SCAN_RSP).

In operation 641, the electronic device (101) may display a hardware component. In one embodiment, the electronic device (101) may display a visual object representing a searched sharer on a UI (e.g., screen (500) of FIG. 5A) for setting the sharing function, based on whether the hardware component shared by the sharer device corresponds to a hardware component for which the electronic device (101) has activated the sharing function.

FIG. 6b is a diagram illustrating operations of broadcasting an advertising packet in electronic devices according to one embodiment.

FIG. 6B may be described with reference to FIGS. 1 to 6A. The operations of FIG. 6B may be included in operations 613 and 623 of FIG. 6A. The operations of FIG. 6B may be included in operations 615 and 625 of FIG. 6A. The operations of FIG. 6B may be included in operations 617 and 627 of FIG. 6A.

The connection manager (601) and MCF (603) of FIG. 6B may be part of a program of the electronic device (303), but are not limited thereto. The connection manager (601) and MCF (603) of FIG. 6B may be part of a program of the electronic device (305). The connection manager (601) and MCF (603) of FIG. 6B may be part of a program of the electronic device (307).

The operations of FIG. 6b may be performed based on the activation of the sharing function of a hardware component for operating as a sharer.

Referring to FIG. 6B, in operation 651, the connection manager (601) may request a bind from the MCF (603). In one embodiment, the connection manager (601) may request a bind from the MCF (603) to connect an application (or process) related to sharing of hardware components to a network.

In one embodiment, the MCF (603) may, in response to a bind request, establish a communication connection between an application (or process) related to sharing of hardware components and the MCF (603). The communication between the application (or process) and the MCF (603) may be inter-process communication (e.g., socket communication).

In operation 653, the MCF (603) may return an instance to the connection manager (601). In one embodiment, the instance may include, but is not limited to, identification information of the MCF (603) and/or class information.

In operation 655, the connection manager (601) may request the MCP (603) to start advertising. The connection manager (601) may request the MCF (603) to start advertising for sharing of hardware components.

In operation 623, the MCF (603) may broadcast an advertisement packet. In one embodiment, the MCF (603) may broadcast an advertisement packet (e.g., ADV_IND) indicating that sharing is enabled via the first communication circuit (391).

FIG. 6c is a diagram illustrating operations of scanning an advertising packet in an electronic device according to one embodiment.

FIG. 6c can be described with reference to FIGS. 1 to 6b. The operations of FIG. 6c can be included in operations 611, 621, and 631 of FIG. 6a.

The connection manager (605) and MCF (607) of FIG. 6c may be part of the program (140) of the electronic device (101).

The operations of FIG. 6c can be performed based on the activation of the shared function of the hardware component for operating as a receiver.

Referring to FIG. 6c, in operation 661, the connection manager (605) may request a bind from the MCF (607). In one embodiment, the connection manager (605) may request a bind from the MCF (607) to connect an application (or process) related to sharing of hardware components to a network.

In one embodiment, the MCF (607) may, in response to a bind request, establish a communication connection between an application (or process) related to sharing of hardware components and the MCF (607). The communication between the application (or process) and the MCF (607) may be inter-process communication (e.g., socket communication).

In operation 663, the MCF (607) may return an instance to the connection manager (605). In one embodiment, the instance may include, but is not limited to, identification information of the MCF (607) and/or class information.

At operation 665, the connection manager (605) may request the MCF (607) to initiate discovery. The connection manager (605) may request the MCF (607) to initiate discovery for sharing hardware components.

In operation 621, MCF (607) may scan advertising packets.

At operation 667, the MCF (607) may call back to the connection manager (605). The MCF (607) may call back to the connection manager (605) that an advertisement packet indicating that sharing of a hardware component is enabled has been received. For example, the MCF (607) may not call back to the connection manager (605) that an advertisement packet has been received if the received advertisement packet does not indicate that sharing of a hardware component is enabled.

FIG. 7A is a diagram illustrating operations for sharing hardware resources between electronic devices according to one embodiment.

FIG. 7A may be described with reference to FIGS. 1 to 6C. The operations of FIG. 7A may be performed after operations 631 or 641 of FIG. 6A. The operations of FIG. 7A may be performed after operation 667 of FIG. 6C.

Referring to FIG. 7A, in operation 711, the electronic device (101) may execute a client process. In one embodiment, the electronic device (101) may execute a client program related to a hardware component of a sharer device (e.g., electronic device (303)) after the configuration of the hardware component is completed.

In operation 721, the electronic device (101) may request the shared device to execute a server process. In one embodiment, after the execution of the client program (or the configuration of the hardware component) is completed, the electronic device (101) may transmit a request to the shared device to execute a server program related to the hardware component. According to an embodiment, the request to execute the server program may include a binding request between the server program and the client program.

In operation 723, the electronic device (303) may execute a server process. In one embodiment, the electronic device (303) may execute a server program associated with a hardware component in response to an execution request.

In one embodiment, the electronic device (303) may, in response to an execution request, establish a communication connection between a running server program and a client program running on a recipient device (e.g., the electronic device (101)).

In operation 733, the electronic device (303) may notify the electronic device (101) that the connection is complete.

In operation 741, the electronic device (101) may register a hardware component. The electronic device (101) may register the hardware component with the device manager. For example, as the hardware component is registered with the device manager, a device list of hardware components actually included in the electronic device (101) and hardware components shared from a sharer device may be provided to the application (146) through the device manager.

In operation 750, the electronic device (101) and the electronic device (303) can share hardware components.

In one embodiment, the electronic device (101) may obtain a request for a hardware component shared from an application (146). In one embodiment, the electronic device (101) may obtain a request from a client program running on a recipient device.

In one embodiment, the electronic device (101) may transmit a request from an application (146) to a client program through a device manager. In one embodiment, the electronic device (101) may transmit the request transmitted to the client program to a server program running on the electronic device (303).

In one embodiment, the electronic device (303) may obtain a response indicating an execution result (or control result) (or access result) of a hardware component based on a request. In one embodiment, the electronic device (303) may transmit the response to a client program running on the electronic device (101) via a server program.

In one embodiment, the electronic device (101) may transmit a response indicating an execution result (or control result) (or access result) of a hardware component to the application (146) through a client program and/or a device manager.

FIG. 7b is a diagram illustrating operations for setting performance information of hardware components between electronic devices according to one embodiment.

FIG. 7B can be described with reference to FIGS. 1 to 6C. The operations of FIG. 7B can be performed after operations 631 or 641 of FIG. 6A. The operations of FIG. 7B can be performed after operation 667 of FIG. 6C. The operations of FIG. 7B can be performed before operation 711 of FIG. 7A. However, this is not limited thereto. The operations of FIG. 7B can be performed after operation 741 of FIG. 7A.

Referring to FIG. 7B, in operation 753, the electronic device (303) may transmit performance information of a hardware component for which a sharing function is enabled to the electronic device (101). For example, the electronic device (303) may broadcast a media configuration specification message (e.g., MediaConfigSpec) including performance information of the hardware component to the electronic device (101) via the first communication circuit (393).

In operation 761, the electronic device (101) may transmit performance setting information of a hardware component with a shared function enabled.

In one embodiment, the electronic device (101) may determine configuration information of a hardware component based on a media configuration specification message (e.g., MediaConfigSpec) including performance information. In one embodiment, the electronic device (101) may transmit a media configuration message (e.g., MediaConfig) including the determined configuration information to the electronic device (303) via the first communication circuit (391).

In operation 763, the electronic device (303) may set the performance of a hardware component with a shared function enabled. In one embodiment, the electronic device (303) may change the settings of the hardware component in response to a media configuration message (e.g., MediaConfig).

In operation 773, the electronic device (303) may report to the electronic device (101) the completion of setting the performance for the hardware component for which the sharing function is enabled. In one embodiment, the electronic device (303) may transmit a media configuration message (e.g., MediaConfig) to the electronic device (101) indicating that the configuration of the hardware component has been changed.

FIG. 8A is a diagram illustrating an example of a screen displayed during sharing of hardware resources in another electronic device, according to one embodiment.

Fig. 8a can be explained with reference to Fig. 1 and Fig. 7b.

Referring to FIG. 8A, the electronic device (303) may display a screen (800) including a background area (810) and a UI (820) indicating that the camera is shared during camera sharing (e.g., sharing the camera with the electronic device (101). In one embodiment, the screen (800) may be a screen for indicating the sharing status of the camera. For example, the background area (810) may display information related to the camera. For example, the electronic device (303) may display a preview image of an image acquired by the camera in a designated state (e.g., a blurred state) on the background area (810). However, the present invention is not limited thereto.

In one embodiment, the UI (820) may include an object (e.g., pause) to stop sharing the camera.

In one embodiment, the electronic device (303) may stop sharing the camera based on a user input. For example, the user input to stop sharing the camera may include an input to an object (e.g., pause or end) of the UI (820) indicating that the camera is being shared. For example, based on an input to an object of the UI (820) for pause, the electronic device (303) may stop transmitting data acquired through the camera. For example, based on an input to an object of the UI (820) for pause, the electronic device (303) may stop acquiring data through the camera. For example, based on an input to an object of the UI (820) for end, the electronic device (303) may stop transmitting data acquired through the camera and exit the screen (800). For example, based on an input for an object of the UI (820) for end, the electronic device (303) can stop acquiring data through the camera and exit the screen (800). Here, the electronic device (303) exiting the screen (800) may indicate that the electronic device (303) displays a screen other than the screen (800) (e.g., a home screen, a lock screen, or a screen of another application). For example, based on an input for an object of the UI (820) for end, the electronic device (303) can deactivate a sharing function (program and/or device driver). According to an embodiment, the electronic device (303) can transmit a signal indicating that the sharing function (program and/or device driver) is deactivated to the electronic device (101). The electronic device (101) can deactivate the sharing function (program and/or device driver) based on the signal indicating that the sharing function (program and/or device driver) is deactivated.

For example, a user input to stop sharing the camera may include, but is not limited to, an input to leave the screen (800) (e.g., an input to switch to the home screen, or an input to switch applications).

Referring to FIG. 8A, the electronic device (303) may identify a notification while sharing the camera. For example, based on the identification of the notification, the electronic device (303) may display a UI (830) indicating the notification on the screen (803). In one embodiment, the notification may include a notification indicating receipt of a call request, but is not limited thereto.

In one embodiment, the electronic device (303) may stop or pause sharing of the camera based on a user input to the UI (830), but is not limited thereto.

FIG. 8b is a diagram illustrating an example of a screen displayed during sharing of hardware resources in an electronic device according to one embodiment.

Fig. 8b can be explained with reference to Fig. 1 and Fig. 7b.

Referring to FIG. 8B, the electronic device (101) may display a screen (805) including an area (840) for displaying a preview image obtained from the camera during camera sharing (e.g., while sharing a camera from the electronic device (303)), and an area (850) for controlling the camera. In one embodiment, the screen (805) may be a screen for displaying a sharing status of the camera. For example, the area (850) may include objects (851, 853, 855, 857, and 859) for selecting one or more functions related to the camera.

For example, one or more functions related to the camera may include image effects that the camera can provide from the performance information of the hardware component. For example, the image effects that the camera can provide may include a background blur function (851) for applying a blur effect to an area other than the subject (or, a focal length equal to the subject). For example, the image effects that the camera can provide may include a face focus function (853) for automatically detecting a designated subject (e.g., a human face) and automatically adjusting focus and exposure based on the detected subject. For example, the image effects that the camera can provide may include an automatic framing function (855) for automatically adjusting the composition based on the subject (or, the person taking the picture) (or, the subject of the picture). For example, the image effects that the camera can provide may include a high dynamic range (HDR) function (857) for improving contrast ratio (e.g., backlight compensation). However, the present invention is not limited thereto.

For example, one or more functions related to the camera may include a function for switching (or changing) the camera. For example, based on the selection of an object (859) for switching (or changing) the camera, the electronic device (101) may switch the camera for displaying a preview image in an area (840) of the screen (805) among cameras registered in the electronic device (101) (e.g., an actual camera of the electronic device (101) and a camera shared by the electronic device (303).

In one embodiment, the electronic device (101) may stop sharing a hardware component based on a user input. For example, the user input to stop sharing a hardware component may include, but is not limited to, an input to leave the screen (805) (e.g., an input to switch to the home screen or an input to switch applications).

FIG. 9 is a diagram illustrating an example of a program architecture of electronic devices according to one embodiment.

The program architecture (900) of FIG. 9 may represent the program architecture of a recipient device (or guest device) (e.g., electronic device (101)), and the program architecture (905) may represent the program architecture of a sharer device (or host device) (e.g., electronic devices (303, 305, 307)).

The program architecture (900) may include an application layer (910), a framework layer (930), a hardware abstraction layer (HAL) (950), and a kernel layer (970).

The application layer (910) may include a ^third party application (APP) (911) and a device sharing APP (913). The framework layer (930) may include a framework (931) and an Android interface definition language (AIDL) (939). The HAL (950) may include modules (951) for each of the hardware components. Each of the modules (951) of the HAL (950) may be a program for interfacing with device drivers of the hardware components. The kernel layer (970) may include device drivers of one or more hardware components (e.g., a camera driver (971), a camera driver (973), a display driver (975), and a storage driver (979)).

The program architecture (905) may include an application layer (920), a framework layer (940), a HAL (960), and a kernel layer (980).

The application layer (920) may include a device sharing APP (923). The framework layer (940) may include a framework (941) and AIDL (949). The HAL (960) may include modules (961) for each of the hardware components. Each of the modules (961) of the HAL (960) may be a program for interfacing with device drivers of the hardware components. The kernel layer (980) may include device drivers of one or more hardware components (e.g., a camera driver (981), a camera driver (983), a display driver (985), and a storage driver (989)).

Referring to FIG. 9, the device manager (935) of the recipient device can identify an access request to the camera from a ^3rd party APP (911).

In one embodiment, based on the fact that the camera accessed by the ^3rd party APP (911) is a camera of the recipient device, the device manager (935) may transmit an access request to the camera through the AIDL (939), modules (951) of the HAL (950), and the camera driver (971) to access the camera of the recipient device.

In one embodiment, based on the fact that the camera accessed by the ^3rd party APP (911) is a shared camera, the device manager (935) may transmit an access request to the sharer's camera through the client program (or device sharing APP (913)), the server program (or device sharing APP (923)), the device manager (945), the AIDL (949), the modules (961) of the HAL (960), and the camera driver (981) to access the camera of the sharer's device.

The server program (or device sharing APP (923)) may encode (e.g., encoding based on h.264) data (e.g., camera raw frame data) obtained from the camera in response to a request through an encoder (927). In one embodiment, the encoder (927) may be an example of a server program.

The server program (or device sharing APP (923)) can transmit encoded data to the communication client (915) of the client program (or device sharing APP (913)) via the communication server (925) (e.g., a real time streaming protocol (RTSP) server). In one embodiment, the communication server (925) may be an example of a server program. In one embodiment, the communication client (915) may be an example of a client program. In one embodiment, the communication server (925) and the communication client (915) may be connected to each other through MCFs (937, 947). For example, the MCFs (937, 947) may bind the communication server (925) and the communication client (915) in response to a bind request from a connection manager (933, 943). However, the present invention is not limited thereto.

The client program (or device sharing APP (913)) can decode the encoded data through a decoder (917). In one embodiment, the decoder (917) may be an example of a client program.

The client program (or device sharing APP (913)) can transmit the decoded data to the ^3rd party APP (911) through the virtual driver (919) and device manager (935).

Depending on the embodiment, the programs included in the client program (or device sharing APP (913)) and/or the server program (or device sharing APP (923)) may be determined based on the settings of the performance settings between the sharer device and the recipient device, but are not limited thereto.

FIG. 10A is a diagram illustrating operations for another electronic device to request initialization of a resource context, according to one embodiment. The operations of FIG. 10A may be performed upon booting of the electronic device (303), but are not limited thereto.

Referring to FIG. 10A, the electronic device (303) may include a resource handler (1001), a resource holder (1002), and a communication manager (1003). In one embodiment, the resource handler (1001) may be included in the device sharing APP (923) of FIG. 9. In one embodiment, the resource holder (1002) may be included in the MCF (947) of FIG. 9. In one embodiment, the communication manager (1003) may be included in the connection manager (943) of FIG. 9.

Referring to FIG. 10A, in operation 1011, the resource handler (1001) may initialize the resources of the resource holder (1002). For example, the resource holder (1002) may initialize the resources of the hardware component to be shared. The resource holder (1002) may initialize the performance information of the hardware component to be shared.

In operation 1013, the resource handler (1001) may initialize a cluster. In one embodiment, the cluster may include one or more hardware components for sharing.

In operation 1015, the resource handler (1001) may set up a cluster of resource holders (1002). The resource handler (1001) may set up one or more hardware components for sharing.

In operation 1017, the resource holder (1002) may request an update of the resource context to the communication manager (1003). In one embodiment, the resource context may include, but is not limited to, performance information of hardware components and/or cluster information.

In operation 1019, the communication manager (1003) may broadcast an advertisement packet for updating the resource context.

FIG. 10B is a diagram illustrating operations of another electronic device requesting an update of a resource context, according to an embodiment. The operations of FIG. 10B may be performed in situations other than booting the electronic device (303), such as during use. For example, the operations of FIG. 10B may be performed when the electronic device (303) is updated. For example, the update may be an update to additionally provide a service of a hardware component. For example, adding a service of a hardware component may include adding a shareable hardware component.

Referring to FIG. 10B, the electronic device (303) may include a resource handler (1001), a resource holder (1002), and a communication manager (1003). In one embodiment, the resource handler (1001) may be included in the device sharing APP (923) of FIG. 9. In one embodiment, the resource holder (1002) may be included in the MCF (947) of FIG. 9. In one embodiment, the communication manager (1003) may be included in the connection manager (943) of FIG. 9.

Referring to FIG. 10b, at operation 1021, the resource handler (1001) may obtain a message (e.g., intent, listener) indicating that device information (e.g., hardware component) has changed.

In operation 1023, the resource handler (1001) may request the resource holder (1002) to set a property. For example, the resource handler (1001) may request the resource holder (1002) to set a property related to a hardware component. In one embodiment, setting a property may include changing a property of a resource.

In operation 1025, the resource handler (1001) may request a resource update from the resource holder (1002). The resource handler (1001) may request the resource holder (1002) to update the resources of a hardware component whose device information has changed. In one embodiment, updating the resources may include adding, deleting, and/or changing the resources.

In operation 1027, the resource handler (1001) may request the communication manager (1003) to update the resource context. In one embodiment, the resource context may include, but is not limited to, performance information of hardware components and/or cluster information.

At operation 1029, the communication manager (1003) may broadcast an advertisement packet for updating the resource context.

FIG. 10c is a diagram illustrating operations of an electronic device to update a resource context according to one embodiment.

Referring to FIG. 10c, the electronic device (101) may include a resource handler (1004), a resource holder (1005), and a communication manager (1006). In one embodiment, the resource handler (1004) may be included in the device sharing APP (913) of FIG. 9. In one embodiment, the resource holder (1005) may be included in the MCF (937) of FIG. 9. In one embodiment, the communication manager (1006) may be included in the connection manager (933) of FIG. 9.

Referring to FIG. 10c, in operation 1031, the communication manager (1006) may receive an advertisement packet. The communication manager (1006) may receive an advertisement packet for updating a resource context.

In operation 1033, the communication manager (1006) may notify the resource handler (1004) of a change in context. The communication manager (1006) may notify the resource handler (1004) that it has received an advertisement packet for updating the resource context.

In operation 1035, the resource handler (1004) may request the resource holder (1005) to update the resource. The resource handler (1004) may request the resource holder (1005) to update the resource based on the advertisement packet.

FIG. 10d is a diagram illustrating operations of an electronic device requesting resources for updating a resource context, according to one embodiment.

Referring to FIG. 10d, the electronic device (101) may include a resource handler (1004), a resource holder (1005), and a communication manager (1006). In one embodiment, the resource handler (1004) may be included in the device sharing APP (913) of FIG. 9. In one embodiment, the resource holder (1005) may be included in the MCF (937) of FIG. 9. In one embodiment, the communication manager (1006) may be included in the connection manager (933) of FIG. 9.

Referring to FIG. 10d, the electronic device (303) may include a resource handler (1001), a resource holder (1002), and a communication manager (1003). In one embodiment, the resource handler (1001) may be included in the device sharing APP (923) of FIG. 9. In one embodiment, the resource holder (1002) may be included in the MCF (947) of FIG. 9. In one embodiment, the communication manager (1003) may be included in the connection manager (943) of FIG. 9.

Referring to FIG. 10d, in operation 1031, the communication manager (1006) may receive an advertisement packet. The communication manager (1006) may receive an advertisement packet for updating a resource context.

In operation 1033, the communication manager (1006) may notify the resource handler (1004) of a change in context. The communication manager (1006) may notify the resource handler (1004) that it has received an advertisement packet for updating the resource context.

In operation 1041, the resource handler (1004) may request a resource from the resource handler (1001). For example, the resource handler (1004) may request a resource from the resource handler (1001) if a resource for a hardware component of the electronic device (303) is not identified (in the advertisement packet).

In operation 1043, the resource handler (1001) may pass a resource to the resource handler (1004). For example, the resource handler (1001) may pass a resource in a specified format (e.g., a JSON string format) to the resource handler (1004).

In operation 1035, the resource handler (1004) may request a resource update from the resource holder (1005). The resource handler (1004) may request a resource update from the resource holder (1005) based on the resource acquired from the resource handler (1001).

FIG. 10e is a diagram illustrating operations of an electronic device requesting resources for updating a resource context, according to one embodiment.

Referring to FIG. 10e, the electronic device (101) may include a resource handler (1004), a resource holder (1005), and a communication manager (1006). In one embodiment, the resource handler (1004) may be included in the device sharing APP (913) of FIG. 9. In one embodiment, the resource holder (1005) may be included in the MCF (937) of FIG. 9. In one embodiment, the communication manager (1006) may be included in the connection manager (933) of FIG. 9.

Referring to FIG. 10e, the electronic device (303) may include a resource handler (1001), a resource holder (1002), and a communication manager (1003). In one embodiment, the resource handler (1001) may be included in the device sharing APP (923) of FIG. 9. In one embodiment, the resource holder (1002) may be included in the MCF (947) of FIG. 9. In one embodiment, the communication manager (1003) may be included in the connection manager (943) of FIG. 9.

Referring to FIG. 10e, in operation 1051, the resource handler (1004) may request a resource from the resource handler (1001). For example, if a sequence included in an advertisement packet of the electronic device (303) has changed, the resource handler (1004) may request a resource from the resource handler (1001). Here, the sequence may be included as part of the identification information in a packet including performance information (or resources).

In operation 1053, the resource handler (1001) may request a profile from the resource holder (1002). The resource handler (1001) may request a profile related to a hardware component from the resource holder (1002).

In operation 1055, the resource holder (1002) can pass the profile to the resource handler (1001).

In operation 1057, the resource handler (1001) may pass a resource to the resource handler (1004). The resource handler (1001) may pass a resource identified based on a profile to the resource handler (1004).

In operation 1059, the resource handler (1004) may request a resource update from the resource holder (1005). The resource handler (1004) may request a resource update from the resource holder (1005) based on the resource acquired from the resource handler (1001).

FIG. 11 is a diagram illustrating an example of a relationship between processes of electronic devices according to one embodiment.

In one embodiment, the hardware resource controller (1113) of the electronic device (101) may be included in the device sharing APP (913) of FIG. 9. In one embodiment, at least one client among the clients (1115, 1117, 1119) of the electronic device (101) may be included in the device sharing APP (913) of FIG. 9. For example, when the electronic device (101) receives sharing of a camera, the hardware resource controller (1113) and the camera client (1115) may be included in the device sharing APP (913) of FIG. 9. For example, when the electronic device (101) receives sharing of a storage, the hardware resource controller (1113) and the storage client (1117) may be included in the device sharing APP (913) of FIG. For example, if the electronic device (101) receives speaker sharing, the hardware resource controller (1113) and the audio client (1119) may be included in the device sharing APP (913) of FIG. 9.

Referring to FIG. 11, in order to provide a shared function of hardware components of the electronic device (303) to a ^3rd party APP (911), each of the clients (1115, 1117, 1119) may include multiple programs. For example, the camera client (1115) may include programs for a virtual camera driver (1121), a shared memory (1123), and a data manager (1125). For example, the virtual camera driver (1121) may include information about a camera driver (1131) and/or a media source (1135). For example, the data manager (1125) may include information about a manager (1141), a decoder (1143), a utility (1145), and/or a command (CMD) (1147).

In one embodiment, the hardware resource controller (1153) of the electronic device (303) may be included in the device sharing APP (923) of FIG. 9. In one embodiment, at least one of the servers (1155, 1157, 1159) of the electronic device (303) may be included in the device sharing APP (923) of FIG. 9. For example, when the electronic device (303) receives sharing of a camera, the hardware resource controller (1153) and the camera server (1155) may be included in the device sharing APP (923) of FIG. 9. For example, when the electronic device (303) receives sharing of a storage, the hardware resource controller (1153) and the storage server (1157) may be included in the device sharing APP (923) of FIG. For example, if the electronic device (303) receives speaker sharing, the hardware resource controller (1153) and the audio server (1159) may be included in the device sharing APP (923) of FIG. 9.

Referring to FIG. 11, each of the servers (1155, 1157, 1159) can be connected to each of the clients (1115, 1117, 1119) of the electronic device (101) through a communication connection via the MCFs (937, 947).

Each of the servers (1155, 1157, 1159) may include a plurality of programs to provide functions corresponding to each of the clients (1115, 1117, 1119) of the electronic device (101). For example, the camera server (1155) may include programs for data management (1161), CONFIG (1163), frame queue (1165), and RAW FEED API (application programming interface) (1167). For example, data management (1161) may include information about the manager (1171), the encoder (1173), the utility (1175), and/or the CMD (1177). For example, CONFIG (1163) may include setting information. The frame queue (1165) may include images acquired through the camera. The RAW FEED API (1167) may include an API for providing camera raw frame data.

FIG. 12 is a flowchart illustrating the operation of an electronic device according to one embodiment.

Referring to FIG. 12, in operation 1210, the electronic device (101) may receive an advertising packet. The electronic device (101) may receive an advertising packet indicating that sharing is activated.

In operation 1220, the electronic device (101) may identify a hardware component based on an advertisement packet. For example, an advertisement packet indicating that sharing is enabled may include information about a hardware component for which sharing is enabled in the electronic device (303) that transmitted the advertisement packet. For example, the electronic device (101) may identify a hardware component based on receiving information about a hardware component for which sharing is enabled.

In operation 1230, the electronic device (101) may activate a driver corresponding to a hardware component. For example, the electronic device (101) may execute a client program corresponding to a hardware component for which sharing is enabled. For example, the electronic device (101) may request the electronic device (303) to execute a server program corresponding to the client program. For example, the electronic device (101) may activate (or load) the driver corresponding to the hardware component based on receiving a response from the electronic device (303) indicating that execution of the server program has been completed.

In one embodiment, the electronic device (101) may keep a driver corresponding to a hardware component for which sharing is disabled in a disabled state based on receiving an advertising packet indicating that sharing is disabled. In one embodiment, the electronic device (101) may keep a driver corresponding to a hardware component in a disabled state based on receiving an advertising packet while sharing of the hardware component of the electronic device (303) is disabled.

FIG. 13 is a diagram illustrating an example of different orientations and/or aspect ratios of electronic devices according to one embodiment.

FIG. 13 may illustrate a situation in which at least one of the orientation or aspect ratio of the electronic device (101) and the electronic device (303) is different in a situation in which the camera of the electronic device (303) is shared with the electronic device (101).

A situation (1301) of FIG. 13 may represent an image captured by a camera of the electronic device (303) while the orientation of the electronic device (303) is landscape. The image captured by the camera of the electronic device (303) may be displayed on a display area of a display of the electronic device (101) (e.g., a display module (160) of FIG. 1). For example, when the orientation and aspect ratio of the electronic device (303) (or an image captured by the camera of the electronic device (303)) are the same as the orientation and aspect ratio of the electronic device (101) (or the display area of the electronic device (101), the image captured by the camera of the electronic device (303) may be displayed on the electronic device (101) (or the display area of the electronic device (101)) without additional image processing.

In the situation (1301) of FIG. 13, when the orientation of the electronic device (101) (or the display area of the electronic device (101)) and the orientation of the electronic device (303) (or the image captured through the camera of the electronic device (303)) are both landscape, but the aspect ratio (e.g., 16:9) of the electronic device (101) (or the display area of the electronic device (101)) is different from the aspect ratio (e.g., 4:3) of the electronic device (303) (or the image captured through the camera of the electronic device (303)), an area (1311) of an image corresponding to the aspect ratio (e.g., 16:9) of the electronic device (101) (or the display area of the electronic device (101)) can be displayed on the electronic device (101) (or the display area of the electronic device (101)). Alternatively, in the situation (1301) of FIG. 13, when the orientation (i.e., portrait) of the electronic device (101) (or the display area of the electronic device (101)) is different from the orientation (i.e., landscape) of the electronic device (303) (or the image captured through the camera of the electronic device (303)), an area (1315) of the image corresponding to the orientation (i.e., portrait) of the electronic device (101) (or the display area of the electronic device (101)) may be displayed on the electronic device (101) (or the display area of the electronic device (101)). Alternatively, in the situation (1301) of FIG. 13, when the orientation (i.e., portrait) and aspect ratio (e.g., 9:16) of the electronic device (101) (or the display area of the electronic device (101)) are different from the orientation (i.e., landscape) and aspect ratio (e.g., 4:3) of the electronic device (303) (or the image captured through the camera of the electronic device (303)), an area (1315) of an image corresponding to the orientation (i.e., portrait) and aspect ratio (e.g., 9:16) of the electronic device (101) (or the display area of the electronic device (101)) may be displayed on the electronic device (101) (or the display area of the electronic device (101)).

A situation (1305) of FIG. 13 may represent an image captured by a camera of the electronic device (303) while the orientation of the electronic device (303) is a portrait. The image captured by the camera of the electronic device (303) may be displayed on a display area of a display of the electronic device (101) (e.g., a display module (160) of FIG. 1). For example, when the orientation and aspect ratio of the electronic device (303) (or an image captured by the camera of the electronic device (303)) are the same as the orientation and aspect ratio of the electronic device (101) (or the display area of the electronic device (101), the image captured by the camera of the electronic device (303) may be displayed on the electronic device (101) (or the display area of the electronic device (101)) without additional image processing.

In the situation (1305) of FIG. 13, when the orientation (i.e., landscape) of the electronic device (101) (or the display area of the electronic device (101)) is different from the orientation (i.e., portrait) of the electronic device (303) (or the image captured through the camera of the electronic device (303)), an area (1321) of an image corresponding to the orientation (i.e., landscape) of the electronic device (101) (or the display area of the electronic device (101)) can be displayed on the electronic device (101) (or the display area of the electronic device (101)). Alternatively, in the situation (1305) of FIG. 13, when the orientation (i.e., landscape) and aspect ratio (e.g., 16:9) of the electronic device (101) (or the display area of the electronic device (101)) are different from the orientation (i.e., portrait) and aspect ratio (e.g., 3:4) of the electronic device (303) (or the image captured through the camera of the electronic device (303)), an area (1315) of an image corresponding to the orientation (i.e., portrait) and aspect ratio (e.g., 16:9) of the electronic device (101) (or the display area of the electronic device (101)) may be displayed on the electronic device (101) (or the display area of the electronic device (101)). In a situation (1305) of FIG. 13, when both the orientation of the electronic device (101) and the orientation of the electronic device (303) (or the image captured through the camera of the electronic device (303)) are portraits, but the aspect ratio (e.g., 9:16) of the electronic device (101) (or the display area of the electronic device (101)) is different from the aspect ratio (e.g., 3:4) of the electronic device (303) (or the image captured through the camera of the electronic device (303)), an area (1325) of the image corresponding to the aspect ratio (e.g., 9:16) of the electronic device (101) (or the display area of the electronic device (101)) may be displayed in the display area of the electronic device (101).

Depending on the situation, if the orientation of the electronic device (101) (or the area displayed on the electronic device (101)) and the orientation of the electronic device (303) (or the image captured by the camera) are different, a rotated image may be displayed on the electronic device (101) (or the area displayed on the electronic device (101). For example, if the electronic device (101) is rotated 90 degrees in a first direction (e.g., clockwise) in a portrait state and the electronic device (303) is rotated 90 degrees in a second direction (e.g., counterclockwise) opposite to the first direction in the portrait state, a rotated image may be displayed on the electronic device (101) (or the area displayed on the electronic device (101)). For example, when the electronic device (101) is rotated 180 degrees in the first direction or the second direction in the portrait state and the electronic device (303) is not rotated in the portrait state, a rotated image may be displayed on the electronic device (101) (or an area displayed on the electronic device (101)). However, this is not limited thereto.

Referring to situations (1301, 1305) of FIG. 13, when the aspect ratio of the electronic device (101) (or the area displayed on the electronic device (101)) and the aspect ratio of the electronic device (303) (or the image captured through the camera) are different from each other, only a part of the image may be displayed on the electronic device (101) (or the area displayed on the electronic device (101)).

Accordingly, a method may be required to correspond the orientation and/or aspect ratio of the electronic device (101) (or the area displayed on the electronic device (101)) to the orientation and/or aspect ratio of the electronic device (303) (or the image captured by the camera).

FIG. 14a is a flowchart illustrating the operation of an electronic device according to one embodiment.

The operations of FIG. 14a may be performed in parallel with the operations of FIG. 14b, but are not limited thereto. After the operations of FIG. 14a are performed, the operations of FIG. 14b may be performed. After the operations of FIG. 14b are performed, the operations of FIG. 14a may be performed.

Referring to FIG. 14A, in operation 1410, the electronic device (101) may obtain orientation information of the electronic device (101) and orientation information of the electronic device (303). In one embodiment, the electronic device (101) may obtain orientation information of the electronic device (303) from the electronic device (303). For example, the electronic device (101) may request and obtain orientation information from the electronic device (303), periodically receive orientation information from the electronic device (303), or obtain orientation information of the electronic device (303) based on a change in the orientation of the electronic device (303). For example, the electronic device (101) may obtain orientation information of the electronic device (101) based on a sensor (e.g., the sensor module (176) of FIG. 1) (e.g., an acceleration sensor) of the electronic device (101).

In operation 1420, the electronic device (101) can determine whether the orientations are different. In one embodiment, the electronic device (101) can determine whether the orientations of the electronic device (101) and the orientations of the electronic device (303) are different from each other. In one embodiment, the electronic device (101) can determine whether the orientations of an area displayed on the electronic device (101) and the orientations of an image captured by a camera of the electronic device (303) are different from each other.

In operation 1420, based on the determination that the orientations are different, the electronic device (101) may perform operation 1430. In operation 1420, based on the determination that the orientations are the same, the electronic device (101) may terminate the operation of FIG. 14A.

In operation 1430, the electronic device (101) may rotate the image. The electronic device (101) may rotate the image by a rotation amount (e.g., 90 degrees, -90 degrees, or 180 degrees) so that the orientation of the electronic device (101) and the orientation of the electronic device (303) correspond to each other. In one embodiment, the electronic device (101) may rotate the image by a rotation amount so that the orientation of the area displayed on the electronic device (101) and the orientation of the image captured by the camera of the electronic device (303) correspond to each other.

FIG. 14b is a flowchart illustrating the operation of an electronic device according to one embodiment.

The operations of FIG. 14b may be performed in parallel with the operations of FIG. 14a, but are not limited thereto. After the operations of FIG. 14b are performed, the operations of FIG. 14a may be performed. After the operations of FIG. 14a are performed, the operations of FIG. 14b may be performed.

Referring to FIG. 14B, in operation 1440, the electronic device (101) may obtain aspect ratio information of the electronic device (101) and aspect ratio information of the electronic device (303). In one embodiment, the electronic device (101) may obtain aspect ratio information of the electronic device (303) from the electronic device (303). For example, the electronic device (101) may request and obtain aspect ratio information from the electronic device (303), or may obtain the aspect ratio of the electronic device (303) based on a change in orientation of the electronic device (303). In one embodiment, the electronic device (101) may obtain information about an aspect ratio of an area displayed on the electronic device (101) and an aspect ratio of an image captured through a camera of the electronic device (303).

In operation 1450, the electronic device (101) can determine whether the aspect ratios are different. In one embodiment, the electronic device (101) can determine whether the aspect ratio of an area displayed on the electronic device (101) and the aspect ratio of an image captured by a camera of the electronic device (303) are different from each other.

At operation 1450, based on the determination that the aspect ratios are different, the electronic device (101) may perform operation 1460. At operation 1450, based on the determination that the aspect ratios are the same, the electronic device (101) may terminate the operation of FIG. 14b.

In operation 1460, the electronic device (101) may crop the image. In one embodiment, the electronic device (101) may crop the image captured by the camera of the electronic device (303) to an area displayed on the electronic device (101).

FIG. 15A is a diagram illustrating operations of an electronic device for processing an image, according to one embodiment.

In the operations of FIG. 15a, the electronic device (303) may be a sharer device that shares a camera with the electronic device (101), and the electronic device (101) may be a receiver device that uses the camera of the electronic device (303). Substantially simultaneously with the operations of FIG. 15a, the electronic device (303) may be sharing an original image acquired through the camera with the electronic device (101).

Referring to FIG. 15A, in operation 1510, the electronic device (303) can identify camera-related information.

In one embodiment, the camera-related information may include orientation information of the electronic device (303). In one embodiment, the orientation information may indicate how much the electronic device (303) (or the camera of the electronic device (303)) is rotated in a specified direction (e.g., clockwise or counterclockwise) from a normal state (e.g., portrait state). For example, the electronic device (303) may identify the orientation of the electronic device (303) based on a sensor of the electronic device (303) (e.g., the sensor module (176) of FIG. 1) (e.g., an acceleration sensor).

In one embodiment, the camera-related information may include size information (or resolution information) (or aspect ratio information) of an image captured by the camera of the electronic device (303).

In operation 1520, the electronic device (303) may transmit camera-related information to the electronic device (101). The electronic device (303) may transmit camera-related information to the electronic device (101) based on a change in the camera-related information of the electronic device (303). For example, the electronic device (303) may transmit orientation information to the electronic device (101) based on a change in the orientation of the electronic device (303). For example, the electronic device (303) may transmit size information (or resolution information) (or aspect ratio information) to the electronic device (101) based on a change in the size information (or resolution information) (or aspect ratio information) of an image captured by a camera of the electronic device (303).

At operation 1530, the electronic device (101) can compare camera-related information.

In one embodiment, the electronic device (101) can compare the orientation of the electronic device (101) with the orientation of the electronic device (303). In one embodiment, the electronic device (101) can compare the orientation of an area displayed on a recipient device (e.g., electronic device (101)) with the orientation of an image captured through a camera of a sharer device (e.g., electronic device (303)).

In one embodiment, the electronic device (101) can compare the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (101) with the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (303). In one embodiment, the electronic device (101) can compare the size information (or resolution information) (or aspect ratio information) of the area displayed on the recipient device with the size information (or resolution information) (or aspect ratio information) of an image captured through a camera of the sharer device.

At operation 1540, the electronic device (101) can determine whether image processing is required.

For example, the electronic device (101) can determine that image processing is required when the orientation of the electronic device (101) and the orientation of the electronic device (303) are different from each other. For example, the electronic device (101) can determine that image processing is required when the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (101) and the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (303) are different from each other.

In operation 1540, based on determining that image processing is required, the electronic device (101) may perform operation 1550. In operation 1540, based on determining that image processing is not required, the electronic device (101) may perform operation 1560.

In operation 1550, the electronic device (101) may process an image. In one embodiment, the image processing may include cropping the image and/or rotating the image.

For example, the electronic device (101) can crop the image acquired by the camera of the sharer device based on the aspect ratio of the camera requested by the receiver device. If the orientations of the electronic device (101) and the orientations of the electronic device (303) are different, the electronic device (101) can crop the image acquired by the camera of the electronic device (303) based on the inverse aspect ratio of the camera requested by the electronic device (101).

For example, when the orientation of the electronic device (101) and the orientation of the electronic device (303) are different from each other, the electronic device (101) may rotate the cropped image by an amount of rotation (e.g., 90 degrees, -90 degrees, or 180 degrees) so that the orientation of the electronic device (101) and the orientation of the electronic device (303) correspond to each other.

In operation 1560, the electronic device (101) can display an image. For example, if the electronic device (101) is a receiver device, the electronic device (101) can display an image.

FIG. 15b is a diagram illustrating operations of an electronic device for processing an image, according to one embodiment.

In the operations of FIG. 15b, the electronic device (101) may be a sharer device that shares a camera with the electronic device (303), and the electronic device (303) may be a receiver device that uses the camera of the electronic device (101). Substantially simultaneously with the operations of FIG. 15b, the electronic device (101) may acquire an original image through the camera.

Referring to FIG. 15B, in operation 1515, the electronic device (303) may identify camera-related information. In one embodiment, the camera-related information may include orientation information of the electronic device (303) and/or size information (or resolution information) (or aspect ratio information) of an image captured by the camera of the electronic device (303).

In operation 1525, the electronic device (303) may transmit camera-related information to the electronic device (101). The electronic device (303) may transmit camera-related information to the electronic device (101) based on a change in the camera-related information of the electronic device (303).

In operation 1535, the electronic device (101) may compare camera-related information. In one embodiment, the electronic device (101) may compare the orientation of the electronic device (101) with the orientation of the electronic device (303). In one embodiment, the electronic device (101) may compare the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (101) with the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (303).

In operation 1545, the electronic device (101) can determine whether image processing is required. For example, the electronic device (101) can determine that image processing is required when the orientation of the electronic device (101) and the orientation of the electronic device (303) are different from each other. For example, the electronic device (101) can determine that image processing is required when the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (101) and the size information (or resolution information) (or aspect ratio information) of the display area of the electronic device (303) are different from each other.

In operation 1545, based on determining that image processing is required, the electronic device (101) may perform operation 1555. In operation 1545, based on determining that image processing is not required, the electronic device (101) may perform operation 1570.

In operation 1555, the electronic device (101) may process an image. In one embodiment, the image processing may include cropping the image and/or rotating the image.

For example, the electronic device (101) can crop an image acquired by the camera of the electronic device (101), which is a sharer device, based on the aspect ratio of the camera requested by the electronic device (303), which is a receiver device. If the orientations of the electronic device (101) and the orientations of the electronic device (303) are different, the electronic device (101) can crop an image acquired by the camera of the electronic device (101) based on the inverse aspect ratio of the camera requested by the electronic device (303).

For example, when the orientation of the electronic device (101) and the orientation of the electronic device (303) are different from each other, the electronic device (101) may rotate the cropped image by an amount of rotation (e.g., 90 degrees, -90 degrees, or 180 degrees) so that the orientation of the electronic device (101) and the orientation of the electronic device (303) correspond to each other.

In operation 1570, the electronic device (101) can transmit the processed image to the electronic device (303), which is a receiver device.

In operation 1580, the electronic device (303) can display an image.

As described above, the electronic device (101) may include a communication circuit (391) for BLE (Bluetooth low energy). The electronic device (101) may include at least one processor (120) including a processing circuit. The electronic device (101) may include a memory (130) that stores instructions and includes one or more storage media. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive an advertising packet for sharing a hardware component of the other electronic device (303) from another electronic device (303) through the communication circuit (391). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to activate a driver (919) for access to the hardware component indicated by the advertising packet based on the advertising packet being received while the sharing of the hardware component of the electronic device (101) is enabled. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to keep the driver (919) in a disabled state based on the advertising packet being received while the sharing of the hardware component of the electronic device (101) is disabled.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to identify that sharing of the hardware component of the other electronic device (303) is disabled while the driver (919) is activated. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to change the driver (919) to a disabled state in response to identifying that sharing of the hardware component of the other electronic device (303) is disabled.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to execute the client process (1015, 1017, 1019) among the client processes (1015, 1017, 1019) associated with the hardware component and the server processes (1155, 1157, 1159) associated with the hardware component based on the advertisement packet being received while sharing of the hardware component is enabled.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to obtain, through the communication circuit (391), from the other electronic device (303), a signal indicating that the server process (1155, 1157, 1159) executing on the other electronic device (303) is connected to the client process (1015, 1017, 1019). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to register the hardware component with a device manager (935) associated with the hardware component based on obtaining the signal.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to provide a list containing identification information of the hardware components to the application (911) based on identifying a request for a list of types of the hardware components from the application (911).

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to transmit a control request to the client process (1015, 1017, 1019) through the device manager (935) based on identifying a control request of the hardware component from an application (911). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to transmit the control request to the client process (1015, 1017, 1019) through the communication circuit (391) to the server process (1155, 1157, 1159).

The electronic device (101) may include another communication circuit (392) based on a wireless communication technique other than the BLE. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive data acquired by the hardware component from the other electronic device (303) through the other communication circuit (392) while the driver (919) is activated.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to obtain performance information related to the performance of the hardware component from the other electronic device (303) via the communication circuit (391) after the advertisement packet is received while sharing of the hardware component is activated. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to transmit, via the communication circuit (391), to the other electronic device (303) configuration information for configuring the hardware component based on the performance information. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive, via the other communication circuit (392), the data acquired by the hardware component based on the configuration information.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to transmit, via the communication circuit (391), reception status information indicating a reception status of the data to the other electronic device (303). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive, via the other communication circuit (392), the data acquired by the hardware component based on setting information changed based on the reception status information.

The electronic device (101) may include a display. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to display a portion of the image, cropped to correspond to a second aspect ratio, in the area on the display where the image is displayed on the electronic device (101), based on a difference between a first aspect ratio of the image represented by the data and a second aspect ratio of the area on the display where the image is displayed.

The electronic device (101) may include a display. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to display a portion of the image in an area, wherein the portion is rotated to correspond to a second orientation of the image represented by the data, based on a difference between a first orientation of the image and a second orientation of an area on the display in which the image is displayed in the electronic device (101).

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to identify a plurality of hardware components of a specified type based on advertising packets of a plurality of electronic devices received via the communication circuit (391) while the sharing of the hardware components of the electronic device (101) is activated. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to activate the driver (919) for access to the hardware component based on an input for selecting the hardware component of the other electronic device (303) from among the plurality of hardware components of the specified type.

The electronic device (101) may include other communication circuits (392) based on a wireless communication technique other than the BLE. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to transmit data to be output to the hardware component through the other communication circuits (392) while the driver (919) is activated.

As described above, the electronic device (303) may include a communication circuit (393) for BLE (Bluetooth low energy). The electronic device (303) may include at least one processor (311) including a processing circuit. The electronic device (303) may include a memory (315) that stores instructions and includes one or more storage media. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to broadcast an advertisement packet for sharing a hardware component of the electronic device (303) to another electronic device (101) via the communication circuit (393). The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to obtain, from the other electronic device (101) via the communication circuit (393), an access request for the hardware component indicated by the advertising packet. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to connect a server process (1155, 1157, 1159) associated with the hardware component to a client process (1015, 1017, 1019) associated with the hardware component running on the other electronic device (101), based on obtaining the access request. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit, via the communication circuit (393), a signal to the other electronic device (101) indicating that the server process (1155, 1157, 1159) is connected to the client process (1015, 1017, 1019) executing on the other electronic device (101).

The electronic device (303) may include another communication circuit (394) based on a wireless communication technique other than the BLE. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit data acquired by the hardware component to the other electronic device (101) through the other communication circuit (394) while the server process (1155, 1157, 1159) is connected to the client process (1015, 1017, 1019).

The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit, via the communication circuit (393), reception status information indicating a reception status of the data to the other electronic device (303). The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit, via the other communication circuit (394), the data acquired by the hardware component based on setting information changed based on the reception status information.

The electronic device (303) may include other communication circuits (394) based on a wireless communication technique other than the BLE. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to receive data to be output to the hardware component through the other communication circuits (394) while the server process (1155, 1157, 1159) is connected to the client process (1015, 1017, 1019).

As described above, the method can be performed in an electronic device (101) including a communication circuit (391) for BLE (Bluetooth low energy). The method can include an operation of receiving, from another electronic device (303), an advertisement packet for sharing a hardware component of the other electronic device (303) via the communication circuit (391). The method can include an operation of activating a driver (919) for accessing the hardware component indicated by the advertisement packet based on the advertisement packet being received while the sharing of the hardware component of the electronic device (101) is activated. The method can include an operation of maintaining the driver (919) in a deactivated state based on the advertisement packet being received while the sharing is deactivated.

The method may include an operation of executing the client process (1015, 1017, 1019) among the client processes (1015, 1017, 1019) associated with the hardware component and the server processes (1155, 1157, 1159) associated with the hardware component based on the advertisement packet being received while sharing of the hardware component is activated.

The method may include an operation of obtaining, through the communication circuit (391), from the other electronic device (303), a signal indicating that the server process (1155, 1157, 1159) running on the other electronic device (303) is connected to the client process (1015, 1017, 1019). The method may include an operation of registering the hardware component with a device manager (935) associated with the hardware component based on obtaining the signal.

As described above, the method can be performed in an electronic device (303) including a communication circuit (393) for BLE (Bluetooth low energy). The method can include an operation of broadcasting an advertisement packet for sharing a hardware component of the electronic device (303) to another electronic device (101) through the communication circuit (392). The method can include an operation of obtaining, from the other electronic device (101) through the communication circuit (392), an access request for the hardware component indicated by the advertisement packet. Based on obtaining the access request, the method can include an operation of connecting a server process (1155, 1157, 1159) related to the hardware component to a client process (1015, 1017, 1019) related to the hardware component running on the other electronic device (101). The method may include an operation of transmitting a signal to the other electronic device (101) via the communication circuit (392) indicating that the server process (1155, 1157, 1159) is connected to the client process (1015, 1017, 1019) running on the other electronic device (101).

A non-transitory computer readable storage medium as described above can store a program including instructions. The instructions, when individually or collectively executed by at least one processor (120) of an electronic device (101) including a communication circuit (391) for BLE (Bluetooth low energy), can cause the electronic device (101) to receive, through the communication circuit (391), an advertisement packet for sharing a hardware component of the other electronic device (303) from another electronic device (303). The instructions, when individually or collectively executed by the at least one processor (120), can cause the electronic device (101) to activate a driver (919) for access to the hardware component indicated by the advertisement packet based on the advertisement packet being received while the sharing of the hardware component of the electronic device (101) is activated. The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to keep the driver (919) in a disabled state based on the advertisement packet being received while the sharing is disabled.

As described above, a non-transitory computer readable storage medium can store a program including instructions. The instructions, when individually or collectively executed by at least one processor (311) of an electronic device (303) including a communication circuit (393) for BLE (Bluetooth low energy), can cause the electronic device (303) to broadcast an advertisement packet for sharing a hardware component of the electronic device (303) to another electronic device (101) via the communication circuit (393). The instructions, when individually or collectively executed by the at least one processor (311), can cause the electronic device (303) to obtain, from the other electronic device (101) via the communication circuit (393), an access request for the hardware component indicated by the advertisement packet. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to connect a server process (1155, 1157, 1159) associated with the hardware component to a client process (1015, 1017, 1019) associated with the hardware component running on the other electronic device (101), based on the access request being obtained. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit, via the communication circuit (393), a signal to the other electronic device (101) indicating that the server process (1155, 1157, 1159) is connected to the client process (1015, 1017, 1019) running on the other electronic device (101).

As described above, the electronic device (101) may include a communication circuit (391) for wireless communication based on a wireless communication technique, at least one processor (120) including a processing circuit; and a memory (130) storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive, from another electronic device (303) via the communication circuit (391), an advertisement packet including information on a hardware component of the other electronic device (303). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to change, from a deactivated state to an activated state, a program (919) indicating information that enables access to the hardware component indicated by the advertisement packet, based on at least a portion of the information included in the advertisement packet.

The instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to change the program (919) from the activated state to the deactivated state based on other information indicating deactivation of sharing of the hardware component of the other electronic device (303) while the program (919) is activated.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to provide a list containing identification information of the hardware components to the application (911) based on identifying a request for a list of types of the hardware components from the application (911).

The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to transmit the control request to the other electronic device (303) using the program (919) through the communication circuit (391) based on identifying a control request of the hardware component from the application (911).

As described above, the electronic device (101) may include another communication circuit (392) based on a different wireless communication technique than the wireless communication technique described above. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive data acquired by the hardware component from the other electronic device (303) through the other communication circuit (392) while the program (919) is activated.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to identify a request for the data from an application (911) while the program (919) is activated. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to establish a wireless connection with the other electronic device (303) via the other communication circuit (392) based on identifying the request.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to obtain performance information related to the performance of the hardware component from the other electronic device (303) via the communication circuit (391). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to transmit, via the communication circuit (391), to the other electronic device (303) configuration information for configuring the hardware component based on the performance information. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive, via the other communication circuit (392), the data acquired by the hardware component based on the configuration information.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to transmit, via the communication circuit (391), reception status information indicating a reception status of the data to the other electronic device (303). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive, via the other communication circuit (392), the data acquired by the hardware component based on setting information changed based on the reception status information.

The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to identify a plurality of hardware components of a specified type based on advertising packets of a plurality of electronic devices received via the communication circuit (391) while the sharing of the hardware components of the electronic device (101) is activated. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to activate the program (919) based on an input for selecting the hardware component of the other electronic device (303) from among the plurality of hardware components of the specified type.

As described above, the electronic device (101) may include a display. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to identify a user input for a visual object for activating or deactivating the sharing of the hardware component in a user interface (UI) displayed on the display. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to receive the advertising packets of the plurality of electronic devices through the communication circuit (391) while the sharing of the hardware component is activated, based on the user input. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to display another UI on the display, the UI including a list (541) of the plurality of electronic devices identified based on the advertisement packet. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to identify an input for selecting the other electronic device (303) from among the plurality of electronic devices included in the list (541).

As described above, the electronic device (101) may include at least one processor (120) including a first communication circuit (391) for a first wireless communication based on a first wireless communication technique, a second communication circuit (392) for a second wireless communication based on a second wireless communication technique that is distinct from the first wireless communication technique, a display, and a processing circuit; and a memory (130) that stores instructions and includes one or more storage media. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to obtain first information related to a camera from another electronic device (303) while sharing of the camera of the other electronic device (303) is activated through the first communication circuit (391). The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to acquire second information related to the display on which the image acquired by the camera is displayed. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to display, in an area of the display, the image acquired from the other electronic device (303) via the second communication circuit (392) based on a correspondence between the first information and the second information. The instructions, when individually or collectively executed by the at least one processor (120), may cause the electronic device (101) to display, in the area, the image that has been image-processed to correspond to the second information based on a difference between the first information and the second information.

The instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to display the image in the area, rotated to correspond to the second orientation, based on a difference between the first orientation of the image represented by the first information and the second orientation of the area on the display represented by the second information.

The instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to display the image in the area, rotated to correspond to the second orientation, based on a difference between the first orientation of the image represented by the first information and the second orientation of the area on the display represented by the second information.

As described above, the electronic device (303) may include a communication circuit (393) for wireless communication based on a wireless communication technique, at least one processor (311) including a processing circuit; and a memory (315) storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to broadcast an advertisement packet including information of a hardware component of the electronic device (303) to another electronic device (101) via the communication circuit (393). The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to obtain, from the other electronic device (101) via the communication circuit (393), an access request for the hardware component indicated by the advertisement packet. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to associate, based on the access request being obtained, with a program (919) that is associated with the hardware component and that is running on the electronic device (101) and that indicates information that enables access to the hardware component.

As described above, the electronic device (303) may include another communication circuit (394) based on a different wireless communication technique than the above wireless communication technique. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit data acquired by the hardware component to the other electronic device (101) through the other communication circuit (394) while connected to the program (919).

The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit, via the communication circuit (393), reception status information indicating a reception status of the data to the other electronic device (303). The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to transmit, via the other communication circuit (394), the data acquired by the hardware component based on setting information changed based on the reception status information.

As described above, the electronic device (303) may include another communication circuit (394) based on a different wireless communication technique than the wireless communication technique described above. The instructions, when individually or collectively executed by the at least one processor (311), may cause the electronic device (303) to receive data to be output to the hardware component through the other communication circuit (394) while connected to the program (919).

A method performed in an electronic device (101) including a communication circuit (391) for wireless communication based on a wireless communication technique may include an operation of receiving, from another electronic device (303) through the communication circuit (391), an advertisement packet including information on a hardware component of the other electronic device (303). The method may include an operation of changing, from a deactivated state to an activated state, a program (919) indicating information that enables access to the hardware component indicated by the advertisement packet, based on at least a portion of the information included in the advertisement packet.

The method may include changing the program (919) from the activated state to the deactivated state based on other information indicating deactivation of sharing of the hardware component of the other electronic device (303) while the program (919) is activated.

The method may include providing a list containing identification information of the hardware component to the application (911) based on identifying a request for a list of types of the hardware component from the application (911).

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

The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

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

According to one embodiment, the method according to 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 product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read only memory (CD-ROM)), or may be distributed online (e.g., by download or upload) through an application store (e.g., Play Store ^™ ) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

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 (15)

In an electronic device (101), Communication circuit for wireless communication based on wireless communication technique (391), At least one processor (120) comprising a processing circuit; and A memory (130) storing instructions and including one or more storage media, wherein the instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Through the above communication circuit (391), an advertising packet including information on a hardware component of another electronic device (303) is received from another electronic device (303), Causing a program (919) to change from an inactive state to an active state based on at least a portion of the information contained in the advertising packet, the program (919) indicating information that enables access to the hardware component indicated by the advertising packet. Electronic devices. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: While the above program (919) is activated, based on other information indicating deactivation of sharing of the above hardware component of the other electronic device (303), causing the above program (919) to change from the activated state to the deactivated state. Electronic devices. In claim 1 or claim 2, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Based on identifying a request for a list of types of said hardware components from an application (911), causing a list containing identification information of said hardware components to be provided to said application (911). Electronic devices. In any one of claims 1 to 3, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Based on identifying a control request of the hardware component from the application (911), causing the control request to be transmitted to the other electronic device (303) using the program (919) through the communication circuit (391). Electronic devices. In any one of claims 1 to 4, Includes another communication circuit (392) based on another wireless communication technique different from the above wireless communication technique, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: While the above program (919) is activated, causing the hardware component to receive data acquired from the other electronic device (303) through the other communication circuit (392). Electronic devices. In claim 5, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: While the above program (919) is activated, it identifies a request for the above data from the application (911), Based on identifying the above request, causing a wireless connection to be established with the other electronic device (303) through the other communication circuit (392). Electronic devices. In claim 5, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Through the above communication circuit (391), performance information related to the performance of the hardware component is obtained from the other electronic device (303), Through the above communication circuit (391), setting information for setting the hardware component is transmitted to the other electronic device (303) based on the performance information, Causing the hardware component to receive the data acquired based on the setting information through the other communication circuit (392). Electronic devices. In claim 7, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Through the above communication circuit (391), reception status information indicating the reception status of the data is transmitted to the other electronic device (303), Causing the hardware component to receive the data acquired based on the changed setting information based on the reception status information through the other communication circuit (392). Electronic devices. In any one of claims 1 to 8, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: While the sharing of the hardware components of the electronic device (101) is activated, based on the advertising packets of the plurality of electronic devices received through the communication circuit (391), a plurality of hardware components of a specified type are identified, Causing the program (919) to be activated based on an input for selecting the hardware component of the other electronic device (303) among the plurality of hardware components of the above-mentioned type, Electronic devices. In claim 9, Includes a display, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Identifying a user input for a visual object to activate or deactivate the sharing of the hardware component through a user interface (UI) displayed on the display; Based on the user input, while the sharing of the hardware component is activated, the advertising packets of the plurality of electronic devices are received through the communication circuit (391), Displaying another UI on the display including a list (541) of the plurality of electronic devices identified based on the advertising packet, Causing the input to select the other electronic device (303) among the plurality of electronic devices included in the above list (541), Electronic devices. In an electronic device (101), A first communication circuit (391) for a first wireless communication based on a first wireless communication technique, A second communication circuit (392) for a second wireless communication based on a second wireless communication technique that is distinct from the first wireless communication technique; display, At least one processor (120) comprising a processing circuit; and A memory (130) storing instructions and including one or more storage media, wherein the instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Through the first communication circuit (391), while sharing of the camera of the other electronic device (303) is activated from the other electronic device (303), first information related to the camera is acquired, Obtaining second information related to the display on which the image acquired by the camera is displayed, Based on the correspondence between the first information and the second information, the image obtained from the other electronic device (303) is displayed in the area of the display through the second communication circuit (392), Causing the image, which is image-processed to correspond to the second information, to be displayed in the area based on the difference between the first information and the second information. Electronic devices. In claim 11, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Causing the image to be displayed in the area, rotated to correspond to the second orientation, based on the difference between the first orientation of the image indicated by the first information and the second orientation of the area on the display indicated by the second information. Electronic devices. In claim 11 or claim 12, The above instructions, when individually or collectively executed by the at least one processor (120), cause the electronic device (101) to: Causing the image to be displayed in the area, cropped to correspond to the second orientation, based on the difference between the first aspect ratio of the image indicated by the first information and the second aspect ratio of the area on the display indicated by the second information. Electronic devices. In the electronic device (303), Communication circuit for wireless communication based on wireless communication technique (393), At least one processor (311) comprising a processing circuit; and A memory (315) storing instructions and including one or more storage media, wherein the instructions, when individually or collectively executed by the at least one processor (311), cause the electronic device (303) to: Through the above communication circuit (393), an advertising packet including information on the hardware components of the electronic device (303) is broadcast to another electronic device (101), Through the above communication circuit (393), an access request for the hardware component indicated by the advertising packet is obtained from the other electronic device (101), Based on the above access request being obtained, a program (919) that is related to the hardware component and that represents information that enables access to the hardware component, and that runs on the electronic device (101), causes the hardware component to be connected to the hardware component. Electronic devices. In claim 14, Includes another communication circuit (394) based on another wireless communication technique different from the above wireless communication technique, The above instructions, when individually or collectively executed by the at least one processor (311), cause the electronic device (303) to: While connected to the above program (919), causing the hardware component to transmit the data acquired to the other electronic device (101) through the other communication circuit (394). Electronic devices.