1 / 8

Device Collectives to Share Resources

Device Collectives to Share Resources. Authors:. Date: 2011-05-11. Abstract.

victor-rich
Télécharger la présentation

Device Collectives to Share Resources

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. Dwight Smith, Motorola Mobility Device Collectives to Share Resources Authors: Date: 2011-05-11

  2. Dwight Smith, Motorola Mobility Abstract A proposal is presented that collects logical groups of devices and permits them to share resources needed to utilize the Wi-Fi network. This will help contain the growth in AID allocations as well as assist with some issues raised with extreme low-power, low activity devices seeking service through the network.

  3. Dwight Smith, Motorola Mobility Use Case and Associated Issues • A utility company wants to deploy a large number of low-power meters in a given area. They will be common units and seek to report back to a fixed utility-operated server on a periodic basis. Infrequently, the utility may want to send some data to one/some/all devices to set configuration or other data maintained in the devices. • The devices could consume a large number of Association Ids (AID) if they maintain an association or could need to associate every time they wake to send in a report. • If the devices hold the association, they would normally be expected to hold their IP address assigned as well (potentially large pool needed – seldom used). • If devices need to associate every time they need to send in a report, they would then use more power and be more difficult to reach when the utility wants to send them some data as they would tend to have no means to be engaged.

  4. Dwight Smith, Motorola Mobility Proposal – Group Devices and Share Resources • When a utility plans a deployment, they would likely execute a Service Agreement. From that, a logical group of devices could be identified and they could then share resources within the Wi-Fi service area. • When the devices make an association, they could identify that they are part of a special group. • Could use some identifier tied to the utility doing the deployment • Consequently, they could share a single AID – as each identifies itself, the ESS recognizes the support info and the AP hands each the allocated AID. • To assist with low power operation, and to conserve IP assignments from the DHCP system, they could similarly share an IP address. • The ESS could actually hold the assigned IP address and provide message delivery support. • Some entity in the ESS could collect the data packets from the devices (over time, till buffer full, etc) and then send the data using a simple delivery scheme (TCP/HTTP) to the fixed utility server. • The ESS could also use the AID flag in each AP beacon to signal the devices in the group that the utility system is trying to send them data. • Instead of holding AID till message read – the AP would keep the AID bit ‘on’ for some agreed time interval (presumably longer than the normal sleep interval) to permit all devices to do a read in a ‘come and get it’ approach. • The data presented to the device could include common data elements as well as data intended for specific units (e.g. To turn service for a specific subscriber on or off). • Call the feature something like Device Collective (‘group’ is overused)

  5. Dwight Smith, Motorola Mobility Example Signaling – Association Request

  6. Dwight Smith, Motorola Mobility Example Signaling – Send Data

  7. Dwight Smith, Motorola Mobility Example Signaling – Receive Data

  8. Dwight Smith, Motorola Mobility Potential Impact Areas • Anticipated Areas of Impact in 11ah • May want to indicate feature support in Beacon – Collective IE • May want to add elements to (re)Association Request/response to carry info about associated system (to tie devices in collective together) • Support response codes for collective status, ‘data accepted for delivery’ • May want to provide some info for collective delivery block (version, remaining time or such) to avoid having devices read a block more than once. • Other Impacts • ESS to Utility system would benefit from a well defined interface (ensure parameters are consistently carried). Could be based on other gateway protocols. • ESS may want to align support across related APs – could allocate a common AID over the network and then when devices awake they would be able to send to any AP in the ESS.

More Related