Patent Application
20080026722
Persons of ordinary skill in the art will realize that the following description of the present invention is exemplary and not in any way limiting. Other embodiments of the invention will readily suggest themselves to such skilled persons who also have the benefit of the present disclosure.
Referring generally to the drawings, for illustrative purposes the present invention is shown embodied in
The word “exemplary” is used in this disclosure to mean “serving as an example, instance, or illustration.” Thus, an embodiment described as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
The term computer readable medium is used to refer to any media used to provide, hold, or carry executable instructions (e.g., software, computer programs) usable for execution by a central processing unit (CPU, microprocessor, DSP, or any other logic device capable of executing instructions). Media includes, but is not limited to, memory readable by the CPU that can be local, remote, volatile, non-volatile, removable, etc., and can take any suitable form such as primary memory, secondary memory including disks, removable cards or flash, remote disks, etc. Computer readable medium further includes any means for providing executable code, programming instructions, and/or decision inputs to a CPU used in a wireless communication device, base station, or other entity with a CPU. The executable code, programming instructions, decision inputs, etc., when executed by a CPU is used to cause the CPU to enable, support, and/or perform the inventive features and functions described herein.
Referring to
Communication network 100 comprises a plurality of base stations shown as base stations 116 and 118. Each base station is connected to a base station controller (BSC) 122 in wireless network 120. Wireless network 120 will typically connect to network 114, which in one embodiment is an ESN, through a mobile switching center (MSC). The MSC is not shown in
Wireless network 120 includes at least one position determination entity (PDE) 124. PDE 124 may be software on a server, and in one embodiment further includes GPS receivers as part of an AGPS system. The GPS receiver(s) use includes but is not limited to obtaining ephemeris data, almanac data, and determining timing differences between the MS and the network. This is in addition to the PDE performing position calculations, as needed.
Also shown is position satellite 102, which in one embodiment is a GPS satellite. Mobile wireless communications devices 104 and PDE 124 have receivers enabled to receive data from the satellite.
Transmission path 106 indicates that mobile communications device 104 may be in communication with, or having its transmission received by, a plurality of cells. Multi-cell communications would be used with position determination technologies that use the mobile's signal to determine the mobile's location, or the signals from the cells could be used in technologies exemplified by AFLT.
Communications network 100 is a very high level diagram. No limitations as to particulars of connectivity or functionality within the network are to be assumed based on this high-level illustration. For example, PSAP 126 is shown as coming from network 114. Although the common embodiment in the US has the PSAP accessible through an ESN, the connection may be any networked connection allowing operable communications with a PSAP. One satellite is shown; depending on the system, typically a land device will receive data from at least 4 satellites in order to determine a location or position. These and similar relationships between high-level illustrations such as
Referring to
MSC 132 is the mobile switching center that initially received the incoming emergency call. Even if radio control is handed off to another MSC, illustrated in
The Coordination Routing Database (CRBD) 138 provides, as at least one of its services, a translation between physical locations expressed as coordinates, such as latitude and longitude, and a string of digits that identifies an Emergency Service Zone (ESZ). ESZs are used to route the call to an appropriate PSAP. Note: this is for networks serving PSAPs that can make use of wireless network location information (are E911 phase 2 compliant). ESZs are used to route the call to PSAPs based on zones (corresponding to physical areas), when multiple PSAPs are available and cover different physical areas.
Emergency Services Network Entity (ESNE) 140 routes and processes the voice portion of the emergency call. Emergency Services Message Entity (ESME) 142 routes and processes the out-of-bandwidth, or non-voice, portion of the emergency call. Cloud 152 generally represents the emergency service network portion of a network, which interfaces eventually to the PSAP 150. The connection is shown as a dotted line to indicate the connection involves other network infrastructure not illustrated.
Each of the above-described network entities carries out its role during an emergency call from MS 154. Included in MS 154 is the software needed to receive and use location information sent to it by the network according to the presently disclosed inventive concepts. This is different than the AGPS or GPS pseudorange data the MS may provide to the network. The MS functionality is described more fully below.
The lines connecting the network entities are shown as solid, exemplified by line 154, where a typical implementation will have the entities in direct communication with each other. Clearly not all communications in a wireless network are indicated; rather, this diagram is for the purpose of illustrating a high-level architectural overview of network entities involved in one embodiment of the presently disclosed inventive concepts.
Referring to
Other Wireless Wide Area Networks (WWAN) standards are also fully contemplated herein, such as GSM and WCDMA, for air interface 200.
Wireless mobile device 210 comprises processor 214 coupled to a memory 212 and to transceiver 208 and receiver 218. Programming is stored in memory 212 and executed by processor 214 for the operation wireless mobile device 210. Transceiver 208 is coupled to antenna 206 for communication with network cell 202. Processor 214 is also coupled to interface 216, which may further be coupled to one or more user-interface (UI) devices (not shown), including but not limited to a display device, input keys, a microphone, a speaker, and TTY/TDD equipment. In the illustrated embodiment location information received from GPS satellites in the wireless mobile device will be sent to the network. Note that memory 212 includes all types of memory, including volatile and non-volatile components, removable, etc.
Referring to
The actions corresponding to box 302 are those associated with detecting that an emergency number has been entered by a caller. In the presently described embodiment, this will be done by the mobile communications device. The detection process can be implemented in any way suitable for the particular device, but would typically include comparing the number entered by the caller to a list of emergency numbers (the list may be a single number), such as 911. The detection process will complete after the caller indicates the call is to be completed. Indicating that the call is to be completed will occur when the caller presses the “call”, “send”, “go” or other button to indicate to the mobile communications device to initiate the call over the air interface. Any other user interface may be used to indicate the initiation of a call, including alternate input means such as voice recognition.
Continuing from box 302 to box 304, the actions include those needed to start the location request timer (LRT). Starting the LRT can take many forms. Embodiments include starting the LRT when “call” or “send” is pressed, or when a channel is assigned to the call. The timer implementation may be any which enables passage of time to be measured at the needed level of granularity.
Box 304 is left for decision point 306. Decision point 306 represents the actions associated with checking the status of the LRT timer. If the timer has not expired, decision point 306 is left for decision point 308. The actions corresponding to decision point 308 are those needed to check if a location information request has been received by the mobile communications device. If no such messages have been received, then the “N” exit is taken to decision point 310.
Decision point 310 involves checking the status of the call. If the call is not active, the “N” exit is taken to box 312, where any actions needed to finish the call are taken (there may not be any, depending on the mobile communication device's current state). If the call is active, then the “Y” exit is taken to decision point 306. The loop comprised of 306→308→310→306 is repeated until the timer expires, a location request has been received, or the call is terminated.
Looking at decision point 308, if a location request has been received then the “Y” exit is taken to box 314. The actions corresponding to box 314 are any needed to respond to a location determination request. In current CDMA networks, the PDE will request location information from the wireless mobile device, and will then use the provided information to make a location determination and coordinate calculation. The results are sent to the PSAP. Included are any actions needed to reset the LRT timer, set a flag that a location determination request has been received, or any other way of implementing a state that reflects the receipt of the location request. After responding to the request and setting any state variables (if needed), box 314 is left for box 312. Box 312 represents the termination of the call from the perspective of this disclosure. Clearly other communication events will typically take place between the user and the PSAP operator before the call session is finally terminated.
In another embodiment (not illustrated), the PDE will wait until it detects a successful transmission of the position location coordinates to the PSAP. If the PDE does not receive an acknowledgement that the data was successfully received, the PDE may resend the data. If still unsuccessful, process flow continues in box 316.
Returning to decision point 306, if the LRT has expired the “Y” exit is taken to box 316. The actions corresponding to box 316 are those needed to generate a set of location coordinates using the system available to the wireless mobile device and its network. In the embodiment presently being described, the mobile communications device will initiate a location determination session on the wireless network. Once location coordinates or other means of identifying a location are generated, the location information is communicated to the mobile communications device. Box 316 is left for box 318.
The actions corresponding to box 318 are those used to communicate location information to the caller. This can take any form designers think most effectively communicates the information to a user under the circumstances. In one embodiment, location information will be displayed as text information on the wireless mobile device. In another embodiment, a synthesized voice message will be provided to the caller. If the wireless mobile device is TTY/TDD enabled, that form of communication may be used. Other device-person communications may be used as well; the presently disclosed inventive concepts are usable with any human-device interface.
Box 318 is left for decision point 320. Decision point 320 represents an embodiment where a caller-response to the location information presented in box 318 is detected and acted upon by the wireless mobile device. If a user action is detected after the location information is put into user-receivable form, it is assumed the user is using the location information. User actions are indicated by button presses, vocoder activity, or any other activation of a component of the MS associated with user activities. Activation of any one or more of these indicates user interaction with the MS. This corresponds to the yes exit, which continues into box 324. The actions corresponding to box 324 are those associated with a user communicating location information to a PSAP operator. After the communication is done, box 324 is eventually left for box 312, corresponding to ending the call.
If no user action is detected at decision point 320, the no exit is taken to box 322. The actions corresponding to box 322 are those needed for the mobile communications device to automatically generate a response targeting the PSAP operator. The auto-generated response will generally match the interface that had been used to communicate the location to the user. If a TTY/TDD device was used, a TTY/TDD response (in electronic form) will be generated and sent to the PSAP operator. If a synthesized voice output was used to communicate the location information to the user, the same source can be used to send an electronic voice signal to the PSAP operator, which will then be heard by the PSAP operator as voice location information. Box 322 is then left for box 312, eventually terminating the call.
Combinations of caller interfaces may be used as well. For example, text may be provided on the mobile communications device's screen. The device may wait until the caller takes an action (button press, vocoder activity). If no action is taken by the caller after a predetermined amount of time, the device may assume the text message was not received by the caller (perhaps because the caller can't see, is trapped out of direct visual sight of the screen, is unconscious, etc.) and may then use a synthesized voice to attempt audio communication with the caller.
Variations in sending location information are fully anticipated, including repeating the automatic transmission a set number of times, using a timer to determine when to stop sending location information, or until a response is detected from the a PSAP operator. The embodiment used will depend on the system in which it is to be used, and what designers decide is complementary to the assumed state of the user. For example, most implementations will make the assumption that no user input means the user is incapacitated, so the automated response will take into consideration that fact that the user needs help and cannot respond.
The embodiment just discussed is usable with current CDMA systems interacting with mobile communication devices having AGPS. Current CDMA systems in North America mostly conform to this configuration. However, it is fully contemplated that the inventive concepts disclosed herein are usable with other system configurations as discussed above.
From the above description of exemplary embodiments of the inventive concepts described herein, it is clear that various techniques can be used for implementing the disclosed concepts without departing from the inventive scope of the disclosure. While the invention has been described with specific reference to certain embodiments, a person of skill in this art who also has the benefit of the present disclosure will recognize that changes can be made in form and detail without departing from the spirit and the scope of the inventive concepts disclosed herein. For example, any location determination technology usable with a mobile device may be used while still staying well within the inventive concepts disclosed.
