IP Library › Granted Patent US 11,324,070
Granted Patent B2
US 11,324,070 · App. 16/345,936 · Granted May 3, 2022

Method of and apparatus for releasing mission critical data communication

Inventors: Sapan Pramodkumar Shah (Bangalore, IN); Basavaraj Jayawant Pattan (Bangalore, IN); Siva Prasad Gundur (Bangalore, IN); Suresh Chitturi (Bangalore, IN)
Assignee: Samsung Electronics Co., Ltd.
H04W76/30H04W76/50
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,324,070
App. No.
16/345,936
Granted
May 3, 2022
Kind
B2
Abstract

Disclosures herein provide methods and servers for releasing mission critical data (MCData) communication in a wireless communication system. The release of MCData communication is initiated by MCData UE by using the hyper text transfer protocol (HTTP) or the release of MCData communication is initiated by a MCData server with or without prior notification to the MCData UE.

Claims (49)

1. A method for releasing mission critical data (MCData) communication among a first MCData user equipment (UE), a second MC data UE and an MCData server, the method comprising:

determining, by the MCData server, whether to release an MCData communication, based on a release condition;

transmitting, by the MCData server, an MCData release intent request including a request for more information to the first MCData UE;

receiving, by the MCData server, an MCData more information response from the first MCData UE, in response to the MCData release intent request message including the request for more information;

determining, by the MCData server, whether an MCData request for extension is received within a predetermined time from the first MCData UE, upon receiving the MCData more information response;

determining, by the MCData server, whether to accept the MCData request for extension based on one or more policies, in response to receiving the MCData request for extension;

transmitting, by the MCData server, an MCData response message based on the determination on whether to accept the MCData request for extension to the first MCData UE; and

releasing the MCData communication when the MCData server did not accept the MCData request for extension.

2. The method of claim 1 , wherein the releasing of the MCData communication further comprises:

transmitting an MCData server communication release request to the first MCData UE and the second MCData UE; and

receiving an MCData server communication release response from the first MCData UE and the second MCData UE.

3. The method of claim 1 , wherein the releasing of the MCData communication further comprises:

removing file data stored by the MC Data server.

4. The method of claim 3 , further comprising:

transmitting an MCData server communication release indication to the first MCdata UE.

5. The method of claim 1 , wherein the MCData request for extension includes an identifier indicating a communication for which the extension is requested.

6. A method for releasing mission critical data (MCData) communication among a first MCData user equipment (UE), a second MCData UE and an MCData server, the method comprising:

receiving an MCData release intent request from the MCData Server;

determining whether the MCData release intent request includes a request for more information;

transmitting a MCData more information response to the MCData server, when the request for more information is included in the MCData release intent request;

transmitting an MCData request for extension to the MCData server based on the determination; and

receiving an MCData response for extension from the MCData server or receiving an MCData server communication release indication from the MCData server.

7. The method of claim 6 , further comprising:

receiving an MCData server communication release request from the MCData server; and

transmitting an MCData server communication release response to the MCData server.

8. A mission critical data (MCData) server for releasing MCData communication among a first MCData user equipment (UE), a second MCData UE, and an MCData server, the MCData server comprising:

a transceiver; and

a processor coupled with the transceiver and configured to:

determine whether to release an MCData communication, based on a release condition,

transmit an MCData release intent request including a request for more information to the first MCData UE,

receive an MCData more information response from the first MCData UE, in response to the MCData release intent request message including the request for more information,

determine whether an MCData request for extension is received within a predetermined time from the first MCData UE, upon receiving the MCData more information response,

determine whether to accept the MCData request for extension based on one or more policies, in response to receiving the MCData request for extension,

transmit an MCData response message based on the determination on whether to accept the MCData request for extension to the first MCData UE, and

release the MCData communication when the MCData server did not accept the MCData request for extension.

9. The MCData server of claim 8 , wherein the processor is further configured to:

transmit an MCData server communication release request to the first MCData UE and the second MCData UE, and

receive an MCData server communication release response from the first MCData UE and the second MCData UE.

10. The MCData server of claim 8 , wherein the processor is further configured to:

remove file data stored by the MC Data server, and

transmit an MCData server communication release indication to the first MCData UE.

11. A first mission critical (MCData) user equipment (UE) for releasing MCData communication among a first MCData UE, a second MCData UE, and an MCData server, the first MCData UE comprising:

a transceiver; and

a processor coupled with the transceiver and configured to:

receive an MCData release intent request from the MCData Server,

determine whether the MCData release intent request includes a request for more information,

transmit a MCData more information response to the MCData server, when the request for more information is included in the the MCData release intent request,

transmit an MCData request for extension to the MCData server based on the determination,

receive an MCData response for extension from the MCData server or receive an MCData server communication release indication from the MCData server.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2019
From: SHAH, SAPAN PRAMODKUMAR; PATTAN, BASAVARAJ JAYAWANT; GUNDUR, SIVA PRASAD; CHITTURI, SURESH
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 049022/0638 →
Priority Claims (2)
IN 201641037800 · Nov 4, 2016 · national
IN 201641037800 · Oct 27, 2017 · national
Continuity (1)
Related Publication 20200068649A1 · Feb 27, 2020
Cited By (2)
US 12,245,108 US 12,328,647