POWER EFFICIENT BROADCASTING IN WLAN

Devices, methods, and/or systems for broadcasting in a wireless local area network (WLAN). A STA receives a frame from a wireless access point (AP) which includes an indication that an enhanced broadcast service (eBCS) service is ending. The frame may include an end-of-broadcast-service announcement information element, and/or an indication of a time at which the eBCS service is ending. The STA may negotiate with the AP for continuation of the broadcast service if the STA desires to continue receiving the eBCS service beyond the time at which the eBCS service ends. The STA may receive a trigger frame from the AP which triggers a response from the STA indicating that it desires to continue receiving the eBCS service beyond the time at which the eBCS service ends.

BACKGROUND

A WLAN in Infrastructure Basic Service Set (BSS) mode may include an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. An enhanced broadcast service (eBCS) may include downlink from an AP to non-AP STAs or may include uplink from sensor non-AP STAs. Enhanced Broadcast Service may be provided to both STAs that are associated or un-associated with a particular AP. Some example use cases for eBCS may include stadium video broadcasting; automotive broadcasting; uplink sensor data broadcasting; museum information and multilingual broadcasting; and/or event producer information and content broadcasting.

SUMMARY

Devices, methods, and/or systems for broadcasting in a wireless local area network (WLAN). A STA receives a frame from a wireless access point (AP) which includes an indication that an enhanced broadcast service (eBCS) service is ending. The frame may include an end-of-broadcast-service announcement information element, and/or an indication of a time at which the eBCS service is ending. The STA may negotiate with the AP for continuation of the broadcast service if the STA desires to continue receiving the eBCS service beyond the time at which the eBCS service ends. The STA may receive a trigger frame from the AP which triggers a response from the STA indicating that it desires to continue receiving the eBCS service beyond the time at which the eBCS service ends.

DETAILED DESCRIPTION

In an embodiment, the base station114aand the WTRUs102a,102b,102cmay implement a radio technology such as NR Radio Access, which may establish the air interface116using NR.

The RAN104may be in communication with the CN106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs102a,102b,102c,102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN106may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown inFIG.1A, it will be appreciated that the RAN104and/or the CN106may be in direct or indirect communication with other RANs that employ the same RAT as the RAN104or a different RAT. For example, in addition to being connected to the RAN104, which may be utilizing a NR radio technology, the CN106may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN106shown inFIG.1Cmay include a mobility management entity (MME)162, a serving gateway (SGW)164, and a packet data network (PDN) gateway (PGW)166. While the foregoing elements are depicted as part of the CN106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

The CN106may facilitate communications with other networks. For example, the CN106may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN106and the PSTN108. In addition, the CN106may provide the WTRUs102a,102b,102cwith access to the other networks112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs102a,102b,102cmay be connected to a local DN185a,185bthrough the UPF184a,184bvia the N3 interface to the UPF184a,184band an N6 interface between the UPF184a,184band the DN185a,185b.

A WLAN in Infrastructure Basic Service Set (BSS) mode may include an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP typically has access or interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in and out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and is delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to the respective destinations. Traffic between STAs within the BSS may also be sent through the AP where the source STA sends traffic to the AP and the AP delivers the traffic to the destination STA. Such traffic between STAs within a BSS may be considered peer-to-peer traffic. Such peer-to-peer traffic may also be sent directly between the source and destination STAs with a direct link setup (DLS), e.g., using an 802.11e DLS or an 802.11z tunnelled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may have no AP, and/or may include STAs, communicating directly with each other. This mode of communication is referred to as an “ad-hoc” mode of communication.

Using the 802.11ac infrastructure mode of operation, the AP may transmit a beacon on a fixed channel, e.g., the primary channel. This channel may be 20 MHz wide, and may be the operating channel of the BSS. This channel may also be used by the STAs to establish a connection with the AP. Channel access in an 802.11 system may include Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA). In this mode of operation, every STA, including the AP, may sense the primary channel. If the channel is detected to be busy, the STA may “back off”. Hence only one STA may transmit at any given time in a given BSS.

In 802.11n, High Throughput (HT) STAs may also use a 40 MHz wide channel for communication. This may be achieved by combining the primary 20 MHz channel, with an adjacent 20 MHz channel to form a 40 MHz wide contiguous channel.

In 802.11ac, Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and 160 MHz wide channels. The 40 MHz, and 80 MHz, channels may be formed by combining contiguous 20 MHz channels similar to 802.11n described above. A 160 MHz channel may be formed either by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, this may also be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that divides it into two streams. IFFT and time domain processing may be done on each stream separately, after which, the streams may be mapped on to the two channels, and the data may be transmitted. At the receiver, this mechanism is reversed, and the combined data is sent to the MAC.

Sub 1 GHz modes of operation may be supported by 802.11af, and 802.11ah. For these specifications the channel operating bandwidths, and carriers, may be reduced relative to those used in 802.11n, and 802.11ac. 802.11af may support 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah may support 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. A possible use case for 802.11ah is support for Meter Type Control (MTC) devices in a macro coverage area. MTC devices may have limited capabilities including only support for limited bandwidths, but may also include a requirement for a very long battery life.

WLAN systems which support multiple channels, and channel widths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, may include a channel which is designated as the primary channel. The primary channel may, but not necessarily, have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may therefore be limited by the STA, of all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide if there are STAs (e.g. MTC type devices) that only support a 1 MHz mode even if the AP, and other STAs in the BSS, may support a 2 MHz, 4 MHz, 8 MHz, 16 MHz, or other channel bandwidth operating modes. All carrier sensing, and NAV settings, may depend on the status of the primary channel; i.e., if the primary channel is busy, for example, due to a STA supporting only a 1 MHz operating mode is transmitting to the AP, then the entire available frequency bands may be considered busy even though majority of it stays idle and available.

In the United States, at present, the available frequency bands which may be used by 802.11ah may be from 902 MHz to 928 MHz. In Korea, at present, the available frequency bands which may be used by 802.11ah may be from 917.5 MHz to 923.5 MHz; and in Japan, the available frequency bands which may be used by 802.11ah may be from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah may be 6 MHz to 26 MHz depending on the country code.

IEEE 802.11™ High Efficiency WLAN (HEW) may include amendments to enhance the quality of service all users experience for a broad spectrum of wireless users in many usage scenarios including high-density scenarios in the 2.4 GHz, 5 GHz and 6 GHz band. New use cases which support dense deployments of APs, and STAs, and associated Radio Resource Management (RRM) technologies may be considered.

Potential applications for HEW may include emerging usage scenarios such as data delivery for stadium events, high user density scenarios such as train stations, or enterprise/retail environments, and also evidence for an increased dependence on video delivery, and wireless services for medical applications.

The measured traffic for a variety of applications may have a large likelihood of short packets, and network applications may also generate short packets. Such applications may include Virtual office; transmit power control (TPC) acknowledgement (ACK); video streaming ACK; Device/Controller (Mice, keyboards, Game controls, etc.); access—probe request/response; network selection—probe request, Access Network Query Protocol (ANQP); and/or network management—control frame applications.

802.11ax may include MU features that include UL and DL OFDMA and UL and DL multi-user MIMO (MU-MIMO). Designing and defining a mechanism for multiplexing UL random access for different purposes may be consider in the spec.

802.11ax may address medium access issues in the 6 GHz band, such as by using triggered or scheduled medium access only in the 6 GHz band, and/or restricting active scanning and having scheduled Enhanced Distributed Channel Access (EDCA) medium access in the 6 GHz band.

IEEE 802.11bc may include a MAC amendment to enhanced broadcast service (eBCS) for 802.11 devices. The IEEE 802.11bc amendment may not impact the current IEEE 802.11 PHY specifications.

eBCS service may include downlink from an AP to non-AP STAs or may include uplink from sensor non-AP STAs. Enhanced Broadcast Service may be provided to both STAs that are associated or un-associated with a particular AP. An AP may support up to 3000 non-AP STAs with eBCS service. In addition, there may be a class of low-cost non-AP STAs that consumes the eBCS service that may not be able to transmit directly to the AP.

Some example usage cases for eBCS may include stadium video broadcasting; automotive broadcasting; uplink sensor data broadcasting; museum information and multilingual broadcasting; and/or event producer information and content broadcasting.

In downlink broadcasting use cases, an eBCS AP may provide broadcasting services to STAs that are either associated with it or unassociated with the AP. Since broadcast frames may not be acknowledged, it may not always be clear whether there are any STAs that are utilizing the broadcast service and receiving the broadcast data. If broadcast data is not being received, the AP would be wasting both power as well as wireless medium resources. Some implementations provide a broadcast service mechanism to facilitate a broadcasting service which is power efficient and may only provide broadcast service when and/or if the service is being actively consumed.

For STAs that want to utilize downlink broadcast services provided by one or more APs, the STAs may be associated or unassociated with the APs that provide the broadcast services. Such STAs and APs may need to request broadcast service and negotiate parameters for the requested broadcast services. Some implementations include indication and negotiation procedures to support the broadcast service discovery and parameter negotiation.

Some implementations provide an End of Broadcast Service Announcement information element. In some implementations, an AP may transmit an End of Broadcast Service Announcement frame, or a frame that contains an End of Broadcast Service Announcement information element to announce that one or more eBCS Service is ending.

Example values for the various fields and subfields discussed herein are provided for illustration only, and it is noted that in other implementations, any other suitable value may be used to indicate the same information, or different information. For example, in some implementations, a bit value of 1 in a field may indicate certain information, whereas a bit value of 0 in the field may indicated this same information.

FIG.2is a bitmap diagram illustrating an example format of an End of Broadcast Service Announcement information element. The End of Broadcast Service Announcement information element may contain one or more of the following fields: Element identifier (ID)202, Length204, and Element ID Extension206, Number of Broadcast Service field208, and one or more Broadcast Service fields210. The Element identifier (ID) field202, Length field204, and Element ID Extension field206may indicate that the current element is an End of Broadcast Service Announcement information element and may indicate the length of the current element. The Number of Broadcast Service fields208may indicate the number of Broadcast Service fields that the element includes. The one or more Broadcast Service fields210, each of which may include the information of a particular Broadcast Service, including some or all of the fields described below for each broadcast service.

The one or more Broadcast Service fields210may have a format as shown inFIG.2, and may include one or more of the following fields: Broadcast Service Information Control field212; Broadcast Service ID field214; Higher Layer Destination Address field216; Title Length field218; Title field220; Time to Termination field222; and/or Negotiation Method field224. The Broadcast Service Information Control field212; Broadcast Service ID field214, Title Length field218, Time to Termination field222, and Negotiation Method field224may be 1 byte in length, while the Higher Layer Destination Address field216and Title field may be of variable byte length.

FIG.3is a bitmap diagram illustrating an example format of a Broadcast Service Info Control field212. The Broadcast Service Info Control field212may be 1 byte in length and may include indications of whether certain broadcast information is contained in the Broadcast Service Field210. The Broadcast Service Info Control field212may include one of the following subfields: Broadcast Service ID Present subfield302, Higher Layer Protocol subfield304, Title Present subfield306, Negotiation Method Present subfield308, Association Required subfield310, and Reserved subfield312.

The Broadcast Service ID Present subfield302may be 1 bit of length and indicate whether Broadcast Service ID is included in the Broadcast Service Field. The Higher Layer Protocol subfield304may be three bits in length and may contain a value indicating that a Higher Layer Destination Address is not present or a Higher Layer Destination Address is present in the Broadcast Service field210and may contain a value indicating that a Higher Layer Destination Address present in the Broadcast Service Field2010may be an address associated with one of the Higher Layer Protocols UDP/IPv4; UDP/IPv6; UDP/Hostname; MPEG Transport Stream identifier; MAC Address; or Reserved.

A Title Present subfield306may be one bit in length and may indicate whether a user readable title is present in the Broadcast Service field210. If the Title Present subfield306bit is set to 1, then a Title Length subfield218and a Title subfield220may be included in the Broadcast Service field210. A Negotiation Method Present subfield308may be 1 bit in length and may indicate whether the Negotiation Method subfield224is included in the Broadcast Service field210. An Association Required subfield310may be 1 bit in length and may indicate whether the Broadcast Service described by the current Broadcast Service field210requires association before it can be utilized by another STA.

Referring back toFIG.2, the Broadcast Service ID subfield214may be 1 byte in length and may indicate the identifier of the Broadcast Service. The Higher Layer Destination Address subfield216may take different lengths, e.g., depending on the value indicated in the Higher Layer Protocol field of the Broadcast Service Info Control subfield. The Higher Layer Destination Address subfield216may contain the IP address and UDP port if IPv4/UDP or IPv6/UDP is indicated in the Higher Layer Protocol subfield304.

A Higher Layer Destination Address subfield216may include a MAC address of 6 bytes if a MAC address is indicated in the Higher Layer Protocol subfield304. The Higher Layer Destination Address may not be included in the Broadcast Service field210if the Higher layer Protocol subfield304indicates that no Higher Layer Destination Address field is present.

A Title Length subfield218may be included in the Broadcast Service field210if the Title Present subfield306in the Broadcast Service Info Control subfield212is set to 1; otherwise it may not be present. The Title Length subfield218may be 1 byte in length and may indicate the length of the Title subfield220.

A Title subfield220may be included in the Broadcast Service field210if the Title Present subfield306in the Broadcast Service Info Control subfield212is set to 1; otherwise it may not be present. The Title Length subfield218may be 1 byte in length and may indicate the length of the Title subfield220.

A Time to Termination subfield222may be used to indicate the remaining time left at which the Broadcast Service described in this Broadcast Service field210will terminate unless additional negotiation is conducted by one or more STAs that may consume the said Broadcast Service. In another example, the Time to Termination subfield222may include a time, for example, a timing synchronization function (TSF) time value, or other type of time, at which the said Broadcast Service will terminate unless additional negotiation is conducted by the initiator of the broadcast service or by other users of the said Broadcast Service. Additionally or alternatively, a Timestamp of current time, such as the current value of the TSF timer may be included.

A Negotiation Method subfield224may be included in the Broadcast Service field210if the Negotiation Method Present subfield308is set to 1 (or another suitable indication). The Negotiation Method subfield may be used to indicate the negotiation method that should be used to negotiate for the continuation of the broadcast service beyond the time of termination. The Negotiation Method subfield may contain one or more of the following values: Through Broadcast Service Request frames, Through ANQP/GAS Broadcast Service Request frames, and/or Through IP Request (in this case, the IP version and IP addresses that is needed for negotiation may be included).

In some implementations, any subset of fields or subfields of the End of Broadcast Service Announcement element200may be implemented in any field or subfield or a set or subset of fields of existing or newly designed elements or frames, or PHY and/or MAC headers of any management, control, data frames, or other headers, or other frames.

Some implementations provide an eBCS Service Termination Notice frame format. In some implementations, an eBCS Service Termination Notice frame is transmitted by a STA that is a transmitter of eBCS services to announce the termination of one or more of the eBCS services transmitted by the STA, e.g., an AP, or by other STAs.

FIG.4is a diagram illustrating an example format of a eBCS Termination Notice Frame Action field400. As illustrated inFIG.4, the eBCS Termination Notice Frame Action field400may include a Category field402, Public Action field404, and/or eBCS Service Termination Information Set field406. The Category field402and Public Action field404may be one octet in length while the eBCS Service Termination Information Set field406may be of variable length. In some implementations, the eBCS Service Termination Information Set field406includes one or more of eBCS Service Termination Info subfields500.

FIG.5is a diagram illustrating an example format of an eBCS Service Termination Info subfield500. As shown inFIG.5, the eBCS Service Termination Information Set field406may include one or more of an eBCS Service Termination Information Control subfield502, eBCS Service ID subfield504, Title Length subfield506, Title subfield508, Time to Termination subfield510, Negotiation Method subfield512, Negotiation Address type subfield514, and/or Negotiation Address subfield516.

The eBCS Service Termination Information Control subfield502, eBCS Service ID subfield504, and Negotiation Method subfield512may have a octet length of 1, while the Title Length subfield506and Negotiation Method subfield514may have a octet length of 0 or 1. The Time to Termination subfield510may have an octet length of 2. The Title subfield508and Negotiation Address subfield516may be of variable octet length.

FIG.6is a diagram illustrating an example format of the eBCS Service Termination Info Control subfield502. As shown inFIG.6, the eBCS Service Termination Info Control subfield502may include a Title Presence Indicator subfield602, a Negotiation Address Presence Indicator subfield604, an Association Required subfield606, and/or reserved subfields608.

In one example, a value of 1 in the Title Presence Indicator subfield602indicates that a Title Length subfield506and a Title subfield508are present in the same eBCS Service Termination Info subfield. In one example, a value of 0 in the Title Presence Indicator subfield602indicates that a Title Length subfield506and a Title subfield508are not present in the same eBCS Service Termination Information subfield. In one example, a value of 1 in the Negotiation Address Presence Indicator subfield604indicates that a Negotiation Address Type subfield514and a Negotiation Address subfield516are present in the same eBCS Service Termination Info subfield. In one example, a value of 0 indicates that a Negotiation Address Type subfield514and a Negotiation Address subfield516are not present in the same eBCS Service Termination Info subfield. In one example, a value of 1 in the Association Required subfield606indicates that association is required to consume the eBCS service identified by the eBCS Service ID contained in the eBCS Service ID subfield504. In one example, a value of 0 indicates that association is not required to consume the eBCS service identified by the eBCS Service ID included in the eBCS Service ID subfield504.

Referring back toFIG.5, in some implementations, the eBCS Service ID subfield504is 1 octet in length. In some implementations, the eBCS Service ID subfield504indicates the ID of the eBCS service to be terminated. In some implementations, the Title Length subfield506is 1 octet in length. In some implementations, the Title Length subfield506indicates the length of the Title subfield508in octets. In some implementations, the Title subfield508indicates the Title of the eBCS Service identified by the eBCS Service ID contained in the eBCS Service ID subfield504. In some implementations, the Title subfield508indicates the Title in 8-bit Unicode Transformation Format (UTF-8) format. In some implementations, the Time to Termination subfield510is 2 octets in length. In some implementations, the Time to Termination subfield510indicates the number of TBTTs until the eBCS Service identified by the eBCS Service ID contained in the eBCS Service ID subfield504is terminated. In some implementations, the Time to Termination subfield510may be indicated in other time format, such as milliseconds (ms), microseconds (us), Time Units (TUs), or any other type of time units. In some implementations, the value 0 indicates that the eBCS Service identified by the eBCS Service ID in the same eBCS Service ID subfield504has no specific termination time. In some implementations, some other value, for example, the maximal value of the Time to Termination subfield indicates that the eBCS Service identified by the eBCS Service ID in the same eBCS Service ID subfield504has no specific termination time, or indicates that the eBCS Service identified by the eBCS Service ID in the same eBCS Service ID subfield504has a termination time that is larger than the maximal value that can be contained by the Time To Termination subfield510.

In some implementations, the Negotiation Method subfield512is 1 octet in length. In some implementations, the Negotiation Method subfield512indicates the negotiation method to negotiate extension of the eBCS service identified by the eBCS Service ID contained in the eBCS Service ID subfield504. Example encoding of the Negotiation Method subfield512is defined in Table 1 below. Other values may be used to indicate the same Negotiation Method as detailed in Table 1.

In some implementations, the Negotiation Address Type subfield514is 1 octet in length. In some implementations, the Negotiation Address Type subfield514indicates the type of the address included in the Negotiation Address subfield516. Example encoding of the Negotiation Address Type subfield514is defined in Table 2.

In some implementations, the Negotiation Address subfield516indicates the address to be used for negotiating for the extension of the eBCS service identified by the eBCS Service ID contained in the eBCS Service ID subfield504. In some implementations, the format and the length of the Negotiation Address subfield516depends on the value contained in the Negotiation Address Type subfield514. In some implementations, the Negotiation Address subfield516contains a MAC address, e.g., if the Negotiation Address Type is equal to 0.

FIG.7is a diagram illustrating an example format of the Negotiation Address subfield516, e.g., when the Negotiation Address Type is equal to 1 (or another suitable value indicating this). In some implementations, the IPv4 Address subfield702indicates an IPv4 address used for negotiating the extension of the eBCS service. In some implementations, the Destination UDP Port subfield704indicates the UDP Port associated with the IPv4 address indicated in the IPv4 Address subfield702in little endian format.

FIG.8is a diagram illustrating an example format of the Negotiation Address subfield516, e.g., when the Negotiation Address Type is equal to 2 (or another suitable value indicating this). In some implementations, the IPv6 Address subfield802indicates an IPv6 address used for negotiating the extension of the eBCS service. In some implementations, the Destination UDP Port subfield804indicates the UDP Port associated with the IPv6 address indicated in the IPv6 Address subfield802in little endian format.

FIG.9is a diagram illustrating an example format of the Negotiation Address subfield516, e.g., when the Negotiation Address Type is equal to 3 (or another suitable value indicating this). In some implementations, the Hostname Length subfield902indicates the length of the Hostname subfield, e.g., in octets. In some implementations, the Hostname subfield904indicates the host name for negotiating the extension of the eBCS service, e.g., in UTF-8 format. In some implementations, the Destination UDP Port subfield906indicates the UDP Port associated with the host name indicated in the Hostname subfield, e.g., in little endian format.

FIG.10is a diagram illustrating an example format of the Negotiation Address subfield516, e.g., when the Negotiation Address Type is equal to 4 (or another suitable value indicating this). In some implementations, the MPEG Transport Stream Length subfield1002indicates the length of the MPEG Transport Stream ID subfield1004, e.g., in octets. In some implementations, the MPEG Transport Stream ID subfield1004indicates the MPEG Transport Stream ID, e.g., in UTF-8 format.

Some implementations include an End of Broadcast Service Announcement indication Procedure. In some implementations, the End of Broadcast Service Announcement Indication Procedure for DL broadcast service may be as follows.

An AP may advertise a broadcast service using a Broadcast Service element in its beacon, probe responses, eBCS Service Advertisement frames, and/or eBCS info frames, etc. Some Broadcast Services may be allocated specific time and/or frequency resources. These time and frequency resources may be broadcast with certain periodicities.

A Broadcast Service may be requested by a STA which may be associated or unassociated with the AP, or by STAs that may request the broadcast service through other means, such as through IP protocols. When the Broadcast Service is being requested, a STA may request the Broadcast Service for a certain period of time. For example, the STA may request video playback for 10 minutes. STAs requesting the same or similar services may be grouped by the AP. Broadcast Service periodicities may be modified by the AP based upon explicit or implicit STA or STA group demand.

The AP may indicate the remaining time of a broadcast service that it is providing by including, (e.g., periodically) an End of Broadcast Service Announcement element, in one or more of frames that it is transmitting (e.g., in beacon frames, probe response frames, eBCS data frames, Broadcast Service Request frames, eBCS Service Advertisement frames, and/or eBCS Info frames, etc.)

The AP may indicate that one or more broadcast services that it is providing are ending at a given time, e.g., by including one or more End of Broadcast Service Announcement elements in one or more of frames that it is transmitting (e.g., in beacon frames, probe response frames, eBCS data frames, Broadcast Service Request frames, eBCS Service Advertisement frames, or eBCS Info frames, etc.) The AP may include a Negotiation Method needed for any STAs that are interested in the continuation of the broadcast service beyond the time of termination to conduct negotiation for the broadcast service beyond the indicated time of termination. The AP may indicate that one or more broadcast services that it is providing will be broadcast with specific periodicities before they end.

A STA that is utilizing a broadcast service, or plans to utilize a broadcast service, may receive one or more frames that may contain an End of Broadcast Service Announcement information, or element, for the broadcast service. If the STA desires to utilize the broadcast service beyond the indicated time of termination, it may follow the Negotiation Method indicated by the AP to conduct negotiations with the AP for the continuation of the broadcast service.

If a broadcast service requires association (e.g., as indicated in the Association Required subfield), and the Negotiation is through Broadcast Service Request frames, the STA may conduct an association procedure with the AP. If the STA is already associated with the AP, it may send a Broadcast Service Request frame indicating that it desires one or more broadcast service. The STA may indicate that it desires one or more broadcast service for a certain period of time or with a certain periodicity. The AP may respond with a Broadcast Service Response frame indicating that the broadcast service will be continued for an longer period of time and/or periodicity. If a second STA desires the same broadcast service, and it receives a frame containing an End of Broadcast Service Announcement element or information indicating that the broadcast service has been extended, it may cancel any pending Broadcast Service Request frames that it plans to send to the AP.

If a broadcast service does not require association (e.g., as indicated in the Association Required subfield), and the Negotiation is through ANQP/GAS Broadcast Service Request frames, the STA may send an ANQP/generic advertisement service (GAS) Broadcast Service Request frame indicating that it desires one or more broadcast service or register for one or more broadcast services. The STA may indicate that it desires, or may register for, one or more broadcast service for a certain period of time. The AP may respond with an ANQP/GAS Broadcast Service Response frame indicating that the broadcast service will be continued for an longer period of time. If a second STA desires the same broadcast service, and it received a frame containing an End of Broadcast Service Announcement element or information indicating that the broadcast service has been extended, it may cancel any pending ANQP/GAS Broadcast Service Request frames that it plans to send to the AP.

If a broadcast service does not require association (e.g., as indicated in the Association Required subfield), and the Negotiation is through IP protocols (e.g., IPv4 and IPv6 and with appropriate IP addresses), the STA may send an IP packet, possibly through another interface indicating that it desires one or more broadcast service or register for one or more broadcast services. The STA may indicate that it desires or register for one or more broadcast service for a certain period of time. The AP may send a ANQP/GAS Broadcast Service Response frame, or eBCS Info frame, or beacon frames or eBCS Service Advertisement frames or any other frames with an End of Broadcast Service Announcement frame, indicating that the broadcast service will be continued for an longer period of time. If a second STA desires the same broadcast service, and it received a frame containing an End of Broadcast Service Announcement element or information indicating that the broadcast service has been extended, it may cancel any pending IP packets requesting continued broadcast service.

Some implementations provide an eBCS Service Termination Notice Procedure. In some implementations, the eBCS Service Termination Notice Procedure allows a STA that is a broadcaster of eBCS services to indicate that one or more eBCS services that it is broadcasting is to be terminated. In some implementations, the eBCS Service Termination Notice Procedure allows a STA that is a broadcaster of eBCS services to indicate that one or more eBCS services that is broadcasting is to be terminated. In some implementations, the eBCS Service Termination Notice Procedure allows a STA to indicate that one or more eBCS services that one or more other STAs are broadcasting is to be terminated.

In some implementations, an eBCS STA that is the broadcaster of one or more eBCS services shall start to transmit eBCS Service Termination Notice frames if one or more eBCS Services that it is transmitting will terminate within an interval, e.g., that is equal to or shorter than a time, such as dot11eBCSTerminationNoticeTime, if the STA is not periodically transmitting a schedule for the eBCS services that are to be terminated. In some implementations, an eBCS STA shall start to transmit eBCS Service Termination Notice frames if one or more eBCS Services will terminate within an interval, e.g., that is equal to or shorter than a time, such as dot11eBCSTerminationNoticeTime, if the STA is not periodically transmitting a schedule for the eBCS services that are to be terminated. In some implementations, an eBCS STA shall start to transmit eBCS Service Termination Notice frames if one or more eBCS Services will terminate within an interval, e.g., that is equal to or shorter than a time, such as dot11eBCSTerminationNoticeTime. In some implementations, if the eBCS STA starts to transmit eBCS Service Termination Notice frames, the STA shall transmit the eBCS Service Termination Notice frames with a period, e.g., that is larger than a minimum interval, such as dot11eBCSTerminationNoticeMinimumInterval and smaller than a maximum interval, such as dot11eBCSTerminationNoticeMaximumInterval.

In some implementations, an eBCS STA transmitting an eBCS Service Termination Notice frame indicates in the Time to Termination subfield in a eBCS Service Termination Info subfield the number of TBTTs before the eBCS service identified by the eBCS Service ID contained in the eBCS Service ID subfield in the same eBCS Service Termination Info subfield terminates. In some implementation, the Time to Termination subfield may be indicated in other time format, such as ms, us, Time Units (TUs), or any other type of time units.

In some implementations, an eBCS STA transmitting an eBCS Service Termination Notice frame shall indicate in the Negotiation Method subfield in a eBCS Service Termination Info subfield the negotiation method that a STA should use to negotiate for the extension of the eBCS service identified by the eBCS Service ID contained in the eBCS Service ID subfield in the same eBCS Service Termination Info subfield. In some implementation, the eBCS STA may indicate that no negotiation is available.

In some implementations, an eBCS STA transmitting an eBCS Service Termination Notice frame may indicate in the Negotiation Address subfield in an eBCS Service Termination Info subfield the address associated with the negotiation method indicated in the Negotiation Method subfield in the same eBCS Service Termination Info subfield that a STA should use to negotiate for the extension of the eBCS service identified by the eBCS Service ID contained in the eBCS Service ID subfield in the same eBCS Service Termination Info subfield.

In some implementations, after transmitting a eBCS Service Termination Notice frame, an eBCS STA shall transmit an eBCS Service Termination Notice frame with an updated value in the Time to Termination subfield in an eBCS Service Termination Info subfield if the eBCS Service identified by the eBCS Service ID in the eBCS Service ID subfield in the same eBCS Service Termination Info subfield has been negotiated to another duration or with a new Time to Termination value. In some implementations, if the negotiated duration for the eBCS service is longer than the maximum Time to Termination subfield value, the transmitting STA shall set the Time to Termination subfield to 0. In some implementations, if the negotiated duration for the eBCS service is longer than the maximum Time to Termination subfield value, the transmitting STA shall set the Time to Termination to the maximum value of the Time to Termination subfield. In some implementations, if the negotiated duration for the eBCS service is longer than the maximum Time to Termination subfield value, the transmitting STA shall set the Time to Termination subfield to some specific value N.

In some implementations, after transmitting a eBCS Service Termination Notice frame, an eBCS STA shall transmit an eBCS Service Info frame or other type of frames with an updated value in the Time to Termination subfield or eBCS Service Duration subfield if the eBCS has been negotiated to another duration or with a new Time to Termination value.

In some implementations, an eBCS STA that receives an eBCS Service Termination Notice frame may negotiate for the extension of an eBCS service e.g., if the eBCS service indicated in one of the eBCS Service Termination Info subfield terminates earlier than desired. In some implementations, the eBCS STA may negotiate the extension of the eBCS service, e.g., using the negotiation method as indicated in the Negotiation Method in the eBCS Service Termination Info subfield and in some implementations may follow the procedures defined in 802.11 specifications, e.g., 11.22.6.x (eBCS Service Negotiation Procedure for Associated STAs) and 11.23.3.3 (ANQP Procedures).

In some implementations, an eBCS STA that receives an eBCS Service Info frame or any other time of frames may negotiate for the extension of an eBCS service e.g., if the eBCS service terminates earlier than desired. In some implementations, the eBCS STA may negotiate the extension of the eBCS service, e.g., using the negotiation method as indicated in the Negotiation Method in the eBCS Service Termination Info subfield and in some implementations may follow the procedures defined in 802.11 specifications, e.g., 11.22.6.x (eBCS Service Negotiation Procedure for Associated STAs) and 11.23.3.3 (ANQP Procedures).

In some implementations, an eBCS STA shall skip the transmission of any eBCS Service Request frame or a frame containing an Enhanced Broadcast Request ANQP-element or any frames that contains IP frames requesting an eBCS service if the STA receives an eBCS Service Termination Notice frame with an acceptable Time to Termination value or duration values contained in the eBCS Service Termination Info subfield containing the eBCS Service ID of the eBCS service, or contained in eBCS Service Info frame or other type of frames for the same eBCS service.

Some implementations include an End of Broadcast Service Announcement Indication Procedure with triggering mechanisms. In some implementations, after transmission, by an AP, of an end of broadcast service announcement indication (EBSAI) through management or control frame(s), or aggregated with any type of frame(s), a STAs which may intend to keep current services or negotiate new broadcast services may respond. More than one STAs may need to transmit response to EBSAI.

FIG.11is a signal diagram illustrating an example multiple access procedure. As shown inFIG.11, an AP may transmit a frame with EBSAI. The detailed frame format may be as described herein, e.g., regarding the end of broadcast service announcement information element and/or end of broadcast service announcement indication procedure.

The AP may expect one or more STA to transmit a response frame. The AP may transmit a trigger frame to trigger multiple access response transmission. In some implementations, the trigger frame may be transmitted an interframe space (xIFS) time after the frame with EBSAI. Here xIFS may refer to any existing interframe space or newly defined interframe space. In some implementations, the trigger frame may be aggregated with the frame with EBSAI. The trigger frame may indicate a trigger type in a trigger type field. The trigger type field may indicate a newly defined type, e.g., EBSAI, NDP, or Probe Request management frame trigger etc. Alternatively, the trigger type field may indicate an existing trigger type, e.g., basic trigger etc.

One or more STAs may transmit response to EBSAI, such that the STA may keep the originally negotiated broadcast services, may modify the originally negotiated broadcast services, e.g. to continue service beyond the time of termination, and/or may request to start a new broadcast negotiation for a certain period of time and periodicity.

The STAs may transmit the EBSAI response using one or more of an identical response method, a trigger based random access method, and/or a trigger based Probe Request method.

In an example identical response method, a common end of broadcast respond frame/field/element/PPDU may be defined, such that STAs which may intend to respond may transmit identical physical layer packets concurrently. The AP may be able to detect the concurrent transmissions from STAs, e.g., since they are identical.

In some implementations, e.g., of the identical response method, the STAs may be able to indicate single message (e.g., they prefer keeping the originally negotiated broadcast services). In some implementations, a null data packet (NDP) EBSAI response PPDU may be used for this kind of EBSAI response. The NDP EBSAI response PPDU may carry short training field (STF) and long training field (LTF) and signal training field (SIG) fields (In addition, legacy preamble fields may be prepended for backward compatibility). SIG fields may be modified to indicate that the STAs may prefer keeping the original negotiation. Alternatively, the SIG field may be omitted and the present NDP transmission may indicate the STAs prefer keeping the original setting. The PPDU may be transmitted xIFS after the trigger frame by one or more STAs. With this method, the STAs, which may like to terminate the broadcast service(s), may not need to respond and STAs, which may like to continue the broadcast service(s) may respond.

In some implementations, e.g., of the identical response method, the STAs may be able to carry several messages, (e.g., M messages.) Examples of such messages may include keeping the original negotiation, modifying the original negotiation, starting a new negotiation etc. In one design, a NDP EBSAI response PPDU may be used for this kind of EBSAI response. The NDP EBSAI response PPDU may carry STF and LTF and SIG fields (legacy preamble fields may be prepended for backward compatibility). Some of above mentioned fields may be transmitted in partial bandwidth. The location of the transmission may indicate the message it may carried. For example, the entire bandwidth may be partitioned to M chunks. If the STF and/or LTF and/or SIG field(s) may be transmitted over the first frequency chunk, it may indicate the first message. If the STF and/or LTF and/or SIG field(s) may be transmitted over the second frequency chunk, it may indicate the second message, and so on. The PPDU may be transmitted xSIF right after the trigger frame. In one method, the mapping of the frequency resources and message may be predefined and no signaling needed. In one method, the mapping of the frequency resources and message may be carried in the Trigger frame.

In an example trigger based random access method, one or more of resource units may be allocated for response transmission. The resource allocation may be included in the trigger frame. STAs may start an OFDMA random access procedure to select one or more resource units to transmit its own response frame. The response frame may be a normal MAC frame, which may carry a transmit (Tx) and/or receive (Rx) address, and other fields normally defined in a MAC header. Moreover, it may carry EBSAI response related information.

In an example trigger based probe request method, one or more of resource units may be allocated for this response transmission. The resource allocation may be included in the trigger frame. Unassociated STAs may use Probe Request management frames to select one or more resource units to transmit the frame. This response frame may contain additional information beyond what is currently available in these management frames to negotiate/renegotiate broadcast services.

Some implementations provide an eBCS Service Capability indication. In some implementations, an AP may include a eBCS Service Capability element in any frames that it transmits, such as a probe responses, beacon frames, eBCS Service Advertisement frames, eBCS Info frames, FILS Discovery frames, etc.

FIG.12is a bitmap diagram illustrating an example format of an eBCS Service Capabilities element. The eBCS Service Capabilities element may contain one or more the following subfields: Element ID subfield1202, Length subfield1204, Element ID Extension subfield1206, Sequence Number subfield1208, Number of Fragments subfield1210, Fragment Index subfield1212, DL Broadcast Capabilities subframe1214, Number of Broadcast Services subframe1216, eBCS 1-N subfields1218, Broadcast Info Control subfield1220, Broadcast ID subfield1222, eBCS subfield1224, Association Required subfield1226, UL Transmission Required subfield1228, Broadcast Parameters subfield1230, Broadcast Security subfield1232, Higher Layer Destination Address subfield1234, Title Present subfield1236, Title Length subfield1228, Title subfield1240, Time to Termination subfield1242, Broadcast Control subfield1244, and/or other subfields, e.g., as arranged inFIG.12or otherwise. Descriptions of examples of such subfields are as follows.

For the Element ID subfield1202, Length subfield1204, and Element ID Extension subfield1206, the combination of the Element ID and Element ID Extension may identify the current element as the DL Broadcast Capabilities element, or as DL eBCS element. The Length subfield1204may indicate the length of the element.

The Sequence Number subfield1208may indicate the sequence number of the eBCS Service Capabilities element

The Number of Fragments: subfield1210may indicate the number of fragments that the eBCS Capabilities element identified by the Sequence Number may be partitioned into.

The Fragment Index subfield1212may indicate the index of the fragment of the eBCS Capabilities element that is contained in the current eBCS Capabilities element.

The eBCS 1-N subfields1218may include N subfields which may be contained in the Broadcast element where each field may be used to specify a particular Broadcast service that is provided by the transmitting STA, e.g., the transmitting AP. Each eBCS field may contain one or more of the following subfields: Broadcast Info Control subfield1220; Broadcast ID subfield1222; eBCS Type subfield1224; Association Required subfield1226; UL Transmission Required subfield1228; Broadcast Parameters subfield1230; and/or Broadcast Security subfield1232.

The Broadcast Info Control subfield1220may be 1 byte in length and may contain indications whether certain broadcast information is contained in the eBCS N field. The Broadcast ID subfield1222may be 1 bit of length and indicate whether Broadcast ID is included in the eBCS N field.

The Higher Layer Destination Address subfield1234may be three bits in length and may indicate one of the following values: Higher Layer Destination Address not present, Higher Layer Destination Address present in the eBCS N field, and that the Higher Layer protocol may include: UDP/IPv4; UDP/IPv6; UDP/Hostname; MPEG Transport Stream identifier; MAC Address; and/or Reserved. The Title Present subfield1236may be one bit in length and may indicate whether an user readable title is present in the eBCS N field. If the Title Present bit is set to 1, then a Title Length subfield1238and a Title subfield1240may be included in the eBCS N field. A Broadcast Control Present subfield may be 1 bit in length and may indicate whether the Negotiation Method subfield is included in the eBCS N field.

The Broadcast ID subfield1222may indicate the ID of the Broadcast service. The eBCS Type subfield1224may include the type of broadcast service, e.g., whether the eBCS is UL or DL, or whether the broadcast service is of the category of automotive, direction, emergency, support, informational, event_support. In some implementations, a bitmap may be included in the DL Broadcast element to indicate which types of broadcast service are provided by the transmitting STAs. The type may also be multi-AP broadcast. In some implementations, the broadcast type may be identified by an organizationally unique identifier (OUI).

The Association Required subfield1226may indicate whether association is needed to consume one or more broadcast service, e.g., the broadcast service identified by the Broadcast ID. The UL Transmission Required subfield1228may indicate whether UL transmission is required to consume one or more broadcast service, e.g., the broadcast service identified by the Broadcast ID.

The Broadcast Control subfield1244may indicate how to control the broadcast service. For example, it may indicate that if a STA desires a certain broadcast service, it needs to directly negotiate with the transmitting STA, e.g., the transmitting AP, by using e.g., Broadcast Request frame. In another example, the subfield may indicate a server address, e.g., an IP address of the server, or a controller address, e.g., a MAC address or BSSID of another AP. Such a controller AP may be the master AP of a multi-AP set. The STA may also communicate with the controller or server to provide feedback of the broadcast service or negotiate rates, or encoding. The method for control may be through WLAN, TCP/IP, Broadcast Request negotiation, ANQP or GAS frame exchanges, etc. The Broadcast Parameters subfield may include one or more broadcast parameters, e.g., including Offset and/or Channel. For example, the offset of the start of the next broadcast packet, or broadcast bursts, which may be from the end of the current transmission, or from a target beacon transmission time (TBTT) or other reference points. The channel may include the channel or OFDMA subchannels or resource units (RUs) on which the broadcast service packets may be available.

The Higher Layer Destination Address subfield1234may take different lengths depending on the value indicated in the Higher Layer Protocol field of the Broadcast Service Info Control subfield1220. The Higher Layer Destination Address subfield1234may contain the IP address and UDP port if IPv4/UDP or IPv6/UDP is indicated in the Higher Layer Protocol field. The Higher Layer Destination Address subfield1234may contain MAC address of 6 bytes, e.g., if the MAC address is indicated in the Higher Layer Protocol subfield. The Higher Layer Destination Address may not be included in the Broadcast Service Field if the Higher layer Protocol subfield indicates that no Higher Layer Destination Address field is present.

The Title Length subfield1238may be included in the Broadcast Service field, e.g., if the Title Present subfield1236in the Broadcast Service Info Control subfield is set to 1; otherwise it is not present. The Title Length field may be 1 byte in length and indicates the length of the Title subfield1240.

The Title subfield1240may be included in the Broadcast Service field, e.g., if the Title Present subfield1236in the Broadcast Service Info Control subfield is set to 1; otherwise it may not be present. The Title Length field may be 1 byte in length and may indicate the length of the Title subfield1240.

The Time to Termination subfield1242may be used to indicate the remaining time left at which the Broadcast Service described in this Broadcast Service field will terminate unless additional negotiation is conducted by the initiator of the broadcast service or by other users of the said Broadcast Service. In some implementations, the subfield may include a time (e.g., a TSF time value, or other type of time) at which the said Broadcast Service will terminate unless additional negotiation is conducted by the initiator of the broadcast service or by other users of the said Broadcast Service. Additionally or alternatively, a Timestamp of current time, such as the current value of the TSF timer may be included.

The Broadcast Control subfield1244may be included in the eBCS N field, e.g., if the Broadcast Control Present subfield is set to 1 in the Broadcast Info Control subfield1220. The Broadcast Control subfield1244may be used to indicate the negotiation method that should be used to negotiate for the initialization, control or stop of the broadcast service. The Broadcast Control subfield1244may include one or more of the following values: Through Broadcast Service Request frames; Through ANQP/GAS Broadcast Service Request frames; and/or Through IP Request (in this case, the IP version and IP addresses that are needed for negotiation may be included.)

In some implementations, any subset of fields or subfields of the eBCS Service Capabilities element or eBCS Service Advertisement frame may be implemented in any field or subfield or a set or subset of fields of existing or newly designed elements or frames, or PHY and/or MAC headers of any management, control, and data frames, or other headers, or other frames.

Some implementations include an eBCS Service Request frame format. In some implementations, the eBCS Service Request frame format may be defined as follows. The eBCS Service Request frame may include a eBCS Service Request element. Such eBCS Service Request element may also be included in other frames such as Probe Request frames, Association request frames, ANQP/GAS eBCS Service Request frames, or any other type of frames, e.g., to request one or more eBCS Services.

FIG.13is a bitmap diagram illustrating an example format of an eBCS Service Request element. As shown inFIG.13, in some implementations, an eBCS Service Request element may contain one or more of the following fields: Element ID1302, Length1304, Element ID Extension1306, Number of Broadcast Service fields1308, and/or one or more of Broadcast Service fields1310.

The Element ID field1302, Length field1304, and Element ID Extension field1306may be used to indicate that the current element is an eBCS Service request element and the length of the current element.

The Number of Broadcast Service fields field1308may be used to indicate the number of Broadcast Service fields that the element includes.

In the one or more of Broadcast Service fields1310, each of the Broadcast Service fields1310contains the information of a particular Broadcast Service being requested, and may include the following subfields: Broadcast Service Info Control field subfield1312, Broadcast Service ID subfield1314, Higher Layer Destination Address subfield1316, Title Length subfield1318, Title subfield1320, Requested Duration subfield1322, and/or Requested Parameters subfield1324.

The Broadcast Service Info Control Field subfield1312may be 1 byte in length and may include indications of whether certain broadcast information is contained in the Broadcast Service Field1310. The Broadcast Service ID subfield1314may be 1 byte in length and may be used to indicate the identifier of the Broadcast Service. The Higher Layer Destination Address subfield1316may be of variable bit length depending on the value indicated in the Higher Layer Protocol field of the Broadcast Service Info Control subfield1312. The Higher Layer Destination Address subfield1316may contain the IP address and UDP port if IPv4/UDP or IPv6/UDP is indicated in the Higher Layer Protocol field. It may contain MAC address of 6 bytes if MAC address is indicated in the Higher layer Protocol subfield. The Higher Layer Destination Address is not included in the Broadcast Service Field if the Higher layer Protocol subfield1316indicates that no Higher Layer Destination Address field is present.

The Title Length subfield1318may be included in the Broadcast Service field1310if the Title Present subfield in the Broadcast Service Info Control subfield is set to 1; otherwise it is not present. The Title Length field1318may be 1 byte in length and indicates the length of the Title Field. The title subfield1320may be included in the Broadcast Service field if the Title Present subfield1406in the Broadcast Service Info Control subfield1312is set to 1; otherwise it is not present. The Title Length subfield1318may be 1 byte in length and indicates the length of the Title subfield1320. The Title subfield may be of variable byte length.

The Requested Duration subfield1322may be 1 byte in length and may be used to indicate the requested duration of the requested Broadcast service. The Requested Parameters subfield1324may be 1 byte in length and may indicate the requested parameter for the requested broadcast service, such as time offset compared to a fixed time reference point (e.g. TBTT), channel, RU resource, band, broadcast rate, etc.

FIG.14is a diagram illustrating an example format of the Broadcast Service Info Control Field subfield1312. The Broadcast Service Info Control Field subfield1312may include a Broadcast Service ID Present subfield1402, Higher Layer Protocol1404subfield, Title Present subfield1406, Requested Duration Present subfield1408, and Requested Parameter Present subfield1410. The Broadcast Service Info Control Field subfield1312may also have a reserved subfield1412.

The Broadcast Service ID Present subfield1402may be 1 bit in length and may indicate whether a Broadcast Service ID is included in the Broadcast Service Field1310. The Higher Layer Protocol subfield1404may be three bits in length and may indicate one of the following values: Higher Layer Destination Address not present, Higher Layer Destination Address not present, and/or Higher Layer Destination Address present in the Broadcast Service Field1310. The Higher Layer Protocol subfield1404may include: UDP/IPv4, UDP/IPv6, UDP/Hostname, MPEG Transport Stream identifier, and/or MAC Address. The Title Present subfield1406may be one bit in length and is used to indicate whether an user readable title is present in the Broadcast Service Field1310. If the Title Present bit is set to 1, then a Title Length subfield and a Title subfield may be included in the Broadcast Service field1310. The Negotiation Method Present subfield: this subfield may be 1 bit in length and may be used to indicate whether the Negotiation Method subfield is included in the Broadcast Service Field.

A Requested Duration Present subfield1408may be 1 bit in length and may indicate whether the Requested Duration for the requested Broadcast Service is present in the Broadcast Service Field1310. A Requested Parameters Present subfield1410may be 1 bit in length and may indicate whether the Requested Parameters for the requested Broadcast Service is present in the Broadcast Service Field1310.

In some implementations, any subset of fields or subfields of the eBCS Service Request element may be implemented in any field or subfield or a set or subset of fields of existing or newly designed elements or frames, or PHY and/or MAC headers of any management, control, data frames, or other headers, or other frames, such as EBCS Request frames.

Some implementations include an eBCS Service Response frame format. In some implementations, the eBCS Service Response frame format may be as follows. The eBCS Service Response frame may include a eBCS Service Response element. Such eBCS Service Response element may also be included in other frames such as Probe Response frames, Association response frames, ANQP/GAS eBCS Service Response frames, or any other type of frames to respond to one or more eBCS Services requests.

FIG.15is a bitmap diagram illustrating an example format of an eBCS Service Response element. In some implementations, the eBCS Service Response element may include one or more of the following fields: Element ID field1502, Length field1504, Element ID Extension field1506, Number of Broadcast Service Fields field1508, and/or one or more Broadcast Service Fields fields1510.

The Element ID field1502, Length field1504, and Element ID Extension field1506may indicate that the current element is an eBCS Service response element and the length of the current element. The Number of Broadcast Service Fields field1510may indicate the number of Broadcast Service fields that the element includes.

Each of the one or more of Broadcast Service fields1510may include the response information of a particular Broadcast Service being requested, and may include one or more of a Broadcast Service Info Control field1512, Broadcast Service ID field1514, Higher Layer Destination Address subfield1516Title Length field1518, Title field1520, Status field1522, Broadcast Service Duration field1524, and/or Broadcast Service Parameters field1526.

The Broadcast Service Info Control field1512may be 1 byte in length and may include indications of whether certain broadcast information is contained in the Broadcast Service Field field1510.

FIG.16illustrates an example format of the Broadcast Service Info Control subfield1512. As shown inFIG.16, the Broadcast Service Info Control field1512may include a Broadcast Service ID Present subfield1602, Higher Layer Protocol subfield1604, Title Present subfield1606, Broadcast Service Duration Present subfield1608, Broadcast Service Parameter Present subfield1610, and/or Reserved subfield1612.

The Broadcast Service ID Present subfield1602may be 1 bit in length and indicate whether Broadcast Service ID is included in the Broadcast Service Field. The Higher Layer Protocol subfield1604may be three bits in length and may indicate, for example, one or more of the following values: Higher Layer Destination Address not present, Higher Layer Destination Address present in the Broadcast Service Field (The Higher Layer protocol may be and/or be indicated as: UDP/IPv4, UDP/IPv6, UDP/Hostname, MPEG Transport Stream identifier, MAC Address, and/or Reserved).

The Title Present subfield1606may be one bit in length and may indicate whether an user readable title is present in the Broadcast Service Field1510. If the Title Present bit is set to 1, then a Title Length subfield1518and a Title field1520may be included in the Broadcast Service field1510.

The Broadcast Service Duration Present subfield1608may be 1 bit in length and may indicate whether the Broadcast Service Duration for the offered Broadcast Service is present in the Broadcast Service Field1510. The Broadcast Service Parameters Present subfield1610may be 1 bit in length and may indicate whether the Broadcast Service Parameters for the requested Broadcast Service is present in the Broadcast Service Field1510.

Referring back toFIG.15, the Broadcast Service ID field1514may indicate the identifier of the Broadcast Service, and may be 1 byte in length. The Higher Layer Destination Address subfield1516may have different lengths, e.g., depending on the value indicated in the Higher Layer Protocol field of the Broadcast Service Info Control subfield. The Higher Layer Destination Address subfield1516may include the IP address and UDP port if IPv4/UDP or IPv6/UDP is indicated in the Higher Layer Protocol subfield1604. The Higher Layer Destination Address subfield1516may include a MAC address, e.g., of 6 bytes, e.g., if MAC address is indicated in the Higher layer Protocol subfield1604. The Higher Layer Destination Address may not be included in the Broadcast Service Field1510, e.g., if the Higher layer Protocol subfield indicates that no Higher Layer Destination Address field is present. The Title Length subfield1518may be included in the Broadcast Service field1510, e.g., if the Title Present subfield1606in the Broadcast Service Info Control subfield1512is set to 1; otherwise it may not be present. The Title Length field1518may be 1 byte in length and may indicate the length of the Title subfield1520. The Title subfield1520may be included in the Broadcast Service field1510, e.g., if the Title Present subfield in the Broadcast Service Info Control subfield1512is set to 1; otherwise it may not be present.

The Status subfield1522may indicate whether the request for the broadcast service is successful. The Status subfield may also contain the reason for rejection if a request is rejected. The Broadcast Service Duration subfield may indicate the duration of the provided Broadcast service. The Broadcast Service Parameters subfield may indicate the parameter for the provided broadcast service, such as time offset compared to a fixed time reference point (e.g. TBTT), channel, RU resource, band, broadcast rate, etc.

In some implementations, any subset of fields or subfields of the eBCS Service Response element may be implemented in any field or subfield or a set or subset of fields of existing or newly designed elements or frames, or PHY and/or MAC headers of any management, control, data frames, or other headers, or other frames, such as EBCS Request frames

Some implementations include an eBCS Service Request/Response Procedure. Some implementations include an eBCS Service Request/Response Procedure for unassociated STAs. In some implementations, the eBCS Service Negotiation Procedure for unassociated STAs may be as follows.

In some implementations, an AP may advertise one or more broadcast service, e.g., using a Broadcast Service element in its beacon, probe responses, eBCS Service Advertisement frames, eBCS info frames, etc., and/or simply using probe responses, eBCS Service Advertisement frames, eBCS info frames, or EBCS Termination Notice frame, etc. The AP may indicate the negotiation method for one or more eBCS services, such as through ANQP/GAS frame exchanges, through Probe Request frames, through eBCS Service Request/response frames, or through IP packets.

An unassociated STA may discover a desired broadcast service either after receiving a frame from the AP, such as a EBCS info frames, EBCS Termination Notice frame, or EBCS ANQP Service frames, or from pre-acquired knowledge, or through ANQP/GAS frame exchanges from one or more APs. One or more Broadcast Services, which the AP is capable to provide but is currently not providing, which do not require association, may be requested by the STA. The STA may follow a negotiation method, e.g., as indicated by the AP for that eBCS service and may send a frame to the AP, such as a ANQP/GAS Broadcast Service request frame, or a public action frame containing eBCS Service Request element or information. The requested broadcast service may be indicated by certain IDs such as Broadcast Service ID, Higher Layer Destination Address, MAC address, Title, etc. When the Broadcast Service is being requested, a STA may request the Broadcast Service for a certain period of time, for example, the STA may request video playback for 10 minutes. The STA may also request certain parameters for the broadcast services, such as broadcast frequency, data rate used, to be on a particular channel or RU.

The AP may respond to a eBCS Service Request by sending a eBCS Response frame, or an ANQP/GAS eBCS Service Response frame, or a frame including an eBCS Service Response frame or information. The AP may indicate the status of the request for one or more eBCS Service, such as successful or reject, and it may include a reason for rejection if the request is rejected. The AP may indicate the remaining time of a broadcast service that it is providing. For example, the AP may include Broadcast Service Duration in the eBCS Service Response element, or include, e.g., periodically, an End of Broadcast Service Announcement element, in one or more of frames that it is transmitting, for example, in beacon frames, probe response frames, eBCS data frames, Broadcast Service Request frames, eBCS Service Advertisement frames, or eBCS Info frames, etc. The AP may also include Broadcast Service parameters if the request for the eBCS Service is successful, such as broadcast frequency, data rate used, to be on a particular channel or RU. The AP may thereafter start providing the requested eBCS services accordingly.

Some implementations include an eBCS Service Request/Response Procedure for associated STAs. In some implementations, the eBCS Service Negotiation Procedure for associated STAs may be as follows. An AP may advertise one or more broadcast services, e.g., using a Broadcast Service element in its beacon, probe responses, eBCS Service Advertisement frames, eBCS info frames, etc., or simply using probe responses, eBCS Service Advertisement frames, eBCS info frames, EBCS Termination Notice frame, etc. The AP may indicate the negotiation method for one or more eBCS services, e.g., through ANQP/GAS frame exchanges, through Probe Request frames, through eBCS Service Request/response frames, and/or through IP packets. The AP may indicate for one or more eBCS services that association is required to utilize those eBCS services.

A STA may discover a desired broadcast service either after receiving a frame from the AP, sucj as EBCS Info frame, EBCS Termination Notice frame, or EBCS ANQP Service frames, or from pre-acquired knowledge, and/or through ANQP/GAS frame exchanges from one or more APs. One or more Broadcast Services which the AP is capable to provide but is currently not providing, which require association, may be requested by the STA. If the STA is currently unassociated with the AP, the STA may conduct authentication and association with the AP. The STA may follow a negotiation method indicated by the AP for that eBCS service and may send a frame to the AP, such as an eBCS Service request frame, or a frame containing eBCS Service Request element or information, which may also be contained in the Probe Request frame and/or Association Request frame. The requested broadcast service may be indicated by certain IDs such as Broadcast Service ID, Higher Layer Destination Address, MAC address, Title, etc. When the Broadcast Service is being requested, a STA may request the Broadcast Service for a certain period of time. For example, the STA may request video playback for 10 minutes. The STA may also request certain parameters for the broadcast services, such as broadcast frequency, data rate used, to be on a particular channel or RU.

The AP may respond to a eBCS Service Request by sending a eBCS Response frames, or a frame containing an eBCS Servie Response frame or information, including probe response and association response frames. If a eBCS service requires association, the AP may not start the eBCS (enhanced Broadcasting service) service before the STA is fully associated with the AP. The AP may indicate the status of the request for one or more eBCS Service, such as successful, denied and it may include the rejection reasons. The AP may indicate the remaining time of a broadcast service that it is providing. For example, the AP may include Broadcast Service Duration in the eBCS Service Response element, or include, e.g., periodically, End of Broadcast Service Announcement element, in one or more of frames that it is transmitting, for example, in beacon frames, probe response frames, eBCS data frames, Broadcast Service Request frames, eBCS Service Advertisement frames, or eBCS Info frames, EBCS Termination Notice frame, etc. The AP may also include Broadcast Service parameters if the request for the eBCS Service is successful, such as broadcast frequency, broadcast Service Period duration, data rate used, to be on a particular channel or RU. The AP may thereafter start providing the requested eBCS services accordingly.

Some implementations include an eBCS Service Request/Response Procedure for receive-only STAs. In some implementations, the eBCS Service Negotiation Procedure for receive-only STAs is as follows. An AP may advertise one or more broadcast service using a Broadcast Service element in its beacon, probe responses, eBCS Service Advertisement frames, eBCS info frames, etc., and/or simply using probe responses, eBCS Service Advertisement frames, eBCS info frames, etc. The AP may indicate a negotiation method for one or more eBCS services, such as through ANQP/GAS frame exchanges, through Probe Request frames, through eBCS Service Request/response frames, and/or through IP packets. The AP may indicate for one or more eBCS services that association is required to utilize those eBCS services.

A STA may discover a desired broadcast service either after receiving a frame from the AP, such as EBCS Info frame, EBCS Termination Notice frame, or EBCS ANQP Service frame, or from pre-acquired knowledge, and/or by overhearing ANQP/GAS frame exchanges from one or more APs. One or more Broadcast Services, which require uplink transmissions or associations, may not be requested by receive-only STAs. The receive-only STA may follow the negotiation method as indicated by the AP for that eBCS service and may send, for example, an IP packet through a different network interface to the advertised IP address containing eBCS Service Request element or information.

If the request is successful, the AP may start providing the requested eBCS services accordingly. The AP may indicate the remaining time of a broadcast service that it is providing. For example, the AP may include, e.g., periodically, an End of Broadcast Service Announcement element in one or more of frames that it is transmitting (e.g., in beacon frames, probe response frames, eBCS data frames, Broadcast Service Request frames, eBCS Service Advertisement frames, EBCS Termination Notice frame, and/or eBCS Info frames, etc.).

Although the features and elements of the various examples above are described in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention. Although the solutions described herein consider 802.11 specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

Although xIFS and/or SIFS are used to indicate various inter frame spacing in the examples of the designs and procedures, all other inter frame spacing such as RIFS, AIFS, DIFS or other agreed time interval may be applied in the same solutions. Although four RBs per triggered TXOP are shown in some figures as example, the actual number of RBs/channels/bandwidth utilized may vary.

FIG.17illustrates an exemplary method1700of a STA requesting a continuation of an eNCS service. At step1702, the STA may first receive an eBCS termination notice frame, from an access point (AP), indicating that an eBCS service that the STA is consuming will be terminated. At step1704, the STA, on a condition that the termination is not acceptable, may negotiate for a continuation of the eBCS service. Then, at step1706, upon successfully negotiating a continuation of the eBCS service, the STA may continue to receive the eBCS service. The various steps described with respect to method1700are only examples, and it is noted that other implementations omit some of these steps, include additional steps, or perform these steps in a different order.