Method and system for sharing location information in remote peripheral calls

Abstract

The method includes: determining that a remote peripheral call is established between the MCPTT first electronic device 100 and the MCPTT second electronic device 200; transmitting a floor grant message to the MCPTT second electronic device 200, the floor grant message including a mandatory acknowledgement request indication set for the MCPTT second electronic device 200 by the MCPTT server 300 to share location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100; and receiving a floor grant acknowledgement message having location information of the MCPTT second electronic device 200; and using the floor take message by the MCPTT server 300 to share location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100 in the remote peripheral call of the MCPTT service.

Description

Technical Field

[0001] The present disclosure relates to wireless communication, and more specifically, to a method and system for sharing location information in a remote ambient call of a Mission-Critical Push-To-Talk (MCPTT) service.

Background Art

[0002] After the deployment of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) communication system or pre-5G communication system to meet the increasing demand for wireless data traffic. The 5G communication system or the pre-5G communication system is also referred to as a "beyond 4G network" or a "post long term evolution system". The 5G communication system is expected to be implemented in a higher frequency (mmWave) band, for example, the 60 GHz band, in order to achieve even faster data speeds. In order to reduce radio wave loss and increase the transmission distance, techniques such as beamforming, massive MIMO (Multiple-Input Multiple-Output), FD-MIMO (Full Dimensional MIMO), array antennas, analog beamforming and massive antennas are being discussed for the 5G communication system. Also, in the 5G communication system, development for system network improvement is underway based on next-generation small cells, cloud RAN (Radio Access Network), ultra-dense networks, D2D (Device-to-Device) communication, wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), receiver interference cancellation, etc. In the 5G system, hybrid FSK (Frequency Shift Keying), FQAM (Feher's Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding) have been developed as ACM (Advanced Coding Modulation), and FBMC (Filter Bank Multi Carrier), NOMA (Non-Orthogonal Multiple Access) and SCMA (Sparse Code Multiple Access) have been developed as advanced access technologies.

[0003] The Internet, a human-centered connectivity network where people generate and consume information, is evolving into the Internet of Things (IoT), where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, which is a combination of IoT technology via connection to cloud servers and big data processing technology. Technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology" are required for the implementation of IoT. Therefore, sensor networks, M2M (Machine-to-Machine) communication, MTC (Machine Type Communication), etc. have been recently studied. Such an IoT environment can provide intelligent Internet technology services that create new value for people's lives by collecting and analyzing data generated among connected things. The IoT is also applied to various fields including smart homes, smart buildings, smart cities, smart cars or connected vehicles, smart grids, healthcare, smart home appliances, and next-generation medical services through the convergence and combination of existing information technology (IT) and various industrial applications.

[0004] Accordingly, various attempts have been made to apply the 5G communication system to the IoT network. For example, technologies such as sensor networks, MTC, and M2M communication are also implemented by beamforming, MIMO, and array antennas. The aforementioned application of cloud RAN as big data processing technology can also be regarded as an example of the convergence of 5G technology and IoT technology.

[0005] As described above, various services are also provided by the development of wireless communication systems. Therefore, a method for easily providing such services is required.

[0006] Due to the continuous growth and development in the telecommunications industry, ambient listening calls have gained considerable popularity today. Such ambient listening calls are initiated either by an authorized MCPTT (Mission-Critical Push-To-Talk) user who desires to be listened to by other authorized MCPTT users or by an authorized MCPTT user who desires to listen to other MCPTT users. Further, in such ambient listening calls, the role of the MCPTT client / user is one of the following: i. Listening MCPTT user: In an ambient listening call, an MCPTT user who receives media transmissions from the listened-to MCPTT user, or ii. Speaking MCPTT user: An MCPTT user who is speaking in an ambient listening call may or may not be aware that they are being spoken.

[0007] Furthermore, the type of such ambient listening call is from the perspective of the relationship of the initiator of the ambient listening call to the speaking MCPTT user, and the two types of such ambient listening calls are as follows: i. Remote-init (remote ambient call): Indicating that the listening MCPTT user initiated the call, and ii. Local-init (local ambient call): Indicating that the speaking MCPTT user initiated the call.

[0008] Such ambient listening calls usually involve the participants talking among themselves when the speaking MCPTT user is not able to know that a call is in progress. In one example, remote call infrastructure communication and ambient call infrastructure communication are also used in the case of mission-critical services / MCPTT services (institutions that provide public safety services, i.e., police services, fire services, and ambulance services, etc.).

[0009] As specified in 3GPP (registered trademark) TS 23.379 V17.1.0, the MCPTT service provides location information related to the currently speaking user to all receiving MCPTT users. In the case of a remote perimeter call, there is no procedure defined in the existing methods to share the location information of the transmitting MCPTT user with the receiving MCPTT user. FIG. 1 is a sequence diagram illustrating an existing method for initiating a remote perimeter call in the MCPTT service according to an embodiment as disclosed in the present application.

[0010] The specific preconditions in the existing method for initiating a remote perimeter call in the MCPTT service are given as follows: i. The MCPTT client-1 10 is a client of an authorized user authorized to call a remotely initiated perimeter listening call to be set up in the requested MCPTT client-2 20. ii. The MCPTT client-1 10 is the "receiving MCPTT user", and the MCPTT client-2 20 is the "transmitting MCPTT user (speaker)".

[0011] In step S101, the MCPTT client-1 10 initiates a remotely initiated perimeter listening call (i.e., a remote perimeter call) by transmitting a perimeter listening call request to the MCPTT server 30. The type of remotely initiated perimeter listening call is included in the perimeter listening call request. In step S102, the MCPTT server 30 performs an authorization check related to the MCPTT client-1 10 for the remotely initiated perimeter listening call. If the authorization fails, the MCPTT server 30 provides a failure response to the MCPTT client-1 10. In step S103, the MCPTT server 30 transmits the perimeter listening call request to the MCPTT client-2 20.

[0012] In step S104, the MCPTT client-2 20 returns a peripheral eavesdropping call response to the MCPTT server 30. In step S105, the MCPTT server 30 provides the peripheral eavesdropping call response to the MCPTT client-1 10, indicating whether the call is successfully set up together with the location information received from the MCPTT client-2 20. In step S106, the floor control server of the MCPTT server 30 transmits the message floor-granted according to the peripheral eavesdropping type received in step S101 to the MCPTT client-2 20. In step S107, the floor control server of the MCPTT server 30 transmits floor taken to the MCPTT client-1 10. In steps S108 - S109, after receiving the floor-granted message in the MCPTT client-2 20, the media is transmitted from the MCPTT client-2 20 to the MCPTT client-1 10.

[0013] Furthermore, in the existing system, in a remote peripheral call, there is no standard method to share the location information of the speaking MCPTT user with the receiving MCPTT user. Different MCPTT service providers provide their own mechanisms to share the location information of the speaking MCPTT user who received the remote peripheral call. As a result, if all MCPTT service providers have their own embodiments / procedures, it is difficult to achieve a standardized single procedure, which causes interoperability problems. Therefore, at least, it is desired to provide a useful alternative for sharing the location information of the speaking MCPTT user with the receiving MCPTT user in a remote peripheral call.

SUMMARY OF THE INVENTION

MEANS FOR SOLVING THE PROBLEM

[0014] The main objective of the embodiments of the present disclosure is to provide a method for sharing location information in remote perimeter calls of the MCPTT service by providing a standard procedure for sharing the location information of a transmitting MCPTT (Mission-Critical Push-To-Talk) user with a receiving MCPTT user in remote perimeter calls. The standard procedure for sharing the location information eliminates interoperability issues among different MCPTT service providers.

[0015] Another objective of the embodiments of the present disclosure is to add a confirmation response request instruction to the floor grant message. Thereby, the transmitting MCPTT user can share location information with the receiving MCPTT user in remote perimeter calls.

[0016] Another objective of the embodiments of the present disclosure is to add a location field including the location information of the transmitting MCPTT user (the user granted the floor) to the floor grant confirmation response message. The location field may be omitted when the location information of the transmitting MCPTT user is not permitted by the MCPTT profile of the transmitting MCPTT user, or alternatively, may include a location field set to "0".

[0017] Another objective of the embodiments of the present disclosure is to add a location field including the location information of the transmitting MCPTT user (for example, the floor is granted to the user) to the call control confirmation response message for a pre-established session-based perimeter listening call. The location field may be omitted when the location information of the transmitting MCPTT user is not permitted by the MCPTT profile of the transmitting MCPTT user, or alternatively, may include a location field set to "0".

[0018] Accordingly, embodiments of the present disclosure provide a method for sharing location information in a remote peripheral call of an MCPTT service. The method includes a step determined by the MCPTT server 300 when a remote peripheral call is established between an MCPTT first electronic device and an MCPTT second electronic device. Further, the method includes a step of transmitting, by the MCPTT server, a floor grant message having a mandatory confirmation response request instruction set for the MCPTT second electronic device to share the location information of the MCPTT second electronic device with the MCPTT first electronic device. Further, the method includes a step of receiving, by the MCPTT server, a floor grant confirmation response message having the location information of the MCPTT second electronic device. Further, the method includes a step of sharing, by the MCPTT server, the location information of the MCPTT second electronic device with the MCPTT first electronic device in a floor taken message.

[0019] In one embodiment, the method further includes a step of receiving, by the server, a media transmission from the MCPTT second electronic device. Further, the method includes a step of transmitting, by the server, the media transmission to the MCPTT first electronic device.

[0020] In one embodiment, the method includes a step of receiving, by the MCPTT server, a remote peripheral listening call request from the MCPTT first electronic device to initiate a remote start peripheral listening call. Further, the method includes a step determined by the MCPTT server whether the authentication of the user of the MCPTT first electronic device for the remote start peripheral listening call is successful. Further, the method includes a step of transmitting a failure response to the MCPTT first electronic device in response to determining that the authentication of the user of the MCPTT first electronic device for the remote start peripheral listening call is not successful. Further, the method includes a step of transmitting the remote peripheral listening call request to the MCPTT second electronic device to establish a remote peripheral call between the MCPTT first electronic device and the MCPTT second electronic device.

[0021] In one embodiment, the floor grant message includes at least one of a timer value that the MCPTT second electronic device is permitted to transmit in the duration field, a synchronization source (SSRC) of the granted floor participant field, a granted priority level in the floor priority field, a track information field, and a floor indicator field. The first bit in the subtype of the floor grant message is set to 1 when the call is a remote start perimeter listening call.

[0022] In one embodiment, the track information field includes a path through which the floor control message is routed along with the priority and queuing ability of the MCPTT client, and is included when the MCPTT call involves non-controller ability.

[0023] In one embodiment, the floor indicator field includes additional information related to the received floor control message.

[0024] In one embodiment, when the floor grant message is originated for the MCPTT second electronic device with the floor granted, the MCPTT server starts the floor granted timer and sets the floor granted counter value to 1.

[0025] In one embodiment, after receiving the location information in the floor confirmation response message from the MCPTT second electronic device, the MCPTT server transmits a floor takeover message to the MCPTT first electronic device together with the location information of the MCPTT second electronic device.

[0026] In one embodiment, the MCPTT server starts the expiration of the RTP media timer related to the MCPTT second electronic device with the floor granted and sets the general state to the floor takeover state.

[0027] In one embodiment, the floor grant confirmation response message includes at least one of a source field, a message type field, a track information field, and a location field.

[0028] In one embodiment, the message type field is set to 1, the source field is set to 0, when the call is a remote start perimeter listening call, the location information of the MCPTT second electronic device is added to the location field, and the MCPTT profile of the MCPTT second electronic device allows the MCPTT first electronic device to transmit the location information of the MCPTT second electronic device. Here, the first bit in the subtype of the floor grant message is set to 1.

[0029] In one embodiment, the method includes receiving, by the MCPTT second electronic device, a floor grant message from the MCPTT server. Further, the method includes transmitting, by the MCPTT second electronic device, a floor grant confirmation response message having the location information of the MCPTT second electronic device to the MCPTT server. Further, the method includes providing, by the MCPTT second electronic device, a floor grant notification. Further, the method includes performing, by the MCPTT second electronic device, the end of the RTP media timer and the end of the floor grant timer.

[0030] In one embodiment, the method includes receiving, by an MCPTT server, a remote peripheral listening call request from an MCPTT first electronic device to initiate a remote start peripheral listening call. Further, the method includes determining, by the MCPTT server, that authentication of a user of the MCPTT first electronic device for the remote start peripheral listening call has been successful. Further, the method includes transmitting, by the MCPTT server, the remote peripheral listening call request to an MCPTT second electronic device to establish a remote peripheral call between the MCPTT first electronic device and the MCPTT second electronic device. Further, the method includes receiving, by the MCPTT server, the location information of the MCPTT second electronic device in a connection confirmation response message from the MCPTT second electronic device, where the location information is a field added to the connection confirmation response message. Further, the method includes sharing, by the MCPTT server, the location information of the MCPTT second electronic device with the MCPTT first electronic device.

[0031] Accordingly, an embodiment in the present disclosure provides an MCPTT server that shares location information in a remote peripheral call of an MCPTT service. The MCPTT server includes a floor control unit coupled to a processor and a memory. The floor control unit is configured to determine that a remote peripheral call has been established between an MCPTT first electronic device and an MCPTT second electronic device. Further, the floor control unit is configured to transmit a floor grant message having a mandatory confirmation response request instruction set for the MCPTT second electronic device to share the location information of the MCPTT second electronic device with the MCPTT first electronic device. Further, the floor control unit is configured to receive a floor grant confirmation response message having the location information of the MCPTT second electronic device. Further, the floor control unit is configured to use a floor take message to share the location information of the MCPTT second electronic device with the MCPTT first electronic device in a remote peripheral call of the MCPTT service.

[0032] Accordingly, embodiments in the present disclosure provide an MCPTT second electronic device for sharing location information in a remote peripheral call of an MCPTT service. The MCPTT second electronic device includes a floor control unit coupled to a processor and a memory. The floor control unit is configured to receive a floor grant message from an MCPTT server. Further, the floor control unit sets the message type field of a set of floor confirmation response messages (i.e., floor grant confirmation response messages) to 1, sets the source field of the set of floor confirmation response messages to 0, and is configured to add a location field to the floor confirmation response message when the call is a remote start peripheral listening call. The MCPTT profile of the MCPTT second electronic device is allowed to transmit the location information of the MCPTT second electronic device with the MCPTT first electronic device when the first bit in the subtype of the received floor grant message is set to 1. Further, the floor control unit is configured to transmit the floor confirmation response message to the MCPTT server. Further, the floor control unit is configured to perform the end of the RTP media timer and the end of the floor granted timer.

[0033] Embodiments of the present disclosure will be more preferably recognized and understood when considered in connection with the following description and the accompanying drawings. However, it should be understood that the following description is given by way of example and not limitation, while showing preferred embodiments and numerous specific details thereof. Many changes and modifications may be made within the scope of the embodiments in the present disclosure, and the embodiments in the present disclosure include all such modifications.

[0034] The present disclosure is illustrated in the accompanying drawings, and throughout the drawings, like reference numerals indicate corresponding parts in the various drawings. Embodiments of the present disclosure are better understood from the following description with reference to the drawings.

Brief Description of the Drawings

[0035]

Figure 1

Figure 2A

Figure 2B

Figure 3

Figure 4

Figure 5

Figure 6

[0036] The following description after referring to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. Although various specific details are included for the purpose of assisting such understanding, these details should be regarded as merely exemplary. Thus, those skilled in the art will recognize that various changes and modifications to the various embodiments described in the present disclosure can be made without departing from the scope and spirit of the present disclosure. Furthermore, descriptions of widely known functions and configurations are omitted for the sake of clarity and brevity.

[0037] The terms and words used in the following description and claims are not limited to their bibliographical meanings, but are used only by the inventors to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of the various embodiments of the present disclosure is provided for illustrative purposes only and is not intended to limit the present disclosure as defined by the appended claims and their equivalents.

[0038] The singular forms corresponding to the use of "a", "an" and "the" are to be understood to include plural references unless clearly indicated otherwise. Thus, for example, references to "component surface" include references to one or more such surfaces.

[0039] During the description of this embodiment, technical content that is widely known in the relevant technical field and not directly related to the present disclosure is not provided. By omitting redundant descriptions, the essence of the present disclosure will not be made unclear and will be clearly explained.

[0040] For the same reason, components may also be exaggerated, omitted, or schematically illustrated in the drawings for clarity. Also, the size of each component does not fully reflect the actual size. In the drawings, like reference numerals indicate like elements.

[0041] As used in the present disclosure, the term "and / or" includes any one or more of the related listed items, and all combinations. Expressions such as "at least one of" do not modify the entire list of elements when preceding the list of elements, but rather modify the individual elements of that list. Throughout the present disclosure, the expression "at least one of a, b or c" indicates only a, only b, only c, either a and b, either a and c, either b and c, any of a, b and c, or variations thereof.

[0042] The advantages, features, and methods for achieving them of one or more embodiments of the present disclosure will be more readily understood by referring to the following detailed description of the embodiments and the accompanying drawings. In connection therewith, the embodiments can have different forms and are not to be construed as limited to the descriptions referred to in the present disclosure. Instead, those embodiments are provided so that the present disclosure will be thorough and complete and will fully convey the concept of the embodiments to those skilled in the art, and the present disclosure is defined only by the appended claims.

[0043] Here, it will be understood that the combinations of blocks in a flowchart or process flowchart can be carried out by computer program instructions. Since those computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, the instructions executed by the processor of the computer, or other programmable data processing apparatus, generate units that perform the functions described by the flowchart blocks. The computer program instructions can also be stored in a memory that is usable by or readable by a computer, which can direct the computer, or other programmable data processing apparatus, to implement functions in a particular manner. Thus, the instructions stored in the memory that is usable by or readable by the computer can also generate a manufactured item that includes instruction units for performing the functions described by the flowchart blocks. The computer program instruction words can also be loaded into a computer, or other programmable data processing apparatus, and thus, when a series of operations are performed on a computer, or other programmable data processing apparatus, the instruction words for operating the computer, or other programmable data processing apparatus, by generating a computer-executable process can provide operations for performing the functions described by the flowchart blocks.

[0044] Also, each block can represent a portion, segment, or code of a module that includes one or more executable instruction words for performing a specified logical function. It should also be noted that in some embodiments, the functions referred to by the blocks can occur non-sequentially. For example, two blocks illustrated in succession can actually be executed substantially in parallel, or the blocks can be executed in reverse order at various times, depending on the corresponding functions.

[0045] Here, the term "unit" in the embodiments of the present disclosure means a software component or a hardware component such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and performs a specific function. However, the term "unit" is not limited to software or hardware. The "unit" is formed to be in an addressable recording medium or is also formed to operate one or more processors. Therefore, for example, the term "unit" can refer to components such as software components, object-oriented software components, class components, and task components, and also includes processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided by the components and the "unit" are further combined with fewer components and "units" or are also divided into additional components and "units". Further, the components and the "unit" are also implemented to reproduce one or more central processing units (CPUs) in a device or a security multimedia card. Also, in this embodiment, the "unit" also includes at least one processor. In the present disclosure, the controller is also referred to as a processor.

[0046] Since a wireless communication system provides an initial voice-oriented service, for example, it has evolved to broadband wireless communication systems that provide high-speed and high-quality packet data services, namely, 3GPP's HSPA (High Speed Packet Access), LTE (Long-Term Evolution) or E-UTRA (evolved universal terrestrial radio access) and LTE-A (LTE-advanced); 3GPP2's HRPD (High Rate Packet Data) and UMB (Ultra Mobile Broadband); and the communication standard of IEEE 802.16e. The 5th generation (5G) communication standard or NR (New Radio) communication standard is being developed with a 5G wireless communication system.

[0047] Hereinafter, one or more embodiments will be described with reference to the accompanying drawings. Also, in the description of the present disclosure, specific detailed descriptions of related functions or configurations may be omitted if they are considered to make the essence of the present disclosure unnecessarily unclear. All terms, including narrative or technical terms used in the present disclosure, should be construed to have a meaning obvious to those skilled in the art of this technology. However, the terms may have different meanings due to the intention of those skilled in the art of this technology, precedent, or the emergence of new technologies. Therefore, the terms used in the present disclosure should be defined based on the meaning of the terms together with the description throughout the specification. Hereinafter, the base station is the entity that performs resource allocation for the terminal and is at least one of gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, and node on the network. The terminal includes a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In the present disclosure, DL is the radio transmission path of the signal transmitted from the base station to the terminal, and UL is the radio transmission path of the signal transmitted from the terminal to the base station. Throughout this specification, a layer (or a layered device) is also referred to as an entity. Also, hereinafter, one or more embodiments of the present disclosure will be described as an example of an LTE system or an LTE-A system, but one or more embodiments are also applicable to other communication systems having a similar technical background or channel form. For example, it includes 5G mobile communication technology (5G, New Radio (NR)) developed after the LTE-A. Furthermore, one or more embodiments are also applicable to other communication systems through partial modifications within the scope of the present disclosure without departing from the scope of the present disclosure by those skilled in the art of this technology.

[0048] In an LTE system, which is a typical example of a broadband wireless communication system, an orthogonal frequency division multiplexing (OFDM) scheme is used in the DL, and a single carrier frequency division multiple access (SC-FDMA) scheme is used in the UL. The UL refers to a radio link through which a terminal, UE, or MS transmits data or control signals to a BS or gNode B, and the DL refers to a radio link through which a BS transmits data or control signals to a terminal. In such a large number of access schemes, data or control information of each user is generally classified by allocating and operating data or control information so that time-frequency resources for transmitting data or control information related to each user do not overlap with each other, that is, orthogonality is established.

[0049] Terms such as physical channels and signals in existing LTE systems or LTE-A systems are also used in the description of the methods and apparatuses proposed in this disclosure. However, the content of this disclosure is applicable to wireless communication systems instead of LTE systems or LTE-A systems.

[0050] Embodiments in the present disclosure, as well as their various features and advantageous details, are illustrated in the accompanying drawings and will be further described in detail with reference to non-limiting embodiments that will become detailed in the following description. Descriptions of widely known components and processing techniques are omitted so as not to make the embodiments of the present disclosure unnecessarily unclear. Also, the various embodiments described in the present disclosure are not necessarily mutually exclusive, but some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein refers to non-exclusive unless otherwise indicated. The examples used in the present disclosure are merely for facilitating the understanding of how the embodiments of the present disclosure can be implemented and for further enabling those skilled in the art to implement the embodiments of the present disclosure. Therefore, the examples are not to be construed as limiting the scope of the embodiments of the present disclosure.

[0051] As is common in the art, the present embodiment may be described and illustrated in terms of the functions described, or aspects of the blocks that perform the functions. These blocks may also be referred to herein as managers, units, modules, hardware components, etc., and are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, and hard-wired circuits, and may optionally be driven by firmware. The circuits are implemented, for example, within one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuits that make up the blocks are also implemented by dedicated hardware, by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware that performs some of the functions of the block and a processor that performs the other functions of the block. Each block of the present embodiment can be physically separated into two or more interacting and individual blocks without departing from the scope of the present disclosure. Similarly, the blocks of the present embodiment can be physically combined into even more complex blocks without departing from the scope of the present disclosure.

[0052] It should be understood that the accompanying drawings are used to facilitate the understanding of various technical features and that the embodiments presented in the present disclosure are not limited by the accompanying drawings. Thus, the present disclosure should be construed as extending to any modifications, equivalents, and substitutions other than those presented in the accompanying drawings. Even though terms such as first, second, etc. may be used in the present disclosure to describe various elements, those elements are not limited by those terms. Those terms are generally used only to distinguish one element from another.

[0053] For the purposes of this document, the terms and definitions are given in 3GPP TR 21.905, and the following applies. If the terms defined in this document are in 3GPP TR 21.905, they take precedence over the definitions of the same terms.

[0054] Accordingly, embodiments of the present disclosure provide a method for sharing location information in a remote ambient call of a Mission-Critical Push-To-Talk (MCPTT) service. The method includes a step determined by an MCPTT server when a remote ambient call is established between an MCPTT first electronic device and an MCPTT second electronic device. Further, the method includes a step of transmitting, by the MCPTT server, a floor grant message having a mandatory confirmation response request instruction set for the MCPTT second electronic device to share the location information of the MCPTT second electronic device with the MCPTT first electronic device. Further, the method includes a step of receiving, by the MCPTT server, a floor confirmation response message having the location information of the MCPTT second electronic device. Further, the method includes a step of sharing, by the MCPTT server, the location information of the MCPTT second electronic device with the MCPTT first electronic device in a remote ambient call of the MCPTT service using a floor taken message.

[0055] Accordingly, embodiments in the present disclosure provide an MCPTT server that shares location information in a remote peripheral call of an MCPTT service. The MCPTT server includes a floor control unit coupled to a processor and a memory. The floor control unit is configured to determine that a remote peripheral call is established between an MCPTT first electronic device and an MCPTT second electronic device. Further, the floor control unit is configured to transmit a floor grant message having a mandatory confirmation response request instruction set for the MCPTT second electronic device to share the location information of the MCPTT second electronic device with the MCPTT first electronic device. Further, the floor control unit is configured to receive a floor confirmation response message having the location information of the MCPTT second electronic device. Further, the floor control unit is configured to use a floor take message to share the location information of the MCPTT second electronic device with the MCPTT first electronic device in a remote peripheral call of the MCPTT service.

[0056] Therefore, an embodiment of the present disclosure provides an MCPTT second electronic device for sharing location information in a remote peripheral call of an MCPTT service. The MCPTT second electronic device includes a floor controller coupled to a processor and a memory. The floor controller is configured to receive a floor grant message from an MCPTT server. The floor controller is further configured to set a message type field of a floor acknowledgement message set to 1, set a source field of the floor acknowledgement message set to 0, and add a location field to the floor acknowledgement message when the call is a remotely initiated ambient listening call, and an MCPTT profile of the MCPTT second electronic device is allowed to transmit the location information of the MCPTT second electronic device with the MCPTT first electronic device when a first bit in the subtype of the received floor grant message is set to 1. The floor controller is further configured to transmit the floor acknowledgement message to the MCPTT server. The floor controller is further configured to terminate an RTP media timer and terminate a floor granted timer.

[0057] Unlike existing methods and systems, the proposed method provides a standard procedure for a listening MCPTT user (i.e., MCPTT first electronic device) to share location information of a listened-to MCPTT user (i.e., MCPTT second electronic device) in a remote peripheral call to eliminate interoperability issues between different MCPTT service providers.

[0058] Different from existing methods and systems, the proposed method allows the MCPTT server to add an acknowledgement request indication to the floor grant message, so that the calling MCPTT user can share location information with the called MCPTT user in a remote peripheral call.

[0059] Unlike existing methods and systems, the proposed method allows the MCPTT second electronic device to add a location field to the floor confirmation response message, and the location field includes the location information of the speaking MCPTT user (the user granted the floor). The location field is omitted or, alternatively, includes a location field (not provided) set to "0" when the location information of the speaking MCPTT user is not permitted by the MCPTT profile of the speaking MCPTT user.

[0060] Next, referring to the drawings, and more particularly to FIGS. 2A through 4, which show corresponding features with like reference numerals consistent throughout the drawings, the preferred embodiments are illustrated.

[0061] FIG. 2A is a block diagram of an MCPTT server 300 for sharing location information in a remote peripheral call of an MCPTT service according to one embodiment as disclosed herein. In one embodiment, the MCPTT server 300 is coupled to an MCPTT first electronic device 100 and an MCPTT second electronic device 200. In one embodiment, the MCPTT server 300 includes a memory 310, a processor 320, a communication unit 330, and a floor control unit 340.

[0062] Memory 310 stores the mandatory confirmation response request instruction and the location information of the MCPTT second electronic device 200. Further, memory 310 stores the instruction words executed by processor 320. Memory 310 also includes a non-volatile storage element. Examples of such non-volatile storage elements include magnetic hard disks, optical disks, floppy disks, flash memories, or those in the form of EPROM (Erasable Programmable Read Only Memory) or EEPROM (Electrically Erasable and Programmable Memory). Further, in some embodiments, memory 310 can also be regarded as a non-transitory recording medium. The term "non-transitory" can indicate that the recording medium is not embodied by a carrier wave or a propagated signal. However, the term "non-transitory" is not to be construed as meaning that memory 310 is non-mobile. In some examples, memory 310 is also configured to store a greater amount of information than memory 310. In a particular example, the non-transitory recording medium can store data that can change over time (e.g., in RAM (Random Access Memory) or a cache). In one embodiment, memory 310 is either an internal storage unit or it is an external storage unit of the MCPTT server 300, cloud storage, or any other type of external storage.

[0063] The processor 320 communicates with the memory 310, the communication unit 330, and the floor control unit 340. The processor 320 includes one or more processors, such as a general-purpose processor, i.e., a central processing unit (CPU), an application processor (AP), etc.; a dedicated graphics processing unit, i.e., a graphics processing unit (GPU), a visual processing unit (VPU); and / or a dedicated artificial intelligence (AI) processor, i.e., a neural processing unit (NPU).

[0064] The communication unit 330 is configured to communicate internally among internal hardware components and with external devices (e.g., the MCPTT first electronic device 100 and the MCPTT second electronic device 200) via one or more networks. The communication unit 330 includes specific electronic circuits for enabling wired or wireless communication according to a standard.

[0065] In one embodiment, the floor control unit 340 is implemented by a processing circuit such as a logic gate, an integrated circuit, a microprocessor, a microcontroller, a memory circuit, a passive electronic component, an active electronic component, an optical component, a hard-wired circuit, and can be optionally driven by firmware. The circuit can be implemented, for example, within one or more semiconductor chips or on a substrate support such as a printed circuit board.

[0066] In one embodiment, the floor control unit 340 receives a remote perimeter listening call request to start a remote perimeter listening call from the MCPTT first electronic device 100. Further, the floor control unit 340 determines whether the authentication of the user of the MCPTT first electronic device 100 for the remote start perimeter listening call is successful. Further, the floor control unit 340 transmits a failure response to the MCPTT first electronic device 100 as a response to determining that the authentication of the user of the MCPTT first electronic device 100 for the remote start perimeter listening call is not successful. Further, the floor control unit 340 transmits the remote perimeter listening call request to the MCPTT second electronic device 200 to establish a remote perimeter call between the MCPTT first electronic device 100 and the MCPTT second electronic device 200. Further, the floor control unit 340 receives a perimeter listening call response from the MCPTT second electronic device 200. Further, the floor control unit 340 transmits the received perimeter listening call response to the MCPTT first electronic device 100 and indicates whether the call has been successfully set up (whether the remote perimeter call has been established between the MCPTT first electronic device 100 and the MCPTT second electronic device 200).

[0067] Further, the floor control unit 340 transmits a floor grant message having a mandatory confirmation response request instruction setting for the MCPTT second electronic device 200 to share the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100. Further, the floor control unit 340 receives a floor confirmation response message having the location information of the MCPTT second electronic device 200. Further, the floor control unit 340 uses the floor take message to share the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100 in the remote perimeter call of the MCPTT service. Further, the floor control unit 340 receives a media transmission from the MCPTT second electronic device 200. Further, the floor control unit 340 transmits the received media transmission to the MCPTT first electronic device 100. Further details are described in FIG. 3.

[0068] Furthermore, the floor control unit 340 receives a remote peripheral listening call request to start a remote start peripheral listening call from the MCPTT first electronic device 100. Furthermore, the floor control unit 340 determines that the authentication of the user of the MCPTT first electronic device 100 for the remote start peripheral listening call is successful. Furthermore, the floor control unit 340 transmits the remote peripheral listening call request to the MCPTT second electronic device 200 in order to establish a remote peripheral call between the MCPTT first electronic device 100 and the MCPTT second electronic device 200. Furthermore, the floor control unit 340 receives the location information of the MCPTT second electronic device 200 in the connection confirmation response message from the MCPTT second electronic device 200, and the location is a field added to the connection confirmation response message. Furthermore, the floor control unit 340 shares the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100.

[0069] It should be understood that even though FIG. 2A illustrates various hardware elements of the MCPTT 300, other embodiments are not limited thereto. In other embodiments, the MCPTT server 300 may include fewer or more components. Furthermore, the labels or names of the components are used for illustrative purposes only and do not limit the scope of the invention. One or more components may be coupled together to perform the same or substantially similar functions in order to share location information in a remote peripheral call of the MCPTT service.

[0070] FIG. 2B is a block diagram of the MCPTT second electronic device 200 for sharing location information in a remote peripheral call of the MCPTT service according to an embodiment as disclosed in the present application. The MCPTT second electronic device 200 and the MCPTT first electronic device 100 are, for example, smartphones, wearable devices, IoT devices, but are not limited thereto.

[0071] In one embodiment, the MCPTT second electronic device 200 includes a memory 210, a processor 220, a communication unit 230, and a floor control unit 240.

[0072] The memory 210 stores the mandatory confirmation response request instruction received from the MCPTT server 300 and the location information of the MCPTT second electronic device 200. Further, the memory 210 stores instruction words to be executed by the processor 220. The memory 210 also includes a non-volatile storage element. Examples of such non-volatile storage elements include magnetic hard disks, optical disks, floppy disks, flash memories, or those in the form of EPROM or EEPROM. Furthermore, the memory 210 is also regarded as a non-transitory recording medium in some embodiments. The term "non-transitory" can indicate that the recording medium is not embodied by a carrier wave or a propagated signal. However, the term "non-transitory" is not interpreted to mean that the memory 210 is non-mobile. In some examples, the memory 210 is also configured to store a larger amount of information than the memory 210. In a specific example, the non-transitory recording medium can store data that can change over time (e.g., in RAM or cache). In one embodiment, the memory 210 is either an internal storage unit or it can be an external storage unit of the MCPTT second electronic device 200, cloud storage, or any other type of external storage.

[0073] The processor 220 communicates with the memory 210, the communication unit 230, and the floor control unit 240. The processor 220 can include one or more processors, such as a general-purpose processor, say, a central processing unit (CPU), an application processor (AP), etc.; a graphics dedicated processing unit, say, a graphics processing unit (GPU), a vision processing unit (VPU); and / or an artificial intelligence (AI) dedicated processor, say, a neural processing unit (NPU).

[0074] The communication unit 230 is configured to communicate internally between internal hardware components and with external devices (e.g., the MCPTT first electronic device 100 and the MCPTT server 300) via one or more networks. The communication unit 230 includes specific electronic circuits for enabling wired or wireless communication against a standard.

[0075] In one embodiment, the floor control unit 240 is implemented by a processing circuit such as a logic gate, an integrated circuit, a microprocessor, a microcontroller, a memory circuit, a passive electronic component, an active electronic component, an optical component, a hardwired circuit, and can be optionally driven by firmware. The circuit can be implemented, for example, within one or more semiconductor chips or on a substrate support such as a printed circuit board.

[0076] In one embodiment, upon successful authentication of the MCPTT first electronic device 100 at the MCPTT server 300, the floor control unit 240 receives a peripheral eavesdropping call request from the MCPTT server 300. Further, the floor control unit 240 transmits a peripheral eavesdropping call response indicating whether the call is successfully set up to the MCPTT server 300. Further, the floor control unit 240 receives a floor grant message from the MCPTT server 300. Further, the floor control unit 240 determines whether the first bit in the subtype of the received floor grant message is set to 1. Further, when the first bit in the subtype of the received floor grant message is set to 1, the call is a remotely initiated peripheral eavesdropping call, and the MCPTT profile of the MCPTT second electronic device 200 is allowed to transmit the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100, the floor confirmation response message set sets the message type field to 1, sets the source field of the floor confirmation response message set to 0, and adds a location field to the floor confirmation response message. Further details are described in FIG. 3.

[0077] It should be understood that even though FIG. 2B illustrates various hardware elements of the MCPTT second electronic device 200, other embodiments are not limited thereto. In other embodiments, the MCPTT second electronic device 200 may include fewer or more components. Further, the labels or names of the components are used for illustrative purposes only and do not limit the scope of the invention. One or more components may be coupled together to perform the same or substantially similar functions to share location information in a remote peripheral call of the MCPTT service.

[0078] FIG. 3 is a sequence diagram illustrating a method for sharing location information in a remote peripheral call of an MCPTT service according to one embodiment as disclosed in the present application.

[0079] Specific preconditions in the method for sharing location information in a remote peripheral call of the MCPTT service are given below. i. The MCPTT first electronic device 100 is a client of an authorized user authorized to call a remotely initiated peripheral listening call set up in the requested MCPTT second electronic device 200. ii. The MCPTT first electronic device 100 is the "receiving MCPTT user", and the MCPTT second electronic device 200 is the "transmitting MCPTT user (speaker)".

[0080] In step S301, the MCPTT first electronic device 100 starts a remotely initiated peripheral listening call (i.e., a remote peripheral call) by transmitting a peripheral listening call request to the MCPTT server 300. The remotely initiated peripheral listening call type is included in the peripheral listening call request. In step S302, the MCPTT server 300 performs an authorization check on the MCPTT first electronic device 100 regarding the remotely initiated peripheral listening call. If the authorization fails, the MCPTT server 300 provides a failure response to the MCPTT first electronic device 100. In step S303, the MCPTT server 300 transmits the peripheral listening call request to the MCPTT second electronic device 200. In step S304, the MCPTT second electronic device 200 returns a peripheral listening call response to the MCPTT server 300. In step S305, the MCPTT server 300 provides the MCPTT first electronic device 100 with a peripheral listening call response indicating whether the call is successfully set up.

[0081] In step S306, the floor control server of the MCPTT server 300 thereby transmits a message floor - granted according to the peripheral listening type received in step S301 to the MCPTT second electronic device 200. The floor - granted message includes an instruction to the MCPTT second electronic device 200 to transmit a floor confirmation response message for the received floor - granted message. In step S307, the MCPTT second electronic device 200 transmits a floor confirmation response message having the location information of the MCPTT second electronic device 200 to the floor control server of the MCPTT server 300. In step S308, the floor control server of the MCPTT server 300 transmits floor taking to the MCPTT first electronic device 100 together with the received location information of the MCPTT second electronic device 200. In steps S309 - S310, after the MCPTT second electronic device 200 receives the floor - granted message, media is transmitted from the MCPTT second electronic device 200 to the MCPTT first electronic device 100.

[0082] Figure 4 is a sequence diagram illustrating a method of adding a location field to a call control confirmation response message (connection confirmation response message) for pre - established session - based perimeter listening calls according to an embodiment as disclosed in the present application.

[0083] In the remote perimeter call of the MCPTT service, specific pre - conditions in the method of sharing location information are given below. i. The MCPTT first electronic device 100 is a client of an authorized user authorized to call a remote - start perimeter listening call set up in the requested MCPTT second electronic device 200. ii. The MCPTT first electronic device 100 is the "receiving MCPTT user", and the MCPTT second electronic device 200 is the "transmitting MCPTT user (speaker)".

[0084] In step S401, the MCPTT first electronic device 100 starts a remotely initiated ambient listening call by transmitting an ambient listening call request to the MCPTT server 300. The remotely initiated ambient listening call type is included. In step S402, the MCPTT server 300 performs an authorization check for the user (i.e., the MCPTT first electronic device 100) authorized for the remotely initiated ambient listening call. If the authorization fails, the MCPTT server 300 provides a failure response to the MCPTT first electronic device 100. In step S403, the MCPTT server 300 transmits the ambient listening call request to the MCPTT second electronic device 200. In step S404, the MCPTT second electronic device 200 returns an ambient listening call response including location information to the MCPTT server 300. In step S405, the MCPTT server 300 provides the MCPTT first electronic device 100 with an ambient listening call response indicating whether the call is successfully set up, together with the location information received from the MCPTT second electronic device 200. In step S406, the floor control server of the MCPTT server 300 then transmits the granted floor to the MCPTT second electronic device 200 according to the ambient listening type received in step S401. In step S407, the floor control server of the MCPTT server 300 transmits floor seizure to the MCPTT first electronic device 100. In steps S408 - S409, after receiving the floor - granted message in the MCPTT second electronic device 200, media is transmitted from the MCPTT second electronic device 200 to the MCPTT first electronic device 100.

[0085] In one embodiment, the following information elements and procedures are required to achieve the proposed solution.

[0086] Entry into the "G: Floor Seizure" state: The floor control arbitration logic in the floor control server of the MCPTT server 300 will be described below.

[0087] In one embodiment, the MCPTT server 300 transmits the floor-granted message to the floor participant to whom the floor is granted (i.e., the MCPTT second electronic device 200). The floor-granted message is: a. including the value of timer T2 (dialog interruption) in the duration field; b. including the granted priority in the floor priority field; c. including the saved track information field if a track information field related to the floor control server state transition diagram is saved for the "general floor control operation"; d. including a floor indicator field with appropriate instructions if the group call is a broadcast group call, a system call, an emergency call, an imminent danger call, or an ad-hoc group session; and e. If the call is a perimeter listening call and the perimeter listening call type is remote-initiated, set the first bit in the subtype of the floor-granted message to "1" (a confirmation response is required) as described in subsection 8.2.2 below. If the call is a perimeter listening call and the perimeter listening call type is remote-initiated, the floor participant to whom the floor is granted is the call-ending floor participant. Otherwise, the floor is granted to the participant who requested the floor.

[0088] In other embodiments, the MCPTT server 300 transmits the floor-taking message to all other floor participants. The floor-taking message: a. If the floor is currently granted to only one participant: i. If privacy is not requested, include the MCPTT ID of the granted MCPTT user (the ID of the MCPTT second electronic device 200) in the identity field of the granted party; and ii. If privacy is not requested, it also includes the functional alias of the granted MCPTT user in the functional alias field; b. If multiple speakers are supported and the floor is currently granted to a number of participants: i. Include a floor indicator field with an I-bit set to "1" (multiple speakers); ii. Include the newly granted speaker and include the list of granted users of the multi-speaker group in the list of granted user fields; iii. Include a list of SSRCs of the granted floor participants; and iv. The list of function aliases of the granted floor participants can be included in the list of function alias fields; c. Include a message sequence number field with the message sequence value incremented by 1. d. If the session is a broadcast group call or a peripheral listening call, include permission to request a floor field set to "0"; e. If the session is not a broadcast group call, it also includes permission to request a floor field set to "1"; and f. If the group call is a broadcast group call, a system call, an emergency call, an imminent danger call, or an ad-hoc group session, include a floor indicator field with appropriate instructions.

[0089] In other embodiments, the MCPTT server 300 starts a timer T1 (end of RTP media) for each participant to whom the floor is granted; In other embodiments, the MCPTT server 300 sets the general state to the "G: Floor Take" state; and In other embodiments, if the MCPTT server 300 is configured to support a multi-speaker floor control group, the MCPTT identity of the participant to whom the floor is granted is added to the list of currently granted speakers.

[0090] Receive a floor - granted message (R: floor - granted): When receiving a floor - granted message from the floor control server or a floor - granted instruction as an SIP 200 (OK) response in the application layer and the signaling layer, the floor participant: In one embodiment, if the first bit in the subtype of the floor - granted message is set to "1" (a confirmation response is required) as described in sub - clause 8.2.2 of TS3 GPP 24.380, the MCPTT second electronic device 200 transmits a floor confirmation response message. The floor confirmation response message: a. Includes a message type field set to "1" (floor - granted); b. Includes a source field set to "0" (the floor participant is the source); c. Includes location information if the call is a perimeter eavesdropping call and the perimeter eavesdropping call type is remotely initiated.

[0091] In other embodiments, if the floor indicator field is included and the B - bit is set to "1" (broadcast group call) in the MCPTT second electronic device 200, a notification indicating the call type is provided to the user.

[0092] In other embodiments, if the G - bit in the floor instructor is set to "1" (dual floor) in the MCPTT second electronic device 200, the participant saves an instruction that the call will be aborted without cancellation.

[0093] In other embodiments, if it is running, the MCPTT second electronic device 200 aborts the optional timer T103 (end of RTP media).

[0094] In other embodiments, the MCPTT second electronic device 200 aborts the timer T101 (floor request).

[0095] In another embodiment, the MCPTT second electronic device 200 proceeds to the "U: With Permission" state.

[0096] Floor confirmation response message (i.e., floor grant confirmation response message): The floor confirmation response message is used to respond to any floor control message that includes a first bit set to 1 (marked as x in the subtype) (see subclause 8.2.2 of TS3 GPP 24.380). The floor confirmation response message is used only in the on-network mode. The floor confirmation response message is used via a unicast bearer. Table 1 shows the content of the floor confirmation response message.

[0097]

Table 1

[0098] The sub-type is coded according to Table 8.2.2-1 of TS3 GPP 24.380. Its length is coded as specified in sub-clause 8.1.2 of TS3 GPP 24.380. The SSRC field carries the SSRC of the source identified by the source field. The SSRC field is coded as specified in IETF RFC 3550. The source field is coded as specified in 8.2.3.12 of TS3 GPP 24.380. The message type field includes floor control messages that are acknowledged by floor confirmation response messages. The message type field is coded as specified in sub-clause 8.2.3.14 of TS3 GPP 24.380. The track information field is included when the MCPTT call (peripheral listening call) involves a non-controlled MCPTT function. The coding of the track information field is described in sub-clause 8.2.3.13 of TS3 GPP 24.380. The location field is coded as described in sub-clause 8.2.3.21 of TS3 GPP 24.380, includes the location information of the terminating user of the peripheral listening call, and the peripheral listening call type is remotely initiated. The location field is omitted or, alternatively, includes a location type field (not reported) set to 0 when the location information of the terminating user is not allowed by the MCPTT profile of the terminating user.

[0099] Linked message (R: Linked) reception: When receiving a linked message, 1. If the MCPTT client (MCPTT second electronic device 200) accepts the incoming call, the MCPTT client shall: a. Transmit a confirmation response message (i.e., a call control confirmation response message) with a reason code field set to "Accept"; b. If the connection message includes a media stream field, use only the media stream of the pre - established session indicated to be used in the associated call session media stream field; c. Generate an instance of the "Floor Participant State Transition Diagram for Basic Operations" as specified in sub - clause 6.2.4 of TS3 GPP 24.380; d. If the call is a peripheral listening call and the peripheral listening call type is remotely initiated, include location information; and e. Proceed to the "U: In - use pre - established session" state; or 2. Otherwise, the MCPTT client: a. Transmit a confirmation response message (call control confirmation response message) with a reason code field set to "busy" or "not accepted"; and b. Remain in the "U: Not - in - use pre - established session" state.

[0100] The confirmation response message (call control confirmation response message) receives the following: Table 2 shows the content of the confirmation response message.

[0101]

Table 2

[0102] Except for the first three 32-bit words, the order of fields is irrelevant. The subtype shall be coded according to Table 8.3.2-1 of TS3 GPP 24.380. Its length shall be coded as specified in subclause 8.1.2 of TS3 GPP 24.380. The SSRC field shall carry the SSRC of the floor participant. The SSRC field shall be coded as specified in IETF RFC 3550. The reason code field shall be coded as described in subclause 8.3.3.8 of TS3 GPP 24.380. The location field shall be coded as described in subclause 8.2.3.21 of TS3 GPP 24.380, include the location information of the terminating user of the eavesdropping call, and the type of the eavesdropping call is remotely initiated. The field shall be omitted or alternatively include a location type field (not reported) set to 0 when the location information of the terminating user is not allowed by the terminating user's MCPTT profile.

[0103] In one embodiment, the procedures described in the foregoing embodiments for sharing location information are applicable to any other applicable service and are not limited to the MCPTT service only.

[0104] The embodiments disclosed in the present application are implemented using at least one hardware device, can perform network management functions, and can control elements.

[0105] FIG. 5 is a drawing illustrating a UE according to an embodiment of the present disclosure.

[0106] Referring to FIG. 5, the UE 500 also includes a processor 510, a transceiver 520, and a memory 530. However, none of the illustrated components are essential. The UE 500 may also be implemented with more or fewer components than those illustrated in FIG. 5. Furthermore, the processor 510, the transceiver 520, and the memory 530 may also be implemented as a single chip according to other embodiments. In various embodiments of the present disclosure, the UE 500 may also be understood as the MCPTT first electronic device 100 or the MCPTT second electronic device 200.

[0107] The foregoing components will be described in more detail.

[0108] The processor 510 includes one or more processors or other processing devices that control the proposed functions, processes, and / or methods. The operations of the UE 500 are also implemented by the processor 510.

[0109] The transceiver 520 is connected to the processor 510 and can transmit and / or receive signals. Also, the transceiver 520 can receive signals via a wireless channel and output the signals to the processor 510. The transceiver 520 can transmit the signals output from the processor 510 via a wireless channel.

[0110] The memory 530 can store the control information or data included in the signals acquired by the UE 500. The memory 530 is connected to the processor 510 and can store at least one instruction word, protocol, or parameter for the proposed functions, processes, and / or methods. The memory 530 also includes a ROM and / or a RAM and / or a hard disk and / or a CD-ROM (Compact Disc Read-Only Memory) and / or a DVD (Digital Versatile Disc) and / or other storage devices.

[0111] FIG. 6 schematically illustrates a core network entity according to an embodiment of the present disclosure.

[0112] Referring to FIG. 6, the core network entity 600 also includes a processor 610, a transceiver 620, and a memory 630. However, none of the illustrated components are essential. The core network entity 600 may also be implemented by more or fewer components than those illustrated in FIG. 6. Furthermore, the processor 610, the transceiver 620, and the memory 630 may also be implemented as a single chip according to other embodiments. In various embodiments of the present disclosure, the core network entity 600 is also understood as the MCPTT server 300.

[0113] The foregoing components will be described in more detail.

[0114] The transceiver 620 can provide an interface for communicating with other devices in the network. In other words, the transceiver 620 can convert the bit stream transmitted from the core network entity 600 to other devices into a physical signal, and convert the physical signal received from other devices into a bit stream. In other words, the transceiver 620 can transmit and receive signals. The transceiver 620 may be referred to as a modem, a transmitter, a receiver, a communication unit, and a communication module. The transceiver 620 can enable the core network entity 600 to communicate with other devices or systems via a backhaul connection or other connection methods.

[0115] The memory 630 can store a basic program, an application program, and setting information related to the operation of the core network entity 600. The memory 630 also includes a volatile memory, a non-volatile memory, and a combination of a volatile memory and a non-volatile memory. The memory 630 can provide data in response to a request from the processor 610.

[0116] The processor 610 can control the overall operation of the core network entity 600. For example, the processor 610 can transmit and receive signals via the transceiver 620. The processor 610 also includes at least one processor. The processor 610 can control the core network entity 600 to perform operations according to the embodiments of the present disclosure.

[0117] According to an embodiment of the present disclosure, in a remote peripheral call of the MCPTT service, a method for sharing location information includes a step in which the MCPTT server 300 determines that the remote peripheral call is established between the MCPTT first electronic device 100 and the MCPTT second electronic device 200. In this embodiment, the method includes a step of transmitting, by the MCPTT server 300, a floor grant message to the MCPTT second electronic device 200, where the floor grant message includes a mandatory confirmation response request instruction set for the MCPTT second electronic device 200 to share the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100. In this embodiment, the method includes a step of receiving, by the MCPTT server 300, a floor grant confirmation response message having the location information of the MCPTT second electronic device 200, and a step of sharing, by the MCPTT server 300, the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100 in a floor take message.

[0118] According to an embodiment, the method further includes a step of receiving, by the MCPTT server 300, a media transmission from the MCPTT second electronic device 200, and a step of transmitting, by the MCPTT server 300, the received media transmission to the MCPTT first electronic device 100.

[0119] According to one embodiment, the stage in which the MCPTT server 300 determines that a remote peripheral call has been established between the MCPTT first electronic device 100 and the MCPTT second electronic device 200 includes the stage of receiving, by the MCPTT server 300, a remote peripheral listening call request from the MCPTT first electronic device 100 to start a remote start peripheral listening call, the stage of the MCPTT server 300 determining whether the authentication of the user of the MCPTT first electronic device 100 for the remote start peripheral listening call is successful, and in response to determining that the authentication of the user of the MCPTT first electronic device 100 for the remote start peripheral listening call is not successful, transmitting a failure response to the MCPTT first electronic device 100, and transmitting the remote peripheral listening call request to the MCPTT second electronic device 200 to establish a remote peripheral call between the MCPTT first electronic device 100 and the MCPTT second electronic device 200, and the MCPTT server 300 performing one of the above steps.

[0120] According to one embodiment, the floor grant message includes at least one of a timer value allowed to be transmitted by the MCPTT second electronic device 200 in the duration field, a granted priority level in the floor priority field, a track information field, and a floor indicator field, and the first bit in the subtype of the floor grant message is set to 1 when the call is a remote start peripheral listening call.

[0121] According to one embodiment, the track information field stores a state transition diagram for general floor control operations.

[0122] According to one embodiment, when the group call is one of a broadcast group call, a system call, an emergency call, an imminent danger call, or a temporary group session, the floor indicator field has an appropriate indication.

[0123] According to one embodiment, when there is a floor grant message in the queue related to the MCPTT second electronic device 200 to which the floor is granted, the MCPTT server 300 starts a floor-granted timer and sets the floor-granted counter value to 1.

[0124] According to one embodiment, the MCPTT server 300 transmits a floor-taking message to the MCPTT first electronic device 100.

[0125] According to one embodiment, the MCPTT server 300 starts the end of the RTP media timer related to the MCPTT second electronic device 200 to which the floor is granted.

[0126] According to one embodiment, the floor grant confirmation response message includes at least one of a source field, a message type field, a track information field, and a location field.

[0127] According to one embodiment, the message type field is set to 1, the source field is set to 0, when the call is a remote start perimeter listening call, the location information of the MCPTT second electronic device 200 is added to the location field, and the MCPTT profile of the MCPTT second electronic device 200 allows the MCPTT first electronic device 100 to transmit the location information of the MCPTT second electronic device 200. In this embodiment, the first bit in the subtype of the received floor grant message is set to 1.

[0128] According to one embodiment, the MCPTT second electronic device 200 receives a floor grant message including an essential confirmation response request instruction from the MCPTT server 300, transmits a floor grant confirmation response message having the location information of the MCPTT second electronic device 200 to the MCPTT server 300, provides a floor grant notification, and is configured to perform the end of the RTP media timer and the end of the floor-granted timer.

[0129] According to one embodiment, the method includes receiving, by an MCPTT server 300, a remote peripheral listening call request from an MCPTT first electronic device 100 to initiate a remote start peripheral listening call; determining, by the MCPTT server 300, that the authentication of the user of the MCPTT first electronic device 100 for the remote start peripheral listening call is successful; transmitting, by the MCPTT server 300, the remote peripheral listening call request to an MCPTT second electronic device 200 to establish a remote peripheral call between the MCPTT first electronic device 100 and the MCPTT second electronic device 200; receiving, by the MCPTT server 300, location information of the MCPTT second electronic device 200 in a connection confirmation response message from the MCPTT second electronic device 200, where the location is a field added to the connection confirmation response message, the step of receiving the location information; and sharing, by the MCPTT server 300, the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100.

[0130] According to one embodiment of the present disclosure, an MCPTT server 300 for sharing location information in a remote peripheral call of an MCPTT service includes a memory 310, a processor 320, and a floor control unit 340 operatively coupled to the memory 310. The processor 320 is configured to determine that a remote peripheral call is established between an MCPTT first electronic device 100 and an MCPTT second electronic device 200, transmit a floor grant message to the MCPTT second electronic device 200, the floor grant message including a mandatory confirmation response request instruction set for the MCPTT second electronic device 200 to share the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100, receive a floor grant confirmation response message having the location information of the MCPTT second electronic device 200, and share the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100 in a floor take message.

[0131] According to one embodiment, the processor 320 is further configured to receive a media transmission from the MCPTT second electronic device 200 and transmit the received media transmission to the MCPTT first electronic device 100.

[0132] According to one embodiment, determining that a remote peripheral call is established between the MCPTT first electronic device 100 and the MCPTT second electronic device 200 includes receiving a remote peripheral listening call request from the MCPTT first electronic device 100 to initiate a remote start peripheral listening call, determining whether the authentication of the user of the MCPTT first electronic device 100 for the remote start peripheral listening call is successful, and in response to determining that the authentication of the user of the MCPTT first electronic device 100 for the remote start peripheral listening call is not successful, transmitting a failure response to the MCPTT first electronic device 100, and transmitting the remote peripheral listening call request to the MCPTT second electronic device 200 to establish a remote peripheral call between the MCPTT first electronic device 100 and the MCPTT second electronic device 200, including performing one of them.

[0133] According to one embodiment, the floor grant message includes at least one of a timer value allowed to be transmitted by the MCPTT second electronic device 200 in the duration field, a granted priority level in the floor priority field, a track information field, and a floor indicator field, and the first bit in the subtype of the floor grant message is set to 1 when the call is a remote start peripheral listening call.

[0134] According to one embodiment, the track information field stores a state transition diagram for general floor control operations.

[0135] According to one embodiment, the floor indicator field has an appropriate indication when the group call is one of a broadcast group call, a system call, an emergency call, an imminent danger call, or a temporary group session.

[0136] According to one embodiment, when there is a floor grant message in the queue related to the MCPTT second electronic device 200 for which the floor is granted, the MCPTT server 300 starts a floor grant timer and sets the floor grant counter value to 1.

[0137] According to one embodiment, the MCPTT server 300 transmits a floor take message to the MCPTT first electronic device 100.

[0138] According to one embodiment, the MCPTT server 300 starts the end of the RTP media timer related to the MCPTT second electronic device 200 to which the floor is granted.

[0139] According to one embodiment, the floor grant confirmation response message includes at least one of a source field, a message type field, a track information field, and a location field.

[0140] According to one embodiment, the processor 320 receives a remote start peripheral listening call request from the MCPTT first electronic device 100 to start a remote start peripheral listening call, determines that the authentication of the user of the MCPTT first electronic device 100 for the remote start peripheral listening call is successful, and transmits the remote start peripheral listening call request to the MCPTT second electronic device 200 to establish a remote peripheral call between the MCPTT first electronic device 100 and the MCPTT second electronic device 200. In the connection confirmation response message from the MCPTT second electronic device 200, the location information of the MCPTT second electronic device 200 is received, and the location is a field added to the connection confirmation response message. The location information is received, and the location information of the MCPTT second electronic device 200 is configured to be shared with the MCPTT first electronic device 100.

[0141] According to one embodiment of the present disclosure, in a remote peripheral call of an MCPTT service, a second electronic device 200 that shares location information includes a memory 210, a processor 220, and a floor control unit 240 operatively coupled to the memory 210 and the processor 220. The floor control unit 240 receives, from an MCPTT server 300, a floor grant message including a mandatory confirmation response request instruction, transmits a floor grant confirmation response message having the location information of the MCPTT second electronic device 200 to the MCPTT server 300, provides a floor grant notification, includes a floor indicator field, and provides a notification indicating a call type to a user when a B-bit is set to 1. When a G-bit in the floor indicator is set to 1, a participant stores an instruction that the participant is given priority without cancellation, and is configured to perform an end of an RTP media timer and an end of a floor-granted timer.

[0142] According to one embodiment, the floor grant confirmation response message includes at least one of a source field, a message type field, a track information field, and a location field.

[0143] According to one embodiment, the message type field is set to 1, the source field is set to 0, when the call is a remote start peripheral listening call, the location information of the MCPTT second electronic device 200 is added to the location field, and the MCPTT profile of the MCPTT second electronic device 200 allows the MCPTT first electronic device 100 to transmit the location information of the MCPTT second electronic device 200, where a first bit in a subtype of the floor grant message is set to 1.

[0144] According to one embodiment of the present disclosure, in a remote peripheral call of an MCPTT service, a system 1000 for sharing location information includes an MCPTT server 300 and an MCPTT second electronic device 200. The MCPTT server 300 determines that a remote peripheral call has been established between the MCPTT first electronic device 100 and the MCPTT second electronic device 200, and transmits a floor grant message to the MCPTT second electronic device 200. The floor grant message includes a mandatory confirmation response request instruction set for the MCPTT second electronic device 200 to share the location information of the MCPTT second electronic device 200 with the MCPTT first electronic device 100. The MCPTT server 300 transmits the floor grant message, receives a floor grant confirmation response message having the location information of the MCPTT second electronic device 200, and uses the floor take message to share the location information between the MCPTT first electronic device 100 and the MCPTT second electronic device 200 in the remote peripheral call of the MCPTT service. The MCPTT second electronic device 200 receives a floor grant message including a mandatory confirmation response request instruction from the MCPTT server 300, and transmits a floor grant confirmation response message having the location information of the MCPTT second electronic device 200 to the MCPTT server 300, provides a floor grant notification, includes a floor indicator field, and provides a notification indicating a call type to the user when the B-bit is set to 1. When the G-bit in the floor indicator is set to 1, the participant saves an instruction to be aborted without cancellation, and is configured to perform the end of the RTP media timer and the end of the floor grant timer.

[0145] The foregoing description of specific embodiments fully discloses the general nature of the embodiments in the present disclosure, such that others can, by applying current knowledge, readily modify and / or adapt such specific embodiments for various applications without departing from the general concepts. Therefore, such adaptations and modifications should be understood to be within the meaning and scope of the equivalents of the disclosed embodiments and are intended to be so understood. It must be understood that the syntax or terminology employed in this disclosure is for the purpose of description and not of limitation. Therefore, although embodiments herein have been described in terms of aspects of the preferred embodiments, those of ordinary skill in the relevant art will recognize that the embodiments herein can be practiced with modifications within the scope of the embodiments as described in this application.

Description of Reference Numerals

[0146] 100 MCPTT Client - 1, First MCPTT Electronic Device 200 MCPTT Client - 2, Second MCPTT Electronic Device 210 Memory 220 Processor 230 Communication Unit 240 Floor Control Unit 300 MCPTT Server 310 Memory 320 Processor 330 Communication Unit 340 Floor Control Unit 500 User Equipment (UE) 510 Processor 520 Transceiver 530 Memory 600 Core Network Entity 610 Processor 620 Transceiver 630 Memory

Claims

1. In a wireless communication system, in a method performed by a server, identifying whether a remote peripheral listening call has been requested from a first device to a second device; when the call is the remote peripheral listening call, transmitting a floor granted message including a confirmation response request indicator including information indicating whether a confirmation response is required to the second device; receiving, from the second device, a floor confirmation response message including location information of the second device based on the floor granted message; transmitting, to the first device, a floor take message including the location information of the second device, the method comprising:

2. further comprising receiving media from the second device; transmitting the received media to the first device, the method according to claim 1.

3. The step of identifying whether the remote peripheral listening call has been requested comprises: receiving, from the first device, a remote peripheral listening call request; identifying whether authentication of the first device for the remote peripheral listening call has been successful; transmitting the remote peripheral listening call request to the second device; receiving, from the second device, a remote peripheral listening call response, the method according to claim 1.

4. The floor granted message includes at least one of a duration field including a timer value allowed to be transmitted by the second device, a floor priority field including a granted priority level, a track information field, a floor indicator field, or information related to a subtype of the floor granted message, wherein the information related to the subtype includes a first bit set to 1, the method according to claim 1.

5. The floor confirmation response message includes at least one of a message type field set to 1, a source field set to 0, or a location field including the location information of the second device, the method according to claim 1.

6. The location field includes at least one of a location field ID, a location length, or a location value, the method according to claim 5.

7. The method according to claim 1, wherein the floor-taking message further includes at least one of information related to the identity of the granted user or information related to the function alias of the granted user.

8. In a server in a wireless communication system, a communication unit, and at least one processor coupled to the communication unit, wherein the at least one processor identifies whether a remote peripheral listening call has been requested from a first device to a second device, and when the call is the remote peripheral listening call, controls the communication unit to transmit a floor-granted message including a confirmation response request indicator including information indicating whether a confirmation response is required to the second device, controls the communication unit to receive, from the second device, a floor confirmation response message including location information of the second device based on the floor-granted message, and is configured to transmit a floor-taking message including the location information of the second device to the first device.

9. The at least one processor is further configured to control the communication unit to receive media from the second device, and control the communication unit to transmit the received media to the first device. The server according to claim 8.

10. The at least one processor is further configured to control the communication unit to receive a remote peripheral listening call request from the first device, identify whether authentication of the first device for the remote peripheral listening call is successful, control the communication unit to transmit the remote peripheral listening call request to the second device, and control the communication unit to receive a remote peripheral listening call response from the second device. The server according to claim 8.

11. The floor-granted message includes at least one of a duration field including a timer value allowed to be transmitted by the second device, a floor priority field including a granted priority level, a track information field, a floor indicator field, or information related to a subtype of the floor-granted message, and the information related to the subtype includes a first bit set to 1. The server according to claim 8.

12. The server according to claim 8, wherein the floor confirmation response message includes at least one of a message type field set to 1, a source field set to 0, or a location field including the location information of the second device.

13. The server according to claim 12, wherein the location field includes at least one of a location field ID, a location length, or a location value.

14. The server according to claim 8, wherein the floor take message further includes at least one of information related to the identity of the granted user or information related to the function alias of the granted user.

15. In a wireless communication system, in a method performed by a second device, when a remote peripheral listening call is requested from a first device, receiving, from a server, a floor granted message including a confirmation response request indicator indicating whether a confirmation response is required if the call is the remote peripheral listening call; and transmitting, to the server, a floor confirmation response message including the location of the second device based on the floor granted message.

Images