WO2006021005A2 - Testing for mobile device locator systems, such as for e911 - Google Patents
Testing for mobile device locator systems, such as for e911 Download PDFInfo
- Publication number
- WO2006021005A2 WO2006021005A2 PCT/US2005/029551 US2005029551W WO2006021005A2 WO 2006021005 A2 WO2006021005 A2 WO 2006021005A2 US 2005029551 W US2005029551 W US 2005029551W WO 2006021005 A2 WO2006021005 A2 WO 2006021005A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- test
- call
- mobile
- message
- communication
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
- H04L63/304—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information intercepting circuit switched data communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/80—Arrangements enabling lawful interception [LI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
Definitions
- a call is automatically forwarded to a public safety answering point (PSAP) also called a 911 call center.
- PSAP public safety answering point
- the caller will tell a 91 1 operator about the emergency and, when possible, will give the caller's location.
- E91 1 enhanced 911
- E911 for wireless communications is being implemented in three stages.
- Phase 1 wireless service providers are required to direct all emergency calls to a PSAP even if the caller is not a subscriber to their service or the device is not activated.
- Phase 1 the FCC requires that a phone number be displayed with each 91 1 call (automatic number identification (ANI)), allowing a PSAP operator to call back if there is a disconnection.
- ANI automatic number identification
- Phase 2 is designed to bring wireless calls up to the level of landline-based E911 calls, which means a caller's phone number and location is automatically identified for each emergency call.
- the E911 for wireless the upgrade is universally complete, all cell phone 911 callers will be pinpointed to a range within FCC guidelines (e.g., 50 meters to 300 feet of the caller's location). For example, a cell phone user's phone number and the address and location of the receiving antenna site will be sent to an E911 tandem, which is the switch that routes 911 calls to an appropriate PSAP based on the ANI-defined geographic location. Once the caller's voice and callback number are transferred to the appropriate PSAP 1 the PSAP operator will be able to view a graphic display that shows the longitude and latitude of the caller as accessed through GPS satellites or other locator means. The PSAP operator's computer links to the ALI database, which stores address data and other information. The details of this process may vary, depending on the types of systems used.
- Wireless service providers are currently configuring their systems to be compliant with the E911 requirements.
- wireless service providers use a significant number of test calls to maintain the functionality and integrity of the E911 service. Testing may be in the context of periodic location accuracy certification, new installation validation, network modification validation, troubleshooting, etc., and may take place over the life of the network (i.e., not just at initial system configuration or implementation).
- Figure 1 is a block diagram showing an example of a system for implementing an E911 testing scheme in an ANSI-41 network.
- Figures 2A-2D are block diagrams showing examples of systems for implementing an E911 testing scheme in variants of a Global System for Mobile
- FIGS. 3A and 3B are block diagrams showing examples of systems for implementing an E911 testing scheme in variants of a Universal Mobile
- FIGS 4A-4B are flow diagrams showing high-level transaction flows between various components of the system of Figure 1 (ANSI-41 network), toon]
- Figures 5A and 5B are flow diagrams showing high-level transaction flows between various components of the system of Figure 2A (GSM E5 network).
- Figures 5C and 5D are flow diagrams showing high-level transaction flows between various components of the system of Figure 2B (GSM E5 network).
- Figures 6A and 6B are flow diagrams showing high-level transaction flows between various components of the system of Figure 2C (GSM Lg-lnterface network).
- Figures 6C and 6D are flow diagrams showing high-level transaction flows between various components of the system of Figure 2D (GSM Lg-lnterface network).
- Figures 7A-7D are flow diagrams showing high-level transaction flows between various components within UMTS systems, such as the UMTS systems of Figures 3A and 3B.
- the same reference numbers identify identical or substantially similar elements or acts. To facilitate the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced (e.g., element 204 is first introduced and discussed with respect to Figure 2).
- a system and method for testing implementation of an E911 wireless system is described herein.
- a wireless service provider uses the infrastructure and capabilities of an unrelated but already- implemented electronic surveillance service, such as the services mandated by the Communications Assistance for Law Enforcement Act of 1994 (CALEA), to test an E911 service. While the CALEA service is unrelated to the E911 service, implementation of E911 testing configurations using the CALEA infrastructure allows for a simplified, efficient, and effective testing scheme for E911 systems, as both services are common to most North American wireless architectures.
- CALEA Communications Assistance for Law Enforcement Act of 1994
- Electronic surveillance services such as CALEA can have many components, including the interception of call content, commonly referred to as CALEA
- CALEA defines "call identifying information” as dialing or signaling information that identifies the origin, direction, destination, or termination of each communication generated or received by a subscriber by means of any equipment, facility, or service of a telecommunications carrier.
- CALEA authorizes certain types of electronic surveillance in the fight against crime and terrorism. More specifically, CALEA defines the existing statutory obligation of telecommunications carriers to assist law enforcement in executing electronic surveillance pursuant to court order or other lawful authorization. For example, CALEA requires carriers to design or modify their systems to ensure that lawfully authorized electronic surveillance can be performed.
- the J-STD-025 standard serves as a CALEA standard for wire line, cellular, and broadband PCS carriers and manufacturers.
- the J-STD-025 standard defines services and features required by wire line, cellular, and broadband PCS carriers to support lawfully authorized electronic surveillance and specifies interfaces needed to deliver intercepted communications and call identifying information to a law enforcement agency.
- the system and method for testing employs test methodology that is independent of the location estimate technology (e.g., U- TDOA, A-GPS, E-OTD, etc.).
- the test methodology is also independent of the wireless network technology (e.g., GSM, UMTS, IS-136, CDMA, etc.).
- test calls are made to a "dummy" 911 recipient.
- the configuration of the dummy 911 recipient is not important. For example, it can be nothing more than a number to a voicemail box.
- the wireless service provider's mobile switching centers MSCs.
- the mobile service provider's MSCs are configured to deliver call-associated event messages to a E911 test platform each time a test mobile station places an emergency call to the dummy 911 recipient.
- the E91 1 test platform is set up to look like a law enforcement message collection function used in a CALEA system.
- the E911 test platform is configured to receive Lawfully Authorized Electronic Surveillance Protocol (LAESP) messages.
- LAESP Lawfully Authorized Electronic Surveillance Protocol
- the type of information sent to the test platform in the form of LAESP messages may include dialing or signaling information that identifies the origin, direction, destination, and/or termination of a communication generated or received by a subscriber.
- the E911 test platform uses the LAESP messages to trigger location requests based on call origination events, to provide notification of intersystem handoffs, to submit location update requests via detection of dual tone multi-frequency (DTMF) signals during the call, and to provide notification of test call release to enable resource reallocation.
- the testing scheme can be used to provide testing of new E911 services prior to PSAP integration, testing of site modifications, troubleshooting, pre-PSAP integration spot validation, and accuracy testing/validation over the life of the E911 system.
- FIG. 1-3B and the following discussion provide a brief, general description of a suitable environment in which the invention can be implemented. Although not required, aspects of the invention are described in the general context of computer-executable instructions, such as routines executed by a general-purpose computer (e.g., a server computer, wireless device, or personal/laptop computer).
- a general-purpose computer e.g., a server computer, wireless device, or personal/laptop computer.
- aspects of the invention can be embodied in a special purpose computer or data processor that is specifically programmed, configured, or constructed to perform one or more of the computer-executable instructions explained in detail herein.
- aspects of the invention can also be practiced in distributed computing environments where tasks or modules are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
- aspects of the invention may be stored or distributed on computer-readable media, including magnetically or optically readable computer disks, as microcode on semiconductor memory, nanotechnology memory, organic or optical memory, or other portable data storage media.
- computer-implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Internet or over other networks (including wireless networks) on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or on any analog or digital network (packet switched, circuit switched, or other scheme).
- a propagation medium e.g., an electromagnetic wave(s), a sound wave, etc.
- packet switched, circuit switched, or other scheme any analog or digital network
- the illustrated embodiments show testing of an E911 system implemented within ANSI-41 , GSM, and UMTS networks.
- a preexisting wireless service provider system already configured for CALEA can be upgraded for E911 testing using only minimum modifications.
- upgrading a preexisting emergency communications services system e.g., such as a preexisting MPC/GMLC system
- the E911 testing system has the capacity to support large numbers of simultaneous calls network-wide, as well as significant numbers of outstanding location request operations without blocking.
- test calls may be stored in the system for documentation or tracking and the testing scheme may include reporting systems.
- the various network components making up a testing platform may be configured to send the results of the location estimate back to the test mobile station via a short messaging service (SMS) message, email server, instant messaging server, etc.
- SMS short messaging service
- the test platform may be configured to send results of a location estimate to a provisioned email address or email list.
- the E911 testing scheme may be implemented in the context of an ANSI-41 environment 100.
- the testing scheme may include a test mobile station 102 from which test calls are placed and a voice response unit 104 (VRU) that provides audible feedback to a user making a test call.
- the ANSI-41 environment may also include a base station 106 and a mobile switching center (MSC) 108.
- the MSC 108 is updated to obtain and store routing translations for a pool of test emergency services routing key numbers.
- the VRU 104 may also receive the test emergency services routing key numbers.
- a special trunking configuration may be used if the MSC 108 is not able to support shared trunk routing which uses a public switched telephone network directory number to reach the VRU 104.
- a home location register (HLR) (not shown) used in the testing scheme may be implemented to store a profile for the test mobile station 102.
- profiles may consist of private mobile directory numbers (MDNs) and/or mobile station ISDNs (MSISDNs), which may be configured so that the test mobile stations 102 cannot receive calls from outside the wireless service provider sector.
- the MSC 108 interfaces with a mobile positioning center (MPC) 1 10 that, together with a position determining entity 1 12, provides location information for the test mobile 102.
- the MPC 110 may have originally been implemented as CALEA infrastructure but may be updated to accommodate the E91 1 testing scheme so that it can identify E91 1 calls that originate from test MDNs.
- the MPC 110 is also updated to use a different emergency services routing key pool for routing the test MDNs (versus the actual E91 1 PSAP pool of emergency services routing keys).
- the MPC 110 may be updated to establish one or more J-STD-036 E2 connections to the E91 1 test server 114.
- An E911 test server 1 14 may then collect and compile location information received from the MPC 1 10 to produce test data.
- the E911 test server 114 may trigger E911 location requests on the MPC 110. Such location requests may be triggered by real time call event messages received as permitted by the underlying CALEA framework. The location responses may be logged onto the E91 1 test server 1 14, which acts as a repository for the collected test data.
- the E911 test server 114 may be configured to immediately send the location estimate messages back to the test mobile station 102 (e.g., via a SMS text message via an email server 1 16).
- the E911 test server 114 and the email server 116 may also be configured to send such a message to another destination (e.g., an email message sent to a desktop networked computer).
- the E911 test server 1 16 may also send out daily logs, via email, for each test mobile station 102 used in the system.
- Other network nodes that may be affected under the testing scheme include a delivery function (DF) node 118, which is provided as part of the underlying CALEA system.
- the delivery function node 1 18 is responsible for delivering intercepted communications to one or more law enforcement collection functions in the standard's format appropriate for the type of intercept.
- the delivery function node 118 delivers messages to the E911 test server 116, which is functioning as a proxy or stand-in for law enforcement collection functions.
- the delivery function may deliver information over various types of channels (e.g., call content channels (CCCs) and call data channels (CDCs).
- CCCs call content channels
- CDCs call data channels
- the testing scheme is intended to predict the quality of mobile station location information to be received by an emergency services network 120, including a public safety answering point (PSAP) system 122 and other components, during an actual 911 call.
- PSAP public safety answering point
- the testing scheme may not need to rely on components of the emergency services network 120 in its implementation.
- the E911 testing scheme may be implemented in the context of a GSM network 200, such as a general packet radio service (GPRS) network.
- GPRS general packet radio service
- the GSM network testing scheme may include a test mobile station 202 and a VRU 204.
- the GSM network may also include a base station 206, and a base station controller (BSC) 208.
- a monitoring unit 210 may monitor communications between the base station 206 and the BSC 208.
- the GSM network 200 may also include a GSM mobile switching center (GSM MSC) 212.
- GSM MSC GSM mobile switching center
- an E911 test server 214 interfaces with an MPC 216 and a CALEA delivery function to collect location information during testing.
- a PDE 220 may be involved in the location determining process for the test mobile 202.
- An email server 222 or other communication component may be involved in the dissemination of test data collected by the E911 test server 214.
- FIGS 2B-2D show other GSM network implementations in which the invention can be implemented.
- various aspects of the GSM network may vary.
- the MPC 216 of Figures 2A and 2B may be replaced with a gateway mobile location center (GMLC) component 226 in the GSM networks depicted in Figures 2C and 2D.
- GMLC gateway mobile location center
- the testing schemes illustrated in figures 2A- 2D are intended to predict the quality of mobile station location information to be received by an emergency services network coupled to the GSM network, including a PSAP system and other components, during an actual 911 call.
- the testing scheme may not need to rely on components of the emergency services network 224 in its implementation.
- the E911 testing scheme may be implemented in the context of a UMTS network 300.
- the UMTS network testing scheme may include a test user endpoint 302 and a VRU 304.
- the UMTS network may also include a base station 306, and a radio network controller (RNC) 308.
- the UMTS network 300 may also include a MSC 310.
- an E911 test server 312 interfaces with a GMLC 314 and a CALEA delivery function 316 to collect location information during testing.
- an email server 318 or other communication component may be involved in the dissemination of test data collected by the E911 test server 312.
- FIG. 3B shows another UMTS network implementation in which the invention can be implemented.
- the testing schemes illustrated in figures 3A and 3B are intended to predict the quality of mobile station location information to be received by an emergency services network coupled to the UMTS network, including a PSAP system and other components, during an actual 91 1 call.
- the testing scheme may not need to rely on components of the emergency services network in its implementation.
- Figures 4A-4B, 5A-5D, and 6A-6D, and 7A-7D are representative flow diagrams that show processes that occur within the various system of Figures 1 , 2A-2D, and 3A-3B. These flow diagrams do not show all functions or exchanges of data but, instead, provide an understanding of commands and data exchanged under the system. Those skilled in the relevant art will recognize that some functions or exchanges of commands and data may be repeated, varied, omitted, or supplemented, and other aspects not shown may be readily implemented. For example, while not described in detail, a message containing data may be transmitted through a message queue, over HTTP, etc.
- the flows represented in Figures 4A-7D are high-level flows in which the entire transaction is shown from initiation to completion. The various entities that may be involved in the transactions of Figures 4A-7D are also depicted throughout Figures 1-3B.
- the test mobile station 102 may include a sequence of communications between various components of the ANSI- 41 network, including the test mobile station 102, the PDE 112, the MSC 108, the E91 1 test server 1 14, the MPC 110, and the VRU 104.
- the test mobile station 102 initiates an emergency services test call.
- the emergency services call may be made by dialing the number "91 1.”
- the emergency services call may be made by dialing a predetermined number that the MSC may recognize as an emergency services test call (e.g., "31 1").
- the MSC 108 configured with various E91 1 features (e.g., features that allow for the display of the 911 caller's phone number at the receiving end), sends a first request message (e.g., ORIGREQ) to the MPC 164.
- the first request message may indicate the cell site and sector from which the mobile call originated, as well as MIN information, MDN information, and ESN information for the test mobile station 102.
- the called party number (CdPN) is identified as "91 1 ,” and the calling party number (CgPN) is identified as the test mobile station 102 (e.g., 555-NXX-XXXX).
- the MSC 108 identifies the test call as a call requesting electronic surveillance (as it would with a CALEA call) and sends a J- STD-025 LAESP origination message to a delivery function (DF) node (shown only in Figure 1).
- DF delivery function
- a forwarding function at the DF node then forwards a LAESP origination message to the E911 test server 116 as if the E911 test server 116 is a CALEA law enforcement collection function.
- the MPC 110 performs one or more of the following steps:
- the MPC 1 10 recognizes the test mobile station 102 as an E911 test mobile station, based on the MDN of the test mobile station (or other identifying information).
- the MPC 110 analyzes the digits in the received origination request message and, based on this analysis, determines a routing scheme for the test call.
- the MPC 110 assigns a temporary test emergency services routing key (ESRK) (or returns a set of test emergency services routing digits (ESRD) associated with the cell/sector) as the routing digits to be used by the MSC 108 and sends this information to the MSC 108.
- ESRK temporary test emergency services routing key
- ESRD test emergency services routing digits
- the MSC 108 forwards the call to a test destination other than the PSAP (e.g., the VRU 104).
- a test destination other than the PSAP
- ISUP integrated services digital network user part
- IAM integrated services digital network user part
- CdPN calling party number
- ESRK test emergency services routing key
- the MPC 1 10 launches a position request message (GPOSREQ) to the appropriate PDE (not shown) associated with the serving cell/sector for the test mobile.
- the PDE 1 12 receives the request and initiates location estimate processes/procedures (which may be location technology dependent).
- call setup signaling is completed.
- the PDE 112 completes the location estimate processes/procedures (or a time-out event occurs).
- the PDE 1 12 then returns the location of the test mobile station to the MPC 110 in the form of latitude and longitude information.
- the MPC 110 returns the location information back to the E911 test server 114.
- the E911 test server 114 logs the location information (test call results) in a report file.
- the E911 test server 114 may also (optionally) send the test call results to the mobile as an SMS message and/or email the test call results to a designated email account, or otherwise report the information as needed.
- the test call is released.
- the MSC 108 sends the E91 1 test server 1 14 an LAESP release message via the CALEA intercept. This permits the E911 server 116 to release any resources associated with the call, assuming any resources have been used.
- the MSC 108 sends a call termination report message is sent to the MPC 1 10 to permit the MPC 110 to release any resources used during the call.
- the MPC 1 10 acknowledges receipt of the call termination report message.
- ANSI-41 network depicted in Figure 1 may include a sequence of communications between the various components, as shown in Figure 4A, in order to update the location for a test mobile station 102 that has moved to a different location after the test call is initially placed.
- an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 4A).
- an operator of the test mobile station 102 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- the MSC 108 receives the code input and in response, sends a dialed digit extraction message to the E91 1 test server 114.
- the E911 test server 114 generates and sends an
- the MPC 110 receives the ESPOSREQ, which triggers the MPC 110 to generate an intersystem position request (ISPOSREQ). The MPC 110 then sends the ISPOSREQ to the MSC 108.
- ISPOSREQ intersystem position request
- the MSC 108 sends back the requested information (e.g., TDMA mobile information, mobile capabilities, serving cell) via an ISPOSREQ response message.
- the MPC 110 builds a GPOSREQ (e.g., based on the ESPOSREQ and ISPOSREQ) to send to the PDE 112 that is requesting a location estimate.
- the PDE 1 12 receives the GPOSREQ and initiates location estimate processes/procedures (which may be location technology dependent).
- the PDE 112 calculates an acceptable location estimate (or a timer expires). The PDE 112 may then return updated location information for the test mobile station 102 to the MPC 110 via a GPOSREQ response (e.g., in the form of latitude and longitude information).
- the MPC 110 returns the location information back to the E911 test server in a ESPOREQ response.
- the E911 test server 114 logs the received location information (e.g., in a report file).
- the E911 test server 114 may also (optionally) send the results to the mobile as an SMS and/or email the results to a designated email account.
- test call is released.
- the MSC 108 sends an LAESP release message to the E911 test server 114 via the CALEA intercept. This may permit the E911 test server 114 to release any resources associated with the test call.
- the MSC 108 may send a call termination report (e.g., CALLTERMRPT) to the MPC 110 to permit it to release any resources associated with the call.
- the MPC acknowledges the call termination report with a response.
- testing scheme may be implemented in a
- the GSM architecture may include several components, including the test mobile station 202, the base station controller 208, the PDE 220, the MSC 212, the E911 test server 214, the MPC 216, and the VRU 204.
- FIG. 5A shows an example of an initial location call flow in the context of a GSM E5 environment.
- the test mobile station 202 initiates an emergency services call.
- the emergency services call may be made by dialing the number "911.”
- the emergency services call may be made by dialing a number for a test call destination (e.g., "311").
- the MSC 212 identifies the test call as a test emergency service call and forwards call to the MPC 216 with the serving cell information (e.g., ESRD) and calling party number (e.g., MDN) in an integrated services digital network user part (ISUP) initial address message (e.g., IAM).
- serving cell information e.g., ESRD
- MDN integrated services digital network user part
- IAM integrated services digital network user part
- the MSC 212 identifies the call as requiring electronic surveillance (i.e., test mobile provisioned on MSC for CALEA intercept) and forwards the call to the MPC 216 with the serving cell information (emergency services routing digits) and mobile directory number (MDN) for the calling party.
- the call forwarding is implemented using a J-STD-025 LAESP origination message sent via a CALEA DF to the E911 Test Server 214, as if the E911 test server 214 is a law enforcement collection function (CF).
- CF law enforcement collection function
- the MPC 216 analyzes the MDN from the IAM message and identifies the call as a test call based on the MDN. The MPC 216 then assigns a temporary test ESRK as the routing digits to the MSC 212. The IAM is returned to the MSC 212 over the ISUP loop-around (e.g., with the called and calling party set equal to the test-ESRK).
- the MPC 216 sends a GPOSREQ message over the E5-interface (e.g., J-STD-036B) to the PDE 220 requesting a location estimate for the test call.
- the PDE 220 triggered by the GPOSREQ message, initiates processes and procedures to generate a location estimate.
- Origination message sends an ESPOSREQ to the MPC 216, which may include the MDN of the test mobile station 202 (as received in the LAESP origination message).
- the MSC 212 forwards the call to the test destination (e.g., a destination other than the PSAP) based on the test ESRK.
- call setup signaling is completed.
- the PDE 220 calculates an acceptable location estimate or a timer expires.
- the PDE 220 returns the location of the test mobile station 202 (e.g., in the form of a latitude and longitude) to the MPC 216 via a GPOSREQ response.
- the MPC 216 returns the location information back to the E911 test server in an ESPOSREQ response.
- the E91 1 test server 214 logs the received location information in a report file.
- the E911 test server 214 may also (optionally) send the received location information to the mobile as a SMS message and/or email the results to a designated email account.
- the test call is released.
- the MSC 212 sends an LAESP release message to the E911 test server 214 via the CALEA intercept to permit the E911 test server 214 to release any resources associated with the call.
- a location update call flow in an GSM network may include a sequence of communications between the various components, as shown in Figure 5A, in order to update the location for a test mobile station 202 that has moved to a different location after the test call is initially placed.
- an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 4A).
- an operator of the test mobile station 202 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- the MSC 212 receives the code input and in response, sends a dialed digit extraction message to the E91 1 test server 214.
- the E91 1 test server 214 generates and sends an
- the MPC 216 receives the ESPOSREQ, which triggers the MPC 216 to generate a GPOSREQ.
- the MPC 216 then sends the GPOSREQ to the PDE 220.
- the PDE 220 calculates an acceptable location estimate (or a timer expires).
- the PDE 220 returns location information (e.g., in the form of a latitude and longitude) for the updated location of the test mobile 202 to the MPC 216 in a GPOSREQ response.
- location information e.g., in the form of a latitude and longitude
- the MPC 110 returns the location information back to the E911 test server in a ESPOSREQ response.
- the E911 test server 214 logs the received location information (e.g., in a report file).
- the E911 test server 214 may also (optionally) send the results to the mobile as an SMS and/or email the results to a designated email account.
- the test call is released.
- the MSC 212 sends an LAESP release message to the E911 test server 214 via the CALEA intercept. This may permit the E911 test server 214 to release any resources associated with the test call.
- FIG. 5C illustrates an example of an initial location call flow in a second version of a GSM E5 network architecture.
- the test mobile station 202 initiates an emergency services test call.
- the MSC 212 identifies the call as an emergency service call and forwards call to the MPC 216 with the serving cell information (ESRD) and calling party number (MDN) in an ISUP initial address message (IAM).
- ESRD serving cell information
- MDN calling party number
- IAM ISUP initial address message
- the MSC 212 identifies the test call as requiring electronic surveillance (i.e., test mobile provisioned on MSC for CALEA intercept) and sends a J-STD-025 LAESP origination message via a CALEA DF to the E911 test server 214 as if the E911 test server 214 is a law enforcement collection function (CF).
- the MPC 216 analyzes the MDN from the IAM message and identifies the call as a test call based on the MDN. The MPC 216 assigns a temporary test ESRK as the routing digits to the MSC.
- the call may not be routed to the MPC 216 via ISUP Loop-around trunks because the MPC 216 does not need call information.
- the route can also be determined by the MSC based on dialed digit string (e.g., '119') or IMSI-specifc switch translations.
- the E911 test server 214 sends a GPOSREQ message to the PDE 220 over the E5-interface (J-STD-036B).
- the sent message may request a location estimate for the test call.
- the PDE 220 initiates processes and procedures to generate a location estimate.
- the MSC 212 forwards the call to the test destination (i.e., not the PSAP) based on the test ESRK (or dialed digits, IMSI, etc).
- call setup signaling is completed.
- the PDE 220 calculates an acceptable location estimate (or a timer expires).
- the PDE 220 returns the location of the test mobile station 202 in the form of a latitude and longitude to the E911 test server 214 in a GPOSREQ response.
- the E911 test server 214 logs the data in a report file.
- the E911 test server 214 may also (optionally) send the results to the mobile as an SMS and/or email the results to a designated email account.
- the test call is released.
- MSC 212 sends an LAESP release message to the E911 test server 214 via the CALEA intercept. This may permit the E911 test server 214 to release any resources associated with the test call.
- Figure 5D illustrates an example of location update call flow in the second version of a GSM E5 network architecture.
- an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 5B).
- an operator of the test mobile station 202 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- the MSC 212 receives the code input and in response, sends a dialed digit extraction message to the E911 test server 214.
- the E911 test server 214 generates and sends a
- the PDE 220 calculates an acceptable location estimate (or a timer expires).
- the PDE 220 returns location information (e.g., in the form of a latitude and longitude) for the updated location of the test mobile 202 to the E91 1 test server 214 in a GPOSREQ response.
- the E911 test server 214 logs the received location information (e.g., in a report file).
- the E911 server may also (optionally) send the results to the mobile as an SMS and/or email the results to a designated email account.
- the test call is released.
- the MSC 212 sends an LAESP release message to the E911 test server 214 via the CALEA intercept. This may permit the E91 1 test server 214 to release any resources associated with the test call.
- FIGS 6A-6D are representative flow diagrams that show an alternate implementation of the testing scheme that incorporates a into a GSM network architecture, and more particularly, a GSM network architecture having an Lg- Interface.
- This network architecture can be implemented with or without the occurrence of an ISUP loop-around and may include a sequence of communications between various network components including a test mobile station 202, a serving mobile location center (SMLC) 228, BSC 208, a MSC 212, an E911 test server 214, a GMLC 226, and a VRU 204.
- SMLC serving mobile location center
- FIG. 6A illustrates an example of an initial location call flow in a GSM Lg- lnterface network architecture.
- the test mobile station 202 initiates an emergency services call.
- the MSC 212 launches a subscriber location report (SLR) message to the GMLC 226 with the test MSISDN and the serving cell/sector from which the mobile call originated (i.e. CGI or ESRD) to request an ESRK.
- SLR subscriber location report
- the MSC 212 identifies the test call as requiring electronic surveillance (i.e., test mobile provisioned on MSC for CALEA intercept) and sends a J-STD-025 LAESP origination message from its CALEA Delivery Function (DF) to the E911 test server 214 as if the server is a law enforcement collection function (CF).
- the GMLC 226 analyzes the MSISDN from the SLR message and identifies the call as a test call (e.g., based on an MSISDN). The GMLC 226 assigns a temporary test ESRK as the routing digits to the MSC. The ESRK is returned to the MSC in a response message.
- the E911 test server 214 sends an ESPOSREQ to the GMLC 226 which includes the MDN of the test mobile station 202, as received in the LAESP Origination message.
- the GMLC 226 receives the ESPOSREQ, which triggers the generation of a provide subscriber location (PSL) request that is sent to the MSC 212.
- PSL subscriber location
- the MSC 212 forwards the test call to the test destination (e.g. a destination other than the PSAP) based on the test ESRK.
- the MSC 212 translates the data contained in the PSL to generate and send a provide location request (PLR) message to the SMLC 228.
- PLR provide location request
- call setup signaling is completed.
- the SMLC 228 calculates/obtains an acceptable location estimate using applicable positioning methods/procedures (or a timer expires).
- the SMLC 228 then returns the location of the test mobile station 204 in the form of a latitude and longitude to the MSC 212 in a PLR response.
- the MSC 212 then returns (via PSL) the location estimate of the test mobile station 204 to the GMLC 226 (e.g., in the form of a latitude and longitude) to the GMLC 226.
- the GMLC 226 returns the location information back to the E91 1 test server 214 in an ESPOSREQ response.
- the E911 server logs the data in a report file.
- the E911 server may also (optionally) send the results to the mobile as an SMS and/or email the results to a designated email account.
- the test call is released.
- an LAESP Release message is sent by the MSC to the E91 1 server via the CALEA intercept to permit the E911 server to release any resources associated with the call (if any).
- the MSC 212 sends a SLR (release) message to the GMLC 226 (e.g., to permit the GMLC 226 to release any resources associated with the call).
- the GMLC 226 acknowledges receipt of the SLR message.
- Figure 6B illustrates an example of location update call flow in the GSM Lg- lnterface network architecture.
- an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 6A).
- an operator of the test mobile station 202 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- a communication 621 it is assumed that an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 6A).
- an operator of the test mobile station 202 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- a communication 621 it is assumed that an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 6A).
- an operator of the test mobile station 202 requests a new E911 location (e.g., by
- the MSC 212 receives the code input and in response, sends a dialed digit extraction message to the E911 test server 214.
- the E91 1 test server 214 generates and sends an
- the GMLC 226 receives the ESPOSREQ which triggers the generation of a PSL message that the GMLC 226 sends to the MSC 212.
- the MSC 212 translates the data contained in the PSL message to generate and send a PLR message to the SMLC 228.
- the SMLC 228 calculates/obtains an acceptable location estimate using applicable positioning methods/procedures (or a timer expires).
- the SMLC 228 returns location information (e.g., in the form of a latitude and longitude) for the updated location of the test mobile 202 to the MSC 212 in a PLR response.
- the MSC 212 returns the location estimate of the test mobile station 202 in the form of a latitude and longitude to the GMLC 226 in a PSL response.
- the GMLC 226 returns the location information back to the E911 test server 214 in a ESPOSREQ response.
- the E91 1 test server 214 logs the data in a report file.
- the E91 1 server may also (optionally) send the results to the mobile as an SMS and/or email the results to a designated email account.
- the test call is released.
- the MSC 212 sends an LAESP release message to the E911 test server 214 via the CALEA intercept. This may permit the E911 test server 214 to release any resources associated with the test call.
- the MSC 212 sends a SLR (release) message to the GMLC 226 to permit the GMLC 226 to release any resources associated with the test call.
- the GMLC 226 acknowledges receipt of the SLR message.
- Figure 6C illustrates an example of an initial location call flow in a GSM Lg- lnterface network architecture with ISUP loop-around.
- the test mobile station 202 initiates an emergency services call.
- the MSC 212 identifies the call as an emergency service call and forwards call to the GMLC 226 with the serving cell information (e.g., ESRD) and calling party number (e.g., MSISDN) in an ISUP initial address message (IAM).
- the MSC 212 uses E911 features within the MSC 212, the MSC 212 sends a PLR message to the SMLC 228 via the BSC 208.
- the MSC 212 identifies the test call as a call requiring electronic surveillance (e.g., as a test mobile provisioned on MSC for CALEA intercept) and sends, for example, a J-STD-025 LAESP origination message from its CALEA delivery function to the E911 test server 214 as if the E911 test server 214 is a law enforcement collection function.
- the GMLC 226 analyzes the MDN of the test mobile station (based on information in the IAM message) and identifies the call as a test call (e.g., based on the MDN or called number). At this point, the GMLC 226 may assign a temporary test ESRK as the routing digits to the MSC 212. The GMLC 226 may return the IAM to the MSC 212 over the ISUP loop-around (e.g., with the called party and calling party set equal to the test ESRK).
- the SMLC 228 upon receiving the PLR initiated by the MSC 212, the SMLC 228 begins the applicable location estimate process and procedures.
- the E911 test server 214 sends an ESPOSREQ message to the GMLC 226.
- the ESPOSREQ may include the MDN of the test mobile station 202 (e.g., as received in the LAESP origination message).
- the MSC 212 forwards the test call to the test destination (e.g., a location other than the PSAP) based on the test ESRK.
- the test destination e.g., a location other than the PSAP
- call setup signaling is completed.
- the SMLC 228 calculates/obtains an acceptable location estimate using applicable processes/procedures (or a timer expires).
- the SMLC 228 sends the location estimate back to the MSC 212 in a PLR response via the BSC 208.
- the MSC 212 returns the location estimate of the test mobile (e.g., in the form of a latitude and longitude information) to the GMLC 226 in a SLR message.
- the GMLC 226 acknowledges receipt of the SLR with a SLR response.
- the GMLC 226 returns the location information back to the E911 server in a ESPOSREQ response.
- the E911 test server 214 may log the data in a report file.
- the E911 test server may also send the results to the test mobile station 202 (e.g., as an SMS message) and/or may email the results to a designated email account.
- test call is released.
- the MSC 212 may send an LAESP release message to the E911 test server via the CALEA intercept (e.g., to permit the E91 1 server to release any resources associated with the call).
- the MSC 212 sends a SLR (release) message to the GMLC 226 to permit the GMLC 226 to release any resources associated with the call.
- the GMLC 226 acknowledges receipt of the SLR message.
- Figure 6D illustrates an example of location update call flow in the GSM Lg- lnterface network architecture with ISUP loop-around.
- an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 6C).
- an operator of the test mobile station 202 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- the MSC 212 receives the code input and in response, sends a dialed digit extraction message to the E91 1 test server 214.
- the E911 test server 214 generates and sends an ESPOSREQ to the GMLC 226 (e.g., by mapping the caselD/calllD to the proper MSISDN and by mapping the information in the dialed digit extraction to the proper location request type).
- the GMLC 226 receives the ESPOSREQ which triggers the generation of a ProvideSubscriberLocation (PSL) that is sent to the MSC.
- PSL ProvideSubscriberLocation
- the MSC 212 translates the data contained in PSL to generate and send a PLR message to the SMLC 228.
- the SMLC 228 calculates/obtains an acceptable location estimate using applicable positioning methods/procedures (or a timer expires).
- the SMLC 228 returns location information for the test mobile station 202 (e.g., in the form of a latitude and longitude) to the MSC 212 in a PLR response.
- the MSC 212 returns the location information to the GMLC 226 in a PSL response message.
- the GMLC 226 returns the location information back to the E911 test server 214 in an ESPOSREQ response.
- the E911 test server may then log the location information in a report file.
- the E911 server may also send the location information to the mobile as an SMS message and/or email the results to a designated email account.
- the test call is released.
- the MSC 212 sends a LAESP release message to the E911 test server 214 via the CALEA intercept (e.g., to permit the E91 1 test server 214 to release any resources associated with the call).
- the MSC 212 sends a SLR (release) message to the GMLC 226 to permit the GMLC 226 to release any resources associated with the call.
- the GMLC 226 acknowledges receipt of the SLR message.
- FIGS 7A-7D are representative flow diagrams that show an alternate implementation of the testing scheme in UMTS network architecture.
- This network architecture can be implemented with or without the occurrence of an ISUP loop- around and may include a sequence of communications between various network components including a test user endpoint 302, a RNC 308, a MSC 310, an E911 test server 312, a GMLC 314, and a VRU 304.
- FIG. 7A illustrates an example of an initial location call flow in a UMTS network architecture.
- the user endpoint 302 initiates an emergency services call.
- the proper signaling message flow for UMTS call setup is not depicted, but condensed into a CM Service request for the purpose of maintaining clarity in the drawings.
- the MSC 310 uses E911 features within the MSC 310, the MSC 310 sends a SLR message to the GMLC 314 to request an ESRK.
- the SLR message may include the test MSISDN and information relating to the serving cell/sector from which the mobile call originated (e.g., CGI or ESRD).
- the MSC 310 identifies the test call as a communication requiring electronic surveillance (e.g., as a test mobile provisioned on the MSC 310 for CALEA intercept) and sends, for example, a J- STD-025 LAESP origination message from its CALEA delivery function to the E911 test server 312 as if the E911 test server 312 is a law enforcement collection function (CF).
- CF law enforcement collection function
- the GMLC 314 analyzes the MSISDN from the
- the GMLC 314 may assign a temporary test ESRK as the routing digits to the MSC 310.
- the SLR response message enables the ESRK to be returned to the MSC 310.
- the E911 test server 312 sends an ESPOSREQ (which may include the MDN of the user endpoint 302, as received in the LAESP origination message) to the GMLC 314.
- the GMLC 314 receives the ESPOSREQ, which triggers the generation of a PSL message that the GMLC 314 sends to the MSC 310.
- the MSC 310 based on the test ESRK, forwards the call to the test destination (e.g., a destination other than the PSAP).
- the MSC 310 translates the data contained in the PSL to generate and send a LRC message to the RNC 308.
- call setup signaling is completed.
- the RNC 308 calculates/obtains an acceptable location estimate using applicable positioning methods/procedures (or a timer expires).
- the RNC 308 returns the location of the user endpoint 302 (e.g., in the form of a latitude and longitude) to the MSC 310 in a location report message.
- the MSC 310 returns the location estimate of the user endpoint 302 in the form of a latitude and longitude to the GMLC 314 in a PSL response message.
- the GMLC 314 returns the location information back to the E911 test server 312 in an ESPOSREQ response.
- the E911 test server 312 logs the data in a report file.
- the E911 test server 312 may also (optionally) send the results to a designated recipient via, for example, an SMS or email message.
- the test call is released.
- the MSC 310 sends an LAESP release message to the E911 test server via the CALEA intercept to permit the E911 test server to release any resources associated with the call.
- the MSC 310 sends an SLR (release) message to the GMLC 314 to permit the GMLC 314 to release any resources associated with the test call.
- the GMLC 314 acknowledges receipt of the SLR message.
- Figure 7B illustrates an example of location update call flow in the UMTS network architecture.
- an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 7A).
- an operator of the test user endpoint 302 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- the MSC 310 receives the code input and in response, sends a dialed digit extraction message to the E911 test server 214.
- the E911 test server 312 generates and sends an
- the GMLC 314 receives the ESPOSREQ which triggers the generation of a PSL message that the GMLC 314 sends to the MSC 310.
- the MSC 310 translates the data contained in the PSL to generate and send an LRC message to the RNC 308.
- the RNC 308 calculates/obtains an acceptable location estimate using applicable positioning methods/procedures (or a timer expires).
- the RNC 308 returns the location of the test user endpoint 302 (e.g., in the form of a latitude and longitude) to the MSC 310 in a LocationReport (LR) message.
- LR LocationReport
- the MSC 310 returns the location estimate of the test user endpoint 302 to the GMLC 314 in a PSL response message.
- the GMLC 314 returns the location information back to the E911 server in and ESPOSREQ response.
- the E911 test server 312 logs the data (e.g., in a report file).
- the E911 server may also (optionally) send the results to a designated source (e.g., as an SMS to the test user endpoint 302 and/or as an email to a designated email account).
- the test call is released.
- the MSC 310 sends an LAESP release message to the E911 test server 312 via the CALEA intercept to permit the E911 test server 312 to release any resources associated with the call (if any).
- the MSC 310 sends a SLR (release) message to the GMLC 314 to permit the GMLC 314 to release any resources associated with the call.
- the GMLC 314 acknowledges receipt of the SLR message.
- FIG. 7C illustrates an example of an initial location call flow in a UMTS network architecture with ISUP loop-around.
- the test user endpoint 302 initiates an emergency services call.
- the MSC 310 identifies the call as an emergency service call and forwards call to the GMLC 314 with the serving cell information (ESRD) and calling party number (MSISDN) in an ISUP initial address message (IAM).
- ESRD serving cell information
- MSISDN calling party number
- IAM ISUP initial address message
- the MSC 310 launches a LRC message to the RNC 308.
- the MSC 310 identifies the call as requiring electronic surveillance (e.g., as a test mobile provisioned on the MSC 310 for CALEA intercept) and sends, for example, a J-STD-025 LAESP origination message from its CALEA delivery function to the E911 test server 312, as if the E911 test server 312 is a law enforcement collection function.
- the GMLC 314 analyzes the MDN (e.g., from the MDN).
- the RNC 308 upon receiving the LRC initiated by the MSC 310, the RNC 308 begins executing applicable location estimate process and procedures.
- the E911 test server 312 sends an ESPOSREQ message to the GMLC 314, which may include the MDN of the test user endpoint 302 (e.g., as received in the LAESP origination message).
- the MSC 310 forwards the call to the test destination (e.g., a destination other than the PSAP) based on the test ESRK.
- the RNC 308 calculates/obtains an acceptable location estimate (or a timer expires).
- the RNC 308 sends the location estimate back to the MSC 310 in a LR message.
- the MSC 310 returns the location estimate of the test user endpoint 302 (e.g., in the form of a latitude and longitude) to the GMLC 314 in a SLR message.
- the GMLC 314 acknowledges receipt of the SLR message with a SLR response message.
- the GMLC 314 returns the location information back to the E911 test server 312 (e.g., in an ESPOSREQ response message).
- the E911 test server 312 logs the location information in a report file.
- the E911 test server 312 may also send the location information to a designated client (e.g., the test user endpoint 302 as an SMS and/or a designated email account via email).
- the test call is released.
- the MSC 310 sends an LAESP release message to the E911 test server 312 via the CALEA intercept to permit the E911 test server 312 to release any resources associated with the call.
- the MSC 310 sends a SLR (release) message to the GMLC 314 to permit the GMLC 314 to release any resources associated with the call.
- the GMLC 314 acknowledges receipt of the SLR message.
- Figure 7D illustrates an example of location update call flow in the UMTS network architecture with ISUP loop-around.
- a communication 761 it is assumed that an emergency services call has previously been established (e.g., call setup signaling is completed per the initial location call flow of Figure 7A).
- an operator of the test user endpoint 302 requests a new E911 location (e.g., by typing in a code using a keypad of the test mobile station).
- the MSC 310 receives the code input and in response, sends a dialed digit extraction message to the E91 1 test server 214.
- the E911 test server 312 generates and sends an
- the GMLC 314 receives the ESPOSREQ, which triggers the generation of a PSL message that the GMLC 314 sends to the MSC 310.
- the MSC 310 translates the data contained in the PSL to generate and send an LRC message to the RNC 308.
- the RNC 308 calculates/obtains an acceptable location estimate using applicable positioning methods/procedures (or a timer expires).
- the RNC 308 returns the location of the test user endpoint 302 (e.g., in the form of a latitude and longitude) to the MSC 310 in a LocationReport (LR) message.
- the MSC 310 returns the location estimate of the test user endpoint 302 to the GMLC 314 in a PSL response message.
- the GMLC 314 returns the location information back to the E91 1 server in an ESPOSREQ response.
- the E911 test server 312 logs the data (e.g., in a report file).
- the E91 1 server may also (optionally) send the results to a designated source (e.g., as an SMS to the test user endpoint 302 and/or as an email to a designated email account).
- a designated source e.g., as an SMS to the test user endpoint 302 and/or as an email to a designated email account.
- the test call is released.
- the MSC 310 sends an LAESP release message to the E911 test server 312 via the CALEA intercept to permit the E911 test server 312 to release any resources associated with the call (if any).
- the MSC sends a SLR (release) message to the GMLC 314 to permit the GMLC 314 to release any resources associated with the call.
- the GMLC 314 acknowledges receipt of the SLR message.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Technology Law (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Alarm Systems (AREA)
- Monitoring And Testing Of Exchanges (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA002577887A CA2577887A1 (en) | 2004-08-19 | 2005-08-19 | Testing for mobile device locator systems, such as for e911 |
JP2007528040A JP2008511209A (en) | 2004-08-19 | 2005-08-19 | Test on mobile device locator system for E911 etc. |
EP05826813A EP1784997A4 (en) | 2004-08-19 | 2005-08-19 | Testing for mobile device locator systems, such as for e911 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US60296004P | 2004-08-19 | 2004-08-19 | |
US60/602,960 | 2004-08-19 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006021005A2 true WO2006021005A2 (en) | 2006-02-23 |
WO2006021005A3 WO2006021005A3 (en) | 2006-09-28 |
Family
ID=35908244
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2005/029551 WO2006021005A2 (en) | 2004-08-19 | 2005-08-19 | Testing for mobile device locator systems, such as for e911 |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1784997A4 (en) |
JP (1) | JP2008511209A (en) |
CA (1) | CA2577887A1 (en) |
WO (1) | WO2006021005A2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8451987B1 (en) * | 2007-12-13 | 2013-05-28 | Sprint Communcations Company L.P. | Detecting 911 service disruptions |
WO2018111937A1 (en) * | 2016-12-12 | 2018-06-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Emergency call routing virtual testing apparatus |
EP3439353A1 (en) * | 2017-08-04 | 2019-02-06 | Deutsche Telekom AG | Method for performing end-to-end testing of an emergency call or quality management system or an emergency call or quality management functionality, mobile communication network, and system, program and computer program product |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5712900A (en) * | 1996-05-21 | 1998-01-27 | Ericsson, Inc. | Emergency call back for roaming mobile subscribers |
US5963866A (en) * | 1997-01-15 | 1999-10-05 | Lucent Technologies Inc. | Wireless location messaging |
US5923744A (en) * | 1997-04-24 | 1999-07-13 | Ericsson Inc. | Intercepting call communications within an intelligent network |
US6577865B2 (en) * | 1998-11-05 | 2003-06-10 | Ulysses Holdings, Llc | System for intercept of wireless communications |
US6782264B2 (en) * | 1999-01-08 | 2004-08-24 | Trueposition, Inc. | Monitoring of call information in a wireless location system |
US6184829B1 (en) * | 1999-01-08 | 2001-02-06 | Trueposition, Inc. | Calibration for wireless location system |
US6873290B2 (en) * | 1999-01-08 | 2005-03-29 | Trueposition, Inc. | Multiple pass location processor |
US6792080B1 (en) * | 2000-05-31 | 2004-09-14 | Lucent Technologies Inc. | System and method for testing enhanced 911 signalling over a digital loop carrier trunk |
US6868410B2 (en) * | 2000-06-05 | 2005-03-15 | Stephen E. Fortin | High-performance location management platform |
US6745011B1 (en) * | 2000-09-01 | 2004-06-01 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
US7242948B2 (en) * | 2001-03-23 | 2007-07-10 | Lucent Technologies Inc. | Providing location based directory numbers for personalized services |
US20030025476A1 (en) * | 2001-04-30 | 2003-02-06 | Trela Richard Steven | Method of distributing widespread portable emergency cellular power and e-911 assistance |
US7107619B2 (en) * | 2001-08-31 | 2006-09-12 | International Business Machines Corporation | System and method for the detection of and reaction to denial of service attacks |
US6597916B2 (en) * | 2001-12-26 | 2003-07-22 | Siemens Information And Communication Networks, Inc. | Hybrid architecture for supporting location determination in a wireless network |
US6922565B2 (en) * | 2002-03-28 | 2005-07-26 | Telecommunication Systems, Inc. | Public safety access point (PSAP) selection for E911 wireless callers in a GSM type system |
US6996392B2 (en) * | 2002-09-03 | 2006-02-07 | Trueposition, Inc. | E911 overlay solution for GSM, for use in a wireless location system |
US7174149B2 (en) * | 2003-07-14 | 2007-02-06 | Lucent Technologies Inc. | Method and system for indirectly establishing a call |
US7177399B2 (en) * | 2004-02-27 | 2007-02-13 | Nortel Network Limited | Determining the geographical location from which an emergency call originates in a packet-based communications network |
-
2005
- 2005-08-19 CA CA002577887A patent/CA2577887A1/en not_active Abandoned
- 2005-08-19 WO PCT/US2005/029551 patent/WO2006021005A2/en active Application Filing
- 2005-08-19 JP JP2007528040A patent/JP2008511209A/en active Pending
- 2005-08-19 EP EP05826813A patent/EP1784997A4/en not_active Withdrawn
Non-Patent Citations (1)
Title |
---|
See references of EP1784997A4 * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8451987B1 (en) * | 2007-12-13 | 2013-05-28 | Sprint Communcations Company L.P. | Detecting 911 service disruptions |
WO2018111937A1 (en) * | 2016-12-12 | 2018-06-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Emergency call routing virtual testing apparatus |
US11490315B2 (en) | 2016-12-12 | 2022-11-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Emergency call routing virtual testing apparatus |
EP3439353A1 (en) * | 2017-08-04 | 2019-02-06 | Deutsche Telekom AG | Method for performing end-to-end testing of an emergency call or quality management system or an emergency call or quality management functionality, mobile communication network, and system, program and computer program product |
Also Published As
Publication number | Publication date |
---|---|
EP1784997A4 (en) | 2009-11-11 |
CA2577887A1 (en) | 2006-02-23 |
EP1784997A2 (en) | 2007-05-16 |
WO2006021005A3 (en) | 2006-09-28 |
JP2008511209A (en) | 2008-04-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7966020B2 (en) | Wireless user based notification system | |
CN102640090B (en) | Location intelligence management system | |
US8515565B2 (en) | Method and system for an integrated incident information and intelligence system | |
CN101682827B (en) | Method and system for call management based on geographical location | |
US7548158B2 (en) | First responder wireless emergency alerting with automatic callback and location triggering | |
EP2070354B1 (en) | System, apparatus and method for location related data interception | |
JP5279212B2 (en) | Emergency communication method, server, network and computer program for such communication | |
US8805415B2 (en) | Systems and methods for determination of mobile devices in or proximate to an alert area | |
EP1460876A2 (en) | Lawful intercept service | |
US20090137222A1 (en) | Location-based alert system | |
US20150312527A1 (en) | Video surveillance system using mobile terminals | |
US20210058508A1 (en) | Emergency Network Test Apparatus and Method | |
CN105188134A (en) | Mobile terminal locating system and mobile terminal locating method | |
WO2006021005A2 (en) | Testing for mobile device locator systems, such as for e911 | |
WO2013097089A1 (en) | Method for monitoring position of mobile subscriber and monitoring system | |
US20210368320A1 (en) | Employing data from a combination of cell sectors | |
WO2009070029A1 (en) | Location-based alert system | |
CN107194852A (en) | The method that unaware region mobile personnel accurately monitors | |
WO2012177279A1 (en) | Cellular messaging alert method and system | |
EP2862341B1 (en) | Methods, computer program products and apparatuses enabling to conceal lawful interception from network operators | |
Kamat et al. | Emergency Handling System | |
AU2012216715A1 (en) | Method and system for an integrated incident information and intelligence system | |
NO327933B1 (en) | Location-based notification service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007528040 Country of ref document: JP Ref document number: 2577887 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005826813 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2005826813 Country of ref document: EP |