Apparatus, system and method of communicating in a neighbor awareness networking (NAN) cluster

Some demonstrative embodiments include apparatuses, systems and/or methods of communicating in an awareness cluster. For example, an apparatus may include logic and circuitry configured to cause a first Neighbor Awareness Networking (NAN) device to communicate during one or more Discovery Windows (DWs) of a NAN cluster; to setup a NAN Data link (NDL) with a second NAN device of the NAN cluster, the NDL belonging to a NAN Data Cluster (NDC) having a NDC base schedule; and to communicate data with the second NAN device via the NDL according to the NDC base schedule.

TECHNICAL FIELD

Embodiments described herein generally relate to communicating in a Neighbor Awareness Networking (NAN) Cluster.

BACKGROUND

Awareness networking, for example, according to a Wireless Fidelity (Wi-Fi) Aware Specification, may enable wireless devices, for example, Wi-Fi devices, to perform device/service discovery, e.g., in their close proximity.

The awareness networking may include forming a cluster, e.g., a Wi-Fi Aware cluster, for devices in proximity. Devices in the same Wi-Fi Aware cluster may be configured to follow the same time schedule, e.g., a discovery window (DW), for example, to facilitate cluster formation and/or to achieve low power operation.

DETAILED DESCRIPTION

Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing Wireless Fidelity (WiFi) Alliance (WFA) Specifications (includingWi-Fi Neighbor Awareness Networking(NAN)Technical Specification, Version1.0, May 1, 2015) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing WFA Peer-to-Peer (P2P) specifications (WiFi P2P technical specification, version1.5, Aug. 4, 2014) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless-Gigabit-Alliance (WGA) specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHY Specification Version1.1, April 2011, Final specification) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.11 standards (IEEE 802.11-2012, IEEE Standard for Information technology—Telecommunications and information exchange between systems Local and metropolitan area networks—Specific requirements Part11: Wireless LAN Medium Access Control(MAC)and Physical Layer(PHY)Specifications, Mar. 29, 2012; IEEE802.11ac-2013 (“IEEE P802.11ac-2013, IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control(MAC)and Physical Layer(PHY)Specifications—Amendment4: Enhancements for Very High Throughput for Operation in Bands below 6GHz”, December, 2013);IEEE802.11ad (“IEEE P802.11ad-2012, IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control(MAC)and Physical Layer(PHY)Specifications—Amendment3: Enhancements for Very High Throughput in the 60GHz Band”, 28 December, 2012); and/orIEEE-802.11REVmc(“IEEE802.11-REVmc™/D3.0, June 2014draft standard for Information technology—Telecommunications and information exchange between systems Local and metropolitan area networks Specific requirements; Part11: Wireless LAN Medium Access Control(MAC)and Physical Layer(PHY)Specification”)) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing cellular specifications and/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE) and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.

The term “communicating” as used herein with respect to a communication signal includes transmitting the communication signal and/or receiving the communication signal. For example, a communication unit, which is capable of communicating a communication signal, may include a transmitter to transmit the communication signal to at least one other communication unit, and/or a communication receiver to receive the communication signal from at least one other communication unit. The verb communicating may be used to refer to the action of transmitting or the action of receiving. In one example, the phrase “communicating a signal” may refer to the action of transmitting the signal by a first device, and may not necessarily include the action of receiving the signal by a second device. In another example, the phrase “communicating a signal” may refer to the action of receiving the signal by a first device, and may not necessarily include the action of transmitting the signal by a second device.

Some demonstrative embodiments may be used in conjunction with a WLAN, e.g., a wireless fidelity (WiFi) network. Other embodiments may be used in conjunction with any other suitable wireless communication network, for example, a wireless area network, a “piconet”, a WPAN, a WVAN and the like.

The phrase “peer to peer (PTP) communication”, as used herein, may relate to device-to-device communication over a wireless link (“peer-to-peer link”) between devices. The PTP communication may include, for example, a WiFi Direct (WFD) communication, e.g., a WFD Peer to Peer (P2P) communication, wireless communication over a direct link within a QoS basic service set (BSS), a tunneled direct-link setup (TDLS) link, a STA-to-STA communication in an independent basic service set (IBSS), or the like.

Some demonstrative embodiments are described herein with respect to WiFi communication. However, other embodiments may be implemented with respect to any other communication scheme, network, standard and/or protocol.

Reference is now made toFIG. 1, which schematically illustrates a block diagram of a system100, in accordance with some demonstrative embodiments.

As shown inFIG. 1, in some demonstrative embodiments system100may include a wireless communication network including one or more wireless communication devices, e.g., wireless communication devices102,140,160and/or180.

In some demonstrative embodiments, devices102,140,160and/or180may include, operate as, and/or perform the functionality of one or more STAs. For example, device102may include at least one STA, and/or device140may include at least one STA.

In some demonstrative embodiments, devices102,140,160and/or180may include, operate as, and/or perform the functionality of one or more WLAN STAs.

In some demonstrative embodiments, devices102,140,160and/or180may include, operate as, and/or perform the functionality of one or more Wi-Fi STAs.

In some demonstrative embodiments, devices102,140,160and/or180may include, operate as, and/or perform the functionality of one or more BT devices.

In some demonstrative embodiments, devices102,140,160and/or180may include, operate as, and/or perform the functionality of one or more Neighbor Awareness Networking (NAN) STAs.

In some demonstrative embodiments, devices102,140,160and/or180may include, operate as, and/or perform the functionality of one or more location measurement STAs.

In one example, a station (STA) may include a logical entity that is a singly addressable instance of a medium access control (MAC) and physical layer (PHY) interface to the wireless medium (WM). The STA may perform any other additional or alternative functionality.

In some demonstrative embodiments, devices102,140,160and/or180may include, operate as, and/or perform the functionality of any other devices and/or STAs.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to operate as, and/or to perform the functionality of, an access point (AP) STA.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to operate as, and/or to perform the functionality of, a non-AP STA.

In one example, an AP may include an entity that contains a station (STA), e.g., one STA, and provides access to distribution services, via the wireless medium (WM) for associated STAs. The AP may perform any other additional or alternative functionality.

In one example, a non-AP STA may include a STA that is not contained within an AP. The non-AP STA may perform any other additional or alternative functionality.

In one example, device102may be configured to operate as, and/or to perform the functionality of an AP STA, and/or device140may be configured to operate as, and/or to perform the functionality of a non-AP STA.

In some demonstrative embodiments, device102may include, for example, one or more of a processor191, an input unit192, an output unit193, a memory unit194, and/or a storage unit195; and/or devices140,160and/or180may include, for example, one or more of a processor181, an input unit182, an output unit183, a memory unit184, and/or a storage unit185. Devices102,140,160and/or180may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of one or more of devices102,140,160and/or180may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of one or more of devices102,140,160and/or180may be distributed among multiple or separate devices.

In some demonstrative embodiments, wireless communication devices102,140,160and/or180may be capable of communicating content, data, information and/or signals via a wireless medium (WM)103. In some demonstrative embodiments, wireless medium103may include, for example, a radio channel, a cellular channel, a Global Navigation Satellite System (GNSS) Channel, an RF channel, a Wireless Fidelity (WiFi) channel, an IR channel, a Bluetooth (BT) channel, and the like.

In some demonstrative embodiments, wireless communication medium103may include a wireless communication channel over a 2.4 Gigahertz (GHz) frequency band, a 5 GHz frequency band, a millimeterWave (mmWave) frequency band, e.g., a 60 GHz frequency band, a Sub 1 Gigahertz (S1G) band, and/or any other frequency band.

In some demonstrative embodiments, devices102,140,160and/or180may include one or more radios including circuitry and/or logic to perform wireless communication between devices102,140,160,180and/or one or more other wireless communication devices. For example, device102may include at least one radio114, and/or device140may include at least one radio144.

In some demonstrative embodiments, radio114may include one or more wireless receivers (Rx) including circuitry and/or logic to receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio114may include at least one receiver116, and/or radio144may include at least one receiver146.

In some demonstrative embodiments, radios114and/or144may include one or more wireless transmitters (Tx) including circuitry and/or logic to transmit wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio114may include at least one transmitter118, and/or radio144may include at least one transmitter148.

In some demonstrative embodiments, radios114and/or144may be configured to communicate over a 2.4 GHz band, a 5 GHz band, an mmWave band, a SIG band, and/or any other band.

In some demonstrative embodiments, radios114and/or144may include, or may be associated with, one or more antennas107and/or147, respectively.

In one example, device102may include a single antenna107. In another example, device102may include two or more antennas107.

In one example, device140may include a single antenna147. In another example, device140may include two or more antennas147.

Antennas107and/or147may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas107and/or147may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. Antennas107and/or147may include, for example, antennas suitable for directional communication, e.g., using beamforming techniques. For example, antennas107and/or147may include a phased array antenna, a multiple element antenna, a set of switched beam antennas, and/or the like. In some embodiments, antennas107and/or147may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas107and/or147may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

In some demonstrative embodiments, wireless communication devices102,140,160and/or180may form, and/or may communicate as part of, a wireless local area network (WLAN).

In some demonstrative embodiments, wireless communication devices102,140,160and/or180may form, and/or may communicate as part of, a WiFi network.

In some demonstrative embodiments, wireless communication devices102,140,160and/or180may form, and/or may communicate as part of, a WiFi Direct (WFD) network, e.g., a WiFi direct services (WFDS) network, and/or may perform the functionality of one or more WFD devices.

In one example, wireless communication devices102,140,160and/or180may include, or may perform the functionality of a WiFi Direct device.

In some demonstrative embodiments, wireless communication devices102,140,160and/or180may be capable of performing awareness networking communications, for example, according to an awareness protocol, e.g., a WiFi aware protocol, and/or any other protocol, e.g., as described below.

In some demonstrative embodiments, wireless communication devices102,140,160and/or180may be capable of forming, and/or communicating as part of, a Neighbor Awareness Networking (NAN) network, e.g., a WiFi NAN or WiFi Aware network, and/or may perform the functionality of one or more NAN devices (“WiFi aware devices”).

In some demonstrative embodiments, wireless communication medium103may include a direct link, for example, a PTP link, e.g., a WiFi direct P2P link or any other PTP link, for example, to enable direct communication between wireless communication devices102,140,160and/or180.

In some demonstrative embodiments, wireless communication devices102,140,160and/or180may perform the functionality of WFD P2P devices. For example, devices102,140,160and/or180may be able to perform the functionality of a P2P client device, and/or P2P group Owner (GO) device.

In other embodiments, wireless communication devices102,140,160and/or180may form, and/or communicate as part of, any other network, and/or may perform the functionality of any other wireless devices or stations.

In some demonstrative embodiments, devices102,140,160and/or180may include one or more applications configured to provide, share, and/or to use one or more services, e.g., a social application, a file sharing application, a media application and/or the like, for example, using an awareness network, NAN network (“WiFi Aware network”), a PTP network, a P2P network, WFD network, or any other network.

In some demonstrative embodiments, device102may execute an application125and/or an application126. In some demonstrative embodiments, device140may execute an application145.

In some demonstrative embodiments, devices102,140,160and/or180may include a controller configured to control one or more functionalities of devices102,140,160and/or180, for example, one or more functionalities of communication, e.g., awareness networking communications, WiFi Aware (NAN) communication and/or any other communication, between devices102,140,160and/or180and/or other devices, and/or any other functionality, e.g., as described below. For example, device102may include a controller124, and/or device140may include a controller154.

In some demonstrative embodiments, controller124may be configured to perform one or more functionalities, communications, operations and/or procedures between wireless communication devices102,140,160and/or180, and/or one or more other devices, e.g., as described below.

In some demonstrative embodiments, controller124may include circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, Media-Access Control (MAC) circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic, and/or any other circuitry and/or logic, configured to perform the functionality of controller124. Additionally or alternatively, one or more functionalities of controller124may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

In one example, controller124may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device102, and/or a wireless station, e.g., a wireless STA implemented by device102, to perform one or more operations, communications and/or functionalities, e.g., as described herein.

In one example, controller154may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device140, and/or a wireless station, e.g., a wireless STA implemented by device140, to perform one or more operations, communications and/or functionalities, e.g., as described herein.

In one example, controller124may perform one or more functionalities of a NAN engine, e.g., a NAN discovery engine (DE), for example to process one or more service queries and/or responses, e.g., from applications and/or services on devices102,140,160and/or180, and/or one or more other devices.

In one example, controller154may perform one or more functionalities of a NAN engine, e.g., a NAN discovery engine (DE), for example to process one or more service queries and/or responses, e.g., from applications and/or services on devices102,140,160and/or180, and/or one or more other devices.

In some demonstrative embodiments, device102may include a message processor128configured to generate, process and/or access one or messages communicated by device102.

In one example, message processor128may be configured to generate one or more messages to be transmitted by device102, and/or message processor128may be configured to access and/or to process one or more messages received by device102, e.g., as described below. In one example, message processor128may be configured to process transmission of one or more messages from a wireless station, e.g., a wireless STA implemented by device102; and/or message processor128may be configured to process reception of one or more messages by a wireless station, e.g., a wireless STA implemented by device102.

In some demonstrative embodiments, device140may include a message processor158configured to generate, process and/or access one or messages communicated by device140.

In one example, message processor158may be configured to generate one or more messages to be transmitted by device140, and/or message processor158may be configured to access and/or to process one or more messages received by device140, e.g., as described below. In one example, message processor158may be configured to process transmission of one or more messages from a wireless station, e.g., a wireless STA implemented by device140; and/or message processor158may be configured to process reception of one or more messages by a wireless station, e.g., a wireless STA implemented by device140.

In some demonstrative embodiments, message processors128and/or158may include circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, Media-Access Control (MAC) circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic, and/or any other circuitry and/or logic, configured to perform the functionality of message processors128and/or158. Additionally or alternatively, one or more functionalities of message processors128and/or158may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

In one example, message processors128and/or158may perform one or more functionalities of a NAN MAC configured to generate, process and/or handle one or more NAN messages, e.g., NAN Beacon frames and/or NAN Service Discovery frames.

In some demonstrative embodiments, at least part of the functionality of message processor128may be implemented as part of radio114.

In some demonstrative embodiments, at least part of the functionality of message processor128may be implemented as part of controller124.

In other embodiments, the functionality of message processor128may be implemented as part of any other element of device102.

In some demonstrative embodiments, at least part of the functionality of controller124, radio114, and/or message processor128may be implemented by an integrated circuit, for example, a chip, e.g., a System in Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio114. For example, the chip or SoC may include one or more elements of controller124, one or more elements of message processor128, and/or one or more elements of radio114. In one example, controller124, message processor128, and radio114may be implemented as part of the chip or SoC.

In some demonstrative embodiments, at least part of the functionality of message processor158may be implemented as part of radio144.

In some demonstrative embodiments, at least part of the functionality of message processor158may be implemented as part of controller154.

In other embodiments, the functionality of message processor158may be implemented as part of any other element of device140.

In some demonstrative embodiments, at least part of the functionality of controller154, radio144, and/or message processor158may be implemented by an integrated circuit, for example, a chip, e.g., a System in Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio144. For example, the chip or SoC may include one or more elements of controller154, one or more elements of message processor158, and/or one or more elements of radio144. In one example, controller154, message processor158, and radio144may be implemented as part of the chip or SoC.

In some demonstrative embodiments, devices102,140,160and/or180may perform the functionality of a device or station, for example, an awareness networking device, a NAN device, a WiFi device, a WiFi Aware device, a WFD device, a WLAN device and/or any other device, capable of discovering other devices according to a discovery protocol and/or scheme.

In some demonstrative embodiments, radios114and/or144may communicate over wireless communication medium103according to an awareness networking scheme, for example, a discovery scheme, for example, a WiFi Aware discovery scheme (“NAN discovery scheme”), and/or any other awareness networking and/or discovery scheme, e.g., as described below.

In some demonstrative embodiments, the awareness networking scheme, e.g., NAN, may enable applications to discover services in their close proximity. For example, the NAN technology may be a low power service discovery, which may, for example, scale efficiently, e.g., in dense Wi-Fi environments.

In some demonstrative embodiments, a device, e.g., wireless communication devices102,140,160and/or180, may include one or more blocks and/or entities to perform network awareness functionality. For example, a device, e.g., devices102,140,160and/or180, may be capable of performing the functionality of a NAN device, may include a NAN MAC and/or a Discovery Engine (DE). In one example, controllers124and/or154may be configured to perform the functionality of the discovery engine, and/or message processors128and/or158may be configured to perform the functionality of the NAN MAC, e.g., as described above. In another example, the functionality of the NAN MAC and/or the Discovery engine may be performed by any other element and/or entity of devices102,140,160and/or180.

In some demonstrative embodiments, the awareness networking scheme may include a discovery scheme or protocol, e.g., as described below.

In some demonstrative embodiments, devices102,140,160and/or180may perform a discovery process according to the awareness networking scheme, for example, to discover each other and/or to establish a wireless communication link, e.g., directional and/or high throughput wireless communication link and/or any other link.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to enable time synchronization between devices102,140,160,180and/or one or more other devices, e.g., performing the functionality of Wi-Fi stations (STAs), for example, such that STAs can discover each other more efficiently and/or quickly.

Some demonstrative embodiments are described below with respect to a NAN discovery scheme, and to NAN discovery frames of the NAN discovery scheme. However, in other embodiments, any other discovery scheme and/or discovery frames may be used.

In some demonstrative embodiments, the discovery scheme may include a plurality of contention-based discovery windows (DWs).

In some demonstrative embodiments, communication during the DWs may be configured to enable time synchronization between Wi-Fi stations (STAs), e.g., devices102,140,160and/or180, so that STAs can find each other more efficiently during a DW.

In some demonstrative embodiments, devices of an awareness network, e.g., a NAN network, may form one or more clusters, e.g., in order to publish and/or subscribe for services. A NAN cluster may be defined by an Anchor Master (AM) (also referred to as a “NAN master device” or “anchor device”). In one example, the AM may include a NAN device, which has the highest rank in the NAN cluster.

In some demonstrative embodiments, NAN data exchange may be reflected by discovery frames, e.g., Publish, Subscribe and/or Follow-Up Service discovery frames (SDF). These frames may include action frames, which may be sent by a device that wishes to publish a service/application, and/or to subscribe to a published service/application at another end.

In one example, one of devices102,140,160and/or180, e.g., device102, may perform the functionality of an AM. The AM may be configured to transmit one or more beacons. Another one of devices102,140,160and/or180, e.g., device140, may be configured to receive and process the beacons.

In one example, devices102,140,160and/or180may perform the functionality of NAN devices, e.g., belonging to a NAN cluster, which may share a common set of NAN parameters, for example, including a common NAN timestamp, and/or a common time period between consecutive discovery windows (DWs). The NAN timestamp may be communicated, for example, as part of a NAN beacon frame, which may be communicated in the NAN cluster. In one example, the NAN timestamp may include a Time Synchronization Function (TSF) value, for example, a cluster TSF value, or any other value.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to discover one another over a predefined communication channel (“the social channel”). In one example, the Channel6in the 2.4 GHz band may be defined as the NAN social channel. Any other channel may be used as the social channel.

In some demonstrative embodiments, devices102,140,160and/or180may transmit discovery frames, e.g., SDFs, during the plurality of DWs, e.g., over the social channel. For example the NAN AM may advertise the time of the DW, during which NAN devices may exchange SDFs.

In one example, devices102,140,160and/or180may transmit the discovery frames to discover each other, for example, to enable using the one or more services provided by applications125and/or126.

In some demonstrative embodiments, devices102,140,160and/or180may communicate during a DW according to a contention mechanism. For example, devices102,140,160and/or180may check whether or not a channel is unoccupied prior to an attempt to transmit a discovery frame during the discovery window.

In some demonstrative embodiments, a device of devices102,140,160and/or180, e.g., device102, may not transmit the discovery frame during the DW, e.g., if the channel is occupied. In some demonstrative embodiments, device102may transmit the discovery frame during the DW, e.g., if the channel is unoccupied.

In some embodiments, the discovery frame may be transmitted as a group addressed, e.g., broadcast or multicast, discovery frame. In other embodiments, the discovery frame may be transmitted as any other type of flame.

In some demonstrative embodiments, the discovery frame may nut require an acknowledgement frame. According to these embodiments, a transmitter of the discovery frame may not backoff a transmission of the discovery frame.

In some demonstrative embodiments, the discovery frame transmitted by device102during the DW may be configured to enable other devices or services that are running on other devices to discover the services on device102.

In some demonstrative embodiments, devices of system100may utilize availability information, e.g., in the form of an Availability Interval Bitmap and/or Further Availability Map, for example, to allow a device of devices102,140,160and/or180, to advertise its availability, for example, in terms of at least one channel and one or more timeslots, during which the device may be available, e.g., active (“awake”), for example, to perform post NAN activities.

In one example, the availability information may be communicated as part of an Availability Attribute, e.g., including a 32-bit bitmap for 32 timeslots, for example, wherein each timeslot is 16 milliseconds (ins) long. For example, each bit that is not zero may represent a timeslot, during which a device sending the Availability Attribute is to be awake and available to send and/or receive data in a specified method.

In some demonstrative embodiments, device102may be part of an awareness cluster, e.g., a NAN cluster109.

In some demonstrative embodiments, NAN cluster109may include one or more other NAN devices130.

In one example, one or more NAN devices130may include devices140,160and/or180.

In another example, one or more NAN devices130may include any other NAN devices of NAN cluster109.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to communicate according to a Wi-Fi Aware specification and/or any other awareness networking specification, which may be configured to allow a group of devices to discover other devices/services nearby and/or in close proximity, e.g., with low power.

In some demonstrative embodiments, devices102,140,160and/or180may form NAN cluster109and may synchronize to the same clock, e.g., as described above.

In one example, all devices of the same cluster, e.g., NAN cluster109, may converge on a time period and channel, e.g., a DW, to facilitate the discovery of services of devices102,140,160and/or180, and/or to achieve low power consumption, e.g., as described above.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to enable data transmission for a specific service among multiple devices, post service discovery.

In some demonstrative embodiments, to enable data transmission post service discovery the two devices may be required to use a common schedule, e.g., to be available at a same channel at a same time.

In some demonstrative embodiments, device102may be configured to determine the schedule for data transmission post service discovery with other devices130, for example, based on a base schedule, e.g., as described below.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to utilize schemes, which may enable devices102,140,160and/or180to transmit data to each other, e.g., without any infrastructure, e.g., directly.

In some demonstrative embodiments, device102and/or device140may establish a Service Data Session (SDS), for example, to communicate, e.g., directly, between devices102and140.

In some demonstrative embodiments, during the SDS, devices102and140may set up a NAN data link (NDL)149, e.g., to support the SDS and/or one or more other SDSs.

In some demonstrative embodiments, a NAN Data Cluster (NDC)129may be defined, for example, for NAN data link149.

In some demonstrative embodiments, the NDC129may include a cluster, which includes NAN devices in the same NAN cluster that share a common base schedule (also referred to as “NDC base schedule” or “base schedule”).

In one example, the NDC129may include NAN devices102,140and/or160of NAN cluster109.

In some demonstrative embodiments, devices of NDC129may be configured to determine, set, define, and/or communicate according to an NDC base schedule, e.g., as described below.

In some demonstrative embodiments, a NAN device, e.g., device102, device140, device160, and/or device180, may be configured to advertise the NDC base schedule, e.g., as described below.

In some demonstrative embodiments, one or more NAN devices, e.g., devices102,140,160and/or180, may be configured to join the NDC129, e.g., as described below.

In some demonstrative embodiments, one or more NAN devices, e.g., devices102,140,160and/or180, may be configured to propagate the NDC base schedule, e.g., as described below.

In some demonstrative embodiments, it may not be advantageous to determine a NDC base schedule according to an algorithm in which, when an NDL between two devices is initially formed, the devices decide on a NDC base schedule; whenever a new NDL is formed with another device in the same NDC, a new base schedule is selected that is a subset and a prefix of the original base schedule; and/or when more and more devices join the NDC more and more new base schedules are added.

In some demonstrative embodiments, this algorithm may be very complex and hard to implement.

In one example, according to this algorithm, a device will have its own base schedule, and the peers of a device having an NDL with the device may also change its base schedule after a new NDL is formed. According to this example, the device may need to constantly poll the peers to confirm the base schedule, and to record the different base schedules of its peers.

Some demonstrative embodiments may provide a scheme, which may enable to determine and use an NDC base schedule in a simplified manner, which may be, for example, easy to implement and/or follow.

In some demonstrative embodiments, a device of NDC129, for example, device102, may be defined to determine an NDC base schedule, e.g., for all the other NAN devices that will join the NDC, e.g., as described below.

In some demonstrative embodiments, the NDC base schedule may include a series of timeslots and channels that are advertised, for example, through a further availability bitmap in a NAN service descriptor.

In some demonstrative embodiments, the NAN device that determines the NDC base schedule may be, for example, the first NAN device that opens an NDC, for example, due to an NDL the NAN device may have with some other NAN device.

In some demonstrative embodiments, the NAN device, which is to determine the NDC base schedule may be referred to as the NDC anchor device.

In some demonstrative embodiments, one or more other NAN devices, e.g., one or more of devices102,140,160and/or180, which wish to join the NDC, e.g., NDC129, may be configured to adopt the NDC base schedule, and to advertise the NDC base schedule, for example, on demand, e.g., whenever a new NDL is formed, e.g., as described below.

In some demonstrative embodiments, two NAN devices, e.g., devices102and/or140, that are part of the same NAN cluster may setup NDL149, e.g., to exchange data between device102and140.

In some demonstrative embodiments, controller124may be configured to control, cause and/or trigger device102to setup the NDL149with device140.

In some demonstrative embodiments, the NDL149may belong to NDC129having an NDC base schedule.

In some demonstrative embodiments, controller124may be configured to control, cause and/or trigger device102to communicate data with device140via the NDL149according to the NDC base schedule of NDC129.

In some demonstrative embodiments, the NDC base schedule of NDC129may be determined by an NDC anchor of the NDC129.

In one example, device102may operate as, and/or perform the functionality of, the NDC anchor of NDC129. According to this example, device102may communicate data with device140via the NDL149according to an NDC base schedule determined by device102.

In some demonstrative embodiments, controller124may be configured to control, cause and/or trigger device102to determine the schedule to be used to communicate with the one or more other NAN devices130based on the NDC base schedule.

In some demonstrative embodiments, controller124may be configured to control, cause and/or trigger device102to setup NDC129as a new NDC, for example, upon setting up the NDL149, e.g., as described below.

In some demonstrative embodiments, controller124may be configured to control, cause and/or trigger device102to setup the NDL149in an existing NDC to which at least one of device102and device140already belongs.

For example, device102may setup the NDL149in NDC129, for example, if device102already belongs to NDC129, e.g., as described below.

In some demonstrative embodiments, according to a first scenario, device102and device140may not be part of the same NDC for the same service, e.g., a service having the same service identifier (ID) as a service identifier of a service corresponding to an existing NDC.

In some demonstrative embodiments, an NDL, e.g., NDL149, may be formed between device102and device140, for example, when device102and device104want to use a common service.

In some demonstrative embodiments, device102and device140may form NDC129with an NDC base schedule, for example, since an NDL between device102and140may be required to be belong to an NDC.

In some demonstrative embodiments, according to the first scenario, the NDC anchor may be determined, set and/or defined based on one or more criteria, e.g., as described below.

In some demonstrative embodiments, the NDC anchor may be the publisher of a service.

In some demonstrative embodiments, a publisher of a service may be a device, which sends a publish message, e.g., a solicited or unsolicited publish, for example, according to a NAN specification.

In some demonstrative embodiments, the NDC anchor may be an unsolicited subscriber to a service.

In some demonstrative embodiments, the NDC anchor may be the initiator of an NDL setup, e.g., the initiator of NDL149.

In some demonstrative embodiments, the NDC anchor may be defined or selected according to any other additional or alternative parameter, attribute and/or criteria.

In some demonstrative embodiments, an identity of the NDC anchor may be indicated in an NDC attribute, e.g., as described below.

In some demonstrative embodiments, the NDC may be related to a common service or application, which may be shared by the two devices. Accordingly, the NDC may be defined, for example, by a service ID and an identifier of the NDC anchor, and/or based on any other information.

In some demonstrative embodiments, the Service ID may be indicated in the NDC attribute, e.g., as described below.

In some demonstrative embodiments, the NDC base schedule may include a combination of one or more timeslots and one or more channels, which may be, for example, suitable for communication by the NDC anchor.

In some demonstrative embodiments, the NDC base schedule may include, for example, at least one timeslot and at least one channel.

In some demonstrative embodiments, an NDL schedule to communicate over an NDL may be a superset of the NDC base schedule, e.g., determined by the NDC anchor.

In some demonstrative embodiments, controller124may be configured to control, cause and/or trigger device102to process an NDC attribute.

In some demonstrative embodiments, the NDC attribute may include at least base schedule information of the NDC base schedule.

In one example, device102may send the NDC attribute to device140. In another example, device102may receive the NDC attribute from device140.

In some demonstrative embodiments, the NDC attribute may include a service identifier (ID) of a service to which the NDC refers. For example, the NDC attribute may include a service ID of application125, e.g., if NDC129refers to application125.

In some demonstrative embodiments, the NDC attribute may include an identifier of an NDC anchor of the NDC129. For example, the NDC attribute may include an identifier, e.g., a MAC address or any other identifier, of device102, for example, if device102is the NDC anchor of the NDC129.

In some demonstrative embodiments, the NDC attribute may include a hop count field to indicate a number of hops between a transmitter of the NDC attribute and an NDC anchor of the NDC, e.g., as described below.

In one example, a device, e.g., a device of devices102,140and/or160, which sets up a NDL with another device, may be configured to maintain a current hop count from the NDC anchor, and may increase the minimum of the current hop count of the device from the NDC anchor by one. The current hop count may be initialized, for example, to255(maximum number), or any other value.

In some demonstrative embodiments, the NDC attribute may include a hop count limit field to indicate a maximal number of hops allowed between a NAN device belonging to the NDC129and the NDC anchor of the NDC.

In some demonstrative embodiments, the NDC anchor may be configured to limit the NDC size, for example, by using a hop count limitation, e.g., in the hop count limit field

In some demonstrative embodiments, an NDC attribute may include one or more of the following fields:

TABLE 1SizeField(octets)ValueDescriptionAttribute ID1TBDIdentifies the type of NAN attribute.Length2VariableLength of the following fields in theattribute.Service ID6VariableService ID this NDC refers toNDC Anchor6VariableMAC address of NDC anchor.Hop count1VariableThe hop from NDC anchorHop count limit1VariableA limitation on the hop count for thisNDCMap Control1VariableThe availability channel and time mapcontrol information, as defined inTable 5-17 of the NAN Specification.Availability IntervalsVariableVariableThe Availability Intervals BitmapBitmapdivides the time between thebeginnings of consecutive DiscoveryWindows of a given NAN cluster intoconsecutive time intervals of equaldurations. The time interval durationis specified by the AvailabilityInterval Duration subfield of the MapControl field. A NAN device that setsthe i-th bit of the Availability IntervalsBitmap to 1 shall be present during thecorresponding i-th time interval in theoperation channel indicated by theassociated Further Availability Mapattribute. A NAN device that sets thei-th bit of the Availability IntervalsBitmap to 0 may be present during thecorresponding i-th time interval in theoperation channel indicated by theassociated Further Availability Mapattribute.

In some demonstrative embodiments, the NDC attribute may include one or more additional or alternative fields.

In some demonstrative embodiments, one or more fields of the NDC attribute of Table 1 may be optional. For example, the Service ID, NAN Anchor, and/or Hop Count Limit fields may be optional fields.

In one example, a NAN device may be configured to choose not to include part of the attributes, e.g., one or more of the optional fields, such as, for example, service ID, NAN Anchor, Hop Count limit.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to generate, transmit, receive and/or process one or more messages including the NDC attribute.

In some demonstrative embodiments, according to a second scenario, at least one device of two devices, e.g., device102and device140, may be part of one or more different NDC(s) for the service ID.

In some demonstrative embodiments, when at least one of devices102and140is part of an NDC for the same service ID, the two devices may choose to open a new NDC, e.g., NDC129, for the same service, or one of the devices may select join an existing NDC of the other one.

In some demonstrative embodiments, for example, a first device (“the new device”), e.g., device140, may join an existing NDC of a second device, e.g., device102. For example, the second device may be the NDC anchor or any other device that is part of the existing NDC. According to these embodiments, the new device joining the NDC shall adopt the NDC base schedule of the existing NDC.

In some demonstrative embodiments, the device joining the NDC may receive the NDC base schedule, for example, as part of the NDL setup, for example, by receiving the NDC attribute, e.g., the NDC attribute of Table 1, from the second device that already belongs to the NDC.

In some demonstrative embodiments, if, for example, the new device is not able to commit, or selects not to commit, to the NDC schedule of the other device, the first and second devices may select to negotiate a new NDC, e.g., as described above with respect to the first scenario.

In some demonstrative embodiments, the second device may accept or reject the request, for example, according to its own resource availability, and/or based on any other criteria.

In some demonstrative embodiments, the NDC anchor device may be configured to be present in the timeslot advertised by the NDC schedule. Other NAN devices that wish to join the NDC of the NDC anchor may setup NDLs in the NDC schedule timeslots.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to tear down an NDC and/or NDL, e.g., as described below. For example, devices102and/or140may be configured to tear down NDL149and/or NDC129.

In some demonstrative embodiments, an NDL, which was used to setup the NDC, may be torn down.

In one example, an NDL between a first device, which is the NDC anchor, e.g., device102, and a second device, e.g., device140, may be torn down, for example, if the NDC anchor does not belong to the NDC anymore, e.g., if the NDC anchor becomes unavailable, or for any other reason.

In some demonstrative embodiments, for example, to maintain simplicity for the tear down, the remaining NDLs in the NDC, e.g., NDLs between device140and one or more other devices in the NDC, may simply reuse the existing NDC base schedule, and there may be no need to change the NDC base schedule, e.g., to save signaling overhead.

In some demonstrative embodiments, if device140has NDLs with other peers in the same NDC, device140may set itself as an NDC anchor of the NDC, e.g., instead of device102.

In some demonstrative embodiments, device140may choose not to update the Hop Count with its peers with NDLs in the same NDC, for example, since an update of NDC parameters such as Hop Count may introduce signaling overhead, e.g., when device140replaces device102.

In some demonstrative embodiments, devices102,140,160and/or180may be configured to update the NDC base schedule.

In some demonstrative embodiments, the NDC case schedule may not be updated frequently, e.g., most of the time, for example, when the NDC is large, e.g., to avoid signaling overhead.

In some demonstrative embodiments, for example, when the NDC is small, e.g., a device is one-hop away from the NDC anchor, a device of the NDC may be configured to send an update request to the NDC anchor.

In some demonstrative embodiments, the NDC anchor may select to initiate a base schedule update, or may select to reject the attempt of update, e.g., in response to the update request.

Reference is made toFIG. 2, which schematically illustrates a method of communicating in a NAN cluster, in accordance with some demonstrative embodiments. For example, one or more of the operation ofFIG. 2may be performed by one or more elements of a system, system100(FIG. 1); a device, e.g., wireless communication devices102,140,160and/or180(FIG. 1); a controller, e.g., controller124(FIG. 1), and/or controller154(FIG. 1); a radio, e.g., radio114(FIG. 1); and/or radio144(FIG. 1); and/or a message processor, e.g., message processor128(FIG. 1) and/or message processor158(FIG. 1).

As indicated at block202, the method may include setting up a NAN Data link (NDL) with an other NAN device, the NDL belonging to a NAN Data Cluster (NDC) having a NDC base schedule. For example, controller124(FIG. 1) may control, cause and/or trigger device102(FIG. 1) to setup NDL149(FIG. 1) with NAN device140(FIG. 1), the NDL149(FIG. 1) belonging to NDC129(FIG. 1) having the NDC base schedule, e.g., as described above.

As indicated at block204, setting up a the NDL may include setting up the NDL belonging to the NDC having an NDC base schedule determined by an NDC anchor of the NDC. For example, controller124(FIG. 1) may control, cause and/or trigger device102(FIG. 1) to setup NDL149(FIG. 1) with NAN device140(FIG. 1), the NDL149(FIG. 1) belonging to NDC129(FIG. 1) having the NDC base schedule determined by device102(FIG. 1) the NDC anchor of NDC129(FIG. 1), e.g., as described above.

As indicated at block206, the method may include communicating data with the other NAN device via the NDL according to the NDC base schedule. For example, device102and device140(FIG. 1) may communicate data via NDL149(FIG. 1) according to the NDC base schedule, e.g., as described above.

As indicated at block208, the method may include determining the schedule to be used to communicate with the other NAN device, e.g., based on the NDC base schedule. For example, controller124(FIG. 1) may control, cause and/or trigger device102(FIG. 1) to determine the schedule to be used to communicate with the one or more other NAN devices130(FIG. 1) based on the NDC base schedule of NDC129(FIG. 1), e.g., as described above.

Reference is made toFIG. 3, which schematically illustrates a product of manufacture300, in accordance with some demonstrative embodiments. Product300may include one or more tangible computer-readable non-transitory storage media302, which may include computer-executable instructions, e.g., implemented by logic304, operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at devices102,140,160and/or180(FIG. 1), radio114(FIG. 1), transmitter118(FIG. 1), receiver116(FIG. 1), controller124, controller154(FIG. 1), message processor128(FIG. 1), message processor158(FIG. 1), and/or to perform, trigger and/or implement one or more operations and/or functionalities of theFIG. 2, and/or one or more operations described herein. The phrase “non-transitory machine-readable medium” is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising logic and circuitry configured to cause a first Neighbor Awareness Networking (NAN) device to communicate during one or more Discovery Windows (DWs) of a NAN cluster; setup a NAN Data link (NDL) with a second NAN device of the NAN cluster, the NDL belonging to a NAN Data Cluster (NDC) having an NDC base schedule; and communicate data with the second NAN device via the NDL according to an NDL schedule, which is based on the NDC base schedule.

Example 2 includes the subject matter of Example 1, and optionally, wherein the NDC base schedule is determined by an NDC anchor of the NDC.

Example 3 includes the subject matter of Example 1 or 2, and optionally, wherein the apparatus is configured to cause the first NAN device to setup the NDC as a new NDC upon setting up the NDL.

Example 4 includes the subject matter of Example 1 or 2, and optionally, wherein the apparatus is configured to cause the first NAN device to setup the NDL in an existing NDC to which at least one of the first NAN device and the second NAN device belongs.

Example 5 includes the subject matter of any one of Examples 1-4, and optionally, wherein the apparatus is configured to cause the first NAN device to process an NDC attribute comprising at least base schedule information of the NDC base schedule.

Example 6 includes the subject matter of Example 5, and optionally, wherein the NDC attribute comprises a service identifier (ID) of a service to which the NDC refers.

Example 7 includes the subject matter of Example 5 or 6, and optionally, wherein the NDC attribute comprises an identifier of an NDC anchor of the NDC.

Example 8 includes the subject matter of any one of Examples 5-7, and optionally, wherein the NDC attribute comprises a hop count field to indicate a number of hops between a transmitter of the NDC attribute and an NDC anchor of the NDC.

Example 9 includes the subject matter of any one of Examples 5-8, and optionally, wherein the NDC attribute comprises a hop count limit field to indicate a maximal number of hops allowed between a NAN device belonging to the NDC and an NDC anchor of the NDC.

Example 10 includes the subject matter of any one of Examples 1-9, and optionally, comprising one or more antennas, a memory and a processor.

Example 11 includes a system of wireless communication comprising a first Neighbor Awareness Networking (NAN) device, the first NAN device comprising one or more antennas; a memory; a processor; and a controller configured to cause the first NAN device to communicate during one or more Discovery Windows (DWs) of a NAN cluster; setup a NAN Data link (NDL) with a second NAN device of the NAN cluster, the NDL belonging to a NAN Data Cluster (NDC) having an NDC base schedule; and communicate data with the second NAN device via the NDL according to an NDL schedule, which is based on the NDC base schedule.

Example 12 includes the subject matter of Example 11, and optionally, wherein the NDC base schedule is determined by an NDC anchor of the NDC.

Example 13 includes the subject matter of Example 11 or 12, and optionally, wherein the controller is configured to cause the first NAN device to setup the NDC as a new NDC upon setting up the NDL.

Example 14 includes the subject matter of Example 11 or 12, and optionally, wherein the controller is configured to cause the first NAN device to setup the NDL in an existing NDC to which at least one of the first NAN device and the second NAN device belongs.

Example 15 includes the subject matter of any one of Examples 11-14, and optionally, wherein the controller is configured to cause the first NAN device to process an NDC attribute comprising at least base schedule information of the NDC base schedule.

Example 16 includes the subject matter of Example 15, and optionally, wherein the NDC attribute comprises a service identifier (ID) of a service to which the NDC refers.

Example 17 includes the subject matter of Example 15 or 16, and optionally, wherein the NDC attribute comprises an identifier of an NDC anchor of the NDC.

Example 18 includes the subject matter of any one of Examples 15-17, and optionally, wherein the NDC attribute comprises a hop count field to indicate a number of hops between a transmitter of the NDC attribute and an NDC anchor of the NDC.

Example 19 includes the subject matter of any one of Examples 15-18, and optionally, wherein the NDC attribute comprises a hop count limit field to indicate a maximal number of hops allowed between a NAN device belonging to the NDC and an NDC anchor of the NDC.

Example 20 includes a method to be performed at a first Neighbor Awareness Networking (NAN) device, the method comprising communicating during one or more Discovery Windows (DWs) of a NAN cluster; setting up a NAN Data link (NDL) with a second NAN device of the NAN cluster, the NDL belonging to a NAN Data Cluster (NDC) having an NDC base schedule; and communicating data with the second NAN device via the NDL according to an NDL schedule, which is based on the NDC base schedule.

Example 21 includes the subject matter of Example 20, and optionally, wherein the NDC base schedule is determined by an NDC anchor of the NDC.

Example 22 includes the subject matter of Example 20 or 21, and optionally, comprising setting up the NDC as a new NDC upon setting up the NDL.

Example 23 includes the subject matter of Example 20 or 21, and optionally, comprising setting up the NDL in an existing NDC to which at least one of the first NAN device and the second NAN device belongs.

Example 24 includes the subject matter of any one of Examples 20-23, and optionally, comprising processing an NDC attribute comprising at least base schedule information of the NDC base schedule.

Example 25 includes the subject matter of Example 24, and optionally, wherein the NDC attribute comprises a service identifier (ID) of a service to which the NDC refers.

Example 26 includes the subject matter of Example 24 or 25, and optionally, wherein the NDC attribute comprises an identifier of an NDC anchor of the NDC.

Example 27 includes the subject matter of any one of Examples 24-26, and optionally, wherein the NDC attribute comprises a hop count field to indicate a number of hops between a transmitter of the NDC attribute and an NDC anchor of the NDC.

Example 28 includes the subject matter of any one of Examples 24-27, and optionally, wherein the NDC attribute comprises a hop count limit field to indicate a maximal number of hops allowed between a NAN device belonging to the NDC and an NDC anchor of the NDC.

Example 29 includes a product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at a first Neighbor Awareness Networking (NAN) device, the operations comprising communicating during one or more Discovery Windows (DWs) of a NAN cluster; setting up a NAN Data link (NDL) with a second NAN device of the NAN cluster, the NDL belonging to a NAN Data Cluster (NDC) having an NDC base schedule; and communicating data with the second NAN device via the NDL according to an NDL schedule, which is based on the NDC base schedule.

Example 30 includes the subject matter of Example 29, and optionally, wherein the NDC base schedule is determined by an NDC anchor of the NDC.

Example 31 includes the subject matter of Example 29 or 30, and optionally, wherein the operations comprise setting up the NDC as a new NDC upon setting up the NDL.

Example 32 includes the subject matter of Example 29 or 30, and optionally, wherein the operations comprise setting up the NDL in an existing NDC to which at least one of the first NAN device and the second NAN device belongs.

Example 33 includes the subject matter of any one of Examples 29-32, and optionally, wherein the operations comprise processing an NDC attribute comprising at least base schedule information of the NDC base schedule.

Example 34 includes the subject matter of Example 33, and optionally, wherein the NDC attribute comprises a service identifier (ID) of a service to which the NDC refers.

Example 35 includes the subject matter of Example 33 or 34, and optionally, wherein the NDC attribute comprises an identifier of an NDC anchor of the NDC.

Example 36 includes the subject matter of any one of Examples 33-35, and optionally, wherein the NDC attribute comprises a hop count field to indicate a number of hops between a transmitter of the NDC attribute and an NDC anchor of the NDC.

Example 37 includes the subject matter of any one of Examples 33-36, and optionally, wherein the NDC attribute comprises a hop count limit field to indicate a maximal number of hops allowed between a NAN device belonging to the NDC and an NDC anchor of the NDC.

Example 38 includes an apparatus of a first Neighbor Awareness Networking (NAN) device, the apparatus comprising means for communicating during one or more Discovery Windows (DWs) of a NAN cluster; means for setting up a NAN Data link (NDL) with a second NAN device of the NAN cluster, the NDL belonging to a NAN Data Cluster (NDC) having an NDC base schedule; and means for communicating data with the second NAN device via the NDL according to an NDL schedule, which is based on the NDC base schedule.

Example 39 includes the subject matter of Example 38, and optionally, wherein the NDC base schedule is determined by an NDC anchor of the NDC.

Example 40 includes the subject matter of Example 38 or 39, and optionally, comprising means for setting up the NDC as a new NDC upon setting up the NDL.

Example 41 includes the subject matter of Example 38 or 39, and optionally, comprising means for setting up the NDL in an existing NDC to which at least one of the first NAN device and the second NAN device belongs.

Example 42 includes the subject matter of any one of Examples 38-41, and optionally, comprising means for processing an NDC attribute comprising at least base schedule information of the NDC base schedule.

Example 43 includes the subject matter of Example 42, and optionally, wherein the NDC attribute comprises a service identifier (ID) of a service to which the NDC refers.

Example 44 includes the subject matter of Example 42 or 43, and optionally, wherein the NDC attribute comprises an identifier of an NDC anchor of the NDC.

Example 45 includes the subject matter of any one of Examples 42-44, and optionally, wherein the NDC attribute comprises a hop count field to indicate a number of hops between a transmitter of the NDC attribute and an NDC anchor of the NDC.

Example 46 includes the subject matter of any one of Examples 42-45, and optionally, wherein the NDC attribute comprises a hop count limit field to indicate a maximal number of hops allowed between a NAN device belonging to the NDC and an NDC anchor of the NDC.