1 / 21

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

IEEE-802-15-11-0731-01-0ptc. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ Introduction to IEEE 802.15 Positive Train Control Interest Group ] Date Submitted: [ 13 October, 2011 ] Source: [ Jon Adams ] Company [ Independent ]

shadow
Download Presentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

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. IEEE-802-15-11-0731-01-0ptc Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title:[Introduction to IEEE 802.15 Positive Train Control Interest Group] Date Submitted: [13 October, 2011] Source:[Jon Adams] Company [Independent] Address [12023 N 62nd St, Scottsdale AZ, 85254 USA] Voice:[+1 415.683.0213], FAX: [Add FAX number], E-Mail:[jonadams@ieee.org] Re: [If this is a proposed revision, cite the original document.] [If this is a response to a Call for Contributions, cite the name and date of the Call for Contributions to which this document responds, as well as the relevant item number in the Call for Contributions.] [Note: Contributions that are not responsive to this section of the template, and contributions which do not address the topic under which they are submitted, may be refused or consigned to the “General Contributions” area.] Abstract:[Overview of the PTC-IG, the goals, the IEEE process and schedule. ] Purpose:[Intention of this document is to inform the newly formed PTC-IG of the goals and process.] Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15. NOTE: Update all red fields replacing with your information; they are required. This is a manual update in appropriate fields. All Blue fields are informational and are to be deleted. Black stays. After updating delete this box/paragraph. Jon Adams, Independent

  2. Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. • Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2]: • “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents • “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims • “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) • The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group • Early identification of holders of potential Essential Patent Claims is strongly encouraged • No duty to perform a patent search Slide #1

  3. Patent Related Links All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: IEEE-SA Standards Boards Bylaws http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/develop/policies/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/about/sasb/patcom/materials.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/about/sasb/patcom/index.html This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt Slide #2

  4. Call for Potentially Essential Patents • If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: • Either speak up now or • Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or • Cause an LOA to be submitted Slide #3

  5. Other Guidelines for IEEE WG Meetings • All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. • Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. • Don’t discuss specific license rates, terms, or conditions. • Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. • Technical considerations remain primary focus • Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. • Don’t discuss the status or substance of ongoing or threatened litigation. • Don’t be silent if inappropriate topics are discussed … do formally object. --------------------------------------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Slide #4

  6. IEEE-802-15-11-0731-01-0ptc Inaugural Telecon STDS-802-15-PTC Interest Group Jon Adams Independent Interim Chair Jon Adams, Independent

  7. IEEE-802-15-11-0731-01-0ptc • Introductions • Roll Call - please email (either during or shortly after themeeting) your attendance to me: jonadams@ieee.org • Reminder of IEEE P&P and Patent Policy and call for PotentiallyEssential Patents. Please see http://grouper.ieee.org/groups/802/15/pub/Rules.html and http://standards.ieee.org/board/pat/pat-slideset.ppt before the call. • Efforts to pursue before November IEEE Atlanta meeting • Reminder of dates for registration and hotel availability • Scheduling of sessions at Atlanta • Differences between amendments and new standards • The IEEE 802 way: Project Authorization Requests (PAR), the Five Criteria (5C), the process for moving from Interest Group to Study Group to Task Group to ratified output • Review and comment on landing page • http://www.ieee802.org/15/pub/IGptc.html • Any other business Agenda Jon Adams, Independent

  8. IEEE-802-15-11-0731-01-0ptc • PTC has four primary components • Equipment deployed on the locomotive/train • Equipment deployed trackside • Equipment deployed at a remotely located control center • A bi-directional wireless data link that links all these elements. It is this component upon which the Interest Group shall focus. Why Are We Here? Jon Adams, Independent

  9. IEEE-802-15-11-0731-01-0ptc Long (31 years and counting) and successful history of creating robust and well deployed wired and wireless standards Formal, coordinated, consensus-based and open process Participation is by individual contributor, not by company Six face to face meetings per year to allow sufficient vetting and promote standard development Voting rights maintained only through active participation Broad international participation Why IEEE 802? Jon Adams, Independent

  10. IEEE-802-15-11-0731-01-0ptc IEEE 802.1      Bridging (networking) and Network Management IEEE 802.2      Link Layer Control IEEE 802.3      Ethernet IEEE 802.5      MAC layer for Token Ring IEEE 802.11 a/b/g/n/… Wireless LAN (WLAN) & Mesh (Wi-Fi certification) IEEE 802.15     Wireless PAN IEEE 802.16     Broadband Wireless Access (WiMAX certification) IEEE 802.17     Resilient packet ring IEEE 802.18     Radio Regulatory TAG IEEE 802.19     Coexistence TAG IEEE 802.20     Mobile Broadband Wireless Access IEEE 802.21     Media Independent Handoff IEEE 802.22     Wireless Regional Area Network IEEE 802.23     Emergency Services Some of IEEE 802 Efforts Jon Adams, Independent

  11. IEEE-802-15-11-0731-01-0ptc • IEEE 802.15 Wireless PAN Working Group • IEEE 802.15.2 WIEEE 802.15 and 802.11 coexistence • IEEE 802.15.4 (2006) • Used by the ZigBee Alliance, ISA, Wireless HART, IETF (6LoWPAN), others • IEEE 802.15.4g Smart Utility Network • In-process effort to enable wireless connectivity for next generation of smart utility meters (electricity, gas, water, heat) with utilities • Operates on licensed or license-free bands, wide variety of channel widths, bandwidths, data rates • Ranges to 10’s of km • IEEE 802.15.4k Low-Energy Critical Infrastructure Monitoring • PHY amendment to 802.15.4 to facilitate point to multi-thousands of points communications for critical infrastructure monitoring devices (bridges, buildings, canals, etc.) • Addresses application's user needs of minimal network infrastructure • Enables the collection of scheduled and event data from a large number of non-mains powered end points that are widely dispersed, or are in challenging propagation environments • To facilitate low energy operation necessary for multi-year battery life, amendment minimizes network maintenance traffic and device wake durations • Ranges to 10’s of km • IEEE 802.15.4m TV White Space Amendment • Chartered to specify new PHY to add functionality to the existing standard 802.15.4-2006 MAC meeting TV white space regulatory requirements • enables operation in the available TV white space • supports typical data rates in the 40 kbits per second to 2000 kbits per second range • Designed for optimal and power efficient device command and control applications Why IEEE 802.15? Jon Adams, Independent

  12. IEEE-802-15-11-0731-01-0ptc • PTC overview at July 2011 IEEE 802.11 WNG and 802.15 WNG sessions • Entitled: PTC Radio and System Architecture (11-11-1032-00-0wng-positive-train-control-radio-and-system-architecture.ppt), Jia-Ru Li, Lilee Systems • 802.15 voted to approve formation of an interest group • First step was to explore alignment with 15.4k LECIM Why IEEE 802.15? Jon Adams, Independent

  13. IEEE-802-15-11-0731-01-0ptc Challenging Propagation Environment • In the US, PTC allocated 220 – 222 MHz band (λ = 1.36 m) • High speed mobility environment • 500 km/h locomotive to trackside (1000 km/h closing speed) • “Collector” atop locomotive • Antenna on locomotive “roof”, 5m height above railtop • Roof 15 – 25 m long, 2.5 m wide, potentially 2km of metal-roofed cars ahead or behind • Endpoints (Wayside Equipment) • Fixed equipment along the track, antennas may only a few meters high or pole-mounted up to 8-10 m • Base Station • Network-connected base stations • Antennas may be on towers, buildings or other structures • Track environment – extreme in every direction • Mountainous terrain, tunnels, open cuts, viaduct with sound walls • All of above but with horizontal curvature and rain sheeting down walls • Dead flat straight track, technically line-of-sight between collector/endpoint but very strong Rayleigh fading due to strong reflection from rail/ground surface • Dense urban, non-line of sight, extreme multipath • Distributed Power Unit (DPU) • Remote controlled locomotive(s) separated from the crewed lead locomotive, separation up to 3 km Jon Adams, Independent

  14. PTC Considerations 1 Train-centric communications (locomotive/train is “center of universe”) High reliability PHY link, fault-tolerant, error-correcting or at least error-detecting Intention that data carried may be “vital” (life/safety critical) Strong link layer security features (flexible encryption, unique identity) Data rates relatively low, depending on function (9.6k to 100’s of kbps) Data communication speeds may be asymmetric Propagation generally non-line of sight or close to ground, fade environment often Rayleigh, exponents 2.6 (fixed to fixed) to 3.2 (fixed to mobile) Range to 2x braking distance (3 - 15 km) in typical urban/suburban/rural environments Equivalent Radiated Power (ERP) (depending on antenna height, channel #, region) Operation in licensed US 220 – 222 MHz band (but not excluding others) Channel spacing 5 kHz, may be aggregated (by license) Can support separate uplink and downlink bands (base and mobile) Potential for adjacent/alternate channel interferers Frequency agility may be useful IEEE-802-15-11-0731-01-0ptc Jon Adams, Independent

  15. IEEE-802-15-11-0731-01-0ptc PTC Considerations 2 • Absolute need for high-speed node mobility • Speeds up to 500km/h, closing speeds to 1000 km/h • Latencies determined by stopping distance, order of 1 second sufficient • Payloads from a few bytes for control/command to ability to transfer larger files with fragmentation for remote upgrade/maintenance • Selectable QoS or communications priority may be useful • Wayside devices likely extremely power constrained (battery, vibration, pressure, solar, other scavenging) • Current requirements up to 24 locomotives and 30 waysides on one base station, but concept scales to dozens of devices per km of track • Flexible enough to handle very rapidly changing network membership • Time slotted and contention access periods necessary Slide 15 Jon Adams, Independent

  16. Other Potential Future Rail Environment Applications of 802.15 Standards Track and track infrastructure Switch/turnout operation and position Block occupancy Damage to rails Right of Way fouling Perimeter monitoring Bridge, viaduct, tunnel, culvert, etc. Highway / Rail grade crossing Rolling Stock Defects Defect detection (hot box, dragging equipment, high/wide, etc.) Signals Signal indication Signal function Grade crossing signaling and warning equipment Maintenance of Way Vehicle On/off rail status Position, direction, speed Positive control? Maintenance workers Rest-of-train car-to-car communication networks Hot box, brake line pressure, end of train marker, etc. IEEE-802-15-11-0731-01-0ptc Jon Adams, Independent

  17. IEEE-802-15-11-0731-01-0ptc • Idea or concept to be standardized, may be broad or specific • 802.15 PTC is currently working to meet the requirements to enter the Project Initiation Phase • IEEE Sponsor • in this case, it’s IEEE Computer Society and IEEE 802 Local and Metropolitan Area Network Standards Committee Standards Development Lifecycle Jon Adams, Independent

  18. IEEE-802-15-11-0731-01-0ptc • Propose the idea • PTC proposal was done at July 2011 IEEE 802 Plenary in both 802.11 and 802.15 WNG sessions • Get recognized officially • Interest Group IEEE 802.15 PTC • formed under the 802.15 Working Group (WG) • Interim Chair: Jon Adams, Independent • Interim Vice Chair: Dr Mark Hartong, FRA • Interim Secretary – any volunteers? • Meeting minutes, attendance-keeping, etc. • Study Group • Develop Project Authorization Request and complete the “Five Criteria” document • Get PAR done, approved by WG, and submitted to 802 Executive Committee • Task Group • Once TG is formed, group may “do work” and move along path of creating a draft standard • Once draft standard is successfully balloted and approved by TG and WG, submit draft to 802 EC for approval Process (in shorthand) Jon Adams, Independent

  19. IEEE-802-15-11-0731-01-0ptc • Register for the Atlanta IEEE802 Plenary 7-11 November • http://802world.org/plenary/ • IEEE 802.15 sessions run from 7-10 November, in order to get credit for attendance you need to attend at least 75% of all the 802.15 sessions • Hotel rooms are filling up • Standard Registration • before 6PM PT, Monday, October 31, 2011 (UTC: 1am Tuesday, November 1, 2011) • If you have questions on IEEE rules and participation, please let me know Next Steps for Participation Jon Adams, Independent

  20. IEEE-802-15-11-0731-01-0ptc Jon Adams, Independent

  21. IEEE-802-15-11-0731-01-0ptc • Next meeting • 1400 Pacific/1700 Eastern (US) (19 Oct) • 0500 China/Taiwan - 0600 Japan/Korea (20 Oct) • Proposed weekly meetings until Atlanta • 26 October • 2 November Next Meetings Jon Adams, Independent

More Related