IP Library Granted Patent US 10,178,236
Granted Patent B2
US 10,178,236 · App. 15/477,725 · Granted Jan 8, 2019

Emergency call handling

Inventors: Frank Kowalewski (Goettingen, DE); Muthaiah Venkatachalam (Beaverton, OR); Thomas Luetzenkirchen (Taufkirchen, DE); Usharani Ayyalasomayajula (Bangalore, IN)
Assignee: Intel IP Corporation
H04M11/04G08B25/016H04B7/00H04L1/1678H04L5/14H04L47/2466H04L47/2475H04L47/28H04L65/1006H04L65/1016H04L65/1069H04W4/022H04W4/027H04W4/90H04W8/08H04W28/0226H04W28/0247H04W28/0268H04W28/08H04W36/00H04W36/0061H04W64/006H04W72/0413H04W72/0446H04W72/085H04W76/00H04W76/50H04W88/06H04W92/02H04L1/1607H04M2242/04H04W84/042H04W84/12H04W88/08Y02D70/12Y02D70/126
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,178,236
App. No.
15/477,725
Granted
Jan 8, 2019
Kind
B2
Abstract

Technology for initiating emergency calls is disclosed. A minimum set of emergency related data (MSD) associated with the emergency call may be identified at a terminal equipment (TE) of a mobile terminal. An attention (AT) command may be generated that includes the MSD and selected configuration information related to the emergency call. The AT command may be sent from the TE of the mobile terminal to a mobile termination (MT) of the mobile terminal in order to setup the emergency call, wherein the mobile terminal (MT) routes the emergency call to a public safety answering point (PSAP) in a communication network.

Claims (44)

1. An apparatus of a user equipment (UE) operable to perform an emergency call (eCall), the apparatus comprising:

one or more processors configured to:

generate, at a terminal equipment (TE) of the UE, a command to trigger an eCall from the UE to a network, wherein the command includes a minimum set of emergency related data (MSD) associated with the eCall;

provide, from the TE of the UE, the command that includes the MSD to a mobile termination (MT) of the UE via a terminal adaptor (TA) of the UE; and

initiate, at the MT of the UE, the eCall to the network in response to receiving the command from the TE of the UE, wherein the MSD is provided to the network during initiation of the eCall to the network; and

memory operable to store the command.

2. The apparatus of claim 1 , further comprising a transceiver configured to transmit the MSD received from the MT of the UE to the network.

3. The apparatus of claim 1 , wherein the one or more processors are configured to generate, at the TE of the UE, a command to include additional data in an updated MSD to be provided to the network during an ongoing eCall at the UE.

4. The apparatus of claim 1 , wherein the one or more processors are configured to generate, at the TE of the UE, the command to include:

a type of eCall parameter of an integer type, wherein the type of eCall parameter indicates a type of eCall;

a format parameter of an integer type, wherein the format parameter indicates a format of the MSD; and

an MSD data length parameter of an integer type, wherein the MSD data length parameter indicates a size of the MSD.

5. The apparatus of claim 4 , wherein the type of eCall is one of: a test call represented by an integer value of “0”, a reconfiguration call eCall represented by an integer value of “1”, a manually initiated eCall represented by an integer value of “2” or an automatically initiated eCall represented by an integer value of “3”.

6. The apparatus of claim 4 , wherein the format of the MSD includes a binary format represented by an integer value of “1”.

7. The apparatus of claim 1 , wherein the MSD is of a string type.

8. The apparatus of claim 1 , wherein the command is a +CECALL command, wherein a syntax of the +CECALL command is represented as +CECALL=<type_of_eCall>[,<format>,<msd_data_length>,<msd_data>], wherein <type_of_eCall> indicate a type of eCall, <format> indicates a format associated with the MSD, <msd_data_length> is a size of the MSD, and <msd_data> is the MSD.

9. At least one non-transitory machine readable storage medium having instructions embodied thereon for performing an emergency call (eCall) from a user equipment (UE), the instructions when executed by one or more processors of the UE perform the following:

generating, at a terminal equipment (TE) of the UE, a command to trigger an eCall from the UE to a network, wherein the command includes a minimum set of emergency related data (MSD) associated with the eCall;

providing, from the TE of the UE, the command that includes the MSD to a mobile termination (MT) of the UE via a terminal adaptor (TA) of the UE; and

initiating, at the MT of the UE, the eCall to the network in response to receiving the command from the TE of the EE, wherein the MSD is provided to the network during initiation of the eCall to the network.

10. The at least one machine readable storage medium of claim 9 , further comprising instructions when executed perform the following: generating, at the TE of the UE, a command to include additional data in an updated MSD to be provided to the network during an ongoing eCall at the UE.

11. The at least one machine readable storage medium of claim 9 , further comprising instructions when executed perform the following: generating, at the TE of the UE, the command to include:

a type of eCall parameter of an integer type, wherein the type of eCall parameter indicates a type of eCall;

a format parameter of an integer type, wherein the format parameter indicates a format of the MSD; and

an MSD data length parameter of an integer type, wherein the MSD data length parameter indicates a size of the MSD.

12. The at least one machine readable storage medium of claim 11 , wherein the type of eCall is one of: a test call represented by an integer value of “0”, a reconfiguration call eCall represented by an integer value of “1”, a manually initiated eCall represented by an integer value of “2” or an automatically initiated eCall represented by an integer value of “3”.

13. The at least one machine readable storage medium of claim 11 , wherein the format of the MSD includes a binary format represented by an integer value of “1”.

14. The at least one machine readable storage medium of claim 9 , wherein the MSD is of a string type.

15. The at least one machine readable storage medium of claim 9 , wherein the command is a +CECALL command, wherein a syntax of the +CECALL command is represented as +CECALL=<type_of_eCall>[,<format>,<msd_data_length>,<msd_data>], wherein <type_of_eCall> indicate a type of eCall, <format> indicates a format associated with the MSD, <msd_data_length> is a size of the MSD, and <msd_data> is the MSD.

16. An apparatus of a user equipment (UE) operable to initiate an emergency call (eCall) to a network, the apparatus comprising:

a terminal adaptor (TA);

a terminal equipment (TE) operable to generate an attention (AT) command to trigger an eCall from the UE to the network, wherein the AT command includes a minimum set of emergency related data (MSD) associated with the eCall and selected configuration information associated with the eCall; and

a mobile termination (MT) operable to:

receive the AT command that includes the MSD and the selected configuration information from the TE via the TA; and

initiate the eCall to the network in response to receiving the AT command from the TE, wherein the MSD is provided to the network during initiation of the eCall to the network.

17. The apparatus of claim 16 , wherein the TE is further operable to generate an AT command to include additional data in an updated MSD to be provided to the network during an ongoing eCall at the UE.

18. The apparatus of claim 16 , wherein the selected configuration information includes:

a type of eCall parameter of an integer type, wherein the type of eCall parameter indicates a type of eCall;

a format parameter of an integer type, wherein the format parameter indicates a format of the MSD; and

an MSD data length parameter of an integer type, wherein the MSD data length parameter indicates a size of the MSD.

19. The apparatus of claim 18 , wherein the type of eCall is one of: a test call represented by an integer value of “0”, a reconfiguration call eCall represented by an integer value of “1”, a manually initiated eCall represented by an integer value of “2” or an automatically initiated eCall represented by an integer value of “3”.

20. The apparatus of claim 18 , wherein the format of the MSD includes a binary format represented by an integer value of “1”.

21. The apparatus of claim 16 , wherein the MSD is of a string type.

22. The apparatus of claim 16 , wherein the AT command is a +CECALL command, wherein a syntax of the +CECALL command is represented as +CECALL=<type_of_eCall>[,<format>,<msd_data_length>,<msd_data>], wherein <type_of_eCall> indicate a type of eCall, <format> indicates a format associated with the MSD, <msd_data_length> is a size of the MSD, and <msd_data> is the MSD.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 26, 2020
From: INTEL CORPORATION
To: APPLE INC.
Reel/Frame 053063/0205 →
CONFIRMATORY ASSIGNMENT Recorded Jun 25, 2020
From: INTEL IP CORPORATION
To: INTEL CORPORATION
Reel/Frame 053051/0016 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2017
From: KOWALEWSKI, FRANK; VENKATACHALAM, MUTHAIAH; LUETZENKIRCHEN, THOMAS; AYYALASOMAYAJULA, USHARANI
To: INTEL IP CORPORATION
Reel/Frame 042441/0314 →
Continuity (3)
Continuation 14495469 · Sep 24, 2014
Provisional Application 61893792 · Oct 21, 2013
Related Publication 20170208180A1 · Jul 20, 2017
Cited By (1)
US 12,445,920