Wireless Emergency Services Protocols Translator Between ANSI-41 and VoIP Emergency Services Protocols

• US 20130148555A1
• Filed: 02/04/2013
• Published: 06/13/2013
• Est. Priority Date: 05/30/2008
• Status: Active Grant

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: Gordon J. Hines, Todd Poremba Jr, Victor Burton
• Inventors: Hines, Gordon J., Burton, Victor, Poremba, Todd Jr.
• Granted Patent: US 9,001,719 B2
• Time in Patent Office: Days
• US Class Current: 370/310
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 76/50 for emergency connections
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

A protocol converter or translator between ANSI-41 ORREQs and VoIP V2 messaging. The protocol converter may alternatively (or also) provide conversion between GMS MAP and VoIP V2 messaging. Interaction of VSPs with a Mobile Positioning Center (MPC) or a Gateway Mobile Location Center (GMLC) is permitted, as is interaction of wireless carriers with a Voice Positioning Center (VPC). In this way existing GMLCs or MPCs may be used to service VoIP 9-1-1 calls. Moreover, operators of Voice Positioning Centers (VPCs) who implement wireless offerings can re-use their existing VPCs to service wireless 9-1-1 calls.

Claims

1-21. -21. (canceled)

22. Apparatus to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP, comprising:

a receiver to receive, from a mobile switching (MSC), an ANSI-41 ORREQ containing at least one of a call back number (CBN) and emergency service routing digits (ESRD);

a converter to convert said at least one of a CBN and an ESRD to a VoIP request;

a transmitter to send, to a VoIP positioning center (VPC), said VoIP request; and

a VoIP receiver to receive, from said VoIP positioning center (VPC), said VoIP request including at least one of an emergency service query key (ESQK) and an emergency service routing number (ESRN), said VoIP request having said at least one of an ESQK and an ESRN inserted in at least one of a designated field;

whereby said ORREQ permits setup of an emergency services call with at least one of an ISDN User Part (ISUP) and Multi-Frequency (MF) signaling.

23. Apparatus to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP according to claim 22, wherein said at least one of a designated field comprises:

a Dialed Digits field;

a Mobile Directory Number (MDN) field;

a BillingDigits field; and

a GenericDigits field.

24. A method to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP, comprising:

receiving, from a mobile switching center (MSC), an ANSI-41 ORREQ containing at least one of a call back number (CBN) and emergency service routing digits (ESRD);

converting said at least one of a CBN and an ESRD to a VoIP request;

sending, to a VoIP positioning center (VPC), said VoIP request; and

receiving, from a VoIP positioning center (VPC), said VoIP request including at least one of an emergency service query key (ESQK) and an emergency service routing number (ESRN) inserted therein in at least one of a designated field;

whereby said ORREQ permits setup of an emergency services call over at least one of ISDN User Part (ISUP) and Multi-Frequency (MF) signaling.

25. The method to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP according to claim 24, wherein said at least one of a designated field comprises:

a Dialed Digits field;

a Mobile Directory Number (MDN) field;

a BillingDigits field; and

a GenericDigits field.