DE112017007842T5 - DEVICE, SYSTEM AND METHOD FOR THE NEIGHBOR AWARENESS NETWORKING (NAN) -MULTICAST SERVICE GROUP (NMSG) -DISPONATION - Google Patents

Abstract

Some illustrative embodiments include devices, systems, and / or methods for neighbor awareness networking (NAN) multicast service group (NMSG) scheduling. For example, a device may include logic and circuitry configured to cause a NAN device to: Exchange multicast traffic with one or more other NAN devices in an NMSG according to an NMSG multicast schedule from a schedule owner ; Receiving a first schedule update frame containing updated schedule information of an updated NMSG multicast schedule; Determining, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame containing the updated schedule information.

Description

CROSS REFERENCE

This application claims priority from the preliminary U.S. Patent Application No. 62 / 542,367 entitled "APPARATUS, SYSTEM AND METHOD OF FORWARDING A MULTICAST SCHEDULE IN A NEIGHBOR AWARENESS NETWORKING (NAN) MULTICAST SERVICE GROUP (NMSG)", filed on August 8, 2017, the entire disclosure of which is hereby incorporated by reference into the present text.

TECHNICAL AREA

The embodiments described herein generally relate to Neighbor Awareness Networking (NAN) Multicast Service Group (NMSG) scheduling.

BACKGROUND

Neighbor awareness networking, for example according to a Wi-Fi Aware specification, may allow wireless devices, for example Wi-Fi devices, to perform device or service discovery, for example, in their immediate vicinity.

Neighbor Awareness Networking may include clustering, for example a Wi-Fi Aware cluster, for nearby devices. Devices in the same Wi-Fi Aware cluster can be configured to follow the same schedule, for example, a discovery window (DW), for example, to facilitate clustering and / or to achieve low-power operation.

Figure list

• 1 ist eine schematische Blockdiagrammveranschaulichung eines Systems gemäß einigen veranschaulichenden Ausführungsformen.
• 2 ist eine schematische Veranschaulichung einer praktischen Verwendung von Vorrichtungen in einer Neighbor Awareness Networking (NAN) Multicast Service Group (NMSG) gemäß einigen veranschaulichenden Ausführungsformen.
• 3 ist eine schematische Veranschaulichung eines Sequenzdiagramms der Weiterleitung einer Multicast-Zeitplanaktualisierung (Multicast Schedule Update) in einer NMSG gemäß einigen veranschaulichenden Ausführungsformen.
• 4 ist eine schematische Flussdiagrammveranschaulichung eines Verfahrens einer NMSG-Disponierung gemäß einigen veranschaulichenden Ausführungsformen.
• 5 ist eine schematische Veranschaulichung eines Produktes gemäß einigen veranschaulichenden Ausführungsformen.

For the sake of simplicity and clarity of illustration, the elements shown in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be shown enlarged relative to other elements for clarity of illustration. In addition, reference numbers can be repeated between the figures to denote corresponding or analogous elements. The figures are listed below.

• 1 10 is a schematic block diagram illustration of a system according to some illustrative embodiments.
• 2nd 10 is a schematic illustration of practical use of devices in a Neighbor Awareness Networking (NAN) Multicast Service Group (NMSG), according to some illustrative embodiments.
• 3rd 10 is a schematic illustration of a sequence diagram of the forwarding of a multicast schedule update in an NMSG, according to some illustrative embodiments.
• 4th 10 is a schematic flow diagram illustration of a method of NMSG scheduling in accordance with some illustrative embodiments.
• 5 10 is a schematic illustration of a product according to some illustrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, one of ordinary skill in the art will appreciate that some embodiments can be practiced without these specific details. In other instances, well-known methods, procedures, components, units, and / or circuits have not been described in detail so as not to obscure the essential aspects of the discussion.

Discussions in this text that use terms such as "process", "calculate", "calculate", "determine", "create", "analyze", "test" or the like may affect one or more operations and / or one or more processes of a computer, one Obtain a computer platform, computer system, or other electronic computing device that processes and / or transform data presented as physical (e.g., electronic) quantities in the registers and / or memories of the computer to other data, similarly as physical Quantities are displayed in the registers and / or memories of the computer or from another information storage medium that can store instructions for performing operations and / or processes.

The terms “several” and “a plurality of” contain, for example, “several” or “two or more” in the sense of the present text. For example, "multiple items" contain two or more items.

References to “a particular embodiment”, “an embodiment”, “illustrative embodiment”, “various embodiments”, etc. mean that the embodiment (s) thus described include, but not necessarily, a particular feature, structure, or characteristic each embodiment includes the particular feature, structure, or property. Furthermore, the repeated use of the phrase "in a particular embodiment" does not necessarily refer to the same embodiment, although it may.

Unless otherwise stated, the use of the order adjectives "first", "second", "third" etc. to describe a common object in the sense of the present text merely means that different instances of the same objects are meant. It is not meant that the objects described in this way must exist in a specific order, be it in terms of time, space, rank or in any other way.

Some embodiments may be associated with devices and / or networks that comply with existing (WiFi) Alliance (WFA) specifications (including the WiFi Neighbor Awareness Networking (NAN) technical specification, version 1.0, May 1, 2015) and / or future ones Versions and / or derivatives thereof, devices and / or networks operating in accordance with existing WFA Peer-to-Peer (P2P) specifications (WiFi P2P technical specification, version 1.7, July 6, 2016) and / or future versions and / or derivatives thereof, devices and / or networks that operate in accordance with existing IEEE 802.11 standards (including IEEE 802.11-2016 (IEEE 802.11-2016, IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, December 7, 2016) and / or zu future versions and / or derivatives thereof, devices and / or networks that operate in accordance with existing mobile radio specifications and / or protocols, for example 3rd Generation Partnership Project (3GPP) or 3GPP Long Term Evolution (LTE), and / or future versions and / or derivatives thereof work, units and / or devices that are part of the above-mentioned networks, and the like are used.

Some embodiments may be used in conjunction with one-way and / or two-way radio communication systems, cellular radiotelephone communication systems, a cellular phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device that includes a wireless communication device, a mobile or Portable Global Positioning System (GPS) device, a device that contains a GPS receiver or transceiver or chip, a device that contains an RFID element or an RFID chip, a multiple input multiple output (MIMO) - A transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device that has one or more internal antennas and / or external antennas, digital Video broadcast (DVB) devices or systems, multi-standard radio devices or systems, one wired or wireless handheld device such as a smartphone, wireless application protocol (WAP) device, or the like.

Some embodiments may be associated with one or more types of wireless communication signals and / or systems, for example radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), orthogonal frequency division multiple access (OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Multi-User MIMO (MU-MIMO), 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 (GSM) communication, 2G, 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) cellular networks , 3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates for GSM Evolution (EDGE) or the like can be used. Various embodiments may be used in various other devices, systems, and / or networks.

For the purposes of the present text, the term “wireless device” includes, for example, a device which is capable of wireless communication, a communication device which is capable of wireless communication, a communication station which is capable of wireless communication, a portable or non-portable device that is capable of wireless communication, or the like. In some illustrative embodiments, a wireless device may be or include a peripheral device that is integrated into a computer or a peripheral device that connects to a computer. In some illustrative embodiments, the term "wireless device" may optionally include a wireless service.

The term “communicating” in the sense of the present text contains the transmission of the communication signal and / or the reception of the communication signal with reference to a communication signal. For example, a communication unit that may be able to transmit a communication signal may include a transmitter for sending the communication signal to at least one other communication unit and / or a communication receiver for receiving the communication signal from at least one other communication unit. The verb "transmit" can be used to refer to the action of sending or the action of receiving. In one example, the phrase "transmitting a signal" may refer to the action of sending the signal by a first device and need not necessarily include the action of receiving the signal by a second device. In another example, the phrase "transmitting a signal" can refer to the action of receiving the signal by a first device and need not necessarily include the action of sending the signal by a second device.

Some illustrative embodiments can be used in connection with a WLAN, for example a WiFi network. Other embodiments can be used in connection with any other suitable wireless communication network, for example a wireless area network, a "piconet", a WPAN, a WVAN and the like.

For the purposes of the present text, the term "circuits" can refer to, can be part of, or can contain: an application specific integrated circuit (ASIC), an integrated circuit, an electronic circuit, a processor (collectively shared, dedicated, or group), and / or memory (shared, dedicated, or group) executing one or more software or firmware programs, a combinatorial logic circuit, and / or other suitable hardware components that describe the Provide functionality. In some embodiments, the circuitry may be implemented by one or more software or firmware modules, or functions associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, circuitry may include logic that may at least partially run in hardware.

For example, the term “logic” may refer to computational logic embedded in circuitry of a computing device and / or computational logic stored in a memory of a computing device. For example, the logic may be accessible to a processor of the computing device to execute the calculation logic to perform calculation functions and / or operations. In one example, logic may be embedded in different types of memory and / or firmware, for example silicon blocks from different chips and / or processors. Logic may be included in, and / or may be implemented as part of, various circuits, for example radio circuits, receiver circuits, control circuits, transmitter circuits, transceiver circuits, processor circuits and / or the like. In one example, logic may be embedded in volatile memory and / or non-volatile memory, including random access memory, read-only memory, programmable memory, magnetic memory, flash memory, permanent memory and / or the like. Logic can be executed by one or more processors using memory, such as registers, buffers, stacks, and the like, coupled to the one or more processors, as is necessary, for example, to execute the logic.

The term “antenna” in the sense of the present text can contain any suitable configuration, structure and / or arrangement of one (or one) or more antenna elements, components, units, assemblies and / or groupings. In some embodiments, the antenna can implement transmit and receive functions using separate transmit and receive antenna elements. In some embodiments, the antenna can implement transmit and receive functions using shared and / or integrated transmit / receive elements. For example, the antenna may include a phased array antenna, a single element antenna, a set of switched beam antennas, and / or the like.

The term “peer-to-peer (PTP) communication” in the sense of the present text can refer to the communication from device to device (device-to-device) via a wireless connection (“peer-to-peer connection”) relate between devices. PTP communication can be, for example, WiFi Direct (WFD) communication, for example WFD Peer to Peer (P2P) communication, wireless communication via a direct connection within a QoS Basic Service Set (BSS), a tunneled direct Link Setup (TDLS) connection, STA-to-STA communication in an Independent Basic Service Set (IBSS), or the like.

Some illustrative embodiments are described herein with respect to WiFi communication. However, other embodiments can be implemented with respect to any other communication regime, communication network, communication standard and / or communication protocol.

We now turn 1 to which is a schematic block diagram of a system 100 according to some illustrative embodiments.

As in 1 shown the system 100 In some illustrative implementations, include a wireless communication network that includes one or more wireless communication devices and, for example, the wireless communication devices 102 , 140 , 160 and or 180 contains.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 for example a UE, an MD, an STA, an AP, a PC, a desktop computer, a mobile computer, a laptop computer, an Ultrabook ™ computer, a notebook computer, a tablet computer, a server Computers, a hand-held computer, a hand-held device, an Internet of Things (IoT) device, a sensor device, a wearable device, a PDA device, a hand-held PDA device, an on-board device, an off- Board device, a hybrid device (for example, a combination of mobile phone functionalities with PDA device functionalities), a consumer electronic device, a vehicle device, a non-vehicle device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular phone, a PCS device, a PDA device including 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 BluRay disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, an HD DVD recorder, a personal video recorder (PVR), an HD radio receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a radio receiver, a flat screen, a personal media player (PMP), a digital video camera (DVC), one digital audio player, a speaker, an audioe Receivers, an audio amplifier, a game device, a data source, a data sink, a digital photo camera (DSC), a media player, a smartphone, a television, a music player or the like.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 contain one or more STAs, work as such and / or perform their functionality. For example, the device 102 contain at least one STA, and / or the device 140 can contain at least one STA.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 contain one or more WLAN STAs, work as such and / or perform their functionality.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 contain one or more Wi-Fi STAs, work as such and / or perform their functionality.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 contain one or more Bluetooth (BT) devices, work as such and / or perform their functionality.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 contain one or more Neighbor Awareness Networking (NAN) STAs, work as such and / or perform their functionality.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 contain one or more location measurement STAs, work as such and / or perform their functionality.

In one example, a station (STA) can contain a logical entity, which can be an individually addressable instance of a medium access control (MAC) and a physical layer (PHY) interface to the wireless medium (wireless medium, WM). The STA can perform any other additional or alternative functionality.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 contain one or more other devices and / or STAs, work as such and / or perform their functionality.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured so that they work as an access point (AP) -STA and / or perform the functionality of such.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to operate and / or perform the functionality of such as a non-AP STA.

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

In one example, a non-AP STA may include an STA that may not be included in an AP. The non-AP STA can perform any other additional or alternative functionality.

In one example, the device 102 be configured so that it works as an AP-STA and / or takes over its functionality, and / or the device 140 can be configured to work as a non-AP-STA and / or to take over the functionality of a non-AP-STA.

In some illustrative embodiments, the device 102 for example one or more of a processor 191 , an input unit 192 , an output unit 193 , a storage unit 194 and / or a storage unit 195 contain; and / or the devices 140 , 160 and or 180 can, for example, one or more of a processor 181 , an input unit 182 , an output unit 183 , a storage unit 184 and / or a storage unit 185 contain. The devices 102 , 140 , 160 and or 180 can optionally contain other suitable hardware components and / or software components. In some illustrative implementations, some or all of the components of one or more of the devices may be 102 , 140 , 160 and or 180 be enclosed by a common housing or a common encapsulation and can be connected to one another or operatively coupled via one or more wired or wireless connections. In other embodiments, components of one or more of the devices 102 , 140 , 160 and or 180 be distributed over several or separate devices.

In some illustrative embodiments, the processor 191 and / or the processor 181 for example a central processing unit (CPU), a digital signal processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multi-core processor, a microprocessor, a host processor, a controller, several processors or controllers, a chip, one Microchip, one or more circuits, circuits, a logic unit, an integrated circuit (IC), an application-specific IC (ASIC) or any other suitable general-purpose or special-purpose processor or controller. The processor 191 leads instructions for example one Operating system (OS) of the device 102 and / or one or more suitable applications. The processor 181 maintains instructions, for example, of an operating system (OS) of the device 140 and / or one or more suitable applications.

In some illustrative embodiments, the input device 192 and / or the input unit 182 for example, include a keyboard, keypad, mouse, touchscreen, touchpad, trackball, pen, microphone, or other suitable pointing device or input device. The output unit 193 and / or the output unit 183 include, for example, a monitor, a screen, a touch screen, a flat screen, a light emitting diode (LED) display unit, a liquid crystal display (LCD) unit, a plasma display unit, one or more speakers or headphones or other suitable output devices.

In some illustrative embodiments, the storage device 194 and / or the storage unit 184 for example, random access memory (RAM), read only memory (ROM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), flash memory, volatile memory, non-volatile memory, cache memory, a buffer , a short-term storage unit, a long-term storage unit or other suitable storage units. The storage unit 195 and / or the storage unit 185 include, for example, a hard disk drive, a floppy disk drive, a compact disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage devices. The storage unit 194 and / or the storage unit 195 can, for example, store data generated by the device 102 are processed. The storage unit 184 and / or the storage unit 185 can, for example, store data generated by the device 140 are processed.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 be able to share content, data, information and / or signals over a wireless medium (WM) 103 transferred to. In some illustrative embodiments, the wireless medium 103 for example, a radio channel, a cellular channel, a GNSS (Global Navigation Satellite System) channel, an RF channel, a WiFi channel, an IR channel, a Bluetooth (BT) channel and the like.

In some illustrative implementations, the wireless communication medium 103 a wireless communication channel over a 2.4 gigahertz (GHz) frequency band, a 5 GHz frequency band, a millimeter wave (mmWave) frequency band, for example a 60 GHz frequency band, a sub-1 gigahertz (S1G) band and / or contain any other frequency band.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 include one or more radio devices that include circuitry and / or logic to facilitate wireless communication between the devices 102 , 140 , 160 , 180 and / or one or more other wireless communication devices. For example, the device 102 at least one radio device 114 included, and / or the device 140 can have at least one radio device 144 contain.

In some illustrative embodiments, the radio device 114 include one or more wireless receivers (Rx) that include circuitry and / or logic for receiving wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data elements and / or data. For example, radio device 114 at least one recipient 116 included, and / or the radio device 144 can have at least one recipient 146 contain.

In some illustrative embodiments, the radio devices 114 and or 144 include one or more wireless transmitters (Tx) that include circuitry and / or logic for transmitting wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data elements and / or data. For example, the radio device 114 at least one transmitter 118 included, and / or the radio device 144 can have at least one transmitter 148 contain.

In some illustrative embodiments, the radio device 114 and / or the radio device 144 , the transmitter 118 and or 148 and / or the recipients 116 and or 146 Circuits, logic, radio frequency (RF) elements, circuits and / or logic, baseband elements, circuits and / or logic, modulation elements, circuits and / or logic, demodulation elements, circuits and / or logic, amplifiers , Analog-digital and / or digital-analog converter, filters and / or the like included. For example, the radio device 114 and / or the radio device 144 a wireless Network interface card (NIC) and the like included or implemented as part of such.

In some illustrative embodiments, the radio devices 114 and or 144 be configured so that they can communicate via a 2.4 GHz band, a 5 GHz band, a mmWave band, an S1G band and / or any other band.

In some illustrative embodiments, the radio devices 114 and or 144 one or more antennas 107 and or 147 included or assigned to them.

In one example, the device 102 a single antenna 107 contain. In another example, the device 102 two or more antennas 107 contain.

In one example, the device 140 a single antenna 147 contain. In another example, the device 140 two or more antennas 147 contain.

The antennas 107 and or 147 may include any type of antenna suitable for sending and / or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and / or data. For example, the antennas 107 and or 147 include any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. The antennas 107 and or 147 For example, can include antennas suitable for directional radio communication using, for example, beamforming techniques. The antennas 107 and or 147 For example, may include a phased array antenna, a multi-element antenna, a set of switched beam antennas, and / or the like. In some embodiments, the antennas 107 and or 147 Implement transmit and receive functions using separate transmit and receive antenna elements. In some embodiments, the antennas 107 and or 147 Implement transmit and receive functions using shared and / or integrated transmit / receive elements.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 form a Wireless Local Area Network (WLAN) and / or can communicate as part of one.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 form a WiFi network and / or can communicate as part of one.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 form a WiFi Direct (WFD) network and / or can communicate as part of such, for example a WiFi Direct Services (WFDS) network, and / or can operate and / or perform their functionality as one or more WFD devices.

In one example, the wireless communication devices 102 , 140 , 160 and or 180 contain a WiFi Direct device, work as such and / or perform its functionality.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 be able to carry out awareness networking communication, for example according to an awareness protocol, for example a WiFi Aware protocol, and / or any other protocol, as described below, for example.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 be able to form and / or communicate as part of a Neighbor Awareness Networking (NAN) network, for example a WiFi NAN or WiFi Aware network, and / or the functionality of one or more NAN devices (“WiFi Aware Devices”).

Here, some illustrative embodiments are described with respect to one or more NAN devices that communicate as part of a NAN network, such as a NAN cluster. However, the embodiments are not limited to these illustrative embodiments, and other embodiments may be related to any other type of device and / or STAs are implemented which communicate as part of another group, a different service set and / or a different network.

In some illustrative embodiments, the wireless communication medium may 103 a direct connection, for example a PTP connection, for example a WiFi Direct-P2P connection or another PTP connection, for example for a direct communication between the wireless communication devices 102 , 140 , 160 and or 180 to enable.

In some illustrative embodiments, the wireless communication devices 102 , 140 , 160 and or 180 work as WFD-P2P devices and / or perform their functionality. For example, the devices 102 , 140 , 160 and or 180 be able to work as a P2P client device and / or as a P2P Group Owner (GO) device and / or to perform its functionality.

In other embodiments, the wireless communication devices 102 , 140 , 160 and or 180 form and / or communicate as part of another network and / or can perform the functionality of other wireless devices or stations.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 include one or more applications configured to provide, share, and / or use one or more services, for example, a social application, a file sharing application, a media application, and / or the like, for example, at Use of an awareness network, a NAN network ("WiFi Aware network"), a PTP network, a P2P network, a WFD network, or another network.

In some illustrative embodiments, the device 102 an application 125 and / or an application 126 To run. In some illustrative embodiments, the device 140 an application 145 To run.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 be able to share content, data and / or information for example between applications and / or services of the devices 102 , 140 , 160 and or 180 and / or share, show, transmit, transmit, print, output, provide, synchronize and / or exchange one or more other devices.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 include a controller configured to perform one or more operations and / or functionalities of the devices 102 , 140 , 160 and or 180 , for example one or more operations and / or functionalities of communication, for example awareness networking communication, WiFi Aware (NAN) communication and / or any other communication between the devices 102 , 140 , 160 and or 180 and / or other devices and / or any other functionality controls, such as will be described below, for example.

In some illustrative implementations, the device 102 a controller 124 included, and / or the device 140 can be a controller 154 contain. The controller 124 may be configured to perform one or more communications, generate and / or transmit one or more messages and / or transmissions, and / or one or more functionalities, operations, and / or processes between the devices 102 , 140 , 160 , 180 and / or one or more other devices, and / or the device 102 triggers, prompts, instructs and / or controls to do so; and / or the controller 154 may be configured to perform one or more communications, generate and / or transmit one or more messages and / or transmissions, and / or one or more functionalities, operations, and / or processes between the devices 102 , 140 , 160 , 180 and / or one or more other devices, and / or the device 140 triggers, prompts, instructs and / or controls to do such as will be described below, for example.

In some illustrative embodiments, the controllers 124 and or 154 Contain circuits and / or logic, or can be implemented partially or completely by circuits and / or logic, for example one or more processors with circuits and / or logic, memory circuits and / or logic, media access control (MAC) circuits and / or logic, physical layer (PHY) circuits and / or logic, baseband (BB) circuits and / or logic, a BB processor, a BB memory, application processor (AP) circuits and / or - Logic, an AP processor, an AP Memory and / or other circuitry and / or logic that is configured to provide the functionality of the controller 124 and or 154 To run. Additionally or alternatively, one or more functionalities of the controller 124 and or 154 implemented by logic that can be executed by a machine and / or one or more processors, as described below, for example.

In one example, the controller 124 Circuitry and / or logic include, for example, one or more processors with circuitry and / or logic around a wireless device, for example the device 102 , and / or a wireless station, for example one through the device 102 implemented wireless STA to cause, trigger and / or control to perform one or more operations, communications and / or functionalities, such as described herein.

In one example, the controller 154 Circuitry and / or logic include, for example, one or more processors with circuitry and / or logic around a wireless device, for example the device 140 , and / or a wireless station, for example one through the device 140 implemented wireless STA to cause, trigger and / or control to perform one or more operations, communications and / or functionalities, such as described herein.

In some illustrative embodiments, at least part of the functionality of the controller may be 124 as part of one or more elements of the radio device 114 be implemented, and / or at least part of the functionality of the controller 154 can be part of one or more elements of the radio device 144 be implemented.

In other embodiments, the functionality of the controller 124 as part of any other element of the device 102 be implemented, and / or the functionality of the controller 154 can be part of any other element of the device 140 be implemented.

In some illustrative embodiments, the controller may 124 the device can and / or perform one or more operations and / or functionalities of a NAN engine, for example a NAN Discovery Engine (DE) 102 cause to execute, for example, one or more service requests and / or responses, for example, applications and / or services on the devices 102 and or 140 and / or to process one or more other devices.

In some illustrative embodiments, the controller may 154 the device can and / or perform one or more operations and / or functionalities of a NAN engine, for example a NAN Discovery Engine (DE) 140 cause to execute, for example, one or more service requests and / or responses, for example, applications and / or services on the devices 102 and or 140 and / or to process one or more other devices.

In some illustrative embodiments, the device 102 a message processor 128 included that is configured to pass one or more through the device 102 transmitted messages are generated, processed and / or accessed.

In one example, the message processor 128 configured to generate one or more messages generated by the device 102 to be sent, and / or the message processor 128 may be configured to respond to one or more messages through the device 102 received, accessed and / or processed, as described below, for example. In one example, the message processor 128 be configured to send one or more messages from a wireless station, for example one through the device 102 implemented wireless STA, processed; and / or the message processor 128 may be configured to receive one or more messages from a wireless station, for example one from the device 102 implemented wireless STA, processed.

In some illustrative embodiments, the device 140 a message processor 158 included that is configured to pass one or more through the device 140 transmitted messages are generated, processed and / or accessed.

In one example, the message processor 158 configured to generate one or more messages generated by the device 140 to be sent, and / or the message processor 158 may be configured to respond to one or more messages through the device 140 received, accessed and / or processed, as described below, for example. In one example, the message processor 158 be configured to send one or more messages from a wireless station, for example one through the device 140 implemented wireless STA, processed; and / or the message processor 158 may be configured to receive one or more messages from a wireless station, for example one from the device 140 implemented wireless STA, processed.

In some illustrative embodiments, the message processors can 128 and or 158 Contain circuits and / or logic, or can be implemented partially or completely by circuits and / or logic, for example one or more processors with circuits and / or logic, memory circuits and / or logic, media access control (MAC) circuits and / or logic, physical layer (PHY) circuits and / or logic, BB circuits and / or logic, a BB processor, a BB memory, AP circuits and / or logic, an AP processor , an AP memory and / or other circuitry and / or logic configured to support the functionality of the message processors 128 and or 158 To run. Additionally or alternatively, one or more functionalities of the message processors can be used 128 and or 158 implemented by logic that can be executed by a machine and / or one or more processors, as described below, for example.

In some illustrative embodiments, the controllers 124 and or 154 and / or the message processors 128 and or 158 perform one or more operations and / or functionalities of a NAN-MAC, and / or can cause an STA to execute one that can be configured to receive one or more NAN messages, for example NAN beacon frames and / or NAN service Discovery frames (SDFs), generated, processed and / or handled.

In some illustrative embodiments, at least part of the functionality of the message processor may be 128 as part of the radio device 114 be implemented.

In some illustrative embodiments, at least part of the functionality of the message processor may be 128 as part of the controller 124 be implemented.

In other embodiments, the functionality of the message processor 128 as part of every other element of the device 102 be implemented.

In some illustrative embodiments, at least part of the functionality of the controller may be 124 , the radio device 114 and / or the message processor 128 by an integrated circuit, for example a chip, for example a system-on-chip (SoC). In one example, the chip or SoC can be configured to include one or more functionalities of the radio device 114 To run. For example, the chip or SoC can be one or more elements of the controller 124 , one or more elements of the message processor 128 and / or one or more elements of the radio device 114 contain. In one example, the controller 124 , the message processor 128 and the radio device 114 implemented as part of the chip or SoC.

In some illustrative embodiments, at least part of the functionality of the message processor may be 158 as part of the radio device 144 be implemented.

In some illustrative embodiments, at least part of the functionality of the message processor may be 158 as part of the controller 154 be implemented.

In other embodiments, the functionality of the message processor 158 as part of every other element of the device 140 be implemented.

In some illustrative embodiments, at least part of the functionality of the controller may be 154 , the radio device 144 and / or the message processor 158 by an integrated circuit, for example a chip, for example a SoC. In one example, the chip or SoC can be configured to include one or more functionalities of the radio device 144 To run. For example, the chip or SoC can be one or more elements of the controller 154 , one or more elements of the message processor 158 and / or one or more elements of the radio device 144 contain. In one example, the controller 154 , the message processor 158 and the radio device 144 implemented as part of the chip or SoC.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 operate as a device or a station and / or perform its functionality, for example an awareness networking device, a NAN device, a WiFi device, a WiFi Aware device, a WFD device, a WLAN device, a low Power Long Range (LPLR) device, and / or any other device capable of recognizing other devices according to a detection protocol and / or regime.

In some illustrative embodiments, the radio devices 114 and or 144 over the wireless communication medium 103 communicate in accordance with an awareness networking regime, for example a recognition regime, for example a WiFi Aware recognition regime (“NAN recognition regime”), and / or another awareness networking and / or recognition regime, as described below, for example.

In some illustrative embodiments, the awareness networking regime, such as NAN, may allow applications to discover services in their immediate vicinity. For example, NAN technology can be a low power service detection that can be scaled efficiently, for example, in dense Wi-Fi environments.

In some illustrative embodiments, a device, for example one or more of the wireless communication devices 102 , 140 , 160 and or 180 , contain one or more blocks and / or units to perform a network awareness functionality. For example, one device, for example one or more of the devices 102 , 140 , 160 and or 180 , perform the functionality of a NAN device, which may include a NAN-MAC and / or a Discovery Engine (DE). In one example, the controllers 124 and or 154 and / or the message processors 128 and or 158 configured to run the functionality of the Discovery Engine and / or the message processors 128 and or 158 and / or the controller 124 and or 154 can be configured to perform the functionality of the NAN-MAC, as described above, for example. In another example, the functionality of the NAN-MAC and / or the discovery engine can be performed by any other element and / or any other entity of the devices 102 , 140 , 160 and or 180 be carried out.

In some illustrative embodiments, the awareness networking regime may include a recognition regime or protocol, such as described below, for example.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 perform a recognition process according to the awareness networking regime, for example to recognize each other and / or to establish a wireless communication connection, for example a directional and / or high-throughput wireless communication connection and / or any other connection.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 be configured to have time synchronization between the devices 102 , 140 , 160 , 180 and / or enable one or more other devices that, for example, perform the functionality of STAs, for example Wi-Fi stations, so that, for example, STAs can recognize one another more efficiently and / or more quickly.

Some illustrative embodiments relating to a NAN detection regime and NAN detection frames of the NAN detection regime are described below. In other embodiments, however, any other recognition regime and / or any other recognition frames can be used.

In some illustrative embodiments, the detection regime may include multiple conflict-based detection windows (Discovery Windows, DWs).

In some illustrative embodiments, communication during DWs may be configured to time-sync between STAs, for example Wi-Fi stations, for example devices 102 , 140 , 160 and or 180 , is enabled so that the STAs can find each other more efficiently during a DW.

In some illustrative embodiments, devices of an awareness network, for example a NAN network, may form one or more clusters to provide services, for example publish and / or subscribe. A NAN cluster can be defined by an anchor master (AM) (also known as a “NAN master device” or “anchor device”). In one example, the AM may include a NAN device that ranks highest in the NAN cluster.

In some illustrative embodiments, the NAN data exchange may be reflected by discovery frames, for example publish, subscribe and / or follow-up service discovery frames (SDF). These frames may include action frames that can be sent by a device that wants to publish a service or application and / or subscribe to a published service or application at the other end.

In one example, one of the devices 102 , 140 , 160 and or 180 , for example the device 102 , work as AM and / or perform its functionality. The AM can be configured to send one or more beacon signals. Another of the devices 102 , 140 , 160 and or 180 , for example the device 140 , can be configured to receive and process the beacon signals.

In one example, the devices 102 , 140 , 160 and or 180 operate as NAN devices and / or execute their functionality, which belong, for example, to a NAN cluster that has a common set of NAN parameters, including, for example, a common NAN time stamp, and / or a common period between successive detection windows (DWs ) can share. The NAN timestamp can be transmitted, for example, as part of a NAN directional frame that can be transmitted in the NAN cluster. In one example, the NAN timestamp may include a Time Synchronization Function (TSF) value, for example a cluster TSF value, or any other value.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 be configured so that they recognize each other via a predefined communication channel (“the social channel”). In one example, channel 6 in the 2.4 GHz band can be defined as a social NAN channel. Any other additional or alternative channel can also be used as a social channel.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 Recognition frames, for example SDFs, broadcast during the multiple DWs, for example over the social channel and / or any other channel that can be used for recognition. For example, the NAN-AM can display the time of the DW while the NAN devices can exchange SDFs.

In one example, the devices 102 , 140 , 160 and or 180 send the recognition frames to recognize each other, for example to enable the use of the one or more services provided by the applications 125 , 126 and or 145 to be provided.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 communicate during a DW according to a competitive mechanism. For example, the devices 102 , 140 , 160 and or 180 Before trying to send a detection frame during the search window, check if a channel is free or not.

In some illustrative embodiments, a device of the devices 102 , 140 , 160 and or 180 , for example the device 102 , the detection frame may not send during DW, for example if the channel is busy. For example, in some illustrative embodiments, the device 102 send the detection frame during DW, for example when the channel is free.

In some embodiments, the detection frame can be sent as a group-addressed, e.g., broadcast or multicast, detection frame. In other embodiments, the recognition frame can be sent as any other type of frame.

In some illustrative embodiments, the recognition frame need not require an acknowledgment frame. According to these embodiments, a transmitter of the recognition frame must not postpone transmission of the recognition frame.

In some illustrative embodiments, this can be done by the device 102 Detection frame sent during the DW may be configured to allow other devices or services running on other devices to use the services in the device 102 to recognize.

In some illustrative embodiments, devices of the system 100 Use availability information, for example in the form of an availability interval bitmap and / or further availability map, to use it, for example, of a device of the devices 102 , 140 , 160 and or 180 allow to display their availability, for example, with respect to at least one channel and one or more time slots during which the device is available, for example active ("awake"), for example to carry out NAN connection activities.

In one example, the availability information may be communicated as part of an availability attribute that includes, for example, a 32-bit bitmap for 32 time slots, where each time slot can be 16 milliseconds (ms) long. For example, each non-zero bit may represent a time slot during which a device that sends the availability attribute should be awake and available to send and / or receive data in a particular method. In another example, the availability information can contain all other additional or alternative information and / or can be transmitted and / or formatted in any other way.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 Be part of an awareness cluster, such as a NAN cluster.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 form the NAN cluster.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to communicate according to a Wi-Fi Aware specification and / or other awareness networking specification, which may be configured so that a group of devices other devices or services nearby and / or in the immediate vicinity , for example with low power.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 form the NAN cluster and synchronize to the same clock as described, for example, above.

In one example, all devices of the NAN cluster can converge on a time period and channel, for example one or more DWs, to identify services of the devices 102 , 140 , 160 and or 180 to enable and / or to achieve low power consumption, as described above, for example.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 Configured to use NAN as energy efficient and / or scalable peer-to-peer technology, for example to enable Wi-Fi devices to recognize devices and / or services in their immediate vicinity and / or establish one or more data paths with one or more peer devices.

For example, the devices 102 , 140 , 160 and or 180 configured to form a NAN cluster for nearby devices, and devices in the same NAN cluster can follow the same wake schedule, for example the same DWs, to enable clustering and / or low performance operation achieve, as described above, for example.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 Send NAN service discovery frames, for example during DWs, to publish, for example, services in which the devices are interested or offered by and / or to subscribe to one or more published services, such as above has been described.

In some illustrative embodiments, two or more NAN devices can establish a NAN data path (NDP), for example, via a NAN data link (NDL) between the two NAN devices, which allows packets to be interposed between them the two Send NAN devices. For example, the two or more NAN devices can set up the NDL and / or the NDP when a desired service is detected.

In some illustrative embodiments, two or more devices, for example two or more of the devices 102 , 140 , 160 and or 180 want to communicate with each other. The two or more devices can establish a service data session (SDS) during which the two devices can establish an NDP and / or an NDL, for example to support these SDS or multiple SDS.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to perform one or more operations of a flow, for example a data path setup flow, for setting up a NAN service, for example a unicast or multicast service.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 be configured to perform one or more operations of a flow, for example an NDP negation flow, for example to set up a service, for example for data transmission between two NAN devices, for example NAN2 devices, for example between the Devices 102 and 140 to enable.

In some illustrative embodiments, simultaneous multi-user (MU) communication may, for example, according to an IEEE 802.11ax specification, for example, in a time domain and / or frequency domain, for example for downlink (DL) and uplink (UL) transmissions be carried out.

In some illustrative embodiments, an AP may be configured to enable MU communication for, for example, downlink (DL) and uplink (UL) transmissions. For example, a downlink MU transmission may include an MU transmission from the AP to multiple stations (STAs), and / or an uplink MU transmission may include an MU transmission from the multiple STAs to the AP.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to communicate multicast traffic, for example, between devices within a NAN Multicast Service Group (NMSG), as described below, for example.

In one example, two or more of the devices 102 , 140 , 160 and or 180 belong to the NMSG, as described below, for example.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to perform many-to-many multicast data communication, for example, between devices within an NMSG, for example, according to a NAN specification, for example a future WiFi Aware NAN 2.0 specification and / or another specification or another Protocol, support.

In some illustrative embodiments, the NMSG may include a many-to-many NMSG, as described below, for example.

In some illustrative embodiments, the NMSG may include a group formed by one or more NAN devices for a multicast service instance. For example, the NMSG devices may communicate according to an NMSG schedule, which may include, for example, a set of resource blocks used by an NMSG for data communication.

For example, in some illustrative embodiments, a multicast source device (also referred to as an “originator”) may start a new NMSG. For example, one or more other multicast devices can join this group and send their own multicast packets.

In one example, a NAN device of the devices 102 , 140 , 160 and or 180 , for example the device 140 , start a new NMSG and can take on the role of the NMSG originator.

For example, in some illustrative embodiments, a schedule responsibility device may be responsible for maintaining an NMSG schedule.

For example, a NAN device of the devices 102 , 140 , 160 and or 180 , for example the device 140 , take on the role of the schedule responsibility device and / or can be configured to maintain the NMSG schedule.

In one example, the originator, for example the device 140 , the first schedule responsibility device.

For example, in some illustrative embodiments, in some cases, when the originator leaves the NMSG, another device may take on the role of schedule manager. For example, the schedule manager can be configured to change a current schedule to a new or updated schedule.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to perform one or more operations, one or more functionalities, and / or a role of a NAN multicast device in the NMSG, such as the originator device, a registration device, a registration device, the schedule owner, and / or another Role.

For example, in some illustrative embodiments, a schedule followed in an NMSG may need to be updated, for example occasionally, as described below.

For example, in some illustrative embodiments, an NMSG originator may transmit the NMSG multicast schedule to NMSG registrants, for example during NMSG registrations.

For example, in some illustrative embodiments, the NMSG originator may update the NMSG multicast schedule, as described below, for example.

In some illustrative embodiments, an NMSG schedule update may occur after a NAN device, for example the device 102 , has requested a change of schedule and a schedule owner, for example the device 140 that accepted schedule change request.

In some illustrative embodiments, the NMSG schedule update may occur after the schedule owner updates the schedule himself.

In other embodiments, the NMSG schedule may be updated based on any other suitable operation, communication, and / or other suitable criteria.

In some illustrative embodiments, it may be technically advantageous if there is a possibility that some, most or even all of the devices in the NMSG will follow the new schedule, for example so that they can continue to hear each other and send communications.

In some illustrative embodiments, it may be a schedule owner, for example the device 140 , be allowed to update an NMSG schedule by sending a frame, for example a NAN action frame (NAF) or any other frame that contains, for example, at least one new schedule and for example a time, on which the person responsible for the schedule switches to the new schedule.

In some illustrative embodiments, the schedule owner may send the new schedule, for example the NAF that contains the updated schedule, multiple times to ensure, for example, that all devices within range will correctly receive the new schedule.

In some illustrative implementations, in some use cases, scenarios, and / or uses, it may be necessary to resolve a technical problem related to the forwarding of an updated NMSG schedule to devices in the NMSG, as described below, for example.

For example, it may be sufficient to require a schedule manager to send the updated NMSG schedule, for example, assuming a network and / or use, where all devices in the NMSG can hear each other. On the other hand, it may not be enough to have the schedule owner send the updated NMSG schedule, for example, in some networks and / or uses, for example, if some devices in an NMSG cannot hear one or more other devices in the NMSG.

In one example, multi-hop many-to-many NMSG networks can be formed in some cases. Accordingly, for example, in a multi-hop many-to-many NMSG, a situation may arise where some devices do not hear the schedule owner, such as with reference to FIG 2nd is still described.

We turn 2nd to, which schematically use 200 Devices illustrated in an NMSG according to some illustrative embodiments.

As in 2nd shown, the NMSG may include, for example, a many-to-many NMSG.

As in 2nd shown are some devices of the NMSG, for example at least the device " C. ", May not be able to use an NMSG originator, for example the device" A ", to listen.

For example, as in 2nd shown the device C. out of range 210 the originator or schedule owner A lie.

If in such networks, for example, the person responsible for the schedule, for example the device A , the schedule is updated so devices can be out of range, for example the device C. , may not follow the new schedule. As a result, the NMSG can disintegrate, resulting in an interruption in service.

In some illustrative embodiments, one or more devices may be in a many-to-many NMSG, for example device E and / or device D in the many-to-many NMSG from 2nd , configured to work as a "registrar" (enroller), the schedules from the schedule owner, for example the device A forward only when new devices are registered.

In some illustrative embodiments, one or more devices of the network of 2nd configured to support forwarding the NMSG schedule updates to NMSG devices, for example, according to a forwarding regime, as will be described below.

In some illustrative embodiments, there may be a technical problem in forwarding the updated schedule, for example when the schedule owner, for example the device A , updated a schedule and existing registries, for example the device C. , the new schedule may not get, for example, if the registrants are out of reach 210 the device A lie.

According to a solution for forwarding the schedule update, a device, for example the device B that hears a schedule update from any higher master ranked device, resend an NAF that contains the same schedule update information.

In one example, for example for the purpose of limiting the number of such transmissions, a device may refrain from sending this NAF, for example, if the device receiving the schedule update, for example the device B , another device with a higher master rank, a higher rank or a higher hop count belonged to the person in charge of the schedule who sent this NAF and the received signal strength of the transmitter is above a certain threshold. In some use cases, scenarios and / or implementations, however, this solution may not be efficient, for example, to reliably distribute the schedule to all devices in the NMSG, for example, if no rank or jump count information is included in the schedule update NAF frame .

We are returning 1 back. In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to forward an updated NMSG multicast schedule, for example, according to a forwarding regime that, for example, allows the updated NMSG multicast schedule to be "flooded" by a schedule officer, as described below, for example.

In some illustrative embodiments, a NAN device, for example the device 102 receiving the updated NMSG multicast schedule may be configured to select, for example, based on one or more forwarding criteria, whether or not to forward the schedule update, as described below, for example.

In some illustrative embodiments, a NAN device, for example the device 102 receiving a schedule from a neighboring NAN device in an NMSG may be configured to decide not to resend that schedule, for example, if it is not a new schedule, for example to control administrative data (Overhead) with flooding, as described below, for example.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 be configured to forward the updated NMSG multicast schedule according to a forwarding regime that may, for example, be configured to efficiently forward the updated NMSG multicast schedule, for example, even if in a NAF that contains a schedule update frame, there is no jump count or rank information, as described below, for example.

In some illustrative embodiments, some or all of the devices in an NMSG may forward updated NMSG multicast schedules from a schedule owner, for example, by selectively sending an NAF that contains the same schedule information as that from another device in the NMSG, including, for example, the Those responsible for the schedule, as described below, for example.

In some illustrative embodiments, the devices 102 , 140 , 160 and or 180 configured to deliver multicast traffic as part of an NMSG, for example, according to an NMSG multicast schedule from a schedule owner, as described below, for example.

For example, in some illustrative embodiments, the device 102 configured to transmit multicast traffic with one or more other NAN devices in an NMSG, as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, initiates and / or triggers multicast traffic with one or more other NAN devices in the NMSG, for example according to an NMSG multicast schedule, from a schedule manager. In one example, the device 102 Multicast traffic with one or more NAN devices 140 , 160 and or 180 for example according to an NMSG multicast schedule from the device 140 to transfer.

In some illustrative embodiments, a NAN device may be the NMSG, for example the device 102 , configured to process a frame, for example an NAF or any other frame that contains updated schedule information of an updated NMSG multicast schedule of the NMSG.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, causes, and / or triggers to receive a first schedule update frame that contains updated schedule information of an updated NMSG multicast schedule, as described below, for example.

In some illustrative embodiments, the updated schedule information may include a multicast schedule change attribute and a NAN availability attribute, as described below, for example. In other embodiments, the updated schedule information may include any other additional or alternative attributes, elements and / or information.

In some illustrative embodiments, an NMSG originator of an NMSG, for example a one-to-many NMSG or a many-to-many NMSG, may be defined as the schedule manager of the NMSG.

In some illustrative embodiments, it may be the NMSG originator, for example the device 140 , may be allowed to update the NMSG multicast schedule, as described below, for example.

For example, in some illustrative embodiments, an NMSG schedule manager, for example the device 140 update the NMSG multicast schedule, for example, by sending a NAN schedule update notification frame that includes a multicast schedule change attribute and a NAN availability attribute that specify a new NMSG multicast schedule, such as will be described below.

In some illustrative embodiments, the schedule update notification frame may be sent as either a unicast frame or a multicast frame, as described below, for example.

For example, in some illustrative embodiments, all NMSG member devices that receive the updated NMSG multicast schedule should begin using the new schedule for multicast-related operations.

In some illustrative embodiments, for example, if the originator of the many-to-many NMSG drops out, the multicast schedule of the NMSG should remain unchanged.

In some illustrative embodiments, the updated schedule information may include an indication of when to transition to the updated NMSG multicast schedule, as described below, for example.

In some illustrative embodiments, the first schedule update frame may include an NAF. In other embodiments, the first schedule update frame may include any other type of frame, message, or transmission.

In some illustrative embodiments, the first schedule update frame may come from the schedule owner, as described below, for example. For example, the device 102 the first schedule update frame from the device 140 receive.

In some illustrative embodiments, the first schedule update frame may come from an originator of the NMSG, as described below, for example. For example, the device 102 the first schedule update frame from the device 140 receive.

In some illustrative embodiments, the first schedule update frame may come from another NAN device that is not the schedule owner, as described below, for example. For example, the device 102 the first schedule update frame from the device 180 receive.

In some illustrative embodiments, the first schedule update frame may include a multicast frame to the NMSG, as described below, for example. For example, a transmitter of the first schedule update frame, for example the device 140 , the device 160 or the device 180 send a multicast transmission including the first schedule update frame to the NMSG, and the device 102 can receive the first schedule update frame in the multicast transmission.

In some illustrative embodiments, the first schedule update frame may be a unicast frame to the NAN device 102 contain. For example, the device 140 , the device 160 or the device 180 a unicast transmission of the first schedule update frame to the device 102 send.

In some illustrative embodiments, a NAN device may be the NMSG, for example the device 102 , the device 140 , the device 160 and / or the device 180 , for this configured to determine whether or not the updated schedule information of the updated NMSG multicast schedule of the NMSG is forwarded based on one or more NMSG schedule forwarding criteria in the NMSG, as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to drive the device 102 controls, initiates and / or triggers, for example, to determine, based on at least one forwarding criterion, whether or not the updated schedule information should be forwarded, as will be described below, for example.

In some illustrative embodiments, a NAN device of the NMSG that receives the updated schedule information (also referred to as the "relay device") may, for example, the device 102 , the device 140 , the device 160 and / or the device 180 configured to, if, at the moment, and / or based on that, it is determined that the updated schedule information of the updated NMSG multicast schedule should be forwarded to the NMSG in the NMSG, a frame, for example, to send an NAF or other frame that contains the updated schedule information of the updated schedule of the NMSG (also referred to as the "schedule update"), as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, causes and / or triggers to send a second schedule update frame containing the updated schedule information contained in, for example, the first schedule update frame, for example as soon as, if, at the moment, where, and / or based on that it is determined that the updated schedule information is to be forwarded, as described below, for example.

In some illustrative embodiments, the second schedule update frame may include an NAF. In other embodiments, the second schedule update frame may include any other frame.

In some illustrative embodiments, the second schedule update frame may include a multicast frame to the NMSG. For example, the device 102 multicast the second schedule update frame to the NMSG.

In some illustrative embodiments, the relaying NAN device may be configured to determine whether, for example, the relaying NAN device has previously received the same schedule information of the updated NMSG multicast schedule from the same schedule manager updated NMSG multicast schedules should or should not be forwarded in the NMSG, as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, prompts and / or triggers to decide not to forward the updated schedule information, for example, if the updated schedule information is the same as the updated schedule information previously received from the schedule owner. The device 102 For example, may decide that the updated schedule information is not forwarded if, for example, the updated schedule information is the same as before from the device 140 received updated schedule information.

In some illustrative embodiments, one or more NMSG schedule forwarding criteria may be configured to allow only a subset of devices in the NMSG to forward the updated schedule information, as described below, for example.

For example, in some illustrative embodiments, only a subset of devices need to be allowed and / or required in the NMSG to pass the updated schedule information.

In some illustrative embodiments, the at least one forwarding criterion may relate to whether the NAN device that has received the updated schedule is a registrar (enroller) or a registrant (enrollee), as described below, for example.

In some illustrative embodiments, only registrars need to forward the updated schedule information.

In some illustrative embodiments, all registrants can forward the updated schedule information.

In some illustrative embodiments, only some registrars need to forward the updated schedule information, for example, all registrants who have previously registered a device with the NMSG. The set of such registries can be decided by the schedule manager, for example, or determined locally by each registrar.

In some illustrative embodiments, all registrants may forward the updated schedule information and / or only some registrants need to forward the updated schedule information.

In some illustrative embodiments, for example, in a many-to-many NMSG, registrants are to forward each new schedule from the schedule owner. For example, a registrar may be required to forward, for example, always forward, each new schedule from the schedule owner.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, prompts and / or triggers to determine that the updated schedule information should be forwarded, for example, when the device 102 is a registrar of the NMSG.

In some illustrative embodiments, registrants can forward any new schedule from the schedule owner. For example, registrants can be allowed to choose whether or not to forward a new schedule from the schedule owner.

In some illustrative embodiments, the controller may 124 be configured to it the device 102 to allow to determine, for example, to choose whether to determine or not to determine that the updated schedule information is to be forwarded, for example when the device 102 is a registered member of the NMSG.

In some illustrative embodiments, the at least one relay criteria may relate to whether the relaying NAN device, for example the device 102 , 140 , 160 and or 180 , is a multicast source, as described below, for example.

In some illustrative embodiments, only multicast sources need to forward the updated schedule information.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, prompts and / or triggers to determine that the updated schedule information should be forwarded, for example, when the device 102 is a multicast source.

In some illustrative embodiments, the routing criteria may include a criterion that defines that only devices with higher battery power or other system parameters are allowed to route the updated schedule information.

In some embodiments, the routing criteria may be defined based on some or all of the criteria and / or parameters listed above, and / or additional or alternative criteria and / or parameters may be used.

In some illustrative embodiments, the relay device, for example the device 102 , configured to retransmit the updated schedule information multiple times, for example, to ensure that its neighbors receive the updated schedule information correctly.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, causes and / or triggers to retransmit the second schedule update frame several times, for example to ensure that one or more other devices of the NMSG, for example the devices 140 , 160 and or 180 that received the updated schedule information correctly.

In some illustrative embodiments, the forwarded updated schedule information in the schedule update may be the same as that sent by the schedule owner.

In some illustrative embodiments, a NAN device may be the NMSG, for example the device 102 , the device 140 , the device 160 and / or the device 180 , configured to determine, for example, at least based on whether the NAN device previously received the same schedule update from the same schedule manager, whether or not to receive a received schedule update.

In one example, a NAN device should not forward a received schedule update, for example, for the purpose of limiting the administrative data overhead of forwarding schedule updates, if, for example, the NAN device concludes that it is previously responsible for the same schedule update from the same schedule manager had received.

In some illustrative embodiments, the NAN device may be configured to determine, for example, based on one or more parameters and / or criteria, whether the NAN device previously received the same schedule update from the same schedule manager, such as below is described.

In some illustrative embodiments, the NAN device may be configured to determine, for example, by comparing one or more of the following parameters whether the NAN device has previously received the same schedule update from the same schedule manager: Common Resource Blocks (CRBs) ) the NMSG multicast schedule in the received schedule update, a corresponding transition time TSF and schedule manager information, and / or a sequence identifier (ID) associated with the schedule update.

In other embodiments, some or all of these parameters and / or other additional or alternative parameters may be implemented.

In some illustrative embodiments, the device may conclude that the received updated schedule information is the same that it currently has stored for the NMSG, for example, if all or some of these parameters match their corresponding values that the device is currently for has saved this NMSG.

In some illustrative embodiments, the device may conclude that the received updated schedule information is a new schedule and may resend the received updated schedule information.

In some illustrative embodiments, a NAN device, for example the device 102 , the device 140 , the device 160 and / or the device 180 , configured to use a sequence ID to determine whether or not to forward the updated schedule information, as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, initiates, and / or triggers based on a sequence ID in the first schedule update frame to determine whether or not to update the updated schedule information, as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, causes, and / or triggers to determine that the updated schedule information should be forwarded, for example, if the sequence ID in the first schedule update frame is greater than a stored sequence ID that corresponds to the NMSG, such as below is still described.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, initiates and / or triggers to determine that the updated Schedule information should not be forwarded, for example, if the sequence ID in the first schedule update frame is not greater than the stored sequence ID that corresponds to the NMSG, as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, causes, and / or triggers to update the stored sequence ID corresponding to the NMSG so that the sequence ID is included in the first schedule update frame, as described below, for example.

In some illustrative embodiments, a device, for example the device 102 For example, upon receipt of a schedule update notification frame, determine that the schedule contained in the schedule update notification frame is new, for example, if the sequence ID in the received NAN availability attribute is greater than that which the device is currently serving for it NMSG has saved. For example, in this case the device can record this sequence ID and can forward the schedule, for example, by sending a schedule update notification frame containing the received multicast schedule change attribute and the NAN availability attribute, such as below is still described.

In some illustrative embodiments, the NAN device may be configured to determine whether the NAN device previously does so, for example, by comparing one or more other additional or alternative fields and / or attributes in a received NAF that includes the schedule update received the same schedule update from the same schedule manager. These fields or attributes can be new and / or already existing.

In some illustrative embodiments, one or more additional or alternative routing criteria may be defined, for example, to reduce and / or limit the administrative data overhead for routing schedule updates, as described below, for example.

In some illustrative embodiments, a NAN device of the devices 102 , 140 , 160 and or 180 , for example the device 102 , configured to determine, for example, based on a proximity criterion, whether or not the updated schedule information should be forwarded, as will be described below, for example.

In one example, a NAN device may be the NMSG, for example the device 102 , the device 140 , the device 160 and / or the device 180 , configured to decide not to forward a received schedule, for example when the NAN device is close to the device that is sending the schedule updates, as described below, for example.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, initiates and / or triggers based on a proximity criterion that is close to the device 102 and a device from which the updated schedule information is sent corresponds to determine whether or not the updated schedule information should be forwarded.

In one example, the device 102 configured to determine, for example, based on a received signal strength indicator (RSSI) that corresponds to the first schedule update frame, whether the device is 102 is close to the device from which the updated schedule information is sent,

In another example, the device 102 configured to determine whether the device is based on other other additional or alternative parameters and / or measurements, such as one or more range or location estimates 102 is close to the device from which the updated schedule information is sent.

In some illustrative embodiments, NAN devices, for example the device 102 , the device 140 , the device 160 and / or the device 180 , configured to allow schedule change requests, but for example, not to allow a new schedule manager selection in the NMSG, for example to limit schedule updates in the NMSG, as described below, for example.

In some illustrative embodiments, one or more criteria for enabling schedule change requests can be configured, for example to offer a technical solution that allows, for example, the number of schedule change requests in the NMSG and thus the number of possible schedule updates to be limited.

In some illustrative embodiments, configuration support and / or ability to enable schedule change requests may be advertised in one or more publication messages and / or other NAN frames, for example during data path setup, for example using existing or new fields and / or Attributes. In other embodiments, this configuration need not be advertised at all.

In some illustrative embodiments, the configuration that enables the schedule change requests may be displayed using, for example, one or more reserved bits in, for example, a service descriptor extension attribute (SDEA) control panel in publication frames.

In some illustrative embodiments, the configuration that enables the schedule change requests may be displayed using, for example, one or more reserved bits in, for example, a control panel in an NMSG attribute.

In one example, according to this regime, a NAN device is needed, for example a NAN device of the devices 102 , 140 , 160 and or 180 To send schedule change requests only to the originator. For example, even if the schedule change requests are not confirmed, the NAN device does not need to initiate a new schedule manager selection. This regime can effectively mean that only the originator can update schedules and only devices within range of the originator can successfully change the NMSG's schedule.

In some illustrative embodiments, a NAN device of the devices 102 , 140 , 160 and or 180 , for example the device 102 , configured to send a schedule request to the schedule owner with a requested schedule change, as described below, for example. For example, the device 102 configured to make a schedule request with a requested schedule change to the device 140 sends.

In some illustrative embodiments, the controller may 124 be configured to use the device 102 controls, initiates, and / or triggers to send a unicast schedule request to the schedule owner with a requested schedule change and to receive the first schedule update frame from the schedule owner in response to the schedule request.

In some illustrative embodiments, the first schedule update frame may include a display panel to indicate whether the requested schedule change is accepted or rejected, as described below, for example.

In some illustrative embodiments, a NAN device, for example the devices 102 , 140 , 160 and or 180 , configured to include one or more attributes in information content for schedule frames used for the NMSG schedule update operation, for example, based on one or more definitions and / or criteria, for example as follows are: Table 1 Attributes Schedule request Schedule response Schedule update notification MSCA response status A R Ability of the device O O O O NAN availability M M O M Multicast schedule change M M M M Element container O O O O Misaligned schedule O O O O

For example, according to Table 1, one or more attributes can be optional (Optional, O), while one or more other attributes can be mandatory (Mandatory, M).

In one example, Table 1 may require that a schedule request include a NAN availability attribute and a multicast schedule change attribute, for example, while one or more other attributes For example, a device capability attribute, an element container attribute, and / or an unaligned schedule attribute may be optional.

In another example, according to Table 1, one or more attributes of a schedule response can be based on whether the schedule response contains an indication (status) of accepted (accepted, A) or rejected (rejected, r) or not.

For example, as shown in Table 1, the schedule response that contains an accepted status may require, for example, a NAN availability attribute and a multicast schedule change attribute, while one or more other attributes, for example a device capability, Attribute, an element container attribute and / or a schedule misalignment attribute, may be optional.

For example, as shown in Table 1, the schedule response that contains a denied status may include, for example, a multicast schedule change attribute, while one or more other attributes, such as a NAN availability attribute, include a device capability Attribute, an element container attribute and / or a schedule misalignment attribute, may be optional.

In another example, Table 1 may require that a schedule update notification include a NAN availability attribute and a multicast schedule change attribute, while one or more other attributes, for example a device capability attribute, include one Element container attribute and / or a schedule misalignment attribute, may be optional.

In other embodiments, the content of one or more messages and / or frames need only be defined based on some of the criteria of Table 1 and / or other additional or alternative criteria.

In some illustrative embodiments, the Multicast Schedule Change Attribute (MSCA) format may be configured to include one or more fields, for example: Table 2 field Size (octets) value description Attribute ID 1 0x25 Identifies the type of the NAN attribute length 2nd variable Length of the following fields in the attribute NMSG ID 8th variable NMSG ID if an NMSG Schedule change time 8th variable TSF the time for the schedule change MSCA control 2nd variable See table 3 Reason code 1 variable Identifies the reason when the response flag in the MSCA control panel is set to 1 and the accept / reject flag is set to 0. This field is reserved if these flags are set to other values. Multicast schedule change entry list variable variable One or more multicast schedule change entries

For example, in some illustrative embodiments, the MSCA control panel may be defined in an example as follows: Table 3 Number of bits information Remarks 1 Accept / reject flag Set to 1 if schedule change is accepted, otherwise 0 1 Requirement Request flag (set to 1 if it is a request, otherwise 0) 1 answer Reply flag (1 if there is an answer, 0 otherwise) 5 Reserved Reserved for future use

In other embodiments, the MSCA control field can be defined to include other fields and / or information.

In some illustrative embodiments, a schedule owner may, in one example, update a schedule by, for example, creating a schedule update notification frame with a multicast schedule change attribute, in which the request field and the response field, for example, both in his MSCA control field 0 and a corresponding NAN availability attribute, in which the multicast schedule change attribute changed subfield in the attribute control field is set to 1, and indicates the updated schedule.

For example, the device 140 assume a role of the schedule manager and can update a schedule of the NMSG by, for example, a schedule update notification frame with a multicast schedule change attribute, for example according to Table 2, in which the request field and the response field, for example in the MSCA Control field according to Table 3 are both set to 0 and a corresponding NAN availability attribute, in which the multicast schedule change attribute changed subfield in the attribute control field is set to 1, and indicates the updated schedule.

In some illustrative embodiments, the multicast schedule change attribute may also indicate a time when the schedule owner switches to the new schedule, for example in the schedule change time field of Table 2.

In other embodiments, the schedule update notification frame may include one or more other fields and / or values to indicate the schedule update.

In some illustrative embodiments, there may be devices in an NMSG, for example the devices 102 , 140 and or 180 may be allowed to request a change in the schedule of the NMSG by, for example, a unicast schedule request frame containing a multicast schedule change attribute to the schedule owner, e.g. the device 140 , is sent. For example, the multicast schedule change attribute may include the request flag set to one (1) and the requested schedule, for example, as shown in Table 2.

In some illustrative embodiments, the schedule owner, for example, if the schedule owner, for example, the device 140 that accepts schedule request, send a schedule response frame that contains a multicast schedule change attribute, with a response flag set to one (1) and an accept / reject flag set to one (1), and can use a method to update the NMSG schedule, such as described above.

In some illustrative embodiments, the schedule owner, for example, if the schedule owner, for example, the device 140 that rejects schedule request, can send a schedule response frame that contains a multicast schedule change attribute, with a response flag set to one (1) and an accept / reject flag set to zero (0) specify a reason in the reason code field.

In one example, a multicast schedule change attribute format may include one or more fields that include a reason code field to indicate the reason when the response flag in the MSCA control field is set to 1 and the accept / Deny flag is set to 0.

Reference is made to 3rd which schematically shows a sequence diagram 300 of forwarding a multicast schedule update in an NMSG, according to some illustrative embodiments.

In some illustrative embodiments, one or more of the communications of the sequence diagram of FIG 3rd executed by devices of an NMSG to forward schedule updates from the NMSG. For example, the NMSG, as in 3rd shown, contain six devices, which are designated with device A, device B, device C, device D, device E and device F.

In one example, the devices 102 , 140 , 160 and or 180 ( 1 ) configured to perform one or more operations of the devices of 3rd To run.

It should be noted that only some of the possible multicast schedule update NAF transmissions in the sequence diagram 300 are shown.

As in 3rd shown, the device A take on a role as the person responsible for the schedule, for example the device 140 who have updated schedule information 310 can use the devices in the NMSG via multicast. For example, as in 3rd shown updated schedule information 310 received by some of the devices in the NMSG, for example by the device B , the device D , the device E and the device F .

As in 3rd shown receives the device C. may not have the updated schedule information 310 , for example when the device C. out of range of the device A lies.

As in 3rd shown, the device E the updated schedule information 310 received by the schedule manager and can determine to forward the updated schedule information to, for example, the devices in the NMSG ( 320 ).

As in 3rd shown, the device A the forwarded updated schedule information 320 from the device E receive.

As in 3rd shown, the device D receive the updated schedule information from the schedule owner and may determine to forward the updated schedule information to, for example, the devices in the NMSG ( 330 ).

As in 3rd shown, the devices B , A and or F the forwarded updated schedule information 330 from the device D receive.

As in 3rd shown, the device B the updated schedule information 310 received by the schedule owner and can determine to forward the updated schedule information to the devices in the NMSG ( 340 ).

As in 3rd shown, the devices A , D , F and or C. the forwarded updated schedule information 340 from the device B receive.

As in 3rd shown, the device C. that have the updated schedule information 310 has not received the forwarded updated schedule information directly from the schedule owner 340 from the device B receive.

We turn 4th 10 schematically illustrates a method of the NMSG multicast schedule according to some illustrative embodiments. For example, one or more of the operations of the method of 4th through one or more elements of a system, the system 100 ( 1 ); a device, for example the wireless communication devices 102 , 140 , 160 and or 180 ( 1 ); a controller, for example the controller 124 ( 1 ) and / or the controller 154 ( 1 ); a radio device, for example the radio device 114 ( 1 ) and / or the radio device 144 ( 1 ); and / or a message processor, for example the message processor 128 ( 1 ) and / or the message processor 158 ( 1 ) are carried out.

As in block 402 As indicated, the method may include exchanging, in a NAN device, multicast traffic with one or more other NAN devices in an NMSG according to an NMSG multicast schedule from a schedule manager. For example, the controller 124 ( 1 ) the device 102 ( 1 ) control, initiate and / or trigger multicast traffic with one or more other NAN devices in the NMSG according to the NMSG multicast schedule from the device 140 ( 1 ) to exchange, as described above, for example.

As in block 404 As indicated, the method may include receiving a first schedule update frame that contains updated schedule information of an updated NMSG multicast schedule. For example, the controller 124 ( 1 ) the device 102 ( 1 ) control, initiate and / or trigger the first schedule update frame, which contains the updated schedule information of the updated NMSG multicast schedule, from the device 140 ( 1 ) as described above, for example.

As in block 406 Indicated, the method can include determining, based on at least one forwarding criterion, whether the updated schedule information should be forwarded or not. For example, the controller 124 (Photo 1) the device 102 (Figure 1) control, initiate and / or trigger, for example using the at least one forwarding criterion to determine whether the updated schedule information should be forwarded or not, as described above, for example.

As in block 408 As indicated, the method may include, if, at the moment, and / or based on that it is determined that the updated schedule information is to be forwarded, send a second schedule update frame containing the updated schedule information. For example, the controller 124 ( 1 ) the device 102 ( 1 ) control, cause and / or trigger to send the second schedule update frame containing the updated schedule information, for example if the device 102 ( 1 ) determines that the updated schedule information should be forwarded, as described above, for example.

Reference is made to 5 which schematically show a product 500 illustrated according to some illustrative embodiments. The product 500 can be one or more tangible computer readable (machine readable) non-transitory storage media 502 included, which may include computer-executable instructions, such as logic 504 are implemented and are designed, when executed by at least one computer processor, to enable the at least one computer processor to perform one or more operations in the device 102 , the device 140 , the device 160 , the device 180 ( 1 ), the radio device 114 ( 1 ), the radio device 144 ( 1 ), the broadcaster 118 ( 1 ), the broadcaster 148 ( 1 ), the recipient 116 ( 1 ), the recipient 146 ( 1 ), the controller 124 ( 1 ), the controller 154 ( 1 ), the message processor 128 ( 1 ) and / or the message processor 158 ( 1 ) execute the device 102 , the device 140 , the device 160 , the device 180 ( 1 ), the radio device 114 ( 1 ), the radio device 144 ( 1 ), the transmitter 118 ( 1 ), the transmitter 148 ( 1 ), the recipient 116 ( 1 ), the recipient 146 ( 1 ), the controller 124 ( 1 ), the controller 154 ( 1 ), the message processor 128 ( 1 ) and / or the message processor 158 ( 1 ) to cause, trigger and / or implement one or more operations and / or functionalities, and / or one or more operations and / or functionalities related to the 1 , 2nd , 3rd and / or 4 are described, and / or perform, trigger and / or implement one or more of the operations described herein. The phrase "non-transitory machine-readable medium" can refer to all computer-readable media, the only exception being a transitory propagation signal.

In some illustrative embodiments, the product 500 and / or the machine-readable storage medium 502 contain one or more types of computer readable storage media that can store data including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory and the like. To the machine-readable storage media 502 may include, for example: RAM, DRAM, double data rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM ), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g. NOR or NAND flash memory), content-addressable memory (CAM) , Polymer memory, phase change memory, ferroelectric memory, silicon oxide nitride oxide silicon (SONOS) memory, a disk, a floppy disk, a hard disk drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card , a tape, a cassette and the like. Computer readable storage media can include any suitable media used in downloading or transferring a computer program from a remote computer to a requesting computer, the computer program being data signals embodied in a carrier wave or other propagation media over a communication link , for example a modem, radio or network connection.

In some illustrative embodiments, the logic 504 Instructions, data, and / or code that, when executed by a machine, may cause the machine to perform a method, process, and / or operations as described herein. For example, the machine may include any suitable processing platform, computer platform, computing device or device, computer system or processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.

In some illustrative embodiments, the logic 504 Software, a software module, an application, a program, a subroutine, instructions, an instruction set, computer code, words, values, symbols and the like are included or implemented as such. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code and the like. The instructions can be implemented according to a predefined computer language, manner, or syntax to instruct a processor to perform a particular function. The instructions can be implemented using any suitable higher, lower, object-oriented, visual, compiled and / or interpreted programming language such as C, C ++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code and the like.

EXAMPLES

The following examples relate to further embodiments.

Example 1 includes a device that includes logic and circuitry configured to cause a Neighbor Awareness Networking (NAN) device to: Exchange multicast traffic with one or more other NAN devices in a NAN multicast service group (NMSG) according to an NMSG multicast schedule from a schedule manager, receiving a first schedule update frame that includes updated schedule information of an updated NMSG multicast schedule; Determining, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame that includes the updated schedule information.

Example 2 contains the subject matter of Example 1, and optionally the device is configured to cause the NAN device to determine whether to update the updated schedule information based on a sequence identifier (ID) in the first schedule update frame or not.

Example 3 includes the subject matter of Example 2, and optionally the device is configured to cause the NAN device to determine that the updated schedule information should be forwarded if the sequence ID in the first schedule update frame is greater than a stored sequence ID that corresponds to the NMSG.

Example 4 contains the subject of Example 3, and optionally the device is configured to cause the NAN device to update the stored sequence ID corresponding to the NMSG so that the sequence ID is updated in the first schedule Frame is included.

Example 5 contains the subject of one of Examples 1-4, and optionally the device is configured to cause the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registrar of the NMSG.

Example 6 includes the subject of one of Examples 1-5, and optionally the device is configured to allow the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registered member of the NMSG .

Example 7 contains the subject of one of Examples 1-6, and optionally the first schedule update frame comes from the schedule owner.

Example 8 includes the subject of one of Examples 1-7, and optionally the device is configured to cause the NAN device to send a unicast schedule request with a requested schedule change to the schedule owner and the first in response to the schedule request Receive schedule update frame from the schedule owner.

Example 9 contains the subject matter of Example 8, and optionally the first schedule update frame includes a notification box to indicate whether the requested schedule change is accepted or rejected.

Example 10 contains the subject of one of Examples 1-6, and optionally the first schedule update frame comes from another NAN device that is not the schedule owner.

Example 11 contains the subject of one of Examples 1-6, and optionally the first schedule update frame comes from an originator of the NMSG.

Example 12 includes the subject of one of Examples 1-11, and optionally the first schedule update frame includes a multicast frame to the NMSG.

Example 13 contains the subject of one of Examples 1-11, and optionally the first schedule update frame includes a unicast frame to the NAN device.

Example 14 contains the subject of one of Examples 1-13, and optionally the second schedule update frame comprises a multicast frame to the NMSG.

Example 15 includes the subject of one of Examples 1-14, and optionally the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute.

Example 16 contains the subject matter of one of Examples 1-15, and optionally the updated schedule information includes an indication of a point in time at which the updated NMSG multicast schedule is to be transitioned to.

Example 17 contains the subject of one of Examples 1-16, and optionally the first schedule update frame includes a NAN Action Frame (NAF).

Example 18 includes the subject of one of Examples 1-17, and optionally the second schedule update frame includes a NAN Action Frame (NAF).

Example 19 contains the subject matter of one of Examples 1-18, and the at least one forwarding criterion optionally relates to whether the NAN device is a registrar or a registrant.

Example 20 includes the subject of one of Examples 1-19, and the at least one forwarding criterion optionally relates to whether the NAN device is a multicast source.

Example 21 contains the subject of one of Examples 1-20, and optionally the device is configured to cause the NAN device to retransmit the second schedule update frame several times.

Example 22 contains the subject of one of Examples 1-21, and optionally the device is configured to cause the NAN device to decide not to forward the updated schedule information if the updated schedule information is the same as previously received from the same schedule owner updated schedule information.

Example 23 contains the subject matter of one of Examples 1-22, and optionally the device is configured to cause the NAN device based on a proximity criterion that is the proximity between the NAN device and a device of which the updated schedule information is sent corresponds to determining whether to update the updated schedule information or not.

Example 24 contains the subject of one of Examples 1-23, and optionally the NMSG comprises a many-to-many NMSG.

Example 25 contains the subject of one of Examples 1-24 and optionally includes a radio device.

Example 26 contains the subject matter of one of Examples 1-25 and optionally includes one or more antennas, a processor and a memory.

Example 27 includes a wireless communication system that includes a Neighbor Awareness Networking (NAN) device, the NAN device comprising: one or more antennas; a radio device; a memory; a processor; and a controller configured to cause the NAN device to: exchange multicast traffic with one or more other NAN devices in a NAN Multicast Service Group (NMSG) according to an NMSG multicast schedule of one Schedule managers, receiving a first schedule update frame that includes updated schedule information of an updated NMSG multicast schedule; Determining, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame that includes the updated schedule information.

Example 28 contains the subject matter of Example 27, and optionally the controller is configured to cause the NAN device to determine whether to update the updated schedule information based on a sequence identifier (ID) in the first schedule update frame or not.

Example 29 contains the subject matter of Example 28, and optionally the controller is configured to cause the NAN device to determine that the updated schedule information should be forwarded if the sequence ID in the first schedule update frame is greater than a stored sequence ID that corresponds to the NMSG.

Example 30 contains the subject matter of Example 29, and optionally the controller is configured to cause the NAN device to update the stored sequence ID corresponding to the NMSG so that the sequence ID is in the first schedule update Frame is included.

Example 31 contains the subject of one of Examples 27-30, and optionally the controller is configured to cause the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registrar of the NMSG.

Example 32 includes the subject of one of Examples 27-31, and optionally the controller is configured to allow the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registered member of the NMSG .

Example 33 contains the subject of one of Examples 27-32, and optionally the first schedule update frame comes from the schedule owner.

Example 34 includes the subject of one of Examples 27-33, and optionally the controller is configured to cause the NAN device to send a unicast schedule request to the schedule owner with a requested schedule change, and the first in response to the schedule request Receive schedule update frame from the schedule owner.

Example 35 contains the subject matter of Example 34, and optionally the first schedule update frame includes a notification box to indicate whether the requested schedule change is accepted or rejected.

Example 36 includes the subject of one of Examples 27-32, and optionally the first schedule update frame is from another NAN device that is not the schedule owner.

Example 37 contains the subject of one of Examples 27-32, and optionally the first schedule update frame is from an originator of the NMSG.

Example 38 contains the subject of one of Examples 27-37, and optionally the first schedule update frame includes a multicast frame to the NMSG.

Example 39 contains the subject of one of Examples 27-37, and optionally the first schedule update frame includes a unicast frame to the NAN device.

Example 40 contains the subject of one of Examples 27-39, and optionally the second schedule update frame includes a multicast frame to the NMSG.

Example 41 includes the subject of one of Examples 27-40, and optionally the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute.

Example 42 contains the subject of one of Examples 27-41, and optionally the updated schedule information includes an indication of a point in time at which the updated NMSG multicast schedule is to be transitioned to.

Example 43 contains the subject of one of Examples 27-42, and optionally the first schedule update frame includes a NAN Action Frame (NAF).

Example 44 contains the subject of one of Examples 27-43, and optionally the second schedule update frame includes a NAN Action Frame (NAF).

Example 45 contains the subject matter of one of Examples 27-44, and the at least one forwarding criterion optionally relates to whether the NAN device is a registrar or a registrant.

Example 46 contains the subject of one of Examples 27-45, and the at least one forwarding criterion optionally relates to whether the NAN device is a multicast source.

Example 47 contains the subject of one of Examples 27-46, and optionally the controller is configured to cause the NAN device to retransmit the second schedule update frame several times.

Example 48 includes the subject of one of Examples 27-47, and optionally the controller is configured to cause the NAN device to decide not to forward the updated schedule information if the updated schedule information is the same as that previously received from the same schedule owner updated schedule information.

Example 49 contains the subject matter of one of Examples 27-48, and optionally the controller is configured to cause the NAN device based on a proximity criterion that is the proximity between the NAN device and a device of which the updated schedule information is sent corresponds to determining whether or not to forward the updated schedule information.

Example 50 contains the subject of one of Examples 27-49, and optionally the NMSG comprises a many-to-many NMSG.

Example 51 includes a method to be performed in a Neighbor Awareness Networking (NAN) device, the method comprising: exchanging multicast traffic with one or more other NAN devices in a NAN Multicast Service Group (NMSG) according to an NMSG multicast schedule from a schedule owner; Receiving a first schedule update frame including updated schedule information of an updated NMSG multicast schedule; Determining, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame that includes the updated schedule information.

Example 52 includes the subject matter of Example 51 and optionally includes using a sequence identifier (ID) in the first schedule update frame to determine whether or not to update the updated schedule information.

Example 53 includes the subject of Example 52 and optionally includes determining that the updated schedule information should be forwarded if the sequence ID in the first schedule update frame is greater than a stored sequence ID that corresponds to the NMSG.

Example 54 contains the subject matter of Example 53 and optionally includes updating the stored sequence ID that corresponds to the NMSG to include the sequence ID in the first schedule update frame.

Example 55 includes the subject of one of Examples 51-54 and optionally includes determining that the updated schedule information should be forwarded if the NAN device is a registrar of the NMSG.

Example 56 includes the subject of one of Examples 51-55 and optionally includes allowing the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registered member of the NMSG.

Example 57 contains the subject of one of Examples 51-56, and optionally the first schedule update frame comes from the schedule owner.

Example 58 includes the subject of one of Examples 51-57 and optionally includes sending a unicast schedule request with a requested schedule change to the schedule manager and receiving the first schedule update frame from the schedule manager in response to the schedule request.

Example 59 contains the subject matter of Example 58, and optionally the first schedule update frame includes a message box to indicate whether the requested schedule change is accepted or rejected.

Example 60 contains the subject of one of Examples 51-56, and optionally the first schedule update frame is from another NAN device that is not the schedule owner.

Example 61 contains the subject of one of Examples 51-56, and optionally the first schedule update frame is from an originator of the NMSG.

Example 62 contains the subject of one of Examples 51-61, and optionally the first schedule update frame includes a multicast frame to the NMSG.

Example 63 contains the subject of one of Examples 51-61, and optionally the first schedule update frame includes a unicast frame to the NAN device.

Example 64 contains the subject of one of Examples 51-63, and optionally the second schedule update frame comprises a multicast frame to the NMSG.

Example 65 includes the subject of one of Examples 51-64, and optionally the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute.

Example 66 includes the subject of one of Examples 51-65, and optionally the updated schedule information includes an indication of a time at which to transition to the updated NMSG multicast schedule.

Example 67 includes the subject of one of Examples 51-66, and optionally the first schedule update frame includes a NAN Action Frame (NAF).

Example 68 includes the subject of one of Examples 51-67, and optionally the second schedule update frame includes a NAN Action Frame (NAF).

Example 69 contains the subject matter of one of Examples 51-68, and the at least one forwarding criterion optionally relates to whether the NAN device is a registrar or a registrant.

Example 70 contains the subject of one of Examples 51-69, and the at least one forwarding criterion optionally relates to whether the NAN device is a multicast source.

Example 71 includes the subject of one of Examples 51-70 and optionally includes retransmitting the second schedule update frame.

Example 72 includes the subject of one of Examples 51-71 and optionally includes deciding not to forward the updated schedule information if the updated schedule information is the same as updated schedule information previously received from the same schedule owner.

Example 73 includes the subject matter of one of Examples 51-72 and optionally includes determining whether the updated schedule information is based on a proximity criterion that corresponds to the proximity between the NAN device and a device from which the updated schedule information is being sent should be forwarded or not.

Example 74 contains the subject of one of Examples 51-73, and optionally the NMSG comprises a many-to-many NMSG.

Example 75 includes a product that includes one or more tangible, computer-readable, non-transitory storage media that include computer-executable instructions that, when executed by at least one processor, are capable of enabling the at least one processor to perform one Induce a neighbor awareness networking (NAN) device to: exchange multicast traffic with one or more other NAN devices in a NAN multicast service group (NMSG) according to an NMSG multicast schedule from a schedule manager; Receiving a first schedule update frame including updated schedule information of an updated NMSG multicast schedule; Determining, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame that includes the updated schedule information.

Example 76 contains the subject matter of Example 75, and optionally the instructions, when executed, cause the NAN device to use a sequence identifier (ID) in the first schedule update frame to determine whether or not to forward the updated schedule information .

Example 77 contains the subject matter of Example 76, and optionally the instructions, when executed, cause the NAN device to determine that the updated schedule information should be forwarded if the sequence ID in the first schedule update frame is greater than a stored sequence ID that corresponds to the NMSG.

Example 78 contains the subject of Example 77, and optionally the instructions, when executed, cause the NAN device to update the stored sequence ID corresponding to the NMSG so that the sequence ID is updated in the first schedule Frame is included.

Example 79 includes the subject of one of Examples 75-78, and optionally the instructions, when executed, cause the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registrar of the NMSG.

Example 80 includes the subject of one of Examples 75-79, and optionally the instructions, when executed, allow the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registered member of the NMSG .

Example 81 contains the subject of one of Examples 75-80, and optionally the first schedule update frame comes from the schedule owner.

Example 82 contains the subject of one of Examples 75-81, and optionally the instructions, when executed, cause the NAN device to send a unicast schedule request to the schedule owner with a requested schedule change and in response to the schedule request the first Receive schedule update frame from the schedule owner.

Example 83 contains the subject matter of Example 82, and optionally the first schedule update frame includes a message box to indicate whether the requested schedule change is accepted or rejected.

Example 84 contains the subject of one of Examples 75-80, and optionally the first schedule update frame comes from another NAN device that is not the schedule owner.

Example 85 contains the subject of one of Examples 75-80, and optionally the first schedule update frame is from an originator of the NMSG.

Example 86 contains the subject of one of Examples 75-85, and optionally the first schedule update frame includes a multicast frame to the NMSG.

Example 87 contains the subject of one of Examples 75-85, and optionally the first schedule update frame includes a unicast frame to the NAN device.

Example 88 contains the subject of one of Examples 75-87, and optionally the second schedule update frame comprises a multicast frame to the NMSG.

Example 89 contains the subject of one of Examples 75-88, and optionally the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute.

Example 90 includes the subject of one of Examples 75-89, and optionally the updated schedule information includes an indication of a time at which to transition to the updated NMSG multicast schedule.

Example 91 includes the subject of one of Examples 75-90, and optionally the first schedule update frame includes a NAN Action Frame (NAF).

Example 92 contains the subject of one of Examples 75-91, and optionally the second schedule update frame includes a NAN Action Frame (NAF).

Example 93 contains the subject matter of one of Examples 75-92, and the at least one forwarding criterion optionally relates to whether the NAN device is a registrar or a registrant.

Example 94 contains the subject matter of one of Examples 75-93, and the at least one forwarding criterion optionally relates to whether the NAN device is a multicast source.

Example 95 contains the subject of one of Examples 75-94, and optionally the instructions, when executed, cause the NAN device to retransmit the second schedule update frame several times.

Example 96 contains the subject matter of one of Examples 75-95, and optionally the instructions, when executed, cause the NAN device to decide not to forward the updated schedule information if the updated schedule information is the same as previously received from the same schedule owner updated schedule information.

Example 97 contains the subject of one of Examples 75-96, and optionally the instructions, when executed, cause the NAN device to operate based on a proximity criterion that is the proximity between the NAN device and a device of which the updated schedule information is sent corresponds to determining whether to update the updated schedule information or not.

Example 98 contains the subject of one of Examples 75-97, and optionally the NMSG comprises a many-to-many NMSG.

Example 99 includes a device for wireless communication through a Neighbor Awareness Networking (NAN) device, the NAN device comprising: means for exchanging multicast traffic with one or more other NAN devices in a NAN Multicast Service Group ( NMSG) according to an NMSG multicast schedule by a schedule manager; means for receiving a first schedule update frame comprising updated schedule information of an updated NMSG multicast schedule; means for determining, based on at least one forwarding criterion, whether or not the updated schedule information should be forwarded; and means for sending a second schedule update frame comprising the updated schedule information when it is determined that the updated schedule information is to be forwarded.

Example 100 contains the subject matter of Example 99 and optionally includes a means to determine whether or not to update the updated schedule information based on a sequence identifier (ID) in the first schedule update frame.

Example 101 contains the subject matter of Example 100 and optionally includes a means for determining that the updated schedule information should be forwarded if the sequence ID in the first schedule update frame is greater than a stored sequence ID that corresponds to the NMSG.

Example 102 contains the subject matter of Example 101 and optionally includes a means to update the stored sequence ID corresponding to the NMSG so that the sequence ID is included in the first schedule update frame.

Example 103 includes the subject of one of Examples 99-102 and optionally includes a means for determining that the updated schedule information should be forwarded when the NAN device is a registrar of the NMSG.

Example 104 contains the subject of one of Examples 99-103 and optionally includes a means to allow the NAN device to determine that the updated schedule information should be forwarded if the NAN device is a registered member of the NMSG.

Example 105 contains the subject of one of Examples 99-104, and optionally the first schedule update frame comes from the schedule owner.

Example 106 includes the subject of one of Examples 99-105 and optionally includes means for sending a unicast schedule request with a requested schedule change to the schedule owner and receiving the first schedule update frame from the schedule officer in response to the schedule request.

Example 107 contains the subject matter of Example 106, and optionally the first schedule update frame includes a message box to indicate whether the requested schedule change is accepted or rejected.

Example 108 contains the subject of one of Examples 99-104, and optionally the first schedule update frame comes from another NAN device that is not the schedule owner.

Example 109 contains the subject of one of Examples 99-104, and optionally the first schedule update frame is from an originator of the NMSG.

Example 110 contains the subject of one of Examples 99-109, and optionally the first schedule update frame includes a multicast frame to the NMSG.

Example 111 contains the subject of one of Examples 99-109, and optionally the first schedule update frame includes a unicast frame to the NAN device.

Example 112 contains the subject of one of Examples 99-111, and optionally the second schedule update frame comprises a multicast frame to the NMSG.

Example 113 includes the subject of one of Examples 99-112, and optionally the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute.

Example 114 includes the subject of one of Examples 99-113, and optionally the updated schedule information includes an indication of a time at which to transition to the updated NMSG multicast schedule.

Example 115 contains the subject of one of Examples 99-114, and optionally the first schedule update frame includes a NAN Action Frame (NAF).

Example 116 includes the subject of one of Examples 99-115, and optionally the second schedule update frame includes a NAN Action Frame (NAF).

Example 117 contains the subject of one of Examples 99-116, and the at least one forwarding criterion optionally relates to whether the NAN device is a registrar or a registrant.

Example 118 contains the subject of one of Examples 99-117, and the at least one forwarding criterion optionally relates to whether the NAN device is a multicast source.

Example 119 contains the subject of one of Examples 99-118 and optionally includes a means for retransmitting the second schedule update frame several times.

Example 120 includes the subject of one of Examples 99-119 and optionally includes a means for deciding not to forward the updated schedule information if the updated schedule information is the same as updated schedule information previously received from the same schedule owner.

Example 121 includes the subject of one of Examples 99-120 and optionally includes a means to determine whether based on a proximity criterion that corresponds to the proximity between the NAN device and a device from which the updated schedule information is being sent the updated schedule information should or should not be forwarded.

Example 122 contains the subject of one of Examples 99-121, and optionally the NMSG comprises a many-to-many NMSG.

Functions, operations, components, and / or features described herein with reference to one or more embodiments may be combined with one or more other functions, operations, components, and / or features described herein with reference to one or more other embodiments have been described, combined or used in combination with them, or vice versa.

While certain features have been illustrated and described herein, many modifications, substitutions, changes, and equivalents can occur to those skilled in the art. Therefore it is to be understood that the appended claims are intended to embrace all modifications and changes that come within the spirit of the disclosure.

QUOTES INCLUDE IN THE DESCRIPTION

This list of documents listed by the applicant has been generated automatically and is only included for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent literature cited

• US 62542367 [0001]

Claims (25)

Device comprising logic and circuitry configured to cause a Neighbor Awareness Networking (NAN) device to: Exchanging multicast traffic with one or more other NAN devices in a NAN Multicast Service Group (NMSG) according to an NMSG multicast schedule from a schedule manager; Receiving a first schedule update frame including updated schedule information of an updated NMSG multicast schedule; Determine, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame that includes the updated schedule information. Device after Claim 1 configured to cause the NAN device to determine whether or not to forward the updated schedule information based on a sequence identifier (ID) in the first schedule update frame. Device after Claim 2 configured to cause the NAN device to determine that the updated schedule information should be forwarded if the sequence ID in the first schedule update frame is greater than a stored sequence ID that corresponds to the NMSG. Device after Claim 3 configured to cause the NAN device to update the stored sequence ID that corresponds to the NMSG to include the sequence ID in the first schedule update frame. Device after Claim 1 configured to cause the NAN device to determine that the updated schedule information should be forwarded when the NAN device is a registrar of the NMSG. Device after Claim 1 configured to allow the NAN device to determine that the updated schedule information should be forwarded when the NAN device is a registered member of the NMSG. Device according to one of the Claims 1 - 6 , wherein the first schedule update frame comes from the schedule owner. Device according to one of the Claims 1 - 6 configured to cause the NAN device to send a unicast schedule request with a requested schedule change to the schedule manager and to receive the first schedule update frame from the schedule manager in response to the schedule request. Device after Claim 8 wherein the first schedule update frame includes a notification field that indicates whether the requested schedule change is accepted or rejected. Device according to one of the Claims 1 - 6 , wherein the first schedule update frame comes from another NAN device that is not the schedule owner. Device according to one of the Claims 1 - 6 wherein the second schedule update frame comprises a multicast frame to the NMSG. Device according to one of the Claims 1 - 6 wherein the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute. Device according to one of the Claims 1 - 6 wherein the second schedule update frame comprises a NAN Action Frame (NAF). Device according to one of the Claims 1 - 6 wherein the at least one forwarding criterion relates to whether the NAN device is a registrar or a registrant. Device according to one of the Claims 1 - 6 configured to cause the NAN device to retransmit the second schedule update frame several times. Device according to one of the Claims 1 - 6 configured to cause the NAN device to determine whether the updated schedule information is forwarded based on a proximity criterion that corresponds to the proximity between the NAN device and a device from which the updated schedule information is sent should be or not. Device according to one of the Claims 1 - 6 , which comprises one or more antennas, a processor and a memory. A wireless communication system that includes a Neighbor Awareness Networking (NAN) device, the NAN device comprising: one or more antennas, a radio device; a memory; a processor; and a controller configured to cause the NAN device to do the following: Exchanging multicast traffic with one or more other NAN devices in a NAN Multicast Service Group (NMSG) according to an NMSG multicast schedule from a schedule manager; Receiving a first schedule update frame including updated schedule information of an updated NMSG multicast schedule; Determine, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame that includes the updated schedule information. System according to Claim 18 wherein the controller is configured to cause the NAN device to determine whether or not to forward the updated schedule information based on a sequence identifier (ID) in the first schedule update frame. System according to Claim 18 or 19th wherein the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute. A method to be performed in a Neighbor Awareness Networking (NAN) device, the method comprising: Exchanging multicast traffic with one or more other NAN devices in a NAN Multicast Service Group (NMSG) according to an NMSG multicast schedule from a schedule manager; Receiving a first schedule update frame including updated schedule information of an updated NMSG multicast schedule; Determine, based on at least one forwarding criterion, whether or not to forward the updated schedule information; and if it is determined that the updated schedule information is to be forwarded, sending a second schedule update frame that includes the updated schedule information. Procedure according to Claim 21 comprising determining whether or not to forward the updated schedule information based on a sequence identifier (ID) in the first schedule update frame. Procedure according to Claim 21 which includes sending a unicast schedule request with a requested schedule change to the schedule manager and receiving the first schedule update frame from the schedule manager in response to the schedule request. Procedure according to Claim 21 wherein the updated schedule information includes a multicast schedule change attribute and a NAN availability attribute. Product that includes one or more tangible, computer-readable, non-transitory storage media that includes computer-executable instructions that, when executed by at least one processor, are capable of enabling the at least one processor to be a neighbor Awareness Networking (NAN) device to initiate the process according to one of the Claims 21 - 24th to execute.

Images