Enhanced data path structure for multi-band operations in wireless communications

This disclosure describes systems, methods, and devices related to data path structure for multi-band operation. A neighbor awareness networking (NAN) device may determine a first NAN data link (NDL) associated with a first frequency band, a first processing core, and a first NAN management interface (NMI). The NAN device may determine a second NDL associated with a second frequency band, a second processing core, and a second NMI. The NAN device may send one or more multi-band indications of at least one of the first NMI or the second NMI, the one or more multi-band indications being indicative of at least one of the first frequency band or the second frequency band. The NAN device may establish a NAN data path (NDP) with a second NAN device using at least one of the first NDL or the second NDL.

TECHNICAL FIELD

This disclosure generally relates to systems, methods, and devices for wireless communications and, more particularly, to data path structure for multi-band operation.

BACKGROUND

Wireless devices are becoming widely prevalent. Recently, there has been a shift in technology to support direct wireless communications between wireless devices. Neighbor awareness networking (NAN) may refer to a specification for Wi-Fi for device and/or service discovery and peer-to-peer communication. NAN may describe the formation of a cluster of devices (referred to as a NAN cluster) for devices in physical proximity to one another.

DETAILED DESCRIPTION

Example embodiments described herein provide certain systems, methods, and devices for providing data path structure for multi-band operation.

Neighbor Awareness Networking (NAN) is a peer-to-peer discovery and communication protocol defined by the IEEE 802.11 communication standards. The NAN protocol establishes synchronized timing and slots for station devices (STAs) so that STAs may discover each other and exchange data communications using specific slots. For example, the STAs may discover each other during a discovery window (DW), then two STAs may establish a data path (e.g., a NAN data path—NDP) and agree on specific slots referred to as NAN data links (NDLs) to facilitate data communication between the STAs.

An established NDL may be used for executing/exchanging multiple services between the two NAN devices. Different services may have different requirements like security and addresses, for example. As a result, specific NAN data paths (NDPs) may be built for different services. The address that may be used for a NDP may be called a NAN data interface (NDI). An address that may be used for discovery before establishing a NDP may be called a NAN management interface (NMI).

Some NDIs and NMIs and some NDPs and NDLs may be agnostic to a frequency band used between two NAN devices (e.g., some NDIs and NMIs and some NDPs and NDLs may be used for different frequency bands). The ability to use different frequency bands may be possible because the most common frequency bands between two NAN devices may include the 2.4 GHz band and the 5 GHz band, and the medium access control (MAC) operation for these two bands may be provided by one processing core (e.g., a single hardware chip). Operations for other frequency bands, such as higher frequency bands at 60 GHz, may be supported by separate processing cores (e.g., the 60 GHz band may require a different chip than a chip designed to support the 2.4 GHz and 5 GHz bands) due to different frequency modulations needed for the different frequency bands, and because the processing core supporting the lower 2.4 GHz and 5 GHz frequency bands may support an omni-directional antenna, while the processing core supporting an antenna at a higher frequency band such as 60 GHz may support a directional antenna which may be beamforming-trained and may use a different MAC. For example, just because a processing core may support a 2.4 GHz and 5 GHz frequency in Wi-Fi or other wireless communications does not mean that the same processing core may support another higher frequency Wi-Fi communication. MAC and other modifications to a processing core may be needed to support a higher frequency band, and the operations supporting the different frequency bands may require coordination.

A NAN MAC may facilitate synchronization in a NAN cluster (e.g., multiple NAN devices synchronized to a common time source) in which a NAN Device is operating by participating in a NAN synchronization beacon frame transmission. As part of the synchronization function, the NAN MAC may run a time synchronization factor (TSF) timer. The NAN MAC is also responsible for transmitting NAN discovery beacon frames and conducting passive NAN discovery to find out available NAN clusters.

A NAN discovery engine which may be used by services of a NAN device may be accessed through a NMI. A NAN device may keep a NMI and may maintain one or more NDI addresses. The NMI and NDI may be globally unique or locally administrated. A NDI may be the same as a NMI. A NAN device may use the NMI or NDI as a transmitter address for any management frames sent within a NAN cluster. A NAN device may use the NMI or NDI of an intended recipient NAN device as a receiver address for any unicast management frames sent within a NAN cluster, and may use the broadcast address as a receiver address for management frames destined for any NAN devices within a NAN cluster. When a NAN device sets up a NDP with a peer NAN device, it may select an NDI for the NDP. The NAN device may use the NDI as a transmitter address for any data frames associated with that NDP. A NAN Device may use the same NDI for multiple different NDPs, or it may use different NDIs for different NDPs. A NDL may be uniquely identified by the NMIs of the two NAN devices that established the NDL.

Services used by NAN devices may operate better using certain frequency bands, and therefore the processing cores associated with those frequency bands. For example, higher frequency bands may be less reliable for transmissions of longer distances than lower frequency bands. A NAN device using a service such as a voice service may experience better stability using a 2.4 GHz or 5 GHz frequency band than using a 60 GHz or other high-frequency band, or transmissions of longer distances may be more reliable in a 2.4 GHz or 5 GHz frequency band than using a 60 GHz or other high-frequency band. A NAN device may transfer a NDP for a service from a NDL in one frequency band to another frequency band based on the needs of the service, such as transmission distance. Such a transfer may require switching operations from one processing core to another processing core. For example, switching a NDP from a 2.4 GHz or 5 GHz frequency band to a 60 GHz or other high-frequency band may require switching operations from one processing core to another processing core with different characteristics, such as different MAC characteristics and different antenna settings. Thus, to switch operations between processing cores may require enhanced coordination.

As Wi-Fi devices moves to multi-band capability, for example with the addition of a 60 GHz frequency band, Wi-Fi devices may need an additional processing core to facilitate 60 GHz operations due to different baseband (BB) and lower MAC operations. As a result, a corresponding design consideration for NAN data interfaces and a NAN data structure may require corresponding changes.

Example embodiments of the present disclosure relate to systems, methods, and devices for a data path structure for multi-band operation.

In one embodiment, a data path structure for multi-band operation system may define the following data architecture for accommodating the 60 GHz band operation.

In one embodiment, in option (1): a separate NDL may be built for 60 GHz band. One of the NAN devices may use a different NMI to set up the NDL in the 60 GHz band. A NAN device may indicate to another NAN device the NMI used by the same NAN device in different band. The NMI in a different band may be communicated to the other NAN device by using the multi-band element defined in the IEEE 802.11 specification, for example. The NMI in a different band may be indicated by defining new multi-band attribute. For example, NAN measurement frame sent during a discovery window and/or a NAN frame sent during an NDL negotiation may indicate the NMI. A NDP may be set up to use the NDL in a 2.4 GHz/5 GHz band, the 60 GHz band, or both bands (e.g., based on a distance between the NAN devices). The same NDI may be used for the NDL in the 2.4 GHz/5 GHz band or the 60 GHz band. A NDP may be transferred from the NDL in the 60 GHz band to the 2.4 GHz/5 GHz band, or vice versa (e.g., based on a distance between the NAN devices).

In one embodiment, in option (2): one NDL (e.g., pipe) may be built for the 2.4 GHz/5 GHz/60 GHz band (e.g., one NDL for both the 2.4 GHz/5 GHz band and the 60 GHz band). This may represent a direct extension of an existing data structure. Only one NMI may be used for the NDL setup. A NDP may indicate a requirement of transmitting in certain bands. Option (2) may be a subcase of option (1) depending on the usage of NMI on different bands between two devices.

In one embodiment, an advantage of option (1) may be because a different MAC core may be used for NAN operations in the 2.4 GHz/5 GHz band than for the 60 GHz band, the nature of NAN communications may be different in the 60 GHz (or other higher frequency) band. For example, the range/distance between devices may impact which NAN services are available. A schedule setup operation may use a separate data link from the NDL setup. Of two NAN devices in communication, one NAN device may use the same NMI for different cores, while the other NAN device may use a different NMI for respective cores.

In one embodiment, option (2) may be useful when a device may unify a NAN operation of two different MAC cores (e.g., a 2.4 GHz/5 GHz MAC core and a 60 GHz MAC core) into a single chip. Because a data link in the 60 GHz band may be unstable due to beamforming training and line of sight requirements, a NAN service such as a voice service (e.g., a service requiring a stable operation) may be better in the 2.4 GHz/5 GHz band. Thus, a NAN device may request a transfer from the 60 GHz band to the 2.4 GHz/5 GHz band based on the type of service used by the NAN devices.

In one embodiment, using option (1), a NAN device may maintain the operation of multiple NMIs in different bands. For example, one NMI may be used for the 2.4/5 GHz band, and another NMI may be used for the 60 GHz or other higher frequency band. A NDL may be established for any NMI in any band. A NDL between two NAN devices may be determined by a pair of NMIs used by the two NAN devices for NDL setup. The NAN devices may send frames including a multi-band element, which may communicate the NMI for any band (including NMIs for multiple bands). An STA MAC address field of the multi-band element may indicate the NMI used for a band indicated by the multi-band element (e.g., an NMI may be associated with the band indicated by a band identifier included in the multi-band element). A basic service set identifier (BSSID) of the multi-band element may be set to indicate a NAN cluster identifier associated with a NAN cluster. If a discovery beacon is transmitted in a band indicated by the multi-band element, a beacon interval field of the multi-band element may be set to a discovery beacon interval (e.g., the time interval between the transmission of discovery beacons) in a band indicated by the multi-band element, and a TSF offset field of the multi-band element may be set to indicate a TSF offset of a discovery beacon in the indicated band to a discovery beacon in a current band. If a discovery beacon is not transmitted in a band indicated by the multi-band element, the beacon interval field and the TSF offset fields may be reserved. The multi-band element may be included in an element container attribute of a NAN frame.

In one embodiment, the multi-band information may be included in a multi-band attribute, which may be added to an existing format of the multi-band element. The multi-band information may include an NMI in the band indicated by the multi-band element. The multi-band information may include an operating class (e.g., indicating a channel set for which the multi-band attribute is applicable), a band identifier, and a channel number. Multi-band information may be included during the NDL/NDP setup (e.g., using a NAN data path request/response frame). For example, the multi-band information may be included in a multi-band element in an element container attribute of a frame, or in a multi-band attribute included in a NDL/NDP set up of the 2.4/5 GHz band to indicate the NMI used in the 60 GHz band.

In one embodiment, the multi-band information may be included in a NAN service discovery frame (SDF), NAN action frame (NAF), a NAN synchronization beacon, a NAN discovery beacon, or other NAN frames (e.g., as defined by the NAN technical standard). The multi-band information may be included in a NDL/NDP set up to indicate allowed bands for NDL set up. For example, if a NDL is established between two NAN devices using NMI1and NMI2on a first band, and if the NAN devices also use NMI1and NMI2on a second band, then the NAN devices may apply the NDL to the second band.

In one embodiment, a NDP may be associated with a single NDL or with multiple NDLs. When a NDP is associated with a single NDL, packets of a NDP may be transmitted using the associated NDL. When a NDP is associated with multiple NDLs, packets of the NDP may be transmitted in any of the associated NDLs using link aggregation, for example. The NMIs used by the setup of the NDP may determine which NDL(s) is/are associated with the NDP. A separate NDP set up may be used if a NDP intends to associate with multiple NDLs.

In one embodiment, a NAN device may terminate a NDP on an indicated NDL (e.g., a NDL indicated by a transmitter address or receiver address of a frame). The indicated NDL may refer to an NMI of the NDL. The NDL may be indicated using a NAF.

In one embodiment, a NAN device may select an NDI during a NDP setup. For example, the same NDI may be used with different NDLs. If an NDP is associated with only one NDL, a NAN device may indicate the transfer of an NDP to another NDL (e.g., a transfer from a NDL in one band to a NDL in another band). A NAN device may include the multi-band information and may indicate corresponding NMIs on both connected NAN devices to identify a destined NDL used to transfer the NDP.

In one embodiment, a lower MAC layer may provide feedback to an upper MAC layer regarding an available band operation from a peer NAN device. A discovery result function may be used by a NAN device to provide feedback regarding the multi-band information from the peer NAN device. The upper MAC layer may request a band requirement for a NDP setup. A NDP may operate on certain bands and not on other bands, or may have no band operating restrictions. A NAN layer may restrict the transmission of data of a NDP on certain bands based on requirements of a NDP. The NAN layer may set up a NDL based on an indicated NDP requirement. For example, the NAN layer may set up a NDL on certain bands allowed by the NDP requirement. The upper MAC layer may indicate a corresponding NMI of a peer NAN device for a setup which may include the setup of a NDL on a specific band. Request signaling may be included in a data request process.

In one embodiment, using option (2), if only one NMI is used at both NAN peer devices for all bands, then only NDL may need to be established. As a result, one NMI may be used for different bands, eliminating a need to include multi-band information. The upper MAC layer may request a band requirement for a NDP setup. The NDP may operate in some or all bands.

FIG. 1depicts a diagram illustrating an example network, according to some example embodiments of the present disclosure. Wireless network100can include one or more user devices120(e.g.,122,124,126, or128), which may communicate in accordance with wireless standards, such as the IEEE 802.11 communication standards. For example, two or more wireless devices may perform connectivity procedures with one another in order to set up Wi-Fi data sessions, according to some example embodiments of the present disclosure. In the example ofFIG. 1, a wireless communication channel may be established between two or more wireless devices (e.g., user device(s)120), where a first user device120may correspond to a service seeker, and a second user device120may correspond to a service advertiser. A service advertiser may be a wireless device that may advertise and provide one or more of these services over a wireless communication channel. The user device(s)120may be wireless devices that are non-stationary and do not have fixed locations. A service seeker may be a wireless device that is seeking certain services, such as printing, playing content, sending, docking, etc.

In some embodiments, the user devices120can include one or more computer systems similar to that of the functional diagram ofFIG. 8and/or the example machine/system ofFIG. 9.

The user device(s)120may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3GPP standards.

Any of the user devices120(e.g.,122,124,126, or128) may include one or more communications antennas. Communications antennas may be any suitable type of antenna corresponding to the communications protocols used by the user device(s)120. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, IEEE 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, MIMO antennas, or the like. The communications antenna may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals, to and/or from the user devices120(e.g.,122,124,126, or128).

In one or more embodiments, the user devices120(e.g.,122,124,126, or128) may exchange one or more frames140. The frames140may be NAN frames used for multi-band communications. For example, the frames140may include discovery beacons, NAN management frames, SDFs, NAFs, and other frames used in NAN communications. The frames140may indicate multi-band capabilities of NAN devices, including band identifiers, channel numbers, device addresses, and other information. The frames140may be used to discover other devices, request and discover services offered by devices, establish NDLs, and exchange data over NDLs, for example.

Referring toFIG. 2A, the synchronization structure200may include a user device201, a first DW202, one or more slots (e.g., slot204, slot206, slot208), and a second DW210. The first DW202may be associated with a time unit212representing the length of time for the first DW202for the user device201. The slot204may be associated with a time unit214representing the length of time for the slot204and one or more additional slots (e.g., slot206, slot208) during a DW interval216. The DW interval216may represent the time between the first DW202and the second DW210. The user device201may be a NAN device and may discover other NAN devices (e.g., the user devices120ofFIG. 1) during the first DW202, then NAN devices may establish a NDP and agree on specific NDL slots (e.g., slot204, slot206, slot208) to facilitate data communication.

Referring toFIG. 2B, the NDL establishment250may include a first user device251and a second user device252, which may be NAN devices. The first user device251may use a first DW253to discover other NAN devices such as the second user device252. The first user device251may transmit using a NDL254, and the second user device252may transmit using a NDL258and a NDL260. The first user device251and the second user device252may use the NAN synchronization structure200ofFIG. 2Ato communicate data until a next DW256. The NDLs may be agreed upon by the first user device251and the second user device252for transmissions during a DW interval262, which may represent the time interval between the DW253and the DW256.

An established NDL (e.g., NDL254) may be used for multiple services between the first user device251and the second user device252. Different service may have different requirements like security and device addresses. As a result, the NDPs may be built specifically for a particular respective service. An NDP may have an address referred to as the NDI. The first user device251and the second user device252may use an address for discovery before setting up respective NDPs may be a NMI.

FIG. 3depicts an illustrative schematic diagram300of data path structure for multi-band operation.

Referring toFIG. 3, a user device302and a user device304may have NAN capabilities. The user device302may have a NMI306associated with an address, and the NMI306may facilitate operations of multiple NDIs, such as NDI308, NDI310, and NDI312. The NMI306may use an address to establish the NDL314, which may include multiple NDPs, such as NDP316, NDP318, and NDP320. The NDI308may serve as the address for the NDP316. The NDI310may serve as the address for the NDP318. The NDI312may serve as the address for the NDP320. The NDP316and the NDP318may use NDI322of the user device304(or the NDI322may be multiple NDIs), and the NDP320may use NDI324of the user device304(or may share a NDI of the user device304with any other NDP). The NDI322may serve as an address of the user device304for the NDP316and the NDP318. The NDI324may serve as an address of the user device304for the NDP320. A NMI326of the user device304may serve as an address for the NDI322and the NDI324.

An example of two different MAC processing cores used for 2.4 GHz/5 GHz and 60 GHz bands is shown inFIG. 4. A baseband and lower-level MAC processing core402(e.g., a single chip) may facilitate communications on a 2.4 GHz band404and a 5 GHz band406. A baseband and lower-level MAC processing core408(e.g., a single chip) may facilitate communications for a 60 GHz band410or other higher-frequency band. The baseband and lower-level MAC processing core402and the baseband and lower-level MAC processing core408may be separate chips used in NAN devices (e.g., the user devices120ofFIG. 1). Baseband and lower-level MAC processing core402may support communications defined by the IEEE 802.11 b/a/g/n/ac communication standards. The baseband and lower-level MAC processing core408may support communications defined by the IEEE 802.11ad communication standard.

Referring toFIGS. 3 and 4, a NAN data interface may be used in operations in multiple bands when those bands are the 2.4 GHz band and the 5 GHz band because, as shown inFIG. 4, a single processing core may support the NAN interface in either band. However, as Wi-Fi devices move to multi-band capability, specifically with the addition of 60 GHz band for Wi-Fi capabilities, Wi-Fi devices may need the baseband and lower-level MAC processing core408. To accommodate the use of multiple processing cores supporting different baseband and MAC operations, the NDI and data structure may be modified. For example, Wi-Fi devices may need to coordinate the functions of each processing core.

Because the baseband and lower-level MAC processing core408may support a higher bandwidth than the baseband and lower-level MAC processing core402, the data procedures supported by the two processing cores may be different. For example, at different frequencies, the modulation schemes may be different. In addition, the baseband and lower-level MAC processing core402may facilitate omni-directional communications, whereas the 60 GHz band410may use a higher frequency and may need more directional antennas which are beamforming trained. The baseband and lower-level MAC processing core408may use different MAC operations. For example, if a NAN device with the two processing cores were using the 2.4 GHz band404or the 5 GHz band406, and moved to a location proximal enough to a connected peer NAN device to use the 60 GHz band410, the NAN devices may switch to the baseband and lower-level MAC processing core408with coordination. However, simply adding the two different processing cores to a device may not result in coordinated NAN communications with multi-band capabilities without some modifications and enhancements.

FIG. 5Adepicts an illustrative schematic diagram of a data path structure500for a multi-band operation system, in accordance with one or more example embodiments of the present disclosure.

Referring toFIG. 5A, a user device502and a user device504may be peer NAN devices. The user device502may use NMI506and NMI508. The NMI506may support multiple NDIs, such as NDI510, NDI512, and NDI514. The NMI508may support multiple NDIs, such as NDI516,518, and NDI520. The user device504may use NMI522and NMI524. The NMI522may support NDI526and NDI528. The NMI524may support NDI528. The NMI524may support NDI530, NDI532, and NDI534. The user device502and the user device504may use NDL536for 2.4/5 GHz operations, and may use NDL538for 60 GHz operations. The NDI526and the NDI510may serve as respective addresses for NDP540between the NDI526and the NDI510using the NDL536. The NDI526and the NDI512may serve as respective addresses for NDP542between the NDI512and the NDI526using the NDL536. The NDI528and the NDI514may serve as respective addresses for NDP544between the NDI514and the NDI528using the NDL536. The NDPs using the NDL536may be used for respective NAN services on the 2.4 GHz band or the 5 GHz band.

Still referring toFIG. 5A, the NDI516and the NDI530may serve as respective addresses for NDP546between the NDI516and the NDI530using the NDL538. The NDI518and the NDI532may serve as respective addresses for NDP548between the NDI518and the NDI532using the NDL538. The NDI520and the NDI534may serve as respective addresses for NDP550between the NDI520and the NDI534using the NDL538. The NDPs of the NDL538may support the same or different services as the NDPs of the NDL536. For example, the NDP540and the NDP546may support the same service, but the NDP540may not support the same security requirements as the NDP546on a 60 GHz band, so the NDP546may use the NDI516as an address for the user device502and the NDI530as an address for the user device504while the NDP540may use the NDI510as an address for the user device502and the NDI526as an address for the user device504.

In one or more embodiments, the data path structure500may refer to option (1) for accommodating a multi-band operation including a 60 GHz band operation. In option (1), the NDL538may be built for the 60 GHz band and may be separate from the NDL536for the 2.4 GHz and 5 GHz bands. The user device502may use the NMI508to establish the NDL538in the 60 GHz band. The user device502may use the 2.4/5 GHz band to communicate the NMI508(e.g., using the one or more frames140ofFIG. 1). A NDL may be established for any NMI and may be determined by the NMIs used by the devices to establish the NDL.

In one or more embodiments, the NMI508may be indicated to the user device504by including a multi-band element in a frame, as defined by an IEEE 802.11 specification, for example. The NMI508may be communicated to the user device504by defining a multi-band attribute as explained further herein. NDPs may be established to use the NDL536, the NDL538, or both the NDL536and the NDL538. A same NDI may be used for the NDL536and the NDL538or 60 GHz. For example, the NDI510may be the same as the NDI516, the NDI518, and/or the NDI520. An NDP may be transferred between the NDL536and the NDL538. For example, if the NDI510is the same as the NDI516, the NDP540may be transferred to the NDP546, and vice versa. A NDP transfer may be useful in situations when use of a NAN service may be improved by using a different band. For example, a NAN voice service may be more stable in the 2.4/5 GHz band than the 60 GHz band, and NAN services which may use directional antennas may be better suited for the 60 GHz band. The distance between the user device502and the user device504may be considered by either device in determining whether to switch between bands. For example, 60 GHz operations may be more appropriate for shorter distances between the devices. Therefore, which processing core (e.g., chip) is used by a device may depend on the distance between peer devices.

In one or more embodiments, the NMI506may be the same as the NMI508, or the NMIs for the user device502may be different. If the user device502uses the same NMI for the NMI506and the NMI508, the user device504does not have to use the same NMI for the NMI522and the NMI524. When using different NDLs, the NMIs used for the respective NDLs may use different MAC addresses. For example, in the NDL536, the NMI506may use a MAC address (or some other address) for the 2.4/5 GHz bands, while the NMI508may use another MAC address for the NDL538in a higher frequency band. The NMI506and the NMI508may be the same NMI for the 2.4/5 GHz and 60 GHz bands, but the NMI522and the NMI524may be different for the user device504, and may have different MAC addresses to allow for associating the MAC addresses with a respective NDL/frequency band.

FIG. 5Bdepicts an illustrative schematic diagram of a data path structure560for a multi-band operation system, in accordance with one or more example embodiments of the present disclosure.

Referring toFIG. 5B, a user device562and a user device564may have NAN capabilities, and may share a NDL565for both the 2.4/5 GHz bands and the 60 GHz band. The user device562may use NMI566to support NDI568, NDI570, and NDI572. The user device564may use NMI574to support NDI576and NDI578. The NDI576may serve as the address for the user device564for NDP582and NDP584(e.g., an NDI may support multiple NDPs). The NDI578may serve as the address for the user device564for NDP586. The NDP582may be between the NDI568and the NDI576. The NDP584may be between the NDI570and the NDI576. The NDP586may be between the NDI572and the NDI578.

The data path structure560may represent option (2) for accommodating a multi-band operation including a 60 GHz band operation. The NDL565may be built for the 2.4/5 GHz band operations and the 60 GHz band operations by leveraging the NAN data structure for the 2.4/5 GHz bands. A single NMI for each device may be used to establish the NDL565. The NDPs may indicate requirements of transmitting data in a respective frequency band.

In one or more embodiments, the user device562and the user device564may unify the multi-band operations supported by multiple MAC processing cores (e.g., a 2.4/5 GHz processing core and a 60 GHz processing core). Because of the unification, the NDL565may support NDPs for operations in different bands.

In one or more embodiments, option (2) may be useful when a data link in one frequency band becomes unstable (e.g., a 60 GHz operation becomes unstable due to line of sight and beamforming training requirements), a NAN service requiring a more stable operation may be transferred to another band. The user device562or the user device564may request the transfer by indicating the frequency band.

FIG. 6depicts a portion600of a multi-band frame element, in accordance with one or more example embodiments of the present disclosure.

Referring toFIG. 6, the portion600may include an element ID field602(e.g., with 1 octet), a length field604(e.g., with 1 octet), a multi-band control field606(e.g., with 1 octet), a band ID field608(e.g., with 1 octet), an operating class field610(e.g., with 1 octet), a channel number field612(e.g., with 1 octet), a BSSID field614(e.g., with 6 octets), a beacon interval field616(e.g., with 2 octets), a TSF offset field618(e.g., with 8 octets), a multi-band connection capability field620(e.g., with 1 octet), a fast session transfer (FST) session timeout field622(e.g., with 1 octet), a STA MAC address field624(with 0-6 octets), a pairwise cipher suite count field626(e.g., with 0-2 octets), and a pairwise cipher suite list field628(e.g., with a variable number of octets).

The portion600of multi-band information may be carried in a multi-band element of a NAN frame (e.g., the one or more frames140ofFIG. 1), such as a NAN frame defined in an IEEE 802.11 specification. The STA MAC address field624may indicate the NMI used in a band indicated (e.g., by the band ID field608) by the multi-band element. The BSSID field614may be set to the NAN cluster ID so that NAN devices in the NAN cluster may identify the frame carrying the portion600. If a discovery beacon is transmitted in the indicated band, the beacon interval field616may be set to the discovery beacon interval (e.g., the DW interval216ofFIG. 2A) in the indicated band, and the TSF offset field618may be set to indicate the TSF offset of the discovery beacon in the indicated band to the discovery beacon in the current band. If there is no discovery beacon transmitted in the indicated band, the beacon interval field616and the TSF offset field618may be reserved. The multi-band element may be included in an element container attribute of a NAN frame. The multi-band information of the portion600may be carried in a new multi-band attribute. An example of the fields of the portion600is shown below in Table 1.

TABLE 1Multi-band Attribute:Field NameSizeValueDescriptionAttribute ID10x00Identifies the type of NAN attribute.Length211Length of the following field in theattribute.Multi-Band Control1VariableBand ID1VariableThe Band ID field provides theidentification of the frequency bandrelated to the Operating Class andChannel Number fields.Operating Class1VariableOperating Class indicates the channel setfor which the Multi-band attributeapplies.Channel Number1VariableOperating Class andChannel Number together specify thechannel frequency and spacing for whichthe Multi-band attributeapplies.FST Session Timeout1VariableThe FSTSessionTimeout field is used inthe FST Setup Request frame to indicatethe timeout value for FSTsession setup protocol. TheFSTSessionTimeout field contains theduration, in TUs, after which the FSTsetup is terminated.STA MAC Address6VariableThe STA MAC Address field containsthe NMI MAC address that thetransmitting STA uses while operating onthe channel indicated in this attribute.

The multi-band information of the portion600may include the NMI in the indicated band (e.g., as indicated by the STA MAC address field624). The multi-band information may be included in an NDL/NDP setup (e.g., a NAN data path request/response frame) to “bootstrap” the NDL/NDP configuration in another band. For example, multi-band information of the portion600may be carried in a multi-band element within an element container attribute, or may be carried in a multi-band attribute included in the NDL/NDP setup of 2.4 GHz/5 GHz band to indicate the NMI used in 60 GHz band and bootstrap the NDL/NDP setup in 60 GHz band.

In one or more embodiments, multi-band information may be included in a NAN SDF, NAN NAF, NAN synchronization beacon, NAN discovery beacon, and so on to bootstrap multi-band discovery.

In one or more embodiments, multi-band information may be included in the NDL/NDP setup to indicate the allowed band (e.g., using the band ID field608) for a NDL setup (e.g., if a NDL is established between two devices with NMI1and NMI2on band1). Two peer NAN devices may use NMI1and NMI2on band2, so the NDL also may apply to band2. A NDP may be associated with only one NDL. Packets of a NDP may be transmitted in the associated NDL. A NDP may be associated with more than one NDL. Packets of a NDP may be transmitted in the associated NDL(s) for link aggregation. The NMIs used by the setup of a NDP between two devices may determine the NDL associated with the NDP. A separate NDP setup may be required if a NDP intends to associate with multiple NDLs. A NAN device may terminate a NDP on an indicated NDL. The indicated NDL may be signaled by including a transmitter address (TA) and/or receiver address (RA), either of which may refer to the NMI of the NDL of a NAF, such as a data path termination NAF. Thus, to terminate a NDP, a NAF may indicate the associated NMI(s) for the NDP by including the TA and/or RA.

In one or more embodiments, a NAN device may be free to choose a NDI during NDP setup, (e.g., a same NDI may be used in different NDLs). If a NDP is associated with one NDL, a device may indicate a transfer of the NDP to another NDL when a transfer is desirable. A NAN device may include the multi-band information and indicate the corresponding NMIs on both devices to identify the destination NDL to which to transfer the NDP. A lower-layer MAC level (e.g., of processing circuitry) may use event to feed back the available band operation from a peer device to an upper layer MAC level. A “discovery result” event may be used to feed back multi-band information from a peer device to the upper layer.

In one or more embodiments, an upper layer MAC level may request a band requirement for NDP setup (e.g., a band restriction). A NDP may operate on any band or may be restricted to certain bands. A band requirement may indicate the bands to which a NDP may be limited. The NAN layer of processing circuitry may restrict transmission of NAN data for the NDP to certain bands based on the requirement. The NAN layer also may establish a NDL based on an indicated band requirement. For example, the NAN layer may establish NDLs using certain bands based on the indicated requirement. An upper layer of the processing circuitry may indicate the corresponding NMI of a peer device for set up, which may include the setup of a NDL on a specific band. The request signaling may be included in the data request event method.

In one or more embodiments, and option (2) may be a subcase of option (1) because option (2) may use the general design of option (1)2. In particular, if only one NMI is used on both peer devices for all bands, then only one NDL may be established. As a result, in option (2), the NAN specification may allow only one NMI to be used for a different band. Such a restriction may eliminate the need to include multi-band information in a NAN frame.

FIG. 7Aillustrates a flow diagram of illustrative process700for an illustrative data path structure for multi-band operation system, in accordance with one or more example embodiments of the present disclosure.

At block702, processing circuitry of a device (e.g., the user device(s)120ofFIG. 1) may determine a first NDL with a first frequency band, and a first processing core. The first frequency band may be a 2.4 GHz/5 GHz frequency band, a 60 GHz frequency band, or another frequency band. The first NDL may support one or more NMIs and one or more NDIs at a first NAN device, and may support one or more NMIs and one or more NDIs at a second NAN device. The first NDL may support multiple NDPs between respective NDIs at the NAN devices, and the respective NDPs may be established specifically for respective NAN services.

At block704, the processing circuitry may determine a second NDL with a second frequency band, and a second processing core. The second frequency band may be different from the first frequency band. The second processing core may be the same processing core as the first processing core (e.g., as shown inFIG. 5B), or a different processing core than the first processing core (e.g., as shown inFIG. 5A). The second processing core may use a same NMI or different NMI at either NAN device connected by the second NDL. The NDPs used by the second processing core may be the same NDPs as the NDPs of the first NDL, but may support different security and other features for the same NAN services as any corresponding NDP of the first NDL, or may be different NDPs supporting different NAN services than the NDPs of the first NDL.

At block706, the processing circuitry may cause the device to send one or more multi-band indications of at least one of the first NMI or the second NMI. The multi-band indications may be included in a multi-band element, which may communicate the NMI for any band (including NMIs for multiple bands). An STA MAC address field of the multi-band element may indicate the NMI used for a band indicated by the multi-band element (e.g., an NMI may be associated with the band indicated by a band identifier included in the multi-band element). A BSSID of the multi-band element may be set to indicate a NAN cluster identifier associated with a NAN cluster. If a discovery beacon is transmitted in a band indicated by the multi-band element, a beacon interval field of the multi-band element may be set to a discovery beacon interval (e.g., the time interval between the transmission of discovery beacons) in a band indicated by the multi-band element, and a TSF offset field of the multi-band element may be set to indicate a TSF offset of a discovery beacon in the indicated band to a discovery beacon in a current band. If a discovery beacon is not transmitted in a band indicated by the multi-band element, the beacon interval field and the TSF offset fields may be reserved. The multi-band information may include an NMI in the band indicated by the multi-band element. The multi-band information may include an operating class (e.g., indicating a channel set for which the multi-band attribute is applicable), a band identifier, and a channel number. Multi-band information may be included during the NDL/NDP setup (e.g., using a NAN data path request/response frame). For example, the multi-band information may be included in a multi-band element in an element container attribute of a frame, or in a multi-band attribute included in a NDL/NDP set up of the 2.4/5 GHz band to indicate the NMI used in the 60 GHz band. The multi-band information may be included in a NAN service discovery frame (SDF), NAN action frame (NAF), a NAN synchronization beacon, a NAN discovery beacon, or other NAN frames (e.g., as defined by the NAN technical standard). The multi-band information may be included in a NDL/NDP set up to indicate allowed bands for NDL set up. For example, if a NDL is established between two NAN devices using NMI1and NMI2on a first band, and if the NAN devices also use NMI1and NMI2on a second band, then the NAN devices may apply the NDL to the second band.

At block708, the device may establish a NDP with another NAN device using the first NDL or the second NDL. Establishing the NDP may include building a direct connection between the device and another NAN device, without an intermediate AP, to communicate data for NAN services and operations. The NDP may be established for the purpose of supporting a particular NAN service agreed upon by the device and the other NAN device.

FIG. 7Billustrates a flow diagram of illustrative process750for an illustrative data path structure for multi-band operation system, in accordance with one or more example embodiments of the present disclosure.

At block752, a device (e.g., the user device(s)120ofFIG. 1) may identify one or more multi-band indications received from a NAN device using at least one of a first NMI or a second NMI. A BSSID of the multi-band element may be set to indicate a NAN cluster identifier associated with a NAN cluster. If a discovery beacon is transmitted in a band indicated by the multi-band element, a beacon interval field of the multi-band element may be set to a discovery beacon interval (e.g., the time interval between the transmission of discovery beacons) in a band indicated by the multi-band element, and a TSF offset field of the multi-band element may be set to indicate a TSF offset of a discovery beacon in the indicated band to a discovery beacon in a current band. If a discovery beacon is not transmitted in a band indicated by the multi-band element, the beacon interval field and the TSF offset fields may be reserved. The multi-band information may include an NMI in the band indicated by the multi-band element. The multi-band information may include an operating class (e.g., indicating a channel set for which the multi-band attribute is applicable), a band identifier, and a channel number. Multi-band information may be included during the NDL/NDP setup (e.g., using a NAN data path request/response frame). For example, the multi-band information may be included in a multi-band element in an element container attribute of a frame, or in a multi-band attribute included in a NDL/NDP set up of the 2.4/5 GHz band to indicate the NMI used in the 60 GHz band. The multi-band information may be included in a NAN service discovery frame (SDF), NAN action frame (NAF), a NAN synchronization beacon, a NAN discovery beacon, or other NAN frames (e.g., as defined by the NAN technical standard). The multi-band information may be included in a NDL/NDP set up to indicate allowed bands for NDL set up. For example, if a NDL is established between two NAN devices using NMI1and NMI2on a first band, and if the NAN devices also use NMI1and NMI2on a second band, then the NAN devices may apply the NDL to the second band.

At block754, the device may determine that the one or more multi-band indications are indicative of a first frequency band or a second frequency band. The multi-band indications may be included in a multi-band element, which may communicate the NMI for any band (including NMIs for multiple bands). An STA MAC address field of the multi-band element may indicate the NMI used for a band indicated by the multi-band element (e.g., an NMI may be associated with the band indicated by a band identifier included in the multi-band element).

At block756, the device may establish a NDP with the NAN device using the first NDL or the second NDL based on which frequency band was indicated by the multi-band indications. Establishing the NDP may include building a direct connection between the device and another NAN device, without an intermediate AP, to communicate data for NAN services and operations. The NDP may be established for the purpose of supporting a particular NAN service agreed upon by the device and the other NAN device.

FIG. 8shows a functional diagram of an exemplary communication station800in accordance with some embodiments. In one embodiment,FIG. 8illustrates a functional block diagram of a communication station that may be suitable for use as a user device120(FIG. 1) in accordance with some embodiments. The communication station800may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.

The communication station800may include communications circuitry802and a transceiver810for transmitting and receiving signals to and from other communication stations using one or more antennas801. The transceiver810may be a device comprising both a transmitter and a receiver that are combined and share common circuitry (e.g., communication circuitry802). The communication circuitry802may include amplifiers, filters, mixers, analog to digital and/or digital to analog converters. The transceiver810may transmit and receive analog or digital signals. The transceiver810may allow reception of signals during transmission periods. This mode is known as full-duplex, and may require the transmitter and receiver to operate on different frequencies to minimize interference between the transmitted signal and the received signal. The transceiver810may operate in a half-duplex mode, where the transceiver810may transmit or receive signals in one direction at a time.

The communications circuitry802may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station800may also include processing circuitry806and memory808arranged to perform the operations described herein. In some embodiments, the communications circuitry802and the processing circuitry806may be configured to perform operations detailed inFIGS. 1-9.

In accordance with some embodiments, the communications circuitry802may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry802may be arranged to transmit and receive signals. The communications circuitry802may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry806of the communication station800may include one or more processors. In other embodiments, two or more antennas801may be coupled to the communications circuitry802arranged for sending and receiving signals. The memory808may store information for configuring the processing circuitry806to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory808may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory808may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

The machine (e.g., computer system)900may include a hardware processor902(e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory904and a static memory906, some or all of which may communicate with each other via an interlink (e.g., bus)908. The machine900may further include a power management device932, a graphics display device910, an alphanumeric input device912(e.g., a keyboard), and a user interface (UI) navigation device914(e.g., a mouse). In an example, the graphics display device910, alphanumeric input device912, and UI navigation device914may be a touch screen display. The machine900may additionally include a storage device (i.e., drive unit)916, a signal generation device918(e.g., a speaker), a data path structure for an enhanced multi-band operation device919, a network interface device/transceiver920coupled to antenna(s)930, and one or more sensors928, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine900may include an output controller934, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).

The storage device916may include a machine readable medium922on which is stored one or more sets of data structures or instructions924(e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions924may also reside, completely or at least partially, within the main memory904, within the static memory906, or within the hardware processor902during execution thereof by the machine900. In an example, one or any combination of the hardware processor902, the main memory904, the static memory906, or the storage device916may constitute machine-readable media.

The data path structure for the enhanced multi-band operation device919may carry out or perform any of the operations and processes (e.g., process700ofFIG. 7A, process750ofFIG. 7B) described and shown above.

In one embodiment, in option (1): a separate NDL may be built for 60 GHz band. The enhanced multi-band operation device919of the NAN device may use a different NMI to set up the NDL in the 60 GHz band. A NAN device may indicate to another NAN device the NMI used by the same NAN device in different band. The NMI in a different band may be communicated to the other NAN device by using the multi-band element defined in the IEEE 802.11 specification, for example. The NMI in a different band may be indicated by defining new multi-band attribute. For example, NAN measurement frame sent during a discovery window and/or a NAN frame sent during an NDL negotiation may indicate the NMI. A NDP may be set up to use the NDL in a 2.4 GHz/5 GHz band, the 60 GHz band, or both bands (e.g., based on a distance between the NAN devices). The same NDI may be used for the NDL in the 2.4 GHz/5 GHz band or the 60 GHz band. A NDP may be transferred from the NDL in the 60 GHz band to the 2.4 GHz/5 GHz band, or vice versa (e.g., based on a distance between the NAN devices).

In one embodiment, in option (2): one NDL (e.g., pipe) may be built for the 2.4 GHz/5 GHz/60 GHz band (e.g., one NDL for both the 2.4 GHz/5 GHz band and the 60 GHz band). This may represent a direct extension of an existing data structure. Only one NMI may be used for the NDL setup. The enhanced multi-band operation device919may send an NDP to indicate a requirement of transmitting in certain bands. Option (2) may be a subcase of option (1) depending on the usage of NMI on different bands between two devices.

In one embodiment, the enhanced multi-band operation device919may use a schedule setup operation with a separate data link from the NDL setup. Of two NAN devices in communication, one NAN device may use the same NMI for different cores, while the other NAN device may use a different NMI for respective cores.

In one embodiment, a device may unify a NAN operation of two different MAC cores (e.g., a 2.4 GHz/5 GHz MAC core and a 60 GHz MAC core) into a single chip. The enhanced multi-band operation device919may be included in multiple cores—one for the 2.4 GHz/5 GHz band, and one or more additional cores for other bands—or may be support multiple bands from the same core. Because a data link in the 60 GHz band may be unstable due to beamforming training and line of sight requirements, a NAN service such as a voice service (e.g., a service requiring a stable operation) may be better in the 2.4 GHz/5 GHz band. Thus, a NAN device may request a transfer from the 60 GHz band to the 2.4 GHz/5 GHz band based on the type of service used by the NAN devices.

In one embodiment, using option (1), the enhanced multi-band operation device919may maintain the operation of multiple NMIs in different bands. For example, one NMI may be used for the 2.4/5 GHz band, and another NMI may be used for the 60 GHz or other higher frequency band. A NDL may be established for any NMI in any band. A NDL between two NAN devices may be determined by a pair of NMIs used by the two NAN devices for NDL setup. The NAN devices may send frames including a multi-band element, which may communicate the NMI for any band (including NMIs for multiple bands). An STA MAC address field of the multi-band element may indicate the NMI used for a band indicated by the multi-band element (e.g., an NMI may be associated with the band indicated by a band identifier included in the multi-band element). A basic service set identifier (BSSID) of the multi-band element may be set to indicate a NAN cluster identifier associated with a NAN cluster. If a discovery beacon is transmitted in a band indicated by the multi-band element, a beacon interval field of the multi-band element may be set to a discovery beacon interval (e.g., the time interval between the transmission of discovery beacons) in a band indicated by the multi-band element, and a TSF offset field of the multi-band element may be set to indicate a TSF offset of a discovery beacon in the indicated band to a discovery beacon in a current band. If a discovery beacon is not transmitted in a band indicated by the multi-band element, the beacon interval field and the TSF offset fields may be reserved. The multi-band element may be included in an element container attribute of a NAN frame.

In one embodiment, the enhanced multi-band operation device919may determine the multi-band information and include the multi-band information in a multi-band attribute, which may be added to an existing format of the multi-band element. The multi-band information may include an NMI in the band indicated by the multi-band element. The multi-band information may include an operating class (e.g., indicating a channel set for which the multi-band attribute is applicable), a band identifier, and a channel number. Multi-band information may be included during the NDL/NDP setup (e.g., using a NAN data path request/response frame). For example, the multi-band information may be included in a multi-band element in an element container attribute of a frame, or in a multi-band attribute included in a NDL/NDP set up of the 2.4/5 GHz band to indicate the NMI used in the 60 GHz band.

In one embodiment, the enhanced multi-band operation device919may include the multi-band information in a NAN service discovery frame (SDF), NAN action frame (NAF), a NAN synchronization beacon, a NAN discovery beacon, or other NAN frames (e.g., as defined by the NAN technical standard). The multi-band information may be included in a NDL/NDP set up to indicate allowed bands for NDL set up. For example, if a NDL is established between two NAN devices using NMI1and NMI2on a first band, and if the NAN devices also use NMI1and NMI2on a second band, then the NAN devices may apply the NDL to the second band.

In one embodiment, the enhanced multi-band operation device919may terminate a NDP on an indicated NDL (e.g., a NDL indicated by a transmitter address or receiver address of a frame). The indicated NDL may refer to an NMI of the NDL. The NDL may be indicated using a NAF.

In one embodiment, the enhanced multi-band operation device919may select an NDI during a NDP setup. For example, the same NDI may be used with different NDLs. If an NDP is associated with only one NDL, a NAN device may indicate the transfer of an NDP to another NDL (e.g., a transfer from a NDL in one band to a NDL in another band). A NAN device may include the multi-band information and may indicate corresponding NMIs on both connected NAN devices to identify a destined NDL used to transfer the NDP.

In one embodiment, the enhanced multi-band operation device919may restrict the transmission of data of a NDP on certain bands based on requirements of a NDP. The NAN layer may set up a NDL based on an indicated NDP requirement. For example, the NAN layer may set up a NDL on certain bands allowed by the NDP requirement. The upper MAC layer may indicate a corresponding NMI of a peer NAN device for a setup which may include the setup of a NDL on a specific band. Request signaling may be included in a data request process.

In one embodiment, using option (2), if only one NMI is used at both NAN peer devices for all bands, then only NDL may need to be established by the enhanced multi-band operation device919. As a result, one NMI may be used for different bands, eliminating a need to include multi-band information. The upper MAC layer may request a band requirement for a NDP setup. The NDP may operate in some or all bands.

It is understood that the above are only a subset of what the data path structure for the enhanced multi-band operation device919may be configured to perform and that other functions included throughout this disclosure may also be performed by the data path structure for the enhanced multi-band operation device919.

The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.

The following examples pertain to further embodiments.

Example 1 may include a device comprising memory and processing circuitry configured to: establish an neighbor awareness networking data link (NDL) with a neighbor awareness networking (NAN) device; determine a multiband attribute comprising one or more fields; and cause to send a NAN frame comprising the multiband attribute to the NAN device.

Example 2 may include the device of example 1 and/or some other example herein, wherein the NDL it may be associated with a 60 GHz frequency band.

Example 3 may include the device of example 1 and/or some other example herein, wherein the multiband attribute comprises at least one of an operating class operating class, a band identification (ID), or a channel number.

Example 4 may include the device of example 1 and/or some other example herein, wherein the NAN frame may be a NAN data link (NDL) or a null data packet (NDP) frame.

Example 5 may include the device of example 1 and/or some other example herein, wherein the memory and the processing circuitry are further configured to determine a null data packet (NDP) frame may be associated with one NAN data link (NDL).

Example 6 may include the device of example 1 and/or some other example herein, wherein the memory and the processing circuitry are further configured to determine an indication to transfer the NDP two another NDL.

Example 7 may include the device of example 1 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.

Example 8 may include the device of example 7 and/or some other example herein, further comprising an antenna coupled to the transceiver.

Example 9 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: establishing an neighbor awareness networking data link (NDL) with a neighbor awareness networking (NAN) device; determining a multiband attribute comprising one or more fields; and causing to send a NAN frame comprising the multiband attribute to the NAN device.

Example 10 may include the non-transitory computer-readable medium of example 9 and/or some other example herein, wherein the NDL it may be associated with a 60 GHz frequency band.

Example 11 may include the non-transitory computer-readable medium of example 9 and/or some other example herein, wherein the multiband attribute comprises at least one of an operating class operating class, a band identification (ID), or a channel number.

Example 12 may include the non-transitory computer-readable medium of example 9 and/or some other example herein, wherein the NAN frame may be a NAN data link (NDL) or a null data packet (NDP) frame.

Example 13 may include the non-transitory computer-readable medium of example 9 and/or some other example herein, wherein the operations further comprise determining a null data packet (NDP) frame may be associated with one NAN data link (NDL).

Example 14 may include the non-transitory computer-readable medium of example 9 and/or some other example herein, wherein the operations further comprise determining an indication to transfer the NDP two another NDL.

Example 15 may include a method comprising: establishing, by one or more processors, an neighbor awareness networking data link (NDL) with a neighbor awareness networking (NAN) device; determining a multiband attribute comprising one or more fields; and causing to send a NAN frame comprising the multiband attribute to the NAN device.

Example 16 may include the method of example 15 and/or some other example herein, wherein the NDL it may be associated with a 60 GHz frequency band.

Example 17 may include the method of example 15 and/or some other example herein, wherein the multiband attribute comprises at least one of an operating class operating class, a band identification (ID), or a channel number.

Example 18 may include the method of example 15 and/or some other example herein, wherein the NAN frame may be a NAN data link (NDL) or a null data packet (NDP) frame.

Example 19 may include the method of example 15 and/or some other example herein, further comprising determining a null data packet (NDP) frame may be associated with one NAN data link (NDL).

Example 20 may include the method of example 15 and/or some other example herein, further comprising determining an indication to transfer the NDP two another NDL.

Example 21 may include an apparatus comprising means for: establishing an neighbor awareness networking data link (NDL) with a neighbor awareness networking (NAN) device; determining a multiband attribute comprising one or more fields; and causing to send a NAN frame comprising the multiband attribute to the NAN device.

Example 22 may include the apparatus of example 21 and/or some other example herein, wherein the NDL it may be associated with a 60 GHz frequency band.

Example 23 may include the apparatus of example 21 and/or some other example herein, wherein the multiband attribute comprises at least one of an operating class operating class, a band identification (ID), or a channel number.

Example 24 may include the apparatus of example 21 and/or some other example herein, wherein the NAN frame may be a NAN data link (NDL) or a null data packet (NDP) frame.

Example 25 may include the apparatus of example 21 and/or some other example herein, further comprising determining a null data packet (NDP) frame may be associated with one NAN data link (NDL).

Example 26 may include the apparatus of example 21 and/or some other example herein, further comprising determining an indication to transfer the NDP two another NDL.

Example 28 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-26, or any other method or process described herein.

Example 29 may include a method, technique, or process as described in or related to any of examples 1-26, or portions or parts thereof.

Example 31 may include a method of communicating in a wireless network as shown and described herein.

Example 32 may include a system for providing wireless communication as shown and described herein.

Example 33 may include a device for providing wireless communication as shown and described herein.