Electronic device and method for transceiving control signal

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

CROSS-REFERENCE TO RELATED APPLICATION

This application is based on and claims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2018-0139239, filed on Nov. 13, 2018, in the Korean Intellectual Property Office, the disclosure of which is incorporated by reference herein in its entirety.

BACKGROUND

Field

The disclosure relates to an electronic device which transceives a control signal and an operating method thereof.

Description of Related Art

An electronic device may transceive a control signal with an external electronic device through an allocated channel. Such an electronic device may include a connector provided with data pins which are allocated a plurality of channels from the external electronic device.

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

SUMMARY

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

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

An electronic device according to various example embodiments may include: a connector configured to be connected with an external electronic device; a memory configured to store instructions; and a processor configured to execute the stored instructions, the instructions, when executed by the processor, cause the processor to control the electronic device to: identify a control signal received through a channel that is initially activated after the external electronic device is connected to the connector from among a plurality of channels, and to perform control based on a message included in the identified control signal.

An electronic device according to various example embodiments may include: a connector configured to be electrically connected with an external electronic device; a communication module comprising communication circuitry configured to communicate with an 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 another 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, may generate a control signal to be transmitted through a channel that is initially activated after the external electronic device is electrically connected to the connector from among a plurality of channels. The connector may be configured to transmit the generated control signal to the external electronic device, such that the external electronic device controls based on a message included in the generated control signal.

DETAILED DESCRIPTION

The power management module188may manage power supplied to the electronic device101. According to an example embodiment, the power management module188may be implemented as at least part of, for example, a power management integrated circuit (PMIC).

It should be appreciated that various embodiments of the present disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment. With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related elements.

FIG. 2is a block diagram200illustrating an example program140according to various embodiments. According to an embodiment, the program140may include an operating system (OS)142to control one or more resources of the electronic device101, middleware144, and/or an application146executable in the OS142. The OS142may include, for example, Android™, iOS™, Windows™, Symbian™, Tizen™, or Bada™. At least part of the program140, for example, may be pre-loaded on the electronic device101during manufacture, or may be downloaded from or updated by an external electronic device (e.g., the electronic device102or104, or the server108) during use by a user. According to an embodiment, the program140may further include a bootloader (not shown) serving to drive the operating system142to boot the electronic device101. According to an embodiment, the bootloader (not shown) may further include a command center rear (CCR) driver (for example, a CCR driver431ofFIG. 4) to drive a universal serial bus (hereinafter, referred to as “USB”) module (not shown) (or a USB controller).

The operating system142may control management (for example, allocation or collection) of one or more system resources (for example, a process, a memory, or power) of the electronic device101. Additionally or alternatively, the operating system142may include one or more driver programs to drive other hardware devices of the electronic device101, for example, the input device150, the sound output device155, the display device160, the audio module170, the sensor module176, the interface177, the haptic module179, the camera module180, the power management module188, the battery189, the communication module190, the subscriber identification module196, or the antenna module197. According to an embodiment, the operating system142may further include a CCR driver (for example, the CCR driver431ofFIG. 4) to drive a USB module (not shown) (or a USB controller). According to an embodiment, the operating system142may include at least one CCR driver. According to an embodiment, the at least one CCR driver (not shown) included in the operating system142may be different from the CCR driver (not shown) included in the bootloader (not shown). According to an embodiment, the CCR driver (not shown) included in the bootloader (not shown) may include instructions to process commands (for example, at least one of a reboot command (REBOOT CMD), or a start up command (START UP CMD), or a combination thereof) received from the external electronic device102through an initially activated channel. According to an embodiment, the CCR driver (not shown) included in the bootloader (not shown) may include instructions to shift the electronic device101from a power off state to a charging state, in which the operating system according to a low power mode is driven, when power is supplied from the external electronic device102. According to an embodiment, at least one CCR driver (not shown) included in the operating system142may include instructions to process commands (for example, at least one of a start up command (START UP CMD), a shut down command (SHUT DOWN CMD), a wake up command (WAKE UP CMD), a sleep command (SLEEP CMD), a reboot command (REBOOT CMD), a CCR state transfer command (CCR STATE T/F CMD), a battery status transfer command (BATTERY STATUS T/F CMD), an application status transfer command (APP STATUS T/F CMD), or a combination thereof) received from the external electronic device102through an initially activated channel.

The middleware144may provide various functions to the application146such that a function or information provided from one or more resources of the electronic device101may be used by the application146. The middleware144may include, for example, an application manager201, a window manager203, a multimedia manager205, a resource manager207, a power manager209, a database manager211, a package manager213, a connectivity manager215, a notification manager217, a location manager219, a graphic manager221, a security manager223, a telephony manager225, or a voice recognition manager227.

The application manager201, for example, may manage the life cycle of the application146. The window manager203, for example, may manage one or more graphical user interface (GUI) resources that are used on a screen. The multimedia manager205, for example, may identify one or more formats to be used to play media files, and may encode or decode a corresponding one of the media files using a codec appropriate for a corresponding format selected from the one or more formats. The resource manager207, for example, may manage the source code of the application146or a memory space of the memory130. The power manager209, for example, may manage the capacity, temperature, or power of the battery189, and determine or provide related information to be used for the operation of the electronic device101based at least in part on corresponding information of the capacity, temperature, or power of the battery189. According to an embodiment, the power manager209may interwork with a basic input/output system (BIOS) (not shown) of the electronic device101.

The database manager211, for example, may generate, search, or change a database to be used by the application146. The package manager213, for example, may manage installation or update of an application that is distributed in the form of a package file. The connectivity manager215, for example, may manage a wireless connection or a direct connection between the electronic device101and the external electronic device. The notification manager217, for example, may provide a function to notify a user of an occurrence of a specified event (e.g., an incoming call, message, or alert). The location manager219, for example, may manage locational information on the electronic device101. The graphic manager221, for example, may manage one or more graphic effects to be offered to a user or a user interface related to the one or more graphic effects.

The security manager223, for example, may provide system security or user authentication. The telephony manager225, for example, may manage a voice call function or a video call function provided by the electronic device101. The voice recognition manager227, for example, may transmit a user's voice data to the server108, and receive, from the server108, a command corresponding to a function to be executed on the electronic device101based at least in part on the voice data, or text data converted based at least in part on the voice data. According to an embodiment, the middleware244may dynamically delete some existing components or add new components. According to an embodiment, at least part of the middleware144may be included as part of the OS142or may be implemented as another software separate from the OS142.

The application146may include, for example, a home251, dialer253, short message service (SMS)/multimedia messaging service (MMS)255, instant message (IM)257, browser259, camera261, alarm263, contact265, voice recognition267, email269, calendar271, media player273, album275, watch277, health279(e.g., for measuring the degree of workout or biometric information, such as blood sugar), or environmental information281(e.g., for measuring air pressure, humidity, or temperature information) application. According to an embodiment, the application146may further include an information exchanging application (not shown) that is capable of supporting information exchange between the electronic device101and the external electronic device. The information exchange application, for example, may include a notification relay application adapted to transfer designated information (e.g., a call, message, or alert) to the external electronic device or a device management application adapted to manage the external electronic device. The notification relay application may transfer notification information corresponding to an occurrence of a specified event (e.g., receipt of an email) at another application (e.g., the email application269) of the electronic device101to the external electronic device. Additionally or alternatively, the notification relay application may receive notification information from the external electronic device and provide the notification information to a user of the electronic device101.

The device management application may control the power (e.g., turn-on or turn-off) or the function (e.g., adjustment of brightness, resolution, or focus) of the external electronic device or some component thereof (e.g., a display device or a camera module of the external electronic device). The device management application, additionally or alternatively, may support installation, delete, or update of an application running on the external electronic device.

FIG. 3Ais a diagram illustrating an example electronic device301and a connector310according to various embodiments.

FIG. 3Bis a diagram illustrating example connectors310,350of an electronic device according to various embodiments.

FIG. 3Cis a diagram illustrating an example pin structure of the connector310of the electronic device according to various embodiments.

Referring toFIG. 3A, in various embodiments, the electronic device310may include the connector310through which an external electronic device (for example, the external electronic device102shown inFIG. 1) is connected. In various embodiments, the electronic device301may be included in the electronic device101shown inFIG. 1. AlthoughFIG. 3Adepicts the electronic device301as a portable electronic device such as a smartphone, a tablet PC, the electronic device301is not limited hereto, and any electronic device that is provided with a connector to be connected with an external electronic device, and transceives data with the external electronic device connected through the connector can be interpreted as the electronic device301ofFIG. 3A.

Referring toFIG. 3A, according to various embodiments, the electronic device301may include an opening formed on one surface of a housing and a hole connected with the opening, and may have the connector310disposed in the hole. As shown inFIG. 3A, an opening and a hole may be formed on one surface of a lower side of the housing of the electronic device301, and the connector310may be disposed in the opening and the hole. However, the disposal position of the connector310is not limited hereto, and the connector310may, for example, be disposed on other surfaces of the housing of the electronic device310.

According to various embodiments, a connector350of an external electronic device may be inserted into the connector310of the electronic device301. There is no limit to types of external electronic devices, and all devices including a battery pack supplying power to the electronic device301, a device communicating with the electronic device301, or an external memory connected with the electronic device301may correspond to the external electronic device.

According to various embodiments, the connector350of the external electronic device may be received through the hole, and may physically contact the connector310of the electronic device301and may be electrically connected according to the physical contact. According to various embodiments, the connector310of the electronic device301and the hole structure may be reversible structures. For example, the connector310may be symmetrical with respect to a first direction which is perpendicular to a direction in which the external electronic device is inserted (for example, a direction from the bottom to the top of the electronic device301), and a second direction which is opposite to the first direction.

Referring toFIG. 3B, the connector350of the external electronic device may be inserted into the connector310of the electronic device301with one surface (for example, the surface A) of the connector350being parallel to the front surface (for example, a surface on which the display is positioned) of the electronic device301, or the connector350of the external electronic device may be inserted with the other surface (for example, the surface B) of the connector350being parallel to the front surface of the electronic device301.

In various embodiments, the connector310may include a plurality of terminals, and, when the connector350of the external electronic device is inserted in a different direction, respective terminals of the external electronic device electrically connected to the terminals of the connector310of the electronic device301may be different.

According to various embodiments, the connector310may, for example, be a connector that follows a universal serial bus (USB) (hereinafter, referred to as “USB”) standard, and for example, may be a connector of a USB type C standard. However, various embodiments of the disclosure are not limited to the USB type C, and are applicable to a connector following the USB-related standards such as, for example, and without limitation, a USB type B, a USB type A, wired interfaces of various standards such as, for example, and without limitation, a lightning port, a high definition multimedia interface (HDMI), recommended standard 232 (RS-232), power line communication, plain old telephone service (POTS), nonstandard wired interfaces, or the like. Various embodiments of the disclosure are applicable to any interface that can transmit data (for example, data which is transmitted from a CC1 pin or CC2 pin included in the type C standard) which is used to automatically detect what type of devices are connected between a source device (for example, a device providing power) and a sync device (for example, a device receiving power), or between a downstream facing port (DFP) (for example, a device providing data) and an upstream facing port (UFP) (for example, a device receiving data).

FIG. 3Cis a diagram illustrating an example of a plurality of terminals provided in the connector310when the connector310of the electronic device (for example, the electronic device301) follows the USB type C standard.

Referring toFIG. 3C, the connector310may include 12 terminals (or pins) in each of the line A on the left and the line B on the right, and may be symmetrical.

In various embodiments, data may be transmitted between the electronic device301and an external electronic device through data pins (or D+ pin and D− pin) positioned at the sixth place and the seventh place in the line A on the left of the connector310, or data pins (or D+ pin and D− pin) positioned at the sixth place and the seventh place in the line B on the right. Power may be supplied to the electronic device301from an external electronic device through a power supply pin (or a VBUS pin) positioned at the fourth place of the line A on the left of the connector310. Since roles of the terminals in various operation modes are defined according to the USB type C standard, the roles of the terminals will not be described.

In various embodiments, when the electronic device310and an external electronic device are connected with each other, electric signals (for example, a digital ID or a resistance ID) may be exchanged through a CC1 pin and a CC2 pin, and accordingly, the electronic device and the external electronic device may detect types of other devices connected thereto. In addition, the electronic device may operate in a downstream facing port (DFP) mode or an upstream facing port (UFP) mode according to a result of detecting a connected device. 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.

FIG. 4Ais a block diagram illustrating an example electronic device401and an example external electronic device402according to various embodiments.

According to various embodiments, the electronic device401may be the same as the electronic device101shown inFIG. 1, the electronic device202shown inFIG. 2, or the electronic device301shown inFIG. 3at least in part.

Referring toFIG. 4A, in various embodiments, the electronic device401may include at least one of a connector410, a power delivery integrated circuit (PDIC)420(hereinafter, referred to as “PDIC”), a processor (e.g., including processing circuitry)430, a battery440, a memory491, and a display497, or any combination thereof. In various embodiments, some elements may be omitted. In various embodiments, the electronic device401may be referred to as a command center rear (CCR) (hereinafter, referred to as “CCR”). In various embodiments, the battery440may be included in the battery189shown inFIG. 1. In various embodiments, the memory491may be included in the memory130shown inFIG. 1. In various embodiments, the display497may be included in the display device160shown inFIG. 1. In various embodiments, the electronic device401may further include a controller (not shown). In various embodiments, the controller (not shown) (for example, a USB controller) may be connected between the connector410and the processor430.

In various embodiments, the connector410may be included in the connection terminal178shown inFIG. 1, or the connector310shown inFIGS. 3A, 3B, and 3C, but the disclosure is not limited thereto. In various embodiments, the connector410may include various types of pins (for example, pins of the connector310shown inFIG. 3C). In various embodiments, the connector410may be electrically connected with a connector450of an external electronic device402through various types of pins. In various embodiments, the connector410may receive power from the connector450of the external electronic device402through a power supply pin (for example, the VBUS pin of the connector310shown inFIG. 3C). In various embodiments, the connector410may deliver data transmission speed information of the electronic device401to the connector450of the external electronic device402through data pins (for example, at least one of the D+ pin, the D− pin of the connector310shown inFIG. 3C, or a combination thereof). In various embodiments, the connector410may transmit data to the connector450of the external electronic device402or may receive data from the connector450of the external electronic device402through the data pins.

In various embodiments, the PDIC420may be electrically connected with the connector410. In various embodiments, the PDIC420may, for example, be a power delivery circuit of the USB type C standard. In various embodiments, the PDIC420may 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 PDIC420may transceive a PD message with the external electronic device402electrically connected through a CC pin of the connector410(for example, at least one of the CC1 pin, the CC2 pin of the connector310shown inFIG. 3C, or a combination thereof). In various embodiments, the PDIC420may be electrically connected with the processor430. In various embodiments, the PDIC420may deliver the PD message received from the external electronic device420to the processor430. In various embodiments, the PD message may include at least one of data regarding the number of data objects, a power role of the electronic device (for example, information regarding whether power is supplied to the external electronic device or received from the external electronic device), a version of a PD specification of the electronic device, and a data role of the electronic device410(for example, information regarding whether data is transmitted to the external electronic device or received from the external electronic device).

In various embodiments, the processor430may be included in the processor120shown inFIG. 1. In various embodiments, the processor430may include various processing circuitry and identify a connection with the external electronic device402based on at least one of a voltage applied to the power supply pin (for example, the VBUS pin shown inFIG. 3C) of the connector410, a voltage applied to the data pins (for example, the D+ pin or D− pin shown inFIG. 3C), or a combination thereof.

In various embodiments, when the electronic device401is connected with the external electronic device402, the processor430may receive a command from the external electronic device410through an initially activated channel. In various embodiments, the processor430may control the electronic device401to transmit a response to the command received through the initially activated channel to the external electronic device402through the initially activated channel. In various embodiments, the initially activated channel may be a communication channel between the electronic device401and the external electronic device402for at least one of US enumeration, USB configuration, or a combination thereof among a plurality of channels. In various embodiments, data transceived through the initially activated channel may be data that has a set end point address among data transceived through the data pins of the connector410. In various embodiments, data transceived through the initially activated channel may be data indicating an end point 0. For example, the initially activated channel may have an end point of 0. However, this should not be considered as limiting.

In various embodiments, when the electronic device401is connected with the external electronic device402, the processor430may receive a descriptor transmission command from the external electronic device402through the initially activated channel. In various embodiments, the processor430may receive the descriptor transmission command from the external electronic device402through the initially activated channel before driving an operating system (for example, the operating system142shown inFIG. 2). In various embodiments, in response to the descriptor transmission command, the processor430may load a descriptor stored in the memory491through a CCR driver (for example, a CCR driver431shown inFIG. 4B) included in a bootloader (not shown). In various embodiments, in response to the descriptor transmission command, the processor430may transmit the loaded descriptor to the external electronic device402through the initially activated channel. In various embodiments, the descriptor may include at least one of classification information of the electronic device401, USB specification information, size information of data transceivable through the initially activated channel, required power information, or a combination thereof.

In various embodiments, the processor430may receive a channel configuration command generated by the external electronic device402based on the descriptor from the external electronic device402through the initially activated channel before driving the operating system (for example, the operating system142shown inFIG. 2). In various embodiments, the processor430may receive a command from the external electronic device401through at least one of the initially activated channel, a channel allocated according to the channel configuration command, or a combination thereof, and may transmit a response to the command to the external electronic device402. In various embodiments, the processor430may exchange data with the external electronic device402through the initially activated channel even after a channel is allocated according to the channel configuration command. In various embodiments, the processor430may exchange data with the external electronic device402through the initially activated channel even after the operating system (for example, the operating system142shown inFIG. 2) is driven.

In various embodiments, the processor430may receive a control command from the external electronic device402through the initially activated channel. In various embodiments, the processor430may execute instructions stored in the memory491based on the control command. In various embodiments, the processor430may transmit a response to the control command to the external electronic device402through the initially activated channel. In various embodiments, the control command may include at least one of a start up command (START UP CMD), a shut down command (SHUT DOWN CMD), a wake up command (WAKE UP CMD), a sleep command (SLEEP CMD), a reboot command (REBOOT CMD), a CCR state transfer command (CCR STATE T/F CMD), a battery status transfer command (BATTERY STATUS T/F CMD), an application status transfer command (APP STATUS T/F CMD), or a combination thereof. Various embodiments of an operation regarding the control command will be described below.

Referring toFIG. 4A, in various embodiments, the external electronic device402may include at least one of the connector450, a PDIC460, a processor (e.g., including processing circuitry)470, a communication module (e.g., including communication circuitry)480, a power supply module (e.g., including power supply circuitry)490, and a memory495, or any combination thereof. In various embodiments, some elements may be omitted. In various embodiments, the external electronic device402may be included in the external electronic device102shown inFIG. 1. In various embodiments, the external electronic device402may be referred to as a command center rear adaptor (CCR AD) (hereinafter, referred to as “CCR AD”). In various embodiments, the memory491may be included in the memory130shown inFIG. 1. In various embodiments, the external electronic device402may further include a controller (not shown). In various embodiments, the controller (not shown) may be connected between the connector450and the processor470.

In various embodiments, the connector450may be an element corresponding to the connector410of the electronic device401. For example, when the connector410of the electronic device401is a female type connector, the connector450may be a male type connector. In various embodiments, the connector450may be included in the connector350shown inFIG. 3B. In various embodiments, the connector450may include various types of pins (for example, pins of the connector310shown inFIG. 3C) corresponding to the connector410.

In various embodiments, the PDIC460may be an element corresponding to the PDIC420of the electronic device401. In various embodiments, the PDIC460may be electrically connected with the connector450. In various embodiments, the PDIC460may include at least one of a CC logic, a PD logic, or a combination thereof. In various embodiments, the PDIC460may transceive a PD message with the electronic device401electrically connected through a CC pin of the connector450. In various embodiments, the PDIC460may be electrically connected with the processor470. In various embodiments, the PDIC460may deliver the PD message received from the electronic device401to the processor470.

In various embodiments, the processor470may be included in the processor120shown inFIG. 1. In various embodiments, the processor470may include various processing circuitry and generate a control message for the electronic device401in response to an event notification of an external electronic device403received through the communication module480. In various embodiments, the processor470may generate a control message for the electronic device401in response to an event notification which occurs by a user pushing an input button (not shown) (for example, a power key). In various embodiments, the input button (not shown) may be a physical button protruding to the outside through the housing (not shown) of the external electronic device402. In various embodiments, the processor470may generate a control message for the electronic device401based on a set condition (for example, a set time interval). In various embodiments, the processor470may transmit the control message to the electronic device401through an initially activated communication channel.

In various embodiments, the power supply module490may be electrically connected with the connector450. In various embodiments, the power supply module490may include various power supply circuitry and apply a set voltage (for example, 5V) to a power supply pin of the connector450. In various embodiments, when the connector410of the electronic device401is connected to the connector450, the power supply module490may supply power to the electronic device401by applying a set current (for example, 1A) to the power supply pin of the connector450. In various embodiments, the power supply module490may receive power from at least one of another external electronic device (for example, a battery of a car), a battery (not shown) embedded in the external electronic device, or a combination thereof. In various embodiments, the power supply module490may be included in the power management module188shown inFIG. 1.

The communication module480may include various communication circuitry and communicate with the external electronic device403. In various embodiments, the communication module480may receive at least one of an event notification of the external electronic device403, an event notification of a car in which the external electronic device403is mounted, or a combination thereof from the external electronic device403. In various embodiments, the communication module480may transmit the received event notification to the processor470. In various embodiments, the communication module480may receive, from the processor470, a command of the electronic device401received by the processor470through the connector450(for example, a car window open command, a car window close command, an indoor lamp turn on command, an indoor lamp turn off command, a volume control command). In various embodiments, the communication module480may transmit the received command of the electronic device401to the external electronic device403. In various embodiments, the communication module480may communicate with the external electronic device403through a controller area network (CAN) (hereinafter, referred to as “CAN”). However, this should not be considered as limiting. In various embodiments, the communication module480may be included in the communication module190shown inFIG. 1.

Referring toFIG. 4A, the external electronic device403may communicate with the external electronic device402. In various embodiments, the external electronic device403may, for example, be configured as a head unit of a car. In various embodiments, the external electronic device403may be an electronic device which is mounted in a car.

FIG. 4Bis a diagram illustrating an example of functional configurations of an electronic device401and external electronic devices402,403according to various embodiments.

Referring toFIG. 4B, in various embodiments, the external electronic device402may communicate with the external electronic device403through a communication module (for example, the communication module480ofFIG. 4A). In various embodiments, a processor (for example, the processor470ofFIG. 4A) of the external electronic device402may include various processing circuitry and drive a CCR AD driver461corresponding to a descriptor received from the electronic device401among a plurality of drivers stored in a memory (for example, the memory495ofFIG. 4A). In various embodiments, the processor of the external electronic device402may transmit a command to the electronic device401through the CCR AD driver461.

Referring toFIG. 4B, in various embodiments, a processor of the electronic device401(for example, the processor430ofFIG. 4A) may include various processing circuitry and drive a CCR driver431stored in a memory (for example, the memory491ofFIG. 4A). In various embodiments, the processor of the electronic device401may generate an event regarding a command received from the external electronic device402through the CCR driver431of a kernel432, and may deliver the event to a custom protocol manager433of a framework434. In various embodiments, the event may be a message to be delivered to the framework434from the kernel432in which the the CCR driver431is driven. In various embodiments, the kernel432, the framework434, and an application435may be included in a program436. In various embodiments, the kernel432may be included in the operating system142ofFIG. 2, the framework434may be included in the middleware144ofFIG. 2, the application435may be included in the application ofFIG. 2, and the program436may be included in the program140ofFIG. 2, but this should not be considered as limiting.

Referring toFIG. 4B, in various embodiments, the custom protocol manager433of the framework of the processor of the electronic device401may deliver a message corresponding to the event to the application435of the event. In various embodiments, the custom protocol manager433of the framework may deliver a response message to the event to the CCR driver431through a virtual file system (for example, Sysfs) node. In various embodiments, the virtual file system (for example, Sysfs) node may be a pseudo file system for providing an interface for the kernel432. In various embodiments, the Sysfs node may be a pseudo file system provided from a Linux kernel.

Referring toFIG. 4B, in various embodiments, the processor of the electronic device401may deliver the response message to the event to the external electronic device402through the CCR driver.

FIG. 5is diagram illustrating an example data transceiving process between the electronic device401and the external electronic device402according to various embodiments.

Referring toFIG. 5, in operation511, the processor470of the external electronic device402according to various embodiments may transmit a command (CMD) (hereinafter, referred to as “CMD”) to the electronic device401. In operation515, the processor430of the electronic device401may transmit acknowledgement (ACK) (hereinafter, referred to as “ACK”) to the external electronic device402, based on the CMD received from the external electronic device402.

Referring toFIG. 5, in operation531, the processor470of the external electronic device402according to various embodiments may transmit a CMD to the electronic device401. In operation533, the processor470of the external electronic device402may transmit data (DATA) (hereinafter, referred to as “DATA”) to the electronic device401based on the CMD. In operation535, the processor430of the electronic device401may transmit ACK to the external electronic device402, based on the CMD and the data received from the external electronic device402.

Referring toFIG. 5, in operation551, the processor470of the external electronic device402according to various embodiments may transmit a CMD to the electronic device401. In operation553, the processor430of the electronic device401may transmit data to the external electronic device402based on the CMD. In operation555, the processor470of the external electronic device402may transmit ACK to the electronic device401based on the data received from the electronic device401.

In various embodiments, the CMD transmitted in operation511,531,551may be data of a structure as shown, for example, in table 1 presented below:

As shown in table 1, the 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, for example, be fields which are defined in a setup packet format according to the USB standard.

In table 1, the bmRequest Type field may be 1 byte long. In various embodiments, an entity of the bmRequest Type field may have a value of 0xC0 or 0x40. In various embodiments, when the entity of the bmRequest Type field is 0xC0, the CMD may indicate that a request direction is from the electronic device401to the external electronic device402, a request type is a vendor type, a recipient is a device (for example, when the external electronic device402is a host, the device may be the electronic device401). In various embodiments, when the entity of the bmRequest Type field is 0x40, the CMD may indicate that a request direction is from the external electronic device402to the electronic device401, a request type is a vendor type, and a recipient is a device (for example, when the external electronic device402is a host, the device may be the electronic device401).

In table 1, the bRequest field may be 1 byte long. In various embodiments, an entity of the bRequest field may have a value of 0xF1. In various embodiments, when the entity of the bRequest field is 0xF1, the CMD may indicate a command which is newly defined to be distinct from standard device request codes according to the USB standard.

In table 1, the wValue field may be 2 bytes long. In various embodiments, an entity of the wValue field may have various values. In various embodiments, based on values of the entity of the wValue field, the CMD may indicate various message types. In various embodiments, various message types distinct from one another by values of the entity of the wValue field may be as shown, for example, in table 2 presented below:

In table 2, a CMD having the message type of START UP may be a CMD to boot the operating system (for example, the operating system142shown inFIG. 2) of the electronic device401. In various embodiments, a CMD having the message type of SHUT DOWN may be a CMD to shut down the operating system (for example, the operating system142shown inFIG. 2) of the electronic device401. In various embodiments, a CMD having the message type of REBOOT may be a CMD to reboot the operating system (for example, the operating system142shown inFIG. 2) of the electronic device401. In various embodiments, a CMD having the message type of SLEEP may be a CMD to turn off the display497. In various embodiments, a CMD having the message type of WAKE UP may be a CMD to turn on the display497. In various embodiments, a CMD of the message type of TOGGLE LOCK/UNLOCK may be a CMD to change ON-OFF states of the display497. In various embodiments, a CMD having the message type of CCR STATE REQUEST may be a CMD to request a current state of the electronic device401. In various embodiments, a CMD having the message type of CCR STATE TRANSFER may be a CMD to request a current state of the electronic device401. In various embodiments, a CMD having the message type of BATTERY STATUS REQUEST may be a CMD to request a current status of the battery491. In various embodiments, a CMD having the message type of BATTERY STATUS TRANSFER may be a CMD to request a current status of the battery491. In various embodiments, a CMD having the message type of APP ACTIVITY STATUS REQUEST may be a CMD to request a current status of the application435. In various embodiments, a CMD having the message type of APP ACTIVITY STATUS TRANSFER may be a CMD to request a current status of the application435.

When the entity of the wValue field is 0x0063, the message type of the 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 the 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 the 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 the 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 the 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 the 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 the CMD may be CCR STATE TRANSFER, the data phase may not be omitted, and data in the data phase may be transmitted from a CCR (for example, the electronic device401). In various embodiments, when the entity of the wValue field is 0x0096, the message type of the 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 the CMD may be BATTERY STATUS TRANSFER, the data phase may not be omitted, and data in the data phase may be transmitted from the CCR (for example, the electronic device401). In various embodiments, when the entity of the wValue field is 0x0098, the message type of the CMD may be APP ACTIVITY 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 data in the data phase may be transmitted from the CCR (for example, the electronic device401). In various embodiments, the data phase may indicate a time period during which data is transmitted after a CMD is transmitted and before ACK is transmitted. For example, when the data phase is omitted, the external electronic device402may transmit a CMD, and then, at the next message transceiving time, the electronic device401may transmit ACK. In another example, when the data phase is not omitted, the external electronic device402may transmit a CMD, and then, at the next message transceiving time, data may be transmitted from the external electronic device402or the electronic device401, and then, at the next message transceiving time, ACK may be transmitted from the electronic device401or the external electronic device402. Operations between the external electronic device402and the electronic device according to message types according to various embodiments will be described below.

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

Referring back to table 1, the wIndex field may be 2 bytes long. In various embodiments, an entity of the wIndex field may have various values. In various embodiments, based on a value of the entity of the wIndex field, the CMD may indicate a shut down time of the electronic device401.

In table 1, the wLength field may be 2 bytes long. In various embodiments, an entity of the wLength field may have various values. In various embodiments, based on a value of the entity of the wLength field, the CMD may indicate a length of data in a data phase.

In various embodiments, when a CMD transmitted to the electronic device401by the external electronic device402is a CMD indicating that a data phase is omitted, the electronic device401may transmit ACK to the CMD to the external electronic device402. In various embodiments, when a CMD transmitted to the electronic device401by the external electronic device402is a CMD indicating that a data phase is not omitted and data according to the data phase is transmitted by the external electronic device402, the external electronic device402may transmit the CMD and then transmit data to the electronic device401, and the electronic device401may transmit ACK to the data to the external electronic device402. In various embodiments, when a CMD transmitted to the electronic device401by the external electronic device402is a CMD indicating that a data phase is not omitted, and data according to the data phase is transmitted by the electronic device401, and the external electronic device402transmits the CMD, the electronic device401may transmit data to the external electronic device402based on the CMD, and the external electronic device402may transmit ACK to the data to the electronic device401. For example, based on a CMD transmitted to the electronic device401by the external electronic device402, processes of operations511and515may be performed, processes of operations531,533, and535may be performed, or processes of operations551,553, and555may be performed. Hereinbelow, at least one of data according to a CMD, ACK, or a combination thereof will not be described for the sake of brevity of explanation. However, when it is illustrated that a CMD is transmitted, at least one of the data according to the transmitted CMD, ACK, or a combination thereof may be transmitted.

In various embodiments, it may be determined whether data is transmitted, based on a value of the entity of the wValue field. For example, when the value of the entity of the wValue field of the CMD is a value corresponding to the message type indicating START UP, transmission of data may be omitted. In another example, when the value of the entity of the wValue field of the CMD is a value corresponding to the message type indicating CCR STATE TRANSFER, data may be transmitted. In various embodiments, a transmission entity of data may be determined based on a value of the entity of the bmRequest Type field. For example, when the value of the entity of the bmRequest Type field of the CMD is 0x40, the transmission entity of data may be the external electronic device402. In another example, when the value of the entity of the bmRequest Type field of the CMD is 0xC0, the transmission entity of data may be the electronic device401. In various embodiments, a length of data may be determined based on a value of the entity of the wLength field of the 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.

FIGS. 6A, 6B, 6C, 6D, 6E, and 6Fillustrate various example data transceiving processes between the electronic device401and the external electronic device402according to various embodiments.FIGS. 6A, 6B, 6C, 6D, 6E, and 6Fwill be described with reference to the configurations of the electronic device401, the external electronic device402, and the external electronic device403shown, for example, inFIG. 4A.

Referring toFIG. 6A, in operation611, when an event occurs in the external electronic device403, the external electronic device403may transmit an event notification regarding the occurred event to the external electronic device402. In various embodiments, the processor470of the external electronic device402may receive the event notification from the external electronic device403through the communication module480. In various embodiments, the event may be a front door open event of a car in which the external electronic device403is mounted. In various embodiments, the front door open event may be an event in which at least one of the front doors of the car in which the external electronic device403is mounted is opened. However, this should not be considered as limiting. In various embodiments, the car in which the external electronic device403is mounted may be a car including front doors and rear doors.

In operation613, the processor470of the external electronic device402may turn on a power supply pin (for example, the VBUS pin shown inFIG. 3C) (VBUS ON) by applying at least one of a set voltage, current, or a combination thereof to the power supply pin (for example, the VBUS pin shown inFIG. 3C) based on the received event notification. In various embodiments, the processor470of the external electronic device402may control the power supply module490to apply at least one of the set voltage, current, or a combination thereof to the power supply pin. In various embodiments, the processor470of the external electronic device402may supply power to the electronic device401connected to the connector450by controlling the power supply module490to apply at least one of the set voltage, current, or a combination thereof to the power supply pin (for example, the VBUS pin shown inFIG. 3C). In various embodiments, the processor470of the external electronic device402may refine a state of the electronic device401into a charging state based on the power supply pin (for example, the VBUS pin shown inFIG. 3C) being turned on. In various embodiments, the state of the electronic device401may be stored in the memory495of the external electronic device402.

In operation615, the battery440of the electronic device401may be charged using power supplied from the external electronic device402through the connector410. In various embodiments, when at least one of the set voltage, current, or a combination thereof is applied to the power supply pin of the connector410, the processor430of the electronic device401may apply a set voltage to the data pin of the connector410. In various embodiments, when at least one of the set voltage, current, or a combination thereof is applied to the power supply pin of the connector410, the processor430of the electronic device401may drive the operating system according to a low power mode stored in the memory491. In various embodiments, when at least one of the set voltage, current, or a combination thereof is applied to the power supply pin of the connector410, the processor430of the electronic device401may drive the bootloader (not shown) and may drive the operating system according to the stored low power mode. In various embodiments, the processor430of the electronic device401may drive a CCR driver (for example, the CCR driver431shown inFIG. 4B) included in the bootloader. In various embodiments, when the CCR driver included in the bootloader (not shown) is driven, the processor430of the electronic device401may receive a command from the external electronic device402through an initially activated channel.

Referring toFIG. 6B, in operation621, when an event occurs in the external electronic device403, the external electronic device403may transmit an event notification regarding the occurred event to the external electronic device402. In various embodiments, the processor470of the external electronic device402may receive the event notification from the external electronic device403through the communication module480. In various embodiments, the event may be a rear door open event of a car in which the external electronic device403is mounted. In various embodiments, the rear door open event may be an event in which at least one of the rear doors of the car in which the external electronic device403is mounted is opened. In various embodiments, the car in which the external electronic device403is mounted may be a car including front doors and rear doors. In various embodiments, the processor470of the external electronic device402may identify whether an event notification occurs through an input button (not shown) (for example, a power key) of the external electronic device402. In various embodiments, the processor470of the external electronic device402may identify that an event notification occurs when a user pushes an input button (not shown) (for example, the power key) of the external electronic device402for a set time in an off-state of the electronic device401.

In operation622, the processor470of the external electronic device402may turn on the power supply pin (for example, the VBUS pin shown inFIG. 3C) (VBUS ON) by applying at least one of a set voltage, current, or a combination thereof to the power supply pin (for example, the VBUS pin shown inFIG. 3C), based on the received event notification. In various embodiments, the processor470of the external electronic device402may refine a state of the electronic device401into a charging state based on the power supply pin (for example, the VBUS pin shown inFIG. 3C) being turned on. In various embodiments, the state of the electronic device401may be stored in the memory495of the external electronic device402.

In operation623, the battery440of the electronic device401may be charged using power supplied from the external electronic device402through the connector410. In various embodiments, when at least one of the set voltage, current, or a combination thereof is applied to the power supply pin of the connector410, the processor430of the electronic device401may drive the operating system according to the low power mode stored in the memory491. In various embodiments, when at least one of the set voltage, current, or a combination thereof is applied to the power supply pin of the connector410, the processor430of the electronic device401may drive the bootloader (not shown) and may drive the operating system according to the low power mode stored in the memory491. In various embodiments, the processor430of the electronic device401may drive a CCR driver (for example, the CCR driver431shown inFIG. 4B) included in the bootloader (not shown). In various embodiments, when the CCR driver included in the bootloader (not shown) is driven, the processor430of the electronic device401may receive a command from the external electronic device402through an initially activated channel.

In operation624, the processor470of the external electronic device402may detect the electronic device401based on at least one of the voltage, current of the power supply pin of the connector450, or a combination thereof. In various embodiments, the processor470of the external electronic device402may detect the electronic device401by detecting a drop of the at least one of the voltage, current of the power supply pin, or a combination thereof that occurs as power is supplied to the electronic device401through the power supply pin of the connector450. In various embodiment, when at least one of the set voltage, current or a combination thereof is applied to the power supply pin of the connector410, the processor430of the electronic device401may apply a set voltage to the data pin of the connector410. In various embodiments, when the set voltage is applied to the data pin, the processor470of the external electronic device402may obtain transmission speed information of the electronic device401through the data pin. In various embodiments, the processor470of the external electronic device402may perform at least one of enumeration, configuration of the electronic device401, or a combination thereof through the initially activated channel, based on the obtained transmission speed information.

In operation625, the processor470of the external electronic device402may transmit a start up command (START UP CMD) to the electronic device401through the initially activated channel, based on the obtained transmission speed information. In various embodiments, the start up command may be configured as shown, for example, in table 3 presented below:

As shown in table 3, the entity of the bmRequest Type field of the start up command may be 0x40, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0063, the entity of the wIndex field may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the start up command may indicate that a request direction is from the external electronic device402to the electronic device401, a request type is a vendor type, and a recipient is a device (for example, the device may be the electronic device401when the external electronic device402is a host) through the bmRequest Type field. In various embodiments, the start up command may indicate a newly defined command through the bRequest field. In various embodiments, the start up command may indicate that a message type is START UP and a data phase is omitted through the wValue field. In various embodiments, the start up command may not indicate a shut down time of the electronic device401through the wIndex field. In various embodiments, the start up command may indicate that a data phase is omitted through the wLength field. In various embodiments, the bmRequest Type, bRequest, wValue, wIndex, and wLength fields of the start up command (START UP CMD) may be fields that are defined in the setup packet format according to the USB standard.

In operation626, the processor430of the electronic device401may boot (drive) the operating system (for example, the operating system142shown inFIG. 2) stored in the memory491of the electronic device401, based on the start up command (START UP CMD). In various embodiments, the processor430of the electronic device401may drive the bootloader (not shown) and may boot (drive) the operating system (for example, the operating system142shown inFIG. 2) stored in the memory491. In various embodiments, when the operating system is driven according to the low power mode, the processor430of the electronic device401may shut down the operating system according to the low power mode and then may drive the bootloader (not shown) and boot the operating system stored in the memory (not shown). In various embodiments, when the processor430of the electronic device401receives the start up command, the processor430of the electronic device401may transmit ACK to the start up command to the external electronic device402.

In operation627, the processor470of the external electronic device402may transmit a CCR state transfer command (CCR STATE T/F CMD) to the electronic device401. In various embodiments, the processor470of the external electronic device402may generate the CCR state transfer command based on a set condition (for example, a set time interval). In various embodiments, the processor470of the external electronic device402may generate the CCR state transfer command at the set time intervals after transmitting the start up command to the electronic device401. In various embodiments, the CCR state transfer command may be configured as shown, for example, in table 4 presented below:

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 of the wIndex may be 0x0000, and the entity of the wLength field may be 0x0100. In various embodiments, the CCR state transfer command may indicate that a request direction is from the electronic device401to the external electronic device402, a request type is a vendor type, and a recipient is a device through the bmRequest Type field. In various embodiments, the CCR state transfer command may indicate that a message type is CCR STATE TRANSFER, and there exists a data phase through the wValue field. In various embodiments, the CCR state transfer command may indicate that data according to the data phase is 1 byte long through the wLength field. 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 that are defined in the setup packet format according to the USB standard.

In various embodiments, when the processor470of the external electronic device402does not receive a response to the CCR state transfer command from the electronic device401for a set time after transmitting the CCR state transfer command to the electronic device401, the processor470may transmit the CCR state transfer command to the electronic device401again.

In operation628, the processor430of the electronic device401may identify a current state (CURRENT STATE) based on the CCR state transfer command (CCR STATE T/F CMD). In various embodiments, the processor430of the electronic device401may generate data indicating the identified current state and may transmit the data to the external electronic device402. In various embodiments, the processor430of the electronic device401may generate data indicating the current state among set states, and may transmit the data to the external electronic device402. In various embodiments, the set states may include an unidentified state, a charging state, an on attachment state, a dimming attachment state, a power off state, or a shut down state. For example, when the processor430is being booted at the time of receiving the CCR state transfer command (CCR STATE T/F CMD), the processor430may generate data indicating that the processor430of the electronic device401in the data phase is in the booting state, and may transmit the data to the external electronic device402. In another example, when the processor430of the electronic device401completes booting at the time of receiving the CCR state transfer command (CCR STATE T/F COMMAND), and then a display (for example, the display497shown inFIG. 4A) is turned on, the processor430of the electronic device401in a data phase may generate data indicating a screen-on state after booting, and may transmit the data to the external electronic device402.

In various embodiments, when the processor470of the external electronic device402receives the data indicating the current state, the processor470of the external electronic device402may transmit ACK to the data indicating the current state to the electronic device401. In various embodiments, the processor470of the external electronic device402may refine the current state of the electronic device401stored in the memory495, based on the data indicating the current state.

Referring toFIG. 6C, in operation631, when an event occurs, the external electronic device403may transmit an event notification regarding the occurred event to the external electronic device402. In various embodiments, the processor470of the external electronic device402may receive the event notification from the external electronic device403through the communication module480. In various embodiments, the event may be a user get-off event of a car in which the external electronic device403is mounted. In various embodiments, the user get-off event may be an event in which a user sitting in a seat between rear doors of the car in which the external electronic device403is mounted gets off the car. However, this should not be considered as limiting. In various embodiments, the processor470of the external electronic device402may identify occurrence of an event notification through an input button (not shown) of the external electronic device402. In various embodiments, the processor470of the external electronic device402may identify that an event notification occurs when a user pushes an input button (not shown) (for example, a power key) of the external electronic device402for a set time in an off state of the electronic device401.

In operation632, the processor470of the external electronic device402may transmit a shut down command (SHUT DOWN CMD) to the electronic device401through an initially activated channel, based on the received event notification. In various embodiments, the shut down command may be configured as shown, for example, in table 5 presented below:

As shown in table 5, the entity of the bmRequest Type field of the shut down command may be 0x40, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0064, the entity of the wIndex field may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the shut down command may indicate that a message type is SHUT DOWN and a data phase is omitted through the wValue field. In various embodiments, when the message type of the wValue field indicates SHUT DOWN, an entity value of the wIndex field of the shut down command may indicate that the operating system is terminated after a set time. For example, when the message type of the wValue field indicates SHUT DOWN and an entity value of the wIndex field of the shut down command is 0x0000, the shut down command may indicate that the operating system is immediately terminated. In another example, when the message type of the wValue field indicates SHUT DOWN, and an entity value of the wIndex field of the shut down command is 0x0A00, the shut down command may indicate that the operating system is terminated after 10 seconds. In various embodiments, the bmRequest Type, bRequest, wValue, wIndex, and wLength fields of the shut down command (SHUT DOWN CMD) may be fields that are defined in the setup packet format according to the USB standard.

In operation633, the processor430of the electronic device401may terminate the running operating system (for example, the operating system142shown inFIG. 2) based on the shut down command. In various embodiments, when the electronic device401receives the shut down command, the processor430of the electronic device401may transmit ACK to the shut down command to the external electronic device402.

In operation634, the processor470of the external electronic device402may transmit a CCR state transfer command (CCR STATE T/F CMD) to the electronic device401. In various embodiments, the processor470of the external electronic device402may generate the CCR state transfer command based on a set condition (for example, a set time interval). In various embodiments, the processor470of the external electronic device402may generate the CCR state transfer command at the set time intervals after transmitting the shut down command. In various embodiments, the CCR state transfer command may be configured as shown in table 4 presented above.

In operation635, the processor430of the electronic device401may identify a current state (CURRENT STATE) based on the CCR state transfer command. In various embodiments, the processor430of the electronic device401may generate data indicating the identified current state, and may transmit the data to the external electronic device402. For example, when the processor430completes termination of the operating system at the time of receiving the CCR state transfer command, the processor430may generate data indicating that the processor430of the electronic device401in the data phase is in a shut down state, and may transmit the data to the external electronic device402.

In various embodiments, when the processor470of the external electronic device402receives the data indicating the current state, the processor470of the external electronic device402may transmit ACK to the data indicating the current state to the electronic device401. In various embodiments, the processor470of the external electronic device402may refine the current state of the electronic device401stored in the memory495based on the data indicating the current state.

In operation636, when the processor of the external electronic device402receives the data indicating the shut down state, the processor of the external electronic device402may turn off at least one of a voltage, current of the power supply pin (for example, the VBUS pin ofFIG. 3C), or a combination thereof (VBUS OFF). In various embodiments, the processor470of the external electronic device402may control the power supply module490to turn off at least one of a set voltage, current applied to the power supply pin, or a combination thereof. In various embodiments, the processor470of the external electronic device402may stop power supply to the electronic device401connected to the connector450by controlling the power supply module490to turn off at least one of the set voltage, current applied to the power supply pin, or a combination thereof.

Referring toFIG. 6D, in operation641, the processor470of the external electronic device402may identify occurrence of an event. In various embodiments, when a user pushes an input button (not shown) (for example, the power key) of the external electronic device402in an off state of the display497after booting of the electronic device401is completed, the processor470of the external electronic device402may identify that an event occurs. However, this should not be considered as limiting.

In operation642, the processor470of the external electronic device402may transmit a wake up command (WAKE UP CMD) to the electronic device401through an initially activated channel, based on the received event notification. In various embodiments, the wake up command may be configured as shown, for example, in table 6 presented below:

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 of the wIndex field may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the wake up command may indicate that a message type is WAKE UP and a data phase is omitted through the wValue field. In various embodiments, the bmRequest Type, bRequest, wValue, wIndex, and wLength fields of the wake up command (WAKE UP CMD) may be fields that are defined in the setup packet format according to the USB standard.

In operation643, the processor430of the electronic device401may turn on the display497of the electronic device401(DISPLAY ON) based on the wake up command. In various embodiments, when the electronic device401receives the wake up command, the processor430of the electronic device401may transmit ACK to the wake up command to the external electronic device402. In various embodiments, the processor470of the external electronic device402may refine a state of the electronic device401into a display on state after booting, based on the ACK to the wake up command.

In operation644, the processor470of the external electronic device402may transmit a CCR state transfer command (CCR STATE T/F CMD) to the electronic device401. In various embodiments, the CCR state transfer command may be configured as shown in table 4 presented above.

In operation645, the processor430of the electronic device401may identify a current state (CURRENT STATE) based on the CCR state transfer command. In various embodiments, the processor430of the electronic device401may generate data indicating the identified current state and may transmit the data to the external electronic device402. In various embodiments, when the processor470of the electronic device402receives the data indicating the current state, the processor470of the external electronic device402may transmit ACK to the data indicating the current state to the electronic device401. In various embodiments, the processor470of the external electronic device402may refine the current state of the electronic device401stored in the memory495based on the data indicating the current state.

Referring toFIG. 6E, in operation651, the processor470of the external electronic device402may identify occurrence of an event. In various embodiments, when a user pushes an input button (not shown) (for example, the power key) of the external electronic device402in an on state of the display497after booting of the electronic device401is completed, the processor470of the external electronic device402may identify that an event occurs. However, this should not be considered as limiting.

In operation652, the processor470of the external electronic device402may transmit a sleep command (SLEEP CMD) to the electronic device401through an initially activated channel, based on the identified event notification. In various embodiments, the sleep command may be configured as shown, for example, in table 7 presented below:

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 of the wIndex field may be 0x0000, and the entity of the wLength field may be 0x0000. In various embodiments, the sleep command may indicate that a message type is SLEEP and a data phase is omitted through the wValue field. In various embodiments, the bmRequest Type, bRequest, wValue, wIndex, and wLength fields of the sleep command (SLEEP CMD) may be fields that are defined in the setup packet format according to the USB standard.

In operation653, the processor430of the electronic device401may turn off the display497of the electronic device401(DISPLAY OFF) based on the sleep command. In various embodiments, when the electronic device401receives the sleep command, the processor430of the electronic device401may transmit ACK to the sleep command to the external electronic device402.

In operation654, the processor430of the electronic device401may transmit a CCR state transfer command (CCR STATE T/F CMD) to the electronic device401. In various embodiments, the CCR state transfer command may be configured as shown in table 4 presented above.

In operation655, the processor430of the electronic device401may identify a current state (CURRENT STATE) based on the CCR state transfer command. In various embodiments, the processor430of the electronic device401may generate data indicating the identified current state and may transmit the data to the external electronic device402. In various embodiments, when the processor470of the external electronic device402receives the data indicating the current state, the processor470of the external electronic device402may transmit ACK to the data indicating the current state to the electronic device401. In various embodiments, the processor470of the external electronic device402may refine the current state of the electronic device401stored in the memory495based on the data indicating the current state.

Referring toFIG. 6F, in operation661, the processor470of the external electronic device402may identify occurrence of an event. In various embodiments, when ACK to a CMD is not received in a state in which a user completes booting of the electronic device401, the processor470of the external electronic device402may identify that an event occurs. However, this should not be considered as limiting. In various embodiments, the processor470of the external electronic device402may identify that an event occurs when a user pushes input buttons (not shown) (for example, a power button) of the external electronic device402during a set period. However, this should not be considered as limiting.

In operation662, the processor470of the external electronic device402may transmit a reboot command (REBOOT CMD) to the electronic device401through an initially activated channel, based on the event notification. In various embodiments, the reboot command may be configured as shown, for example, in table 8 presented below:

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

In operation663, the processor430of the electronic device401may reboot after terminating the running operating system (for example, the operating system142shown inFIG. 2), based on the reboot command. In various embodiments, when the running operating system (for example, the operating system142shown inFIG. 2) is terminated, the processor430of the electronic device401may drive the bootloader (not shown) and may reboot the operating system (for example, the operating system142shown inFIG. 2). In various embodiments, when the electronic device401receives the reboot command, the electronic device401may transmit ACK to the reboot command to the external electronic device402.

In operation664, the processor430of the electronic device401may transmit a CCR state transfer command (CCR STATE T/F CMD) to the electronic device401. In various embodiments, the CCR state transfer command may be configured as shown in table 4 presented above.

In operation665, the processor430of the electronic device401may identify a current state (CURRENT STATE) based on the CCR state transfer command. In various embodiments, the processor430of the electronic device401may generate data indicating the identified current state, and may transmit the data to the external electronic device402. In various embodiments, when the processor470of the external electronic device402receives the data indicating the current state, the processor470of the external electronic device402may transmit ACK to the data indicating the current state to the electronic device401. In various embodiments, the processor470of the external electronic device402may refine the current state of the electronic device401stored in the memory495based on the data indicating the current state.

FIG. 7is a diagram illustrating example states of the electronic device401according to various embodiments.FIG. 7will be described with reference to the configurations of the electronic device401, the external electronic device402, and the external electronic device403shown inFIG. 4A.

As shown inFIG. 7, the electronic device401may have various states. In various embodiments, when the external electronic device402is connected with the electronic device401through the connector450, the external electronic device402may obtain information regarding a current state of the electronic device401through data regarding a CCR state transfer command (CCR STATE T/F CMD).

Referring toFIG. 7, in various embodiments, a power off state710(POWER OFF) may indicate that the processor430is in an OFF state, a controller (not shown) (for example, a USB controller) is in an OFF state, and the display497is in an OFF state. In various embodiments, the OFF state of the controller (not shown) (for example, the USB controller) may indicate a state in which a set voltage is not applied to the power supply pin (for example, the VBUS pin shown inFIG. 3C) among the pins of the connector410. In various embodiments, in the power off state710(POWER OFF), the electronic device401may be shifted to a charging state720(CHARGING) when the power supply pin of the connector450of the external electronic device402is turned on (VBUS ON), and at least one of a set voltage, current or a combination thereof is applied to the power supply pin.

Referring toFIG. 7, according to various embodiments, the charging state720(CHARGING) may indicate that the processor430is in an ON state in which the operating system according to the low power mode (LPM) is driven, the controller (not shown) (for example, the USB controller) is in an ON state, and the display497is in an ON state. In various embodiments, the ON state of the controller (not shown) (for example, the USB controller) may indicate a state in which a set voltage is applied to the power supply pin (for example, the VBUS pin shown inFIG. 3C) among the pins of the connector410. In various embodiments, when the electronic device401receives a start up command (START UP) from the external electronic device402in the charging state720(CHARGING), the electronic device401may be shifted to an on attachment state730(ON ATTACHED). In various embodiments, when the electronic device401is detached from the external electronic device (DETACHED) in the charging state720(CHARGING), the electronic device401may be shifted to the power off state710(POWER OFF).

Referring toFIG. 7, the on attachment state730(ON ATTACHED) may indicate that the processor430is in the ON state in which the operating system (for example, the operating system142shown inFIG. 2) is driven, the controller (not shown) (for example, the USB controller) is in the ON state, and the display497is in the ON state. In various embodiments, the operating system running in states other than the charging state720(CHARGING) may be distinct from the operating system of the lower power mode running in the charging state720(CHARGING). However, this should not be considered as limiting.

In various embodiments, when the electronic device401receives a reboot command (REBOOT) from the external electronic device402in the on attachment state730(ON ATTACHED), the electronic device401may be shifted to the on attachment state730(ON ATTACHED). In various embodiments, when the electronic device401receives a sleep command from the external electronic device402in the on attachment state730(ON ATTACHED), the electronic device401may be shifted to a dimming attachment state740(DIMMING ATTACHED). In various embodiments, when the electronic device401does not receive a user input through a touch screen (not shown) of the display497or does not receive a command from the external electronic device402for a set time in the on attachment state730(ON ATTACHED), the electronic device401may be shifted to the dimming attachment state740(DIMMING ATTACHED). In various embodiments, when the electronic device401receives a shut down command (SHUT DOWN) from the external electronic device402in the on attachment state730(ON ATTACHED), the electronic device401may be shifted to a shut down state750(SHUT DOWN). In various embodiments, when the electronic device401is detached from the external electronic device402in the on attachment state730(ON ATTACHED), the electronic device401may be shifted to an on detachment state760(ON DETACHED). In various embodiments, when THE voltage of the power supply pin of the connector410falls out of a set voltage range (for example, 4.5 V or higher), the processor430of the electronic device401may identify that the electronic device401is detached from the external electronic device402.

Referring toFIG. 7, the dimming attachment state740(DIMMING ATTACHED) may indicate that the processor430is in the ON state in which the operating system is driven, the controller (not shown) (for example, the USB controller) is in the ON state, and the display497is in the OFF state. In various embodiments, the dimming attachment state740(DIMMING ATTACHED) may be a state in which the electronic device401may turn off the display497while reducing illuminance of the display497. In various embodiments, when the electronic device401receives a wake up command (WAKE_UP) from the external electronic device402in the dimming attachment state740(DIMMING ATTACHED), the electronic device401may be shifted to the on attachment state730(ON ATTACHED). In various embodiments, when the electronic device401is detached from the external electronic device402in the dimming attachment state740(DIMMING ATTACHED), the electronic device401may be shifted to the on detachment state760(ON DETACHED).

Referring toFIG. 7, the shut down state750may indicate that the processor430is in the ON state in which the operating system (for example, the operating system142shown inFIG. 2) is driven, the controller (not shown) (for example, the USB controller) is in the OFF state, and the display497is in the ON state. In various embodiment, when the power supply pin of the connector450of the external electronic device402is turned off (VBUS_OFF) and power supply from the external electronic device402is stopped in the shut down state750(SHUT DOWN), the electronic device401may be shifted to the power off state710(POWER OFF). In various embodiments, when a voltage of the power supply pin of the connector410falls out of a set voltage range (for example, 4.5 V or higher), the electronic device401may identify that power supply from the external electronic device402is stopped.

Referring toFIG. 7, the on detachment state760(ON DETACHED) may indicate that the processor430is in the ON state in which the operating system (for example, the operating system142shown inFIG. 2) is driven, the controller (not shown) (for example, the USB controller) is in the ON state, and the display497is in the ON state. In various embodiments, when the electronic device401is attached to the external electronic device402in the on detachment state760(ON DETACHED), the electronic device401may be shifted to the on attachment state730(ON ATTACHED). In various embodiments, when a voltage of the power supply pin of the connector410falls within the set voltage range (for example, 4.5 V or higher), the processor430of the electronic device401may identify that the electronic device401is attached to the external electronic device402. In various embodiments, when the electronic device401does not receive a user input through an input device (for example, a touch screen) for a set time in the on detachment state760(ON DETACHED), the electronic device401may be shifted to a dimming detachment state770(DIMMING DETACHED) after a set time (IN T SEC). In various embodiments, when a user pushes an input button (not shown) (for example, the power key) in the on detachment state760(ON DETACHED), the electronic device401may be shifted to a sleep detachment state780(SLEEP DETACHED).

Referring toFIG. 7, the dimming detachment state770(DIMMING DETACHED) may indicate that the processor430is in the ON state in which the operating system (for example, the operating system142shown inFIG. 2) is driven, the controller (not shown) (for example, the USB controller) is in the ON state, and the display497is in the OFF state. In various embodiments, the dimming detachment state770(DIMMING DETACHED) may be a state in which the electronic device401turns off the display497while reducing illuminance of the display497. In various embodiments, when the electronic device401is attached to the external electronic device402in the dimming detachment state770(DIMMING DETACHED), the electronic device401may be shifted to the on attachment state730(ON ATTACHED). In various embodiments, when a user input is not received through an input device (for example, a touch screen) for a set time in the dimming detachment state770(DIMMING DETACHED), the electronic device401may be shifted to the sleep detachment state780(SLEEP DETACHED) after a set time (IN T SEC).

Referring toFIG. 7, the sleep detachment state780(SLEEP DETACHED) may indicate that the processor430is in the ON state in which the operating system (for example, the operating system142shown inFIG. 2) is driven, the controller (not shown) (for example, the USB controller) is in the ON state, and the display497is in the OFF state. In various embodiments, when the electronic device401is attached to the external electronic device402in the sleep detachment state780(SLEEP DETACHED), the electronic device401may be shifted to the on attachment state730(ON ATTACHED). In various embodiments, when the user pushes an input button (for example, the power key) in the sleep detachment state780(SLEEP DETACHED), the electronic device401may be shifted to the on detachment state760(ON DETACHED).

FIG. 8Ais a diagram illustrating an example data transceiving process between an electronic device and an external electronic device according to various embodiments.FIG. 8Awill be described with reference to the configurations of the electronic device401, the external electronic device402, and the external electronic device403shown inFIG. 4A.

Referring toFIG. 8A, in operation811, the processor470of the external electronic device402may generate a battery status transfer command (BATTERY STATUS T/F CMD), and may transmit the generated battery status transfer command (BATTERY STATUS T/F CMD) to the electronic device401. In various embodiments, the processor470of the external electronic device402may generate the battery status transfer command based on a set condition (for example, a set time interval). In various embodiments, the processor470of the external electronic device402may generate the battery status transfer command at the set time intervals after a state of the electronic device401is refined into the on attachment state. In various embodiments, the battery status transfer command may be configured as shown, for example, in table 9 presented below:

As shown in table 9, the entity of the bmRequest Type field of the battery status transfer command may be 0xC0, the entity of the bRequest field may be 0xF1, the entity of the wValue field may be 0x0097, the entity of the wIndex field may be 0x0000, and the entity of the wLength field may be 0x0004. In various embodiments, the battery status transfer command may indicate that a request direction is from the electronic device401to the external electronic device402, a request type is a vendor type, and a recipient is a device (for example, when the external electronic device402is a host, the device is the electronic device401), through the bmRequest Type field. In various embodiments, the battery status transfer command may indicate that a message type is BATTERY STATUS TRANSFER and there exists a data phase, through the wValue field. In various embodiments, the battery status transfer command may indicate that data according to the data phase is 4 bytes long, through the wLength field. 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 that are defined in the setup packet format according to the USB standard.

In operation812, the processor430of the electronic device401may identify a current status of the battery440of the electronic device401, based on the battery status transfer command, may generate data indicating the identified current status of the battery440, and may transmit the data to the external electronic device402. In various embodiments, the data indicating the current status of the battery440may be configured as shown, for example, in table 10 presented below:

As shown in table 10, the data indicating the current status of the battery440may be configured with battery level, battery health, charging state, and battery temperature fields.

In table 10, the battery level field may be 1 byte long. In various embodiments, an entity of the battery level field may have an integer value between 0 and 100 or a value of 255. In various embodiments, an integer value between 0 and 100 that the entity of the battery level field may have may indicate a value according to a charging percentage of the battery. In various embodiments, when the entity of the battery level field indicates an integer value of 255, it may be indicated that the charging percentage of the battery440is not known.

In table 10, the battery health field may be 1 byte long. In various embodiments, the entity of the battery health field may have values corresponding to types of battery health. In various embodiments, when there are seven types of battery health set, the entity of the battery health field may have 7 values. For example, when types of battery health are set to an unknown state, a good state, an over heat state, a dead state, an over voltage state, an unspecified failure state, or a cold state, the entity of the battery health may have a value indicating one of the unknown state, the good state, the over heat state, the dead state, the over voltage state, the unspecified failure state, or the cold state.

In table 10, the charging state field may be 1 byte long. In various embodiments, the entity of the charging state field may have values corresponding to set types of charging states. In various embodiments, when there are five types of charging states set, the entity of the charging state field may have 5 values. For example, when types of charging states are set to a unknown state, a charging state, a discharging state, a not-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 not-charging state, or the full state.

In table 10, the battery temperature field may be 1 byte long. In various embodiments, the entity of the battery temperature field may have an integer value between −128 and 127. In various embodiments, an integer value between −128 and 127 that the entity of the battery temperature field may have may indicate a value according to temperature of the battery.

In various embodiments, when the processor470of the external electronic device402receives the data indicating the current status of the battery440, the processor470of the external electronic device402may transmit ACK to the data indicating the current status of the battery440to the electronic device401. In various embodiments, the processor470of the external electronic device402may refine the current status of the battery440of the electronic device401based on the data indicating the current status of the battery440.

In various embodiments, the processor470of the external electronic device402may control the power supply pin based on the data indicating the current status of the battery received. In various embodiments, the processor470of the external electronic device402may determine whether to apply at least one of a set voltage, current or a combination thereof to the power supply pin, based on the data indicating the current status of the battery440received. For example, when the data indicating the current status of the battery440indicates the over heat state, the processor470of the external electronic device402may stop power supply to the electronic device401connected to the connector450by controlling the power supply module490to turn off the at least one of the voltage, current applied to the power supply pin, or a combination thereof. In another example, when the data indicating the current status of the battery440indicates a battery level lower than or equal to a set level, the processor470of the external electronic device402may supply power to the electronic device401connected to the connector450by controlling the power supply module490to apply at least one of the set voltage, current or a combination thereof to the power supply pin. However, this should not be considered as limiting.

FIG. 8Bis a diagram illustrating an example data transceiving process between an electronic device and an external electronic device according to various embodiments.FIG. 8Bwill be described with reference to the configurations of the electronic device401, the external electronic device402, and the external electronic device403shown inFIG. 4A.

Referring toFIG. 8B, in operation821, the processor470of the external electronic device402may transmit an application status transfer command (APP STATUS T/F CMD) to the electronic device401. In various embodiments, the processor470of the external electronic device402may generate the application status transfer command based on a set condition (for example, a set time interval). In various embodiments, the processor470of the external electronic device402may generate the application status transfer command at the set time intervals after a state of the electronic device401is refined into the on attachment state. In various embodiments, the application status transfer command may be configured as shown, for example, in table 11 presented below:

As shown in table 11, the entity of the bmRequest Type field of the application 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 of the wIndex field may be 0x0000, and the entity of the wLength field may be 0x0001. In various embodiments, the application status transfer command may indicate that a request direction is from the electronic device401to the external electronic device402, a request type is a vendor type, and a recipient is a device (for example, when the external electronic device402is a host, the device is the electronic device401), through the bmRequest Type field. In various embodiments, the application status transfer command may indicate that a message type is APP ACTIVITY STATUS TRANSFER and there exists a data phase, through the wValue field. In various embodiments, the application status transfer command may indicate that data according to the data phase is 1 byte long, through the wLength field. 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 that are defined in the setup packet format according to the USB standard.

In operation822, the processor430of the electronic device401may identify a current status of a running application (for example, the application146ofFIG. 2) of the electronic device401, based on the application status transfer command, may generate data indicating the identified current status of the application (for example, the application146ofFIG. 2), and may transmit the data to the external electronic device402. In various embodiments, the current status of the running application may be one of an application activity state, an unknown state, an operating system-not-running state, a foreground activity state (activity in foreground), a background activity state (activity in background), an activity-not-running state, or a command touch APP not-installed state.

In various embodiments, when the processor470of the external electronic device402receives the data indicating the current status of the running application, the processor470of the external electronic device402may transmit ACK to the data indicating the current status of the running application to the electronic device401. In various embodiments, the processor470of the external electronic device402may refine the current status of the running application of the electronic device401based on the data indicating the current status of the running application.

According to various example embodiments as described above, an electronic device (for example, the electronic device401) may include: a connector configured to be connected with an external electronic device; a memory configured to store instructions; and a processor configured to execute the stored instructions, the instructions, when executed by the processor, cause the processor to control the electronic device to: identify a control signal received through a channel initially activated based on the external electronic device being connected to the connector from among a plurality of channels, and to perform control based on a message included in the identified control signal.

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

In various embodiments, the message included in the identified control signal may include a start up command, and the processor may be configured to control the electronic device to drive a second operating system based on the start up command included in the message.

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

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

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

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

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

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

According to various example embodiments as described above, an electronic device (for example, the electronic device402) may include: a connector configured to be electrically connected with an external electronic device; a communication module comprising communication circuitry 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 to: based on an event being received from the another external electronic device, control the connector to supply a power to the external electronic device; and based on the power being supplied to the external electronic device, to generate a control signal to be transmitted through a channel initially activated based on the external electronic device being electrically connected to the connector from among a plurality of channels. The connector may be configured to transmit the generated control signal to the external electronic device, such that the external electronic device performs control based on a message included in the generated control signal.

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

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

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 to generate another control signal to be transmitted through the initially activated channel, based on a response to at least one control signal among a plurality of control signals transmitted to the external electronic device through the initially activated channel, not being received from the external electronic device. A message included in the another control signal may include a reboot command, and the external electronic device may be configured to drive the operating system again based on the reboot command included in the message included in the another control signal.

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

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 to generate another control signal to be transmitted through the initially activated channel, based on a response to at least one control signal among a plurality of control signals transmitted to the external electronic device through the initially activated channel, not being received from the external electronic device. A message included in the another control signal may include a reboot command, and the external electronic device may be configured to drive the operating system again based on the reboot command included in the message included in the another control signal.

In various example embodiments, the processor may be configured to control the electronic device to generate another control signal to be transmitted 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 may be configured to shut down the operating system based on a shut down command corresponding to the another event and included in a message of the another control signal.

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

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

According to various example embodiments as described above, method of operating an electronic device (for example, the electronic device401) may include: identifying a control signal received through a channel that is initially activated after an external electronic device is connected to a connector among a plurality of channels; and controlling based on a message included in the identified control signal.

In various example embodiments, the method may further include: based on the electronic device being identified by the external electronic device through the connector, receiving a power supplied by the external electronic device through the connector; and, based on the power supplied by the external electronic device being received, driving an operating system in a power off state.

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

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

In various example embodiments, the message included in the identified control signal may include a battery status transfer 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 transfer command included in the message; and controlling the connector to transmit the data including the battery health information to the external electronic device through the initially activated channel.

As described above, the electronic device401according to various example embodiments receives a control signal from the external electronic device even before an enumeration operation is completed, such that the electronic device410can operate more rapidly. In addition, as described above, the electronic device401according to various example embodiments receives a control signal from the external electronic device through an initially activated channel, and thus reboots the operating system through the control signal even when at least one of the operating system, an application or a combination thereof is in a disabled state, such that reliable operations can be guaranteed.

The electronic device and the method thereof according to various example embodiments can receive a control signal from the external electronic device even before an enumeration operation is completed.

The effects achieved by the disclosure are not limited to those mentioned above, and other effects that are not mentioned above may be clearly understood to those skilled in the art based on the description provided above.

Methods according to embodiments stated in claims and/or descriptions of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

In addition, the programs may be stored in an attachable storage device which is accessible through communication networks such as the Internet, Intranet, local area network (LAN), wide area network (WAN), and storage area network (SAN), or a combination thereof. Such a storage device may access the electronic device via an external port. Further, a separate storage device on the communication network may access a portable electronic device.

In the above-described example embodiments of the present disclosure, a component included in the present disclosure is expressed in the singular or the plural according to a presented example embodiment. However, the singular form or plural form is selected for convenience of description suitable for the presented situation, and various embodiments of the present disclosure are not limited to a single element or multiple elements thereof. Further, either multiple elements expressed in the description may be configured into a single element or a single element in the description may be configured into multiple elements.