WO2014185954A1

WO2014185954A1 - Techniques to manage connection capabilities information in a wireless communications system

Info

Publication number: WO2014185954A1
Application number: PCT/US2013/076933
Authority: WO
Inventors: Emily H. Qi; Minyoung Park
Original assignee: Intel Corporation
Priority date: 2013-05-15
Filing date: 2013-12-20
Publication date: 2014-11-20
Also published as: CN110062370A; EP2997786A4; CN110062370B; EP2997786A1; CN104488349A

Abstract

Techniques to manage connection capabilities information for a wireless communications system are described. In various embodiments, for example an apparatus may comprise a processor circuit, a communications component for execution by the processor circuit to perform neighbor awareness networking (NAN) service discovery and to receive a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device, and a determination component for execution by the processor circuit to determine whether to initiate a connection with the remote device based on the connection capability bitmap field. Other embodiments are described and claimed.

Description

TECHNIQUES TO MANAGE CONNECTION CAPABILITIES INFORMATION IN A

WIRELESS COMMUNICATIONS SYSTEM

RELATED CASE

This application claims priority to United States Provisional Patent Application Number

61/823,800, filed May 15, 2013, the entirety of which is hereby incorporated by reference.

TECHNICAL FIELD

Embodiments described herein generally relate to communications over wireless networks. More particularly, embodiments described herein generally relate to communicating connection capabilities during wireless network service discovery operations.

BACKGROUND

In a wireless communications system, devices may utilize service discovery techniques in order to determine services offered by other devices in the system. To enable discovery of services that it offers, a particular device may periodically advertise service information. Such periodic advertisements may create significant power and traffic loads, however. To address this issue, techniques for device-to-device low power background service discovery may be utilized. Such techniques may enable devices to achieve and/or maintain awareness of nearby devices and services offered by those devices without consuming unacceptably large amounts of power or generating excessive amounts of traffic.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of an operating environment.

FIG. 2 illustrates an embodiment of a first attribute format.

FIG. 3 illustrates an embodiment of a field of the first attribute format.

FIG. 4 illustrates an embodiment of a second attribute format.

FIG. 5 illustrates an embodiment of a third attribute format.

FIG. 6 illustrates an embodiment of a fourth attribute format.

FIG. 7 illustrates an embodiment of a first apparatus and an embodiment of a first system.

FIG. 8 illustrates an embodiment of a first logic flow.

FIG. 9 illustrates an embodiment of a second apparatus and an embodiment of a second system.

FIG. 10 illustrates an embodiment of a second logic flow.

FIG. 11 illustrates an embodiment of a storage medium. FIG. 12 illustrates an embodiment of a device.

DETAILED DESCRIPTION

Techniques to manage connection capabilities information for a wireless communications system are described. In various embodiments, for example an apparatus may comprise a processor circuit, a communications component for execution by the processor circuit to perform neighbor awareness networking (NAN) service discovery and to receive a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device, and a

determination component for execution by the processor circuit to determine whether to initiate a connection with the remote device based on the connection capability bitmap field. Other embodiments are described and claimed.

Various embodiments are generally directed to advanced wireless communications systems. Some embodiments are particularly directed to wireless networks implementing one or more Wi-Fi Alliance (WFA) standards. In some embodiments, for example, a wireless network may operate according to the WFA Wi-Fi Direct standard, 2010 Release. In various

embodiments, neighbor awareness networking (NAN) techniques may be implemented for a wireless network such as a Wi-Fi Direct network to enable device-to-device low power background service discovery. In some embodiments, an improved NAN service discovery scheme may be implemented to enable the exchange of device connection capabilities information during NAN service discovery. The embodiments, however, are not limited to these examples.

This disclosure is not limited to Wi-Fi Direct related standards, but may also apply to wireless local area networks (WLANs), such as WLANs implementing one or more Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (sometimes collectively referred to as "Wi-Fi"). This disclosure may also apply to wireless wide area networks (WWANs), wireless personal area networks (WPANs), and 3G or 4G wireless standards (including progenies and variants) related to wireless devices, user equipment or network equipment included in WWANs. Examples of 3G or 4G wireless standards may include without limitation any of the IEEE 802.16m and 802.16p standards, 3rd Generation Partnership Project (3GPP) Long Term

Evolution (LTE) and LTE-Advanced (LTE-A) standards, and International Mobile

Telecommunications Advanced (IMT-ADV) standards, including their revisions, progeny and variants. Other suitable examples may include, without limitation, Global System for Mobile Communications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE) technologies, Universal Mobile Telecommunications System (UMTS)/High Speed Packet Access (HSPA) technologies, Worldwide Interoperability for Microwave Access (WiMAX) or the WiMAX Π technologies, Code Division Multiple Access (CDMA) 2000 system technologies (e.g.,

CDMA2000 lxRTT, CDMA2000 EV-DO, CDMA EV-DV, and so forth), High Performance Radio Metropolitan Area Network (HIPERMAN) technologies as defined by the European Telecommunications Standards Institute (ETSI) Broadband Radio Access Networks (BRAN), Wireless Broadband (WiBro) technologies, GSM with General Packet Radio Service (GPRS) system (GSM/GPRS) technologies, High Speed Downlink Packet Access (HSDPA)

technologies, High Speed Orthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA) technologies, High-Speed Uplink Packet Access (HSUPA) system technologies, 3GPP Rel. 8-12 of LTE/System Architecture Evolution (SAE), and so forth. The embodiments are not limited in this context.

In various embodiments, a Wi-Fi Direct network may operate according to standards and/or techniques currently under development by the WFA Neighbor Awareness Networking Task Group. For example, in some embodiments, devices in a Wi-Fi Direct network may conduct service discovery according to neighbor awareness networking techniques complying with standards adopted by the WFA Neighbor Awareness Networking Task Group ("the NAN Task Group"). According to the current solutions provided by the NAN Task Group, no mechanism is specified to enable further action on the part of an NAN device once that device has identified a desired service. Attributes are disclosed herein that may address this shortcoming by enabling NAN devices to obtain connection capabilities information during service discovery and to determine how to connect to other devices based on such connection capabilities information. In various embodiments, for example, a NAN device in a Wi-Fi Direct network may identify a desired service on a remote device based on one or more attributes received from the remote device and determine how to connect to the remote device based on connection capabilities information comprised in the one or more attributes. The embodiments are not limited to this example.

With general reference to notations and nomenclature used herein, the detailed descriptions which follow may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art.

A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical

manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein which form part of one or more embodiments. Rather, the operations are machine operations. Useful machines for performing operations of various embodiments include general purpose digital computers or similar devices.

Various embodiments also relate to apparatus or systems for performing these operations. This apparatus may be specially constructed for the required purpose or it may comprise a general purpose computer as selectively activated or reconfigured by a computer program stored in the computer. The procedures presented herein are not inherently related to a particular computer or other apparatus. Various general purpose machines may be used with programs written in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these machines will appear from the description given.

Reference is now made to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. In other instances, well known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modifications, equivalents, and alternatives consistent with the claimed subject matter.

FIG. 1 illustrates an operating environment 100 such as may be representative of various embodiments. As shown in FIG. 1, a wireless device 102 may generate a NAN information element (IE) 104. In some embodiments, wireless device 102 may comprise a NAN-capable wireless communications device, such as a NAN-capable tablet, laptop, or desktop computing device, smart phone, cellular phone, electronic reading device, personal digital assistant, or other electronic device. In an example embodiment, wireless device 102 may comprise an

Ultrabook™ device made by Intel® Corporation, Santa Clara, Calif. In various embodiments, NAN IE 104 may comprise information to be provided to one or more remote devices in conjunction with NAN service discovery. For example, in some embodiments, NAN IE 104 may comprise information regarding services provided by wireless device 102, and may be generated and provided to a remote wireless device 106 in conjunction with NAN service discovery on the part of the remote wireless device 106. In various embodiments, wireless device 106 may comprise another NAN-capable wireless communications device, such as any of the examples previously mentioned with respect to wireless device 102. The embodiments are not limited to these examples.

In some embodiments, NAN IE 104 may comprise a connection capability attribute 108. Connection capability attribute 108 may comprise a data element that is used to convey information relating to connection capabilities of wireless device 102. In various embodiments, when wireless device 106 initiates NAN service discovery, wireless device 102 may be operative to transmit NAN IE 104 to wireless device 106. Wireless device 106 may be operative to determine, based on NAN IE 104, whether wireless device 102 provides any services that wireless device 106 wishes to obtain. In some embodiments, when wireless device 102 does provide one or more desired services, the information already received in connection capability attribute 108 may enable wireless device 106 to determine an appropriate manner via which to connect with wireless device 102 following NAN service discovery. The embodiments are not limited in this context.

FIG. 2 illustrates a connection capability attribute 200, such as may comprise an example of connection capability attribute 108 of FIG. 1. For example, a NAN device in a Wi-Fi Direct network may generate a NAN information element (IE) comprising connection capability attribute 200 during NAN service discovery in some embodiments. As shown in FIG. 2, connection capability attribute 200 may comprise an attribute ID field 202, a length field 204, and a connection capability bitmap field 206. In various embodiments, the attribute ID field 202 may comprise 1 octet, the length field 204 may comprise 2 octets, and the connection capability bitmap field 206 may comprise 2 octets. In some embodiments, attribute ID field 202 may comprise a value indicating that the attribute is a connection capability attribute. In various embodiments, length field 204 may comprise a value indicating a length of the subsequent fields of the connection capability attribute 200. For example, length field 204 may comprise a value indicating a length of connection capability bitmap 206. In various embodiments, length field 204 may comprise a value of 2. In some embodiments, connection capability bitmap field 206 may comprise a set of bits describing connection capabilities of the device that generates the connection capability attribute 200, as will be discussed in more detail below. These fields and field sizes are exemplary, and a given implementation of connection capability attribute 200 may have different fields and field sizes. The embodiments are not limited in this context.

FIG. 3 illustrates a connection capability bitmap field 300, such as may comprise an example of the connection capability bitmap field 206 in the connection capability attribute 200 of FIG. 2. As shown in FIG. 3, the connection capability bitmap field 300 may comprise a Wi-Fi Direct subfield 302, a Wi-Fi Direct Services subfield 304, a TDLS subfield 306, an AP infrastructure subfield 308, a P2P operation subfield 310, and a cellular service subfield 312. In various embodiments, each of these subfields may comprise one bit. In some embodiments, connection capability bitmap field 300 may comprise one or more reserved bits 314. In various embodiments, for example, connection capability bitmap field 300 may comprise ten reserved bits 314. These subfields and subfield sizes are exemplary, and a given implementation of connection capability bitmap field 300 may have different subfields and subfield sizes. The embodiments are not limited in this context.

In some embodiments, Wi-Fi Direct subfield 302 may comprise a value indicating whether a device generating connection capability attribute 200 supports Wi-Fi Direct. In various embodiments, Wi-Fi Direct subfield 302 may comprise a value of 1 if the device supports Wi-Fi Direct, and may otherwise comprise a value of 0. In various embodiments, Wi-Fi Direct Services subfield 304 may comprise a value indicating whether a device generating connection capability attribute 200 supports Wi-Fi Direct Services. In various embodiments, Wi-Fi Direct Services subfield 304 may comprise a value of 1 if the device supports Wi-Fi Direct Services, and may otherwise comprise a value of 0. In some embodiments, TDLS subfield 306 may comprise a value indicating whether a device generating connection capability attribute 200 supports tunneled direct link setup (TDLS). In various embodiments, TDLS subfield 306 may comprise a value of 1 if the device supports TDLS, and may otherwise comprise a value of 0. The embodiments are not limited to these example values.

In various embodiments, AP infrastructure subfield 308 may comprise a value indicating whether a device generating connection capability attribute 200 is connected to an infrastructure access point (AP). In various embodiments, AP infrastructure subfield 308 may comprise a value of 1 if the device is connected to an infrastructure AP, and may otherwise comprise a value of 0. In some embodiments, P2P operation subfield 310 may comprise a value indicating whether a device generating connection capability attribute 200 is operating as a peer-to-peer (P2P) device, group, or client. In various embodiments, P2P operation subfield 310 may comprise a value of 1 if the device is operating as a P2P device, P2P group, or P2P client, and may otherwise comprise a value of 0. In various embodiments, cellular service subfield 312 may comprise a value indicating whether a device generating connection capability attribute 200 is connected to cellular service. In various embodiments, cellular service subfield 312 may comprise a value of 1 if the device is connected to cellular service, and may otherwise comprise a value of 0. The embodiments are not limited to these example values. In some embodiments, a device that receives a connection capability attribute 200 from a second device may determine whether to obtain services from that second device based on connection capabilities indicated by the various subfields of connection capability bitmap field 300. For example, wireless device 106 of FIG. 1 may initiate a connection with wireless device 102 to obtain a service from wireless device 102 based on a determination, according to connection capability bitmap field 300, that wireless device 102 is capable of a desired type of connection. In another example, wireless device 104 may choose not to initiate a connection with wireless device 102 based on a determination, according to connection capability bitmap field 300, that wireless device 102 is not capable of a desired type of connection. The embodiments are not limited to these examples.

In some embodiments, a device that indicates in a connection capability attribute 200 that it is capable of particular connections may generate one or more additional information attributes to provide additional information regarding those capabilities. In various embodiments, a device may include one or more such additional information attributes in a same information element as connection capability attribute 200. For example, in some embodiments, wireless device 102 of FIG. 1 may generate NAN IE 104 such that it comprises connection capability attribute 108 and one or more additional information attributes comprising additional information regarding capabilities identified in connection capability attribute 108. Examples of additional information attributes that a device may generate in various embodiments are discussed below with respect to FIGs. 4-6.

FIG. 4 illustrates an AP infrastructure information attribute 400 that a device connected to an infrastructure AP may generate during service discovery. In various embodiments, a device that generates a connection capability attribute 200 indicating that it is connected to an infrastructure AP may include AP infrastructure information attribute 400 in a same IE as that connection capability attribute 200. For example, a NAN device that generates a NAN IE comprising a connection capability attribute 200 that indicates that the NAN device is connected to an infrastructure AP may include AP infrastructure information attribute 400 within that NAN IE.

As shown in FIG. 4, AP infrastructure information attribute 400 may comprise an attribute ID field 402, a length field 404, a MAC address field 406, a country string field 408, an operating class field 410, a channel number field 412, and a time offset field 414. In some embodiments, the attribute ID field 402 may comprise 1 octet, the length field 404 may comprise 2 octets, the MAC address field 406 may comprise 6 octets, the country string field 408 may comprise 3 octets, the operating class field 410 may comprise 1 octet, the channel number field 412 may comprise 1 octet, and the time offset field 414 may comprise 4 octets. These fields and field sizes are exemplary, and a given implementation of AP infrastructure information attribute 400 may have different fields and field sizes. The embodiments are not limited in this context.

In various embodiments, the attribute ID field 402 may comprise a value indicating that the attribute is an AP infrastructure information attribute. In some embodiments, the length field 404 may comprise a value indicating a length of the subsequent fields of the AP infrastructure information attribute 400. In some embodiments, the length field 404 may comprise a value of 15. In various embodiments, the MAC address field 406 may comprise a basic service set identification (BSSID) of an infrastructure AP to which the device generating AP infrastructure information attribute 400 is connected. In some embodiments, the country string field 408 may comprise a value indicating country codes for which values in operating class field 410 and channel number field 412 are valid. In various embodiments, country string field 408 may comprise a value defined in Annex J of IEEE Standard 802.1 lj-2008 ("Annex J") for a country string attribute, such as a "dotl lCountryString" attribute. In some embodiments, a third octet of country string field 408 may comprise a value of x04 to indicate that Table J-4 of Annex J is used. The embodiments are not limited to these examples.

In various embodiments, the operating class field 410 may comprise a value indicating a frequency band at which the infrastructure AP is currently operating. In some embodiments, a value defined in Annex J may be used for a non-directional-multigigabit (non-DMG) connection and a value defined in Annex E of IEEE Standard 802.11-2012 ("Annex E") may be used for a DMG connection. In some embodiments, the channel number field 412 may comprise a value indicating a channel number on which the infrastructure AP is currently operating. In some embodiments, a value defined in Annex I may be used for a non-DMG connection and a value defined in Annex E may be used for a DMG connection. In various embodiments, the time offset field 414 may comprise a value indicating a start time at which the device will be available using the concurrent operating channel identified by the channel number field 412. In some embodiments, the time offset field 414 may comprise a value expressed in 802.11 time units (TUs). The embodiments are not limited to these examples.

FIG. 5 illustrates a P2P operation information attribute 500 that a device operating as a P2P device may generate during service discovery. In various embodiments, a device that generates a connection capability attribute 200 indicating that it is operating as a P2P device may include P2P operation information attribute 500 in a same IE as that connection capability attribute 200. For example, a NAN device that generates a NAN IE comprising a connection capability attribute 200 that indicates that the NAN device is operating as a P2P device may include P2P operation information attribute 500 within that NAN IE. As shown in FIG. 5, P2P operation information attribute 500 may comprise an attribute ID field 502, a length field 504, a P2P device role field 506, a MAC address field 508, a country string field 510, an operating class field 512, a channel number field 514, and a time offset field 516. In some embodiments, the attribute ID field 502 may comprise 1 octet, the length field 504 may comprise 2 octets, the P2P device role field 506 may comprise 1 octet, the MAC address field 508 may comprise 6 octets, the country string field 510 may comprise 3 octets, the operating class field 512 may comprise 1 octet, the channel number field 514 may comprise 1 octet, and the time offset field 516 may comprise 4 octets. These fields and field sizes are exemplary, and a given implementation of P2P operation information attribute 500 may have different fields and field sizes. The embodiments are not limited in this context.

In various embodiments, the attribute ID field 502 may comprise a value indicating that the attribute is a P2P operation information attribute. In some embodiments, the length field 504 may comprise a value indicating a length of the subsequent fields of the P2P operation information attribute 500. In various embodiments, the length field 504 may comprise a value of 15. In some embodiments, the P2P device role field 506 indicating roles for the device if it is operating as a P2P device. In various embodiments, the device generating P2P operation information attribute 500 may belong to a P2P group, and MAC address field 508 may comprise a MAC address of that P2P group. In other embodiments, the device generating P2P operation information attribute 500 may operate as a P2P device but may not belong to a P2P group, and MAC address field 508 may comprise P2P device address for the device. In some embodiments, the country string field 510 may comprise a value indicating country codes for which values in operating class field 512 and channel number field 514 are valid. In various embodiments, country string field 510 may comprise a value defined in Annex J for a country string attribute, such as a "dotl ICountryString" attribute. In some embodiments, a third octet of country string field 510 may comprise a value of x04 to indicate that Table 1-4 of Annex J is used. The embodiments are not limited to these examples.

In various embodiments in which the device generating P2P operation information attribute 500 belongs to a P2P group, the operating class field 512 may comprise a value indicating a frequency band at which the P2P group is currently operating. In some

embodiments in which the device generating P2P operation information attribute 500 operates as a P2P device but does not belong to a P2P group, the operating class field 512 may comprise a value indicating a frequency band of a P2P listen channel for the device. In some embodiments, a value defined in Annex J may be used for a non-directional-multigigabit (non-DMG) connection and a value defined in Annex E may be used for a DMG connection. In some embodiments in which the device generating P2P operation information attribute 500 belongs to a P2P group, the channel number field 514 may comprise a value indicating a channel number on which the P2P group is currently operating. In various embodiments in which the device generating P2P operation information attribute 500 operates as a P2P device but does not belong to a P2P group, the channel number field 514 may comprise a value indicating a channel number of a P2P listen channel for the device. In some embodiments, a value defined in Annex J may be used for a non-DMG connection and a value defined in Annex E may be used for a DMG connection. In various embodiments, the time offset field 516 may comprise a value indicating a start time at which the device will be available using the operating channel or listen channel identified by the channel number field 514. In some embodiments, the time offset field 516 may comprise a value expressed in 802.11 TUs. The embodiments are not limited to these examples.

FIG. 6 illustrates a cellular service information attribute 600 that a device that is connected to cellular service may generate during service discovery. In various embodiments, a device that generates a connection capability attribute 200 indicating that it is connected to cellular service may include cellular service information attribute 600 in a same IE as that connection capability attribute 200. For example, a NAN device that generates a NAN IE comprising a connection capability attribute 200 that indicates that the NAN device is connected to cellular service may include cellular service information attribute 600 within that NAN IE.

As shown in FIG. 6, cellular service information attribute 600 may comprise an attribute ID field 602, a length field 604, and a phone number field 606. In some embodiments, the attribute ID field 602 may comprise 1 octet, the length field 604 may comprise 2 octets, and the phone number field 606 may comprise 8 octets. These fields and field sizes are exemplary, and a given implementation of cellular service information attribute 600 may have different fields and field sizes. The embodiments are not limited in this context.

In various embodiments, the attribute ID field 602 may comprise a value indicating that the attribute is a cellular service information attribute. In some embodiments, the length field 604 may comprise a value indicating a length of the subsequent fields of the cellular service information attribute 600. In some embodiments, the length field 604 may comprise a value of 8. In various embodiments, the phone number field 606 may comprise a value indicating a phone number of a device generating the cellular service information attribute 600. The embodiments are not limited to these examples.

FIG. 7 illustrates a block diagram of an apparatus 700. Apparatus 700 comprises an example of an apparatus, such as wireless device 102 of FIG. 1, which may generate and send a NAN IE comprising a connection capability attribute such as connection capability attribute 200 of FIG. 2. As shown in FIG. 7, apparatus 700 comprises multiple elements including a processor circuit 702, a memory unit 704, a reporting component 706, and a communications component 708. The embodiments, however, are not limited to the type, number, or arrangement of elements shown in this figure.

In various embodiments, apparatus 700 may comprise processor circuit 702. Processor circuit 702 may be implemented using any processor or logic device, such as a complex instruction set computer (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, an x86 instruction set compatible processor, a processor implementing a combination of instruction sets, a multi-core processor such as a dual-core processor or dual-core mobile processor, or any other

microprocessor or central processing unit (CPU). Processor circuit 702 may also be implemented as a dedicated processor, such as a controller, a microcontroller, an embedded processor, a chip multiprocessor (CMP), a co-processor, a digital signal processor (DSP), a network processor, a media processor, an input/output (I/O) processor, a media access control (MAC) processor, a radio baseband processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), and so forth. In one embodiment, for example, processor circuit 702 may be implemented as a general purpose processor, such as a processor made by Intel® Corporation, Santa Clara, Calif. The embodiments are not limited in this context.

In some embodiments, apparatus 700 may comprise or be arranged to communicatively couple with a memory unit 704. Memory unit 704 may be implemented using any machine- readable or computer-readable media capable of storing data, including both volatile and nonvolatile memory. For example, memory unit 704 may include read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM

(DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, or any other type of media suitable for storing information. It is worthy of note that some portion or all of memory unit 704 may be included on the same integrated circuit as processor circuit 702, or alternatively some portion or all of memory unit 704 may be disposed on an integrated circuit or other medium, for example a hard disk drive, that is external to the integrated circuit of processor circuit 702. Although memory unit 704 is comprised within apparatus 700 in FIG. 7, memory unit 704 may be external to apparatus 700 in some embodiments. The embodiments are not limited in this context.

In various embodiments, apparatus 700 may comprise a reporting component 706.

Reporting component 706 may comprise logic, circuitry, and/or instructions operative to generate NAN IEs for transmission to remote devices in conjunction with NAN service discovery on the part of those remote devices. In some embodiments, reporting component 706 may be operative to generate NAN IEs that comprise information identifying one or more services provided by apparatus 700 and information describing various connection capabilities of apparatus 700. The embodiments are not limited in this context.

In various embodiments, apparatus 700 may comprise a communications component 708. Communications component 708 may comprise logic, circuitry, and/or instructions operative to send messages to one or more remote devices and/or to receive messages from one or more remote devices. In some embodiments, communications component 708 may be operative to exchange messages with one or more remote devices in conjunction with NAN service discovery on the part of those remote devices and/or in conjunction with providing services to those remote devices. In various embodiments, communications component 708 may be operative to send NAN IEs generated by reporting component 706 to one or more remote devices. The embodiments are not limited in this context.

FIG. 7 also illustrates a block diagram of a system 740. System 740 may comprise any of the aforementioned elements of apparatus 700. System 740 may further comprise one or more additional components. For example, in various embodiments, system 740 may comprise a radio frequency (RF) transceiver 744. RF transceiver 744 may include one or more radios capable of transmitting and receiving signals using various suitable wireless communications techniques. Such techniques may involve communications across one or more wireless networks.

Exemplary wireless networks include (but are not limited to) wireless local area networks (WLANs), wireless personal area networks (WPANs), wireless metropolitan area network (WMANs), cellular networks, and satellite networks. In communicating across such networks, RF transceiver 744 may operate in accordance with one or more applicable standards in any version. The embodiments are not limited in this context.

In some embodiments, system 740 may comprise one or more RF antennas 757. Examples of any particular RF antenna 757 may include an internal antenna, an omni-directional antenna, a monopole antenna, a dipole antenna, an end-fed antenna, a circularly polarized antenna, a micro- strip antenna, a diversity antenna, a dual antenna, a tri-band antenna, a quad-band antenna, and so forth. The embodiments are not limited to these examples. In some embodiments, communications component 708 may be operative to exchange communications with one or more remote devices using RF transceiver 744 and/or one or more RF antennas 757. The embodiments are not limited in this context.

In various embodiments, system 740 may include a display 745. Display 745 may comprise any display device capable of displaying information received from processor circuit 702. Examples for display 745 may include a television, a monitor, a projector, and a computer screen. In one embodiment, for example, display 745 may be implemented by a liquid crystal display (LCD), light emitting diode (LED) or other type of suitable visual interface. Display 745 may comprise, for example, a touch- sensitive display screen ("touchscreen"). In various implementations, display 745 may comprise one or more thin-film transistors (TFT) LCD including embedded transistors. The embodiments are not limited in this context.

In general operation, apparatus 700 and or system 740 may be operative to provide one or more services for use by one or more remote devices, which may perform NAN service discovery in order to identify such services. In various embodiments, apparatus 700 and/or system 740 may be operative to generate NAN IEs for transmission to remote devices during NAN service discovery. In some embodiments, the NAN IEs may comprise information identifying services provided by apparatus 700 and/or system 740 and information describing connection capabilities of apparatus 700 and/or system 740. In various embodiments, remote devices that receive such NAN IEs may be operative to obtain services from apparatus 700 and/or system 740 via connections established according to connection capability information comprised in such NAN IEs. The embodiments are not limited in this context.

In some embodiments, reporting component 706 may be operative to determine that service information should be transmitted for use in conjunction with NAN service discovery by one or more remote devices, which may include a remote device 750. Remote device 750 may comprise a NAN-capable device, and may be the same as or similar to wireless device 104 of FIG. 1. The embodiments are not limited in this context.

In various embodiments, reporting component 706 may be operative to generate a NAN IE 710 to enable NAN service discovery on the part of remote device 750 and/or one or more other remote devices. In some embodiments, NAN IE 710 may comprise information regarding services provided by apparatus 700 and/or system 740, and may be the same as or similar to NAN IE 104 of FIG. 1. In various embodiments, NAN IE 710 may comprise a connection capability attribute 712. Connection capability attribute 712 may comprise a data element that is used to convey information relating to connection capabilities of apparatus 700 and/or system 740, and may be the same as or similar to connection capability attribute 108 of FIG. 1 and/or connection capability attribute 200 of FIG. 2. In some embodiments, connection capability attribute 712 may comprise a connection capability bitmap field 714. Connection capability bitmap field 714 may comprise information describing one or more connection capabilities of apparatus 700 and/or system 740, and may be the same as or similar to connection capability bitmap field 206 of FIG. 2 and/or connection capability bitmap field 300 of FIG. 3. The embodiments are not limited in this context. In various embodiments, communications component 708 may be operative to send NAN IE 710 to remote device 750 and/or one or more other remote devices. For example, in some embodiments, communications component 708 may be operative to send NAN IE 710 to remote device 750 using RF transceiver 744 and/or one or more RF antennas 757. In various embodiments, remote device 750 may be operative to receive NAN IE 710 and determine whether to initiate a connection with apparatus 700 and/or system 740 based on NAN IE 710. In some embodiments, remote device 750 may be operative to determine whether apparatus 700 and/or system 740 provides one or more desired services based on NAN IE 710. In various embodiments, when apparatus 700 and/or system 740 provides one or more desired services, remote device 750 may be operative to determine that a connection is to be initiated with apparatus 700 and/or system 740. In some embodiments, remote device 750 may be operative to determine a connection type for such a connection based on the connection capability bitmap field 714. The embodiments are not limited in this context.

FIG. 8 illustrates an embodiment of a logic flow 800, which may be representative of the operations executed by one or more embodiments described herein, such as apparatus 700 and/or system 740 of FIG. 7. As shown in FIG. 8, it may be determined that service information should be transmitted for use in NAN service discovery by one or more remote devices at 802. For example, reporting component 706 of FIG. 7 may be operative to determine that service information identifying one or more services provided by apparatus 700 and/or system 740 should be transmitted to remote device 750. At 804, a NAN IE may be generated that comprises a connection capability bitmap field describing one or more connection capabilities. For example, reporting component 706 of FIG. 7 may be operative to generate a NAN IE 710 comprising a connection capability bitmap field 714 that describes one or more connection capabilities of apparatus 700 and/or system 740. At 806, the NAN IE may be sent to one or more remote devices. For example, communications component 708 of FIG. 7 may be operative to send NAN IE 710 to remote device 750. The embodiments are not limited to these examples.

FIG. 9 illustrates a block diagram of an apparatus 900. Apparatus 900 comprises an example of an apparatus, such as wireless device 104 of FIG. 1, which may receive a NAN IE comprising a connection capability attribute such as connection capability attribute 200 of FIG. 2. As shown in FIG. 9, apparatus 900 comprises multiple elements including a processor circuit 902, a memory unit 904, a communications component 906, and a determination component 908. The embodiments, however, are not limited to the type, number, or arrangement of elements shown in this figure. In various embodiments, apparatus 900 may comprise processor circuit 902. Processor circuit 902 may be implemented using any processor or logic device, and may be the same as or similar to processor circuit 702 of FIG. 7. The embodiments are not limited in this context.

In some embodiments, apparatus 900 may comprise or be arranged to communicatively couple with a memory unit 904. Memory unit 904 may be implemented using any machine- readable or computer-readable media capable of storing data, including both volatile and nonvolatile memory, and may be the same as or similar to memory unit 704 of FIG. 7. It is worthy of note that some portion or all of memory unit 904 may be included on the same integrated circuit as processor circuit 902, or alternatively some portion or all of memory unit 904 may be disposed on an integrated circuit or other medium, for example a hard disk drive, that is external to the integrated circuit of processor circuit 902. Although memory unit 904 is comprised within apparatus 900 in FIG. 9, memory unit 904 may be external to apparatus 900 in some

embodiments. The embodiments are not limited in this context.

In various embodiments, apparatus 900 may comprise a communications component 906. Communications component 906 may comprise logic, circuitry, and/or instructions operative to send messages to one or more remote devices and/or to receive messages from one or more remote devices. In some embodiments, communications component 908 may be operative to exchange messages with a remote device in conjunction with performing NAN service discovery of services provided by that remote device and/or in conjunction with connecting to that remote device to obtain such services. In various embodiments, communications component 906 may be operative to receive one or more NAN IEs from such a remote device during NAN service discovery. The embodiments are not limited in this context.

In some embodiments, apparatus 900 may comprise a determination component 908. Determination component 908 may comprise logic, circuitry, and/or instructions operative to determine whether and/or how to establish a connection to a remote device in order to obtain one or more services provided by that remote device. In various embodiments, reporting component 906 may be operative to generate NAN IEs that comprise information identifying one or more services provided by apparatus 900 and information describing various connection capabilities of apparatus 900. The embodiments are not limited in this context.

FIG. 9 also illustrates a block diagram of a system 940. System 940 may comprise any of the aforementioned elements of apparatus 900. System 940 may further comprise one or more additional components. For example, in various embodiments, system 940 may comprise an RF transceiver 944. RF transceiver 944 may include one or more radios capable of transmitting and receiving signals using various suitable wireless communications techniques, and may be the same as or similar to RF transceiver 744 of FIG. 7. In some embodiments, system 940 may comprise one or more RF antennas 957. Examples of any particular RF antenna 957 may include any of those previously mentioned with respect to RF antennas 757 of FIG. 7. In some embodiments, communications component 906 may be operative to exchange communications with one or more remote devices using RF transceiver 944 and/or one or more RF antennas 957. The embodiments are not limited in this context.

In various embodiments, system 940 may include a display 945. Display 945 may comprise any display device capable of displaying information received from processor circuit 902, and may be the same as or similar to display 745 of FIG. 7. The embodiments are not limited in this context.

In general operation, apparatus 900 and/or system 940 may be operative to perform NAN service discovery in order to identify one or more services provided by one or more remote devices. In various embodiments, during NAN service discovery, apparatus 900 and/or system 940 may be operative to receive various NAN IEs that comprise information identifying available services and information describing connection capabilities of remote devices providing those services. In some embodiments, apparatus 900 and/or system 940 may be operative to obtain services from one or more remote devices via connections established according to connection capability information comprised in such NAN IEs. The embodiments are not limited in this context.

In various embodiments, communications component 906 may be operative to initiate NAN service discovery with a remote device 960. Remote device 960 may comprise a NAN- capable device that provides one or more services, and may be the same as or similar to wireless device 102 of FIG. 1 and/or apparatus 700 and/or system 740 of FIG. 7. The embodiments are not limited in this context.

In some embodiments, during NAN service discovery, communications component 906 may be operative to receive a NAN IE 910 from the remote device 960. In various

embodiments, NAN IE 910 may comprise information regarding services provided by wireless device 960, and may be the same as or similar to NAN IE 104 of FIG. 1 and/or NAN IE 710 of FIG. 7. In some embodiments, NAN IE 910 may comprise a connection capability attribute 912. Connection capability attribute 912 may comprise a data element that is used to convey information relating to connection capabilities of wireless device 960, and may be the same as or similar to connection capability attribute 108 of FIG. 1, connection capability attribute 200 of FIG. 2, and/or connection capability attribute 712 of FIG. 7. In various embodiments, connection capability attribute 912 may comprise a connection capability bitmap field 914. Connection capability bitmap field 914 may comprise information describing one or more connection capabilities of remote device 960, and may be the same as or similar to connection capability bitmap field 206 of FIG. 2, connection capability bitmap field 300 of FIG. 3, and/or connection capability bitmap field 714 of FIG. 7. The embodiments are not limited in this context.

In some embodiments, determination component 908 may be operative to determine whether to initiate a connection with remote device 960 based on NAN IE 910. In various embodiments, determination component 908 may be operative to determine whether remote device 960 provides one or more desired services based on NAN IE 910. In some embodiments, when remote device 960 provides one or more desired services, determination component 908 may be operative to determine that a connection is to be initiated with remote device 960. In various embodiments, when it has determined that a connection is to be initiated with remote device 960, determination component 908 may be operative to determine a connection type for connecting to remote device 960. In some such embodiments, determination component 908 may be operative to determine the connection type based on the connection capability bitmap field 914. In an example embodiment, determination component 908 may be operative to determine that remote device 960 provides a desired service and thus that a connection is to be initiated, and may be operative to determine that the connection is to be a Wi-Fi Direct connection based on information in the connection capability bitmap field 914 indicating that remote device 960 is capable of establishing a Wi-Fi Direct connection. The embodiments are not limited to this example.

FIG. 10 illustrates an embodiment of a logic flow 1000, which may be representative of the operations executed by one or more embodiments described herein, such as apparatus 900 and/or system 940 of FIG. 9. As shown in FIG. 10, NAN service discovery may be initiated at a wireless device at 1002. For example, communications component 906 of FIG. 9 may be operative to initiate NAN service discovery in order to determine whether remote device 960 provides any desired services. At 1004, during NAN service discovery, a NAN IE may be received that comprises a connection capability bitmap field describing one or more connection capabilities of the remote device. For example, during NAN service discovery with respect to remote device 960, communications component 906 of FIG. 9 may be operative to receive NAN IE 910, which may comprise a connection capability attribute 912 including a connection capability bitmap field 914. At 1006, based on the NAN IE, it may be determined whether to initiate a connection with the remote device. For example, based on NAN IE 910, determination component 908 of FIG. 9 may be operative to determine whether to initiate a connection with remote device 960, by determining whether remote device 960 provides any desired services. If it is determined at 1006 that no connection is to be initiated, the logic flow may end. If it is determined at 1006 that a connection is to be initiated, flow may pass to 1008. At 1008, a connection type may be determined for connecting to the remote device, based on the connection capability bitmap field. For example, determination component 908 of FIG. 9 may be operative to determine a connection type for connecting to remote device 960 based on connection capability bitmap field 914. The embodiments are not limited to these examples.

FIG. 11 illustrates an embodiment of a storage medium 1100. The storage medium 1100 may comprise an article of manufacture. In one embodiment, the storage medium 1100 may comprise any non-transitory computer readable medium or machine readable medium, such as an optical, magnetic or semiconductor storage. The storage medium 1100 may store various types of computer executable instructions, such as computer executable instructions to implement logic flow 800 of FIG. 8 and/or logic flow 1000 of FIG. 10. Examples of a computer readable or machine readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non- volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of computer executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The embodiments are not limited in this context.

FIG. 12 illustrates an embodiment of a device 1200 for use in a wireless communications system, such as an IEEE 802.11 WLAN system. Device 1200 may be suitable to implement various embodiments, such as apparatus 700 and/or system 740 of FIG. 7, logic flow 800 of FIG. 8, apparatus 900 and/or system 940 of FIG. 9, and/or logic flow 1000 of FIG. 10. Device 1200 may be implemented, for example, in user equipment (UE), a base station, the storage medium 1100 and/or a logic circuit 1230. The logic circuit 1230 may include physical circuits to perform operations described for a UE or a base station. As shown in FIG. 12, device 1200 may include a radio interface 1210, baseband circuitry 1220, and computing platform 1230, although embodiments are not limited to this configuration.

The device 1200 may implement some or all of the structure and/or operations for a UE, a base station, the storage medium 1100 and/or logic circuit 1230 in a single computing entity, such as entirely within a single device. Alternatively, the device 1200 may distribute portions of the structure and/or operations for a UE, a base station, the storage medium 1100 and/or logic circuit 1230 across multiple computing entities using a distributed system architecture, such as a client- server architecture, a 3-tier architecture, an N-tier architecture, a tightly-coupled or clustered architecture, a peer-to-peer architecture, a master-slave architecture, a shared database architecture, and other types of distributed systems. The embodiments are not limited in this context. In one embodiment, radio interface 1210 may include a component or combination of components adapted for transmitting and/or receiving single carrier or multi-carrier modulated signals (e.g., including complementary code keying (CCK) and/or orthogonal frequency division multiplexing (OFDM) symbols) although the embodiments are not limited to any specific over- the-air interface or modulation scheme. Radio interface 1210 may include, for example, a receiver 1212, a transmitter 1216 and/or a frequency synthesizer 1214. Radio interface 1210 may include bias controls, a crystal oscillator and/or one or more antennas 1218-p. In another embodiment, radio interface 1210 may use external voltage-controlled oscillators (VCOs), surface acoustic wave filters, intermediate frequency (IF) filters and/or RF filters, as desired. Due to the variety of potential RF interface designs an expansive description thereof is omitted.

Baseband circuitry 1220 may communicate with radio interface 1210 to process receive and/or transmit signals and may include, for example, an analog-to-digital converter 1222 for down converting received signals, a digital-to-analog converter 1224 for up converting signals for transmission. Further, baseband circuitry 1220 may include a baseband or physical layer (PHY) processing circuit 1256 for PHY link layer processing of respective receive/transmit signals. Baseband circuitry 1220 may include, for example, a processing circuit 1228 for medium access control (MAC)/data link layer processing. Baseband circuitry 1220 may include a memory controller 1232 for communicating with processing circuit 1228 and/or a computing platform 1230, for example, via one or more interfaces 1234.

In some embodiments, PHY processing circuit 1226 may include a frame construction and/or detection module, in combination with additional circuitry such as a buffer memory, to construct and/or deconstruct communication frames. Alternatively or in addition, MAC processing circuit 1228 may share processing for certain of these functions or perform these processes independent of PHY processing circuit 1226. In some embodiments, MAC and PHY processing may be integrated into a single circuit.

The computing platform 1230 may provide computing functionality for the device 1200. As shown, the computing platform 1230 may include a processing component 1240. In addition to, or alternatively of, the baseband circuitry 1220, the device 1200 may execute processing operations or logic for a UE, a base station, the storage medium 1100 and/or logic circuit 1230 using the processing component 1230. The processing component 1230 (and/or PHY 1226 and/or MAC 1228) may comprise various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

The computing platform 1230 may further include other platform components 1250. Other platform components 1250 include common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components (e.g., digital displays), power supplies, and so forth. Examples of memory units may include without limitation various types of computer readable and machine readable storage media in the form of one or more higher speed memory units, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, an array of devices such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (e.g., USB memory, solid state drives (SSD) and any other type of storage media suitable for storing information.

Device 1200 may be, for example, an ultra-mobile device, a mobile device, a fixed device, a machine- to -machine (M2M) device, a personal digital assistant (PDA), a mobile computing device, a smart phone, a telephone, a digital telephone, a cellular telephone, user equipment, eBook readers, a handset, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a netbook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, game devices, television, digital television, set top box, wireless access point, base station, node B, evolved node B (eNB), subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. Accordingly, functions and/or specific configurations of device 1200 described herein, may be included or omitted in various embodiments of device 1200, as suitably desired. In an example embodiment, device 1200 may comprise an Ultrabook™ device made by Intel® Corporation, Santa Clara, Calif. In some embodiments, device 1200 may be configured to be compatible with protocols and frequencies associated one or more of the 3GPP LTE Specifications and/or IEEE 1202.16 Standards for WMANs, and/or other broadband wireless networks, cited herein, although the embodiments are not limited in this respect.

Embodiments of device 1200 may be implemented using single input single output (SISO) architectures. However, certain implementations may include multiple antennas (e.g., antennas 1218- ») for transmission and/or reception using adaptive antenna techniques for beamforming or spatial division multiple access (SDMA) and/or using MIMO communication techniques.

The components and features of device 1200 may be implemented using any combination of discrete circuitry, application specific integrated circuits (ASICs), logic gates and/or single chip architectures. Further, the features of device 1200 may be implemented using

microcontrollers, programmable logic arrays and/or microprocessors or any combination of the foregoing where suitably appropriate. It is noted that hardware, firmware and/or software elements may be collectively or individually referred to herein as "logic" or "circuit."

It should be appreciated that the exemplary device 1200 shown in the block diagram of FIG. 12 may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and/or elements for implementing these functions would be necessarily be divided, omitted, or included in embodiments.

Example 1 is a wireless communication apparatus, comprising a processor circuit, a communications component for execution by the processor circuit to initiate neighbor awareness networking (NAN) service discovery and to receive a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device, and a determination component for execution by the processor circuit to determine whether to initiate a connection with the remote device based on the NAN IE. In Example 2, the determination component of Example 1 may optionally be for execution by the processor circuit to determine a connection type for connecting to the remote device based on the connection capability bitmap field when it has determined that a connection is to be initiated with the remote device.

In Example 3, the connection capability bitmap field of any one of Examples 1 to 2 may optionally comprise a Wi-Fi Direct subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct connection.

In Example 4, the connection capability bitmap field of any one of Examples 1 to 3 may optionally comprise a Wi-Fi Direct Services subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct Services connection.

In Example 5, the connection capability bitmap field of any one of Examples 1 to 4 may optionally comprise a tunneled direct link setup (TDLS) subfield indicating whether the remote device is capable of establishing a TDLS connection.

In Example 6, the connection capability bitmap field of any one of Examples 1 to 5 may optionally comprise an access point (AP) infrastructure subfield indicating whether the remote device is connected to an infrastructure AP.

In Example 7, the AP infrastructure subfield of Example 6 may optionally indicate that the remote device is connected to an infrastructure AP, and the NAN IE may optionally comprise an AP infrastructure information attribute including a field identifying a basic service set identification (BSSID) of an infrastructure AP to which the remote device is connected.

In Example 8, the AP infrastructure information attribute of Example 7 may optionally comprise an operating class field indicating a frequency band at which the infrastructure AP is currently operating.

In Example 9, the AP infrastructure information attribute of any one of Examples 7 to 8 may optionally comprise a channel number field indicating a channel number on which the infrastructure AP is currently operating.

In Example 10, the AP infrastructure information attribute of Example 9 may optionally comprise a time offset field indicating a start time at which the remote device will be available using the operating channel identified by the channel number field.

In Example 11, the connection capability bitmap field of any one of Examples 1 to 10 may optionally comprise a peer-to-peer (P2P) operation subfield indicating whether the remote device is operating as a P2P device.

In Example 12, the P2P operation subfield of Example 11 may optionally indicate that the remote device is operating as a P2P device, and the NAN IE may optionally comprise a P2P operation information attribute including a field identifying a P2P device address or a P2P group address for the remote device.

In Example 13, the P2P operation information attribute of Example 12 may optionally include a channel number field, and the channel number field may optionally indicate a channel number of a P2P listen channel for the remote device when the remote device does not belong to a P2P group.

In Example 14, the connection capability bitmap field of any one of Examples 1 to 13 may optionally comprise a cellular service subfield indicating whether the remote device is connected to a cellular service.

In Example 15, the cellular service subfield of Example 14 may optionally indicate that the remote device is connected to a cellular service, and the NAN IE may optionally comprise a cellular service information attribute including a field identifying a phone number of the remote device.

In Example 16, the NAN IE of any one of Examples 1 to 15 may optionally include an attribute identifier (ID) field comprising a value indicating that the NAN IE is a connection capability attribute.

In Example 17, the NAN IE of any one of Examples 1 to 16 may optionally include a length field comprising a value indicating a length of the connection capability bitmap field.

In Example 18, the connection capability bitmap field of any one of Examples 1 to 17 may optionally comprise one or more reserved bits.

Example 19 is a system, comprising a wireless communication apparatus according to any one of Examples 1 to 18, a display, a radio frequency (RF) transceiver, and one or more RF antennas.

Example 20 is at least one machine-readable medium comprising a plurality of service discovery instructions that, in response to being executed on a computing device, cause the computing device to initiate neighbor awareness networking (NAN) service discovery at a wireless device, receive a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device, and determine whether to initiate a connection with the remote device based on the NAN IE.

In Example 21, the at least one machine-readable medium of Example 20 may optionally comprise service discovery instructions that, in response to being executed on the computing device, cause the computing device to determine a connection type for connecting to the remote device based on the connection capability bitmap field when it is determined that a connection is to be initiated with the remote device. In Example 22, the connection capability bitmap field of any one of Examples 20 to 21 may optionally comprise a Wi-Fi Direct subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct connection.

In Example 23, the connection capability bitmap field of any one of Examples 20 to 22 may optionally comprise a Wi-Fi Direct Services subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct Services connection.

In Example 24, the connection capability bitmap field of any one of Examples 20 to 23 may optionally comprise a tunneled direct link setup (TDLS) subfield indicating whether the remote device is capable of establishing a TDLS connection.

In Example 25, the connection capability bitmap field of any one of Examples 20 to 24 may optionally comprise an access point (AP) infrastructure subfield indicating whether the remote device is connected to an infrastructure AP.

In Example 26, the AP infrastructure subfield of Example 25 may optionally indicate that the remote device is connected to an infrastructure AP, and the NAN IE may optionally comprise an AP infrastructure information attribute including a field identifying a basic service set identification (BSSID) of an infrastructure AP to which the remote device is connected.

In Example 27, the AP infrastructure information attribute of Example 26 may optionally comprise an operating class field indicating a frequency band at which the infrastructure AP is currently operating.

In Example 28, the AP infrastructure information attribute of any one of Examples 26 to 27 may optionally comprise a channel number field indicating a channel number on which the infrastructure AP is currently operating.

In Example 29, the AP infrastructure information attribute of Example 28 may optionally comprise a time offset field indicating a start time at which the remote device will be available using the operating channel identified by the channel number field.

In Example 30, the connection capability bitmap field of any one of Examples 20 to 29 may optionally comprise a peer-to-peer (P2P) operation subfield indicating whether the remote device is operating as a P2P device.

In Example 31, the P2P operation subfield of Example 30 may optionally indicate that the remote device is operating as a P2P device, and the NAN IE may optionally comprise a P2P operation information attribute including a field identifying a P2P device address or a P2P group address for the remote device.

In Example 32, the P2P operation information attribute of Example 31 may optionally include a channel number field, and the channel number field may optionally indicate a channel number of a P2P listen channel for the remote device when the remote device does not belong to a P2P group.

In Example 33, the connection capability bitmap field of any one of Examples 20 to 32 may optionally comprise a cellular service subfield indicating whether the remote device is connected to a cellular service.

In Example 34, the cellular service subfield of Example 33 may optionally indicate that the remote device is connected to a cellular service, and the NAN IE may optionally comprise a cellular service information attribute including a field identifying a phone number of the remote device.

In Example 35, the NAN IE of any one of Examples 20 to 34 may optionally include an attribute identifier (ID) field comprising a value indicating that the NAN IE is a connection capability attribute.

In Example 36, the NAN IE of any one of Examples 20 to 35 may optionally include a length field comprising a value indicating a length of the connection capability bitmap field.

In Example 37, the connection capability bitmap field of any one of Examples 20 to 36 may optionally comprise one or more reserved bits.

Example 38 is a service discovery method, comprising initiating neighbor awareness networking (NAN) service discovery at a wireless device, receiving a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device, and determining, by a processor circuit, whether to initiate a connection with the remote device based on the NAN IE.

In Example 39, the service discovery method of Example 38 may optionally comprise determining a connection type for connecting to the remote device based on the connection capability bitmap field when it is determined that a connection is to be initiated with the remote device.

In Example 40, the connection capability bitmap field of any one of Examples 38 to 39 may optionally comprise a Wi-Fi Direct subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct connection.

In Example 41, the connection capability bitmap field of any one of Examples 38 to 40 may optionally comprise a Wi-Fi Direct Services subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct Services connection.

In Example 42, the connection capability bitmap field of any one of Examples 38 to 41 may optionally comprise a tunneled direct link setup (TDLS) subfield indicating whether the remote device is capable of establishing a TDLS connection. In Example 43, the connection capability bitmap field of any one of Examples 38 to 42 may optionally comprise an access point (AP) infrastructure subfield indicating whether the remote device is connected to an infrastructure AP.

In Example 44, the AP infrastructure subfield of Example 43 may optionally indicate that the remote device is connected to an infrastructure AP, and the NAN IE may optionally comprise an AP infrastructure information attribute including a field identifying a basic service set identification (BSSID) of an infrastructure AP to which the remote device is connected.

In Example 45, the AP infrastructure information attribute of Example 44 may optionally comprise an operating class field indicating a frequency band at which the infrastructure AP is currently operating.

In Example 46, the AP infrastructure information attribute of any one of Examples 44 to 45 may optionally comprise a channel number field indicating a channel number on which the infrastructure AP is currently operating.

In Example 47, the AP infrastructure information attribute of Example 46 may optionally comprise a time offset field indicating a start time at which the remote device will be available using the operating channel identified by the channel number field.

In Example 48, the connection capability bitmap field of any one of Examples 38 to 47 may optionally comprise a peer-to-peer (P2P) operation subfield indicating whether the remote device is operating as a P2P device.

In Example 49, the P2P operation subfield of Example 48 may optionally indicate that the remote device is operating as a P2P device, and the NAN IE may optionally comprise a P2P operation information attribute including a field identifying a P2P device address or a P2P group address for the remote device.

In Example 50, the P2P operation information attribute of Example 49 may optionally include a channel number field, and the channel number field may optionally indicate a channel number of a P2P listen channel for the remote device when the remote device does not belong to a P2P group.

In Example 51, the connection capability bitmap field of any one of Examples 38 to 50 may optionally comprise a cellular service subfield indicating whether the remote device is connected to a cellular service.

In Example 52, the cellular service subfield of Example 51 may optionally indicate that the remote device is connected to a cellular service, and the NAN IE may optionally comprise a cellular service information attribute including a field identifying a phone number of the remote device. In Example 53, the NAN IE of any one of Examples 38 to 52 may optionally include an attribute identifier (ID) field comprising a value indicating that the NAN IE is a connection capability attribute.

In Example 54, the NAN IE of any one of Examples 38 to 53 may optionally include a length field comprising a value indicating a length of the connection capability bitmap field.

In Example 55, the connection capability bitmap field of any one of Examples 38 to 54 may optionally comprise one or more reserved bits.

Example 56 is at least one machine-readable medium comprising a plurality of instructions that, in response to being executed on a computing device, cause the computing device to perform a service discovery method according to any one of Examples 38 to 55.

Example 57 is an apparatus, comprising means for performing a service discovery method according to any one of Examples 38 to 55.

Example 58 is a system, comprising an apparatus according to Example 57, a display, a radio frequency (RF) transceiver, and one or more RF antennas.

Example 59 is a communications device arranged to perform a service discovery method according to any one of Examples 38 to 55.

Example 60 is a wireless communication apparatus, comprising means for initiating neighbor awareness networking (NAN) service discovery at a wireless device, means for receiving a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device, and means for determining whether to initiate a connection with the remote device based on the NAN IE.

In Example 61 , the wireless communication apparatus of Example 60 may optionally comprise means for determining a connection type for connecting to the remote device based on the connection capability bitmap field when it is determined that a connection is to be initiated with the remote device.

In Example 62, the connection capability bitmap field of any one of Examples 60 to 61 may optionally comprise a Wi-Fi Direct subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct connection.

In Example 63, the connection capability bitmap field of any one of Examples 60 to 62 may optionally comprise a Wi-Fi Direct Services subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct Services connection.

In Example 64, the connection capability bitmap field of any one of Examples 60 to 63 may optionally comprise a tunneled direct link setup (TDLS) subfield indicating whether the remote device is capable of establishing a TDLS connection. In Example 65, the connection capability bitmap field of any one of Examples 60 to 64 may optionally comprise an access point (AP) infrastructure subfield indicating whether the remote device is connected to an infrastructure AP.

In Example 66, the AP infrastructure subfield of Example 65 may optionally indicate that the remote device is connected to an infrastructure AP, and the NAN IE may optionally comprise an AP infrastructure information attribute including a field identifying a basic service set identification (BSSID) of an infrastructure AP to which the remote device is connected.

In Example 67, the AP infrastructure information attribute of Example 66 may optionally comprise an operating class field indicating a frequency band at which the infrastructure AP is currently operating.

In Example 68, the AP infrastructure information attribute of any one of Examples 66 to 67 may optionally comprise a channel number field indicating a channel number on which the infrastructure AP is currently operating.

In Example 69, the AP infrastructure information attribute of Example 68 may optionally comprise a time offset field indicating a start time at which the remote device will be available using the operating channel identified by the channel number field.

In Example 70, the connection capability bitmap field of any one of Examples 60 to 69 may optionally comprise a peer-to-peer (P2P) operation subfield indicating whether the remote device is operating as a P2P device.

In Example 71, the P2P operation subfield of Example 70 may optionally indicate that the remote device is operating as a P2P device, and the NAN IE may optionally comprise a P2P operation information attribute including a field identifying a P2P device address or a P2P group address for the remote device.

In Example 72, the P2P operation information attribute of Example 71 may optionally include a channel number field, and the channel number field may optionally indicate a channel number of a P2P listen channel for the remote device when the remote device does not belong to a P2P group.

In Example 73, the connection capability bitmap field of any one of Examples 60 to 72 may optionally comprise a cellular service subfield indicating whether the remote device is connected to a cellular service.

In Example 74, the cellular service subfield of Example 73 may optionally indicate that the remote device is connected to a cellular service, and the NAN IE may optionally comprise a cellular service information attribute including a field identifying a phone number of the remote device. In Example 75, the NAN IE of any one of Examples 60 to 74 may optionally include an attribute identifier (ID) field comprising a value indicating that the NAN IE is a connection capability attribute.

In Example 76, the NAN IE of any one of Examples 60 to 75 may optionally include a length field comprising a value indicating a length of the connection capability bitmap field.

In Example 77, the connection capability bitmap field of any one of Examples 60 to 76 may optionally comprise one or more reserved bits.

Example 78 is a system, comprising a wireless communication apparatus according to any one of Examples 60 to 77, a display, a radio frequency (RF) transceiver, and one or more RF antennas.

Some embodiments may be described using the expression "one embodiment" or "an embodiment" along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment.

Furthermore, in the following description and/or claims, the terms coupled and/or connected, along with their derivatives, may be used. In particular embodiments, connected may be used to indicate that two or more elements are in direct physical and/or electrical contact with each other. Coupled may mean that two or more elements are in direct physical and/or electrical contact. However, coupled may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate and/or interact with each other. For example, "coupled" may mean that two or more elements do not contact each other but are indirectly joined together via another element or intermediate elements.

In addition, the term "and/or" may mean "and," it may mean "or," it may mean "exclusive- or," it may mean "one," it may mean "some, but not all," it may mean "neither," and/or it may mean "both," although the scope of claimed subject matter is not limited in this respect. In the following description and/or claims, the terms "comprise" and "include," along with their derivatives, may be used and are intended as synonyms for each other.

It is emphasized that the Abstract of the Disclosure is provided to allow a reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. In the appended claims, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein," respectively. Moreover, the terms "first," "second," "third," and so forth, are used merely as labels, and are not intended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and/or methodologies, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims.

Claims

CLAIMS What is claimed is:

1. An apparatus, comprising:

a processor circuit;

a communications component for execution by the processor circuit to initiate neighbor awareness networking (NAN) service discovery and to receive a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device; and

a determination component for execution by the processor circuit to determine whether to initiate a connection with the remote device based on the NAN IE.

2. The apparatus of claim 1, the determination component for execution by the processor circuit to determine a connection type for connecting to the remote device based on the connection capability bitmap field when it has determined that a connection is to be initiated with the remote device.

3. The apparatus of claim 1, the connection capability bitmap field comprising a Wi-Fi Direct subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct connection.

4. The apparatus of claim 1 , the connection capability bitmap field comprising a Wi-Fi Direct Services subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct Services connection.

5. The apparatus of claim 1, the connection capability bitmap field comprising a tunneled direct link setup (TDLS) subfield indicating whether the remote device is capable of establishing a TDLS connection.

6. The apparatus of claim 1, the connection capability bitmap field comprising an access point (AP) infrastructure subfield indicating whether the remote device is connected to an

infrastructure AP.

7. The apparatus of claim 6, the AP infrastructure subfield indicating that the remote device is connected to an infrastructure AP, the NAN IE comprising an AP infrastructure information attribute including a field identifying a basic service set identification (BSSID) of an infrastructure AP to which the remote device is connected.

8. The apparatus of claim 1, the connection capability bitmap field comprising a peer-to-peer (P2P) operation subfield indicating whether the remote device is operating as a P2P device.

9. The apparatus of claim 8, the P2P operation subfield indicating that the remote device is operating as a P2P device, the NAN IE comprising a P2P operation information attribute including a field identifying a P2P device address or a P2P group address for the remote device.

10. The apparatus of claim 1, the connection capability bitmap field comprising a cellular service subfield indicating whether the remote device is connected to a cellular service.

11. The apparatus of claim 10, the cellular service subfield indicating that the remote device is connected to a cellular service, the NAN IE comprising a cellular service information attribute including a field identifying a phone number of the remote device.

12. A system, comprising:

an apparatus according to any one of claims 1 to 11;

a display;

a radio frequency (RF) transceiver; and

one or more RF antennas.

13. A method, comprising:

initiating neighbor awareness networking (NAN) service discovery at a wireless device; receiving a NAN information element (IE) during the NAN service discovery, the NAN IE comprising a connection capability bitmap field describing one or more connection capabilities of a remote device; and

determining, by a processor circuit, whether to initiate a connection with the remote device based on the NAN IE.

14. The method of claim 13, comprising determining a connection type for connecting to the remote device based on the connection capability bitmap field when it is determined that a connection is to be initiated with the remote device.

15. The method of claim 13, the connection capability bitmap field comprising a Wi-Fi Direct subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct connection.

16. The method of claim 13, the connection capability bitmap field comprising a Wi-Fi Direct Services subfield indicating whether the remote device is capable of establishing a Wi-Fi Direct Services connection.

17. The method of claim 13, the connection capability bitmap field comprising a tunneled direct link setup (TDLS) subfield indicating whether the remote device is capable of establishing a TDLS connection.

18. The method of claim 13, the connection capability bitmap field comprising an access point (AP) infrastructure subfield indicating whether the remote device is connected to an

infrastructure AP.

19. The method of claim 18, the AP infrastructure subfield indicating that the remote device is connected to an infrastructure AP, the NAN IE comprising an AP infrastructure information attribute including a field identifying a basic service set identification (BSSID) of an

infrastructure AP to which the remote device is connected.

20. The method of claim 13, the connection capability bitmap field comprising a peer-to-peer (P2P) operation subfield indicating whether the remote device is operating as a P2P device.

21. The method of claim 20, the P2P operation subfield indicating that the remote device is operating as a P2P device, the NAN IE comprising a P2P operation information attribute including a field identifying a P2P device address or a P2P group address for the remote device.

22. The method of claim 13, the connection capability bitmap field comprising a cellular service subfield indicating whether the remote device is connected to a cellular service.

23. The method of claim 22, the cellular service subfield indicating that the remote device is connected to a cellular service, the NAN IE comprising a cellular service information attribute including a field identifying a phone number of the remote device.

24. At least one machine-readable medium comprising a plurality of instructions that, in response to being executed on a computing device, cause the computing device to perform a method according to any one of claims 13 to 23.

25. An apparatus, comprising means for performing a method according to any one of claims 13