Current Updates to Classes of Service. Richard Muscat - Bexar Metro Roger Hixson, ENP - NENA

Transcription

1

2 Current Updates to Classes of Service Richard Muscat - Bexar Metro Roger Hixson, ENP - NENA

3 WELCOME All attendees are reminded that the SBP is an interactive event. Attendees will be provided opportunities to share their insights, experience, and opinions. For the best results, only one person should speak at a time, everyone should listen fully to what other participants say before responding, and attendees should respect different opinions or perspectives.

4 Introduction Historical NENA NG9-1-1 (Data Mapping) NEAD WDL2 WDL1 WCVC NG9-1-1 Data Flow

5 Historical Class of Service (from NENA Master Glossary) A designation of the type of telephone service, e.g. residential, business, Centrex, coin, PBX, wireless. Ref: NENA Ref: NENA

6 Historical Class of Service (from Virginia Wireless Call Processing Terms For The Telecommunicator) A designation of the type of wireless location service. (MOBL, W911, WRLS, WPH1, WPH2)

7 Historical Class of Service (from Mid-America Regional Council s Wireless and VoIP Training Manual) Why do some VoIP calls look like wireline and others like wireless? A. True VoIP calls have a Class of Service or Type code of VOIP. Some companies sell their service as VoIP, but send calls through the landline network. These calls will have a Class of Service the same as landline.

8 Historical Wireline (e.g., RES, BUS, etc.) Wireless (e.g., WRLS, WPH2, etc.) VoIP (e.g. VOIP, etc.)

9 Historical Customer Name Field usage John Smith AT&T Mobility or Verizon Wireless Hotspot Wi-Fi Calling

10 Historical Class of Service may be used to provide an indication of: (1) what type of location information the Telecommunicator and/or the CPE and Mapping should be expecting (e.g., civic location or x, y coordinates)? (2) how the Telecommunicator should handle receipt of the call and dispatch of the call (e.g., commercial building type vs. single family residence; dispatching for a hang up call with no answer on callback; rebidding for location)? (3) expected accuracy level quality of location information (e.g., WPH1 vs. WPH2), and/or whether the caller is believe to be fixed, mobile, or nomadic (e.g., RES, WPH2, VNOM)

11 NENA Last updated in 2006 to additional VoIP Classes of Service

12 Next Generation In NG9-1-1 more detailed information may be available, such as: Service Environment: This element indicates whether a call is from a business or residence. (Required unless the Service Type value is wireless.) Service Type: This defines the type of service over which the call is placed (similar to the Class of Service delivered with legacy emergency calls in some regions). The implied mobility of this service cannot be relied upon. Service Mobility: This provides the service provider s view of the mobility of the caller s device. As the service provider might not know the characteristics of the actual device or access network used, the value should be treated as advisory and not be relied upon.

13 NG9-1-1 Data Mapping (Transitional)

14 NG9-1-1 Data Mapping (Transitional)

15 National Emergency Address Database (Discussion Proposal) WDL2 indicates a wireless call that provides: - civic oriented data (address and sub-address location [where appropriate]) in addition to - traditional WPH2 geodetic X, Y and Uncertainty data associated with the caller s location (where available). When this CoS is used, it indicates the civic oriented data is expected to meet the highest quality level criteria to be dispatchable, and indicates that the sub-address location within the building address is very close to the caller s location.

16 National Emergency Address Database (Discussion Proposal) WDL1 indicates a wireless call that provides: - civic oriented data (address and building zone [where appropriate]) in addition to - traditional WPH2 geodetic X, Y and Uncertainty data associated with the caller s location (where available). When this CoS is used, it indicates the civic oriented data is expected to meet the medium-quality level criteria to be dispatchable by building zone but also indicates a less detailed location than WDL2.

17 National Emergency Address Database (Discussion Proposal) WCVC indicates a wireless call that provides: - civic oriented data (address) in addition to - traditional WPH2 geodetic X, Y and Uncertainty data associated with the caller s location (where available). When this CoS is used, it indicates the civic oriented data is not expected to meet the criteria to be dispatchable by either building zone (WDL1) or subaddress location (WDL2).

18 WIRELESS PHONE PHASE I ANI/ALI S2-10 ESN= (210) :21 08/18/ TMOBILE-SE SECTOR-QF 616C5 (830) WRLS WIRELESS-SAN ANTONIO TX TMOBILE WIRELESS ALT#= TELCO=TMOB X= CNF=000 Y= UNC=0 WIRELESS CALLER VERIFY CALLERS NUMBER VERIFY CALLERS LOCATION

19 WIRELESS ANI/ALI for Dispatchable Location S2-10 ESN= (210) :21 08/18/ Austin St (830) WDL2 WIRELESS-SAN ANTONIO Rm 541 BT=MTM TMOBILE WIRELESS w Civic Location ALT#= TELCO=TMOB X= CNF=090 Y= UNC=98 TX Address Address CoS City, State Location Name WIRELESS CALLER VERIFY CALLERS NUMBER VERIFY CALLERS LOCATION

20 WIRELESS ANI/ALI for Dispatchable Location WDL2 case S2-10 ESN= (210) :21 08/18/ Austin St (830) WDL2 WIRELESS-SAN ANTONIO Rm 541 BT=MTM TMOBILE WIRELESS w Civic Location ALT#= TELCO=TMOB X= CNF=090 Y= UNC=98 TX Address Address CoS City, State Location Name Includes geodetic est location as well, with UNC WIRELESS CALLER VERIFY CALLERS NUMBER VERIFY CALLERS LOCATION

21 WIRELESS ANI/ALI for Dispatchable Location WDL1 case S2-10 ESN= (210) :21 08/18/ Austin St (830) WDL1 WIRELESS-SAN ANTONIO Fl 5 NW Zone BT=MTM TMOBILE WIRELESS w Civic Location ALT#= TELCO=TMOB X= CNF=090 Y= UNC=98 TX Address Address CoS City, State Location (plus/minus one floor and floor quadrant) Name Includes geodetic est location as well, with UNC WIRELESS CALLER VERIFY CALLERS NUMBER VERIFY CALLERS LOCATION

22 WIRELESS ANI/ALI for WCVC case (estimated address but no detailed location) S2-10 ESN= (210) :21 08/18/ Austin St (est) (830) WCVC WIRELESS-SAN ANTONIO BT=MTM TMOBILE WIRELESS w Civic Location ALT#= TELCO=TMOB X= CNF=090 Y= UNC=98 TX Address Address CoS City, State Location field including Building Type Name Includes geodetic est location as well, with UNC WIRELESS CALLER VERIFY CALLERS NUMBER VERIFY CALLERS LOCATION

23 DRAFT EXHIBIT 19 Code Name of Service Commonly Used (4 char) CoS Codes NENA Recommended (4 char) CoS Codes Related ATIS J-STD- 036-C-1 Position Source Codes 1 Residence RESD RESD 2 Business BUSN BUSN 3 Residence PBX PBXR PBXR 4 Business PBX PBXB PBXB 5 Centrex CNTX CNTX 6 Coin 1 Way PAY$, COIN PAY$ 7 Coin 2 Way COIN, PAY$ COIN 8 Mobile MOBL, WRLS MOBL 9 Residence OPX RSDX, RESX RSDX 0 Business OPX BSNX, BUSX BSNX A Customer Owned Coin Telephone COCT COCT B COS Not Available NA NA 48 C VoIP Residence VRES VRES D VoIP Business VBUS VBUS E VoIP Coin/Pay Phone VPAY VPAY F Other Mobile OMBL OMBL G Wireless Phase I WRLS / WPH1 WRLS 49 H Wireless Phase II WPH2 WPH2 1-5, 8-47, 51 I Wireless Phase II with Phase I Information P2P1, WPH1 WPH1 0, 6, 7, 50 J VoIP Nomadic VNOM VNOM K VoIP Enterprise Services - Centrex & PBX VENT VENT

24 DRAFT EXHIBIT 19 (continued) L Semi-Static, Small Coverage Cell * 53 M Static Wireless Device * 54 N Text Message Sent to 911 TEXT TEXT** 52** O Wireless E911 WCVC 55 P Q Civic Address Wireless E911 Dispatchable Location 1 Wireless E911 WDL1 56 WDL2 57 Dispatchable Location 2 R Supplemental Geodetic Location from Third-Party SDXY *** S Available T Telematics TLMA, TELM TLMA U Available V VoIP Services Default COS VOIP VOIP W Available WRLS X Available CELL Y Available Z Available

25 DRAFT EXHIBIT 20 Usual End State CoS Recommended Service Description Telecommunicator Clue Purpose Primary Related ATIS J-STD-036-C-1 Position Source Codes Primary ALI WPH2 FEMTOCELL Also pay attention to any presented fixed civic address information in addition to the x, y coordinates WPH2 INDOOR SMCELL/DAS HEAD The civic address may be highly accurate because it should be a static device with a very small coverage area. Also pay attention to any presented fixed civic address information in addition to the x, y coordinates WPH2, VOIP*, OMBL, SDXY WI-FI CALLING This is believed to be a mobile handset, tablet, or other device using WI-FI connectivity, and disconnection may result if caller were to become mobile 51 x, y coordinates 51 x, y coordinates Not Applicable Either x, y coordinates or Civic Address, and such may vary by either certain circumstances or service provider WDL2 WIRELESS W/ CIVIC ADDRESS (SPECIFIC) Also pay attention to presented x, y coordinates information in addition to the civic address. The caller is likely indoors, but may not have ability to be mobile (e.g., wireless broadband vs. Wi-Fi access point) 57 Civic Address

26 DRAFT EXHIBIT 20 (continued) WDL1 WIRELESS W/ CIVIC ADDRESS (ZONE) Also pay attention to presented x, y coordinates information in addition to the civic address. The caller is likely indoors, but may not have ability to be mobile (e.g., wireless broadband vs. Wi-Fi access point) 56 Civic Address WCVC WIRELESS W/ CIVIC ADDRESS (RANGE) Also pay attention to presented x, y coordinates information in addition to the civic address. The caller is likely indoors, but may not have ability to be mobile (e.g., wireless broadband vs. Wi-Fi access point) 55 Civic Address WPH2, VOIP* NON-MOBILE PHONE While caller may be using wireless network connectivity, this device is NOT believed to be a mobile handset, and disconnection may result if caller were to become mobile. 51, 55, 56, or Not Applicable (VOIP) (1) x, y coordinates when WPH2 is the CoS (2) Wireless Civic Address when either WDL2 or WDL1 is presented (3) VoIP Civic Address when a VOIP CoS is presented

27 NG9-1-1 Data Flow NG9-1-1 Data Flow WG has been formed to address clearly defined recommended structure and minimum content of NG9-1-1 data and presentation in order for it to be effective as the replacement and expansion of traditional ALI. For example with regard NG9-1-1 design, there is no single data item equivalent to CoS; instead there are potentially three different items of data that may be used in combination to provide the same or more information.

28 NG9-1-1 Data Flow (continued) Similar to as was the case in E9-1-1, in NG9-1-1 what a PSAP is willing to display on the call-taking screen may impact data flow and its importance, and there are various data flow alternates and related potential timing issues and combinations. While NG9-1-1 was designed to support either data by value or keys for acquiring data by reference, making best use of this capability to improve call management during the call processing within the NG9-1-1 system are issues for the WG to address.

29 NG9-1-1 Data Flow (continued) #1 goal/objective/deliverable: Define structure and minimum content of ALI equivalent data to be delivered on initial display at PSAP, including identifying possible by-value data items that should be considered as essential data for inclusion in the call stream, where those by-value data items are obtained, and for what purposes are they of use within the core NG9-1-1 system and/or the PSAPs. #2 goal/objective/deliverable: Define structure and content of expanded data to be delivered upon initial and subsequent inquiry. #3 goal/objective/deliverable: Transitional plan for ALI equivalent data to NG9-1-1 information and how to structure other related data.

30 Closing Summary NEAD WDL2 WDL1 WCVC NG9-1-1 (Data Mapping) NG9-1-1 Data Flow

31 Join a NENA WG Select committee name to see a list of active WGs and a link to join the WG NG9-1-1 Data Flow (Co-Chairs: Richard Muscat, Amy McDowell ENP) _ISF NG9-1-1 Data Flow_ChrtrUpdtAppvd

32 Presenter s Contact Info Richard Muscat richard@bexarmetro.com (210) Roger Hixson rhixson@nena.org (202)

33 NENA and the NENA Development Group thank you for participating in this session and for sharing your experience, knowledge, and opinions with your fellow attendees and the session facilitators. This event succeeds because of you!