Method for sharing bluetooth communication information and electronic device thereof

Abstract

An electronic device is provided, comprising: a user interface; a communication circuit supporting Bluetooth (BT) communication and storing a first BT address; a processor operably connected to the user interface and the communication circuit; and a memory operably connected to the processor. The memory stores instructions that, when executed, cause the processor to establish a communication connection with a first external electronic device based on the first BT address; 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; in response to the reconnection request, use the communication circuit to send a communication connection request to the first external electronic device based on a second BT address different from the first BT address; and store information about whether the first external electronic device accepts or rejects the communication connection request in the memory.

Description

Technical Field

[0001] The present disclosure generally relates to techniques for sharing Bluetooth (BT) communication information. Background Art

[0002] The electronic device may establish BT communication with the external electronic device by sequentially performing 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 communication. The electronic device may store information associated with the external electronic device obtained during the inquiry process (e.g., at least a portion of the unique address of the external electronic device), and then may establish BT communication with the external electronic device through a paging process and a pairing process using the information associated with the external electronic device.

[0003] The electronic device may share information about at least one first external electronic device having a history of establishing BT communication with the electronic device (e.g., a BT address of the first external electronic device) with a second external electronic device that has no history of establishing 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 using the information about the first external electronic device sent from the electronic device without a query process.

[0004] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0005] Technical issues

[0006] There may be a situation in which the first external electronic device may reject a BT communication connection request from a second external electronic device whose address is unknown to the first external electronic device when the first external electronic device and the second external electronic device have no previous BT communication history. In this case, the second external electronic device cannot use information about the first external electronic device shared from another electronic device (e.g., the above-mentioned electronic device) to perform BT communication with the first external electronic device. Instead, the second external electronic device may have to perform a query process to receive a unique address of the first external electronic device from the first external electronic device, and only after the process can 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 a scenario in which the second external electronic device uses information about the first external electronic device shared from an electronic device.

[0007] According to one aspect of the present disclosure, an electronic device is provided. The electronic device may include: a user interface; a communication circuit configured to support Bluetooth (BT) communication and store a first BT address; a processor operably connected to the user interface and the communication circuit; and a memory operably connected to 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 circuit; end the communication connection with the first external electronic device; after ending the communication connection, receive a reconnection request based on the first BT address from the first external electronic device; in response to the reconnection request, send a communication connection request to the first external electronic device using the communication circuit based on a second BT address different from the first BT address; and store information about whether the first external electronic device accepts or rejects the communication connection request in the memory.

[0008] According to another aspect of the present disclosure, an electronic device is provided. The electronic device may include: a user interface; at least one communication circuit, the at least one communication circuit being configured to support Bluetooth (BT) communication; a processor, the processor being operably connected to the user interface and the at least one communication circuit; and a memory, the memory being operably connected to the processor. The memory may include instructions, which, when executed, cause the processor to: use the at least one communication circuit to receive first information about at least one second external electronic device to which a first external electronic device is connected via BT communication and second information about the probability that at least one second external electronic device will accept a connection request using an address with no connection history; and provide the second information through the user interface.

[0009] According to another aspect of the present disclosure, an electronic device is provided. The electronic device may include: a user interface; a communication circuit configured to support Bluetooth (BT) communication and store a first BT address; a processor operably connected to the user interface and the communication circuit; and a memory operably connected to the processor. The memory may store instructions that, when executed, cause the processor to: use the communication circuit to establish a communication connection with a first external electronic device based on the first BT address; use the communication circuit to send a communication connection request to the first external electronic device based on a second BT address different from the first BT address; and after the communication connection is established, information about whether the first external electronic device accepts or rejects the communication connection request based on the second BT address is stored in the memory.

[0010] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, together with the annexed drawings, discloses various embodiments of the disclosure.

[0011] Beneficial Effects

[0012] Therefore, an aspect of the present disclosure is to provide a method for sharing Bluetooth (BT) communication information to configure BT communication information including information indicating whether an external electronic device can perform BT communication based on a BT address in which there is no history of establishing BT communication, and an electronic device thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0014] Figure 1a is a block diagram illustrating an electronic device in a network environment according to various embodiments;

[0015] Figure 1b is a diagram illustrating a BT communication system according to an embodiment;

[0016] Figure 2 is a block diagram illustrating a configuration of an electronic device according to an embodiment;

[0017] Figure 3 is a block diagram illustrating a configuration of a second external electronic device according to an embodiment;

[0018] Figure 4a 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 having no connection history according to an embodiment;

[0019] Figure 4b is a flowchart illustrating a method for storing BT communication information at an electronic device according to an embodiment;

[0020] Figure 5a is a signal sequence chart illustrating a method for generating second information on whether a first external electronic device accepts a communication connection request based on a BT address having no connection history according to an embodiment;

[0021] Figure 5b , Figure 5c and Figure 5d is a signal sequence chart illustrating a method for generating second information regarding whether a first external electronic device rejects a communication connection request based on a BT address having no connection history according to an embodiment;

[0022] Figure 5e , Figure 5f and Figure 5g is a signal sequence diagram illustrating a method in which an electronic device does not receive a reconnection request from a first external electronic device according to an embodiment;

[0023] Figure 6 is a diagram illustrating an example of a UI screen for sharing registered device information according to an embodiment;

[0024] Figure 7 is a diagram illustrating another example of a UI screen for sharing registered device information according to an embodiment;

[0025] Figure 8 is a diagram illustrating an example of sharing registered device information at an electronic device according to an embodiment;

[0026] Fig. 9 is a diagram illustrating another example of sharing registered device information at an electronic device according to an embodiment;

[0027] Fig.10 is a diagram illustrating a UI screen for guiding a user to update registered device information at a second external electronic device according to an embodiment;

[0028] Fig.11a and Fig.11b is a diagram illustrating a UI screen for selecting a display scheme of registered device information according to an embodiment;

[0029] Fig.12a and Figure 12b is a diagram illustrating an example of displaying registered device information according to an embodiment; and

[0030] Fig.13 is a diagram illustrating a UI screen for sharing and using registered device information according to an embodiment. DETAILED DESCRIPTION

[0031] This application is based on and claims the benefit of priority under 35 USC §119 from Korean Patent Application No. 10-2019-0016150 filed on February 12, 2019, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference.

[0032] An aspect of the present disclosure is to solve at least the above-mentioned problems and / or disadvantages and to provide at least the following advantages. Therefore, an aspect of the present disclosure is to provide a method for sharing Bluetooth (BT) communication information to configure BT communication. The communication information may include information indicating whether an external electronic device can perform BT communication based on a BT address of an electronic device that has no BT communication history established.

[0033] Figure 1a 1 is a block diagram illustrating an electronic device 1401 in a network environment 1400 according to various embodiments. Figure 1a , the electronic device 1401 in the network environment 1400 may communicate with the electronic device 1402 via the first network 1498 (e.g., a short-range wireless communication network), or communicate with the electronic device 1404 or the server 1408 via the second network 1499 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 1401 may communicate with the electronic device 1404 via the server 1408. According to an embodiment of the present disclosure, the electronic device 1401 may include a processor 1420, a memory 1430, an input device 1450, a sound output device 1455, a display device 1460, an audio module 1470, a sensor module 1476, an interface 1477, a haptic module 1479, a camera module 1480, a power management module 1488, a battery 1489, a communication module 1490, a user identification module (SIM) 1496, or an antenna module 1497. In some embodiments, at least one of the components (e.g., display device 1460 or camera module 1480) may be omitted from electronic device 1401, or one or more other components may be added to electronic device 1401. In some embodiments, some of the components may be implemented as a single integrated circuit. For example, sensor module 1476 (e.g., fingerprint sensor, iris sensor, or illumination sensor) may be implemented as embedded in display device 1460 (e.g., display).

[0034] The processor 1420 may run, for example, software (e.g., program 1440) to control at least one other component (e.g., hardware component or software component) of the electronic device 1401 connected to the processor 1420, and may perform various data processing or calculations. According to one embodiment, as at least part of the data processing or calculation, the processor 1420 may load a command or data received from another component (e.g., sensor module 1476 or communication module 1490) into the volatile memory 1432, process the command or data stored in the volatile memory 1432, and store the result data in the non-volatile memory 1434. According to an embodiment, the processor 1420 may include a main processor 1421 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 1423 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is independent of or combined with the main processor 1421 in operation. Additionally or alternatively, the auxiliary processor 1423 may be adapted to consume less power than the main processor 1421, or to be adapted to be specifically used for a specified function. The auxiliary processor 1423 may be implemented as separate from the main processor 1421, or as part of the main processor 1421.

[0035] When the main processor 1421 is in an inactive (e.g., sleep) state, the auxiliary processor 1423 (rather than the main processor 1421) may control at least some of the functions or states related to at least one component (e.g., display device 1460, sensor module 1476, or communication module 1490) among the components of the electronic device 1401, or when the main processor 1421 is in an active state (e.g., running an application), the auxiliary processor 1423 may control at least some of the functions or states related to at least one component (e.g., display device 1460, sensor module 1476, or communication module 1490) among the components of the electronic device 1401 together with the main processor 1421. According to an embodiment of the present disclosure, the auxiliary processor 1423 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., camera module 1480 or communication module 1490) that is functionally related to the auxiliary processor 1423.

[0036] The memory 1430 may store various data used by at least one component of the electronic device 1401 (e.g., the processor 1420 or the sensor module 1476). The various data may include, for example, software (e.g., program 1440) and input data or output data for commands related thereto. The memory 1430 may include a volatile memory 1432 or a non-volatile memory 1434.

[0037] The program 1440 may be stored as software in the memory 1430 , and the program 1440 may include, for example, an operating system (OS) 1442 , middleware 1444 , or an application 1446 .

[0038] The input device 1450 may receive commands or data from outside the electronic device 1401 (e.g., a user) to be used by other components of the electronic device 1401 (e.g., the processor 1420). The input device 1450 may include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus).

[0039] The sound output device 1455 can output a sound signal to the outside of the electronic device 1401. The sound output device 1455 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as playing multimedia or playing records, and the receiver can be used for incoming calls. Depending on the embodiment, the receiver can be implemented as a separate part from the speaker, or as part of the speaker.

[0040] The display device 1460 may visually provide information to the outside (e.g., a user) of the electronic device 1401. The display device 1460 may include, for example, a display, a holographic device, or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. According to an embodiment, the display device 1460 may include a touch circuit adapted to detect a touch or a sensor circuit (e.g., a pressure sensor) adapted to measure the strength of a force caused by a touch.

[0041] The audio module 1470 may convert sound into an electrical signal, or vice versa. According to an embodiment, the audio module 1470 may obtain sound via the input device 1450, or output sound via a sound output device 1455 or an earphone of an external electronic device (e.g., electronic device 1402) directly (e.g., wired) connected to the electronic device 1401 or wirelessly connected thereto.

[0042] The sensor module 1476 may detect an operating state (e.g., power or temperature) of the electronic device 1401 or an environmental state (e.g., a user's state) outside the electronic device 1401, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 1476 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.

[0043] The interface 1477 may support one or more specific protocols that will be used to connect the electronic device 1101 directly (e.g., wired) or wirelessly to an external electronic device (e.g., the electronic device 1402). According to an embodiment, the interface 1477 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0044] The connection end 1478 may include a connector, wherein the electronic device 1401 can be physically connected to an external electronic device (e.g., the electronic device 1402) via the connector. According to an embodiment of the present disclosure, the connection end 1478 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0045] The haptic module 1479 may convert the electrical signal into mechanical stimulation (eg, vibration or motion) or electrical stimulation that can be recognized by the user via his sense of touch or kinesthetic sense. According to an embodiment, the haptic module 1479 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0046] The camera module 1480 may capture a still image or a moving image. According to an embodiment, the camera module 1480 may include one or more lenses, an image sensor, an image signal processor, or a flash.

[0047] The power management module 1488 may manage power supply to the electronic device 1401. According to one embodiment, the power management module 1488 may be implemented as at least part of a power management integrated circuit (PMIC), for example.

[0048] The battery 1489 may power at least one component of the electronic device 1401. According to an embodiment, the battery 1489 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0049] The communication module 1490 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 1401 and an external electronic device (e.g., electronic device 1402, electronic device 1404, or server 1408), and perform communication via the established communication channel. The communication module 1490 may include one or more communication processors capable of operating independently from the processor 1420 (e.g., an application processor (AP)) and supporting direct (e.g., wired) communication or wireless communication. According to an embodiment, the communication module 1490 may include a wireless communication module 1492 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 1494 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate with an external electronic device via a first network 1498 (e.g., a short-range communication network such as Bluetooth, Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA)) or a second network 1499 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules can be implemented as a single component (e.g., a single chip), or these various types of communication modules can be implemented as multiple components separated from each other (e.g., multiple chips). The wireless communication module 1492 can identify and authenticate the electronic device 1401 in a communication network (such as the first network 1498 or the second network 1499) using user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 1496.

[0050] The antenna module 1497 may transmit a signal or power to the outside of the electronic device 1401 (e.g., an external electronic device) or receive a signal or power from the outside of the electronic device 1401 (e.g., an external electronic device). According to an embodiment, the antenna module 1497 may include an antenna including a radiating element formed of a conductive material or a conductive pattern formed in or on a substrate (e.g., a PCB). According to an embodiment, the antenna module 1497 may include a plurality of antennas. In this case, at least one antenna suitable for a communication scheme used in a communication network (such as the first network 1498 or the second network 1499) may be selected from the plurality of antennas by, for example, the communication module 1490 (e.g., the wireless communication module 1492). Then, a signal or power may be transmitted or received between the communication module 1490 and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as a part of the antenna module 1497.

[0051] At least some of the above components may be connected to each other via an inter-peripheral communication scheme (e.g., a bus, a general purpose input output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) and communicatively transmit signals (e.g., commands or data) therebetween.

[0052] According to an embodiment, a command or data may be sent or received between the electronic device 1401 and the external electronic device 1404 via the server 1408 connected to the second network 1499. Each of the electronic device 1402 and the electronic device 1404 may be a device of the same type as the electronic device 1401, or a device of a different type from the electronic device 1401. According to an embodiment, all or some operations to be executed at the electronic device 1401 may be executed at one or more of the external electronic devices 1402, 1404, or 1408. For example, if the electronic device 1401 should automatically execute a function or service or should execute a function or service in response to a request from a user or another device, the electronic device 1401 may request the one or more external electronic devices to execute at least part of the function or service instead of executing the function or service, or the electronic device 1401 may request the one or more external electronic devices to execute at least part of the function or service in addition to executing the function or service. The one or more external electronic devices that receive the request may execute at least part of the requested function or service, or execute another function or another service related to the request, and transmit the result of the execution to the electronic device 1401. The electronic device 1401 may provide the result as at least a partial reply to the request in the case of further processing the result or in the case of not further processing the result. To this end, for example, cloud computing technology, distributed computing technology, or client-server computing technology may be used.

[0053] Figure 1b is a diagram illustrating a BT communication system according to an embodiment.

[0054] refer to Figure 1b According to an embodiment, the BT communication system 100 may include an electronic device 110 (eg, Figure 1a electronic device 1401), a first external electronic device 120 (eg, Figure 1a 1402), and a second external electronic device 130 (eg, Figure 1a electronic device 1404).

[0055] When there is no history of establishing BT communication with the first external electronic device 120, the electronic device 110 can establish BT communication with the first external electronic device 120 through an inquiry process, a paging process, and a pairing process based on the first BT address. The electronic device 120 can store the first information about the first external electronic device 120 obtained in the inquiry process in its memory, and then establish BT communication with the first external electronic device 120 in addition to the inquiry process. The first information about the first external electronic device 120 may include, for example, a BT address of the first external electronic device 120 and a name of the first external electronic device 120. The first BT address may be a unique address of the electronic device 110 used for BT communication. The BT address of the first external electronic device 120 may be a unique address of the first external electronic device 120 used for BT communication.

[0056] According to an embodiment, after establishing communication with the first external electronic device 120 based on the first BT address, the electronic device 110 may send a communication connection request to the first external electronic device 120 based on a second BT address different from the first BT address, and may identify whether the first external electronic device 120 accepts or rejects the communication connection request. The second BT address may be, for example, a BT address that has no history of establishing communication with the first external electronic device 120. The electronic device 110 may identify whether the first external electronic device 120 accepts or rejects the communication connection request based on the second BT address, and may store the second information about the probability that the first external electronic device 120 will accept the communication connection request (information about whether the first external electronic device 120 accepts or rejects the communication connection request) in a memory. For example, the electronic device 110 may associate the first information about the first external electronic device 120 (e.g., Bluetooth address and / or name) with the second information about the probability that the first external electronic device 120 will accept the communication connection request and store it in a memory. The second information about the probability that the first external electronic device 120 will accept the communication connection request may include, for example, information indicating whether the first external electronic device 120 will accept or reject a request to establish communication without an associated connection history. In another example, the second information may include information indicating whether the first external electronic device 120 accepts or rejects a communication connection request received from the electronic device 110 when the first external electronic device 120 is powered on (eg, when Bluetooth of the first external electronic device 120 is powered on).

[0057] According to an embodiment, the electronic device 110 may share (e.g., transmit) first information about at least one first external electronic device (e.g., the first external electronic device 120) with the second external electronic device 130. For example, the electronic device 110 may transmit first information about the first external electronic device 120 and second information about the probability of whether the first external electronic device 120 will accept a connection request based on a BT address with no connection history to the first external electronic device 120, the first information and the second information being associated with each other. According to an embodiment, the electronic device 110 may identify the probability that the first external electronic device 120 will accept a connection request based on the second BT address (identify whether the first external electronic device 120 accepts or rejects the connection request). When it is identified that the first external electronic device 120 will accept the connection request, the electronic device 110 may transmit the first information and the second information about the first external electronic device 120 to the second external electronic device 130. According to another embodiment, when it is identified that the first external electronic device 120 will reject the connection request, the electronic device 110 may prohibit the first information about the first external electronic device 120 from being transmitted to the second external electronic device 130. In an embodiment, when sharing first information about the first external electronic device 120 with the second external electronic device 130, the electronic device 110 may send the first information about the first external electronic device 120 directly to the second external electronic device 130 or may send the first information about the first external electronic device 120 to the second external electronic device 130 via another electronic device (e.g., an external server).

[0058] According to an embodiment, when receiving first information about the first external electronic device 120 and second information about the probability that the first external electronic device 120 will accept a connection request based on a BT address with no connection history from the electronic device 110, the second external electronic device 130 may provide the second information with the first information through a user interface and associate the two. In an embodiment, the second external electronic device 130 may be, for example, a device configured to have the same user account as the electronic device 110. For example, the second external electronic device 130 may be a device configured to have a personal account (e.g., a family account or a colleague account) associated with the user of the electronic device 110.

[0059] According to an embodiment, when an input associated with establishing BT communication between the second external electronic device 130 and the first external electronic device 120 is recognized (e.g., received), the second external electronic device 130 may send a BT address-based communication connection request of the second external electronic device 130 to the first external electronic device 120 using the first information about the first external electronic device 120. The first external electronic device 120 may accept the communication connection request of the second external electronic device 130, and the second external electronic device 130 and the first external electronic device 120 may establish BT communication.

[0060] According to the above-mentioned embodiments, each of the electronic device 110, the first external electronic device 120 and the second external electronic device 130 may be an electronic device capable of performing BT communication and may be, for example, a portable communication device (e.g., a 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., a BT headset).

[0061] According to the above-described embodiment, the electronic device 110 may configure BT communication information about the first external electronic device 120 that can establish BT communication based on an address with no history of establishing BT communication and may share the configured BT communication information with the second external electronic device 130. Alternatively, the electronic device 110 may configure BT communication information that identifies whether BT communication can be performed based on an address with no history of establishing BT communication and may share the configured BT communication information with the second external electronic device 130.

[0062] Figure 2 is a block diagram illustrating a configuration of an electronic device according to an embodiment.

[0063] refer to Figure 2 According to the electronic device 110 (eg, Figure 1b The electronic device 110 may include a user interface 210 (eg, Figure 1a display device 1460), communication circuit 220 (e.g., Figure 1a communication module 1490), memory 230 (e.g., Figure 1a 1430) and the processor 240 (e.g., Figure 1a In an embodiment, the electronic device 110 may exclude some components or may further include additional components. In an embodiment, some components of the electronic device 110 may be combined into one entity to perform the functions of the components in the same manner as before the combination.

[0064] According to an embodiment, the user interface 210 may include an input circuit and a display. The input circuit may include at least one of a touch sensor or a physical button. The display may include a display included in the electronic device 110 or a display included in another electronic device communicating with the electronic device 110. In this embodiment as an example, the user interface 210 is a touch screen display, i.e., a display combined with a touch sensor.

[0065] According to an embodiment, the communication circuit 220 may include at least one communication circuit configured to support BT communication. The communication circuit 220 may be configured with a first BT address. For example, the communication circuit 220 may include an integrated circuit for BT communication, and the integrated circuit may store the first BT address in its internal memory. The communication circuit 220 may also 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 110 used for BT communication. The second BT address may be, for example, an address different from the unique address of the electronic device 110 used for BT communication, and may be used for multiple electronic devices including the electronic device 110. The second BT address may be determined, for example, when the electronic device 110 is manufactured, and may be stored in the communication circuit 220. Alternatively, the second BT address may be randomly set by the processor 240 or may be set by the processor 240 based on at least a portion 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 110). For example, the second BT address may be set based on the BT address of a device configured to have the same user account as the electronic device 110. According to an embodiment, the second BT address may be stored in the memory 230.

[0066] According to an embodiment, the memory 230 may store instructions, which, when executed, cause the processor 240 to: communicate with the first external electronic device (eg, Figure 1b The method includes: establishing a communication connection with the first external electronic device 120 of the electronic device 110; ending the communication connection with the first external electronic device 120; receiving a reconnection request based on the first BT address from the first external electronic device 120 after ending the communication connection; sending a communication connection request to the first external electronic device 120 based on a second BT address different from the first BT address using the communication circuit 220 in response to the reconnection request; and storing second information about the probability that the first external electronic device 120 will accept or reject the communication connection request in the memory 230. The memory 230 may store, for example, commands or data associated with at least one other component of the electronic device 110. The memory 230 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.

[0067] The processor 240 may use the instructions stored in the memory 230 to perform calculations or data processing related to the control and / or communication of at least one other component of the electronic device 110. The processor 240 may include a microprocessor or any suitable type of processing circuit, such as one or more general-purpose processors (e.g., ARM-based processors), digital signal processors (DSPs), programmable logic devices (PLDs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), graphics processing units (GPUs), graphics card controllers, etc. In addition, it will be recognized that when a general-purpose computer accesses the code for implementing the processing shown herein, the execution of the code converts the general-purpose computer into a special-purpose computer for performing the processing shown herein. Certain functions and steps provided in the figure may be implemented in hardware, software, or a combination of both, and may be executed in whole or in part within the programming instructions of a computer. No claim element here can be interpreted according to the provisions of 35 U.S.C. §112 (f) unless the element is explicitly described using the phrase "means for..." In addition, the technician understands and appreciates that a "processor" or "microprocessor" may be hardware claimed for protection in the present disclosure. According to the broadest reasonable interpretation, the attached claims are statutory subject matter in accordance with 35 U.S.C. §101.

[0068] According to an embodiment, the processor 240 may establish a communication connection with the first external electronic device 120 based on the first BT address using the communication circuit 220, and may end the communication connection with the first external electronic device 120. For example, when receiving an input associated with the communication connection of the first external electronic device 120 through the user interface 210, the processor 240 may establish a communication connection with the first external electronic device 120 based on the first BT address using the communication circuit 220. The communication connection between the electronic device 110 and the first external electronic device 120 may be intentionally ended by the user of the electronic device 110 or the first external electronic device 120, or may be ended due to various factors, such as degradation of the signal strength of the electronic device 110 or the first external electronic device 120 or an increase in the separation distance between the electronic device 110 and the first external electronic device 120. In an embodiment, the processor 240 may store the first information about the first external electronic device 120 obtained in the communication connection process (e.g., the query process) based on the first BT address in the memory 230. The first information about the first external electronic device 120 may include, for example, the BT address of the first external electronic device 120 and / or the name of the first external electronic device 120.

[0069] According to an embodiment, when a reconnection request based on a first BT address is received from the first external electronic device 120 after the communication connection with the first external electronic device 120 is terminated, the processor 240 may send a communication connection request to the first external electronic device 120 based on a second BT address using the communication circuit 220 in response to the reconnection request. Thereafter, the processor 240 may identify whether the first external electronic device 120 accepts or rejects the communication connection request. For example, when a response to the communication connection request is received from the first external electronic device 120 within a specified time after the communication connection request is sent, the processor 240 may identify that the first external electronic device 120 has accepted the communication connection request. Otherwise, the processor 240 may identify that the first external electronic device 120 has rejected the communication connection request. The response may include, for example, at least one of a setup completion event, an authentication success event, an encryption event, or a service discovery protocol (SDP) completion. The specified time may be experimentally set based on the average time to establish BT communication.

[0070] According to an embodiment, the processor 240 may store the second information about the probability that the first external electronic device 120 will accept or reject the connection request based on the BT address (e.g., the second BT address) without a connection history in the memory 230. For example, the processor 240 may associate the first information about the first external electronic device 120 with the second information about the probability that the first external electronic device 120 will accept the connection request and store it in the memory 230. In another example, the processor 240 may store the registered device information, including the first information about at least one first external electronic device (e.g., the first external electronic device 120) and the second information about the probability that the at least one first external electronic device will accept the connection request, in the memory (e.g., a lookup table of the memory 230). The first information about the at least one first external electronic device may be obtained by the processor 240 using the communication circuit 220 by communicating with each of the at least one first external electronic device based on the first BT address. The second information about the probability that the at least one first external electronic device will accept the connection request may be obtained by the processor 240 using the communication circuit 220 by communicating with each of the at least one first external electronic device based on the second BT address.

[0071] According to an embodiment, after storing the second information about the probability that the first external electronic device 120 will accept the connection request in the memory 230, the processor 240 may establish communication with the first external electronic device 120 based on the first BT address using the communication circuit 220 (hereinafter referred to as "first BT communication"). For example, when the first external electronic device 120 accepts the communication connection request based on the second BT address, the processor 240 may store the second information about the first external electronic device 120 accepting the communication connection request in the memory 230 and may establish communication with the first external electronic device 120 based on the second BT address using the communication circuit 220 (hereinafter referred to as "second BT communication"). Thereafter, the processor 240 may end the second BT communication connection with the first external electronic device 120 and may establish the first BT communication connection with the first external electronic device 120. In another example, when the first external electronic device 120 rejects the communication connection request based on the second BT address, the processor 240 may store information about the first external electronic device 120 rejecting the communication connection request in the memory 230. Thereafter, the processor 240 may establish the first BT communication connection with the first external electronic device 120 based on the first BT address. In yet another example, after storing the second information about the probability that the first external electronic device accepts the communication connection request in the memory 230, the processor 240 may receive a reconnection request based on the first BT address from the first external electronic device 120. In this case, the processor 240 may respond to the reconnection request based on the first BT address and may establish a first BT communication connection with the first external electronic device 120.

[0072] According to an embodiment, the processor 240 may use the communication circuit 220 to communicate with a second external electronic device (eg, Figure 1bThe processor 240 may share (e.g., send) at least a portion of the registered device information with the second external electronic device 130 of the user interface 210. For example, the processor 240 may send the first information about one or more first external electronic devices included in the registered device information and the second information about the probability that the first external electronic device will accept or reject the communication connection request to the second external electronic device 130. In another example, the processor 240 may send the first information about the first external electronic device selected by the user interface 210 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 130. In yet another example, the processor 240 may selectively send the first information about the first external electronic device among the multiple first external electronic devices 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) 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 130. The processor 240 may make a selection based on the second information about the probability that the first external electronic device will accept the communication connection request.

[0073] In the above exemplary embodiment, when a reconnection request is received from the first external electronic device 120 after the first BT communication with the first external electronic device 120 is terminated, the processor 240 sends a communication connection request based on the second BT address. However, the present disclosure is not limited thereto. For example, when a communication based on the first BT address is established with the first external electronic device 120, the processor 240 may send a communication connection request based on the second BT address to the first external electronic device 120. In another example, when the first BT communication is established with the first external electronic device 120, the processor 240 may intentionally end the first BT communication connection and may send a communication connection request to the first external electronic device 120 based on the second BT address. In yet another example, after the communication connection with the first external electronic device 120 based on the first BT address is terminated, the processor 240 may send a communication connection request to the first external electronic device 120 based on the second BT address at a specified time. The specified time may be specified periodically or may be the time when the processor 240 performs the query process.

[0074] According to the above embodiment, the electronic device 110 can configure BT communication information (registered device information) for notifying the user whether the first external electronic device accepts a communication connection request based on a BT address (e.g., a second BT address) in which there is no connection history. Therefore, the attempt and failure of the second external electronic device 130 that receives the registered device information from the electronic device 110 to establish a communication connection with the first external electronic device 120 can be prevented. This reduces the inconvenience of a failed BT communication connection.

[0075] Figure 3is a block diagram illustrating a configuration of a second external electronic device according to an embodiment.

[0076] refer to Figure 3 According to the second external electronic device 130 (eg, Figure 1b The second external electronic device 130 may include a user interface 310 (eg, Figure 1a display device 1460), communication circuit 320 (e.g., Figure 1a communication module 1490), memory 330 (e.g., Figure 1a 1430) and the processor 340 (e.g., Figure 1a In an embodiment, the second external electronic device 130 may exclude some components or may further include additional components. In an embodiment, some components of the second external electronic device 130 may be combined into one entity to perform the functions of the components in the same manner as before the combination.

[0077] According to an embodiment, the user interface 310 may include an input circuit and a display. The input circuit 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 130 or a display included in another electronic device communicating with the second external electronic device 130. In this embodiment as an example, the user interface 310 is a touch screen display, i.e., a display combined with a touch sensor.

[0078] According to an embodiment, the communication circuit 320 may include at least one communication circuit configured to support BT communication. The communication circuit 320 may be configured with a third BT address. For example, the communication circuit 320 may include an integrated circuit for BT communication, and the third BT address may be stored 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 130 for BT communication.

[0079] The memory 330 may include instructions that, when executed, cause the processor 340 to receive information about an electronic device (e.g., Figure 2 The electronic device 110) is connected to at least one first external electronic device (eg, Figure 1b The memory 230 may store, for example, commands or data associated with at least one other component of the second external electronic device 120, and second information about the probability that the at least one first external electronic device will accept a connection request using an address with no connection history, and provide the second information via the user interface 310. The memory 230 may store, for example, commands or data associated with at least one other component of the second external electronic device 130. The memory 330 may be a volatile memory (e.g., RAM), a nonvolatile memory (e.g., ROM or flash memory), or a combination thereof.

[0080] The processor 340 may use the instructions stored in the memory 330 to perform calculations or data processing regarding control and / or communication of at least one other component of the second external electronic device 130. The processor 340 may include, for example, at least one of a CPU, a GPU, a microprocessor, an application processor, an ASIC, or an FPGA and may have a plurality of cores.

[0081] According to an embodiment, the processor 340 may receive first information about at least one first external electronic device to which the electronic device 110 is connected via BT communication and second information about the probability that the at least one first external electronic device will accept a connection request using an address with no connection history from the electronic device 110 via the communication circuit 320. For example, when the electronic device 110 sends the registered device information, the processor 340 may receive the registered device information. In another example, when an input associated with receiving the registered device information is received via the user interface 310, the processor 340 may send a request associated with sending the registered device information to the electronic device 110, and may receive at least a portion of the registered device information as a response to the request from the electronic device 110.

[0082] According to an embodiment, when receiving first information about at least one first external electronic device and second information about the probability that at least one first external electronic device will accept a connection request, the processor 340 may provide a screen allowing a user to select at least a portion of the first information and the second information received via the user interface 310. The processor 340 may store the first information and the second information selected through the screen in the memory 330.

[0083] According to an embodiment, when the registered device information is received, the processor 340 may provide first guide information for providing a notification that the reception of the registered device information is completed via the user interface 310. In addition, the processor 340 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 310. In this case, the processor 340 may provide the updated registered device information via the user interface 310 in response to an input associated with selecting the second guide information.

[0084] According to an embodiment, the processor 340 may provide second information about the probability that at least one first external electronic device will accept the connection request via the user interface 310. For example, the processor 340 may classify at least one first external electronic device into a first type of first external electronic device currently connected via BT communication, a second type of first external electronic device capable of establishing a BT communication connection based on an address in which there is no connection history, and a third type of first external electronic device that cannot establish a BT communication connection based on an address in which there is no connection history. The processor 340 may provide first information about at least one first external electronic device in the above classification (e.g., one of the first type to the third type) via the user interface 310. For example, the processor 340 may display first information about a first external electronic device of the first type in blue, may display first information about a first external electronic device of the second type in black, and may display first information about a first external electronic device of the third type in gray. According to another embodiment, the processor 340 may display first information about a first external electronic device of the first type and first information about a first external electronic device of the second type, and may not display first information about a first external electronic device of the third type.

[0085] According to an embodiment, when an input associated with a connection request for one of at least one first external electronic device is received via the user interface 310, the processor 340 may establish a communication connection based on a third BT address using first information about the first external electronic device (e.g., the BT address of the first external electronic device) corresponding to the input associated with the connection request.

[0086] According to the above-described embodiment, the second external electronic device 130 can provide registered device information including second information about the probability that at least one first external electronic device 120 will accept a connection request using an address having no connection history. Therefore, when attempting to establish a BT communication connection using the registered device information, the user of the second external electronic device 130 can easily identify the first external electronic device to which the second external electronic device 130 can be connected.

[0087] Figure 4a 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 having no connection history according to an embodiment.

[0088] refer to Figure 4a In operation 410, an electronic device (eg, Figure 2 The electronic device 110 may be connected to the communication circuit (eg, Figure 2 The communication circuit 220) uses the first BT address to communicate with the first external electronic device (eg, Figure 1b The first BT address may be, for example, a unique address of the electronic device 110 for BT communication. In operation 410, the electronic device 110 may store first information about the first external electronic device 120 in a memory (eg, Figure 2 For example, the first information about the first external electronic device 120 may include a BT address and / or a name of the first external electronic device.

[0089] In operation 420, the electronic device 110 may end the communication connection with the first external electronic device 120. In operation 420, the communication connection may be intentionally ended by a user of the electronic device 110 or the first external electronic device 120, or may be ended due to various factors, such as degradation of signal strength of the electronic device 110 or the first external electronic device 120 or an increase in a separation distance between the electronic device 110 and the first external electronic device 120.

[0090] In operation 430 , after ending the communication connection with the first external electronic device 120 , the electronic device 110 may receive a reconnection request based on the first BT address from the first external electronic device 120 .

[0091] In operation 440, in response to the reconnection request, the electronic device 110 may send a communication connection request to the first external electronic device 120 based on a second BT address different from the first BT address using the communication circuit 220. For example, the second BT address may be an address that has no history of establishing a communication connection with the first external electronic device 120.

[0092] In operation 450, the electronic device 110 may recognize that the first external electronic device 120 accepts the communication connection request based on the second BT address. When the first external electronic device 120 accepts the communication connection request based on the second BT address, the electronic device 110 may establish BT communication with the first external electronic device 120 based on the second BT address.

[0093] In operation 460, the electronic device 110 may store second information about the probability that the first external electronic device 120 will accept the communication connection request in the memory 230. For example, the electronic device 110 may associate the first information about the first external electronic device 120 with the second information about the probability that the first external electronic device 120 will accept the communication connection request and store it in the memory 230. The second information about the probability that the first external electronic device 120 will accept the communication connection request may include, for example, information indicating whether the first external electronic device 120 accepts or rejects a request to establish a BT communication without a connection history. In another example, the second information about the probability that the first external electronic device 120 will accept the communication connection request may include information indicating whether the first external electronic device 120 accepts or rejects a communication connection request received from the electronic device 110 when the first external electronic device 120 is powered on (e.g., Bluetooth is powered on).

[0094] After operation 460, the electronic device 110 may transmit a reconnection request based on the first BT address to the first external electronic device 120, and may establish a communication connection with the first external electronic device 120 in response to the reconnection request.

[0095] According to another embodiment, in operation 430, the electronic device 110 may not receive a reconnection request based on the first BT address from the first external electronic device 120, and may send a reconnection request based on the second BT address to the first external electronic device 120. In this case, operation 440 may be omitted.

[0096] According to yet another embodiment, after ending the communication connection with the first external electronic device 120 in operation 420, the electronic device 110 may immediately send a reconnection request based on the second BT address to the first external electronic device 120, as shown in operation 440. In this case, operation 430 may be omitted.

[0097] Figure 4b is a flowchart illustrating a method for storing BT communication information at an electronic device according to an embodiment.

[0098] refer to Figure 4b In operation 470, an electronic device (eg, Figure 1b The electronic device 110) can use the first BT address to communicate with the first external electronic device (eg, Figure 1b The first BT address may be, for example, a unique address of the electronic device 110 for BT communication. In operation 470, the electronic device 110 may store the first information about the first external electronic device 120 in a memory (eg, Figure 2For example, the first information about the first external electronic device 120 may include a BT address and / or a name of the first external electronic device 120.

[0099] In operation 480, the electronic device 110 may transmit a communication connection request to the first external electronic device 120 based on the second BT address. The second BT address may be an address that has no history of establishing a communication connection with the first external electronic device 120.

[0100] In operation 490, the electronic device 110 may store second information about whether the first external electronic device 120 accepts or rejects the communication connection request based on the second BT address. For example, the electronic device 110 may identify whether the first external electronic device 120 accepts or rejects the communication connection request based on the second BT address, and may store information about the identified acceptance or rejection.

[0101] Figure 5a is a signal sequence diagram illustrating a method for generating second information on whether the first external electronic device accepts a communication connection request based on a BT address with no connection history according to an embodiment. The electronic device 110 may include a host (eg, an application processor) and a client (eg, a call processor). Figure 5a The operation may be performed by the client. Here, before operation 510, 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 120 will accept or reject a communication connection request from the host based on a BT address with no connection history. The client may perform the following based on the received command: Figure 5a In this case, the client may send information associated with the completion of operation 540 to the host, and may stop executing by receiving a command from the host to stop identifying information. Figure 5a In another embodiment, when the client is initialized, it can perform Figure 5a operation even if it does not receive commands from the host.

[0102] refer to Figure 5a, in operation 510, the electronic device 110 may receive a reconnection request from the first external electronic device 120. The two devices together have a history of establishing a first BT communication connection. For example, when an ID packet with a first access code is received from the first external electronic device 120 in operation 511, the electronic device 110 may send an ID packet with the first access code in response in operation 512. The first access code (device access code (DAC) for the device under test (DUT)) may be generated based on the unique address of the electronic device 110 for BT communication (the low address portion "LAP" of the first BT address). When receiving the ID packet with the first access code, the first external electronic device 120 may send the BT address of the first external electronic device 120 and the FHS packet with the first access code in operation 513. Despite receiving the FHS packet with the first access code, in operation 514, the electronic device 110 may not be able to send an ID packet with the first access code in response to the FHS packet. In operation 520, in response to the reconnection request of the first external electronic device 120, the electronic device 110 may send a communication connection request based on a second BT address (an address different from the first BT address) to the first external electronic device 120. For example, the electronic device 110 may send an ID packet with a second access code (DAC for peer) in response to the reconnection request in operation 521, and may receive an ID packet with the second access code from the first external electronic device in operation 522 as a response. The electronic device 110 may send an FHS packet with a second BTS address in operation 523 and may receive an ID packet with a second access code from the first external electronic device 120 in operation 524 as a response. Thereafter, in operations 525 and 526, the electronic device 110 and the first external electronic device 120 may exchange a first poll and a first null value based on the second BT address.

[0103] In operation 530, the electronic device 110 may identify that the first external electronic device 120 accepts (or rejects) the communication connection request based on the second BT address. For example, when it is identified in operation 531 after sending the communication connection request based on the second BT address that the authentication by the first external electronic device 120 succeeds within a specified time, the electronic device 110 may determine that the first external electronic device 120 accepts the communication connection request. After identifying that the first external electronic device 120 accepts or rejects the communication connection request based on the second BT address, the electronic device 110 may store second information about whether the first external electronic device 120 accepts or rejects the communication connection request in a memory (e.g., Figure 2After recognizing that the first external electronic device 120 accepts or rejects the communication connection request based on the second BT address, the electronic device 110 may release the communication connection based on the second BT address in operation 533.

[0104] In operation 540, the electronic device 110 may establish a communication connection based on the first BT address. The electronic device 110 may send a reconnection request based on the BT address of the first external electronic device 120 to the first external electronic device 120 to reconnect with the first external electronic device 120, and may establish a communication connection with the first external electronic device 120 in response. For example, the electronic device 110 may send an ID packet with a second access code (peer DAC) in operation 541, and may receive an ID packet with a second access code from the first external electronic device 120 in operation 542 in response. Thereafter, the electronic device 110 may send an FHS packet with a first BT address in operation 543, and may receive an ID packet with a second access code from the first external electronic device 120 in operation 544 in response. Thereafter, the electronic device 110 may exchange a first poll and a first null value with the first external electronic device 120 based on the first BT address in operations 545 and 546, and may establish a communication connection with the first external electronic device 120.

[0105] Figure 5b to Figure 5d is a signal sequence chart illustrating a method for generating second information regarding whether a first external electronic device rejects a communication connection request based on a BT address having no connection history according to an embodiment.

[0106] Figure 5b Includes operation 550 instead of Figure 5a Operation 530. Figure 5c Include operation 560 instead of Figure 5a Operation 530. Figure 5d Include operation 520' instead of Figure 5a Operation 520. Figure 5b to Figure 5d and Figure 5a The difference is that operation 530 is omitted. This difference will be described below.

[0107] refer to Figure 5b In operation 550, the electronic device 110 may recognize that the first external electronic device 120 has failed to authenticate the communication connection request based on the second BT address. In this case, the electronic device 110 may determine that the first external electronic device 120 has rejected the communication connection request based on the BT address with no connection history, and may associate the second information about the first external electronic device 120 rejecting the communication connection request with the first information about the first external electronic device 120 and store it in a memory (e.g., Figure 2 in the memory 230).

[0108] refer to Figure 5c , in operation 561, the electronic device 110 may recognize that the first external electronic device 120 successfully authenticates the communication connection request based on the second BT address. However, in operation 562, the electronic device 110 may recognize that the first external electronic device 120 has not yet been connected. In this case, the electronic device 110 may determine that the first external electronic device 120 has rejected the communication connection request based on the BT address with no connection history, and may associate the second information about the first external electronic device 120 rejecting the communication connection request with the first information about the first external electronic device 120 and store it in the memory 230.

[0109] refer to Figure 5d , in operation 520', the electronic device 110 may send an ID packet with a second access code (peer DAC) in response to the reconnection request of the first external electronic device 120 in operation 521, and may receive an ID packet with the second access code from the first external electronic device 120 in response in operation 522. The electronic device 110 may send an FHS packet with a second BT address in operation 523, and may not receive an ID packet with the second access code from the first external electronic device 120 in operation 524'. In this case, the electronic device 110 may determine that the first external electronic device 120 has rejected the communication connection request based on the BT address with no connection history, and may associate the second information about the first external electronic device 120 rejecting the communication connection request with the first information about the first external electronic device 120 and store it in the memory 230.

[0110] Figure 5e to Figure 5g is a signal sequence diagram illustrating a method in which an electronic device does not receive a reconnection request from a first external electronic device according to an embodiment.

[0111] Figure 5e to Figure 5g and Figure 5a The difference is Figure 5e Includes operation 510b instead of Figure 5a Operation 510, Figure 5f Includes operation 510c instead of Figure 5a Operation 510, Figure 5g Includes operation 510d instead of Figure 5a Operation 510. Therefore, this difference will be described below.

[0112] refer to Figure 5e, in operation 511, the electronic device 110 may receive an ID packet with a first access code from a first external electronic device 120 having a history of establishing a first BT communication connection. In operation 512, the electronic device 110 may send an ID packet with a first access code in response. When receiving the ID packet with the first access code, in operation 513, the first external electronic device 120 may send the BT address of the first external electronic device 120 and the FHS packet with the first access code. In operation 515, the electronic device 110 may send an ID packet with a second access code (peer DAC). In operations 516 and 517, the electronic device 110 may exchange a first poll and a first null value with the first external electronic device 120 based on the first BT address. In operation 518, the electronic device 110 may prohibit the execution of subsequent operations such as authentication and may wait until the communication connection expires.

[0113] refer to Figure 5f , in operation 511, the electronic device 110 may receive an ID packet with a first access code from a first external electronic device 120 having a history of establishing a first BT communication connection. In operation 512, the electronic device 110 may send an ID packet with the first access code in response. When receiving the ID packet with the first access code, in operation 513, the first external electronic device 120 may send the BT address of the first external electronic device 120 and the FHS packet with the first access code. In operation 515, the electronic device 110 may send an ID packet with a second access code (peer DAC). In operations 516 and 517, the electronic device 110 may exchange a first poll and a first null value with the first external electronic device 120 based on the first BT address. In operation 519, the electronic device 110 may release the communication connection with the first external electronic device 120.

[0114] refer to Figure 5g , in operation 511, the electronic device 110 may receive an ID packet with a first access code from a first external electronic device 120 having a history of establishing a first BT communication connection. In operation 512, the electronic device 110 may send an ID packet with the first access code in response. When receiving the ID packet with the first access code, in operation 513, the first external electronic device 120 may send the BT address of the first external electronic device 120 and the FHS packet with the first access code. In operation 515, the electronic device 110 may send an ID packet with a second access code (peer DAC). In operations 516 and 517, the electronic device 110 may exchange a first poll and a first null value with the first external electronic device 120 based on the first BT address. Thereafter, the electronic device 110 may perform Figure 5a Operations 520 to 540.

[0115] Figure 6 is a diagram illustrating an example of a UI screen for sharing registered device information according to an embodiment. Figure 6 An example of sharing registered device information using a designated application (app) of the electronic device 110 is illustrated.

[0116] refer to Figure 6 In reference numeral 610, when receiving an input associated with running a specified application, the electronic device 110 may run the specified application, which is referred to as a "smart switch" in this embodiment. The specified application may be an application that provides a function of sharing registered device information.

[0117] In reference numeral 620, when the designated application is running, the electronic device 110 may provide a virtual button for selecting a registered device information transmission method. The virtual button may include, for example, a virtual button 621 for selecting a first method using USB communication, a virtual button 623 for selecting a second method using wireless communication (e.g., Wi-Fi or BT), and a virtual button 625 for selecting a third method using an external memory (e.g., an SD card or USB storage).

[0118] In reference numeral 630, when one of the first method to the third method is selected by the user input, the electronic device 110 may provide first information 631 about at least one first external electronic device and a virtual button 633 for selecting the first information about at least some of the at least one first external electronic device. The first information may be transmitted to the second external electronic device 130. The electronic device 110 may transmit only the first information about the first external electronic device selected using the virtual button 633 to the second external electronic device 130. For example, when the virtual button 621 for selecting the first method is selected, the electronic device 110 may transmit the first information about the selected first external electronic device to the second external electronic device 130 connected to the electronic device 110 through USB communication. In another example, when the virtual button 623 for selecting the second method is selected, the electronic device 110 may transmit the first information about the selected first external electronic device to the second external electronic device 130 connected to the electronic device 110 through wireless communication. In yet another example, when the virtual button 625 for selecting the third method is selected, the electronic device 110 may store the first information about the selected first external electronic device in an external memory of the electronic device 110. The external memory may then be transferred to the second external electronic device 130 such that the first information is transmitted via the external memory.

[0119] Figure 7 is a diagram illustrating another example of a UI screen for sharing registered device information according to an embodiment.

[0120] refer to Figure 7 , after sending the registered device information to the second external electronic device 130, the electronic device 110 may provide a notification that the transmission of the registered device information is completed. For example, reference numeral 710 may include information 711 for providing a notification that the transmission of the registered device information is completed and the transmitted (shared) first information 713 about at least one first external electronic device. Reference numeral 710 may also include information 715 for selecting to delete or retain the transmitted first information 713 about at least one first external electronic device after the electronic device 110 sends the first information 713 to the second external electronic device 130. When the transmitted first information 713 is selected to be deleted, the electronic device 110 may no longer receive further connection requests and notifications from at least one first external electronic device. According to another embodiment, when the first information 713 about the first external electronic device matches a specific condition such as a specific time or a specific place, the electronic device 110 may be configured to receive a connection request and notification from at least one first external electronic device.

[0121] After receiving the first information about at least one first external electronic device from the electronic device 110, the second external electronic device 130 may provide a notification that the reception of the first information 723 about the at least one first external electronic device is completed. For example, reference numeral 720 may include information 721 for providing a notification that the reception of the first information 723 about the at least one first external electronic device is completed, the received first information 723 about the at least one first external electronic device, and a virtual button 725 for selecting the first information about the first external electronic device to be stored in the memory of the second external electronic device 130. The first information about the first external electronic device may include information 723a and information 723b, wherein the information 723a indicates a second type of first external electronic device capable of establishing a BT communication connection based on an address having no connection history, and the information 723b indicates a third type of first external electronic device incapable of establishing a BT communication connection based on an address having no connection history.

[0122] When a request associated with storing the first information about the selected first external electronic device is identified (e.g., the virtual button 727 is selected), the second external electronic device 130 may store only the first information 725a and 725b about the selected first external electronic device in the memory (e.g., Figure 3In this case, the second external electronic device 130 may send a request to the electronic device 110 to release the previous connection with the first external electronic device 120 or to stop the scanning operation for the first external electronic device 120. In response to the request, the electronic device 110 may release the previous connection with the first external electronic device 120 and may stop the scanning operation.

[0123] According to another embodiment, after sharing the first information about at least one first external electronic device with the second external electronic device 130, the electronic device 110 may still store the first information about at least one first external electronic device. In this case, when the second external electronic device 130 attempts to establish a BT communication connection based on the first information about at least one first external electronic device, the electronic device 110 may scan at least one first external electronic device and may interfere with the BT communication between the second external electronic device 130 and the first external electronic device. To prevent it, when matching a specified condition, the electronic device 110 may prohibit the establishment of a BT communication connection based on the first information about at least one first external electronic device. As an example, when the electronic device 110 is close to the second external electronic device 130 within a specified distance, when the electronic device 110 shares the first information about at least one first external electronic device, the first specified time interval has not passed or when the electronic device 110 receives a request to stop the communication connection based on the first information about at least one first external electronic device, the electronic device 110 may avoid establishing a BT communication connection based on the first information about at least one first external electronic device. The electronic device 110 may receive information about an intermediate device (e.g., an access point or a base station) accessed by the second external electronic device 130 or location information (GPS information) of the second external electronic device 130, and may determine whether there is an intermediate device located in the same space as the second external electronic device 130. According to another embodiment, the electronic device 110 may receive information about an intermediate device (e.g., an access point or a base station) accessed by the second external electronic device 130 or location information (GPS information) of the second external electronic device 130. Fig. 9 The external server 400) receives the intermediate device information and location information.

[0124] Figure 8 is a diagram illustrating an example of sharing registered device information at an electronic device according to an embodiment.

[0125] refer to Figure 8 , the electronic device 110 may transmit the registered device information about the first external electronic device 120 to the second external electronic devices 130_1 and 130_2 , so that the second external electronic devices 130_1 and 130_2 may easily establish a BT communication connection with the first external electronic device 120 .

[0126] For example, when the BT detailed setting of the first external electronic device 120 called “Level U Flex” included in the registered device information is selected, the electronic device 110 may display a screen 810 including a designated electronic device list 811 including devices capable of sharing the first information about the first external electronic device 120 and a screen for selecting devices included in the designated electronic device list.

[0127] Virtual buttons 813 of at least some of the electronic devices in 811. Designated electronic devices

[0128] The list 811 may include, for example, at least one designated electronic device that is capable of BT communication and is configured to have the same user account as the electronic device 110 or an account of a person associated with the electronic device 110. The designated electronic device list 811 may be received from, for example, an external server (e.g., a server that manages a user account set in the electronic device 110).

[0129] As indicated by reference numerals 821 and 823 , the electronic device 110 may transmit first information about the first external electronic device 120 to a first designated electronic device (eg, Galaxy Tab S3) 130_1 and a second designated electronic device (eg, Galaxy S9) 130_2 , which are selected by the virtual button 813 .

[0130] According to another embodiment, the electronic device 110 may communicate with the external server (eg, Fig. 9 The external server 400) shares the first information about the first external electronic device 120 with the first designated electronic device 130_1 and the second designated electronic device 130_2.

[0131] Fig. 9 is a diagram illustrating another example of sharing registered device information at an electronic device according to an embodiment.

[0132] refer to Fig. 9 In response to the request for the registered device information, the electronic device 110 may send the registered device information to the designated electronic device via the external server 400 .

[0133] In operation 910, when an input 915 associated with a request for registered device information is recognized, the electronic device 110 may request the external server 400 to share the registered device information with the specified electronic device. According to the request, the electronic device 110 may send the registered device information to the external server 400. The external server 400 may be, for example, a server that manages a user account set in the electronic device 110.

[0134] In operation 920, when receiving the registered device information from the electronic device 110, the external server 400 may search for a designated electronic device corresponding to the registered device information. The designated electronic device may include, for example, a device supporting BT communication in an electronic device configured to have the same user account as the electronic device 110.

[0135] In operation 930, the external server 400 may send the registered device information to the designated electronic device corresponding to the registered device information. According to another embodiment, when the received registered device information is not updated (e.g., the same as the previously received registered device information), the electronic device 110 or the external server 400 may prohibit sending the registered device information to the external server 400 or the designated electronic device.

[0136] According to another embodiment, when there is previously stored registered device information, the electronic device 110 may receive updated registered device information from the external server 400 in response to the input 915 and may store the updated registered device information.

[0137] According to another embodiment, the electronic device 110 may transmit the registered device information to the designated electronic device without intervention of the external server 400 .

[0138] Fig.10 is a diagram illustrating a UI screen for guiding a user to update registered device information at a second external electronic device according to an embodiment.

[0139] refer to Fig.10 , the second external electronic device 130 (eg, Figure 3 The second external electronic device 130 can be from an electronic device (eg, Figure 2 electronic device 110) or an external server (e.g., Fig. 9 The external server 400 receives information about the first external electronic device (eg, Figure 1b The first information about the first external electronic device 120 may be received and a screen for notifying a user of the received first information about the first external electronic device 120 may be output.

[0140] In reference numeral 1010, when receiving first information about the first external electronic device 120 and second information about the probability that the first external electronic device 120 will accept a connection request from the external server 400, the second external electronic device 130 can output a notification bar 1001 for notifying the user that the registered device information is updated.

[0141] In reference numeral 1020, the second external electronic device 130 may display registered device information 1023 including first information 1021 about the first external electronic device 120 received from the electronic device 110 based on an input associated with selecting the notification bar 1001. An icon 1025 for displaying a detailed setting screen for BT communication of each electronic device may be further included in the periphery of the first information of each electronic device included in the registered device information 1023 (e.g., first information about the first external electronic device 120).

[0142] Fig.11a and Fig.11b is a diagram illustrating a UI screen for selecting a display scheme of registered device information according to an embodiment.

[0143] refer to Fig.11a and Fig.11b , when the registered device information is received, the second external electronic device 130 may output a UI screen (eg, UI screen 1110 ) for querying a display manner of the received registered device information.

[0144] refer to Fig.11a , for example, when a Figure 2 When the electronic device 110 receives the registration device information, the second external electronic device 130 (eg, Figure 2 The second external electronic device 130) may output a UI screen 1110 for querying the display mode of the registered device information. On the UI screen 1110, the second external electronic device 130 may display a first virtual button 1111 for selecting a first mode for displaying only the first information about the second type of the first external electronic device and a second virtual button 1115 for selecting a second mode for displaying all the first information of the first external electronic device. The first external electronic device of the second type may be a first external electronic device capable of establishing a BT communication connection based on an address with no connection history. In addition to the first external electronic device of the second type, all types of first external electronic devices may also include, for example, a first external electronic device of the first type currently connected via BT communication and a first external electronic device of the third type that cannot establish a BT communication connection based on an address with no connection history. When displaying the first information about all types of first external electronic devices, the second external electronic device 130 may display the first type to the third type, respectively.

[0145] refer to Fig.11b , the second external electronic device 130 (eg, Figure 3The second external electronic device 130) may display, on the UI screen 1120, for example, a virtual button 1121 for selecting a mode (eg, a first mode or a second mode) for displaying at least one external electronic device in the registered device information.

[0146] Fig.12a and Figure 12b is a diagram illustrating an example of displaying registered device information according to an embodiment.

[0147] refer to Fig.12a , the second external electronic device 130 may only display the first information about the first external electronic device of the first type and the first external electronic device of the second type in the received registered device information. Fig.11a , the second external electronic device 130 may only display first information about a first external electronic device of a first type (e.g., a device currently connected via BT communication) and first information about a first external electronic device of a second type (e.g., a device capable of establishing a BT communication connection based on an address with no connection history). On screen 1210, the second external electronic device 130 may, for example, display first information 1211 about a first external electronic device of a first type in letters of a first thickness, and may display first information 1212 about a first external electronic device of a second type in letters of a second thickness that is smaller than the first thickness. In another example, the second external electronic device 130 may display first information 1211 about a first external electronic device of a first type and first information 1212 about a first external electronic device of a second type in different colors, respectively.

[0148] refer to Figure 12b , the second external electronic device 130 may display all types of first external electronic devices included in the received registered device information on the screen 1220. For example, when Fig.11a When the first virtual button 1111 is selected in the screen 1220, the second external electronic device 130 may display all types of first external electronic devices included in the received registered device information. In addition, the second external electronic device 130 may display an icon 1228 for notifying the user of additional information outside the registered device information on the screen 1220, and may display a sentence 1230 for notifying the user of the characteristics of the first external electronic device 120 selected based on the selection of the icon 1228.

[0149] On screen 1220, the second external electronic device 130 can display first information 1221 and 1222 about the first type of first external electronic device currently connected via BT communication in a first color (e.g., blue), can display first information 1223 and 1224 about the second type of first external electronic device capable of establishing a BT communication connection based on an address with no connection history in a second color (e.g., black), and can display first information 1225 and 1226 about the third type of first external electronic device that cannot establish a BT communication connection based on an address with no connection history in a third color (e.g., gray).

[0150] Additionally or alternatively, the second external electronic device 130 may display an icon 1228 for describing the characteristics of the third type of the first external electronic device on the periphery of the first information about the third type of the first external electronic device. When the icon 1228 is selected, the second external electronic device 130 may display a sentence 1230 for notifying the user of the characteristics of the third type of the first external electronic device on at least a portion of the screen 1220. For example, the sentence 1230 may include guidance on how to establish a BT communication connection to the third type of the first external electronic device, that is, using a conventional connection process.

[0151] Fig.13 is a diagram illustrating a UI screen for sharing and using registered device information according to an embodiment.

[0152] refer to Fig.13 , the electronic device 110 may establish BT communication with the first external electronic device 120 and may share first information (registered device information) about the first external electronic device 120 and second information about the probability that the first external electronic device 120 will accept a connection request based on a BT address that has no connection history with the second external electronic device 130. The second external electronic device 130 may establish a communication connection with the first external electronic device 120 based on the first information about the first external electronic device 120 and the second information about the probability.

[0153] In reference numeral 1310, an electronic device (eg, Figure 2 The electronic device 110) can communicate with the first external electronic device (eg, Figure 1b Therefore, the electronic device 110 can store the first information about the first external electronic device 120 (the BT address and / or name (e.g., level U Flex) of the first external electronic device 120) in the memory (e.g., Figure 2The electronic device 110 may send a communication connection request based on the second BT address to the first external electronic device 120, and may associate the second information about the probability of accepting the communication connection request with the first information about the first external electronic device 120 and store it in the memory 230. The second information about the probability that the first external electronic device 120 will accept the communication connection request may include information indicating whether the first external electronic device 120 accepts the communication connection request based on the second BT address that has no connection history.

[0154] In reference numeral 1320 , the electronic device 110 may transmit (share) the second information on the probability of accepting the communication connection request and the first information on the first external electronic device 120 to the second external electronic device 130 (step ②).

[0155] In reference numeral 1330, the second external electronic device 130 may display the registered device information stored in its memory and may identify an input in the registered device information that is associated with the communication connection with the first external electronic device 120 (step ③). The second external electronic device 130 may establish a communication connection with the first external electronic device 120 based on the BT address of the second external electronic device 130 according to the identified input associated with the communication connection (④).

[0156] In reference numeral 1340 , the second external electronic device 130 may display registered device information indicating that it has established a communication connection with the first external electronic device 120 .

[0157] When a communication connection is established with the first external electronic device 120, the second external electronic device 130 may download and install an application associated with the first external electronic device 120 from an external server. For example, the application associated with the first external electronic device 120 may include an application for parameter settings (e.g., detailed settings) associated with BT communication of the first external electronic device 120. According to another embodiment, when receiving registered device information associated with the first external electronic device 120 from the electronic device 110, the second external electronic device 130 may receive information associated with the application associated with the first external electronic device 120 from the electronic device 110, or may download information about the application from an external server.

[0158] The electronic device according to various embodiments may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. According to an embodiment of the present disclosure, the electronic device is not limited to those described above.

[0159] According to an embodiment, an electronic device (e.g., Figure 1b The electronic device 110 may include: a user interface (eg, Figure 2 user interface 210); communication circuit (eg, Figure 2 A communication circuit 220 configured to support Bluetooth (BT) communication and store a first BT address; a processor (eg, Figure 2 A processor 240) operably connected to the user interface and the communication circuit; and a memory operably connected to the user interface and the communication circuit. The memory may store instructions that, when executed, cause the processor to: use the communication circuit to communicate with a first external electronic device (e.g., Figure 1a The method comprises the steps of: establishing a communication connection with a first external electronic device 120); terminating the communication connection with the first external electronic device; receiving a reconnection request based on a first BT address from the first external electronic device after terminating the communication connection; sending a communication connection request to the first external electronic device based on a second BT address different from the first BT address using a communication circuit in response to the reconnection request; and storing information about whether the first external electronic device accepts or rejects the communication connection request in a memory.

[0160] The instructions may cause the processor to send the stored information to a second external electronic device (e.g., Figure 1b a second external electronic device 130).

[0161] The instructions may cause the processor to associate and store the additional information about the first external electronic device with the information about whether the first external electronic device accepts or rejects the communication connection request. The additional information may be obtained during the communication connection process based on the first BT address.

[0162] The instruction can cause the processor to: identify whether the first external electronic device accepts or rejects the communication connection request based on information about whether the first external electronic device accepts or rejects the communication connection request; when it is identified that the first external electronic device accepts the communication connection request, use the communication circuit to send additional information about the first external electronic device to the second external electronic device; and when it is identified that the first external electronic device rejects the communication connection request, it can prohibit the additional information about the first external electronic device from being sent to the second external electronic device.

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

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

[0165] The information may include information indicating whether the first external electronic device accepts or rejects the communication connection request when the first external electronic device is not in the pairing mode.

[0166] The first BT address may be a unique address of the electronic device, and the second BT address may be an address that has no history of establishing a communication connection with the first external electronic device.

[0167] The instruction may cause the processor to stop scanning the first external electronic device when sending the stored information to the second external electronic device is completed, when a specified time interval has not passed since sending the stored information, or when the electronic device is within a specified distance of the second external electronic device.

[0168] According to an embodiment, an electronic device (e.g., Figure 3 The second external electronic device 130 may include: a user interface (eg, Figure 3 at least one communication circuit (eg, Figure 3 A communication circuit 320) configured to support Bluetooth (BT) communication; a processor (eg, Figure 3 A processor 340) operably connected to a user interface and at least one communication circuit; and a memory (e.g., Figure 3 The memory 330 is operably connected to the processor. The memory may include instructions that, when executed, cause the processor to: use at least one communication circuit to receive information about a first external electronic device (e.g., Figure 1b The first external electronic device 110) is connected to at least one second external electronic device (eg, Figure 1b The present invention provides first information about a first external electronic device 120) and second information about a probability that at least one second external electronic device will accept a connection request using an address with no connection history; and provides the second information through a user interface.

[0169] 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 a user interface.

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

[0171] The instructions may cause the processor to: provide, through a user interface, a user interface element for selection to store the first information and the second information; and store the first information and the second information in a memory based on the selection of the user interface element.

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

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

[0174] According to an embodiment, an electronic device (e.g., Figure 2 The electronic device 110 may include: a user interface (eg, Figure 2 user interface 210); communication circuit (eg, Figure 2 A communication circuit 220 configured to support Bluetooth (BT) communication and store a first BT address; a processor (eg, Figure 2 240) operably connected to the user interface and communication circuitry; and a memory (e.g., Figure 2 The memory 230 is operably connected to the processor. The memory may store instructions that, when executed, cause the processor to: communicate with a first external electronic device (e.g., Figure 1b The invention relates to a method for establishing a communication connection with a first external electronic device 120; using a communication circuit to send a communication connection request to the first external electronic device based on a second BT address different from the first BT address; after the communication connection is established, storing information about whether the first external electronic device accepts or rejects the communication connection request based on the second BT address in a memory.

[0175] The instructions may cause the processor to send the stored information to a second external electronic device (e.g., Figure 1b a second external electronic device 130).

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

[0177] The instruction can cause the processor to: identify whether the first external electronic device accepts or rejects the communication connection request based on information about whether the first external electronic device accepts or rejects the communication connection request; when it is identified that the first external electronic device accepts the communication connection request, use the communication circuit to send additional information about the first external electronic device to the second external electronic device; and when it is identified that the first external electronic device rejects the communication connection request, prohibit sending the additional information about the first external electronic device to the second external electronic device.

[0178] The first BT address may be a unique address of the electronic device, and the second BT address may be an address that has no history of establishing a communication connection with the first external electronic device.

[0179] It should be understood that the various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, but include various changes, equivalent forms or alternative forms for corresponding embodiments. For the description of the accompanying drawings, similar reference numerals may be used to refer to similar or related elements. It will be understood that the noun corresponding to the project in the singular form may include one or more things unless the relevant context clearly indicates otherwise. As used herein, each of the phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C" and "at least one of A, B or C" may include any one or all possible combinations of the items listed together with the corresponding one of the multiple phrases. As used herein, terms such as "1st" and "2nd" or "first" and "second" may be used to simply distinguish the corresponding component from another component, and do not limit the component in other aspects (e.g., importance or order). It will be understood that if an element (e.g., a first element) is referred to as being “combined with another element (e.g., the second element)”, “combined to another element (e.g., the second element)”, “connected with another element (e.g., the second element)”, or “connected to another element (e.g., the second element)” when the terms “operably” or “communicatively” are used or when the terms “operably” or “communicatively” are not used, it means that the element may be directly (e.g., wired) connected to the other element, wirelessly connected to the other element, or connected to the other element via a third element.

[0180] As used herein, the term "module" may include units implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "portion," or "circuit"). A module may be a single integrated component adapted to perform one or more functions or a minimum unit or portion of the single integrated component. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).

[0181] The various embodiments described herein may be implemented as software (e.g., program 1440) including one or more instructions stored in a storage medium (e.g., internal memory 1436 or external memory 1438) that can be read by a machine (e.g., electronic device 1401). For example, under the control of a processor, a processor (e.g., processor 1420) of the machine (e.g., electronic device 1401) may call at least one of the one or more instructions stored in the storage medium and execute the at least one instruction with or without the use of one or more other components. This enables the machine to operate to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be run by an interpreter. A machine-readable storage medium may be provided in the form of a non-transitory storage medium. Among them, the term "non-transitory" only means that the storage medium is a tangible device and does not include a signal (e.g., an electromagnetic wave), but the term does not distinguish between data being semi-permanently stored in a storage medium and data being temporarily stored in a storage medium.

[0182] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be released in the form of a machine-readable storage medium (e.g., a compact disk read-only memory (CD-ROM)), or may be downloaded via an application store (e.g., Play Store TM ) The computer program product may be published (e.g., downloaded or uploaded) online, or the computer program product may be distributed (e.g., downloaded or uploaded) directly between two user devices (e.g., smart phones). If published online, at least part of the computer program product may be temporarily generated, or at least part of the computer program product may be at least temporarily stored in a machine-readable storage medium (such as a memory of a manufacturer's server, an application store's server, or a forwarding server).

[0183] According to various embodiments, each component (e.g., module or program) in the above-mentioned components may include a single entity or multiple entities. According to various embodiments, one or more components in the above-mentioned components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform the one or more functions of each component in the multiple components in the same or similar manner as a corresponding component in the multiple components before integration. According to various embodiments, the operations performed by a module, program or another component may be performed sequentially, in parallel, repeatedly or in a heuristic manner, or one or more operations in the operations may be run or omitted in different orders, or one or more other operations may be added.

[0184] According to certain embodiments disclosed in the present disclosure, an electronic device may configure BT communication information including information indicating whether an external electronic device can establish BT communication based on a BT address with no history of establishing BT communication. In addition, various effects determined directly or indirectly by the present disclosure may be provided.

[0185] While the present 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 spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

[0186] Some of the above-mentioned embodiments of the present disclosure may be implemented in hardware, firmware, or by running software or computer code, which may be stored in a medium such as a CD ROM, a digital versatile disk (DVD), a tape, a RAM, a floppy disk, a hard disk, or a magneto-optical disk, or a computer code (the computer code is downloaded over a network, initially stored on a remote recording medium or a non-transitory machine-readable medium, and the computer code to be stored on a local recording medium), and thus, the methods described herein may be presented via such software stored on a recording medium using a general-purpose computer or a dedicated processor or programmable or dedicated hardware (e.g., an ASIC or FPGA). As will be understood in the art, a computer, a processor, a microprocessor controller, or programmable hardware includes a memory component, such as a RAM, a ROM, a flash memory, etc., that can store or receive software or computer code, which, when accessed and run by a computer, a processor, or hardware, implements the processing methods described herein.

Claims

1. An electronic device, comprising: User interface; a communication circuit configured to support Bluetooth communication and store a first Bluetooth address; a processor operatively connected to the user interface and the communication circuit; as well as a memory operatively connected to the processor, The memory stores instructions, which, when executed, cause the processor to: Using the communication circuit to establish a communication connection with a first external electronic device based on the first Bluetooth address; Ending the communication connection with the first external electronic device; After terminating the communication connection, receiving a reconnection request based on the first Bluetooth address from the first external electronic device; In response to the reconnection request, using the communication circuit to send a communication connection request to the first external electronic device based on a second Bluetooth address different from the first Bluetooth address; storing information about whether the first external electronic device accepts or rejects the communication connection request in the memory, and associating and storing additional information about the first external electronic device with the information about whether the first external electronic device accepts or rejects the communication connection request, wherein the additional information is obtained during the communication connection process based on the first Bluetooth address; identifying whether the first external electronic device accepts or rejects the communication connection request based on information about whether the first external electronic device accepts or rejects the communication connection request; When recognizing that the first external electronic device accepts the communication connection request, sending additional information about the first external electronic device to a second external electronic device using the communication circuit; and When it is recognized that the first external electronic device rejects the communication connection request, transmission of additional information about the first external electronic device to the second external electronic device is prohibited.

2. The electronic device according to claim 1, wherein: The instructions also cause the processor to transmit the stored information to a second external electronic device.

3. The electronic device according to claim 1, wherein: The instructions further cause the processor to establish another communication connection with the first external electronic device based on the first Bluetooth address after storing information about whether the first external electronic device accepts or rejects the communication connection request.

4. The electronic device according to claim 3, wherein: The instructions further cause the processor to: After storing the information in the memory, receiving another reconnection request based on the first Bluetooth address from the first external electronic device; as well as In response to another reconnection request based on the first Bluetooth address, the another communication connection is established with the first external electronic device based on the first Bluetooth address.

5. The electronic device according to claim 1, wherein: When the first external electronic device is not in the pairing mode, the information includes information indicating whether the first external electronic device accepts or rejects the communication connection request.

6. The electronic device according to claim 1, wherein: The first Bluetooth address is a unique address of the electronic device, and The second Bluetooth address is an address that has no history of establishing a communication connection with the first external electronic device.

7. The electronic device according to claim 2, wherein: The instructions further cause the processor to: When the transmission of the stored information to the second external electronic device is completed, when a specified time interval has not elapsed since the transmission of the stored information or when the electronic device is within a specified distance of the second external electronic device, scanning of the first external electronic device is stopped.

8. An electronic device, comprising: User interface; at least one communication circuit configured to support Bluetooth communications; a processor operatively connected to the user interface and the at least one communication circuit; as well as a memory operatively connected to the processor, The memory includes instructions which, when executed, cause the processor to: receiving, using the at least one communication circuit, first information about at least one second external electronic device to which the first external electronic device is connected through Bluetooth communication using a first Bluetooth address and second information about a probability that the at least one second external electronic device will accept a connection request from the first external electronic device using a second Bluetooth address different from the first Bluetooth address having no connection history, wherein the second information indicates that the at least one second external electronic device will accept a connection request using the second Bluetooth address having no connection history; associating the second information with the first information and providing the first information and the second information through the user interface; Using the first information, a communication connection request based on the Bluetooth address is sent to the second external electronic device.

9. The electronic device according to claim 8, wherein: The first external electronic device and the electronic device are configured with the same user account.

10. The electronic device according to claim 8, wherein: The instructions further cause the processor to: providing, through the user interface, a user interface element for selecting to store the first information and the second information; and Based on a selection of the user interface element, the first information and the second information are stored in the memory.

11. The electronic device according to claim 8, wherein: The instructions also cause the processor to receive the first information and the second information from the first external electronic device or server.

12. The electronic device according to claim 8, wherein: The instructions also cause the processor to install an application associated with the at least one second external electronic device based on the first information.

Images