KR20130046090A - Wakeup state synchronization method between docking system using the same - Google Patents

Wakeup state synchronization method between docking system using the same Download PDF

Info

Publication number
KR20130046090A
KR20130046090A KR1020110110447A KR20110110447A KR20130046090A KR 20130046090 A KR20130046090 A KR 20130046090A KR 1020110110447 A KR1020110110447 A KR 1020110110447A KR 20110110447 A KR20110110447 A KR 20110110447A KR 20130046090 A KR20130046090 A KR 20130046090A
Authority
KR
South Korea
Prior art keywords
terminal
event
wakeup event
wakeup
smart
Prior art date
Application number
KR1020110110447A
Other languages
Korean (ko)
Inventor
안병남
김승일
조영묵
Original Assignee
한동엘앤씨(주)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 한동엘앤씨(주) filed Critical 한동엘앤씨(주)
Priority to KR1020110110447A priority Critical patent/KR20130046090A/en
Publication of KR20130046090A publication Critical patent/KR20130046090A/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/10—Program control for peripheral devices
    • G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/382—Information transfer, e.g. on bus using universal interface adapter
    • G06F13/385—Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)

Abstract

Disclosed are a state synchronization method between a docked terminal and a docking system using the same. The method for synchronizing the terminal state may include: entering a SLEEP mode by operating a first terminal as a USB host, entering a sleep mode by operating a second USB client, and when a WAKEUP event occurs by the first terminal, A first terminal provides a WAKEUP event to a second terminal through a USB interface, a first terminal waits for reconnection by providing a signal through an HDMI interface, and a second terminal receives the WAKEUP event provided from the first terminal. And attempting to reconnect with the first terminal on the basis. Accordingly, even when some of the docked terminals are WAKEUP, the WAKEUP event can be transmitted to other terminals, so that both terminals can operate independently. In addition, the inconvenience that the user has to separately WAKEUP the other terminal for the interlocked operation is eliminated.

Description

Wakeup state synchronization method between docked terminals and docking system using the same

The present invention relates to a wake-up state synchronization method between a docked terminal and a docking system using the same. More specifically, when a WAKEUP event occurs in one of the docked terminals, a wake-up for transmitting a WAKEUP event to another terminal. A method for synchronizing up state and a docking system using the same.

In recent years, due to the rapid development of communication technology and the popularization of smart phones, many users have smart phones, and they are no longer just for the purpose of calling, but also for entertainment, document creation, securities, multimedia playback, and social relations. It is possessed and used for various purposes.

However, smartphones have only limited interface devices and, unlike desktop computers, do not have interface devices such as mass storage devices, backup drives, and local printers. In addition, since the smartphone is manufactured in consideration of portability, the size of the display is limited, and the size of the buttons or items on the screen for data input is also small, which makes it difficult to operate quickly and easily.

Therefore, most users perform tasks or tasks through separate devices such as desktops, laptops, and laptops at work or at home, and use smartphones in an environment where such separate devices cannot be used.

However, in order to use an application or environment used in a smartphone again on a separate device, it is cumbersome to transfer the data stored in the smartphone to a separate device or reset the environment on a separate device.

 For the convenience of a user using a smartphone with such a limited interface device, a docking station is used to provide additional input / output interface devices. The docking station allows users to use expansion slots, external storage devices, large-screen displays, keyboards, mice, local printers, etc., so that they can work or work efficiently, while retaining the applications and environments used in smartphones. It can be used and the task and work continuity can be given.

However, in order to consider the convenience of a user using the docked terminals in conjunction, the docking terminals must be maintained in association with each other, it is necessary to prevent one terminal and the other terminal from operating each. One of the cases where such independent operation may occur is when a WAKEUP event occurs in one of the situations where both the smartphone and the separate device enter the SLEEP mode.

When a WAKEUP event occurs in one side, when only one terminal is WAKEUP and the other terminal maintains SLEEP mode, there is inconvenience that the user has to make each WAKEUP, and some of the docked terminals are rear or rear of the other terminal. That discomfort is doubled if it is located in.

Therefore, even when a WAKEUP event occurs for only one of the terminals, a search for a scheme for allowing the two terminals to be interlocked with each other is performed.

The present invention has been made to solve the above problems, an object of the present invention, when a WAKEUP event occurs in any one of the docked terminal, transmits the WAKEUP event to the other terminal to synchronize the state of both terminals To provide a way to do so.

When the first terminal is docked to the second terminal through a plurality of interfaces according to an embodiment of the present invention for achieving the above object, a method for synchronizing the state of the second terminal to the state of the first terminal The first terminal operating as a USB host to enter a SLEEP mode, and the second terminal operating as a USB client to enter a SLEEP mode; Providing, by the first terminal, a WAKEUP event to the second terminal through a USB interface when the WAKEUP event occurs by the first terminal; Waiting for reconnection by the first terminal providing a signal through an HDMI interface; And the second terminal attempting to reconnect with the first terminal based on the WAKEUP event received from the first terminal.

In the providing of the WAKEUP event, when the WAKEUP event is generated by the first terminal, the first terminal may provide a WAKEUP event to the second terminal by turning on a signal transmitted to the USB VBUS line.

In addition, the reconnection waiting step, the first terminal transmits a TMDS signal to the TMDS data line and waits for reconnection, the reconnection attempt step, the information indicating that the TMDS signal has been received to the TMDS data line; Transmitting an event occurring when the first terminal and the second terminal are connected to an event controller managing the event; And attempting to reconnect with the first terminal by the event controller.

Meanwhile, when the first terminal is docked to the second terminal through a plurality of interfaces according to another embodiment of the present invention for achieving the above object, synchronizing the state of the second terminal to the state of the first terminal The method includes the steps of the first terminal operating as a USB host to enter a SLEEP mode, and the second terminal operating as a USB client to enter a SLEEP mode; Providing, by the second terminal, a WAKEUP event to the first terminal through an HDMI interface when the WAKEUP event occurs by the second terminal; The first terminal turning on a USB VBUS signal based on a WAKEUP event received from the second terminal, and providing data to the second terminal through the HDMI interface to wait for reconnection; And the second terminal attempting to reconnect with the first terminal based on the data provided from the first terminal.

In the providing of the WAKEUP event, when the WAKEUP event is generated by the second terminal, the second terminal may provide a WAKEUP event to the first terminal through a RESERVED PIN of the HDMI interface.

In addition, the reconnection waiting step, the first terminal transmits a TMDS signal to the TMDS data line and waits for reconnection, the reconnection attempt step, the information indicating that the TMDS signal has been received to the TMDS data line; Transmitting an event occurring when the first terminal and the second terminal are connected to an event controller managing the event; And attempting to reconnect with the first terminal by the event controller.

On the other hand, when the first terminal is docked to the second terminal through a plurality of interfaces according to an embodiment of the present invention for achieving the object, for synchronizing the state of the second terminal to the state of the first terminal The docking system operates as a USB host, enters the SLEEP mode, provides a WAKEUP event to a second terminal through a USB interface when a WAKEUP event occurs by itself, and provides a TMDS signal to the second terminal through an HDMI interface. Waits for reconnection, and when a WAKEUP event occurs by the second terminal, turns on a USB VBUS signal based on a signal received from the second terminal through a RESERVED PIN of the HDMI interface, and then A first terminal waiting for reconnection by providing the TMDS signal to a second terminal; And enters the SLEEP mode by operating as a USB client and attempts to reconnect based on the TMDS signal received from the first terminal through the HDMI interface when a WAKEUP event occurs by the first terminal. When a WAKEUP event occurs, the second terminal provides a WAKEUP event to the first terminal through the RESERVED PIN of the HDMI interface, and attempts to reconnect based on the TMDS signal received from the first terminal through the HDMI interface. It includes;

Accordingly, even when some of the docked terminals are WAKEUP, the WAKEUP event can be transmitted to other terminals, so that both terminals can operate independently. In addition, the inconvenience that the user has to separately WAKEUP the other terminal for the interlocked operation is eliminated.

1 and 2 show a docking system to which the present invention is applicable;
3 shows a block diagram of a docking system,
4 is a view showing some of the architecture layers under the Android platform as one of the applications that can be used in smart phones and smart pads,
5 is a flowchart used to describe a method of transmitting a wake-up event to a smart pad by generating a wake-up event in the smart phone, and
6 is a flowchart used to describe a method of transmitting a wake-up event to a smart phone by generating a wake-up event in the smart pad.

Hereinafter, the present invention will be described in detail with reference to the drawings.

1 and 2 show a docking system to which the present invention is applicable.

First, FIG. 1 is a view illustrating a docking system for an interlocking operation between a smart phone 100 and a smart pad 200. The smart phone 100 and the smart pad 200 may be operated by separate operating systems, and may drive separate application programs, respectively, and have separate devices. Of course, these operating systems and applications may be the same, similar, or separate from each other, and the devices provided may also be identical, similar, or separate from each other.

For example, if the smartphone 100 is operated by the Android operating system and can drive the application program of A, B, C, the smart pad 200 is operated by the Android operating system, but the application program of B, C, D Can be driven. In addition, when the smart phone 100 is provided with a communication module for a call, a camera module for taking a picture, the smart pad 20 may have the same but a high specification camera module for the call. .

Since the smart phone 100 and the smart pad 200 are each equipped with a separate operating system and operate by each operating system, the smartphone 100 and the smart pad 200 operate through their respective operating systems when not docked with each other as shown in the left side of FIG. 1. Done.

However, in the smart phone 100 and the smart pad 200 according to the present invention, as shown in the center of FIG. 1, the smart phone 100 may be docked at a docking station located at the rear of the smart pad 200. . Of course, since the docking station is located at the rear of the smart pad 200 and the smart phone 100 is docked, when the smart phone 100 and the smart pad 200 are used in a docked state, the smart phone 100 is used from the smart phone 100. In order to prevent the input by the wrong operation of the smart phone 100 will be docked as shown in the center shown in Figure 1 so that the front portion of the smart phone 100 is not exposed.

On the right side of FIG. 1, the smartphone 100 and the smart pad 200 are docked to display a screen operated by an operating system mounted on the smartphone 100 or a screen on which an application program installed in the smartphone 100 operates. have.

As such, when the smartphone 100 and the smart pad 200 are docked and used in conjunction with each other, the user's point of view can be a continuity of work or work that has been progressed through the smartphone 100. In addition, it is possible to use devices such as a wide display or a high output speaker, which is an advantage of the smart pad 200, thereby facilitating work or work convenience.

Next, Figure 2 is a view showing a docking system for the interlocking operation between the smartphone 100 and the laptop 300. 1, the docking system of FIG. 2 is not docked so that the smartphone 100 is completely inserted into the docking station of the laptop 300, and only a part of the docking part is inserted into the docking system of the laptop 300. ) May serve as a number pad of the laptop 300.

Thus, unlike FIG. 1, the smartphone 100 is docked to the laptop 300 so that the display of the smartphone 100 is exposed.

Even by this, when docking and using the smart phone 100 and the laptop 300, the user can achieve the continuity of the work or work that was in progress through the smart phone (100). In addition, the advantages of the laptop 300 can be used as it is.

Meanwhile, in FIG. 2, it is assumed that the smart phone 100 is used as a numeric pad of the laptop 300 for convenience of description, but this is merely an example for convenience of description and is not a numeric pad but a general touch pad. Even when used, the technical idea of the present invention may be applied as it is.

In addition, in FIGS. 1 and 2, for convenience of description, the smart phone 100 and the smart pad 200 or the laptop 300 have been described as docked with each other, but this is merely an example for convenience of description. The terminal is docked with each other, such as the smart pad 200 and the laptop 300 docked, or the smart phone 100 and the desktop (not shown) docked with each other and the matters that are executed on one of the terminals are different. In the case of borrowing a device, it will be within the scope of the present invention.

In addition, the docking position or the docking method of the above-described smart phone 100 is also merely exemplary, and the present invention may be applied even when docked by methods not shown in a position not shown.

3 is a block diagram of the aforementioned docking system. Hereinafter, for convenience of description, it will be assumed that the smart phone 100 and the smart pad 200 are interoperated with each other.

The smart phone 100 includes a phone input / output unit 110, a phone control unit 120, a phone communication unit 130, and a phone storage unit 140.

The phone input / output unit 110 is used for receiving a signal input from a user or an external server or a terminal such as a touch screen, a button, a speaker, etc., and displaying the received signal on a screen or outputting a voice.

The phone controller 120 controls the phone input / output unit 110, the phone communication unit 130, and the phone storage unit 140 so that the smart phone 100 can operate inherently. In particular, the phone controller 120 controls the phone input / output unit 110 so that a signal or a user input received by the phone input / output unit 110 is processed, and the processed result is displayed or output through the phone input / output unit 110. Be sure to In addition, the phone controller 120 controls the phone communication unit 130 to enable information exchange, data transmission and reception between the smart phone 100 and the smart pad 200. In addition, the phone controller 120 controls the phone storage unit 140 to store data received by the phone input / output unit 110, data transmitted and received through the phone communication unit 140, or the phone storage unit 140. The data stored in the) is displayed through the phone input / output unit 110 or transmitted to the smart pad 200.

In addition, the phone controller 120 controls the smart phone 100 to be executed according to the operating system stored in the phone storage 140 or the smart phone 100 to be executed according to the application program stored in the phone storage 140. .

In addition, when the smart phone 100 is docked to the smart pad 200, the phone controller 120 operates each device of the smart pad 200 according to an operating system and an application program executed by the smart phone 100. Control each device.

For example, when the smart phone 100 is docked to the smart pad 200, the phone controller 120 controls the phone input / output unit 110 to deactivate the phone input / output unit 110, and the phone communication unit 140. Input / output data is transferred to the smart pad 200 through the () to allow the input and output from the smart pad 200.

The phone communication unit 130 operates as a means for communicating with the smart pad 200 or an external terminal under the control of the phone control unit 120. In particular, the phone communication unit 130 includes an HDMI interface 131 and a USB interface 135 to transmit and receive data and signals by communicating with the smart pad 200. A detailed process of transmitting a SLEEP event between the smartphone 100 and the smart pad 200 using the HDMI interface 131 and the USB interface 135 and entering the WAKEUP mode will be described later.

The phone storage unit 150 stores an operating system and application programs for driving the smart phone 100.

As such, the smartphone 100 may display a screen or voice generated by the smartphone 100 on the smart pad 200 through the HDMI interface 131 and the USB interface 135 provided in the phone communication unit 130. Will cause the output.

The smart pad 200 includes a pad input / output unit 210, a pad controller 220, a pad communication unit 230, and a pad storage unit 240.

Hereinafter, the operation in the case where the smart phone 100 is docked to the smart pad 200 will be described mainly.

The pad controller 220 controls the pad communicator 230 to enable information exchange, data transmission, and the like, between the smart phone 100 and the smart pad 200. In addition, the pad controller 220 controls the phone storage unit 240 to store data received from the smart phone 100 through the pad communication unit 240 or data stored in the pad storage unit 240. To be delivered to the smartphone (100).

When the smartphone 100 is docked to the smart pad 200, the pad controller 220 may operate each device of the smart pad 200 according to an operating system and an application program executed by the smartphone 100. Control them.

Meanwhile, when the smart pad 200 is not linked with the smart phone 100, the smart pad 200 is operated by an independent operating system, and when the smart pad 200 is linked with the smart phone 100, matters that are operated by the operating system of the smart phone 100. Receives data about the smartphone from the smartphone 100 through the pad communication unit 230 to provide to the user.

FIG. 4 is a view showing some of the architecture layers under the Android platform as one of application systems that can be used in the smart phone 100 and the smart pad 200. The Android operating system is stored in the phone storage 140 of the smart phone 100 and the pad storage 240 of the smart pad 200 so that the smart phone 100 and the smart pad 200 are operated by the stored Android operating system. do.

The Android platform means a software package including a Linux kernel, a hardware abstraction layer (HAL), a library, an application framework, and an application. Hereinafter, the application framework area and the Linux kernel area, which are necessary parts for understanding the present invention, will be described. Shall be.

The lower layer of the application area, which is the top layer, is the application framework area. There are several controllers in the application framework area that run as daemons and manage the operating system. In particular, there is an event machine 410 or an event controller 420 in this application framework area.

The event machine 410 operating in the application framework area of the smart phone 100 manages the WRAPPER device driver 430 which will be described later, and the smart phone 100 when the smart phone 100 and the smart pad 200 are connected. Manages the actions that occur in.

In addition, the event controller 420 operating in the application framework area of the smart pad 200 manages operations occurring in the smart pad 200 when the smart phone 100 and the smart pad 200 are connected. To perform.

The lowest layer is the Linux kernel area. The Linux kernel area includes drivers such as display drivers, camera drivers, and audio drivers. The Linux kernel area serves as an abstraction layer between hardware and the rest of the Android platform stack.

On the other hand, in the Linux kernel area of the smartphone 100, the driver for the device that the PHONE ONLY DEVICE DRIVER (441) and the device that the smartphone 100 and the smart pad 200 at the same time has a driver for the device that only the smartphone (100) SAME DEVICE DRIVER 445 is present. The PHONE ONLY DEVICE DRIVER 441 and the SAME DEVICE DRIVER 445 are collectively referred to as PHONE DEVICE DRIVER 440.

In addition, when the smartphone 100 already knows the device list of the smart pad 200, the smartphone 100 generates a virtual pad device driver 450 for such a device, and the WRAPPER device driver 430 is a SAME DEVICE DRIVER 445. ) And VIRTUAL PAD DEVICE DRIVER 450 to manage the interlocking operation of the smartphone 100 at the same time.

On the other hand, data transmission and reception between the smart phone 100 and the smart pad 200 is made through the PHONE DATA TX / RX (460) and PAD DATA TX / RX (470), PHONE DATA TX / RX (460) and PAD DATA TX / RX 470 is the same concept as the above-described phone communication unit 130 and the pad communication unit 230, respectively.

In the above, it is assumed that the event machine 410 and the event controller 420 reside in the application framework area, but this is merely an example for convenience of description. Accordingly, the technical concept of the present invention may be applied to the event machine 410 and the event controller 420 even if the event machine 410 and the event controller 420 are present in another area of the kernel area rather than the application framework area. In addition, it may be assumed that the event machine 410 and the event controller 420 exist in the kernel region.

Hereinafter, a process in which the smart phone 100 and the smart pad 200 are converted together from the sleep mode to the wake up mode will be described with reference to FIGS. 5 and 6.

5 is a flowchart used to describe a method of transmitting a wake-up event to the smart pad 200 by generating a wake-up event in the smart phone 100.

First, in order to transmit a wake-up event, the smart phone 100 and the smart pad 200 need to maintain a sleep mode (S505 and S510). In particular, the smartphone 100 maintains a sleep mode as a USB host, and the smart pad 200 maintains a sleep mode as a USB client. This is because, as will be described later, the smartphone 100 must be a USB host to transmit the USB VBUS signal to the smart pad 200.

When the wake-up event occurs in the smart phone 100 (S515), the smart phone 100 enters the ACTIVE state (S520). In the ACTIVE state, the smartphone 100 determines which path a wake-up event has occurred. When a wake-up event occurs by the smart phone 100 itself, such as a call or an alarm (S525-Y), since the smart phone 100 is in the USB host state, the VBUS is turned on (S535) and the smart pad. In step S540, the VBUS signal is transmitted.

On the other hand, if the wake-up event is generated by the smart pad 200, not the smart phone 100 (S525-N), the wake-up event is generated by the smart pad 200 to take a procedure (S530) which will be described later This will be described with reference to FIG. 6.

Upon receiving the VBUS signal, the smart pad 200 recognizes that a wake-up event has occurred based on the VBUS signal (S545), thereby entering the ACTIVE state (S550).

Like the smart phone 100, the smart pad 200 determines which path a wake-up event has occurred. When a wake-up event occurs by the smart pad 200 itself, such as a call or an alarm ringing (S560-Y), a procedure in which the wake-up event occurs by the smart pad 200 is performed (S560). This will be described with reference to FIG. 6 to be described later.

Meanwhile, the smartphone 100 turns on the TMDS (S565) and transmits a TMDS signal to the smart pad 200 through the TMDS data line (S570) and waits for reconnection with the smart pad 200 (S575). The pad 200 transmits the received TMDS signal to the event controller 420 (S580) and attempts to reconnect with the smart phone 100 (S585).

As a result, when the WAKEUP event occurs in the smart phone 100, only the smart phone 100 is WAKEUP and the smart pad 200 can exclude a situation in which the SLEEP mode is maintained, without having to wake up each of the smart phones. The interlocked operation may be performed in which the 100 and the smart pad 200 are WAKEUP together.

FIG. 6 is a flowchart used to describe a method of transmitting a wake-up event to the smart phone 100 after a wake-up event occurs in the smart pad 200.

First, in order to transmit a wake-up event, the smart phone 100 and the smart pad 200 need to maintain a sleep mode (S605 and S610). In particular, the smartphone 100 maintains a sleep mode as a USB host, and the smart pad 200 maintains a sleep mode as a USB client.

When the wakeup event occurs in the smart pad 200 (S615), the smart pad 200 enters the ACTIVE state (S620). In the ACTIVE state, the smart pad 200 determines which path a wake-up event occurs.

If the wake-up event is generated by the smart phone 100 instead of the smart pad 200 (S625-N), the wake-up event is generated by the smart phone 100 (S630). See 5.

On the other hand, when the wakeup event occurs by the smart pad 200 itself (S625-Y), the event controller 420 wakes up the HDMI interface (S635) to control the RESERVED PIN (S640). That is, the smart pad 200 transmits a wake-up signal to the smart phone 100 through the RESERVED PIN of the WAKEUP HDMI interface (S645).

The smart phone 100 receives the wakeup signal through the RESERVED PIN and finds that a wakeup event has occurred (S650), thereby entering the ACTIVE state (S655).

Like the smart pad 200, the smart phone 100 determines which path a wake-up event has occurred (S660). When a wake-up event occurs by the smart phone 100 itself, such as a call or an alarm ringing (S660-Y), the wake-up event is generated by the smart phone 100 (S665). This may be referred to the aforementioned FIG. 5.

On the other hand, when a wake-up event occurs by the smart pad 200 (S660-N), the smart phone 100 turns on the VBUS and TMDS (S670) to transfer the TMDS signal to the smart pad 200 through the TMDS data line. After transmitting (S680) and waiting for reconnection with the smart pad 100 (S575), the smart pad 200 checks the received TMDS signal (S685) and delivers it to the event controller 420 (S690) and the smart phone ( Attempt to reconnect with 100) (S695).

As a result, when the WAKEUP event occurs in the smart pad 200, only the smart pad 200 is WAKEUP and it is possible to exclude the situation in which the smart phone 100 maintains the sleep mode, without having to wake up each of the smart phones. The interlocked operation may be performed in which the 100 and the smart pad 200 are WAKEUP together.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is clearly understood that the same is by way of illustration and example only and is not to be construed as limiting the scope of the invention as defined by the appended claims. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

100: smartphone 200: smart pad
110: phone input unit 210: pad input unit
120: phone control unit 220: pad control unit
130: phone communication unit 230: pad communication unit
140: phone storage unit 240: pad storage unit
410: event machine 420: event controller
430: WRAPPER device driver 440: phone device driver
441: PHONE ONLY DEVICE DRIVER 445: SAME DEVICE DRIVER
450: Virtual pad device driver 460: PHONE DATA TX / RX
470: PAD DATA TX / RX 480: PAD DEVICE DRIVER

Claims (7)

A method for synchronizing the state of the second terminal to the state of the first terminal when the first terminal is docked to the second terminal through a plurality of interfaces,
Entering the SLEEP mode by operating the first terminal as a USB host and entering the SLEEP mode by operating the second terminal as a USB client;
Providing, by the first terminal, a WAKEUP event to the second terminal through a USB interface when the WAKEUP event occurs by the first terminal;
Waiting for reconnection by the first terminal providing a signal through an HDMI interface; And
And attempting to reconnect with the first terminal based on the WAKEUP event received from the first terminal by the second terminal. The method of claim 1,
The WAKEUP event providing step,
And generating a WAKEUP event to the second terminal by turning on a signal transmitted through a USB VBUS line when the WAKEUP event is generated by the first terminal. The method of claim 1,
The reconnection waiting step,
The first terminal transmits a TMDS signal to a TMDS data line and waits for reconnection;
The reconnection attempt step,
Transmitting information indicating that the TMDS signal has been received to the TMDS data line to an event controller managing an event occurring when the first terminal is connected to the second terminal; And
And attempting to reconnect with a first terminal by the event controller. A method for synchronizing the state of the second terminal to the state of the first terminal when the first terminal is docked to the second terminal through a plurality of interfaces,
Entering the SLEEP mode by operating the first terminal as a USB host and entering the SLEEP mode by operating the second terminal as a USB client;
Providing, by the second terminal, a WAKEUP event to the first terminal through an HDMI interface when the WAKEUP event occurs by the second terminal;
The first terminal turning on a USB VBUS signal based on a WAKEUP event received from the second terminal, and providing data to the second terminal through the HDMI interface to wait for reconnection; And
And attempting to reconnect with the first terminal based on the data received from the first terminal by the second terminal. The method of claim 1,
The WAKEUP event providing step,
And when the WAKEUP event occurs by the second terminal, the second terminal provides a WAKEUP event to the first terminal through a RESERVED PIN of the HDMI interface. The method of claim 1,
The reconnection waiting step,
The first terminal transmits a TMDS signal to a TMDS data line and waits for reconnection;
The reconnection attempt step,
Transmitting information indicating that the TMDS signal has been received to the TMDS data line to an event controller managing an event occurring when the first terminal is connected to the second terminal; And
And attempting to reconnect with a first terminal by the event controller. In a docking system for synchronizing the state of the second terminal to the state of the first terminal when the first terminal is docked to the second terminal through a plurality of interfaces,
It enters SLEEP mode by operating as a USB host, and when a WAKEUP event occurs by itself, provides a WAKEUP event to a second terminal through a USB interface, and reconnects by providing a TMDS signal to the second terminal through an HDMI interface. Waiting,
When the WAKEUP event occurs by the second terminal, the USB VBUS signal is turned on based on the signal received from the second terminal through the RESERVED PIN of the HDMI interface, and then the TMDS signal is transmitted to the second terminal through the HDMI interface. Providing a first terminal waiting for reconnection; And
Enters the SLEEP mode by operating as a USB client, when a WAKEUP event occurs by the first terminal, attempts to reconnect based on the TMDS signal received from the first terminal through the HDMI interface,
If a WAKEUP event occurs by the user, providing a WAKEUP event to the first terminal through the RESERVED PIN of the HDMI interface, and attempting to reconnect based on the TMDS signal received from the first terminal through the HDMI interface. Docking system comprising; a second terminal.
KR1020110110447A 2011-10-27 2011-10-27 Wakeup state synchronization method between docking system using the same KR20130046090A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020110110447A KR20130046090A (en) 2011-10-27 2011-10-27 Wakeup state synchronization method between docking system using the same

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020110110447A KR20130046090A (en) 2011-10-27 2011-10-27 Wakeup state synchronization method between docking system using the same

Publications (1)

Publication Number Publication Date
KR20130046090A true KR20130046090A (en) 2013-05-07

Family

ID=48657876

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020110110447A KR20130046090A (en) 2011-10-27 2011-10-27 Wakeup state synchronization method between docking system using the same

Country Status (1)

Country Link
KR (1) KR20130046090A (en)

Similar Documents

Publication Publication Date Title
US9843618B2 (en) Method and apparatus for displaying user interface through sub device that is connectable with portable electronic device
US8949494B2 (en) User equipment connectable to an external device
US9083778B2 (en) Adapter for connecting two mobile devices
US20130103861A1 (en) Wake up state synchronization method between docked terminals and docking system using the same
US20130009864A1 (en) Method and apparatus for interfacing between external device and mobile device
US9201814B2 (en) Electronic devices and methods for sharing peripheral devices in dual operating systems
US20130050122A1 (en) Controlling user equipment as touch pad for external device connected thereto
EP3869346B1 (en) Apparatus and method of recognizing external device in a communication system
EP3623932B1 (en) Display method and device
US9542338B2 (en) Controlling applications according to connection state and execution condition
US8959267B2 (en) Controlling an external device connected to user equipment
KR20130053935A (en) Contents transferring method and device, server using the method
US11169763B2 (en) Mobile terminal and electronic device comprising the same
US11989405B2 (en) Screen locking method and apparatus
WO2020207031A1 (en) Method and apparatus for dynamically configuring screen transmission timeout period, and wireless screen transmission device and receiving end
US20130104149A1 (en) Selective data processing method between docked terminals and selective data processing system using the same
EP3951589A1 (en) View display method and electronic device
US20130326092A1 (en) Processing input event of external device
US20140043267A1 (en) Operation Method of Dual Operating Systems, Touch Sensitive Electronic Device Having Dual Operating Systems, and Computer Readable Storage Medium Having Dual Operating Systems
US20160191337A1 (en) Visualized device interactivity management
WO2015070718A1 (en) Communication number notification method and communication device
KR20130046090A (en) Wakeup state synchronization method between docking system using the same
KR101522401B1 (en) Mobile Terminal for connection with external device, and method for changing screen image thereof
US20130104174A1 (en) Video transmitting and receiving method between docked terminals and docking system using the same
KR20130046089A (en) Sleep state synchronization method between docking terminals and docking system using the same

Legal Events

Date Code Title Description
WITN Withdrawal due to no request for examination