IP Library › Granted Patent US 10,638,524
Granted Patent B2
US 10,638,524 · App. 16/050,654 · Granted Apr 28, 2020

Method and system for providing mission critical service (MCX) in wireless communication network

Inventors: Irshad Ahamed Kapatralla (Kadapa, IN); Kiran Gajula (Karimnagar, IN); Narasimha Rao Thurlapati (Narasaraopet, IN); Thiyagesh Kalyanaraman (Chennai, IN); Sapan Pramodkumar Shah (Bengaluru, IN)
Assignee: SAMSUNG ELECTRONICS CO., LTD.
H04W76/11H04L12/66H04L63/0861H04L65/1016H04L65/1046H04L65/1073H04L65/4038H04W4/90H04W60/04H04W76/16H04L67/34H04W4/029
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,638,524
App. No.
16/050,654
Granted
Apr 28, 2020
Kind
B2
Abstract

A method and system for providing mission critical service (MCX) in a wireless communication network are provided. The method includes receiving, by a network-bridge entity, a communication request from an electronic device in a non-MCX zone. The network-bridge entity interfaces communication between the non-MCX zone and an MCX zone in the wireless communication network. Further, the method includes performing, by the network-bridge entity, a registration of the electronic device with an MCX server present in the MCX zone. Further, the method includes establishing, by the network-bridge entity, an MCX with the MCX server. Further, the method includes transferring, by the network-bridge entity, an MCX functionality to the electronic device in the non-MCX zone.

Claims (44)

1. A method for providing a mission critical service (MCX) in a wireless communication network, the method comprising:

receiving, by a network-bridge entity that interfaces communication between a non-MCX zone and an MCX zone in the wireless communication network, a communication request from an electronic device that is in the non-MCX zone;

registering, by the network-bridge entity, the electronic device with an MCX server that is in the MCX zone;

establishing, by the network-bridge entity, an MCX with the MCX server; and

transferring, by the network-bridge entity, an MCX functionality to the electronic device in the non-MCX zone, wherein the MCX functionality includes a virtual MCX user interface (UI) for displaying one or more selectable options on the electronic device.

2. The method of claim 1 , wherein the one or more selectable options comprise at least two of an MCX request for accessing a floor, an MCX request for releasing a floor, an MCX request for accessing a private group, an MCX request to join a video group, an MCX request to view available groups.

3. The method of claim 1 , wherein the transferring the MCX functionality to the electronic device in the non-MCX zone comprises:

connecting, by the network-bridge entity, the electronic device in the non-MCX zone with the established MCX;

receiving, by the network-bridge entity, a request from the electronic device to access a floor or transmission control for media transmission with the MCX server; and

notifying, by the network-bridge entity, the electronic device of at least one access response from the MCX.

4. The method of claim 1 , wherein the communication request is at least one of a voice over long-term evolution (VoLTE) communication request, a video over LTE (ViLTE) communication request, a voice over new radio (VoNR) communication request, and a voice over Wi-Fi (VoWiFi) communication request.

5. The method of claim 1 , wherein the network-bridge entity is one of a gateway, a server, and a relay.

6. The method of claim 5 , wherein the relay is a hybrid electronic device that is capable of the MCX and a packet switched (PS) service, and registered in an MCX network.

7. The method of claim 1 , further comprising:

receiving, by the network-bridge entity, an MCX user interface (UI) from the MCX server representing one of a flow of the MCX and the MCX functionality;

generating, by the network-bridge entity, a virtual MCX UI simulating the MCX UI received from the MCX server; and

transferring, by the network-bridge entity, the virtual MCX UI to the electronic device.

8. The method of claim 7 , wherein the virtual MCX UI is transferred by the network-bridge entity to the electronic device using one of a voice over long-term evolution (VoLTE) communication request, a video over LTE (ViLTE) communication request, a voice over new radio (VoNR) communication request, and a voice over Wi-Fi (VoWiFi) communication request.

9. The method of claim 1 , further comprising authenticating, the network-bridge entity, the electronic device based on at least one of biometric data and an access token of a user of the electronic device before the establishing the MCX with the MCX server.

10. The method of claim 9 , wherein the access token stored in the electronic device is fetched from the MCX server, while the electronic device is in the MCX zone.

11. A network-bridge entity for providing a mission critical service (MCX) in a wireless communication network, the network-bridge entity comprising:

a memory;

a processor configured to execute instructions stored in the memory; and

an MCX controller configured to interface communication between a non-MCX zone and an MCX zone in the wireless communication network,

wherein the MCX controller is further configured to:

receive a communication request from an electronic device that is in the non-MCX zone,

register the electronic device with an MCX server that is in the MCX zone,

establish an MCX with the MCX server, and

transfer an MCX functionality to the electronic device in the non-MCX zone, the MCX functionality including a virtual MCX user interface (UI) for displaying one or more selectable options on the electronic device.

12. The network-bridge entity of claim 11 , wherein the one or more selectable options comprises at least two of an MCX request for accessing a floor, an MCX request for releasing a floor, an MCX request for accessing a private group, an MCX request to join a video group, an MCX request to view available groups.

13. The network-bridge entity of claim 11 , wherein the MCX controller is further configured to transfer the MCX functionality to the electronic device in the non-MCX zone by:

connecting the electronic device in the non-MCX zone with the established MCX;

receiving a request from the electronic device to access a floor or transmission control for media transmission with the MCX server; and

notifying the electronic device of at least one access response from the MCX.

14. The network-bridge entity of claim 11 , wherein the communication request is at least one of a voice over long-term evolution (VoLTE) communication request, a video over LTE (ViLTE) communication request, a voice over new radio (VoNR) communication request, and a voice over Wi-Fi (VoWiFi) communication request.

15. The network-bridge entity of claim 11 , wherein the network-bridge entity is one of a gateway, a server, and a relay.

16. The network-bridge entity of claim 15 , wherein the relay is a hybrid electronic device that is capable of the MCX and a packet switched (PS) service, and registered in an MCX network.

17. The network-bridge entity of claim 11 , wherein the MCX controller is further configured to:

receive an MCX user interface (UI) from the MCX server representing one of a flow of the MCX and the MCX functionality;

generate a virtual MCX UI simulating the MCX UI received from the MCX server; and

transfer the virtual MCX UI to the electronic device.

18. The network-bridge entity of claim 17 , wherein the virtual MCX UI is transferred by the network-bridge entity to the electronic device using one of a voice over long-term evolution (VoLTE) communication request, a video over LTE (ViLTE) communication request, a voice over new radio (VoNR) communication request, and a voice over Wi-Fi (VoWiFi) communication request.

19. The network-bridge entity of claim 11 , wherein the MCX controller is further configured to authenticate the electronic device based on at least one of biometric data and an access token of a user of the electronic device before establishing the MCX with the MCX server.

20. The network-bridge entity of claim 19 , wherein the access token stored in the electronic device is fetched from the MCX server, while the electronic device is in the MCX zone.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 31, 2018
From: KAPATRALLA, IRSHAD AHAMED; GAJULA, KIRAN; THURLAPATI, NARASIMHA RAO; KALYANARAMAN, THIYAGESH; SHAH, SAPAN PRAMODKUMAR
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 046514/0954 →
Priority Claims (2)
IN 201741027185 · Jul 31, 2017 · national
IN 201741027185 · Jul 27, 2018 · national
Continuity (1)
Related Publication 20190037617A1 · Jan 31, 2019
Cited By (1)
US 12,745,079