KR20150100181A - Method of Data Backup between Wearable Device and Electrical Device - Google Patents

Abstract

A data backup method according to various embodiments of the present invention is performed in a wearable device and includes the steps of registering use of a backup function for a specific application with a backup agent, Receiving a request, the backup agent generating backup data for each of the applications, and the backup agent transmitting the backup data to the electronic device, and in another embodiment Do.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a method of data backup between a wearable device and an electronic device,

Various embodiments of the present invention are directed to data storage between a wearable device and an electronic device.

A wearable device can be commonly used in conjunction with an electronic device such as a smart phone. A wearable device can store data in an electronic device.

A wearable device (such as SmartWatch) can be used in conjunction with an electronic device. A wearable device may lose data associated with an application running on the wearable device if the user performs a reset on the device or a replacement with another wearable device.

Various embodiments of the present invention provide a data backup method capable of storing data related to an application running in a wearable device in an electronic device interlocked with a backup agent, and a wearable device supporting the data backup method.

In addition, various embodiments of the present invention provide a data backup method capable of receiving backup data from an electronic device interlocked with a wearable device, and a wearable device supporting the data backup method.

A data backup method according to various embodiments is performed in a wearable device, and an operation of registering use of a backup function for a specific application with a backup agent, the backup agent receiving a backup request from the electronic device The backup agent may generate backup data for each of the applications and the backup agent may transmit the backup data to the electronic device.

As described above, according to various embodiments of the present invention, a content such as a screen display of an electronic device is outputted through a sense of space, so that a user such as a visually impaired person can understand screen display contents in a cubic way.

The various embodiments of the present invention can safely protect data even when a wearable device is reset or replaced by storing data related to an application running in the wearable device in an electronic device interlocked via a backup agent.

In addition, the various embodiments of the present invention can receive the backup data from the electronic device interlocked with the wearable device and restore the existing data to the new device or the reset device even if the wearable device is reset or replaced.

Figure 1 illustrates a network environment including a wearable device according to various embodiments.
Figure 2 shows a block diagram of a wearable device according to various embodiments.
3 is a block diagram of a wearable device and an electronic device according to various embodiments.
4 is a flowchart for explaining a data backup method in a wearable device according to various embodiments.
5 is a flowchart for explaining a data backup method in an electronic device according to various embodiments.
6 is a signal flow diagram for illustrating a data backup method according to various embodiments.
7 is a signal flow diagram illustrating a process of restoring backup data according to various embodiments.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It is to be understood, however, that the invention is not to be limited to the specific embodiments, but includes all changes and / or equivalents and alternatives falling within the spirit and scope of the invention. In connection with the description of the drawings, like reference numerals have been used for like elements.

The word " comprises " or " comprising may " used in the present specification refers to the existence of the corresponding function, operation, or element, etc., and does not limit the one or more additional functions, operations or components. It is also to be understood that the terms " comprises " or " having ", and the like in the specification are intended to specify the presence of stated features, integers, But do not preclude the presence or addition of features, numbers, steps, operations, components, parts, or combinations thereof.

The " or " in the present invention includes any and all combinations of words listed together. For example, " A or B " may include A, B, or both A and B.

In the present invention, expressions such as " first ", " second " and the like can modify various elements of the present invention, but do not limit the constituent elements. For example, the representations do not limit the order and / or importance of the components.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the meaning in the context of the relevant art and are to be interpreted as ideal or overly formal in the sense of the present invention Do not.

1 illustrates a network environment 100 including a wearable device 101 according to various embodiments.

Referring to FIG. 1, the wearable device 101 may include a bus 110, a processor 120, a memory 130, an input / output interface 140, a display 150, a communication interface 160, and an application control module 170.

The bus 110 may be a circuit that interconnects the components described above and communicates (e.g., control messages) between the components described above.

The processor 120 may be operatively coupled to other components (e.g., the memory 130, the input / output interface 140, the display 150, the communication interface 160, or the application control module 170) via the bus 110 Receives a command, decrypts the received command, and can execute an operation or data processing according to the decrypted command.

The memory 130 may be coupled to the processor 120 or other components such as the processor 120 or other components (e.g., the input / output interface 140, the display 150, the communication interface 160, or the application control module 170) Lt; RTI ID = 0.0 > and / or < / RTI > The memory 130 may include, for example, a kernel 131, a middleware 132, an application programming interface (API) 133, or an application 134. Each of the above-described programming modules may be composed of software, firmware, hardware, or a combination of at least two of them.

The kernel 131 may include system resources (e.g., the bus 110, the processor 120, etc.) used to execute the operations or functions implemented in the other programming modules, e.g., the middleware 132, the API 133, Or the memory 130 and the like). In addition, the kernel 131 may provide an interface for accessing and controlling or managing the individual components of the electronic device 102 in the middleware 132, the API 133, or the application 134.

The middleware 132 can act as an intermediary for the API 133 or the application 134 to communicate with the kernel 131 to exchange data. In addition, the middleware 132 may be configured to communicate system resources (e.g., the bus 110, the processor 120, or the like) of the electronic device 102 to at least one of the applications 134, (E.g., scheduling or load balancing) of a work request using a method of assigning a priority that can be used to the job (e.g., the memory 130).

The API 133 is an interface for the application 134 to control the functions provided by the kernel 131 or the middleware 132. For example, the API 133 may include at least one interface or function for file control, window control, image processing, (E.g., commands).

According to various embodiments, the application 134 may be an SMS / MMS application, an email application, a calendar application, an alarm application, a health care application (e.g., an application that measures momentum or blood glucose) Pressure, humidity, or temperature information, etc.), and the like. Additionally or alternatively, the application 134 may be an application related to the exchange of information between the wearable device 101 and an external electronic device (e.g., electronic device 102). The application associated with the information exchange may include, for example, a notification relay application for communicating specific information to the external electronic device, or a device management application for managing the external electronic device .

For example, the notification delivery application may transmit notification information generated in another application (e.g., an SMS / MMS application, an email application, a healthcare application, or an environment information application) of the wearable device 101 to an external electronic device ). ≪ / RTI > Additionally or alternatively, the notification delivery application may receive notification information from, for example, an external electronic device (e.g., electronic device 102) and provide it to the user. The device management application can be used to provide a function (e.g., a function of turning on / off the external electronic device itself (or some components)) to at least a portion of an external electronic device (e.g., electronic device 102) communicating with the wearable device 101, (E.g., adjusting, turning off, or adjusting the brightness (or resolution) of the display), managing an application running on the external electronic device or services (e.g., call service or message service) )can do.

According to various embodiments, the application 134 may include an application specified according to attributes (e.g., the type of electronic device) of the external electronic device (e.g., electronic device 102). For example, if the external electronic device is an MP3 player, the application 134 may include an application related to music playback. Similarly, if the external electronic device is a mobile medical device, the application 134 may include applications related to health care. According to one embodiment, the application 134 may include at least one of an application specified in the wearable device 101 or an application received from an external electronic device (e.g., the electronic device 102).

The input / output interface 140 connects commands or data input from a user via an input / output device (e.g., a sensor, keyboard, or touch screen) to the processor 120, the memory 130, the communication interface 160 , Or to the application control module 170. For example, the input / output interface 140 may provide the processor 120 with data on the user's touch input through the touch screen. The input / output interface 140 may transmit commands or data received from the processor 120, the memory 130, the communication interface 160, or the application control module 170 via the bus 110 to the input / output device Or display). For example, the input / output interface 140 can output voice data processed through the processor 120 to a user through a speaker.

The display 150 may display various information (e.g., multimedia data or text data) to the user.

The communication interface 160 can connect communication between the electronic device 102 and an external device (e.g., the electronic device 102). For example, the communication interface 160 may be connected to the network 162 via wireless communication or wired communication to communicate with the external device. The wireless communication may include, for example, wireless fidelity, Bluetooth, near field communication (NFC), global positioning system (GPS) , WiBro or GSM, etc.). The wired communication may include at least one of, for example, a universal serial bus (USB), a high definition multimedia interface (HDMI), a recommended standard 232 (RS-232) or a plain old telephone service (POTS).

According to one embodiment, the network 162 may be a telecommunications network. The communication network may include at least one of a computer network, an internet, an internet of things, or a telephone network. (E.g., a transport layer protocol, a data link layer protocol, or a physical layer protocol) for communication between the wearable device 101 and the external device is performed by the application 134, the application programming interface 133, the middleware 132, the kernel 131 Or the communication interface 160. [0035]

The application control module 170 processes at least some of the information obtained from other components (e.g., the processor 120, the memory 130, the input / output interface 140, or the communication interface 160, etc.) . For example, the application control module 170 can select an appropriate application among a plurality of applications stored in the memory 130, based on the user information received through the input / output interface 140. The selected application may provide appropriate services to the user of the wearable device 101 based on data obtained from the electronic device 102 including at least one sensor or external device via the network 162. [ In addition, the application control module 170 may select and control the appropriate applications to obtain information from, or to process and process the information obtained from the various sensors or components mounted on the wearable device 101. An exemplary configuration of a wearable device 101 including various sensors and / or modules is described with reference to FIG.

2 shows a block diagram of a wearable device 201 according to various embodiments. The wearable device 201 may constitute all or part of the wearable device 101 shown in Fig. 1, for example. 2, the wearable device 201 includes at least one application processor 210, a communication module 220, a subscriber identification module (SIM) card 224, a memory 230, a sensor module 240, an input device 250, a display 260, An interface 270, an audio module 280, a camera module 291, a power management module 295, a battery 296, an indicator 297, and a motor 298.

The AP 210 may control a plurality of hardware or software components connected to the AP 210 by operating an operating system or an application program, and may perform various data processing and operations including multimedia data. The AP 210 may be implemented as a system on chip (SoC), for example. According to one embodiment, the AP 210 may further include a graphics processing unit (GPU) (not shown).

The communication module 220 (e.g., the communication interface 160) can perform data transmission and reception in communication between the wearable device 201 (e.g., the wearable device 101) and other electronic devices (e.g., electronic device 102) have. According to one embodiment, the communication module 220 may include a cellular module 221, a Wifi module 223, a BT module 225, a GPS module 227, an NFC module 228, and a radio frequency (RF) module 229.

The cellular module 221 may provide voice calls, video calls, text services, or Internet services over a communication network (e.g., LTE, LTE-A, CDMA, WCDMA, UMTS, WiBro or GSM). In addition, the cellular module 221 can perform identification and authentication of electronic devices within the communication network using, for example, a subscriber identity module (e.g., a SIM card 224). According to one embodiment, the cellular module 221 may perform at least some of the functions that the AP 210 may provide. For example, the cellular module 221 may perform at least some of the multimedia control functions.

According to one embodiment, the cellular module 221 may include a communication processor (CP). Also, the cellular module 221 may be implemented as an SoC, for example. In FIG. 2, components such as the cellular module 221 (e.g., a communication processor), the memory 230, or the power management module 295 are illustrated as separate components from the AP 210. However, according to one embodiment, May include at least a portion of the above-described components (e.g., cellular module 221).

According to one embodiment, the AP 210 or the cellular module 221 (e.g., a communications processor) loads commands or data received from at least one of non-volatile memory or other components connected to each of them into a volatile memory for processing can do. In addition, the AP 210 or the cellular module 221 may store data generated by at least one of the other components or received from at least one of the other components in the non-volatile memory.

Each of the Wifi module 223, the BT module 225, the GPS module 227, and the NFC module 228 may include a processor for processing data transmitted and received through a corresponding module, for example. Although the cellular module 221, the Wifi module 223, the BT module 225, the GPS module 227, or the NFC module 228 are shown as separate blocks in FIG. 2, the cellular module 221, the Wifi module 223, the BT module 225, At least some (e.g., two or more) of modules 227 or NFC modules 228 may be included in one integrated chip (IC) or IC package. For example, at least some of the processors corresponding to the cellular module 221, the Wifi module 223, the BT module 225, the GPS module 227, or the NFC module 228, respectively (e.g., corresponding to the communication processor and Wifi module 223 corresponding to the cellular module 221) Wifi processor) can be implemented in a single SoC.

The RF module 229 can transmit and receive data, for example, transmit and receive RF signals. The RF module 229 may include, for example, a transceiver, a power amplifier module (PAM), a frequency filter, or a low noise amplifier (LNA). In addition, the RF module 229 may further include a component for transmitting and receiving electromagnetic waves in a free space in a wireless communication, for example, a conductor or a lead wire. 2, the cellular module 221, the Wifi module 223, the BT module 225, the GPS module 227, and the NFC module 228 share one RF module 229. However, according to one embodiment, the cellular module 221, the Wifi module 223 , The BT module 225, the GPS module 227, or the NFC module 228 can transmit and receive RF signals through separate RF modules.

The SIM card 224 may be a card including a subscriber identity module and may be inserted into a slot formed at a specific location of the electronic device. The SIM card 224 may include unique identification information (e.g., an integrated circuit card identifier (ICCID)) or subscriber information (e.g., international mobile subscriber identity (IMSI)).

The memory 230 (e.g., the memory 130) may include an internal memory 232 or an external memory 234. The built-in memory 232 may be a volatile memory such as a dynamic RAM (DRAM), a static random access memory (SRAM), a synchronous dynamic RAM (SDRAM), or a non-volatile memory , At least one of an OTPROM (one time programmable ROM), a PROM (programmable ROM), an EPROM (erasable and programmable ROM), an EEPROM (electrically erasable and programmable ROM), a mask ROM, a flash ROM, a NAND flash memory, . ≪ / RTI >

According to one embodiment, the internal memory 232 may be a solid state drive (SSD). The external memory 234 may be a flash drive such as a compact flash (CF), a secure digital (SD), a micro secure digital (SD), a mini secure digital (SD), an extreme digital And the like. The external memory 234 can be functionally connected to the wearable device 201 through various interfaces. According to one embodiment, the wearable device 201 may further include a storage device (or storage medium) such as a hard drive.

The sensor module 240 may measure a physical quantity or sense an operation state of the wearable device 201, and convert the measured or sensed information into an electrical signal. The sensor module 240 includes a gesture sensor 240A, a gyro sensor 240B, an air pressure sensor 240C, a magnetic sensor 240D, an acceleration sensor 240E, a grip sensor 240F, a proximity sensor 240G, a color sensor 240H blue sensor), a living body sensor 240I, a temperature / humidity sensor 240J, an illuminance sensor 240K, or an ultraviolet (UV) sensor 240M. Additionally or alternatively, the sensor module 240 may include an electronic sensor such as, for example, an E-nose sensor (not shown), an EMG sensor (not shown), an EEG sensor (not shown) an electrocardiogram sensor (not shown), an infra red sensor (not shown), an iris sensor (not shown), or a fingerprint sensor (not shown). The sensor module 240 may further include a control circuit for controlling at least one sensor included in the sensor module 240.

The input device 250 may include a touch panel 252, a (digital) pen sensor 254, a key 256, or an ultrasonic input device 258. The touch panel 252 can recognize a touch input in at least one of electrostatic, pressure sensitive, infrared, and ultrasonic modes, for example. The touch panel 252 may further include a control circuit. In electrostatic mode, physical contact or proximity recognition is possible. The touch panel 252 may further include a tactile layer. In this case, the touch panel 252 may provide a tactile response to the user.

The (digital) pen sensor 254 can be implemented, for example, in the same or similar manner as receiving a touch input of a user or using a separate recognition sheet. The key 256 may include, for example, a physical button, an optical key or a keypad. The ultrasonic input device 258 is a device for recognizing data by sensing a sound wave from a wearable device 201 to a microphone (e.g., a microphone 288) through an input tool for generating an ultrasonic signal, and is capable of wireless recognition. According to one embodiment, the wearable device 201 may use the communication module 220 to receive user input from an external device (e.g., a computer or a server) connected thereto.

The display 260 (e.g., the display 150) may include a panel 262, a hologram device 264, or a projector 266. The panel 262 may be, for example, a liquid crystal display (LCD) or an active matrix organic light-emitting diode (AM-OLED). The panel 262 may be embodied, for example, in a flexible, transparent or wearable manner. The panel 262 may be composed of the touch panel 252 and one module. The hologram device 264 can display stereoscopic images in the air using interference of light. The projector 266 can display an image by projecting light onto a screen. The screen may, for example, be located inside or outside the wearable device 201. [ According to one embodiment, the display 260 may further include control circuitry for controlling the panel 262, the hologram device 264, or the projector 266.

The interface 270 may include, for example, a high-definition multimedia interface (HDMI) 272, a universal serial bus (USB) 274, an optical interface 276, or a D-sub (D-subminiature) The interface 270 may, for example, be included in the communication interface 160 shown in FIG. Additionally or alternatively, the interface 270 may include, for example, a mobile high-definition link (MHL) interface, a secure digital (SD) card / multi-media card (MMC) interface, or an infrared data association can do.

The audio module 280 can convert sound and electric signals into both directions. At least some components of the audio module 280 may be included, for example, in the input / output interface 140 shown in FIG. The audio module 280 may process sound information input or output through, for example, a speaker 282, a receiver 284, an earphone 286, a microphone 288, or the like.

The camera module 291 may capture still images and moving images. The camera module 291 may include at least one image sensor (e.g., a front sensor or a rear sensor), a lens (not shown), an image signal processor ) Or a flash (not shown), such as an LED or xenon lamp.

The power management module 295 can manage the power of the wearable device 201. Although not shown, the power management module 295 may include, for example, a power management integrated circuit (PMIC), a charger integrated circuit ("IC"), or a battery or fuel gauge.

The PMIC can be mounted, for example, in an integrated circuit or a SoC semiconductor. The charging method can be classified into wired and wireless. The charging IC can charge the battery, and can prevent an overvoltage or an overcurrent from the charger. According to one embodiment, the charging IC may comprise a charging IC for at least one of a wired charging scheme or a wireless charging scheme. The wireless charging system may be, for example, a magnetic resonance system, a magnetic induction system or an electromagnetic wave system, and additional circuits for wireless charging may be added, such as a coil loop, a resonant circuit or a rectifier have.

The battery gauge can measure the remaining amount of the battery 296, the voltage during charging, the current or the temperature, for example. The battery 296 can store or generate electricity, and can supply power to the wearable device 201 using the stored or generated electricity. The battery 296 may include, for example, a rechargeable battery or a solar battery.

The indicator 297 may indicate a specific state of the wearable device 201 or a part thereof (e.g., the AP 210), for example, a boot state, a message state, or a charged state. The motor 298 can convert an electrical signal to mechanical vibration. Although not shown, the wearable device 201 may include a processing unit (e.g., a GPU) for mobile TV support. The processing device for supporting the mobile TV can process media data conforming to standards such as digital multimedia broadcasting (DMB), digital video broadcasting (DVB), or media flow.

Each of the above-described components of the electronic device according to various embodiments may be composed of one or more components, and the name of the component may be changed according to the type of the electronic device. The electronic device according to various embodiments may be configured to include at least one of the above-described components, and some components may be omitted or further include other additional components. In addition, some of the components of the electronic device according to various embodiments may be combined into one entity, so that the functions of the components before being combined can be performed in the same manner.

The term " module " as used herein may mean a unit that includes, for example, one or a combination of two or more of hardware, software, or firmware. A " module " may be interchangeably used with terms such as, for example, unit, logic, logical block, component or circuit. A " module " may be a minimum unit or a portion of an integrally constructed component. A " module " may be a minimum unit or a portion thereof that performs one or more functions. &Quot; Modules " may be implemented either mechanically or electronically. For example, a "module" in accordance with the present disclosure may be implemented as an application-specific integrated circuit (ASIC) chip, field-programmable gate arrays (FPGAs) or programmable logic arrays (FPGAs) logic device).

According to various embodiments, the wearable device 101 performs data backup to the electronic device 102, and includes an application control module 170 and a backup agent, which controls the use of the backup function for a particular application by the backup agent backup agent, the backup agent receives a backup request from the other electronic device, the backup agent generates backup data for each of the applications, and the backup agent transmits the backup data to the other electronic device .

3 is a block diagram of a wearable device and an electronic device according to various embodiments.

Referring to FIG. 3, the wearable device 101 may include an application 310 and a backup agent 320.

The application 310 can be driven in the wearable device 101. For example, the application 310 may correspond to a camera app or a user healthcare application that can be run on the wearable device 101. The application 310 can store data necessary for driving the application or data about the user. For example, when the application 310 is a healthcare application, data on a user's heart rate change or blood pressure change with time may be stored.

According to one embodiment, the application 310 may correspond to an application using the sensor module 240. The application 310 may store data sensed by the sensor module 240. According to another embodiment, the application 310 may correspond to an application using the camera module 291. The application 310 may store image or moving image data generated by the camera module 291. [ According to another embodiment, the application 310 may correspond to an application using the audio module 280. The application 310 may store a sound signal driven by the audio module 280.

The backup agent 320 may correspond to a software drive module for performing data backup in the wearable device 101. The backup agent 320 can be requested from the application 310 to use the backup function. The backup agent 320 can receive data from each application 310 and generate backup data for the corresponding data. The backup agent 320 can send and receive data necessary for data backup with the electronic device 102. [

The electronic device 102 may include a host manager 330 and a host manager app 340.

The host manager 330 is an application for managing the electronic device 102, and can exchange data with the backup agent 320 for data backup and restoration. The host manager 330 may receive the user's backup request from the host manager application 340. The host manager 330 may provide the host manager application 340 with a data backup result or a data restoration result.

The host manager application 340 may correspond to an application supporting the host manager 330. The host manager application 340 can receive information on whether to perform the backup process of the wearable device 101 from the user. The host manager application 340 may provide the host manager 330 with a backup request or restoration request of the user.

4 is a flowchart for explaining a data backup method in a wearable device according to various embodiments.

4, in operation 410, the application 310 may register the use of the backup function with the backup agent 320 in the wearable device 101. [ According to one embodiment, the backup agent 320 can manage an application registered with a backup function through a separate list. For example, a healthcare app may store information about a user's healthcare (e.g., a user's heart rate or blood pressure at a particular point in time). The healthcare application can register the use of the backup function with the backup agent 320 to prevent loss of the user's healthcare information.

At operation 420, the backup agent 320 may receive a backup request from the electronic device 102 at the wearable device 101. The backup agent 320 can proceed with the backup process for the data of the application 310 that registered the use of the backup function according to the backup request. According to one embodiment, the backup agent 320 may receive a backup request from the host manager 330 of the electronic device 102.

At operation 430, the backup agent 320 may generate backup data for each application that has registered the backup function. According to one embodiment, upon receiving a backup request from the electronic device 102, the backup agent 320 may call a backup application programming interface (API) to generate backup data. The backup API may generate backup data including size information and storage location information. Here, the size information may correspond to the capacity of the data unit of the file to be backed up. The storage location information may correspond to information on the storage path in which the backup data will be finally stored. For example, the storage location information may correspond to a path to a specific folder inside the SD card of the electronic device 102. [

At operation 440, the backup agent 320 may send backup data for each application created to the electronic device 102. According to one embodiment, the backup agent 320 may send to the host manager 330 of the backup data electronic device 102.

5 is a flowchart for explaining a data backup method in an electronic device according to various embodiments.

Referring to FIG. 5, in operation 510, the host manager application 340 may request the host manager 330 for a backup of an application running in the wearable device 101. The host manager application 340 can receive information on whether to perform the backup process of the wearable device 101 from the user. The host manager application 340 can provide the request to the host manager 330 when there is a backup request of the user.

In operation 520, the host manager 330 may send a backup request of the host manager application 340 to the backup agent 320 of the wearable device 101.

At operation 530, the host manager 330 may receive backup data from the backup agent 320. According to one embodiment, the host manager 330 may receive backup data for each of the applications that are run in the wearable device 101.

At operation 540, the host manager 330 may store the received backup data. The stored backup data may then be provided to the wearable device 101 through a restore process. According to one embodiment, when the storage location information is included in the backup data, the host manager 330 may store the backup data according to the storage location information. For example, if the storage location information corresponds to a specific folder in the SD card of the electronic device 102, the host manager 330 may store the backup data in the folder.

At operation 550, the host manager 330 may provide the backup results to the host manager application 340. The host manager application 340 can inform the user of the backup result through a pop-up screen.

6 is a signal flow diagram for illustrating a data backup method according to various embodiments.

Referring to FIG. 6, at operation 610, the application 310 may register the use of the backup function in the wearable device 101 with the backup agent 320. The data of the application 310 to which the function is registered can be stored in the electronic device 102 through the backup agent 320.

At operation 620, the backup agent 320 may await receipt of a backup request from the electronic device 102. According to one embodiment, when the backup agent 320 stores a list of applications to perform a backup function and receives a backup request of the user from the electronic device 102, the backup agent 320 performs a backup operation on the data of the applications included in the list You can proceed.

At operation 630, the host manager application 340 may request the host manager 330 to back up the application running on the wearable device 101. The host manager application 340 can receive information on whether to perform the backup process of the wearable device 101 from the user. The host manager application 340 can provide the request to the host manager 330 when there is a backup request of the user.

At operation 640, the host manager 330 may send a backup request of the host manager application 340 to the backup agent 320 of the wearable device 101.

At operation 650, the backup agent 320 may receive backup requests from the host manager 330 of the electronic device 102 and may generate backup data for each application that registered the backup function.

At operation 660, the backup agent 320 may send the backup data for each application created to the host manager 330 of the electronic device 102.

At operation 670, the host manager 330 may store the corresponding backup data. The host manager 330 may store the backup data according to the storage location information when the backup data includes the storage location information.

At operation 680, the host manager 330 may provide a backup result to the host manager application 340. The host manager application 340 can inform the user of the backup result through a pop-up screen.

7 is a signal flow diagram illustrating a process of restoring backup data according to various embodiments.

Referring to FIG. 7, at operation 710, application 310 may drive backup agent 320. The backup data stored in the electronic device 102 can be restored through the backup agent 320. [

At operation 720, the backup agent 320 may await receipt of backup data from the electronic device 102.

At operation 730, the host manager application 340 may request restoration of the backup data stored in the host manager 330. The host manager application 340 can receive information on whether to perform the restoration process for the backup data from the user. The host manager application 340 can provide the request to the host manager 330 when the user requests restoration.

At operation 740, the host manager 330 may send the stored backup data to the backup agent 320 if there is a user's restore request. According to one embodiment, if the host manager 330 is provided with a list of applications to be restored from the wearable device 101, the host manager 330 may extract backup data for the applications included in the list of applications and transmit the backup data to the backup agent 320.

At operation 750, the backup agent 320 may generate restoration data based on the backup data received from the host manager 330. According to one embodiment, when the backup agent 320 is requested to perform the restoration process for a specific application, the backup agent 320 can generate only the data related to the application from the backup data as the restored data. According to one embodiment, when the backup agent 320 receives the restoration request from the electronic device 102, it can call the restoration API (application programming interface) to generate restoration data. The restoration API can generate restoration data that can be used in the application 310 running on the wearable device 101 based on the backup data.

According to various embodiments, at least a portion of a device (e.g., modules or functions thereof) or a method (e.g., operations) according to the present invention may be stored in a computer readable storage medium -readable storage media). The instructions, when executed by one or more processors (e.g., the processor 210), may cause the one or more processors to perform functions corresponding to the instructions. The computer readable storage medium may be, for example, the memory 230. At least some of the programming modules may be implemented (e.g., executed) by, for example, the processor 210. At least some of the programming modules may include, for example, modules, programs, routines, sets of instructions or processes, etc. to perform one or more functions.

The computer-readable storage medium may include magnetic media such as a hard disk, a floppy disk and a magnetic tape, an optical recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc) A magneto-optical medium such as a floppy disk, and a program command such as a read only memory (ROM), a random access memory (RAM), a flash memory, Module) that is configured to store and perform the functions described herein. The program instructions may also include machine language code such as those generated by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

A module or a programming module according to the present invention may include at least one or more of the above-described components, some of which may be omitted, or may further include other additional components. Operations performed by modules, programming modules, or other components in accordance with the present invention may be performed in a sequential, parallel, iterative, or heuristic manner. Also, some operations may be performed in a different order, omitted, or other operations may be added.

It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. Accordingly, the scope of the present invention should be construed as being included in the scope of the present invention, all changes or modifications derived from the technical idea of the present invention.

101: Wearable device 102: Second electronic device
110: bus
120: processor 130: memory
131: Kernel 132: Middleware
133: Application Programming Interface (API)
134: Application 140: I / O interface
150: Display module 160: Communication interface
162: network 170: application control module
200: electronic device 210: application processor (AP)
220: Communication module 221: Cellular module
223: wifi module 225: BT module
227: GPS module 228: NFC module
229: RF module 230: memory
232: internal memory 234: external memory
224: SIM card 240: Sensor module
240A: Gesture sensor 240B: Gyro sensor
240C: Pressure sensor 240D: Magnetic sensor
240E: Acceleration sensor 240F: Grip sensor
240G: Proximity sensor 240H: RGB sensor
240I: Biosensor 240J: On / Humidity sensor
240K: Light sensor 240M: UV sensor
250: input device 252: touch panel
254: pen sensor 256: key
258: Ultrasonic input device 260: Display module
262: Panel 264: Hologram
266: projector 270: interface
272: HDMI 274: USB
276: Optical interface 278: D-SUB
280: Audio module 282: Speaker
284: Receiver 286: Earphone
288: Microphone 291: Camera module
295: Power management module 296: Battery
297: Indicator 298: Motor
310: Application 320: Backup Agent
330: Host Manager 340: Host Manager App

Claims (10)

A method of backing up data between a wearable device and an electronic device,
Registering, in the wearable device, a use of a backup function for a specific application with a backup agent;
In the wearable device, the backup agent may receive a backup request from the electronic device;
In the wearable device, the backup agent may generate backup data for each of the applications; And
In the wearable device, the backup agent transmits the backup data to the electronic device. The method of claim 1,
In the wearable device, the backup agent comprises: receiving backup data from the electronic device; And
In the wearable device, the backup agent converts the backup data into restoration data usable in the application. The method of claim 1, wherein the act of registering with the backup agent
And storing a list of applications for which the backup agent requested the backup function. 2. The method of claim 1, wherein the act of generating the backup data comprises:
And storing the size information and the storage location information of the backup data. A method of backing up data between a wearable device and an electronic device,
In the electronic device, sending a backup request to the wearable device;
Receiving, in the electronic device, backup data classified according to an application from the wearable device;
And in the electronic device, storing the backup data. 6. The method of claim 5,
In the electronic device, providing the backup data to the wearable device;
And receiving, in the electronic device, restoration information for each application from the wearable device. 7. The method of claim 6, wherein providing backup data comprises:
Receiving an application list to be restored from the wearable device in the electronic device;
And in the electronic device, extracting backup data for an application included in the application list. 6. The method of claim 5,
And size information of the backup data and storage location information. 9. The method of claim 8, wherein the act of storing the backup data
And storing the backup data based on the storage location information. 1. A wearable device for performing data backup to another electronic device,
An application control module and a backup agent,
The application control module registers usage of a backup function for a specific application with the backup agent,
The backup agent receiving a backup request from the another electronic device,
Wherein the backup agent generates backup data for each of the applications,
And the backup agent transmits the backup data to the other electronic device.

Images