Electronic apparatus and control method

According to one embodiment, an electronic apparatus includes a transceiver and a processor. The transceiver is connectable to any of a plurality of wearable devices wearable by a user. The processor updates a configuration file that stores one or more configuration values of the plurality of wearable devices. The processor provides, when a first wearable device of the plurality of wearable devices is connected to the electronic apparatus, the one or more configuration values to the first wearable device. The processor provides, when a second wearable device of the plurality of wearable devices is connected to the electronic apparatus, the one or more configuration values to the second wearable device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based upon and claims the benefit of priority from Japanese Patent Application No. 2018-158396, filed Aug. 27, 2018, the entire contents of which are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to an electronic apparatus and a control method of the electronic apparatus.

BACKGROUND

Recently, an IoT (Internet of Things) age in which many things are connected through the Internet has come. A technique called “edge computing” is required as a tool for network communication and information sharing in offices, factories, and in other various situations. In order to realize the edge computing, development of a practical mobile edge computing device (MECD) having high degrees of versatility and processing capacity, and can be used by an operator (user) on site, is needed separately from a data center (or cloud). Thereby, it is expected that promotion of the operational efficiency and productivity improvement at a workplace and the like, or load dispersion of data and improvement in a network environment and the like, will be achieved.

Mobile devices such as MECD may be used with any wearable device such as an eyeglass-type equipment and a bracelet-type equipment. The mobile device and the wearable device mutually transmit and receive data, so that the mobile device can process data generated by, for example, a camera or a sensor provided in the wearable device.

The wearable device operates based on configurations (also referred to as environment settings). A user may change the configurations by an operation to the wearable device or an operation to a mobile device to which the wearable device is connected. Information related to the configurations of the wearable device is, for example, stored in the wearable device.

The information related to the configurations may be stored in a volatile memory. In that case, the information will be lost when power to the wearable device is shut off.

Furthermore, there is a case where a wearable device is connected to a mobile device and then another wearable device is connected to the mobile device. In that case, if these wearable devices are products of the same type, and if a user wants to use these wearable devices in the same configurations, the user must perform operations of configurations for each of these wearable devices.

DETAILED DESCRIPTION

In general, according to one embodiment, an electronic apparatus includes a transceiver and a processor. The transceiver is connectable to any of a plurality of wearable devices wearable by a user. The processor updates a configuration file that stores one or more configuration values of the plurality of wearable devices. The processor provides, when a first wearable device of the plurality of wearable devices is connected to the electronic apparatus, the one or more configuration values to the first wearable device. The processor provides, when a second wearable device of the plurality of wearable devices is connected to the electronic apparatus, the one or more configuration values to the second wearable device.

Hereinafter, embodiments will be described with reference to the drawings. Note that the disclosure is merely an example, and the invention is not limited by the content described in the following embodiments. Naturally, the modifications easily conceivable by those skilled in the art are included in the scope of the disclosure. In order to make the description clearer, there are cases where the size, shape, etc., of each part in the drawings are schematically represented by changing them relative to the actual embodiment. In a plurality of drawings, corresponding elements are denoted by the same reference numerals, and a detailed explanation may be omitted.

First, referring toFIG. 1, a configuration of a control system1including an electronic apparatus according to an embodiment will be described. This electronic apparatus is a portable wireless device that can be implemented as a mobile personal computer (PC) including a mobile edge computing device (MECD), or a mobile information terminal such as a smartphone, a mobile phone, a PDA, and the like. Hereinafter, a case where this electronic apparatus is realized as a mobile PC2will be exemplified.

The control system1includes the mobile PC2and a wearable device3. The user carries the mobile PC2and wears the wearable device3. The wearable device3can be worn on a user's body (for example, the arm, the neck, the head, etc.). As the wearable device3, a wearable device of a glass-type, a bracelet-type, a wristwatch-type, a headphone-type, or the like can be used. In the following, it is assumed that the wearable device3is a glass-type wearable device.

The wearable device3includes an eyeglass frame142and a wearable device main body4. The eyeglass frame142may have a shape obtained by removing a lens from general eyeglasses, and is mounted on the face of an operator. The eyeglass frame142may have a structure to which eyeglasses are attached. In a case where an operator regularly uses eyeglasses, lenses having the same power as those of regularly used eyeglasses may be attached to the eyeglass frame142. The wearable device main body4is constituted of a side part241to be along the temple of the eyeglass frame142, and a front part242to be positioned on the line of sight of one eyeball of the operator. The angle which the front part242forms with the side part241is adjustable.

The mobile PC2and the wearable device3establish a wired connection or a wireless connection to communicate. In the example shown inFIG. 1, the mobile PC2and the wearable device3are connected by a cable146. This cable146is, for example, a cable conforming to USB type-C (registered trademark) standard. The mobile PC2may communicate with the wearable device3by various wireless communication methods such as wireless LAN or Bluetooth (registered trademark).

As shown inFIG. 1, at the rear end of the side part241of the wearable device main body4, a USB Type-C standard receptacle132to which a plug146A at one end of the cable146is to be inserted is provided. A plug146B at the other end of the cable146is inserted into a receptacle207conforming to USB Type-C standard provided on the upper end face of the mobile PC2. As described above, the wearable device main body4is connected to the mobile PC2through the USB type-C cable146, and various signals are transmitted from/to the wearable device main body4to/from the mobile PC2. The plugs and receptacles may be replaced with each other in accordance with the design or the like, and they may be referred to as connector. The wearable device main body4may also be connected to the mobile PC16by means of wireless communication such as a wireless LAN, Bluetooth, and the like.

In the embodiment, the wearable device main body4is not provided with a battery or DC terminal serving as a drive power supply, and the drive power is supplied from the mobile PC2to the wearable device main body4through the USB type-C cable146. However, the wearable device main body24may also be provided with a drive power supply.

The operator may always use a particular mobile PC2or may use one of mobile PCs2. That is, the operator may pick up a new one from the mobile PCs2at each operation occasion. Furthermore, for example, one wearable device3is connected to the mobile PC2used by the operator in each time. The wearable device3to be connected to the mobile PC2may be different at each time. The wearable devices3that may be connected to the mobile PC2may be devices of same type or devices having the same functions.

The number of mobile PCs2and the number of wearable devices3that constitute the control system1used by operators may have a relationship of 1 to N or N to N where N is an integer of one or more.

FIG. 2shows an example of an external appearance of the mobile PC (mobile edge computing device)2. The mobile PC2is a small-sized PC that can be held by one hand, and has a small size and light weight, i.e., a width thereof is about 10 cm or less, height thereof is about 18 cm or less, thickness thereof is about 2 cm, and weight thereof is about 300 g. Accordingly, the mobile PC2can be held in a pocket of the work clothing of the operator, holster to be attached to a belt, or a shoulder case, and is wearable. Although the mobile PC2incorporates therein semiconductor chips such as the CPU, semiconductor memory, and the like, and storage devices such as a Solid State Disk (SSD), and the like, the mobile PC2is not provided with a display device and hardware keyboard for input of characters.

On the front surface of the mobile PC2, cursor buttons202constituted of an up button202a, right button202b, down button202c, left button202d, and decision button202e(also called a center button or enter button) are arranged, and fingerprint sensor204is arranged below the cursor buttons202. The mobile PC2is not provided with a hardware keyboard for input of characters, and a password number (also called a PIN) cannot be input. Therefore, the fingerprint sensor204is used for user authentication at the time of login of the mobile PC2. A command can be input from the cursor buttons202.

The operation procedures of the cursor buttons202are determined by programs.

For example,

when the decision button202eis pressed once, item selection/item execution is carried out,

when the decision button202eis pressed for a long time, ending or cancellation of an operation is carried out,

when the up button202ais pressed once, the cursor is moved upward,

when the up button202ais pressed for a long time, a list of application programs being executed is displayed,

when the down button202cis pressed once, the cursor is moved downward,

when the down button202cis pressed for a long time, a menu of quick settings is displayed,

when the left button202dis pressed once, the right icon is selected, and

when the right button202bis pressed once, the left icon is selected.

On the upper side face of the mobile PC2, a USB 3.0 receptacle206, a USB type-C receptacle207, and an audio jack208are provided.

On one side face (e.g., side face on the left side when viewed from the front) of the mobile PC2, a memory card slot218for a memory card is provided. The memory card includes, for example, an SD card, micro SD card (registered trademark), and the like.

On the other side face (e.g., side face on the right side when viewed from the front) of the mobile PC2, a slot210for Kensington Lock (registered trademark), power switch212, power LED213, DC IN/battery LED214, DC terminal216, and ventilation holes222for cooling are provided. The power LED213is arranged around the power switch212, and is turned on while the mobile PC2is being powered on. The DC IN/battery LED214indicates the state of the mobile PC2such as whether the battery is being charged, and remaining battery level. Although the mobile PC2may be driven by the battery, the mobile PC2can also be driven in the state where the AC adaptor is connected to the DC terminal216. Although not shown, the back side of the mobile PC2is configured such that the battery can be replaced with a new one by a one-touch operation.

FIG. 3shows an example of the system configuration of the mobile PC2. The mobile PC2includes a system controller302. The system controller302includes a processor (CPU) and a controller hub. A main memory308, a BIOS-ROM310, the power LED213, the DC IN/battery214, and a USB controller322are connected to the processor. A flash memory326, a memory card controller328, a storage device330including an HDD or an SSD, a USB switch324, an audio codec334, a 3G/LTE/GPS device336, the finger print sensor204, a USB 3.0 receptacle206, a Bluetooth/wireless LAN device340, and an EC/KBC344are connected to the controller hub.

The system controller302executes various programs loaded from the storage device330into the main memory308. The system controller302controls the operation of each component in the mobile PC2by executing the instructions included in the programs.

The programs include an OS308A, a configuration service308B, a first configuration utility308C, a second configuration utility308D, and various application programs308E. The configuration service308B is a program to provide a function to manage configurations (that is, environment settings) of the mobile PC2and the wearable device3, and a function to apply the configurations to each of the mobile PC2and the wearable device3.

The first configuration utility308C is a utility program to confirm and change the configurations by a user (for example, administrator) with input/output devices such as display, keyboard, pointing device connected to the mobile PC2. The second configuration utility308D is a utility program to confirm and change the configurations by a user (for example, operator, worker, etc.) with the wearable device3connected to the mobile PC2. A user uses at least one of the first configuration utility308C and the second configuration utility308D in accordance with the operation environment of the user, for example.

The application programs308E include programs related to the operation of the wearable device3. The application program308E is used for voice conversation, video streaming, image sharing, and the like. When executing each program, a change to the configurations of the wearable device3may be necessary.

The first configuration utility308C, second configuration utility308D, and various application programs308E may request the configuration service308B to change the configurations. The configuration service308B changes the configurations in accordance with the request, and provides the changed configurations to at least one of the mobile PC2and the wearable device3.

The audio codec334converts a digital audio signal to be played into an analog audio signal and supplies the converted analog signal to the audio jack208. Further, the audio codec334converts an analog audio signal input from the audio jack208into a digital signal.

The memory card controller328accesses a memory card (for example, an SD card) inserted into the memory card slot218, and controls reading/writing of data from/to the memory card.

The USB controller322controls transmission and reception of data with respect to a USB Type-C cable including a plug that is connected to the USB Type-C receptacle207or a USB 3.0 cable (not shown) including a plug that is connected to the USB 3.0 receptacle206. A type of interface that is not provided in the mobile PC2, such as USB, HDMI (registered trademark) and the like can be used by connecting a USB hub and a port extension adapter to the USB Type-C receptacle207.

The Bluetooth/wireless LAN device340executes wireless communication conforming to the Bluetooth/IEEE802.11 standard for the purpose of connection to the network. For the connection to the network, not only wireless communication but also wired LAN communication conforming to the IEEE802.3 standard may be used.

The fingerprint sensor204is used for fingerprint authentication at the time of boot or reboot of the mobile PC2.

A sub-processor346, the power switch212, and the cursor buttons202are connected to the EC/KBC344. The EC/KBC344has a function of turning on or turning off the power to the mobile PC2in response to the operation of the power switch212. The control of power-on and power-off is executed by the cooperative operation of the EC/KBC344and power circuit350. Even during a power-off period of the mobile PC2, the EC/KBC344operates by the power from a battery352or AC adaptor358connected as an external power supply. The power circuit350uses the power from the battery352or AC adaptor358to thereby control power to be supplied to each component. The power circuit350includes a voltage regulator module356. The voltage regulator module356is connected to the processor in the system controller302.

Although the mobile PC2is constituted as a body separate from the wearable device main body4, the mobile PC2may be incorporated into the wearable device main body4, and both of them may also be integrated into one body.

An example of the external appearance of the wearable device3connected to the mobile PC2will be explained with reference toFIGS. 4 and 5. As described above, the wearable device3includes the eyeglass frame142and the wearable device main body4.

The eyeglass frame142is provided with mounting brackets144on both the right and left temples thereof. The wearable device main body24is attached to and detached from one of the mounting brackets144on the right or left temple. InFIG. 4, the mounting bracket144on the temple on the right side of the operator is hidden behind the wearable device main body4, and hence is not shown. As described above, the wearable device main body4is provided with a display device124. The display device124is configured in such a way as to be viewed by one eye. Therefore, the mounting brackets144are provided on both the right and left temples so that the wearable device main body4can be attached to the mounting bracket on the dominant eye side. The wearable device main body4need not be detachably attached to the eyeglass frame142by means of the mounting bracket144. The wearable devices3for the right eye and left eye in which the wearable device main bodies4are respectively fixed to the eyeglass frames142on the right and left frames may be prepared. Furthermore, the wearable device main body4may not be attached to the eyeglass frame142, but may be attached to the head of the operator by using a helmet or goggle.

An engaging piece128(shown inFIG. 4) of the wearable device main body4is forced between upper and lower frames of the mounting bracket144, whereby the wearable device main body4is attached to the eyeglass frame142. When the wearable device main body4is to be detached from the eyeglass frame142, the wearable device main body4is plucked out of the mounting bracket144.

In a state where the wearable device main body4is attached to the mounting bracket144, the engaging piece128is somewhat movable backward and forward in the mounting bracket144. Accordingly, the wearable device main body4is adjustable in the front-back direction so that the operator's eye can be brought to a focus on the display device124.

Furthermore, the mounting bracket144is rotatable around an axis144A perpendicular to the temple. After the wearable device main body4is attached to the eyeglass frame142, the wearable device main body4is adjustable in the vertical direction so that the display device124can be positioned on the operator's line of sight. Moreover, the rotational angle of the mounting bracket144is about 90 degrees and, by largely rotating the mounting bracket144in the upward direction, the wearable device main body4can be flipped up from the eyeglass frame142. Thereby, even when it is difficult to watch the real thing because the field of view is obstructed by the wearable device main body4or even when the wearable device main body4interferes with surrounding objects in a small space, it is possible to temporarily divert/restore the wearable device main body4from/to the field of view of the operator without detaching/reattaching the entire wearable device3from/to the face of the operator.

As described above, the wearable device main body4is constituted of the side part241to be along the temple of the eyeglass frame142, and the front part242to be positioned on the line of sight of one eyeball of the operator. The angle which the front part242forms with the side part is adjustable.

As shown inFIG. 4, on the outside surface of the front part242, a camera116, a light118, and a camera LED120are provided. The light118is an auxiliary lighting fixture emitting light at the time of shooting a dark object. The camera LED120is configured to be turned on at the time of shooting a photograph or video to thereby cause the objective person to be photographed to recognize that he or she is to be photographed.

On the top surface of the side part241of the wearable device main body4attached to the right side temple, first, second, and third buttons102,104, and106are provided. When the dominant eye of the operator is the left eye, the wearable device main body4is attached to the left side temple. The top and the bottom of the wearable device main body4are reversed according to whether the wearable device main body4is attached to the right side temple or to the left side temple. Therefore, the first, second, and third buttons102,104, and106may be provided on both the top surface and undersurface of the side part241.

On the outside surface of the side part241, a touchpad110, fourth button108, microphone112, and illuminance sensor114are provided. The touchpad110and fourth button108can be operated by a forefinger. When the wearable device main body4is attached to the right side temple, the buttons102,104, and106are arranged at positions at which the buttons102,104, and106can be operated by a forefinger, middle finger, and third finger, respectively. The touchpad110is configured such that the movement of finger in up and down directions or back and forth directions on the surface on the touchpad110as indicated by arrows can be detected. The movement to be detected includes flicking of a finger for grazing the surface quickly in addition to dragging of a finger for moving the finger with the finger kept in contact with the surface. Upon detection of up-and-down or back-and-force movement of the operator's finger, the touchpad110inputs a command. In this description, a command implies an executive instruction to execute specific processing to be issued to the wearable device main body4. Operation procedures for the first to fourth buttons102,104,106, and108, and touchpad110are determined in advance by the programs.

For example,

when the third button106is pressed once, item selection/item execution is carried out (corresponding to pressing once of the decision button202ein the mobile PC2),

when the third button106is pressed for a long time, a list of application programs being executed is displayed (corresponding to pressing the up button202afor a long time in the mobile PC2),

when the second button104is pressed once, the screen returns to a home screen,

when the second button104is pressed for a long time, a menu of quick settings is displayed (corresponding to pressing the down button202cfor a long time in the mobile PC2), and

when the first button102is pressed once, cancelation of operation (corresponding to pressing once of the decision button202ein the mobile PC2or operation identical to the operation of the Esc key of keyboard) is executed.

Regarding the operation of the touchpad110, for example,

when the touchpad110is dragged up and down, the cursor is moved up and down,

when the touchpad110is flicked forward (to the front of the head), the left icon is selected (continuously scrolled) (corresponding to pressing once of the right button202bin the mobile PC2),

when the touchpad110is flicked backward (to the back of the head), the right icon is selected (continuously scrolled) (corresponding to pressing once of the left button202din the mobile PC2),

when the touchpad110is dragged forward, the left icon is selected (items are scrolled one by one) (corresponding to pressing once of the right button202bin the mobile PC2), and

when the touchpad110is dragged backward, the right icon is selected (items are scrolled one by one) (corresponding to pressing once of the left button202din the mobile PC2).

The first button102, second button104, third button106, and fourth button108are arranged to be operated by a forefinger, a middle finger, a third finger, and a little finger, respectively. The reason why the fourth button108is provided not on the top surface of the side part241, but on the outside surface of the side part241is that there is space restriction. The fourth button108may also be provided on the top surface of the side part241in the same manner as the first to third buttons102,104, and106.

The operations performed with the buttons102,104,106, and108and touchpad110of the wearable device main body4can be performed similarly with the cursor buttons202provided with the mobile PC2. Since operators cannot view the operation of the buttons102,104,106, and108and the touchpad110of the wearable device main body4, some operators may require a time to get used to perform intentional operation. Furthermore, the buttons102,104,106, and108and the touchpad110are small and may be difficult to operate. In the present embodiment, the same operations can be performed with the cursor buttons202of the mobile PC2, and thus, the above problems can be solved.

The illuminance sensor114detects the illuminance of the surrounding area in order to automatically adjust the brightness of the display device. The sensor controller162(shown inFIG. 6) and the display controller170(shown inFIG. 6) have a brightness auto-adjustment function to automatically adjust the brightness of display124based on the illuminance detected by the illuminance sensor114. The sensor controller162and the camera controller168(shown inFIG. 6) has an LED auto-adjustment function to automatically switch on or off of the flashlight118based on the illuminance detected by the illuminance sensor114.

FIG. 5shows an example of an external appearance of the back side of the wearable device main body4. On the inner side of the front part242, a display device124constituted of an LCD is provided. On the inner side of the side part241, a microphone126, speaker130, and engaging piece128are provided. The microphone126is provided at a front position of the side part241, and speaker130and engaging piece128are provided at a rear position of the side part. Headphones may be used in place of the speaker130. In this case, the microphone and headphones may also be provided in an integrated manner as a headset.

FIG. 6shows an example of the system configuration of the wearable device main body4. The USB type-C receptacle132is connected to a mixer166. The display controller170and USB hub164are respectively connected to a first terminal and second terminal of the mixer166. The display device124is connected to the display controller170. The camera controller168, an audio codec172, and the sensor controller162are connected to the USB hub164. The camera116, flashlight118, and camera LED120are connected to the camera controller168. Audio signals from the microphones112and126are input to the audio codec172, and audio signal from the audio codec172is input to the speaker130through an amplifier174.

A motion sensor (for example, acceleration, geomagnetism, gravitation, gyroscopic sensor, etc.)176, the illuminance sensor114, a proximity sensor178, the touchpad110, the first to fourth buttons102,104,106, and108, and a GPS sensor180are connected to the sensor controller162. The sensor controller162processes signals generated by the motion sensor176, illuminance sensor114, proximity sensor178, touchpad110, first to fourth buttons102,104,106, and108, and GPS sensor180, and supplies a command to the mobile PC16. Although not shown inFIG. 5, the motion sensor176and proximity sensor178are arranged inside the wearable device main body4.

The motion sensor176detects movement, orientation, posture, and the like of the wearable device main body4. The sensor controller162and the display controller170have an orientation auto-adjustment function to automatically adjust the orientation of the screen image displayed on the display124based on the movement, orientation, posture, and the like detected by the motion sensor176.

The proximity sensor178detects attachment of the wearable device3based on approach of a face, finger and the like of the operator thereto.

The memory controller182controls reading and writing of data with respect to RAM184that is a volatile memory. Furthermore, the memory controller182controls reading and writing of data with respect to a flash memory186that is a nonvolatile memory. One or more configuration values to control operation of each component in the wearable device3are stored in at least one of the RAM184and the flash memory186. Each component of the wearable device3is operated based on the one or more configuration values stored in the RAM184and the flash memory186.

Each configuration value stored in the RAM184and the flash memory186is updated in accordance with a signal to change the configuration value sent from the mobile PC2. The configuration values stored in the RAM184are lost by the boot or reboot of the mobile PC2. If the wearable device main body4includes a drive power source, the configuration values stored in the RAM184are lost when the wearable device main body4is turned off.

Note that, instead of the RAM184and the flash memory186, at least one of a volatile memory and a nonvolatile memory may be installed into each of the sensor controller162, the camera controller168, the display controller170, and the audio codec172. In that case, the configuration values related to these components162,168,170, and172may be stored in each installed memory.

FIG. 7shows an example where input/output devices are connected to the mobile PC2via the USB hub5. As described above, the USB 3.0 receptacle206is provided with the upper side surface of the mobile PC2. A plug50A at one end of USB 3.0 cable50provided with the USB hub5is inserted into the USB 3.0 receptacle206. The USB hub5includes multiple USB 3.0 receptacles. Thus, when the plug50A is inserted into the USB 3.0 receptacle206of the mobile PC2, various input/output devices can be connected to the mobile PC2via the USB hub5. The input/output devices are, for example, a display6, a keyboard7, and a pointing device8(for example, mouse).

The display6receives image signals sent from the mobile PC2via the USB hub5and displays a screen image based on the image signals. The keyboard7sends a signal corresponding to an operation by a user (for example, a code corresponding to a key pressed by the user) to the mobile PC2via the USB hub5. The pointing device8sends a signal corresponding to an operation by a user (for example, data indicative of a button pressed by the user, and/or coordinate data indicative of a position instructed by the user) to the mobile PC2via the USB hub5.

The display6displays, for example, a screen image including GUI to confirm and change the configurations of the mobile PC2and the wearable device3when the first configuration utility308C is executed on the mobile PC2. The keyboard7and the pointing device8may be used for operating the GUI.

FIG. 8shows an example of the functional configuration of the mobile PC2. The mobile PC2includes, for example, an update control module41, a connection detection module42, and a configuration control module43. These modules41,42, and43are realized by the system controller302(processor) of the mobile PC2executing instructions included in the configuration service308B and controlling the operation of each component indicated as the system configuration of the mobile PC2. The system configuration of the mobile PC2is described above with reference toFIG. 3.

The update control module41updates a configuration file (also referred to as an environment setting file)45in cooperation with the first configuration utility308C, the second configuration utility308D, and the application programs308E. The first configuration utility308C, second configuration utility308D, and application programs308E may use API to operate in cooperation with the update control module41(configuration service308B). The first configuration utility308C, the second configuration utility308D, and the application programs308E use API to request the update control module41to acquire current configuration values and to update configuration values, for example.

The configuration file45stores one or more configuration values related to the configurations of the wearable device3. The configuration values are used to control the operation of one or more components provided in each of one or more wearable devices3that may be connected to the mobile PC2. The one or more components may include any of the components of the wearable device3explained above with reference toFIG. 6.

The configuration values that may be acquired or changed by the first configuration utility308C, the second configuration utility308D and the application programs308E, are managed by a single configuration file45. The configuration file45may be used as a master of the configuration values to provide the same configuration to the wearable devices3A,3B, and3C. Thus, upon connection of any of the wearable devices3A,3B, and3C to the mobile PC2, the configuration values indicated in the configuration file45are provided to the connected wearable device3A,3B, or3C. Thus, any of the wearable devices3A,3B, and3C can be operated with the single configurations.

The configuration file45is stored in the nonvolatile memory such as a storage device330or a flash memory326. Note that the configuration file45may be stored in a server to which the mobile PC2is connected via the network. In that case, the update control module41may acquire the configuration file45from the server via the network and update the configuration file45stored in the server via the network, for example.

Now, operation of each component at the time when the acquisition and change of the configuration values are requested by the first configuration utility308C, the second configuration utility308D, or the application program308E will be specifically explained.

Firstly, the update control module41provides configuration values indicated in the configuration file45when the first configuration utility308C, the second configuration utility308D, or the application program308E is started.

By using the provided configuration values, the first configuration utility308C displays GUI for a user (for example, administrator) to confirm and change the configurations on the display6connected to the mobile PC2. The user may perform an operation to change any of the configuration values to the GUI using an input device such as the keyboard7or the pointing device8. The first configuration utility308C requests the update control module41to change the configuration values in accordance with the operation by the user.

Similarly, by using the provided configuration values, the second configuration utility308D displays GUI for a user (for example, operator, worker, etc.) to confirm and change the configurations on the display124of the wearable device3. The user may perform an operation to change any of the configuration values to the GUI using the cursor buttons202or the like. The second configuration utility308D requests the update control module41to change the configuration values in accordance with the operation by the user.

Furthermore, the application program308E is, for example, an application program for voice conversation, image streaming, screen sharing, and the like. The application program308E that has been started requests, when the configuration values provided by the configuration service308B are not suitable for the function provided by the application program308E, the update control module41to change the configuration value (or values). The application program308E may request the update control module41to change the configuration value (or values) in accordance with a user's operation using the configuration menu or the like provided with the application program308E.

The update control module41receives a request related to a change of the configuration value (or values) from each of the first configuration utility308C, the second configuration utility308D, and the application program308E. The request includes, for example, information indicative of the configuration value after the change. The update control module41updates the configuration file45in accordance with the request. Note that, the wearable device3may not be connected to the mobile PC2while the operation to change the configuration value is performed and the process to update the configuration file45is executed. The configuration file45can be updated regardless of whether or not the wearable device3is connected to the mobile PC2.

FIG. 9shows a configuration example of the configuration file45. The configuration file45includes records corresponding to configuration values. Each record includes respective fields of a target, a parameter, possible configuration values, an initial value, and a current value.

In a record corresponding to a configuration value, the target field shows an element in the wearable device3that operates based on the configuration value. The target field may show an element corresponding to a component in the wearable device3, or an element corresponding to multiple components in the wearable device3. The element is, for example, “display”, “touchpad”, “button”, “flashlight”, “audio”, or the like. The “display”, “touchpad”, “button”, and “flashlight” indicate the display124, the touchpad110, the buttons102,104,106, and108, and the flashlight118, respectively, as the components in the wearable device3. Furthermore, the “audio” indicates at least one of the microphones112and126and the speaker130.

The field of possible configuration values shows values or a range of values that can be set as the corresponding configuration value. The initial value field shows a value initially set as the configuration value. The current value field shows a value to be currently set as the configuration value. The value shown in the current value field is provided to the configuration value stored in the wearable device3to control the operation of the wearable device3.

Values set to the target filed, the parameter field, the field of possible configuration values, and the initial value field may be preliminarily defined by an administrator or the like. On the other hand, the value set in the current value field may be changed in accordance with a request of change by any one of the first configuration utility308C, the second configuration utility308D, and the application program308E.

In the following description, a specific example of the configuration file45shown inFIG. 9will be explained.

In the four records each including the target field to which “display” is set, the parameter fields of the four records show “brightness auto-adjustment”, “brightness”, “orientation auto-adjustment”, and “orientation”, respectively.

The “brightness auto-adjustment” is a parameter to turn on or off the brightness auto-adjustment function to automatically change the brightness of the display124. In the corresponding record, the field of possible configuration values shows “on” and “off”. This record also includes the initial value field showing “on” and the current value field showing “on”.

The “brightness” is a parameter to set the brightness of the display124. In the corresponding record, the field of possible configuration values shows 0 to 255. This record also includes the initial value field showing “70” and the current value field showing “100”.

The “orientation auto-adjustment” is a parameter to turn on or off the orientation auto-adjustment function to automatically change the orientation of screen image displayed on the display124. In the corresponding record, the field of possible configuration values shows “on” and “off”. This record also includes the initial value field showing “off” and the current value field showing “on”.

The “orientation” is a parameter to set the orientation of the screen image displayed on the display124. In the corresponding record, the field of possible configuration values shows “left” and “right”. This record also includes the initial value field showing “right” and the current value field showing “right”.

In the three records each including the target field to which “touchpad” is set, the parameter fields of the three records show “touchpad”, “vertical direction flip”, and “horizontal direction flip”, respectively.

The “touchpad” is a parameter to turn on or off the input using the touchpad110. In the corresponding record, the field of possible configuration values shows “on” and “off”. This record also includes the initial value field showing “on” and the current value field showing “on”.

The “vertical direction flip” is a parameter to turn on or off the input by flipping in which a finger is vertically slid on the touchpad110. In the corresponding record, the field of possible configuration values shows “on” and “off”. This record also includes the initial value field showing “off” and the current value field showing “off”.

The “horizontal direction flip” is a parameter to turn on or off the input by flipping in which a finger is horizontally slid on the touchpad110. In the corresponding record, the field of possible configuration values shows “on” and “off”. This record also includes the initial value field showing “off” and the current value field showing “off”.

In the nine records each including the target field to which “button” is set, the parameter fields of the nine records show “current profile”, “first button short key code”, “second button short key code”, “third button short key code”, “fourth button short key code”, “first button long key code”, “second button long key code”, “third button long key code”, and “fourth button long key code”, respectively.

The “current profile” is a parameter to set the profile of the first to fourth buttons102,104,106, and108. In the corresponding record, the field of possible configuration values shows 0 to 7. This record also includes the initial value field showing “0” and the current value field showing “0”.

The “first button short key code” is a parameter to set a key code generated when the first button102is pressed for less than a threshold value. In the corresponding record, the field of possible configuration value shows USB HID key codes (that is, values defined as USB HID key codes). This record also includes the initial value field showing “114” and the current value field showing “114”.

The “first button long key code” is a parameter to set a key code generated when the first button102is pressed for the threshold value or more. In the corresponding record, the field of possible configuration values shows USB HID key codes. This record also includes the initial value field showing “114” and the current value field showing “114”.

Similarly, each of the records that include parameter fields showing “second button short key code”, “third button short key code”, “fourth button short key code”, “first button long key code”, “second button long key code”, “third button long key code”, and “fourth button long key code”, respectively, shows setting related to a key code generated when the second button104, the third button106, or the fourth button108is pressed.

In the record including the target field to which “flashlight” is set, the parameter field of the record shows “LED light auto-adjustment”. The “LED light auto-adjustment” is a parameter to turn on or off an auto-flash function (that is, LED light auto-adjustment function) based on illuminance and the like by the flashlight118. In the corresponding record, the field of possible configuration values shows “on” and “off”. This record also includes the initial value field showing “on” and the current value field showing “off”.

In the record including the target field in which “audio” is set, the parameter field of the record shows “audio mode”. The “audio mode” is a parameter to set a mode of the microphones112and126, and the speaker130. In the corresponding record, the field of possible configuration values shows “voice call”, “live recording”, and “personal recording”. This record also includes the initial value field showing “live recording” and the current value field showing “live recording”.

The update control module41changes, when a change of a configuration value is requested by the first configuration utility308C, the second configuration utility308D, or the application program308E, the value indicated in the current value field of the corresponding record in the configuration file45to the requested value. Each request from the first configuration utility308C, the second configuration utility308D, and the application program308E includes information corresponding to target, parameter and current value fields, for example.

The connection detection module42may detect that the wearable device3is connected to the mobile PC2and that the wearable device3is disconnected from the mobile PC2. Thus, the connection detection module42can determine whether the wearable device3is in connection.

Wearable devices3A,3B, and3C of the same type or wearable devices3A,3B, and3C having the same function (or functions) may be connected to the mobile PC2. The wearable devices3A,3B, and3C having the same function are devices which are operated similarly based on a certain configuration value.

The configuration control module43provides the configuration values, which are indicated in the configuration file45, to the wearable device3connected to the mobile PC2. Examples of timing when the configuration values indicated in the configuration file45are provided to the wearable device3will listed below. Note that, in any case, the configuration service308B is executed on the mobile PC2.

(1) when the mobile PC2is booted or rebooted while the wearable device3is connected to the mobile PC2;

(2) when the mobile PC2transitions to a sleep or a suspend (or hibernation) state and then returns from the state while the wearable device3is connected to the mobile PC2;

(3) when the configuration file45is updated in the mobile PC2in operation while the wearable device3is connected to the mobile PC2;

(4) when the wearable device3is newly connected to the mobile PC2in operation; and

(5) when the wearable device3is connected to the mobile PC in a sleep or a suspend state and then the mobile PC2returns from the state.

At each timing of (1)˜(5), the configuration values indicated in the configuration file45are provided to the wearable device3, and thus, the following advantages can be achieved.

In the cases of (1) and (2), even if the configuration values stored in the volatile memory of the wearable device3is lost because the mobile PC2is turned off or is in a sleep or a suspend state (that is, power supplied from the mobile PC2to the wearable device3is shut off), or because the mobile PC2is rebooted, the configuration values indicated in the configuration file45stored in the mobile PC2can be provided to the wearable device3. Thus, a user can use the wearable device3with the same configuration as used before the mobile PC2is turned off, is rebooted, or transitions to a sleep or a suspend state.

In the case of (3), the configuration values indicated in the configuration file45updated in the mobile PC2can be immediately provided to the wearable device3in connection.

In the case of (4), the configuration values indicated in the configuration file45can be immediately provided to the wearable device3newly connected to the mobile PC2in operation.

In the case of (5), the configuration values indicated in the configuration file45can be immediately provided to the wearable device3newly connected to the mobile PC2in a sleep or a suspend state after the mobile PC2returns from that state.

Furthermore, in the cases of (1), (4), and (5), a new wearable device3which has not been connected to the mobile PC2, or a second wearable device3which is different from a first wearable device3connected immediately before the connection of the second wearable device3may be connected to the mobile PC2. In each of the new wearable device3and the second wearable device3, configuration values of initial condition or configuration values set in the connection to a different mobile PC2may be stored. The mobile PC2can provide the configuration values, which are indicated in the configuration file45, to such wearable devices3.

The configuration file45may be a file to be used for the configurations of a different wearable device3which had been connected before. Thus, the mobile PC2uses the configuration file45stored in the mobile PC2such that wearable devices3to be connected to the mobile PC2are operated in the same configurations. Since a user does not perform an operation for configurations of the wearable device3at each time when the wearable device3is connected, a workload by the user to set the configurations can be reduced.

Specifically, the configuration control module43uses the configuration file45including the configurations ofFIG. 9to perform the configurations of the wearable device3. That is, the mobile PC2is operated such that the configuration values indicated in the configuration file45are provided to the configuration values stored in the wearable device3. For example, the configuration control module43sends signals indicative of each configuration value indicated in the configuration file45to the wearable device3connected thereto. The wearable device3receives the signals sent from the configuration control module43, and updates the corresponding configuration value stored in the wearable device3with the configuration value indicated by the signals.

A certain wearable device3A may be always connected to the mobile PC2, or any one of wearable devices3A,3B, and3C may be connected to the mobile PC2at each occasion. The configuration control module43can provide the configuration values, which are indicated in the configuration file45, to the wearable device3A,3B, or3C connected to the mobile PC2.

Furthermore, the mobile PC2may be shared by multiple users. In that case, an individual configuration file45is created in the mobile PC2for each user account. Thus, in the mobile PC2, configuration files45associated with user accounts, respectively, may be created.

The configuration control module43uses a configuration file45associated with a user account of a user currently using the mobile PC2to provide the configuration values, which are indicated in the configuration file45, to the wearable device3connected to the mobile PC2.

For example, when a first user uses the mobile PC2and a first wearable device3A is connected to the mobile PC2, the configuration control module43provides the configuration values, which are included in a first configuration file45associated with the first user, to the first wearable device3A. When the first user uses the mobile PC2and a second wearable device3B is connected to the mobile PC2, the configuration control module43provides the configuration values, which are included in the first configuration file45, to the second wearable device3B.

Furthermore, when a second user uses the mobile PC2and the first wearable device3A is connected to the mobile PC2, the configuration control module43provides the configuration values, which are included in a second configuration file45associated with the second user, to the first wearable device3A. When the second user uses the mobile PC2and the second wearable device3B is connected to the mobile PC2, the configuration control module43provides the configuration values, which are included in the second configuration file45, to the second wearable device3B.

As above, whichever wearable device of the wearable devices3A,3B, and3C is connected to the mobile PC2, each user can use the connected wearable device in the configurations customized for the user.

FIG. 10shows an example of a screen image51displayed on the display6by the first configuration utility308C. The screen image51is displayed as, for example, a window with GUI on the screen of the display6. The screen image51includes a first area510in which targets of the configurations are shown and a second area520in which configuration values related to one of the targets are shown.

A first area510includes a home button511and buttons510to518. The home button511is used for returning to the home screen. The buttons510to518indicate targets of the configurations, respectively. The targets of the configurations may include the components of the mobile PC2in addition to the components of the wearable device3. In the example ofFIG. 10, a “sign-in assist” button512and a “cursor button” button513indicate components of the mobile PC2, and other buttons514to518indicate components of the wearable device3.

GUI depicted in the second area520is switched in response to an operation to select one of the buttons512to518(for example, click operation using the pointing device8). The GUI is used to edit the configuration values related to the target indicated by one of the buttons512to518selected by the user. For example, when the “wearable device display” button514is selected, as shown inFIG. 10, objects to edit four configuration values related to the display124is depicted in the second area520.

The four configuration values related to the display124include, for example, brightness auto-adjustment, brightness, orientation auto-adjustment, and orientation. The following objects are shown in the second area520such that the user can edit the four configuration values.

(1-2) Radio button522to turn on the brightness auto-adjustment function and radio button523to turn off the brightness auto-adjustment function (either the radio button522or the radio button523is in a selected state at a time)

(2-2) Input area532to input a value of the brightness (a text indicative of a range of possible configuration values may be depicted in the proximity)

(2-3) Button534to increase the value shown in the input area532and button535to decrease the value shown in the input area532

(3-2) Radio button542to turn on the orientation auto-adjustment function and radio button543to turn off the orientation auto-adjustment function

(4-2) Radio button552to set the orientation to right and radio button553to set the orientation to left

Through the operation using the keyboard7and the pointing device8on the screen image51, a user can select one of the buttons512to518in the first area510corresponding to the target of configurations to be edited, and can edit the configuration values related to the selected target in the second area520.

Upon changing of a certain configuration value, for example, the first configuration utility308C requests the update control module41in the configuration service308B to change the value. Alternatively, when a button to request update (which is not shown) has been selected or the first configuration utility308C ends, the first configuration utility308C may request the update control module41to change one or more configuration values.

FIG. 11shows an example of a screen image61displayed on the display124of the wearable device3by the second configuration utility308D.

The screen image61includes buttons611to617that indicate targets of configurations, respectively. The targets of configurations may include the components of the mobile PC2in addition to the components of the wearable device3. In the example ofFIG. 11, a “wireless LAN” button611and a “cursor button” button612indicate the components of the mobile PC2, and the other buttons613to617indicate the components of the wearable device3.

In response to operations for selecting one of the buttons611to617(for example, selection operations using the cursor button202, the first to fourth buttons102,104,106, and108, and/or the touchpad110), the screen image61is changed to a next screen image. The next screen image includes the same objects as in the second area520ofFIG. 10, for example, and thus, the configuration values related to a target corresponding to one of the buttons611to617selected by the user can be edited.

Thus, by the operation using the cursor button202or the like on the screen image61, a user can select one of the buttons611to617indicative of a target of configurations to be edited, and can edit the configuration values related to the selected target in the next screen image.

As described above, the screen image61may be displayed on the display124of the wearable device3. Thus, the number of objects such as buttons611to617in the screen image61is less than the number of objects in the screen image51displayed on the display6shown inFIG. 10such that the objects in the screen image61can be easily selected by the cursor buttons202alone. That is, in the screen image61displayed on the display124of the wearable device3, the objects to be included at once are narrowed down than the objects in the screen image51displayed on the display6. Furthermore, the objects such as buttons611to617in the screen image61may be arranged to be intuitionally selected by the user using the cursor buttons202a,202b,202c, and202dindicating the vertical and horizontal directions (for example, the buttons611to617are aligned in the vertical direction or in the horizontal direction). Thus, the user can easily perform the operation using the cursor buttons202and the like on the screen image61.

Upon changing of a certain configuration value, for example, the second configuration utility308D requests the update control module41in the configuration service308B to change the value. Alternatively, when a button to request update (which is not shown) has been selected, or when the second configuration utility308D ends, the second configuration utility308D may request the update control module41to change one or more configuration values.

With reference to the flowchart ofFIG. 12, an example of the procedure of a configuration process executed by the mobile PC2will be explained. The configuration process is started in response to the boot or reboot of the mobile PC2.

Upon boot or reboot, the mobile PC2starts the configuration service308B (step S101). The configuration service308B includes a function to provide the configuration values, which are indicated in the configuration file45, to the wearable device3connected thereto, and a function to process various requests by the first configuration utility308C, the second configuration utility308D, and the application program308E.

Then, the mobile PC2determines whether the wearable device3is connected to the mobile PC2(step S102). When the wearable device3is connected to the mobile PC2(YES in step S102), the mobile PC2provides the configuration values, which are indicated in the configuration file45, to the wearable device3(step S103). Specifically, the mobile PC2reads the configuration file45stored in the storage device330or the like, and sends signals corresponding to the configuration values indicated in the read configuration file45to the wearable device3. The wearable device3receives the signals, and changes the configuration values stored in the wearable device3in accordance with the received signals.

On the other hand, when the wearable device3is not connected to the mobile PC2(NO in step S102), step S103is skipped.

Then, the mobile PC2determines whether the acquisition of the configuration values is requested (step S104). For example, the first configuration utility308C, the second configuration utility308D, or the application program308D requests the acquisition of the configuration values at the time of start. When the acquisition of the configuration values is requested (YES in step S104), the mobile PC2reads the configuration file45in accordance with the request, and provides the configuration values indicated in the read configuration file45(step S105). When the configuration file45has already been read in step S103, the configuration values therein may be provided.

When the acquisition of the configuration value is not requested (NO in step S104), step S105is skipped.

Then, the mobile PC2determines whether a change of one or more of the configuration values is requested (step S106). For example, the first configuration utility308C, the second configuration utility308D, or the application program308D requests the change of one or more of the configuration values. For example, the change of one or more of the configuration values is requested in response to a user operation on the first configuration utility308C or the second configuration utility308D. Alternatively, the change of one or more of the configuration values is requested by the application program308E. The request includes, for example, information to specify one or more configuration values to be changed (for example, “target” and “parameter” shown inFIG. 9) and one or more values to be newly set as the one or more configuration values.

When the change of one or more of the configuration values is requested (YES in step S106), the mobile PC2updates the configuration file45in accordance with the request (step S107). Then, the mobile PC2determines whether the wearable device3is connected to the mobile PC2(step S108). When the wearable device3is connected to the mobile PC2(YES in step S108), the mobile PC2provides the configuration values, which are indicated in the updated configuration file45, to the wearable device3(step S109), and the process returns to step S104.

On the other hand, when the wearable device3is not connected to the mobile PC2(NO in step S108), step S109is skipped and the process returns to step S104.

Furthermore, when the change of one or more of the configuration values is not requested (NO in step S106), the mobile PC2determines whether the mobile PC2newly detects that the wearable device3is connected thereto (step S110). The mobile PC2can detect that the wearable device3is newly connected to the mobile PC2after the mobile PC2determines that the wearable device3is not connected in step S102or step S108, for example. When the connection of the wearable device3is newly detected (YES in step S110), the mobile PC2provides the configuration values, which are indicated in the configuration file45, to the wearable device3(step S111), and the process returns to step S104. Thus, in response to newly detecting the connection of the wearable device3, the configuration values can be provided to the wearable device3that was not connected to the mobile PC2when booting or rebooting of the mobile PC2or updating the configuration file45.

On the other hand, when the connection of the wearable device3is not detected (NO in step S110), step S111is skipped and the process returns to step S104.

As above, the process from step S104to step S111is repeated during the execution of configuration service308B.

Through the above process, the mobile PC2can manage the configuration file45, and can provide the configuration values, which are indicated in the configuration file45, to the wearable device3connected to the mobile PC2. Note that, the above-described configuration process may be started when the mobile PC2returns from the sleep or suspend state.

As explained above, in the present embodiment, the configurations of the wearable device3can be facilitated. Any one of the wearable devices3wearable by a user can be connected to the mobile PC2(specifically, USB Type-C receptacle207). The update control module41updates the configuration file45for configurations of the wearable devices3. The configuration control module43provides, when the first wearable device3A of the wearable devices3is connected to the mobile PC2, the configuration values, which are included in the configuration file45, to the first wearable device3A. The configuration control module43provides, when the second wearable device3B of the wearable devices3is connected to the mobile PC2, the configuration values to the second wearable device3B.

Thus, a user can easily use the wearable devices3A and3B connected to the mobile PC2with the same configurations without performing complicated operations for configurations in each wearable device.

Each of various functions described in the embodiment may be realized by a circuit (e.g., processing circuit). An exemplary processing circuit may be a programmed processor such as a central processing unit (CPU). The processor executes computer programs (instructions) stored in a memory thereby perform the described functions. The processor may be a microprocessor including an electric circuit. An exemplary processing circuit may be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a microcontroller, a controller, or other electric circuit components. The components other than the CPU described according to the embodiment may be realized in a processing circuit.

Furthermore, various processes of the embodiment can be realized by executing a computer programs. Thus, the same advantages obtained by the embodiment can be achieved by installing the computer program into a computer via a computer readable storage medium storing the computer program.