Mobile device

Abstract

To determine a mobile device to connect from additional information in performing pairing connection to a host terminal.SOLUTION: A mobile device comprises connection means that wirelessly connects to a host terminal 300, and status acquisition means 110 that acquires the state of the device, and has state information addition means 140 that adds status information corresponding to the state of the device acquired by the status acquisition means 110, to identification information used for the wireless connection by the connection means. The mobile device can execute an advertisement mode for broadcasting advertisement data for executing the wireless connection. The identification information is character information included in the advertisement data. The state information addition means 140 preferably adds a specific identification code indicating the status information behind the character information.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a mobile device that wirelessly connects to an upper terminal.

Background Art

[0002] There are various connection forms in a mobile device that wirelessly connects to an upper terminal. As an example, once a connection is established, there is Bluetooth (registered trademark) Low Energy (hereinafter, BLE) that automatically connects to the upper terminal and operates thereafter. When pairing and connecting any one of a plurality of mobile devices to an upper terminal (for example, a smartphone), it is necessary to select a device name in the advertising mode on the screen of the upper terminal side.

[0003] Individual mobile devices display identification information for pairing on the screen of the upper terminal. However, it is difficult to accurately identify a mobile device by checking the identification information on the screen of the upper terminal, which is inconvenient when pairing.

[0004] In such a system, for example, as in the technology described in Patent Document 1, a plurality of mobile devices each receive an advertising packet from another device, and the upper terminal identifies and pairs the mobile devices using the event state of each mobile device (for example, a touch event using other short-range wireless communication) as a trigger.

[0005] Also, for example, there is Patent Document 2 in which an acceleration sensor is provided in a mobile device, and the acceleration of the mobile device can be used to execute pairing by recording information on the movement of the mobile device using a continuous reading function of acceleration information.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0007] However, in the case of the device described in Patent Document 1, a control function for identifying and pairing a mobile device on the upper terminal side triggered by an event state is required. Further, in the case of the device described in Patent Document 2, settings and control functions for executing pairing using acceleration are required.

Means for Solving the Problems

[0008] In view of the above, the mobile device according to the present invention comprises connection means for wirelessly connecting to an upper terminal, status acquisition means for acquiring the status of the device, and is characterized by having status information addition means for adding status information corresponding to the status of the device acquired by the status acquisition means to the identification information used for the wireless connection by the connection means.

Advantages of the Invention

[0009] According to the present invention, when there are a plurality of mobile devices, the mobile device to be connected can be easily determined from the status information.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Embodiments for Carrying Out the Invention

[0011] [Embodiment 1] Hereinafter, Embodiment 1 of the present invention will be described in detail with reference to schematic diagrams, system configuration diagrams, and sequence diagrams. Note that the present invention can also be applied to other devices as long as an operation for changing the status of the mobile device during pairing can be externally executed.

[0012] FIG. 1 is a schematic diagram showing the overall configuration of a mobile device and a host terminal. FIG. 1 shows, as an example, a situation where two types of mobile devices 11 and 12, and mobile devices 21 and 22 can be connected to a host terminal 31 via Bluetooth as a peripheral. When each mobile device is set to the advertising mode, it broadcasts advertising data. On the screen of the host terminal 31 (central), a list of connectable mobile devices is displayed based on the scanned advertising data. The host terminal 31 performs pairing by selecting the connection ID of the mobile device to be connected from the connection IDs (identification information) of each mobile device displayed on the list screen of the host terminal 31. In the following description, the mobile device may be described as mobile device 100 and the host terminal as host terminal 300.

[0013] FIG. 2 is a system configuration diagram showing the overall configuration of the mobile device 100 according to Embodiment 1 of the present invention. As shown in FIG. 2, the mobile device according to Embodiment 1 of the present invention includes a mobile device status acquisition unit 110, a charging information acquisition unit 120 that acquires the charging state of the built-in battery, a sensing data acquisition unit 130 that acquires sensing data such as pulse wave, skin potential, motion, and body temperature information, a status information addition unit 140, and a radio wave intensity information acquisition unit 150. Note that the information acquired by the charging information acquisition unit 120, the sensing data acquisition unit 130, and the radio wave intensity information acquisition unit 150 is input to the mobile device status acquisition unit 110 to acquire the status (status information) of the mobile device. Further, it has an attribute data storage means (not shown) in which attribute information such as Company ID, UUID, and device name used in BLE is stored as various attribute data 160 of the mobile device.

[0014] In addition, the upper terminal 300 connected to the mobile device 100 includes, as a main configuration according to the present invention, a wireless communication means (not shown) capable of wireless communication with the mobile device 100, and a connectable ID display means 310 on which the identification code of the device connectable by wireless communication is displayed.

[0015] The mobile device status acquisition unit 110 determines the mobile device status based on the charging state obtained from the charging information acquisition unit 120, any one of the pulse wave, skin potential, motion, and body temperature information obtained from the sensing data acquisition unit 130, and the radio wave intensity information obtained from the radio wave intensity information acquisition unit 150. Note that this radio wave intensity information is the radio wave intensity when the mobile device is connected to an external device via a wireless LAN or the like.

[0016] The status information addition unit 140 acquires reference data of the connection ID as unique information of the mobile device obtained from the various attribute data 160 of the mobile device, and adds a specific identification code to the connection ID based on the status information of the mobile device obtained from the mobile device status acquisition unit 110.

[0017] The mobile device 100 sets a connection ID with a specific identification code as the connection ID to be included in the advertisement data during pairing. When the upper terminal 300 detects the mobile device 100 as being in a pairable state, a connection ID with a specific identification code reflecting the status of the mobile device is displayed on the screen, making it possible to easily pair with the mobile device in the intended status state. The method of attaching the specific identification code to the connection ID will be described in detail later.

[0018] FIG. 3 is an explanatory diagram showing the state of the connection ID displayed on the upper terminal 300 during pairing. Four mobile devices are displayed. In order from the top, for the mobile device 11, it is acquired by the charging information acquisition means 120 that the built-in battery is being charged, and as a specific identification code indicating this, a connection ID with an emoji indicating the battery added is displayed on the upper terminal 31 side.

[0019] Here, FIG. 4 shows an example of advertisement data (advertisement packet). In this advertisement data, as shown in FIG. 4, as a whole, it consists of "Preamble", "Access Address", "Protocol Data Unit (PDU)", and "CRC". Among them, "Protocol Data Unit (PDU)" further consists of "Header", "Advertiser’s Address", and "Advertiser’s Data". "Advertiser’s Data" can include a desired number n of "AD Structures" as shown below, and the rest is padded with "0".

[0020] This "AD Structure" further consists of "Length" indicating the data length, "AD type" indicating the data type, and "AD Data" representing the content of the data. The connection ID can be defined as a "complete local name" by setting the "AD type" among these to "0x09". In this embodiment, after the data (character information) indicating the character string set as the reference data of the connection ID, it is realized by adding the data (specific identification code) indicating the status information of the mobile device acquired by the mobile device status acquisition means 110. Regarding the topmost mobile device 11 in FIG. 3, an emoji indicating the battery is added as the specific identification code, and in the mobile device 21 and the like described later, alphanumeric characters (such as "A!!!") are added. In the "complete local name" of "0x09", it is possible to describe using UTF-8 as the character code, and in these examples, they are described with numerical values corresponding to those emojis and character strings.

[0021] Regarding how to add a specific identification code to the connection ID, in FIG. 3, as an example corresponding to the mobile device 11, an example is shown where an emoji indicating a battery is added after the connection ID "Camera_001". On the other hand, as an example corresponding to the mobile device 12, an example is shown where an emoji as if the device vibrated is added before the connection ID "Camera_002". Thus, when adding a specific identification code to the connection ID, it may be added either before or after it. In particular, when adding the specific identification code after the connection ID, the visibility of multiple mobile devices with connection IDs having the same string on the screen of the upper terminal 31 is improved. On the other hand, when adding the specific identification code before the connection ID, the visibility of the mobile device corresponding to the desired status state (for example, when the motion sensor is operating) is improved. Thus, it is possible to add the specific identification code to either the front or the back of the connection ID according to the purpose, and it may also be switched whether to add it before or after the connection ID according to the type of the specific identification code. For example, a specific identification code indicating the charging status of the built-in battery may be added before the connection ID, while other specific identification codes may be added after the connection ID. Also, it may be switched whether to add the specific identification code before or after the connection ID according to the fact that the mobile device is in a specific mode or in a certain device state.

[0022] Furthermore, when the connection ID is composed of a combination of two or more different types of character strings such as a character string + serial number like "Camera_001" shown in the mobile device 11, etc., a specific identification code may be added between them. For example, "A!!!" as a specific identification code may be added like "Camera_A!!!_001", etc. Also, UTF-8 is just an example, and it may be described using other character codes.

[0023] Also, by setting "AD type" to "0x0A", it can be defined as "Tx Power Level", and in this embodiment, the transmission power can be notified to the upper terminal 300. By combining it with RSSI (Received Signal Strength Indicator), the distance between the mobile device 100 and the upper terminal 300 can also be measured using the so-called Friis transmission formula.

[0024] Furthermore, by setting "AD type" to "0xFF", it can be defined as "Manufacturer Specific Data". In this embodiment, it is possible to add attachment information to the data (specific identification code) indicating the status information of the mobile device acquired by the mobile device status acquisition means 110 together with the enterprise identifier code. Using the attachment information, it becomes possible to change the display mode of the characters displayed on the upper terminal 300.

[0025] Next, for the mobile device 12, it is sensed by the sensing data acquisition means 130 that the motion sensor is in an operating state, and as a specific identification code indicating this, a connection ID with an emoji added as if the device has vibrated is displayed on the upper terminal 31 side. For the mobile device 21, it is acquired by the radio wave intensity information acquisition means 150 that the radio wave intensity is high in the wireless connection with a device different from the upper terminal 31, and as a specific identification code indicating this, a connection ID with the character string "A!!!" added is displayed on the upper terminal 31 side. This "A" is an example of an identification code indicating a different device, "!" indicates the radio wave intensity by its number, and "!!!" indicates that the radio wave intensity is strong. The mobile device 22 is a mobile device having a card reader, and it is acquired by the sensing data acquisition means 130 that a card is inserted into the card reader and the reading operation is in progress, and as a specific identification code indicating this, a connection ID with the character string "B!" added is displayed on the upper terminal 31 side. This "B" is an example of a character string indicating the type of the card reader possessed by the mobile device, and "!" indicates that the reader is operating. Note that these character strings and the like are examples, and it is preferably set appropriately to a character string that can be understood what it is when looking at the device name.

[0026] Regarding the connection ID including the specific identification codes of "A!!!" and "B!" displayed on the upper-level terminal 31 side, in order to make it easier to determine the device to be connected, the application operating on the upper-level terminal 31 may be set to change the display colors of the character strings of "A!!!" and "B!" according to the settings predefined for the received data. Furthermore, the display density of the character strings of "A!!!" and "B!" may be changed to be darker when strong and lighter when weak based on the radio wave intensity and transmission power. Note that these display modes and the like are just examples, and it is preferable to appropriately set them to a display mode such that the state can be understood when seeing the display of the device name.

[0027] In this way, in the present embodiment, status information indicating the mobile device status is added to the end of the connection ID. When the status in the mobile device 100 changes, it is automatically reflected in the connection ID of the advertisement data, and the information of the connection ID displayed on the upper-level terminal 31 side is updated.

[0028] When pairing from the upper-level terminal 300 using the connection ID in the advertisement data that is dynamically changed as the status state of the mobile device 100 changes, for example, even if the application operating on the upper-level terminal 300 side changes the information of the connection ID of the mobile device 100 to its own, as long as the connection IDs before and after the change are associated and stored, it is possible to add the character string (specific identification code) of the dynamically changing part indicating the status information added to the connection ID before the change to the connection ID after the change and display it on the screen.

[0029] Also, when pairing using the connection ID that includes status information and dynamically changes, communication is performed between the connected mobile device 100 and the upper-level terminal 300, and the information of the connection ID of the fixed part can be automatically obtained. Thereby, even when the connection ID is edited on the upper-level terminal 300 side, it can be made to correspond to the mobile device 100.

[0030] Next, while referring to FIGS. 2 and 5, a series of processing flows during pairing will be described. In FIG. 5, the mobile device side is described as peripheral and the upper terminal side as central, but two or more peripherals can execute. Also, in the following description, as a sensing data acquisition means, an embodiment having a pulse wave sensor for acquiring the pulse wave of a person wearing the mobile device, a skin potential sensor for detecting the skin potential, a body temperature sensor for acquiring the body temperature, and a motion sensor for detecting the movement of the mobile device will be described as an example.

[0031] First, at step S161 during pairing, a connection ID is created from various attribute data 160 of the mobile device. The connection ID is represented as an arbitrary character string as BLE advertisement data.

[0032] Next, the processing after step S121 is executed. In each process of information acquisition from step S121 to step S151, it is preferable to be parallel to the pairing process of the mobile device 100 and for each process to be executed in parallel.

[0033] At step S121, charging information of the mobile device 100 is acquired. When the charging information acquisition means 120, regardless of contact type or non-contact type, places the mobile device 100 on a charging stand such as a cradle for charging and detects that it is being charged by a known method such as detecting the voltage of the charging terminal, it notifies the mobile device status acquisition means 110 of the charging state.

[0034] At step S131, pulse wave information in the mobile device 100 is acquired. If the detection result by the pulse wave sensor is almost 0, the sensing data acquisition means 130 notifies the mobile device status acquisition means 110 that the pulse wave sensor surface is not in contact with the body. When the pulse wave is correctly detected by the pulse wave sensor, it notifies the mobile device status acquisition means 110 that the detection is in progress.

[0035] In step S132, skin potential information in the mobile device 100 is acquired. If the detection result by the skin potential sensor is approximately 0, the sensing data acquisition means 130 notifies the mobile device status acquisition means 110 that the skin potential sensor surface is not in contact with the body. If the skin potential is correctly detected by the skin potential sensor, it notifies the mobile device status acquisition means 110 that the detection is in progress.

[0036] In step S133, motion sensor information in the mobile device 100 is acquired. As the motion sensor, an acceleration sensor or an angular velocity sensor (gyro sensor) can be used. If the motion sensor has a value equal to or greater than a certain value, the sensing data acquisition means 130 notifies the mobile device status acquisition means 110 that the mobile device body is being moved or operated regardless of whether the device is worn or not.

[0037] In step S134, body temperature information in the mobile device 100 is acquired. The sensing data acquisition means 130 compares the detection result by the body temperature sensor with the outside air temperature. If the difference is approximately 0, it notifies the mobile device status acquisition means 110 that the body temperature sensor surface is not in contact with the body. If the body temperature is correctly detected by the body temperature sensor, it notifies the mobile device status acquisition means 110 that the detection is in progress. It is preferable to have a temperature sensor for acquiring the outside air temperature, but it is not limited to this, and outside air temperature data may be input from the outside. Also, various methods such as comparing the detection results by the body temperature sensor in time series and switching the attachment / detachment flag when a change occurs can be used to detect attachment / detachment.

[0038] Next, when the mobile device 100 is wirelessly connected to a device different from the upper terminal 300, the radio wave intensity is measured (step S151). The acquired radio wave intensity is notified to the mobile device status acquisition means 110. At that time, it is preferable to also notify the identification code such as the device name of the connected device (such as a wireless router).

[0039] In step S141, based on the status information obtained in steps S121 to S151, the status information addition means 140 generates and updates additional information for the connection ID, and any specific identification code indicating the charging status of the mobile device, the status of each sensor, and the radio wave intensity between the mobile device and a device different from the upper terminal is added to the connection ID. Basically, it is preferably determined that the condition for being added to the connection ID is satisfied with an active state such as during detection or operation, but this is not limited thereto.

[0040] At this time, a priority is set for each status information. When there are multiple pieces of status information that satisfy the condition for being added to the connection ID, they are added to the connection ID in order according to the priority, or only one or more pieces of status information with a higher priority may be added. For example, information indicating that detection is in progress in sensing data may indicate that multiple mobile devices are in the detection state when multiple people are nearby. Therefore, by increasing the priorities of the motion sensor and the charging information, it becomes possible for the user of the mobile device to intentionally change the status without detaching the mobile device and switch the connection ID in real time, which is preferable. In particular, when the status information is configured to be added to the connection ID as satisfying the condition when sensing data is being detected, by setting the priority of the motion sensor as the highest priority, even in a state where charging is in progress or other sensors are in the detection state (for example, multiple units), by causing the desired operation to be performed on the desired mobile device 100, the operation state is reflected in the connection ID, so that it becomes possible to easily identify the mobile device 100 to be connected. In this way, by preferentially adding the fact that detection is in progress by the sensing data acquisition means 130, which makes it easy for the user to intentionally change the status, it becomes possible to more easily identify the mobile device 100.

[0041] Also, when priority is set, the advertising interval described later may be changed according to the data acquisition interval in the sensing data acquisition means 130 corresponding to the status information added to the connection ID.

[0042] Alternatively, when indicating that detection is in progress with a plurality of sensing data, it may be changed so that the priority of the one showing the most sensitive detection result becomes higher.

[0043] The status information adding means 140 broadcasts advertising data including a connection ID with a specific identification code added thereto for the central including the upper terminal 300 (step S142).

[0044] The connectable ID display means 310 in the upper terminal 300 acquires the connection ID with the specific identification code added from the advertising data received in step S301, and displays it in the list of pairable devices on the screen of the upper terminal 300 (step S302).

[0045] As shown in FIG. 3, pairing is performed using the connection ID displayed in the list of pairable devices (step S303), and after the pairing is completed, communication suitable for the mobile device designated by the upper terminal 31 can be started.

[0046] Also, in step S303, when it is determined that the status information previously specified by the upper terminal 300 is included when acquiring the connection ID with the specific identification code added from the advertising data received in step S301, automatic pairing with the corresponding mobile device may be executed. In this case, on the upper terminal 300 side, an application with such a setting is executed, and it is preferable to display the list of pairable devices by that application.

[0047] Note that the processing on the upper terminal 300 side may be realized as a function of the OS operating on the upper terminal, or may be realized as a function of an application different from the OS described above.

[0048] Summarizing the embodiment described above, the specific identification code in step S141 is a character string recognized as the format of the connection ID. For example, it can be a symbol, character string, emoji, etc. that allows an operator to immediately understand the charging status at a glance, a symbol, emoji, etc. that allows an operator to immediately understand whether each built-in sensor is worn on the body, and a numerical value, symbol, etc. indicating the radio wave intensity between the mobile information terminal and a device different from the upper terminal.

[0049] The specific identification code adds the charging information in step S121 and the motion acquisition information in step S133 to the connection ID with the highest priority respectively. Thereby, it becomes possible to perform pairing processing by referring to the specific identification code set based on event conditions such as installing and charging on a charging cradle, shaking a mobile device in a specific direction, and moving it at a constant speed.

[0050] Furthermore, when the specific identification code acquires the pulse wave information in step S131, the skin potential information in step S132, and the body temperature information in step S134, only the information with the highest value among any of the information is added to the connection ID. This is for performing pairing processing based on the sensor that was intentionally adhered to the sensor surface to generate event conditions, but this mode is not limited thereto.

[0051] As described above, in Embodiment 1 of the mobile device shown in FIG. 2, when performing BLE pairing, the status information of the mobile device capable of communicating via BLE can be added to the connection ID displayed in the list of pairable devices to represent the device state. Thereby, it becomes possible to easily determine or easily connect the mobile device that wants to pair with the central device from among a large number of peripherals on the screen.

[0052] Therefore, according to Embodiment 1 of the mobile device shown in FIG. 3, when there are multiple products without a UI on the mobile device side and products using BLE, the possibility of connection errors on the central side during pairing can be suppressed. Also, when the structure on the mobile device side is very small and the connection information described on the main body is in a very difficult-to-read form such as engraving, the mobile device can intentionally change the status state, and based on the changed connection ID etc., it is possible to easily confirm the mobile device to be connected.

[0053] In addition, the present invention is not limited to the above-described embodiments, and various modifications are possible. For example, when obtaining a connection ID with a specific identification code added from the advertisement data received in step S301, the RSSI of the advertisement data is obtained, and by making an electronic sound with a different frequency or volume based on its strength, it is also possible to know the displacement of the distance of the device to be paired.

[0054] Also, as status information acquired by the mobile device status acquisition means 110, it is also possible to acquire the device name of the upper terminal connected last time, the connection time (disconnection time), etc. Similarly in this case, it becomes clear which upper terminal the mobile device was connected to and when, by the connection ID, and the selectivity is improved.

[0055] In the above-described embodiments, the status information is added as it is to the "complete local name" column where the "AD type" in the "AD Structure" of the advertisement data is defined as "0x09" so as to be reflected in the device name, but it is not limited to this. For example, as the "AD type" in the "AD Structure", "128-bit Service UUIDs" of "0x06" etc. may be used, and the status information may be described there. In this case, since it is necessary to extract the status information from "0x06" on the upper terminal side and associate it with the connection ID, it is preferable to execute the scan of the advertisement data and the display of the connection ID in the application executed on the upper terminal.

[0056] Also, the advertisement interval is appropriately set between 20 milliseconds and 10.24 seconds. In the present embodiment, it is preferable that the advertisement interval is set to an interval corresponding to the data acquisition interval of the sensing data acquisition means. For example, when the detection interval of the pulse wave sensor is set to acquire data at 1-second intervals, the advertisement interval is preferably set to 1 second or more. This is just an example, and an advertisement interval longer than the data acquisition interval of the sensing data acquisition means may be set. In this way, by configuring the advertisement interval to be longer than or equal to the data acquisition interval of the sensing data acquisition means and yet short (for example, longer than or equal to the data acquisition interval and up to twice that), the status information can be reliably reflected in the connection ID without impairing connectivity. Also, when reducing power consumption by lengthening the advertisement interval, it becomes possible to set a time when the status information is likely to be reflected in the connection ID.

[0057] Also, the status information may be changed in the connection ID according to the type of "Advertisement Type" included in the advertisement data. For example, only when the "Advertisement Type" is "Connectable Undirected" (connection possible and scanable), it may be configured to acquire data via the sensing data acquisition means and add it to the connection ID. In this case, since the sensing data is acquired only when the mobile device is connection possible and scanable (= connection possible), power consumption can be reduced compared to the case where the sensing data is acquired even when it is not connectable.

[0058] The present invention is not limited to the above-described embodiments, and various modifications can be applied without departing from the gist of the present invention.

[0059] Also, in the above-described embodiment, in the part where it was described that the application executed on the upper-level terminal is to be executed, at least a part of the functions may be configured to be realized by the OS of the upper-level terminal.

[0060] Note that the state (status information) of the mobile device described in the above embodiment is an example, and as long as status information is used to set conditions (additional conditions) added to the connection ID for each, it is acceptable. For example, in a mobile device having a display unit, assuming that the state displayed on the display unit satisfies the additional condition, a character string such as "displaying" or a specific identification code corresponding to the status may be added to the connection ID. Alternatively, assuming that the state of performing a specific display satisfies the additional condition, a character string such as "XXX displaying" or a specific identification code corresponding to the status may be added to the connection ID. Also, in a mobile device having a hardware key such as a power button or a soft key, assuming that the state where the key is pressed satisfies the additional condition, a character string such as "key pressed" or a specific identification code corresponding to the status may be added to the connection ID.

[0061] Also, as another example of the state (status information) of the mobile device, the case where the mobile device can be connected to a specific cloud server via a wireless LAN or the like will be described. In this case, the availability of cloud services available on the connected cloud server can be set as the state of the device. For example, for a predetermined cloud service YYY, assuming that the additional condition is satisfied when the mobile device is in a state where it can use the cloud service due to an authenticated state or the like, a character string such as "YYY connected" or "YYY available" or a specific identification code corresponding to the status may be added to the connection ID.

[0062] Also, as another example or an additional example of the state of the mobile device, time information related to the mobile device may be used as status information. For example, the cumulative power-on time of the mobile device or the current power-on time may be used as status information. For example, when the power-on time is 10 hours, a string such as "ON state for 10 hours" or a specific identification code corresponding to the status state may be added to the connection ID.

[0063] In the above embodiment, an example was described in which a string "charging" indicating that the built-in battery is charging or a specific identification code corresponding to the status state is added to the connection ID as the status information of the mobile device. However, the remaining amount of the built-in battery may be further added as status information. For example, a specific identification code written together with the fact that it is charging, such as "charging 30%", can be used, or other modes may be used. Also, only the remaining amount of the built-in battery may be added as status information, and a specific identification code may be added, for example, as in "battery 80%".

[0064] Also, the status states described in the above-described embodiments and the like may be used in combination. For example, a plurality of status information such as "charging, vibrating, ON state for 1 hour" may be reflected in the connection ID as the status state.

[0065] Also, in each of the above embodiments, an example was described in which a specific identification code is added to the connection ID when it is determined that the condition for adding each status information to the connection ID is satisfied. However, the present invention is not limited to this, and the specific identification code to be added may be configured to be changed depending on whether or not a specific condition is determined to be satisfied for each status information. For example, during charging of the built-in battery, an emoji indicating that it is charging or a character string such as "charging" is added before the connection ID, and when it is not charging, an emoji representing a non-charging battery or a character string such as "non-charging" is added before the connection ID. This is particularly suitable when configured such that a specific identification code is added before the connection ID because the visibility is improved. However, it may also be added after the connection ID.

Explanation of Signs

[0066] 11, 12, 21, 22, 100 Mobile device 31, 300 Upper terminal 110 Mobile device status acquisition means 120 Charge information acquisition means 130 Sensing data acquisition means 140 Status information addition means 150 Radio field strength information acquisition means 310 Connectable ID display means

Claims

1. connection means for wirelessly connecting to a host terminal, status acquisition means for acquiring the status of the device, and a mobile device, characterized in that it has status information addition means for adding status information corresponding to the status of the device acquired by the status acquisition means to the identification information used for the wireless connection by the connection means.

2. The mobile device according to claim 1, characterized in that the identification information is a connection ID used for the wireless connection.

3. The wireless connection is a Bluetooth connection and can execute an advertising mode for broadcasting advertising data. The connection ID is character information included in the advertising data, and the status information addition means adds a specific identification code indicating the status information before and after the character information. The mobile device according to claim 2.

4. The mobile device according to claim 3, characterized in that the connection ID is character information defined as a local name in the advertising data.

5. The mobile device according to claim 1, characterized in that the status of the device is whether data is being acquired by a sensor included in the mobile device.

6. The mobile device according to claim 1, characterized in that the status of the device is the charging status of a battery included in the mobile device.

7. The mobile device according to claim 3, characterized in that the advertising interval for broadcasting the advertising data is set to a time equal to or longer than the acquisition interval for acquiring data by the sensor.

Images