Telecommunication Systems, Inc.

Telecommunications Systems, Inc.

Firdaus Aryana

Andrew M Singer

Donald Le Roy Mitchell

Gordon John Hines

Roger Stuart Marshall

Lance Douglas Pitt

Thomas S Ginter

Farhad Kasad

Chih Wang

Michael Cuff

Don P Mitchell

Donald LeRoy Mitchell, Jr

A rapid assignment dynamic ownership queue for text message sessions queues incoming text messages destined for a service bureau, at a network server. Simultaneous access is provided to any one text message of the queued incoming text messages to a plurality of operator terminals at the service bureau. Initial ownership of the one text message is assigned as a result of a first acting terminal of the plurality of operator terminals having completed an action in service to the text message, and ownership is re-assigned to a subsequent operator terminal having completed another action in service to the text message after the first acting terminal. A configurable escalation queue may be implemented to assign an escalation code to each queued item, regardless of its position in the queue list, to alter the presentation of the queue item.

Rapid assignment dynamic ownership queue

Dynamically selecting and facilitating stored caller information to a communications recipient device with a communications event, based on communication recipient credentials (e.g. IP address, MDN, etc.), preferences outlined in a subscriber profile associated with a relevant calling device, and other variables, e.g., time of day, location of calling device, etc. A subscriber is permitted to provision subscriber preferences and subscriber information associated with users of a subscribing communications device in to a subscriber profile, for use during a communications event. Subscriber preferences are defined to place restrictive conditions on stored subscriber information that may be transmitted with a communications event initiated by a corresponding communications device. A content collection node dynamically selects customized caller information via a subscriber information content collection process. Customized caller information is transmitted to appropriate recipient devices with a corresponding communication event.

Mobile user information selection and delivery event based upon credentials and variables

Automatic Location Information (ALI) data that is representative of a landline address is digitally retrieved, and automatically transferred to an emergency call taker over a wireless system emergency network. Importantly, the ALI information is determined based on association to a proximate location. Before an emergency call is initiated, additional environmental information, such as a RFID tag, location beacon, WiFi access point, Bluetooth device, or other communication signal with a known location, is included in the wireless session data exchange, used to match one or more location inputs to a fixed civic location (street address) which is used to dispatch emergency responders. Alternatively, the mechanism matches to a precise geodetic location (e.g., where no civic location is available).

Automated proximate location association mechanism for wireless emergency services

Dynamically selecting and facilitating stored caller information to a communications recipient device with a communications event, based on communication recipient credentials (e.g. MDN, etc.), preferences outlined in a subscriber profile associated with a relevant calling device, and other variables, e.g., time of day, etc. A subscriber provisions subscriber preferences and subscriber information associated with users of a subscribing communications device in to a subscriber profile, for use during a communications event. Subscriber preferences place restrictive conditions on stored subscriber information that may be transmitted with a communications event initiated by a corresponding communications device. A content collection node dynamically selects customized caller information via a subscriber information content collection process. Customized caller information is transmitted to appropriate recipient devices with a corresponding communications event. In the event of a 911 communications event, customized caller information may be transmitted to emergency dispatch personnel via the legacy E2 query interface.

Wireless emergency caller profile data delivery over a legacy interface

A rapid assignment dynamic ownership queue for text message sessions queues incoming text messages destined for a service bureau, at a network server. Simultaneous access is provided to any one text message of the queued incoming text messages to a plurality of operator terminals at the service bureau. Initial ownership of the one text message is assigned as a result of a first acting terminal of the plurality of operator terminals having completed an action in service to the text message, and ownership is re-assigned to a subsequent operator terminal having completed another action in service to the text message after the first acting terminal. A configurable escalation queue may be implemented to assign an escalation code to each queued item, regardless of its position in the queue list, to alter the presentation of the queue item. A No Responders Online feature can indicate if all terminal devices are 'offline'.

No responders online

iAlert_Enhanced_Alert_Manager enables a user to register an interest in their current location, as well as persons, places and/or things in which the user holds some regard. The iAlert_Enhanced_Alert_Manager provides notification and clarifying information to user's devices concerning events/happenstance that have occurred or are likely to occur within a proximity of registered persons, places, and/or things. The iAlert_Enhanced_Alert_Manager comprises data structures (e.g. an Affinity Table, a SPIN table, a SPIN-List Table, an Affinity-List Table, and a Keyword-List Table) to manage affinities, Spheres of Influence (SPINs), and relationships therebetween that may positively or negatively induce a person. Timely notification of events/happenstance to a user comprises the computation of iEvent-vectors and iAlert-vectors. An iEvent-vector contains fields pertaining to events/happenstance whereas an iAlert-vector comprises information pertaining to notifications. Transmission of a notification is determined as a function of the magnitude of an event/happenstance and the proximity of an event/happenstance to registered objects of interest.

Growing community of inventors

Seattle, WA, United States of America

Firdaus Aryana