Patent application number | Description | Published |
20090147775 | Ancillary data support in session initiation protocol (SIP) messaging - A SIP ancillary data server provides host to auxiliary data for an emergency SIP session (call) uniquely referred to in a transported SIP header. In a manner similar to how location is represented in an emergency call, a SIP header is extended. The extended SIP Header contains one of two possible types of content elements: either (a) a content pointer element to a SIP Message body part (a “cid:”, or content identifier); or (b) an (a.k.a, “info_URI” in this document). | 06-11-2009 |
20100003976 | Mobile based area event handling when currently visited network does not cover area - An area event handler informs when a target mobile enters or leaves a network covering a pre-defined target area, and re-aims an original area event request. When the event occurs, the mobile sends a location report to an initiator of the request. A PLMN list with estimated geographic coverage areas is stored in a Home GMLC, and sent to each relevant mobile. When a mobile enters new network coverage, it uses this list for network access selection. When the Home GMLC discovers that the currently visited PLMN does not serve the original target area, it modifies the area event to the that mobile, so that the Home GMLC will be notified when the target mobile once again enters a PLMN that serves the original target area. Then, after being so notified, the Home GMLC re-sends the original area event location service request to the target mobile. | 01-07-2010 |
20100284366 | Multiple location retrieval function (LRF) network having location continuity - An IMS emergency call is reliably handed off within the PS domain or from the PS domain to the CS domain, by providing continuous support of location of a user device on behalf of a PSAP. The invention provides for handover of an IMS emergency call with EPS/GPRS access in a multi-LRF environment. Emergency location services for CS based emergency and/or IMS based emergency location services are often provided by multiple emergency location service providers. The information element that is critical for supporting Location Continuity in Multi-LRF environment can be either the assigned ESQK or the Serving LRF address. ESQK is assigned by the Serving LRF during IMS emergency call setup, and is used to uniquely identify the emergency service provider that operates the serving LRF. A simpler implementation uses the Serving LRF's address to identify the Serving LRF during and after the handover (PS-PS or PS-CS). | 11-11-2010 |
20100323674 | Mobile based area event handling when currently visited network does not cover area - An area event handler informs when a target mobile enters or leaves a network covering a pre-defined target area, and re-aims an original area event request. When the event occurs, the mobile sends a location report to an initiator of the request. A PLMN list with estimated geographic coverage areas is stored in a Home GMLC, and sent to each relevant mobile. When a mobile enters new network coverage, it uses this list for network access selection. When the Home GMLC discovers that the currently visited PLMN does not serve the original target area, it modifies the area event to the that mobile, so that the Home GMLC will be notified when the target mobile once again enters a PLMN that serves the original target area. Then, after being so notified, the Home GMLC re-sends the original area event location service request to the target mobile. | 12-23-2010 |
20110064046 | User plane emergency location continuity for voice over internet protocol (VoIP)/IMS emergency services - Continuity of location information relating to an IMS emergency call during their IMS emergency call is maintained by triggering, during an IMS emergency call, a request to a location service based on an occurrence of a handover of an IMS emergency calling mobile device. A physical user plane location server initiates a user plane positioning request, and an updated location of the IMS emergency call is obtained during the IMS emergency call but after the handover. Updated location information relating to an IMS emergency caller is kept track of during IMS handover during their IMS emergency call by mapping access network information relating to a mobile IMS emergency calling device. Coverage information relating to a plurality of location servers is maintained, and a currently serving location server is associated with an updated location of the IMS emergency caller as the IMS emergency caller changes location during an IMS emergency call. | 03-17-2011 |
20110134839 | User plane location based service using message tunneling to support roaming - An improved User Plane location based service (LBS) architecture and message flow, enabling seamless User Plane location based services even when a mobile or wireless device has roamed among different carrier networks. The present invention overcomes constraints inherent in the current protocol for roaming support defined by the Secure User Plane Location Service specification. A location system is enabled to automatically fall back to a message tunneling mechanism to ensure the security of a communication path between the location service system and the target wireless device, ensuring that the communication path is uninterrupted as the wireless device travels. | 06-09-2011 |
20120149371 | User Plane Location Based Service Using Message Tunneling to Support Roaming - An improved User Plane location based service (LBS) architecture and message flow, enabling seamless User Plane location based services even when a mobile or wireless device has roamed among different carrier networks. The present invention overcomes constraints inherent in the current protocol for roaming support defined by the Secure User Plane Location Service specification. A location system is enabled to automatically fall back to a message tunneling mechanism to ensure the security of a communication path between the location service system and the target wireless device, ensuring that the communication path is uninterrupted as the wireless device travels. | 06-14-2012 |
20120178443 | Area event handling when current network does not cover target area - Area event triggers are handled by receiving an original area event trigger with an initial target area within a given mobile network, for a given target mobile device. When the target mobile device is outside the mobile network serving the target area, a first changed area event trigger based on entry into the given mobile network is transmitted to the given target mobile device. When the first changed area event trigger becomes satisfied, a second changed area event trigger is generated based on entry into the initial target area, and transmitted to the given target mobile device. The second changed area event trigger may be based on entry into a region larger than, but including, the initial target area. Then when the second changed area event trigger becomes satisfied, the original area event trigger may be transmitted to the target mobile device. | 07-12-2012 |
20120184239 | Emergency 911 Data Messaging - A data request is generated (e.g., text, email, SMS, multimedia messaging system (MMS), etc.) from a source device. The data request is delivered to a PSAP or other emergency monitoring service location in a useable format. Exemplary useable formats include a canned voice message, delivery to a call center that translates data to voice, text to speech, and text to instant messaging (IM). Additional information and location are staged for use by the PSAP or other monitoring service location. | 07-19-2012 |
20120259984 | Ancillary data support in session initiation protocol (SIP) messaging - A SIP ancillary data server provides host to auxiliary data for an emergency SIP session (call) uniquely referred to in a transported SIP header. In a manner similar to how location is represented in an emergency call, a SIP header is extended. The extended SIP Header contains one of two possible types of content elements: either (a) a content pointer element to a SIP Message body part (a “cid:”, or content identifier); or (b) an (a.k.a, “info_URI” in this document). | 10-11-2012 |
20120263279 | Extended Efficient Usage of Emergency Services Keys - An emergency services key (e.g., ESQK or ESRK) is guaranteed to be available from a limited size ESQK pool. A plurality of ESQKs are grouped into a pool of emergency service keys “ESQK Pool ID”, each including anywhere from 1 to N number of ESQKs. Each ESQK preferably has a “Timestamp”, information relating to the specific emergency E911 call (“Call Data ID”), a guard timer, and an optional hold timer. The ESQK having a Call Data ID=“NULL”, and having the oldest Timestamp, is chosen for selection. If no such ESQK has both Call Data ID=NULL and the oldest Timestamp is found, then the ESQK with merely the oldest Timestamp is selected. The timestamp is reset to a current time plus a guard timer, or hold timer if desired. | 10-18-2012 |
20130059604 | Mobile Internet Protocol (IP) Location - A mobile IP location server that retrieves the location of a mobile device based on the public IP address that a mobile device is using. A mobile IP location server comprises a mobile location protocol interface, an identifier resolver, and a location manager. The mobile location protocol interface interacts with location applications and receives and responds to location requests. The identifier resolver converts a device's public IP address to a real mobile identifier (e.g. MSISDN) and performs address conversion by either interacting with an HTTP proxy server or querying a network address translation (NAT) table. The location manager retrieves the location of a mobile device given the device's real mobile identifier (e.g. MSISDN). A web application requests mobile IP location services by transmitting an IP request to the mobile IP location server. An IP location request contains a mobile device's public IP address, port number, and any application specific information. | 03-07-2013 |
20140066018 | Location Based Privacy for Proximity Services - Location based privacy settings for proximity based services that enable an end-user to define one or more geographic areas, and then explicitly opt in or opt out to proximity based services per geographic area. Location based privacy settings can be stored and managed at a network level or stored and managed locally. In the network-centric solution, privacy settings for proximity based services are defined via a subscriber privacy register. In the mobile-centric solution, privacy settings for proximity based services are defined via a user interface on a proximity services enabled device. When a proximity services enabled device receives a request for proximity based services (i.e. a peer discovery signal command for device discovery or a peer-to-peer communications request for direct communications), the device checks the current date/time and a serving network identifier/current location against location based privacy settings to determine if proximity based services are allowed on the device. | 03-06-2014 |
20140066056 | User Plane Location based Service Using Message Tunneling to Support Roaming - An improved User Plane location based service (LBS) architecture and message flow, enabling seamless User Plane location based services even when a mobile or wireless device has roamed among different carrier networks. The present invention overcomes constraints inherent in the current protocol for roaming support defined by the Secure User Plane Location Service specification. A location system is enabled to automatically fall back to a message tunneling mechanism to ensure the security of a communication path between the location service system and the target wireless device, ensuring that the communication path is uninterrupted as the wireless device travels. | 03-06-2014 |
20140135023 | Area Event Handling When Current Network Does Not Cover Target Area - Area event triggers are handled by receiving an original area event trigger with an initial target area within a given mobile network, for a given target mobile device. When the target mobile device is outside the mobile network serving the target area, a first changed area event trigger based on entry into the given mobile network is transmitted to the given target mobile device. When the first changed area event trigger becomes satisfied, a second changed area event trigger is generated based on entry into the initial target area, and transmitted to the given target mobile device. The second changed area event trigger may be based on entry into a region larger than, but including, the initial target area. Then when the second changed area event trigger becomes satisfied, the original area event trigger may be transmitted to the target mobile device. | 05-15-2014 |
20140171112 | Location Service Requests Throttling - A technique to allow a server such as a location server to throttle concurrent or closely timed location requests for the position of a given wireless device such that within a certain time period preferably only one location request will be initiated to the positioning engine and the remaining closely-timed location requests will be buffered or cached. When a position for the given wireless device is returned per the outstanding location request, then the retrieved position will be used to respond to each of the buffered location requests. Thus, a plurality of location requests are satisfied with a single request to the positioning engine. By optimizing the use of cached position requests, throttling of location requests per the invention reduces network traffic significantly, increases the efficiency of a positioning server (therefore reducing business cost), and provides for an improved grade or quality of location based services in general. | 06-19-2014 |
20140189112 | User Plane Location Services Over Session Initiation Protocol (SIP) - A method and mechanism to allow a location server to initiate a user plane location service (e.g., SUPL defined by OMA) procedure to a user plane enabled device via Instant Messaging, or alternatively, via an existing SIP session if a multimedia session is already established. The location request is signaled to the user plane enabled device via a SIP INFO message. The location request uses SIP messaging to overcome firewall and other network security issues. Location using SUPL over SIP may be provided about a caller making an E911 emergency call. An Instant Message may be sent to the user plane enabled device, e.g., a VoIP wireless phone. | 07-03-2014 |
20150017943 | Emergency 911 Data Messaging - A data request is generated (e.g., text, email, SMS, multimedia messaging system (MMS), etc.) from a source device. The data request is delivered to a PSAP or other emergency monitoring service location in a useable format. Exemplary useable formats include a canned voice message, delivery to a call center that translates data to voice, text to speech, and text to instant messaging (IM). Additional information and location are staged for use by the PSAP or other monitoring service location. | 01-15-2015 |
20150023477 | Extended Efficient Usage of Emergency Services Keys - An emergency services key (e.g., ESQK or ESRK) is guaranteed to be available from a limited size ESQK pool. A plurality of ESQKs are grouped into a pool of emergency service keys “ESQK Pool ID”, each including anywhere from 1 to N number of ESQKs. Each ESQK preferably has a “Timestamp”, information relating to the specific emergency E911 call (“Call Data ID”), a guard timer, and an optional hold timer. The ESQK having a Call Data ID=“NULL”, and having the oldest Timestamp, is chosen for selection. If no such ESQK has both Call Data ID=NULL and the oldest Timestamp is found, then the ESQK with merely the oldest Timestamp is selected. The timestamp is reset to a current time plus a guard timer, or hold timer if desired. | 01-22-2015 |
20150072713 | Extended Area Event for Network Based Proximity Discovery - A network-centric device discovery solution that leverages area event location services. A proximity server (PS) performing device discovery for a discoverer mobile initiates an area event, via a location server, for each device subscribed to the same proximity service group as the discoverer mobile and camped on the same zone as the discoverer mobile. The area event notifies the PS each time such device moves into an area of an E-CGI and/or WiFI access point where the discoverer mobile attaches. If the PS receives an area event notification for the device camped on the same zone as the discoverer mobile, the PS requests location information for the device and uses returned location information to determine if the device is within a predefined proximity of the discoverer mobile. If the device is within a predefined proximity of the discoverer mobile, the PS sends a proximity alert message to the discoverer mobile. | 03-12-2015 |
Patent application number | Description | Published |
20090004999 | Solutions for voice over internet protocol (VoIP) 911 location services - An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a mobile VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Mid-call updating of location of a moving VoIP terminal is provided to a PSAP. The location of the VoIP is validated using HTTP based protocol by pushing location information to a VoIP location server, and comparing it against a geographic location database to confirm that a contained street address is valid. | 01-01-2009 |
20110222441 | Solutions for voice over internet protocol (VolP) 911 location services - An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a mobile VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Mid-call updating of location of a moving VoIP terminal is provided to a PSAP. The location of the VoIP is validated using HTTP based protocol by pushing location information to a VoIP location server, and comparing it against a geographic location database to confirm that a contained street address is valid. | 09-15-2011 |
20130163589 | Solutions for Voice Over Internet Protocol (VoIP) 911 Location Services - An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a mobile VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Mid-call updating of location of a moving VoIP terminal is provided to a PSAP. The location of the VoIP is validated using HTTP based protocol by pushing location information to a VoIP location server, and comparing it against a geographic location database to confirm that a contained street address is valid. | 06-27-2013 |
20140286197 | Solutions for Voice Over Internet Protocol (VoIP) 911 Location Services - An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a mobile VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Mid-call updating of location of a moving VoIP terminal is provided to a PSAP. The location of the VoIP is validated using HTTP based protocol by pushing location information to a VoIP location server, and comparing it against a geographic location database to confirm that a contained street address is valid. | 09-25-2014 |