1 / 8

Discussion on Functional Requirements

Discussion on Functional Requirements. Date: 2019-07-09. Authors:. Abstract. In this contribution, we discuss functional requirements for AP to advertise eBCS capabilities and/or services. Introduction (1/2).

cecilg
Download Presentation

Discussion on Functional Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Discussion on Functional Requirements • Date: 2019-07-09 Authors: Xiaofei Wang (InterDigital)

  2. Xiaofei Wang (InterDigital) Abstract In this contribution, we discuss functional requirements for AP to advertise eBCS capabilities and/or services.

  3. Introduction (1/2) • 802.11bc has agreed to have the following requirements regarding (eBCS) discovery [1] • TGbc R3.5.1: 802.11bc amendment shall have a mechanism to facilitate discovery of 11bc-capable STAs. • TGbc R3.5.2: 802.11bc amendment shall have a mechanism to facilitate the discovery of STAs consuming a particular broadcast service. • The requirements above seem to aim at non-AP STA side Xiaofei Wang (InterDigital)

  4. Introduction (2/2) • In addition, there are proposals to add the following requirements regarding (eBCS) discovery [2] • TGbc R3.5.1: The 802.11bc amendment shall have a mechanism to facilitate discovery of 11bc-capable STAs. • TGbc R3.5.1.1: The 802.11bc amendment shall describe the use of an extended capability bit to indicate eBCS capability. • TGbc R3.5.2: The 802.11bc amendment shall have a mechanism to facilitate the discovery of STAs consuming a particular broadcast service. • TGbc R3.5.2.1 The 802.11bc amendment shall describe a query/response mechanism for eBCS services. • TGbc R3.5.2.2 The 802.11bc amendment shall be capable of indicating 0, 1, or multiple eBCS services within an eBCS response frame/message. • However, some of the eBCS AP related discovery seems to be missing Xiaofei Wang (InterDigital)

  5. The benefit for eBCS AP to indicate eBCS services in certain scenarios (1/2) • Stadium video distribution • There may be a class of STAs that cannot transmit. In order to utilize eBCS service • Option 1: all information of eBCS service and candidate eBCS APs must be loaded in firmware • Option 2: eBCS may announce that they are capable of eBCS service and what types of eBCS services are provided • Option 2 may provide more implementation and operation flexibility • Many other scenarios including ITS, multi-channel/multi-lingual/emergency broadcast, etc • An eBCS AP announcing its eBCS services may speed up the process of set up eBCS service Xiaofei Wang (InterDigital)

  6. The benefit for eBCS AP to indicate eBCS services in certain scenarios (2/2) • UL Sensor Broadcast • eBCS APs indicating that they provide UL Sensor Broadcast service may improve reliability of uplink broadcast Xiaofei Wang (InterDigital)

  7. Proposed Update to functional requirement document • TGbc R3.5.3: The 802.11bc amendment shall have a mechanism for eBCS APs to advertise their eBCS capabilities and eBCS services provided. Xiaofei Wang (InterDigital)

  8. Xiaofei Wang (InterDigital) References [1] IEEE 11-19/151r3, 802.11bc Functional Requirements Document, June 2019 [2] IEEE 11-19/1001r1, Functional Requirements Document Proposed Update, July 2019

More Related