Patent Description:
With the recent development of digital technology, various types of electronic devices, such as mobile communication terminals, smart phones, tablet personal computers (PCs), notebooks, wearable devices, digital cameras, personal computers, and Internet-of-things (IoT) devices, have been widely used. Various types of proximity services utilizing low-power discovery technology employing short-range communication technology have also been developed in recent years. For example, a proximity communication service in which neighboring electronic devices are able to quickly exchange data through a proximity network is being developed. Proximity services may include low-power proximity services using Bluetooth<IMG> low energy (BLE) beacons or proximity services utilizing low-power short-range communication technology based on neighbor awareness networking (NAN) (e.g., Wi-Fi aware) in a wireless local area network (WLAN) (hereinafter, NAN).

In a NAN-based low-power proximity service (hereinafter, a proximity service), a proximity network that is dynamically changed according to the movement of the electronic device is configured and used, and a set of electronic devices constituting the proximity network is referred to as a cluster. In the proximity service, electronic devices included in a cluster may transmit/receive a signal for discovery (e.g., a beacon) and a service discovery frame (SDF) to/from each other within a synchronized time duration or a communication interval (e.g., a discovery window (DW)). For example, at least one electronic device in the cluster may transmit a signal to notify of the existence of the cluster to a new electronic device wishing to join the cluster, and may receive a response signal from the new electronic device wishing to join the cluster.

<CIT> discloses, according to its abstract: methods, apparatuses, and systems related to signaling for concurrent operation and/or cancellation capabilities for termination of concurrent operations on networks (e.g., NAN, WLAN networks); in some implementations, systems and methods are provided for handling of time blocks that partially overlaps with the concurrent operations.

In order to perform NAN communication in an interval other than the DW, the electronic device may configure a NAN data path (NDP). For example, a time slot for data transmission in the interval between DWs may be defined even though a connection process between devices is omitted, thereby transmitting/receiving data in the time slot interval.

In the NAN communication, it is possible to perform data communication quickly and simply by operating on a connectionless basis, and to perform data communication flexibly with a plurality of devices.

If a Wi-Fi direct channel and a Wi-Fi channel are established differently from each other, Wi-Fi direct communication cannot be performed while the Wi-Fi channel is used because the Wi-Fi direct channel cannot be used during that time.

For example, if two or more electronic devices connected through a Wi-Fi Direct channel are using different Wi-Fi channels, it is possible to establish a Wi-Fi direct channel in the same manner as one Wi-Fi channel, thereby performing Wi-Fi direct communication. However, when other Wi-Fi channels are activated, Wi-Fi direct communication cannot be performed.

As such, there is a need in the art for method of scheduling a communication data link of an electronic device, to increase efficiency of NAN communication by enabling Wi-Fi direct communication to be more seamlessly performed.

In accordance with an aspect of the disclosure, an electronic device according to claim <NUM> is provided.

In accordance with another aspect of the disclosure, a method according to claim <NUM> is provided.

Accordingly, an aspect of the disclosure is to provide an electronic device and a method of scheduling a communication data link of the electronic device, to increase efficiency of NAN communication.

Another aspect of the disclosure is to provide an electronic device and a method of scheduling a communication data link of the electronic device, which may identify a non-NAN connection state between an electronic device and an external electronic device to perform NAN communication, and may perform scheduling of a NAN data link, thereby increasing the transmission speed of NAN data communication and efficiently performing NAN communication and non-NAN communication.

The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:.

Hereinafter, various embodiments will be described with reference to the accompanying drawings. Descriptions of known functions and/or configurations will be omitted for the sake of clarity and conciseness.

It should be appreciated that embodiments of the disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment.

Herein, expressions 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" should be interpreted as including any one of the listed items or as including any possible combination thereof. As used herein, such terms as "1st" and "2nd," or "first" and "second" may be used to simply distinguish a corresponding component from another, and do not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term "operatively" or "communicatively", as "coupled with," or "connected with," another element (e.g., a second element), this indicates that the first element may be coupled with the second element directly (e.g., wiredly), wirelessly, or via a third element.

<FIG> illustrates an electronic device <NUM> in a network environment <NUM> according to an embodiment. Referring to <FIG>, the electronic device <NUM> in the network environment <NUM> may communicate with an electronic device <NUM> via a first network <NUM> (e.g., a short-range wireless communication network), with an electronic device <NUM> or a server <NUM> via a second network <NUM> (e.g., a long-range wireless communication network), or with the electronic device <NUM> via the server <NUM>.

The electronic device <NUM> may include a processor <NUM>, memory <NUM>, an input device <NUM>, an audio output device <NUM>, a display device <NUM>, an audio module <NUM>, a sensor module <NUM>, an interface <NUM>, a haptic module <NUM>, a camera module <NUM>, a power management module <NUM>, a battery <NUM>, a communication module <NUM>, a subscriber identification module (SIM) card <NUM>, and an antenna module <NUM>. At least one of the components may be omitted from the electronic device <NUM>, or one or more other components may be added in the electronic device <NUM>. Some of the components may be implemented as single integrated circuitry.

The processor <NUM> may execute software (e.g., a program <NUM>) to control at least one other component (e.g., a hardware or software component) of the electronic device <NUM> coupled with the processor <NUM>, and may perform various data processing or computation. As at least part of the data processing or computation, the processor <NUM> may load a command or data received from another component in volatile memory <NUM>, process the command or the data stored in the volatile memory <NUM>, and store resulting data in non-volatile memory <NUM>.

The auxiliary processor <NUM> may be adapted to consume less power than the main processor <NUM>, or to be specific to a specified function.

The auxiliary processor <NUM> may control at least some of functions or states related to at least one component among the components of the electronic device <NUM>, instead of the main processor <NUM> while the main processor <NUM> is in an inactive (e.g., sleep) state, or together with the main processor <NUM> while the main processor <NUM> is in an active state.

The memory <NUM> may store various data used by at least one component of the electronic device <NUM>. The various data may include software and input data or output data for a command related thereto.

The program <NUM> may be stored in the memory <NUM> as software, and may include an operating system (OS) <NUM>, middleware <NUM>, or an application <NUM>.

The input device <NUM> may receive a command or data to be used by other component of the electronic device <NUM>, from a user of the electronic device <NUM>. The input device <NUM> may include a microphone, a mouse, a keyboard, or a digital or stylus pen.

The sound output device <NUM> may output sound signals to the outside of the electronic device <NUM>, and may include a speaker or a receiver. The receiver may be implemented as separate from, or as part of the speaker.

The display device <NUM> may visually provide information to the user of the electronic device <NUM>. The display device <NUM> may include a display, a hologram device, or a projector and control circuitry to control a corresponding one of the display, hologram device, and projector, as well as touch circuitry adapted to detect a touch, or sensor circuitry (e.g., a pressure sensor) adapted to measure the intensity of force incurred by the touch.

The audio module <NUM> may convert a sound into an electrical signal and vice versa, may obtain the sound via the input device <NUM>, or output the sound via the sound output device <NUM> or a headphone of an external electronic device <NUM> directly (e.g., wiredly) or wirelessly coupled with the electronic device <NUM>.

The sensor module <NUM> may include a gesture sensor, a gyro 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 illuminance sensor.

The interface <NUM> may support one or more specified protocols to be used for the electronic device <NUM> to be coupled with the external electronic device <NUM> directly (e.g., wiredly) or wirelessly, and may include a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

The connecting terminal <NUM> may include a HDMI connector, a USB connector, a SD card connector, or an audio connector (e.g., a headphone connector).

The haptic module <NUM> may convert an electrical signal into a mechanical stimulus (e.g., a vibration or a movement) or electrical stimulus which may be recognized by a user via his tactile sensation or kinesthetic sensation, and may include a motor, a piezoelectric element, or an electric stimulator.

The camera module <NUM> may capture a still image or moving images, and may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module <NUM> may manage power supplied to the electronic device <NUM>, and may be implemented as at least part of a power management integrated circuit (PMIC).

The battery <NUM> may supply power to at least one component of the electronic device <NUM> and may include a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

The communication module <NUM> may support establishing a wired communication channel or a wireless communication channel between the electronic device <NUM> and the external electronic device <NUM>, <NUM>, or the server <NUM>, and performing communication via the established communication channel. The communication module <NUM> may include one or more communication processors that are operable independently from the processor <NUM> (e.g., the AP) and supports a wired communication or a wireless communication.

The communication module <NUM> may include a wireless communication module <NUM> (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 <NUM> (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). The wireless communication module <NUM> may identify and authenticate the electronic device <NUM> in a communication network, such as the first network <NUM> or the second network <NUM>, using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the SIM card <NUM>.

The antenna module <NUM> may include an antenna including a radiating element composed of a conductive material or a conductive pattern formed in or on a substrate (e.g., PCB). The antenna module <NUM> may include a plurality of antennas. In such a case, at least one antenna appropriate for a communication scheme used in the communication network, such as the first network <NUM> or the second network <NUM>, may be selected by the communication module <NUM> from the plurality of antennas. Another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as part of the antenna module <NUM>.

At least some of the above-described components may be coupled mutually and communicate signals therebetween via an inter-peripheral communication scheme (e.g., a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).

To that end, a cloud, distributed, or client-server computing technology may be used, for example.

<FIG> illustrates an example of a system configuration according to an embodiment.

Specifically, <FIG> illustrates an example of the configuration of a NAN cluster <NUM> for a proximity network. In the following description, the cluster <NUM> may denote a set of electronic devices (or NAN devices) <NUM>, <NUM>, <NUM>, and <NUM> that configure a proximity network such that the respective electronic devices <NUM>, <NUM>, <NUM>, and <NUM> are able to transmit and receive data to and from each other. For example, the cluster <NUM> may be referred to as a NAN cluster according to the NAN specification (or standard).

Referring to <FIG>, the cluster <NUM> may include a plurality of electronic devices <NUM>, <NUM>, <NUM>, and <NUM>. The electronic devices <NUM>, <NUM>, <NUM>, and <NUM> included in the cluster <NUM> may transmit/receive a beacon (or a discovery beacon), an SDF, or a NAN action frame (NAF) within a synchronized time duration or a communication interval, such as a search DW. For example, the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM> may be synchronized in the time clock with each other, and may exchange beacons, SDFs, or NAFs with each other in the same DW. An electronic device supporting a NAN-based low-power short-range communication technology may broadcast discovery signals (e.g., beacons) for discovering another electronic device in a predetermined first cycle (e.g., about <NUM> milliseconds (msec)), and may perform scanning in a predetermined second cycle (e.g., about <NUM> msec), thereby receiving a discovery signal broadcast from another electronic device. The electronic device may recognize at least one of other electronic devices located near the electronic device, based on the discovery signal received through scanning, and may perform time and channel synchronization with the at least one recognized electronic device.

As illustrated in <FIG>, respective electronic devices <NUM>, <NUM>, <NUM>, and <NUM> may transmit beacons, and may receive beacons from other electronic devices <NUM>, <NUM>, <NUM>, and <NUM>, thereby configuring one cluster <NUM>, and the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM> may perform time and channel synchronization.

Time and channel synchronization may be performed based on the time and channel of the electronic device having the highest master preference in the cluster <NUM>. For example, the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM> configured through discovery may exchange signals regarding master preference information indicating preference for operating as an anchor master, and the electronic device having the highest master preference may be determined to be an anchor master (or a master device) through the exchanged signals.

The anchor master may denote an electronic device that is a reference for time and channel synchronization of the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM>. The anchor master may differ according to the master preference of the electronic device. Each of the time- and channel-synchronized electronic devices <NUM>, <NUM>, <NUM>, and <NUM> may transmit a beacon and an SDF and receive a beacon and an SDF from other electronic devices in the cluster <NUM> within a DW (or discovery interval) repeated in a predetermined cycle.

The beacon may be periodically transmitted and received every DW in order to continue to maintain time and channel synchronization of the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM>.

The SDF may be transmitted and received in the DW as necessary in order to provide services to the discovered electronic devices <NUM>, <NUM>, <NUM>, and <NUM>. The electronic device operating as an anchor master, among the time- and channel-synchronized electronic devices <NUM>, <NUM>, <NUM>, and <NUM>, may transmit a beacon to detect a new electronic device in an interval between the DWs.

Each of the time- and channel-synchronized electronic devices <NUM>, <NUM>, <NUM>, and <NUM> may transmit a NAF and receive an NAF from other electronic devices in the cluster <NUM> within a DW (or a discovery interval) repeated in a predetermined cycle. The NAF may include one piece of information related to configuration of an NDP, information related to schedule update, or information related to NAN ranging so as to perform data communication in the interval between DWs. For example, the NAF may control a schedule of radio resources for coexistence of NAN operations and non-NAN operations (e.g., Wi-Fi direct, mesh, independent basic service set (IBSS), WLAN, Bluetooth™, or near-field communication (NFC)). The NAF may include time and channel information available for NAN communication.

Each of the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM> may operate in an active state only during the DWs, and may operate in a low-power state (e.g., a sleep state) during the remaining intervals other than the DWs, thereby reducing power consumption. For example, the DW may be a period of time (e.g., milliseconds) during which the electronic device is in an active state (or a wake-up state) in which a large amount of power is consumed, while the electronic device remains in a sleep state in an interval other than the DW, thereby enabling low-power discovery. Accordingly, the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM> may be simultaneously activated at the start time (e.g., a DW start), which is time-synchronized, and may simultaneously switch to the sleep state at the end time of the DW.

The respective electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM> may exchange messages in other intervals, as well as in the DWs. For example, the electronic devices <NUM>, <NUM>, <NUM>, and <NUM> in the cluster <NUM> may perform additional communication by configuring an active time slot in the interval between the DWs. The electronic devices may transmit and receive, in an active time slot, the SDF that the electronic devices failed to transmit and receive within the DW, and may specify a NAN communication operation interval and/or a non-NAN communication operation interval, thereby performing a NAN communication connection and/or a non-NAN communication connection.

The electronic devices <NUM>, <NUM>, <NUM>, and <NUM> included in the cluster <NUM> may perform discovery, synchronization, and data exchange operations using the protocol illustrated in <FIG>, which will now be described.

<FIG> illustrates an example of a signal transmission protocol in a proximity network according to an embodiment.

For example, <FIG> may illustrate an example of a DW. An example in which electronic devices included in a single cluster transmit signals through a specific channel (e.g., channel <NUM> (Ch6)), based on the NAN standard, will be described with reference to <FIG>.

Referring to <FIG>, electronic devices included in one cluster may transmit synchronization beacons <NUM> and SDFs <NUM> in a synchronized DW <NUM>. Discovery beacons <NUM> may be transmitted by at least one electronic device in an interval <NUM> other than the DWs <NUM> (e.g., an interval between the DWs). The electronic devices may transmit the synchronization beacons <NUM> and the SDFs <NUM> on a contention basis. For example, the synchronization beacons <NUM> and the SDFs <NUM> may be transmitted based on contention between the electronic devices included in the cluster. Each of the electronic devices included in the cluster may have a transmission priority of the beacon <NUM> higher than that of the SDF <NUM>.

Electronic devices included in a single cluster may transmit and receive NAFs in the synchronized DWs <NUM>. The NAF may include one piece of information related to configuration of an NDP, information related to schedule update, or information related to NAN ranging so as to perform data communication in the interval between the DWs.

The DW <NUM> may be an interval in which a corresponding electronic device is activated by switching from a sleep state, which corresponds to a power saving mode, to a wake-up state in order for the electronic devices to exchange data with each other. For example, the DW <NUM> may be divided into time units (TUs) in milliseconds. The DW <NUM> for transmitting and receiving the synchronization beacons <NUM> and the SDFs <NUM> may occupy <NUM> TUs, and may have a cycle (or period) that is repeated every <NUM> TUs.

The discovery beacon <NUM> may be a signal transmitted to allow another electronic device that failed to join the cluster to discover the cluster. For example, the discovery beacon <NUM> is a signal to notify of the existence of the cluster, and the electronic devices that did not join the cluster may perform a passive scan to receive the discovery beacon <NUM>, thereby discovering and joining the cluster.

The discovery beacon <NUM> may include information necessary for synchronization with the cluster, such as at least one of a frame control (FC) field indicating a function of a signal (e.g., a beacon), a broadcast address, a media access control (MAC) address of a transmission electronic device, a cluster identifier (ID), a sequence control field, a time stamp for a beacon frame, a beacon interval indicating the transmission interval of the discovery beacon <NUM>, or capability information on a transmission electronic device. The discovery beacon <NUM> may include at least one proximity network (or cluster)-related information element, which is referred to herein as "attribute information".

The synchronization beacon <NUM> may indicate a signal for maintaining synchronization between the synchronized electronic devices in the cluster. The synchronization beacon <NUM> may be transmitted by a synchronization device among the electronic devices in the cluster. For example, the synchronization device may include an anchor master device, a master device, or a non-master synchronization device, which is defined in the NAN standard.

The synchronization beacon <NUM> may include information necessary for synchronization of the electronic devices in the cluster. For example, the synchronization beacon <NUM> may include at least one of an FC field indicating a function of a signal (e.g., a beacon), a broadcast address, a MAC address of a transmission electronic device, a cluster identifier, a sequence control field, a time stamp for a beacon frame, a beacon interval indicating the interval between start points of the DWs <NUM>, or capability information on a transmission electronic device. The synchronization beacon <NUM> may include at least one proximity network (or cluster)-related information element, such as contents for services provided through the proximity network.

The SDF <NUM> may denote a signal for exchanging data through a proximity network. The SDF <NUM> may represent a vendor-specific public action frame, and may include various fields. For example, the SDF <NUM> may include a category or an action field, and may include at least one piece of proximity network-related information.

As described above, the synchronization beacon <NUM>, the SDF <NUM>, and the discovery beacon <NUM> may include proximity network-related information such as an identifier indicating the type of information, a length of information, and a body field, which is corresponding information. The corresponding information may include at least one piece of master indication information, cluster information, service identifier list information, service descriptor information, connection capability information, an extended WLAN infrastructure attribute, and peer-to-peer (P2P) operation information, IBSS information, mesh information, additional proximity network service discovery information, further availability map information, country code information, ranging information, cluster discovery information, or vendor-specific information.

<FIG> illustrates an example of data transmission and reception in a cluster according to an embodiment.

For example, <FIG> illustrates an example in which a first electronic device <NUM>, a second electronic device <NUM>, and a third electronic device <NUM> configure one cluster through a wireless short-range communication technology, and the respective electronic devices <NUM>, <NUM>, and <NUM> may transmit and receive beacons, SDFs, and/or NAFs to and from each other. In <FIG>, the first electronic device <NUM>, among the electronic devices <NUM>, <NUM>, and <NUM> constituting the cluster, may serve as a master electronic device.

Referring to <FIG>, the first electronic device <NUM> may transmit beacons, SDFs, or NAFs in the DW <NUM>, and may broadcast beacons, SDFs, or NAFs every DW <NUM> repeated every predetermined interval <NUM>.

The second electronic device <NUM> and the third electronic device <NUM> may receive beacons, SDFs, or NAFs transmitted by the first electronic device <NUM> every DW <NUM>.

The beacon transmitted in the DW <NUM> may indicate a synchronization beacon, and may include information for maintaining synchronization between the electronic devices <NUM>, <NUM>, and <NUM>. For example, if the electronic devices <NUM>, <NUM>, and <NUM> are included in a cluster, a time clock is synchronized with a master electronic device <NUM>, so that the DW <NUM> may be simultaneously activated.

The electronic devices <NUM>, <NUM>, and <NUM> may remain in a sleep state in intervals <NUM> other than the DWs <NUM> in order to reduce power consumption. For example, the electronic devices <NUM>, <NUM>, and <NUM> may operate in a wake-up state only in the DWs <NUM>, based on the synchronized time clock, thereby reducing power consumption.

The electronic devices <NUM>, <NUM>, and <NUM> may configure an active time slot in intervals <NUM> other than the DWs <NUM>, thereby performing additional communication. For example, the electronic devices may transmit and receive an SDF, which was not transmitted/received in the DW, in the active time slot, or may specify an operation for a Wi-Fi Direct, mesh, IBSS, WLAN, Bluetooth™, or NFC connection during the active time slot, thereby performing a legacy Wi-Fi connection or a discovery operation.

<FIG> illustrates an example of a system according to an embodiment.

Referring to <FIG>, an electronic device <NUM> may establish a first connection <NUM> based on a first communication protocol (e.g., Wi-Fi) with a first external electronic device <NUM>. For example, the electronic device <NUM> and the first external electronic device <NUM> may negotiate a channel for communication (e.g., channel <NUM>), and may establish a first connection <NUM> using the negotiated channel, thereby transmitting and receiving data.

A second external electronic device <NUM> capable of configuring a NAN cluster with the electronic device <NUM> may establish a third connection <NUM> based on a third communication protocol (e.g., Wi-Fi or Wi-Fi Direct) with a third external electronic device <NUM>. The second external electronic device <NUM> may establish a third connection <NUM> using a channel (e.g., channel <NUM>) negotiated with the third external electronic device <NUM>, thereby transmitting and receiving data.

The electronic device <NUM> may identify the second external electronic device <NUM> using the second communication protocol (e.g., NAN). For example, the electronic device <NUM> may transmit and receive a beacon, an SDF, or an NAF within a synchronized time duration (e.g., a DW), thereby identifying the second external electronic device <NUM>. The electronic device <NUM> may identify at least one of a NAN availability attribute, an extended WLAN infrastructure attribute, or an unaligned schedule attribute using at least one of a beacon, an SDF, or an NAF transmitted from the second external electronic device <NUM>. For example, the electronic device <NUM> may identify information related to the third connection <NUM> of the second external electronic device <NUM>, based on at least one of a NAN availability attribute, an extended WLAN infrastructure attribute, or an unaligned schedule attribute.

The electronic device <NUM> may schedule a data path based on the second communication protocol in consideration of information related to the first connection <NUM> and information related to the third connection <NUM>. For example, the electronic device may configure at least one further available window (FAW) in the interval between synchronized time durations, and may perform data communication.

The electronic device <NUM> may use channel information on the third connection <NUM> in order to establish a second connection <NUM> with the second external electronic device <NUM>. For example, the electronic device <NUM> may communicate with the second external electronic device <NUM> using channel information (e.g., channel <NUM>) on the third connection <NUM>. In this case, the electronic device <NUM> may switch between a first channel (e.g., channel <NUM>) for the first connection <NUM> and a second channel (e.g., channel <NUM>) for the second connection <NUM>, thereby maintaining both connections. For example, both connections may be maintained by allocating <NUM>% of the radio resources to each of the first and second channels. In this case, the electronic device and the second external electronic device <NUM> may perform data communication with an efficiency of up to about <NUM>%.

The electronic device <NUM> may improve data communication efficiency with the second external electronic device <NUM>. For example, the electronic device <NUM> and the second external electronic device <NUM> may simultaneously switch between channels, thereby performing continuous data communication.

An electronic device <NUM> as described above may include a communication module configured to support a first communication protocol and a second communication protocol, a processor operably connected to the communication module, and a memory operably connected to the processor, wherein the memory may store instructions that, when executed, allow (or enable) the processor to establish a first connection <NUM> based on the first communication protocol with a first external electronic device <NUM>, identify a second external electronic device <NUM> and a connection state of the second external electronic device <NUM> using the second communication protocol, produce a first message, based at least in part on the first connection <NUM> and the connection state of the second external electronic device <NUM>, transmit the produced first message to the second external electronic device <NUM> using the second communication protocol, receive, from the second external electronic device <NUM>, a second message in response to the first message using the second communication protocol, and based at least in part on the received second message, schedule a data link based on the second communication protocol.

The first communication protocol may support a communication operation other than a NAN communication operation, and the second protocol may support the NAN communication operation.

The first message or the second message may be included in at least one of a beacon, an SDF, or an NAF, which is transmitted within a synchronized time duration.

The first message or the second message may include one of a NAN availability attribute, an extended WLAN infrastructure attribute, or an unaligned schedule attribute.

The instructions may allow the processor to determine at least one FAW included in an interval between the synchronized time durations and include the at least one determined FAW in the first message, thereby proposing a schedule.

The first message may include at least one of channel information, band information, a start offset, a bit duration, or a period, which is related to the at least one determined FAW.

The second message may be configured as a schedule response including one of "acceptance", "refusal", or "modification proposal" with respect to the proposed schedule.

The connection state of the second external electronic device <NUM> may include information related to a third connection <NUM> based on a third communication protocol, which is established between the second external electronic device <NUM> and the third external electronic device <NUM>.

According to an embodiment, an electronic device may include a communication module configured to support a first communication protocol and a second communication protocol, a processor operably connected to the communication module; and a memory operably connected to the processor, wherein the memory may store instructions that, when executed, allow the processor to establish a first connection based on the first communication protocol with a first external electronic device, produce a first message, based at least in part on the first connection information, transmit the produced first message using the second communication protocol, receive, from the second external electronic device, a second message in response to the first message using the second communication protocol, and based at least in part on the received second message, schedule a data link based on the second communication protocol.

The first message or the second message may be included in at least one of a beacon, an SDF), or an NAF, which is transmitted within a synchronized time duration.

The second message may include information related to a third connection based on a third communication protocol, which is established between the second external electronic device and the third external electronic device.

<FIG> illustrates a scheduling method of a communication data link in a system according to an embodiment. The electronic device <NUM> may perform the operations described with reference to <FIG> in the system shown in <FIG>.

Referring to <FIG>, in step <NUM>, the electronic device <NUM> may establish a first connection <NUM> based on a first communication protocol with a first external electronic device <NUM>. The first communication protocol may support non-NAN communication operation. Herein, non-NAN communication may indicate various communication manners other than NAN communication, such as at least one of Wi-Fi Direct, mesh, IBSS, WLAN, Bluetooth™, or NFC. A non-NAN communication may support at least one standard of IEEE <NUM>. 11a, IEEE <NUM>, IEEE <NUM>. 11n, or IEEE <NUM>. For example, the first communication protocol used for the first connection <NUM> may support a communication connection having a carrier frequency in a <NUM> gigahertz (GHz) band or a <NUM> band.

In step <NUM>, the electronic device <NUM> may identify a second external electronic device <NUM> and a connection state of the second external electronic device <NUM> using the second communication protocol. The second communication protocol may support a NAN communication operation according to the NAN standard. The electronic device <NUM> may exchange beacons, SDFs, or NAFs with the second external electronic device <NUM> within a synchronized time duration (e.g., a DW), thereby identifying the second external electronic device <NUM>.

The electronic device <NUM> may broadcast discovery signals (e.g., beacons) for discovering another electronic device in a predetermined first cycle (e.g., about <NUM> msec), and may perform scanning in a predetermined second cycle (e.g., about <NUM> msec), thereby receiving a discovery signal broadcast from another electronic device. For example, based on the discovery signal received through scanning, the electronic device <NUM> may identify the second external electronic device <NUM> located near the electronic device, and may perform time and channel synchronization.

The electronic device <NUM> may identify a connection state of the second external electronic device <NUM>. For example, a beacon, an SDF, or an NAF received from the second external electronic device <NUM> may include at least one of a NAN availability attribute, an extended WLAN infrastructure attribute, or an unaligned schedule attribute. The electronic device <NUM> may identify the non-NAN communication-based connection state of the second external electronic device <NUM>, based on at least one of the received NAN availability attribute, an extended WLAN infrastructure attribute, and an unaligned schedule attribute. For example, the extended WLAN infrastructure attribute may include a non-NAN operation channel information field. The electronic device <NUM> may refer to the non-NAN operation channel information field in the extended WLAN infrastructure attribute, and may identify channel information (e.g., Wi-Fi channel information) being used by the second external electronic device <NUM>.

In step <NUM>, the electronic device <NUM> may produce a first message, based at least in part on the first connection <NUM> and the connection state of the second external electronic device <NUM>. For example, if the second external electronic device <NUM> is in a third connection <NUM> based on the third communication protocol with a third external electronic device <NUM>, the electronic device <NUM> may produce a first message, based at least in part on the first connection <NUM> and the third connection <NUM>. As another example, if the second external electronic device <NUM> is not in a non-NAN communication-based connection, the electronic device <NUM> may produce a first message, based at least in part on the first connection <NUM>.

The first message may be configured in the form of a NAN availability attribute and/ or an unaligned schedule attribute. The electronic device <NUM> may include a data link schedule proposal (e.g., a schedule request) based on the second communication protocol in the NAN availability attribute and/or the unaligned schedule attribute. The schedule proposal may be included in the NAN availability attribute, the unaligned schedule attribute, or a combination of the NAN availability attribute and the unaligned schedule attribute. If the NAN availability attribute and the unaligned schedule attribute overlap each other, the unaligned schedule attribute may have priority.

In step <NUM>, the electronic device <NUM> may transmit the produced first message to the second external electronic device <NUM> using the second communication protocol. The first message may be included in at least one of a beacon, an SDF, or an NAF to then be transmitted to the second external electronic device <NUM>.

In step <NUM>, the electronic device may receive, from the second external electronic device <NUM>, a second message in response to the first message using the second communication protocol.

If the first message includes a data link schedule proposal based on the second communication protocol, the second message may be configured as a schedule response including one of "acceptance", "refusal", or "modification proposal". For example, if the second message received from the second external electronic device <NUM> includes "acceptance", the data link based on the second communication protocol may be scheduled as an initial proposal of the electronic device <NUM>. If the second message received from the second external electronic device <NUM> includes "refusal", the electronic device <NUM> may give up scheduling of the data link based on the second communication protocol. If the second message received from the second external electronic device <NUM> includes "modification proposal", the electronic device <NUM> may transmit, to the second external electronic device <NUM>, a third message including one of "acceptance", "refusal", or "modification proposal".

In step <NUM>, based at least in part on the second message received from the second external electronic device <NUM>, the electronic device <NUM> may schedule the data link based on the second communication protocol. For example, the electronic device <NUM> may perform second-communication protocol-based data communication, based on the schedule negotiated with the second external electronic devices <NUM>.

According to an embodiment, a method of scheduling a communication data link of an electronic device may include establishing a first connection based on the first communication protocol with a first external electronic device, identifying a second external electronic device and a connection state of the second external electronic device using the second communication protocol, producing a first message, based at least in part on the first connection and the connection state of the second external electronic device, transmitting the produced first message to the second external electronic device using the second communication protocol, receiving, from the second external electronic device, a second message in response to the first message using the second communication protocol, and based at least in part on the received second message, scheduling a data link based on the second communication protocol.

<FIG> illustrates a method of scheduling a communication data link in a system according to an embodiment. The electronic device <NUM> may perform the operations described with reference to <FIG> in the system shown in <FIG>.

Referring to <FIG>, in step <NUM>, the electronic device <NUM> may subscribe to a discovery signal (e.g., a beacon) transmitted from the second external electronic device <NUM>. For example, if the second external electronic device <NUM> broadcasts or unicasts a discovery signal, the electronic device <NUM> may receive the broadcast or unicast discovery signal to subscribe to NAN service discovery. The discovery signal may include connection state information of the second external electronic device <NUM>. The electronic device <NUM> may identify a connection state of the second external electronic device <NUM> (e.g., the third connection <NUM>), based on the discovery signal received from the second external electronic device <NUM>. For example, the electronic device <NUM> may identify Wi-Fi channel information (e.g., channel <NUM>) of the third connection <NUM>, based on the discovery signal received from the second external electronic device <NUM>.

In step <NUM>, the electronic device <NUM> may publish a discovery signal (e.g., a beacon) including its own connection state information. For example, the electronic device <NUM> may issue a beacon indicating the operation of a NAN service. The second external electronic device <NUM> may subscribe to a discovery signal issued from the electronic device <NUM>, and may identify a connection state of the electronic device <NUM> (e.g., the first connection <NUM>). The order of steps <NUM> and <NUM> may vary, or steps <NUM> and <NUM> may be performed simultaneously.

In step <NUM>, the electronic device <NUM> may produce a first message, based at least in part on the first connection <NUM> and the connection state of the second external electronic device <NUM>, and may transmit the same to the second external electronic device <NUM>. The first message may be included in at least one of a beacon, an SDF, or an NAF to then be transmitted to the second external electronic device <NUM>. The first message may be configured in the form of a NAN availability attribute and/or an unaligned schedule attribute. The electronic device <NUM> may include a data link schedule proposal (e.g., a schedule request) based on the second communication protocol in the NAN availability attribute and/or the unaligned schedule attribute.

In step <NUM>, the electronic device <NUM> may receive, from the second external electronic device <NUM>, a second message in response to the first message using the second communication protocol. The second message may be configured as a schedule response including one of "acceptance", "refusal", or "modification proposal".

In step <NUM>, if the second message includes "acceptance" or "modification proposal", the electronic device <NUM> may transmit a schedule confirmation message in response to the second message using the second communication protocol. Based on the schedule confirmation message, the second electronic device <NUM> may identify that the schedule was determined. Transmission of the schedule confirmation message may optionally be performed. For example, the electronic device <NUM> may omit step <NUM>.

In step <NUM>, the electronic device <NUM> may schedule a second-communication protocol-based data link, based at least in part on the second message received from the second external electronic device <NUM>, and may perform second-communication protocol-based (NAN) data communication with the second external electronic device <NUM>.

<FIG> illustrates a schedule proposal according to the embodiment illustrated in <FIG>. The electronic device <NUM> may produce a schedule proposal shown in <FIG> as part of step <NUM> in <FIG>.

Referring to <FIG>, a data link schedule proposal (e.g., a schedule request) based on the second communication protocol may be included in a first message configured in the form of a NAN availability attribute and/or an unaligned schedule attribute. In addition, the NAN availability attribute and/or the unaligned schedule attribute may be included in at least one of a beacon, an SDF, or an NAF.

The electronic device <NUM> may produce a data path schedule proposal based on the second communication protocol in consideration of information related to the first connection <NUM> and/or information related to the third connection <NUM>. For example, the electronic device may configure at least one FAW in an interval <NUM> between synchronized time durations (e.g., DW0, DW1, or DW2), and may schedule a data path.

The FAW may be configured based on the NAN availability attribute. The FAW may be configured as a radio time resource unit having a length of <NUM> TUs according to the NAN standard. For example, a FAW (or a NAN slot) configured as a multiple of a length of 16TUs may be allocated to the interval <NUM> between the DWs (e.g., DW0, DW1, or DW2). The NAN availability attribute (e.g., a first NAN availability attribute <NUM> or a second NAN availability attribute <NUM> may include channel and band information and information related to one of a start offset, a bit duration, or a period, which are used for each FAW (e.g., NAN slot #<NUM> or NAN slot #<NUM>).

The channel information may be used to specify an operating class and to configure a primary channel. The band information may be used to configure a band (e.g., a <NUM> band or a <NUM> band) to perform NAN communication. The start offset may be used to indicate an offset between the start point of the FAW (or NAN slot) and the start point of the DW (e.g., DW0, DW1, or DW2). The bit duration may be used to indicate the duration time of the FAW (NAN slot). The period may be used to indicate a cycle in which the FAWs (or NAN slots) <NUM> repeat.

For example, a first NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. As another example, a second NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. The first NAN availability attribute <NUM> and/or the second NAN availability attribute <NUM> may include band information on the respective FAWs.

<FIG> illustrates an allocation range of a data link when the schedule proposal according to <FIG> is accepted. If the electronic device <NUM> receives, from the second external device <NUM>, a second message including "acceptance" in response to the first message, the electronic device <NUM> and the second external electronic device <NUM> may continue to perform data communication while performing channel switching (e.g., channel <NUM> → channel <NUM>) at the same time. For example, the second external device <NUM> may perform channel switching, based on the second-communication protocol-based data link schedule proposal (e.g., a schedule request), which is received from the electronic device <NUM>.

If the second external device <NUM> is not able to comply with the schedule proposal received from the electronic device <NUM>, the second external device <NUM> may transmit, to the electronic device <NUM>, a second message including "refusal" or "modification proposal" in response to the first message. In this case, the electronic device <NUM> may transmit, to the second external electronic device <NUM>, a third message including "acceptance", "refusal", or "modification proposal".

Embodiments herein may allow a plurality of devices to switch to the same channel simultaneously, thereby supporting endless and persistent NAN data communication <NUM>.

<FIG> illustrates a method of scheduling a communication data link in a system according to an embodiment. The electronic device <NUM> may perform the steps described with reference to <FIG> in the system shown in <FIG>.

Referring to <FIG>, in step <NUM>, the electronic device <NUM> may transmit a beacon, an SDF, or an NAF including a schedule proposal (e.g., a schedule request) as a first message. For example, at least one of the beacon, the SDF, or the NAF may include a NAN availability attribute and/or an unaligned schedule attribute, and the NAN availability attribute and/or the unaligned schedule attribute may include a data link schedule proposal based on the second communication protocol. Since the electronic device <NUM> has no information on the third connection <NUM> of the second external electronic device <NUM>, the electronic device <NUM> may produce a schedule proposal only in consideration of information on the first connection <NUM>.

In step <NUM>, the electronic device <NUM> may receive, from the second external electronic device <NUM>, a second message in response to the first message using the second communication protocol. The second message may be configured as a schedule response including one of "acceptance", "refusal", or "modification proposal". The second external electronic device <NUM> may recognize the schedule intended by the electronic device <NUM>, and may propose modification of the schedule according to the intention of the electronic device <NUM>. For example, the second external electronic device <NUM> may recognize that the electronic device <NUM> has proposed scheduling without information on the third connection <NUM>, and may produce a schedule modification proposal according to the third connection <NUM>.

In step <NUM>, if the second message includes "acceptance" or "modification proposal", the electronic device <NUM> may transmit a schedule confirmation message using the second communication protocol in response to the second message. For example, if the second message received from the second external electronic device <NUM> includes "acceptance", the electronic device may transmit a schedule confirmation message to schedule the data link based on the second communication protocol as initially suggested by the electronic device <NUM>. If the second message received from the second external electronic device <NUM> includes "modification proposal", the electronic device <NUM> may transmit a schedule confirmation message indicating "acceptance". The second message may include one of "refusal" or "modification proposal", in which case the electronic device <NUM> may transmit a third message in response to the second message to the second external electronic device <NUM>. The second electronic device <NUM> may identify that the schedule was determined based on the schedule confirmation message. Transmission of the schedule confirmation message may optionally be performed. For example, the electronic device <NUM> may omit step <NUM>.

In step <NUM>, the electronic device <NUM> may schedule a data link based on the second communication protocol, based at least in part on the second message received from the second external electronic device <NUM>, and may perform second-communication protocol-based (NAN) data communication with the second external electronic device <NUM>.

<FIG> illustrates a schedule proposal according to the method illustrated in <FIG>. The electronic device <NUM> may produce the schedule proposal shown in <FIG> as a part of step <NUM> in <FIG>.

A data link schedule proposal (e.g., a schedule request) based on the second communication protocol may be included in a NAN availability attribute and/or an unaligned schedule attribute. In addition, the NAN availability attribute and/or the unaligned schedule attribute may be included in at least one of a beacon, an SDF, or an NAF.

The electronic device <NUM> may schedule a data path based on the second communication protocol in consideration of information related to the first connection <NUM>.

Referring to <FIG>, a first NAN availability attribute <NUM> may be configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. The electronic device <NUM> that failed to identify the connection state of the second electronic device <NUM> may configure an initial schedule proposal in various forms. For example, the schedule proposal shown in <FIG> or the schedule proposal shown in <FIG> may be produced. The electronic device <NUM> may make a request to the second electronic device <NUM> for a schedule proposal by including only information on the first connection <NUM>.

<FIG> illustrates a schedule response according to the embodiment shown in <FIG>. The electronic device <NUM> may obtain the schedule response shown in <FIG> as a part of step <NUM> in <FIG>. For example, the second electronic device <NUM> may obtain the schedule proposal shown in <FIG>, and may produce the schedule response shown in <FIG> in response thereto.

The second external electronic device <NUM> may recognize the schedule intended by the electronic device <NUM>, and may propose modification of the schedule according to the intention of the electronic device <NUM>. For example, a second NAN availability attribute <NUM> may be added using an empty slot in the schedule proposal of the electronic device <NUM>.

Referring to <FIG>, the second NAN availability attribute <NUM> may be configured as a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * 16TUs, and a period of <NUM> * 16TUs so as to be included in an empty slot in the schedule proposal of the electronic device <NUM>. The second external electronic device <NUM> may transmit, to the electronic device <NUM>, a second message including the first NAN availability attribute <NUM> proposed by the electronic device <NUM> and the second NAN availability attribute <NUM> proposed by the second external electronic device <NUM>.

<FIG> illustrates an allocation range of a data link when scheduling is completed according to <FIG> and <FIG>. For example, if the electronic device <NUM> "accepts" the schedule response included in the second message, the electronic device <NUM> and the second external electronic device <NUM> may perform channel switching (e.g., channel <NUM> → channel <NUM>) simultaneously to continue to perform data communication <NUM>. For example, the electronic device <NUM> may perform channel switching, based on a data link schedule proposal (e.g., a schedule response) based on the second communication protocol, which is received from the second external device <NUM>. A NAN data link may be scheduled in a manner similar to the embodiment shown in <FIG>.

<FIG> illustrates an example of a system configuration according to various embodiments.

Referring to <FIG>, the electronic device <NUM> may establish a first connection <NUM> based on a first communication protocol (e.g., Wi-Fi) with the first external electronic device <NUM>. For example, the electronic device <NUM> and the first external electronic device <NUM> may negotiate a channel (e.g., channel <NUM>) for communication, and the electronic device <NUM> and the first external electronic device <NUM> may establish a first connection <NUM> using the negotiated channel, thereby transmitting and receiving data.

The electronic device <NUM> may identify a second external electronic device <NUM> capable of establishing a second connection <NUM> using a second communication protocol (e.g., NAN). For example, the electronic device <NUM> may transmit and receive a beacon, an SDF, or an NAF within a synchronized time duration (e.g., a DW), thereby identifying the second external electronic device <NUM>.

The electronic device <NUM> may schedule a data path based on the second communication protocol in consideration of information related to the first connection <NUM>. For example, the electronic device may configure at least one FAW in an interval between synchronized time durations, and may perform data communication.

Referring to <FIG>, in step <NUM>, the electronic device <NUM> may transmit (e.g., broadcast or unicast) a beacon, an SDF, or an NAF including a schedule proposal (e.g., a schedule request) as a first message. For example, at least one of the beacon, the SDF, or the NAF may include a NAN availability attribute and/or an unaligned schedule attribute, and the NAN availability attribute and/or the unaligned schedule attribute may include a data link schedule proposal based on a second communication protocol.

In step <NUM>, the electronic device <NUM> may receive, from a second external electronic device <NUM>, a second message in response to the first message using the second communication protocol. The second message may be configured as a schedule response including one of "acceptance", "refusal", or "modification proposal". The second external electronic device <NUM> may recognize the schedule intended by the electronic device <NUM>, and may propose modification of the schedule conforming to the intention of the electronic device <NUM>.

<FIG> illustrates a schedule proposal according to the method illustrated in <FIG>. The electronic device <NUM> may produce the schedule proposal shown in <FIG> as a part of step <NUM> described with reference to <FIG>.

Referring to <FIG>, a data link schedule proposal (e.g., a schedule request) based on the second communication protocol may be included in a NAN availability attribute and/or an unaligned schedule attribute. In addition, the NAN availability attribute and/ or the unaligned schedule attribute may be included in at least one of a beacon, an SDF, or an NAF.

The electronic device <NUM> may schedule a data path based on the second communication protocol in consideration of information related to the first connection <NUM>. For example, the electronic device may configure at least one FAW in an interval <NUM> between synchronized time durations (e.g., DW0, DW1, or DW2), and may schedule a data path.

A first NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> TUs, and a period of <NUM> TUs.

<FIG> illustrates an allocation range of a data link when the schedule proposal is accepted according to <FIG>. For example, if the electronic device <NUM> receives, from the second external device <NUM>, a second message including "acceptance" in response to the first message, the electronic device <NUM> and the second external electronic device <NUM> may continue to perform data communication <NUM> using the same channel. If the second external electronic device <NUM> is not connected to another electronic device other than the electronic device <NUM> (e.g., is not in the third connection <NUM> in <FIG>), the electronic device <NUM> and the second external electronic device <NUM> may not require channel switching. For example, channel formation for data communication with another electronic device may not be required. Accordingly, the electronic device <NUM> and the second external electronic device <NUM> may perform data communication <NUM> using the same channel without channel switching.

Referring to <FIG>, an electronic device <NUM> may establish a first connection <NUM> based on a first communication protocol (e.g., Wi-Fi) with a first external electronic device <NUM>. For example, the electronic device <NUM> and the first external electronic device <NUM> may negotiate a channel for communication (e.g., channel <NUM>), and the electronic device <NUM> and the first external electronic device <NUM> may establish a first connection <NUM> using the negotiated channel, thereby transmitting and receiving data.

A second external electronic device <NUM> capable of configuring a NAN cluster - based second connection <NUM> with the electronic device <NUM> may establish a third connection <NUM> based on a third communication protocol (e.g., Wi-Fi or Wi-Fi direct) with a third external electronic device <NUM>. The second external electronic device <NUM> may establish a third connection <NUM> using a channel (e.g., channel <NUM>) negotiated with the third external electronic device <NUM>, thereby transmitting and receiving data.

A fourth external electronic device <NUM> capable of configuring a NAN cluster - based fourth connection <NUM> with the electronic device <NUM> may establish a fifth connection <NUM> based on a third communication protocol (e.g., Wi-Fi or Wi-Fi Direct) with a fifth external electronic device <NUM>. The fourth external electronic device <NUM> may establish a fifth connection <NUM> using a channel (e.g., channel <NUM>) negotiated with the fifth external electronic device <NUM>, thereby transmitting and receiving data.

The electronic device <NUM> may identify the second external electronic device <NUM> and the fourth external electronic device <NUM> using the second communication protocol (e.g., a NAN). For example, the electronic device <NUM> may transmit and receive a beacon, an SDF), or an NAF within a synchronized time duration (e.g., a DW), thereby identifying the second external electronic device <NUM> and the fourth external electronic device <NUM>.

The electronic device <NUM> may schedule a data path based on the second communication protocol in consideration of information related to the first connection <NUM>, the third connection <NUM>, and the fifth connection <NUM>. For example, the electronic device may configure at least one FAW in the interval between synchronized time durations, and may perform data communication. The electronic device <NUM> may identify at least one of a NAN availability attribute, an extended WLAN infrastructure attribute, or an unaligned schedule attribute using at least one of a beacon, an SDF, or an NAF transmitted from the second external electronic device <NUM> or the fourth external electronic device <NUM>. For example, the electronic device <NUM> may identify information related to at least one of the third connection <NUM> of the second external electronic device <NUM> or the fourth connection <NUM> of the fourth external electronic device <NUM>, based on at least one of the NAN availability attribute, the extended WLAN infrastructure attribute, or the unaligned schedule attribute.

Referring to <FIG>, in step <NUM>, the electronic device <NUM> may subscribe to a discovery signal (e.g., a beacon) transmitted from the second external electronic device <NUM>. For example, if the second external electronic device <NUM> broadcasts or unicasts a discovery signal, the electronic device <NUM> may receive the broadcast or unicast discovery signal to subscribe to NAN service discovery. The discovery signal may include connection state information of the second external electronic device <NUM>. The electronic device <NUM> may identify a connection state of the second external electronic device <NUM> (e.g., the third connection <NUM>), based on the discovery signal transmitted from the second external electronic device <NUM>. For example, the electronic device <NUM> may identify Wi-Fi channel information (e.g., channel <NUM>) of the third connection <NUM>, based on the discovery signal received from the second external electronic device <NUM>.

In step <NUM>, the electronic device <NUM> may publish a discovery signal including its own connection state information. For example, the electronic device <NUM> may issue a beacon indicating the operation of a NAN service to the second external electronic device <NUM>. The second external electronic device <NUM> may subscribe to a discovery signal issued from the electronic device <NUM>, and may identify a connection state of the electronic device <NUM> (e.g., the first connection <NUM>).

In step <NUM>, the electronic device <NUM> may subscribe to a discovery signal transmitted from the fourth external electronic device <NUM>. For example, if the fourth external electronic device <NUM> broadcasts or unicasts a discovery signal, the electronic device <NUM> may receive the broadcast or unicast discovery signal to subscribe to NAN service discovery. The discovery signal may include connection state information of the fourth external electronic device <NUM>. The electronic device <NUM> may identify a connection state of the fourth external electronic device <NUM> (e.g., the fifth connection <NUM>), based on the discovery signal transmitted from the fourth external electronic device <NUM>. For example, the electronic device <NUM> may identify Wi-Fi channel information (e.g., channel <NUM>) of the fifth connection <NUM>, based on the discovery signal received from the fourth external electronic device <NUM>.

In step <NUM>, the electronic device <NUM> may publish a discovery signal including its own connection state information. For example, the electronic device <NUM> may issue a beacon indicating the operation of a NAN service to the fourth external electronic device <NUM>. The fourth external electronic device <NUM> may subscribe to a discovery signal issued from the electronic device <NUM>, and may identify a connection state of the electronic device <NUM> (e.g., the first connection <NUM>).

The order of steps <NUM> to <NUM> may vary, or steps <NUM> to <NUM> may be performed simultaneously.

In step <NUM>, the electronic device <NUM> may produce a first message, based at least in part on the first connection <NUM>, the third connection <NUM>, or the fifth connection <NUM>, and may transmit the same to the second external electronic device <NUM>. The first message may be included in at least one of a beacon, an SDF, or an NAF to then be transmitted to the second external electronic device <NUM>. The first message may be configured in the form of a NAN availability attribute and/or an unaligned schedule attribute. The electronic device <NUM> may include a data link schedule proposal (e.g., a schedule request) based on the second communication protocol in the NAN availability attribute and/or the unaligned schedule attribute.

In step <NUM>, if the second message includes "acceptance" or "modification proposal", the electronic device <NUM> may transmit a schedule confirmation message in response to the second message using the second communication protocol. Based on the schedule confirmation message, the second external electronic device <NUM> may identify that the schedule was determined. Transmission of the schedule confirmation message may optionally be performed. For example, the electronic device <NUM> may omit step <NUM>.

In step <NUM>, the electronic device <NUM> may transmit the first message to the fourth external electronic device <NUM> using the second communication protocol. The first message may be included in at least one of a beacon, an SDF, or an NAF to then be transmitted to the fourth external electronic device <NUM>. The first message may be configured in the form of a NAN availability attribute and/or an unaligned schedule attribute. The electronic device <NUM> may include a data link schedule proposal (e.g., a schedule request) based on the second communication protocol in the NAN availability attribute and/or the unaligned schedule attribute.

In step <NUM>, the electronic device <NUM> may receive, from the fourth external electronic device <NUM>, a third message in response to the first message. The third message may be configured as a schedule response including one of "acceptance", "refusal", or "modification proposal".

In step <NUM>, if the third message includes "acceptance" or "modification proposal", the electronic device <NUM> may transmit a schedule confirmation message in response to the third message using the second communication protocol. Based on the schedule confirmation message, the fourth external electronic device <NUM> may identify that the schedule was determined. Transmission of the schedule confirmation message may optionally be performed. For example, the electronic device <NUM> may omit step <NUM>.

In step <NUM>, the electronic device <NUM> may schedule a second-communication protocol-based (NAN) data link, based at least in part on the third message received from the fourth external electronic device <NUM>, and may perform second-communication protocol-based data communication with the fourth external electronic device <NUM>.

<FIG> illustrates a schedule proposal according to the method illustrated in <FIG>. The electronic device <NUM> may produce the schedule proposal shown in <FIG> as a part of step <NUM> or <NUM> described with reference to <FIG>.

A data link schedule proposal (e.g., a schedule request) based on the second communication protocol may be included in a first message configured in the form of a NAN availability attribute and/or an unaligned schedule attribute. In addition, the NAN availability attribute and/or the unaligned schedule attribute may be included in at least one of a beacon, an SDF, or an NAF.

The electronic device <NUM> may produce a second-communication protocol-based data path schedule proposal, based at least in part on the first connection <NUM>, the third connection <NUM>, and/or the fifth connection <NUM>. For example, the electronic device may configure at least one FAW in an interval <NUM> between synchronized time durations (e.g., DW0, DW1, or DW2), and may schedule a data path.

Referring to <FIG>, a first NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. As another example, a second NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. As another example, a third NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. The first availability attribute <NUM>, the second NAN availability attribute <NUM>, and/or the third NAN availability attribute <NUM> may include band information on the respective FAWs.

<FIG> illustrates when an unaligned schedule attribute is included. For example, a first NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. As another example, a second unaligned schedule attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs. As another example, a third NAN availability attribute <NUM> may produce a FAW (e.g., NAN slot #<NUM>) configured as channel <NUM>, a start offset of <NUM> * <NUM> TUs, a bit duration of <NUM> * <NUM> TUs, and a period of <NUM> * <NUM> TUs.

<FIG> illustrates an allocation range of a data link when scheduling of the electronic device is completed according to the method of <FIG> or <FIG>. For example, if the electronic device <NUM> receives, from the second external device <NUM>, a second message including "acceptance" in response to the first message, and if the electronic device <NUM> receives, from the fourth external device <NUM>, a third message including "acceptance" in response to the first message, the electronic device <NUM>, the second external electronic device <NUM>, and the fourth external electronic device <NUM> may continue to perform data communication <NUM> or <NUM> while performing channel switching (e.g., channel <NUM> → channel <NUM> → channel <NUM>) simultaneously. For example, the second external electronic device <NUM> and the fourth external electronic device <NUM> may perform channel switching, based on the second-communication protocol-based data link schedule proposal (e.g., a schedule request) received from the electronic device <NUM>.

An electronic device according to embodiments disclosed herein may include 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 home appliance. The electronic devices are not limited to those described above.

As used herein, the term "module" may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms such as "logic," "logic block," "part," or "circuitry". For example, the module may be implemented in a form of an application-specific integrated circuit (ASIC).

Embodiments as set forth herein may be implemented as software including one or more instructions that are stored in a storage medium that is readable by a machine. For example, a processor of the machine may invoke and execute at least one of the one or more instructions stored in the storage medium, thereby enabling the machine to be operated to perform at least one function according to the invoked at least one instruction. The term "non-transitory" indicates that the storage medium is a tangible device, and does not include a signal, but does not differentiate between where data is semi-permanently and temporarily stored in the storage medium.

A method according to embodiments of the disclosure may be included and provided in a computer program product. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store (e.g., Play Store<IMG>), or between two user devices (e.g., smart phones) directly.

Each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities. One or more components of the above-described components or operations may be omitted, or one or more other components or operations may be added. In such a case, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. Operations performed by the module, the program, or another component may be performed sequentially, in parallel, repeatedly, or heuristically, one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.

Claim 1:
An electronic device (<NUM>, <NUM>) comprising:
a communication module (<NUM>) configured to support a first communication protocol and a second communication protocol;
a processor (<NUM>) operably connected to the communication module (<NUM>); and
a memory (<NUM>) operably connected to the processor (<NUM>),
wherein the memory (<NUM>) stores instructions that, when executed, enable the processor (<NUM>) to:
establish (<NUM>) a first connection based on the first communication protocol with a first external electronic device;
identify (<NUM>) a second external electronic device (<NUM>) by obtaining identification information (<NUM>) corresponding to the second external electronic device (<NUM>) and a connection state of the second external electronic device (<NUM>) using the second communication protocol;
produce (<NUM>) a first message including a proposed schedule related to at least one further available window, FAW, determined based at least in part on information about the first connection and the connection state of the second external electronic device (<NUM>), the at least one determined FAW being included in an interval between synchronized time durations, wherein the first message comprises at least one of channel information, band information, a start offset, a bit duration, and a period, which are related to the at least one determined FAW;
transmit (<NUM>) the produced first message to the second external electronic device (<NUM>) using the second communication protocol;
receive (<NUM>), from the second external electronic device (<NUM>), a second message in response to the first message using the second communication protocol, wherein the second message is configured as a schedule response comprising one of acceptance, refusal, or modification proposal with respect to the proposed schedule; and
schedule (<NUM>), based at least in part on the received second message, a data link based on the second communication protocol.