WO2018186919A1

WO2018186919A1 - Neighbor awareness networking services indication

Info

Publication number: WO2018186919A1
Application number: PCT/US2017/068468
Authority: WO
Inventors: Andrei Otcheretianski; Po-Kai Huang; Elad OREN; Emily H. Qi
Original assignee: Intel Corporation
Priority date: 2017-04-07
Filing date: 2017-12-27
Publication date: 2018-10-11

Abstract

This disclosure describes systems, methods, and devices related to a neighbor awareness networking (NAN) services indication. A device may identify a publish message received from a NAN device, wherein the NAN device is capable of performing a NAN service. The device may determine a first attribute in the publish message, wherein the 5 first attribute comprises an indication of one or more constraints associated with the NAN service. The device may cause to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service.

Description

NEIGHBOR AWARENESS NETWORKING SERVICES INDICATION CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 62/483, 124, filed April 7, 2017, the disclosure of which is incorporated herein by reference as if set forth in full. TECHNICAL FIELD

[0002] This disclosure generally relates to systems, methods, and devices for wireless communications and, more particularly, to neighbor awareness networking (NAN) services indication.

BACKGROUND

[0003] Wireless devices are becoming widely prevalent. Recently, there has been a shift in technology to support direct wireless communications between wireless devices. NAN may refer to a specification for Wi-Fi devices to enable 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 depicts a diagram illustrating an example network environment for a neighbor awareness networking (NAN) services indication, in accordance with one or more example embodiments of the present disclosure.

[0005] FIG. 2 depicts an illustrative schematic diagram for a three-way NAN data path connection, in accordance with one or more example embodiments of the present disclosure.

[0006] FIGs. 3 A and 3B depict illustrative schematic diagrams of a NAN services indication, in accordance with one or more example embodiments of the present disclosure.

[0007] FIG. 4 depicts an illustrative schematic diagram of a NAN services indication system, in accordance with one or more example embodiments of the present disclosure.

[0008] FIG. 5 depicts an illustrative schematic diagram of a NAN services indication system, in accordance with one or more example embodiments of the present disclosure.

[0009] FIGs. 6A and 6B depict flow diagrams of illustrative processes for a NAN services indication system, in accordance with one or more embodiments of the present disclosure. [0010] FIG. 7 depicts a functional diagram of an example communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.

[0011] FIG. 8 depicts a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.

DETAILED DESCRIPTION

[0012] Example embodiments described herein provide certain systems, methods, and devices for providing a neighbor awareness networking (NAN) services indication.

[0013] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0014] NAN is a specification for Wi-Fi devices to enable device/service discovery in their close proximity. The main idea is to form a NAN cluster for devices in proximity to each other. Devices in the same NAN cluster will follow the same awake time schedule, called discovery window (DW), to facilitate cluster formation and achieve low power operation. In the DWs, the devices may transmit NAN service discovery frames (SDFs) to subscribe or publish the services that the devices are interested in or providing. Once the device finds the interested service, it can set up a data path with a peer device.

[0015] The data path connection between two NAN devices is carried on specific time slots and channels and is called a NAN data link (NDL). The NDL is negotiated during the initial data path established between peers using two or three NAFs (NAN action frames) in a handshake. The NDL establishment is initiated by the service subscriber and may be accepted/rejected or countered by the peer. For example, the service publisher (or the service subscriber) may have a different timing constraint, and the responder may counter by suggesting another schedule. This leads to a three-way handshake, and the initiator device shall accept or reject the NDL in the third "Confirm" message. The NDL may also be renegotiated during an active connection, using a similar update flow.

[0016] There is a mechanism in the NAN specification to specify the quality of service (QoS) requirements and/or to request an immutable schedule. The QoS requirement may include the number of slots that the other peer is requested to allocate and the latency between slots. Another requirement may be to request an immutable schedule. Immutable slots means that the slots are scheduled by both sides, and the peers have to accept. This mechanism of specifying the QoS requirements and/or requesting an immutable schedule is only possible during NDL establishment or NDL update flow. In fact, the current NAN specification does not provide any procedure for the publisher device to advertise its NDL QoS and immutable constraints prior to NDL establishment. This leads to the situation where the initiator device of the NDL has no information about what schedule it should propose for a specific service. When the initiator device wants to open a connection with the publisher device, the initiator device is not aware of constraints that the publisher device may have on the QoS requirement or the immutable schedule. This results in arbitrary schedule proposals from the NDL initiator device, which are based only on its own constraints. In a likely case that such a proposal does not meet the publisher's QoS requirement, the publisher device will have to make a counter proposal or reject the proposal. This leads to a longer handshake, potentially less efficient schedules and a higher NDL rejection rate.

[0017] Example embodiments of the present disclosure relate to systems, methods, and devices for a NAN services indication.

[0018] In one embodiment, a NAN services indication system may allow a service publisher (also referred to as the responder) to advertise its QoS requirement at an early stage before establishing the connection in the publish NAN service discovery frames (SDFs), and to extend the QoS requirement with a new "recommended time slots" field. The subscriber device (also referred to as the initiator device), which is the initiator device of the NDL establishment, will know this information and will build a more effective proposal. This may result in a quicker agreement (and more optimal resulting schedule) on a proposed schedule between two devices.

[0019] If the publisher device has any immutable slot requirements or QoS requirements, the publisher device must send a counter proposal. That is, the publisher device needs to convey its requirement and not just accept whatever arbitrary proposal is received from the subscriber device.

[0020] In one embodiment, a NAN services indication system may provide a mechanism to advertise the required per service immutable schedule in the publish SDFs. This information may be needed to propose optimized schedules for services with strict timing limitations and eliminate the need of a counter proposal only to convey this information to the subscriber device. The SDF frame may comprise a descriptor called a service descriptor extension attribute (SDEA). [0021] If the publisher device uses this mechanism, and the subscriber device proposes a compliant proposal, the publisher device may accept without having to send a counter proposal. In the case where the subscriber device still does send a counter proposal, the counter proposal may override what was published in these new attributes.

[0022] In one embodiment, a NAN services indication system may introduce new attributes (or change existing ones) to provide the required information to the subscriber device. The required information may include the constraints that the publisher device may impose on data connections.

[0023] In one embodiment, a NAN services indication system may allow the inclusion of existing attributes in the SDF frames.

[0024] In one embodiment, a NAN services indication system may optimize the NDL establishment/update procedures in order to consider the provided QoS/immutable information during the publish subscribe stage.

[0025] In one embodiment, a NAN services indication system may extend the NDL QoS attribute to include "recommended time slots" to indicate what schedule is needed for an optimized user experience.

[0026] One or more benefits of using the above mechanism provided by the NAN services indication system may shorten the connection time between the NAN devices because in the NDL establishment procedure, the information may be available at a much earlier state, may improve NDL schedule efficiency and may reduce NDL connection failure rates.

[0027] The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, etc., may exist, some of which are described in detail below. Example embodiments will now be described with reference to the accompanying figures.

[0028] FIG. 1 is a network diagram illustrating an example wireless network 100 of a flexible connectivity framework system, according to some example embodiments of the present disclosure. Wireless network 100 can include one or more user devices 120 (e.g., 122, 124, 126, or 128), 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 of FIG. 1, a wireless communication channel may be established between two or more wireless devices (e.g., user device(s) 120), where a first user device 120 may correspond to a service seeker, and a second user device 120 may 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) 120 may 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.

[0029] In some embodiments, the user devices 120 can include one or more computer systems similar to that of the functional diagram of FIG. 7 and/or the example machine/system of FIG. 8.

[0030] One or more illustrative user device(s) 120 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 may be STAs. The one or more illustrative user device(s) 120 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user device(s) 120 (e.g., 122, 124, 126, or 128) may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static, device. For example, user device(s) 120 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a "carry small live large" (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an "origami" device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.

[0031] As used herein, the term "Internet of Things (IoT) device" is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of "legacy" Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).

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

[0033] Any of the user devices 120 (e.g., 122, 124, 126, or 128) may be configured to communicate with each other and any other component of the wireless network 100 directly and/or via one or more communications networks 130, wirelessly or wired. Any of the communications networks 130 may include, but not be limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, any of the communications networks 130 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.

[0034] Any of the user devices 120 (e.g., 122, 124, 126, or 128) 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 devices 120 (e.g., 122, 124, 126, or 128).

[0035] Any of the user devices 120 (e.g., 122, 124, 126, or 128) may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi Direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards_and/or Wi-Fi Alliance standards. In certain example embodiments, the radio component, in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g., 802.11b, 802. llg, 802.11η), 5 GHz channels (e.g., 802.11η, 802.1 lac, 802.1 lax), or 60 GHz channels (e.g., 802. Had, 802.11ay). In some embodiments, non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), ultra-high frequency (UHF) (e.g., IEEE 802.11af, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and a digital baseband.

[0036] In NAN, wireless devices may communicate with each other without the need for an access point (AP). Without an AP to transmit information that facilitates communication among the wireless devices, however, the wireless devices may not know when they will communicate with another device and with which device they will communicate. Therefore, a device may be required to use power and processing resources to listen for data packets and to determine if those data packets are meant for the device. Instead of a device constantly listening for and receiving data packets without knowing if they are meant for the device, the device may need to be woken up to establish communication with another device.

[0037] The existing NAN standard establishes a process for waking up a NAN device for service advertising and finding interesting service in the proximity, but has not established a dedicated data path between NAN devices. For example, a NAN data path (NDP) may be a data connection established between a pair of NAN devices for a service instance. NAN2 includes enhancements to the NAN standard and may include an establishment of a dedicated NDP between NAN2 devices in a NAN data cluster (NDC), which may allow for improved management of device resources. The dedicated NDP may be specific to connected NAN2 devices in an NDC, and the NDC may be a collection of NAN data links with a same NAN data cluster base schedule. In addition, because NAN2 devices may communicate in very high throughput environments that may include significant communication traffic, NAN2 devices may benefit from the communication and use of channel protection information to reduce interference, for example.

[0038] A NAN network comprises all NAN devices that share a common set of NAN parameters that include the time period between consecutive discovery windows, the time duration of the discovery windows, the beacon interval, and the NAN discovery channel(s).

[0039] A NAN cluster is a collection of NAN devices that share a common set of NAN parameters and are synchronized to the same discovery window schedule. A NAN device may send multicast NAN service discovery frames directly to other NAN devices within range in the same NAN cluster during the discovery window. A NAN device may send unicast NAN service discovery frames directly to any other NAN device within range in the same NAN cluster during the discovery window. [0040] A NAN2 device may be capable of operating in a NAN2 network and other types of networks, including a NAN network, a WLAN infrastructure, an Independent Base Service Set (IBSS), Wi-Fi Direct, Bluetooth, and the like. A NAN2 device may send multicast NAN2 service discovery frames directly to other NAN2 devices within range in the same NAN2 cluster during the discovery window (DW). A NAN2 device may also send unicast NAN2 service discovery frames directly to any other NAN2 device within range in the same NAN2 cluster during the DW.

[0041] The 802.11 data frames/packets carry protocols and data from higher layers within the frame/packet body. A data frame/packet, for example, could be carrying the data associated with the video that the user is viewing. Other frames/packets that stations may use for management and control may carry specific information regarding the wireless link in the frame/packet body. For example, a beacon frame may contain the service set identifier (SSID), a timestamp, and other pertinent information regarding the access point.

[0042] One or more NAN devices may establish a NAN data link (NDL). The established NDL may allow for the data exchange of one or more services between different NAN devices. Each service may have different requirements, such as security and address requirements. As a result, specific NAN data paths (NDPs) may be provided for different services. For example, these devices may have a video service, a printing service, or other service between them. All of these services may be transmitted on one NDL. A device is capable of conveying information associated with a service using an NDP. A NAN data interface (NDI) address may then be associated with one or more NDPs. Further, a NAN management interface (NMI) address is used to address all the NDIs and the NDPs that are established between NAN devices. In general, if a NAN device can do multi-band operation, the NAN device may have different hardware processing circuitry for different bands.

[0043] With reference to FIG. 1, the NDL is negotiated during the initial data path established between peers using two or three NAFs (NAN action frames) in a handshake. The NDL establishment is initiated by the service subscriber and may be accepted/rejected or countered by the peer. For example, the service publisher (or the service subscriber) may have a different timing constraint, and the responder may counter by suggesting another schedule. This leads to a three-way handshake, and the initiator device shall accept or reject the NDL in the third "confirm" message. The NDL may also be renegotiated during an active connection, using a similar update flow.

[0044] In one embodiment, a NAN services indication system may allow a service publisher (also referred to as the responder) to advertise its QoS requirement at an early stage before the connection in publish NAN service discovery frames (SDFs), and to extend the QoS requirement with a new "recommended time slots" field. The subscriber device (also referred to as the initiator device), which is the initiator device of the NDL establishment, will know this information and will build a more effective proposal. This may result in a quicker agreement on a proposed schedule between two devices.

[0045] If the publisher device has any immutable slot requirements or QoS requirements, the publisher device must send a counter proposal. That is, the publisher device needs to convey its requirement and not just accept whatever arbitrary proposal is received from the subscriber device.

[0046] It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0047] FIG. 2 depicts an illustrative schematic diagram 200 for a three-way NAN data path connection.

[0048] Referring to FIG. 2, there is shown a responder device 201 and an initiator device 202, which may be user devices 120 of FIG. 1. The responder device 201 and the initiator device 202 may be devices that support NAN services. For example, the responder device 201 may publish one or more of its services using NAN, and similarly the initiator device 202 may subscribe to one or more services provided by the responder device 201. The responder device 201 and the initiator device 202 may be considered the NDP responder and the NDP initiator device to indicate that they are communicating using the NDP.

[0049] To successfully establish the NDL, both peers (e.g., the initiator device 202 and the responder device 201) may need to exchange their proposed schedules and provide "schedule constraints" to the each other. The NAN specification defines the following schedule constraints:

[0050] 1. Minimum required time slots and maximum allowed gap (latency) - carried in the NDL QoS attribute.

[0051] 2. Immutable schedule, which the peer shall include in its schedule or reject - carried inside the NDL attribute.

[0052] 3. A common schedule for the data cluster - carried inside the NDC attribute.

[0053] These constraints occur during NDL establishment between both peers.

[0054] However, the current NAN specification does not provide any procedure for the publisher device to advertise its NDL QoS and immutable constraints prior to NDL establishment. This leads to the situation, where the initiator device of the NDL has no information about what schedule it should propose for a specific service. This results in arbitrary schedule proposals from the NDL initiator device, which are based only on its own constraints. In a likely case that such the proposal does not meet the publisher's QoS requirement, the publisher device will have to make a counter proposal or reject the proposal. This leads to a longer handshake, potentially less efficient schedules and a higher NDL rejection rate.

[0055 ] Furthermore, the current NAN specification mandates that the responder (publisher) should respond with a counter proposal, if it has any QoS or immutable requirements, as specified in the following tables, leading to a longer handshake and more complicated implementation of the NDL state machine.

[0056] Table 1 shows that the responder is not allowed to include QoS or immutable requirements/constraints in the compliant response.

[0057] Table 1: Key Components in NAN Schedule Initial and Compliant Proposals

[0058] Table 2 shows that when the responder device 201 has any QoS/immutable constraints, it should "counter" the proposal resulting in a three-way handshake.

[0059] Table 2: Key Components in NAN Schedule Initial and Counter Proposals

[0060] Referring to HG. 2, there is shown that the initiator device 202 may optionally send a subscribe message 203, which may be a message to subscribe to a specific service that may be published by the responder device 201. The responder device 201 may send a publish message 204, which provides a service descriptor extension attribute (SDEA). However, the SDEA does not contain any information related to QoS or immutable schedule. The initiator device 202 may receive the publish message 204 and may start an NDL/NDP establishment procedure by sending data path request 205 which may include NDP attributes and initiate the negotiation with the responder device 201. The negotiator would continue with the responder device 201 sending a data path response 206, which includes an NDL counter proposal. The initiator device 202 may then confirm this proposal by sending a data path confirm 207. This in fact results in a three-way handshake such that the initiator device 202 and the responder device 201 have to exchange a minimum of three messages in order to confirm a schedule, in particular data path request 205, data path response 206, and data path confirm 207.

[0061] In one embodiment, a NAN services indication system may avoid the above issues because the NAN services indication system may exchange the above information in an earlier stage, for example, during service publish and/or subscribe. In addition, the subscriber device for a potentially low throughput service cannot propose an efficient schedule, since the current specification does not provide a mechanism to signal such a constraint. For example, a low power IoT device may need to establish a NAN data path with some service; however, such device would not want to "waste" the time slots if they are not really needed.

[0062] FIGs. 3A and 3B depict illustrative schematic diagrams for a NAN services indication, in accordance with one or more example embodiments of the present disclosure.

[0063] In one embodiment, a NAN services indication system may allow the publisher device to advertise its QoS and immutable schedule requirements in the NAN service discovery frame (SDF) if any. The NAN services indication system may introduce "Recommended Time Slots" as a new parameter in the QoS attribute.

[0064] A NAN services indication system may introduce a mechanism to publish per service QoS and immutable requirements. The publisher device may be allowed to include the NDL QoS attributes in the publish SDF frames.

[0065] A NAN services indication system may modify NAN attributes in the NAN SDF frames table (Table 3) accordingly for the case where the QoS required bit needs to be mandatorily set for this service. The change may be to add the QoS required column and optionally allow the NDL QoS attributes.

[0066] Table 3 : NAN Attributes in NAN SDF Frames

[0067] In addition, the NDL QoS attribute may be changed to reflect optional per service

QoS requirements by adding the fields "Instance ID" and "Recommended Time Slots" as shown below in Table 4. The "Instance ID" field may indicate the instance ID of a published service this attributed applies to. The value may be set to "0" if this is valid for all published services. The "Recommended Time Slots" field may be used to indicate the number of recommended time slots needed for optimized user experience for this connection. [0068] Table 4: NDL QoS Attribute Format

[0069] In one embodiment, and as another option for not changing the format of the NDL QoS attribute, the NDL QoS attribute may be appended after the service descriptor attribute (SDA) or SDEA that describes a service to indicate the QoS requirement for the service.

[0070] Referring to FIG. 3 A, if the receiver (e.g., the initiator device 202 of FIG. 2) identifies the NDL QoS attribute (e.g., NDL QoS attribute fields 303 and 305) after receiving an SDA or SDEA (e.g., SDA for service 1 field 302 and SDEA for service 2 field 304), the receiver may consider the NDL QoS indication when the receiver initiates the NDL setup for the service indicated in the SDA or SDEA.

[0071] Referring to FIG. 3B, if the receiver sees the NDL QoS attribute (e.g., NDL QoS attribute field 311) after a series of SDA or SDEA (e.g., SDEA for service 3 field 308, SDA for service 2 field 309, and SDEA for service 2 field 310), then the receiver may consider the NDL QoS indication when the receiver initiates the NDL setup for the service indicated in the series of SDA or SDEA.

[0072] These approaches may allow the sender (e.g., the responder device 201 of FIG. 2) of the publish SDF to order the attribute in a specific way so that the receiver can easily identify if there is an NDL QoS indication for a service. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0073] FIG. 4 depicts an illustrative schematic diagram for a NAN services indication system, in accordance with one or more example embodiments of the present disclosure.

[0074] In one embodiment, a NAN services indication system may introduce a new attribute with fields similar to Tables 3-5 above. In this case, Table 3 may be changed accordingly.

[0075] In one embodiment, a NAN services indication system may change the SDEA to include a "Minimum Time Slots" field, a "Maximum Latency" field, and a "Recommended Time Slots" field as shown in Table 5 below. The "Minimum Time Slots" field may indicate the minimum number of further available NAN slots needed per DW interval. This field may be set to a value of zero (0) if no preference. This field will be present only if the "QoS Required" bit is set. The "Maximum Latency" field may indicate the maximum allowed NAN slots between every two non-contiguous NDL common resource blocks (CRBs). The value may be set to "65535" if no preference. This field is present only if the "QoS Required" bit is set. The "Recommended Time Slots" field may indicate the number of recommended time slots needed for optimized user experience for this connection. This field may be larger than or equal to the minimum time slots. This field may be set to zero (0) if no preference. This field may be present only if the "QoS Required" bit is set.

76] Table 5: Service Descriptor Extension Attribute (SDEA) Format

[0077] In one embodiment, a NAN services indication system may introduce new attribute "Service Immutable Schedule" to convey the information about the required immutable schedule as shown in Table 6. The "Service Immutable Schedule" may be included in an SDF or the SDEA and may be comprised of one or more fields. For example, it may include an "Instance ID" field, which may indicate an instance ID of a published service this attribute applies to. Another field may be a "Schedule Entry List" field, which may indicate one or more schedule entries.

[0078] Table 6: Service Immutable Schedule

[0079] In addition, "Immutable Schedule Required" bit 404 may be introduced in the SDEA control field 400.

[0080] In one embodiment, the NDL QoS attribute/or a newly introduced attribute for that purpose may be further extended to include the immutable schedule as well. In one embodiment, the SDEA attribute may be extended to include this information as follows:

[0081] Table 7: Service Descriptor Extension Attribute (SDEA) Format

[0082] Referring to FIG. 4, there is shown an SDEA control field 400. The subscriber device (e.g., an initiator device) that establishes a connection with a service publisher (e.g., a responder device) that indicates either "QoS Required" (e.g., field 402) or "Immutable Schedule Required" (e.g., field 404) in the SDEA and advertises the QoS and immutable schedule attributes may propose a schedule which is a superset of both. The responder may reject the initial proposal if those requirements are not met. In addition, the subscriber device that wishes to optimize its schedule (in order to save power or accommodate more concurrent connections) may consider the "Recommended Time Slots" requirement too. The publisher device, which advertises its QoS and immutable schedule requirements in the SDFs may omit these attributes in the data response frame, and may immediately accept the proposed schedule. The publisher device may not reject the initial "Data Path Request" message if the "Recommended Time Slots" requirement is not met. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0083] FIG. 5 depicts an illustrative schematic diagram 500 for a NAN services indication system, in accordance with one or more example embodiments of the present disclosure.

[0084] Referring to FIG. 5, there is shown a responder device 501 and an initiator device 502, which may be user devices 120 of FIG. 1. The responder device 501 and the initiator device 502 may be devices that support NAN services. For example, the responder device 501 may publish one or more of its services using NAN, and similarly the initiator device 502 may subscribe to one or more services provided by the responder device 501 by first sending a subscribe frame 503. The responder device 501 and the initiator device 502 may be considered NDP responder and NDP initiator devices to indicate that they are communicating using NDP.

[0085] Referring to FIG. 5, the diagram shows two-way NAN data path establishment optimized by using the NDL QoS and immutable requirements advertised in the publish SDF frame 504, in accordance with one or more example embodiments of the present disclosure.

[0086] In one embodiment, the initiator device 502 may send a data path request 505, which may include information in response to the constraints included in the publish message of the publish SDF frame 504. For example, the data path request 505 may include an initial proposal, which may be based on the publish message in the publish SDF frame 504. This will include a proposal that is based on the immutable schedule and the QoS requirements that were received in the publish message of the publish SDF frame 504.

[0087] In one embodiment, the responder device 501 may still be allowed to include a different QoS and immutable schedule in the data path response 506. However, in this case, the status may be set to "continued," and the behavior may be according to the current NAN specification. In any case of contradiction between the SDF and the NAFs' QoS/Immutable requirements, the NAFs may take preference. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0088] FIG. 6A illustrates a flow diagram of an illustrative process 600 for an illustrative NAN services indication system, in accordance with one or more example embodiments of the present disclosure.

[0089] At block 602, a device (e.g., a user device 120 of FIG. 1) may identify a publish message received from a neighbor awareness networking (NAN) device, wherein the NAN device is capable of performing a NAN service. For example, a service publisher (also referred to as the responder) may advertise its QoS requirement at an early stage before establishing a connection in the publish NAN service discovery frames (SDFs), and to extend the QoS requirement with a new "recommended time slots" field. The subscriber device (also referred to as the initiator device), which is the initiator device of the NDL establishment, will know this information and will build a more effective proposal. This may result in a quicker agreement on a proposed schedule between two devices.

[0090] At block 604, the device may determine a first attribute in the publish message, wherein the first attribute comprises an indication of one or more constraints associated with the NAN service. If the publisher device has any immutable slot requirements or QoS requirements, the publisher device must send a counter proposal. That is, the publisher device needs to convey its requirement and not just accept whatever arbitrary proposal is received from the subscriber device. The publisher may advertise the required per service immutable schedule in publish SDFs. This information may be needed to propose optimized schedules for services with strict timing limitations and to eliminate the need of a counter proposal only to convey this information to the subscriber device. The SDF frame may comprise a descriptor called a service descriptor extension attribute (SDEA). The SDEA may comprise a bit that is used to indicate for a specific service whether it is allowed to have a data connection.

[0091] At block 606, the device may cause to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service. The initiator device may receive the publish message and may start an NDL/NDP establishment procedure by sending the data path request which may include NDP attributes and initiate the negotiation with the responder device. The negotiation would continue with the responder device sending a data path response, which includes an NDL counter proposal. The initiator device may then confirm this proposal by sending a data path confirm. This in fact results in a three-way handshake such that the initiator device and the responder device have to exchange a minimum of three messages in order to confirm a schedule, in particular, data path request, the data path response, and the data path confirm. [0092] It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0093] FIG. 6B illustrates a flow diagram of an illustrative process 650 for a NAN services indication system, in accordance with one or more embodiments of the present disclosure.

[0094] At block 652, a device (e.g., a user device 120 of FIG. 1) may determine a publish message comprising a service descriptor extension attribute (SDEA) and a neighbor awareness networking (NAN) data link (NDL) quality of service (QoS) attribute. For example, a publisher device may publish a NAN service that it may be providing. When the subscriber device receives this publish message, it may determine the type of service and/or constraints that may be included in the publish message.

[0095] At block 654, the device may cause to send a publish message to a NAN device, wherein the publish message is associated with a NAN service. For example, when the subscriber device receives the publish message from the publisher device, it may decode the message and may determine that it is in an SDF frame. It may also determine one or more attributes that may be included in this SDF frame. These attributes may include QoS requirements and/or an immutable schedule proposed by the publisher device. If the publisher device has any immutable slot requirements or QoS requirements, the publisher device must send a counter proposal. That is, the publisher device needs to convey its requirement and not just accept whatever arbitrary proposal is received from the subscriber device.

[0096] At block 656, the device may cause to identify a data path request received from the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service. The initiator device may receive the publish message and may start an NDL/NDP establishment procedure by sending the data path request which may include the NDP attributes and initiate the negotiation with the responder device. The negotiation would continue with the responder device sending a data path response, which includes an NDL counter proposal. The initiator device may then confirm this proposal by sending a data path confirm. This in fact results in a three way handshake such that the initiator device and the responder device have to exchange a minimum of three messages in order to confirm a schedule, in particular, the data path request, the data path response, and the data path confirm.

[0097] It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0098] FIG. 7 shows a functional diagram of an exemplary communication station 700 in accordance with some embodiments. In one embodiment, FIG. 7 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or a user device 120 (FIG. 1) in accordance with some embodiments. The communication station 700 may 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.

[0099] The communication station 700 may include communications circuitry 702 and a transceiver 710 for transmitting and receiving signals to and from other communication stations using one or more antennas 701. The transceiver 710 may be a device comprising both a transmitter and a receiver that are combined and share common circuitry (e.g., communication circuitry 702). The communications circuitry 702 may include amplifiers, filters, mixers, analog to digital and/or digital to analog converters. The transceiver 710 may transmit and receive analog or digital signals. The transceiver 710 may 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 transceiver 710 may operate in a half-duplex mode, where the transceiver 710 may transmit or receive signals in one direction at a time.

[00100] The communications circuitry 702 may include circuitry that can operate the physical layer (PHY) communications and/or media access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station 700 may also include processing circuitry 706 and memory 708 arranged to perform the operations described herein. In some embodiments, the communications circuitry 702 and the processing circuitry 706 may be configured to perform operations detailed in FIGs. 2, 3A and 3B, 4, 5, and 6A and 6B.

[00101] In accordance with some embodiments, the communications circuitry 702 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 702 may be arranged to transmit and receive signals. The communications circuitry 702 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 706 of the communication station 700 may include one or more processors. In other embodiments, two or more antennas 701 may be coupled to the communications circuitry 702 arranged for sending and receiving signals. The memory 708 may store information for configuring the processing circuitry 706 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 708 may 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 memory 708 may 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.

[00102] In some embodiments, the communication station 700 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

[00103] In some embodiments, the communication station 700 may include one or more antennas 701. The antennas 701 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.

[00104] In some embodiments, the communication station 700 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[00105] Although the communication station 700 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station 700 may refer to one or more processes operating on one or more processing elements.

[00106] Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, the communication station 700 may include one or more processors and may be configured with instructions stored on a computer-readable storage device memory.

[00107] FIG. 8 illustrates a block diagram of an example of a machine 800 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine 800 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 800 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 800 may act as a peer machine in peer-to- peer (P2P) (or other distributed) network environments. The machine 800 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations.

[00108] Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating. A module includes hardware. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating. In this example, the execution units may be a member of more than one module. For example, under operation, the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.

[00109] The machine (e.g., computer system) 800 may include a hardware processor 802 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 804 and a static memory 806, some or all of which may communicate with each other via an interlink (e.g., bus) 808. The machine 800 may further include a power management device 832, a graphics display device 810, an alphanumeric input device 812 (e.g., a keyboard), and a user interface (UI) navigation device 814 (e.g., a mouse). In an example, the graphics display device 810, alphanumeric input device 812, and UI navigation device 814 may be a touch screen display. The machine 800 may additionally include a storage device (i.e., drive unit) 816, a signal generation device 818 (e.g., a speaker), a NAN services indication device 819, a network interface device/transceiver 820 coupled to antenna(s) 830, and one or more sensors 828, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine 800 may include an output controller 834, 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.)).

[00110] The storage device 816 may include a machine readable medium 822 on which is stored one or more sets of data structures or instructions 824 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 824 may also reside, completely or at least partially, within the main memory 804, within the static memory 806, or within the hardware processor 802 during execution thereof by the machine 800. In an example, one or any combination of the hardware processor 802, the main memory 804, the static memory 806, or the storage device 816 may constitute machine- readable media.

[00111] The NAN services indication device 819 may carry out or perform any of the operations and processes (e.g., processes 600 and 650) described and shown above. For example, the NAN services indication device 819 may allow a service publisher (also referred to as the responder) to advertise its QoS requirement at an early stage before establishing the connection in the publish NAN service discovery frames (SDFs), and to extend the QoS requirement with a new "recommended time slots" field. The subscriber device (also referred to as the initiator device), which is the initiator device of the NDL establishment, will know this information and will build a more effective proposal. This may result in a quicker agreement on a proposed schedule between two devices. If the publisher device has any immutable slot requirements or QoS requirements, the publisher device must send a counter proposal. That is, the publisher device needs to convey its requirement and not just accept whatever arbitrary proposal is received from the subscriber device.

[00112] The NAN services indication device 819 may provide a mechanism to advertise the required per service immutable schedule in publish SDFs. This information may be needed to propose optimized schedules for services with strict timing limitations and eliminate the need of a counter proposal only to convey this information to the subscriber device. The SDF frame may comprise an SDEA. The SDEA may comprise a bit that is used to indicate for a specific service whether it is allowed to have a data connection. If the publisher device uses this mechanism, and the subscriber device proposes a compliant proposal, the subscriber device may accept without having to send a counter proposal. In the case where the subscriber device still does send a counter proposal, the counter proposal may override what was published in these new attributes. In the publish message, the publisher device publishes the constraints. The subscriber device can use those constraints to build a better proposal that will have a higher likelihood of being accepted by the publisher device without having to have additional messaging through a counter proposal.

[00113] The NAN services indication device 819 may introduce new attributes (or change existing ones) to provide the required information to the subscriber device. The required information may include the constraints that the publisher device may impose on data connections.

[00114] The NAN services indication device 819 may allow the inclusion of existing attributes in the SDF frames.

[00115] The NAN services indication device 819 may optimize the NDL establishment/update procedures, in order to consider the provided QoS/immutable information during the publish/subscribe stage.

[00116] The NAN services indication device 819 may extend the NDL QoS attribute to include "recommended time slots" to indicate what schedule is needed for an optimized user experience.

[00117] One or more benefits of using the above mechanism provided by the NAN services indication device 819 may shorten the connection time between the NAN devices because in the NDL establishment procedure, the information may be available at a much earlier state, may improve the NDL schedule efficiency and may reduce NDL connection failure rates.

[00118] It is understood that the above are only a subset of what the NAN services indication device 819 may be configured to perform and that other functions included throughout this disclosure may also be performed by the NAN services indication device 819.

[00119] While the machine-readable medium 822 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 824.

[00120] Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.

[00121] The term "machine-readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and that cause the machine 800 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media. In an example, a massed machine -readable medium includes a machine-readable medium with a plurality of particles having resting mass. Specific examples of massed machine -readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks.

[00122] The instructions 824 may further be transmitted or received over a communications network 826 using a transmission medium via the network interface device/transceiver 820 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others. In an example, the network interface device/transceiver 820 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 826. In an example, the network interface device/transceiver 820 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple- output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and includes digital or analog communications signals or other intangible media to facilitate communication of such software. The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.

[00123] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The terms "computing device," "user device," "communication station," "station," "handheld device," "mobile device," "wireless device" and "user equipment" (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary.

[00124] As used within this document, the term "communicate" is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as "communicating," when only the functionality of one of those devices is being claimed. The term "communicating" as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.

[00125] As used herein, unless otherwise specified, the use of the ordinal adjectives "first," "second," "third," etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[00126] 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.

[00127] Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an onboard device, an off-board device, a hybrid device, a vehicular device, a non- vehicular device, a mobile or portable device, a consumer device, a non- mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio- video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.

[00128] Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple-input multiple-output (MIMO) transceiver or device, a single-input multiple-output (SIMO) transceiver or device, a multiple-input single-output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi- standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.

[00129] Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDM A), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3rd Generation Partnership Project (3GPP), long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.

[00130] Example 1 may include a device comprising memory and processing circuitry configured to: identify a publish message received from a neighbor awareness networking (NAN) device, wherein the NAN device may be capable of performing a NAN service; determine a first attribute in the publish message, wherein the first attribute comprises an indication of one or more constraints associated with the NAN service; and cause to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service.

[00131] Example 2 may include the device of example 1 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF).

[00132] Example 3 may include the device of example 1 and/or some other example herein, wherein the first attribute may be a service descriptor extension attribute (SDEA).

[00133] Example 4 may include the device of example 1 and/or some other example herein, wherein the memory and the processing circuitry are further configured to cause to send a subscribe message to the NAN device to establish a NAN data path. [00134] Example 5 may include the device of example 2 and/or some other example herein, wherein the SDF comprises a NAN data link (NDL) quality of service (QoS) attribute, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00135] Example 6 may include the device of example 2 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00136] Example 7 may include the device of example 6 and/or some other example herein, wherein the schedule comprises a first subset of the immutable schedule included in the SDF.

[00137] Example 8 may include the device of example 5 and/or some other example herein, wherein the NDL QoS attribute comprises at least one of a minimum time slots field, a maximum latency field, or a recommended time slots field.

[00138] Example 9 may include the device of example 5 and/or some other example herein, wherein the NDL QoS attribute may be identified after at least one of a service descriptor attribute (SDA) or a service descriptor extension attribute (SDEA).

[00139] Example 10 may include the device of example 8 and/or some other example herein, wherein the recommended time slots field indicates a number of recommend time slots needed to optimize a connection with the NAN device.

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

[00141] Example 12 may include the device of example 11 and/or some other example herein, further comprising one or more antennas coupled to the transceiver.

[00142] Example 13 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: determining a publish message comprising a service descriptor extension attribute (SDEA) and a neighbor awareness networking (NAN) data link (NDL) quality of service (QoS) attribute; causing to send a publish message to a NAN device, wherein the publish message may be associated with a NAN service; and identifying a data path request received from the NAN device.

[00143] Example 14 may include the non-transitory computer-readable medium of example 13 and/or some other example herein, wherein the NDL QoS attribute may be preceded by the SDEA in the publish message.

[00144] Example 15 may include the non-transitory computer-readable medium of example 13 and/or some other example herein, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00145] Example 16 may include the non-transitory computer-readable medium of example 13 and/or some other example herein, wherein the QoS attribute may be found after at least one of a service descriptor attribute or a service descriptor extension attribute.

[00146] Example 17 may include the non-transitory computer-readable medium of example 13 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF).

[00147] Example 18 may include the non-transitory computer-readable medium of example 17 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00148] Example 19 may include a method comprising: identifying, by one or more processors, a publish message received from a neighbor awareness networking (NAN) device, wherein the NAN device may be capable of performing a NAN service; determining a first attribute in the publish message, wherein the first attribute comprises an indication of one or more constraints associated with the NAN service; and causing to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service.

[00149] Example 20 may include the method of example 19 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF).

[00150] Example 21 may include the method of example 19 and/or some other example herein, wherein the first attribute may be a service descriptor extension attribute (SDEA).

[00151] Example 22 may include the method of example 19 and/or some other example herein, further comprising causing to send a subscribe message to the NAN device to establish a NAN data path.

[00152] Example 23 may include the method of example 20 and/or some other example herein, wherein the SDF comprises a NAN data link (NDL) quality of service (QoS) attribute, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00153] Example 24 may include the method of example 20 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00154] Example 25 may include the method of example 24 and/or some other example herein, wherein the schedule comprises a first subset of the immutable schedule included in the SDF. [00155] Example 26 may include the method of example 24 and/or some other example herein, wherein the NDL QoS attribute comprises at least one of a minimum time slots field, a maximum latency field, or a recommended time slots field.

[00156] Example 27 may include the method of example 24 and/or some other example herein, wherein the NDL QoS attribute may be identified after at least one of a service descriptor attribute (SDA) or a service descriptor extension attribute (SDEA).

[00157] Example 28 may include the method of example 26 and/or some other example herein, wherein the recommended time slots field indicates a number of recommend time slots needed to optimize a connection with the NAN device.

[00158] Example 29 may include an apparatus comprising means for performing a method as claimed in any one of examples 19-28.

[00159] Example 30 may include a system comprising at least one memory device having programmed instruction that, in response to execution cause at least one processor to perform the method of any one of examples 19-28.

[00160] Example 31 may include a machine readable medium including code, when executed, to cause a machine to perform the method of any one of examples 19-28.

[00161] Example 32 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: identifying a publish message received from a neighbor awareness networking (NAN) device, wherein the NAN device may be capable of performing a NAN service; determining a first attribute in the publish message, wherein the first attribute comprises an indication of one or more constraints associated with the NAN service; and causing to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service.

[00162] Example 33 may include the non-transitory computer-readable medium of example 32 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF).

[00163] Example 34 may include the non-transitory computer-readable medium of example 32 and/or some other example herein, wherein the first attribute may be a service descriptor extension attribute (SDEA).

[00164] Example 35 may include the non- transitory computer-readable medium of example 32 and/or some other example herein, wherein the operations further comprise causing to send a subscribe message to the NAN device to establish a NAN data path.

[00165] Example 36 may include the non-transitory computer-readable medium of example 33 and/or some other example herein, wherein the SDF comprises a NAN data link (NDL) quality of service (QoS) attribute, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00166] Example 37 may include the non-transitory computer-readable medium of example 33 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00167] Example 38 may include the non- transitory computer-readable medium of example

37 and/or some other example herein, wherein the schedule comprises a first subset of the immutable schedule included in the SDF.

[00168] Example 39 may include the non-transitory computer-readable medium of example 36 and/or some other example herein, wherein the NDL QoS attribute comprises at least one of a minimum time slots field, a maximum latency field, or a recommended time slots field.

[00169] Example 40 may include the non- transitory computer-readable medium of example 36 and/or some other example herein, wherein the NDL QoS attribute may be identified after at least one of a service descriptor attribute (SDA) or a service descriptor extension attribute (SDEA).

[00170] Example 41 may include the non-transitory computer-readable medium of example

38 and/or some other example herein, wherein the recommended time slots field indicates a number of recommend time slots needed to optimize a connection with the NAN device.

[00171] Example 42 may include an apparatus comprising means for identify a publish message received from a neighbor awareness networking (NAN) device, wherein the NAN device may be capable of performing a NAN service; means for determining a first attribute in the publish message, wherein the first attribute comprises an indication of one or more constraints associated with the NAN service; and means for causing to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service.

[00172] Example 43 may include the apparatus of example 42 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF).

[00173] Example 44 may include the apparatus of example 42 and/or some other example herein, wherein the first attribute may be a service descriptor extension attribute (SDEA).

[00174] Example 45 may include the apparatus of example 42 and/or some other example herein, further comprising means for causing to send a subscribe message to the NAN device to establish a NAN data path.

[00175] Example 46 may include the apparatus of example 43 and/or some other example herein, wherein the SDF comprises a NAN data link (NDL) quality of service (QoS) attribute, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00176] Example 47 may include the apparatus of example 43 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00177] Example 48 may include the apparatus of example 47 and/or some other example herein, wherein the schedule comprises a first subset of the immutable schedule included in the SDF.

[00178] Example 49 may include the apparatus of example 46 and/or some other example herein, wherein the NDL QoS attribute comprises at least one of a minimum time slots field, a maximum latency field, or a recommended time slots field.

[00179] Example 50 may include the apparatus of example 46 and/or some other example herein, wherein the NDL QoS attribute may be identified after at least one of a service descriptor attribute (SDA) or a service descriptor extension attribute (SDEA).

[00180] Example 51 may include the apparatus of example 49 and/or some other example herein, wherein the recommended time slots field indicates a number of recommend time slots needed to optimize a connection with the NAN device.

[00181] Example 52 may include a device comprising memory and processing circuitry configured to: determine a publish message comprising a service descriptor extension attribute (SDEA) and a neighbor awareness networking (NAN) data link (NDL) quality of service (QoS) attribute; cause to send a publish message to a NAN device, wherein the publish message may be associated with a NAN service; and identify a data path request received from the NAN device.

[00182] Example 53 may include the device of example 52 and/or some other example herein, wherein the NDL QoS attribute may be preceded by the SDEA in the publish message.

[00183] Example 54 may include the device of example 52 and/or some other example herein, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00184] Example 55 may include the device of example 52 and/or some other example herein, wherein the QoS attribute may be found after at least one of a service descriptor attribute or a service descriptor extension attribute.

[00185] Example 56 may include the device of example 52 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF). [00186] Example 57 may include the device of example 55 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00187] Example 58 may include the device of example 52 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.

[00188] Example 59 may include the device of example 58 and/or some other example herein, further comprising one or more antennas coupled to the transceiver.

[00189] Example 60 may include a method comprising: determining a publish message comprising a service descriptor extension attribute (SDEA) and a neighbor awareness networking (NAN) data link (NDL) quality of service (QoS) attribute; causing to send a publish message to a NAN device, wherein the publish message may be associated with a NAN service; and identifying a data path request received from the NAN device.

[00190] Example 61 may include the method of example 60 and/or some other example herein, wherein the NDL QoS attribute may be preceded by the SDEA in the publish message.

[00191] Example 62 may include the method of example 60 and/or some other example herein, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00192] Example 63 may include the method of example 60 and/or some other example herein, wherein the QoS attribute may be found after at least one of a service descriptor attribute or a service descriptor extension attribute.

[00193] Example 64 may include the method of example 60 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF).

[00194] Example 65 may include the method of example 64 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00195] Example 66 may include an apparatus comprising means for performing a method as claimed in any one of examples 60-65.

[00196] Example 67 may include a system comprising at least one memory device having programmed instruction that, in response to execution cause at least one processor to perform the method of any one of examples 60-65.

[00197] Example 68 may include a machine readable medium including code, when executed, to cause a machine to perform the method of any one of examples 60-65.

[00198] Example 69 may include an apparatus comprising means for determining a publish message comprising a service descriptor extension attribute (SDEA) and a neighbor awareness networking (NAN) data link (NDL) quality of service (QoS) attribute; means for causing to send a publish message to a NAN device, wherein the publish message may be associated with a NAN service; and means for identifying a data path request received from the NAN device.

[00199] Example 70 may include the apparatus of example 69 and/or some other example herein, wherein the NDL QoS attribute may be preceded by the SDEA in the publish message.

[00200] Example 71 may include the apparatus of example 69 and/or some other example herein, wherein the NDL QoS attribute may include a field associated with one or more recommended time slots to perform the NAN service.

[00201] Example 72 may include the apparatus of example 69 and/or some other example herein, wherein the QoS attribute may be found after at least one of a service descriptor attribute or a service descriptor extension attribute.

[00202] Example 73 may include the apparatus of example 69 and/or some other example herein, wherein the publish message may be a NAN service discovery frame (SDF).

[00203] Example 74 may include the apparatus of example 73 and/or some other example herein, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

[00204] Example 75 may include an apparatus comprising means for performing a method as claimed in any of the preceding examples.

[00205] Example 76 may include a machine-readable storage including machine -readable instructions, when executed, to implement a method as claimed in any preceding example.

[00206] Example 77 may include a machine-readable storage including machine -readable instructions, when executed, to implement a method or realize an apparatus as claimed in any preceding example.

[00207] Example 78 may include one or more non- transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-77, or any other method or process described herein

[00208] Example 79 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-77, or any other method or process described herein.

[00209] Example 80 may include a method, technique, or process as described in or related to any of examples 1-77, or portions or parts thereof. [00210] Example 81 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-77, or portions thereof.

[00211] Example 82 may include a method of communicating in a wireless network as shown and described herein.

[00212] Example 83 may include a system for providing wireless communication as shown and described herein.

[00213] Example 84 may include a device for providing wireless communication as shown and described herein.

[00214] Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject- matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.

[00215] The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[00216] Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations.

[00217] Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations.

[00218] These computer-executable program instructions may be loaded onto a special- purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.

[00219] Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

[00220] Conditional language, such as, among others, "can," "could," "might," or "may," unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

[00221] Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

CLAIMS What is claimed is:

1. A device, the device comprising memory and processing circuitry configured to: identify a publish message received from a neighbor awareness networking (NAN) device, wherein the NAN device is capable of performing a NAN service;

determine a first attribute in the publish message, wherein the first attribute comprises an indication of one or more constraints associated with the NAN service; and cause to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service.

2. The device of claim 1, wherein the publish message is a NAN service discovery frame (SDF).

3. The device of claim 1, wherein the first attribute is a service descriptor extension attribute (SDEA).

4. The device of any one of claims 1 to 3, wherein the memory and the processing circuitry are further configured to cause to send a subscribe message to the NAN device to establish a NAN data path.

5. The device of claim 2, wherein the SDF comprises a NAN data link (NDL) quality of service (QoS) attribute, wherein the NDL QoS attribute includes a field associated with one or more recommended time slots to perform the NAN service.

6. The device of claim 2, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

7. The device of claim 6, wherein the schedule comprises a first subset of the immutable schedule included in the SDF.

8. The device of claim 5, wherein the NDL QoS attribute comprises at least one of a minimum time slots field, a maximum latency field, or a recommended time slots field.

9. The device of claim 5, wherein the NDL QoS attribute is identified after at least one of a service descriptor attribute (SDA) or a service descriptor extension attribute (SDEA).

10. The device of claim 8, wherein the recommended time slots field indicates a number of recommend time slots needed to optimize a connection with the NAN device.

11. The device of claim 1, further comprising a transceiver configured to transmit and receive wireless signals.

12. The device of claim 11, further comprising one or more antennas coupled to the transceiver.

13. A non- transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: determining a publish message comprising a service descriptor extension attribute (SDEA) and a neighbor awareness networking (NAN) data link (NDL) quality of service (QoS) attribute;

causing to send a publish message to a NAN device, wherein the publish message is associated with a NAN service; and

identifying a data path request received from the NAN device.

14. The non-transitory computer-readable medium of claim 13, wherein the NDL QoS attribute is preceded by the SDEA in the publish message.

15. The non-transitory computer-readable medium of claim 13, wherein the NDL QoS attribute includes a field associated with one or more recommended time slots to perform the NAN service.

16. The non-transitory computer-readable medium of claim 13, wherein the QoS attribute is found after at least one of a service descriptor attribute or a service descriptor extension attribute.

17. The non-transitory computer-readable medium of any one of claims 13 to 16, wherein the publish message is a NAN service discovery frame (SDF).

18. The non-transitory computer-readable medium of claim 17, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

19. A method comprising:

identifying, by one or more processors, a publish message received from a neighbor awareness networking (NAN) device, wherein the NAN device is capable of performing a NAN service;

determining a first attribute in the publish message, wherein the first attribute comprises an indication of one or more constraints associated with the NAN service; and causing to send a data path request to the NAN device, wherein the data path request comprises a schedule comprising one or more slots associated with the NAN service.

20. The method of claim 19, wherein the publish message is a NAN service discovery frame (SDF).

21. The method of claim 19, wherein the first attribute is a service descriptor extension attribute (SDEA).

22. The method of any one of claims 19 to 21, further comprising causing to send a subscribe message to the NAN device to establish a NAN data path.

23. The method of claim 20, wherein the SDF comprises a NAN data link (NDL) quality of service (QoS) attribute, wherein the NDL QoS attribute includes a field associated with one or more recommended time slots to perform the NAN service.

24. The method of claim 20, wherein the SDF comprises an immutable schedule required, wherein the immutable schedule required comprises one or more schedule entries.

25. The method of claim 24, wherein the schedule comprises a first subset of the immutable schedule included in the SDF.