Search

US-12628244-B2 - Methods and systems for managing emergency indications and emergency state of MCPTT clients/group

US12628244B2US 12628244 B2US12628244 B2US 12628244B2US-12628244-B2

Abstract

The present disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The disclosure provides methods and systems for managing emergency indications and emergency state of MCPTT clients.

Inventors

  • Kiran Gurudev KAPALE
  • Arunprasath Ramamoorthy
  • Sapan Pramodkumar SHAH
  • Basavaraj Jayawant Pattan

Assignees

  • SAMSUNG ELECTRONICS CO., LTD.

Dates

Publication Date
20260512
Application Date
20210812
Priority Date
20210609

Claims (20)

  1. 1 . A method performed by a mission critical push to talk (MCPTT) server in a wireless communication system, the method comprising: receiving, from a first MCPTT terminal of a first MCPTT user in an MCPTT group, an emergency indication; based on the emergency indication, setting an in-progress emergency state of the MCPTT group; receiving, from a second MCPTT terminal of a second MCPTT user in the MCPTT group, a request to cancel the in-progress emergency state, while no call associated with the in-progress emergency state is ongoing; identifying whether the request to cancel is an authorized request to cancel the in-progress emergency state; and in case that the request to cancel is the authorized request to cancel the in-progress emergency state, clearing the in-progress emergency state of the MCPTT group.
  2. 2 . A mission critical push to talk (MCPTT) server in a wireless communication system, the MCPTT server comprising: a transceiver configured to transmit and receive a signal; and a controller coupled with the transceiver and configured to: receive, from a first MCPTT terminal of a first MCPTT user in an MCPTT group, an emergency indication, based on the emergency indication, set an in-progress emergency state of the MCPTT group, receive, from a second MCPTT terminal of a second MCPTT user in the MCPTT group, a request to cancel the in-progress emergency state, while no call associated with the in-progress emergency state is ongoing, identify whether the request to cancel is an authorized request to cancel the in-progress emergency state, and in case that the request to cancel is the authorized request to cancel the in-progress emergency state, clear the in-progress emergency state of the MCPTT group.
  3. 3 . A method performed by a first mission critical push to talk (MCPTT) terminal in a wireless communication system, the method comprising: generating an emergency indication for setting an in-progress emergency state of an MCPTT group, the first MCPTT terminal of a first MCPTT user being included in the MCPTT group; and transmitting, to an MCPTT server, the emergency indication, wherein a request to cancel the in-progress emergency state is transmitted from a second MCPTT terminal of a second MCPTT user in the MCPTT group to the MCPTT server, while no call associated with the in-progress emergency state of the MCPTT group is ongoing, and wherein in case that the request to cancel is an authorized request to cancel the in-progress emergency state, the in-progress emergency state of the MCPTT group is cleared.
  4. 4 . A first mission critical push to talk (MCPTT) terminal in a wireless communication system, the first MCPTT terminal comprising: a transceiver configured to transmit and receive a signal; and a controller coupled with the transceiver and configured to: generate an emergency indication for setting an in-progress emergency state of an MCPTT group, the first MCPTT terminal of a first MCPTT user being included in the MCPTT group, and transmit, to an MCPTT server, the emergency indication, wherein a request to cancel the in-progress emergency state is transmitted from a second MCPTT terminal of a second MCPTT user in the MCPTT group to the MCPTT server, while no call associated with the in-progress emergency state of the MCPTT group is ongoing, and wherein, in case that the request to cancel is an authorized request to cancel the in-progress emergency state, the in-progress emergency state of the MCPTT group is cleared.
  5. 5 . The method of claim 1 , further comprising: caching an identifier (ID) of the first MCPTT user; receiving, from a third MCPTT terminal of a third MCPTT user, a new emergency indication; and transmitting, to an MCPTT terminal of at least one MCPTT user in the MCPTT group, a session initiation protocol (SIP) message to notify the new emergency indication of the third MCPTT user, wherein the SIP message includes an ID of the third MCPTT user.
  6. 6 . The method of claim 1 , further comprising: in case that the request to cancel is the authorized request to cancel the in-progress emergency state of the MCPTT group, transmitting, to an MCPTT terminal of at least one MCPTT user in the MCPTT group, a session initiation protocol (SIP) message to notify a cancellation of the in-progress emergency state of the MCPTT group.
  7. 7 . The method of claim 1 , further comprising: in case that the request to cancel is an unauthorized request to cancel the in-progress emergency state of the MCPTT group, identifying whether the request to cancel is an authorized request for an MCPTT emergency alert cancellation; in case that the request to cancel is an unauthorized request for the MCPTT emergency alert cancellation, rejecting the request to cancel; and in case that the request to cancel is the authorized request for the MCPTT emergency alert cancellation, clearing a cached identifier of an MCPTT user that has outstanding emergency alert state.
  8. 8 . The method of claim 7 , further comprising: in case that the request to cancel is the authorized request for the MCPTT emergency alert cancellation, transmitting, to an MCPTT terminal of at least one MCPTT user in the MCPTT group, a session initiation protocol (SIP) message to notify a cancellation of the emergency alert of the MCPTT user.
  9. 9 . The MCPTT server of claim 2 , wherein the controller is further configured to: cache an identifier (ID) of the first MCPTT user, receive, from a third MCPTT terminal of a third MCPTT user, a new emergency indication, and transmit, to an MCPTT terminal of at least one MCPTT user in the MCPTT group, a session initiation protocol (SIP) message to notify the new emergency indication of the third MCPTT user, and wherein the SIP message includes an ID of the third MCPTT user.
  10. 10 . The MCPTT server of claim 2 , wherein, in case that the request to cancel is the authorized request to cancel the in-progress emergency state of the MCPTT group, the controller is further configured to transmit, to an MCPTT terminal of at least one MCPTT user in the MCPTT group, a session initiation protocol (SIP) message to notify a cancellation of the in-progress emergency state of the MCPTT group.
  11. 11 . The MCPTT server of claim 2 , wherein the controller is further configured to: in case that the request to cancel is an unauthorized request to cancel the in-progress emergency state of the MCPTT group, identify whether the request to cancel is an authorized request for an MCPTT emergency alert cancellation, in case that the request to cancel is an unauthorized request for the MCPTT emergency alert cancellation, reject the request to cancel, and in case that the request to cancel is the authorized request for the MCPTT emergency alert cancellation, clear a cached identifier of an MCPTT user that has outstanding emergency alert state.
  12. 12 . The MCPTT server of claim 11 , wherein, in case that the request to cancel is the authorized request for the MCPTT emergency alert cancellation, the controller is further configured to transmit, to an MCPTT terminal of at least one MCPTT user in the MCPTT group, a session initiation protocol (SIP) message to notify a cancellation of the emergency alert of the MCPTT user.
  13. 13 . The method of claim 3 , further comprising: receiving, from the MCPTT server, a session initiation protocol (SIP) message to notify a new emergency indication of a third MCPTT user, wherein the SIP message is transmitted based on a transmission of the new emergency indication from a third MCPTT terminal of the third MCPTT user in the MCPTT group to the MCPTT server, wherein an identifier (ID) of the first MCPTT user is cached, and wherein the SIP message includes an ID of the third MCPTT user.
  14. 14 . The method of claim 3 , further comprising: in case that the request to cancel is the authorized request to cancel the in-progress emergency state of the MCPTT group, receiving, from the MCPTT server, a session initiation protocol (SIP) message to notify a cancellation of the in-progress emergency state of the MCPTT group.
  15. 15 . The method of claim 3 , wherein, in case that the request to cancel is an unauthorized request to cancel the in-progress emergency state of the MCPTT group, and the request to cancel is an unauthorized request for an MCPTT emergency alert cancellation, the request to cancel is rejected, and wherein, in case that the request to cancel is the unauthorized request to cancel the in-progress emergency state of the MCPTT group, and the request to cancel is an authorized request for the MCPTT emergency alert cancellation, a cached identifier of an MCPTT user that has outstanding emergency alert state is cleared.
  16. 16 . The method of claim 15 , further comprising: in case that the request to cancel is the authorized request for the MCPTT emergency alert cancellation, receiving, from the MCPTT server, a session initiation protocol (SIP) message to notify a cancellation of the emergency alert of the MCPTT user.
  17. 17 . The first MCPTT terminal of claim 4 , wherein the controller is further configured to receive, from the MCPTT server, a session initiation protocol (SIP) message to notify a new emergency indication of a third MCPTT user, wherein the SIP message is transmitted based on a transmission of the new emergency indication from a third MCPTT terminal of the third MCPTT user in the MCPTT group to the MCPTT server, wherein an identifier (ID) of the first MCPTT user is cached, and wherein the SIP message includes an ID of the third MCPTT user.
  18. 18 . The first MCPTT terminal of claim 4 , wherein, in case that the request to cancel is the authorized request to cancel the in-progress emergency state of the MCPTT group, the controller is further configured to receive, from the MCPTT server, a session initiation protocol (SIP) message to notify a cancellation of the in-progress emergency state of the MCPTT group.
  19. 19 . The first MCPTT terminal of claim 4 , wherein, in case that the request to cancel is an unauthorized request to cancel the in-progress emergency state of the MCPTT group, and the request to cancel is an unauthorized request for an MCPTT emergency alert cancellation, the request to cancel is rejected, and wherein, in case that the request to cancel is the unauthorized request to cancel the in-progress emergency state of the MCPTT group, and the request to cancel is an authorized request for the MCPTT emergency alert cancellation, a cached identifier of an MCPTT user that has outstanding emergency alert state is cleared.
  20. 20 . The first MCPTT terminal of claim 19 , wherein, in case that the request to cancel is the authorized request for the MCPTT emergency alert cancellation, the controller is further configured to receive, from the MCPTT server, a session initiation protocol (SIP) message to notify a cancellation of the emergency alert of the MCPTT user.

Description

TECHNICAL FIELD Embodiments herein relate to Mission Critical Push to Talk (MCPTT) services, and more particularly to methods and systems for managing emergency indications received from MCPTT clients of an MCPTT group and managing in-progress emergency state of the MCPTT group. BACKGROUND ART To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post LTE System’. The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G communication systems. In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud Radio Access Networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), reception-end interference cancellation and the like. In the 5G system, Hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed. The Internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the Internet of Things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of the IoT technology and the Big Data processing technology through connection with a cloud server, has emerged. As technology elements, such as “sensing technology”, “wired/wireless communication and network infrastructure”, “service interface technology”, and “Security technology” have been demanded for IoT implementation, a sensor network, a Machine-to-Machine (M2M) communication, Machine Type Communication (MTC), and so forth have been recently researched. Such an IoT environment may provide intelligent Internet technology services that create a new value to human life by collecting and analyzing data generated among connected things. IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications. In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as a sensor network, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas. Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology. Continuous growth and development in wireless telecommunication systems has allowed users to avail emergency services. 3rd Generation Partnership Project (3GPP) has introduced Mission Critical Push to Talk (MCPTT) services, to allow users, such as personnel involved in mission critical communications or first responders, to effectively avail emergency services. The mission critical services are generally availed in performing operations that are associated with preventing loss of human life and/or property. The mission critical services can be relevant, especially for agencies providing public safety and health services such as, police services, fire services, and ambulance services. Therefore, in order to cater to emergency situations, as experienced by the agencies providing the public safety and health services, the mission critical services needs to be rendered with a high degree of reachability, availability, reliability, Quality of Service (QoS), and so on. DISCLOSURE OF INVENTION Technical Problem The principal object of the embodiments herein is to disclose methods and systems for handling emergency indications from at least one Mission Critical Push to Talk (MCPTT) client of an MCPTT group, wherein MCPTT clients of the MCPTT group may be engaged in an MCPTT emergency group call. Another object of the embodiments herein is to detect an emergency indication from an MCPTT client of the MCPTT group, and alert all MCPTT clients of the MCPTT group, engaged in