Patent Description:
An electronic device may establish BT communication with an external electronic device by sequentially executing an inquiry process, a paging process, and a pairing process. In this case, the electronic device and the external electronic device may not have a history of previous BT communications. The electronic device may store information associated with the external electronic device (e.g., at least a part of a unique address of the external electronic device), obtained in the inquiry process, and may then establish BT communication with the external electronic device via the paging process and the pairing process using the information associated with the external electronic device.

The electronic device may share information about at least one first external electronic device (e.g., a BT address of the first external electronic device), which has a history of established BT communication with the electronic device, with a second external electronic device which does not have a history of established BT communication with the first external electronic device. In this case, the second external electronic device may establish BT communication with the first external electronic device without the inquiry process using the information about the first external electronic device transmitted from the electronic device.

<CIT> discloses a Bluetooth connection method, comprising: a first terminal sends a Bluetooth low energy (BLE) broadcast message, the BLE broadcast message comprising device information; a second terminal receives the BLE broadcast message, obtains the device information, matches the device information with pre-stored device information, and initiates, if the device information successfully matches the pre-stored device information, a classic Bluetooth connection request to the first terminal; and a classic Bluetooth connection is established between the first and second terminals.

There may be a case in which a first external electronic device may refuse a BT communication connection request from a second external electronic device whose address the first external electronic device does not know, i.e. when the first external electronic device and the second external electronic device have no previous BT communication history. In such a case, the second external electronic device cannot perform BT communication with the first external electronic device using information about the first external electronic device shared from another electronic device, e.g. the aforementioned electronic device. Instead, the second external electronic device may have to perform an inquiry process in order to receive a unique address of the first external electronic device from the first external electronic device, and only after this process may the second external electronic device establish BT communication with the first external electronic device. In this case, the time and load for establishing BT communication may increase, compared to the scenario when the second external electronic device uses the information about the first external electronic device shared from the electronic device.

In accordance with an aspect of the disclosure, an electronic device is provided. The electronic device may include a user interface, a communication circuitry configured to support Bluetooth (BT) communication and to store a first BT address, a processor operatively connected with the user interface and the communication circuitry, and a memory operatively connected with the processor. The memory may store instructions that, when executed, cause the processor to establish a communication connection with a first external electronic device based on the first BT address, using the communication circuitry, end the communication connection with the first external electronic device, receive a reconnection request based on the first BT address from the first external electronic device, after ending the communication connection, transmit a communication connection request to the first external electronic device based on a second BT address different from the first BT address, using the communication circuitry in response to the reconnection request, and store information about whether the first external electronic device accepts or declines the communication connection request in the memory.

Accordingly, an aspect of the disclosure is to provide a method for sharing Bluetooth (BT) communication information to configure BT communication information including information indicating whether it is able for an external electronic device to perform BT communication based on a BT address in which there is no history of establishing BT communication and an electronic device therefor.

Accordingly, an aspect of the disclosure is to provide a method for sharing Bluetooth (BT) communication information to configure BT communication. The communication information includes information indicating whether an external electronic device is able to perform BT communication based on a BT address of an electronic device for which there is no history of established BT communication. The invention corresponds to the disclosure of the first five steps of <FIG> and <FIG> and to the related text. The remaining of the description and the figures are not according to the invention and are presented for illustration and for understanding the invention but are not part of the invention.

<FIG> is a drawing illustrating a BT communication system according to an embodiment.

Referring to <FIG>, a BT communication system <NUM> according to an embodiment may include an electronic device <NUM> (e.g., the electronic device <NUM> of <FIG>), a first external electronic device <NUM> (e.g., the electronic device <NUM> of <FIG>), and a second external electronic device <NUM> (e.g., the electronic device <NUM> of <FIG>).

When there is no history of established BT communication with the first external electronic device <NUM>, the electronic device <NUM> may establish BT communication with the first external electronic device <NUM> through an inquiry process, a paging process, and a pairing process based on a first BT address. The electronic device <NUM> may store first information about the first external electronic device <NUM>, obtained in the inquiry process, in its memory and may then establish BT communication with the first external electronic device <NUM> in addition to the inquiry process. The first information about the first external electronic device <NUM> may include, for example, the BT address of the first external electronic device <NUM> and the name of the first external electronic device <NUM>. The first BT address may be a unique address of the electronic device <NUM> for BT communication. The BT address of the first external electronic device <NUM> may be a unique address of the first external electronic device <NUM> for BT communication.

According to an embodiment, after establishing the communication based on the first BT address with the first external electronic device <NUM>, the electronic device <NUM> may transmit a communication connection request to the first external electronic device <NUM> based on a second BT address different from the first BT address and may identify whether the first external electronic device <NUM> accepts or declines the communication connection request. The second BT address may be, for example, a BT address for which there is no history of established communication with the first external electronic device <NUM>. The electronic device <NUM> may identify that the first external electronic device <NUM> accepts or declines the communication connection request based on the second BT address and may store second information about the possibility that the first external electronic device <NUM> will accept the communication connection request (information about that the first external electronic device <NUM> accepts or declines the communication connection request) in the memory. For example, the electronic device <NUM> may associate and store the first information about the first external electronic device <NUM> (e.g., the Bluetooth address and/or the name) with the second information about the possibility that the first external electronic device <NUM> will accept the communication connection request in the memory. The second information about the possibility that the first external electronic device <NUM> will accept the communication connection request may include, for example, information indicating whether the first external electronic device <NUM> will accept or decline a request to establish communication for which there is no associated connection history. The second information may include, in another example, information indicating whether the first external electronic device <NUM> will accept or decline a communication connection request received from the electronic device <NUM> when the first external electronic device <NUM> is powered on (e.g., when the Bluetooth of the first external electronic device <NUM> is powered on).

According to an embodiment, the electronic device <NUM> may share (e.g., transmit) first information about at least one first external electronic device (e.g., the first external electronic device <NUM>) with the second external electronic device <NUM>. For example, the electronic device <NUM> may transmit the first information about the first external electronic device <NUM> and the second information about the probability whether the first external electronic device <NUM> will accept the connection request based on the BT address for which there is no connection history, the first information and the second information being associated with each other, to the second external electronic device <NUM>. According to an embodiment, the electronic device <NUM> may identify a probability that the first external electronic device <NUM> will accept the connection request based on the second BT address (identify that the first external electronic device <NUM> accepts or declines the connection request). When it is identified that the first external electronic device <NUM> will accept the connection request, the electronic device <NUM> may transmit the first information about the first external electronic device <NUM> and the second information to the second external electronic device <NUM>. According to another embodiment, when it is identified that the first external electronic device <NUM> will decline the connection request, the electronic device <NUM> may refrain from transmitting the first information about the first external electronic device <NUM> to the second external electronic device <NUM>. In an embodiment, when sharing the first information about the first external electronic device <NUM> with the second external electronic device <NUM>, the electronic device <NUM> may directly transmit the first information about the first external electronic device <NUM> to the second external electronic device <NUM> or may transmit the first information about the first external electronic device <NUM> to the second external electronic device <NUM> via another electronic device (e.g., an external server).

According to an embodiment, when receiving the first information about the first external electronic device <NUM> and the second information about the possibility that the first external electronic device <NUM> will accept the connection request based on the BT address for which there is no connection history from the electronic device <NUM>, the second external electronic device <NUM> may associate and provide the second information with the first information through a user interface. In an embodiment, the second external electronic device <NUM> may be, for example, a device configured to have the same user account as the electronic device <NUM>. The second external electronic device <NUM> may be, for another example, a device configured to have an account of a person related to the user of the electronic device <NUM> (e.g., a family account or a colleague account).

According to an embodiment, when identifying (e.g., receiving) an input associated with establishing BT communication between the second external electronic device <NUM> and the first external electronic device <NUM>, the second external electronic device <NUM> may transmit a communication connection request based on the BT address of the second external electronic device <NUM> to the first external electronic device <NUM> using the first information about the first external electronic device <NUM>. The first external electronic device <NUM> may accept the communication connection request of the second external electronic device <NUM>, and the second external electronic device <NUM> and the first external electronic device <NUM> may establish BT communication.

According to the above-mentioned embodiment, each of the electronic device <NUM>, the first external electronic device <NUM>, and the second external electronic device <NUM> may be an electronic device capable of performing BT communication and may be, for example, a portable communication device (e.g., smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, a home appliance, or an accessory device (e.g., BT earphones).

According to the above-mentioned embodiment, the electronic device <NUM> may configure BT communication information about the first external electronic device <NUM> capable of establishing BT communication based on an address for which there is no history of establishing BT communication and may share the configured BT communication information to the second external electronic device <NUM>. Alternatively, the electronic device <NUM> may configure BT communication information that identifies whether it is able to perform BT communication based on an address for which there is no history of establishing BT communication and may share the configured BT communication information to the second external electronic device <NUM>.

<FIG> is a block diagram illustrating a configuration of an electronic device according to an embodiment.

Referring to <FIG>, an electronic device <NUM> (e.g., an electronic device <NUM> of <FIG>) according to an embodiment may include a user interface <NUM> (e.g., the display device <NUM> of <FIG>), a communication circuitry <NUM> (e.g., the communication module <NUM> of <FIG>), a memory <NUM> (e.g., the memory <NUM> of <FIG>), and a processor <NUM> (e.g., the processor <NUM> of <FIG>). In an embodiment, the electronic device <NUM> may exclude some components or may further include an additional component. In an embodiment, some of the components of the electronic device <NUM> may be combined into one entity to perform functions of the components before the combination in the same manner.

According to an embodiment, the user interface <NUM> may include an input circuitry and a display. The input circuitry may include at least one of a touch sensor or a physical button. The display may include a display included in the electronic device <NUM> or a display included in another electronic device which communicates with the electronic device <NUM>. In this embodiment, which is an example, the user interface <NUM> is a touch screen display, i.e. a display combined with a touch sensor.

According to an embodiment, the communication circuitry <NUM> may include at least one communication circuitry configured to support BT communication. The communication circuitry <NUM> may be configured with a first BT address. For example, the communication circuitry <NUM> may include an integrated circuit for BT communication, and the integrated circuit may store the first BT address in its internal memory. The communication circuitry <NUM> may further include a second BT address different from the first BT address. The first BT address may be, for example, a unique address of the electronic device <NUM> for BT communication. The second BT address may be, for example, an address different from the unique address of the electronic device <NUM> for BT communication, and may be used for a plurality of electronic devices including the electronic device <NUM>. The second BT address may be determined, for example, when the electronic device <NUM> is manufactured, and may be stored in the communication circuitry <NUM>. Alternatively, the second BT address may be randomly set by the processor <NUM> or may be set by the processor <NUM> based on at least a part of the first BT address or information received from another electronic device (e.g., a device configured to have the same user account as the electronic device <NUM>). For example, the second BT address may be set based on a BT address of a device configured to have the same user account as the electronic device <NUM>. According to an embodiment, the second BT address may be stored in the memory <NUM>.

According to an embodiment, the memory <NUM> may store instructions, when executed, causing the processor <NUM> to establish a communication connection with a first external electronic device (e.g., the first external electronic device <NUM> of <FIG>) based on the first BT address using the communication circuitry <NUM>, end the communication connection with the first external electronic device <NUM>, receive a reconnection request based on the first BT address from the first external electronic device <NUM> after ending the communication connection, transmit a communication connection request to the first external electronic device <NUM> based on the second BT address different from the first BT address using the communication circuitry <NUM> in response to the reconnection request, and store second information about a probability that the first external electronic device <NUM> will accept or decline the communication connection request in the memory <NUM>. The memory <NUM> may store, for example, a command or data associated with at least one other component of the electronic device <NUM>. The memory <NUM> may be a volatile memory (e.g., a random access memory (RAM)), a non-volatile memory (e.g., a read only memory (ROM) or a flash memory), or a combination thereof.

The processor <NUM> may execute calculation or data processing about control and/or communication of at least one other component of the electronic device <NUM> using the instructions stored in the memory <NUM>. The processor <NUM> may include a microprocessor or any suitable type of processing circuitry, such as one or more general-purpose processors (e.g., ARM-based processors), a Digital Signal Processor (DSP), a Programmable Logic Device (PLD), an Application-Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), a Graphical Processing Unit (GPU), a video card controller, etc. In addition, it would be recognized that when a general purpose computer accesses code for implementing the processing shown herein, the execution of the code transforms the general purpose computer into a special purpose computer for executing the processing shown herein. Certain of the functions and steps provided in the Figures may be implemented in hardware, software or a combination of both and may be performed in whole or in part within the programmed instructions of a computer. No claim element herein is to be construed under the provisions of <NUM> U. §<NUM>(f), unless the element is expressly recited using the phrase "means for. " In addition, an artisan understands and appreciates that a "processor" or "microprocessor" may be hardware in the claimed disclosure. Under the broadest reasonable interpretation, the appended claims are statutory subject matter in compliance with <NUM> U.

According to an embodiment, the processor <NUM> may establish a communication connection with the first external electronic device <NUM> based on the first BT address using the communication circuitry <NUM> and may end the communication connection with the first external electronic device <NUM>. For example, when receiving an input associated with the communication connection with the first external electronic device <NUM> through the user interface <NUM>, the processor <NUM> may establish the communication connection with the first external electronic device <NUM> based on the first BT address using the communication circuitry <NUM>. The communication connection between the electronic device <NUM> and the first external electronic device <NUM> may be intentionally ended by users of the electronic device <NUM> or the first external electronic device <NUM>, or may be ended due to various factors, such as deterioration in signal intensity of the electronic device <NUM> or the first external electronic device <NUM> or an increase in separation distance between the electronic device <NUM> and the first external electronic device <NUM>. In an embodiment, the processor <NUM> may store first information about the first external electronic device <NUM>, obtained in a communication connection process (e.g., an inquiry process) based on the first BT address, in the memory <NUM>. The first information about the first external electronic device <NUM> may include, for example, the BT address of the first external electronic device <NUM> and/or the name of the first external electronic device <NUM>.

According to an embodiment, when receiving a reconnection request based on the first BT address from the first external electronic device <NUM> after ending the communication connection with the first external electronic device <NUM>, the processor <NUM> may transmit a communication connection request to the first external electronic device <NUM> based on the second BT address using the communication circuitry <NUM> in response to the reconnection request. Thereafter, the processor <NUM> may identify that the first external electronic device <NUM> accepts or declines the communication connection request. For example, when receiving a response to the communication connection request from the first external electronic device <NUM> within a specified time after transmitting the communication connection request, the processor <NUM> may determine that the first external electronic device <NUM> accepted the communication connection request. Otherwise, the processor <NUM> may determine that the first external electronic device <NUM> declined the communication connection request. The response may include at least one of, for example, a setup complete event, an authentication success event, an encryption on event, or service discovery protocol (SDP) completion. The specified time may be experimentally set based on the average time for establishing BT communication.

According to an embodiment, the processor <NUM> may store second information about the probability that the first external electronic device <NUM> will accept or decline a connection request based on a BT address for which there is no connection history (e.g. the second BT address) in the memory <NUM>. For example, the processor <NUM> may associated and store the first information about the first external electronic device <NUM> with the second information about the probability that the first external electronic device <NUM> will accept the connection request in the memory <NUM>. In another example, the processor <NUM> may store registered device information, including first information about at least one first external electronic device (e.g., the first external electronic device <NUM>) and second information about a probability that the at least one first external electronic device accepts a connection request, in a memory (e.g., a lookup table of the memory <NUM>). The first information about the at least one first external electronic device may be obtained through communication based on a first BT address with each of the at least one first external electronic device using the communication circuitry <NUM> by the processor <NUM>. The second information about the probability that the at least one first external electronic device will accept the connection request may be obtained through communication based on a second BT address with each of the at least one first external electronic device using the communication circuitry <NUM> by the processor <NUM>.

According to an embodiment, after storing the second information about the probability that the first external electronic device <NUM> will accept the connection request in the memory <NUM>, the processor <NUM> may establish communication based on the first BT address (hereinafter referred to as "first BT communication") with the first external electronic device <NUM> using the communication circuitry <NUM>. For example, when the first external electronic device <NUM> accepts a communication connection request based on the second BT address, the processor <NUM> may store the second information about the first external electronic device <NUM> accepting the communication connection request in the memory <NUM> and may establish communication based on the second BT address (hereinafter referred to as "second BT communication") with the first external electronic device <NUM> using the communication circuitry <NUM>. Thereafter, the processor <NUM> may end the second BT communication connection with the first external electronic device <NUM> and may establish the first BT communication connection with the first external electronic device <NUM>. In another example, when the first external electronic device <NUM> declines the communication connection request based on the second BT address, the processor <NUM> may store information about the first external electronic device <NUM> declining the communication connection request in the memory <NUM>. Thereafter, the processor <NUM> may establish the first BT communication connection based on the first BT address with the first external electronic device <NUM>. In yet another example, after storing the second information about the probability the first external electronic accepting the communication connection request in the memory <NUM>, the processor <NUM> may receive a reconnection request based on the first BT address from the first external electronic device <NUM>. In this case, the processor <NUM> may respond to the reconnection request based on the first BT address and may establish the first BT communication connection with the first external electronic device <NUM>.

According to an embodiment, the processor <NUM> may share (e.g., transmit) at least a part of the registered device information with a second external electronic device (e.g., a second external electronic device <NUM> of <FIG>) using the communication circuitry <NUM>. For example, the processor <NUM> may transmit the first information about one or more first external electronic devices included in the registered device information and the second information about the probability whether the first external electronic devices will accept or decline the communication connection request to the second external electronic device <NUM>. In another example, the processor <NUM> may transmit first information about a first external electronic device selected through the user interface <NUM> and second information about a probability that the selected first external electronic device will accept a communication connection request to the second external electronic device <NUM>. In yet another example, the processor <NUM> may selectively transmit the first information about a first external electronic device that will accept the communication connection request based on the second BT address (e.g., a BT address in which there is no connection history) among a plurality of first external electronic devices and the second information about the probability that the selected first external electronic device will accept the communication connection request to the second external electronic device <NUM>. The processor <NUM> may make this selection based on the second information about the probability that the first external electronic device will accept the communication connection request.

In the exemplary above-mentioned embodiment, when receiving the reconnection request from the first external electronic device <NUM> after ending the first BT communication with the first external electronic device <NUM>, the processor <NUM> transmits the communication connection request based on the second BT address. However, the instant disclosure is not so limited. For example, when communication based on the first BT address is established with the first external electronic device <NUM>, the processor <NUM> may transmit the communication connection request based on the second BT address to the first external electronic device <NUM>. In another example, when the first BT communication is established with the first external electronic device <NUM>, the processor <NUM> may intentionally end the first BT communication connection and may transmit a communication connection request to the first external electronic device <NUM> based on the second BT address. In yet another example, after the communication connection based on the first BT address with the first external electronic device <NUM> is ended, the processor <NUM> may transmit a communication connection request to the first external electronic device <NUM> based on the second BT address at a specified time. The specified time may be specified periodically or may be a time when the processor <NUM> performs an inquiry process.

According to the above-mentioned embodiment, the electronic device <NUM> may configure BT communication information (registered device information) used to notify a user whether the first external electronic device <NUM> accepts a communication connection request based on a BT address (e.g., the second BT address) in which there is no connection history. Thus, the second external electronic device <NUM> which receives the registered device information from the electronic device <NUM> may be prevented from trying and failing to establish a communication connection with the first external electronic device <NUM>. This reduces the inconvenience of failed BT communication connections.

<FIG> is a block diagram illustrating a configuration of a second external electronic device according to an embodiment.

Referring to <FIG>, a second external electronic device <NUM> (e.g., the second external electronic device <NUM> of <FIG>) according to an embodiment may include a user interface <NUM> (e.g., the display device <NUM> of <FIG>), a communication circuitry <NUM> (e.g., the communication module <NUM> of <FIG>), a memory <NUM> (e.g., the memory <NUM> of <FIG>), and a processor <NUM> (e.g., the processor <NUM> of <FIG>). In an embodiment, the second external electronic device <NUM> may exclude some components or may further include an additional component. In an embodiment, some of the components of the second external electronic device <NUM> may be combined into one entity to perform functions of the components before the combination in the same manner.

According to an embodiment, the user interface <NUM> may include an input circuitry and a display. The input circuitry may include at least one of a touch sensor or a physical button. The display may include a display included in the second external electronic device <NUM> or a display included in another electronic device which communicates with the second external electronic device <NUM>. In this embodiment, which is an example, the user interface <NUM> is a touch screen display, i.e. a display combined with a touch sensor.

According to an embodiment, the communication circuitry <NUM> may include at least one communication circuitry configured to support BT communication. The communication circuitry <NUM> may be configured with a third BT address. For example, the communication circuitry <NUM> may include an integrated circuit for BT communication, and may store the third BT address in an internal memory of the integrated circuit. The third BT address may be, for example, a unique address of the second external electronic device <NUM> for BT communication.

The memory <NUM> may include instructions, when executed, causing the processor <NUM> to receive first information about at least one first external electronic device (e.g., the first external electronic device <NUM> of <FIG>) with which an electronic device (e.g., the electronic device <NUM> of <FIG>) is connected through BT communication and second information about a probability that the at least one first external electronic device will accept a connection request using an address for which there is no connection history and provide the second information via the user interface <NUM>. The memory <NUM> may store, for example, a command or data associated with at least one other component of the second external electronic device <NUM>. The memory <NUM> may be a volatile memory (e.g., a RAM), a non-volatile memory (e.g., a ROM or a flash memory), or a combination thereof.

The processor <NUM> may execute calculation or data processing about control and/or communication of at least one other component of the second external electronic device <NUM> using the instructions stored in the memory <NUM>. The processor <NUM> may include at least one of, for example, a CPU, a GPU, a microprocessor, an application processor, an ASIC, or FPGA and may have a plurality of cores.

According to an embodiment, the processor <NUM> may receive first information about at least one first external electronic device with which the electronic device <NUM> is connected through BT communication and second information about a probability that the at least one first external electronic device will accept a connection request using an address for which there is no connection history, from the electronic device <NUM> via the communication circuitry <NUM>. For example, when the electronic device <NUM> transmits registered device information, the processor <NUM> may receive the registered device information. In another example, when receiving an input associated with receiving registered device information via the user interface <NUM>, the processor <NUM> may transmit a request associated with transmitting the registered device information to the electronic device <NUM> and may receive at least a part of the registered device information as a response to the request from the electronic device <NUM>.

According to an embodiment, when the first information about the at least one first external electronic device and the second information about the probability that the at least one first external electronic device will accept the connection request are received, the processor <NUM> may provide a screen allowing the user select at least a part of the first information and the second information received via the user interface <NUM>. The processor <NUM> may store the first information and the second information selected through the screen in the memory <NUM>.

According to an embodiment, when the registered device information is received, the processor <NUM> may provide first guide information for providing a notification that the reception of the registered device information is completed, via the user interface <NUM>. Furthermore, the processor <NUM> may provide second guide information (e.g., a notification bar) for providing a notification that the registered device information is updated when the registered device information is updated, via the user interface <NUM>. In this case, the processor <NUM> may provide the updated registered device information via the user interface <NUM> in response to an input associated with selecting the second guide information.

According to an embodiment, the processor <NUM> may provide the second information about the probability that the at least one first external electronic device will accept the connection request, via the user interface <NUM>. For example, the processor <NUM> may classify the at least one first external electronic device into a first type of first external electronic devices which is currently connected through BT communication, a second type of first external electronic devices capable of establishing a BT communication connection based on an address for which there is no connection history, and a third type of first external electronic devices incapable of establishing the BT communication connection based on the address for which there is no connection history. The processor <NUM> may provide the first information about the at least one first external electronic device via the user interface <NUM> in the above classification (e.g., one of the first to third types). For example, the processor <NUM> may display first information about the first type of first external electronic devices in blue, may display first information about the second type of first external electronic devices in black, and may display first information about the third type of first external electronic devices in gray. According to another embodiment, the processor <NUM> may display the first information about the first type of first external electronic device and the first information about the second type of first external electronic device and may fail to display the first information about the third type of first external electronic device.

According to an embodiment, when receiving an input associated with a connection request for one of the at least one first external electronic device via the user interface <NUM>, the processor <NUM> may establish a communication connection based on the third BT address using first information about the first external electronic device corresponding to the input associated with the connection request (e.g., the BT address of the first external electronic device).

According to the above-mentioned embodiment, the second external electronic device <NUM> may provide registered device information including second information about a probability that the at least one first external electronic device <NUM> will accept a connection request using an address for which there is no connection history. Thus, the user of the second external electronic device <NUM> may, when attempting to establish a BT communication connection using the registered device information, may readily recognize while first external electronic device the second external electronic device <NUM> can connect to.

<FIG> is a flowchart illustrating a method for generating second information about a probability that a first external electronic device will accept a connection request based on an address for which there is no connection history, according to an embodiment.

Referring to <FIG>, in operation <NUM>, an electronic device (e.g., the electronic device <NUM> of <FIG>) establishes a communication connection with a first external electronic device (e.g., the first external electronic device <NUM> of <FIG>) using a first BT address via a communication circuitry (e.g., the communication circuitry <NUM> of <FIG>). The first BT address may be, for example, a unique address of the electronic device <NUM> for BT communication. In operation <NUM>, the electronic device <NUM> may store first information about the first external electronic device <NUM> in a memory (e.g., the memory <NUM> of <FIG>). For example, the first information about the first external electronic device <NUM> may include the BT address and/or the name of the first external electronic device.

In operation <NUM>, the electronic device <NUM> ends the communication connection with the first external electronic device <NUM>. In operation <NUM>, the communication connection may be ended intentionally by the users of electronic device <NUM> or the first external electronic device <NUM> or may be ended due to various factors such as deterioration in signal intensity of the electronic device <NUM> or the first external electronic device <NUM> or an increase in separation distance between the electronic device <NUM> and the first external electronic device <NUM>.

After ending the communication connection with the first external electronic device <NUM>, in operation <NUM>, the electronic device <NUM> receives a reconnection request based on the first BT address from the first external electronic device <NUM>.

In operation <NUM>, the electronic device <NUM> transmits a communication connection request to the first external electronic device <NUM> based on a second BT address different from the first BT address using the communication circuitry <NUM> in response to the reconnection request. The second BT address is an address for which there is no history of established communication connections with the first external electronic device <NUM>.

In operation <NUM>, the electronic device <NUM> may identify that the first external electronic device <NUM> accepts the communication connection request based on the second BT address. When the first external electronic device <NUM> accepts the communication connection request based on the second BT address, the electronic device <NUM> may establish BT communication based on the second BT address with the first external electronic device <NUM>.

In operation <NUM>, the electronic device <NUM> stores second information about a probability that the first external electronic device <NUM> will accept the communication connection request in the memory <NUM>. For example, the electronic device <NUM> may associate and store the first information about the first external electronic device <NUM> with the second information about the probability that the first external electronic device <NUM> will accept the communication connection request in the memory <NUM>. The second information about the probability that the first external electronic device <NUM> will accept the communication connection request may include, for example, information indicating whether the first external electronic device <NUM> accepts or declines a request to establish BT communication for which there is no connection history. The second information about the probability that the first external electronic device <NUM> will accept the communication connection request may include, in another example, information indicating whether the first external electronic device <NUM> accepts or declines the communication connection request received from the electronic device <NUM> when the first external electronic device <NUM> is powered on (e.g., Bluetooth is powered on).

After operation <NUM>, the electronic device <NUM> may transmit the reconnection request based on the first BT address to the first external electronic device <NUM> and may establish a communication connection with the first external electronic device <NUM> in response to the reconnection request.

According to another embodiment, in operation <NUM>, the electronic device <NUM> may fail to receive the reconnection request based on the first BT address from the first external electronic device <NUM> and may transmit a reconnection request based on the second BT address to the first external electronic device <NUM>. In this case, operation <NUM> may be omitted.

According to yet another embodiments, immediately after ending the communication connection with the first external electronic device <NUM> in operation <NUM>, the electronic device <NUM> may transmit the reconnection request based on the second BT address to the first external electronic device <NUM> as shown in operation <NUM>. In this case, operation <NUM> may be omitted.

<FIG> is a flowchart illustrating a method for storing BT communication information at an electronic device according to an embodiment.

Referring to <FIG>, in operation <NUM>, an electronic device (e.g., the electronic device <NUM> of <FIG>) establishes a communication connection with a first external electronic device (e.g., the first external electronic device <NUM> of <FIG>) using a first BT address. The first BT address may be, for example, a unique address of the electronic device <NUM> for BT communication. In operation <NUM>, the electronic device <NUM> may store first information about the first external electronic device <NUM> in a memory (e.g., a memory <NUM> of <FIG>). For example, the first information about the first external electronic device <NUM> may include the BT address and/or the name of the first external electronic device <NUM>.

In operation <NUM>, the electronic device <NUM> transmits a communication connection request to the first external electronic device <NUM> based on a second BT address. The second BT address is an address for which there is no history of established communication connections with the first external electronic device <NUM>.

In operation <NUM>, the electronic device <NUM> stores second information about whether the first external electronic device <NUM> accepted or declined the communication connection request based on the second BT address. For example, the electronic device <NUM> may identify that the first external electronic device <NUM> accepted or declined the communication connection request based on the second BT address and may store information about the identified acceptance or denial.

<FIG> is a signal sequence diagram illustrating a method for generating second information about whether a first external electronic device accepts a communication connection request based on a BT address for which there is no connection history, according to an embodiment. The electronic device <NUM> may include a host (e.g., an application processor) and a client (e.g., a call processor). Operations of <FIG> may be performed by the client. Herein, prior to operation <NUM>, the client may establish a communication connection with the host and may receive a command to identify information about whether the first external electronic device <NUM> would accept or decline a communication connection request based on a BT address for which there is no connection history from the host. The client may perform the operations of <FIG> based on the received command. In this case, the client may transmit information associated with the completion of operation <NUM> to the host, and may stop performing the operation of <FIG> by receiving a command to stop identifying the information from the host. In another embodiment, when the client is initialized, it may perform the operations of <FIG>, even if it does not receive the command from the host.

Referring to <FIG>, in operation <NUM>, the electronic device <NUM> may receive a reconnection request from the first external electronic device <NUM>. Together the two devices have a history of establishing a first BT communication connection. For example, when receiving an ID packet with a first access code from the first external electronic device <NUM> in operation <NUM>, the electronic device <NUM> may transmit the ID packet with the first access code as the response in operation <NUM>. The first access code (a device access code (DAC) for device under test (DUT)) may be generated based on a unique address (Lower Address Part "LAP" of the first BT address) of the electronic device <NUM> for BT communication. When the ID packet with the first access code is received, the first external electronic device <NUM> may transmit the BT address of the first external electronic device <NUM> and an FHS packet with the first access code in operation <NUM>. Although receiving the FHS packet with the first access code, the electronic device <NUM> may fail to transmit the ID packet with the first access code, which responds to the FHS packet, in operation <NUM>. In operation <NUM>, the electronic device <NUM> may transmit a communication connection request based on a second BT address (an address different from the first BT address) to the first external electronic device <NUM> in response to the reconnection request of the first external electronic device <NUM>. For example, the electronic device <NUM> may transmit an ID packet with a second access code (DAC for Peer) in response to the reconnection request in operation <NUM> and may receive an ID packet with the second access code as the response from the first external electronic device <NUM> in operation <NUM>. The electronic device <NUM> may transmit an FHS packet with the second BTS address in operation <NUM> and may receive an ID packet with the second access code as the response from the first external electronic device <NUM> in operation <NUM>. Thereafter, the electronic device <NUM> and the first external electronic device <NUM> may exchange a first poll and a first null based on the second BT address in operations <NUM> and <NUM>.

In operation <NUM>, the electronic device <NUM> may identify that the first external electronic device <NUM> accepts (or declines) the communication connection request based on the second BT address. For example, when identifying that authentication with the first external electronic device <NUM> succeeds within a specified time in operation <NUM> after transmitting the communication connection request based on the second BT address, the electronic device <NUM> may determine that the first external electronic device <NUM> accepts the communication connection request. After identifying that the first external electronic device <NUM> accepts or declines the communication connection request based on the second BT address, the electronic device <NUM> may store second information about whether the first external electronic device <NUM> accepts or declines the communication connection request in a memory (e.g., a memory <NUM> of <FIG>). After identifying that the first external electronic device <NUM> accepts or declines the communication connection request based on the second BT address, the electronic device <NUM> may release the communication connection based on the second BT address in operation <NUM>.

In operation <NUM>, the electronic device <NUM> may establish a communication connection based on the first BT address. The electronic device <NUM> may transmit a reconnection request based on a BT address of the first external electronic device <NUM> to the first external electronic device <NUM> to be re-connected with the first external electronic device <NUM> and may establish a communication connection with first external electronic device <NUM> as the response. For example, the electronic device <NUM> may transmit an ID packet with the second access code (DAC for Peer) in operation <NUM> and may receive an ID packet with the second access code as the response from the first external electronic device <NUM> in operation <NUM>. Thereafter, the electronic device <NUM> may transmit an FHS packet with a first BT address in operation <NUM> and may receive an ID packet with the second access code as the response from the first external electronic device <NUM> in operation <NUM>. Thereafter, the electronic device <NUM> may exchange a first poll and a first null with the first external electronic device <NUM> based on the first BT address in operations <NUM> and <NUM> and may establish the communication connection with the first external electronic device <NUM>.

<FIG> are signal sequence diagrams illustrating methods for generating second information about whether a first external electronic device declines a communication connection request based on a BT address for which there is no connection history, according to an embodiment.

<FIG> includes operation <NUM> rather than operation <NUM> of <FIG>. <FIG> includes operation <NUM> rather than operation <NUM> of <FIG>. <FIG> includes operation <NUM>' rather than operation <NUM> of <FIG>. <FIG> is different from <FIG> in that operation <NUM> is omitted. Thus, description will be given below of the difference.

Referring to <FIG>, in operation <NUM>, an electronic device <NUM> may identify that the first external electronic device <NUM> fails in authenticating a communication connection request based on the second BT address. In this case, the electronic device <NUM> may determine that the first external electronic device <NUM> has declined the communication connection request based on the BT address for which there is no connection history and may associate and store second information about the first external electronic device <NUM> declining the communication connection request with first information about the first external electronic device <NUM> in a memory (e.g., a memory <NUM> of <FIG>).

Referring to <FIG>, in operation <NUM>, the electronic device <NUM> may identify that the first external electronic device <NUM> succeeds in authenticating the communication connection request based on the second BT address. However, in operation <NUM>, the electronic device <NUM> may identify that the first external electronic device <NUM> has not connected. In this case, the electronic device <NUM> may determine that the first external electronic device <NUM> has declined the communication connection request based on a BT address for which there is no connection history and may associate and store second information about the first external electronic device <NUM> declining the communication connection request with first information about the first external electronic device <NUM> in the memory <NUM>.

Referring to <FIG>, in operation <NUM>', the electronic device <NUM> may transmit an ID packet with a second access code (DAC for Peer) in response to a reconnection request of the first external electronic device <NUM> in operation <NUM> and may receive an ID packet with the second access code as the response from the first external electronic device <NUM> in operation <NUM>. The electronic device <NUM> may transmit an FHS packet with a second BT address in operation <NUM> and may fail to receive an ID packet with the second access code from the first external electronic device <NUM> in operation <NUM>'. In this case, the electronic device <NUM> may determine that the first external electronic device <NUM> has declined a communication connection request based on a BT address for which there is no connection history and may associate and store second information about the first external electronic device <NUM> declining the communication connection request with first information about the first external electronic device <NUM> in the memory <NUM>.

<FIG> are signal sequence diagrams illustrating methods where an electronic device does not receive a reconnection request from a first external electronic device, according to an embodiment.

<FIG> are different from <FIG> in that <FIG> includes operation 510b rather than operation <NUM> of <FIG>, <FIG> includes operation 510c rather than operation <NUM> of <FIG>, and <FIG> includes operation 510d rather than operation <NUM> of <FIG>. Thus, descriptions will be given below of the difference.

Referring to <FIG>, in operation <NUM>, an electronic device <NUM> may receive an ID packet with a first access code from a first external electronic device <NUM> which has a history of establishing a first BT communication connection. In operation <NUM>, the electronic device <NUM> may transmit an ID packet with the first access code as the response. When the ID packet with the first access code is received, in operation <NUM>, the first external electronic device <NUM> may transmit a BT address of the first external electronic device <NUM> and an FHS packet with the first access code. In operation <NUM>, the electronic device <NUM> may transmit an ID packet with a second access code (DAC for Peer). In operations <NUM> and <NUM>, the electronic device <NUM> may exchange a first poll and a first null with the first external electronic device <NUM> based on a first BT address. In operation <NUM>, the electronic device <NUM> may refrain from performing a subsequent operation such as authentication and may wait until the communication connection expires.

Referring to <FIG>, in operation <NUM>, the electronic device <NUM> may receive an ID packet with a first access code from the first external electronic device <NUM> which has a history of establishing a first BT communication connection. In operation <NUM>, the electronic device <NUM> may transmit an ID packet with the first access code as the response. When the ID packet with the first access code is received, in operation <NUM>, the first external electronic device <NUM> may transmit a BT address of the first external electronic device <NUM> and an FHS packet with the first access code. In operation <NUM>, the electronic device <NUM> may transmit an ID packet with a second access code (DAC for Peer). In operations <NUM> and <NUM>, the electronic device <NUM> may exchange a first poll and a first null with the first external electronic device <NUM> based on a first BT address. In operation <NUM>, the electronic device <NUM> may release the communication connection with the first external electronic device <NUM>.

Referring to <FIG>, in operation <NUM>, the electronic device <NUM> may receive an ID packet with a first access code from the first external electronic device <NUM> which has a history of establishing a first BT communication connection. In operation <NUM>, the electronic device <NUM> may transmit an ID packet with the first access code as the response. When the ID packet with the first access code is received, in operation <NUM>, the first external electronic device <NUM> may transmit a BT address of the first external electronic device <NUM> and an FHS packet with the first access code. In operation <NUM>, the electronic device <NUM> may transmit an ID packet with a second access code (DAC for Peer). In operations <NUM> and <NUM>, the electronic device <NUM> may exchange a first poll and a first null with the first external electronic device <NUM> based on a first BT address. Thereafter, the electronic device <NUM> may perform operations <NUM> to <NUM> of <FIG>.

<FIG> is a drawing illustrating an example of a UI screen for sharing registered device information according to an embodiment. <FIG> illustrates an example of sharing registered device information using a specified app of an electronic device <NUM>.

Referring to <FIG>, in reference numeral <NUM>, when receiving an input associated with executing the specified app, the electronic device <NUM> may execute the specified app, called "Smart Switch" in this embodiment. The specified app may be an app that provides a function for sharing registered device information.

In reference numeral <NUM>, when the specified app is run, the electronic device <NUM> may provide virtual buttons for selecting registered device information transmission methods. The virtual buttons may include, for example, a virtual button <NUM> for selecting a first method using USB communication, a virtual button <NUM> for selecting a second method using wireless communication (e.g., Wi-Fi or BT), and a virtual button <NUM> for selecting a third method using an external memory (e.g., an SD card or a USB storage).

In reference numeral <NUM>, when one of the first to third methods is selected by a user input, the electronic device <NUM> may provide first information <NUM> about at least one first external electronic device and virtual buttons <NUM> for selecting first information about at least some of the at least one first external electronic device. The first information may be transmitted to a second external electronic device <NUM>. The electronic device <NUM> may transmit only first information about the first external electronic device selected using the virtual buttons <NUM> to the second external electronic device <NUM>. For example, when the virtual button <NUM> for selecting the first method is selected, the electronic device <NUM> may transmit the first information about the selected first external electronic device(s) to the second external electronic device <NUM> which is connected with the electronic device <NUM> through USB communication. In another example, when the virtual button <NUM> for selecting the second method is selected, the electronic device <NUM> may transmit the first information about the selected first external electronic device(s) to the second external electronic device <NUM> which is connected with the electronic device <NUM> through wireless communication. In yet another example, when the virtual button <NUM> for selecting the third method is selected, the electronic device <NUM> may store the first information about the selected first external electronic device(s) in an external memory of the electronic device <NUM>. The external memory may then be transferred to the second external electronic device <NUM> such that the first information is transmitted via the external memory.

<FIG> is a drawing illustrating another example of a UI screen for sharing registered device information according to an embodiment.

Referring to <FIG>, after transmitting registered device information to a second external electronic device <NUM>, an electronic device <NUM> may provide a notification that the transmission of the registered device information is completed. For example, reference numeral <NUM> may include information <NUM> for providing a notification that the transmission of the registered device information is completed and transmitted (shared) first information <NUM> about at least one first external electronic device. Reference numeral <NUM> may further include information <NUM> for selecting to delete or maintain transmitted first information <NUM> about the at least one first external electronic device after the electronic device <NUM> transmits the first information <NUM> to the second external electronic device <NUM>. When it is selected to delete the transmitted first information <NUM>, the electronic device <NUM> may not receive further connection requests and notifications from the at least one first external electronic device. According to another embodiment, when the first information <NUM> about the first external electronic device is matched with a specified condition such as a certain time or a specific place, the electronic device <NUM> may be configured to receive a connection request and notification from the at least one first external electronic device.

After receiving the first information about the at least one first external electronic device from the electronic device <NUM>, the second external electronic device <NUM> may provide a notification that the reception of the first information <NUM> about the at least one first external electronic device is completed. For example, reference numeral <NUM> may include information <NUM> for providing a notification that the reception of the first information <NUM> about the at least one first external electronic device is completed, the received first information <NUM> about the at least one first external electronic device, and a virtual button <NUM> for selecting first information about the first external electronic device to be stored in a memory of the second external electronic device <NUM>. The first information about the first external electronic device may include information 723a indicating the second type of first external electronic device capable of establishing a BT communication connection based on an address for which there is no connection history and information 723b indicating the third type of first external electronic device incapable of establishing a BT communication connection based on an address for which there is no connection history.

When identifying a request (e.g., selecting the virtual button <NUM>) associated with storing first information about the selected first external electronic device, the second external electronic device <NUM> may store only first information 725a and 725b about the selected first external electronic devices in a memory (e.g., a memory <NUM> of <FIG>). In this case, the second external electronic device <NUM> may transmit a request to release the previous connection to the first external electronic device <NUM> or stop a scan operation to the electronic device <NUM>. The electronic device <NUM> may release the previous connection to the first external electronic device <NUM> and may stop the scan operation, in response to the request.

According to another embodiments, after sharing the first information about the at least one first external electronic device with the second external electronic device <NUM>, the electronic device <NUM> may still store the first information about the at least one first external electronic device. In this case, when the second external electronic device <NUM> attempts to establish a BT communication connection based on the first information about the at least one first external electronic device, the electronic device <NUM> may scan the at least one first external electronic device and may interfere with BT communication between the second external electronic device <NUM> and the first external electronic device. To prevent it, when matched with a specified condition, the electronic device <NUM> may refrain from establishing a BT communication connection based on the first information about the at least one first external electronic device. As examples, when the electronic device <NUM> is close to the second external electronic device <NUM> within a specified distance, when a first specified time interval does not elapse after the electronic device <NUM> shares the first information about the at least one first external electronic device, or when a second specified time interval does not elapse after the electronic device <NUM> receives a request to stop a communication connection based on the first information about the at least one first external electronic device, the electronic device <NUM> may refrain from establishing the BT communication connection based on the first information about the at least one first external electronic device. The electronic device <NUM> may receive information about a mediation device (e.g., an access point or a base station) the second external electronic device <NUM> accesses or location information (GPS information) of the second external electronic device <NUM> and may determine whether there is the mediation device on the same space as the second external electronic device <NUM>. According to another embodiment, the electronic device <NUM> may receive the mediation device information and the location information from an external server (e.g., an external server <NUM> of <FIG>).

<FIG> is a drawing illustrating an example of sharing registered device information at an electronic device according to an embodiment.

Referring to <FIG>, an electronic device <NUM> may transmit registered device information about a first external electronic device <NUM> to second external electronic devices 130_1 and 130_2 such that the second external electronic devices 130_1 and 130_2 can easily establish a BT communication connection with the first external electronic device <NUM>.

For example, when a BT detailed setting for the first external electronic device <NUM> called "Level U Flex" included in the registered device information is selected, the electronic device <NUM> may display a screen <NUM> including a specified electronic device list <NUM>, which includes electronic devices capable of sharing first information about the first external electronic device <NUM>, and virtual buttons <NUM> for selecting at least some of the electronic devices included in the specified electronic device list <NUM>. The specified electronic device list <NUM> may include, for example, at least one specified electronic device, capable of performing BT communication, configured to have the same user account as the electronic device <NUM> or an account of a person associated with the electronic device <NUM>. The specified electronic device list <NUM> may be received from, for example, an external server (e.g., a server which manages a user account set in the electronic device <NUM>).

As shown by reference numerals <NUM> and <NUM>, the electronic device <NUM> may transmit the first information about the first external electronic device <NUM> to the first specified electronic device (e.g., Galaxy Tab S3) 130_1 and the second specified electronic device (e.g., Galaxy S9) 130_2, which are selected through the virtual buttons <NUM>.

According to another embodiment, the electronic device <NUM> may share the first information about the first external electronic device <NUM> with the first specified electronic device 130_1 and the second specified electronic device 130_2 via an external server (e.g., an external server <NUM> of <FIG>).

<FIG> is a drawing illustrating another example of sharing registered device information at an electronic device according to an embodiment.

Referring to <FIG>, in response to a request for registered device information, an electronic device <NUM> may transmit the registered device information to a specified electronic device via an external server <NUM>.

In operation <NUM>, when identifying an input <NUM> associated with the request for the registered device information, the electronic device <NUM> may request the external server <NUM> to share the registered device information with the specified electronic device. Upon the request, the electronic device <NUM> may transmit the registered device information to the external server <NUM>. The external server <NUM> may be, for example, a server which manages a user account set in the electronic device <NUM>.

In operation <NUM>, when receiving the registered device information from the electronic device <NUM>, the external server <NUM> may search for a specified electronic device corresponding to the registered device information. The specified electronic device may include, for example, a device which supports BT communication among electronic devices configured to have the same user account as the electronic device <NUM>.

In operation <NUM>, the external server <NUM> may transmit the registered device information to the specified electronic device corresponding to the registered device information. According to another embodiment, when the received registered device information is not updated (e.g., is identical to previously received registered device information), the electronic device <NUM> or the external server <NUM> may refrain from transmitting the registered device information to the external server <NUM> or the specified electronic device.

According to another embodiment, when there is previously stored registered device information, the electronic device <NUM> may receive updated registered device information from the external server <NUM> in response to the input <NUM> and may store the updated registered device information.

According to another embodiment, the electronic device <NUM> may transmit the registered device information to the specified electronic device without intervention of the external server <NUM>.

<FIG> is a drawing illustrating a UI screen for guiding a user to update registered device information at a second external electronic device according to an embodiment.

Referring to <FIG>, a second external electronic device <NUM> (e.g., the second external electronic device <NUM> of <FIG>) may receive first information about a first external electronic device (e.g., the first external electronic device <NUM> of <FIG>) from an electronic device (e.g., the electronic device <NUM> of <FIG>) or an external server (e.g., the external server <NUM> of <FIG>) and may output screens for notifying the user of the received first information about the first external electronic device <NUM>.

In reference numeral <NUM>, when receiving the first information about the first external electronic device <NUM> and second information about a probability that the first external electronic device <NUM> will accept a connection request from the external server <NUM>, the second external electronic device <NUM> may output a notification bar <NUM> for notifying the user that registered device information is updated.

In reference numeral <NUM>, the second external electronic device <NUM> may display registered device information <NUM> including first information <NUM> about the first external electronic device <NUM>, received from the electronic device <NUM>, based on an input associated with selecting the notification bar <NUM>. An icon <NUM> for displaying a detailed setting screen of BT communication of each electronic device may be further included in the periphery of first information of each electronic device (e.g., the first information about the first external electronic device <NUM>), included in the registered device information <NUM>.

<FIG> and <FIG> are drawings illustrating UI screens for selecting a display scheme of registered device information according to an embodiment.

Referring to <FIG> and <FIG>, when receiving registered device information, a second external electronic device <NUM> may output a UI screen (e.g., a UI screen <NUM>) for inquiring about the manner for which the received registered device information is displayed.

Referring to <FIG>, for example, when receiving registered device information from an electronic device (e.g., the electronic device <NUM> of <FIG>), the second external electronic device <NUM> (e.g., the second external electronic device <NUM> of <FIG>) may output the UI screen <NUM> for inquiring about the manner for which the registered device information is displayed. On the UI screen <NUM>, the second external electronic device <NUM> may display a first virtual button <NUM> for selecting a first mode for displaying only first information about the second type of first external electronic devices and a second virtual button <NUM> for selecting a second mode for displaying all of first information of the first external electronic devices. The second type of first external electronic devices may be those capable of establishing a BT communication connection based on an address for which there is no connection history. All the types of first external electronic devices may include, for example, the first type of first external electronic devices which are currently connected through BT communication and the third type of first external electronic device incapable of establishing a BT communication connection based on an address for which there is no connection history, in addition to the second type of first external electronic devices. When displaying the first information about all the types of first external electronic devices, the second external electronic device <NUM> may separately display the first to third types.

Referring to <FIG>, the second external electronic device <NUM> (e.g., the second external electronic device <NUM> of <FIG>) may display, for example, a virtual button <NUM> for selecting a mode (e.g., the first mode or the second mode) for displaying at least one external electronic device in the registered device information on a UI screen <NUM>.

<FIG> and <FIG> are drawings illustrating examples of displaying registered device information according to an embodiment.

Referring to <FIG>, a second external electronic device <NUM> may display only first information about the first type of first external electronic device and the second type of first external electronic device in received registered device information. For example, when a first virtual button <NUM> is selected in <FIG>, the second external electronic device <NUM> may display only the first information about the first type of first external electronic devices (e.g., the devices which are currently connected through BT communication) and the first information about the second type of first external electronic devices (e.g., the devices capable of establishing a BT communication connection based on an address for which there is no connection history). On screen <NUM>, the second external electronic device <NUM> may display, for example, first information <NUM> about the first type of first external electronic device in letters of a first thickness, and may display first information <NUM> about the second type of first external electronic device in letters of a second thickness less than the first thickness. In another example, the second external electronic device <NUM> may display the first information <NUM> about the first type of first external electronic device and the first information <NUM> about the second type of first external electronic device separately in different colors.

Referring to <FIG>, the second external electronic device <NUM> may display all types of first external electronic devices included in the received registered device information on a screen <NUM>. For example, when the first virtual button <NUM> is selected in <FIG>, the second external electronic device <NUM> may display all types of first external electronic devices included in the received registered device information. Furthermore, the second external electronic device <NUM> may display an icon <NUM> for notifying the user of additional information on the periphery of registered device information and may display a sentence <NUM> for notifying the user of characteristics of the first external electronic device <NUM> selected based on the selection of the icon <NUM> on the screen <NUM>.

On the screen <NUM>, the second external electronic device <NUM> may display first information <NUM> and <NUM> about the first type of first external electronic device which is currently connected through BT communication in a first color (e.g., blue), may display first information <NUM> and <NUM> about the second type of first external electronic device capable of establishing a BT communication connection based on an address for which there is no connection history in a second color (e.g., black), and may display first information <NUM> and <NUM> about the third type of first external electronic device incapable of establishing a BT communication connection based on an address for which there is no connection history in a third color (e.g., gray).

Additionally or alternatively, the second external electronic device <NUM> may display an icon <NUM> for describing characteristics of the third type of first external electronic device on the periphery of first information about the third type of first external electronic device. When the icon <NUM> is selected, the second external electronic device <NUM> may display a sentence <NUM> for notifying a user of characteristics of the third type of first external electronic device on at least a part of the screen <NUM>. For example, the sentence <NUM> may include a guide on how to establish a BT communication connection to the third type of first external electronic device, i.e. using conventional connection procedures.

<FIG> is a drawing illustrating UI screens for sharing and using registered device information according to an embodiment.

Referring to <FIG>, an electronic device <NUM> may establish BT communication with a first external electronic device <NUM> and may share first information (registered device information) about the first external electronic device <NUM> and second information about a probability that the first external electronic device <NUM> will accept a connection request based on a BT address for which there is no connection history with a second external electronic device <NUM>. The second external electronic device <NUM> may establish a communication connection with the first external electronic device <NUM> based on the first information about the first external electronic device <NUM> and the second information about the probability.

In reference numeral <NUM>, the electronic device (e.g., the electronic device <NUM> of <FIG>) may establish a communication connection based on a first BT address with the first external electronic device (e.g., the first external electronic device <NUM> of <FIG>) (step ①). As a result, the electronic device <NUM> may store first information about the first external electronic device <NUM> (the BT address and/or the name (e.g., level U Flex) of the first external electronic device <NUM>) in a memory (e.g., a memory <NUM> of <FIG>). The electronic device <NUM> may transmit a communication connection request based on a second BT address to the first external electronic device <NUM> and may associate and store the second information about the probability of accepting the communication connection request with the first information about the first external electronic device <NUM> in the memory <NUM>. The second information about the probability that the first external electronic device <NUM> will accept the communication connection request may include information indicating whether the first external electronic device <NUM> accepts the communication connection request based on the second BT address for which there is no connection history.

In reference numeral <NUM>, the electronic device <NUM> may transmit (share) the second information about the probability of accepting the communication connection request and the first information about the first external electronic device <NUM> to the second external electronic device <NUM> (step ②).

In reference numeral <NUM>, the second external electronic device <NUM> may display registered device information stored in its memory and may identify an input associated with a communication connection with the first external electronic device <NUM> in the registered device information (step ③). The second external electronic device <NUM> may establish a communication connection with the first external electronic device <NUM> based on a BT address of the second external electronic device <NUM> depending on the identified input associated with the communication connection (④).

In reference numeral <NUM>, the second external electronic device <NUM> may display registered device information indicating that it established the communication connection with the first external electronic device <NUM>.

When the communication connection is established with the first external electronic device <NUM>, the second external electronic device <NUM> may download and install an app associated with the first external electronic device <NUM> from an external server. For example, the app associated with the first external electronic device <NUM> may include an app for a parameter setting (e.g., a detailed setting) associated with BT communication of the first external electronic device <NUM>. According to another embodiment, when receiving registered device information associated with the first external electronic device <NUM> from the electronic device <NUM>, the second external electronic device <NUM> may receive information associated with the app associated with the first external electronic device <NUM> from the electronic device <NUM> or may download the information about the app from the external server.

According to an embodiment, an electronic device (e.g., an electronic device <NUM> of <FIG>) may include a user interface (e.g., a user interface <NUM> of <FIG>), a communication circuitry (e.g., a communication circuitry <NUM> of <FIG>) configured to support Bluetooth (BT) communication and to store a first BT address, a processor (e.g., a processor <NUM> of <FIG>) operatively connected with the user interface and the communication circuitry, and a memory operatively connected with the processor. The memory may store instructions that, when executed, cause the processor to establish a communication connection with a first external electronic device (e.g.,. a first external electronic device <NUM> of <FIG>) based on the first BT address, using the communication circuitry, end the communication connection with the first external electronic device, receive a reconnection request based on the first BT address from the first external electronic device after ending the communication connection, transmit a communication connection request to the first external electronic device based on a second BT address different from the first BT address, using the communication circuitry in response to the reconnection request, and store information about whether the first external electronic device accepts or declines the communication connection request in the memory.

The instructions may cause the processor to transmit the stored information to a second external electronic device (e.g., a second external electronic device <NUM> of <FIG>).

The instructions may cause the processor to associate and store additional information about the first external electronic device with the information about the first external electronic device accepts or declines the communication connection request. The additional information may be obtained in a communication connection process based on the first BT address.

The instructions may cause the processor to identify whether the first external electronic device accepts or declines the communication connection request, based on the information about whether the first external electronic device accepts or declines the communication connection request, transmit the additional information about the first external electronic device to a second external electronic device using the communication circuitry, when it is identified that the first external electronic device accepts the communication connection request, and may refrain from transmitting the additional information about the first external electronic device to the second external electronic device, when it is identified that the first external electronic device declines the communication connection request.

The instructions may cause the processor to establish another communication connection based on the first BT address with the first external electronic device, after storing the information about whether the first external electronic device accepts or declines the communication connection request.

The instructions may cause the processor to receive another reconnection request based on the first BT address from the first external electronic device, after storing the information in the memory, and establish the other communication connection with the first external electronic device based on the first BT address, in response to the other reconnection request based on the first BT address.

The information may include information indicating whether the first external electronic device accepts or declines the communication connection request, when the first external electronic device is not in a pairing mode.

The first BT address may be a unique address of the electronic device, and the second BT address may be an address for which there is no history of established communication connections with the first external electronic device.

The instructions may cause the processor to, when transmission of the stored information to the second external electronic device is completed, stop a scan of the first external electronic device when a specified time interval has not elapsed from when the stored information is transmitted or when the electronic device is within a specified distance of the second external electronic device.

According to an embodiment, an electronic device (e.g., a second external electronic device <NUM> of <FIG>) may include a user interface (e.g., a user interface <NUM> of <FIG>), at least one communication circuitry (e.g., a communication circuitry <NUM> of <FIG>) configured to support Bluetooth (BT) communication, a processor (e.g., a processor <NUM> of <FIG>) operatively connected with the user interface and the at least one communication circuitry, and a memory (e.g., a memory <NUM> of <FIG>) operatively connected with the processor. The memory may include instructions that, when executed, cause the processor to receive first information about at least one second external electronic device (e.g., a first external electronic device <NUM> of <FIG>) with which a first external electronic device (e.g., an electronic device <NUM> of <FIG>) is connected through BT communication and second information about a probability that the at least one second external electronic device will accept a connection request using an address for which there is no connection history, using the at least one communication circuitry, and provide the second information through the user interface.

The instructions may cause the processor to associate the second information with the first information and provide the second information and the first information through the user interface.

The first external electronic device and the electronic device may be configured with the same user account.

The instructions may cause the processor to provide a user interface element for selecting to store the first information and the second information through the user interface and store the first information and the second information in the memory based on a selection of the user interface element.

The instructions may cause the processor to receive the first information and the second information from the first external electronic device or a server.

The instructions may cause the processor to install an app associated with the at least one second external electronic device based on the first information.

According to an embodiment, an electronic device (e.g., an electronic device <NUM> of <FIG>) may include a user interface (e.g., a user interface <NUM> of <FIG>), a communication circuitry (e.g., a communication circuitry <NUM> of <FIG>) configured to support Bluetooth (BT) communication and to store a first BT address, a processor (e.g., a processor <NUM> of <FIG>) operatively connected with the user interface and the communication circuitry, and a memory (e.g., a memory <NUM> of <FIG>) operatively connected with the processor. The memory may store instructions that, when executed, cause the processor to establish a communication connection with a first external electronic device (e.g., a first external electronic device <NUM> of <FIG>) based on the first BT address, using the communication circuitry, transmit a communication connection request to the first external electronic device based on a second BT address different from the first BT address, using the communication circuitry, after the communication connection is established, and store information about whether the first external electronic device accepts or declines the communication connection request based on the second BT address in the memory.

The instructions may cause the processor to associate and store the information about whether the first external electronic device accepts or declines the communication connection request with additional information about the first external electronic device, the additional information being obtained in a communication connection process based on the first BT address.

The instructions may cause the processor to identify whether the first external electronic device accepts or declines the communication connection request, based on the information about whether the first external electronic device accepts or declines the communication connection request, transmit the additional information about the first external electronic device to a second external electronic device using the communication circuitry, when it is identified that the first external electronic device accepts the communication connection request, and refrain from transmitting the additional information about the first external electronic device to the second external electronic device, when it is identified that the first external electronic device declines the communication connection request.

According to certain embodiments disclosed in the present disclosure, the electronic device may configure BT communication information including information indicating whether it is possible for an external electronic device to establish BT communication based on a BT address for which there is no history of establishing the BT communication. In addition, various effects directly or indirectly ascertained through the present disclosure may be provided.

While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the appended claims.

Claim 1:
An electronic device (<NUM>), comprising:
a user interface (<NUM>);
a communication circuitry (<NUM>) configured to support Bluetooth, BT, communication and to store a first BT address;
a processor (<NUM>) operatively connected with the user interface and the communication circuitry; and
a memory (<NUM>) operatively connected with the processor,
wherein the memory stores instructions that, when executed, cause the processor to:
establish a communication connection with a first external electronic device (<NUM>) based on the first BT address, using the communication circuitry (<NUM>, <NUM>);
end the communication connection with the first external electronic device (<NUM>);
receive a reconnection request based on the first BT address from the first external electronic device, after ending the communication connection (<NUM>);
transmit a communication connection request to the first external electronic device based on a second BT address different from the first BT address, when there is no connection history using the second BT address, using the communication circuitry in response to the reconnection request (<NUM>; <NUM>);
store information about whether the first external electronic device accepts or declines the communication connection request in the memory (<NUM>) and associate and store additional information about the first external electronic device (<NUM>) with the information about the first external electronic device accepts or declines the communication connection request, wherein the additional information is obtained in a communication connection process based on the first BT address;
identify whether the first external electronic device (<NUM>) accepts or declines the communication connection request, based on the information about whether the first external electronic device accepts or declines the communication connection request;
transmit the additional information about the first external electronic device to a second external electronic device (<NUM>) using the communication circuitry (<NUM>), when it is identified that the first external electronic device accepts the communication connection request; and
refrain from transmitting the additional information about the first external electronic device to the second external electronic device, when it is identified that the first external electronic device declines the communication connection request.