1 / 4

Use Case Document: AP tagged UL forwarding

Use Case Document: AP tagged UL forwarding. Date: 2019-05-14. Authors:. Abstract. This presentation provides an additional use case scenario to be incorporated into TGbc use case document (11-19/0 268) and updating the TGbc Functional Requirements document (11-19/0151). Stakeholders

rmartin
Télécharger la présentation

Use Case Document: AP tagged UL forwarding

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. Use Case Document: AP tagged UL forwarding • Date: 2019-05-14 Authors: Abhishek Patil (Qualcomm)

  2. Abhishek Patil (Qualcomm) Abstract This presentation provides an additional use case scenario to be incorporated into TGbc use case document (11-19/0268) and updating the TGbc Functional Requirements document (11-19/0151).

  3. Abhishek Patil (Qualcomm) Stakeholders IoT Users, IoT operators, tracking services, etc Manufactures of semiconductor, APs, networking and mobile devices Use Case xx: AP tagged UL forwarding Topology/Architecture • Required function • Pre-configured low-cost low power tracker device automatically connects to an end server through eBCS APs in the neighborhood with zero setup action • Tracker device periodically reports to its server through eBCS APs without scanning and association • eBCS AP appends metadata (such as IP, date/time, location, RSSI etc) to the packets before forwarding to the destination server • Meta-data from an eBCS AP will be protected • Service scene • An eBCS AP provides forwarding service to an end-servers for eBCS non-AP STAs that may not be associated with the AP • An eBCS AP appends on additional information before forwarding the packet to the addressed server • Expected Benefits: • Ability to broadcast information destined to the end server • Ability to reduce cost and implementation complexity • Ability to enable low power STA operations

  4. Additions to Functional Requirements document • 3.4 Association state • TGbc R6: The 802.11bc amendment shall support modes of operation: • a) in an infrastructure BSS where there is an association between the transmitter and the receiver(s) • b) in cases where there is no association between transmitter(s) and receiver(s). [Ref-1 5.2.b] • TGbc R7: 802.11bc amendment shall have a mechanism to facilitate power-efficient broadcasting. • TGbc R8: 802.11bc amendment assumes that there is no association and/or handshake required between STA and the AP. • TGbc Rx: 802.11bc amendment shall provide a mechanism for an AP to append metadata (such as IP address, date, time, location, RSSI) to a packet before forwarding it to a remote server • 3.3 Security • TGbc R3: The 802.11bc amendment shall provide origin authenticity protection for broadcast data frames. [Ref-1 5.2.b] • TGbc R4: The 802.11bc amendment shall provide a broadcast mechanism in which e2e security w/ confidentiality and integrity between STA and the server is assumed. • TGbc R5: The 802.11bc amendment shall provide a mechanism for the AP to verify the STA before forwarding the packets. • TGbc Rx: The 802.11bc amendment shall provide a mechanism in which e2e security w/ confidentiality and integrity between AP and the remote server is achieved Abhishek Patil (Qualcomm)

More Related