IP Library › Granted Patent US 11,751,036
Granted Patent B2
US 11,751,036 · App. 17/109,047 · Granted Sep 5, 2023

Emergency rich communication services

Inventor: Ramaswamy Chockalingam (Bellevue, WA)
Assignee: T-Mobile USA, Inc.
H04W4/90H04W4/12
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 11,751,036
App. No.
17/109,047
Granted
Sep 5, 2023
Kind
B2
Abstract

A fifth generation (5G) network can provide Rich Communication Services (RCS) between a user equipment (UE) and an emergency control center. An RCS server in an IP Multimedia Subsystem (IMS) can be used to transfer data associated with a chat, an image, and/or a video between the UE and a public service answering point (PSAP) associated with the emergency control center. The RCS server can initiate, establish, maintain, format, augment, or otherwise determine a rich communication service between the UE and the PSAP over the 5G network.

Claims (51)

1. A method comprising:

receiving, by a server of an Internet Protocol (IP) Multimedia Subsystem (IMS) of a network, a message from a user equipment (UE) indicating a Rich Communication Services (RCS) request to a public service answering point (PSAP), wherein the IMS is separate and distinct from the PSAP;

identifying, by the server, a protocol associated with the PSAP for sending the message;

formatting, by the server and based at least in part on the protocol, the message for sending to the PSAP as a formatted message; and

sending, by the server, the formatted message indicating the RCS request from the UE to the PSAP.

2. The method of claim 1 , wherein the network comprises a fifth generation telecommunications network and the RCS request comprises at least one of: an image, a video, or a file transfer.

3. The method of claim 1 , wherein formatting the message for sending comprises augmenting the message to be recognized in accordance with the protocol associated with the PSAP.

4. The method of claim 1 , further comprising:

determining, by the server, that the message is associated with an emergency event, and

wherein identifying the protocol associated with the RCS request for sending the message is based at least in part on determining that the message is associated with the emergency event.

5. The method of claim 1 , further comprising:

receiving, by the server, data associated with the message from at least one of: a proxy call session control function server, an emergency call session control function server, or a gateway mobile location center, and

wherein formatting the message for sending to the PSAP is further based at least in part on the data.

6. The method of claim 5 , wherein the data represents location information associated with the message or protocol information associated with the PSAP.

7. The method of claim 1 , further comprising:

determining, by the server, a conversion value to convert a protocol associated with the message received from the UE to the protocol associated with the PSAP, and

wherein identifying the protocol associated with the PSAP for sending the message is based at least in part on the conversion value.

8. The method of claim 1 , wherein the network comprises a different protocol for communication of the message than the protocol associated with the PSAP.

9. The method of claim 1 , wherein formatting the message for sending to the PSAP comprises assigning a priority to the message to indicate a level of emergency associated with the message.

10. A system comprising:

one or more processors; and

memory storing computer-executable instructions that, when executed by the one or more processors, cause the system to perform operations comprising:

receiving, by a server of an Internet Protocol (IP) Multimedia Subsystem (IMS) of a network, a message from a user equipment (UE) indicating a Rich Communication Services (RCS) request to a public service answering point (PSAP), wherein the IMS is separate and distinct from the PSAP;

identifying, by the server, a protocol associated with the PSAP for sending the message;

formatting, by the server and based at least in part on the protocol, the message for sending to the PSAP as a formatted message; and

sending, by the server, the formatted message indicating the RCS request from the UE to the PSAP.

11. The system of claim 10 , wherein formatting the message for sending comprises augmenting the message to be recognized in accordance with the protocol associated with the PSAP.

12. The system of claim 10 , the operations further comprising:

determining, by the server, that the message is associated with an emergency event, and

wherein identifying the protocol associated with the RCS request for sending the message is based at least in part on determining that the message is associated with the emergency event.

13. The system of claim 10 , the operations further comprising:

receiving, by the server, data associated with the message from at least one of: a proxy call session control function server, an emergency call session control function server, or a gateway mobile location center,

wherein formatting the message for sending to the PSAP is further based at least in part on the received data.

14. The system of claim 10 , the operations further comprising

determining, by the server, a conversion value to convert a protocol associated with the message received from the UE to the protocol associated with the PSAP, and

wherein identifying the protocol associated with the PSAP for sending the message is based at least in part on the conversion value.

15. A method comprising:

determining, by a server of an Internet Protocol (IP) Multimedia Subsystem (IMS) of a network, a protocol for sending a message comprising a Rich Communication Services (RCS) request from a user equipment (UE) to a public service answering point (PSAP), wherein the IMS is separate and distinct from the PSAP;

receiving, by the server, location data associated with the message from at least one of: an emergency call session control function server or a gateway mobile location center;

formatting, by the server and based at least in part on the protocol and the location data, the message for receipt by the PSAP; and

receiving a response from the PSAP indicating a channel for communicating the RCS request of the message from the UE.

16. The method of claim 15 , wherein:

the RCS request comprises at least one of: an image, a video, or a file transfer, and

determining the protocol for sending the message comprises determining that the protocol is compatible for communicating the RCS request with the PSAP.

17. The method of claim 16 , wherein the network comprises a fifth generation telecommunications network.

18. The method of claim 15 , further comprising establishing, by the IMS and based at least in part on the response from the PSAP, a communication session between the UE and the PSAP using the channel received from the PSAP.

19. The method of claim 15 , further comprising:

determining, by the server, a difference between a protocol associated with communicating the message from the UE over the network and the protocol for sending the message to the PSAP;

determining, by the server and based at least in part on the difference, a protocol conversion value; and

wherein determining the protocol for sending the message to the PSAP comprises converting, based at least in part on the protocol conversion value, the protocol associated with communicating the message from the UE over the network to the protocol for sending the message to the PSAP.

20. The method of claim 15 , further comprising associating, by the server, user information, location information, timing information, or motion information associated with the UE.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 31, 2020
From: CHOCKALINGAM, RAMASWAMY
To: T-MOBILE USA, INC.
Reel/Frame 054785/0893 →
Continuity (1)
Related Publication 20220174462A1 · Jun 2, 2022
Cited By (1)
US 12,470,612