Electronic device and method for transmitting and receiving control signals

Abstract

The electronic device according to various embodiments may include: a connector configured to connect with an external electronic device; a memory configured to store instructions; and a processor. The processor is configured to execute the stored instructions to control the electronic device: identify a control signal received through a channel initially activated based on the external electronic device being connected to the connector among a plurality of channels, and perform control based on a message included in the identified control signal.

Description

Technical Field

[0001] The present disclosure relates to an electronic device for transmitting and receiving a control signal and an operating method thereof. Background Art

[0002] The electronic device can transmit and receive control signals with the external electronic device through the allocated channels. Such an electronic device may include a connector provided with data pins, and the data pins are allocated with a plurality of channels by the external electronic device.

[0003] The electronic device can receive a control signal from the external electronic device using a channel allocated by the enumeration operation of the external electronic device. Before the enumeration operation in the external electronic device is completed, the electronic device may not recognize the data received through the plurality of data channels as its own data, and thus may not receive a control signal from the external electronic device.

[0004] The above information is provided as background information only to assist in understanding the present disclosure. No determination or assertion is made as to whether any of the above may be applicable as prior art to the present disclosure. Summary of the invention

[0005] Solution to the problem

[0006] According to an embodiment of the present disclosure, even before the enumeration operation is completed, the electronic device and the operating method thereof according to various embodiments may receive a control signal from the external electronic device.

[0007] The technical advantages achieved by the present disclosure are not limited to those described above, and other technical advantages not mentioned above may be clearly understood by those skilled in the art based on the description provided below.

[0008] An electronic device according to various example embodiments may include: a connector configured to connect to an external electronic device; a memory configured to store instructions; and a processor. The processor is configured to execute the stored instructions, which, when executed by the processor, causes the processor to control the electronic device by identifying a control signal received through a channel initially activated after the external electronic device is connected to the connector among a plurality of channels, and performing control based on a message included in the identified control signal.

[0009] An electronic device according to various example embodiments may include: a connector configured to be electrically connected to an external electronic device; a communication module including a communication circuit configured to communicate with the external electronic device; a memory configured to store instructions; and a processor configured to execute the stored instructions. When an event is received from the other external electronic device, the processor may control the connector to supply power to the external electronic device, and after the power is supplied to the external electronic device, a control signal to be sent through a channel initially activated after the external electronic device is electrically connected to the connector among a plurality of channels may be generated. The connector may be configured to send the generated control signal to the external electronic device so that the external electronic device performs control based on a message included in the generated control signal. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0011] Figure 1 is a block diagram illustrating an example electronic device in a network environment according to various embodiments;

[0012] Figure 2 is a diagram illustrating an example program of an electronic device according to various embodiments;

[0013] Figure 3A are views showing example electronic devices and connectors according to various embodiments;

[0014] Figure 3B is a diagram showing an example connector of an electronic device according to various embodiments;

[0015] Figure 3C is a view showing an example pin structure of a connector of an electronic device according to various embodiments;

[0016] Figure 4A is a block diagram illustrating an example electronic device and an example external electronic device according to various embodiments;

[0017] Figure 4B is a block diagram showing an example of a functional configuration of an electronic device and an external electronic device according to various embodiments;

[0018] Figure 5 is a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments;

[0019] Fig. 6Ais a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments;

[0020] Figure 6B is a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments;

[0021] Figure 6C is a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments;

[0022] Fig.6D is a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments;

[0023] Fig. 6E is a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments;

[0024] Fig. 6F is a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments;

[0025] Figure 7 is a diagram showing example states of an electronic device according to various embodiments;

[0026] Fig. 8A is a view showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments; and

[0027] Figure 8B is a view illustrating an example data transceiving process between an electronic device and an external electronic device according to various embodiments. DETAILED DESCRIPTION

[0028] Figure 1 1 is a block diagram illustrating an electronic device 101 in a network environment 100 according to various embodiments. Figure 1, the electronic device 101 in the network environment 100 may communicate with the electronic device 102 via the first network 198 (e.g., a short-range wireless communication network), or communicate with the electronic device 104 or the server 108 via the second network 199 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 via the server 108. According to an embodiment, the electronic device 101 may include a processor 120, a memory 130, an input device 150, a sound output device 155, a display device 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 user identification module (SIM) 196, or an antenna module 197. In some embodiments, at least one of the components (e.g., the display device 160 or the camera module 180) may be omitted from the electronic device 101, or one or more other components may be added to the electronic device 101. In some embodiments, some of the components may be implemented as a single integrated circuit.For example, the sensor module 176 (eg, a fingerprint sensor, an iris sensor, or an illumination sensor) may be implemented to be embedded in the display device 160 (eg, a display).

[0029] The processor 120 may run, for example, software (e.g., program 140) to control at least one other component (e.g., hardware component or software component) of the electronic device 101 connected to the processor 120, and may perform various data processing or calculations. According to an example embodiment, as at least part of the data processing or calculation, the processor 120 may load a command or data received from another component (e.g., sensor module 176 or communication module 190) into the volatile memory 132, process the command or data stored in the volatile memory 132, and store the resultant data in the non-volatile memory 134. According to an embodiment, the processor 120 may include a main processor 121 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 123 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is independent of or combined with the main processor 121 in operation. Additionally or alternatively, the auxiliary processor 123 may be adapted to consume less power than the main processor 121, or adapted to be specifically used for a specified function. The auxiliary processor 123 may be implemented separately from the main processor 121 , or as part of the main processor 121 .

[0030] When the main processor 121 is in an inactive (e.g., sleep) state, the auxiliary processor 123 may control at least some of the functions or states related to at least one component (e.g., display device 160, sensor module 176, or communication module 190) among the components of the electronic device 101 (not the main processor 121), or when the main processor 121 is in an active state (e.g., running an application), the auxiliary processor 123 may control at least some of the functions or states related to at least one component (e.g., display device 160, sensor module 176, or communication module 190) among the components of the electronic device 101 together with the main processor 121. According to an embodiment, the auxiliary processor 123 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., camera module 180 or communication module 190) that is functionally related to the auxiliary processor 123.

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

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

[0033] The input device 150 may receive commands or data from outside the electronic device 101 (eg, a user) to be used by other components of the electronic device 101 (eg, the processor 120). The input 150 may include, for example, a microphone, a mouse, a keyboard, or a digital pen (eg, a stylus).

[0034] The sound output device 155 can output a sound signal to the outside of the electronic device 101. The sound output 155 may include, for example, a speaker or a receiver. The speaker may be used for general purposes such as playing multimedia or playing records, and the receiver may be used for incoming calls. Depending on the embodiment, the receiver may be implemented as a separate part from the speaker, or as part of the speaker.

[0035] The display device 160 may visually provide information to the outside of the electronic device 101 (e.g., a user). The display device 160 may include, for example, a display, a holographic device, or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. According to an embodiment, the display device 160 may include a touch circuit adapted to detect a touch or a sensor circuit (e.g., a pressure sensor) adapted to measure the strength of a force caused by a touch.

[0036] The audio module 170 may convert sound into an electrical signal, or vice versa. According to an embodiment, the audio module 170 may obtain sound via the input device 150, or output sound via the sound output device 155 or an earphone of an external electronic device (e.g., electronic device 102) directly (e.g., wired) or wirelessly connected to the electronic device 101.

[0037] The sensor module 176 may detect an operating state (e.g., power or temperature) of the electronic device 101 or an environmental state (e.g., a state of a user) outside the electronic device 101, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.

[0038] The interface 177 may support one or more specific protocols to be used to connect the electronic device 101 directly (e.g., wired) or wirelessly to an external electronic device (e.g., the electronic device 102). According to an embodiment, the interface 177 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0039] The connection end 178 may include a connector, wherein the electronic device 101 can be physically connected to an external electronic device (e.g., the electronic device 102) via the connector. According to an embodiment, the connection end 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0040] The haptic module 179 may convert the electrical signal into mechanical stimulation (eg, vibration or motion) or electrical stimulation that can be recognized by the user via his sense of touch or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0041] The camera module 180 may capture still images or moving images. According to an embodiment, the camera module 180 may include one or more lenses, an image sensor, an image signal processor, or a flash.

[0042] The power management module 188 may manage power supply to the electronic device 101. According to example embodiments, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0043] The battery 189 may power at least one component of the electronic device 101. According to an embodiment, the battery 189 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0044] The communication module 190 may support establishing 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 perform communication via the established communication channel. The communication module 190 may include one or more communication processors capable of operating independently from the processor 120 (e.g., an application processor (AP)) and supporting direct (e.g., wired) communication or wireless communication. According to an 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 (PLC) module). A corresponding one of these communication modules can communicate with an external electronic device via a first network 198 (e.g., a short-range communication network such as Bluetooth, Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA)) or a second network 199 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules can be implemented as a single component (e.g., a single chip), or these various types of communication modules can be implemented as multiple components separated from each other (e.g., multiple chips). The wireless communication module 192 can identify and authenticate the electronic device 101 in a communication network (such as the first network 198 or the second network 199) using user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 196.

[0045] The antenna module 197 may transmit or receive a signal or power to or from the outside of the electronic device 101 (e.g., an external electronic device). According to an embodiment, the antenna module 197 may include an antenna including a radiating element formed of a conductive material or a conductive pattern formed in or on a substrate (e.g., a PCB). According to an embodiment, the antenna module 197 may include a plurality of antennas. In this case, at least one antenna suitable for a communication scheme used in a communication network (such as the first network 198 or the second network 199) may be selected from the plurality of antennas by, for example, the communication module 190 (e.g., the wireless communication module 192). A signal or power may then be transmitted or received between the communication module 190 and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as a part of the antenna module 197.

[0046] At least some of the above components may be connected to each other via an inter-peripheral communication scheme (e.g., a bus, a general purpose input output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) and communicatively transmit signals (e.g., commands or data) therebetween.

[0047] According to an embodiment, a command or data may be sent or received between the electronic device 101 and the external electronic device 104 via the server 108 connected to the second network 199. Each of the electronic device 102 and the electronic device 104 may be a device of the same type as the electronic device 101, or a device of a different type from the electronic device 101. According to an embodiment, all or some operations to be executed in the electronic device 101 may be executed in one or more of the external electronic device 102, the external electronic device 104, or the server 108. For example, if the electronic device 101 should automatically execute a function or service or should execute a function or service in response to a request from a user or another device, the electronic device 101 may request the one or more external electronic devices to execute at least part of the function or service instead of executing the function or service, or the electronic device 101 may request the one or more external electronic devices to execute at least part of the function or service in addition to executing the function or service. The one or more external electronic devices that receive the request may execute the requested at least part of the function or service, or execute another function or another service related to the request, and transmit the result of the execution to the electronic device 101. The electronic device 101 may provide the result as at least a partial reply to the request with or without further processing the result. To this end, for example, cloud computing technology, distributed computing technology, or client-server computing technology may be used.

[0048] The electronic device according to various embodiments may be one of various types of electronic devices. The electronic device may include, for example, but not limited to, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance, etc. According to an embodiment of the present disclosure, the electronic device is not limited to those electronic devices described above.

[0049] It should be understood that the various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, but rather include various changes, equivalents or alternative forms for the corresponding embodiments. For the description of the drawings, similar reference numerals may be used to refer to similar or related elements.

[0050] It will be understood that a noun corresponding to a term in the singular may include one or more things unless the relevant context clearly indicates otherwise. As used herein, each of phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B or C" may include any one or all possible combinations of the items listed with the corresponding one of the plurality of phrases. As used herein, terms such as "1st" and "2nd" or "first" and "second" may be used to simply distinguish a corresponding component from another component and do not limit the components in other respects (e.g., importance or order). It will be understood that if an element (e.g., a first element) is referred to as being "coupled with another element (e.g., a second element)", "coupled to another element (e.g., the second element)", "connected with another element (e.g., the second element)" or "connected to another element (e.g., the second element)" when the terms "operably" or "communicatively" are used or when the terms "operably" or "communicatively" are not used, the element may be directly (e.g., wired) connected to the other element, wirelessly connected to the other element, or connected to the other element via a third element.

[0051] As used herein, the term "module" may include units implemented in hardware, software, firmware, or any combination thereof, and may be used interchangeably with other terms (e.g., "logic," "logic block," "portion," or "circuit"). A module may be a single integrated component adapted to perform one or more functions or a minimum unit or portion of the single integrated component. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).

[0052] The various embodiments described herein may be implemented as software (e.g., program 140) including one or more instructions stored in a storage medium (e.g., internal memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101). For example, under the control of a processor, a processor (e.g., processor 120) of the machine (e.g., electronic device 101) may call at least one of the one or more instructions stored in the storage medium and execute the at least one instruction with or without the use of one or more other components. This enables the machine to operate to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be run by an interpreter. A machine-readable storage medium may be provided in the form of a non-transitory storage medium. Among them, a "non-transitory" storage medium is a tangible device and does not include a signal (e.g., an electromagnetic wave), but the term does not distinguish between data being semi-permanently stored in a storage medium and data being temporarily stored in a storage medium.

[0053] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be released in the form of a machine-readable storage medium (e.g., a compact disk read-only memory (CD-ROM)), or may be downloaded via an application store (e.g., Play Store TM ) The computer program product may be published (e.g., downloaded or uploaded) online, or the computer program product may be distributed (e.g., downloaded or uploaded) directly between two user devices (e.g., smart phones). If published online, at least part of the computer program product may be temporarily generated, or at least part of the computer program product may be at least temporarily stored in a machine-readable storage medium (such as a memory of a manufacturer's server, an application store's server, or a forwarding server).

[0054] According to various embodiments, each component (e.g., module or program) in the above-mentioned components may include a single entity or multiple entities. According to various embodiments, one or more components in the above-mentioned components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform the one or more functions of each component in the multiple components in the same or similar manner as a corresponding component in the multiple components before integration. According to various embodiments, the operations performed by a module, program or another component may be performed sequentially, in parallel, repeatedly or in a heuristic manner, or one or more operations in the operations may be run or omitted in different orders, or one or more other operations may be added.

[0055] Figure 2 2 is a block diagram 200 showing an example program 140 according to various embodiments. According to an embodiment, the program 140 may include an operating system (OS) 142 for controlling one or more resources of the electronic device 101, middleware 144, or an application 146 that can be executed in the OS 142. The OS 142 may include, for example, an Android TM 、iOS TM , Windows TM , Symbian TM 、Tizen TM or Bada TM . For example, at least a portion of the program 140 may be preloaded onto the electronic device 101 during manufacturing, or at least a portion of the program 140 may be downloaded from an external electronic device (e.g., electronic device 102 or electronic device 104, or server 108) or updated by an external electronic device during user use. According to an embodiment, the program 140 may also include a boot loader (not shown) that is used to drive an operating system 142 to boot the electronic device 101. According to an embodiment, the boot loader (not shown) may also include a command center rear (CCR) driver (e.g., CCR driver 431 of FIG. 4 ) that is used to drive a universal serial bus (hereinafter referred to as "USB") module (not shown) (or USB controller).

[0056] OS 142 may control the management (e.g., allocation or deallocation) of one or more system resources (e.g., processes, memory, or power) of electronic device 101. Additionally or alternatively, OS 142 may include one or more drivers for driving other hardware devices (e.g., input device 150, sound output device 155, display device 160, audio module 170, sensor module 176, interface 177, tactile module 179, camera module 180, power management module 188, battery 189, communication module 190, user identification module 196, or antenna module 197) of electronic device 101. According to an embodiment, operating system 142 may also include a CCR driver (e.g., CCR driver 431 of FIG. 4) to drive a USB module (not shown) (or USB controller). According to an embodiment, operating system 142 may include at least one CCR driver. According to an embodiment, at least one CCR driver (not shown) included in operating system 142 may be different from a CCR driver (not shown) included in a boot loader (not shown). According to an embodiment, a CCR driver (not shown) included in a boot loader (not shown) may include an instruction for processing a command (e.g., at least one of a restart command (REBOOT CMD), a start command (START UP), or a combination thereof) received from the external electronic device 102 through an initially activated channel. According to an embodiment, a CCR driver (not shown) included in a boot loader (not shown) may include an instruction for transitioning the electronic device 101 from a power-off state to a charging state when power is supplied from the external electronic device 102, in which the operating system according to the low power mode is driven. According to an embodiment, at least one CCR driver (not shown) included in the operating system 142 may include receiving an instruction from the external electronic device 102 through an initially activated channel, the instruction being used to process a command (e.g., a start command (STARTUP CMD), a shutdown command (SHUT DOWN CMD), a wake-up command (WAKE UP CMD), a sleep command (SLEEP CMD), a restart (REBOOT CMD), a CCR state transmission command (CCR STATE T / F CMD), a battery status transmission command (BATTERYSTATUS T / F CMD), an application status transmission command (APP STATUS T / F CMD), or at least one of a combination thereof).

[0057] The middleware 144 may provide various functions to the application 146 so that the application 146 can use functions or information provided from one or more resources of the electronic device 101. The middleware 144 may 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 connection manager 215, a notification manager 217, a location manager 219, a graphic manager 221, a security manager 223, a telephony manager 225, or a voice recognition manager 227.

[0058] The application manager 201 may, for example, manage the life cycle of the application 146. The window manager 203 may, for example, manage one or more graphical user interface (GUI) resources used on the screen. The multimedia manager 205 may, for example, identify one or more formats to be used for playing a media file, and may encode or decode a corresponding media file among the media files using a codec suitable for a corresponding format selected from the one or more formats. The resource manager 207 may, for example, manage the source code of the application 146 or the storage space of the memory 130. The power manager 209 may, for example, manage the capacity, temperature, or power of the battery 189, and may determine or provide relevant information to be used for the operation of the electronic device 101 based at least in part on the corresponding information of the capacity, temperature, or power of the battery 189. According to an embodiment, the power manager 209 may work in conjunction with a basic input / output system (BIOS) (not shown) of the electronic device 101.

[0059] The database manager 211 may, for example, generate, search for, or change a database to be used by the application 146. The package manager 213 may, for example, manage the installation or update of applications distributed in the form of package files. The connection manager 215 may, for example, manage a wireless connection or a direct connection between the electronic device 101 and an external electronic device. The notification manager 217 may, for example, provide a function for notifying a user of the occurrence of a specific event (e.g., an incoming call, message, or alarm). The location manager 219 may, for example, manage location information about the electronic device 101. The graphic manager 221 may, for example, manage one or more graphic effects to be provided to the user or a user interface related to the one or more graphic effects.

[0060] The security manager 223 may, for example, provide system security or user authentication. The phone manager 225 may, for example, manage a voice call function or a video call function provided by the electronic device 101. The voice recognition manager 227 may, for example, send the user's voice data to the server 108, and receive from the server 108 a command corresponding to a function that runs on the electronic device 101 based at least in part on the voice data or text data converted at least in part on the voice data. According to an embodiment, the middleware 144 may dynamically delete some existing components or add new components. According to an embodiment, at least a portion of the middleware 144 may be included as a part of the OS 142, or at least a portion of the middleware 144 may be implemented as another software separated from the OS 142.

[0061] Applications 146 may include, for example, a home page 251, a dialer 253, a short message service (SMS) / multimedia message service (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., for measuring exercise level or bio-information (such as blood sugar)) or an environmental information 281 (e.g., for measuring air pressure, humidity or temperature information) application. According to an embodiment, application 146 may also include an information exchange application (not shown) capable of supporting information exchange between the electronic device 101 and an external electronic device. The information exchange application may, for example, include a notification forwarding application suitable for transmitting specified information (e.g., a call, message or alarm) to an external electronic device or a device management application suitable for managing an external electronic device. The notification forwarding application may transmit notification information corresponding to a specific event (e.g., receipt of an email) occurring in another application (e.g., email application 269) of the electronic device 101 to an external electronic device. Additionally or alternatively, the notification forwarding application may receive notification information from the external electronic device and provide the notification information to a user of the electronic device 101.

[0062] The device management application may control the power (e.g., turning on or off) or functions (e.g., adjustment of brightness, resolution, or focus) of the external electronic device or some components of the external electronic device (e.g., a display device or a camera module of the external electronic device). Additionally or alternatively, the device management application may support installation, deletion, or updating of applications running on the external electronic device.

[0063] Figure 3A is a diagram illustrating an example electronic device 301 and a connector 310 according to various embodiments.

[0064] Figure 3B 3 is a diagram illustrating example connectors 310 and 350 of an electronic device according to various embodiments.

[0065] Figure 3C is a view showing an example pin structure of a connector 310 of an electronic device according to various embodiments.

[0066] refer to Figure 3A In various embodiments, the electronic device 310 may include a connector 310, an external electronic device (eg, Figure 1 The external electronic device 102 shown is connected via the connector 310. In various embodiments, the electronic device 301 may be included in Figure 1 In the electronic device 101 shown. Figure 3A The electronic device 301 is depicted as a portable electronic device such as a smart phone, a tablet computer, etc., but the electronic device 301 is not limited thereto, and any electronic device provided with a connector for connecting to an external electronic device and transmitting and receiving data with the external electronic device connected through the connector can be interpreted as Figure 3A electronic device 301.

[0067] refer to Figure 3A According to various embodiments, the electronic device 301 may include an opening formed on one surface of a housing and a hole connected to the opening, and may have a connector 310 disposed in the hole. Figure 3A As shown, the opening and the hole can be formed on one surface of the lower side of the housing of the electronic device 301, and the connector 310 can be disposed in the opening and the hole. However, the arrangement position of the connector 310 is not limited thereto, and the connector 310 can be, for example, disposed on other surfaces of the housing of the electronic device 310.

[0068] According to various embodiments, the connector 350 of the external electronic device may be inserted into the connector 310 of the electronic device 301. The type of the external electronic device is not limited, and all devices including a battery pack that supplies power to the electronic device 301, a device that communicates with the electronic device 301, or an external memory connected to the electronic device 301 may correspond to the external electronic device.

[0069] According to various embodiments, the connector 350 of the external electronic device may be received through the hole, may physically contact the connector 310 of the electronic device 301, and may be electrically connected according to the physical contact. According to various embodiments, the connector 310 of the electronic device 301 and the hole structure may be a reversible structure. For example, the connector 310 may be symmetrical with respect to a first direction perpendicular to the direction in which the external electronic device is inserted (e.g., a direction from the bottom to the top of the electronic device) and a second direction opposite to the first direction.

[0070] Reference Figure 3B, the connector 350 of the external electronic device can be inserted into the connector 310 of the electronic device 301 with one surface of the connector 350 (for example, surface A) parallel to the front surface of the electronic device 301 (for example, the surface on which the display is provided), or the connector 350 of the external electronic device can be inserted with the other surface of the connector 350 (for example, surface B) parallel to the front surface of the electronic device 301.

[0071] In various embodiments, the connector 310 may include a plurality of ends, and when the connector 350 of the external electronic device is inserted in different directions, respective ends of the external electronic device electrically connected to the ends of the connector 310 of the electronic device 301 may be different.

[0072] According to various embodiments, the connector 310 may be, for example, a connector complying with the Universal Serial Bus (USB) (hereinafter referred to as “USB”) standard, and may be, for example, a connector complying with the USB Type-C standard. However, various embodiments of the present disclosure are not limited to the USB Type-C, and may be applicable to connectors complying with USB-related standards (e.g., but not limited to USB Type-B, USB Type-A), wired interfaces of various standards (e.g., but not limited to a lightning port, a high-definition multimedia interface (HDMI), a recommended standard 232 (RS-232), power line communication, a plain telephone service (POTS), or a non-standard wired interface, etc.). Various embodiments of the present disclosure are applicable to any interface that can transmit data (e.g., data transmitted from a CC1 pin or a CC2 pin included in the Type-C standard) for automatically detecting what type of device is connected between a source device (e.g., a device that provides power) and a synchronization device (e.g., a device that receives power) or between a downstream facing port (DFP) (e.g., a device that provides data) and an upstream facing port (UFP) (e.g., a device that receives data).

[0073] Figure 3C is a diagram showing an example of a plurality of terminals provided in a connector 310 when a connector 310 of an electronic device (eg, electronic device 301 ) complies with the USB Type-C standard.

[0074] refer to Figure 3C , the connector 310 may include 12 terminals (or pins) in each of the left line A and the right line B, and may be symmetrical.

[0075] In various embodiments, data may be transmitted between the electronic device 301 and the external electronic device through the sixth and seventh data pins (or D+ pin and D- pin) in the line A located on the left side of the connector 310 or the sixth and seventh data pins (or D+ pin and D- pin) in the line B located on the right side. The electronic device 301 may be powered from the external electronic device through the power pin (or VBUS pin) at the fourth position of the line A located on the left side of the connector 310. Since the role of the terminal in various operation modes is defined according to the USB Type-C standard, the role of the terminal will not be described.

[0076] In various embodiments, when the electronic device 310 and the external electronic device are connected to each other, electrical signals (e.g., digital ID or resistance ID) may be exchanged through the CC1 pin and the CC2 pin, and thus, the electronic device and the external electronic device may detect the type of other device connected thereto. In addition, according to the result of detecting the connected device, the electronic device may operate in a downstream port (DFP) mode or an upstream port (UFP) mode. The DFP mode may refer to a mode in which data is provided, and the UFP mode may refer to a mode in which data is received.

[0077] Figure 4A is a block diagram illustrating an example electronic device 401 and an example external electronic device 402 according to various embodiments.

[0078] According to various embodiments, the electronic device 401 may be at least partially connected to Figure 1 The electronic device 101 shown, Figure 2 The electronic device 202 shown is the same as the electronic device 301 shown in FIG. 3 .

[0079] refer to Figure 4A In various embodiments, the electronic device 401 may include a connector 410, a power delivery integrated circuit (PDIC) 420 (hereinafter referred to as "PDIC"), a processor (e.g., a built-in processing circuit) 430, a battery 440, a memory 491, a display 497, or any combination thereof. In various embodiments, some elements may be omitted. In various embodiments, the electronic device 401 may be referred to as a command center rear (CCR) (hereinafter referred to as "CCR"). In various embodiments, the battery 440 may be included in Figure 1 In various embodiments, the memory 491 may be included in the battery 189 shown. Figure 1 In various embodiments, the display 497 may be included in the memory 130. Figure 1In the display device 160 shown. In various embodiments, the electronic device 401 may further include a controller (not shown). In various embodiments, the controller (not shown) (eg, a USB controller) may be connected between the connector 410 and the processor 430.

[0080] In various embodiments, connector 410 may include Figure 1 The connection end 178 shown, or may be included in Figure 3A , Figure 3B and Figure 3C In the connector 310 shown, the present disclosure is not limited thereto. In various embodiments, the connector 410 may include various types of pins (e.g., Figure 3C In various embodiments, the connector 410 can be electrically connected to the connector 450 of the external electronic device 402 through various types of pins. In various embodiments, the connector 410 can be electrically connected to the connector 450 of the external electronic device 402 through power pins (e.g., Figure 3C The VBUS pin of the connector 310 shown in the figure) receives power from the connector 450 of the external electronic device 402. In various embodiments, the connector 410 can receive power through the data pin (e.g., Figure 3C The connector 410 may transmit data transmission speed information of the electronic device 401 to the connector 450 of the external electronic device 402 (at least one of the D+ pin, the D- pin, or a combination thereof of the connector 310 shown in FIG. 4 ). In various embodiments, the connector 410 may transmit data to the connector 450 of the external electronic device 402, or may receive data from the connector 450 of the external electronic device 402 through the data pin.

[0081] In various embodiments, the PDIC 420 may be electrically connected to the connector 410. In various embodiments, the PDIC 420 may be, for example, a power delivery circuit of the USB Type-C standard. In various embodiments, the PDIC 420 may include at least one of a configuration channel (CC) (hereinafter referred to as “CC”) logic (not shown), a power delivery (PD) (hereinafter referred to as “PD”) logic (not shown), or a combination thereof. In various embodiments, the PDIC 420 may be connected to the CC pin (e.g., Figure 3CIn various embodiments, the PDIC 420 may be electrically connected to the processor 430. In various embodiments, the PDIC 420 may transmit the PD message received from the external electronic device 420 to the processor 430. In various embodiments, the PD message may include at least one of the following: data on the number of data objects, a power role of the electronic device (e.g., information on whether to provide power to the external electronic device or to receive power from the external electronic device), a version of the PD specification of the electronic device, and a data role of the electronic device 410 (e.g., information on whether to send data to the external electronic device or to receive data from the external electronic device).

[0082] In various embodiments, processor 430 may be included in Figure 1 In various embodiments, processor 430 may include various processing circuits and may be configured based on a power supply pin (e.g., Figure 3C ), the voltage applied to the data pins (e.g., Figure 3C The connection with the external electronic device 402 is identified by at least one of the voltages of the D+ pin or the D- pin) or a combination thereof.

[0083] In various embodiments, when the electronic device 401 is connected to the external electronic device 402, the processor 430 may receive a command from the external electronic device 410 through the initially activated channel. In various embodiments, the processor 430 may control the electronic device 401 to send a response to the command received through the initially activated channel to the external electronic device 402 through the initially activated channel. In various embodiments, the initially activated channel may be a communication channel for at least one of the multiple channels between the electronic device 401 and the external electronic device 402 for US enumeration, USB configuration, or a combination thereof. In various embodiments, the data sent and received through the initially activated channel may be data having a set endpoint address among the data sent and received through the data pin of the connector 410. In various embodiments, the data sent and received through the initially activated channel may be data indicating endpoint 0. For example, the endpoint of the initially activated channel may be 0. However, this should not be considered as a limitation.

[0084] In various embodiments, when the electronic device 401 is connected to the external electronic device 402, the processor 430 may receive a descriptor transfer command from the external electronic device 402 through an initially activated channel. In various embodiments, the processor 430 may receive a descriptor transfer command when driving an operating system (e.g., Figure 2In various embodiments, the processor 430 may receive a descriptor transfer command from the external electronic device 402 through the initially activated channel before the operating system 142 shown in FIG. 1 is used. In response to the descriptor transfer command, the processor 430 may transmit the descriptor to the external electronic device 402 through a CCR driver (e.g., Figure 4B 4) to load the descriptor stored in the memory 491. In various embodiments, in response to the descriptor transfer command, the processor 430 may send the loaded descriptor to the external electronic device 402 through the initially activated channel. In various embodiments, the descriptor may include at least one of classification information of the electronic device 401, USB specification information, size information of data that can be transceived through the initially activated channel, required power information, or a combination thereof.

[0085] In various embodiments, processor 430 may be operable to drive an operating system (e.g., Figure 2 142 shown in the operating system 142, the processor 430 receives a channel configuration command generated by the external electronic device 402 based on the external descriptor 142 from the external electronic device 402 through the initially activated channel. In various embodiments, the processor 430 may receive a command from the external electronic device 401 through at least one of the initially activated channel, the channel allocated according to the channel configuration command, or a combination thereof, and may send a response to the command to the external electronic device 402. In various embodiments, even after the channel is allocated according to the channel configuration command, the processor 430 may exchange data with the external electronic device 402 through the initially activated channel. In various embodiments, even in the operating system (e.g., Figure 2 After the operating system 142 shown in FIG. 1 is driven, the processor 430 may also exchange data with the external electronic device 402 through the initially activated channel.

[0086] In various embodiments, the processor 430 may receive a control command from the external electronic device 402 through the initially activated channel. In various embodiments, the processor 430 may execute instructions stored in the memory 491 based on the control command. In various embodiments, the processor 430 may send a response to the control command to the external electronic device 402 through the initially activated channel. In various embodiments, the control command may include at least one of the following: a start command (START UP CMD), a shutdown command (SHUT DOWN CMD), a wake-up command (WAKE UP CMD), a sleep command (SLEEP CMD), a restart (REBOOT CMD), a CCR state transmission command (CCR STATE T / F CMD), a battery state transmission command (BATTERY STATUS T / FCMD), an application state transmission command (APP STATUS T / F CMD), or a combination thereof. Various embodiments of the operation of the control command will be described below.

[0087] Reference Figure 4A In various embodiments, the external electronic device 402 may include at least one of the following: a connector 450, a PDIC 460, a processor (e.g., including a processing circuit) 470, a communication module (e.g., including a communication circuit) 480, a power module (e.g., including a power circuit) 490, a memory 495, or any combination thereof. In various embodiments, some elements may be omitted. In various embodiments, the external electronic device 402 may be included in Figure 1 In various embodiments, the external electronic device 402 may be referred to as a command center rear adapter (CCR AD) (hereinafter referred to as "CCR AD"). In various embodiments, the memory 491 may be included in Figure 1 In various embodiments, the external electronic device 402 may further include a controller (not shown). In various embodiments, the controller (not shown) may be connected between the connector 450 and the processor 470.

[0088] In various embodiments, the connector 450 may be an element corresponding to the connector 410 of the electronic device 401. For example, when the connector 410 of the electronic device 401 is a female connector, the connector 450 may be a male connector. In various embodiments, the connector 450 may be included in Figure 3B In various embodiments, connector 450 may include various types of pins corresponding to connector 410 (e.g., Figure 3C 310 pins as shown).

[0089] In various embodiments, the PDIC 460 may be an element corresponding to the PDIC 420 of the electronic device 401. In various embodiments, the PDIC 460 may be electrically connected to the connector 450. In various embodiments, the PDIC 460 may include at least one of CC logic, PD logic, or a combination thereof. In various embodiments, the PDIC 460 may send and receive PD messages to the electronic device 401 electrically connected via the CC pin of the connector 450. In various embodiments, the PDIC 460 may be electrically connected to the processor 470. In various embodiments, the PDIC 460 may pass the PD message received from the electronic device 401 to the processor 470.

[0090] In various embodiments, processor 470 may be included in Figure 1 In the processor 120 shown. In various embodiments, the processor 470 may include various processing circuits, and generate a control message for the electronic device 401 in response to an event notification of the external electronic device 403 received through the communication module 480. In various embodiments, the processor 470 may generate a control message for the electronic device 401 in response to an event notification occurring by a user pressing an input button (not shown) (e.g., a power key). In various embodiments, the input button (not shown) may be a physical button protruding to the outside through a housing (not shown) of the external electronic device 402. In various embodiments, the processor 470 may generate a control message for the electronic device 401 based on a set condition (e.g., a set time interval). In various embodiments, the processor 470 may send a control message to the electronic device 401 through an initially activated communication channel.

[0091] In various embodiments, the power module 490 may be electrically connected to the connector 450. In various embodiments, the power module 490 may include various power circuits and apply a set voltage (e.g., 5V) to the power pin of the connector 450. In various embodiments, when the connector 410 of the electronic device 401 is connected to the connector 450, the power module 490 may supply power to the electronic device 401 by applying a set current (e.g., 1A) to the power pin of the connector 450. In various embodiments, the power module 490 may receive power from at least one of another external electronic device (e.g., a battery of a car), a battery embedded in the external electronic device (not shown), or a combination thereof. In various embodiments, the power module 490 may be included in Figure 1 In the power management module 188 shown.

[0092] The communication module 480 may include various communication circuits and communicate with the external electronic device 403. In various embodiments, the communication module 480 may receive at least one of an event notification of the external electronic device 403, an event notification of the car in which the external electronic device 403 is installed, or a combination thereof from the external electronic device 403. In various embodiments, the communication module 480 may send the received event notification to the processor 470. In various embodiments, the communication module 480 may receive from the processor 470 a command of the electronic device 401 received by the processor 470 through the connector 450 (e.g., a window opening command, a window closing command, an interior light opening command, an interior light closing command, a volume control command). In various embodiments, the communication module 480 may send the received command of the electronic device 401 to the external electronic device 403. In various embodiments, the communication module 480 may communicate with the external electronic device 403 via a controller area network (CAN) (hereinafter referred to as "CAN"). However, this should not be considered as limiting. In various embodiments, the communication module 480 may be included in Figure 1 In the communication module 190 shown.

[0093] refer to Figure 4A , the external electronic device 403 can communicate with the external electronic device 402. In various embodiments, the external electronic device 403 can be configured as a car audio body, for example. In various embodiments, the external electronic device 403 can be an electronic device installed in a car.

[0094] Figure 4B 401 and 403 are diagrams showing examples of functional configurations of an electronic device 401 and external electronic devices 402 and 403 according to various embodiments.

[0095] refer to Figure 4B In various embodiments, the external electronic device 402 may be connected to the external electronic device 402 through a communication module (eg, Figure 4A The communication module 480 of the external electronic device 402 communicates with the external electronic device 403. In various embodiments, the processor of the external electronic device 402 (eg, Figure 4A The processor 470 may include various processing circuits and may drive the memory (e.g., Figure 4A The processor of the external electronic device 402 may send a command to the electronic device 401 through the CCR AD driver 461.

[0096] Reference Figure 4B In various embodiments, the processor of the electronic device 401 (eg, Figure 4AThe processor 430 may include various processing circuits and drive the memory (e.g., Figure 4A In various embodiments, the processor of the electronic device 401 may generate an event regarding a command received from the external electronic device 402 through the CCR driver 431 of the kernel 432, and may send the event to the custom protocol manager 433 of the framework 434. In various embodiments, the event may be a message to be passed from the kernel 432 in which the CCR driver 431 is driven to the framework 434. In various embodiments, the kernel 432, the framework 434, and the application 435 may be included in the program 436. In various embodiments, the kernel 432 may be included in Figure 2 In the operating system 142, the framework 434 may be included in Figure 2 In the middleware 144, the application 435 may be included in Figure 2 of the application, and procedure 436 may be included in Figure 2 140, but these should not be considered limiting.

[0097] refer to Figure 4B In various embodiments, the custom protocol manager 433 of the framework of the processor of the electronic device 401 may pass a message corresponding to the event to the application 435 of the event. In various embodiments, the custom protocol manager 433 of the framework may pass a response message to the event to the CCR driver 431 through a virtual file system (e.g., Sysfs) node. In various embodiments, the virtual file system (e.g., Sysfs) node may be a pseudo file system for providing an interface for the kernel 432. In various embodiments, the Sysfs node may be a pseudo file system provided by the Linux kernel.

[0098] refer to Figure 4B In various embodiments, the processor of the electronic device 401 may transmit a response message to the event to the external electronic device 402 through the CCR driver.

[0099] Figure 5 is a view illustrating an example data transceiving process between an electronic device 401 and an external electronic device 402 according to various embodiments.

[0100] refer to Figure 5 In operation 511, the processor 470 of the external electronic device 402 according to various embodiments may send a command (CMD) (hereinafter referred to as “CMD”) to the electronic device 401. In operation 515, the processor 430 of the electronic device 401 may send an acknowledgement (ACK) (hereinafter referred to as “ACK”) to the external electronic device 402 based on the CMD received from the external electronic device 402.

[0101] refer to Figure 5 In operation 531, the processor 470 of the external electronic device 402 according to various embodiments may send a CMD to the electronic device 401. In operation 533, the processor 470 of the external electronic device 402 may send data (DATA) (hereinafter, referred to as "DATA") to the electronic device 401 based on the CMD. In operation 535, the processor 430 of the electronic device 401 may send an ACK to the external electronic device 402 based on the CMD and the data received from the external electronic device 402.

[0102] refer to Figure 5 In operation 551, the processor 470 of the external electronic device 402 according to various embodiments may send a CMD to the electronic device 401. In operation 553, the processor 430 of the electronic device 401 may send data to the external electronic device 402 based on the CMD. In operation 555, the processor 470 of the external electronic device 402 may send an ACK to the electronic device 401 based on the data received from the electronic device 401.

[0103] In various embodiments, the CMD sent in operations 511, 531, 551 may be data of a structure such as shown in Table 1 presented below:

[0104] [Table 1]

[0105] bmRequest Type bRequest wValue wIndex wLength

[0106] As shown in Table 1, CMD may include a bmReqeust type field, a bRequest field, a wValue field, a wIndex field, and a wLength field. In various embodiments, the bmReqeust type, bRequest, wValue, wIndex, and wLength fields may be fields defined in a setup packet format according to the USB standard, for example.

[0107] In Table 1, the length of the bmRequest type field may be 1 byte. In various embodiments, the value of the entity of the bmRequest type field may be 0xC0 or 0x40. In various embodiments, when the entity of the bmRequest type field is 0xC0, CMD may indicate that the request direction is from the electronic device 401 to the external electronic device 402, the request type is a provision type, and the recipient is a device (for example, when the external electronic device 402 is a host, the device may be the electronic device 401). In various embodiments, when the entity of the bmRequest type field is 0x40, CMD may indicate that the request direction is from the external electronic device 402 to the electronic device 401, the request type is a provision type, and the recipient is a device (for example, when the external electronic device 402 is a host, the device may be the electronic device 401).

[0108] In Table 1, the length of the bRequest field may be 1 byte. In various embodiments, the value of the entity of the bRequest field may be 0xF1. In various embodiments, when the entity of the bRequest field is 0xF1, CMD may indicate a command newly defined as different from a standard device request code according to the USB standard.

[0109] In Table 1, the length of the wValue field may be 2 bytes. In various embodiments, the value of the entity of the wValue field may be various values. In various embodiments, based on the value of the entity of the wValue field, the CMD may indicate various message types. In various embodiments, various message types that may differ from each other by, for example, the value of the entity of the wValue field are shown, for example, in Table 2 presented below:

[0110] [Table 2]

[0111]

[0112]

[0113] In Table 2, the CMD with the message type START UP may be an operating system for booting the electronic device 401 (eg, Figure 2 In various embodiments, the CMD with the message type SHUT DOWN may be a CMD for shutting down the operating system of the electronic device 401 (eg, Figure 2 In various embodiments, the CMD with the message type REBOOT may be used to restart the operating system of the electronic device 401 (eg, Figure 2In various embodiments, a CMD with a message type of SLEEP may be a CMD for turning off the display 497. In various embodiments, a CMD with a message type of WAKE UP may be a CMD for turning on the display 497. In various embodiments, a CMD with a message type of TOGGLE LOCK / UNLOCK may be a CMD for changing the ON-OFF state of the display 497. In various embodiments, a CMD with a message type of CCR STATE REQUEST may be a CMD for requesting the current state of the electronic device 401. In various embodiments, a CMD with a message type of CCR STATE TRANSFER may be a CMD for requesting the current state of the electronic device 401. In various embodiments, a CMD with a BATTERY STATUSREQUEST message type may be a CMD for requesting the current state of the battery 491. In various embodiments, a CMD with a BATTERY STATUS TRANSFER message type may be a CMD for requesting the current state of the battery 491. In various embodiments, a CMD having a message type of APP ACTIVITY STATUS REQUEST may be a CMD requesting the current state of the application 435. In various embodiments, a CMD having a message type of APP ACTIVITY STATUS TRANSFER may be a CMD requesting the current state of the application 435.

[0114] When the entity of the wValue field is 0x0063, the message type of CMD may be START UP, and the data phase may be omitted, as shown in Table 2. In various embodiments, when the entity of the wValue field is 0x0065, the message type of CMD may be REBOOT, and the data phase may be omitted. In various embodiments, when the entity of the wValue field is 0x0066, the message type of CMD may be SLEEP, and the data phase may be omitted. In various embodiments, when the entity of the wValue field is 0x0067, the message type of CMD may be WAKE UP, and the data phase may be omitted. In various embodiments, when the entity of the wValue field is 0x0068, the message type of CMD may be TOGGLE LOCK / UNLOCK, and the data phase may be omitted. In various embodiments, when the entity of the wValue field is 0x0069, the message type of CMB may be CCR STATE REQUEST, and the data phase may be omitted. In various embodiments, when the entity of the wValue field is 0x0070, the message type of CMD may be CCR STATE TRANSFER, the data phase may not be omitted, and the data in the data phase may be sent from the CCR (e.g., the electronic device 401). In various embodiments, when the entity of the wValue field is 0x0096, the message type of CMD may be BATTERY STATUS REQUEST, and the data phase may be omitted. In various embodiments, when the entity of the wValue field is 0x0097, the message type of CMD may be BATTERY STATUSTRANSFER TRANSFER, the data phase may not be omitted, and the data in the data phase may be sent from the CCR (e.g., the electronic device 401). In various embodiments, when the entity of the wValue field is 0x0098, the message type of CMD may be APPACTIVITY STATUS REQUEST, and the data phase may be omitted. In various embodiments, when the entity of the wValue field is 0x0099, the message type of the CMD may be APP ACTIVITY STATUS TRANSFER, the data phase may not be omitted, and the data in the data phase may be sent from the CCR (e.g., the electronic device 401). In various embodiments, the data phase may indicate a time period for sending data after sending the CMD and before sending the ACK. For example, when the data phase is omitted, the external electronic device 402 may send the CMD, and then, at the next message transceiving time, the electronic device 401 may send the ACK.In another example, when the data phase is not omitted, the external electronic device 402 may send a CMD, and then, at the next message transceiving time, data may be sent from the external electronic device 402 or the electronic device 401, and then, for example, at the next message transceiving time, ACK may be sent from the electronic device 401 or the external electronic device 402. Operations between the external electronic device 402 and the electronic device according to message types according to various embodiments will be described below.

[0115] In various embodiments, when the message type of CMD is START UP, SHUT DOWN, REBOOT, SLEEP, WAKEUP, TOGGLE LOCK / UNLOCK, CCR STATE REQUEST, BATTERY STATUS REQUEST, or APP ACTIVITYSTATUS REQUEST, the entity of the bmRequest type field may be 0x40. In various embodiments, when the message type of CMD is CCR STATE TRANSFER, BATTERY STATUS TRANSFER, or APP ACTIVITY STATUSTRANSFER, the entity of the bmRequest type field may be 0xC0.

[0116] Referring again to Table 1, the length of the wIndex field may be 2 bytes. In various embodiments, the value of the entity of the wIndex field may be various values. In various embodiments, based on the value of the entity of the wIndex field, the CMD may indicate the shutdown time of the electronic device 401.

[0117] In Table 1, the length of the wLength field may be 2 bytes. In various embodiments, the value of the entity of the wLength field may be various values. In various embodiments, based on the value of the entity of the wLength field, the CMD may indicate the data length in the data phase.

[0118] In various embodiments, when the CMD sent by the external electronic device 402 to the electronic device 401 is a CMD indicating that the data stage is omitted, the electronic device 401 may send an ACK for the CMD to the external electronic device 402. In various embodiments, when the CMD sent by the external electronic device 402 to the electronic device 401 is a CMD indicating that the data stage is not omitted, and data according to the data stage is sent by the external electronic device 402, the external electronic device 402 may send the CMD and then send the data to the electronic device 401, and the electronic device 401 may send an ACK for the data to the external electronic device 402. In various embodiments, when the CMD sent by the external electronic device 402 to the electronic device 401 is a CMD indicating that the data stage is not omitted, and data according to the data stage is sent by the electronic device 401, and the external electronic device 402 sends the CMD, the electronic device 401 may send data to the external electronic device 402 based on the CMD, and the external electronic device 402 may send an ACK for the data to the electronic device 401. For example, based on the CMD transmitted to the electronic device 401 by the external electronic device 402, the processes of operations 511 and 515 may be performed, the processes of operations 531, 533, and 535 may be performed, or the processes of operations 551, 553, and 555 may be performed. Hereinafter, for the sake of brevity, at least one of the data according to the CMD, ACK, or a combination thereof will not be described. However, when it is shown that the CMD is sent, at least one of the data according to the sent CMD, ACK, or a combination thereof may be sent.

[0119] In various embodiments, it may be determined whether to send data based on the value of the entity of the wValue field. For example, when the value of the entity of the wValue field of CMD is a value corresponding to the message type indicating START UP, the sending of data may be omitted. In another example, when the value of the entity of the wValue field of CMD is a value corresponding to the message type indicating CCR STATE TRANSFER, data may be sent. In various embodiments, the sending entity of data may be determined based on the value of the entity of the bmRequest type field. For example, when the value of the entity of the bmRequest type field of CMD is 0x40, the sending entity of data may be an external electronic device 402. In another example, when the value of the entity of the bmRequest type field of CMD is 0xC0, the sending entity of data may be an electronic device 401. In various embodiments, the length of data may be determined based on the value of the entity of the wLength field of CMD. For example, when the value of the entity of the wLength field is 2, the length of data may be 2 bytes. In another example, when the value of the entity of the wLength field is 1, the length of data may be 1 byte.

[0120] Fig. 6A , Figure 6B , Figure 6C , Fig.6D , Fig. 6E and Fig. 6F Various exemplary data transceiving processes between the electronic device 401 and the external electronic device 402 according to various embodiments are shown. Figure 4A The configurations of the electronic device 401, the external electronic device 402, and the external electronic device 403 shown in FIG. Fig. 6A , Figure 6B , Figure 6C , Fig.6D , Fig. 6E and Fig. 6F .

[0121] Reference Fig. 6A In operation 611, when an event occurs in the external electronic device 403, the external electronic device 403 may send an event notification about the occurred event to the external electronic device 402. In various embodiments, the processor 470 of the external electronic device 402 may receive the event notification from the external electronic device 403 through the communication module 480. In various embodiments, the event may be an event in which the front door of the car in which the external electronic device 403 is installed is opened. In various embodiments, the front door opening event may be an event in which at least one front door of the car in which the external electronic device 403 is installed is opened. However, this should not be considered as limiting. In various embodiments, the car in which the external electronic device 403 is installed may be a car including a front door and a rear door.

[0122] In operation 613, the processor 470 of the external electronic device 402 may, based on the received event notification, apply at least one of a set voltage, a current, or a combination thereof to a power pin (eg, Figure 3C VBUS shown in the figure) to turn on the power pin (for example, Figure 3C In various embodiments, the processor 470 of the external electronic device 402 may control the power module 490 to apply at least one of a set voltage, a current, or a combination thereof to the power pin. In various embodiments, the processor 470 of the external electronic device 402 may control the power module 490 to apply at least one of a set voltage, a current, or a combination thereof to the power pin (e.g., Figure 3C ) to power the electronic device 401 connected to the connector 450. In various embodiments, the processor 470 of the external electronic device 402 can be based on the power pin (e.g., Figure 3CThe VBUS pin shown in FIG. 4 is turned on to refine the state of the electronic device 401 into a charging state. In various embodiments, the state of the electronic device 401 may be stored in the memory 495 of the external electronic device 402.

[0123] In operation 615, the battery 440 of the electronic device 401 may be charged using power provided from the external electronic device 402 through the connector 410. In various embodiments, when at least one of a set voltage, a current, or a combination thereof is applied to the power pin of the connector 410, the processor 430 of the electronic device 401 may apply the set voltage to the data pin of the connector 410. In various embodiments, when at least one of a set voltage, a current, or a combination thereof is applied to the power pin of the connector 410, the processor 430 of the electronic device 401 may drive the operating system according to the low power mode stored in the memory 491. In various embodiments, when at least one of a set voltage, a current, or a combination thereof is applied to the power pin of the connector 410, the processor 430 of the electronic device 401 may drive a boot loader (not shown) and may drive the operating system according to the stored low power mode. In various embodiments, the processor 430 of the electronic device 401 may drive a CCR driver (e.g., Figure 4B In various embodiments, when driving the CCR driver included in a boot loader (not shown), the processor 430 of the electronic device 401 may receive a command from the external electronic device 402 through the initially activated channel.

[0124] Reference Figure 6B In operation 621, when an event occurs in the external electronic device 403, the external electronic device 403 may send an event notification about the occurred event to the external electronic device 402. In various embodiments, the processor 470 of the external electronic device 402 may receive the event notification from the external electronic device 403 through the communication module 480. In various embodiments, the event may be a rear door opening event of a car in which the external electronic device 403 is installed. In various embodiments, the rear door opening event may be an event in which at least one rear door of the car in which the external electronic device 403 is installed is opened. In various embodiments, the car in which the external electronic device 403 is installed may be a car including a front door and a rear door. In various embodiments, the processor 470 of the external electronic device 402 may identify whether the event notification occurs through an input button (not shown) (e.g., a power key) of the external electronic device 402. In various embodiments, the processor 470 of the external electronic device 402 may recognize that an event notification occurs when a user presses an input button (not shown) (eg, a power key) of the external electronic device 402 for a set time when the electronic device 401 is turned off.

[0125] In operation 622, the processor 470 of the external electronic device 402 may, based on the received event notification, apply at least one of a set voltage, a current, or a combination thereof to a power pin (eg, Figure 3C VBUS shown in the figure) to turn on the power pin (for example, Figure 3C In various embodiments, the processor 470 of the external electronic device 402 can be based on the power pin (eg, Figure 3C The VBUS pin shown in FIG. 4 is turned on to refine the state of the electronic device 401 into a charging state. In various embodiments, the state of the electronic device 401 may be stored in the memory 495 of the external electronic device 402.

[0126] In operation 623, the battery 440 of the electronic device 401 may be charged using power provided from the external electronic device 402 through the connector 410. In various embodiments, when at least one of a set voltage, current, or a combination thereof is applied to the power pin of the connector 410, the processor 430 of the electronic device 401 may drive the operating system according to the low power mode stored in the memory 491. In various embodiments, when at least one of a set voltage, current, or a combination thereof is applied to the power pin of the connector 410, the processor 430 of the electronic device 401 may drive a boot loader (not shown) and may drive the operating system according to the low power mode stored in the memory 491. In various embodiments, the processor 430 of the electronic device 401 may drive a CCR driver (e.g., Figure 4B In various embodiments, when driving the CCR driver included in a boot loader (not shown), the processor 430 of the electronic device 401 may receive a command from the external electronic device 402 through the initially activated channel.

[0127] In operation 624, the processor 470 of the external electronic device 402 may detect the electronic device 401 based on at least one of a voltage, a current, or a combination thereof of a power pin of the connector 450. In various embodiments, the processor 470 of the external electronic device 402 may detect the electronic device 401 by detecting that a drop in at least one of a voltage, a current, or a combination thereof of a power pin occurs when power is supplied to the electronic device 401 through the power pin of the connector 450. In various embodiments, when at least one of a set voltage, a current, or a combination thereof is applied to the power pin of the connector 410, the processor 430 of the electronic device 401 may apply a set voltage to a data pin of the connector 410. In various embodiments, when the set voltage is applied to the data pin, the processor 470 of the external electronic device 402 may obtain transmission speed information of the electronic device 401 through the data pin. In various embodiments, the processor 470 of the external electronic device 402 may perform at least one of enumeration, configuration of the electronic device 401, or a combination thereof through an initially activated channel based on the acquired transmission speed information.

[0128] In operation 625, the processor 470 of the external electronic device 402 may send a start command (START UP CMD) to the electronic device 401 through the initially activated channel based on the acquired transmission speed information. In various embodiments, the start command may be configured as shown in Table 3 below, for example:

[0129] [Table 3]

[0130] bmRequest Type bRequest wValue wIndex wLength 40 F1 63 00 00 00 00 00

[0131] As shown in Table 3, the entity of the bmRequest type field of the start command may be 0x40, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0063, the entity field of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the start command may indicate through the bmRequest type field that the request direction is from the external electronic device 402 to the electronic device 401, the request type is a provide type, and the recipient is a device (for example, when the external electronic device 402 is a host, the device may be the electronic device 401). In various embodiments, the start command may indicate a newly defined command through the bRequest field. In various embodiments, the start command may indicate through the wValue field that the message type is START UP and that the data phase is omitted. In various embodiments, the start command may not indicate the shutdown time of the electronic device 401 through the wIndex field. In various embodiments, the start command may indicate through the wLength field that the data phase is omitted. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLength fields of the start command (START UP CMD) may be fields defined in a setup packet format according to the USB standard.

[0132] In operation 626, the processor 430 of the electronic device 401 may boot (drive) an operating system (eg, Figure 2 In various embodiments, the processor 430 of the electronic device 401 may drive a boot loader (not shown) and may boot (drive) an operating system (e.g., Figure 2 In various embodiments, when the operating system is driven according to the low power mode, the processor 430 of the electronic device 401 may shut down the operating system according to the low power mode, and then may drive a boot loader (not shown) and boot the operating system stored in the memory (not shown). In various embodiments, when the processor 430 of the electronic device 401 receives the start command, the processor 430 of the electronic device 401 may send an ACK for the start command to the external electronic device 402.

[0133] In operation 627, the processor 470 of the external electronic device 402 may send a CCR state transmission command (CCR STATE T / F CMD) to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may generate the CCR state transmission command based on a set condition (e.g., a set time interval). In various embodiments, the processor 470 of the external electronic device 402 may generate the CCR state transmission command at a set time interval after sending the start command to the electronic device 401. In various embodiments, the CCR state transmission command may be configured, for example, as shown in Table 4 below:

[0134] [Table 4]

[0135] bmRequest Type bRequest wValue wIndex wLength C0 F1 70 00 00 00 01 00

[0136] As shown in Table 4, the entity of the bmRequest type field of the CCR state transfer command may be 0xC0, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0063, the entity field of the wIndex may be 0x0000, and the entity of the wLength may be 0x0100. In various embodiments, the CCR state transfer command may indicate through the bmRequest type field that the request direction is from the electronic device 401 to the external electronic device 402, the request type is a provision type, and the recipient is a device. In various embodiments, the CCR state transfer command may indicate through the wValue field that the message type is CCR STATE TRANSFER and that there is a data phase. In various embodiments, the CCR state transfer command may indicate through the wLength field that the data length according to the data phase is 1 byte. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLength fields of the CCR state transfer command (CCR STATE T / F CMD) may be fields defined in a setup packet format according to the USB standard.

[0137] In various embodiments, when the processor 470 of the external electronic device 402 does not receive a response to a CCR status transmission command from the electronic device 401 within a set time after sending a CCR status transmission command to the electronic device 401, the processor 470 may send a CCR status transmission command to the electronic device 401 again.

[0138] In operation 628, the processor 430 of the electronic device 401 may identify the current state (CURRENT STATE) based on the CCR state transmission command (CCR STATET / F CMD). In various embodiments, the processor 430 of the electronic device 401 may generate data indicating the identified current state, and may send the data to the external electronic device 402. In various embodiments, the processor 430 of the electronic device 401 may generate data indicating the current state in the set state, and may send the data to the external electronic device 402. In various embodiments, the set state may include an unrecognized state, a charging state, an on attachment state, a dimming attachment state, a power-off state, or a closed state. For example, when the processor 430 is being booted when the CCR state transmission command (CCR STATE T / F CMD) is received, the processor 430 may generate data indicating that the processor 430 of the electronic device 401 in the data stage is in the boot state, and the processor 430 may send the data to the external electronic device 402. In another example, when the processor 430 of the electronic device 401 completes the booting and then turns on the display (eg, Figure 4A When the display 497 is shown, the processor 430 of the electronic device 401 in the data stage can generate data indicating the screen-on state after booting, and can send the data to the external electronic device 402.

[0139] In various embodiments, when the processor 470 of the external electronic device 402 receives the data indicating the current state, the processor 470 of the external electronic device 402 may send an ACK for the data indicating the current state to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may refine the current state of the electronic device 401 stored in the memory 495 based on the data indicating the current state.

[0140] Reference Figure 6C, in operation 631, when an event occurs, the external electronic device 403 may send an event notification about the event that occurred to the external electronic device 402. In various embodiments, the processor 470 of the external electronic device 402 may receive the event notification from the external electronic device 403 through the communication module 480. In various embodiments, the event may be an event in which a user gets off a car in which the external electronic device 403 is installed. In various embodiments, the user gets off an event may be an event in which a user sitting on a seat between the rear doors of a car in which the external electronic device 403 is installed gets off a car. However, this should not be considered as limiting. In various embodiments, the processor 470 of the external electronic device 402 may identify the occurrence of an event notification through an input button (not shown) of the external electronic device 402. In various embodiments, the processor 470 of the external electronic device 402 may identify that an event notification occurs when a user presses an input button (not shown) (e.g., a power key) of the external electronic device 402 for a set time in a closed state of the electronic device 401.

[0141] In operation 632, based on the received event notification, the processor 470 of the external electronic device 402 may send a shutdown command (SHUT DOWN CMD) to the electronic device 401 through the initially activated channel. In various embodiments, the shutdown command may be configured as shown in Table 5 below, for example: [Table 5]

[0142] bmRequest Type bRequest wValue wIndex wLength 40 F1 64 00 00 00 00 00

[0143] As shown in Table 5, the entity of the bmRequest type field of the close command may be 0x40, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0064, the entity field of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the close command may indicate that the message type is SHUT DOWN through the wValue field, and the data phase is omitted. In various embodiments, when the message type of the wValue field indicates SHUT DOWN, the entity value of the wIndex field of the close command may indicate that the operating system terminates after a set time. For example, when the message type of the wValue field indicates SHUT DOWN and the entity value of the wIndex field of the close command is 0x0000, the close command may instruct the operating system to terminate immediately. In another example, when the message type of the wValue field indicates SHUT DOWN, and the entity value of the wIndex field of the close command is 0x0A00, the close command may instruct the operating system to terminate after 10 seconds. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLegnth fields of the SHUT DOWN CMD may be fields defined in a setup packet format according to the USB standard.

[0144] In operation 633, the processor 430 of the electronic device 401 may terminate the operating system (eg, Figure 2 In various embodiments, when the electronic device 401 receives the shutdown command, the processor 430 of the electronic device 401 may send an ACK for the shutdown command to the external electronic device 402.

[0145] In operation 634, the processor 470 of the external electronic device 402 may send a CCR state transmission command (CCR STATE T / F CMD) to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may generate a CCR state transmission command based on a set condition (e.g., a set time interval). In various embodiments, the processor 470 of the external electronic device 402 may generate a CCR state transmission command at a set time interval after sending a shutdown command. In various embodiments, the CCR state transmission command may be configured as shown in Table 4 above.

[0146] In operation 635, the processor 430 of the electronic device 401 may identify the current state (CURRENT STATE) based on the CCR state transmission command. In various embodiments, the processor 430 of the electronic device 401 may generate data indicating the identified current state, and may send the data to the external electronic device 402. For example, when the processor 430 completes the termination of the operating system upon receiving the CCR state transmission command, the processor 430 may generate data indicating that the processor 430 of the electronic device 401 in the data stage is in a shutdown state, and the processor 430 may send the data to the external electronic device 402.

[0147] In various embodiments, when the processor 470 of the external electronic device 402 receives the data indicating the current state, the processor 470 of the external electronic device 402 may send an ACK for the data indicating the current state to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may refine the current state of the electronic device 401 stored in the memory 495 based on the data indicating the current state.

[0148] In operation 636, when the processor of the external electronic device 402 receives the data indicating the shutdown state, the processor of the external electronic device 402 may shut down the power pin (eg, Figure 3C In various embodiments, the processor 470 of the external electronic device 402 may control the power module 490 to turn off at least one of the set voltage, current, or combination thereof applied to the power pin. In various embodiments, the processor 470 of the external electronic device 402 may stop supplying power to the electronic device 401 connected to the connector 450 by controlling the power module 490 to turn off at least one of the set voltage, current, or combination thereof applied to the power pin.

[0149] refer to Fig.6D , in operation 641, the processor 470 of the external electronic device 402 may recognize the occurrence of an event. In various embodiments, when the user presses an input button (not shown) (e.g., a power key) of the external electronic device 402 in a turned-off state of the display 497 after the booting of the electronic device 401 is completed, the processor 470 of the external electronic device 402 may recognize the occurrence of an event. However, this should not be considered as limiting.

[0150] In operation 642, based on the received event notification, the processor 470 of the external electronic device 402 may send a wake-up command (WAKE UP CMD) to the electronic device 401 through the initially activated channel. In various embodiments, the wake-up command may be configured as shown in Table 6 below, for example:

[0151] [Table 6]

[0152] bmRequest Type bRequest wValue wIndex wLength 40 F1 67 00 00 00 00 00

[0153] As shown in Table 6, the entity of the bmRequest type field of the wake-up command may be 0x40, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0067, the entity field of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the wake-up command may indicate that the message type is WAKE UP through the wValue field, and the data phase is omitted. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLength fields of the wake-up command (WAKE UP CMD) may be fields defined in a setup packet format according to the USB standard.

[0154] In operation 643, the processor 430 of the electronic device 401 may turn on the display 497 (DISPLAY ON) of the electronic device 401 based on the wake-up command. In various embodiments, when the electronic device 401 receives the wake-up command, the processor 430 of the electronic device 401 may send an ACK for the wake-up command to the external electronic device 402. In various embodiments, the processor 470 of the external electronic device 402 may refine the state of the electronic device 401 to a display-on state after booting based on the ACK for the wake-up command.

[0155] In operation 644, the processor 470 of the external electronic device 402 may send a CCR state transmission command (CCR STATE T / F CMD) to the electronic device 401. In various embodiments, the CCR state transmission command may be configured as shown in Table 4 above.

[0156] In operation 645, the processor 430 of the electronic device 401 may identify the current state (CURRENT STATE) based on the CCR state transmission command. In various embodiments, the processor 430 of the electronic device 401 may generate data indicating the identified current state, and may transmit the data to the external electronic device 402. In various embodiments, when the processor 470 of the electronic device 402 receives the data indicating the current state, the processor 470 of the external electronic device 402 may transmit an ACK for the data indicating the current state to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may refine the current state of the electronic device 401 stored in the memory 495 based on the data indicating the current state.

[0157] refer to Fig. 6E , in operation 651, the processor 470 of the external electronic device 402 may recognize the occurrence of an event. In various embodiments, when the user presses an input button (not shown) (e.g., a power key) of the external electronic device 402 in a turned-on state of the display 497 after the booting of the electronic device 401 is completed, the processor 470 of the external electronic device 402 may recognize the occurrence of an event. However, this should not be considered as limiting.

[0158] In operation 652, the processor 470 of the external electronic device 402 may send a sleep command (SLEEP CMD) to the electronic device 401 through the initially activated channel based on the identified event notification. In various embodiments, the sleep command may be configured as shown in Table 7 below, for example:

[0159] [Table 7]

[0160] bmRequest Type bRequest wValue wIndex wLength 40 F1 66 00 00 00 00 00

[0161] As shown in Table 7, the entity of the bmRequest type field of the sleep command may be 0x40, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0066, the entity field of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the sleep command may indicate that the message type is SLEEP through the wValue field, and the data phase is omitted. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLength fields of the sleep command (SLEEP CMD) may be fields defined in a setup packet format according to the USB standard.

[0162] In operation 653, the processor 430 of the electronic device 401 may turn off the display 497 (DISPLAY OFF) of the electronic device 401 based on the sleep command. In various embodiments, when the electronic device 401 receives the sleep command, the processor 430 of the electronic device 401 may send an ACK for the sleep command to the external electronic device 402.

[0163] In operation 654, the processor 430 of the electronic device 401 may send a CCR state transmission command (CCR STATE T / F CMD) to the electronic device 401. In various embodiments, the CCR state transmission command may be configured as shown in Table 4 above.

[0164] In operation 655, the processor 430 of the electronic device 401 may identify the current state (CURRENT STATE) based on the CCR state transmission command. In various embodiments, the processor 430 of the electronic device 401 may generate data indicating the identified current state, and may transmit the data to the external electronic device 402. In various embodiments, when the processor 470 of the external electronic device 402 receives the data indicating the current state, the processor 470 of the external electronic device 402 may transmit an ACK for the data indicating the current state to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may refine the current state of the electronic device 401 stored in the memory 495 based on the data indicating the current state.

[0165] refer to Fig. 6F , in operation 661, the processor 470 of the external electronic device 402 may recognize the occurrence of an event. In various embodiments, when the ACK to CMD is not received in a state where the user completes the booting of the electronic device 401, the processor 470 of the external electronic device 402 may recognize that an event occurs. However, this should not be considered as limiting. In various embodiments, the processor 470 of the external electronic device 402 may recognize that an event occurs when the user presses an input button (not shown) (e.g., a power button) of the external electronic device 402 within a set time period. However, this should not be considered as limiting.

[0166] In operation 662, the processor 470 of the external electronic device 402 may send a reboot command (REBOOT CMD) to the electronic device 401 through the initially activated channel based on the identified event notification. In various embodiments, the reboot command may be configured as shown in Table 8 below, for example:

[0167] [Table 8]

[0168] bmRequest Type bRequest wValue wIndex wLength 40 F1 65 00 00 00 00 00

[0169] As shown in Table 8, the entity of the bmRequest type field of the restart command may be 0x40, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0065, the entity field of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the restart command may indicate that the message type is REBOOT through the wValue field, and the data stage is omitted. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLength fields of the restart command (REBOOT CMD) may be fields defined in a setup packet format according to the USB standard.

[0170] In operation 663, the processor 430 of the electronic device 401 may terminate the running operating system (eg, Figure 2 In various embodiments, when the running operating system (e.g., Figure 2 When the operating system 142 shown in FIG. 1 is restarted, the processor 430 of the electronic device 401 may drive a boot loader (not shown) and may restart the operating system (e.g., Figure 2 In various embodiments, when the electronic device 401 receives the restart command, the electronic device 401 may send an ACK for the restart command to the external electronic device 402.

[0171] In operation 664, the processor 430 of the electronic device 401 may send a CCR state transmission command (CCR STATE T / F CMD) to the electronic device 401. In various embodiments, the CCR state transmission command may be configured as shown in Table 4 above.

[0172] In operation 665, the processor 430 of the electronic device 401 may identify the current state (CURRENT STATE) based on the CCR state transmission command. In various embodiments, the processor 430 of the electronic device 401 may generate data indicating the identified current state, and may transmit the data to the external electronic device 402. In various embodiments, when the processor 470 of the external electronic device 402 receives the data indicating the current state, the processor 470 of the external electronic device 402 may transmit an ACK for the data indicating the current state to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may refine the current state of the electronic device 401 stored in the memory 495 based on the data indicating the current state.

[0173] Figure 7 4 is a diagram showing an example state of an electronic device 401 according to various embodiments. Figure 4A The configurations of the electronic device 401, the external electronic device 402, and the external electronic device 403 shown in FIG. Figure 7 .

[0174] like Figure 7 As shown, the electronic device 401 can have various states. In various embodiments, when the external electronic device 402 is connected to the electronic device 401 through the connector 450, the external electronic device 402 can obtain information about the current state of the electronic device 401 through data about the CCR state transmission command (CCR STATE T / F CMD).

[0175] Reference Figure 7 In various embodiments, the power-off state 710 (POWER OFF) may indicate that the processor 430 is in an off state, the controller (not shown) (e.g., a USB controller) is in an off state, and the display 497 is in an off state. In various embodiments, the off state of the controller (not shown) (e.g., a USB controller) may indicate that no power is supplied to the power pins (e.g., Figure 3C In various embodiments, in the power-off state 710 (POWER OFF), when the power pin of the connector 450 of the external electronic device 402 is turned on (VBUS_ON) and at least one of the set voltage, current, or a combination thereof is applied to the power pin, the electronic device 401 may transition to the charging state 720 (CHARGING).

[0176] refer to Figure 7 According to various embodiments, the charging state 720 (CHARGING) may indicate that the processor 430 is in an ON state, in which the operating system according to the low power mode (LPM) is driven, the controller (not shown) (e.g., the USB controller) is in an ON state, and the display 497 is in an ON state. In various embodiments, the ON state of the controller (not shown) (e.g., the USB controller) may indicate that a power supply pin (e.g., Figure 3C In various embodiments, when the electronic device 401 receives a start command (START UP) from the external electronic device 402 in the charging state 720 (CHARGING), the electronic device 401 may be converted to the ON ATTACHED state 730. In various embodiments, when the electronic device 401 is separated (DETACHED) from the external electronic device in the charging state 720 (CHARGING), the electronic device 401 may be switched to the power-off state 710 (POWER OFF).

[0177] Reference Figure 7 The ON ATTACHED state 730 may indicate that the processor 430 is in an ON state, in which the operating system (eg, Figure 2 The operating system 142 shown in the figure is driven, a controller (not shown) (e.g., a USB controller) is in an on state, and the display 497 is in an on state. In various embodiments, the operating system running in a state other than the charging state 720 (charging) may be different from the operating system of the low power mode running in the charging state 720 (charging). However, this should not be considered as limiting.

[0178] In various embodiments, when the electronic device 401 receives a restart command (REBOOT) from the external electronic device 402 in the on-attached state 730 (ON ATTACHED), the electronic device 401 may be switched to the on-attached state 730 (ON ATTACHED). In various embodiments, when the electronic device 401 in the on-attached state 730 (ON ATTACHED) receives a sleep command from the external electronic device 402, the electronic device 401 may be switched to the dimming-attached state 740 (DIMMING ATTACHED). In various embodiments, when the electronic device 401 does not receive a user input through the touch screen (not shown) of the display 497 or does not receive a command from the external electronic device 402 within a set time in the on-attached state 730 (ON ATTACHED), the electronic device 401 may be switched to the dimming-attached state 740 (DIMMING ATTACHED). In various embodiments, when the electronic device 401 receives a shutdown command (SHUT_DOWN) from the external electronic device 402 in the on-attached state 730 (ON ATTACHED), the electronic device 401 may be switched to the off state 750 (SHUT DOWN). In various embodiments, when the electronic device 401 is separated from the external electronic device 402 in the on-attached state 730 (ON ATTACHED), the electronic device 401 may move to the on-detached state 760 (ON DETACHED). In various embodiments, when the voltage of the power pin of the connector 410 falls within a set voltage range (e.g., 4.5V or higher), the processor 430 of the electronic device 401 may recognize that the electronic device 401 is separated from the external electronic device 402.

[0179] refer to Figure 7, the dimming attachment state 740 (DIMMING ATTACHED) may indicate that the processor 430 is in an on state to drive the operating system, in which the operating system is driven, a controller (not shown) (e.g., a USB controller) is in an on state, and the display 497 is in an off state. In various embodiments, the dimming attachment state 740 (DIMMING ATTACHED) may be a state in which the electronic device 401 may turn off the display 497 while reducing the brightness of the display 497. In various embodiments, when the electronic device 401 receives a wake-up command (WAKE_UP) from the external electronic device 402 in the dimming attachment state 740 (DIMMING ATTACHED), the electronic device 401 may switch to the on attachment state 730 (ONATTACHED). In various embodiments, when the electronic device 401 is separated from the external electronic device 402 in the dimming attachment state 740 (DIMMING ATTACHED), the electronic device 401 may move to the on detachment state 760 (ON DETACHED).

[0180] Reference Figure 7 , the off state 750 may indicate that the processor 430 is in an on state, in which the operating system (e.g., Figure 2 The operating system 142 shown in the figure is driven, a controller (not shown) (e.g., a USB controller) is in a shutdown state, and the display 497 is in an on state. In various embodiments, when the power pin of the connector 450 of the external electronic device 402 is turned off (VBUS_OFF) and the power from the external electronic device 402 is stopped (SHUTDOWN) in the shutdown state 750, the electronic device 401 can be switched to the power-off state 710 (POWER OFF). In various embodiments, when the voltage of the power pin of the connector 410 falls outside a set voltage range (e.g., 4.5V or higher), the electronic device 401 can recognize that the power from the external electronic device 402 is stopped.

[0181] Reference Figure 7 , the ON DETACHED state 760 may indicate that the processor 430 is in an ON state, in which the operating system (eg, Figure 2The operating system 142 shown is driven, a controller (not shown) (e.g., a USB controller) is in an on state, and the display 497 is in an on state. In various embodiments, when the electronic device 401 is attached to the external electronic device 402 in the on detached state 760 (ON DETACHED), the electronic device 401 may be converted to the on attachment state 730 (ON ATTACHED). In various embodiments, when the voltage of the power pin of the connector 410 falls within a set voltage range (e.g., 4.5V or higher), the processor 430 of the electronic device 401 may recognize that the electronic device 401 is attached to the external electronic device 402. In various embodiments, when the electronic device 401 does not receive a user input through an input device (e.g., a touch screen) within a set time in the on detached state 760 (ON DETACHED), the electronic device 401 may be switched to the dimming detached state 770 (DIMMING DETACHED) after a set time (IN T SEC). In various embodiments, when the user presses an input button (not shown) (eg, a power key) in the ON DETACHED state 760 , the electronic device 401 may be switched to the SLEEP DETACHED state 780 .

[0182] Reference Figure 7 , the dimming separation state 770 (DIMMING DETACHED) may indicate that the processor 430 is in an on state, in which the operating system (eg, Figure 2 The operating system 142 shown in the figure is driven, a controller (not shown) (e.g., a USB controller) is in an on state, and the display 497 is in an off state. In various embodiments, the dimming detached state 770 (DIMMING DETACHED) may be a state in which the electronic device 401 turns off the display 497 while reducing the brightness of the display 497. In various embodiments, when the electronic device 401 is attached to the external electronic device 402 in the dimming detached state 770 (DIMMING DETACHED), the electronic device 401 may be converted to the on attachment state 730 (ON ATTACHED). In various embodiments, when no user input is received through an input device (e.g., a touch screen) within a set time in the dimming detached state 770 (DIMMING DETACHED), the electronic device 401 may be switched to the sleep detached state 780 (SLEEP DETACHED) after a set time (IN T SEC).

[0183] Reference Figure 7The sleep detached state 780 (SLEEP DETACHED) may indicate that the processor 430 is in an on state, in which the operating system (eg, Figure 2 The operating system 142 shown in the figure is driven, a controller (not shown) (e.g., a USB controller) is in an on state, and the display 497 is in an on state. In various embodiments, when the electronic device 401 is attached to the external electronic device 402 in the sleep detached state 780 (SLEEP DETACHED), the electronic device 401 can be converted to the on attachment state 730 (ON ATTACHED). In various embodiments, when the user presses an input button (e.g., a power key) in the sleep detached state 780 (SLEEP DETACHED), the electronic device 401 can be switched to the on detached state 760 (ON DETACHED).

[0184] Fig. 8A FIG. 2 is a diagram showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments. Figure 4A The configurations of the electronic device 401, the external electronic device 402, and the external electronic device 403 shown in FIG. Fig. 8A .

[0185] Reference Fig. 8A In operation 811, the processor 470 of the external electronic device 402 may generate a battery status transmission command (BATTERY STATUS T / F CMD), and may send the generated battery status transmission command (BATTERY STATUS T / F CMD) to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may generate a battery status transmission command based on a set condition (e.g., a set time interval). In various embodiments, the processor 470 of the external electronic device 402 may generate a battery status transmission command at a set time interval after the state of the electronic device 401 is refined to the on-attachment state. In various embodiments, the battery status transmission command may be configured, for example, as shown in Table 9 below:

[0186] [Table 9]

[0187] bmRequest Type bRequest wValue wIndex wLength C0 F1 97 00 00 00 04 00

[0188] As shown in Table 9, the entity of the bmRequest type field of the battery status transmission command may be 0xC0, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0097, the entity field of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0004. In various embodiments, the battery status transmission command may indicate through the bmRequest type field that the request direction is from the electronic device 401 to the external electronic device 402, the request type is a provide type, and the recipient is a device (for example, when the external electronic device 402 is a host, the device is the electronic device 401). In various embodiments, the battery status transmission command may indicate through the wValue field that the message type is BATTERYSTATUS TRANSFER and that there is a data phase. In various embodiments, the battery status transmission command may indicate through the wLength field that the data length according to the data phase is 4 bytes. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLength fields of the battery status transfer command (BATTERY STATUS T / F CMD) may be fields defined in a setup packet format according to the USB standard.

[0189] In operation 812, the processor 430 of the electronic device 401 may identify the current state of the battery 440 of the electronic device 401 based on the battery state transmission command, and may generate data indicating the identified current state of the battery 440, and may transmit the data to the external electronic device 402. In various embodiments, the data indicating the current state of the battery 440 may be configured, for example, as shown in Table 10 below:

[0190] [Table 10]

[0191]

[0192] As shown in Table 10, data indicating the current state of the battery 440 may be configured with battery level, battery health, charging state, and battery temperature fields.

[0193] In Table 10, the length of the battery level field may be 1 byte. In various embodiments, the entity of the battery level field may have an integer value between 0 and 100 or a value of 255. In various embodiments, the integer value between 0 and 100 that the entity of the battery level field may have may indicate a value according to a charge percentage of the battery. In various embodiments, when the entity of the battery level field indicates an integer value of 255, it may indicate that the charge percentage of the battery 440 is unknown.

[0194] In Table 10, the length of the battery health field may be 1 byte. In various embodiments, the entity of the battery health field may have a value corresponding to the type of battery health. In various embodiments, when there are seven types of battery health conditions, the entity of the battery health field may have 7 values. For example, when the type of battery health status is set to unknown state, good state, overheat state, failure state, overvoltage state, unspecified fault state, or overcooling state, the entity of the battery health may have a value indicating one of the unknown state, good state, overheat state, failure state, overvoltage state, unspecified fault state, or overcooling state.

[0195] In Table 10, the length of the charging state field may be 1 byte. In various embodiments, the entity of the charging state field may have a value corresponding to the type of the charging state. In various embodiments, when there are five types of charging states, the entity of the charging state field may have 5 values. For example, when the type of the charging state is set to an unknown state, a charging state, a discharging state, a non-charging state, or a full state, the entity of the charging state field may have a value indicating one of the unknown state, the charging state, the discharging state, the non-charging state, or the full state.

[0196] In Table 10, the length of the battery temperature field may be 1 byte. In various embodiments, the entity of the battery temperature field may have an integer value between -128 and 127. In various embodiments, the entity of the battery temperature field may have an integer value between -128 and 127, which may indicate a value according to the temperature of the battery.

[0197] In various embodiments, when the processor 470 of the external electronic device 402 receives the data indicating the current state of the battery 440, the processor 470 of the external electronic device 402 may send an ACK for the data indicating the current state of the battery 440 to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may refine the current state of the battery 440 of the electronic device 401 based on the data indicating the current state of the battery 440.

[0198] In various embodiments, the processor 470 of the external electronic device 402 may control the power pin based on the data indicating the current state of the received battery. In various embodiments, the processor 470 of the external electronic device 402 may determine whether to apply at least one of a set voltage, current, or a combination thereof to the power pin based on the data indicating the current state of the received battery 440. For example, when the data indicating the current state of the battery 440 indicates an overheating state, the processor 470 of the external electronic device 402 may stop supplying power to the electronic device 401 connected to the connector 450 by controlling the power module 490 to turn off at least one of the voltage, current, or a combination thereof applied to the power pin. In another example, when the data indicating the current state of the battery 440 indicates that the battery charge is lower than or equal to a set level, the processor 470 of the external electronic device 402 may control the power module 490 to apply at least one of a set voltage, current, or a combination thereof to the power pin to supply power to the electronic device 401 connected to the connector 450. However, this should not be considered as limiting.

[0199] Figure 8B FIG. 2 is a diagram showing an example data transceiving process between an electronic device and an external electronic device according to various embodiments. Figure 4A The configurations of the electronic device 401, the external electronic device 402, and the external electronic device 403 shown in FIG. Figure 8B .

[0200] Reference Figure 8B , in operation 821, the processor 470 of the external electronic device 402 may send an application status transmission command (APP STATUS T / F CMD) to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may generate an application status transmission command based on a set condition (e.g., a set time interval). In various embodiments, the processor 470 of the external electronic device 402 may generate an application status transmission command at a set time interval after refining the state of the electronic device 401 to the open attachment state. In various embodiments, the application status transmission command may be configured, for example, as shown in Table 11 below:

[0201] [Table 11]

[0202] bmRequest Type bRequest wValue wIndex wLength C0 F1 99 00 00 00 01 00

[0203] As shown in Table 11, the entity of the bmRequest type field of the reference status transfer command may be 0xC0, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0099, the entity field of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0001. In various embodiments, the application status transfer command may indicate through the bmRequest type field that the request direction is from the electronic device 401 to the external electronic device 402, the request type is a provide type, and the recipient is a device (e.g., when the external electronic device 402 is a host, the device is the electronic device 401). In various embodiments, the application status transfer command may indicate through the wValue field that the message type is APPACTIVITY STATUS TRANSFER and that there is a data phase. In various embodiments, the application status transfer command may indicate through the wLength field that the data length according to the data phase is 1 byte. In various embodiments, the bmRequest type, bRequest, wValue, wIndex, and wLength fields of the application status transfer command (APP STATUS T / F CMD) may be fields defined in a setup packet format according to the USB standard.

[0204] In operation 822, the processor 430 of the electronic device 401 may identify the running application (eg, Figure 2 146), and may generate an indication of the current state of the identified application (e.g., Figure 2 The data of the current state of the application 146) can be sent to the external electronic device 402. In various embodiments, the current state of the running application can be one of the following: application activity state, unknown state, operating system not running state, foreground activity state (foreground activity), background activity state (background activity), activity not running state or command touch APP not installed state.

[0205] In various embodiments, when the processor 470 of the external electronic device 402 receives the data indicating the current state of the running application, the processor 470 of the external electronic device 402 may send an ACK for the data indicating the current state of the running application to the electronic device 401. In various embodiments, the processor 470 of the external electronic device 402 may refine the current state of the running application of the electronic device 401 based on the data indicating the current state of the running application.

[0206] According to various example embodiments as described above, an electronic device (e.g., electronic device 401) may include: a connector configured to connect to an external electronic device; a memory configured to store instructions; and a processor configured to execute the stored instructions, which, when executed by the processor, causes the processor to control the electronic device to identify a control signal received through a channel among multiple channels that is initially activated based on the external electronic device being connected to the connector, and to perform control based on a message included in the identified control signal.

[0207] In various example embodiments, based on power being provided from the external electronic device through the connector, the processor may be configured to control the electronic device to drive the first operating system in a power-off state.

[0208] In various embodiments, the message included in the recognized control signal may include a startup command, and the processor may be configured to control the electronic device to drive the second operating system based on the startup command included in the message.

[0209] In various example embodiments, the processor may be configured to control the electronic device: based on the second operating system being driven, identify another control signal received through the initially activated channel, and perform control based on a message included in the identified another control signal.

[0210] In various example embodiments, the identified another control signal may be generated by the external electronic device based on a response to at least one control signal of a plurality of control signals, the plurality of control signals being sent by the external electronic device based on the second operating system being driven, and not received from the electronic device. The message included in the message of the identified another control signal may include a restart command, and the processor may be configured to control the electronic device to drive the second operating system again based on the restart command included in the message of the identified another control signal.

[0211] In various example embodiments, the identified another control signal may be generated by the external electronic device based on an event received by the external electronic device from another external electronic device. The message included in the identified another control signal may include a shutdown command. The processor may be configured to control the electronic device to shut down the second operating system based on the shutdown command included in the message of the identified another control signal.

[0212] In various example embodiments, the event may include an opening event of a door of a car detected by another external electronic device.

[0213] In various example embodiments, the electronic device may further include a battery configured to supply power to the electronic device.

[0214] The message included in the identified control signal may include a battery status transmission command, and the processor may be configured to control the electronic device: generate data including battery health information of the battery based on the battery status transmission command included in the message, and control the connector to send data including battery health information to the external electronic device through the initially activated channel.

[0215] According to various example embodiments as described above, an electronic device (e.g., electronic device 402) may include: a connector configured to be electrically connected to an external electronic device; a communication module including a communication circuit configured to communicate with another external electronic device; a memory configured to store instructions; and a processor configured to execute the stored instructions. The processor may be configured to control the electronic device: based on receiving an event from another external electronic device, control the connector to supply power to the external electronic device; and based on power being supplied to the external electronic device, generate a control signal to be sent through a channel that is initially activated based on the external electronic device being electrically connected to the connector among multiple channels. The connector may be configured to send the generated control signal to the external electronic device so that the external electronic device performs control based on a message included in the generated control signal.

[0216] In various example embodiments, the processor may be configured to control the electronic device to generate a control signal such that a message included in the generated control signal includes a command corresponding to an event received from another external electronic device.

[0217] In various example embodiments, the command corresponding to the event received from another external electronic device may be a start command, and the external electronic device may be configured to drive an operating system based on the start command included in the message.

[0218] In various example embodiments, based on the operating system being driven in the external electronic device, the processor may be configured to control the electronic device: based on a response to at least one control signal among a plurality of control signals, another control signal to be sent through the initially activated channel is generated, the plurality of control signals being sent to the external electronic device through the initially activated channel instead of being received from the external electronic device. The message included in the another control signal may include a restart command, and the external electronic device may be configured to drive the operating system again based on the restart command included in the message included in the another control signal.

[0219] According to various example embodiments, a command corresponding to an event received from another external electronic device may be a start command, and the external electronic device may be configured to drive an operating system based on the start command included in the message.

[0220] In various example embodiments, based on the operating system being driven in the external electronic device, the processor may be configured to control the electronic device: generate another control signal to be sent through the initially activated channel based on a response to at least one control signal among a plurality of control signals, the plurality of control signals being sent to the external electronic device through the initially activated channel instead of being received from the external electronic device. The message included in the another control signal may include a restart command, and the external electronic device may be configured to drive the operating system again based on the restart command included in the message included in the another control signal.

[0221] In various example embodiments, the processor may be configured to control the electronic device to generate another control signal to be sent to the external electronic device through the initially activated channel based on another event received from another external electronic device, and the external electronic device may be configured to shut down the operating system based on a shutdown command corresponding to the other event and included in the message of the other control signal.

[0222] In various example embodiments, the processor may be configured to control the electronic device: based on power being provided to the external electronic device, generate another control signal to be sent through the initially activated channel, the message of the other control signal including a battery status transmission command regarding a battery of the external electronic device; and control power supply to the external electronic device in response to the other control signal based on battery health information of data received from the external electronic device.

[0223] In various example embodiments, the event may include an opening event of a door of a car detected by another external electronic device.

[0224] According to the various example embodiments described above, a method for operating an electronic device (e.g., electronic device 401) may include: identifying a control signal received through a channel among multiple channels that is initially activated after an external electronic device is connected to a connector; and performing control based on a message included in the identified control signal.

[0225] In various example embodiments, the method may further include: receiving power provided by the external electronic device through the connector based on the electronic device being recognized by the external electronic device through the connector; and driving the operating system in a power-off state based on the power provided by the external electronic device being received.

[0226] In various example embodiments, the message included in the recognized control signal may include a start command, and controlling based on the message included in the recognized control signal may include driving an operating system based on the start command included in the message.

[0227] In various example embodiments, the method may include: recognizing another control signal received from the external electronic device through the initially activated channel based on the operating system being driven; and controlling based on a message included in the recognized another control signal.

[0228] In various embodiments, the message included in the identified control signal may include a battery status transmission command, and controlling based on the message included in the identified control signal may include: generating data including battery health information of the battery based on the battery status transmission command included in the message, and controlling the connector to send data including battery health information to an external electronic device through an initially activated channel.

[0229] As described above, the electronic device 401 according to various exemplary embodiments receives a control signal from the external electronic device even before the enumeration operation is completed, so that the electronic device 410 can operate more quickly. In addition, as described above, the electronic device 401 according to various exemplary embodiments receives a control signal from the external electronic device through the initially activated channel, and thus restarts the operating system through the control signal even when at least one of the operating system, application, or a combination thereof is in a disabled state, so that reliable operation can be ensured.

[0230] Even before the enumeration operation is completed, the electronic device and method thereof according to various exemplary embodiments may receive a control signal from the external electronic device.

[0231] Effects obtained by the present disclosure are not limited to those mentioned above, and other effects not mentioned above may be clearly understood by those skilled in the art based on the description provided above.

[0232] The methods according to the embodiments described in the claims and / or the specification of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0233] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in the electronic device. At least one program may include instructions for causing the electronic device to execute the method as defined by the appended claims disclosed herein and / or the various embodiments of the present disclosure.

[0234] The program (software module or software) may be stored in a non-volatile memory including random access memory and flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage device, a compact disk (CD-ROM), a digital versatile disk (DVD) or other types of optical storage devices or tapes. Alternatively, any combination of some or all may form a memory storing the program. In addition, a plurality of such memories may be included in the electronic device.

[0235] In addition, the program may be stored in a connectable storage device that is accessible via a communications network (e.g., the Internet, an intranet, a local area network (LAN), a wide area network (WAN), and a storage area network (SAN), or a combination thereof). Such a storage device may access the electronic device via an external port. Furthermore, a separate storage device on a communications network may access the portable electronic device.

[0236] In the above-mentioned example embodiments of the present disclosure, the components included in the present disclosure are expressed in the singular or plural, depending on the example embodiments presented. However, for ease of description, the singular form or plural form is selected to be suitable for the presented situation, and the various embodiments of the present disclosure are not limited to one element or multiple elements thereof. In addition, multiple elements described in the specification can be configured as one element, or one element in the specification can be configured as multiple elements.

[0237] While the present disclosure has been shown and described with reference to various example embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the present disclosure.

Claims

1. An electronic device, comprising: a connector configured to connect to an external electronic device; processor; as well as a memory storing instructions that, when executed by the processor, cause the electronic device to: recognizing a control signal received through a channel initially activated based on the external electronic device being connected to the connector among a plurality of channels while driving the operating system according to the low power mode, and controlling the electronic device based on a message included in the identified control signal, the message including a start command, and The electronic device is controlled to drive a first operating system based on the boot command included in the message, the first operating system being different from the operating system according to the low power mode.

2. The electronic device according to claim 1, wherein: The instructions, when executed by the processor, cause the electronic device to control the electronic device to drive a second operating system in a power-off state based on power supplied from the external electronic device through the connector.

3. The electronic device according to claim 1, wherein: The instructions, when executed by the processor, cause the electronic device to: Based on the first operating system being driven, identifying another control signal received through the initially activated channel, and The electronic device is controlled based on the message included in the identified another control signal.

4. The electronic device according to claim 3, wherein: the identified another control signal is generated by the external electronic device based on a response to at least one control signal of a plurality of control signals, the plurality of control signals being sent by the external electronic device based on the first operating system being driven and not received from the electronic device, wherein the message included in the identified another control signal includes a restart command, and Wherein, when the instructions are executed by the processor, the electronic device drives the first operating system based on the restart command included in the message of the identified another control signal.

5. The electronic device according to claim 3, wherein: the identified another control signal is generated by the external electronic device based on an event, the event being received by the external electronic device from another external electronic device, wherein the message included in the identified another control signal includes a shutdown command, and Wherein, when the instructions are executed by the processor, the electronic device shuts down the first operating system based on the shutdown command included in the message of the identified another control signal.

6. The electronic device according to claim 5, wherein: The event includes an opening event of a car door detected by the another external electronic device.

7. The electronic device according to claim 1, further comprising a battery, wherein the battery is configured to supply power to the electronic device. in, The message included in the identified control signal includes a battery status transmission command, and Wherein, when the instructions are executed by the processor, the electronic device: generating data including battery health information of the battery based on the battery status transmission command included in the message, and The connector is controlled to send the data including the battery health information to the external electronic device through the initially activated channel.

8. An electronic device, comprising: a connector configured to electrically connect to an external electronic device; a communication module, the communication module comprising a communication circuit configured to communicate with another external electronic device; processor; as well as a memory storing instructions that, when executed by the processor, cause the electronic device to: controlling the connector to supply power to the external electronic device driving an operating system according to a low power mode based on receiving an event from the other external electronic device; as well as generating a control signal based on the power being supplied to the external electronic device, the control signal to be transmitted through a channel among a plurality of channels that is initially activated based on the external electronic device being electrically connected to the connector, wherein the connector is configured to transmit the generated control signal to the external electronic device so that the external electronic device performs control based on a message included in the generated control signal, wherein the instructions, when executed by the processor, further cause the electronic device to generate the control signal, so that the message included in the generated control signal includes a command corresponding to the event received from the other external electronic device, wherein the command corresponding to the event received from the other external electronic device comprises a start command, and The external electronic device is configured to drive a first operating system based on the startup command included in the message, the first operating system being different from the operating system according to the low power mode.

9. The electronic device according to claim 8, wherein: The instructions, when executed by the processor, cause the electronic device to be driven in the external electronic device based on the first operating system, and generate another control signal to be sent through the initially activated channel based on a response to at least one control signal of a plurality of control signals, the plurality of control signals being sent to the external electronic device through the initially activated channel instead of being received from the external electronic device, The message included in the other control signal includes a restart command, and The external electronic device is configured to drive the first operating system again based on the restart command included in the message included in the other control signal.

10. The electronic device according to claim 8, wherein: The instructions, when executed by the processor, cause the electronic device to generate another control signal to be sent to the external electronic device through the initially activated channel based on another event received from the another external electronic device, and The external electronic device is configured to shut down the first operating system based on a shutdown command corresponding to the other event included in the message of the other control signal.

11. The electronic device according to claim 8, wherein: The instructions, when executed by the processor, cause the electronic device to: generating another control signal to be transmitted through the initially activated channel based on the power being supplied to the external electronic device, a message of the another control signal including a battery status transmission command regarding a battery of the external electronic device; as well as In response to the another control signal, power supply to the external electronic device is controlled based on battery health information of the data received from the external electronic device.

12. The electronic device according to claim 8, wherein: The event includes an opening event of a car door detected by the another external electronic device.

Images