Method and apparatus for merging ongoing temporary group communications

Abstract

Techniques and apparatus are provided for merging ongoing temporary group communications. A first critical task (MC) user equipment is in a first ongoing temporary group communication with a second MC user equipment and in a second ongoing temporary group communication with a third MC user equipment. The process required to merge two ongoing critical task temporary group communications comprises: receiving a merge temporary group communication request from the first MC user equipment to merge the first temporary group communication and the second temporary group communication; verifying whether the first MC user equipment is authorized to combine the first temporary group communication and the second temporary group communication; and transmitting a merged temporary group communication response to the first MC user equipment. Further, the second ongoing temporary group communication is terminated, combined with the first temporary group, and all participants are added to the first ongoing temporary group communication.

Description

[0001] Related applications This patent application claims priority to Indian Provisional Patent Application No. 202311076097, filed on 7 November 2023, which is incorporated herein by reference in its entirety. Technical Field

[0002] Various example embodiments generally relate to wireless communication. More specifically, methods, apparatus, and computer program products for merging ongoing ad-hoc group communications in a communication network are described. Background Technology

[0003] Various example embodiments relate to considerations in (e.g., mobile and / or wireless) communication networks, such as GSM networks, UMTS, LTE networks, 5G (also known as NR) networks, and next-generation systems beyond 5G networks.

[0004] Public safety is paramount in emergencies—it is mission critical (MC). To protect people in emergencies such as earthquakes, wildfires, and terrorist attacks, reliable security systems are needed, and most importantly, reliable communication networks, namely mission critical networks (MCNs). MCNs are dedicated communication networks used by public agencies such as police, fire departments, and the military for routine operations, especially in emergency situations.

[0005] In 3GPP TS 23.379 Release 14.0.0, the 3rd Generation Partnership Project (3GPP) introduced the functional architecture and information flow to support LTE Mission-Critical Push-to-Talk (MCPTT). Later, in 3GPP TS 23.379 Release 18.0.0, a similar concept was introduced for 5G. The MCPTT service provides reliable communication for emergency services and supports communication between multiple users (e.g., user equipment) (e.g., group calls, group data communications, and / or group video communications), where each user (e.g., user equipment) can obtain permission to initiate and / or participate in group calls, send data, and provide video through arbitration. The MCPTT service also supports private communication between two users (e.g., two user equipment).

[0006] Other MC support services involving group communications in LTE and / or 5G networks, such as temporary video group communications and temporary data group communications defined in 3GPP TS 23.281 and 3GPP TS 23.282 respectively. Therefore, group communications in the following disclosure should be understood to refer to communications such as voice calls, video communications, and / or data group communications.

[0007] One drawback of the Current Temporary Group Communication (MCN) defined in the 3GPP standard is that—although individual users (e.g., user equipment) can be invited and / or added one by one—the current 3GPP standard does not support combining two or more ongoing group communications. Therefore, it is necessary to merge ongoing temporary group communications in 3GPP networks to enable more reliable and faster communication from public authorities in emergency situations.

[0008] List of abbreviations and acronyms Use the following abbreviations and acronyms throughout the thematic disclosure: 3GPP Third Generation Partnership Project 5G, the fifth generation, is a new wireless network (also abbreviated as NR). AMF Access and Mobility Management Functions AS Access Layer CN Core Network GSM Global Mobile Communication System GW gateway ID identifier LTE Long Term Evolution Network MC (Minecraft) MCN (Mission-Critical Network) MCPTT Critical Mission One-Click NAS Non-Access Layer PDU (Processing Data Unit) RAN (Radio Access Network) RRC (Radio Resource Control) UE User Equipment UMTS Universal Mobile Telecommunication System Overview This disclosure provides a mechanism for merging ongoing temporary group communications in a communication network. This disclosure also provides methods and apparatus for merging ongoing temporary group calls, data communications, and video communications in a communication network (e.g., an MCN).

[0009] The subject matter of the independent claims is provided for some aspects. Other aspects are defined in the dependent claims.

[0010] According to a first aspect of this disclosure, a mission-critical (MC) service server is provided. The MC service server includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the MC service server to at least: receive a merge temporary group communication request from a first MC user equipment to merge the first temporary group communication and the second temporary group communication; verify whether the first MC user equipment is authorized to merge the first temporary group communication and the second temporary group communication; and transmit a merge temporary group communication response to the first MC user equipment. The instructions, when executed by the at least one processor, also cause the MC service server to: transmit a first temporary group communication release request to a third MC user equipment to release the second temporary group communication; receive a first temporary group communication release response from the third MC user equipment; transmit a second temporary group communication release request to the first MC user equipment to release the second temporary group communication; receive a second temporary group communication release response from the first MC user equipment; transmit a temporary group communication request for the first temporary group communication to the third MC user equipment; and receive a temporary group communication response from the third MC user equipment.

[0011] In a variation of the first aspect, the instructions further cause the MC service server to transmit a temporary group communication notification to the first MC user equipment to indicate that the third MC user equipment has been added to the first temporary group communication. In another variation of the first aspect, the instructions, when executed by the at least one processor, further cause the MC service server to transmit a temporary group communication membership notification to the first MC user equipment, the second MC user equipment, and the third MC user equipment to indicate the members of the first temporary group communication.

[0012] In an additional variation of the first aspect, the merge temporary group communication request includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an identifier of the second temporary group communication. In yet another additional variation of the first aspect, the merge temporary group communication response includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

[0013] According to a second aspect of this disclosure, a first mission-critical (MC) user equipment (UE) is provided. The first MC UE includes at least one processor and a memory storing instructions, which, when executed by the at least one processor, cause the first MC UE to at least: transmit a merge temporary group communication request to an MC service server to merge the first temporary group communication and the second temporary group communication; receive a merge temporary group communication response from the MC service server; receive a temporary group communication release request from the MC service server to release the second temporary communication; and transmit a temporary group communication release response to the MC service server.

[0014] In a variation of the second aspect, the instruction, when executed by the at least one processor, further causes the first MC user equipment to receive a temporary group communication notification from the MC service server to indicate that the third MC user equipment has been added to the first temporary group communication. In yet another variation of the second aspect, the instruction further causes the first MC user equipment to receive a temporary group communication member notification from the MC service server to indicate the members of the first temporary group communication. In still another variation of the second aspect, the instruction, when executed by the at least one processor, further causes the first MC user equipment, in response to receiving the temporary group communication release request, to notify its user that the second temporary group communication has been terminated and merged with the first temporary group.

[0015] In an additional variation of the second aspect, the merge temporary group communication request includes at least one of the following: an identifier of the first MC user equipment; a functional alias of the first MC user equipment; an identifier of the first temporary group communication; and an identifier of the second temporary group communication. In yet another additional variation of the second aspect, the merge temporary group communication response includes at least one of the following: an identifier of the first MC user equipment, a functional alias of the first MC user equipment, an identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

[0016] According to a third aspect, a third mission-critical (MC) user equipment is provided. The apparatus includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the third MC user equipment to at least: receive a temporary group communication release request from an MC service server to release a second temporary group communication, transmit a temporary group communication release response to the MC service server, receive a temporary group communication request from the MC service server to enter a first temporary group communication established between a first MC user equipment and a second MC user equipment, and transmit a temporary group communication response to the MC service server.

[0017] In a variation of the third aspect, the instruction, when executed by the at least one processor, further causes the third MC user equipment to receive a temporary group communication member notification from the MC service server to indicate the members of the first temporary group communication. In another variation of the third aspect, the instruction, when executed by the at least one processor, further causes the third MC user equipment to notify its user that the second temporary group communication has been terminated and merged with the first temporary group in response to receiving the temporary group communication release request. In yet another variation of the third aspect, the instruction, when executed by the at least one processor, further causes the third MC user equipment to notify its user that the first temporary group communication has been established in response to receiving the temporary group communication request.

[0018] As a fourth aspect, a method performed by a mission-critical (MC) service server is provided. The method includes: receiving a merge temporary group communication request from a first MC user equipment (UE) to merge first temporary group communication and second temporary group communication; verifying whether the first MC UE is authorized to merge the first temporary group communication and the second temporary group communication; and transmitting a merge temporary group communication response to the first MC UE. The method further includes: transmitting a first temporary group communication release request to a third MC UE to release the second temporary group communication; receiving a first temporary group communication release response from the third MC UE; transmitting a second temporary group communication release request to the first MC UE to release the second temporary group communication; receiving a second temporary group communication release response from the first MC UE; transmitting a temporary group communication request for the first temporary group communication to the third MC UE; and receiving a temporary group communication response from the third MC UE.

[0019] In a variation of the fourth aspect, the method further includes transmitting a temporary group communication notification to the first MC user equipment to indicate that the third MC user equipment has been added to the first temporary group communication. In another variation of the fourth aspect, the method further includes transmitting a temporary group communication membership notification to the first MC user equipment, the second MC user equipment, and the third MC user equipment to indicate the membership of the first temporary group communication.

[0020] In an additional variation of the fourth aspect, the merge temporary group communication request includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an identifier of the second temporary group communication. In yet another additional variation of the fourth aspect, the merge temporary group communication response includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

[0021] As a fifth aspect, a method is provided performed by a first mission-critical (MC) user equipment in a network, the first MC user equipment being in a first temporary group communication with a second MC user equipment and in a second temporary group communication with a third MC user equipment. The method includes: transmitting a merge temporary group communication request to an MC service server to merge the first temporary group communication and the second temporary group communication; receiving a merge temporary group communication response from the MC service server; receiving a temporary group communication release request from the MC service server to release the second temporary communication; and transmitting the temporary group communication release response to the MC service server.

[0022] In a variation of the fifth aspect, the method further includes receiving a temporary group communication notification from the MC service server to indicate that the third MC user equipment has been added to the first temporary group communication. In another variation of the fifth aspect, the method further includes receiving a temporary group communication membership notification from the MC service server to indicate the members of the first temporary group communication. In yet another variation of the fifth aspect, the method further includes receiving the temporary group communication release request to notify the user of the device that the second temporary group communication has been terminated and merged with the first temporary group.

[0023] In an additional variation of the fifth aspect, the merge temporary group communication request includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an identifier of the second temporary group communication. In yet another additional variation of the fifth aspect, the merge temporary group communication response includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

[0024] As a sixth aspect, a method is provided performed by a third mission-critical (MC) user equipment in a network, the third MC user equipment being in second temporary group communication with a first MC user equipment. The method includes: receiving a temporary group communication release request from an MC service server to release the second temporary group communication; transmitting a temporary group communication release response to the MC service server; receiving a temporary group communication request from the MC service server to enter a first temporary group communication established between the first MC user equipment and the second MC user equipment; and transmitting a temporary group communication response to the MC service server.

[0025] In a variation of the sixth aspect, the method further includes receiving a temporary group communication member notification from the MC service server to indicate the members of the first temporary group communication. In another variation of the sixth aspect, the method further includes, in response to receiving the temporary group communication release request, notifying a user of the device that the second temporary group communication has been terminated and merged with the first temporary group. In yet another variation of the sixth aspect, the method further includes, in response to receiving the temporary group communication request, notifying a user of the device that the first temporary group communication has been established.

[0026] As a seventh aspect, a computer program product is provided, which includes program instructions stored on a computer-readable medium that, when executed on a computer, perform the methods described herein.

[0027] Brief description of the attached figures This disclosure can be better understood when the following detailed description of various embodiments is considered in conjunction with the accompanying drawings, in which: Figure 1 A schematic diagram of an example (mobile or wireless) communication network is shown; Figure 2 A schematic diagram of an example wireless device or entity is shown; Figure 3 A schematic diagram of an example network node or entity is shown; Figure 4 A flowchart is shown of an example method performed by a mission-critical service server as described herein; Figure 5 A flowchart is shown of an example method performed by a first mission-critical user equipment as described herein; Figure 6 A flowchart is shown of an example method performed by a third-critical-mission user equipment as described herein; Figure 7 The procedure for merging temporary group calls according to an example embodiment is shown; Figure 8 The procedure for merging temporary group data communications is shown; Figure 9 The process for merging temporary group video communications according to an example embodiment is illustrated; Detailed description The examples and embodiments set forth below represent information that enables those skilled in the art to practice this disclosure. Upon reading the following description taken in conjunction with the accompanying drawings, those skilled in the art will understand the concepts described and recognize the application of these concepts not specifically mentioned herein. It should be understood that these concepts and applications fall within the scope of this description.

[0028] Numerous specific details are set forth in the following description. However, it should be understood that embodiments can be implemented without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail so as not to obscure the understanding of this description. Those skilled in the art will be able to implement appropriate functionality without excessive experimentation based on the included description.

[0029] References to "an embodiment," "an embodiment," "an exemplary embodiment," etc., in the specification indicate that the described embodiment may include a specific feature, structure, or characteristic, but each embodiment does not necessarily include that specific feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is believed that those skilled in the art will be able to implement such feature, structure, or characteristic in combination with other embodiments, whether explicitly described or not.

[0030] It is important to note that the detailed descriptions sometimes use one or more specifications as non-limiting and illustrative examples of certain architectures, network configurations, and system deployments. More specifically, the detailed descriptions use 3GPP standards as non-limiting and illustrative examples. Therefore, the exemplary embodiments provided herein may specifically employ terminology directly related to them. Such terminology is used only in the context of non-limiting and illustrative examples and is not intended to limit the exemplary embodiments in any way. Rather, any other system configuration or deployment may be utilized while conforming to the content described herein, and / or the exemplary embodiments are applicable to it.

[0031] For example, various example embodiments are applicable to any (e.g., mobile or wireless) communication network, such as 5G networks and next-generation networks beyond 5G. For example, various example embodiments are applicable to 3GPP standardized mobile or wireless communication networks operating according to 3GPP Release 18 and any future versions of 3GPP standards.

[0032] In the following description, various example embodiments are used with multiple variations and / or alternatives. It should be noted that, depending on certain implementations or constraints, all described variations and / or alternatives may be provided individually or in any conceivable combination (e.g., combinations of individual features of these various variations and / or alternatives are also included).

[0033] As used herein, the terms "comprising" and "including" should be understood to mean that the exemplary embodiments are not limited to consisting only of those features mentioned, and that the exemplary embodiments may also include other things, such as features, structures, units, modules or the like not specifically mentioned.

[0034] As used herein, "at least one of the following: " and "at least one of " and similar wording such as "one or more", where the list of two or more elements is connected by "and" or "or", means at least any one element, or at least any two or more elements, or at least all elements.

[0035] As used herein, according to various example embodiments, any operation of sending or receiving may include actual transmission or communication operations, i.e., transmitting or communicating associated messages or signals, but may also additionally or alternatively include associated processing operations, i.e., preparing / generating / emitting associated messages or signals before sending and / or acquiring / processing / handling associated messages or signals after receiving. For example, sending a message by an entity may include generating / emitting and / or transmitting / communicating its or a corresponding signal by that entity, and receiving a message by an entity may include acquiring / processing and / or processing its or a corresponding signal by that entity. As used herein, a message may refer to and / or contain any kind of corresponding information, signal, or the like.

[0036] In the accompanying drawings, it should be noted that the lines / arrows connecting the various blocks or entities are generally intended to illustrate operational coupling between them. This coupling can be physical and / or logical, implementation-independent (e.g., wired or wireless), and can also include any number of intermediate functional blocks or entities not shown. In flowcharts or sequence diagrams, the order of operations or actions shown is generally non-limiting and illustrative, and any other order of the various operations or actions may be contemplated where feasible.

[0037] Before explaining the example embodiments in detail, refer to Figures 1 to 3 A brief explanation of some general principles of (mobile or wireless) communication systems is provided to aid in understanding the underlying technology of the example embodiments.

[0038] Figure 1An example of a (mobile or wireless) communication system 100 according to embodiments described herein is illustrated. The communication system 100 includes wireless communication devices or entities, such as user equipment (UE) 110 (e.g., 110A-110C), and access network nodes or entities, such as wireless access network nodes 120 (e.g., 120A-120B) (e.g., eNB, gNB, etc.), connected to one or more network nodes or entities 130, such as servers, on an interconnection network 125. UEs 110 within coverage area 115 may each be able to communicate directly with wireless access network nodes 120 via a wireless link (e.g., a radio link, such as a Uu link).

[0039] As an example, UE 110A can communicate with radio access network node 120A via a wireless link (e.g., a radio link). That is, UE 110A can transmit wireless signals (e.g., radio signals) to and / or receive wireless signals (e.g., radio signals) from radio access network node 120A. The wireless signals may contain voice traffic, data traffic, control signals, and / or any other suitable information. Furthermore, UEs 110A-110C can be mission-critical (MC) UEs, meaning they can perform temporary group communications with other UEs. For example, UE 110A can make a temporary group call with UE 110B and another temporary group call with UE 110C. Group communications can involve two, three, four, or more UEs.

[0040] As used herein, the term "User Equipment" (UE) has the full breadth of its common meaning and can refer to any type of wireless communication device or entity capable of communicating with a network node or entity accessing the network and / or with another UE in the mobile or wireless system 100. A UE can be a D2D UE, a machine-type UE, or a UE capable of machine-to-machine (M2M) communication. Examples of UEs include personal digital assistants, tablets, mobile terminals, mobile phones, smartphones, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, ProSe UEs, vehicle-to-vehicle (V2V) UEs, V2X UEs, MTC UEs, eMTC UEs, FeMTC UEs, UE Cat 0, UE Cat M1, narrowband IoT (NB-IoT) UEs, UE Cat NB1, etc. Example embodiments of UEs will be described below relative to... Figure 2 To provide a more detailed description.

[0041] In some embodiments, the wireless signal coverage area 115 associated with the wireless access network node 120 may be referred to as a cell. However, particularly with regard to fifth-generation (5G) / new radio (NR) technologies, beams may be used instead of cells; therefore, it is important to note that the concepts described herein also apply to cells and beams.

[0042] Regarding a beam-based mobile communication system, a radio access network node 120 (e.g., a base station) may transmit beamforming signals to a UE 110 in one or more transmission directions (transmit beam, Tx beam). The UE 110 may receive beamforming signals from the base station 120 in one or more reception directions (receive beam, Rx beam). The UE 110 may also transmit beamforming signals to the base station 120 in one or more directions, and the base station 120 may receive beamforming signals from the UE 110 in one or more directions. The radio access network node (e.g., base station) 120 and the UE 110 may determine optimal reception and transmission directions, for example, in the sense that these directions result in the highest link quality or satisfy other quality conditions in the most suitable manner, for each base station / UE pair.

[0043] Interconnection network 125 can refer to any network capable of transmitting audio, video, signals, data, messages, or any combination thereof received from wireless access network node 120. Interconnection network 125 may include a transport network, a core network, a public switched telephone network (PSTN), a public data network, a private data network, a wireless network such as a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communications or computer network such as the Internet, a wired network, a corporate intranet, any other suitable network, or a combination thereof.

[0044] In some embodiments, one or more network nodes or entities 130 may include an MC service server. UE 110 may include an MCPTT client, as described below, and the MCPTT client may exchange certain signals with the MC service server using Non-Access Stratum (NAS) signaling. NAS signaling between UE 110 (e.g., the MCPTT client) and the MC service server may be transparently transmitted through radio access network node 120. In some embodiments, radio access network node 120 may communicate with one or more network nodes or entities 130, including the MC service client, via an inter-node interface.

[0045] As used herein, the term "access network node or entity" has the full breadth of its common meaning and can correspond to any type of access node (e.g., a WiFi™ access point or a wireless access network node) that can communicate with a UE. Examples of wireless access network nodes are NodeBs, MeNBs, SeNBs, wireless access network nodes that may belong to MCGs or SCGs, base stations (BSs), multi-standard radio (MSR) wireless access nodes such as MSR BSs, eNodeBs, network controllers, radio network controllers (RNCs), base station controllers (BSCs), relays, donor nodes of control relays, base transceivers (BTSs), access points (APs), transport points, transport nodes, RRUs, RRHs, and nodes in distributed antenna systems (DASs). Example embodiments of wireless access network nodes will be described below relative to... Figure 3 To provide a more detailed description.

[0046] In some embodiments, the wireless access network node 120 may be a distributed wireless access node. The components and associated functions of the wireless access network node 120 may be divided into two main units (or sub-wireless network nodes), which may be referred to as a central unit (CU) and a distributed unit (DU). Different distributed wireless network node architectures are possible. For example, in some architectures, the DU may be connected to the CU via a dedicated wired or wireless link (e.g., fiber optic cable), while in other architectures, the DU may be connected to the CU via a transport network. Furthermore, how the various functions of the wireless access network node 120 are separated between the CU and the DU may vary depending on the chosen architecture.

[0047] Exemplary technologies and protocols for wireless communication systems are standardized by the 3rd Generation Partnership Project (3GPP). Various developments of Radio Access Technologies (RATs) described in 3GPP specifications are referred to as versions. More recent developments of RATs described in 3GPP standards include Long Term Evolution (LTE) of Universal Mobile Telecommunications System (UMTS), LTE Advanced (LTE-A), and 5G or NR. LTE (LTE-A) networks employ a radio access network called Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network called Evolved Packet Core (EPC). E-UTRAN radio access network nodes (e.g., base stations) are referred to as Evolved or Enhanced Node Bs (eNBs) and provide E-UTRAN features such as user plane packet data aggregation and / or Radio Link Control / Media Access Control / Physical Layer Protocols (PDCP / RLC / MAC / PHY) and Radio Resource Control (RRC) protocol termination to the control plane of communication devices. Other examples of RATs include those provided by access nodes in communication networks based on technologies such as WLAN and / or Global Microwave Access Interoperability (WiMax). Wireless access network nodes (e.g., base stations) can provide coverage for an entire cell or similar wireless service area.

[0048] Another example of a communication network is the 5G or NR communication network described in the 3GPP standard. The radio access network of a 5G or NR communication network is called a Next Generation Radio Access Network (NG-RAN). The radio access nodes (e.g., base stations) of NG-RAN can be referred to as Next Generation Node Bs (gNBs). UEs configured for NR communication and RAN nodes of NG-RAN can use multiple-input multiple-output (MIMO) antennas, and NG-RAN can include far more base stations or nodes than E-UTRAN (the so-called small cell concept), including macro sites operating in conjunction with smaller sites, and perhaps employing various wireless technologies to achieve better coverage and enhanced data rates.

[0049] Future communication networks can leverage Network Functions Virtualization (NFV), a proposed concept that virtualizes network node functions as "building blocks" or entities that can be operationally connected or linked together to provide services. Virtualized network node functions can include one or more virtual machines running on standard or general-purpose computing devices or systems (e.g., computing devices or systems including processors and memory), rather than custom hardware. Cloud computing systems can also provide virtualized network node functions. For wireless communication between wireless communication devices (e.g., UEs) and wireless access network nodes, the wireless access network node can include virtual network node functions hosted or running on computing devices (e.g., servers) coupled to a remote radio head, and perform wireless communication operations with the wireless communication device (e.g., the UE).

[0050] The example 5G core network (CN) of interconnection network 125 includes functional entities, typically referred to as core network functions or core network entities. The CN connects to wireless communication devices (e.g., UEs) via access nodes (e.g., radio access network nodes of the RAN). A UPF (User Plane Function), typically referred to as a PSA (PDU Session Anchor), connected to interconnection network 125 via the N6 interface, is responsible for forwarding data traffic back and forth between the DN (Data Network) and the tunnel established between the RAN node and the PSA when a data session (e.g., a PDU session) is established between the wireless communication network (e.g., UE 110), the RAN node 120, and the core network's UPF. The UPF is controlled by an SMF (Session Management Function), which receives policies from a PCF (Policy Control Function), including policies related to traffic transmission between the UPF and the wireless communication device (e.g., UE 110). The CN may also include an AMF (Access and Mobility Function), configured to perform access and mobility management for wireless communication devices (e.g., UE 110) connected to the core network.

[0051] Generally, all concepts disclosed herein can be applied to different communication networks, including but not limited to LTE, LTE-A, 5G, 5G advanced, 6G and other future or already implemented networks.

[0052] Figure 2 This is a schematic diagram of an example UE 110 according to certain example embodiments. UE 110 may include one or more of at least one of the following: at least one transceiver 210, at least one processor 220, at least one memory 230, and at least one network interface 240. In some example embodiments, transceiver 210 facilitates the transmission of and reception of wireless signals (e.g., radio signals) to and from a wireless access network node 120 (e.g., via a transmitter (Tx), a receiver (Rx), and one or more antennas). Processor 220 executes instructions to provide some or all of the functions provided by UE 110 as described herein, and memory 230 stores the instructions executed by processor 220. In some embodiments, processor 220 and memory 230 form a processing circuit.

[0053] Processor 220 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the functions described herein for UE 110. In some embodiments, processor 220 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more hardware accelerators, one or more graphics processing units (GPUs), one or more tensor processing units (TPUs), one or more application-specific integrated circuits (ASICs), one or more field-programmable gate arrays (FPGAs), and / or other logic.

[0054] Memory 230 is generally operable to store instructions, such as computer programs, software, application programs including one or more of logic, rules, algorithms, code, tables, etc., and / or other instructions executable by processor 220. Examples of memory 230 include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., optical disc (CD) or digital video disc (DVD)) and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processor 220 of UE 110. For example, memory 230 includes instructions that cause processor 220 to perform processing according to any of the corresponding methods described herein.

[0055] Network interface 240 is communicatively coupled to processor 220 and can refer to any suitable device operable to receive input from UE 110, send output from UE 110, perform appropriate processing on the input or output or both, communicate with other devices, or any combination thereof. Network interface 240 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, for communication over a network.

[0056] Other embodiments of UE 110 may include beyond Figure 2The additional components shown may be responsible for providing certain aspects of the functionality of UE 110, including any functionality described herein and / or any additional functionality (including any functionality required to support the mechanisms disclosed in this subject matter). As an example, UE 110 may include input devices and circuitry, output devices, and one or more synchronization units or circuits, which may be part of processor 220. Input devices include mechanisms for inputting data into UE 110, such as a keyboard, a keyboard (e.g., a touch-sensitive keyboard), and a touchscreen display. Examples of other input devices include a microphone. Output devices may include mechanisms for outputting data in audio, video, and / or hardcopy formats. Examples of output devices may include speakers and displays. In embodiments, UE 110 according to this disclosure includes a Mission Critical Push-to-Talk (MCPTT) client, a Mission Critical Video client, or a Mission Critical Data client. UE 110 may also include a single client having all three capabilities: MCPTT, Mission Critical Video client, and Mission Critical Data client.

[0057] In some example embodiments, UE 110 may include a series of modules configured to implement the functions of UE 110 described herein. It should be understood that the various modules can be implemented as a combination of hardware and software, for example, Figure 2 The processor, memory, and transceiver of UE 110 are shown. Some example embodiments may also include additional modules to support additional and / or optional functions.

[0058] Figure 3 This is a schematic diagram of an example wireless access network node 120 according to certain example embodiments. The wireless access node 120 may include at least one transceiver 310, at least one processor 320, at least one memory 330, and at least one network interface 340. In some example embodiments, the transceiver 310 facilitates the transmission of and reception of wireless signals to and from a wireless device (e.g., UE 110) via a transmitter (Tx), receiver (Rx), and antenna. The processor 320 executes instructions to provide some or all of the functions described herein provided by the wireless access node 120. The memory 330 stores instructions to be executed by or for execution by the processor 320. In some embodiments, the processor 320 and memory 330 form a processing circuit. The network interface 340 can communicate signals or data to back-end network components (e.g., a core network or a radio network controller).

[0059] Processor 320 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the functions of wireless access node 120 or network node or entity 130, such as those described herein. In some embodiments, processor 320 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application-specific integrated circuits (ASICs), one or more hardware accelerators, one or more graphics processing units (GPUs), one or more tensor processing units (TPUs), one or more field-programmable gate arrays (FPGAs), and / or other logic.

[0060] The memory 330 is generally operable to store instructions, such as computer programs, software, applications including logic, rules, algorithms, code, tables, etc., and / or other instructions executable by the processor 320. Examples of the memory 330 include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., optical disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device storing information. For example, the memory 330 includes instructions that cause the processor 320 to perform processing according to any of the corresponding methods described herein.

[0061] In some example embodiments, the network interface 340 is communicatively coupled to the processor 320 and can refer to any suitable device operable to receive input from the wireless access network node 120, send output from the wireless access network node 120, perform suitable processing on the input or output or both, communicate with other devices, or any combination thereof. The network interface 340 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, for communication over a network.

[0062] Other example embodiments of the wireless access node 120 may include, in addition to Figure 3 Additional components beyond those shown may be responsible for providing certain aspects of the node's functionality, including any of the functions described herein and / or any additional functions (including any functions required to support the solutions described herein). Various different types of wireless access nodes or network nodes may include components that have the same physical hardware but are configured (e.g., through programming) to support different wireless access technologies, or may represent partially or completely different physical components.

[0063] and Figure 3Similar processors, interfaces, and memories described herein may be included in other nodes or entities (such as UE 110, radio access network node 120, etc.). Other radio access network nodes or entities may optionally include or exclude radio interfaces (such as...). Figure 3 (The transceiver described in the text).

[0064] In some example embodiments, the radio access network node 120 may include a series of modules configured to implement the functions of the radio access network node 120 described herein. It should be understood that the various modules can be implemented as a combination of hardware and software, for example, Figure 3 The wireless access node 120 shown includes a processor, memory, and transceiver. Some example embodiments may also include additional modules to support additional and / or optional functionality.

[0065] Refer again Figure 1 Network node or entity 130 may include an MC service server. Examples of MC service servers include an MCPTT server, a mission-critical video server, or a mission-critical data server. In some embodiments, the MC service server may also include the capabilities of all three of the following: an MCPTT server, a mission-critical video server, or a mission-critical data server. The MC service server may include at least one processor, at least one memory, and at least one network interface. The at least one memory may store instructions that, when executed by the at least one processor, cause the MC service server to perform or execute the following description. Figure 4 The method shown.

[0066] Turn now Figures 4 to 6 The flowchart illustrates the process of merging or combining ongoing temporary group communications (e.g., temporary) performed by the MC service server. As mentioned above, the MC service server is a server that provides MC services to the UE.

[0067] Figure 4 A flowchart illustrates a process performed by an MC service server providing mission-critical communications to merge ongoing temporary group communications. Merging temporary group communications means releasing one temporary group communication, and the participants of the released temporary group communication are added to another ongoing temporary group communication. The MC service server can be an MCPTT server, an MC data server, an MC video server, or a combination thereof.

[0068] The process of merging ongoing temporary group communications has several prerequisites. These prerequisites include the presence of an MC service server and two different UEs (e.g., the first MC user equipment, for example, ...). Figure 1 UE 110A, the second MC user equipment, for example, Figure 1UE110B, and the third MC user equipment, for example, Figure 1 At least two temporary group communications need to be in progress between UE 110C. The procedure described herein applies if the first MC user equipment and the second MC user equipment have a first ongoing temporary group communication with the MC service server, and if the first MC user equipment and the third MC user equipment are on another ongoing temporary group communication, and the first MC user equipment detects an input indicating that it is requesting to merge the first temporary group communication with the second temporary group communication. Furthermore, the user of the first MC user equipment must be authorized to merge the ongoing temporary group communication.

[0069] Figure 4 The process illustrated begins with the MC server receiving a request to merge temporary group communications from the first MC user equipment (box 401). Such a request is initiated, for example, when a user of the first MC user equipment wishes to merge or combine two ongoing temporary group calls (or temporary group data or video communications). For example, a city mayor might be using a UE to conduct a first ongoing temporary group call with police and a second ongoing temporary group call with firefighters. For efficiency and speed in an emergency response, the two ongoing temporary calls need to be merged so that all participants in the first ongoing temporary group call can listen to the second temporary group call.

[0070] In some embodiments, a request to merge two temporary group communications may include at least one of an identifier of a first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an identifier of the second temporary group communication. For example, a request to merge temporary group communications may include the identifier of the first MC user equipment, the identifier of the first temporary group communication, and the identifier of the second temporary group communication, but may optionally include only the function alias of the first MC user equipment. It should be noted that the identifier and function alias of the first MC user equipment may be specific to and associated with the first MC user equipment, but may also be user-specific, that is, it may be the identifier and function alias of the user of the first MC user equipment.

[0071] The method proceeds to box 402, where the MC service server verifies whether the first MC user device (or its user) is authorized to merge two ongoing temporary group communications. For example, each MC user device (or each MC user device's user) can be assigned an authorization level or parameter indicating whether the client is permitted to merge two ongoing temporary group communications.

[0072] If the MC service server can verify that the first MC user equipment is authorized to merge the first temporary group communication and the second temporary group communication, the MC service server transmits a merge temporary group communication response to the first MC user equipment (box 403).

[0073] In some embodiments, the merge temporary group communication response may include at least an identifier of the first MC user equipment, a functional alias of the first MC user equipment, an identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful. For example, the merge temporary group communication response may include the identifier of the first MC user equipment, the identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful, but may optionally include only the functional alias of the first MC user equipment. It should be noted that the identifier and functional alias of the first MC user equipment may be specific to and associated with the first MC user equipment, but may also be user-specific, that is, it may be the identifier and functional alias of the user of the first MC user equipment.

[0074] The MC service server continues to transmit a first temporary group communication release request (box 404) to the third MC user equipment to terminate the ongoing second temporary group communication and indicate that the temporary group communication will be merged. Typically, the first temporary group communication release request is the same as or similar to a group call release request, group data session release request, or group video session release request as defined in 3GPP TS 23.379, TS 23.281, or TS 23.282; however, the first temporary group communication release request also includes an identifier of the temporary group communication to be merged with another temporary group communication. It should be noted that for releasing or establishing temporary group communication within the process of merging temporary group communication described herein, procedures defined for releasing or establishing temporary group communication may apply in other cases. Therefore, the temporary group communication release request may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0075] The MC service server then receives the first temporary group communication release response from the third MC user equipment (box 405). Typically, the first temporary group communication release response is the same as or similar to the group call release response, group data session release response, or group video session release response defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that for procedures that release or establish temporary group communications within the process of merging at least two temporary group communications described herein, procedures defined for releasing or establishing temporary group communications in other cases may apply. Therefore, the temporary group communication release response may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0076] The MC service server transmits a second temporary group communication release request (box 406) to the first MC user equipment to terminate the ongoing second temporary group communication and merge the temporary group communication. Typically, the second temporary group communication release request is the same as or similar to the group call release request, group data session release request, or group video session release request defined in 3GPP TS 23.379, TS 23.281, or TS 23.282; however, the second temporary group communication release request includes an identifier of the temporary group communication to be merged with another temporary group communication. It should be noted that for releasing or establishing temporary group communication within the group communication merging described herein, the procedures defined for releasing or establishing temporary group communication in other cases may apply. Therefore, the temporary group communication release request may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0077] The MC service server then receives the second temporary group communication release response from the first MC user equipment (box 407). Typically, the second temporary group communication release response is the same as or similar to the group call release response, group data session release response, or group video session release response defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that for releasing or establishing temporary group communication within the procedures described herein for merging temporary group communication, procedures defined for releasing or establishing temporary group communication may apply in other cases. Therefore, the temporary group communication release response may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0078] It should also be noted that the processes in boxes 404 and 405, as well as 406 and 407, can be executed in different orders or in parallel.

[0079] In addition, the MC service server transmits a temporary group communication request (box 408) to the third MC user equipment for the first temporary group communication. Typically, the temporary group communication request is the same as or similar to a group call request, group data session request, or group video session request as defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that the procedures defined for releasing or establishing temporary group communication in other cases may apply to the release or establishment of temporary group communication within the group communication merge described herein. Therefore, regarding the content of the temporary group communication request, we refer to the standards mentioned herein, particularly version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0080] Finally, the MC service server receives a temporary group communication response (box 409) from the third MC user equipment for the first temporary group communication. Typically, the temporary group communication response is the same as or similar to the group call response, group data session response, or group video session response defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that for releasing or establishing temporary group communication within the group communication merge described herein, the procedures defined for releasing or establishing temporary group communication may apply in other cases. Therefore, the temporary group communication response may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0081] In some embodiments, the process performed by the MC service server may further include transmitting a temporary group communication notification to the first MC user equipment to indicate that a third MC user equipment has been added to the first temporary group communication. Furthermore, in some other embodiments, the MC service server may also transmit temporary group communication member notifications to the first MC user equipment, the second MC user equipment, and the third MC user equipment to indicate the members of the first temporary group communication.

[0082] Figure 5 A flowchart of a process performed by a first MC user equipment according to an embodiment of this disclosure is now presented. The first MC user equipment is a UE that initiates the merging of temporary group communications. Merging temporary group communications means releasing one temporary group communication and adding the participants of the released temporary group communication to another ongoing temporary group communication. The process of merging ongoing group communications has some preconditions. At least two temporary group communications need to be in progress. Therefore, we consider here at least the first MC user equipment, for example, Figure 1 UE 110A, the second MC user equipment, for example, Figure 1 UE 110B, and the third MC user equipment, for example, Figure 1The procedure described herein applies if the first MC user equipment and the second MC user equipment are on a first ongoing temporary group communication, if the first MC user equipment and the third MC user equipment are on another ongoing temporary group communication, and if the user of the first MC user equipment actively requests to merge the first temporary group communication with the second temporary group communication. Furthermore, the user of the first MC user equipment must be authorized to merge the ongoing group communication.

[0083] Therefore, the process for the first MC user equipment begins with the first MC user equipment transmitting a merge temporary group communication request to the MC service server to merge the first temporary group communication and the second temporary group communication (box 501). In some embodiments, the merge temporary group communication request may include at least one of the following: an identifier of the first MC user equipment; a functional alias of the first MC user equipment; an identifier of the first temporary group communication; and an identifier of the second temporary group communication. For example, the merge temporary group communication request may include the identifier of the first MC user equipment, the identifier of the first temporary group communication, and the identifier of the second temporary group communication; however, in some embodiments, the merge temporary group communication request may only include the functional alias of the first MC user equipment. It should be noted that the identifier of the first MC user equipment and the functional alias of the first MC user equipment may be specific to and associated with the first MC user equipment, but they may also be user-specific, that is, they may be the identifier of the user of the first MC user equipment and the functional alias of the user of the first MC user equipment.

[0084] Then the first MC user equipment receives the merge temporary group communication response from the MC service server (box 502), which confirms that it has successfully received the merge temporary group communication request.

[0085] In some embodiments, the merge temporary group communication response may include at least an identifier of the first MC user equipment, a functional alias of the first MC user equipment, an identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful. For example, the merge temporary group communication response may include the identifier of the first MC user equipment, the identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful. However, in some embodiments, the merge temporary group communication response may only include the functional alias of the first MC user equipment. It should be noted that the identifier and functional alias of the first MC user equipment may be specific to and associated with the first MC user equipment, but they may also be user-specific, that is, they may be the identifier and functional alias of the user of the first MC user equipment.

[0086] Since the second temporary group communication should be terminated, the first MC user equipment receives a temporary group communication release request from the MC service server to release the second temporary communication (box 503). Typically, the temporary group communication release request is the same as or similar to the group call release request, group data session release request, or group video session release request defined in 3GPP TS 23.379, TS 23.281, or TS 23.282; however, the temporary group communication release request includes an identifier of the first temporary group communication to be merged with the second temporary group communication. It should be noted that for releasing or establishing temporary group communication within the process of merging temporary group communication described herein, procedures defined for releasing or establishing temporary group communication may apply in other cases. Therefore, the temporary group communication release request may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0087] Finally, the MC user equipment transmits a temporary group communication release response to the MC service server (box 504). Typically, the temporary group communication release response is the same as or similar to the group call release response, group data session release response, or group video session release response defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that for releasing or establishing temporary group communication within the procedures described herein for merging temporary group communication, procedures defined for releasing or establishing temporary group communication may apply in other cases. Therefore, additional information that may be included in the temporary group communication release response is described in versions 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0088] In some embodiments, the first MC user equipment may also receive a temporary group communication notification from the MC service server to indicate that a third MC user equipment has been added to the first temporary group communication. In some other embodiments, the first MC user equipment may also, or additionally, receive a temporary group communication member notification from the MC service server to indicate the members of the first temporary group communication. In response to receiving a temporary group communication release request, the first MC user equipment may also, or additionally, notify the first MC user equipment that the user's second temporary group communication has been terminated and merged with the first temporary group.

[0089] Now about Figure 6This describes the process performed by a third MC user equipment. The third MC user equipment is a UE (or one of several UEs) that should move from a second temporary group communication to a first temporary group communication when two temporary group communications are merged or combined by the MC service server. Merging temporary group communications means releasing one temporary group communication, and the participants of the released temporary group communication are added to another ongoing temporary group communication. The process for merging or combining at least two ongoing group communications has certain preconditions. The at least two group communications need to be in progress. Therefore, we consider at least a first MC user equipment here, for example, Figure 1 UE 110A, the second MC user equipment, for example, Figure 1 UE 110B, and the third MC user equipment, for example, Figure 1 The procedure described herein applies if the first MC user equipment and the second MC user equipment are on a first ongoing temporary group communication, if the first MC user equipment and the third MC user equipment are on another ongoing temporary group communication, and if the user of the first MC user equipment actively requests to merge the first temporary group communication with the second temporary group communication. Furthermore, the user of the first MC user equipment must be authorized to merge the ongoing group communication.

[0090] The procedure for the third MC user equipment begins with receiving a temporary group communication release request from the MC service server to release the second temporary group communication (box 601). Typically, the temporary group communication release request is the same as or similar to the group call release request, group data session release request, or group video session release request defined in 3GPP TS 23.379, TS 23.281, or TS 23.282; however, the temporary group communication release request includes an identifier for the temporary group communication to be merged. It should be noted that for releasing or establishing temporary group communication within the procedure for merging temporary group communication described herein, procedures defined for releasing or establishing temporary group communication may apply in other cases. Therefore, the temporary group communication release request may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0091] The third MC user equipment then transmits a temporary group communication release response to the MC service server (box 602). Typically, the temporary group communication release response is the same as or similar to the group call release response, group data session release response, or group video session release response defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that for releasing or establishing temporary group communication within the group communication merge described herein, the procedures defined for releasing or establishing temporary group communication may apply in other cases. Therefore, the temporary group communication release response may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0092] Since not only must the second temporary group communication be terminated, but the third MC user equipment must also join the first temporary group communication, the third MC user equipment also receives a temporary group communication request from the MC service server to enter the first temporary group communication (box 603). Typically, the temporary group communication request is the same as or similar to a group call request, group data session request, or group video session request as defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that the procedures defined for releasing or establishing temporary group communication in other cases can be applied to the release or establishment of temporary group communication during the temporary group communication merging described herein. Therefore, the temporary group communication request may include additional information, such as the information described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0093] Finally, the MC user equipment sends a temporary group communication response (box 604) to the MC service server for the first temporary group communication. Typically, the temporary group communication response is the same as or similar to the group call response, group data session response, or group video session response defined in 3GPP TS 23.379, TS 23.281, or TS 23.282. It should be noted that the procedures defined for releasing or establishing temporary group communication in other cases can be applied to the release or establishment of temporary group communication during the temporary group communication merging process described herein. Therefore, the temporary group communication response may include additional information, such as that described in version 19.0.0 of 3GPP TS 23.379, TS 23.281, and TS 23.282.

[0094] Figure 7 The process of merging temporary group calls according to an example embodiment is shown. Figure 7The entities involved in the process shown are MCPTT server 700, MCPTT client 1 701 (e.g., the MCPTT client of the first MC user equipment), MCPTT client 2 702 (e.g., the MCPTT client of the second MC user equipment), and MCPTT client 3 703 (e.g., the MCPTT client of the third MC user equipment). Two temporary group calls have been established and are in progress, as shown. Figure 7 The two solid-line boxes at the beginning of the process illustrate temporary group call 1 between MCPTT client 1 701 and MCPTT client 2 702, both supported by MCPTT server 700, and temporary group call 2 between MCPTT client 2 702 and MCPTT client 3 703, both supported by MCPTT server 700.

[0095] At point 711, MCPTT client 1 701 sends a request to MCPTT server 700 to merge two ongoing temporary group calls. MCPTT client 1 701 sends a merge temporary group call request to MCPTT server 700 to transfer temporary group participants from temporary group call 2 to temporary group call 1.

[0096] MCPTT server 700 then verifies at 712 whether MCPTT client 1 701 is authorized to merge two ongoing temporary group calls into a single temporary group call. If MCPTT client 1 701 is authorized to merge two ongoing temporary group calls into a single temporary group call, MCPTT server 700 sends a merge temporary group call response to MCPTT client 1 701 at 713.

[0097] MCPTT server 700 then sends a temporary group call release request (which includes an identifier of the temporary group call to be released and merged) to MCPTT client 3 703 at 714a to cancel temporary group call 2. In some embodiments, the MCPTT user of MCPTT client 3 703 may be notified that temporary group call 2 has been canceled, as shown at 714b. MCPTT client 3 703 sends a temporary group call release response to MCPTT server 700 at 714c.

[0098] MCPTT server 700 sends a temporary group call release request to MCPTT client 1 701 at 715a to cancel temporary group call 2. In some embodiments, the MCPTT user of MCPTT client 1 701 may be notified that the temporary group call has been canceled, as shown at 715b. MCPTT client 1 701 sends a temporary group call release response to MCPTT server 700 at 715c.

[0099] At 716a, MCPTT server 700 sends a temporary group call request to MCPTT client 3 703 to add an MCPTT user of MCPTT client 3 703 as a new participant in temporary group call 1. In some embodiments, the MCPTT user of MCPTT client 3 703 may be notified, which is again shown at 716b. At 716c, MCPTT client 3 703 sends a temporary group call response to MCPTT server 700.

[0100] In some embodiments, MCPTT server 700 may notify MCPTT users of MCPTT client 1 701 about users and / or clients added to the ongoing temporary group call 1. This notification, as shown in 717, may be sent multiple times by MCPTT server 700 to MCPTT users of MCPTT client 1 701 during a call when MCPTT users and / or clients join the temporary group call. Temporary group call 1 is then established between participants of the previous temporary group call 1 and participants of the previous temporary group call 2. Finally, in some embodiments, MCPTT server 700 may notify participants of changes to the participant list of the ongoing temporary group call 1, as shown in 718.

[0101] exist Figure 7 In this embodiment, the information elements included in the merged temporary group call request can be in the form of Table 1 below: Table 1:

[0102] exist Figure 7 In this embodiment, the information elements contained in the merged temporary group call response can be in the form of Table 2 below: Table 2:

[0103] In addition, the information elements included in the temporary group call release request can take the form shown in Table 3 below: Table 3:

[0104] Figure 8 A process for temporary data communication according to an example embodiment is shown. Figure 8 The entities involved in the process shown are MCData server 800, MCData client 1 801 (e.g., the first MC user device), MCData client 2 802 (e.g., the second MC user device), and MCData client 3 803 (e.g., the third MC user device). Figure 8As shown in the two solid-line boxes at the beginning, two ongoing temporary group data connections or data sessions (e.g., PDU sessions) have been established: Temporary Group Data Communication 1 between MCData Client 1 801 and MCData Client 2 802, supported by MCData Server 800, and Temporary Group Data Communication 2 between MCData Client 1 801 and MCData Client 3 803, supported by MCData Server 800.

[0105] At point 811, a request to merge two ongoing temporary data communications is transmitted from MCData client 1 801 to MCData server 800. MCData client 1 801 sends a request to merge temporary group data communications to MCData server 800 to transfer temporary group participants from temporary group data communication 2 to temporary group data communication 1.

[0106] Then, at 812, MCData server 800 verifies whether MCData client 1 801 is authorized to merge two ongoing temporary group data communications into a single temporary group data communication. If MCData client 1 801 is authorized to merge two ongoing temporary group data communications into a single temporary group data communication, then MCData server 800 sends a merge temporary group data communication response to MCData client 1 801 at 813.

[0107] The MCData server 800 also sends a temporary group data communication release request to the MCData client 3 803 at 814a. This request includes an identifier of the temporary group data communication to be released, in order to cancel temporary group data communication 2. In some embodiments, the MCPTT user of the MCData client 3 803 can be notified that temporary group data communication 2 has been canceled, as shown at 814b. The MCData client 3 803 sends a temporary group data communication release response to the MCData server 800 at 814c.

[0108] The MCData server 800 sends a temporary group data communication release request to the MCData client 1 801 at 815a to cancel the temporary group data communication 2. In some embodiments, the MCData user of the MCData client 1 801 can be notified that the temporary group data communication has been canceled, as shown at 815b. The MCData client 1 801 sends a temporary group data communication release response to the MCData server 800 at 815c.

[0109] The MCData server 800 sends a temporary group data communication request to the MCData client 3 803 at 816a to add the MCData user of the MCData client 3 803 as a new participant in the temporary group data communication 1. In some embodiments, the MCData user of the MCData client 3 803 can be notified, as shown again at 816b. The MCData client 3 803 sends a temporary group data communication response to the MCData server 800 at 816c.

[0110] In some embodiments, the MCData server 800 may notify MCData users of MCData client 1 801 of users and / or clients who have been added to the ongoing temporary group data communication 1. This notification (as shown in 817) may be sent multiple times by the MCData server 800 to users of MCData client 1 801 during data communication as users and / or clients join the temporary group data communication. Temporary group data communication 1 is then established between participants of the previous temporary group data communication 1 and participants of the previous temporary group data communication 2. Finally, in some embodiments, the MCData server 800 may notify participants of changes to the participant list of the ongoing temporary group data communication 1, as shown in 818.

[0111] exist Figure 8 In the embodiments, the information elements included in the merge temporary group data communication request can take the form of Table 4 below: Table 4:

[0112] exist Figure 8 In the embodiments, the information elements included in the merged temporary group data communication response can take the form shown in Table 5 below: Table 5:

[0113] In addition, the information elements included in the temporary group data communication release request can take a form similar to Table 3.

[0114] Figure 9 A process for merging temporary group video communications is illustrated according to an example embodiment. Figure 9 The entities involved in the process shown are MCVideo server 900, MCVideo client 1 901 (e.g., a first MC user device), MCVideo client 2 902 (e.g., a second MC user device), and MCVideo client 3 903 (e.g., a third MC user device). Figure 9As shown in the two solid boxes at the beginning, two temporary group data connections or data sessions (e.g., PDU sessions) have been established and are in progress: temporary group video communication 1 between MCVideo client 1 901 and MCVideo client 2 902, supported by MCVideo server 900, and temporary group video communication 2 between MCVideo client 1 901 and MCVideo client 3 903, supported by MCVideo server 900. In the case of temporary group video communication, video communication may also involve (video) calls and have similar properties.

[0115] At position 911, MCVideo client 1 901 sends a request to MCVideo server 900 to merge two ongoing temporary group video communications. MCVideo client 1 901 sends a merge temporary group call request to MCVideo server 900 in order to transfer temporary group participants from temporary group video communication 2 to temporary group video communication 1.

[0116] MCVideo server 900 then verifies at 912 whether MCVideo client 1 901 is authorized to merge two ongoing temporary group video communications into a single temporary group video communication. If MCVideo client 1 901 is authorized to merge two ongoing temporary group video communications into a single temporary group video communication, MCVideo server 900 sends a merge temporary group call response to MCVideo client 1 901 at 913.

[0117] At 914a, MCVideo server 900 sends a temporary group call release request to MCVideo client 3 903, the request including an identifier of the temporary group video communication to be released, to cancel temporary group video communication 2. In some embodiments, a user of the UE including MCVideo client 3 903 can be notified that temporary group video communication 2 has been canceled, as shown at 914b. At 914c, MCVideo client 3 903 sends a temporary group call release response to MCVideo server 900.

[0118] At 915a, MCVideo server 900 sends a temporary group call release request to MCVideo client 1 901 to cancel the temporary group video communication 2. In some embodiments, the user of MCVideo client 1 901 may be notified that the temporary group video communication has been canceled, as shown at 915b. At 915c, MCVideo client 1 901 sends a temporary group call release response to MCVideo server 900.

[0119] At 916a, MCVideo server 900 sends a temporary group video communication request to MCVideo client 3 903 to add the MCData user of MCVideo client 3 903 as a new participant in temporary group video communication 1. In some embodiments, the user of MCVideo client 3 903 may be notified, which is again shown at 916b. At 916c, MCVideo client 3 903 sends a temporary group call response to MCVideo server 900.

[0120] In some embodiments, the MCVideo server 900 may notify users of MCVideo client 1 901 about users and / or clients added to the ongoing temporary group video communication 1. This notification (as shown at 917) may be sent multiple times by the MCVideo server 900 to users of MCVideo client 1 901 during the video communication as MCData users and / or clients join the temporary group video communication. Temporary group video communication 1 is then established between participants of the previous temporary group video communication 1 and participants of the previous self-organized video communication 2. Finally, in some embodiments, the MCVideo server 900 may notify participants at 918 about changes to the list of participants in the ongoing temporary group video communication 1.

[0121] exist Figure 9 In this embodiment, the information elements included in the merged temporary group call request (for video calls) can take the form shown in Table 6 below: Table 6:

[0122] exist Figure 9 In this embodiment, the information elements included in the merged temporary group call response (for video calls) can take the form shown in Table 7 below: Table 7:

[0123] In addition, the information elements (for video calls) included in the temporary group call release request can take a form similar to Table 3.

[0124] For details regarding the operability and / or functionality of the MC server, the first, second, or third MC user equipment (or its units and / or components) according to some embodiments of the subject matter of this disclosure, please refer to the in conjunction with... Figures 1 to 9 The above description of any one of the above. The MC server, the first, second, or third MC user equipment may include components for execution and / or may be configured to execute respectively in Figure 4-6 The method described in [the document / document].

[0125] It should be understood that the device may include or be coupled to other units or modules, such as radio components or radio heads for transmission and / or reception. Although the device has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0126] It should be noted that although the embodiments have been described in conjunction with LTE and 5G NR, similar principles can be applied to other networks and communication systems that require forced rapid connection re-establishment. Therefore, although some embodiments have been described above by way of example with reference to certain example architectures of wireless networks, technologies, and standards, the embodiments can be applied to any other suitable form of communication system besides those shown and described herein.

[0127] It should also be noted that while exemplary embodiments have been described above, several changes and modifications may be made to the disclosed solutions without departing from the scope of this disclosure.

[0128] Generally, various exemplary embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects of the subject matter of this disclosure can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the subject matter of this disclosure is not limited thereto. While various aspects of the subject matter of this disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that these blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0129] Example embodiments of the subject matter of this disclosure can be implemented by computer software executable by a mobile device's data processor, such as in a processor entity, or by hardware, or by a combination of software and hardware. Computer software or programs, also known as program products, include software routines, applets, and / or macros, and can be stored in any device-readable data storage medium, and they include program instructions for performing a specific task. A computer program product may include one or more computer-executable components that, when the program runs, are configured to perform the embodiment. The one or more computer-executable components may be at least one piece of software code or a portion thereof.

[0130] Furthermore, it should be noted that any block in the logical flow diagram can represent a program step, or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. Software can be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants, and CDs. These physical media are non-transient media.

[0131] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), FPGAs, gate-level circuits, and processors based on multi-core processor architectures, as non-limiting examples.

[0132] Example embodiments of the subject matter of this disclosure can be practiced in various components such as integrated circuit modules. The design of integrated circuits is largely a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready for etching and formation on a semiconductor substrate.

[0133] The foregoing description provides a complete and informative description of exemplary embodiments of the subject matter of this disclosure by way of non-limiting example. However, various modifications and adaptations may become apparent to those skilled in the art when reading the foregoing description in conjunction with the accompanying drawings and appended claims. Nevertheless, all such and similar modifications to the teachings of the invention will still fall within the scope of the subject matter of this disclosure as defined in the appended claims. Indeed, there are other embodiments that include combinations of one or more embodiments with any other embodiments discussed above.

Claims

1. A mission-critical MC service server, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to perform at least the following: Receive a merge temporary group communication request from the first MC user equipment to merge the first temporary group communication and the second temporary group communication; Verify whether the first MC user equipment is authorized to merge the first temporary group communication and the second temporary group communication; Transmit a merged temporary group communication response to the first MC user equipment; Transmit a first temporary group communication release request to the third MC user equipment to release the second temporary group communication; Receive a first temporary group communication release response from the third MC user equipment; Transmit a second temporary group communication release request to the first MC user equipment to release the second temporary group communication; Receive the second temporary group communication release response from the first MC user equipment; Transmit a temporary group communication request for the first temporary group communication to the third MC user equipment; as well as Receive temporary group communication response from the third MC user equipment.

2. The MC service server according to claim 1, wherein the instructions, when executed by the at least one processor, further cause the MC service server to perform: Transmit a temporary group communication notification to the first MC user equipment to indicate that the third MC user equipment has been added to the first temporary group communication.

3. The MC service server according to claim 1 or claim 2, wherein the instructions further cause the device to perform: Transmit temporary group communication member notifications to the first MC user equipment, the second MC user equipment, and the third MC user equipment to indicate the members of the first temporary group communication.

4. The MC service server according to any one of claims 1 to 3, wherein the merged temporary group communication request includes at least one of the following: the identifier of the first MC user equipment, the function alias of the first MC user equipment, the identifier of the first temporary group communication, and the identifier of the second temporary group communication.

5. The MC service server of claim 4, wherein the merged temporary group communication response includes at least one of the following: the identifier of the first MC user equipment, the function alias of the first MC user equipment, the identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

6. A first-critical-mission MC user equipment (UE), comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the first MC UE to at least execute: Transmit a request to merge temporary group communications to the MC service server to merge the first temporary group communications and the second temporary group communications; Receive a merged temporary group communication response from the MC service server; Receive a temporary group communication release request from the MC service server to release the second temporary communication; as well as Transmit a temporary group communication release response to the MC service server.

7. The first MC UE according to claim 6, wherein the instruction further causes the device to perform: Receive a temporary group communication notification from the MC service server to indicate that the third MC user equipment has been added to the first temporary group communication.

8. The first MC UE according to claim 6 or claim 7, wherein the instruction further causes the device to perform: Receive temporary group communication member notifications from the MC service server to indicate the members of the first temporary group communication.

9. The first MC UE according to any one of claims 6 to 8, wherein the instructions further cause the device to perform: In response to receiving the temporary group communication release request, the user of the device is notified that the second temporary group communication has been terminated and merged with the first temporary group.

10. The first MC UE according to any one of claims 6 to 9, wherein the merged temporary group communication request includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an identifier of the second temporary group communication.

11. The first MC UE of claim 10, wherein the merged temporary group communication response includes at least one of the following: the identifier of the first MC user equipment, the function alias of the first MC user equipment, the identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

12. A third mission-critical (MC) user equipment (UE), comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to perform at least the following: Receive a temporary group communication release request from the MC service server to release the second temporary group communication between the third MC UE and the first MC UE; Transmit a temporary group communication release response to the MC service server; Receive a temporary group communication request from the MC service server to enter the first temporary group communication established between the first MC UE and the second MC UE; as well as Transmit a temporary group communication response to the MC service server.

13. The third MC UE of claim 12, wherein the instructions further cause the device to perform: Receive temporary group communication member notification from the MC service server, which indicates the members of the first temporary group communication.

14. The third MC UE according to claim 12 or claim 13, wherein the instructions further cause the device to perform: In response to receiving the temporary group communication release request, the user of the device is notified that the second temporary group communication has been terminated and merged with the first temporary group.

15. The third MC UE of claim 14, wherein the instructions further cause the device to perform: In response to receiving the temporary group communication request, the user of the device is notified that the first temporary group communication has been established.

16. A method executed by a mission-critical (MC) service server, the method comprising: Receive a merge temporary group communication request from the first MC user equipment to merge the first temporary group communication and the second temporary group communication; Verify whether the first MC user equipment is authorized to merge the first temporary group communication and the second temporary group communication; Transmit a merged temporary group communication response to the first MC user equipment; Transmit a first temporary group communication release request to the third MC user equipment to release the second temporary group communication; Receive a first temporary group communication release response from the third MC user equipment; Transmit a second temporary group communication release request to the first MC user equipment to release the second temporary group communication; Receive the second temporary group communication release response from the first MC user equipment; Transmit a temporary group communication request for the first temporary group communication to the third MC user equipment; as well as Receive temporary group communication response from the third MC user equipment.

17. The method of claim 16, further comprising: Transmit a temporary group communication notification to the first MC user equipment to indicate that the third MC user equipment has been added to the first temporary group communication.

18. The method according to claim 16 or claim 17, further comprising: Transmit temporary group communication member notifications to the first MC user equipment, the second MC user equipment, and the third MC user equipment to indicate the members of the first temporary group communication.

19. The method according to any one of claims 16 to 18, wherein the merged temporary group communication request includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an identifier of the second temporary group communication.

20. The method of claim 19, wherein the merged temporary group communication response includes at least one of the following: the identifier of the first MC user equipment, the function alias of the first MC user equipment, the identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

21. A method executed by a first mission-critical (MC) user equipment, the method comprising: Transmit a request to merge temporary group communications to the MC service server in order to merge the first temporary group communications and the second temporary group communications; Receive a merged temporary group communication response from the MC service server; Receive a temporary group communication release request from the MC service server to release the second temporary communication; as well as Transmit a temporary group communication release response to the MC service server.

22. The method of claim 21, further comprising: Receive a temporary group communication notification from the MC service server to indicate that the third MC user equipment has been added to the first temporary group communication.

23. The method according to claim 21 or claim 22, further comprising: Receive temporary group communication member notifications from the MC service server to indicate the members of the first temporary group communication.

24. The method according to any one of claims 21 to 23, further comprising: In response to receiving the temporary group communication release request, the user of the device is notified that the second temporary group communication has been terminated and merged with the first temporary group.

25. The method according to any one of claims 21 to 24, wherein the merged temporary group communication request includes at least one of the following: an identifier of the first MC user equipment, a function alias of the first MC user equipment, an identifier of the first temporary group communication, and an identifier of the second temporary group communication.

26. The method of claim 25, wherein the merged temporary group communication response includes at least one of the following: the identifier of the first MC user equipment, the function alias of the first MC user equipment, the identifier of the first temporary group communication, and an indication of whether the merge of the first temporary group communication and the second temporary group communication was successful.

27. A method performed by a third critical mission (MC) user equipment (UE), the method comprising: Receive a temporary group communication release request from the MC service server to release the second temporary group communication between the third MC UE and the first MC UE; Transmit a temporary group communication release response to the MC service server; Receive a temporary group communication request from the MC service server to join the first temporary group communication established between the first MC UE and the second MC UE; as well as Transmit a temporary group communication response to the MC service server.

28. The method of claim 27, further comprising: Receive temporary group communication member notifications from the MC service server to indicate the members of the first temporary group communication.

29. The method according to claim 27 or claim 28, further comprising: In response to receiving the temporary group communication release request, the user of the device is notified that the second temporary group communication has been terminated and merged with the first temporary group.

30. The method of claim 29, further comprising: In response to receiving the temporary group communication request, the user of the device is notified that the first temporary group communication has been established.

31. A computer program product comprising program instructions stored on a computer-readable medium, which, when executed on a computer, perform the method of any one of claims 16 to 30.

32. A computer-readable medium comprising instructions that, when executed by at least one processor of a mission-critical user equipment, cause the mission-critical user equipment to perform the method of any one of claims 16 to 30.

Images