1111111111111111 IIIIII IIIII 11111 1111111111 11111 lllll 111111111111111 111111111111111 11111111
`US 20030063714Al
`
`(19) United States
`(12) Patent Application Publication
`Stumer et al.
`
`(10) Pub. No.: US 2003/0063714 Al
`Apr. 3, 2003
`(43) Pub. Date:
`
`(54)
`
`INTERNET PROTOCOL (IP) EMERGENCY
`CONNECTIONS (ITEC) TELEPHONY
`
`(57)
`
`ABSTRACT
`
`(76)
`
`Inventors: Peggy M. Stumer, Boca Raton, FL
`(US); Robert Stampfl, Hohenkammer
`(DE); Alfons Fartmann, Neufahrn
`(DE); Walter Hipfinger, Vienna (AT)
`
`Correspondence Address:
`Siemens Corporation
`Intellectual Property Department
`186 Wood Avenue South
`Iselin, NJ 08830 (US)
`
`(21) Appl. No.:
`
`09/963,242
`
`(22) Filed:
`
`Sep.26,2001
`
`Publication Classification
`
`Int. CI.7 .................................................... H04M 11/04
`(51)
`(52) U.S. Cl.
`................................................. 379/37; 379/45
`
`An IP Telephony Emergency Connections (ITEC) system
`and method that determines the precise origin of an emer(cid:173)
`gency call and routes the call to the proper Public Service
`Answering Point (PSAP). A source-based routing mecha(cid:173)
`nism is provided in an IP telephony type network, such as a
`VoIP or IP over LAN/ATM. Emergency calls are routed to
`the correct PSAP jurisdiction. Each server/switch may
`include the mechanism such that the IP Telephony network
`can identify an E911 connection and egress to a public
`network at a point closest to the emergency call point of
`origin. Whenever an emergency number call is made, the
`call's origin is determined during call setup establishment.
`Every port or end user jack in the network is assigned a
`Source Group Index (SGI), which is a number or index
`representing each PSAP jurisdiction in the network. All
`ports/jacks within the same PSAP jurisdiction are assigned
`the same SGI. Users may be in different areas of multiple
`PSAP jurisdictions.
`
`NE1
`
`110
`
`102
`
`FIXED
`STATIONS
`
`WIRELESS
`
`PSAP
`J1
`
`PSAP
`J2
`
`PSAP
`Jn
`
`FIXED
`STATIONS
`
`WifHESS- - - -
`
`Motorola Solutions, Inc., Ex1014, p. 1
`
`

`

`Patent Application Publication Apr. 3, 2003 Sheet 1 of 6
`
`US 2003/0063714 Al
`
`126
`
`NE1
`
`~-:: .__o_E~_~c_E __,,
`
`FIG. 1.
`
`NE1
`
`12B
`
`102
`
`FIXED
`STATIONS
`
`WIRELESS
`
`IP DEVICES
`NE1
`
`112
`
`LAN/WAN
`
`110
`
`IP DEVICES
`NE1
`
`FIXED
`STATIONS
`
`[filJ
`
`WIRELESS- - - -
`
`PSAP
`Ji
`
`PSAP
`J2
`
`PSAP
`Jn
`
`Motorola Solutions, Inc., Ex1014, p. 2
`
`

`

`Patent Application Publication
`
`Apr. 3, 2003 Sheet 2 of 6
`
`US 2003/0063714 Al
`
`FIG. 2
`
`ITEC
`COMPONENTS
`I
`
`ECI
`I SEND I v1so
`I
`I
`RECEIVE
`154
`I
`I
`EMERGENCY
`NUMBERS
`
`1S2
`I
`I
`ECI DATA
`FROM PEN
`
`NAR
`LOGIC
`
`160,
`16h ~
`162
`I
`ELIN
`TABLE
`
`1,4
`
`SOURCE
`GROUP
`TABLE
`
`'
`
`168
`I
`ROUTING
`
`166
`I
`PACKET
`RCV
`SEND
`
`Motorola Solutions, Inc., Ex1014, p. 3
`
`

`

`Patent Application Publication
`
`Apr. 3, 2003 Sheet 3 of 6
`
`US 2003/0063714 Al
`
`FIG. 3
`
`STATION/LINE
`
`STATION/LINE
`
`178
`
`180
`
`182
`
`170
`
`SHELF 1
`
`186
`
`188
`FIXED
`
`TRUNKS
`
`TRUNKS
`
`172
`
`PSTN
`PRIVATE
`WIRELESS
`
`(ROAMING)
`
`IP
`
`IP
`
`174
`
`==~===========~======== LAN
`
`SHELF 2
`
`SHELF 3
`
`Motorola Solutions, Inc., Ex1014, p. 4
`
`

`

`1·•-·-------\
`:
`SGS
`.,
`!
`! 2
`
`,------..
`
`,
`
`'
`
`··--·--·--------
`SG7
`.
`PSAP J7
`.. -::::::::::=:-
`:.·:::::::: ... --
`----:::::::=-•---
`
`c t
`
`I
`
`,...,_, ......_, ~
`
`I
`
`\ 192
`!
`I
`L----F:~--
`i 208
`i
`!
`PSAP J1 ~~ 194
`L _________________________ _
`212
`
`FIG. 4
`,··-··-··7
`SGS
`:
`:
`I
`!
`PSAP JS
`j ...------. A 204
`PSAP JS \ \~ =1d NE2 I
`!
`!
`/
`I
`. ..-~::1-G~;::': r - - - -
`R-TG!~ / /
`_,
`/
`----------.. ---·-
`NE1
`----- --------
`------
`·---"--~
`,.-··
`.-··
`------··
`
`r-··-------··7
`-·
`SG4
`:
`_/ PSAP J4
`!
`210 \
`./ 7
`
`NE3
`
`PSAP J9
`
`.
`
`___ ;__
`
`~ .... ~ = ....
`~ "Cl -....
`~ ....
`.... 0 =
`~
`O' -....
`~ ....
`.... 0 =
`I ~
`~ :;
`-----~·-7
`
`SG3
`!
`PSAP J3 !
`!
`_j
`
`........,....,~
`.
`202
`
`·--7-·-··-··
`
`pEVI CE_j---197
`----·------
`
`'
`~2
`/
`L .. PSAP J2 ··---------j
`
`""C
`
`I")
`
`I")
`
`~~
`N
`0
`8
`rF.J. =(cid:173)~
`~ ....
`0 ...,
`
`,i;;..
`
`O'I
`
`d
`rF.J.
`N
`0
`
`@
`
`0
`0
`O'I
`~
`-..J
`'"""
`,i;;..
`>
`'"""
`
`Motorola Solutions, Inc., Ex1014, p. 5
`
`

`

`Patent Application Publication Apr. 3, 2003 Sheet 5 of 6
`
`US 2003/0063714 Al
`
`FIG. SA
`
`216
`
`214
`
`EMERGENCY
`NUMBERS
`
`222
`
`220
`
`NE1
`ALONE,
`NE1-3
`LAN/IP
`
`218
`
`STATION
`
`NE1-3
`FIXED
`226
`
`GET PEN/ELINx
`SGI
`
`WIRELESS
`MOBILE
`NE1-3
`TDM
`
`230
`
`224
`
`REMOTE
`STAT/SWITCH
`NEi-3
`FIXED
`
`232
`
`GET PEN/ELINx
`SGI
`
`GET PEN/ELINx
`SGI
`
`228
`
`GET PEN/ELINx
`SGI
`
`SEND INTERNAL
`ECI MESSAGE
`W/ECI DATA
`
`NO
`
`'-------i~RCV 1 - - - - ~
`...__
`MSG
`
`248
`
`SEND ECI
`PACKET TO NE3
`W/ECI DATA
`
`242
`
`256
`
`NORMAL
`PROCESSING
`
`252
`
`ROUTING:
`CALLEO#
`MATCHING
`
`NO
`
`YES
`
`TO STEP 258
`FIG. SB
`
`Motorola Solutions, Inc., Ex1014, p. 6
`
`

`

`Patent Application Publication
`
`Apr. 3, 2003 Sheet 6 of 6
`
`US 2003/0063714 Al
`
`FIG. 58
`
`258
`
`FROM STEP 254
`FIG. SA
`
`SOURCE GROUP
`TABLE
`LOOK UP ECI
`INDEX FOR
`ROUTE
`
`260
`
`ELIN INDEX
`LOOK UP
`
`RECEIVE
`PACKET
`ACK
`
`270
`
`PACKET TO
`ECI SENDER
`ACK
`
`261
`
`- - I e - - NORMAL PROCESSING - - - - i
`
`YES
`
`QUEUE
`ACCORDING
`TO PRIORITY
`
`SET UP TO
`EMERGENCY#,
`ELIN/CALL BACK#
`
`NO
`
`264
`
`266
`
`LAN/IP TO NE2 OR NE3
`OF RT/TG LOCATION
`
`PACKET TO
`NE wliERE
`TO ROUTE CALL
`TO EMERGENCY#
`WITH/ELIN
`CALLBACK# OR
`CALLING#, PRIORITY
`i - - - - - NORMAL PROCESSING - - -
`
`Motorola Solutions, Inc., Ex1014, p. 7
`
`

`

`US 2003/0063714 Al
`
`Apr. 3, 2003
`
`1
`
`INTERNET PROTOCOL (IP) EMERGENCY
`CONNECTIONS (ITEC) TELEPHONY
`
`RELATED APPLICATION
`
`[0001] This application is related to co-owned co-pending
`application Ser. No. 09/816,627 entitled "Priority Based
`Methods and Apparatus For Transmitting Accurate Emer(cid:173)
`gency Location Identification Numbers (ELINs) From
`Behind A Multiline Telephone system (MLTS)"; co-owned,
`co-pending application Ser. No. 09/816,380 entitled "Meth(cid:173)
`ods And Apparatus For Transmitting Over A Private Net(cid:173)
`work Accurate Emergency Location Identification Numbers
`(ELINs) From Behind a Multiline Telephone System
`(MLTS); co-owned co-pending application Ser. No. 09/816,
`823 entitled "Methods And Apparatus For Transmitting
`Accurate Emergency Location Identification Numbers
`(ELINs) From Behind A Multi-Line Telephone System
`(MLTS) After An Emergency Caller Disconnects";
`co-owned co-pending application Ser. No. 09/816,838
`entitled "Methods And Apparatus For Transmitting Accurate
`Emergency Location Identification Numbers (ELINs) After
`An Emergency Caller Disconnects"; co-owned co-pending
`application Ser. No. 09/815,685 entitled "Methods And
`Apparatus For Dialing An Emergency Telephone Number
`From A Teleworking Client Remotely Coupled To A PBX";
`co-owned co-pending application Ser. No. 09/815,468
`entitled "System For Dialing An Emergency Telephone
`Number From A Teleworking Client Remotely Coupled To
`A PBX"; and co-owned co-pending application Ser. No.
`09/816,843 entitled "Methods And Apparatus For Transmit(cid:173)
`ting Accurate Emergency Location Identification Numbers
`(ELINs) From Behind A Multi-Line Telephone System
`(MLTS) Utilizing Port Equipment Numbers", the complete
`disclosures of which are hereby incorporated by reference.
`
`BACKGROUND OF THE INVENTION
`
`[0002] 1. Field of the Invention
`
`[0003] This invention relates to telecommunications sys(cid:173)
`tems, especially telecommunication systems capable of
`computer telephony such as voice over internet protocol
`(VoIP). Specifically, the invention relates to completing an
`emergency, e.g. 911, call from a station/device over a data
`network, e.g., a private corporate local area network (LAN/
`IP) or the Internet, to a public network emergency facility
`and delivering precise location information of the caller and
`a call back number based on a port equipment number
`associated with the port from which the emergency call
`originated.
`
`[0004] 2. Brief Description of the Prior Art
`
`[0005] When a caller calls an emergency number, e.g. 911
`(E911), the call is routed to a Public Safety Answering Point
`(PSAP). In some jurisdictions, regulatory agencies require
`that the caller's telephone number/callback number and/or
`precise physical location referred to as an Emergency Loca(cid:173)
`tion Identification Number (ELIN), be automatically pro(cid:173)
`vided to the PSAP. The information in the ELIN is used to
`locate the caller and to call back to the caller should there be
`a disconnect.
`
`[0006] A caller identification (i.e., telephone number and
`ELIN) may be delivered to the PSAP either in-band (e.g.,
`using DTMF signaling) or out-of-band (e.g., using ISDN
`
`signaling) depending on the type of trunk circuit employed.
`Normally, for residential callers Caller ID number is suffi(cid:173)
`cient for the PSAP. In some cases, the ELIN is geodetic, i.e.
`includes earth coordinates or geo-positional synchronous
`(GPS) data.
`
`[0007] Digitally encoded voice communications that are
`transmitted over a network, using what is typically referred
`to as Voice over Internet Protocol (VoIP) may originate
`anywhere and possibly, follow a circuitous convoluted route
`to a distant destination for far-end hop-off to a public service
`telephone network (PSTN). Thus, placing an E911 call over
`a VoIP enabled telephone network, may be a problem.
`Heretofore, there has not been a way in an IP network (e.g.,
`voice over IP) to identify the source location of an origi(cid:173)
`nating device whose destination is 911 (or other emergency
`number) and to route the call to the proper PSAP jurisdiction
`( or other designated destination).
`
`[0008] Thus, there is a need for a way to determine the
`proper destination PSAP of emergency calls in an IP net(cid:173)
`work and further to correctly route an emergency call from
`the IP network to the public network of the appropriate
`PSAP.
`
`SUMMARY OF THE INVENTION
`
`[0009]
`It is therefore a purpose of the invention to accu(cid:173)
`rately report the emergency location of an emergency caller
`calling on a VoIP network to public safety personnel.
`
`[0010]
`It is another purpose of the invention to accurately
`report the callback number of an emergency caller using
`VoIP to public safety personnel.
`
`[0011]
`It is yet another purpose of the invention to accu(cid:173)
`rately report the ELIN and callback number of a caller
`making an emergency call using VoIP to call a PSAP over a
`private network in a manner that does not interfere with
`features of the PBX/MLTS.
`
`[0012]
`It is yet another purpose of the invention to locate
`an E911 caller from the source of the call, regardless of the
`call origination location including calls originating in an IP
`private network, and route the call to the most appropriate
`PSAP, closest to the caller.
`
`[0013] The present invention is an IP Telephony Emer(cid:173)
`gency Connections (ITEC) system and method that deter(cid:173)
`mines the precise origin of an emergency call and routes the
`call to the proper Public Service Answering Point (PSAP).
`A source-based routing mechanism is provided in an IP
`telephony type network, such as a Voice over IP (VoIP) or IP
`over Local Area Network/Asynchronous Transfer Mode
`(LAN/ATM). Emergency calls are routed to the correct
`PSAP jurisdiction. Emergency calls may include, but are not
`limited to voice calls. The routing mechanism may be
`deployed in any intelligent distributed or centralized net(cid:173)
`work. For example, a server/switch at a gateway may
`include the mechanism such that the IP Telephony network
`can identify an E911 connection and egress to a public
`network at a point closest to the emergency call point of
`origin. Whenever a call is recognized as being an emergency
`number call, the call's origin is determined during call setup
`establishment. Every port or end user jack in the network is
`assigned a Source Group Index (SGI), regardless of whether
`a port is physical or logical, e.g., for multi-drop. An SGI is
`a number or index representing each PSAP jurisdiction in
`
`Motorola Solutions, Inc., Ex1014, p. 8
`
`

`

`US 2003/0063714 Al
`
`Apr. 3, 2003
`
`2
`
`the network. Port/jack level management granularity allows
`any server/switch to serve users that may be in different
`areas of multiple PSAP jurisdictions. So, all ports/jacks
`within the same PSAP jurisdiction are assigned the same
`SGI.
`[0014] Advantageously, an emergency call made using
`VoIP is routed to the proper authorities. The routing can be
`provided at any network entity that is equipped with appro(cid:173)
`priate trunks, including the network entity where the call
`originated or, at a gateway located near the source of the call.
`This call handling circumvents normal call routing and may
`fulfill expected governmental requirements for emergency
`calls. Accordingly, emergency request information is sent to
`the correct PSAP regardless of where the user resides in an
`IP network.
`
`[0015] Thus, the apparatus of the invention includes data(cid:173)
`base management, emergency number detection, call rout(cid:173)
`ing and both ISDN and non-ISDN signaling. The present
`invention may be configured so that either the callback
`number, the ELIN, or both are transmitted to the PSAP.
`Further, the invention may be configured to recognize mul(cid:173)
`tiple emergency numbers and to give emergency calls pri(cid:173)
`ority over non-emergency calls.
`[0016] Additional benefits and features of the invention
`will be apparent from the following detailed description
`taken together with the attached drawings.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0017] FIG. 1 shows an example of an overview of a
`preferred embodiment network with Voice over IP (VoIP)
`emergency call capability (IP Telephony Emergency Con(cid:173)
`nections (ITEC)) according to the present invention;
`[0018] FIG. 2 shows an example of ITEC components of
`network elements of a preferred embodiment system accord(cid:173)
`ing to the present invention;
`[0019] FIG. 3 shows an example of SGI and ELIN index
`port assignment for three shelves;
`[0020] FIG. 4 shows an example of various network
`entities distributed throughout different geographically dis(cid:173)
`tinct PSAP jurisdictions with corresponding routes and trunk
`group assignments;
`[0021] FIGS. 5A-B are a flow diagram showing how
`emergency numbers are processed according to a preferred
`embodiment of the present invention;
`
`DETAILED DESCRIPTION
`
`[0022] Turning now to the drawings and more particularly
`FIG. 1 shows an example of an overview of a preferred
`embodiment network 100 with Voice over IP (VoIP) emer(cid:173)
`gency call capability (IP Telephony Emergency Connections
`(ITEC)) according to the present invention. Essentially,
`ITEC is a source-based routing mechanism in an IP Tele(cid:173)
`phony type network (e.g., voice over IP or IP over Local
`Area Network/Asynchronous Transfer Mode (LAN/ATM))
`that determines the precise emergency call origin in a Public
`Service Answering Point (PSAP)) jurisdiction of an emer(cid:173)
`gency call (including, but not limited to voice calls) and
`routes the call to the appropriate public safety personnel in
`that jurisdiction. This routing mechanism may be developed
`in an intelligent network routing entity 102, 104 with other
`
`network entities 106, 108 that are in communication with
`each other over Local Area Network (LAN) or Wide Area
`Network (WAN) 110. The intelligent network routing entity
`maybe distributed or centralized, for example, a server/
`switch, gateway 102, 104, where the IP Telephony network
`can convert the emergency call connection (if required) and
`egress to a public network at a point closest to the point of
`origin of the call. Whenever a call is recognized as an
`emergency number, the preferred routing mechanism makes
`a call origin determination during call setup establishment.
`Each server/switch 102 may serve users that span multiple
`PSAP jurisdictions, so every port or end user jack in the
`network 100, whether physical and/or logical e.g., for multi(cid:173)
`drop, is assigned a Source Group Index (SGI). Each PSAP
`jurisdiction in the network is represented by one SGI and so,
`all ports/jacks within the same PSAP jurisdiction are
`assigned the same SGI.
`
`[0023] All network entities, such as ethernet switches and
`servers, where users are attached to ports/jacks or where end
`user devices are attached to the IP network include a unique
`Emergency Connection Identifier (ECI) module. At least one
`Network Area Router (NAR) module (in server 102 in this
`example) provides database maintenance, administration
`and special messaging, i.e., packets and internal messages.
`The ECI modules and data may reside in one or more
`network entities.
`
`[0024] For purposes of the description of the present
`invention, network entities may be categorized as belonging
`to one of three categories, NEl, NE2 or NE3. NEl type
`devices include only an ECI module and do not include a
`gateway (GWY) or a centralized manager (MGR). NE2 type
`devices include both an ECI module and a gateway, but do
`not include a centralized manager. NE3 devices are Network
`Area Routers (NAR) that each include an ECI module, a
`gateway and a centralized manager. Thus, server 102 is an
`NE3 type network entity. Remote switch 104 is an NE2 type
`network entity. Devices 106, 108 are each NEl type network
`entities.
`
`[0025] Server 102 is shown with ports for fixed stations,
`wireless phones, IP devices and one or more remote stations
`112 attached and in communication with the LAN/WAN 110
`through network area router 114. Both gateway 116 and
`trunks 118 are connected to a public service ( or switched)
`telephone network (PSTN) 120. Each remote station 112 is
`directly connected to PSTN 120. Remote switch 104 is
`shown with ports for IP devices, fixed stations, wireless
`phones and one or more remote stations 122. As an NE2
`device, remote switch 104 includes the LAN/WAN 110
`through a trunk 124 with the PSTN 120. So, in this example,
`network entity 106 is an internet protocol (IP) device, e.g.,
`a communication device with an attached handset 126.
`Device 108, which is an NEl type network entity, includes
`ports for various communication type devices such as
`remote station 128, fixed stations, wireless devices and IP
`devices. The PSTN 120 is in telephonic communication with
`Public Safety Answering Point (PSAP) jurisdictions (Jl-Jn)
`that are located in each corresponding port location for each
`of the network entities 102, 104, 106, 108.
`
`[0026] Further, the PSTN 120 may be in communication
`with a remote dial-up Emergency Location identification
`Number Apparatus as described in co-owned co-pending
`application Ser. No. 09/816,627 entitled "Priority Based
`
`Motorola Solutions, Inc., Ex1014, p. 9
`
`

`

`US 2003/0063714 Al
`
`Apr. 3, 2003
`
`3
`
`Methods and Apparatus For Transmitting Accurate Emer(cid:173)
`gency Location Identification Numbers (ELINs) From
`Behind A Multiline Telephone system (MLTS)"; co-owned,
`co-pending application Ser. No. 09/816,380 entitled "Meth(cid:173)
`ods And Apparatus For Transmitting Over A Private Net(cid:173)
`work Accurate Emergency Location Identification Numbers
`(ELINs) From Behind a Multiline Telephone System
`(MLTS); co-owned co-pending application Ser. No. 09/816,
`823 entitled "Methods And Apparatus For Transmitting
`Accurate Emergency Location Identification Numbers
`(ELINs) From Behind A Multi-Line Telephone System
`(MLTS) After An Emergency Caller Disconnects";
`co-owned co-pending application Ser. No. 09/816,838
`entitled "Methods And Apparatus For Transmitting Accurate
`Emergency Location Identification Numbers (ELINs) After
`An Emergency Caller Disconnects"; co-owned co-pending
`application Ser. No. 09/815,685 entitled "Methods And
`Apparatus For Dialing An Emergency Telephone Number
`From A Teleworking Client Remotely Coupled To A PBX";
`co-owned co-pending application Ser. No. 09/815,468
`entitled "System For Dialing An Emergency Telephone
`Number From A Teleworking Client Remotely Coupled To
`A PBX"; and co-owned co-pending application Ser. No.
`09/816,843 entitled "Methods And Apparatus For Transmit(cid:173)
`ting Accurate Emergency Location Identification Numbers
`(ELINs) From Behind A Multi-Line Telephone System
`(MLTS) Utilizing Port Equipment Numbers", the complete
`disclosures of which are hereby incorporated by reference,
`and referred to generically hereinafter as ELIN references or
`an ELIN apparatus.
`[0027]
`It is understood that the number of PSAPs involved
`depends on the location of ports connecting each individual
`fixed station, wireless device, IP device and remote station
`for each of the individual network entities 102, 104, 106,
`108. Each PSAP jurisdiction is a geographically distinct
`location, e.g., a county, a town, a city, a precinct, etc.) All
`ports/jacks, physically located within each jurisdiction must
`have the same SGI assigned for that particular region.
`Therefore, users may be attached to/move between the
`different network entities and the assigned SGI is based on
`the port to which they are physically connected. Emergency
`calls placed from each user are routed according to the SGI
`to the correct PSAP jurisdiction. Users connected to NEl
`network entities 106, 108 are routed through server 102 or
`remote switch 104 to the PSTN 120 (i.e., whichever entity
`has access to the PSAP correct jurisdiction) and, thereafter,
`the call is directed to public safety personnel in jurisdiction,
`J1 ... , Jn.
`[0028] When a number is dialed, the ECI module checks
`an ECI emergency number table to determine if the number
`is an emergency call number as indicated by whether the
`dialed number is listed as such. If the dialed number is not
`found in the ECI table, the call is not processed by ITEC.
`However, if the number matches an emergency number in
`the ECI table, then, the ITEC processes the call and it is
`routed to a PSAP jurisdiction based on the originating port
`SGI. The NAR determines the route based on the port's SGI
`which is included in routing tables and routes emergency
`calls to egress to the proper PSAP jurisdiction. Preferably,
`the ECI modules are located in each individual network
`entity 102, 104, 106, 108. However, all ECI modules may be
`located at a central processing entity, provided the PENs are
`unique network wide (e.g., prefixed with a network entity
`unique identifier).
`
`[0029] FIG. 2 shows an example of ITEC components of
`network elements of a preferred embodiment system accord(cid:173)
`ing to the present invention. As noted above, each network
`element includes an emergency connection identifier (ECI)
`module 150 regardless of network element type. Further, at
`least one network element includes a network area router
`NAR 160, i.e., NE3 type network element. The ECI module
`150 both sends and receives messages and handles all
`communications between the NAR 160 and users at con(cid:173)
`nected ports, regardless of whether the ECI module 150 and
`NAR 160 are in the same or separate network elements.
`Accordingly, the ECI module 150 also includes ECI data in
`an ECI data table 152 for each port in the network entity. An
`ECI table 152 entry is attached to any emergency messages
`that are sent from or received by the network entity. ECI data
`table 152 includes a port equipment number (PEN) field, a
`port source group index number (SGI) field and a local
`PSAP emergency location identifier number (ELINx) field.
`Also, the ECI module 150 includes an emergency number
`table 154 with a list of emergency numbers and associated
`priorities.
`
`[0030]
`If the network entity is NE3 type, it includes
`network area router 160 and logic 161. The NAR logic 161
`routes messages to and from connected network entities as
`directed by each particular network entity's ECI module
`150. Accordingly, the network area router maintains an
`ELIN table 162, a source group table 164, an IP packet
`receive/send table 166 and a routing table 168. The routing
`table 168 corresponds messages to a particular origination
`port as identified by the ECI data of the particular message.
`
`[0031] Each ECI module 150 recognizes emergency calls
`that originate from the particular network entity in which the
`ECI module 150 resides. The ECI module 150 identifies
`each emergency call's SGI and other pertinent information
`(e.g., ELIN) and flags emergency calls for emergency pri(cid:173)
`ority. The ECI module 150 compares each call's destination
`digits to entries in an ECI emergency number table 154. The
`ECI module 150 transmits a small data packet ( or internal
`message when the NAR 160 and ECI module 150 reside in
`the same network entity) that includes the port's SGI,
`destination digits and other connection information to the
`NAR 160. The NAR logic 160 processes each data packet
`(subject to normal retransmission handling) or internal mes(cid:173)
`sage (if the ECI module 150 and NAR 160 are located
`together) in order to determine how the call should be
`switched. A call may be sent initially as data packets for
`partial packet switching and, then to a gateway for circuit(cid:173)
`switching or, immediately to a local B-channel for circuit
`switching from the source entity. The routing instructions
`are returned to the sender ECI module 150 or an acknowl(cid:173)
`edgment (ACK) may be sent when another gateway is to
`route the call. This message/packet exchange must be
`uniquely identified with each particular call.
`
`[0032] FIG. 3 shows an example of SGI and ELIN index
`port assignments for three shelves 170, 172, 174. Each shelf
`170, 172, 174 includes two slots indicated by a correspond(cid:173)
`ing 1 or 2 subscript, e.g., 1701 , 1702 . Boards in each slot may
`be stations/lines, trunks or IP interfaces, for example. Ports
`176, 178, 180, 182, 184 are shown, typically in each slot,
`e.g., on station/lines 1701 , 1702 and so on. It should be noted
`that this is for example only and the present invention may
`be applied to any combination of slots or shelves.
`
`Motorola Solutions, Inc., Ex1014, p. 10
`
`

`

`US 2003/0063714 Al
`
`Apr. 3, 2003
`
`4
`
`TABLE 1
`
`PEN
`
`SGI
`
`ELIN index
`
`Comment
`
`1-1-001
`1-2-005
`1-3-001
`1-4-002
`
`2
`2
`8
`2
`
`101
`220
`125
`23
`
`fixed station
`IP device
`RS
`wireless phone
`
`[0033] Table 1 is an example of an ECI PEN table, e.g.,
`table 152 of FIG. 2. Port Equipment Numbers (PEN) point
`to the assigned ELIN and SGI for the particular port, where
`the port is ambiguous network wide. Port equipment num(cid:173)
`bers are assigned to each port and have the format: shelf
`number-slot number-port number. Thus, the number
`2-11-111 indicates shelf number 2, slot number 11, port
`number 111. Typically fixed stations are in the same PSAP
`jurisdiction as the particular network entity and so, have the
`same SGI. If a station/device or RS extends into another
`PSAP jurisdiction, a different SGI index (i.e., the SGI for
`devices in that jurisdiction) is assigned. The ELIN index is
`as described in the ELIN references.
`
`TABLE 2
`
`Dialed#
`
`Priority
`
`9 1 1
`9 9 11
`9931111
`
`3 e.g., local police station
`
`[0034] Table 2 is an example of an ECI Emergency
`Number Table. Calls are assigned priority relative to normal
`everyday calls which may be given a lowest priority, e.g.,
`priority 9. Emergency calls are typically given highest
`priority, priority one. So, for purposes of this example, one
`is the highest priority and nine is the lowest. Each call is
`assigned a unique call ID, e.g. a number generated from a
`random number generator. Any emergency number is
`flagged by the ECI data and does not include a routing
`number. When a call is made from a device at a network
`entity, the ECI module checks against an emergency number
`in the routing table. If the dialed number is an emergency
`number, then the ECI module processes the number. Oth(cid:173)
`erwise the ECI module ignores the number and it is treated
`as a normal call.
`[0035]
`In this example, shelf 170 has three ports assigned
`for fixed telephone, and additional ports are assigned for
`roaming connection, e.g., cellular phones. A remote station
`may also be connected to station/line boards 1701, 1702.
`Fixed telephone 186 is assigned to SGl and is located in a
`different PSAP jurisdiction than fixed telephone 188, which
`is assigned to SG4. Trunks in shelf 172 connect to a PSTN
`and also provide private and wireless connections to the
`PSTN. The first port of shelf 172 is also shown in the same
`jurisdiction as fixed telephone 186 and so, is also assigned
`SGl. Shelf 174 is shown with port connections to a LAN.
`Each of the LAN port connections may be distributed in
`different jurisdictions and assigned, SGl, SG2, SG3 ... , for
`example. An ECI message may be internal (when the ECI
`module is located on an NE3 type network entity) or over a
`signaling channel to an NE3 type network entity. Generally,
`an ECI packet includes an ECI packet type, a calling number
`(i.e., the user not the port number) a called number (the
`
`PSAP telephone number) a network-wide unique call ID and
`ECI data. As noted above ECI data may include the SGI and
`ELIN index. Optionally, a priority may also be included.
`
`[0036] FIG. 4 shows an example of various network
`entities distributed throughout different geographically dis(cid:173)
`tinct PSAP jurisdictions with corresponding routes and trunk
`group assignments. This example includes ten individual
`network entities 192-210. Network entities 192, 194, 196
`and 198 are NEl type network entities. Network entities
`200, 202, 204, and 206 are NE2 type network entities.
`Network entities 208 and 210 are NE3 type network entities.
`For redundancy, multiple NE3 type network entities (2 in
`this example) may serve NEl and NE2 type network enti(cid:173)
`ties. A remote station 212 and a mobile/wireless phone 214
`are shown. These ten network entities 192-210 include ports
`that are distributed in ten individual PSAP jurisdictions
`designated 11-110. Typically, network entities have ports in
`the PSAP jurisdiction in which they are located. However,
`network entity 200 also includes ports in two other juris(cid:173)
`dictions, including jurisdiction 12, 18 and 110. Network
`entity 206 includes ports in jurisdictions 16 and 17. Mobile
`phone 214 is potentially in connection with each of network
`entities 198 and 202 and 210 because of its roaming capa(cid:173)
`bility, e.g., handoff from one network entity 198,202,210 to
`another. Therefore, mobile phone 214 may be in each of
`jurisdictions 13, 19 and 14, respectively.
`
`[0037] Accordingly, an emergency call may be made from
`a network port on network entity 200 where the port resides
`in jurisdiction 110. Relevant call information is passed over
`the IP network to one of NE3 208 or 210, depending upon
`which is controlling NE2 200 at the time of the call. An
`emergency call from device 197 is signaled through NE2
`200 which has access to PSAP 110. The emergency call is
`relayed to the PSAP jurisdiction in 110. Likewise an emer(cid:173)
`gency call made from network entity 194 in jurisdiction 11
`is passed to network entity 208 which is a network area
`router. Network area router 208 passes the call to the PSTN
`to make the connection to the PSAP in 11. Also, an emer(cid:173)
`gency call made from network entity 192 in jurisdiction 17
`is signaled through network area router 208 to take route 17
`from network entity 206 where the call is made, i.e., to the
`PSAP jurisdiction in 17.
`
`[0038] So, for every PSAP jurisdiction where users reside
`in the IP network, at least one gateway ( capable of switching
`a connection between IP network and PSTN technology,
`CAMA or ISDN) also must exist within that area. This
`gateway serves calls originating in that PSAP by either
`routing local calls to the PSTN or converting arriving
`emergency calls from IP packets to circuit-switched tech(cid:173)
`nology for egress to the public network.
`
`TABLE 4
`
`Dial Pattern
`
`Rt#
`
`Priority
`
`Comments
`
`Rt 55
`1 2 3 4
`Go to SG Table
`9 1 1
`Go to SG Table
`9 9 11
`9931111 Go to SG Table
`
`9
`EC! data
`EC! data
`EC! data
`
`normal call
`ITEC call
`ITEC call
`ITEC call
`
`Motorola Solutions, Inc., Ex1014, p. 11
`
`

`

`US 2003/0063714 Al
`
`Apr. 3, 2003
`
`5
`
`[0039] Table 4 is an example of a NAR routing table with
`emergency call number entry examples. Each call number
`entry in this example includes a dial pattern, ECI data (SGI
`priority), a route number and a priority number. In this
`example a first dial pattern 1234 represents any DID number,
`for example, and the ECI data field indicates that the number
`is not an emergency number. This first dial pattern is
`associated with a route number 55 and given a low priority,
`9, in this