Device, method, and non-transitory computer-readable storage medium for call setup

Abstract

A mission critical push to talk (MCPTT) server may comprise at least one processor. The at least one processor is configured to establish a call connection between an MCPTT calling device and an MCPTT device by: receiving, from the MCPTT calling device, a call request message including information about a zone; monitoring whether location information about at least one MCPTT device is received in the zone indicated by the call request message of the MCPTT calling device; in response to receiving the location information about the MCPTT device in the zone, transmitting a call request message of the MCPTT server to the MCPTT device; in response to the call request message of the MCPTT server, receiving a call response message from the MCPTT device; and in response to the call request message of the MCPTT calling device, transmitting a call response message of the MCPTT server to the MCPTT calling device.

Description

Device, method, and non-transitory computer-readable storage medium for setting up a call

[0001] The following descriptions relate to devices, methods, and non-transitory computer-readable storage media for setting up a call.

[0002] MCPTT (Mission Critical Push to Talk) is a group communication service that features fast setup time, the ability to handle large groups, strong security, and priority handling. An MCPTT server can establish a call connection between an MCPTT calling device and an MCPTT client device.

[0003] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.

[0004] A mission critical push to talk (MCPTT) server is provided. The MCPTT server may include communication circuitry. The MCPTT server may include a memory storing instructions and including one or more storage media. The MCPTT server may include at least one processor including a processing circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to receive a call request message including information about a zone from an MCPTT calling device. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to monitor whether location information of at least one MCPTT device is received in the zone indicated by the call request message of the MCPTT calling device. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to transmit a call request message to the MCPTT device in response to receiving location information of the MCPTT device in the zone. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to receive a call response message from the MCPTT device in response to the call request message of the MCPTT server.The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to establish a call connection between the MCPTT calling device and the MCPTT device by sending a call response message of the MCPTT server to the MCPTT calling device in response to the call request message of the MCPTT calling device.

[0005] A method performed by an MCPTT server is provided. The method may include receiving a call request message from an MCPTT calling device, the call request message including information about a zone. The method may include monitoring whether location information of at least one MCPTT device is received in the zone indicated by the call request message of the MCPTT calling device. The method may include transmitting a call request message of the MCPTT server to the MCPTT device in response to receiving the location information of the MCPTT device in the zone. The method may include receiving a call response message from the MCPTT device in response to the call request message of the MCPTT server. The method may include establishing a call connection between the MCPTT calling device and the MCPTT device by transmitting a call response message of the MCPTT server to the MCPTT calling device in response to the call request message of the MCPTT calling device.

[0006] A non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by an MCPTT server including at least one processor, cause the MCPTT server to receive a call request message including information about a zone from an MCPTT calling device. The one or more programs may include instructions that, when executed by the MCPTT server including at least one processor, cause the MCPTT server to monitor whether location information of at least one MCPTT device is received in the zone indicated by the call request message of the MCPTT calling device. The one or more programs may include instructions that, when executed by the MCPTT server including at least one processor, cause the MCPTT server to transmit a call request message of the MCPTT server to the MCPTT device in response to receiving location information of the MCPTT device in the zone. The one or more programs may include instructions that, when executed by an MCPTT server including at least one processor, cause the MCPTT server to receive a call response message from the MCPTT device in response to the call request message of the MCPTT server. The one or more programs may include instructions that, when executed by an MCPTT server including at least one processor, cause the MCPTT server to establish a call connection between the MCPTT calling device and the MCPTT device by sending a call response message of the MCPTT server to the MCPTT calling device in response to the call request message of the MCPTT calling device.

[0007] An MCPTT device is provided. The MCPTT device may include communication circuitry. The MCPTT device may include a display. The MCPTT device may include a memory storing instructions and including one or more storage media. The MCPTT device may include at least one processor including a processing circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to receive a message from an MCPTT server indicating activation of an event associated with a zone-based call setup. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to display, using the display, a zone associated with the event and a pending status of a call request by an MCPTT calling device, based on the message. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to transmit location information of the MCPTT device to the MCPTT server based on obtaining user input for the area displayed by the display.

[0008] A method is provided that is performed by an MCPTT device. The method may include receiving a message from the MCPTT server indicating the activation of an event associated with a zone-based call setup. The method may include displaying, based on the message, a zone associated with the event and a pending status of a call request by the MCPTT calling device using a display. The method may include transmitting location information of the MCPTT device to the MCPTT server based on obtaining a user input for the zone displayed by the display.

[0009] A non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by an MCPTT device comprising at least one processor, cause the MCPTT device to receive a message from the MCPTT server indicating activation of an event associated with a zone-based call setup. The one or more programs may include instructions that, when executed by an MCPTT server comprising at least one processor, cause the MCPTT device to display, on a display, a zone associated with the event and a pending status of a call request by an MCPTT calling device based on the message. The one or more programs may include instructions that, when executed by an MCPTT server comprising at least one processor, cause the MCPTT device to transmit location information of the MCPTT device to the MCPTT server based on obtaining a user input for the zone displayed by the display.

[0010] In connection with the description of the drawings, the same or similar reference numerals may be used for identical or similar components.

[0011] Figure 1 illustrates signaling for call setup for mission critical push to talk (MCPTT) according to one embodiment.

[0012] Figures 2a and 2b illustrate examples of failed call setup for MCPTT.

[0013] Figure 3 illustrates signaling for call setup for MCPTT according to one embodiment.

[0014] FIG. 4 is a flowchart illustrating the operation of an MCPTT server for call setup for MCPTT according to one embodiment.

[0015] Figure 5 illustrates an example of call setup for MCPTT.

[0016] Figure 6 illustrates an example of signaling for call setup for MCPTT according to one embodiment.

[0017] Figure 7 illustrates a screen of an MCPTT device for call setup for MCPTT according to one embodiment.

[0018] FIG. 8 is a flowchart illustrating the operation of an MCPTT device for call setup for MCPTT according to one embodiment.

[0019] Figure 9 is a simplified block diagram of an MCPTT server.

[0020] FIG. 10 is a block diagram of an electronic device within a network environment according to various embodiments.

[0021] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0022] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0023] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}.

[0024] Although this disclosure describes embodiments using terminology used in certain communication standards (e.g., 3rd Generation Partnership Project (3GPP)), this is merely an example for illustrative purposes. Embodiments of this disclosure can also be applied to other communication and broadcasting systems.

[0025] FIG. 1 illustrates signaling for call setup for MCPTT according to one embodiment. Referring to FIG. 1, a mission critical push to talk (MCPTT) system may include an MCPTT calling device (110), an MCPTT server (120), an MCPTT device (130), and an MCPTT device (140). However, this is merely an example, and the present disclosure is not limited thereto. For example, the MCPTT system may include multiple MCPTT calling devices. For example, the MCPTT system may include one MCPTT device. In FIG. 1, the MCPTT calling device (110) and the MCPTT device are illustrated as being different, but this is merely an example. For example, the MCPTT calling device (110) and the MCPTT device may be implemented by an electronic device (e.g., the electronic device (1001) of FIG. 10) on which an application associated with MCPTT is installed. In one example, the MCPTT calling device (110), the MCPTT device (130), or the MCPTT device (140) may be referred to as an MCPTT client. In FIG. 1, signaling for first-to-answer call setup is described.

[0026] Referring to FIG. 1, in operation 101, the MCPTT server (120) may receive a call request message from the MCPTT calling device (110).

[0027] In one embodiment, the MCPTT server (120) may receive a call request message from an MCPTT calling device (110) using a network (e.g., a base station, a session initiation protocol (SIP) core).

[0028] In one embodiment, the call request message of the MCPTT calling device (110) may include an identifier of the MCPTT calling device (110), a list of MCPTT identifiers, or a combination thereof. For example, the MCPTT identifier list may include identifiers (IDs) of the target MCPTT devices of the call request. In one example, the MCPTT identifier list may include an identifier of the MCPTT device (130) and an identifier of the MCPTT device (140).

[0029] In operation 102, the MCPTT server (120) may identify MCPTT devices to which the call request message of the MCPTT server (120) is to be transmitted. In one embodiment, the MCPTT server (120) may identify MCPTT devices to which the call request message of the MCPTT server (120) is to be transmitted based on a list of MCPTT identifiers. In one example, the MCPTT server (120) may identify MCPTT devices (130) and MCPTT devices (140) based on the list of MCPTT identifiers.

[0030] In operation 103, the MCPTT server (120) may transmit a call request message of the MCPTT server (120) to the MCPTT device (130). In one embodiment, the call request message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), a session description protocol (SDP) offer, or a combination thereof. For example, the SDP offer may include media parameters.

[0031] In operation 104, the MCPTT server (120) may transmit a call request message of the MCPTT server (120) to the MCPTT device (140). In one embodiment, the call request message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (140), an SDP proposal, or a combination thereof.

[0032] In operation 105, the MCPTT server (120) may receive a call response message from the MCPTT device (130). In one embodiment, the call response message of the MCPTT device (130) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), an SDP answer, or a combination thereof. For example, the SDP answer may include at least one media parameter selected by the MCPTT device (130) from among the media parameters of the SDP proposal.

[0033] In operation 106, the MCPTT server (120) may transmit a call response message of the MCPTT server (120) to the MCPTT calling device (110). In one embodiment, the call response message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), an SDP response, or a combination thereof.

[0034] In operation 107, the MCPTT server (120) may transmit a call cancellation request message to the MCPTT device (140). In one embodiment, since the call request of FIG. 1 relates to a first-to-answer call request, the MCPTT server (120) may transmit the call cancellation request message to the MCPTT device (140) in response to receiving a call response message from the MCPTT device (130). For example, the call cancellation request message may include an identifier of the MCPTT calling device (110) and an identifier of the MCPTT device (140).

[0035] In operation 108, the MCPTT server (120) may establish a media plane for a call between the MCPTT calling device (110) and the MCPTT device (130). In one embodiment, if floor control is used, the MCPTT calling device (110) and the MCPTT device (130) may transmit media individually. In one embodiment, if floor control is not used, the MCPTT calling device (110) and the MCPTT device (130) may transmit media simultaneously.

[0036] Figures 2a and 2b illustrate examples of call setup failures for MCPTT. Referring to Figures 2a and 2b, a mission critical push to talk (MCPTT) system may include an MCPTT calling device (110), an MCPTT device (130), an MCPTT device (140), and a network (210) (e.g., a base station). For example, the network (210) may have coverage (220).

[0037] As described in FIG. 1, the MCPTT calling device (110) can establish a call connection with an MCPTT device (e.g., MCPTT device (130) or MCPTT device (140)) by requesting call setup from the MCPTT server (120) using the MCPTT identifier list. However, in the event of a disaster (e.g., fire, earthquake, tsunami), the establishment of a call connection through the call request of the MCPTT calling device (110) may fail.

[0038] Referring to FIG. 2A, in operation 201, an MCPTT calling device (110) (e.g., a supervisor's device) may request a call connection to an MCPTT device (130) (e.g., a dispatcher's device) and an MCPTT device (140) (e.g., a dispatcher's device) using an MCPTT identifier list. For example, the MCPTT device (130) and the MCPTT device (140) may be located within the coverage (220) of the network (210). However, since the network (210) is unavailable (e.g., a network failure) due to a disaster, the MCPTT server (120) cannot receive (or obtain) responses from the MCPTT device (130) and the MCPTT device (140). Therefore, in operation 202, the MCPTT calling device (110) can receive a message about a failure of the call connection.

[0039] Referring to FIG. 2B, in operation 201, the MCPTT calling device (110) may request a call connection to the MCPTT device (130) and the MCPTT device (140) using the MCPTT identifier list. However, the MCPTT device (130) and the MCPTT device (140) approaching the disaster situation may be located outside the coverage (220) of the network (210). The MCPTT server (120) may not receive (or obtain) a response from the MCPTT device (130) and the MCPTT device (140). Therefore, in operation 202, the MCPTT calling device (110) may receive a message regarding a call connection failure.

[0040] As described above, an MCPTT identifier list may be used to establish a call connection in an MCPTT system. Since the MCPTT server (120) establishes a call connection to an MCPTT device using the MCPTT identifier list, the establishment of the call connection may fail if the MCPTT device's network is unavailable or the MCPTT device is located outside of the network's coverage. If the establishment of the call connection fails, a user of the MCPTT calling device (110) (e.g., a supervisor) may retry the call connection or establish a broadcast call connection. However, retrying the call connection by the user of the MCPTT calling device (110) may delay the supervisor's response to a disaster situation. Establishing a broadcast call connection may place a burden on the network.

[0041] To address the above-described issues, in embodiments of the present disclosure, a zone-based (or location-based) call establishment procedure that does not specify a recipient for establishing a call connection may be performed. By performing the zone-based call establishment procedure, the MCPTT server (120) can wait until it receives a response from the MCPTT device, either when the network becomes available or when the MCPTT device enters the network's coverage area (or a zone designated by a user of the MCPTT calling device). Hereinafter, the zone-based call establishment procedure is described in the present disclosure.

[0042] FIG. 3 illustrates signaling for call setup for MCPTT according to one embodiment. Referring to FIG. 3, the MCPTT system may include an MCPTT call device (110), an MCPTT server (120), an MCPTT device (130), and an MCPTT device (140). However, this is merely an example, and the present disclosure is not limited thereto. For example, the MCPTT system may include multiple MCPTT call devices. For example, the MCPTT system may include one MCPTT device. In FIG. 3, the MCPTT call device (110) and the MCPTT device are depicted as being different, but this is merely an example. For example, the MCPTT call device (110) and the MCPTT device may be implemented by an electronic device (e.g., the electronic device (1001) of FIG. 10) on which an application associated with MCPTT is installed. In one example, the MCPTT calling device (110), the MCPTT device (130), or the MCPTT device (140) may be referred to as an MCPTT client. In FIG. 3, signaling for first-to-answer call setup based on a zone (or location) is described. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed. For example, at least two operations may be performed in parallel.

[0043] Referring to FIG. 3, in operation 301, the MCPTT server (120) can receive a call request message from the MCPTT calling device (110).

[0044] In one embodiment, the MCPTT server (120) may receive a call request message from an MCPTT calling device (110) using a network (e.g., a base station, a session initiation protocol (SIP) core).

[0045] In one embodiment, the call request message of the MCPTT calling device (110) may include an identifier of the MCPTT calling device (110), information about a zone, or a combination thereof. For example, the information about the zone may include geofence information about the zone.

[0046] In operation 302, the MCPTT server (120) can identify a zone for the call request based on the call request message of the MCPTT calling device (110).

[0047] In one embodiment, the MCPTT server (120) may perform an authentication procedure for the MCPTT calling device (110). For example, the MCPTT server (120) may identify whether the user of the MCPTT calling device (110) is authorized to initiate a zone-based call. For example, if the user of the MCPTT calling device (110) is authenticated, the MCPTT server (120) may identify the zone for the call request.

[0048] In one embodiment, the MCPTT server (120) may identify a zone for a call request based on a call request message from the MCPTT calling device (110). For example, the MCPTT server (120) may identify a zone for a call request based on a uniform resource identifier (URI) of the call request message. For example, the zone may be specified by a user of the MCPTT calling device (110) based on a predefined list. For example, the zone may include at least a portion of the coverage area of ​​a network. For example, the zone may include at least a portion of the coverage area of ​​multiple networks.

[0049] In operation 303, the MCPTT server (120) may activate an event for call setup. In one embodiment, the MCPTT server (120) may activate an event for call setup in response to a call request message from the MCPTT calling device (110). For example, the event for call setup may be used to receive a response from an authenticated MCPTT device within the zone. For example, the event may be used to monitor location information that may be received from any MCPTT device upon network recovery. For example, the event may be used to monitor location information that may be received from any MCPTT device upon entry of any MCPTT device into the zone. In one example, the event may be referred to as an event listener.

[0050] In one embodiment, the MCPTT device (130) may perform an authentication procedure using the network when the network is restored. In another example, the MCPTT device (130) may perform an authentication procedure using the network when entering network coverage. For example, the MCPTT device (130) may obtain authorization to use the MCPTT service based on the authentication procedure.

[0051] In one embodiment, the MCPTT device (140) may perform an authentication procedure using the network when the network is restored. In another example, the MCPTT device (140) may perform an authentication procedure using the network when entering network coverage. For example, the MCPTT device (140) may obtain authorization to use the MCPTT service based on the authentication procedure.

[0052] In one embodiment, although not shown, the MCPTT server (120) may transmit a message indicating the activation of an event to MCPTT devices of authorized users associated with the MCPTT service. For example, the message may include a unique identifier of the event for call setup, information about the zone, or a combination thereof. For example, the message may be broadcast over a network. In one example, the message may be used to display the zone on the display of the MCPTT device (130). In one example, the message may be used to display the zone on the display of the MCPTT device (140).

[0053] In operation 304, the MCPTT server (120) can receive location information of the MCPTT device (130) from the MCPTT device (130).

[0054] In one embodiment, the MCPTT device (130) may perform an authentication procedure using the network when the network is restored. In another example, the MCPTT device (130) may perform an authentication procedure using the network when entering the zone. For example, the MCPTT device (130) may obtain authorization to use the MCPTT service based on the authentication procedure.

[0055] In one embodiment, an MCPTT device (130) authenticated (or registered) by the network may be pre-configured to transmit location information of the MCPTT device (130) to the MCPTT server (120). For example, the MCPTT device (130) may be pre-configured to transmit location information of the MCPTT device (130) to the MCPTT server (120) using the network after an authentication procedure is performed. For example, the MCPTT device (130) may be pre-configured to periodically transmit location information of the MCPTT device (130) to the MCPTT server (120). For example, the MCPTT server (120) may receive location information of the MCPTT device (130) based on transmissions of the pre-configured MCPTT device (130).

[0056] In one embodiment, an MCPTT device (130) authenticated (or registered) by the network may, in response to receiving a message indicating activation of an event, transmit location information of the MCPTT device (130) to an MCPTT server (120) using the network. For example, the MCPTT server (120) may receive location information of the MCPTT device (130) from the MCPTT device (130) in response to a message indicating activation of an event.

[0057] In operation 305, the MCPTT server (120) can receive location information of the MCPTT device (140) from the MCPTT device (140).

[0058] In one embodiment, the MCPTT device (140) may perform an authentication procedure using the network when the network is restored. In another example, the MCPTT device (140) may perform an authentication procedure using the network when entering the zone. For example, the MCPTT device (140) may obtain authorization to use the MCPTT service based on the authentication procedure.

[0059] In one embodiment, an MCPTT device (140) authenticated (or registered) by the network may be pre-configured to transmit location information of the MCPTT device (140) to the MCPTT server (120). For example, the MCPTT device (140) may be pre-configured to transmit location information of the MCPTT device (140) to the MCPTT server (120) using the network after an authentication procedure is performed. For example, the MCPTT device (140) may be pre-configured to periodically transmit location information of the MCPTT device (140) to the MCPTT server (120). For example, the MCPTT server (120) may receive location information of the MCPTT device (140) based on transmissions of the pre-configured MCPTT device (140).

[0060] In one embodiment, an MCPTT device (140) authenticated (or registered) by the network may, in response to receiving a message indicating activation of an event, transmit location information of the MCPTT device (140) to an MCPTT server (120) via the network. For example, the MCPTT server (120) may receive location information of the MCPTT device (140) from the MCPTT device (140) in response to a message indicating activation of an event.

[0061] In operation 306, the MCPTT server (120) may transmit a call request message to the MCPTT device (130).

[0062] In one embodiment, the MCPTT server (120) may identify whether the location of the MCPTT device (130) is within the zone based on the location information of the MCPTT device (130). For example, the MCPTT server (120) may send a call request message to the MCPTT device (130) in accordance with the identification that the location of the MCPTT device (140) is within the zone. For example, the MCPTT server (120) may not send a call request message to the MCPTT device (130) in accordance with the identification that the location of the MCPTT device (130) is outside the zone.

[0063] In one embodiment, the call request message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), a session description protocol (SDP) offer, or a combination thereof. For example, the SDP offer may include media parameters.

[0064] In operation 307, the MCPTT server (120) may transmit a call request message to the MCPTT device (140).

[0065] In one embodiment, the MCPTT server (120) may identify whether the location of the MCPTT device (140) is within the zone based on the location information of the MCPTT device (140). For example, the MCPTT server (120) may transmit a call request message to the MCPTT device (140) based on the identification that the location of the MCPTT device (140) is within the zone. For example, the MCPTT server (120) may not transmit a call request message to the MCPTT device (140) based on the identification that the location of the MCPTT device (140) is outside the zone.

[0066] In one embodiment, the call request message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (140), an SDP proposal, or a combination thereof.

[0067] In operation 308, the MCPTT server (120) may receive a call response message from the MCPTT device (130). In one embodiment, the call response message of the MCPTT device (130) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), an SDP answer, or a combination thereof. For example, the SDP answer may include at least one media parameter selected by the MCPTT device (130) from among the media parameters of the SDP proposal.

[0068] In operation 309, the MCPTT server (120) may transmit a call response message to the MCPTT calling device (110). In one embodiment, the call response message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), an SDP response, or a combination thereof.

[0069] In operation 310, the MCPTT server (120) may transmit a call cancellation request message to the MCPTT device (140). In one embodiment, since the call request of FIG. 3 relates to a first-to-answer call request, the MCPTT server (120) may transmit the call cancellation request message to the MCPTT device (140) in response to receiving a call response message from the MCPTT device (130). For example, the call cancellation request message may include an identifier of the MCPTT calling device (110) and an identifier of the MCPTT device (140). Although not shown, the MCPTT server (120) may receive a call cancellation response message from the MCPTT device (140) in response to the call cancellation request message.

[0070] In operation 311, the MCPTT server (120) may establish a media plane for a call between the MCPTT calling device (110) and the MCPTT device (130). For example, the MCPTT server (120) may establish a call connection between the MCPTT calling device (110) and the MCPTT device (130) by sending a call response message of the MCPTT server (120) to the MCPTT calling device (110). In one embodiment, when floor control is used, the MCPTT calling device (110) and the MCPTT device (130) may transmit media individually. In one embodiment, when floor control is not used, the MCPTT calling device (110) and the MCPTT device (130) may transmit media simultaneously.

[0071] In operation 312, the MCPTT server (120) may disable an event for call setup. In one embodiment, the MCPTT server (120) may disable an event for call setup after a call connection between the MCPTT calling device (110) and the MCPTT device (130) is established. In a non-limiting example, the MCPTT server (120) may disable an event for call setup in response to receiving a call response message from an MCPTT device (130) within the zone.

[0072] FIG. 4 is a flowchart illustrating the operation of an MCPTT server for call setup for MCPTT according to one embodiment. In FIG. 4, the operations of an MCPTT (mission critical push to talk) server (120) for first-to-answer call setup based on a zone (or location) are described. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed. For example, at least two operations may be performed in parallel.

[0073] In operation 401, the MCPPTT server (120) may receive a call request message from the MCPTT calling device (110).

[0074] In one embodiment, the MCPTT server (120) may receive a call request message from an MCPTT calling device (110) using a network (e.g., a base station, a session initiation protocol (SIP) core).

[0075] In one embodiment, the call request message of the MCPTT calling device (110) may include an identifier of the MCPTT calling device (110), information about a zone, or a combination thereof. For example, the information about a zone may include geofence information about the zone.

[0076] In one embodiment, the MCPTT server (120) may perform an authentication procedure for the MCPTT calling device (110). For example, the MCPTT server (120) may identify whether the user of the MCPTT calling device (110) is authorized to initiate a zone-based call. For example, if the user of the MCPTT calling device (110) is authenticated, the MCPTT server (120) may identify the zone for the call request.

[0077] In one embodiment, the MCPTT server (120) may identify a zone for a call request based on a call request message from the MCPTT calling device (110). For example, the MCPTT server (120) may identify a zone for a call request based on a uniform resource identifier (URI) of the call request message. For example, the zone may be specified by a user of the MCPTT calling device (110) based on a predefined list. For example, the zone may include at least a portion of the coverage area of ​​a network. For example, the zone may include at least a portion of the coverage area of ​​multiple networks.

[0078] In operation 402, the MCPTT server (120) can monitor whether location information is received in the area indicated by the call request message of the MCPTT calling device (110).

[0079] In one embodiment, the MCPTT server (120) may activate an event for call setup in response to a call request message from the MCPTT calling device (110). For example, the event for call setup may be used to receive a response from an authenticated MCPTT device within the zone. For example, the event may be used to monitor location information that may be received from any MCPTT device upon network recovery. For example, the event may be used to monitor location information that may be received from any MCPTT device upon entry of any MCPTT device into the zone. In one example, the event may be referred to as an event listener.

[0080] In one embodiment, the MCPTT server (120) may transmit a message indicating the activation of an event to MCPTT devices of authorized users associated with the MCPTT service. For example, the message may include a unique identifier for the event for call setup, information about the zone, or a combination thereof. For example, the message may be broadcast over a network. In one example, the message may be used to display the zone on the display of the MCPTT device (130). In one example, the message may be used to display the zone on the display of the MCPTT device (140).

[0081] In one embodiment, at least one MCPTT device authenticated (or registered) by the network may be pre-configured to transmit location information to the MCPTT server (120). For example, the at least one MCPTT device may be pre-configured to transmit location information of the at least one MCPTT device to the MCPTT server (120) using the network after an authentication procedure is performed. For example, the at least one MCPTT device may be pre-configured to periodically transmit location information of the at least one MCPTT device to the MCPTT server (120). For example, the MCPTT server (120) may receive location information of the at least one MCPTT device based on a transmission from the pre-configured MCPTT device (130).

[0082] In one embodiment, at least one MCPTT device authenticated (or registered) by the network may, in response to receiving a message indicating activation of an event, transmit location information of the at least one MCPTT device to an MCPTT server (120) via the network. For example, the MCPTT server (120) may receive location information of the at least one MCPTT device in response to a message indicating activation of an event.

[0083] In operation 403, the MCPTT server (120) may transmit a call request message to at least one MCPTT device.

[0084] In one embodiment, the MCPTT server (120) may identify whether the location of at least one MCPTT device is within the zone based on location information of at least one MCPTT device. In one example, the MCPTT server (120) may transmit a call request message to the MCPTT device (130) in accordance with the identification that the location of the at least one MCPTT device (130) among the received location information is within the zone. In one example, the MCPTT server (120) may not transmit a call request message to the MCPTT device (140) in accordance with the identification that the location of the at least one MCPTT device (140) among the received location information is outside the zone.

[0085] In one embodiment, the call request message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), a session description protocol (SDP) offer, or a combination thereof. For example, the SDP offer may include media parameters.

[0086] In operation 404, the MCPTT server (120) may receive a call response message from the MCPTT device (130). In one embodiment, the MCPTT server (120) may receive a call response message from the MCPTT device (130) among at least one MCPTT device. For example, the call response message of the MCPTT device (130) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), a SIP answer, or a combination thereof. For example, the SDP answer may include at least one media parameter selected by the MCPTT device (130) among the media parameters of the SDP proposal.

[0087] In operation 405, the MCPTT server (120) may transmit a call response message to the MCPTT calling device (110).

[0088] In one embodiment, the MCPTT server (120) may send a call response message to the MCPTT calling device (110). For example, the call response message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), an SDP response, or a combination thereof.

[0089] In one embodiment, the MCPTT server (120) may send a call cancellation request message to other MCPTT devices except the MCPTT device (130). For example, the MCPTT server (120) may send a call response message to the MCPTT calling device (130), and then send a call cancellation request message to other MCPTT devices except the MCPTT device (130). For example, since the call request in FIG. 3 is a first-come, first-served call request, the MCPTT server (120) may send the call cancellation request message to the other MCPTT devices based on receiving a call response message from the MCPTT device (130). For example, the call cancellation request message may include an identifier of the MCPTT calling device (110) and an identifier of the MCPTT device that is the target of the cancellation request message. For example, the MCPTT server (120) may receive a call cancellation response message from the other MCPTT devices in response to the call cancellation request message.

[0090] In one embodiment, the MCPTT server (120) may establish a media plane for a call between the MCPTT calling device (110) and the MCPTT device (130). For example, the MCPTT server (120) may establish a media plane for a call between the MCPTT calling device (110) and the MCPTT device (130) after transmitting a call response message to the MCPTT calling device (130). For example, the MCPTT server (120) may establish a call connection between the MCPTT calling device (110) and the MCPTT device (130) by transmitting a call response message of the MCPTT server (120) to the MCPTT calling device (110). In one embodiment, when floor control is used, the MCPTT calling device (110) and the MCPTT device (130) may individually transmit media. In one embodiment, if floor control is not used, the MCPTT calling device (110) and the MCPTT device (130) can transmit media simultaneously.

[0091] In one embodiment, the MCPTT server (120) may disable an event for call setup. For example, the MCPTT server (120) may disable an event for call setup after transmitting a call response message to the MCPTT calling device (130). For example, the MCPTT server (120) may disable an event for call setup after a call connection between the MCPTT calling device (110) and the MCPTT device (130) is established. In a non-limiting example, the MCPTT server (120) may disable an event for call setup in response to receiving a call response message from an MCPTT device (130) within the zone.

[0092] Figure 5 illustrates an example of a call setup for MCPTT. Referring to Figure 5, an MCPTT (mission critical push to talk) system may include a first MCPTT call device (110), a second MCPTT call device (510), and a network (210) (e.g., a base station). For example, the network (210) may have coverage (220).

[0093] Referring to FIG. 5, in operation 501, a first MCPTT calling device (110) may transmit a call request to MCPTT devices within the coverage (220) of a network (210). In operation 502, a second MCPTT calling device (510) may transmit a call request to MCPTT devices within the coverage (220) of a network (210). For example, the zone according to the call request of the first MCPTT calling device (110) may be the same as the zone according to the call request of the second MCPTT calling device (510).

[0094] As described above, a zone-based call request with the same conditions may be triggered by different MCPTT calling devices. The MCPTT server (120) may not be able to identify which calling device, the first MCPTT calling device (110) or the second MCPTT calling device (510), should the call be established for. For example, the MCPTT server (120) may not be able to identify which device identifier should be included in the call request message sent to the MCPTT device (e.g., MCPTT device (130), MCPTT device (140)).

[0095] To address the above-described issues, the following embodiments enable MCPTT calling devices to participate in existing call requests. The present disclosure describes call establishment procedures when multiple MCPTT calling devices trigger zone-based call requests under the same conditions.

[0096] Figure 6 illustrates an example of signaling for call setup for MCPTT according to one embodiment. Figure 6 illustrates the operations of an MCPTT (mission critical push to talk) server (120) for zone (or location)-based, first-to-answer call setup. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed. For example, at least two operations may be performed in parallel.

[0097] In operation 601, the MCPTT server (120) may receive a call request message from the MCPTT calling device (110).

[0098] In one embodiment, the MCPTT server (120) may receive a call request message from an MCPTT calling device (110) using a network (e.g., a base station, a session initiation protocol (SIP) core).

[0099] In one embodiment, the call request message of the MCPTT calling device (110) may include an identifier of the MCPTT calling device (110), information about a zone, or a combination thereof. For example, the information about a zone may include geofence information about the zone.

[0100] In operation 602, the MCPTT server (120) may identify a zone for the call request. For example, the MCPTT server (120) may identify the zone for the call request based on the call request message. For example, the MCPTT server (120) may identify the zone for the call request based on the uniform resource identifier (URI) of the call request message. For example, the zone may be specified by the user of the MCPTT calling device (110) based on a predefined list. For example, the zone may include at least a portion of the coverage area of ​​a network. For example, the zone may include at least a portion of the coverage area of ​​multiple networks.

[0101] In operation 603, the MCPTT server (120) may activate an event for call setup. For example, the MCPTT server (120) may activate an event for call setup based on receiving a call request message from the MCPTT calling device (110). For example, the event may be used to monitor location information that may be received from any MCPTT device upon network recovery. For example, the event may be used to monitor location information that may be received from any MCPTT device upon entry into the area of ​​any MCPTT device. In one example, the event may be referred to as an event listener.

[0102] In one embodiment, although not shown, the MCPTT server (120) may transmit a message indicating the activation of an event to MCPTT devices of authorized users of the network. For example, the message may include a unique identifier for the event, information about the area (e.g., geofence information), or a combination thereof. For example, the message may be broadcast over the network. For example, the message may be used to display the area on the display of the MCPTT device.

[0103] In operation 604, the MCPTT server (120) may receive an event list request message from the MCPTT calling device (510). For example, the event list request message may correspond to a message requesting a list of activated events of the MCPTT server (120).

[0104] In operation 605, the MCPTT server (120) may transmit an event list response message to the MCPTT calling device (510). For example, the event list response message may include a list of activated events of the MCPTT server (120). For example, the event list response message may include a unique identifier of an event for call setup and information about a zone associated with the event.

[0105] In operation 606, the MCPTT server (120) may receive a call request message from the MCPTT calling device (510). For example, the call request message may include an identifier of the MCPTT calling device (510), a unique identifier of the event, information about the zone, or a combination thereof.

[0106] In operation 607, the MCPTT server (120) may transmit a notification message to the MCPTT calling device (110). For example, the MCPTT server (120) may transmit the notification message to the MCPTT calling device (110) based on receiving a call request message from the MCPTT calling device (510). For example, the notification message may be used to notify the MCPTT calling device (110) of the participation of the MCPTT calling device (510).

[0107] At step 608, the MCPTT server (120) may send a call response message to the MCPTT calling device (510). For example, the MCPTT server (120) may index the MCPTT calling device (510) as a subscriber. For example, the call response message may be used to inform the MCPTT calling device (510) that the call request of the MCPTT calling device (510) has been accepted.

[0108] In operation 609, the MCPTT server (120) can receive location information from the MCPTT device (130).

[0109] In one embodiment, the MCPTT device (130) may perform an authentication procedure using the network when the network is restored. In another example, the MCPTT device (130) may perform an authentication procedure using the network when entering network coverage. For example, the MCPTT device (130) may obtain authorization to use the MCPTT service based on the authentication procedure.

[0110] In one embodiment, an MCPTT device (130) authenticated (or registered) by the network may be pre-configured to transmit location information of the MCPTT device (130) to the MCPTT server (120). For example, the MCPTT device (130) may be pre-configured to transmit location information of the MCPTT device (130) to the MCPTT server (120) using the network after an authentication procedure is performed. For example, the MCPTT device (130) may be pre-configured to periodically transmit location information of the MCPTT device (130) to the MCPTT server (120). For example, the MCPTT server (120) may receive location information of the MCPTT device (130) based on transmissions of the pre-configured MCPTT device (130).

[0111] In one embodiment, an MCPTT device (130) authenticated (or registered) by the network may, in response to receiving a message indicating activation of an event, transmit location information of the MCPTT device (130) to an MCPTT server (120) using the network. For example, the MCPTT server (120) may receive location information of the MCPTT device (130) from the MCPTT device (130) in response to a message indicating activation of an event.

[0112] In operation 610, the MCPTT server (120) can receive location information from the MCPTT device (140).

[0113] In one embodiment, the MCPTT device (140) may perform an authentication procedure using the network when the network is restored. In another example, the MCPTT device (140) may perform an authentication procedure using the network when entering network coverage. For example, the MCPTT device (140) may obtain authorization to use the MCPTT service based on the authentication procedure.

[0114] In one embodiment, an MCPTT device (140) authenticated (or registered) by the network may be pre-configured to transmit location information of the MCPTT device (140) to the MCPTT server (120). For example, the MCPTT device (140) may be pre-configured to transmit location information of the MCPTT device (140) to the MCPTT server (120) using the network after an authentication procedure is performed. For example, the MCPTT device (140) may be pre-configured to periodically transmit location information of the MCPTT device (140) to the MCPTT server (120). For example, the MCPTT server (120) may receive location information of the MCPTT device (140) based on transmissions of the pre-configured MCPTT device (140).

[0115] In one embodiment, an MCPTT device (140) authenticated (or registered) by the network may, in response to receiving a message indicating activation of an event, transmit location information of the MCPTT device (140) to an MCPTT server (120) via the network. For example, the MCPTT server (120) may receive location information of the MCPTT device (140) from the MCPTT device (140) in response to a message indicating activation of an event.

[0116] In operation 611, the MCPTT server (120) may transmit a call request message to the MCPTT device (130).

[0117] In one embodiment, the MCPTT server (120) may identify whether the location of the MCPTT device (130) is within the zone based on the location information of the MCPTT device (130). For example, the MCPTT server (120) may send a call request message to the MCPTT device (130) in accordance with the identification that the location of the MCPTT device (130) is within the zone. In another example, the MCPTT server (120) may not send a call request message to the MCPTT device (130) in accordance with the identification that the location of the MCPTT device (130) is outside the zone.

[0118] In one embodiment, the call request message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), a session description protocol (SDP) offer, or a combination thereof. For example, the SDP offer may include media parameters.

[0119] In operation 612, the MCPTT server (120) may transmit a call request message to the MCPTT device (140).

[0120] In one embodiment, the MCPTT server (120) may identify whether the location of the MCPTT device (140) is within the zone based on the location information of the MCPTT device (140). For example, the MCPTT server (120) may send a call request message to the MCPTT device (140) in accordance with the identification that the location of the MCPTT device (140) is within the zone. In another example, the MCPTT server (120) may not send a call request message to the MCPTT device (140) in accordance with the identification that the location of the MCPTT device (140) is outside the zone.

[0121] In one embodiment, the call request message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (140), a session description protocol (SDP) offer, or a combination thereof. For example, the SDP offer may include media parameters.

[0122] In operation 613, the MCPTT server (120) may receive a call response message from the MCPTT device (130). In one embodiment, the call response message of the MCPTT device (130) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), an SDP answer, or a combination thereof. For example, the SDP answer may include at least one media parameter selected by the MCPTT device (130) from among the media parameters of the SDP proposal.

[0123] In operation 614, the MCPTT server (120) may transmit a call response message to the MCPTT calling device (110). In one embodiment, the call response message of the MCPTT server (120) may include an identifier of the MCPTT calling device (110), an identifier of the MCPTT device (130), an SDP response, or a combination thereof.

[0124] In operation 615, the MCPTT server (120) may transmit a call cancellation request message to the MCPTT device (140). In one embodiment, since the call request of FIG. 3 relates to a first-come, first-served call request, the MCPTT server (120) may transmit the call cancellation request message to the MCPTT device (140) in response to receiving a call response message from the MCPTT device (130). For example, the call cancellation request message may include an identifier of the MCPTT calling device (110) and an identifier of the MCPTT device (140). Although not shown, the MCPTT server (120) may receive a call cancellation response message from the MCPTT device (140) in response to the call cancellation request message.

[0125] In operation 616, the MCPTT server (120) may establish a media plane for calls from the MCPTT calling device (110), the MCPTT calling device (510), and the MCPTT device (130). For example, the MCPTT server (120) may establish the media planes from the MCPTT calling device (110), the MCPTT calling device (510), and the MCPTT device (130) by sending a call response message from the MCPTT server (120) to the MCPTT calling device (110). In one embodiment, when floor control is used, the MCPTT calling device (110) and the MCPTT device (130) may transmit media individually. In one embodiment, when floor control is not used, the MCPTT calling device (110) and the MCPTT device (130) may transmit media simultaneously.

[0126] In operation 617, the MCPTT server (120) may transmit a call invitation message to the MCPTT calling device (510). For example, the MCPTT server (120) may transmit the call invitation message to the MCPTT calling device (510) after a call connection between the MCPTT calling device (110) and the MCPTT device (130) is established. For example, the MCPT server (120) may transmit the call invitation message to the MCPTT calling device (510) after a media plane is established. For example, the call invitation message may include parameters for joining the call connection. In one example, the call invitation message may be referred to as a late call entry invite.

[0127] In operation 618, the MCPTT server (120) may disable an event for call setup. In one embodiment, the MCPTT server (120) may disable an event for call setup after a call connection between the MCPTT calling device (110) and the MCPTT device (130) is established. In a non-limiting example, the MCPTT server (120) may disable an event for call setup in response to receiving a call response message from an MCPTT device (130) within the zone.

[0128] FIG. 7 illustrates a screen of an MCPTT device for establishing a call for MCPTT according to one embodiment. FIG. 7 illustrates operations of an MCPTT device (130) for establishing an MCPTT call connection. While FIG. 7 illustrates operations of the MCPTT device (130), the present disclosure is not limited thereto. The operations described in FIG. 7 may be performed by an MCPTT call device (510) or an MCPTT device (140).

[0129] In one embodiment, the MCPTT device (130) may display a zone (731) for a call request and a pending state (732) of the call request on the screen (710) of the display. For example, the MCPTT device (130) may receive a message from the MCPTT server (120) indicating the activation of an event associated with a call setup. For example, the MCPTT device (130) may receive a message from the MCPTT server (120) indicating the activation of an event associated with a call setup upon network recovery or entry into a zone. For example, the message may include a unique identifier of the event, information about the zone (e.g., geofence information), or a combination thereof. For example, the MCPTT device (130) may display a zone (731) on the screen (710) of the display based on the information about the zone. For example, the MCPTT device (130) may display a pending status (732) of a call request on the screen (710). For example, the pending status (732) may indicate that a call connection based on a call request of the MCPTT calling device (110) has not been established. For example, the MCPTT device (130) may transmit a message to the MCPTT server (120) based on obtaining a user input for a zone (731) displayed by the display of the MCPTT device (130). For example, the MCPTT device (130) may perform procedures for establishing a call connection with the MCPTT calling device (110) by transmitting a message to the MCPTT server (120).

[0130] In one embodiment, the MCPTT device (130) may display the zone (731) for the call request and the ongoing state (733) of the call connection on the screen (720) of the display. For example, the MCPTT device (130) may receive a message from the MCPTT server (120) indicating that a call connection has been established based on the call request of the MCPTT calling device (110) while the screen (710) is being displayed. For example, the MCPTT device (130) may change the screen displayed by the display of the MCPTT device (130) from the screen (710) to the screen (720) based on receiving the message. For example, the MCPTT device (130) may display the zone (731) and the ongoing state (733) of the call connection on the screen (720) of the display based on the message. For example, the progress status (733) may indicate that a call connection has been established based on a call request from an MCPTT calling device (110). For example, the MCPTT device (130) may transmit a join request message for the call connection to the MCPTT server (120) based on obtaining a user input for an area (731) displayed by the display. For example, the MCPTT device (130) may join a call connection established for the MCPTT calling device (110) by transmitting a join request message to the MCPTT server (120).

[0131] FIG. 8 is a flowchart illustrating the operation of an MCPTT device for call setup for MCPTT according to one embodiment. In FIG. 8, the operations of an MCPTT (mission critical push to talk) device (130) for first-to-answer call setup based on a zone (or location) are described. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed. For example, at least two operations may be performed in parallel.

[0132] In operation 801, the MCPTT device (130) may receive a message from the MCPTT server (120) indicating the activation of an event associated with a zone-based call setup. For example, the event may be used for monitoring location information by the MCPTT server (120). For example, the message may include a unique identifier of the event, information about the zone (e.g., geofence information), or a combination thereof.

[0133] In operation 802, the MCPTT device (130) may display the zone associated with the event and the pending status of the call request using the display. For example, the MCPTT device (130) may display the zone (e.g., zone (731) of FIG. 7) on the screen of the display based on the zone information of the message. For example, the MCPTT device (130) may display the pending status of the call request (e.g., pending status (732) of FIG. 7) on the screen of the display. For example, the pending status may indicate that a call connection based on the call request of the MCPTT calling device (110) has not been established.

[0134] In operation 803, the MCPTT device (130) may transmit location information of the MCPTT device (130) to the MCPTT server (120). For example, the MCPTT device (130) may obtain user input for an area displayed by the display. For example, the MCPTT device (130) may transmit location information of the MCPTT device (130) to the MCPTT server (120) based on obtaining user input for the area.

[0135] In operation 804, the MCPTT device (130) may receive a call request message from the MCPTT server (120). For example, the MCPTT device (130) may receive the call request message from the MCPTT server (120) in response to the location information. For example, the MCPTT device (130) may display an object on the screen of the display indicating whether to establish a call connection to the MCPTT calling device (110) based on receiving the call request message. For example, the MCPTT device (130) may obtain a user input for establishing a call connection to the MCPTT calling device (110) through the object displayed by the display.

[0136] In operation 805, the MCPTT device (130) may transmit a call response message to the MCPTT server (120). For example, the MCPTT device (130) may transmit the call response message to the MCPTT server (120) based on obtaining a user input for establishing a call connection to the MCPTT calling device (110) through an object displayed by the display. For example, the MCPTT device (130) may establish a call connection with the MCPTT calling device (110) by transmitting the call response message to the MCPTT server (120). In one embodiment, the MCPTT device (130) may display the progress status of the call connection on the screen of the display based on establishing the call connection with the MCPTT calling device (110).

[0137] Figure 9 is a simplified block diagram of an MCPTT server.

[0138] Referring to FIG. 9, the MCPTT server (120) may include a processor (910), a memory (920), and a communication circuit (930). The processor (910) may be operatively coupled with or connected with the memory (920) and the communication circuit (930).

[0139] In one embodiment, the processor (910) may control the memory (920) and the communication circuit (930). For example, the processor (910) may be composed of at least one processor. For example, the processor (910) may include at least one processor. For example, the processor (910) may include hardware components for processing data based on instructions. For example, the processor (910) may perform the operations of the MCPTT server (120) described above by executing instructions stored in the memory (920). For example, the processor (910) may correspond to multiple processors that divide and perform multiple operations among the processors. For example, the processor (910) may correspond to multiple processors that collectively perform multiple operations among the processors.

[0140] In one embodiment, memory (920) may be used to store information or data. For example, memory (920) may include non-volatile memory. For example, memory (920) may include volatile memory. For example, memory (920) may include a computer-readable storage medium, such as a magnetic or optical disk. For example, memory (920) may store data acquired based on operations performed by processor (910).

[0141] In one embodiment, the communication circuit (930) may be utilized for various radio access technologies (RATs). For example, the communication circuit (930) may correspond to at least a portion of the communication module (1090) of FIG. 10. For example, the communication circuit (930) may support the establishment of a direct (e.g., wired) or wireless communication channel between the MCPTT server (120) and the MCPTT device, and the performance of communication through the established communication channel.

[0142] The MCPTT calling device or MCPTT device that performs the above-described operations may correspond to the electronic device (1201) of FIG. 10 below.

[0143] FIG. 10 is a block diagram of an electronic device within a network environment according to various embodiments.

[0144] Referring to FIG. 10, in a network environment (1000), an electronic device (1001) may communicate with an electronic device (1002) via a first network (1098) (e.g., a short-range wireless communication network), or may communicate with at least one of an electronic device (1004) or a server (1008) via a second network (1099) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (1001) may communicate with the electronic device (1004) via the server (1008). According to one embodiment, the electronic device (1001) may include a processor (1020), a memory (1030), an input module (1050), an audio output module (1055), a display module (1060), an audio module (1070), a sensor module (1076), an interface (1077), a connection terminal (1078), a haptic module (1079), a camera module (1080), a power management module (1088), a battery (1089), a communication module (1090), a subscriber identification module (1096), or an antenna module (1097). In some embodiments, the electronic device (1001) may omit at least one of these components (e.g., the connection terminal (1078)), or may have one or more other components added. In some embodiments, some of these components (e.g., sensor module (1076), camera module (1080), or antenna module (1097)) may be integrated into a single component (e.g., display module (1060)).

[0145] The processor (1020) may, for example, execute software (e.g., a program (1040)) to control at least one other component (e.g., a hardware or software component) of the electronic device (1001) connected to the processor (1020) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (1020) may store commands or data received from other components (e.g., a sensor module (1076) or a communication module (1090)) in the volatile memory (1032), process the commands or data stored in the volatile memory (1032), and store result data in the non-volatile memory (1034). According to one embodiment, the processor (1020) may include a main processor (1021) (e.g., a central processing unit or an application processor) or a secondary processor (1023) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together with the main processor (1021). For example, when the electronic device (1001) includes the main processor (1021) and the secondary processor (1023), the secondary processor (1023) may be configured to use less power than the main processor (1021) or to be specialized for a given function. The secondary processor (1023) may be implemented separately from the main processor (1021) or as a part thereof.

[0146] The auxiliary processor (1023) may control at least a portion of functions or states associated with at least one component (e.g., the display module (1060), the sensor module (1076), or the communication module (1090)) of the electronic device (1001), for example, on behalf of the main processor (1021) while the main processor (1021) is in an inactive (e.g., sleep) state, or together with the main processor (1021) while the main processor (1021) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (1023) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (1080) or a communication module (1090)). In one embodiment, the auxiliary processor (1023) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, on the electronic device (1001) itself where the artificial intelligence model is executed, or can be performed through a separate server (e.g., server (1008)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0147] The memory (1030) can store various data used by at least one component (e.g., the processor (1020) or the sensor module (1076)) of the electronic device (1001). The data can include, for example, software (e.g., the program (1040)) and input data or output data for commands related thereto. The memory (1030) can include volatile memory (1032) or non-volatile memory (1034).

[0148] The program (1040) may be stored as software in memory (1030) and may include, for example, an operating system (1042), middleware (1044), or an application (1046).

[0149] The input module (1050) can receive commands or data to be used in a component of the electronic device (1001) (e.g., a processor (1020)) from an external source (e.g., a user) of the electronic device (1001). The input module (1050) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0150] The audio output module (1055) can output audio signals to the outside of the electronic device (1001). The audio output module (1055) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0151] The display module (1060) can visually provide information to an external party (e.g., a user) of the electronic device (1001). The display module (1060) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. In one embodiment, the display module (1060) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0152] The audio module (1070) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (1070) can acquire sound through the input module (1050), output sound through the sound output module (1055), or an external electronic device (e.g., electronic device (1002)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (1001).

[0153] The sensor module (1076) can detect the operating status (e.g., power or temperature) of the electronic device (1001) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (1076) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0154] The interface (1077) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (1001) with an external electronic device (e.g., the electronic device (1002)). In one embodiment, the interface (1077) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0155] The connection terminal (1078) may include a connector through which the electronic device (1001) may be physically connected to an external electronic device (e.g., the electronic device (1002)). According to one embodiment, the connection terminal (1078) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0156] The haptic module (1079) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. In one embodiment, the haptic module (1079) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0157] The camera module (1080) can capture still images and videos. According to one embodiment, the camera module (1080) may include one or more lenses, image sensors, image signal processors, or flashes.

[0158] The power management module (1088) can manage power supplied to the electronic device (1001). According to one embodiment, the power management module (1088) can be implemented, for example, as at least a part of a power management integrated circuit (PMIC).

[0159] A battery (1089) may power at least one component of the electronic device (1001). In one embodiment, the battery (1089) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0160] The communication module (1090) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (1001) and an external electronic device (e.g., electronic device (1002), electronic device (1004), or server (1008)), and the performance of communication through the established communication channel. The communication module (1090) may operate independently from the processor (1020) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (1090) may include a wireless communication module (1092) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (1094) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, a corresponding communication module can communicate with an external electronic device (1004) via a first network (1098) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (1099) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules can be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (1092) can verify or authenticate the electronic device (1001) within a communication network such as the first network (1098) or the second network (1099) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (1096).

[0161] The wireless communication module (1092) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimizing terminal power and connecting multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (1092) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (1092) may support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (1092) may support various requirements specified in the electronic device (1001), an external electronic device (e.g., the electronic device (1004)), or a network system (e.g., the second network (1099)). According to one embodiment, the wireless communication module (1092) may support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL) each, or 1 ms or less for round trip) for URLLC realization.

[0162] The antenna module (1097) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (1097) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (1097) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (1098) or the second network (1099), may be selected from the plurality of antennas by, for example, the communication module (1090). A signal or power may be transmitted or received between the communication module (1090) and an external electronic device through the at least one selected antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (1097).

[0163] According to various embodiments, the antenna module (1097) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band.

[0164] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0165] According to one embodiment, commands or data may be transmitted or received between the electronic device (1001) and an external electronic device (1004) via a server (1008) connected to a second network (1099). Each of the external electronic devices (1002 or 1004) may be the same or a different type of device as the electronic device (1001). According to one embodiment, all or part of the operations executed in the electronic device (1001) may be executed in one or more of the external electronic devices (1002, 1004, or 1008). For example, when the electronic device (1001) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (1001) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (1001). The electronic device (1001) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (1001) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (1004) may include an Internet of Things (IoT) device. The server (1008) may be an intelligent server utilizing machine learning and / or a neural network.According to one embodiment, an external electronic device (1004) or server (1008) may be included in the second network (1099). The electronic device (1001) may be applied to intelligent services (e.g., smart homes, smart cities, smart cars, or healthcare) based on 5G communication technology and IoT-related technology.

[0166] A mission critical push to talk (MCPTT) server (or MCPTT device) according to the present disclosure can perform procedures for a zone-based call setup that does not specify a target recipient. By performing the procedures for a zone-based call setup, the MCPTT server can wait to receive a response from any MCPTT device due to network recovery. The MCPTT server can wait to receive a response from any MCPTT device as any MCPTT device enters a disaster zone. By waiting to receive a response from any MCPTT device, the MCPTT server can prevent a delay in the response of a user of an MCPTT call device to a disaster situation. When a zone-based call request with the same condition is triggered from multiple MCPTT call devices, the MCPTT server can establish a call connection by allowing other MCPTT call devices to join the existing call request.

[0167] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the above description.

[0168] As described above, the MCPTT server may include communication circuitry. The MCPTT server may include a memory storing instructions and including one or more storage media. The MCPTT server may include at least one processor including a processing circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to receive a call request message including information about a zone from an MCPTT calling device. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to monitor whether location information of at least one MCPTT device is received in the zone indicated by the call request message of the MCPTT calling device. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to transmit a call request message of the MCPTT server to the MCPTT device in response to receiving location information of the MCPTT device in the zone. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to receive a call response message from the MCPTT device in response to the call request message of the MCPTT server. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to establish a call connection between the MCPTT calling device and the MCPTT device by sending a call response message of the MCPTT server to the MCPTT calling device in response to the call request message of the MCPTT calling device.

[0169] For example, the instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to, in response to receiving the call request message of the MCPTT calling device, activate an event for monitoring location information of the at least one MCPTT device, in response to activating the event, transmit a message comprising a unique identifier of the event and information about the zone to MCPTT devices in a network associated with the MCPTT server, and in response to the message, receive location information of the MCPTT devices from the MCPTT devices.

[0170] For example, the instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to identify, based on location information of the MCPTT devices, whether the MCPTT devices are located in the zone, to send call request messages to the at least one MCPTT device based on the identification that at least one MCPTT device of the MCPTT devices is located in the zone, to receive, from the MCPTT device of the at least one MCPTT device, the call response message of the MCPTT device, and to deactivate the event based on receiving the call response message of the MCPTT device.

[0171] For example, the instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT server to receive a call request message from another MCPTT calling device, the call request message including a unique identifier of an event for monitoring location information of the at least one MCPTT device being activated, and to transmit a call invitation message to the other MCPTT calling device after the call connection between the MCPTT calling device and the MCPTT device is established.

[0172] For example, the call request message of the MCPTT calling device may not indicate a target recipient.

[0173] An MCPTT device as described above may include communication circuitry. The MCPTT device may include a display. The MCPTT device may include a memory storing instructions and including one or more storage media. The MCPTT device may include at least one processor including a processing circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to receive a message from an MCPTT server indicating activation of an event associated with a zone-based call setup. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to display, using the display, a zone associated with the event and a pending status of a call request by an MCPTT calling device, based on the message. The instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to transmit location information of the MCPTT device to the MCPTT server based on obtaining user input for the area displayed by the display.

[0174] For example, the instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to receive a call request message from the MCPTT server in response to location information of the MCPTT device, and to display an object on the display indicating whether to establish a call connection to the MCPTT calling device based on receiving the call request message.

[0175] For example, the instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to establish the call connection with the MCPTT calling device by sending a call response message to the MCPTT server based on obtaining user input for establishing the call connection to the MCPTT calling device through the object.

[0176] For example, the instructions, when individually or collectively executed by the at least one processor, may cause the MCPTT device to display, using the display, an ongoing state of the call connection to the MCPTT call device based on establishing the call connection with the MCPTT call device.

[0177] For example, a message indicating activation of the event may include a unique identifier for the event and information about the zone associated with the event.

[0178] The method performed by the MCPTT server as described above may include receiving a call request message including information about a zone from an MCPTT calling device. The method may include monitoring whether location information of at least one MCPTT device is received in the zone indicated by the call request message of the MCPTT calling device. The method may include transmitting a call request message of the MCPTT server to the MCPTT device in response to receiving the location information of the MCPTT device in the zone. The method may include receiving a call response message from the MCPTT device in response to the call request message of the MCPTT server. The method may include establishing a call connection between the MCPTT calling device and the MCPTT device by transmitting a call response message of the MCPTT server to the MCPTT calling device in response to the call request message of the MCPTT calling device.

[0179] For example, the method may further include, in response to receiving the call request message of the MCPTT calling device, activating an event for monitoring location information of the at least one MCPTT device; in response to activating the event, transmitting a message including a unique identifier of the event and information about the zone to MCPTT devices of a network associated with the MCPTT server; and in response to the message, receiving location information of the MCPTT devices from the MCPTT devices.

[0180] For example, the method may further include an operation of identifying whether the MCPTT devices are located in the zone based on location information of the MCPTT devices, an operation of transmitting call request messages to at least one MCPTT device based on identification that at least one MCPTT device among the MCPTT devices is located in the zone, an operation of receiving the call response message of the MCPTT device from the MCPTT device among the at least one MCPTT devices, and an operation of deactivating the event based on receiving the call response message of the MCPTT device.

[0181] For example, the method may further include, after an event for monitoring location information of the at least one MCPTT device is activated, receiving a call request message including a unique identifier of the event from another MCPTT calling device, and after the call connection between the MCPTT calling device and the MCPTT device is established, transmitting a call invitation message to the other MCPTT calling device.

[0182] For example, the call request message of the MCPTT calling device may not indicate a target recipient.

[0183] The method performed by the MCPTT device as described above may include receiving a message from the MCPTT server indicating activation of an event associated with a zone-based call setup. The method may include displaying, based on the message, a zone associated with the event and a pending status of a call request by the MCPTT calling device using a display. The method may include transmitting location information of the MCPTT device to the MCPTT server based on obtaining a user input for the zone displayed by the display.

[0184] For example, the method may further include receiving a call request message from the MCPTT server in response to location information of the MCPTT device, and displaying an object using the display indicating whether to establish a call connection to the MCPTT calling device based on receiving the call request message.

[0185] For example, the method may further include an operation of establishing the call connection with the MCPTT calling device by sending a call response message to the MCPTT server based on obtaining a user input for establishing the call connection to the MCPTT calling device through the object.

[0186] For example, based on establishing the call connection with the MCPTT calling device, the method may further include an operation of displaying an ongoing state of the call connection to the MCPTT calling device using the display.

[0187] For example, a message indicating activation of the event may include a unique identifier for the event and information about the zone associated with the event.

[0188] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0189] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure. The one or more programs may be provided as a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0190] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0191] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0192] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0193] According to embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0194] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible within the scope of the present disclosure.

Claims

1. In the MCPTT (mission critical push to talk) server, communication circuit; A memory storing instructions and including one or more storage media; and At least one processor comprising a processing circuit, The above instructions, when individually or collectively executed by the at least one processor, cause the MCPTT server to: Receive a call request message containing information about a zone from an MCPTT calling device, Monitor whether at least one MCPTT device location information is received in the zone indicated by the call request message of the MCPTT calling device; In the above area, in response to receiving location information of the MCPTT device, the MCPTT server transmits a call request message to the MCPTT device, In response to the call request message of the MCPTT server, a call response message is received from the MCPTT device, and By transmitting a call response message of the MCPTT server to the MCPTT calling device in response to the call request message of the MCPTT calling device, thereby causing a call connection to be established between the MCPTT calling device and the MCPTT device, MCPTT server.

2. In paragraph 1, The above instructions, when individually or collectively executed by the at least one processor, In response to receiving the call request message of the MCPTT calling device, activating an event for monitoring location information of the at least one MCPTT device, In response to activating the above event, a message including a unique identifier of the event and information about the zone is transmitted to MCPTT devices in the network associated with the MCPTT server, and In response to the above message, to receive location information of the MCPTT devices from the MCPTT devices, causing the above MCPTT server to MCPTT server.

3. In paragraph 2, The above instructions, when individually or collectively executed by the at least one processor, Based on the location information of the above MCPTT devices, identify whether the above MCPTT devices are located in the above zone, Based on the identification that at least one MCPTT device among the above MCPTT devices is located in the zone, transmitting call request messages to the at least one MCPTT device, Receive the call response message of the MCPTT device from the MCPTT device among the at least one MCPTT device, and To disable the event based on receiving the call response message from the MCPTT device; causing the above MCPTT server to MCPTT server.

4. In paragraph 1, The above instructions, when individually or collectively executed by the at least one processor, After an event for monitoring the location information of at least one MCPTT device is activated, a call request message including a unique identifier of the event is received from another MCPTT calling device, and After the call connection between the MCPTT calling device and the MCPTT device is established, transmit a call invitation message to the other MCPTT calling device. causing the above MCPTT server to MCPTT server.

5. In paragraph 1, The call request message of the above MCPTT calling device does not indicate the target recipient. MCPTT server.

6. In MCPTT (mission critical push to talk) devices, communication circuit; display; A memory storing instructions and including one or more storage media; and At least one processor comprising a processing circuit, The above instructions, when individually or collectively executed by the at least one processor, cause the MCPTT device to: Receive a message from the MCPTT server indicating the activation of an event associated with zone-based call setup; Based on the above message, the area associated with the above event and the pending status of the call request by the MCPTT calling device are displayed using the above display, and Causing the MCPTT device to transmit location information to the MCPTT server based on obtaining user input for the area indicated by the display. MCPTT device.

7. In paragraph 6, The above instructions, when individually or collectively executed by the at least one processor, In response to the location information of the MCPTT device, a call request message is received from the MCPTT server, and Based on receiving the above call request message, display an object using the display indicating whether to establish a call connection to the MCPTT calling device. causing the above MCPTT device, MCPTT device.

8. In paragraph 7, The above instructions, when individually or collectively executed by the at least one processor, By obtaining a user input for establishing the call connection to the MCPTT calling device through the object, by sending a call response message to the MCPTT server, to establish the call connection with the MCPTT calling device, causing the above MCPTT device, MCPTT device.

9. In paragraph 8, The above instructions, when individually or collectively executed by the at least one processor, Based on establishing the call connection with the MCPTT call device, display the ongoing state of the call connection for the MCPTT call device using the display. causing the above MCPTT device, MCPTT device.

10. In paragraph 6, A message indicating the activation of the above event includes a unique identifier of the event and information about the zone associated with the event. MCPTT device.

11. In a method performed by a MCPTT (mission critical push to talk) server, An action of receiving a call request message containing information about a zone from an MCPTT calling device; An operation of monitoring whether location information of at least one MCPTT device is received in the zone indicated by the call request message of the MCPTT calling device; In the above zone, in response to receiving location information of the MCPTT device, an action of transmitting a call request message of the MCPTT server to the MCPTT device; In response to the call request message of the MCPTT server, the operation of receiving a call response message from the MCPTT device; and Including an operation of establishing a call connection between the MCPTT calling device and the MCPTT device by transmitting a call response message of the MCPTT server to the MCPTT calling device in response to the call request message of the MCPTT calling device. method.

12. In paragraph 11, In response to receiving the call request message of the MCPTT calling device, an action of activating an event for monitoring location information of the at least one MCPTT device; In response to activating the event, transmitting a message including a unique identifier of the event and information about the zone to MCPTT devices in the network associated with the MCPTT server; and In response to the above message, further comprising an action of receiving location information of the MCPTT devices from the MCPTT devices. method.

13. In paragraph 12, An operation of identifying whether the MCPTT devices are located in the zone based on the location information of the MCPTT devices; An operation of transmitting call request messages to at least one MCPTT device based on identification that at least one MCPTT device among the MCPTT devices is located in the zone; An operation of receiving the call response message of the MCPTT device from the MCPTT device among the at least one MCPTT device; and Further comprising an action of disabling the event based on receiving the call response message of the MCPTT device. method.

14. In paragraph 11, After an event for monitoring location information of at least one MCPTT device is activated, an operation of receiving a call request message including a unique identifier of the event from another MCPTT calling device; and After the call connection between the MCPTT calling device and the MCPTT device is established, the method further includes transmitting a call invitation message to the other MCPTT calling device. method.

15. In paragraph 11, The call request message of the above MCPTT calling device does not indicate the target recipient. method.

Images